WO2022028340A1 - 频域资源的确定方法、设备及存储介质 - Google Patents

频域资源的确定方法、设备及存储介质 Download PDF

Info

Publication number
WO2022028340A1
WO2022028340A1 PCT/CN2021/109897 CN2021109897W WO2022028340A1 WO 2022028340 A1 WO2022028340 A1 WO 2022028340A1 CN 2021109897 W CN2021109897 W CN 2021109897W WO 2022028340 A1 WO2022028340 A1 WO 2022028340A1
Authority
WO
WIPO (PCT)
Prior art keywords
frequency domain
terminal device
type
network device
random access
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/109897
Other languages
English (en)
French (fr)
Inventor
侯海龙
郑娟
李超君
费永强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to JP2023508527A priority Critical patent/JP7551899B2/ja
Priority to EP21852128.4A priority patent/EP4192164B1/en
Priority to KR1020237007932A priority patent/KR20230048383A/ko
Priority to ES21852128T priority patent/ES3052424T3/es
Priority to EP25200173.0A priority patent/EP4679928A3/en
Priority to BR112023002181-2A priority patent/BR112023002181B1/pt
Publication of WO2022028340A1 publication Critical patent/WO2022028340A1/zh
Anticipated expiration legal-status Critical
Priority to JP2024152711A priority patent/JP7798984B2/ja
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0836—Random access procedures, e.g. with 4-step access with 2-step access

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method, device and storage medium for determining frequency domain resources.
  • NR new radio
  • REDCAP reduced capability
  • REDCAP-type terminals include typical bandwidths of 5MHz, 10MHz, and 20MHz.
  • BWP bandwidth part
  • BWP is a frequency domain resource for terminals to receive and transmit data, including downlink BWP and uplink BWP.
  • the network side configures an initial downlink BWP (initial downlink BWP) and an initial uplink BWP (initial uplink BWP) for the terminal.
  • Both the initial downlink BWP and the initial uplink BWP are BWPs that are public and exclusive to the cell.
  • FR1 that is, the carrier frequency is less than 6 GHz, and the bandwidth of the initial BWP can reach a maximum of 100 MHz.
  • the bandwidth of a REDCAP type terminal is relatively small, so that this type of terminal may not be able to perform a random access procedure normally, thereby reducing communication reliability.
  • the present application provides a method, device and storage medium for determining frequency domain resources, which help to improve the reliability in the communication process.
  • an embodiment of the present application provides a method for determining frequency domain resources, including: a network device sending configuration information to a terminal device, the configuration information including configuration information of at least two frequency domain resources, the at least two frequency domain resources
  • the domain resources include at least one first type frequency domain resource and at least one second type frequency domain resource; the first type frequency domain resource is used for the first type terminal device and/or the second type terminal device to communicate with the network device ; the second type frequency domain resource is used for the second type terminal device to communicate with the network device; the network device uses one of the at least two frequency domain resources to communicate with the terminal device .
  • the first type of terminal device in the above solution may be an ordinary terminal, and the second type of terminal device may be a REDCAP type terminal or other type of terminal.
  • the terminal device in the above solution may be a common terminal or a REDCAP type terminal.
  • the frequency domain resources configured by the network device for the terminal device in the above solution include N consecutive/non-consecutive physical resource blocks/resource blocks (PRB/RB), where N is a positive integer.
  • PRB/RB physical resource blocks/resource blocks
  • the frequency domain resource includes N consecutive PRBs/RBs
  • the frequency domain resource may be the initial uplink BWP.
  • the network device configures at least two frequency domain resources for the terminal device, and sends configuration information configured with at least two frequency domain resources to the terminal device, so that the terminal device determines, based on the configuration information, which of the at least two frequency domain resources.
  • a frequency domain resource which is used to communicate with the network device, thereby improving the data transmission performance of the terminal device. Since the network device is configured with multiple frequency domain resources, at least one frequency domain resource among the multiple frequency domain resources can be used by the terminal device, so as to avoid that the bandwidth of the frequency domain resource currently configured by the network exceeds the maximum bandwidth supported by the terminal device. , which makes the terminal equipment unable to communicate normally, and improves the communication reliability.
  • the first type of frequency domain resource includes a first initial uplink bandwidth part BWP
  • the second type of frequency domain resource includes a second initial uplink BWP
  • the first type frequency domain resource is used for the first type terminal device and the second type terminal device to communicate with the network device; the method further includes: The network device sends indication information to the terminal device, where the indication information is used to indicate one frequency domain resource among the at least two frequency domain resources, and one frequency domain resource among the at least two frequency domain resources is used for Communication between terminal equipment and network equipment.
  • the first type of frequency domain resources configured by the network device for the terminal device can be used not only for the first type of terminal device to communicate with the network device, but also for the second type of terminal device to communicate with the network device. That is, the first type of frequency domain resources configured by the network device can be shared for use by two types of terminal devices, for example, the first type of frequency domain resources can be used by common terminals and REDCAP type terminals.
  • the first type of frequency domain resource is only used for the first type of terminal device to communicate with the network device, and the method further includes: the network device to the network device The terminal device sends indication information, where the indication information is used to indicate one frequency domain resource in the at least two second type frequency domain resources, and one frequency domain resource in the at least two second type frequency domain resources is used for Terminal devices communicate with network devices.
  • the first-type frequency domain resources configured by the network device for the terminal device can be used for the first-type terminal device to communicate with the network device, but not for the second-type terminal device to communicate with the network device. That is, the first type of frequency domain resources configured by the network device can only be used by the first type of terminal equipment, and the second type of terminal equipment can only use the second type of frequency domain resources but not the first type of frequency domain resources, such as the first type of frequency domain resources.
  • the resources can be used by common terminals, the REDCAP type terminal cannot use the first type of frequency domain resources, and the REDCAP type terminal uses the second type of frequency domain resources to communicate with network equipment.
  • the network device in addition to configuring at least two frequency domain resources for the terminal device and sending configuration information including at least two frequency domain resource configuration information to the terminal device, the network device also sends indication information to the terminal device, The terminal device determines one of the at least two frequency domain resources based on the configuration information and the indication information, and uses the frequency domain resource to communicate with the network device, thereby improving the data transmission performance of the terminal device. Since the network device is configured with multiple frequency domain resources, at least one frequency domain resource among the multiple frequency domain resources can be used by the terminal device, so as to avoid that the bandwidth of the frequency domain resource currently configured by the network exceeds the maximum bandwidth supported by the terminal device. , so that the terminal device cannot communicate normally.
  • the network device sends indication information to the terminal device, the indication information can instruct the terminal device to use one of the frequency domain resources of at least two frequency domain resources, and can also instruct the terminal device to prohibit access or to indicate that the terminal device that has been accessed is prohibited from accessing.
  • the access is beneficial to the network side to perform flexible scheduling among multiple frequency domain resources, so as to achieve the effect of relatively balanced access load of each frequency domain resource, and help to improve user transmission performance.
  • the indication information is included in a random access response message, and the random access response message is used by the network device to respond to the random access request of the terminal device.
  • the network device sends indication information to the terminal device through a random access response message in the random access process, which is used to instruct the terminal device to use one of the at least two frequency domain resources to communicate with the network device, or , indicating that the terminal equipment is prohibited from accessing, or, indicating that the terminal equipment that has been accessed is prohibited from accessing.
  • the random access procedure includes two random access procedures, namely, a 4-step random access procedure (4-Step RACH procedure) and a 2-step random access procedure (2-Step RACH procedure).
  • the indication information is included in Msg2, where the Msg2 is used by the network device to respond to the random access request of the terminal device.
  • Msg2 in this solution belongs to the random access response message of the 4-Step RACH process.
  • the network device sends indication information to the terminal device through Msg2, which is used to instruct the terminal device to use one of the at least two frequency domain resources and the network device. Perform communication, or instruct the terminal device to prohibit access, or instruct the terminal device that has accessed to prohibit access.
  • the indication information is included in the MsgB, where the MsgB is used by the network device to respond to the random access request of the terminal device.
  • the MsgB in this solution belongs to the random access response message of the 2-Step RACH process.
  • the network device sends indication information to the terminal device through MsgB, which is used to instruct the terminal device to use one of the at least two frequency domain resources and the network device. Perform communication, or instruct the terminal device to prohibit access, or instruct the terminal device that has accessed to prohibit access.
  • the indication information includes a physical uplink shared channel PUSCH frequency domain resource allocation indication field in the uplink grant in the random access response message.
  • the indication information is located in at least one high-order bit of a physical uplink shared channel PUSCH frequency domain resource allocation indication field in an uplink grant in the random access response message.
  • the indication information is located in several low-order bits (least significant bits, LSB) of the random access preamble identification RAPID of the MAC subPDU carrying the RAR.
  • the indication information is located in several bits of the reserved bits of the MAC subPDU carrying the RAR.
  • the network device sends indication information to the terminal device through several bits in the random access response message, which is used to instruct the terminal device to use one of the at least two frequency domain resources to communicate with the network device, or to indicate The terminal device prohibits access, or indicates that the access terminal device is prohibited from accessing.
  • the indication information is included in downlink control information DCI, and the DCI is used to schedule a random access response message.
  • the indication information may be included in the DCI for scheduling Msg2, and may also be included in the DCI for scheduling MsgB.
  • the indication information is located in at least one bit of the reserved reserved bits of the DCI.
  • the network device sends indication information to the terminal device through DCI, which is used to instruct the terminal device to use one of the at least two frequency domain resources to communicate with the network device, or to instruct the terminal device to prohibit access, or, Indicates that the connected terminal equipment is prohibited from accessing.
  • the indication information is included in the random access response message and the DCI that schedules the random access response message, and bits in the random access response message and the DCI together indicate to the terminal device communicating with the network device using one of the at least two frequency domain resources.
  • the network device can jointly indicate at least one frequency domain resource of two frequency domain resources through the combination of bits in the DCI and random access response message. , the joint indication can achieve the purpose of saving bit overhead.
  • sending the configuration information by the network device to the terminal device includes: the network device sends the configuration information to the terminal device through system information or high-layer signaling or physical layer signaling.
  • configuration information includes SIB1 and other system information.
  • High-level signaling includes radio resource control layer (radio resource control, RRC) signaling, media access control layer control element (media access control control element, MAC CE) control element, and physical layer signaling includes downlink control information (downlink control information) , DCI) and other signaling.
  • the bandwidth of the second type of frequency domain resources is less than or equal to the maximum bandwidth supported by the terminal device.
  • the bandwidth of the second type of frequency domain resources is less than or equal to the maximum bandwidth supported by the REDCAP type terminal, and typical bandwidths corresponding to the REDCAP type terminal include 5MHz, 10MHz, and 20MHz.
  • the bandwidth of the second type of frequency domain resources is less than or equal to the bandwidth of the first type of frequency domain resources.
  • an embodiment of the present application provides a method for determining frequency domain resources, the method includes: a terminal device receives configuration information from a network device, the configuration information includes configuration information of at least two frequency domain resources, and the at least two frequency domain resources are configured.
  • the two frequency domain resources include at least one first type frequency domain resource and at least one second type frequency domain resource; the first type frequency domain resource is used for the first type terminal device and/or the second type terminal device and the network device communication; the second type frequency domain resource is used for the second type terminal device to communicate with the network device; the terminal device determines one frequency domain of the at least two frequency domain resources according to the configuration information resource; the terminal device communicates with the network device by using one frequency domain resource in the at least two frequency domain resources.
  • the network device sends configuration information to the terminal device, where the configuration information includes configuration information of at least two frequency domain resources, and the terminal device determines one of the at least two frequency domain resources according to the received configuration information, and The frequency domain resource is used to communicate with the network device, thereby improving the data transmission performance of the terminal device. Since the network device is configured with multiple frequency domain resources, at least one frequency domain resource among the multiple frequency domain resources can be used by the terminal device, so as to avoid that the bandwidth of the frequency domain resource currently configured by the network exceeds the maximum bandwidth supported by the terminal device. , so that the terminal device cannot communicate normally.
  • the first type of frequency domain resource includes a first initial uplink bandwidth part BWP
  • the second type of frequency domain resource includes a second initial uplink BWP
  • the first type frequency domain resource is used for the first type terminal device and the second type terminal device to communicate with the network device; the method further includes: The terminal device receives indication information from the network device, where the indication information is used to indicate one frequency domain resource in the at least two frequency domain resources; the terminal device determines according to the configuration information and the indication information One frequency domain resource in the at least two frequency domain resources.
  • the first type of frequency domain resource is only used for the first type of terminal device to communicate with the network device, and the method further includes: the terminal device receives data from the network Indication information of the device, the indication information is used to indicate one frequency domain resource of the at least two second type frequency domain resources; the terminal device determines the at least two frequency domain resources according to the configuration information and the indication information One frequency domain resource in the second type of frequency domain resources.
  • the terminal device in addition to receiving configuration information from the network device, the terminal device also receives indication information from the network device, and the terminal device determines one of the at least two frequency domain resources based on the configuration information and the indication information. resource, and use the frequency domain resource to communicate with the network device, thereby improving the data transmission performance of the terminal device. Since the network device is configured with multiple frequency domain resources, at least one frequency domain resource among the multiple frequency domain resources can be used by the terminal device, so as to avoid that the bandwidth of the frequency domain resource currently configured by the network exceeds the maximum bandwidth supported by the terminal device. , so that the terminal device cannot communicate normally.
  • the indication information is included in a random access response message, and the random access response message is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in Msg2, where the Msg2 is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in the MsgB, where the MsgB is used by the network device to respond to the random access request of the terminal device.
  • the indication information is located in the physical uplink shared channel PUSCH frequency domain resource allocation indication field in the uplink grant in the random access response message.
  • the indication information is located in at least one high-order bit of a physical uplink shared channel PUSCH frequency domain resource allocation indication field in an uplink grant in the random access response message.
  • the indication information is located in several low-order bits (least significant bits, LSB) of the random access preamble identification RAPID of the MAC subPDU carrying the RAR.
  • the indication information is located in several bits of the reserved bits of the MAC subPDU carrying the RAR.
  • the indication information is included in downlink control information DCI, where the DCI is used to schedule a random access response message, and the random access response message is used by the network device to respond to the random access of the terminal device ask.
  • the indication information is included in the reserved bits of the DCI.
  • the indication information is included in the random access response message and the DCI that schedules the random access response message, and bits in the random access response message and the DCI together indicate to the terminal device communicating with the network device using one of the at least two frequency domain resources.
  • the bandwidth of the second type of frequency domain resources is less than or equal to the maximum bandwidth supported by the terminal device.
  • the bandwidth of the second type frequency domain resource is less than or equal to the maximum bandwidth supported by the REDCAP type terminal.
  • the bandwidth of the second type of frequency domain resources is less than or equal to the bandwidth of the first type of frequency domain resources.
  • the terminal device receiving the configuration information from the network device includes: the terminal device receives the configuration information from the network device from system information or high-layer signaling or physical layer signaling information.
  • an embodiment of the present application provides a network device, including: a transceiver module configured to send configuration information to a terminal device, where the configuration information includes configuration information of at least two frequency domain resources, the at least two frequency domain resources
  • the resources include at least one first type frequency domain resource and at least one second type frequency domain resource; the first type frequency domain resource is used for the first type terminal device and/or the second type terminal device to communicate with the network device; The second type frequency domain resource is used for the second type terminal device to communicate with the network device; the processing module is configured to use one frequency domain resource in the at least two frequency domain resources to communicate with the terminal device .
  • the first type of frequency domain resource includes a first initial uplink bandwidth part BWP
  • the second type of frequency domain resource includes a second initial uplink BWP
  • the first type frequency domain resource is used for the first type terminal device and the second type terminal device to communicate with the network device; the transceiver module is further configured to send to the terminal device indication information, where the indication information is used to indicate one frequency domain resource in the at least two frequency domain resources.
  • the first type frequency domain resource is only used for the first type terminal device to communicate with the network device, and the transceiver module is further configured to send indication information to the terminal device, the indication information It is used to indicate a second type frequency domain resource in the at least two frequency domain resources.
  • the indication information is included in a random access response message, and the random access response message is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in Msg2, where the Msg2 is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in the MsgB, where the MsgB is used by the network device to respond to the random access request of the terminal device.
  • the indication information is located in the physical uplink shared channel PUSCH frequency domain resource allocation indication field in the uplink grant in the random access response message.
  • the indication information is located in at least one high-order bit of a physical uplink shared channel PUSCH frequency domain resource allocation indication field in an uplink grant in the random access response message.
  • the indication information is included in downlink control information DCI, where the DCI is used to schedule a random access response message, and the random access response message is used by the network device to respond to the random access of the terminal device ask.
  • the indication information is included in the reserved bits of the DCI.
  • the indication information is included in the random access response message and the DCI that schedules the random access response message, and bits in the random access response message and the DCI together indicate to the terminal device communicating with the network device using one of the at least two frequency domain resources.
  • the bandwidth of the second type of frequency domain resources is less than or equal to the maximum bandwidth supported by the terminal device.
  • the transceiver module is specifically configured to send the configuration information to the terminal device through system information or high-layer signaling or physical layer signaling.
  • an embodiment of the present application provides a terminal device, including: a transceiver module configured to receive configuration information from a network device, where the configuration information includes configuration information of at least two frequency domain resources, the at least two frequency domain resources
  • the domain resources include at least one first type frequency domain resource and at least one second type frequency domain resource; the first type frequency domain resource is used for the first type terminal device and/or the second type terminal device to communicate with the network device; the second type frequency domain resource is used for the second type terminal device to communicate with the network device; the processing module is configured to determine one frequency domain resource in the at least two frequency domain resources according to the configuration information, communicating with the network device using one of the at least two frequency domain resources.
  • the first type of frequency domain resource includes a first initial uplink bandwidth part BWP
  • the second type of frequency domain resource includes a second initial uplink BWP
  • the first type frequency domain resource is used for the first type terminal device and the second type terminal device to communicate with the network device; the transceiver module is further configured to receive an indication from the network device information, the indication information is used to indicate one frequency domain resource in the at least two frequency domain resources; the processing module is specifically configured to determine the at least two frequency domain resources according to the configuration information and the indication information A frequency domain resource in .
  • the first type frequency domain resource is only used for the first type terminal device to communicate with the network device;
  • the transceiver module is further configured to receive indication information from the network device, and the indication information is used for indicating one frequency domain resource of the at least two second type frequency domain resources;
  • the processing module is specifically configured to determine, according to the configuration information and the indication information, one of the at least two second type frequency domain resources a frequency domain resource.
  • the indication information is included in a random access response message, and the random access response message is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in Msg2, where the Msg2 is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in the MsgB, where the MsgB is used by the network device to respond to the random access request of the terminal device.
  • the indication information is located in the physical uplink shared channel PUSCH frequency domain resource allocation indication field in the uplink grant in the random access response message.
  • the indication information is located in at least one high-order bit of a physical uplink shared channel PUSCH frequency domain resource allocation indication field in an uplink grant in the random access response message.
  • the indication information is included in downlink control information DCI, where the DCI is used to schedule a random access response message, and the random access response message is used by the network device to respond to the random access of the terminal device ask.
  • the indication information is included in the reserved bits of the DCI.
  • the indication information is included in the random access response message and the DCI that schedules the random access response message, and bits in the random access response message and the DCI together indicate to the terminal device communicating with the network device using one of the at least two frequency domain resources.
  • the bandwidth of the second type of frequency domain resources is less than or equal to the maximum bandwidth supported by the terminal device.
  • the transceiver module is specifically configured to receive configuration information from the network device from system information or high-level signaling or physical layer signaling.
  • an embodiment of the present application provides a network device, including: a memory and a processor, where the memory is used to store program instructions, and the processor is used to call the program instructions stored in the memory to implement the first aspect. The method of any one.
  • an embodiment of the present application provides a terminal device, including: a memory and a processor, where the memory is used to store program instructions, and the processor is used to call the program instructions stored in the memory to implement the second aspect. The method of any one.
  • an embodiment of the present application provides a readable storage medium, including: an execution instruction is stored in the readable storage medium, and when at least one processor of a network device executes the execution instruction, the network device executes the first execution instruction.
  • an execution instruction is stored in the readable storage medium, and when at least one processor of a network device executes the execution instruction, the network device executes the first execution instruction.
  • an embodiment of the present application provides a readable storage medium, including: an execution instruction is stored in the readable storage medium, and when at least one processor of a terminal device executes the execution instruction, the terminal device executes the first execution instruction.
  • an execution instruction is stored in the readable storage medium, and when at least one processor of a terminal device executes the execution instruction, the terminal device executes the first execution instruction. The method of any one of the two aspects.
  • an embodiment of the present application provides a chip, including: a processor and an interface, configured to call and run a computer program stored in the memory from a memory, and execute the method described in any one of the first aspects.
  • an embodiment of the present application provides a chip, including: a processor and an interface, configured to call and run a computer program stored in the memory from a memory, and execute the method according to any one of the second aspects.
  • an embodiment of the present application provides a communication system, including: at least one network device according to the fifth aspect and a terminal device according to the sixth aspect, wherein the network device can be used to perform any one of the first aspects.
  • the terminal device can be used to execute the method described in any one of the second aspect.
  • Embodiments of the present application provide a method, device, and storage medium for determining frequency domain resources.
  • the method includes: a network device preconfigures at least two frequency domain resources for a terminal device, wherein the at least two frequency domain resources include at least one first type frequency domain resources and at least one second type frequency domain resource, the first type frequency domain resource is used for the first type terminal device and/or the second type terminal device to communicate with the network device, the second type frequency domain resource is used for The second type of terminal equipment communicates with network equipment.
  • the network device sends configuration information configured with at least two frequency domain resources to the terminal device, and the terminal device determines one of the at least two frequency domain resources according to the configuration information, and uses the frequency domain resource to communicate with the network device.
  • the network device configures multiple frequency domain resources for the terminal device, at least one frequency domain resource among the multiple frequency domain resources can be used by the terminal device, which can prevent the bandwidth of the frequency domain resource configured in the prior art from exceeding the terminal device.
  • the maximum bandwidth supported by the device makes the terminal device unable to communicate with the network device normally, which improves the reliability of data transmission of the communication system.
  • FIG. 1 is a system architecture diagram provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of a random access process according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a random access process according to an embodiment of the present application.
  • FIG. 4 is an interactive schematic diagram of a method for determining frequency domain resources provided by an embodiment of the present application
  • FIG. 5 is a schematic diagram of frequency domain resources configured by a network device for a terminal device according to an embodiment of the present application
  • FIG. 6 is an interactive schematic diagram of a method for determining frequency domain resources provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a PUSCH frequency domain resource allocation field in a random access response RAR provided by the implementation of the present application;
  • FIG. 8 is a schematic structural diagram of a MAC RAR provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of downlink control information DCI reserved bits indicating initial uplink BWP provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a terminal device according to an embodiment of the application.
  • FIG. 12 is a schematic diagram of a hardware structure of a network device according to an embodiment of the application.
  • FIG. 13 is a schematic diagram of a hardware structure of a terminal device according to an embodiment of the present application.
  • FIG. 1 is a system architecture diagram provided by an embodiment of the present application.
  • an embodiment of the present application provides a communication system.
  • the communication system 100 includes a network device 110 and a plurality of terminal devices, such as the one shown in FIG. 1 .
  • Terminal devices 101 to 106 The network device 110 is connected to the terminal devices 101 to 106 in communication respectively.
  • the terminal device 104 and the terminal device 106 may also be communicatively connected to the network device 110 through the terminal device 105 .
  • the terminal device involved in the embodiments of this application may also be referred to as a terminal, which may be a device with a wireless transceiver function, which may be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it may also be deployed on water (such as ships, etc.); can also be deployed in the air (such as on airplanes, balloons, satellites, etc.).
  • the terminal device may be a user equipment (user equipment, UE), wherein the UE includes a handheld device, a vehicle-mounted device, a wearable device or a computing device with a wireless communication function.
  • the UE may be a mobile phone, a tablet computer, or a computer with a wireless transceiver function.
  • the terminal device may also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, intelligent Wireless terminals in power grids, wireless terminals in smart cities, wireless terminals in smart homes, and so on.
  • the device for realizing the function of the terminal may be a terminal; it may also be a device capable of supporting the terminal to realize the function, such as a chip system, and the device may be installed in the terminal.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the network device involved in the embodiments of the present application includes a base station (base station, BS), which may be a device deployed in a wireless access network and capable of wirelessly communicating with a terminal.
  • the base station may have various forms, such as a macro base station, a micro base station, a relay station, and an access point.
  • the base station involved in the embodiment of the present application may be a base station in 5G or a base station in LTE, where the base station in 5G may also be called a transmission reception point (transmission reception point, TRP) or gNB.
  • the apparatus for implementing the function of the network device may be a network device; it may also be an apparatus capable of supporting the network device to implement the function, such as a chip system, and the apparatus may be installed in the network device.
  • the technical solutions of the embodiments of the present application can be applied to the Long Term Evolution (Long Term Evolution, LTE) architecture, and can also be applied to the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UMTS Terrestrial Radio Access Network, UTRAN) ) architecture, or the GSM EDGE Radio Access Network (GERAN) architecture of the Global System for Mobile Communication (GSM)/Enhanced Data Rate for GSM Evolution (EDGE) system .
  • UMTS Universal Mobile Telecommunications System
  • UTRAN Universal Mobile Telecommunications System
  • GERAN GSM EDGE Radio Access Network
  • GSM Global System for Mobile Communication
  • EDGE Enhanced Data Rate for GSM Evolution
  • the technical solutions provided in the embodiments of the present application can also be applied to any other wireless communication systems with similar structures and functions, such as a public land mobile network (Public Land Mobile Network, PLMN) system, a 5G communication system or communication after 5G system, etc., this embodiment of the present application does not make any limitation. It should be noted that the technical solutions provided in the embodiments of the present application can also be applied to a machine-to-machine (M2M) system, which is mainly used for the air interface physical layer process, and the system architecture of which can follow the existing NR system architecture. .
  • M2M machine-to-machine
  • the wireless communication between communication devices may include: wireless communication between a network device and a terminal, wireless communication between a network device and a network device, and wireless communication between a terminal and a terminal.
  • wireless communication may also be referred to as “communication” for short, and the term “communication” may also be described as “data transmission”, “information transmission” or “transmission”.
  • Those skilled in the art can use the technical solutions provided in the embodiments of the present application for wireless communication between network devices and terminals, such as wireless communication between access network devices and terminals, and wireless communication between core network devices and terminals.
  • the bandwidth part BWP is defined in the NR system, which is used by the terminal to receive or transmit data.
  • the network side configures an initial downlink BWP (initial downlink BWP) and an initial uplink BWP (initial uplink BWP) for the terminal.
  • Both the initial downlink BWP and the initial uplink BWP are BWPs that are public and dedicated to the cell.
  • the base station can configure user-specific downlink BWP and uplink BWP for each terminal through Radio Resource Control (RRC) dedicated signaling, and the user-specific uplink and downlink BWP can be configured for each terminal.
  • RRC Radio Resource Control
  • the network side can configure the initial uplink and downlink BWP for the terminal through RRC dedicated signaling.
  • the network side configures one of the BWPs for the terminal as the activated BWP, and the terminal works on the currently activated BWP.
  • the maximum bandwidth of the initial downlink BWP is 20MHz, and the configuration of the initial uplink BWP is not limited, and the maximum bandwidth can reach 100MHz.
  • the NR R17 REDCAP project is aimed at the Internet of Things scenario, and considers introducing a new type of terminal. Compared with the existing NR terminal, the terminal has the characteristics of reduced bandwidth, reduced processing speed, and reduced number of antennas. This type of terminal is called REDCAP type. terminal.
  • REDCAP-type terminals may support one or more bandwidths, and typical bandwidths include 5MHz, 10MHz, and 20MHz.
  • the existing initial uplink BWP bandwidth of the NR system may exceed the bandwidth of the REDCAP type terminal, resulting in the REDCAP type terminal being unable to perform random access procedures or early data transmission.
  • the embodiments of the present application provide a method for determining frequency domain resources, which is mainly aimed at REDCAP type terminals in a communication system, considering that new frequency domain resources are configured for them, and the bandwidth of the configured new frequency domain resources is different. Exceeds the bandwidth of REDCAP-type endpoints. It can be understood that in the Internet of Things scenario, the number of connected terminals will be very large. Considering that the uplink transmission includes msg1, msg3, and early data transmission, etc., this will lead to a heavy uplink load. Therefore, the network side can configure at least two terminals for the terminal. frequency domain resources to achieve the purpose of load balancing.
  • the frequency domain resources configured by the network device for the terminal device in the embodiment of the present application include N consecutive/non-consecutive physical resource blocks/resource blocks (PRB/RB), where N is a positive integer.
  • PRB/RB physical resource blocks/resource blocks
  • the frequency domain resource includes N consecutive PRBs/RBs, and the frequency domain resource may be the initial uplink BWP.
  • network access can be completed through an uplink random access procedure.
  • data transmission can also be completed in the random access process.
  • the network side can also instruct the terminal to perform random access to regain timing advance (TA) synchronization. Beam recovery is performed during the entry process.
  • the current random access procedure in NR includes the following two types: 4-step random access procedure (4-Step RACH procedure) defined by NR R15 and 2-step random access procedure (2-Step RACH procedure) defined by NR R16 .
  • FIG. 2 is a schematic diagram of a random access process provided by an embodiment of the present application.
  • the random access process provided by this embodiment is a 4-Step RACH process, which mainly includes the following steps:
  • Step 101 the gNB sends the resource configuration of the physical random access channel PRACH to the terminal device.
  • the gNB sends the PRACH resource configuration to the terminal device through a system broadcast message, which mainly includes PRACH time-frequency domain resources, preamble preamble sequences, and the like.
  • the time-frequency resource for the gNB to transmit and receive the physical random access channel PRACH is called a random access opportunity (RACH occasion, RO).
  • RO random access opportunity
  • the gNB can be configured with multiple mutually orthogonal preambles, and different terminal devices can use different or the same preamble on the same RO for random access.
  • Step 102 the terminal device sends Msg1 to the gNB through PRACH.
  • Msg1 includes the preamble preamble.
  • the gNB detects the preambles sent by each terminal device on the RO resource, and if the preambles are detected, the gNB performs step 103 in response to the random access request of each terminal device.
  • Step 103 the gNB sends the Msg2 including the random access response RAR to the terminal device.
  • the gNB can schedule the downlink physical shared channel PDSCH through the random access wireless network temporary identifier RA-RNTI to scramble the DCI format 1_0 of the cyclic redundancy check CRC, and the PDSCH carries all the data for the RO. or RAR for partial random access request.
  • the same RO is associated with only one RA-RNTI.
  • the terminal device After sending the Msg1, the terminal device starts a random access response window, and monitors the RAR sent by the network side in this window.
  • step 104 is executed. Specifically, if the terminal device receives the physical downlink control channel PDCCH scrambled with RA-RNTI, and the RAR carried by the PDSCH scheduled by the PDCCH includes a random access preamble identifier with the same preamble index as the sent preamble index RAPID to identify the MAC subPDU, the random access is considered successful.
  • the terminal device If the terminal device does not detect the RAR, the random access fails, and the terminal device re-initiates the random access procedure according to the fallback parameter indicated by the gNB until the maximum number of random access times is reached.
  • Step 104 The terminal device sends Msg3 to the gNB according to the RAR instruction.
  • the main function of the Msg3 is to send an RRC connection establishment request, and the Msg3 carries the identification ID of the terminal device.
  • Msg3 can also carry service data (UL small data).
  • service data UL small data
  • Step 105 the gNB sends Msg4 (feedback) to the terminal device.
  • the terminal device After the terminal device sends the Msg3, it monitors the Msg4 delivered by the network side, and the Msg4 carries the conflict resolution identifier and the air interface parameter configuration for the terminal device. If the terminal device successfully receives Msg4, the random access is successful, and the terminal device sends Msg5 to the gNB, where Msg5 is used to send an RRC establishment complete command. If the terminal device does not receive Msg4, the random access fails, and the terminal device re-initiates the random access procedure according to the fallback parameter indicated by the gNB until the maximum number of random access times is reached.
  • Msg2 and Msg4 are transmitted on the initial downlink BWP, and Msg1 and Msg3 are transmitted on the initial uplink BWP.
  • Msg1 and Msg3 are transmitted on the initial uplink BWP.
  • the protocol defines that all configured PRACH resources must be completely within the initial uplink BWP range.
  • FIG. 3 is a schematic diagram of a random access process provided by an embodiment of the present application.
  • the random access process provided by this embodiment is a 2-Step RACH process, which mainly includes the following steps:
  • Step 201 the terminal device sends the MsgA to the gNB.
  • the MsgA sent by the terminal device includes Msg1 and Msg3 in the 4-Step RACH process, such as the preamble and the ID of the terminal device.
  • MsgA can also carry service data.
  • Step 202 the gNB sends the MsgB to the terminal device.
  • MsgB is equivalent to Msg2 (RAR) and Msg4 (feedback) in the 4-Step RACH process.
  • the gNB can schedule the PDSCH through the DCI format 1_0 of the MsgB-RNTI/RA-RNTI scrambled CRC, and the PDSCH carries the RAR for all or part of the random access request for the RO.
  • the same RO is associated with only one MsgB-RNTI/RA-RNTI.
  • the terminal device After sending the preamble, the terminal device starts the random access response time window MsgB-response window, and monitors the PDCCH of the MsgB-RNTI scrambled CRC sent by the gNB in the MsgB-response window.
  • the physical downlink control channel PDCCH, and the RAR carried by the PDSCH scheduled by the PDCCH contains a MAC subPDU identified by the same random access preamble identifier RAPID as the sent preamble inde, then the random access is considered successful. . Otherwise, the random access is considered to have failed.
  • the 2-Step RACH will fall back to the 4-Step RACH, and the RAR returned by the gNB is fallbackRAR. If both the preamble and PUSCH of the terminal device are detected successfully, the RAR returned by the gNB is successRAR.
  • MsgB is transmitted on the initial downlink BWP
  • MsgA is transmitted on the initial uplink BWP.
  • the protocol defines that all configured PRACH resources must be completely within the initial upstream BWP range.
  • FIG. 4 is an interactive schematic diagram of a method for determining frequency domain resources provided by an embodiment of the present application. As shown in FIG. 4 , the method provided by this embodiment includes the following steps:
  • Step 301 The network device configures at least two frequency domain resources for the terminal device.
  • the at least two frequency domain resources include at least one first type frequency domain resource and at least one second type frequency domain resource.
  • the first type frequency domain resource is used for the first type terminal device and/or the second type terminal device to communicate with the network device
  • the second type frequency domain resource is used for the second type terminal device to communicate with the network device.
  • the first type of terminal equipment may be an ordinary terminal
  • the second type of terminal equipment may be a REDCAP type terminal or other terminal.
  • first type of terminal device may include at least one of the following:
  • the carrier bandwidth of the second type terminal equipment is not greater than 50MHz, such as at least one of 50MHz, 40MHz, 20MHz, 15MHz, 10MHz or 5MHz, and the carrier bandwidth of the first type terminal equipment is greater than 50MHz.
  • the number of transceiver antennas is different.
  • the second type of terminal device may support 2-receive and 1-transmit (2 receive antennas and 1 transmit antenna), or 1-receive and 1-transmit (1 receive antenna and 1 transmit antenna).
  • the first type of terminal equipment can support 4 receive and 2 transmit (4 receive antennas and 2 transmit antennas). It can be understood that, under the condition of realizing the same data transmission rate, since the number of transceiver antennas of the second type terminal equipment is less than the number of transceiver antennas of the first type terminal equipment, there is no difference between the second type terminal equipment and the base station.
  • the maximum coverage that can be achieved by the data transmission of the first type is smaller than the maximum coverage that can be achieved by the data transmission between the first type terminal device and the base station.
  • the uplink maximum transmit power is different.
  • the maximum uplink transmit power of the second type of terminal equipment may be a value between 4 decibel milliwatts (dBm) and 20 dBm.
  • the maximum uplink transmit power of the first type terminal equipment may be 23dBm or 26dBm.
  • the protocol version is different.
  • the second type of terminal equipment may be a terminal equipment in NR release 17 (release-17, Rel-17) or a later version of NR Rel-17.
  • the first type of terminal device may be, for example, a terminal device in NR release 15 (release-15, Rel-15) or NR release 16 (release-16, Rel-16).
  • the first type of terminal equipment may also be referred to as NR legacy (NR legacy) terminal equipment.
  • the second type of terminal equipment does not support carrier aggregation
  • the first type of terminal equipment may support carrier aggregation.
  • both the first type of terminal equipment and the second type of terminal equipment can support carrier aggregation, but the maximum number of carrier aggregations simultaneously supported by the second type of terminal equipment is smaller than the maximum number of carrier aggregations simultaneously supported by the first type of terminal equipment.
  • the terminal equipment of the second type supports aggregation of 2 carriers at the same time
  • the terminal equipment of the first type can support the aggregation of 5 carriers or 32 carriers at the same time.
  • the second type of terminal equipment supports half-duplex frequency division duplexing (FDD).
  • the first type of terminal equipment supports full duplex FDD.
  • the data processing time capability is different.
  • the minimum delay between receiving downlink data and sending feedback on the downlink data by the second type terminal equipment is greater than the minimum delay between receiving the downlink data and sending feedback on the downlink data by the first type terminal equipment; and/ Or, the minimum delay between sending uplink data and receiving feedback on the uplink data by the second type terminal device is greater than the minimum delay between sending uplink data and receiving feedback on the uplink data by the first type terminal device.
  • the baseband processing capability of the terminal device of the second type is lower than the baseband processing capability of the terminal device of the first type.
  • the baseband processing capability may include at least one of the following: the maximum number of multiple input multiple output (MIMO) layers supported by the terminal device during data transmission, and the hybrid automatic repeat request (Hybrid Automatic Repeat reQuest) supported by the terminal device. , HARQ) process number, the maximum transmission block size (TBS) supported by the terminal device.
  • the upstream and/or downstream transmission peak rates are different.
  • the peak transmission rate refers to the maximum data transmission rate that a terminal device can achieve in a unit time (eg, per second).
  • the uplink peak rate supported by the second type of terminal equipment may be lower than the uplink peak rate supported by the first type of terminal equipment, and/or the downlink peak rate supported by the second type of terminal equipment may be lower than the downlink peak rate supported by the first type of terminal equipment .
  • the peak uplink rate of the second type terminal equipment is less than or equal to 50Mbps
  • the peak downlink rate is less than or equal to 150Mbps
  • the peak uplink rate of the first type terminal equipment is greater than or equal to 50Mbps
  • the peak downlink rate is greater than or equal to 150Mbps.
  • the peak uplink rate or downlink rate of the second type of terminal equipment is in the order of hundreds of Mbps
  • the peak uplink rate or downlink peak rate of the first type of terminal equipment is in the order of Gbps.
  • the buffer size is different.
  • the cache buffer can be understood as the total size of the layer 2 (Layer 2, L2) cache, which is defined as the word buffered in the radio link control (radio link control, RLC) transmission window and reception and reordering window of the terminal device for all radio bearers The sum of the number of sections and the number of bytes buffered in the Packet Data Convergence Protocol (PDCP) reordering window.
  • the buffer buffer can also be understood as the total number of soft channel bits that can be used by HARQ processing.
  • FIG. 5 is a schematic diagram of frequency domain resources configured by a network device for a terminal device according to an embodiment of the present application.
  • a network device configures a first-type frequency domain resource and a second-type frequency domain resource for the terminal device.
  • the first type of frequency domain resources and the second type of frequency domain resources are two consecutive frequency domain resources in the frequency domain.
  • the first type of frequency domain resources and the second type of frequency domain resources are two frequency domain resources that are discontinuous in the frequency domain.
  • the first type of frequency domain resources and the second type of frequency domain resources have overlapping parts.
  • the initial uplink BWP is taken as the frequency domain resource
  • the first initial uplink BWP is taken as the first type of frequency domain resource
  • the second initial uplink BWP is taken as the second type of frequency domain resource.
  • the frequency domain resource may also be the downlink BWP. .
  • the network device configures at least two initial uplink BWPs for the terminal device, including: a first initial uplink BWP and at least one second initial uplink BWP.
  • the first initial uplink BWP is an initial uplink BWP configured by the network side for the terminal device in the existing protocol, and may also be called UL initial BWP, which can be used for common terminals to communicate with network devices.
  • the first The initial upstream BWP can also be used for REDCAP type terminals to communicate with network equipment.
  • the second initial upstream BWP is an initial upstream BWP newly configured by the network side for the terminal device, and the second initial upstream BWP may be used for the REDCAP type terminal to communicate with the network device.
  • the configured second initial uplink BWP may only be used for REDCAP type terminals.
  • the network device configures the terminal device with bandwidths of two second initial upstream BWPs, respectively 20 MHz and 10 MHz, or 20 MHz and 5 MHz, and the bandwidths of the two second initial upstream BWPs can be used for REDCAP-type terminals and networks.
  • the bandwidth limitation supported by the REDCAP terminal device can be fully considered during the configuration of the dedicated BWP, so as to ensure that the REDCAP terminal device can successfully connect to the REDCAP terminal device through the second initial upstream BWP.
  • the second initial upstream BWP with different bandwidths can be configured for REDCAP terminals with different bandwidths, which can effectively avoid the problem that REDCAP terminals cannot access the existing first initial upstream BWP due to bandwidth limitations, and can also pass Configuring new second initial uplink BWPs of different types achieves the effect of balancing the access loads of different BWPs.
  • the configured second initial uplink BWP may be used for both REDCAP-type terminals and common terminals.
  • the network device configures the terminal device with a bandwidth of a second initial upstream BWP of 20 MHz, and the bandwidth of the second initial upstream BWP can be used for some REDCAP-type terminals to communicate with the network device, and can also be used for common terminals and network devices.
  • the configuration of the second initial uplink BWP can effectively alleviate the overload of the first initial uplink BWP, while taking into account the access capability of REDCAP type terminals, improving the second initial uplink BWP. usage efficiency.
  • the REDCAP type terminal may be a massive machine type communication (massive Machine Type of Communication, mMTC) terminal, a low-capacity terminal, or an Internet of Things terminal, which is not limited in this embodiment of the present application.
  • massive machine type communication massive Machine Type of Communication, mMTC
  • mMTC massive Machine Type of Communication
  • the bandwidth relationship between the second initial upstream BWP and the first initial upstream BWP includes the following possible situations:
  • the network device is configured with a second initial uplink BWP and a first initial uplink BWP, and the bandwidth of the second initial uplink BWP is less than or equal to the bandwidth of the first initial uplink BWP.
  • the terminal device may directly determine one BWP among the at least two initial uplink BWPs according to the configuration information from the network device, and use the BWP to communicate with the network device.
  • One of the at least two initial uplink BWPs determined by the terminal device may be the first initial uplink BWP (provided that the bandwidth of the first initial uplink BWP is less than or equal to the maximum bandwidth supported by the terminal device), or the second initial uplink BWP.
  • the terminal device can directly determine access to the second initial uplink BWP according to the configuration information, without the need for additional instruction information to indicate.
  • the network device is configured with at least two second initial uplink BWPs and one first initial uplink BWP, and the bandwidth of each of the at least two second initial uplink BWPs is less than or equal to is equal to the bandwidth of the first initial upstream BWP.
  • the terminal device may determine one second initial uplink BWP from at least two second initial uplink BWPs according to the configuration information, and use the second initial uplink BWP to communicate with the network device.
  • the terminal device may, according to the configuration information, determine a BWP from the first initial uplink BWP (provided that the bandwidth of the first initial uplink BWP is less than or equal to the maximum bandwidth supported by the terminal device) and at least two initial uplink BWPs, and use the BWP Communicate with network devices.
  • the network device is configured with at least two second initial upstream BWPs and one first initial upstream BWP, and the bandwidth of a part of the second initial upstream BWPs in the at least two second initial upstream BWPs is less than or equal to this
  • the bandwidth of the first initial upstream BWP, and the bandwidth of another part of the second initial upstream BWP is greater than the bandwidth of the first initial upstream BWP.
  • the network device is configured with at least one second initial uplink BWP and multiple first initial uplink BWPs.
  • the bandwidth of each second initial uplink BWP in the second initial uplink BWP is less than or equal to the maximum bandwidth supported by the terminal device, and the bandwidth of at least one of the multiple first initial uplink BWPs is less than or equal to the bandwidth of the first initial uplink BWP. Equal to the maximum bandwidth supported by the end device.
  • the terminal device may determine a BWP from at least one second initial uplink BWP and at least one first initial uplink BWP among the multiple first initial uplink BWPs according to the configuration information, and use the BWP to communicate with the network device.
  • the bandwidth of part of the second initial uplink BWPs in the second initial uplink BWPs is less than or equal to the maximum bandwidth supported by the terminal device, and the bandwidth of at least one first initial uplink BWP among the plurality of first initial uplink BWPs is less than or equal to The maximum bandwidth supported by the end device.
  • the terminal device may, according to the configuration information, determine a BWP from a part of the second initial uplink BWPs and at least one first initial uplink BWP among the multiple first initial uplink BWPs, and use the BWP to communicate with the network device.
  • the relationship between the first initial upstream BWP and the maximum bandwidth supported by the terminal device includes the following possible situations:
  • the network device is configured with a first initial upstream BWP, and the bandwidth of the first initial upstream BWP is less than or equal to the maximum bandwidth supported by the terminal device, or the bandwidth of the first initial upstream BWP is greater than that of the terminal device. Maximum bandwidth supported.
  • the network device is configured with at least two first initial upstream BWPs, and the bandwidth of each of the at least two first initial upstream BWPs is greater than the maximum bandwidth supported by the terminal device, or , the bandwidth of at least one of the at least two first initial uplink BWPs is less than or equal to the maximum bandwidth supported by the terminal device.
  • the relationship between the second initial upstream BWP and the maximum bandwidth supported by the terminal device includes the following possible situations:
  • the network device is configured with a second initial upstream BWP, and the bandwidth of the second initial upstream BWP is less than or equal to the maximum bandwidth supported by the terminal device.
  • the network device is configured with at least two second initial uplink BWPs, and the bandwidths of all second initial uplink BWPs in the at least two second initial uplink BWPs are less than or equal to the maximum bandwidth supported by the terminal device.
  • the network device is configured with at least two second initial uplink BWPs, and the bandwidth of a part of the second initial uplink BWPs in the at least two second initial uplink BWPs is less than or equal to the maximum bandwidth supported by the terminal device.
  • the maximum bandwidth supported by the terminal device may refer to the maximum bandwidth supported by the terminal of the REDCAP type.
  • the maximum bandwidth supported by a REDCAP type terminal includes 5MHz, 10MHz, and 20MHz.
  • the network device if the network device is only configured with the first initial upstream BWP, no dedicated initial upstream BWP is configured for the REDCAP type terminal, and the bandwidth of the first initial upstream BWP is greater than the maximum bandwidth supported by the REDCAP type terminal , it can be understood that the network device has implicitly indicated that the REDCAP terminal is prohibited from accessing the cell.
  • the network device is configured with a first initial upstream BWP and an initial upstream BWP dedicated to a REDCAP terminal, and the bandwidth of the first initial upstream BWP is greater than the maximum bandwidth supported by a REDCAP terminal.
  • the REDCAP type terminal in this example can use the above-mentioned dedicated initial uplink BWP to send uplink data.
  • the network device is configured with a first initial upstream BWP and a dedicated initial upstream BWP for REDCAP terminals, and the bandwidth of the first initial upstream BWP is less than or equal to the maximum bandwidth supported by REDCAP terminals.
  • the REDCAP type terminal in this example can use the first initial uplink BWP or the above-mentioned dedicated initial uplink BWP to send uplink data.
  • Step 302 The network device sends configuration information to the terminal device, where the configuration information includes configuration information of at least two frequency domain resources.
  • the initial uplink BWP is used as the frequency domain resource, and it should be understood that the frequency domain resource may also be the downlink BWP.
  • the network device may send configuration information to the terminal device through system information, where the system information includes SIB1 and other system information.
  • the network device may also send configuration information through higher-layer signaling such as radio resource control layer RRC signaling, medium access control layer control element MAC CE control element, and the like.
  • the network device may also send configuration information through physical layer signaling such as downlink control information DCI.
  • the configuration information of any one of the at least two initial uplink BWPs includes the frequency domain location and bandwidth of the BWP, random access channel RACH configuration information, physical uplink shared channel PUSCH configuration information, physical uplink control channel PUCCH configuration information and other uplink configuration information Transfer configuration information or part of it.
  • Step 303 The terminal device determines one frequency domain resource of at least two frequency domain resources according to the configuration information.
  • the terminal device may also determine one frequency domain of the at least two frequency domains according to a predefined or preconfigured rule.
  • step 303 in this embodiment may be used as an optional step.
  • Step 304 The terminal device communicates with the network device by using one frequency domain resource among the at least two frequency domain resources.
  • the initial uplink BWP is taken as the frequency domain resource
  • the first initial uplink BWP is taken as the first type of frequency domain resource
  • the second initial uplink BWP is taken as the second type of frequency domain resource.
  • the frequency domain resource may also be the downlink BWP. .
  • the terminal device can communicate with the network device according to the first initial uplink BWP of the at least two initial uplink BWPs configured in the configuration information, that is, still through the initial uplink BWP Communicate with network devices.
  • the terminal device A second initial upstream BWP among the initial upstream BWPs communicates with the network device.
  • the terminal device can communicate with the network device according to at least one second initial uplink BWP among the at least two initial uplink BWPs configured in the configuration information.
  • the terminal device can Any one of the second initial upstream BWPs communicates with the network device.
  • the terminal device can The first initial upstream BWP in the BWP communicates with the network device.
  • the terminal device sends Msg1 or Msg3 or other subsequent uplink data on one of the determined at least two initial uplink BWPs.
  • the terminal device sends MsgA or other uplink data on one BWP of the determined at least two initial uplink BWPs.
  • configuration information configured with at least two frequency domain resources is sent to a terminal device through a network device, and the terminal device determines one of the at least two frequency domain resources according to the configuration information, Use this frequency domain resource to communicate with network devices. Since the network device configures multiple frequency domain resources for the terminal device, at least one frequency domain resource among the multiple frequency domain resources can be used by the terminal device, which can prevent the bandwidth of the frequency domain resource currently configured on the network side from exceeding the terminal device. The maximum supported bandwidth makes the terminal device unable to communicate with the network device normally, which improves the data transmission performance of the terminal device and improves the reliability of communication.
  • the above embodiment shows a technical solution in which the network side configures multiple frequency domain resources for the terminal device, which improves the data transmission performance of different types of terminals.
  • the following embodiments show that the network side sends indication information to the terminal device, and the terminal device specifically determines one frequency domain resource among multiple frequency domain resources according to the indication information on the network side, and based on the frequency domain The bandwidth of the resource sends uplink data to the network side.
  • FIG. 6 is an interactive schematic diagram of a method for determining frequency domain resources provided by an embodiment of the present application. As shown in FIG. 6 , the method provided by this embodiment includes the following steps:
  • Step 401 The network device configures at least two frequency domain resources for the terminal device.
  • Step 402 The network device sends configuration information to the terminal device, where the configuration information includes configuration information of at least two frequency domain resources.
  • Step 401 and step 402 in this embodiment are the same as step 301 and step 302 in the foregoing embodiment.
  • Step 401 and step 402 in this embodiment are the same as step 301 and step 302 in the foregoing embodiment.
  • Step 403 The network device sends indication information to the terminal device.
  • the initial uplink BWP is taken as the frequency domain resource
  • the first initial uplink BWP is taken as the first type of frequency domain resource
  • the second initial uplink BWP is taken as the second type of frequency domain resource.
  • the frequency domain resource may also be the downlink BWP. .
  • the indication information is used to instruct the terminal device to use one BWP of the at least two initial uplink BWPs to communicate with the network device.
  • the indication information is used to instruct the terminal device to communicate with the network device on the bandwidth of one BWP in the at least two initial uplink BWPs, or in other words, the indication information is used to instruct the terminal device to use the A BWP has the bandwidth to communicate with network devices.
  • the BWP indicated in the indication information may be a first initial uplink BWP in at least one first initial uplink BWP, and may also be a second initial uplink BWP in at least one second initial uplink BWP.
  • the network device is configured with a second initial upstream BWP and a first initial upstream BWP.
  • the indication information can be used to indicate the terminal equipment.
  • the first initial upstream BWP or the second initial upstream BWP is used to communicate with the network device.
  • the indication information can be used to instruct the terminal equipment to use the second initial uplink BWP Communicate with network devices.
  • the terminal device may directly determine to use the second initial uplink BWP to communicate with the network device according to the configuration information, or may determine to use the second initial uplink BWP to communicate with the network device according to the configuration information and the indication information.
  • the network device is configured with at least two second initial uplink BWPs and one first initial uplink BWP, and the bandwidth of each of the at least two second initial uplink BWPs is less than or equal to Equal to the bandwidth of the first initial uplink BWP, the first initial uplink BWP can be used for the first type terminal device and the second type terminal device to communicate with the network device.
  • the indication information may be used to indicate one second initial uplink BWP among the at least two second initial uplink BWPs.
  • a second initial upstream BWP is determined in the BWP, and the second initial upstream BWP is used to communicate with the network device.
  • the indication information is mainly used to indicate one second initial uplink BWP among the at least two second initial uplink BWPs.
  • the indication information may be used to indicate the first initial uplink BWP.
  • the terminal device may determine the first initial uplink BWP according to the configuration information and the indication information, and use the first initial uplink BWP to communicate with the network device. communication.
  • the network device may send indication information to the terminal device through the random access process, that is, the indication information may be included in the random access response message, and the random access response The message is used by the network device to respond to the random access request of the terminal device.
  • the indication information can be included in the following messages:
  • the indication information may be included in Msg2, which is used by the network device to respond to the random access request of the terminal device.
  • the indication information may be included in the MsgB, which is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in the random access response RAR of the Msg2, and the RAR is used by the network device to respond to the random access request (ie, Msg1) of the terminal device.
  • the indication information is included in the RAR of Msg2, including the following situations:
  • the indication information is located in the PUSCH frequency domain resource allocation indication field of the uplink grant UL grant in the RAR of Msg2.
  • the indication information is located in several high-order bits (most significant bits, MSBs) of the PUSCH frequency domain resource allocation indication field of the UL grant in the RAR.
  • the PUSCH frequency domain resource allocation domain of the UL grant in the RAR includes 14 bits, as shown in Figure 7.
  • BW bandwidth
  • SCS subcarrier space
  • the 11 low-order bits in the PUSCH frequency domain resource allocation field are used to indicate the PUSCH frequency domain resource allocation.
  • the 13 low-order bits in the PUSCH frequency domain resource allocation field are used to indicate the PUSCH frequency domain resource allocation.
  • several high-order bits of the PUSCH frequency domain resource allocation field are empty.
  • the spare high-order bits can be reinterpreted to indicate the uplink BWP used by the terminal for uplink transmission, including the newly configured at least one second initial The upstream BWP or the first initial upstream BWP.
  • the terminal may also determine the PUSCH frequency domain of the UL grant in the RAR according to the initial uplink BWP with the largest number of PRBs in the multiple available initial uplink BWPs. The number of bits occupied by the resource allocation field.
  • the indication information of the network device is described below by taking the network device preconfiguring two initial upstream BWPs dedicated to REDCAP type terminals (that is, preconfiguring two second initial upstream BWPs) as an example.
  • the two preconfigured initial uplink BWPs dedicated to REDCAP type terminals are named NR REDCAP initial UL BWP#1 and NR REDCAP initial UL BWP#2 respectively, where initial UL can also be recorded as UL initial.
  • the high-order 1 bit of the PUSCH frequency domain resource allocation field of the UL grant in the RAR can be used to instruct the terminal device to send Msg3 or other uplink transmission
  • the initial upstream BWP used exemplary, is shown in Table 1.
  • the upper 2 bits of the PUSCH frequency domain resource allocation field of the UL grant in the RAR can also be used to indicate one of the two preconfigured initial uplink BWPs dedicated to REDCAP type terminals, and 2 bits can represent 4 indication states.
  • two states respectively indicate the configured initial uplink BWP dedicated to two REDCAP type terminals
  • one state may indicate the existing initial uplink BWP of the NR, that is, the first initial uplink BWP, which may be It is expressed as UL initial BWP_NR legacy.
  • the network device can instruct the terminal access of the REDCAP type to be prohibited by indicating the existing initial upstream BWP of NR. In other words, it indicates that the terminal of the REDCAP type currently accessing is prohibited from accessing.
  • the upper 2 bits of the PUSCH frequency domain resource allocation field of the UL grant in the RAR can be used to instruct the terminal device to send Msg3 or other uplinks
  • the initial upstream BWP used for transmission Exemplarily, as shown in Table 3, three states of 2 bits may be used to respectively indicate the first initial uplink BWP and the initial uplink BWPs dedicated to two REDCAP type terminals. Further, the remaining one status of 2 bits may be used to indicate whether the REDCAP type terminal is allowed to access the current cell, and when the access is prohibited, the REDCAP type terminal cannot access the current cell.
  • the indication information is located in several low-order bits (least significant bits, LSB) of the RAPID of the MAC subPDU carrying the RAR.
  • the indication information is located in several bits of the reserved bits of the MAC subPDU carrying the RAR.
  • FIG. 8 is a schematic structural diagram of a MAC RAR provided by an embodiment of the present application.
  • the indication information may be located in several high-order bits of the PUSCH frequency domain resource allocation field of the UL grant shown in FIG. 8 , and may also be located in FIG. 8 Several low-order bits of the shown RAPID field may also be located in several bits of the R field (ie, reserved bits) shown in FIG. 8 .
  • the network device may also instruct the terminal device to send Msg3 or the initial uplink BWP used for other uplink transmissions through the combination of bits in any two or three fields.
  • Table 4 shows the bit allocation table of the UL grant in FIG. 8 (which can be used in a non-shared spectrum channel access scenario).
  • the network device instructs the terminal device (which can be specifically referred to as a REDCAP type terminal) to send the initial uplink BWP used by Msg3 or other uplink transmissions through several bits in the random access response RAR of Msg2, so that the terminal device accesses according to the instruction information.
  • the terminal device which can be specifically referred to as a REDCAP type terminal
  • the data transmission performance of the terminal equipment is improved.
  • the following two possible implementations are also included.
  • the indication information is included in the DCI for scheduling the Msg2 (or in other words, for scheduling the PDSCH carrying the RAR). Specifically, the indication information is located in several bits of the reserved reserved bits of the DCI.
  • the network device may instruct the terminal device to send the initial uplink BWP used for Msg3 or other uplink transmissions by scrambling several bits of the reserved bits in the DCI of the CRC through the RA-RNTI.
  • the bit length and indication manner of the initial uplink BWP indicated by the network device are the same as those in the above-mentioned first implementation manner. For details, refer to the above.
  • the terminal equipment that uses the same RO to initiate random access or the terminal equipment that monitors the DCI of the same RA-RNTI scrambled CRC, can use several bits of the reserved bits in the DCI sent by the network equipment, Determine the initial upstream BWP used to send Msg3 or other upstream transmissions.
  • the network device can group the terminal devices according to the preamble ID and/or RAPID, and the network device can use the same number of bits Indicates the initial uplink BWP of the terminal equipment of the same group.
  • the network equipment can group the terminal equipment through SIB1 or high-level configuration, and the grouping method includes:
  • Method 2 Consecutive M preamble ID/RAPID UEs are grouped into a group, for example: ⁇ 0,1,...,M-1 ⁇ , ⁇ M,M+1,M+2,...,2M-1 ⁇ ,... , ⁇ M*NM,M*NM-2,...,M*N-1 ⁇ , where N is the number of packets, and M*N is the number of preambles multiplexed on the same RO.
  • each group uses X bits to indicate the initial uplink BWP used by the group, it needs to occupy N*X bits in the DCI reserved bits in total, as shown in FIG. 9 .
  • the network device can perform packet transmission on RARs corresponding to different preambles of the same RO.
  • N is the number of RAR packets
  • low-order bits can be reused, and can also be used to instruct the terminal device to send the initial uplink BWP used for Msg3 or other uplink transmissions.
  • the network device instructs the terminal device (which can be specifically referred to as a REDCAP type terminal) to send the initial uplink BWP used for Msg3 or other uplink transmissions through several bits in the DCI used for scheduling Msg2, so that the terminal device accesses the current BWP according to the instruction information. cell to improve the data transmission performance of terminal equipment.
  • the terminal device which can be specifically referred to as a REDCAP type terminal
  • the indication information is included in the DCI for scheduling Msg2 and in the RAR.
  • This method mainly considers the situation that the bits in the DCI or RAR are not enough, and the network device can jointly indicate one BWP in at least two initial uplink BWPs through the combination of the bits in the DCI and the RAR. Joint indication can achieve the purpose of saving bit overhead.
  • the indication information may also be included in both the DCI for scheduling Msg2 and the RAR of Msg2.
  • all the bits of any two, three or more indication fields in the indication fields indicated in this embodiment that can be used to indicate the initial uplink BWP can be combined. Indicates the initial upstream BWP of one or a group of terminal devices.
  • bits in the above-mentioned indication field can also be used to indicate that channels such as Msg2, Msg3, and Msg4 perform repeated transmission and the number of times of repeated transmission.
  • the above embodiment shows the indication information in the 4-Step RACH process, and the following describes the indication information in the 2-Step RACH process in detail.
  • the terminal device sends MsgA (including Msg1 and Msg3) through the PRACH and PUSCH channels.
  • MsgA including Msg1 and Msg3
  • Msg3 is carried in the PUSCH; in the data early transmission scenario, the PUSCH can carry the uplink service data.
  • the initial uplink BWP for the terminal device to send the MsgA-PUSCH is predefined or pre-configured.
  • the network device may preconfigure the configuration information of the initial uplink BWP for sending the MsgA-PUSCH through SIB1 or other system information, and the terminal device determines the initial uplink BWP for sending the MsgA-PUSCH according to the configuration information.
  • the above method is also applicable.
  • the network device may also send indication information to the terminal device, and the transmitted indication information includes the following possible implementations:
  • the indication information is included in the random access response RAR of the MsgB, and the RAR is used by the network device to respond to the random access request (ie, MsgA) of the terminal device.
  • the indication information is included in the RAR of MsgB, including the following situations:
  • the indication information is located in the PUSCH frequency domain resource allocation indication field of the uplink grant UL grant in the RAR of the MsgB.
  • the indication information is located in several high-order bits of the PUSCH frequency domain resource allocation indication field of the UL grant in the RAR of the MsgB.
  • the indication information is located in several high-order bits of the PUSCH frequency domain resource allocation indication field of the UL grant in the successRAR/fallbackRAR of MsgB.
  • the network device receives the MsgA from the terminal device, and when the network device detects both the preamble and the MsgA-PUSCH, the random access is successful, and the network device sends a conflict resolution identifier in the MsgB.
  • the network device indicates the initial uplink BWP used by the terminal device for subsequent uplink transmission through the successRAR of MsgB, including MsgB-PUSCH feedback, subsequent 4-Step RA (random access) process or 2-Step RA process.
  • the network device receives the MsgA from the terminal device.
  • the 2-Step RACH can fall back to the 4-Step RACH, and the network device passes through the MsgB. fallbackRAR schedules PUSCH to continue transmission.
  • an important reason for the failure of MsgA-PUSCH detection is poor channel quality. Enables frequency hopping over a wider frequency range to increase frequency selective gain.
  • the indication information is located in several low-order bits of the RAPID of the MAC subPDU carrying the RAR.
  • the indication information is located in several low-order bits of the RAPID of the MAC subPDU carrying the successRAR/fallbackRAR.
  • the indication information is located in several bits of the reserved bits of the MAC subPDU carrying the RAR.
  • the indication information is located in several bits of the reserved bits of the MAC subPDU carrying the successRAR/fallbackRAR.
  • the indication information is included in the DCI for scheduling the MsgB. Specifically, the indication information is located in the reserved reserved bits of the DCI.
  • the network device may use the RA/MsgB-RNTI to scramble several bits of the reserved bits in the DCI of the CRC to instruct the terminal device to send the initial uplink BWP used for Msg3 or other uplink transmissions.
  • the bit length and indication manner of the network device indicating the initial uplink BWP are the same as the first implementation manner of the indication information in the above-mentioned 4-Step RACH embodiment. For details, refer to the above.
  • the network device receives the MsgA from the terminal device.
  • the 2-Step RACH can fall back to the 4-Step RACH, and the network device passes through the MsgB. fallbackRAR schedules PUSCH to continue transmission.
  • the network device may also indicate the initial uplink BWP used by the terminal device for subsequent uplink transmission through the DCI used for scheduling the MsgB.
  • the indication information is included in the DCI for scheduling the MsgB and the RAR. This method mainly considers the situation that the bits in the DCI or the RAR are not enough, and the network device can jointly indicate one BWP of the at least two initial uplink BWPs through the combination of the bits in the DCI and the RAR.
  • all the bits of any two, three or more indication fields in the indication fields indicated in this embodiment that can be used to indicate the initial uplink BWP can be combined. Indicates the initial upstream BWP of one or a group of terminal devices.
  • Step 404 The terminal device determines one frequency domain resource of the at least two frequency domain resources according to the configuration information and the indication information.
  • Step 405 the terminal device communicates with the network device by using one frequency domain resource among the at least two frequency domain resources.
  • the initial uplink BWP is used as the frequency domain resource, and it should be understood that the frequency domain resource may also be the downlink BWP.
  • the terminal device determines one BWP of at least two initial uplink BWPs according to the configuration information and the indication information, and sends Msg3 or other subsequent uplink data on the bandwidth of the determined BWP.
  • the terminal device determines one BWP among at least two initial uplink BWPs according to the configuration information and the indication information, and sends other subsequent uplink data on the bandwidth of the determined BWP.
  • the network device pre-configures at least two frequency domain resources for the terminal device through system information or signaling, which can be used for scheduling Msg2/MsgB through the DCI and/or the random access process.
  • the random access response message indicates a frequency domain resource used by the terminal device for subsequent transmission of uplink data.
  • the terminal device determines one frequency domain resource among the at least two frequency domain resources according to the preconfiguration and instructions on the network side, and uses the frequency domain resource to be used with the same frequency domain resource. network devices to communicate.
  • the above solution solves the problem that the frequency domain resources currently configured on the network side may exceed the maximum bandwidth supported by the terminal device, resulting in the terminal device being unable to communicate with the network device, thereby improving the reliability of the communication process.
  • the uplink frequency selective gain on the network side is increased, which is also beneficial for the network side to flexibly perform load balancing among multiple frequency domain resources, and improve the data transmission performance of the terminal device.
  • FIG. 10 is a schematic structural diagram of a network device according to an embodiment of the application.
  • the network device 500 is, for example, the network device described in the embodiment shown in FIG. 4 or the embodiment shown in FIG. 6 .
  • the network device 500 includes a processing module 501 .
  • a transceiver module 502 may also be included.
  • the network device 500 may be a network device, or may be a chip applied in the network device or other combined devices, components, etc. having the functions of the above-mentioned network device.
  • the transceiver module 502 may be a transceiver
  • the transceiver may include an antenna and a radio frequency circuit, etc.
  • the processing module 501 may be a processor (or a processing circuit), such as a baseband processor.
  • CPUs central processing units
  • the transceiver module 502 may be a radio frequency unit, and the processing module 501 may be a processor (or a processing circuit), such as a baseband processor.
  • the transceiver module 502 may be an input/output interface of a chip (eg, a baseband chip), and the processing module 501 may be a processor (or a processing circuit) of the chip system, which may include one or more central processing units. unit.
  • processing module 501 in this embodiment of the present application may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit), and the transceiver module 502 may be implemented by a transceiver or a transceiver-related circuit component.
  • the transceiver module 502 is configured to send configuration information to the terminal device, where the configuration information includes configuration information of at least two frequency domain resources, and the at least two frequency domain resources include at least one first type frequency domain resource and at least one second type frequency domain resource; the first type frequency domain resource is used for the first type terminal device and/or the second type terminal device to communicate with the network device; the second type frequency domain resource The domain resource is used for the second type terminal device to communicate with the network device; the processing module 501 is configured to communicate with the terminal device using one frequency domain resource of the at least two frequency domain resources.
  • the first type of frequency domain resource includes a first initial uplink bandwidth part BWP
  • the second type of frequency domain resource includes a second initial uplink BWP
  • the first type frequency domain resource is used for the first type terminal device and the second type terminal device to communicate with the network device; the transceiver module 502 is further configured to send the terminal device to the Sending indication information, where the indication information is used to indicate one frequency domain resource in the at least two frequency domain resources.
  • the first type frequency domain resource is only used for the first type terminal device to communicate with the network device, and the transceiver module 502 is further configured to send indication information to the terminal device, the indication The information is used to indicate a second type frequency domain resource in the at least two frequency domain resources.
  • the indication information is included in a random access response message, and the random access response message is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in Msg2, where the Msg2 is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in the MsgB, where the MsgB is used by the network device to respond to the random access request of the terminal device.
  • the indication information is located in the physical uplink shared channel PUSCH frequency domain resource allocation indication field in the uplink grant in the random access response message.
  • the indication information is located in at least one high-order bit of a physical uplink shared channel PUSCH frequency domain resource allocation indication field in an uplink grant in the random access response message.
  • the indication information is included in downlink control information DCI, where the DCI is used to schedule a random access response message, and the random access response message is used by the network device to respond to the random access of the terminal device ask.
  • the indication information is included in the reserved bits of the DCI.
  • the indication information is included in the random access response message and the DCI that schedules the random access response message, and bits in the random access response message and the DCI together indicate to the terminal device communicating with the network device using one of the at least two frequency domain resources.
  • the bandwidth of the second type of frequency domain resources is less than or equal to the maximum bandwidth supported by the terminal device.
  • the transceiver module 502 is specifically configured to send the configuration information to the terminal device through system information or high-layer signaling or physical layer signaling.
  • the network device provided in this embodiment can be used to implement the technical solutions of the network device in any of the above method embodiments, and the implementation principles and technical effects thereof are similar, and details are not repeated here.
  • FIG. 11 is a schematic structural diagram of a terminal device according to an embodiment of the application.
  • the terminal device 600 is, for example, the terminal device described in the embodiment shown in FIG. 4 or the embodiment shown in FIG. 6 .
  • the terminal device 600 includes a processing module 601 .
  • a transceiver module 602 may also be included.
  • the terminal device 600 may be a terminal device, or may be a chip applied in the terminal device or other combined devices, components, etc. having the functions of the above-mentioned terminal device.
  • the transceiver module 602 may be a transceiver, the transceiver may include an antenna and a radio frequency circuit, etc.
  • the processing module 601 may be a processor (or a processing circuit), such as a baseband processor.
  • CPUs central processing units
  • the transceiver module 602 may be a radio frequency unit, and the processing module 601 may be a processor (or a processing circuit), such as a baseband processor.
  • the transceiver module 602 may be an input/output interface of a chip (eg, a baseband chip), and the processing module 601 may be a processor (or a processing circuit) of the chip system, which may include one or more central processing units. unit.
  • processing module 601 in this embodiment of the present application may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit), and the transceiver module 602 may be implemented by a transceiver or a transceiver-related circuit component.
  • the transceiver module 602 is configured to receive configuration information from a network device, where the configuration information includes configuration information of at least two frequency domain resources, and the at least two frequency domain resources include at least one first One type of frequency domain resources and at least one second type of frequency domain resources; the first type of frequency domain resources are used for the first type of terminal equipment and/or the second type of terminal equipment to communicate with the network equipment; the second type of frequency domain resources Domain resources are used for the second type terminal device to communicate with the network device;
  • the processing module 601 is configured to determine one frequency domain resource among the at least two frequency domain resources according to the configuration information, and use one frequency domain resource among the at least two frequency domain resources to communicate with the network device.
  • the first type of frequency domain resource includes a first initial uplink bandwidth part BWP
  • the second type of frequency domain resource includes a second initial uplink BWP
  • the first type of frequency domain resource is used for the first type of terminal device and the second type of terminal device to communicate with the network device; the transceiver module 602 is further configured to receive data from the network device. indication information, where the indication information is used to indicate one frequency domain resource in the at least two frequency domain resources; the processing module 601 is specifically configured to determine the at least two frequency domain resources according to the configuration information and the indication information One of the frequency domain resources in the domain resources.
  • the first type frequency domain resource is only used for the first type terminal device to communicate with the network device; the transceiver module 602 is further configured to receive indication information from the network device, the indication information is used to indicate one frequency domain resource in the at least two second type frequency domain resources; the processing module 601 is specifically configured to determine the at least two second type frequency domain resources according to the configuration information and the indication information A frequency domain resource in the resource.
  • the indication information is included in a random access response message, and the random access response message is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in Msg2, where the Msg2 is used by the network device to respond to the random access request of the terminal device.
  • the indication information is included in the MsgB, where the MsgB is used by the network device to respond to the random access request of the terminal device.
  • the indication information is located in the physical uplink shared channel PUSCH frequency domain resource allocation indication field in the uplink grant in the random access response message.
  • the indication information is located in at least one high-order bit of a physical uplink shared channel PUSCH frequency domain resource allocation indication field in an uplink grant in the random access response message.
  • the indication information is included in downlink control information DCI, where the DCI is used to schedule a random access response message, and the random access response message is used by the network device to respond to the random access of the terminal device ask.
  • the indication information is included in the reserved bits of the DCI.
  • the indication information is included in the random access response message and the DCI that schedules the random access response message, and bits in the random access response message and the DCI together indicate to the terminal device communicating with the network device using one of the at least two frequency domain resources.
  • the bandwidth of the second type of frequency domain resources is less than or equal to the maximum bandwidth supported by the terminal device.
  • the transceiver module 602 is specifically configured to receive configuration information from network devices from system information or high-layer signaling or physical layer signaling.
  • the terminal device provided in this embodiment can be used to execute the technical solutions of the terminal device in any of the above method embodiments, and the implementation principles and technical effects thereof are similar, and are not repeated here.
  • FIG. 12 is a schematic diagram of a hardware structure of a network device according to an embodiment of the present application. As shown in FIG. 12, the network device 700 includes:
  • the memory 702 is used to store computer programs; the processor 701 is used to execute the computer programs stored in the memory 702, so as to implement the method executed by the network device in any of the above method embodiments.
  • the communication interface 703 is used for data communication or signal communication with other devices.
  • the memory 702 may be independent or integrated with the processor 701 .
  • the network device 700 may further include: a bus 704 for connecting the memory 702 and the processor 701 .
  • the processing module 501 in FIG. 10 may be integrated in the processor 701 to be implemented, and the transceiver module 502 may be integrated in the communication interface 703 to be implemented.
  • the processor 701 may be used to implement the signal processing operation of the network device in the above method embodiment, and the communication interface 703 may be used to implement the signal transceiving operation of the network device in the above method embodiment.
  • the network device provided in this embodiment can be used to execute the method performed by the network device in any of the foregoing method embodiments, and the implementation principle and technical effect thereof are similar, and details are not described herein again.
  • FIG. 13 is a schematic diagram of a hardware structure of a terminal device according to an embodiment of the present application. As shown in FIG. 13, the terminal device 800 includes:
  • the memory 802 is used to store computer programs; the processor 801 is used to execute the computer programs stored in the memory 802 to implement the method executed by the terminal device in any of the above method embodiments.
  • the communication interface 803 is used for data communication or signal communication with other devices.
  • the memory 802 may be independent or integrated with the processor 801 .
  • the terminal device 800 may further include: a bus 804 for connecting the memory 802 and the processor 801.
  • the processing module 602 in FIG. 11 may be integrated in the processor 801 and implemented, and the transceiver module 601 may be integrated in the communication interface 803 and implemented.
  • the processor 801 may be used to implement the signal processing operation of the terminal device in the above method embodiment, and the communication interface 803 may be used to implement the signal transceiving operation of the terminal device in the above method embodiment.
  • the terminal device in this embodiment can be used to execute the method executed by the terminal device in any of the above method embodiments, and its implementation principle and technical effect are similar, and details are not repeated here.
  • the present application further provides a readable storage medium, where an execution instruction is stored in the readable storage medium, and when at least one processor of a network device executes the execution instruction, the network device executes the technical solution of the network device in any of the above method embodiments .
  • the present application also provides a readable storage medium, where an execution instruction is stored in the readable storage medium, and when at least one processor of a terminal device executes the execution instruction, the terminal device executes the technical solutions of the terminal device in any of the above method embodiments .
  • the present application also provides a computer program product comprising executable instructions stored in a readable storage medium.
  • At least one processor of the network device may read the execution instruction from the readable storage medium, and the execution of the execution instruction by the at least one processor causes the network device to implement the technical solutions of the network device in any of the foregoing method embodiments.
  • the present application also provides a computer program product comprising executable instructions stored in a readable storage medium.
  • At least one processor of the terminal device may read the execution instruction from the readable storage medium, and the execution of the execution instruction by the at least one processor causes the terminal device to implement the technical solutions of the terminal device in any of the foregoing method embodiments.
  • the present application further provides a chip, including: a processor and an interface, where the processor can execute the technical solution of the network device in any of the above method embodiments.
  • the chip further includes a memory, a computer program is stored in the memory, and the processor is configured to execute the computer program stored in the memory to implement the technical solution of the network device in any of the above method embodiments.
  • An embodiment of the present application further provides a chip, including: a processor and an interface, where the processor can execute the technical solution of the terminal device in any of the foregoing method embodiments.
  • the chip further includes a memory, a computer program is stored in the memory, and the processor is configured to execute the computer program stored in the memory to implement the technical solution of the terminal device in any of the above method embodiments.
  • An embodiment of the present application further provides a communication system, including: at least one network device and a terminal device, wherein the network device can be used to execute the technical solutions of the network device in any of the above method embodiments, and the terminal device can be used to execute any of the above methods The technical solution of the terminal device in the embodiment.
  • each module of the network equipment or terminal equipment is only a division of logical functions, and may be fully or partially integrated into a physical entity in actual implementation, or may be physically separated.
  • these modules can all be implemented in the form of software calling through processing elements; they can also all be implemented in hardware; some modules can also be implemented in the form of calling software through processing elements, and some modules can be implemented in hardware.
  • the processing module may be a separately established processing element, or may be integrated into a certain chip of the above-mentioned device to be implemented, in addition, it may also be stored in the memory of the above-mentioned device in the form of program code, and a certain processing element of the above-mentioned device Call and execute the function of the above determined module.
  • the implementation of other modules is similar.
  • all or part of these modules can be integrated together, and can also be implemented independently.
  • the processing element described herein may be an integrated circuit with signal processing capabilities.
  • each step of the above-mentioned method or each of the above-mentioned modules can be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.
  • the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more application specific integrated circuits (ASIC), or one or more microprocessors (digital) signal processor, DSP), or, one or more field programmable gate arrays (field programmable gate array, FPGA), etc.
  • ASIC application specific integrated circuits
  • DSP digital signal processor
  • FPGA field programmable gate array
  • the processing element may be a general-purpose processor, such as a central processing unit (central processing unit, CPU) or other processors that can call program codes.
  • these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种频域资源的确定方法、设备及存储介质，该方法包括：网络设备为终端设备配置至少两个频域资源，至少两个频域资源包括至少一个第一类型频域资源及至少一个第二类型频域资源，第二类型频域资源可用于REDCAP类型终端与网络设备进行通信。网络设备向终端设备发送配置有至少两个频域资源的配置信息，终端设备根据配置信息确定至少两个频域资源中的一个频域资源，使用该频域资源与网络设备进行通信。由于网络设备配置多个频域资源，多个频域资源中至少有一个频域资源可供终端设备使用，这样可以避免由于当前配置的频域资源的带宽超出终端设备的最大带宽，使得终端设备无法与网络设备进行正常通信的问题，提高通信系统可靠性。

