Message scheduling method and apparatus
By employing multiple time-domain resource allocation sets and adjusting parameters like K2 and Δ, the method addresses processing delays in Rel 18 eRedCap devices, ensuring timely message transmission and enhancing network scheduling flexibility.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- HUAWEI TECH CO LTD
- Filing Date
- 2024-04-23
- Publication Date
- 2026-05-19
AI Technical Summary
Rel 18 eRedCap terminal devices face challenges in processing messages due to their limited processing power, leading to potential delays in uplink transmissions when using existing TDRA tables designed for legacy devices, resulting in incomplete message processing before scheduled transmission.
Implementing multiple time-domain resource allocation sets to accommodate different types of terminal devices, allowing each type to process and transmit messages in a timely manner by adjusting parameters such as K2 and Δ based on pre-configuration conditions, ensuring adequate processing time for Rel 18 eRedCap devices.
Enhances network scheduling flexibility by enabling Rel 18 eRedCap devices to process and send messages promptly, aligning with their processing capabilities, thereby improving transmission efficiency.
Smart Images

Figure 2026516136000001_ABST
Abstract
Description
[Technical Field]
[0001] This application relates to the field of communication technology, and more particularly to a message scheduling method and apparatus. [Background technology]
[0002] (Cross-reference to related applications) This application claims priority to Chinese Patent Application No. 20231054136.4, filed with the State Intellectual Property Administration of China on 12 May 2023 and titled "MESSAGE SCHEDULING METHOD AND APPARATUS," which is incorporated herein by reference in its entirety.
[0003] With the evolution of mobile communication technology, multiple types of terminal devices have been defined. Different types of terminal devices have different functions. For example, in new radio (NR) systems, the Release 18 (Rel 18) enhanced reduced capability (eRedCap) terminal device is newly defined. Compared to legacy terminal devices, Rel 18 eRedCap terminal devices support smaller radio frequency bandwidth, lower peak rates, and more.
[0004] Third Generation Partnership Project (3 rdIn a mobile communication network (Generation Partnership Project, 3GPP), resources used for data transmission by terminal devices are scheduled by the base station. For example, during the random access phase, after receiving a random access response (RAR) from the base station, the terminal device sends message 3 to the base station. When scheduling message 3, the base station may include a roll index in the RAR uplink grant. The roll index corresponds to parameters such as the slot offset and start symbol in the time domain resource allocation (TDRA) table. Based on the roll index, the terminal device can determine information such as the slot where message 3 is located and the number of symbols occupied. When scheduling message 3, the base station considers the time required by the terminal device to process the RAR. Thus, the interval between the scheduled message 3 and the RAR is greater than the time required by the terminal device to process the RAR.
[0005] However, due to the limited processing power of Rel 18 eRedCap terminal devices, the time required for the terminal device to process messages increases. The current TDRA table is designed for legacy terminal devices or terminal devices such as Rel 17 RedCap terminal devices. Therefore, when the TDRA table is used directly, when the base station schedules a terminal device to perform data transmission, the Rel 18 eRedCap terminal device may have to send an uplink message before it has finished processing the received message. Consequently, the Rel 18 eRedCap terminal device cannot perform uplink transmission based on the schedule. [Overview of the Initiative]
[0006] This application provides a message scheduling method and apparatus for scheduling multiple types of terminal devices.
[0007] According to a first aspect, the present application provides a message scheduling method. The method is performed by a terminal device or a module or chip within a terminal device. The method includes determining a target time domain resource allocation set, wherein the target time domain resource allocation set is a first time domain resource allocation set or a second time domain resource allocation set; receiving a first message, wherein the first message indicates a first parameter, the first parameter being for determining the interval between the first message and the second message in a time domain, and the first parameter being a parameter within the target time domain resource allocation set; and transmitting a second message based on the first parameter.
[0008] According to the method provided in this application, there are multiple time-domain resource allocation sets so that different time-domain resource allocation sets are used under different conditions. In this way, different types of terminal devices can be scheduled so that each type of terminal device can process scheduling messages and transmit scheduled messages in a timely manner, thereby improving the flexibility of network scheduling.
[0009] In possible implementations, determining the target time domain resource allocation set includes determining a first time domain resource allocation set as the target time domain resource allocation set when a pre-configuration condition is met, or determining a second time domain resource allocation set as the target time domain resource allocation set when the pre-configuration condition is not met. The pre-configuration condition includes at least one of the following:
[0010] The quantity of frequency domain resources for scheduling the first message is greater than a first threshold, or the first system message indicates random access resources used by a first type of terminal device to perform random access, and the first system message is from a network device.
[0011] In possible implementations, when the subcarrier interval of the channel where the first message resides is 15 kHz, the first threshold is 25 resource blocks, and when the subcarrier interval of the channel where the first message resides is 30 kHz, the first threshold is 12 resource blocks, or When the subcarrier spacing of the channel where the first message is located is 60 kHz, the first threshold is 6 resource blocks.
[0012] In a possible implementation, the first time-domain resource allocation set contains N values of parameter K2, each of which is greater than or equal to 2, and N is an integer greater than 0.
[0013] Since the value of parameter K2 is 2 or greater, the interval determined based on parameter K2 may be longer than the time required for the terminal device to process the first message so that the terminal device can send the second message in a timely manner.
[0014] In possible implementations, when the value of parameter K2 is equal to 2, the channel mapping mode of the PUSCH where the second message is located is type B, and the index S of the start symbol of the second message is 3 or greater.
[0015] Alternatively, when the value of parameter K2 is greater than 2, the channel mapping mode of the PUSCH where the second message is located is type A or type B, the index S of the starting symbol of the second message is greater than or equal to 0, or is within the range of the resource indication value RIV code of the index S of the starting symbol of the second message, and the length L of the symbol occupied by the second message is between 0 and 127.
[0016] In a possible implementation, when the target time domain resource allocation set is the first time domain resource allocation set, the interval determined based on the first parameter is greater than or equal to the second threshold, where the second threshold is the minimum time interval between the last symbol of the PDSCH carrying the first message and the first symbol of the PUSCH carrying the second message, and the second threshold corresponds to the first type of terminal device.
[0017] In a possible implementation, at least one of the first time-domain resource allocation set and the second time-domain resource allocation set comes from network devices.
[0018] In possible implementations, the first message is either a random access response message or a fallback random access response message.
[0019] The second message is message 3 in the random access procedure.
[0020] According to a second aspect, the present application provides a message scheduling method. The method is executed by a network device or a module or chip within the network device. The method includes determining a target time domain resource allocation set, where the target time domain resource allocation set is a first time domain resource allocation set or a second time domain resource allocation set, and transmitting a first message, where the first message indicates a first parameter, the first parameter is for determining an interval between a first message and a second message within a time domain, and the first parameter is a parameter within the target time domain resource allocation set, and receiving a second message.
[0021] In a possible implementation, determining the target time domain resource allocation set includes determining the first time domain resource allocation set as the target time domain resource allocation set when a preset condition is satisfied, or determining the second time domain resource allocation set as the target time domain resource allocation set when the preset condition is not satisfied. The preset condition includes at least one of the following.
[0022] The quantity of frequency domain resources for scheduling the first message is greater than a first threshold, or the resources occupied by a third message are random access resources used by a first type of terminal device for performing random access, the third message is a message before the first message, and the third message is from the terminal device.
[0023] In a possible implementation, when the subcarrier spacing of the channel where the first message is located is 15 kHz, the first threshold is 25 resource blocks; when the subcarrier spacing of the channel where the first message is located is 30 kHz, the first threshold is 12 resource blocks; or when the subcarrier spacing of the channel where the first message is located is 60 kHz, the first threshold is 6 resource blocks.
[0024] In a possible implementation, the first time-domain resource allocation set includes N values of parameter K2, each of the N values is greater than or equal to 2, and N is an integer greater than 0.
[0025] In a possible implementation, when the value of parameter K2 is equal to 2, the channel mapping mode of the PUSCH where the second message is located is type B, and the index S of the start symbol of the second message is greater than or equal to 3; or when the value of parameter K2 is greater than 2, the channel mapping mode of the PUSCH where the second message is located is type A or type B, and the index S of the start symbol of the second message is greater than or equal to 0; or it is the value range of the RIV code of the index S of the start symbol of the second message, and the length L of the symbol occupied by the second message is from 0 to 127.
[0026] In a possible implementation, when the target time-domain resource allocation set is the first time-domain resource allocation set, the interval determined based on the first parameter is greater than or equal to the second threshold, and the second threshold is the minimum time interval between the last symbol of the PDSCH carrying the first message and the first symbol of the PUSCH carrying the second message, and the second threshold corresponds to the first type of terminal device.
[0027] In a possible implementation, at least one of the first time-domain resource allocation set and the second time-domain resource allocation set is from a network device.
[0028] In a possible implementation, the first message is a random access response message or a fallback random access response message, and the second message is message 3 in the random access procedure.
[0029] According to a third aspect, the present application provides a message scheduling method. The method is performed by a terminal device or a module or chip within a terminal device. The method includes receiving a first message, wherein the first message contains a parameter K2, which is for determining the interval between the first message and a second message in a time domain, and the value of parameter K2 is greater than or equal to a third threshold when a preset condition is met, and transmitting a second message based on parameter K2.
[0030] According to the method provided in this application, when the pre-configured conditions are met, the value of parameter K2 is greater than or equal to a third threshold such that the interval between the scheduling message and the scheduled message is extended, and the first type of terminal device can also process the first message in a timely manner in order to send the second message.
[0031] In possible implementations, when the pre-configured conditions are not met, the value of parameter K2 is less than a third threshold.
[0032] In a possible implementation, the pre-configuration conditions include at least one of the following: the quantity of frequency domain resources for scheduling a first message is greater than a first threshold, or the first system message indicates a random access resource used by a first type of terminal device to perform random access, and the first system message is from a network device.
[0033] In possible implementations, when the subcarrier interval of the channel where the first message resides is 15 kHz, the first threshold is 25 resource blocks, and when the subcarrier interval of the channel where the first message resides is 30 kHz, the first threshold is 12 resource blocks, or When the subcarrier spacing of the channel where the first message is located is 60 kHz, the first threshold is 6 resource blocks.
[0034] In possible implementations, the third threshold is equal to 3.
[0035] A third threshold is 3, and the first type of terminal device can also process the first message and transmit the second message in a timely manner, such that the interval determined based on parameter K2 is greater than or equal to the minimum time interval between the last symbol of the PDSCH carrying the first message and the first symbol of the PUSCH carrying the second message.
[0036] According to a fourth aspect, the present application provides a message scheduling method. The method is performed by a network device or a module or chip within a network device. The method includes transmitting a first message, the first message containing a parameter K2, the parameter K2 for determining the interval between the first message and a second message in a time domain, and the value of parameter K2 being greater than or equal to a third threshold when a preset condition is met, and transmitting a second message.
[0037] In possible implementations, when the pre-configured conditions are not met, the value of parameter K2 is less than a third threshold.
[0038] In a possible implementation, the pre-configuration conditions include at least one of the following: the quantity of frequency domain resources for scheduling the first message is greater than a first threshold, or the resources occupied by the third message are random access resources used by a first type of terminal device to perform random access, the third message is the message preceding the first message, and the third message originates from a terminal device.
[0039] In a possible implementation, when the subcarrier spacing of the channel where the first message resides is 15 kHz, the first threshold is 25 resource blocks. When the subcarrier interval of the channel where the first message is located is 30 kHz, the first threshold is 12 resource blocks, or When the subcarrier spacing of the channel where the first message is located is 60 kHz, the first threshold is 6 resource blocks.
[0040] In possible implementations, the third threshold is equal to 3.
[0041] According to a fifth aspect, the present application provides a message scheduling method. The method is performed by a terminal device or a module or chip within a terminal device. The method includes receiving a first message, the first message indicating a parameter K2, where the parameter K2 and parameter Δ are for determining the interval between a first message and a second message in a time domain, where when a pre-defined condition is met, the value of parameter Δ is equal to a first value, or when the pre-defined condition is not met, the value of parameter Δ is equal to a second value, the first value is greater than the second value, and there is a correspondence between parameter Δ and the subcarrier interval of the channel in which the first message is located, and transmitting a second message based on the parameter K2 and parameter Δ.
[0042] According to the method provided in this application, when the pre-set conditions are met, the value of parameter Δ increases, so that the interval between the scheduling message and the scheduled message is extended, and the first type of terminal device can process the first message in a timely manner in order to send the second message.
[0043] In a possible implementation, the pre-configuration conditions include at least one of the following: the quantity of frequency domain resources for scheduling a first message is greater than a first threshold, or the first system message indicates a random access resource used by a first type of terminal device to perform random access, and the first system message is from a network device, or the first system message does not indicate a random access resource used by a first type of terminal device to perform random access, and the first system message is from a network device.
[0044] In possible implementations, when the subcarrier interval of the channel where the first message is located is 15 kHz, the first threshold is 25 resource blocks; when the subcarrier interval of the channel where the first message is located is 30 kHz, the first threshold is 12 resource blocks; or When the subcarrier spacing of the channel where the first message is located is 60 kHz, the first threshold is 6 resource blocks.
[0045] In possible implementations, the first value is 4 or greater when the pre-configured conditions are met and the subcarrier interval of the channel where the first message is located is 15 kHz or 30 kHz.
[0046] In possible implementations, if the pre-configured conditions are not met and the subcarrier interval of the channel where the first message is located is 15 kHz, the second value is 2. If the subcarrier interval of the channel where the first message is located is 30 kHz, the second value is 3.
[0047] According to a sixth aspect, the present application provides a message scheduling method. The method is performed by a network device or a module or chip within a network device. The method includes transmitting a first message, the first message comprising a parameter K2, where the parameter K2 and parameter Δ are for determining the interval between a first message and a second message in a time domain, where when a pre-configured condition is met, the value of parameter Δ is equal to a first value, or when the pre-configured condition is not met, the value of parameter Δ is equal to a second value, the first value is greater than the second value, and there is a correspondence between parameter Δ and the subcarrier interval of the channel in which the first message is located, and receiving a second message.
[0048] In a possible implementation, the pre-configuration conditions include at least one of the following: the quantity of frequency domain resources for scheduling the first message is greater than a first threshold, or the resources occupied by the third message are random access resources used by a first type of terminal device to perform random access; the third message is the message preceding the first message, the third message is from a terminal device, or the resources occupied by the third message are not random access resources used by a first type of terminal device to perform random access.
[0049] In possible implementations, when the subcarrier interval of the channel where the first message is located is 15 kHz, the first threshold is 25 resource blocks; when the subcarrier interval of the channel where the first message is located is 30 kHz, the first threshold is 12 resource blocks; or When the subcarrier spacing of the channel where the first message is located is 60 kHz, the first threshold is 6 resource blocks.
[0050] In possible implementations, the first value is 4 or greater when the pre-configured conditions are met and the subcarrier interval of the channel where the first message is located is 15 kHz or 30 kHz.
[0051] In possible implementations, if the pre-configured conditions are not met and the subcarrier interval of the channel where the first message is located is 15 kHz, the second value is 2. If the subcarrier interval of the channel where the first message is located is 30 kHz, the second value is 3.
[0052] According to the seventh aspect, embodiments of the present application provide a communication device. The device may be a terminal device or a module (e.g., a chip) used within a terminal device. The device has a function that implements a method in any one of the possible implementations of the first, third, or fifth aspects. The function may be implemented by hardware or by hardware running corresponding software. The hardware or software includes one or more modules corresponding to the function.
[0053] According to the eighth aspect, embodiments of the present application provide a communication device. The device may be a network device or a module (e.g., a chip) used within a network device. The device has a function that implements a method in any one of the possible implementations of the second, fourth, or sixth aspects. The function may be implemented by hardware or by hardware running corresponding software. The hardware or software includes one or more modules corresponding to the function.
[0054] According to the ninth aspect, an embodiment of the present application provides a communication device including a processor and memory. The memory is configured to store computer instructions. When the device is operated, the processor executes the computer instructions stored in memory to cause the device to perform a method in any one of the possible implementations of the first through sixth aspects.
[0055] According to the tenth aspect, an embodiment of the present application provides a communication device comprising units or means for performing any implementation step of the first to sixth aspects.
[0056] According to the eleventh aspect, an embodiment of the present application provides a communication device including a processor and an interface circuit. The processor is configured to communicate with another device via the interface circuit and to perform a method in any one of the possible implementations of the first to sixth aspects. There are one or more processors.
[0057] According to the twelfth aspect, an embodiment of the present application provides a communication device including a processor and memory. The processor is configured to call a program stored in memory and execute any implementation of the first through sixth aspects. The memory may be located inside or outside the device. In addition, there may be one or more processors.
[0058] According to the thirteenth aspect, embodiments of the present application further provide a computer-readable storage medium. The computer-readable storage medium stores instructions. When an instruction is executed on a communication device, a method in any one of the possible implementations of the first to sixth aspects is executed.
[0059] According to the fourteenth aspect, embodiments of the present application further provide a computer program product, which includes a computer program or instructions. When the instructions are executed on a communication device, a method in any one of the possible implementations of the first to sixth aspects is performed.
[0060] According to the fifteenth aspect, an embodiment of the present application further provides a chip including a processor configured to perform a method in any one of the possible implementations of the first to sixth aspects.
[0061] According to the sixteenth aspect, embodiments of the present application further provide a communication system, which includes terminal devices and network devices.
[0062] The terminal device is configured to perform a method in any one of the possible implementations of the first, third, or fifth embodiment.
[0063] The network device is configured to perform a method in any one of the possible implementations of the second, fourth, or sixth embodiment.
[0064] These and other aspects of this application will be understood more concisely and readily in the following description of embodiments. [Brief explanation of the drawing]
[0065] [Figure 1] This is a diagram of a mobile communication system applicable to one embodiment of this application. [Figure 2] This is a schematic flowchart of a message scheduling method according to one embodiment of this application. [Figure 3] This is a diagram showing the interval between messages according to one embodiment of the present application. [Figure 4] This is a schematic flowchart of a message scheduling method according to one embodiment of this application. [Figure 5] This is a schematic flowchart of a message scheduling method according to one embodiment of this application. [Figure 6] This is a schematic flowchart of an access method according to one embodiment of this application. [Figure 7] This is a diagram showing the structure of a communication device according to one embodiment of this application. [Figure 8] This is a diagram showing the structure of a communication device according to one embodiment of this application. [Modes for carrying out the invention]
[0066] The following describes the technical solutions in the embodiments of this application clearly and completely with reference to the accompanying drawings of the embodiments.
[0067] The communication methods provided in the embodiments of this application include, for example, the Internet of Things (IoT), the Narrowband Internet of Things (NB-IoT), Long Term Evolution (LTE), and the Fifth Generation (5 th This may apply to various mobile communication systems, such as 5G generation communication systems (e.g., 5G new radio (NR)), hybrid architectures of LTE and 5G, or new communication systems that may emerge in 6G or future communication developments. Alternatively, the communication system may be a machine-to-machine (M2M) network, a machine-type communication (MTC) network, or another network.
[0068] In this application, the names of messages, indication information, and fields in the following procedures are merely examples. As communication technology evolves, the names of messages, indication information, and fields in the following procedures may change. However, regardless of how the names change, as long as the meaning of the message, indication information, or field remains the same as in this application, the message, indication information, or field is within the scope of protection of this application. The sequence of steps in the following procedures are merely examples. In actual application, the sequence of steps in each procedure may be modified.
[0069] The methods and apparatus provided in the embodiments of this application are based on the same or similar technical concepts. Because the problem-solving principles of the methods and apparatus are similar, cross-referencing is permitted in the implementation of the apparatus and methods. Repeated descriptions are not provided.
[0070] To facilitate understanding of the embodiments of this application, the communication system shown in Figure 1 is first used as an example to illustrate in detail a communication system applicable to the embodiments of this application. Figure 1 is a diagram of a communication system applicable to a communication method according to one embodiment of this application. As shown in Figure 1, the communication system includes a network device and terminal devices 1 through 6. In the communication system, terminal devices 1 through 6 may transmit uplink data to the network device, and the network device may transmit downlink data from terminal device 1 to terminal device 6. Furthermore, the communication system may alternatively include terminal devices 4 through 6. In this case, in the communication system, the network device may transmit downlink data from terminal devices 4 and 6 to terminal device 5, which may then forward the downlink data to terminal devices 4 and 6.
[0071] In this embodiment of the present application, the network device may be an access network device within a wireless network. For example, the network device may be a radio access network (RAN) node that connects terminal devices to the wireless network, and may be referred to as an access network device. The network device includes, but is not limited to, evolved NodeB (eNB), radio network controller (RNC), NodeB (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home NodeB, HNB), baseband unit (BBU), access point (AP) in a wireless fidelity (Wi-Fi) system, radio relay node, radio backhaul node, transmission point (TP), transmission reception point (TRP), etc. Alternatively, the network device may be a network device within a 5G mobile communication system, for example, a next-generation NodeB (gNB), a transmission reception point (TRP), or a TP within an NR system, or one antenna panel or group of antenna panels (including multiple antenna panels) of a base station within a 5G mobile communication system. Alternatively, the network device may be a network node constituting a gNB or transmission point, for example, a BBU or a distributed unit (DU).
[0072] In some deployments, the gNB may include a central unit (CU) and a DU. The gNB may further include an active antenna unit (AAU). The CU implements some of the functions of the gNB, and the DU implements some of the functions of the gNB. For example, the CU is responsible for handling non-real-time protocols and services in order to implement the functions of the radio resource control (RRC) layer. The DU is responsible for handling physical layer protocols and real-time services, and for implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer.
[0073] The terminal device in the embodiments of this application may be a wireless terminal device capable of receiving scheduling and indication information from a network device. The terminal device may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc. Some examples of terminal devices include mobile phones, tablet computers, notebook computers, palmtop computers, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals for industrial control, wireless terminals for the Internet of Vehicles, wireless terminals for self-driving, wireless terminals for remote medical surgery, wireless terminals for smart grids, wireless terminals for transportation safety, wireless terminals for smart cities, wireless terminals for smart homes, device-to-device (D2D) communication terminals, vehicle-to-everything (V2X) communication terminals, intelligent vehicles, and telematics boxes (also known as vehicle-mounted transmission units). Examples include box (T-box), machine-to-machine / machine-type communication (M2M / MTC) terminal devices, and Internet of Things (IoT) terminal devices.
[0074] In embodiments of this application, the device configured to implement the functions of a terminal device may be a terminal device, or it may be a device capable of supporting a terminal device to implement the functions, such as a chip system, and the device may be installed in the terminal device. In the technical solutions provided in embodiments of this application, the technical solutions provided in embodiments of this application are illustrated by using an example in which the device configured to implement the functions of a terminal device is a terminal device.
[0075] In embodiments of this application, there may be multiple types of terminal devices. For example, the types of terminal devices may include legacy terminal devices, reduced capability (RedCap) terminal devices, enhanced RedCap (eRedCap) terminal devices, and the like. Legacy terminal devices may be NR Release 15 (Rel-15) terminal devices or NR Rel-16 terminal devices, but are not limited thereto. eRedCap terminal devices may alternatively be R18 eRedCap terminal devices.
[0076] In this application, the eRedCap terminal device may also be referred to as the first type of terminal device, and the legacy terminal device and the RedCap terminal device may also be referred to as the second type of terminal device.
[0077] In this application, the first type of terminal device may satisfy at least one of the following conditions:
[0078] 1. The radio frequency bandwidth of the first type of terminal device exceeds the maximum baseband processing bandwidth.
[0079] 2. The maximum transmission bandwidth supported by the first type of terminal device exceeds the maximum baseband processing bandwidth.
[0080] 3. The maximum scheduling bandwidth supported by the first type of terminal device exceeds the maximum baseband processing bandwidth.
[0081] 4. The first type of terminal device supports a peak data rate of a first value, and the first value may be 10 Mbps or 6 Mbps.
[0082] 5. The first type of terminal device operates in frequency range 1 (FR1).
[0083] 6. The first type of terminal device satisfies a maximum scheduling bandwidth of 20 MHz and satisfies the following constraints: the product of the maximum number of layers supported by the first type of terminal device, the maximum modulation order supported by the first type of terminal device, and the scale factor is 0.75 or 0.8 or greater, or v Layers Q m f ≥ Y (the value of Y can be 0.75 or 0.8). Layers Q represents the maximum number of layers supported by the first type of terminal device. m represents the maximum modulation sequence supported by the first type of terminal device, and f represents the scale factor, which is set by the network device.
[0084] 7. The first type of terminal device has a maximum number of physical resource blocks (PRBs) on a physical shared channel per uplink hop in a slot when the subcarrier spacing (SCS) is 15 kHz, and a maximum number of PRBs on a physical shared channel per uplink hop in a slot when the SCS is 30 kHz, and the product of the maximum number of layers supported by the first type of terminal device, the maximum modulation order supported by the first type of terminal device, and the scale factor is 3 or 3.2 or greater, or v Layers Qm It is a terminal device where f ≥ X (where X can be 3 or 3.2).
[0085] The maximum bandwidth supported by RedCap terminal devices in FR1 is 20 MHz, the maximum bandwidth supported by RedCap terminal devices in frequency range 2 (FR2) is 100 MHz, the maximum number of data radio bearers (DRBs) mandatorily supported by RedCap terminal devices is 8, the packet data convergence protocol sequence number size (PDCP SN SIZE) mandatorily supported by RedCap terminal devices is 12, the PDCP SN size optionally supported by RedCap terminal devices is 18, the radio link control amplitude modulation sequence number size (RLC AM SN SIZE) mandatorily supported by RedCap terminal devices is 12, the RLC AM SN size optionally supported by RedCap terminal devices is 18, and during operation in FR1, a RedCap terminal device supporting one receiving antenna has one downlink multiple-input multiple-output RedCap terminal devices support multiple-output (MIMO) layers and two receiving antennas. RedCap terminal devices support two downlink MIMO layers, and while operating in FR2, RedCap terminal devices always support two receiving antennas and one or two downlink MIMO layers. RedCap terminal devices support carrier aggregation (CA), multi-rate dual connectivity (MR-DC), dual protocol stack (DAPS), conditional primary / secondary cell addition / change (CPAC), and integrated access and backhaul.It does not support functions or capabilities related to backhaul, IAB, etc.
[0086] The first type of terminal device may have a first capability or a second capability. The first capability and the second capability may be defined in different ways.
[0087] The first capability and the second capability are defined as follows. A first type of terminal having the first capability is a terminal device that satisfies the constraint of ·Q Layers ·Q m ·f≧Y (the value of Y can be 0.75 or 0.8) and satisfies a maximum scheduling bandwidth of 20 MHz. A first type of terminal having the second capability, when the SCS is 15 kHz, the maximum number of RBs on the physical shared channel per uplink hop in a slot is 25 PRBs, and when the SCS is 30 kHz, the maximum number of RBs on the physical shared channel per uplink hop in a slot is 12 PRBs, and ·Q Layers ·Q m ·f≧X (the value of X can be 3 or 3.2).
[0088] The network architectures and service scenarios described in the embodiments of this application are intended to more clearly explain the technical solutions in the embodiments of this application and do not constitute limitations on the technical solutions provided in the embodiments of this application. Those skilled in the art can understand that due to the evolution of network architectures and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0089] For the sake of clarity, in this application, resources used by a first type of terminal to initiate random access, resources for transmitting a preamble sequence, or random access resources dedicated to a first type of terminal device are referred to as first random access resources, and resources used by a second type of terminal NR RedCap terminal device to initiate random access, resources for transmitting a preamble sequence, or random access resources dedicated to an NR RedCap terminal device are referred to as second random access resources.
[0090] In the embodiments of this application, the NR network scenario in a wireless communication network is used as an example to illustrate several scenarios. It should also be noted that the solutions in the embodiments of this application may be further applied to other wireless communication networks, and corresponding names may be replaced with the names of corresponding functions in other wireless communication networks.
[0091] When the following method procedure of this application is applied to the system shown in Figure 1, the network device or module or chip within the network device in Figure 1 may implement the method performed by the network device in the following procedure, and the terminal device or module or chip within the terminal device in Figure 1 may implement the method performed by the terminal device in the following procedure. It should be understood that the particular structure of the execution body of the method provided in the embodiments of this application is not particularly limited in the following embodiments, provided that a program recording the code of the method provided in the embodiments of this application can be executed to perform access in accordance with the method provided in the embodiments of this application. For example, the method may be implemented by a terminal device or a functional module within the terminal device that can call and execute a program, or by a network device or a functional module within the network device that can call and execute a program. The following uses only terminal devices or network devices as examples for illustrative purposes.
[0092] Figure 2 is a schematic flowchart of a message scheduling method according to one embodiment of this application. The method includes the following steps.
[0093] Step 201: The terminal device sends a random access request message to the network device.
[0094] In response, the network device receives a random access request message.
[0095] A random access request message may be message 1 (msg1) or message A (msgA) in a random access procedure.
[0096] If the network side configures a first random access resource for a first type of terminal device, the terminal device may send a random access request message by using the first random access resource, provided that the terminal device is of the first type.
[0097] A network device may configure a first random access resource by using a first system message. The specific process is not described.
[0098] This application is illustrated by using an example in which a terminal device accesses a network device using a random access procedure, and the network device uses a first message to schedule a second message. If this application is applied to a different scenario, step 201 may be performed instead.
[0099] Step 202: The network device sends the first message.
[0100] In response, the terminal device receives the first message.
[0101] The first message may be a message in response to a random access request message. In one embodiment, the first message is a message scheduled by using a random access (RA) radio network temporary identifier (RNTI) or downlink control information (DCI) scrambled using the msgB RNTI. For example, the first message may be a random access response (RAR) message or a fallback RAR message, or the first message may be message B (msgB).
[0102] The first message may further indicate a first parameter, which determines the interval between the first and second messages in the time domain. The second message may be a message scheduled using the first message. For example, the second message is message 3 in a random access procedure.
[0103] In one embodiment, the first parameter is a parameter within a target time domain resource allocation (TDRA) set, and the target time domain resource allocation set is either a first time domain resource allocation set or a second time domain resource allocation set.
[0104] For example, the first parameter is parameter K2, and the target time domain resource allocation set includes one or more values for parameter K2.
[0105] In one embodiment, the first message may include a RAR uplink (UL) grant, the RAR UL grant may include a physical uplink shared channel (PUSCH) time domain resource allocation field, the PUSCH time domain resource allocation field may include a row index in the target time domain resource allocation set, one row index corresponding to one value of the first parameter in the target time domain resource allocation set. A terminal device may determine the value of the first parameter based on the PUSCH time domain resource allocation field in the first message.
[0106] In one embodiment, if the terminal device is of the first type, the time required for the terminal device to process the second message is Nt, 1+Nt, 2+0.5+X in milliseconds (ms). If the terminal device is of the second type, the time required for the terminal device to process the second message is Nt, 1+Nt, 2+0.5.
[0107] In one embodiment, the interval determined based on the first parameter is greater than or equal to a second threshold. The second threshold is the minimum time interval between the last symbol of the PDSCH carrying the first message and the first symbol of the PUSCH carrying the second message. For example, as shown in Figure 3, when the target time domain resource allocation set is the first time domain resource allocation set, the second threshold corresponds to the first type of terminal device. For example, the second threshold is Nt, 1+Nt, 2+0.5+X. When the target time domain resource allocation set is the second time domain resource allocation set, the second threshold corresponds to the second type of terminal device. For example, the second threshold is Nt, 1+Nt, 2+0.5.
[0108] In one embodiment, the interval between the first and second messages, determined based on a first parameter, is equal to K² + Δ-1 in units of slots. When the subcarrier interval is 15 kHz, one slot = 1 ms. When the subcarrier interval is 30 kHz, one slot = 0.5 ms. One slot contains 14 orthogonal frequency division multiplexing (OFDM) symbols (hereinafter abbreviated as symbols). In another case of the subcarrier interval, the duration of one slot can be inferred by analogy. Details are not described.
[0109] If the terminal device is of type 1, the duration corresponding to K2+Δ-1 is greater than or equal to the duration corresponding to Nt, 1+Nt, 2+0.5+X. If the terminal device is of type 2, the duration corresponding to K2+Δ-1 is greater than or equal to the duration corresponding to Nt, 1+Nt, 2+0.5. Nt, 1 represents the PDSCH processing time of the terminal device, and Nt, 2 represents the PUSCH preparation time of the terminal device. The values of the parameter K2 and the parameter Δ are explained below.
[0110] In one embodiment, when the subcarrier interval of PUSCH is 15 kHz, the maximum value of Nt, 1+Nt, 2+0.5 is 31 symbols, or when the subcarrier interval of PUSCH is 30 kHz, the maximum value of Nt, 1+Nt, 2+0.5 is 39 symbols.
[0111] The value of X may be predefined or set by the network device. In one embodiment, when the subcarrier interval of the PUSCH carrying the second message is 15 kHz, the value of X is 0.5 ms, or when the subcarrier interval of the PUSCH carrying the second message is 30 kHz, the value of X is 0.25 ms.
[0112] In one embodiment, when the subcarrier interval of the PUSCH carrying the second message is 15 kHz, the value of X is 1 ms, or when the subcarrier interval of the PUSCH carrying the second message is 30 kHz, the value of X is 0.5 ms.
[0113] The above is merely an example, and other cases for the value of X are possible. Details will not be explained here.
[0114] In one embodiment, the first time domain resource allocation set may correspond to a first type of terminal device, or the first time domain resource allocation set may be used for scheduling a first type of terminal device. The second time domain resource allocation set may correspond to a second type of terminal device, or the second time domain resource allocation set may be used for scheduling a second type of terminal device. The above correspondences may be pre-configured or configured by the network device.
[0115] In one embodiment, before sending the first message, the network device determines the target time domain resource allocation set from the first time domain resource allocation set and the second time domain resource allocation set.
[0116] For example, a network device may determine the type of terminal device that will receive a first message. If the terminal device is of a first type, the network device may determine a first time-domain resource allocation set as the target time-domain resource allocation set. If the terminal device is of a second type, the network device may determine either the first or second time-domain resource allocation set as the target time-domain resource allocation set. The method by which the network device determines the type of terminal device is not limited in this application. Further details are not described herein.
[0117] In another example, when the first preconfiguration condition is met, the network device determines the first time domain resource allocation set as the target time domain resource allocation set, or when the first preconfiguration condition is not met, the network device determines the second time domain resource allocation set as the target time domain resource allocation set.
[0118] In one embodiment, the first preset condition includes at least one of the following:
[0119] The quantity of frequency domain resources for scheduling the first message is greater than the first threshold; in other words, the quantity of frequency domain resources occupied by the first message is greater than the first threshold. The quantity of frequency domain resources as used herein may be bandwidth size, resource blocks (RB), etc., but is not limited to these.
[0120] The resource occupied by the third message is a random access resource (hereinafter abbreviated as the first random access resource) used by the first type of terminal device to perform random access, the third message is the message preceding the first message, and the third message is from the terminal device. The first message may be a response message to the third message. For example, the third message may be the random access request message in step 201.
[0121] The value of the first threshold may relate to the subcarrier interval of the channel in which the first message resides, and the channel in which the first message resides may be a physical downlink shared channel (PDSCH). In one embodiment, when the subcarrier interval of the channel in which the first message resides is 15 kHz, the first threshold is 25 resource blocks; when the subcarrier interval of the channel in which the first message resides is 30 kHz, the first threshold is 12 resource blocks; or when the subcarrier interval of the channel in which the first message resides is 60 kHz, the first threshold is 6 resource blocks.
[0122] Referring to the above description, in the first implementation, if the quantity of frequency domain resources used by the network device to schedule the first message is greater than a first threshold, and the receiving end of the first message is a first type of terminal device, then the first time domain resource allocation set is determined as the target time domain resource allocation set. If the quantity of frequency domain resources used by the network device to schedule the first message is greater than a first threshold, and the receiving end of the first message is a second type of terminal device, then the second time domain resource allocation set is determined as the target time domain resource allocation set.
[0123] In the second implementation, when the quantity of frequency domain resources used by the network device to schedule the first message is greater than a first threshold, the first time domain resource allocation set is determined as the target time domain resource allocation set, regardless of whether the receiving end of the first message is a first type terminal device or a second type terminal device. When the quantity of frequency domain resources used by the network device to schedule the first message is less than or equal to the first threshold, the second time domain resource allocation set is determined as the target time domain resource allocation set, regardless of whether the receiving end of the first message is a first type terminal device or a second type terminal device.
[0124] In the third implementation, when the resource occupied by the third message received by the network device is the first random access resource, the first time-domain resource allocation set is determined as the target time-domain resource allocation set. When the resource occupied by the third message received by the network device is not the first random access resource (for example, the second random access resource), the second time-domain resource allocation set is determined as the target time-domain resource allocation set.
[0125] In the fourth implementation, when the resource occupied by the third message received by the network device is the first random access resource, the first time-domain resource allocation set is determined as the target time-domain resource allocation set. In this case, the second time-domain resource allocation set may be ignored and is no longer used. For both the first type of terminal device and the second type of terminal device, the first time-domain resource allocation set is determined as the target time-domain resource allocation set.
[0126] In the fifth implementation, the first time-domain resource allocation set is determined as the target time-domain resource allocation set when the quantity of frequency-domain resources used by the network device to schedule the first message is greater than the first threshold, and the resources occupied by the third message received by the network device are the first random-access resources. The second time-domain resource allocation set is determined as the target time-domain resource allocation set when the quantity of frequency-domain resources used by the network device to schedule the first message is less than or equal to the first threshold, or when the resources occupied by the third message received by the network device are not the first random-access resources.
[0127] Similarly, after receiving the first message, the terminal device determines the target time domain resource allocation set from the first time domain resource allocation set and the second time domain resource allocation set.
[0128] For example, when the second pre-configuration condition is met, the terminal device determines the first time domain resource allocation set as the target time domain resource allocation set, or when the second pre-configuration condition is not met, the terminal device determines the second time domain resource allocation set as the target time domain resource allocation set.
[0129] In one embodiment, the second preset condition includes at least one of the following:
[0130] The quantity of frequency domain resources required to schedule the first message is greater than the first threshold.
[0131] The first system message indicates a random access resource (hereinafter referred to as the first random access resource) used by a first type of terminal device to perform random access, the first system message originates from a network device, and the first system message precedes the first message.
[0132] Referring to the above description, in the first implementation, if the terminal device is a first type of terminal device, the first time domain resource allocation set is determined as the target time domain resource allocation set when the quantity of frequency domain resources used by the network device to schedule the first message is greater than the first threshold. If the terminal device is a second type of terminal device, the second time domain resource allocation set is determined as the target time domain resource allocation set when the quantity of frequency domain resources used by the network device to schedule the first message is greater than the first threshold.
[0133] In the second implementation, when the quantity of frequency domain resources used by the network device to schedule the first message is greater than a first threshold, the first time domain resource allocation set is determined as the target time domain resource allocation set, regardless of whether the terminal device is a first type terminal device or a second type terminal device. When the quantity of frequency domain resources used by the network device to schedule the first message is less than or equal to the first threshold, the second time domain resource allocation set is determined as the target time domain resource allocation set, regardless of whether the terminal device is a first type terminal device or a second type terminal device.
[0134] In the third implementation, when the first system message indicates a first random access resource, the first time-domain resource allocation set is determined as the target time-domain resource allocation set. When the first system message does not indicate a first random access resource, the second time-domain resource allocation set is determined as the target time-domain resource allocation set.
[0135] In the fourth implementation, when the first system message indicates the first random access resource, the first time-domain resource allocation set is determined as the target time-domain resource allocation set. In this case, the second time-domain resource allocation set may be ignored and is no longer used. For both the first type of terminal device and the second type of terminal device, the first time-domain resource allocation set is determined as the target time-domain resource allocation set.
[0136] In the fifth implementation, the first time-domain resource allocation set is determined as the target time-domain resource allocation set when the quantity of frequency-domain resources used by the network device to schedule the first message is greater than a first threshold and the first system message indicates a first random-access resource. The second time-domain resource allocation set is determined as the target time-domain resource allocation set when the quantity of frequency-domain resources used by the network device to schedule the first message is less than or equal to the first threshold, or when the first system message does not indicate a first random-access resource.
[0137] In this application, the first time-domain resource allocation set and the second time-domain resource allocation set may be predefined or configured by the network.
[0138] In one embodiment, the second time domain resource allocation set may be shown in Table 1.
[0139] [Table 1]
[0140] Each row index corresponds to four parameters: PUSCH mapping type, K2, S, and L. The PUSCH mapping type indicates the mapping type of PUSCH carrying the second message, S indicates the index of the starting symbol of the second message, and L indicates the number of symbols occupied by the second message.
[0141] When the target time-domain resource allocation set is the second time-domain resource allocation set, please refer to Table 2 for the value of j.
[0142] [Table 2]
[0143] μ PUSCH This indicates the subcarrier spacing of the PUSCH that carries the second message. For example, μ PUSCH When is 0, the subcarrier spacing of PUSCH is 15 × 2 μPUSCH = 15 × 2 0 = 15kHz, or μ PUSCH When is 1, the subcarrier spacing of PUSCH is 15 × 2 μPUSCH = 15 × 2 1 =30kHz. Other cases are inferred by analogy and details are not explained.
[0144] When the target time-domain resource allocation set is the second time-domain resource allocation set, please refer to Table 3 for the value of parameter Δ.
[0145] [Table 3]
[0146] In this application, if the terminal device is a second type of terminal device, or if the first pre-configuration condition is not met, the network device determines that the target time domain resource allocation set is the second time domain resource allocation set, and the value of the first parameter indicated by the network device using the first message is the value corresponding to parameter K2 of the second time domain resource allocation set. In this case, it can be guaranteed that the interval determined based on the first parameter is Nt, 1 + Nt, 2 + 0.5 or greater. Therefore, the terminal device can transmit the second message in a timely manner.
[0147] In this application, when a terminal device is a terminal device of a first type, or when a first pre-configuration condition is met, the network device determines that the target time domain resource allocation set is a first time domain resource allocation set, and the value of a first parameter indicated by the network device by using a first message is the value corresponding to parameter K2 of the first time domain resource allocation set. In order to ensure that the interval determined based on the first parameter is Nt, 1+Nt, 2+0.5+X or greater, and that the terminal device has enough time to process the first message and send a second message based on the first message, the first time domain resource allocation set may satisfy at least one of the following constraints.
[0148] The first time-domain resource allocation set contains N values of parameter K2, each of which is 2 or greater, or each of which is j+1 or greater, and N is an integer greater than 0.
[0149] When the value of parameter K2 is equal to 2, the channel mapping mode of the PUSCH where the second message is located is type B, and the index S of the start symbol of the second message is 3 or greater, or When the value of parameter K2 is greater than 2, the channel mapping mode of the PUSCH where the second message is located is type A or type B, the index S of the starting symbol of the second message is greater than or equal to 0, or is within the range of the resource indication value (RIV) code of the index S of the starting symbol of the second message, and the length L of the symbol occupied by the second message is between 0 and 127, where the second message can be replaced with "a message scheduled using the first message".
[0150] For example, in the first implementation, the first time-domain resource allocation set may be shown in Table 4.
[0151] [Table 4]
[0152] From Table 4, it can be seen that when the PUSCH mapping type is type A, or when the PUSCH mapping type is type B and the index S of the starting symbol is less than 3, K2 is greater than or equal to j+2. In another case, K2 is equal to j+1.
[0153] In this implementation, the value of j is determined based on Table 2. The value of the parameter Δ is determined based on Table 3.
[0154] In this implementation, the interval determined based on the first parameter is K2+Δ-1. When the subcarrier interval is 15 kHz, the minimum value of K2+Δ-1 is 3 slots, i.e., 42 symbols. Assuming X=0.5, the maximum value of Nt, 1+Nt, 2+0.5+X is 38 symbols, and K2+Δ-1 is greater than the maximum value of Nt, 1+Nt, 2+0.5+X. When the subcarrier interval is 30 kHz, the minimum value of K2+Δ-1 is 4 slots, i.e., 56 symbols. Assuming X=1, the maximum value of Nt, 1+Nt, 2+0.5+X is 53 symbols, and K2+Δ-1 is greater than the maximum value of Nt, 1+Nt, 2+0.5+X. Therefore, if the terminal device is a terminal device of the first type, or if the network device decides to schedule the second message using the value of parameter K2 of the first time domain resource allocation set when the first preconfiguration condition is met, the terminal device can process the first message in a timely manner and thus send the second message based on the first message.
[0155] In the second implementation, the first time-domain resource allocation set may be shown in Table 5.
[0156] [Table 5]
[0157] Table 5 shows that when the PUSCH mapping type is type B and K2 is equal to j+1, the value of S is 3 or greater. In another case, K2 is j+2 or greater, and S is equal to 0.
[0158] In this implementation, the value of j is determined based on Table 2. The value of the parameter Δ is determined based on Table 3.
[0159] In this implementation, when a terminal device is a terminal device of a first type, or when a network device decides to schedule a second message using the value of parameter K2 in a first time domain resource allocation set when a first preconfiguration condition is met, the interval K2+Δ-1 determined based on the first parameter is also greater than or equal to the maximum value of Nt, 1+Nt, 2+0.5+X, and the terminal device can process the first message in a timely manner, and therefore can send a second message based on the first message.
[0160] In this application, when a first time domain resource allocation set is set by a network device, the network device may set the first time domain resource allocation set by using a second system message.
[0161] In one embodiment, the second system message is a system information block 1 (SIB1), and the PUSCH-TimeDomainResourceAllocation field within the SIB1 may contain a first time domain resource allocation set.
[0162] Similarly, if a second time-domain resource allocation set is to be configured by a network device, the network device may configure the second time-domain resource allocation set by using a second system message. The specific process is not described.
[0163] Step 203: The terminal device sends a second message based on the first parameter.
[0164] In response, the network device receives a second message.
[0165] A terminal device may, based on a first parameter, determine the interval between the last symbol of the PDSCH carrying the first message and the first symbol of the PUSCH carrying the second message, i.e., the symbolic position of the second message in the time domain, and then transmit the second message on the corresponding symbol. The specific process is not described.
[0166] According to the method provided in this application, there are multiple time-domain resource allocation sets so that different time-domain resource allocation sets are used under different conditions. In this way, different types of terminal devices can be scheduled so that each type of terminal device can process scheduling messages and send scheduled messages in a timely manner, thereby improving the flexibility of network scheduling.
[0167] In this application, the first type of terminal device and the second type of terminal device may further jointly handle a single time domain resource allocation set. When scheduling the first type of terminal device, the network device preferentially uses a larger value for the parameter K2, thereby extending the interval between the scheduling message and the scheduled message, allowing the first type of terminal device to process the first message in a timely manner. A detailed explanation is provided below.
[0168] Figure 4 is a schematic flowchart of a message scheduling method according to one embodiment of this application. The method includes the following steps.
[0169] Step 401: The terminal device sends a random access request message to the network device.
[0170] In response, the network device receives a random access request message.
[0171] A random access request message may be message 1 or message A in a random access procedure.
[0172] If the network side configures a random access resource for a first type of terminal device, that is, a dedicated random access resource for the first type of terminal device, then when the terminal device is a first type of terminal device, the terminal device may send a random access request message by using the dedicated random access resource for the first type of terminal device.
[0173] A network device may configure a random access resource to be used by a first type of terminal device to perform random access by using a first system message. The specific process is not described.
[0174] This application is illustrated by using an example in which a terminal device accesses a network device using a random access procedure, and the network device uses a first message to schedule a second message. If this application is applied to a different scenario, step 401 may be performed instead.
[0175] Step 402: The network device sends the first message.
[0176] In response, the terminal device receives the first message.
[0177] For the implementation of the first message, please refer to the explanation in step 202. Further details will not be explained again here.
[0178] In one implementation, the first message indicates parameter K2, which determines the interval between the first and second messages in the time domain. Parameter K2 is a parameter within the time domain resource allocation set, which contains multiple values for parameter K2. For specific details of the time domain resource allocation set, please refer to Table 1 above. In other words, the time domain resource allocation set here may be the same as the second time domain resource allocation set in the procedure described above. Further details will not be explained again here.
[0179] In one implementation, the first message may include a RAR UL grant, which may include a PUSCH time-domain resource allocation field, which may include a row index in the time-domain resource allocation set, where one row index corresponds to one value of parameter K2 in the time-domain resource allocation set. A terminal device may determine the value of parameter K2 based on the PUSCH time-domain resource allocation field in the first message.
[0180] In one implementation, the interval determined based on parameter K2 is greater than or equal to a second threshold. The second threshold is the minimum time interval between the last symbol of the PDSCH carrying the first message and the first symbol of the PUSCH carrying the second message. For example, for a first type of terminal device, the second threshold is Nt, 1+Nt, 2+0.5+X. For a second type of terminal device, the second threshold is Nt, 1+Nt, 2+0.5.
[0181] The interval determined based on parameters K2 and Δ may be equal to K2 + Δ - 1. For the values of X and parameter Δ, please refer to the explanation in step 202. Further details will not be explained again here.
[0182] In one implementation, if the terminal device is of type 1, or if the pre-configuration conditions are met, the duration corresponding to K2+Δ-1 is greater than or equal to the duration corresponding to Nt, 1+Nt, and 2+0.5+X. If the terminal device is of type 2, or if the pre-configuration conditions are not met, the duration corresponding to K2+Δ-1 is greater than or equal to the duration corresponding to Nt, 1+Nt, and 2+0.5.
[0183] In one implementation, when a pre-configured condition is met, the value of parameter K2 is greater than or equal to a third threshold; or, when the pre-configured condition is not met, the value of parameter K2 may be less than or greater than the third threshold. For example, the third threshold is equal to 3. The third threshold may be pre-defined or set by the network device.
[0184] In one implementation, when the pre-configuration conditions are met, the value of parameter K2 in the time domain resource allocation set, which corresponds to the row index included in the first message, is greater than or equal to the third threshold.
[0185] For example, the third threshold is equal to 3. When the pre-configured conditions are met, the row index included in the first message is one of {11, 12, 13, 15, 16}. In this case, the value of parameter K2 indicated by the first message is 3 or greater.
[0186] In one implementation, when the pre-configured conditions are met, the parameter j used to determine parameter K2 is equal to the third value, the third value is greater than or equal to the fourth threshold, and the fourth threshold is the third threshold minus 1. Thus, the value of parameter K2 may be greater than or equal to the third threshold. When the pre-configured conditions are not met, the parameter j used to determine parameter K2 is equal to the fourth value. There is a correspondence between the third and fourth values and the subcarrier interval of the channel where the first message is located.
[0187] For example, when the fourth threshold is equal to 2 and the pre-defined conditions are met, the value of j may be shown in Table 6.
[0188] [Table 6]
[0189] When the pre-set conditions are not met, the value of j may be as shown in Table 2.
[0190] In one implementation, when a pre-configured condition is met, parameter j is equal to the fifth value, or when the pre-configured condition is not met, parameter j is equal to the sixth value. In this way, the value of parameter K2 can increase so that the terminal device has more time to process the message. There is a correspondence between the fifth and sixth values and the subcarrier interval of the channel in which the first message resides. When the fifth and sixth values correspond to the same subcarrier interval, the fifth value is greater than the sixth value. In one implementation, the value of parameter K2 indicated by the first message is a value in the time-domain resource allocation set, which contains multiple values for parameter K2. For specific details of the time-domain resource allocation set, please refer to Table 1 above. In other words, the time-domain resource allocation set in this implementation may be the same as the second time-domain resource allocation set in the procedure described above. Details will not be explained again here.
[0191] In one implementation, the fifth value is equal to the sum of the sixth value and the preset value. For example, the preset value is equal to 2. Only one value is used to satisfy the scheduling time sequence requirements for two different subcarrier intervals.
[0192] In one implementation, the preset value is related to the subcarrier interval of the channel where the first message resides. For example, when the subcarrier interval is 15 kHz, the preset value is equal to 2, or when the subcarrier interval is 30 kHz, the preset value is equal to 1. Different time sequences are used to mitigate the time between the two subcarrier intervals, improving the flexibility of network scheduling.
[0193] Subcarrier intervals of 15 kHz and 30 kHz are used as examples. When the pre-configured conditions are met, the value of j may be shown in Table 7.
[0194] [Table 7]
[0195] When the pre-set conditions are not met, the value of j may be as shown in Table 8.
[0196] [Table 8]
[0197] According to Tables 7 and 8, when the subcarrier interval is 15 kHz and the pre-set conditions are met, j=3, or when the pre-set conditions are not met, j=1.
[0198] In one implementation, the first message may further indicate the value of parameter j. For example, when a pre-configured condition is met, the first message may indicate that the value of parameter j is the fifth value, or when the pre-configured condition is not met, the first message may indicate that the value of parameter j is the sixth value.
[0199] In one implementation, the preconfiguration conditions for a network device include at least one of the following:
[0200] The quantity of frequency domain resources required to schedule the first message is greater than the first threshold.
[0201] The resource occupied by the third message is a random access resource (i.e., the first random access resource) used by the first type of terminal device to perform random access, the third message is the message preceding the first message, and the third message originates from the terminal device. For example, the third message is a random access request message.
[0202] In one implementation, the pre-configuration conditions for a terminal device include at least one of the following:
[0203] The quantity of frequency domain resources for scheduling the first message is greater than the first threshold, or The first system message indicates a random access resource (i.e., the first random access resource) used by a first type of terminal device to perform random access, and the first system message is from a network device.
[0204] For example, the value of parameter K2 is greater than or equal to the third threshold when the quantity of frequency domain resources for scheduling the first message is greater than the first threshold, or when the first system message indicates a first random access resource, or when the resources occupied by the third message are random access resources used by a first type of terminal device to perform random access.
[0205] For example, when the number of frequency domain resources for scheduling the first message is greater than the first threshold, and the first system message indicates the first random access resource, the value of parameter K2 is greater than or equal to the third threshold.
[0206] For example, when the number of frequency domain resources for scheduling the first message is greater than the first threshold, and the resources occupied by the third message are the first random access resources, then the value of parameter K2 is greater than or equal to the third threshold.
[0207] For the first threshold, please refer to the explanation in step 202. Further details will not be explained again here.
[0208] Step 403: The terminal device sends a second message based on parameter K2.
[0209] In response, the network device receives a second message.
[0210] Figure 5 is a schematic flowchart of a message scheduling method according to one embodiment of this application. The method includes the following steps.
[0211] Step 501: The terminal device sends a random access request message to the network device.
[0212] In response, the network device receives a random access request message.
[0213] A random access request message may be message 1 or message A in a random access procedure.
[0214] If the network side configures a random access resource for a first type of terminal device, that is, a dedicated random access resource for the first type of terminal device, then when the terminal device is a first type of terminal device, the terminal device may send a random access request message by using the dedicated random access resource for the first type of terminal device.
[0215] A network device may configure a random access resource to be used by a first type of terminal device to perform random access by using a first system message. The specific process is not described.
[0216] This application is illustrated by using an example in which a terminal device accesses a network device using a random access procedure, and the network device uses a first message to schedule a second message. If this application is applied to a different scenario, step 501 may be performed instead.
[0217] Step 502: The network device sends the first message.
[0218] In response, the terminal device receives the first message.
[0219] For the implementation of the first message, please refer to the explanation in step 202. Further details will not be explained again here.
[0220] In one implementation, the first message indicates parameter K2, and parameters K2 and Δ are used to determine the interval between the first and second messages in the time domain. Parameter K2 is a parameter in the time domain resource allocation set, which contains multiple values of parameter K2. For specific details of the time domain resource allocation set, please refer to Table 1 above. In other words, the time domain resource allocation set here may be the same as the second time domain resource allocation set in the procedure described above. Further details will not be explained again here.
[0221] For details on how the first message indicates parameter K2, please refer to the explanation in step 402. Further details will not be explained again here.
[0222] In one implementation, the interval determined based on parameters K2 and Δ is greater than or equal to a second threshold. The second threshold is the minimum time interval between the last symbol of the PDSCH carrying the first message and the first symbol of the PUSCH carrying the second message. For example, for a first type of terminal device, the second threshold is Nt, 1+Nt, 2+0.5+X. For a second type of terminal device, the second threshold is Nt, 1+Nt, 2+0.5.
[0223] The value of X may be predefined or set by the network device. In one implementation, when the subcarrier interval of the PUSCH carrying the second message is 15 kHz, the value of X is 0.5 ms, or when the subcarrier interval of the PUSCH carrying the second message is 30 kHz, the value of X is 0.25 ms.
[0224] In one implementation, when the subcarrier interval of the PUSCH carrying the second message is 15 kHz, the value of X is 1 ms, or when the subcarrier interval of the PUSCH carrying the second message is 30 kHz, the value of X is 0.5 ms.
[0225] The interval determined based on the parameters K2 and Δ may be equal to K2 + Δ - 1.
[0226] In one implementation, if the terminal device is of type 1, or if the pre-configuration conditions are met, the duration corresponding to K2+Δ-1 is greater than or equal to the duration corresponding to Nt, 1+Nt, and 2+0.5+X. If the terminal device is of type 2, or if the pre-configuration conditions are not met, the duration corresponding to K2+Δ-1 is greater than or equal to the duration corresponding to Nt, 1+Nt, and 2+0.5.
[0227] In one implementation, when a pre-configured condition is met, the value of parameter Δ is equal to a first value, or when the pre-configured condition is not met, the value of parameter Δ is equal to a second value. The first value is greater than the second value, and there is a correspondence between parameter Δ and the subcarrier interval of the channel in which the first message resides. The first and second values may be predefined or may be set by the network device. When the first and second values correspond to the same subcarrier interval, the first value is greater than the second value.
[0228] Alternatively, the first value may be the sum of the second value and a preset value. The preset value is an integer greater than 0. The preset value may be predefined or set by a network device.
[0229] In one implementation, when the pre-configuration conditions are met and the subcarrier interval of the channel where the first message is located is 15 kHz or 30 kHz, the first value is 4 or greater. When the pre-configuration conditions are not met and the subcarrier interval of the channel where the first message is located is 15 kHz, the second value is 2, or when the subcarrier interval of the channel where the first message is located is 30 kHz, the second value is 3.
[0230] For example, when the pre-defined conditions are met, the value of parameter Δ may be shown in Table 9.
[0231] [Table 9]
[0232] When the pre-set conditions are not met, the value of parameter Δ may be as shown in Table 3 above.
[0233] In one implementation, the preconfiguration conditions for a network device include at least one of the following:
[0234] The quantity of frequency domain resources for scheduling the first message is greater than the first threshold. The resource occupied by the third message is the first random access resource, the third message is the message preceding the first message, the third message originates from a terminal device, for example, the third message is a random access request message, or The resource occupied by the third message is not the first random access resource.
[0235] In one implementation, the pre-configuration conditions for a terminal device include at least one of the following:
[0236] The quantity of frequency domain resources for scheduling the first message is greater than the first threshold. The first system message indicates a random access resource (hereinafter referred to as the first random access resource) used by a first type of terminal device to perform random access, and the first system message is from a network device, or The first system message does not indicate the first random access resource.
[0237] For example, when the quantity of frequency domain resources for scheduling the first message is greater than the first threshold, or when the first system message indicates a first random access resource, or when the resource occupied by the third message is a random access resource used by a first type of terminal device to perform random access, the value of parameter Δ is equal to the first threshold.
[0238] For example, when the quantity of frequency domain resources for scheduling the first message is less than or equal to the first threshold, or when the first system message does not indicate the first random access resource, the value of parameter Δ is equal to the second value.
[0239] For example, when the number of frequency domain resources for scheduling the first message is greater than the first threshold, and the first system message indicates the first random access resource, the value of parameter Δ is equal to the first value.
[0240] For example, when the quantity of frequency domain resources for scheduling the first message is less than or equal to the first threshold, or when the first system message does not indicate the first random access resource, the value of parameter Δ is equal to the second value.
[0241] For the first threshold, please refer to the explanation in step 202. Further details will not be explained again here.
[0242] Step 503: The terminal device sends a second message based on parameters K2 and Δ.
[0243] In response, the network device receives a second message.
[0244] In this application, if a terminal device is a first type of terminal device, the terminal device may further indicate to network devices that it is a first type of terminal device by using a logical channel identifier. In other words, whether or not a first random access resource is configured, a first type of terminal device is identified by using a dedicated first logical channel identifier and / or a dedicated second logical channel identifier. The first random access resource may alternatively be a dedicated random access resource for a first type of terminal device, and the second random access resource may alternatively be a dedicated random access resource for a second type of terminal device. See the description below for further details.
[0245] Figure 6 is a schematic flowchart of an access method according to one embodiment of this application.
[0246] Step 601: The terminal device sends a fourth message to the network device.
[0247] Step 602: The network device receives the fourth message.
[0248] In one implementation, the fourth message is message 3 in the random access procedure.
[0249] In one implementation, there is a correspondence between a first type of terminal device, a first logical channel identifier, and a second logical channel identifier. This correspondence is either predefined, preconfigured, or set by the network device.
[0250] For example, the values of the first logical channel identifier and the second logical channel identifier can each be one of 37 to 42. For example, the value of the first logical channel identifier is 37, and the value of the second logical channel identifier is 38.
[0251] When a terminal device is a terminal device of the first type, the fourth message transmitted by the terminal device includes a first logical channel identifier or a second logical channel identifier. Upon receiving a fourth message containing a first logical channel identifier or a second logical channel identifier, the network device determines that the terminal device is a terminal device of the first type.
[0252] In the first case, if a dedicated random access resource is configured for the first type of terminal device and the terminal device is of the first type, the transmitted fourth message includes either the first logical channel identifier or the second logical channel identifier.
[0253] A first type of terminal device is identified by using a dedicated first logical channel identifier and / or a dedicated second logical channel identifier.
[0254] In the second case, if a dedicated random access resource is not configured for the first type of terminal device, and a dedicated random access resource is configured for the second type of terminal device, and the terminal device is the first type of terminal device, then the transmitted fourth message includes the first logical channel identifier or the second logical channel identifier. The first type of terminal device is identified by using a dedicated first logical channel identifier and / or a dedicated second logical channel identifier.
[0255] In the third case, if no dedicated random access resources are configured for the first type of terminal device, and no dedicated random access resources are configured for the second type of terminal device, and the terminal device is a first type of terminal device, the transmitted fourth message includes a first logical channel identifier or a second logical channel identifier. The first type of terminal device is identified by using a dedicated first logical channel identifier and / or a dedicated second logical channel identifier.
[0256] In this application, in possible implementations, the network device may further transmit first indication information or second indication information.
[0257] Accordingly, the terminal device receives either the first or second indication information from the network device.
[0258] The first indication information indicates a terminal device for reporting the first capability information, and the second indication information indicates a terminal device for reporting the second capability information.
[0259] In another possible implementation, the terminal device proactively transmits either the first or second capability information to the network device without considering whether the terminal device receives either the first or second indication information from the network device.
[0260] The terminal device transmits either first capability information or second capability information to the network device. The first capability information indicates that the terminal device possesses a first capability, and the second capability information indicates that the terminal device possesses a second capability.
[0261] In response, the network device receives either the first capability information or the second capability information from the terminal device.
[0262] The first or second capability information may be indicated by using one of the following: message 1 (Msg1) in a random access procedure, message A (MsgA) in a random access procedure, message 3 (Msg3) in a random access procedure, and radio resource control (RRC) signaling. The random access type corresponding to message 1 and message 3 is 4-step random access, and the random access type corresponding to message A is 2-step random access.
[0263] In this embodiment of the present application, when the first capability information or the second capability information is indicated based on message 3, there is a correspondence between the capabilities of the terminal device and the logical channel identifier (LCID). Specifically, the first capability corresponds to the first logical channel identifier, and the second capability corresponds to the second logical channel identifier. The correspondence is predefined, preconfigured, or configured by the network device. The first logical channel identifier is different from the second logical channel identifier.
[0264] For example, the first capability information may be a first logical channel identifier corresponding to the first capability, and the second capability information may be a second logical channel identifier corresponding to the second capability. The value of the first logical channel identifier may be one of 37 to 42, and the value of the second logical channel identifier may be one of 37 to 42.
[0265] When the capability of the terminal device is the first capability, the first capability information included in message 3 transmitted by the terminal device is the first logical channel identifier. When receiving message 3 including the first logical channel identifier, the network device determines that the terminal device is a first type of terminal device having the first capability.
[0266] When the capability of the terminal device is the second capability, the second capability information included in message 3 transmitted by the terminal device is the second logical channel identifier. When receiving message 3 including the second logical channel identifier, the network device determines that the terminal device is a first type of terminal device having the second capability.
[0267] For example, the value of the first logical channel identifier is 37, and the value of the second logical channel identifier is 38.
[0268] When the capability of the terminal device is the first capability, the logical channel identifier included in message 3 transmitted by the terminal device is 37. When receiving message 3 including the logical channel identifier of 37, the network device determines that the terminal device is a first type of terminal device having the first capability.
[0269] When the capability of the terminal device is the second capability, the logical channel identifier included in message 3 transmitted by the terminal device is 38. When receiving message 3 including the logical channel identifier of 38, the network device determines that the terminal device is a first type of terminal device having the second capability.
[0270] In the present embodiment of the present application, when the first capability information or the second capability information is indicated based on message 1 or message A, there is a correspondence between the capabilities of the terminal device and the transmission resources of message 1 or message A. In other words, the first capability corresponds to the first transmission resource, and the second capability corresponds to the second transmission resource. The correspondence relationship is predefined, pre-set, or set by the network device.
[0271] The transmission resources include one or more of a physical random access channel (PRACH) time-domain resource, a PRACH frequency-domain resource, a PRACH code-domain resource, a PRACH transmission opportunity, and a preamble sequence.
[0272] When the capability of the terminal device is the first capability, the fact that the terminal device has the first capability is indicated based on the first transmission resource. The first transmission resource may be an existing transmission resource for message 1 or message A.
[0273] When the capability of the terminal device is the second capability, the fact that the terminal device has the second capability is indicated based on the second transmission resource. The second transmission resource may be a newly defined transmission resource for transmitting message 1 or message A.
[0274] For example, when the transmission resource is a preamble sequence, preamble sequences 1 through 64 are currently defined as a transmission resource, and the first transmission resource is an existing transmission resource for message 1 or message A. Therefore, the first transmission resource includes preamble sequences 1 through 64. The second transmission resource is a newly defined transmission resource for transmitting message 1 or message A. Therefore, the second transmission resource may include preamble sequences 65 through 128.
[0275] The first capability information is a preamble sequence transmitted by the terminal device. Message 1 or Message A transmitted by the terminal device includes one of preamble sequences 1 through 64 and indicates that the terminal device's capability is the first capability.
[0276] The second capability information may also be a preamble sequence transmitted by the terminal device. Message 1 or Message A transmitted by the terminal device includes one of preamble sequences 65 to 128, indicating that the terminal device's capability is the second capability.
[0277] It should be understood that the correspondence between the capabilities of a terminal device and the transmission resources for message 1 or message A may be predefined or preconfigured, or may be configured by the network device.
[0278] In the method described above, the type or capabilities of the terminal device are indicated in advance during the initial access process, and the network device is able to schedule resources for the terminal device that are appropriate to the type or capabilities of the terminal device, thereby improving resource utilization and system efficiency.
[0279] The methods and procedures described above may be implemented independently or in combination. This is not limited to the present application.
[0280] In the embodiments provided in this application, the methods provided in the embodiments are described separately in terms of device-to-device interaction. To implement the functionality in the methods provided in the embodiments, a network device or terminal device may include a hardware structure and / or software module, and the functionality may be implemented in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. Whether the functionality in the aforementioned functionality is performed by using a hardware structure, a software module, or a combination of a hardware structure and a software module depends on the design constraints of the particular application and technical solution.
[0281] In this embodiment of the present application, module partitioning is merely an example and represents a logical functional partitioning. In actual implementations, other partitioning methods may be used. In addition, the functional modules in this embodiment may be integrated into a single processor, exist physically independently, or two or more modules may be integrated into a single module. The integrated module may be implemented in hardware form or in the form of a software functional module.
[0282] Similar to the concepts described above, as shown in Figure 7, embodiments of the present application further provide a communication device 700 configured to implement the functions of a network device or terminal device in the manner described above. For example, the device may be a software module or a chip system. In these embodiments of the present application, the chip system may include a chip, or it may include a chip and other separate components. The communication device 700 may include a processing unit 701 and a communication unit 702.
[0283] In embodiments of this application, the processing unit may also be referred to as a processor, processing board, processing module, processing device, etc. The communication unit may also be referred to as a transceiver, transceiver machine, transceiver device, transceiver unit, etc. The communication unit may include a transmitting unit and / or receiving unit configured to perform the transmitting and receiving steps of a network device or terminal device in the embodiments of the method described above.
[0284] The communication device provided in the embodiments of this application will be described in detail below with reference to Figures 7 and 8. Please understand that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for details not described in detail, please refer to the method embodiments described above. For brevity, further details will not be explained again here.
[0285] In one implementation, the communication device 700 may perform the following functions:
[0286] The processing unit is configured to determine the target time domain resource allocation set, which is either the first time domain resource allocation set or the second time domain resource allocation set.
[0287] The communication unit receives a first message, which contains a first parameter, the first parameter being used to determine the interval between the first and second messages in a time domain, the first parameter being a parameter in a target time domain resource allocation set, and is configured to send the second message based on the first parameter.
[0288] In one implementation, the communication device 700 may perform the following functions:
[0289] The processing unit is configured to determine a target time domain resource allocation set, and the target time domain resource allocation set is a first time domain resource allocation set or a second time domain resource allocation set.
[0290] The communication unit is configured to transmit a first message, the first message indicates a first parameter, the first parameter is for determining an interval between the first message and a second message within a time domain, the first parameter is a parameter within the target time domain resource allocation set, and is configured to receive the second message.
[0291] In one implementation, the communication device 700 may perform the following functions.
[0292] The communication unit is configured to receive a first message, the first message indicates a parameter K2, the parameter K2 is for determining an interval between the first message and a second message within a time domain, and when a preset condition is satisfied, the value of the parameter K2 is greater than or equal to a third threshold.
[0293] The processing unit is configured to use the communication unit to transmit a second message based on the parameter K2.
[0294] In one implementation, the communication device 700 may perform the following functions. [[ID=
[0297] In one implementation, the communication device 700 may perform the following functions:
[0298] The processing unit is configured to receive a first message using a communication unit, the first message containing parameter K2, and parameters K2 and Δ are used to determine the interval between the first message and the second message in the time domain. When a pre-configured condition is met, the value of parameter Δ is equal to the first value, or when the pre-configured condition is not met, the value of parameter Δ is equal to the second value. The first value is greater than the second value, and there is a correspondence between parameter Δ and the subcarrier interval of the channel in which the first message is located.
[0299] The processing unit is configured to use the communication unit to send a second message based on parameters K2 and Δ.
[0300] In one implementation, the communication device 700 may perform the following functions:
[0301] The processing unit is configured to send a first message using the communication unit, the first message containing parameter K2, and parameters K2 and Δ are used to determine the interval between the first message and the second message in the time domain. When a pre-configured condition is met, the value of parameter Δ is equal to the first value, or when the pre-configured condition is not met, the value of parameter Δ is equal to the second value. The first value is greater than the second value, and there is a correspondence between parameter Δ and the subcarrier interval of the channel in which the first message is located.
[0302] The processing unit is configured to receive a second message using the communication unit.
[0303] The above is merely one example. The processing unit 701 and the communication unit 702 can perform other functions. For a more detailed explanation, please refer to the relevant descriptions in the embodiments of the method described above. Details are not described here.
[0304] Figure 8 shows a communication device 800 according to one embodiment of the present application. The device shown in Figure 8 may be a hardware circuit implementation of the device shown in Figure 7. The communication device is applicable to the flowchart described above and performs the functions of a network device or terminal device in the embodiments of the method described above. For the sake of clarity, Figure 8 shows only the main components of the communication device.
[0305] As shown in Figure 8, the communication device 800 includes a processor 810 and an interface circuit 820. The processor 810 and the interface circuit 820 are coupled to each other. It can be understood that the interface circuit 820 may be a transceiver or an input / output interface.
[0306] In one implementation, the communication device 800 may further include a memory 830 configured to store instructions executed by the processor 810, or input data required by the processor 810 to execute an instruction, or data generated after the processor 810 has executed an instruction.
[0307] When the communication device 800 is configured to implement the method described above, the processor 810 is configured to implement the functions of the processing unit 701, and the interface circuit 820 is configured to implement the functions of the communication unit 702.
[0308] It can be understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or may be another general-purpose processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general-purpose processor may be a microprocessor or any ordinary processor, etc.
[0309] The memory in the embodiments of this application may be random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), registers, hard disks, removable hard disks, CD-ROMs, or any other form of storage medium known in the art. For example, the storage medium is coupled to the processor so that the processor can read information from and write information to the storage medium. Indeed, the storage medium may be a component of the processor. The processor and the storage medium may be located within an ASIC.
[0310] Those skilled in the art should understand that embodiments of this application may be provided as methods, systems, or computer program products. Accordingly, this application may utilize embodiments of hardware only, software only, or a combination of software and hardware. Furthermore, this application may utilize the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk memory, optical memory, etc.) containing computer-usable program code.
[0311] This application will be described with reference to flowcharts and / or block diagrams of the methods, devices (systems), and computer program products described herein. It should be understood that computer program instructions may be used to implement each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams. These computer program instructions may be provided to a general-purpose computer, a dedicated computer, an embedded processor, or a processor of any other programmable data processing device, so as to generate a machine, where instructions executed by the processor of the computer or any other programmable data processing device generate a device for implementing one or more processes in the flowchart and / or one or more blocks in the block diagram.
[0312] These computer program instructions may be stored in computer-readable memory that can instruct a computer or any other programmable data processing device to operate in a specific manner, and as a result, the instructions stored in computer-readable memory generate artifacts including an instruction unit. The instruction unit implements a specific function in one or more processes in a flowchart and / or in one or more blocks in a block diagram.
[0313] It will be apparent to those skilled in the art that various modifications and variations can be made to this application without departing from its scope. Provided that such modifications and variations fall within the scope of protection defined by the following claims and their equivalents, this application is intended to encompass such modifications and variations.
Claims
1. A message scheduling method, Determining a target time domain resource allocation set, wherein the target time domain resource allocation set is either a first time domain resource allocation set or a second time domain resource allocation set. Receiving a first message, wherein the first message indicates a first parameter, the first parameter is for determining the interval between the first message and the second message in a time domain, and the first parameter is a parameter in the target time domain resource allocation set. Sending the second message based on the first parameter and A method that includes this.
2. Determining the aforementioned target time domain resource allocation set means that When the pre-configured conditions are met, the first time domain resource allocation set is determined to be the target time domain resource allocation set, or When the pre-configured conditions are not met, the second time domain resource allocation set is determined to be the target time domain resource allocation set, The aforementioned pre-set conditions are: The quantity of frequency domain resources for scheduling the first message is greater than the first threshold, or The first system message indicates a random access resource used by a first type of terminal device to perform random access, and the first system message originates from a network device. The method according to claim 1, comprising at least one of the following.
3. When the subcarrier interval of the channel in which the first message is located is 15 kHz, the first threshold is 25 resource blocks. When the subcarrier interval of the channel in which the first message is located is 30 kHz, the first threshold is 12 resource blocks, or The method according to claim 2, wherein when the subcarrier interval of the channel in which the first message is located is 60 kHz, the first threshold is 6 resource blocks.
4. The first time domain resource allocation set is parameter K 2 The method according to any one of claims 1 to 3, wherein the formula includes N values, each of which is 2 or greater, and N is an integer greater than 0.
5. The aforementioned parameter K 2 When the aforementioned value is equal to 2, the channel mapping mode of the PUSCH where the second message is located is type B, and the index S of the start symbol of the second message is 3 or greater, or The aforementioned parameter K 2 The method according to claim 4, wherein when the value of is greater than 2, the channel mapping mode of the physical uplink shared channel PUSCH on which the second message is located is type A or type B, the index S of the start symbol of the second message is 0 or greater, or is within the range of the resource indication value RIV code of the index S of the start symbol of the second message, and the length L of the symbol occupied by the second message is from 0 to 127.
6. The method according to any one of claims 1 to 5, wherein when the target time domain resource allocation set is the first time domain resource allocation set, the interval determined based on the first parameter is greater than or equal to a second threshold, the second threshold being the minimum time interval between the last symbol of the physical downlink shared channel PDSCH carrying the first message and the first symbol of the physical uplink shared channel PUSCH carrying the second message, and the second threshold being the first type of terminal device.
7. The method according to any one of claims 1 to 6, wherein at least one of the first time domain resource allocation set and the second time domain resource allocation set is from the network device.
8. The first message is a random access response message or a fallback random access response message. The method according to any one of claims 1 to 7, wherein the second message is message 3 in a random access procedure.
9. A message scheduling method, Determining a target time domain resource allocation set, wherein the target time domain resource allocation set is either a first time domain resource allocation set or a second time domain resource allocation set. Sending a first message, wherein the first message contains a first parameter, the first parameter is for determining the interval between the first message and the second message in a time domain, and the first parameter is a parameter in the target time domain resource allocation set. Receiving the second message and A method that includes this.
10. Determining the aforementioned target time domain resource allocation set means that When the pre-configured conditions are met, the first time domain resource allocation set is determined to be the target time domain resource allocation set, or When the pre-configured conditions are not met, the second time domain resource allocation set is determined to be the target time domain resource allocation set, The aforementioned pre-set conditions are: The quantity of frequency domain resources for scheduling the first message is greater than the first threshold, or The resource occupied by the third message is a random access resource used by a first type of terminal device to perform random access, the third message is a message preceding the first message, and the third message is from the terminal device. The method according to claim 9, comprising at least one of the following.
11. When the subcarrier interval of the channel in which the first message is located is 15 kHz, the first threshold is 25 resource blocks. When the subcarrier interval of the channel in which the first message is located is 30 kHz, the first threshold is 12 resource blocks, or The method according to claim 10, wherein when the subcarrier interval of the channel in which the first message is located is 60 kHz, the first threshold is 6 resource blocks.
12. The first time domain resource allocation set is parameter K 2 The method according to any one of claims 9 to 11, wherein the formula includes N values, each of which is 2 or greater, and N is an integer greater than 0.
13. The aforementioned parameter K 2 When the aforementioned value is equal to 2, the channel mapping mode of the PUSCH where the second message is located is type B, and the index S of the start symbol of the second message is 3 or greater, or The aforementioned parameter K 2 The method according to claim 12, wherein when the value of is greater than 2, the channel mapping mode of the PUSCH in which the second message is located is type A or type B, the index S of the start symbol of the second message is 0 or greater, or is within the range of the resource indication value RIV code of the index S of the start symbol of the second message, and the length L of the symbol occupied by the second message is from 0 to 127.
14. The method according to any one of claims 9 to 13, wherein when the target time domain resource allocation set is the first time domain resource allocation set, the interval determined based on the first parameter is greater than or equal to a second threshold, the second threshold being the minimum time interval between the last symbol of the PDSCH carrying the first message and the first symbol of the PUSCH carrying the second message, and the second threshold being the first type of terminal device.
15. The method according to any one of claims 9 to 14, wherein at least one of the first time domain resource allocation set and the second time domain resource allocation set is from the network device.
16. The first message is a random access response message or a fallback random access response message. The method according to any one of claims 9 to 15, wherein the second message is message 3 in a random access procedure.
17. A communication device, A processing unit configured to determine a target time domain resource allocation set, wherein the target time domain resource allocation set is a first time domain resource allocation set or a second time domain resource allocation set, A communication unit configured to receive a first message, the first message containing a first parameter, the first parameter being for determining the interval between the first message and a second message in a time domain, the first parameter being a parameter in the target time domain resource allocation set, and to transmit the second message based on the first parameter. A communication device equipped with this device.
18. The aforementioned processing unit is When the pre-configured conditions are met, the first time domain resource allocation set is determined as the target time domain resource allocation set, or When the pre-configured conditions are not met, the system is specifically configured to determine the second time domain resource allocation set as the target time domain resource allocation set. The aforementioned pre-set conditions are: The quantity of frequency domain resources for scheduling the first message is greater than the first threshold, or The first system message indicates a random access resource used by a first type of terminal device to perform random access, and the first system message originates from a network device. The apparatus according to claim 17, comprising at least one of the following.
19. When the subcarrier interval of the channel in which the first message is located is 15 kHz, the first threshold is 25 resource blocks. When the subcarrier interval of the channel in which the first message is located is 30 kHz, the first threshold is 12 resource blocks, or The apparatus according to claim 18, wherein when the subcarrier spacing of the channel in which the first message is located is 60 kHz, the first threshold is six resource blocks.
20. The first time domain resource allocation set is parameter K 2 The apparatus according to any one of claims 17 to 19, comprising N values, each of which is 2 or greater, and N is an integer greater than 0.
21. The aforementioned parameter K 2 When the aforementioned value is equal to 2, the channel mapping mode of the PUSCH where the second message is located is type B, and the index S of the start symbol of the second message is 3 or greater, or the parameter K 2 When the value of is greater than 2, the channel mapping mode of the physical uplink shared channel PUSCH where the second message is located is type A or type B, and the index S of the start symbol of the second message is 0 or more, or the value range of the resource indication value RIV code of the index S of the start symbol of the second message, and the length L of the symbol occupied by the second message is from 0 to 127. The apparatus according to claim 20.
22. The apparatus according to any one of claims 17 to 21, wherein when the target time domain resource allocation set is the first time domain resource allocation set, the interval determined based on the first parameter is greater than or equal to a second threshold, the second threshold being the minimum time interval between the last symbol of the physical downlink shared channel PDSCH carrying the first message and the first symbol of the physical uplink shared channel PUSCH carrying the second message, and the second threshold being the terminal device of the first type.
23. The apparatus according to any one of claims 17 to 22, wherein at least one of the first time domain resource allocation set and the second time domain resource allocation set is from the network device.
24. The first message is a random access response message or a fallback random access response message. The apparatus according to any one of claims 17 to 23, wherein the second message is message 3 in a random access procedure.
25. A communication device, A processing unit configured to determine a target time domain resource allocation set, wherein the target time domain resource allocation set is a first time domain resource allocation set or a second time domain resource allocation set, A communication unit configured to transmit a first message, the first message containing a first parameter, the first parameter being for determining the interval between the first message and a second message in a time domain, the first parameter being a parameter in the target time domain resource allocation set, and to receive a second message. A communication device equipped with this device.
26. The aforementioned processing unit is When the pre-configured conditions are met, the first time domain resource allocation set is determined as the target time domain resource allocation set, or When the pre-configured conditions are not met, the system is specifically configured to determine the second time domain resource allocation set as the target time domain resource allocation set. The aforementioned pre-set conditions are: The quantity of frequency domain resources for scheduling the first message is greater than the first threshold, or The resource occupied by the third message is a random access resource used by a first type of terminal device to perform random access, the third message is a message preceding the first message, and the third message is from the terminal device. The apparatus according to claim 25, comprising at least one of the following.
27. When the subcarrier interval of the channel in which the first message is located is 15 kHz, the first threshold is 25 resource blocks. When the subcarrier interval of the channel in which the first message is located is 30 kHz, the first threshold is 12 resource blocks, or The apparatus according to claim 26, wherein when the subcarrier spacing of the channel in which the first message is located is 60 kHz, the first threshold is 6 resource blocks.
28. The first time domain resource allocation set is parameter K 2 The apparatus according to any one of claims 25 to 27, comprising N values, each of which is 2 or greater, and N is an integer greater than 0.
29. The aforementioned parameter K 2 When the aforementioned value is equal to 2, the channel mapping mode of the PUSCH where the second message is located is type B, and the index S of the start symbol of the second message is 3 or greater, or The aforementioned parameter K 2 The apparatus according to claim 27, wherein when the value of is greater than 2, the channel mapping mode of the PUSCH in which the second message is located is type A or type B, the index S of the start symbol of the second message is 0 or greater, or is within the range of the resource indication value RIV code of the index S of the start symbol of the second message, and the length L of the symbol occupied by the second message is from 0 to 127.
30. The apparatus according to any one of claims 25 to 29, wherein when the target time domain resource allocation set is the first time domain resource allocation set, the interval determined based on the first parameter is greater than or equal to a second threshold, the second threshold being the minimum time interval between the last symbol of the PDSCH carrying the first message and the first symbol of the PUSCH carrying the second message, and the second threshold corresponding to the first type of terminal device.
31. The apparatus according to any one of claims 25 to 30, wherein at least one of the first time domain resource allocation set and the second time domain resource allocation set is from the network device.
32. The first message is a random access response message or a fallback random access response message. The apparatus according to any one of claims 25 to 31, wherein the second message is message 3 in a random access procedure.
33. A computer program product comprising an instruction, wherein when the instruction is executed, the method according to any one of claims 1 to 16 is executed.
34. A chip including a processor, wherein the processor is coupled to a memory and configured to execute a computer program or instruction stored in the memory, and to cause the chip to execute the method according to any one of claims 1 to 16.
35. A computer-readable storage medium, wherein the storage medium stores a computer program or instruction, and when the computer program or instruction is executed by a communication device, the method according to any one of claims 1 to 16 is executed.
36. A communication system comprising a terminal device configured to perform the method described in any one of claims 1 to 8, and a network device configured to perform the method described in any one of claims 9 to 16.