Description

频域资源的确定方法、设备及存储介质
本申请要求于2020年8月7日提交中国专利局、申请号为202010791729.0、申请名称为“频域资源的确定方法、设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种频域资源的确定方法、设备及存储介质。
背景技术
随着通信技术的发展，新空口(new radio，NR)系统除了支持增强移动带宽(enhanced mobile broadband，eMBB)业务之外，还可以支持多种其他业务类型，例如物联网场景中各类物联网设备的数据传输业务等，支持这些业务的终端具有带宽减小、处理速度降低、天线数量减小等特点，这类终端被称为能力缩减(reduced capability，REDCAP)类型的终端。REDCAP类型的终端包括5MHz、10MHz、20MHz几种典型的带宽。
NR系统中定义了带宽部分(bandwidth part，BWP)，BWP是终端接收和发送数据的频域资源，包括下行BWP和上行BWP。网络侧为终端配置一个初始下行BWP(initial downlink BWP)和一个初始上行BWP(initial uplink BWP)，初始下行BWP和初始上行BWP均为小区公共专属的BWP。
现有技术中，FR1即载波频率小于6GHz，初始BWP的带宽最大可以达到100MHz。然而，REDCAP类型终端的带宽相对较小，导致这一类型终端可能无法正常地进行随机接入过程，从而使得通信可靠性降低。
发明内容
本申请提供一种频域资源的确定方法、设备及存储介质，有助于提升通信过程中的可靠性。
第一方面，本申请实施例提供一种频域资源的确定方法，包括：网络设备向终端设备发送配置信息，所述配置信息包括至少两个频域资源的配置信息，所述至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源；所述第一类型频域资源用于第一类型终端设备和/或第二类型终端设备与所述网络设备通信；所述第二类型频域资源用于所述第二类型终端设备与所述网络设备通信；所述网络设备使用所述至少两个频域资源中的一个频域资源与所述终端设备通信。
上述方案中的第一类型终端设备可以是普通终端，第二类型终端设备可以是REDCAP类型终端或者其他类型终端。上述方案中的终端设备可以是普通终端，也可以是REDCAP类型终端。
上述方案中的网络设备为终端设备配置的频域资源包括N个连续/非连续的物理资源块/资源块(PRB/RB)，其中，N为正整数。示例性的，频域资源包括N个连续的PRB/RB，频域资源可以是初始上行BWP。
上述方案中，网络设备为终端设备配置至少两个频域资源，并向终端设备发送配置有至少两个频域资源的配置信息，使得终端设备基于该配置信息确定至少两个频域资源的其中一个频域资源，使用该频域资源与网络设备进行通信，从而提高了终端设备的数据传输性能。由于网络设备配置了多个频域资源，这多个频域资源中至少有一个频域资源可供终端设备使用，这样可以避免由于当前网络配置的频域资源的带宽超出终端设备支持的最大带宽，使得终端设备无法正常通信的问题，提升了通信可靠性。
可选的，第一类型频域资源包括第一初始上行带宽部分BWP，第二类型频域资源包括第二初始上行BWP。
在第一方面的一种可能的设计中，所述第一类型频域资源用于所述第一类型终端设备和所述第二类型终端设备与所述网络设备通信；所述方法还包括：所述网络设备向所述终端设备发送指示信息，所述指示信息用于指示所述至少两个频域资源中的一个频域资源，所述至少两个频域资源中的一个频域资源用于终端设备与网络设备通信。
上述方案中，网络设备为终端设备配置的第一类型频域资源既可以用于第一类型终端设备与网络设备通信，又可以用于第二类型终端设备与网络设备通信。即网络设备配置的第一类型频域资源可共享给两种类型的终端设备使用，例如第一类型频域资源可供普通终端和REDCAP类型终端使用。
在第一方面的一种可能的设计中，所述第一类型频域资源仅用于所述第一类型终端设备与所述网络设备通信，所述方法还包括：所述网络设备向所述终端设备发送指示信息，所述指示信息用于指示所述至少两个第二类型频域资源中的一个频域资源，所述至少两个第二类型频域资源中的一个频域资源用于终端设备与网络设备通信。
上述方案中，网络设备为终端设备配置的第一类型频域资源可用于第一类型终端设备与网络设备通信，但不用于第二类型终端设备与网络设备通信。即网络设备配置的第一类型频域资源仅供第一类型终端设备使用，第二类型终端设备仅能使用第二类型频域资源而不能使用第一类型频域资源，例如第一类型频域资源可供普通终端使用，REDCAP类型终端无法使用第一类型频域资源，REDCAP类型终端使用第二类型频域资源与网络设备通信。
上述两种可能的设计中，网络设备除了为终端设备配置至少两个频域资源，并向终端设备发送包括至少两个频域资源配置信息的配置信息之外，还向终端设备发送指示信息，使得终端设备基于配置信息以及指示信息确定至少两个频域资源的其中一个频域资源，并使用该频域资源与网络设备进行通信，从而提高了终端设备的数据传输性能。由于网络设备配置了多个频域资源，这多个频域资源中至少有一个频域资源可供终端设备使用，这样可以避免由于当前网络配置的频域资源的带宽超出终端设备支持的最大带宽，使得终端设备无法正常通信的问题。网络设备通过向终端设备发送指示信息，该指示信息除了可以指示终端设备使用至少两个频域资源的其中一个频域资源之外，还可以指示终端设备禁止接入或者指示已接入终端设备禁止接入，有利于网络侧在多个频域资源之间进行灵活调度，从而实现各个频域资源的接入负载较为均衡的效果，有助于提升用户传输性能。
可选的，所述指示信息包括在随机接入响应消息中，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。该方案中，网络设备通过随机接入 过程中的随机接入响应消息向终端设备发送指示信息，用于指示终端设备使用至少两个频域资源的其中一个频域资源与网络设备进行通信，或者，指示终端设备禁止接入，或者，指示已接入终端设备禁止接入。其中，随机接入过程包括两种随机接入过程，分别为4步随机接入过程(4-Step RACH过程)以及2步随机接入过程(2-Step RACH过程)。
可选的，所述指示信息包括在Msg2中，所述Msg2用于所述网络设备响应所述终端设备的随机接入请求。该方案中的Msg2属于4-Step RACH过程的随机接入响应消息，网络设备通过Msg2向终端设备发送指示信息，用于指示终端设备使用至少两个频域资源的其中一个频域资源与网络设备进行通信，或者，指示终端设备禁止接入，或者，指示已接入终端设备禁止接入。
可选的，所述指示信息包括在MsgB中，所述MsgB用于所述网络设备响应所述终端设备的随机接入请求。该方案中的MsgB属于2-Step RACH过程的随机接入响应消息，网络设备通过MsgB向终端设备发送指示信息，用于指示终端设备使用至少两个频域资源的其中一个频域资源与网络设备进行通信，或者，指示终端设备禁止接入，或者，指示已接入终端设备禁止接入。
可选的，所述指示信息包括位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域。在一种可能的实施方式中，指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域的至少一个高位比特中。在一种可能的实施方式中，指示信息位于携带RAR的MAC subPDU的随机接入前导码标识RAPID的若干低位比特(least significant bit，LSB)中。在一种可能的实施方式中，指示信息位于携带RAR的MAC subPDU的预留比特的若干比特中。上述方案中，网络设备通过随机接入响应消息中的若干比特向终端设备发送指示信息，用于指示终端设备使用至少两个频域资源的其中一个频域资源与网络设备进行通信，或者，指示终端设备禁止接入，或者，指示已接入终端设备禁止接入。
可选的，所述指示信息包括在下行控制信息DCI中，所述DCI用于调度随机接入响应消息。在一种可能的实施方式中，指示信息可以包括在用于调度Msg2的DCI中，还可以包括在用于调度MsgB的DCI中。在一种可能的实施方式中，指示信息位于DCI的预留reserved比特的至少一个比特中。上述方案中，网络设备通过DCI向终端设备发送指示信息，用于指示终端设备使用至少两个频域资源的其中一个频域资源与网络设备进行通信，或者，指示终端设备禁止接入，或者，指示已接入终端设备禁止接入。
可选的，所述指示信息包括在所述随机接入响应消息和调度所述随机接入响应消息的DCI中，所述随机接入响应消息和所述DCI中的比特共同指示所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。该方案主要考虑到DCI或随机接入响应消息中的比特不够用的情况，网络设备可通过DCI和随机接入响应消息中比特的组合，联合指示至少两个频域资源中的一个频域资源，联合指示可达到节能比特开销的目的。
在第一方面的一种可能的设计中，所述网络设备向终端设备发送配置信息，包括：所述网络设备通过系统信息或高层信令或者物理层信令，向所述终端设备发送所述配 置信息。其中，系统信息包括SIB1以及其他系统信息。高层信令包括无线资源控制层(radio resource control，RRC)信令、媒体接入控制层控制单元(media access control control element，MAC CE)控制单元，物理层信令包括下行控制信息(downlink control information，DCI)等信令。
可选的，所述第二类型频域资源的带宽小于或等于所述终端设备支持的最大带宽。在一些实施例中，第二类型频域资源的带宽小于或等于REDCAP类型终端支持的最大带宽，REDCAP类型终端对应的典型带宽包括5MHz、10MHz、20MHz。
可选的，第二类型频域资源的带宽小于或等于第一类型频域资源的带宽。
第二方面，本申请实施例提供一种频域资源的确定方法，该方法包括：终端设备接收来自网络设备的配置信息，所述配置信息包括至少两个频域资源的配置信息，所述至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源；所述第一类型频域资源用于第一类型终端设备和/第二类型终端设备与所述网络设备通信；所述第二类型频域资源用于所述第二类型终端设备与所述网络设备通信；所述终端设备根据所述配置信息确定所述至少两个频域资源中的一个频域资源；所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
上述方案中，网络设备向终端设备发送配置信息，其中配置信息包括至少两个频域资源的配置信息，终端设备根据接收到的配置信息确定至少两个频域资源的其中一个频域资源，并使用该频域资源与网络设备进行通信，从而提高了终端设备的数据传输性能。由于网络设备配置了多个频域资源，这多个频域资源中至少有一个频域资源可供终端设备使用，这样可以避免由于当前网络配置的频域资源的带宽超出终端设备支持的最大带宽，使得终端设备无法正常通信的问题。
可选的，第一类型频域资源包括第一初始上行带宽部分BWP，第二类型频域资源包括第二初始上行BWP。
在第二方面的一种可能的设计中，所述第一类型频域资源用于所述第一类型终端设备和所述第二类型终端设备与所述网络设备通信；所述方法还包括：所述终端设备接收来自网络设备的指示信息，所述指示信息用于指示所述至少两个频域资源中的一个频域资源；所述终端设备根据所述配置信息以及所述指示信息，确定所述至少两个频域资源中的一个频域资源。
在第二方面的一种可能的设计中，所述第一类型频域资源仅用于所述第一类型终端设备与所述网络设备通信，所述方法还包括：所述终端设备接收来自网络设备的指示信息，所述指示信息用于指示所述至少两个第二类型频域资源中的一个频域资源；所述终端设备根据所述配置信息以及所述指示信息，确定所述至少两个第二类型频域资源中的一个频域资源。
上述两种可能的设计中，终端设备除了接收来自网络设备的配置信息之外，还接收来自网络设备的指示信息，终端设备基于配置信息以及指示信息确定至少两个频域资源的其中一个频域资源，使用该频域资源与网络设备进行通信，从而提高了终端设备的数据传输性能。由于网络设备配置了多个频域资源，这多个频域资源中至少有一个频域资源可供终端设备使用，这样可以避免由于当前网络配置的频域资源的带宽超出终端设备支持的最大带宽，使得终端设备无法正常通信的问题。
可选的，所述指示信息包括在随机接入响应消息中，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在Msg2中，所述Msg2用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在MsgB中，所述MsgB用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域。在一种可能的实施方式中，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域的至少一个高位比特中。在一种可能的实施方式中，指示信息位于携带RAR的MAC subPDU的随机接入前导码标识RAPID的若干低位比特(least significant bit，LSB)中。在一种可能的实施方式中，指示信息位于携带RAR的MAC subPDU的预留比特的若干比特中。
可选的，所述指示信息包括在下行控制信息DCI中，所述DCI用于调度随机接入响应消息，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。在一种可能的实施方式中，所述指示信息包括在所述DCI的预留比特中。
可选的，所述指示信息包括在所述随机接入响应消息和调度所述随机接入响应消息的DCI中，所述随机接入响应消息和所述DCI中的比特共同指示所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
可选的，所述第二类型频域资源的带宽小于或等于所述终端设备支持的最大带宽。在一些实施例中，第二类型频域资源的带宽小于或等于REDCAP类型终端支持的最大带宽。
可选的，第二类型频域资源的带宽小于或等于第一类型频域资源的带宽。
上述指示信息的几种可选方案同第一方面，具体可参见第一方面的介绍，此处不再赘述。
在第二方面的一种可能的设计中，所述终端设备接收来自网络设备的配置信息，包括：所述终端设备从系统信息或高层信令或物理层信令中，接收来自网络设备的配置信息。
第三方面，本申请实施例提供一种网络设备，包括：收发模块，用于向终端设备发送配置信息，所述配置信息包括至少两个频域资源的配置信息，所述至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源；所述第一类型频域资源用于第一类型终端设备和/或第二类型终端设备与所述网络设备通信；所述第二类型频域资源用于所述第二类型终端设备与所述网络设备通信；处理模块，用于使用所述至少两个频域资源中的一个频域资源与所述终端设备通信。
可选的，第一类型频域资源包括第一初始上行带宽部分BWP，第二类型频域资源包括第二初始上行BWP。
可选的，所述第一类型频域资源用于所述第一类型终端设备和所述第二类型终端设备与所述网络设备通信；所述收发模块，还用于向所述终端设备发送指示信息，所述指示信息用于指示所述至少两个频域资源中的一个频域资源。
可选的，所述第一类型频域资源仅用于所述第一类型终端设备与所述网络设备通信，所述收发模块，还用于向所述终端设备发送指示信息，所述指示信息用于指示所述至少两个频域资源中的一个第二类型频域资源。
可选的，所述指示信息包括在随机接入响应消息中，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在Msg2中，所述Msg2用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在MsgB中，所述MsgB用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域。在一种可能的实施方式中，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域的至少一个高位比特中。
可选的，所述指示信息包括在下行控制信息DCI中，所述DCI用于调度随机接入响应消息，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。在一种可能的实施方式中，所述指示信息包括在所述DCI的预留比特中。
可选的，所述指示信息包括在所述随机接入响应消息和调度所述随机接入响应消息的DCI中，所述随机接入响应消息和所述DCI中的比特共同指示所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
可选的，所述第二类型频域资源的带宽小于或等于所述终端设备支持的最大带宽。
可选的，所述收发模块，具体用于通过系统信息或高层信令或者物理层信令，向所述终端设备发送所述配置信息。
第四方面，本申请实施例提供一种终端设备，包括：收发模块，用于接收来自网络设备的配置信息，所述配置信息包括至少两个频域资源的配置信息，所述至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源；所述第一类型频域资源用于第一类型终端设备和/第二类型终端设备与所述网络设备通信；所述第二类型频域资源用于所述第二类型终端设备与所述网络设备通信；处理模块，用于根据所述配置信息确定所述至少两个频域资源中的一个频域资源，使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
可选的，所述第一类型频域资源包括第一初始上行带宽部分BWP，所述第二类型频域资源包括第二初始上行BWP。
可选的，所述第一类型频域资源用于所述第一类型终端设备和所述第二类型终端设备与所述网络设备通信；所述收发模块，还用于接收来自网络设备的指示信息，所述指示信息用于指示所述至少两个频域资源中的一个频域资源；处理模块，具体用于根据所述配置信息以及所述指示信息，确定所述至少两个频域资源中的一个频域资源。
可选的，所述第一类型频域资源仅用于所述第一类型终端设备与所述网络设备通信；所述收发模块，还用于接收来自网络设备的指示信息，所述指示信息用于指示所述至少两个第二类型频域资源中的一个频域资源；处理模块，具体用于根据所述配置信息以及所述指示信息，确定所述至少两个第二类型频域资源中的一个频域资源。
可选的，所述指示信息包括在随机接入响应消息中，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在Msg2中，所述Msg2用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在MsgB中，所述MsgB用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域。在一种可能的实施方式中，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域的至少一个高位比特中。
可选的，所述指示信息包括在下行控制信息DCI中，所述DCI用于调度随机接入响应消息，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。在一种可能的实施方式中，所述指示信息包括在所述DCI的预留比特中。
可选的，所述指示信息包括在所述随机接入响应消息和调度所述随机接入响应消息的DCI中，所述随机接入响应消息和所述DCI中的比特共同指示所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
可选的，所述第二类型频域资源的带宽小于或等于所述终端设备支持的最大带宽。
可选的，所述收发模块，具体用于从系统信息或高层信令或物理层信令中，接收来自网络设备的配置信息。
第五方面，本申请实施例提供一种网络设备，包括：存储器和处理器，所述存储器用于存储程序指令，所述处理器用于调用所述存储器中存储的程序指令以实现第一方面中任一项所述的方法。
第六方面，本申请实施例提供一种终端设备，包括：存储器和处理器，所述存储器用于存储程序指令，所述处理器用于调用所述存储器中存储的程序指令以实现第二方面中任一项所述的方法。
第七方面，本申请实施例提供一种可读存储介质，包括：所述可读存储介质中存储有执行指令，当网络设备的至少一个处理器执行该执行指令时，所述网络设备执行第一方面中任一项所述的方法。
第八方面，本申请实施例提供一种可读存储介质，包括：所述可读存储介质中存储有执行指令，当终端设备的至少一个处理器执行该执行指令时，所述终端设备执行第二方面中任一项所述的方法。
第九方面，本申请实施例提供一种芯片，包括：处理器和接口，用于从存储器中调用并运行所述存储器中存储的计算机程序，执行第一方面中任一项所述的方法。
第十方面，本申请实施例提供一种芯片，包括：处理器和接口，用于从存储器中调用并运行所述存储器中存储的计算机程序，执行第二方面中任一项所述的方法。
第十一方面，本申请实施例提供一种通信系统，包括：至少一个第五方面所述的网络设备以及第六方面所述的终端设备，其中，网络设备可用于执行第一方面中任一项所述的方法，终端设备可用于执行第二方面中任一项所述的方法。
本申请实施例提供一种频域资源的确定方法、设备及存储介质，该方法包括：网 络设备为终端设备预配置至少两个频域资源，其中，至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源，第一类型频域资源用于第一类型终端设备和/或第二类型终端设备与所述网络设备通信，第二类型频域资源用于第二类型终端设备与网络设备进行通信。网络设备向终端设备发送配置有至少两个频域资源的配置信息，终端设备根据该配置信息确定至少两个频域资源的其中一个频域资源，使用该频域资源与网络设备进行通信。由于网络设备为终端设备配置了多个频域资源，这多个频域资源中至少有一个频域资源可供终端设备使用，这样可以避免由于现有技术中配置的频域资源的带宽超出终端设备支持的最大带宽，使得终端设备无法与网络设备进行正常通信的问题，提高了通信系统的数据传输的可靠性。
附图说明
图1为本申请实施例提供的一种系统架构图；
图2为本申请实施例提供的一种随机接入过程的示意图；
图3为本申请实施例提供的一种随机接入过程的示意图；
图4为本申请实施例提供的一种频域资源的确定方法的交互示意图；
图5为本申请实施例提供的网络设备为终端设备配置的频域资源的示意图；
图6为本申请实施例提供的一种频域资源的确定方法的交互示意图；
图7为本申请实施提供的随机接入响应RAR中PUSCH频域资源分配域的示意图；
图8为本申请实施例提供的MAC RAR的结构示意图；
图9为本申请实施例提供的下行控制信息DCI预留比特指示初始上行BWP的示意图；
图10为本申请实施例提供的一种网络设备的结构示意图；
图11为本申请实施例提供的一种终端设备的结构示意图；
图12为本申请实施例提供的一种网络设备的硬件结构示意图；
图13为本申请实施例提供的一种终端设备的硬件结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1为本申请实施例提供的一种系统架构图，如图1所示，本申请实施例提供一种通信系统，该通信系统100包括网络设备110以及多个终端设备，例如图1中的终端设备101至106。其中，网络设备110分别与终端设备101至106通信连接。示例性的，终端设备104和终端设备106还可以通过终端设备105与网络设备110通信连接。
本申请实施例涉及到的终端设备还可以称为终端，可以是一种具有无线收发功能的设备，其可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。终端设备可以是用户设备(user equipment，UE)，其中，UE包括具有无线通信功能的手持式设备、车载设备、可穿戴设备或计算设备。示例性地，UE可以是手机(mobile phone)、平板电脑或带无线收发功能的电脑。终端设备还可以是虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、智慧城市 (smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本申请实施例中，用于实现终端的功能的装置可以是终端；也可以是能够支持终端实现该功能的装置，例如芯片系统，该装置可以被安装在终端中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
本申请实施例涉及到的网络设备包括基站(base station，BS)，可以是一种部署在无线接入网中能够和终端进行无线通信的设备。其中，基站可能有多种形式，比如宏基站、微基站、中继站和接入点等。示例性地，本申请实施例涉及到的基站可以是5G中的基站或LTE中的基站，其中，5G中的基站还可以称为发送接收点(transmission reception point，TRP)或gNB。本申请实施例中，用于实现网络设备的功能的装置可以是网络设备；也可以是能够支持网络设备实现该功能的装置，例如芯片系统，该装置可以被安装在网络设备中。
本申请实施例的技术方案可以应用于长期演进(Long Term Evolution，LTE)架构，还可以应用于通用移动通信系统(Universal Mobile Telecommunications System，UMTS)陆地无线接入网(UMTS Terrestrial Radio Access Network，UTRAN)架构，或者全球移动通信系统(Global System for Mobile Communication，GSM)/增强型数据速率GSM演进(Enhanced Data Rate for GSM Evolution，EDGE)系统的无线接入网(GSM EDGE Radio Access Network，GERAN)架构。此外，本申请实施例提供的技术方案还可以应用于其它任何有类似结构和功能的无线通信系统中，例如公共陆地移动网络(Public Land Mobile Network，PLMN)系统，5G通信系统或5G之后的通信系统等，对此本申请实施例不作任何限制。需要说明的是，本申请实施例提供的技术方案还可以应用于机器对机器(machine-to-machine，M2M)系统，主要用于空口物理层过程，其系统架构可沿用现有的NR系统架构。
通信设备间的无线通信可以包括：网络设备和终端间的无线通信、网络设备和网络设备间的无线通信以及终端和终端间的无线通信。其中，在本申请实施例中，术语“无线通信”还可以简称为“通信”，术语“通信”还可以描述为“数据传输”、“信息传输”或“传输”。本领域技术人员可以将本申请实施例提供的技术方案用于进行网络设备和终端间的无线通信，例如接入网设备和终端间的无线通信，核心网设备和终端间的无线通信。
目前，NR系统中定义了带宽部分BWP，用于终端接收或发送数据。对于RRC_Idle或者RRC_Inactive态的终端，网络侧为终端配置一个初始下行BWP(initial downlink BWP)和一个初始上行BWP(initial uplink BWP)，初始下行BWP和初始上行BWP均为小区公共专属的BWP。对于RRC_Connected态的终端，除了初始上下行BWP，基站可以通过无线资源控制(Radio Resource Control，RRC)专用信令给每个终端配置用户专属的下行BWP和上行BWP，用户专属的上下BWP可以各配置最多四个。在一种实施方式中，网络侧可以通过RRC专用信令给终端配置初始上下行BWP。网络侧为终端配置其中一个BWP为激活BWP，终端在当前激活的BWP上工作。目前协议定义，对于FR1即载波频率小于6GHz时，初始下行BWP最大带宽为20MHz，初始上行BWP的配置没有限制，最大可以达到100MHz。
NR R17 REDCAP课题针对物联网场景，考虑引入新类型的终端，该终端相比现有的 NR终端，具有带宽减小、处理速度降低、天线数量减小等特点，这类终端被称为REDCAP类型的终端。REDCAP类型的终端可能支持一种或者多种带宽，典型的带宽包括5MHz、10MHz、20MHz。然而，NR系统现有的初始上行BWP带宽可能会超出REDCAP类型的终端的带宽，导致REDCAP类型的终端无法进行随机接入过程或者数据早传。
针对上述技术问题，本申请实施例提供一种频域资源的确定方法，主要针对通信系统中的REDCAP类型的终端，考虑为它们配置新的频域资源，配置的新的频域资源的带宽不超过REDCAP类型的终端的带宽。可以理解，在物联网场景下，接入的终端数量会非常多，考虑到上行传输包括msg1、msg3以及数据早传等，这将导致上行负荷比较重，因此网络侧可以为终端配置至少两个频域资源，以达到负载均衡的目的。
本申请实施例中的网络设备为终端设备配置的频域资源包括N个连续/非连续的物理资源块/资源块(PRB/RB)，其中，N为正整数。示例性的，频域资源包括N个连续的PRB/RB，频域资源可以是初始上行BWP。
在本申请实施例中，所有以初始上行BWP为举例的发明内容与以频域资源实施的发明内容是等效的。
在介绍本申请提供的技术方案之前，首先介绍当前NR系统的随机接入过程。
对于处于RRC_idle或者RRC_inactive态的终端，可通过上行随机接入过程完成网络接入。对于支持数据早传的终端，还可以在随机接入过程中完成数据传输。对于处于RRC_Connected态的终端，一种情况下，网络侧也可指示终端进行随机接入以重新获得时间提前量(timing advance，TA)同步，另一种情况下，由于波束失败，终端通过随机接入过程进行波束恢复。目前在NR中的随机接入过程包括以下两种类型：NR R15定义的4步随机接入过程(4-Step RACH过程)和NR R16定义的2步随机接入过程(2-Step RACH过程)。
图2为本申请实施例提供的一种随机接入过程的示意图，如图2所示，本实施例提供的随机接入过程为4-Step RACH过程，主要包括如下步骤：
步骤101、gNB向终端设备发送物理随机接入信道PRACH的资源配置。
具体的，gNB通过系统广播消息向终端设备发送PRACH的资源配置，主要包括PRACH的时频域资源、前导码preamble序列等。
在NR系统中，gNB发送和接收物理随机接入信道PRACH的时频资源被称为随机接入时机(RACH occasion，RO)。在同一RO上，gNB可配置多个相互正交的preambles，不同的终端设备可以在同一RO上采用不同或相同的preamble进行随机接入。
步骤102、终端设备通过PRACH向gNB发送Msg1。
Msg1包括前导码preamble。gNB在RO资源上检测各终端设备发送的preambles，如果检测到preambles，gNB响应于各终端设备的随机接入请求，执行步骤103。
步骤103、gNB向终端设备发送包括随机接入响应RAR的Msg2。
具体的，针对同一RO的RAR，gNB可通过随机接入无线网络临时标识RA-RNTI加扰循环冗余校验CRC的DCI format 1_0调度下行物理共享信道PDSCH，PDSCH中承载了针对该RO的全部或部分随机接入请求的RAR。同一RO仅和一个RA-RNTI相关联。
终端设备在发送Msg1之后，启动随机接入响应窗，在该窗口监听网络侧发送的RAR。
如果终端设备成功检测到RAR，则随机接入成功，执行步骤104。具体的，如果终端 设备接收到以RA-RNTI加扰的物理下行控制信道PDCCH，且该PDCCH调度的PDSCH所承载的RAR中，包含了一个以与发送的preamble index相同的随机接入前导码标识RAPID来进行标识的MAC subPDU，则认为随机接入成功。
如果终端设备没有检测到RAR，则随机接入失败，终端设备按照gNB指示的回退参数重新发起随机接入过程，直至达到最大随机接入次数。
步骤104、终端设备根据RAR的指示向gNB发送Msg3。
本步骤中，Msg3的主要作用是发送RRC连接建立请求，Msg3中携带有终端设备的标识ID。在数据早传场景中，Msg3还可以携带业务数据(UL small data)，这对于RRC_inactive态的终端，无需通过随机接入过程进入RRC_connected态之后再进行业务数据传输，从而达到节省空口资源、降低终端功耗、降低传输延迟的目的。
步骤105、gNB向终端设备发送Msg4(feedback)。
具体的，终端设备在发送Msg3之后，监听网络侧下发的Msg4，Msg4携带了冲突解决标识，以及针对该终端设备的空口参数配置。如果终端设备成功接收到Msg4，则随机接入成功，终端设备向gNB发送Msg5，Msg5用于发送RRC建立完成命令。如果终端设备没有接收到Msg4，则随机接入失败，终端设备按照gNB指示的回退参数重新发起随机接入过程，直至达到最大随机接入次数。
在现有NR技术中，对于4-Step RACH过程，Msg2和Msg4在初始下行BWP上传输，Msg1和Msg3在初始上行BWP上传输。对于Msg1，协议定义所有配置的PRACH资源必须完全位于初始上行BWP范围内。
图3为本申请实施例提供的一种随机接入过程的示意图，如图3所示，本实施例提供的随机接入过程为2-Step RACH过程，主要包括如下步骤：
步骤201、终端设备向gNB发送MsgA。
本步骤中，终端设备发送的MsgA包括4-Step RACH过程中的Msg1和Msg3，例如preamble、终端设备的ID。在数据早传场景中，MsgA还可以携带业务数据。
步骤202、gNB向终端设备发送MsgB。
本步骤中，MsgB相当于4-Step RACH过程中的Msg2(RAR)和Msg4(feedback)。针对同一RO的RAR，gNB可通过MsgB-RNTI/RA-RNTI加扰CRC的DCI format 1_0调度PDSCH，PDSCH中承载了针对该RO的全部或部分随机接入请求的RAR。同一RO仅和一个MsgB-RNTI/RA-RNTI相关联。
终端设备在发送preamble之后，启动随机接入响应时间窗MsgB-response window，在MsgB-response window内监听gNB下发的MsgB-RNTI加扰CRC的PDCCH，如果终端设备接收到以MsgB-RNTI加扰的物理下行控制信道PDCCH，且该PDCCH调度的PDSCH所承载的RAR中，包含了一个以与发送的preamble inde相同的随机接入前导码标识RAPID来进行标识的MAC subPDU，则认为随机接入成功。否则，认为随机接入失败。
如果终端设备preamble检测成功，物理上行共享信道PUSCH检测失败，2-Step RACH将退回至4-Step RACH，gNB返回的RAR为fallbackRAR。如果终端设备preamble和PUSCH均检测成功，gNB返回的RAR为successRAR。
在现有NR技术中，对于2-Step RACH过程，MsgB在初始下行BWP上传输，MsgA在初始上行BWP上传输。对于MsgA，协议定义所有配置的PRACH资源必须完全位于初 始上行BWP范围内。
需要说明的是，本申请实施例提供的技术方案可以在图2所示的随机接入过程中实现，也可以在图3所示的随机接入过程中实现。
下面通过具体实施例对本申请实施例提供的技术方案进行详细说明。需要说明的是，本申请实施例提供的技术方案可以包括以下内容中的部分或全部，下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。
图4为本申请实施例提供的一种频域资源的确定方法的交互示意图，如图4所示，本实施例提供的方法，包括如下步骤：
步骤301、网络设备为终端设备配置至少两个频域资源。
其中，至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源。第一类型频域资源用于第一类型终端设备和/或第二类型终端设备与网络设备通信，第二类型频域资源用于第二类型终端设备与网络设备通信。第一类型终端设备可以是普通终端，第二类型终端设备可以是REDCAP类型终端或其他终端。
需要说明的是，第一类型终端设备与第二类型终端设备之间的区别可以包括如下至少一项：
1、带宽能力不同。例如，第二类型终端设备的载波带宽不大于50MHz，例如为50MHz、40MHz、20MHz、15MHz、10MHz或者5MHz中的至少一种，第一类型终端设备的载波带宽大于50MHz。
2、收发天线数不同。例如，第二类型终端设备可以支持2收1发(2个接收天线和1个发送天线)，或者1收1发(1个接收天线和1个发送天线)。第一类型终端设备可以支持4收2发(4个接收天线和2个发送天线)。可以理解的是，在实现相同的数据传输速率的条件下，由于第二类型终端设备的收发天线个数少于第一类型终端设备的收发天线个数，因此第二类型终端设备与基站之间的数据传输所能实现的最大覆盖范围小于第一类型终端设备与基站之间的数据传输所能实现的最大覆盖范围。
3、上行最大发射功率不同。例如，第二类型终端设备的上行最大发射功率可以为4分贝毫瓦(dBm)～20dBm中的一个值。第一类型终端设备的上行最大发射功率可以为23dBm或者26dBm。
4、协议版本不同。第二类型终端设备可以是NR版本17(release-17，Rel-17)或者NR Rel-17以后版本中的终端设备。第一类型终端设备例如可以是NR版本15(release-15，Rel-15)或NR版本16(release-16，Rel-16)中的终端设备。第一类型终端设备也可以称为NR传统(NR legacy)终端设备。
5、载波聚合能力不同。例如，第二类型终端设备不支持载波聚合，第一类型终端设备可以支持载波聚合。又例如，第一类型终端设备和第二类型终端设备都可以支持载波聚合，但是第二类型终端设备同时支持的载波聚合的最大个数小于第一类型终端设备同时支持的载波聚合的最大个数，例如第二类型终端设备最多同时支持2个载波的聚合，第一类型终端设备可以最多同时支持5个载波或者32个载波的聚合。
6、双工能力不同。例如，第二类型终端设备支持半双工频分双工(frequency division duplexing，FDD)。第一类型终端设备支持全双工FDD。
7、数据的处理时间能力不同。例如，第二类型终端设备接收下行数据与发送对该下 行数据的反馈之间的最小时延大于第一类型终端设备接收下行数据与发送对该下行数据的反馈之间的最小时延；和/或，第二类型终端设备发送上行数据与接收对该上行数据的反馈之间的最小时延大于第一类型终端设备发送上行数据与接收对该上行数据的反馈之间的最小时延。
8、处理能力(ability/capability)不同。例如，第二类型终端设备的基带处理能力低于第一类型终端设备的基带处理能力。其中，基带处理能力可以包括以下至少一项：终端设备进行数据传输时支持的最大多进多出(multiple input multiple output，MIMO)层数，终端设备支持的混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)进程数目，终端设备支持的最大传输块大小(transmission block size，TBS)。
9、上行和/或下行的传输峰值速率不同。传输峰值速率是指终端设备在单位时间内(例如每秒)能够达到的最大数据传输速率。第二类型终端设备支持的上行峰值速率可以低于第一类型终端设备支持的上行峰值速率，和/或第二类型终端设备支持的下行峰值速率可以低于第一类型终端设备支持的下行峰值速率。例如，第二类型终端设备的上行峰值速率小于或等于50Mbps，下行峰值速率小于或等于150Mbps，第一类型终端设备的上行峰值速率大于或等于50Mbps，下行峰值速率大于或等于150Mbps。又例如，第二类型终端设备的上行峰值速率或下行为百Mbps量级，第一类型终端设备的上行峰值速率或下行峰值速率为Gbps量级。
10、缓存(buffer)大小不同。缓存buffer可以理解为层2(Layer 2，L2)缓存总大小，其定义为终端设备对于所有无线承载，在无线链接控制(radio link control，RLC)发送窗和接收以及重排序窗中缓存的字节数与在数据包汇聚协议(Packet Data Convergence Protocol，PDCP)重排序窗中缓存的字节数之和。或者，缓存buffer也可以理解为HARQ处理所能使用的软信道比特总数。
示例性的，图5为本申请实施例提供的网络设备为终端设备配置的频域资源的示意图。图5中以网络设备为终端设备配置一个第一类型频域资源和一个第二类型频域资源为例进行举例。在一些实施例中，如图5中的(a)所示，第一类型频域资源与第二类型频域资源为在频域上连续的两个频域资源。在一些实施例中，如图5中的(b)所示，第一类型频域资源与第二类型频域资源为在频域上不连续的两个频域资源。在一些实施例中，如图5中的(c)所示，第一类型频域资源与第二类型频域资源存在重叠部分。
以下，以初始上行BWP作为频域资源，第一初始上行BWP作为第一类型频域资源，第二初始上行BWP作为第二类型频域资源进行举例，应理解，频域资源还可以是下行BWP。
示例性的，网络设备为终端设备配置至少两个初始上行BWP，包括：第一初始上行BWP以及至少一个第二初始上行BWP。其中，第一初始上行BWP为现有协议中网络侧为终端设备配置的一个初始上行BWP，又可以称为UL initial BWP，可用于普通终端与网络设备进行通信，在一些实施例中，第一初始上行BWP还可用于REDCAP类型终端与网络设备进行通信。第二初始上行BWP为网络侧为终端设备新配置的初始上行BWP，第二初始上行BWP可用于REDCAP类型终端与网络设备进行通信。
在一种可能的实施方式中，配置的第二初始上行BWP可能只用于REDCAP类型的终端。示例性的，网络设备为终端设备配置两个第二初始上行BWP的带宽，分别为20MHz以及10MHz，或者，20MHZ以及5MHz，这两个第二初始上行BWP的带宽可用于REDCAP 类型的终端与网络设备进行通信，通过为REDCAP终端设备配置专用的初始上行BWP，专用的BWP的配置过程中可以充分考虑REDCAP终端设备支持的带宽限制，从而能够保证REDCAP终端设备可以成功地通过第二初始上行BWP接入网络设备，进一步的可以对于不同带宽的REDCAP终端配置不同带宽的第二初始上行BWP，从而既能有效避免REDCAP终端由于带宽限制无法接入现有的第一初始上行BWP的问题，也能通过配置新的不同种类的第二初始上行BWP达到平衡不同BWP的接入负载的效果。
在一种可能的实施方式中，配置的第二初始上行BWP可能同时用于REDCAP类型的终端和普通终端。示例性的，网络设备为终端设备配置一个第二初始上行BWP的带宽为20MHz，该第二初始上行BWP的带宽可用于部分REDCAP类型的终端与网络设备进行通信，也可用于普通终端与网络设备进行通信，在这种情况下，第二初始上行BWP的配置可以有效缓解第一初始上行BWP的负载过大的情况，又兼顾了REDCAP类型终端的接入能力，提升了第二初始上行BWP的利用效率。
本申请实施例中，REDCAP类型的终端可以是海量机器类通信(massive Machine Type of Communication，mMTC)终端、低能力终端、或者物联网终端，对此本申请实施例不作任何限制。
第二初始上行BWP与第一初始上行BWP的带宽关系包括如下几种可能的情况：
在一种可能的情况下，网络设备配置了一个第二初始上行BWP和一个第一初始上行BWP，该第二初始上行BWP的带宽小于或等于该第一初始上行BWP的带宽。上述情况，终端设备可直接根据来自网络设备的配置信息，确定至少两个初始上行BWP中的一个BWP，使用该BWP与网络设备通信。终端设备确定的至少两个初始上行BWP中的一个BWP可以是第一初始上行BWP(前提是第一初始上行BWP的带宽小于或等于终端设备支持的最大带宽)，或者，第二初始上行BWP。当配置信息中配置的第二初始上行BWP的数量是1且第一初始上行BWP的带宽大于终端设备支持的带宽时，终端设备可以直接根据配置信息判断接入第二初始上行BWP，而不需要额外的指示信息来指示。
在一种可能的情况下，网络设备配置了至少两个第二初始上行BWP和一个第一初始上行BWP，至少两个第二初始上行BWP中的每一个第二初始上行BWP的带宽均小于或等于该第一初始上行BWP的带宽。上述情况中，终端设备可根据配置信息，从至少两个第二初始上行BWP中确定一个第二初始上行BWP，使用该第二初始上行BWP与网络设备进行通信。或者，终端设备可根据配置信息，从第一初始上行BWP(前提是第一初始上行BWP的带宽小于或等于终端设备支持的最大带宽)和至少两个初始上行BWP中确定一个BWP，使用该BWP与网络设备进行通信。
在一种可能的情况下，网络设备配置了至少两个第二初始上行BWP和一个第一初始上行BWP，至少两个第二初始上行BWP中的一部分第二初始上行BWP的带宽小于或等于该第一初始上行BWP的带宽，另一部分第二初始上行BWP的带宽大于该第一初始上行BWP的带宽。
在一种可能的情况下，网络设备配置了至少一个第二初始上行BWP和多个第一初始上行BWP。示例性的，第二初始上行BWP中的每一个第二初始上行BWP的带宽小于或等于终端设备支持的最大带宽，多个第一初始上行BWP中至少有一个第一初始上行BWP的带宽小于或等于终端设备支持的最大带宽。终端设备可根据配置信息，从至少一个第二 初始上行BWP和多个第一初始上行BWP中的至少一个第一初始上行BWP中确定一个BWP，使用该BWP与网络设备进行通信。示例性的，第二初始上行BWP中的部分第二初始上行BWP的带宽小于或等于终端设备支持的最大带宽，多个第一初始上行BWP中至少有一个第一初始上行BWP的带宽小于或等于终端设备支持的最大带宽。终端设备可根据配置信息，从部分第二初始上行BWP和多个第一初始上行BWP中的至少一个第一初始上行BWP中确定一个BWP，使用该BWP与网络设备进行通信。
第一初始上行BWP与终端设备支持的最大带宽之间的关系包括如下几种可能的情况：
在一种可能的情况下，网络设备配置了一个第一初始上行BWP，该第一初始上行BWP的带宽小于或等于终端设备支持的最大带宽，或者，该第一初始上行BWP的带宽大于终端设备支持的最大带宽。
在一种可能的情况下，网络设备配置了至少两个第一初始上行BWP，至少两个第一初始上行BWP中的每一个第一初始上行BWP的带宽均大于终端设备支持的最大带宽，或者，至少两个第一初始上行BWP中的至少一个第一初始上行BWP的带宽小于或等于终端设备支持的最大带宽。
第二初始上行BWP与终端设备支持的最大带宽之间的关系包括如下几种可能的情况：
在一种可能的情况下，网络设备配置了一个第二初始上行BWP，该第二初始上行BWP的带宽小于或等于终端设备支持的最大带宽。
在一种可能的情况下，网络设备配置了至少两个第二初始上行BWP，至少两个第二初始上行BWP中的所有第二初始上行BWP的带宽小于或等于终端设备支持的最大带宽。
在一种可能的情况下，网络设备配置了至少两个第二初始上行BWP，至少两个第二初始上行BWP中的一部分第二初始上行BWP的带宽小于或等于终端设备支持的最大带宽。
本申请实施例中，终端设备支持的最大带宽可以是指REDCAP类型的终端支持的最大带宽。通常，REDCAP类型的终端支持的最大带宽包括5MHz、10MHz、20MHz。
基于上述描述，下面对网络设备为REDCAP类型终端配置初始上行BWP作如下总结：
在一种可能的实施方式中，如果网络设备只配置了第一初始上行BWP，没有给REDCAP类型终端配置专用的初始上行BWP，且该第一初始上行BWP的带宽大于REDCAP类型终端支持的最大带宽，则可以理解为网络设备采用隐式方式指示了REDCAP类型终端禁止接入小区。
在一种可能的实施方式中，如果网络设备配置了第一初始上行BWP以及REDCAP类型终端专用的初始上行BWP，且该第一初始上行BWP的带宽大于REDCAP类型终端支持的最大带宽。该实例的REDCAP类型终端可采用上述专用的初始上行BWP发送上行数据。
在一种可能的实施方式中，如果网络设备配置了第一初始上行BWP以及REDCAP类型终端专用的初始上行BWP，且该第一初始上行BWP的带宽小于或等于REDCAP类型终端支持的最大带宽。该实例的REDCAP类型终端可采用第一初始上行BWP或上述专用的初始上行BWP发送上行数据。
步骤302、网络设备向终端设备发送配置信息，配置信息包括至少两个频域资源的配置信息。
以下，以初始上行BWP作为频域资源，应理解，频域资源还可以是下行BWP。
在一些实施例中，网络设备可通过系统信息向终端设备发送配置信息，系统信息包括SIB1以及其他系统信息。在一些实施例中，网络设备还可通过无线资源控制层RRC信令、媒体接入控制层控制单元MAC CE控制单元等高层信令发送配置信息。在一些实施例中，网络设备还可以通过下行控制信息DCI等物理层信令发送配置信息。
至少两个初始上行BWP中任意一个初始上行BWP的配置信息包括该BWP的频域位置和带宽、随机接入信道RACH配置信息、物理上行共享信道PUSCH配置信息、物理上行控制信道PUCCH配置信息等上行传输配置信息或者其中的一部分。
步骤303、终端设备根据配置信息确定至少两个频域资源的一个频域资源。
在一些实施例中，终端设备还可根据预定义或者预配置的规则确定至少两个频域的一个频域。
需要说明的是，在一些实施例中，本实施例的步骤303可作为一个可选的步骤。
步骤304、终端设备使用至少两个频域资源中的一个频域资源与网络设备进行通信。
以下，以初始上行BWP作为频域资源，第一初始上行BWP作为第一类型频域资源，第二初始上行BWP作为第二类型频域资源进行举例，应理解，频域资源还可以是下行BWP。
在一种可能的实施方式中，如果终端设备为普通终端，终端设备可根据配置信息中配置的至少两个初始上行BWP中的第一初始上行BWP与网络设备进行通信，即仍然通过初始上行BWP与网络设备进行通信。
可选的，如果至少两个初始上行BWP中的第二初始上行BWP中有一个或多个BWP的带宽小于或等于普通终端支持的最大带宽，终端设备还可以根据配置信息中配置的至少两个初始上行BWP中的第二初始上行BWP与网络设备进行通信。
在一种可能的实施方式中，如果终端设备为REDCAP类型的终端，终端设备可根据配置信息中配置的至少两个初始上行BWP中的至少一个第二初始上行BWP与网络设备进行通信。
可选的，如果至少两个初始上行BWP中的至少一个第二初始上行BWP的带宽均小于REDCAP类型的终端支持的最大带宽，则终端设备可根据配置信息中配置的至少两个初始上行BWP中的任意一个第二初始上行BWP与网络设备进行通信。
可选的，如果至少两个初始上行BWP中的第一初始上行BWP的带宽为20MHz，REDCAP类型的终端支持的最大带宽也为20MHz，则终端设备可根据配置信息中配置的至少两个初始上行BWP中的第一初始上行BWP与网络设备进行通信。
在一种可能实施方式中，在4-Step RACH过程中，终端设备在确定的至少两个初始上行BWP中的一个BWP上发送Msg1或者Msg3或者后续的其他上行数据。
在一种可能实施方式中，在2-Step RACH过程中，终端设备在确定的至少两个初始上行BWP中的一个BWP上发送MsgA或者其他上行数据。
本实施例提供的频域资源的确定方法，通过网络设备向终端设备发送配置有至少两个频域资源的配置信息，终端设备根据配置信息确定至少两个频域资源的其中一个频域资源，使用该频域资源与网络设备进行通信。由于网络设备为终端设备配置了多个频域资源，这多个频域资源中至少有一个频域资源可供终端设备使用，这样可以避免由于当前网络侧配置的频域资源的带宽超出终端设备支持的最大带宽，使得终端设备无法与网络设备进行正常通信的问题，提高了终端设备的数据传输性能，提升了通信的可靠性。
上述实施例示出了网络侧为终端设备配置多个频域资源的技术方案，提高了不同类型终端的数据传输性能。在上述实施例的基础上，下述实施例示出了网络侧向终端设备发出指示信息，终端设备具体根据网络侧的指示信息确定多个频域资源中的一个频域资源，并基于该频域资源的带宽向网络侧发送上行数据。
下面结合附图6对本实施例提供的频域资源的确定方法进行详细说明。图6为本申请实施例提供的一种频域资源的确定方法的交互示意图，如图6所示，本实施例提供的方法，包括如下步骤：
步骤401、网络设备为终端设备配置至少两个频域资源。
步骤402、网络设备向终端设备发送配置信息，配置信息包括至少两个频域资源的配置信息。
本实施例的步骤401和步骤402同上述实施例的步骤301和步骤302，具体可参见上述实施例，此处不再赘述。
步骤403、网络设备向终端设备发送指示信息。
以下，以初始上行BWP作为频域资源，第一初始上行BWP作为第一类型频域资源，第二初始上行BWP作为第二类型频域资源进行举例，应理解，频域资源还可以是下行BWP。
其中，指示信息用于指示终端设备使用至少两个初始上行BWP中的一个BWP与网络设备进行通信。或者说，指示信息用于指示终端设备在至少两个初始上行BWP中的一个BWP的带宽上与网络设备进行通信，亦或者说，指示信息用于指示终端设备通过至少两个初始上行BWP中的一个BWP的带宽与网络设备进行通信。
指示信息中指示的BWP可以是至少一个第一初始上行BWP中的一个第一初始上行BWP，还可以是至少一个第二初始上行BWP中的一个第二初始上行BWP。
在一种可能的情况下，网络设备配置了一个第二初始上行BWP和一个第一初始上行BWP。
当第一初始上行BWP可以用于第一类型终端设备和第二类型终端设备与网络设备通信，第二初始上行BWP用于第二类型终端设备与网络设备通信时，指示信息可用于指示终端设备使用第一初始上行BWP或第二初始上行BWP与网络设备进行通信。
当第一初始上行BWP仅用于第一类型终端设备与网络设备通信，第二初始上行BWP用于第二类型终端设备与网络设备通信时，指示信息可用于指示终端设备使用第二初始上行BWP与网络设备进行通信。终端设备可以直接根据配置信息确定使用第二初始上行BWP与网络设备通信，或者也可以根据配置信息和指示信息确定使用第二初始上行BWP与网络设备进行通信。
在一种可能的情况下，网络设备配置了至少两个第二初始上行BWP和一个第一初始上行BWP，至少两个第二初始上行BWP中的每一个第二初始上行BWP的带宽均小于或等于该第一初始上行BWP的带宽，第一初始上行BWP可用于第一类型终端设备和第二类型终端设备与网络设备通信。在一些实施例中，指示信息可用于指示至少两个第二初始上行BWP中的一个第二初始上行BWP，该情况中，终端设备可根据配置信息以及指示信息，从至少两个第二初始上行BWP中确定一个第二初始上行BWP，使用该第二初始上行BWP与网络设备进行通信。此时指示信息主要用于指示至少两个第二初始上行BWP中的一个第二初始上行BWP。在一些实施例中，指示信息可用于指示该第一初始上行BWP，该情 况中，终端设备可根据配置信息以及指示信息，确定第一初始上行BWP，使用该第一初始上行BWP与网络设备进行通信。
本申请实施例中，网络设备为终端设备配置至少两个初始上行BWP之后，可通过随机接入过程向终端设备发送指示信息，即指示信息可以包括在随机接入响应消息中，随机接入响应消息用于网络设备响应终端设备的随机接入请求。
具体的，指示信息可以包括在如下几种消息中：
在4-Step RACH过程中，指示信息可以包括在Msg2中，Msg2用于网络设备响应终端设备的随机接入请求。在2-Step RACH过程中，指示信息可以包括在MsgB中，MsgB用于网络设备响应终端设备的随机接入请求。
下面针对4-Step RACH过程中的指示信息进行详细说明。
在一种可能的实施方式中，指示信息包括在Msg2的随机接入响应RAR中，RAR用于网络设备响应终端设备的随机接入请求(即Msg1)。
具体的，指示信息包括在Msg2的RAR中，包括如下几种情况：
第一种情况，指示信息位于Msg2的RAR中上行授权UL grant的PUSCH频域资源分配指示域。可选的，指示信息位于RAR中UL grant的PUSCH频域资源分配指示域的若干高位比特(most significant bit，MSB)中。
具体的，对于非共享频谱信道接入场景，RAR中UL grant的PUSCH频域资源分配域包含14bits，如图7所示。当初始上行BWP带宽(bandwidth，BW)配置为20MHz且子载波间隔(subcarrier space，SCS)为30kHz时，PUSCH频域资源分配域中的11个低位比特用于指示PUSCH的频域资源分配。当BW＝20MHz&SCS＝15kHz时，PUSCH频域资源分配域中的13个低位比特用于指示PUSCH的频域资源分配。此时PUSCH频域资源分配域的若干高位比特空余，对于REDCAP类型终端，空余的高位比特可进行重解读，用于指示终端进行上行传输所使用的上行BWP，包括新配置的至少一个第二初始上行BWP或者第一初始上行BWP。
可选的，如果REDCAP类型终端确定了多个可用的初始上行BWP，则终端还可根据多个可用的初始上行BWP中物理资源块PRB数最多的初始上行BWP确定RAR中UL grant的PUSCH频域资源分配域占用的比特数。
下面以网络设备预配置两个REDCAP类型终端专用的初始上行BWP(即预配置两个第二初始上行BWP)为例，对网络设备的指示信息进行说明。假设预配置的两个REDCAP类型终端专用的初始上行BWP分别命名为NR REDCAP initial UL BWP#1和NR REDCAP initial UL BWP#2，其中，initial UL还可以记为UL initial。
(1)当第一初始上行BWP的带宽大于NR REDCAP类型终端支持的最大带宽时，可以使用RAR中UL grant的PUSCH频域资源分配域的高位1个比特指示终端设备发送Msg3或其他上行传输所使用的初始上行BWP，示例性的，如表1所示。
表1
PUSCH频域资源分配域的MSB 1bit 初始上行BWP索引
0 initial UL BWP 1_NR REDCAP
1 initial UL BWP 2_NR REDCAP
可选的，也可以使用RAR中UL grant的PUSCH频域资源分配域的高位2个比特指示 预配置的两个REDCAP类型终端专用的初始上行BWP的其中一个，2比特可表示4个指示状态。示例性的，如表2所示，其中两个状态分别指示配置的两个REDCAP类型终端专用的初始上行BWP，其中一个状态可以指示NR现有的初始上行BWP，即第一初始上行BWP，可表示为UL initial BWP_NR legacy，由于NR现有的初始上行BWP的带宽超出REDCAP类型终端支持的最大带宽，因此网络设备可通过指示NR现有的初始上行BWP的方式指示禁止REDCAP类型的终端接入，或者说，指示禁止当前接入的REDCAP类型的终端接入。
表2
Figure PCTCN2021109897-appb-000001
(2)当第一初始上行BWP的带宽小于或等于NR REDCAP类型终端支持的最大带宽时，可以使用RAR中UL grant的PUSCH频域资源分配域的高位2个比特指示终端设备发送Msg3或其他上行传输所使用的初始上行BWP。示例性的，如表3所示，可使用2比特的三个状态分别指示第一初始上行BWP以及两个REDCAP类型终端专用的初始上行BWP。进一步的，还可以使用2比特的剩余一个状态指示是否允许REDCAP类型终端接入当前小区，当指示禁止接入时，REDCAP类型终端则不能接入到当前小区中。
表3
PUSCH频域资源分配域的MSB 2bits 初始上行BWP索引
00 initial UL BWP_NR legacy
01 initial UL BWP 1_NR REDCAP
10 initial UL BWP 2_NR REDCAP
11 禁止REDCAP类型终端接入
第二种情况，指示信息位于携带RAR的MAC subPDU的RAPID的若干低位比特(least significant bit，LSB)中。
第三种情况，指示信息位于携带RAR的MAC subPDU的预留比特的若干比特中。
图8为本申请实施例提供的MAC RAR的结构示意图，如图8所示，指示信息可位于图8所示的UL grant的PUSCH频域资源分配域的若干高位比特中，还可位于图8所示的RAPID域的若干低位比特中，还可位于图8所示的R域(即预留比特)的若干比特中。需要说明的是，如果上述任意一个域的比特不够用，网络设备还可通过上述任意两个或三个域的比特联合指示终端设备发送Msg3或其他上行传输所使用的初始上行BWP。示例性的，表4示出了图8中的UL grant的比特分配表(可用于非共享频谱信道接入场景)。
表4
Figure PCTCN2021109897-appb-000002
Figure PCTCN2021109897-appb-000003
上述实施方式，网络设备通过Msg2的随机接入响应RAR中的若干比特指示终端设备(可以特指REDCAP类型终端)发送Msg3或其他上行传输所使用的初始上行BWP，使得终端设备根据指示信息接入当前小区，提高终端设备的数据传输性能。除此之外，还包括如下两种可能的实施方式。
在一种可能的实施方式中，指示信息包括在用于调度Msg2的DCI(或者说用于调度承载RAR的PDSCH)中。具体的，指示信息位于DCI的预留reserved比特的若干比特中。
可选的，网络设备可通过RA-RNTI加扰CRC的DCI中的预留比特的若干比特指示终端设备发送Msg3或其他上行传输所使用的初始上行BWP。该实施方式中网络设备指示初始上行BWP的比特长度和指示方式同上述第一种实施方式，具体可参见上文。
在本实施方式中，采用同一RO发起随机接入的终端设备，或者说监听相同RA-RNTI加扰CRC的DCI的终端设备，均可通过网络设备发送的DCI中的预留比特的若干比特，确定发送Msg3或其他上行传输所使用的初始上行BWP。
在一些实施例中，由于多个终端设备可使用同一个RO的不同前导码preamble发起的随机接入，网络设备可根据preamble ID和/或RAPID对终端设备进行分组，网络设备可通过同一若干比特指示相同分组的终端设备初始上行BWP。网络设备可通过SIB1或高层配置对终端设备的分组，分组方法包括：
方法1：preamble ID/RAPID mod N＝X的UE分成一组，X＝{0,1…,N-1}；
方法2：连续的M个preamble ID/RAPID的UE分成一组，例如：{0,1,…,M-1}，{M,M+1,M+2,…,2M-1}，…,{M*N-M,M*N-M-2,…,M*N-1}，其中N为分组数，M*N为同一RO上复用的preamble个数。
如果每个分组使用X个比特指示该分组的使用的初始上行BWP，则共需占用DCI reserved比特中的N*X个比特，如图9所示。
可选的，网络设备可以对同一RO不同preamble相应的RAR进行分组传输，分组方法同上，则承载RAR的MAC subPDU的RAPID的
Figure PCTCN2021109897-appb-000004
(N为RAR的分组数)个低位比特可以重用，同样可用于指示终端设备发送Msg3或其他上行传输所使用的初始上行BWP。
上述实施方式，网络设备通过用于调度Msg2的DCI中的若干比特指示终端设备(可以特指REDCAP类型终端)发送Msg3或其他上行传输所使用的初始上行BWP，使得终端设备根据指示信息接入当前小区，提高终端设备的数据传输性能。
在一种可能的实施方式中，指示信息包括在用于调度Msg2的DCI，以及RAR中。该方式主要考虑到DCI或RAR中的比特不够用的情况，网络设备可通过DCI和RAR中比 特的组合，联合指示至少两个初始上行BWP中的一个BWP。联合指示可达到节能比特开销的目的。在一些实施例中，指示信息还可以既包括在用于调度Msg2的DCI，又包括在Msg2的RAR中。
可选的，对于4-Step RACH过程中的指示信息，本实施例中指出的所有可用于指示初始上行BWP的指示域中的任意两个、三个或者更多的指示域的比特，可以联合指示一个或者一组终端设备的初始上行BWP。
可选的，上述指示域的比特还可用于指示Msg2、Msg3、Msg4等信道进行重复传输以及重复传输的次数。
上述实施例示出了4-Step RACH过程中的指示信息，下面针对2-Step RACH过程中的指示信息进行详细说明。
对于2-Step RACH过程，终端设备通过PRACH和PUSCH两个信道发送MsgA(包括Msg1和Msg3)。在非数据早传场景中，在PUSCH中承载Msg3；在数据早传场景中，PUSCH中可以承载上行业务数据。
对于初始接入场景，在一种实施方式中，终端设备发送MsgA-PUSCH的初始上行BWP是预定义或预配置的。网络设备可通过SIB1或其他系统信息预配置发送MsgA-PUSCH的初始上行BWP的配置信息，终端设备根据该配置信息确定发送MsgA-PUSCH的初始上行BWP。对于非初始接入场景，例如RRC连接态或非激活态或空闲态的终端设备，以上方法同样适用。
在另一种实施方式中，网络设备除了向终端设备发送配置信息之外，还可以向终端设备发送指示信息，发送的指示信息包括如下几种可能的实施方式：
在一种可能的实施方式中，指示信息包括在MsgB的随机接入响应RAR中，RAR用于网络设备响应终端设备的随机接入请求(即MsgA)。
具体的，指示信息包括在MsgB的RAR中，具体包括如下几种情况：
第一种情况，指示信息位于MsgB的RAR中上行授权UL grant的PUSCH频域资源分配指示域。可选的，指示信息位于MsgB的RAR中UL grant的PUSCH频域资源分配指示域的若干高位比特中。可选的，指示信息位于MsgB的successRAR/fallbackRAR中UL grant的PUSCH频域资源分配指示域的若干高位比特。
在一些实施例中，网络设备接收来自终端设备的MsgA，当网络设备同时检测到preamble和MsgA-PUSCH，则随机接入成功，网络设备在MsgB中发送冲突解决标识。同时，网络设备通过MsgB的successRAR指示终端设备后续上行传输使用的初始上行BWP，包括MsgB-PUSCH反馈、后续的4-Step RA(random access)过程或者2-Step RA过程。
在一些实施例中，网络设备接收来自终端设备的MsgA，当网络设备只检测到preamble，没有检测到MsgA-PUSCH时，2-Step RACH可以回退到4-Step RACH，网络设备在MsgB中通过fallbackRAR调度PUSCH继续进行传输。其中，MsgA-PUSCH检测失败的一个比较重要的原因是信道质量较差，在一种实施方式中，网络设备可通过指示终端设备在与第一次不同的初始上行BWP上传输MsgA-PUSCH，可实现在更大频率范围内进行跳频，以增加频率选择性增益。
第二种情况，指示信息位于携带RAR的MAC subPDU的RAPID的若干低位比特中。可选的，指示信息位于携带successRAR/fallbackRAR的MAC subPDU的RAPID的若干低 位比特中。
第三种情况，指示信息位于携带RAR的MAC subPDU的预留比特的若干比特中。可选的，指示信息位于携带successRAR/fallbackRAR的MAC subPDU的预留比特的若干比特中。
在一种可能的实施方式中，指示信息包括在用于调度MsgB的DCI中。具体的，指示信息位于DCI的预留reserved比特。
可选的，网络设备可通过RA/MsgB-RNTI加扰CRC的DCI中的预留比特的若干比特指示终端设备发送Msg3或其他上行传输所使用的初始上行BWP。该实施方式中网络设备指示初始上行BWP的比特长度和指示方式同上述4-Step RACH实施例中指示信息的第一种实施方式，具体可参见上文。
在一些实施例中，网络设备接收来自终端设备的MsgA，当网络设备只检测到preamble，没有检测到MsgA-PUSCH时，2-Step RACH可以回退到4-Step RACH，网络设备在MsgB中通过fallbackRAR调度PUSCH继续进行传输。同时，网络设备还可以通过用于调度MsgB的DCI指示终端设备后续上行传输使用的初始上行BWP。
在一种可能的实施方式中，指示信息包括在用于调度MsgB的DCI，以及RAR中。该方式主要考虑到DCI或RAR中的比特不够用的情况，网络设备可通过DCI和RAR中比特的组合，联合指示至少两个初始上行BWP中的一个BWP。
可选的，对于2-Step RACH过程中的指示信息，本实施例中指出的所有可用于指示初始上行BWP的指示域中的任意两个、三个或者更多的指示域的比特，可以联合指示一个或者一组终端设备的初始上行BWP。
步骤404、终端设备根据配置信息以及指示信息，确定至少两个频域资源的一个频域资源。
步骤405、终端设备使用至少两个频域资源中的一个频域资源与网络设备进行通信。
以下，以初始上行BWP作为频域资源，应理解，频域资源还可以是下行BWP。
在4-Step RACH过程中，终端设备根据配置信息以及指示信息，确定至少两个初始上行BWP中的一个BWP，在确定的这个BWP的带宽上发送Msg3或者后续的其他上行数据。
在2-Step RACH过程中，终端设备根据配置信息以及指示信息，确定至少两个初始上行BWP中的一个BWP，在确定的这个BWP的带宽上发送后续的其他上行数据。
本实施例提供的频域资源的确定方法，网络设备通过系统信息或信令为终端设备预配置至少两个频域资源，可通过随机接入过程中用于调度Msg2/MsgB的DCI和/或随机接入响应消息指示终端设备后续传输上行数据使用的一个频域资源，终端设备根据网络侧的预配置和指示，确定至少两个频域资源中的一个频域资源，使用该频域资源与网络设备进行通信。上述方案解决了当前网络侧配置的频域资源可能超出终端设备支持的最大带宽，导致终端设备无法与网络设备进行通信的问题，提高通信过程的可靠性。同时，增加了网络侧上行频率选择性增益，也有利于网络侧在多个频域资源之间灵活进行负载均衡，提高终端设备的数据传输性能。
图10为本申请实施例提供的一种网络设备的结构示意图。示例性地，网络设备500例如为图4所示的实施例或图6所示的实施例所述的网络设备。
网络设备500包括处理模块501。可选的，还可以包括收发模块502。示例性地，网络设备500可以是网络设备，也可以是应用于网络设备中的芯片或者其他具有上述网络设备功能的组合器件、部件等。当网络设备500是网络设备时，收发模块502可以是收发器，收发器可以包括天线和射频电路等，处理模块501可以是处理器(或者，处理电路)，例如基带处理器，基带处理器中可以包括一个或多个中央处理器CPU。当网络设备500是具有上述网络设备功能的部件时，收发模块502可以是射频单元，处理模块501可以是处理器(或者，处理电路)，例如基带处理器。当网络设备500是芯片系统时，收发模块502可以是芯片(例如基带芯片)的输入输出接口、处理模块501可以是芯片系统的处理器(或者，处理电路)，可以包括一个或多个中央处理单元。应理解，本申请实施例中的处理模块501可以由处理器或处理器相关电路组件(或者，称为处理电路)实现，收发模块502可以由收发器或收发器相关电路组件实现。
在一种可能的实施方式中，收发模块502，用于向终端设备发送配置信息，所述配置信息包括至少两个频域资源的配置信息，所述至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源；所述第一类型频域资源用于第一类型终端设备和/或第二类型终端设备与所述网络设备通信；所述第二类型频域资源用于所述第二类型终端设备与所述网络设备通信；处理模块501，用于使用所述至少两个频域资源中的一个频域资源与所述终端设备通信。
可选的，第一类型频域资源包括第一初始上行带宽部分BWP，第二类型频域资源包括第二初始上行BWP。
可选的，所述第一类型频域资源用于所述第一类型终端设备和所述第二类型终端设备与所述网络设备通信；所述收发模块502，还用于向所述终端设备发送指示信息，所述指示信息用于指示所述至少两个频域资源中的一个频域资源。
可选的，所述第一类型频域资源仅用于所述第一类型终端设备与所述网络设备通信，所述收发模块502，还用于向所述终端设备发送指示信息，所述指示信息用于指示所述至少两个频域资源中的一个第二类型频域资源。
可选的，所述指示信息包括在随机接入响应消息中，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在Msg2中，所述Msg2用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在MsgB中，所述MsgB用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域。在一种可能的实施方式中，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域的至少一个高位比特中。
可选的，所述指示信息包括在下行控制信息DCI中，所述DCI用于调度随机接入响应消息，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。在一种可能的实施方式中，所述指示信息包括在所述DCI的预留比特中。
可选的，所述指示信息包括在所述随机接入响应消息和调度所述随机接入响应消息的 DCI中，所述随机接入响应消息和所述DCI中的比特共同指示所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
可选的，所述第二类型频域资源的带宽小于或等于所述终端设备支持的最大带宽。
可选的，所述收发模块502，具体用于通过系统信息或高层信令或者物理层信令，向所述终端设备发送所述配置信息。
本实施例提供的网络设备，可用于执行上述任一方法实施例中网络设备的技术方案，其实现原理和技术效果类似，此处不再赘述。
图11为本申请实施例提供的一种终端设备的结构示意图。示例性的，终端设备600例如为图4所示的实施例或图6所示的实施例所述的终端设备。
终端设备600包括处理模块601。可选的，还可以包括收发模块602。示例性地，终端设备600可以是终端设备，也可以是应用于终端设备中的芯片或者其他具有上述终端设备功能的组合器件、部件等。当终端设备600是终端设备时，收发模块602可以是收发器，收发器可以包括天线和射频电路等，处理模块601可以是处理器(或者，处理电路)，例如基带处理器，基带处理器中可以包括一个或多个中央处理器CPU。当终端设备600是具有上述终端设备功能的部件时，收发模块602可以是射频单元，处理模块601可以是处理器(或者，处理电路)，例如基带处理器。当终端设备600是芯片系统时，收发模块602可以是芯片(例如基带芯片)的输入输出接口、处理模块601可以是芯片系统的处理器(或者，处理电路)，可以包括一个或多个中央处理单元。应理解，本申请实施例中的处理模块601可以由处理器或处理器相关电路组件(或者，称为处理电路)实现，收发模块602可以由收发器或收发器相关电路组件实现。
在一种可能的实施方式中，收发模块602，用于接收来自网络设备的配置信息，所述配置信息包括至少两个频域资源的配置信息，所述至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源；所述第一类型频域资源用于第一类型终端设备和/第二类型终端设备与所述网络设备通信；所述第二类型频域资源用于所述第二类型终端设备与所述网络设备通信；
处理模块601，用于根据所述配置信息确定所述至少两个频域资源中的一个频域资源，使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
可选的，所述第一类型频域资源包括第一初始上行带宽部分BWP，所述第二类型频域资源包括第二初始上行BWP。
可选的，所述第一类型频域资源用于所述第一类型终端设备和所述第二类型终端设备与所述网络设备通信；所述收发模块602，还用于接收来自网络设备的指示信息，所述指示信息用于指示所述至少两个频域资源中的一个频域资源；处理模块601，具体用于根据所述配置信息以及所述指示信息，确定所述至少两个频域资源中的一个频域资源。
可选的，所述第一类型频域资源仅用于所述第一类型终端设备与所述网络设备通信；所述收发模块602，还用于接收来自网络设备的指示信息，所述指示信息用于指示所述至少两个第二类型频域资源中的一个频域资源；处理模块601，具体用于根据所述配置信息以及所述指示信息，确定所述至少两个第二类型频域资源中的一个频域资源。
可选的，所述指示信息包括在随机接入响应消息中，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在Msg2中，所述Msg2用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息包括在MsgB中，所述MsgB用于所述网络设备响应所述终端设备的随机接入请求。
可选的，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域。在一种可能的实施方式中，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域的至少一个高位比特中。
可选的，所述指示信息包括在下行控制信息DCI中，所述DCI用于调度随机接入响应消息，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。在一种可能的实施方式中，所述指示信息包括在所述DCI的预留比特中。
可选的，所述指示信息包括在所述随机接入响应消息和调度所述随机接入响应消息的DCI中，所述随机接入响应消息和所述DCI中的比特共同指示所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
可选的，所述第二类型频域资源的带宽小于或等于所述终端设备支持的最大带宽。
可选的，所述收发模块602，具体用于从系统信息或高层信令或物理层信令中，接收来自网络设备的配置信息。
本实施例提供的终端设备，可用于执行上述任一方法实施例中终端设备的技术方案，其实现原理和技术效果类似，此处不再赘述。
图12为本申请实施例提供的一种网络设备的硬件结构示意图。如图12所示，网络设备700包括：
处理器701、存储器702和通信接口703。其中，存储器702，用于存储计算机程序；处理器701，用于执行存储器702存储的计算机程序，以实现上述任一方法实施例中网络设备所执行的方法。通信接口703，用于与其他设备进行数据通信或者信号通信。
可选的，存储器702既可以是独立的，也可以跟处理器701集成在一起。当所述存储器702是独立于处理器701之外的器件时，所述网络设备700还可以包括：总线704，用于连接所述存储器702和处理器701。
在一种可能的实施方式中，图10中的处理模块501可以集成在处理器701中实现，收发模块502可以集成在通信接口703中实现。在一种可能的实施方式中，处理器701可用于实现上述方法实施例中网络设备的信号处理操作，通信接口703可用于实现上述方法实施例中网络设备的信号收发操作。
本实施例提供的网络设备，可用于执行上述任一方法实施例中网络设备所执行的方法，其实现原理和技术效果类似，此处不再赘述。
图13为本申请实施例提供的一种终端设备的硬件结构示意图。如图13所示，终端设备800包括：
处理器801、存储器802和通信接口803。其中，存储器802，用于存储计算机程序；处理器801，用于执行存储器802存储的计算机程序，以实现上述任一方法实施例中终端设备所执行的方法。通信接口803，用于与其他设备进行数据通信或者信号通信。
可选的，存储器802既可以是独立的，也可以跟处理器801集成在一起。当所述存储 器802是独立于处理器801之外的器件时，所述终端设备800还可以包括：总线804，用于连接所述存储器802和处理器801。
在一种可能的实施方式中，图11中的处理模块602可以集成在处理器801中实现，收发模块601可以集成在通信接口803中实现。在一种可能的实施方式中，处理器801可用于实现上述方法实施例中终端设备的信号处理操作，通信接口803可用于实现上述方法实施例中终端设备的信号收发操作。
本实施例的终端设备，可用于执行上述任一方法实施例中终端设备所执行的方法，其实现原理和技术效果类似，此处不再赘述。
本申请还提供一种可读存储介质，可读存储介质中存储有执行指令，当网络设备的至少一个处理器执行该执行指令时，网络设备执行上述任一方法实施例中网络设备的技术方案。
本申请还提供一种可读存储介质，可读存储介质中存储有执行指令，当终端设备的至少一个处理器执行该执行指令时，终端设备执行上述任一方法实施例中终端设备的技术方案。
本申请还提供一种计算机程序产品，包括执行指令，该执行指令存储在可读存储介质中。网络设备的至少一个处理器可以从可读存储介质读取该执行指令，至少一个处理器执行该执行指令使得网络设备实施上述任一方法实施例中网络设备的技术方案。
本申请还提供一种计算机程序产品，包括执行指令，该执行指令存储在可读存储介质中。终端设备的至少一个处理器可以从可读存储介质读取该执行指令，至少一个处理器执行该执行指令使得终端设备实施上述任一方法实施例中终端设备的技术方案。
本申请还提供了一种芯片，包括：处理器与接口，该处理器能执行上述任一方法实施例中网络设备的技术方案。可选的，该芯片还包括存储器，存储器中存储有计算机程序，处理器用于执行存储器存储的计算机程序，实现上述任一方法实施例中网络设备的技术方案。
本申请实施例还提供了一种芯片，包括：处理器与接口，该处理器能执行上述任一方法实施例中终端设备的技术方案。可选的，该芯片还包括存储器，存储器中存储有计算机程序，处理器用于执行存储器存储的计算机程序，实现上述任一方法实施例中终端设备的技术方案。
本申请实施例还提供一种通信系统，包括：至少一个网络设备以及终端设备，其中，网络设备可用于执行上述任一方法实施例中网络设备的技术方案，终端设备可用于执行上述任一方法实施例中终端设备的技术方案。
需要说明的是，应理解以上网络设备或终端设备的各个模块的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且这些模块可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分模块通过处理元件调用软件的形式实现，部分模块通过硬件的形式实现。例如，处理模块可以为单独设立的处理元件，也可以集成在上述装置的某一个芯片中实现，此外，也可以以程序代码的形式存储于上述装置的存储器中，由上述装置的某一个处理元件调用并执行以上确定模块的功能。其它模块的实现与之类似。此外这些模块全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件可以是一种集成电路，具有信号的处理 能力。在实现过程中，上述方法的各步骤或以上各个模块可以通过处理器元件中的硬件的集成逻辑电路或者软件形式的指令完成。
例如，以上这些模块可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(application specific integrated circuit，ASIC)，或，一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)等。再如，当以上某个模块通过处理元件调度程序代码的形式实现时，该处理元件可以是通用处理器，例如中央处理器(central processing unit，CPU)或其它可以调用程序代码的处理器。再如，这些模块可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘solid state disk(SSD))等。

Claims (30)

  1. 一种频域资源的确定方法，其特征在于，包括：
    网络设备向终端设备发送配置信息，所述配置信息包括至少两个频域资源的配置信息，所述至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源；
    所述第一类型频域资源用于第一类型终端设备和/或第二类型终端设备与所述网络设备通信；
    所述第二类型频域资源用于所述第二类型终端设备与所述网络设备通信；
    所述网络设备使用所述至少两个频域资源中的一个频域资源与所述终端设备通信。
  2. 根据权利要求1所述的方法，其特征在于，第一类型频域资源包括第一初始上行带宽部分BWP，第二类型频域资源包括第二初始上行BWP。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一类型频域资源用于所述第一类型终端设备和所述第二类型终端设备与所述网络设备通信；所述方法还包括：
    所述网络设备向所述终端设备发送指示信息，所述指示信息用于指示所述至少两个频域资源中的一个频域资源。
  4. 根据权利要求1或2所述的方法，其特征在于，所述第一类型频域资源仅用于所述第一类型终端设备与所述网络设备通信，所述方法还包括：
    所述网络设备向所述终端设备发送指示信息，所述指示信息用于指示所述至少两个频域资源中的一个第二类型频域资源。
  5. 根据权利要求3或4所述的方法，其特征在于，所述指示信息包括在随机接入响应消息中，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。
  6. 根据权利要求5所述的方法，其特征在于，所述指示信息包括在Msg2中，所述Msg2用于所述网络设备响应所述终端设备的随机接入请求；或者
    所述指示信息包括在MsgB中，所述MsgB用于所述网络设备响应所述终端设备的随机接入请求。
  7. 根据权利要求5所述的方法，其特征在于，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域。
  8. 根据权利要求7所述的方法，其特征在于，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域的至少一个高位比特中。
  9. 根据权利要求3或4所述的方法，其特征在于，所述指示信息包括在下行控制信息DCI中，所述DCI用于调度随机接入响应消息，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。
  10. 根据权利要求9所述的方法，其特征在于，所述指示信息包括在所述DCI的预留比特中。
  11. 根据权利要求3或4所述的方法，其特征在于，所述指示信息包括在所述随机接入响应消息和调度所述随机接入响应消息的DCI中，所述随机接入响应消息和所述DCI中的比特共同指示所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
  12. 根据权利要求1-11中任一项所述的方法，其特征在于，所述第二类型频域资源的 带宽小于或等于所述终端设备支持的最大带宽。
  13. 一种频域资源的确定方法，其特征在于，包括：
    终端设备接收来自网络设备的配置信息，所述配置信息包括至少两个频域资源的配置信息，所述至少两个频域资源包括至少一个第一类型频域资源以及至少一个第二类型频域资源；
    所述第一类型频域资源用于第一类型终端设备和/第二类型终端设备与所述网络设备通信；
    所述第二类型频域资源用于所述第二类型终端设备与所述网络设备通信；
    所述终端设备根据所述配置信息确定所述至少两个频域资源中的一个频域资源；
    所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
  14. 根据权利要求13所述的方法，其特征在于，所述第一类型频域资源包括第一初始上行带宽部分BWP，所述第二类型频域资源包括第二初始上行BWP。
  15. 根据权利要求13或14所述的方法，其特征在于，所述第一类型频域资源用于所述第一类型终端设备和所述第二类型终端设备与所述网络设备通信；所述方法还包括：
    所述终端设备接收来自网络设备的指示信息，所述指示信息用于指示所述至少两个频域资源中的一个频域资源；
    所述终端设备根据所述配置信息以及所述指示信息，确定所述至少两个频域资源中的一个频域资源。
  16. 根据权利要求13或14所述的方法，其特征在于，所述第一类型频域资源仅用于所述第一类型终端设备与所述网络设备通信，所述方法还包括：
    所述终端设备接收来自网络设备的指示信息，所述指示信息用于指示所述至少两个第二类型频域资源中的一个频域资源；
    所述终端设备根据所述配置信息以及所述指示信息，确定所述至少两个第二类型频域资源中的一个频域资源。
  17. 根据权利要求15或16所述的方法，其特征在于，所述指示信息包括在随机接入响应消息中，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。
  18. 根据权利要求17所述的方法，其特征在于，所述指示信息包括在Msg2中，所述Msg2用于所述网络设备响应所述终端设备的随机接入请求；或者
    所述指示信息包括在MsgB中，所述MsgB用于所述网络设备响应所述终端设备的随机接入请求。
  19. 根据权利要求17所述的方法，其特征在于，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域。
  20. 根据权利要求19所述的方法，其特征在于，所述指示信息位于所述随机接入响应消息中的上行授权中的物理上行共享信道PUSCH频域资源分配指示域的至少一个高位比特中。
  21. 根据权利要求15或16所述的方法，其特征在于，所述指示信息包括在下行控制信息DCI中，所述DCI用于调度随机接入响应消息，所述随机接入响应消息用于所述网络设备响应所述终端设备的随机接入请求。
  22. 根据权利要求21所述的方法，其特征在于，所述指示信息包括在所述DCI的预留比特中。
  23. 根据权利要求15或16所述的方法，其特征在于，所述指示信息包括在所述随机接入响应消息和调度所述随机接入响应消息的DCI中，所述随机接入响应消息和所述DCI中的比特共同指示所述终端设备使用所述至少两个频域资源中的一个频域资源与所述网络设备进行通信。
  24. 根据权利要求13-23中任一项所述的方法，其特征在于，所述第二类型频域资源的带宽小于或等于所述终端设备支持的最大带宽。
  25. 一种网络设备，其特征在于，包括：
    存储器和处理器；
    所述存储器用于存储程序指令；
    所述处理器用于调用所述存储器中存储的程序指令以实现权利要求1-12中任一项所述的方法。
  26. 一种终端设备，其特征在于，包括：
    存储器和处理器；
    所述存储器用于存储程序指令；
    所述处理器用于调用所述存储器中存储的程序指令以实现权利要求13-24中任一项所述的方法。
  27. 一种可读存储介质，其特征在于，所述可读存储介质中存储有执行指令，当网络设备的至少一个处理器执行该执行指令时，所述网络设备执行权利要求1-12中任一项所述的方法。
  28. 一种可读存储介质，其特征在于，所述可读存储介质中存储有执行指令，当终端设备的至少一个处理器执行该执行指令时，所述终端设备执行权利要求13-24中任一项所述的方法。
  29. 一种芯片，其特征在于，包括：处理器和接口，所述处理器用于从存储器中调用并运行所述存储器中存储的计算机程序，执行权利要求1-12中任一项所述的方法。
  30. 一种芯片，其特征在于，包括：处理器和接口，所述处理器用于从存储器中调用并运行所述存储器中存储的计算机程序，执行权利要求13-24中任一项所述的方法。
PCT/CN2021/109897 2020-08-07 2021-07-30 频域资源的确定方法、设备及存储介质 Ceased WO2022028340A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
JP2023508527A JP7551899B2 (ja) 2020-08-07 2021-07-30 周波数領域リソース決定方法、デバイス、及び記憶媒体
EP21852128.4A EP4192164B1 (en) 2020-08-07 2021-07-30 Frequency domain resource determining method, device, and storage medium
KR1020237007932A KR20230048383A (ko) 2020-08-07 2021-07-30 주파수 영역 리소스 결정 방법, 장치 및 저장 매체
ES21852128T ES3052424T3 (en) 2020-08-07 2021-07-30 Frequency domain resource determining method, device, and storage medium
EP25200173.0A EP4679928A3 (en) 2020-08-07 2021-07-30 Frequency domain resource determining method, device, and storage medium
BR112023002181-2A BR112023002181B1 (pt) 2020-08-07 2021-07-30 Método de determinação de recurso de domínio de frequência, aparelho de comunicação, e mídia de armazenamento
JP2024152711A JP7798984B2 (ja) 2020-08-07 2024-09-04 周波数領域リソース決定方法、デバイス、及び記憶媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010791729.0 2020-08-07
CN202010791729.0A CN114071750B (zh) 2020-08-07 2020-08-07 频域资源的确定方法、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2022028340A1 true WO2022028340A1 (zh) 2022-02-10

Family

ID=80116997

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/109897 Ceased WO2022028340A1 (zh) 2020-08-07 2021-07-30 频域资源的确定方法、设备及存储介质

Country Status (6)

Country Link
EP (2) EP4192164B1 (zh)
JP (2) JP7551899B2 (zh)
KR (1) KR20230048383A (zh)
CN (3) CN119300159A (zh)
ES (1) ES3052424T3 (zh)
WO (1) WO2022028340A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114731204A (zh) * 2022-02-14 2022-07-08 北京小米移动软件有限公司 确定信道的资源位置的方法、装置、通信设备及存储介质
CN115997461A (zh) * 2022-11-11 2023-04-21 北京小米移动软件有限公司 一种处理时延的确定方法、装置、设备及存储介质
CN116349367A (zh) * 2023-02-08 2023-06-27 北京小米移动软件有限公司 确定随机接入的资源的方法、装置、通信设备及存储介质
CN117158045A (zh) * 2022-02-16 2023-12-01 北京小米移动软件有限公司 一种小区接入控制方法、装置及存储介质
CN117242867A (zh) * 2022-04-14 2023-12-15 北京小米移动软件有限公司 资源处理方法及装置、通信设备及存储介质
WO2024037569A1 (zh) * 2022-08-19 2024-02-22 中国电信股份有限公司 下行资源复用增强方法、系统及相关设备
JP2025506210A (ja) * 2022-02-18 2025-03-07 クアルコム，インコーポレイテッド 動的リソース割り当てのための技法
EP4561184A4 (en) * 2022-07-19 2025-09-10 Beijing Xiaomi Mobile Software Co Ltd INFORMATION TRANSMISSION APPARATUS AND METHOD, COMMUNICATION DEVICE AND STORAGE MEDIUM

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4247075A4 (en) * 2020-12-18 2024-01-10 Guangdong Oppo Mobile Telecommunications Corp., Ltd. RESOURCE DETERMINATION METHOD AS WELL AS TERMINAL DEVICE AND NETWORK DEVICE
CN116801393A (zh) * 2022-03-15 2023-09-22 展讯半导体(南京)有限公司 数据传输方法及装置、计算机可读存储介质
CN116939839A (zh) * 2022-04-02 2023-10-24 大唐移动通信设备有限公司 传输处理方法、网络设备、终端、装置及存储介质
WO2023211239A1 (ko) * 2022-04-28 2023-11-02 엘지전자 주식회사 무선 통신 시스템에서 상향링크 또는 하향링크 송수신을 수행하는 방법 및 장치
WO2023231037A1 (zh) * 2022-06-02 2023-12-07 北京小米移动软件有限公司 一种数据链路层l2的缓冲器大小的确定方法及其装置
CN117956489A (zh) * 2022-10-27 2024-04-30 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN118102485A (zh) * 2022-11-25 2024-05-28 展讯通信（上海）有限公司 随机接入方法及装置、存储介质、终端设备、网络设备
CN115866782B (zh) * 2022-12-07 2023-09-08 上海山源电子科技股份有限公司 5g资源位置的确定方法及装置
CN120530663A (zh) * 2023-01-18 2025-08-22 Oppo广东移动通信有限公司 一种通信方法及装置、终端设备、网络设备
EP4669009A4 (en) * 2023-02-16 2026-03-25 Beijing Xiaomi Mobile Software Co Ltd METHOD AND APPARATUS FOR CONFIGURING RANDOM ACCESS RESOURCES, DEVICE AND STORAGE MECHANISM
CN119450737A (zh) * 2023-08-04 2025-02-14 大唐移动通信设备有限公司 频域资源确定方法、频域资源配置方法和通信设备
CN117882469A (zh) * 2023-11-28 2024-04-12 北京小米移动软件有限公司 通信方法、终端、网络设备、通信系统和存储介质
WO2026060656A1 (zh) * 2024-09-20 2026-03-26 北京小米移动软件有限公司 频域资源确定方法、装置、终端、网络设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014023026A1 (zh) * 2012-08-10 2014-02-13 华为技术有限公司 随机接入方法、基站及终端
CN109076617A (zh) * 2018-07-25 2018-12-21 北京小米移动软件有限公司 Mtc系统的随机接入方法、装置及存储介质
WO2020149978A1 (en) * 2019-01-16 2020-07-23 Qualcomm Incorporated Initial control resource set for ues having different bandwidth capabilities
WO2020156559A1 (zh) * 2019-02-03 2020-08-06 华为技术有限公司 一种数据传输方法、网络设备和终端设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10075979B2 (en) * 2012-06-27 2018-09-11 Lg Electronics Inc. Method and apparatus for performing random access procedure in wireless communication system
CN106851744B (zh) * 2015-12-03 2023-04-28 华为技术有限公司 无线通信的方法和装置
CN108811109B (zh) * 2017-05-04 2021-06-04 华为技术有限公司 资源映射方法、网络设备和终端设备
WO2019041261A1 (zh) * 2017-08-31 2019-03-07 华为技术有限公司 一种通信方法及设备
CN115428550B (zh) 2020-02-13 2025-07-15 日本电气株式会社 Ran节点、无线电终端及其方法
EP4135457A4 (en) 2020-04-08 2023-12-06 Beijing Xiaomi Mobile Software Co., Ltd. CONFIGURATION INFORMATION TRANSMISSION METHOD AND APPARATUS, COMMUNICATION DEVICE, AND STORAGE MEDIUM

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014023026A1 (zh) * 2012-08-10 2014-02-13 华为技术有限公司 随机接入方法、基站及终端
CN109076617A (zh) * 2018-07-25 2018-12-21 北京小米移动软件有限公司 Mtc系统的随机接入方法、装置及存储介质
WO2020149978A1 (en) * 2019-01-16 2020-07-23 Qualcomm Incorporated Initial control resource set for ues having different bandwidth capabilities
WO2020156559A1 (zh) * 2019-02-03 2020-08-06 华为技术有限公司 一种数据传输方法、网络设备和终端设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4192164A4

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114731204A (zh) * 2022-02-14 2022-07-08 北京小米移动软件有限公司 确定信道的资源位置的方法、装置、通信设备及存储介质
WO2023151088A1 (zh) * 2022-02-14 2023-08-17 北京小米移动软件有限公司 确定信道的资源位置的方法、装置、通信设备及存储介质
CN114731204B (zh) * 2022-02-14 2024-08-02 北京小米移动软件有限公司 确定信道的资源位置的方法、装置、通信设备及存储介质
CN117158045A (zh) * 2022-02-16 2023-12-01 北京小米移动软件有限公司 一种小区接入控制方法、装置及存储介质
JP2025506210A (ja) * 2022-02-18 2025-03-07 クアルコム，インコーポレイテッド 動的リソース割り当てのための技法
CN117242867A (zh) * 2022-04-14 2023-12-15 北京小米移动软件有限公司 资源处理方法及装置、通信设备及存储介质
EP4561184A4 (en) * 2022-07-19 2025-09-10 Beijing Xiaomi Mobile Software Co Ltd INFORMATION TRANSMISSION APPARATUS AND METHOD, COMMUNICATION DEVICE AND STORAGE MEDIUM
WO2024037569A1 (zh) * 2022-08-19 2024-02-22 中国电信股份有限公司 下行资源复用增强方法、系统及相关设备
CN115997461A (zh) * 2022-11-11 2023-04-21 北京小米移动软件有限公司 一种处理时延的确定方法、装置、设备及存储介质
WO2024098430A1 (zh) * 2022-11-11 2024-05-16 北京小米移动软件有限公司 一种处理时延的确定方法、装置、设备及存储介质
CN116349367A (zh) * 2023-02-08 2023-06-27 北京小米移动软件有限公司 确定随机接入的资源的方法、装置、通信设备及存储介质
CN116349367B (zh) * 2023-02-08 2026-04-07 北京小米移动软件有限公司 确定随机接入的资源的方法、装置、通信设备及存储介质

Also Published As

Publication number Publication date
JP2023537067A (ja) 2023-08-30
CN114071750A (zh) 2022-02-18
JP7551899B2 (ja) 2024-09-17
CN114071750B (zh) 2024-09-06
EP4679928A3 (en) 2026-02-18
CN119300159A (zh) 2025-01-10
ES3052424T3 (en) 2026-01-07
CN119300160A (zh) 2025-01-10
KR20230048383A (ko) 2023-04-11
EP4679928A2 (en) 2026-01-14
JP7798984B2 (ja) 2026-01-14
EP4192164A1 (en) 2023-06-07
EP4192164A4 (en) 2023-12-27
BR112023002181A2 (pt) 2023-03-14
EP4192164B1 (en) 2025-10-08
EP4192164C0 (en) 2025-10-08
JP2025000640A (ja) 2025-01-07

Similar Documents

Publication Publication Date Title
JP7798984B2 (ja) 周波数領域リソース決定方法、デバイス、及び記憶媒体
CN101969697B (zh) 用户设备上行随机接入基站的方法及系统、基站和用户设备
CN110474735B (zh) 通信方法和通信装置
CN110891315B (zh) 通信方法、装置及计算机存储介质
CN108964852B (zh) 频域资源的处理方法、装置及系统
WO2022028295A1 (zh) 一种通信方法及装置
US20230189234A1 (en) Frequency Domain Resource Determining Method, Device, and Storage Medium
CN115211209B (zh) 在下一代移动通信系统中有效传输小尺寸数据的方法和装置
CN115866771B (zh) 载波调度的方法及装置
CN111436085A (zh) 通信方法及装置
CN108809579B (zh) 资源配置方法、装置和系统
WO2023207837A1 (zh) 一种通信方法及装置
WO2023279969A1 (zh) 一种数据传输的方法及通信装置
WO2021218682A1 (zh) 通信方法、装置及系统
WO2022077470A1 (zh) 数据信道的传输方法
WO2026073441A1 (en) Collision of ue-initiated transmission and other uplink (ul) transmission (s) in a wireless communication system
CN112039641A (zh) 一种通信方法及装置
RU2801324C2 (ru) Способ произвольного доступа и устройство
BR112023002181B1 (pt) Método de determinação de recurso de domínio de frequência, aparelho de comunicação, e mídia de armazenamento
WO2024208007A1 (zh) 一种通信方法和通信装置
CN121772026A (zh) 随机接入方法及通信装置
WO2025092495A1 (zh) 通信方法及相关装置
WO2025139870A1 (zh) 一种通信方法及装置
JP2026512044A (ja) アクセス方法および装置
WO2026040734A1 (zh) 一种信道标识的复用方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21852128

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023508527

Country of ref document: JP

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112023002181

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20237007932

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112023002181

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20230206

ENP Entry into the national phase

Ref document number: 2021852128

Country of ref document: EP

Effective date: 20230227

WWG Wipo information: grant in national office

Ref document number: 202327008465

Country of ref document: IN

WWG Wipo information: grant in national office

Ref document number: 2021852128

Country of ref document: EP