WO2022126637A1 - 资源确定方法、终端设备和网络设备 - Google Patents

资源确定方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2022126637A1
WO2022126637A1 PCT/CN2020/137721 CN2020137721W WO2022126637A1 WO 2022126637 A1 WO2022126637 A1 WO 2022126637A1 CN 2020137721 W CN2020137721 W CN 2020137721W WO 2022126637 A1 WO2022126637 A1 WO 2022126637A1
Authority
WO
WIPO (PCT)
Prior art keywords
bandwidth
terminal device
information
random access
frequency domain
Prior art date
Application number
PCT/CN2020/137721
Other languages
English (en)
French (fr)
Inventor
贺传峰
徐伟杰
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2020/137721 priority Critical patent/WO2022126637A1/zh
Priority to CN202080105343.8A priority patent/CN116261889A/zh
Priority to EP20965651.1A priority patent/EP4247075A4/en
Publication of WO2022126637A1 publication Critical patent/WO2022126637A1/zh
Priority to US18/335,967 priority patent/US20230328707A1/en

Links

Images

Classifications

    • 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/0457—Variable allocation of band or rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • 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/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals

Definitions

  • the embodiments of the present application relate to the field of communications, and more particularly, to a resource determination method, a terminal device, and a network device.
  • Reduced Capbility (RedCap) terminals are introduced for scenarios with lower performance requirements such as latency, reliability, bandwidth, coverage, and throughput.
  • RedCap terminals how to determine the frequency domain resources for transmitting information in the random access process is an urgent problem to be solved.
  • the embodiments of the present application provide a resource determination method, a terminal device, and a network device.
  • the terminal device can determine the frequency domain resource for information transmission in the random access process according to the bandwidth capability it supports and the bandwidth information obtained from the system message, It is ensured that the information in the random access process can be sent smoothly, so as to complete the random access process.
  • a resource determination method comprising:
  • the terminal device determines the frequency domain resource for the first information transmission in the random access process according to the bandwidth capability it supports and the bandwidth information obtained from the system message.
  • a resource determination method comprising:
  • the network device determines, according to the bandwidth capability supported by the terminal device and the bandwidth information carried in the system message, the frequency domain resource for first information transmission in the random access process.
  • a terminal device for executing the method in the above-mentioned first aspect.
  • the terminal device includes functional modules for executing the method in the first aspect.
  • a network device for executing the method in the second aspect.
  • the network device includes functional modules for executing the method in the second aspect above.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect.
  • an apparatus for implementing the method in any one of the above-mentioned first to second aspects.
  • the apparatus includes: a processor for invoking and running a computer program from a memory, so that a device on which the apparatus is installed executes the method in any one of the first to second aspects above.
  • a computer-readable storage medium for storing a computer program, the computer program causing a computer to execute the method in any one of the first to second aspects above.
  • a computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method in any one of the first to second aspects above.
  • a computer program which, when run on a computer, causes the computer to perform the method of any one of the above-mentioned first to second aspects.
  • the terminal device can determine the frequency domain resource for the first information transmission in the random access process according to the bandwidth capability it supports and the bandwidth information obtained from the system message, so as to ensure the first information transmission in the random access process.
  • the frequency domain resources for information transmission are within the bandwidth capability range supported by the terminal device, so that the terminal device can correctly send or receive the first information in the random access process, and complete the random access process.
  • the network device can determine the frequency domain resource for the first information transmission in the random access process according to the bandwidth capability supported by the terminal device and the bandwidth information carried in the system message, so as to ensure the first information transmission in the random access process.
  • the frequency domain resources for information transmission are within the bandwidth capability range supported by the terminal device, so that the network device can correctly send or receive the first information in the random access process and complete the random access process.
  • FIG. 1 is a schematic diagram of a communication system architecture to which an embodiment of the present application is applied.
  • FIG. 2 is a schematic flowchart of a four-step random access procedure provided by the present application.
  • FIG. 3 is a schematic flowchart of a two-step random access procedure provided by the present application.
  • FIG. 4 is a schematic flowchart of a method for determining a resource according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a first bandwidth and control resource set 0 provided according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another first bandwidth and control resource set 0 provided according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a second bandwidth and an initial downlink BWP provided according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another second bandwidth and an initial downlink BWP provided according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a third bandwidth and an initial uplink BWP provided according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another third bandwidth and initial uplink BWP provided according to an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another resource determination method provided according to an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.
  • FIG. 13 is a schematic block diagram of a network device provided according to an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
  • Fig. 15 is a schematic block diagram of an apparatus provided according to an embodiment of the present application.
  • FIG. 16 is a schematic block diagram of a communication system provided according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • CDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • NTN Non-Terrestrial Networks
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • Wireless Fidelity Wireless Fidelity
  • WiFi fifth-generation communication
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA standalone
  • the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.
  • the embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • user equipment User Equipment, UE
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device may be a station (STATION, ST) in the WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
  • PLMN Public Land Mobile Network
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • a mobile phone Mobile Phone
  • a tablet computer Pad
  • a computer with a wireless transceiver function a virtual reality (Virtual Reality, VR) terminal device
  • augmented reality (Augmented Reality, AR) terminal Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network device may be a satellite or a balloon station.
  • the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) ) satellite etc.
  • the network device may also be a base station set in a location such as land or water.
  • a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device (
  • the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell).
  • Pico cell Femto cell (Femto cell), etc.
  • These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal).
  • the network device 110 may provide communication coverage for a particular geographic area, and may communicate with terminal devices located within the coverage area.
  • FIG. 1 exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. This application The embodiment does not limit this.
  • the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here.
  • the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobility management entity, etc., which are not limited in this embodiment of the present application.
  • the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship.
  • a indicates B it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • corresponding may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.
  • predefinition may be implemented by pre-saving corresponding codes, forms, or other means that can be used to indicate relevant information in devices (for example, including terminal devices and network devices).
  • the implementation method is not limited.
  • predefined may refer to the definition in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, for example, may include the LTE protocol, the NR protocol, and related protocols applied in future communication systems, which are not limited in this application.
  • the random access process adopts a four-step random access process similar to LTE, as shown in Figure 2:
  • the UE sends a physical random access process channel (Physical Random Access Channel, PRACH) to the base station, and the PRACH includes a random access preamble (preamble), that is, message 1 (Message 1, Msg 1);
  • PRACH Physical Random Access Channel
  • the base station sends a random access response (RAR), that is, message 2 (message 2, Msg 2), to the UE after detecting that the UE sends a random access preamble to inform the UE that it is sending message 3 (message 2).
  • RAR random access response
  • Msg 2 message 2
  • Msg 2 message 2
  • RNTI Radio Network Temporary Identity
  • the UE after the UE receives the RAR, it sends a Msg 3 message on the PUSCH resource specified by the RAR, which carries a UE-specific temporary identification information;
  • the base station sends a message 4 (message 4, Msg 4) message to the UE, including a contention resolution message, and allocates uplink transmission resources for the UE at the same time.
  • Msg 4 messages 4, Msg 4 sent by the base station
  • the UE will detect whether the UE-specific temporary identifier sent by the UE in Msg 3 is included in the contention resolution message sent by the base station.
  • the random access procedure needs to be initiated from the first step again.
  • the delay overhead of the four-step random access process is relatively large, which is not suitable for low-latency and high-reliability scenarios in 5G.
  • a two-step random access process was introduced in Release 16 (release16, R16), namely Type-2 random access process.
  • the access delay can be reduced.
  • the four-step random access procedure is called a Type-1 (Type-1) random access procedure.
  • the two-step random access process is shown in Figure 3 below. In the two-step random access process, simply speaking, it is equivalent to combining Msg 1 and Msg 3 of the four-step random access process into the two-step random access process.
  • S21 the UE sends message A (message A, Msg A), combines Msg 2 and Msg 4 in the four-step random access process into S22 in the two-step random access process, and the base station responds with message B (message B, Msg B) .
  • Msg A includes the preamble and PUSCH parts
  • Msg B includes the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH).
  • PDCH Physical Downlink Control Channel
  • PDSCH Physical Downlink Shared Channel
  • the UE needs to send preamble and PUSCH.
  • the random access process opportunity (Random Access Channel Occasion, RO) where the Preamble is located is the same as the four-step random access process. Through network configuration, its RO can be the same as the four-step random access process. Process RO sharing can also be configured individually.
  • the time-frequency resource where the PUSCH is located is called a PUSCH occasion (PUSCH occasion, PO).
  • One PO may include multiple PUSCH resource units (PUSCH resource units, PRUs), one PRU includes PUSCH resources + DMRS, and a demodulation reference signal (Demodulation Reference Signal, DMRS) includes DMRS ports and DMRS sequences.
  • PO is also configured through the network, and its period is the same as that of RO, and is related.
  • the NR system is mainly designed to support Enhanced Mobile Broadband (eMBB) services. Its main technology is to meet the needs of high speed, high spectral efficiency and large bandwidth.
  • eMBB Enhanced Mobile Broadband
  • the capabilities of terminals supporting these services are reduced compared to those supporting eMBB, such as reduced supported bandwidth, relaxation of processing time, reduction of the number of antennas, relaxation of the maximum modulation order, and the like.
  • the NR system needs to be optimized for these services and corresponding low-capacity terminals, which may be referred to as RedCap terminals for short.
  • the initial access UE After receiving the system message, it initiates a random access procedure to establish a Radio Resource Control (RRC) connection with the network.
  • RRC Radio Resource Control
  • the network needs to identify the type of the UE and obtain UE-related capability information.
  • Msg 1 Indicate in the sending stage of Msg 1, for example, through the initial uplink bandwidth part (Band Width Part, BWP) where Msg 1 is transmitted, through independent PRACH resources, or by dividing into independent PRACH preamble sets;
  • BWP Band Width Part
  • Msg 4 Indicate after Msg 4 is transmitted, such as message 5 (message 5, Msg 5) or as a capability report of the UE;
  • the frequency point of 5G is divided into two parts: FR1 (f ⁇ 6GHz, low frequency) and FR2 (f>6GHz, high frequency, millimeter wave).
  • FR1 f ⁇ 6GHz, low frequency
  • FR2 f>6GHz, high frequency, millimeter wave
  • the bandwidths supported by the UE may be 5MHz, 10MHz, 15MHz, 20MHz, 25MHz, 30MHz, 40MHz, 50MHz, 60MHz, 80MHz and 100MHz.
  • the bandwidth supported by the UE can be 50MHz, 100MHz, 200MHz and 400MHz, etc.
  • the bandwidth of the UE needs to support 100MHz.
  • the bandwidth of the UE needs to support 400 MHz.
  • RedCap terminals one of the main features is the reduction in the supported bandwidth, which reduces power consumption and costs.
  • the existing NR system no special consideration is given to supporting a terminal with low bandwidth capability to access the network, which will cause such a terminal to be unable to access the network due to the small supported bandwidth.
  • the UE needs to obtain the control resource set (Control Resource Set) of type 0 (type0) PDCCH through the master information block (Master Information Block, MIB) information carried by the physical broadcast channel (Physical Broadcast Channel, PBCH), CORESET) #0 and search space (search space) #0 information, used to indicate the type0 PDCCH resource block (Resource block, RB) in the frequency domain and symbols in the time domain.
  • the CORESET#0 information indicates an index, and according to the index, the number of RBs and symbols of CORESET#0, and the RB offset (offset) compared to the synchronization signal block (Synchronization Signal Block, SSB) are obtained.
  • the bandwidth of CORESET#0 can be configured as 24, 48, and 96 RBs, corresponding to bandwidths of 5MHz, 10MHz, and 20MHz. Under the 30kHz subcarrier spacing, the maximum number of RBs configured by CORESET#0 is 48, so it will not exceed the 20MHz bandwidth.
  • the UE receives the scheduling information of the PDSCH carrying the system information block (System Information Block, SIB) through the type0 PDCCH, thereby receiving the SIB1 information.
  • SIB System Information Block
  • the RedCap terminal can support 20MHz bandwidth in the initial access phase, which is greater than or equal to the bandwidth of CORESET#0, so it can successfully receive type0 PDCCH.
  • the RedCap terminal can support 100MHz bandwidth in the initial access stage, which is also greater than or equal to the bandwidth of CORESET#0.
  • the UE can receive the scheduling information of the PDSCH carrying the SIB through the type0 PDCCH, thereby receiving the SIB1 information. From the SIB1 information, the UE can obtain the initial downlink BWP and initial uplink BWP configuration information. In the process of channel transmission and reception in the random access process of the UE, it can be performed on the initial downlink BWP and the initial uplink BWP. In the prior art, the configured bandwidth of the initial downlink BWP and the initial uplink BWP is allowed to exceed the bandwidth of CORESET#0.
  • the cell supports the access of RedCap terminals and continues to use the existing initial downlink BWP and initial uplink BWP configurations, its bandwidth configuration may exceed the bandwidth capability of the RedCap terminal, causing the RedCap terminal to fail to receive and transmit correctly during the initial access phase.
  • Channel information during random access procedure.
  • the present application proposes a resource determination scheme, which can determine the frequency domain resources for information transmission in the random access process according to the bandwidth capability supported by the terminal device and the bandwidth information obtained from the system message, so as to ensure random access.
  • the frequency domain resources of the information transmission in the process are within the bandwidth capability range supported by the terminal device, so that the information in the random access process can be correctly sent or received, and the random access process can be completed.
  • FIG. 4 is a schematic flowchart of a resource determination method 200 according to an embodiment of the present application. As shown in FIG. 4 , the method 200 may include at least part of the following contents:
  • the terminal device determines, according to the bandwidth capability it supports and the bandwidth information obtained in the system message, the frequency domain resource for the first information transmission in the random access process.
  • the terminal device may determine the frequency domain resource for the first information transmission in the random access process according to the bandwidth capability it supports and the bandwidth information obtained in the system message, so as to ensure the first information transmission in the random access process.
  • the frequency domain resources of the device are within the bandwidth capability range supported by the terminal device, so that the first information in the random access process can be correctly sent or received, and the random access process can be completed.
  • the terminal device is a reduced capability terminal (RedCap terminal).
  • the terminal device may also be other terminals with a specific bandwidth capability, which is not limited in this embodiment of the present application.
  • the system information may be SIB1 information.
  • the system information may also be other information, which is not limited in this embodiment of the present application.
  • the bandwidth information includes at least one of the following:
  • Control resource set 0 (CORESET#0), initial downlink BWP, and initial uplink BWP.
  • the bandwidth information includes control resource set 0 and/or initial downlink BWP, in this case, the first information is downlink information in the random access process.
  • the first information includes at least one of the following:
  • the second message (Msg 2) in the four-step random access process, the fourth message (Msg 4) in the four-step random access process, and the second message (Msg B) in the two-step random access process are identical to each other.
  • the terminal device after the terminal device sends Msg 1, it detects the random access radio network temporary identifier (Random Access Radio Network Temporary Identity, RA-RNTI) scrambled cyclic redundancy
  • the DCI format 1_0 of the Cyclical Redundancy Check (CRC) obtains the scheduling information of the PDSCH bearing the RAR.
  • the terminal device After sending Msg A, the terminal device obtains the scheduling information of the PDSCH carrying Msg B by detecting the DCI format 1_0 of the CRC scrambled by the Msg B-RNTI.
  • the scheduling information of the PDSCH includes frequency domain resource indication information.
  • the frequency domain resource is indicated within the bandwidth range of the configured CORESET#0. If CORESET#0 is not configured, it is indicated within the bandwidth range of the configured initial downlink BWP.
  • the bandwidth configuration of CORESET#0 or initial downlink BWP may exceed the bandwidth capability supported by the RedCap terminal. In this case, it is necessary to limit the frequency domain resource indication information to CORESET#0 or The frequency domain range indicated in the initial downlink BWP.
  • the foregoing S210 may specifically be:
  • the terminal device determines that the frequency domain range of the first information transmission is the first bandwidth in the bandwidths of the control resource set 0, and the third A bandwidth is less than or equal to the bandwidth capability supported by the terminal device.
  • the terminal device determines that the frequency domain bandwidth range corresponding to the frequency domain resource indication information is the first bandwidth determined by the above method.
  • the frequency domain resource indication information is as follows:
  • the first bandwidth is located at the center of the bandwidth of the control resource set 0.
  • the first bandwidth is located at the center of the bandwidth of the control resource set 0, and the first bandwidth Equal to half the bandwidth of the control resource set 0.
  • the first bandwidth is located at an edge position in the bandwidth of the control resource set 0, for example, as shown in FIG. 6 , the first bandwidth is located at an edge position in the bandwidth of the control resource set 0, and the first bandwidth is less than the Control half the bandwidth of resource set 0.
  • the center position may be that the center frequency of the first bandwidth is the same as the center frequency of the bandwidth of the control resource set 0 .
  • the edge position may be, for example, a bandwidth of the first bandwidth that is continuous from the first RB of the bandwidth of the control resource set 0 .
  • the first bandwidth is pre-configured or agreed in a protocol, or the first bandwidth is configured or indicated by a network device, or the first bandwidth is obtained from the system message (eg, SIB1 information).
  • the foregoing S210 may specifically be:
  • the terminal device determines that the frequency domain range of the first information transmission is the second bandwidth in the bandwidth of the initial downlink BWP, and the second bandwidth Less than or equal to the bandwidth capability supported by the end device.
  • the terminal device determines that the frequency domain bandwidth range corresponding to the frequency domain resource indication information is the second bandwidth determined by the above method.
  • the frequency domain resource indication information is as follows:
  • the second bandwidth is located at the center of the bandwidth of the initial downlink BWP.
  • the second bandwidth is located at the center of the bandwidth of the initial downlink BWP, and the second bandwidth is equal to the Half the bandwidth of the initial downlink BWP.
  • the second bandwidth is located at an edge position in the bandwidth of the initial downlink BWP.
  • the second bandwidth is located at an edge position in the bandwidth of the initial downlink BWP, and the second bandwidth is equal to the initial downlink BWP.
  • the center position may be that the center frequency of the second bandwidth is the same as the center frequency of the bandwidth of the initial downlink BWP.
  • the edge position may be, for example, a continuous bandwidth of the second bandwidth from the first RB of the bandwidth of the initial downlink BWP.
  • the second bandwidth is pre-configured or agreed in a protocol, or the second bandwidth is configured or indicated by a network device, or the second bandwidth is obtained from the system message (eg, SIB1 information).
  • the foregoing S210 may specifically be:
  • the terminal device determines that the frequency domain range of the first information transmission is the bandwidth of the control resource set 0; or,
  • the terminal device determines that the frequency domain range of the first information transmission is the bandwidth of the initial downlink BWP.
  • the bandwidth information includes the initial uplink BWP, and in this case, the first information is uplink information in the random access process.
  • the first information includes the third piece of information (Msg 3) in the four-step random access procedure.
  • the RedCap terminal detects the DCI format 1_0 of the CRC scrambled by the RA-RNTI, thereby receiving the RAR.
  • the RAR indicates the scheduling information of the PUSCH bearing Msg 3.
  • the scheduling information of the PUSCH includes frequency domain resource indication information. The frequency domain resources are indicated within the bandwidth range of the configured initial uplink BWP.
  • Msg 3 is retransmitted, the scheduling information of the PUSCH is indicated by the DCI format 0_0 of the CRC scrambled by the Temporary Cell RNTI (Temporary Cell RNTI, TC-RNTI).
  • the bandwidth configuration of the initial uplink BWP may exceed the bandwidth capability supported by the RedCap terminal.
  • the frequency domain range indicated by the frequency domain resource indication information in the initial uplink BWP needs to be limited.
  • the foregoing S210 may specifically be:
  • the terminal device determines that the frequency domain range of the first information transmission is the third bandwidth in the bandwidth of the initial uplink BWP, and the third bandwidth Less than or equal to the bandwidth capability supported by the end device.
  • the terminal device determines that the frequency domain bandwidth range corresponding to the frequency domain resource indication information is the third bandwidth determined by the above method.
  • the frequency domain resource indication information is as follows:
  • the foregoing S210 may specifically be:
  • the terminal device determines the frequency domain range of the first information transmission according to the activated uplink BWP and the third bandwidth in the bandwidth of the initial uplink BWP ;
  • the third bandwidth is less than or equal to the bandwidth capability supported by the terminal device.
  • the foregoing S210 may specifically be:
  • the activated uplink BWP and the third bandwidth have the same subcarrier spacing configuration and the same cyclic prefix (Cyclic prefix, CP) length, and the activated uplink BWP includes all resource blocks (Resource Blocks) of the third bandwidth , RB), or, the bandwidth of the activated uplink BWP and the third bandwidth are the same bandwidth, and the terminal device determines that the frequency domain range of the first information transmission is the third bandwidth; or
  • the terminal device determines that the frequency domain range of the first information transmission is the first one in the activated upstream BWP from the serial number W RBs starting from RB, where W is a positive integer, and W is equal to the number of RBs in the third bandwidth.
  • the terminal device when the terminal device is in the connected state and the uplink BWP is configured, in the random access process, in the frequency domain resource indication information of Msg 3, it is necessary to determine the Msg 3 according to the currently activated uplink BWP and the initial uplink BWP.
  • the range of frequency domain resource allocation because the supported bandwidth of the RedCap terminal in the connected state may be different from the initial access, or considering the limitation of the bandwidth capability of the RedCap terminal, the activated uplink BWP bandwidth is smaller than the initial uplink BWP bandwidth Case. Therefore, for the RedCap terminal, it can determine the frequency domain range of the first information transmission based on the relationship between the activated uplink BWP and the third bandwidth.
  • the third bandwidth is located at the center of the bandwidth of the initial uplink BWP.
  • the third bandwidth is located at the center of the bandwidth of the initial uplink BWP, and the The third bandwidth is equal to half of the bandwidth of the initial upstream BWP.
  • the third bandwidth is located at an edge position in the bandwidth of the initial uplink BWP.
  • the third bandwidth is located at the edge position in the bandwidth of the initial uplink BWP, and the third bandwidth is equal to the initial uplink BWP.
  • the center position may be that the center frequency of the third bandwidth is the same as the center frequency of the bandwidth of the initial uplink BWP.
  • the edge position may be, for example, a bandwidth of the third bandwidth that is continuous from the first RB of the bandwidth of the initial uplink BWP.
  • terminal equipment can use Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) waveforms for transmission. It is hoped that The allocation of frequency domain resources should be as continuous as possible. If the frequency domain resource of the Msg 3 transmission of the RedCap terminal is located in the central part of the bandwidth of the configured initial uplink BWP, when the Msg 3 transmission of the RedCap terminal and the Msg 3 transmission of the non-RedCap terminal are in the same time slot, this initial The bandwidth on both sides of the bandwidth of the upstream BWP cannot be well utilized by the Msg 3 transmission of the non-RedCap terminal. Therefore, preferably, the frequency domain resources of the Msg 3 transmission of the RedCap terminal are located at the edge of the configured initial upstream BWP bandwidth.
  • DFT-S-OFDM Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing
  • the third bandwidth is pre-configured or agreed in a protocol, or the third bandwidth is configured or indicated by a network device, or the third bandwidth is the system message (such as SIB1 information) obtained from.
  • example 1 and example 2 may be a case where it is assumed that the initial uplink BWP and the initial downlink BWP are shared by the RedCap terminal and the non-RedCap terminal.
  • the RedCap terminal can determine the transmission frequency domain resources of uplink information in the random access process based on its individually configured initial uplink BWP, or the RedCap terminal can determine the transmission of downlink information in the random access process based on its individually configured initial downlink BWP frequency domain resources.
  • the terminal device can determine the frequency domain resource for the first information transmission in the random access process according to the bandwidth capability it supports and the bandwidth information obtained in the system message, so as to ensure the first information transmission in the random access process.
  • the frequency domain resources for information transmission are within the bandwidth capability range supported by the terminal device, so that the terminal device can correctly send or receive the first information in the random access process, and complete the random access process.
  • terminal-side embodiments of the present application are described in detail above with reference to FIGS. 4 to 10 , and the network-side embodiments of the present application are described in detail below with reference to FIG. 11 . It should be understood that the network-side embodiments and the terminal-side embodiments correspond to each other. For similar descriptions, reference may be made to the terminal-side embodiments.
  • FIG. 11 is a schematic flowchart of a resource determination method 300 according to an embodiment of the present application. As shown in FIG. 11 , the method 300 may include at least part of the following contents:
  • the network device determines, according to the bandwidth capability supported by the terminal device and the bandwidth information carried in the system message, the frequency domain resource for first information transmission in the random access process.
  • the network device may determine the frequency domain resource for the first information transmission in the random access process according to the bandwidth capability supported by the terminal device and the bandwidth information obtained in the system message, so as to ensure the first information in the random access process.
  • the transmitted frequency domain resources are within the bandwidth capability range supported by the terminal device, so that the network device can correctly send or receive the first information in the random access process, and complete the random access process.
  • the terminal device is a reduced capability terminal (RedCap terminal).
  • the terminal device may also be other terminals with a specific bandwidth capability, which is not limited in this embodiment of the present application.
  • the system information may be SIB1 information.
  • the system information may also be other information, which is not limited in this embodiment of the present application.
  • the bandwidth information includes at least one of the following:
  • Control resource set 0 (CORESET#0), initial downlink BWP, and initial uplink BWP.
  • the bandwidth information includes control resource set 0 and/or initial downlink BWP, in this case, the first information is downlink information in the random access process.
  • the first information includes at least one of the following:
  • the second message (Msg 2) in the four-step random access process, the fourth message (Msg 4) in the four-step random access process, and the second message (Msg B) in the two-step random access process are identical to each other.
  • the above S310 may specifically be:
  • the network device determines that the frequency domain range of the first information transmission is the first bandwidth in the bandwidths of the control resource set 0, and the first bandwidth A bandwidth is less than or equal to the bandwidth capability supported by the terminal device.
  • the first bandwidth is located at a central position in the bandwidth of the control resource set 0, or the first bandwidth is located at an edge position in the bandwidth of the control resource set 0.
  • the first bandwidth is pre-configured or agreed in a protocol, or the first bandwidth is configured or indicated by a network device, or the first bandwidth is information carried in the system message (eg, SIB1 information).
  • the above S310 may specifically be:
  • the network device determines that the frequency domain range of the first information transmission is the second bandwidth in the bandwidth of the initial downlink BWP, and the second bandwidth Less than or equal to the bandwidth capability supported by the end device.
  • the second bandwidth is located at a central position in the bandwidth of the initial downlink BWP, or the second bandwidth is located at an edge position in the bandwidth of the initial downlink BWP.
  • the second bandwidth is pre-configured or agreed in a protocol, or the second bandwidth is configured or indicated by a network device, or the second bandwidth is information carried in the system message (eg, SIB1 information).
  • the above S310 may specifically be:
  • the network device determines that the frequency domain range of the first information transmission is the bandwidth of the control resource set 0; or,
  • the network device determines that the frequency domain range of the first information transmission is the bandwidth of the initial downlink BWP.
  • the bandwidth information includes the initial uplink BWP, and in this case, the first information is uplink information in the random access process.
  • the first information includes the third piece of information (Msg 3) in the four-step random access procedure.
  • the foregoing S310 may specifically be:
  • the network device determines that the frequency domain range of the first information transmission is the third bandwidth in the bandwidth of the initial uplink BWP, and the third bandwidth Less than or equal to the bandwidth capability supported by the end device.
  • the foregoing S310 may specifically be:
  • the network device determines the frequency domain range of the first information transmission according to the activated uplink BWP and the third bandwidth in the bandwidth of the initial uplink BWP ;
  • the third bandwidth is less than or equal to the bandwidth capability supported by the terminal device.
  • the foregoing S310 may specifically be:
  • the activated upstream BWP and the third bandwidth have the same subcarrier spacing configuration and the same CP length, and the activated upstream BWP includes all RBs of the third bandwidth, or the activated upstream BWP has the same bandwidth as The third bandwidth is the same bandwidth, and the network device determines that the frequency domain range of the first information transmission is the third bandwidth; or
  • the network device determines that the frequency domain range of the first information transmission is the first one in the activated upstream BWP from the serial number W RBs starting from RB, where W is a positive integer, and W is equal to the number of RBs in the third bandwidth.
  • the third bandwidth is located at a central position in the bandwidth of the initial uplink BWP, or the third bandwidth is located at an edge position in the bandwidth of the initial uplink BWP.
  • the third bandwidth is pre-configured or agreed in a protocol, or the third bandwidth is configured or indicated by a network device, or the third bandwidth is information carried in the system message (eg, SIB1 information).
  • example 3 and example 4 may be a case where it is assumed that the initial uplink BWP and the initial downlink BWP are shared by the RedCap terminal and the non-RedCap terminal.
  • the network device can determine the transmission frequency domain resources of uplink information in the random access process based on the RedCap terminal's independent configuration of the initial uplink BWP, or the network device can determine the downlink information in the random access process based on the RedCap terminal's independent configuration of the initial downlink BWP. transmission frequency domain resources.
  • the network device may determine the frequency domain resource for the first information transmission in the random access process according to the bandwidth capability supported by the terminal device and the bandwidth information carried in the system message, so as to ensure the first information transmission in the random access process.
  • the frequency domain resources for information transmission are within the bandwidth capability range supported by the terminal device, so that the network device can correctly send or receive the first information in the random access process and complete the random access process.
  • FIG. 12 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application.
  • the terminal device 400 includes:
  • the processing unit 410 determines, according to the bandwidth capability supported by the terminal device and the bandwidth information obtained from the system message, the frequency domain resource for transmitting the first information in the random access process.
  • the bandwidth information includes at least one of the following:
  • Control resource set 0, initial downlink bandwidth part BWP, and initial uplink BWP.
  • the bandwidth information includes control resource set 0 and/or initial downlink BWP, and the first information is downlink information in the random access process.
  • processing unit 410 is specifically configured to:
  • the bandwidth of the control resource set 0 is greater than the bandwidth capability supported by the terminal device, determine that the frequency domain range of the first information transmission is the first bandwidth among the bandwidths of the control resource set 0, and the first bandwidth is less than or equal to the bandwidth capability supported by the terminal device; or,
  • the bandwidth of the initial downlink BWP is greater than the bandwidth capability supported by the terminal device, determine that the frequency domain range of the first information transmission is the second bandwidth in the bandwidth of the initial downlink BWP, and the second bandwidth is less than or equal to Bandwidth capability supported by this end device.
  • the first bandwidth is located at a central position in the bandwidth of the control resource set 0, or the first bandwidth is located at an edge position in the bandwidth of the control resource set 0.
  • the second bandwidth is located at a central position in the bandwidth of the initial downlink BWP, or the second bandwidth is located at an edge position in the bandwidth of the initial downlink BWP.
  • the first bandwidth is pre-configured or agreed in a protocol, or the first bandwidth is configured or indicated by a network device, or the first bandwidth is obtained from the system message.
  • the second bandwidth is pre-configured or agreed in a protocol, or the second bandwidth is configured or indicated by a network device, or the second bandwidth is obtained from the system message.
  • processing unit 410 is specifically configured to:
  • the bandwidth of the control resource set 0 is less than or equal to the bandwidth capability supported by the terminal device, determine that the frequency domain range of the first information transmission is the bandwidth of the control resource set 0; or,
  • the bandwidth of the initial downlink BWP is less than or equal to the bandwidth capability supported by the terminal device, it is determined that the frequency domain range of the first information transmission is the bandwidth of the initial downlink BWP.
  • the first information includes at least one of the following:
  • the second message in the four-step random access process, the fourth message in the four-step random access process, and the second message in the two-step random access process are identical to each other.
  • the bandwidth information includes an initial uplink BWP, and the first information is uplink information in a random access process.
  • processing unit 410 is specifically configured to:
  • the bandwidth of the initial uplink BWP is greater than the bandwidth capability supported by the terminal device, determine that the frequency domain range of the first information transmission is the third bandwidth in the bandwidth of the initial uplink BWP, and the third bandwidth is less than or equal to Bandwidth capabilities supported by this end device.
  • processing unit 410 is specifically configured to:
  • the terminal device determine the frequency domain range of the first information transmission according to the activated uplink BWP and the third bandwidth in the bandwidth of the initial uplink BWP;
  • the third bandwidth is less than or equal to the bandwidth capability supported by the terminal device.
  • processing unit 410 is specifically configured to:
  • the activated uplink BWP and the third bandwidth have the same subcarrier spacing configuration and the same cyclic prefix CP length, and the activated uplink BWP includes all resource blocks RB of the third bandwidth, or, the activated uplink
  • the bandwidth of the BWP is the same as the third bandwidth, and the frequency domain range of the first information transmission is determined to be the third bandwidth; or
  • the frequency domain range of the first information transmission is the range starting from the first RB on the number in the activated uplink BWP W RBs, where W is a positive integer, and W is equal to the number of RBs in the third bandwidth.
  • the third bandwidth is located at a central position in the bandwidth of the initial uplink BWP, or the third bandwidth is located at an edge position in the bandwidth of the initial uplink BWP.
  • the third bandwidth is pre-configured or agreed in a protocol, or the third bandwidth is configured or indicated by a network device, or the third bandwidth is obtained from the system message.
  • the first information includes the third piece of information in the four-step random access procedure.
  • the terminal device is a reduced capability terminal.
  • the above-mentioned processing unit may be one or more processors.
  • terminal device 400 may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the terminal device 400 are respectively for realizing the method shown in FIG. 4 .
  • the corresponding process of the terminal device in 200 is not repeated here for brevity.
  • FIG. 13 shows a schematic block diagram of a network device 500 according to an embodiment of the present application.
  • the network device 500 includes:
  • the processing unit 510 determines, according to the bandwidth capability supported by the terminal device and the bandwidth information carried in the system message, the frequency domain resource for transmitting the first information in the random access process.
  • the bandwidth information includes at least one of the following:
  • Control resource set 0, initial downlink bandwidth part BWP, and initial uplink BWP.
  • the bandwidth information includes control resource set 0 and/or initial downlink BWP, and the first information is downlink information in the random access process.
  • processing unit 510 is specifically used for:
  • the bandwidth of the control resource set 0 is greater than the bandwidth capability supported by the terminal device, determine that the frequency domain range of the first information transmission is the first bandwidth among the bandwidths of the control resource set 0, and the first bandwidth is less than or equal to the bandwidth capability supported by the terminal device; or,
  • the bandwidth of the initial downlink BWP is greater than the bandwidth capability supported by the terminal device, determine that the frequency domain range of the first information transmission is the second bandwidth in the bandwidth of the initial downlink BWP, and the second bandwidth is less than or equal to Bandwidth capability supported by this end device.
  • the first bandwidth is located at a central position in the bandwidth of the control resource set 0, or the first bandwidth is located at an edge position in the bandwidth of the control resource set 0.
  • the second bandwidth is located at a central position in the bandwidth of the initial downlink BWP, or the second bandwidth is located at an edge position in the bandwidth of the initial downlink BWP.
  • the first bandwidth is pre-configured or agreed in a protocol, or the first bandwidth is configured or indicated by a network device, or the first bandwidth is information carried in the system message.
  • the second bandwidth is pre-configured or agreed in a protocol, or the second bandwidth is configured or indicated by a network device, or the second bandwidth is information carried in the system message.
  • processing unit 510 is specifically used for:
  • the bandwidth of the control resource set 0 is less than or equal to the bandwidth capability supported by the terminal device, determine that the frequency domain range of the first information transmission is the bandwidth of the control resource set 0; or,
  • the bandwidth of the initial downlink BWP is less than or equal to the bandwidth capability supported by the terminal device, it is determined that the frequency domain range of the first information transmission is the bandwidth of the initial downlink BWP.
  • the first information includes at least one of the following:
  • the second message in the four-step random access process, the fourth message in the four-step random access process, and the second message in the two-step random access process are identical to each other.
  • the bandwidth information includes an initial uplink BWP, and the first information is uplink information in a random access process.
  • processing unit 510 is specifically used for:
  • the bandwidth of the initial uplink BWP is greater than the bandwidth capability supported by the terminal device, determine that the frequency domain range of the first information transmission is the third bandwidth in the bandwidth of the initial uplink BWP, and the third bandwidth is less than or equal to Bandwidth capability supported by this end device.
  • processing unit 510 is specifically used for:
  • the terminal device determine the frequency domain range of the first information transmission according to the activated uplink BWP and the third bandwidth in the bandwidth of the initial uplink BWP;
  • the third bandwidth is less than or equal to the bandwidth capability supported by the terminal device.
  • processing unit 510 is specifically used for:
  • the activated uplink BWP and the third bandwidth have the same subcarrier spacing configuration and the same cyclic prefix CP length, and the activated uplink BWP includes all resource blocks RB of the third bandwidth, or, the activated uplink
  • the bandwidth of the BWP is the same as the third bandwidth, and the frequency domain range of the first information transmission is determined to be the third bandwidth; or
  • the frequency domain range of the first information transmission determines the frequency domain range of the first information transmission to be the range from the first RB on the number in the activated uplink BWP W RBs, where W is a positive integer, and W is equal to the number of RBs in the third bandwidth.
  • the third bandwidth is located at a central position in the bandwidth of the initial uplink BWP, or the third bandwidth is located at an edge position in the bandwidth of the initial uplink BWP.
  • the third bandwidth is pre-configured or agreed in a protocol, or the third bandwidth is configured or indicated by a network device, or the third bandwidth is information carried in the system message.
  • the first information includes the third piece of information in the four-step random access procedure.
  • the terminal device is a reduced capability terminal.
  • the above-mentioned processing unit may be one or more processors.
  • the network device 500 may correspond to the network device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the network device 500 are respectively for realizing the method shown in FIG. 11 .
  • the corresponding process of the network device in 300 is not repeated here for brevity.
  • FIG. 14 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application.
  • the communication device 600 shown in FIG. 14 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the communication device 600 may further include a memory 620 .
  • the processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application.
  • the memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive other Information or data sent by a device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of the antennas may be one or more.
  • the communication device 600 may specifically be the network device in this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 600 may specifically be a terminal device in this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the terminal device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • FIG. 15 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • the apparatus 700 shown in FIG. 15 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in this embodiment of the present application.
  • the apparatus 700 may further include a memory 720 .
  • the processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application.
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
  • the apparatus 700 may further include an input interface 730 .
  • the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
  • the apparatus 700 may further include an output interface 740 .
  • the processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • the apparatus can be applied to the network equipment in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application, which are not repeated here for brevity.
  • the apparatus may be applied to the terminal equipment in the embodiments of the present application, and the apparatus may implement the corresponding processes implemented by the terminal equipment in each method of the embodiments of the present application, which will not be repeated here for brevity.
  • the device mentioned in the embodiment of the present application may also be a chip.
  • it can be a system-on-chip, a system-on-a-chip, a system-on-a-chip, or a system-on-a-chip.
  • FIG. 16 is a schematic block diagram of a communication system 800 provided by an embodiment of the present application. As shown in FIG. 16 , the communication system 800 includes a terminal device 810 and a network device 820 .
  • the terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the terminal device in each method of the embodiments of the present application.
  • the computer program enables the computer to execute the corresponding processes implemented by the terminal device in each method of the embodiments of the present application.
  • Embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.
  • the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the terminal device in each method of the embodiments of the present application. Repeat.
  • the embodiments of the present application also provide a computer program.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • the computer program When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.
  • the computer program may be applied to the terminal device in the embodiments of the present application, and when the computer program runs on the computer, the computer executes the corresponding processes implemented by the terminal device in each method of the embodiments of the present application, for the sake of brevity. , and will not be repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种资源确定方法、终端设备和网络设备，终端设备可以根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中的信息传输的频域资源，确保随机接入过程中的信息可以顺利发送，从而完成随机接入过程。该资源确定方法包括：终端设备根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源。

Description

资源确定方法、终端设备和网络设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种资源确定方法、终端设备和网络设备。
背景技术
在一些通信场景中，引入了降低能力(Reduced Capbility，RedCap)终端，用于对时延、可靠性、带宽、覆盖、吞吐量等性能要求较低的场景。对于此类RedCap终端，如何确定其传输随机接入过程中的信息的频域资源，是一项急需解决的问题。
发明内容
本申请实施例提供了一种资源确定方法、终端设备和网络设备，终端设备可以根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中的信息传输的频域资源，确保随机接入过程中的信息可以顺利发送，从而完成随机接入过程。
第一方面，提供了一种资源确定方法，该方法包括：
终端设备根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源。
第二方面，提供了一种资源确定方法，该方法包括：
网络设备根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源。
第三方面，提供了一种终端设备，用于执行上述第一方面中的方法。
具体地，该终端设备包括用于执行上述第一方面中的方法的功能模块。
第四方面，提供了一种网络设备，用于执行上述第二方面中的方法。
具体地，该网络设备包括用于执行上述第二方面中的方法的功能模块。
第五方面，提供了一种终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面中的方法。
第六方面，提供了一种网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面中的方法。
第七方面，提供了一种装置，用于实现上述第一方面至第二方面中的任一方面中的方法。
具体地，该装置包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该装置的设备执行如上述第一方面至第二方面中的任一方面中的方法。
第八方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面至第二方面中的任一方面中的方法。
第九方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行上述第一方面至第二方面中的任一方面中的方法。
第十方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中的任一方面中的方法。
通过上述第一方面的技术方案，终端设备可以根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源，确保随机接入过程中第一信息传输的频域资源在终端设备支持的带宽能力范围内，从而，终端设备可以正确发送或接收随机接入过程中第一信息，并完成随机接入过程。
通过上述第二方面的技术方案，网络设备可以根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源，确保随机接入过程中第一信息传输的频域资源在终端设备支持的带宽能力范围内，从而，网络设备可以正确发送或接收随机接入过程中第一信息，并完成随机接入过程。
附图说明
图1是本申请实施例应用的一种通信系统架构的示意性图。
图2是本申请提供的四步随机接入过程的示意性流程图。
图3是本申请提供的两步随机接入过程的示意性流程图。
图4是根据本申请实施例提供的一种资源确定方法的示意性流程图。
图5是根据本申请实施例提供的一种第一带宽与控制资源集0的示意性图。
图6是根据本申请实施例提供的另一种第一带宽与控制资源集0的示意性图。
图7是根据本申请实施例提供的一种第二带宽与初始下行BWP的示意性图。
图8是根据本申请实施例提供的另一种第二带宽与初始下行BWP的示意性图。
图9是根据本申请实施例提供的一种第三带宽与初始上行BWP的示意性图。
图10是根据本申请实施例提供的另一种第三带宽与初始上行BWP的示意性图。
图11是根据本申请实施例提供的另一种资源确定方法的示意性流程图。
图12是根据本申请实施例提供的一种终端设备的示意性框图。
图13是根据本申请实施例提供的一种网络设备的示意性框图。
图14是根据本申请实施例提供的一种通信设备的示意性框图。
图15是根据本申请实施例提供的一种装置的示意性框图。
图16是根据本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。针对本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新空口(New Radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、非地面通信网络(Non-Terrestrial Networks，NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、第五代通信(5th-Generation，5G)系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信，或车联网(Vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信系统。
可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
可选地，本申请实施例中的通信系统可以应用于非授权频谱，其中，非授权频谱也可以认为是共享频谱；或者，本申请实施例中的通信系统也可以应用于授权频谱，其中，授权频谱也可以认为是非共享频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中，终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是WLAN中的站点(STATION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统例如NR网络中的终端设备，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
在本申请实施例中，终端设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中，终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称， 如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中，网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备或者基站(gNB)或者未来演进的PLMN网络中的网络设备或者NTN网络中的网络设备等。
作为示例而非限定，在本申请实施例中，网络设备可以具有移动特性，例如网络设备可以为移动的设备。可选地，网络设备可以为卫星、气球站。例如，卫星可以为低地球轨道(low earth orbit，LEO)卫星、中地球轨道(medium earth orbit，MEO)卫星、地球同步轨道(geostationary earth orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等。可选地，网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中，网络设备可以为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备120，网络设备110和终端设备120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。本申请的说明书和权利要求书及所述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
本申请实施例中，“预定义”可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。
本申请实施例中，所述“协议”可以指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
为便于更好的理解本申请实施例，对本申请相关的随机接入过程进行说明。
在5G系统中，随机接入过程采用了类似LTE的四步随机接入过程，如图2所示：
S11，UE向基站发送物理随机接入过程信道(Physical Random Access Channel，PRACH)，该 PRACH包含随机接入前导码(preamble)，也即消息1(Message 1，Msg 1)；
S12，基站检测到有UE发送随机接入前导码之后向UE发送随机接入响应(random access response，RAR)，也即消息2(message 2，Msg 2)，以告知UE在发送消息3(message 3，Msg 3)时可以使用的物理上行共享信道(Physical Uplink Shared Channel，PUSCH)资源，为UE分配临时无线网络临时标识符(Radio Network Temporary Identity，RNTI)，给UE提供定时提前命令(time advance command)等；
S13，UE接收到RAR之后，在RAR所指定的PUSCH资源发送Msg 3消息，其中携带一个UE特定的临时标识信息；
S14，基站向UE发送消息4(message 4，Msg 4)消息，其中包括竞争解决消息，同时为UE分配上行传输资源。UE接收到基站发送的Msg 4时，会检测UE在Msg 3发送的UE特定临时标识是否包含在基站发送的竞争解决消息中，若包含则表明UE随机接入成功，否则认为随机过程失败，UE需要再次从第一步开始发起随机接入过程。
四步随机接入过程的时延开销比较大，对于5G中的低时延高可靠场景是不合适的。在NR的标准化过程中，考虑到低时延高可靠相关业务的特点，在版本16(release16，R16)引入了两步随机接入过程，即类型2(Type-2)随机接入过程，相比四步随机接入过程，可以减少接入时延。相应的，四步随机接入过程称为类型1(Type-1)随机接入过程。
两步随机接入过程如下图3所示，在两步随机接入过程中，简单的说，相当于将四步随机接入过程的Msg 1和Msg 3合并为两步随机接入过程中的S21，UE发送消息A(message A，Msg A)，将四步随机接入过程的Msg 2和Msg 4合并为两步随机接入过程中的S22，基站应答消息B(message B，Msg B)。对于两步随机接入过程中的S21，Msg A包括preamble和PUSCH部分，Msg B包括物理下行控制信道(Physical Downlink Control Channel，PDCCH)和物理下行共享信道(Physical Downlink Shared Channel，PDSCH)。对于Msg A，UE需要发送preamble和PUSCH，其中Preamble所在的随机接入过程时机(Random Access Channel Occasion，RO)与四步随机接入过程一样，通过网络配置，其RO可以与四步随机接入过程的RO共享，也可以单独配置。PUSCH所在的时频资源称为PUSCH时机(PUSCH occasion，PO)。一个PO可以包含多个PUSCH资源单元(PUSCH resource unit，PRU)，一个PRU包含PUSCH资源+DMRS，解调参考信号(Demodulation Reference Signal，DMRS)包含DMRS端口和DMRS序列。PO也是通过网络配置的，其周期与RO是相同的，且是有关联关系的。
为便于更好的理解本申请实施例，对本申请相关的降低能力(Reduced capability，RedCap)终端进行说明。
NR系统主要是为了支持增强移动超宽带(Enhance Mobile Broadband，eMBB)业务而设计的。其主要技术是为了满足高速率、高频谱效率、大带宽的需要。实际上，除了eMBB，还存在多种不同的业务类型，例如传感器网络、视频监控、可穿戴等，它们在速率、带宽、功耗、成本等方面与eMBB业务有着不同的需求。支持这些业务的终端相比支持eMBB的终端的能力是降低的，如支持的带宽减小、处理时间的放松、天线数减少、最大调制阶数的放松等。需要针对这些业务和相应的低能力终端对NR系统进行优化，这类终端可以简称为RedCap终端。在LTE技术中，已经有了类似的系统设计用于支持大连接数、低功耗、低成本的终端，如机器类通信(Machine Type Communication，MTC)，窄带物联网(Narrow Band Internet of Things，NB-IoT)。在NR系统中，希望引入类似的技术用于使用NR技术更好的支持除eMBB业务之外的其他业务类型。对于这类低复杂度、低成本的终端，一种需要进行的优化是覆盖增强，用于提高这类终端的下行和上行覆盖。
为便于更好的理解本申请实施例，对本申请相关的网络对RedCap终端的识别进行说明。
对于初始接入的UE，在接收到系统消息后，发起随机接入过程与网络建立无线资源控制(Radio Resource Control，RRC)连接。在此过程中，网络需要识别UE的类型，获得UE相关的能力信息。
现阶段，可以采用以下方法指示UE的类型：
在Msg 1的发送阶段进行指示，例如通过Msg 1传输所在的初始上行带宽部分(Band Width Part，BWP)，通过独立的PRACH资源，或划分独立的PRACH preamble集合；
在Msg 3的发送阶段进行指示，例如承载的Msg 3 PUSCH的载荷中；
在Msg 4传输之后指示，如消息5(message 5，Msg 5)或者作为UE的能力上报；
对于两步随机接入过程，在Msg A的发送阶段进行指示。
为便于更好的理解本申请实施例，对本申请相关的5G的频点进行说明。
5G的频点分为两部分：FR1(f<6GHz，低频)和FR2(f>6GHz，高频、毫米波)。对于FR1，UE支持的带宽可以是5MHz，10MHz，15MHz，20MHz，25MHz，30MHz，40MHz，50MHz，60MHz，80MHz和100MHz。对于FR2，UE支持的带宽可以是50MHz，100MHz，200MHz和400MHz等。 为了使UE能够支持5G频段上接入网络，对于FR1来说，UE的带宽需要支持100MHz。相应的，对于FR2的频段，UE的带宽需要支持400MHz。
对于RedCap终端来说，其中一个主要的特点是支持的带宽的减少，从而减少功耗、降低成本。在现有的NR系统并没有专门考虑支持低带宽能力的终端接入网络，会造成这类终端由于支持的带宽较小，无法接入网络。
UE在初始接入过程中，需要通过物理广播信道(Physical Broadcast Channel，PBCH)承载的主信息块(Master Information Block，MIB)信息中获得类型0(type0)PDCCH的控制资源集(Control Resource Set，CORESET)#0和搜索空间(search space)#0信息，用于指示type0 PDCCH在频域上的资源块(Resource block，RB)和时域上的符号。CORESET#0信息指示一个索引(index)，根据index，得到CORESET#0的RB个数和符号数，以及相比同步信号块(Synchronization Signal Block，SSB)的RB偏移(offset)。对于FR1，在子载波间隔为15kHz情况下，CORESET#0的带宽可以配置为24、48、96个RB，对应5MHz、10MHz、20MHz的带宽。在30kHz子载波间隔下，CORESET#0配置的最大RB数为48，因此也不会超过20MHz的带宽。UE通过type0 PDCCH接收承载系统信息块(System Information Block，SIB)的PDSCH的调度信息，从而接收SIB1信息。对于FR1来说，RedCap终端在初始接入阶段可以支持20MHz带宽，大于等于CORESET#0的带宽，因此可以成功接收type0 PDCCH。同理，对于FR2来说，RedCap终端在初始接入阶段可以支持100MHz带宽，也大于等于CORESET#0的带宽。
UE可以通过type0 PDCCH接收承载SIB的PDSCH的调度信息，从而接收SIB1信息。从SIB1信息中，UE可以获得初始下行BWP和初始上行BWP配置信息。在UE的随机接入过程中的信道的发送和接收过程中，可以在初始下行BWP和初始上行BWP上进行。在现有技术中，初始下行BWP和初始上行BWP配置的带宽允许超过CORESET#0的带宽。如果该小区支持RedCap终端的接入，并且沿用现有的初始下行BWP和初始上行BWP的配置，可能其带宽配置会超过RedCap终端的带宽能力，造成RedCap终端在初始接入阶段无法正确接收和发送信道(随机接入过程中的信息)。
基于上述技术问题，本申请提出了一种资源确定方案，可以根据终端设备支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中的信息传输的频域资源，确保随机接入过程中的信息传输的频域资源在终端设备支持的带宽能力范围内，从而，可以正确发送或接收随机接入过程中的信息，并完成随机接入过程。
以下通过具体实施例详述本申请的技术方案。
图4是根据本申请实施例的资源确定方法200的示意性流程图，如图4所示，该方法200可以包括如下内容中的至少部分内容：
S210，终端设备根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源。
在本申请实施例中，终端设备可以根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源，确保随机接入过程中第一信息传输的频域资源在终端设备支持的带宽能力范围内，从而，可以正确发送或接收随机接入过程中第一信息，并完成随机接入过程。
可选地，该终端设备为降低能力终端(RedCap终端)。当然，该终端设备也可以是其他具有特定带宽能力的终端，本申请实施例对此并不限定。
可选地，该系统信息可以是SIB1信息。当然，该系统信息也可以是其他信息，本申请实施例对此并不限定。
可选地，在一些实施例中，该带宽信息包括以下中的至少一种：
控制资源集0(CORESET#0)、初始下行BWP、初始上行BWP。
可选地，作为示例1，该带宽信息包括控制资源集0和/或初始下行BWP，此种情况下，该第一信息为随机接入过程中的下行信息。
可选地，在示例1中，该第一信息包括以下至少之一：
四步随机接入过程中的第二条信息(Msg 2)，四步随机接入过程中的第四条信息(Msg 4)，两步随机接入过程中的第二条信息(Msg B)。
需要说明的是，在四步随机接入过程中，当终端设备在发送Msg 1之后，通过检测随机接入无线网络临时标识符(Random Access Radio Network Temporary Identity，RA-RNTI)加扰的循环冗余码校验(Cyclical Redundancy Check，CRC)的DCI格式1_0获得承载RAR的PDSCH的调度信息。对于两步随机接入过程，当终端设备在发送Msg A之后，通过检测Msg B-RNTI加扰的CRC的DCI格式1_0获得承载Msg B的PDSCH的调度信息。其中，PDSCH的调度信息中包括频域资源指示信息。频域资源在配置的CORESET#0的带宽范围内进行指示，如果CORESET#0没有被配置，那就在配置 的初始下行BWP的带宽范围内进行指示。
对于RedCap终端，如果沿用网络配置的CORESET#0或者初始下行BWP，CORESET#0或者初始下行BWP的带宽配置可能超过RedCap终端支持的带宽能力，此时需要限定频域资源指示信息在CORESET#0或者初始下行BWP中所指示的频域范围。
可选地，在示例1的一些实现方式中，上述S210具体可以是：
在该控制资源集0的带宽大于该终端设备支持的带宽能力的情况下，该终端设备确定该第一信息传输的频域范围为该控制资源集0的带宽中的第一带宽，且该第一带宽小于或等于该终端设备支持的带宽能力。
此种情况下，终端设备确定频域资源指示信息对应的频域带宽范围为上述方法确定的第一带宽。具体地，频域资源指示信息如下：
比特数：
Figure PCTCN2020137721-appb-000001
其中
Figure PCTCN2020137721-appb-000002
不再是配置的控制资源集0的带宽，对于RedCap终端来说，是配置的控制资源集0的带宽中定义的部分带宽，即第一带宽。
可选地，该第一带宽位于该控制资源集0的带宽中的中心位置，例如如图5所示，该第一带宽位于该控制资源集0的带宽中的中心位置，且该第一带宽等于该控制资源集0的带宽的一半。或者，该第一带宽位于该控制资源集0的带宽中的边缘位置，例如如图6所示，该第一带宽位于该控制资源集0的带宽中的边缘位置，且该第一带宽不足该控制资源集0的带宽的一半。
需要说明的是，中心位置可以是第一带宽的中心频率与控制资源集0的带宽的中心频率相同。边缘位置例如可以是第一带宽从控制资源集0的带宽的第一个RB开始连续的带宽。
可选地，该第一带宽为预配置或协议约定的，或者，该第一带宽为网络设备配置或指示的，或者，该第一带宽为该系统消息(如SIB1信息)中获取的。
可选地，在示例1的一些实现方式中，上述S210具体可以是：
在该初始下行BWP的带宽大于该终端设备支持的带宽能力的情况下，该终端设备确定该第一信息传输的频域范围为该初始下行BWP的带宽中的第二带宽，且该第二带宽小于或等于该终端设备支持的带宽能力。
此种情况下，终端设备确定频域资源指示信息对应的频域带宽范围为上述方法确定的第二带宽。具体地，频域资源指示信息如下：
比特数：
Figure PCTCN2020137721-appb-000003
其中
Figure PCTCN2020137721-appb-000004
不再是配置的初始下行BWP的带宽，对于RedCap终端来说，是配置的初始下行BWP的带宽中定义的部分带宽，即第二带宽。
可选地，该第二带宽位于该初始下行BWP的带宽中的中心位置，例如如图7所示，该第二带宽位于该初始下行BWP的带宽中的中心位置，且该第二带宽等于该初始下行BWP的带宽的一半。或者，该第二带宽位于该初始下行BWP的带宽中的边缘位置，例如如图8所示，该第二带宽位于该初始下行BWP的带宽中的边缘位置，且该第二带宽等于该初始下行BWP的带宽的一半。
需要说明的是，中心位置可以是第二带宽的中心频率与初始下行BWP的带宽的中心频率相同。边缘位置例如可以是第二带宽从初始下行BWP的带宽的第一个RB开始连续的带宽。
可选地，该第二带宽为预配置或协议约定的，或者，该第二带宽为网络设备配置或指示的，或者，该第二带宽为该系统消息(如SIB1信息)中获取的。
可选地，在示例1的一些实现方式中，上述S210具体可以是：
在该控制资源集0的带宽小于或等于该终端设备支持的带宽能力的情况下，该终端设备确定该第一信息传输的频域范围为该控制资源集0的带宽；或，
在该初始下行BWP的带宽小于或等于该终端设备支持的带宽能力的情况下，该终端设备确定该第一信息传输的频域范围为该初始下行BWP的带宽。
可选地，作为示例2，该带宽信息包括初始上行BWP，此种情况下，该第一信息为随机接入过程中的上行信息。
可选地，在示例2中，该第一信息包括四步随机接入过程中的第三条信息(Msg 3)。
需要说明的是，在四步随机接入过程中，当RedCap终端在发送Msg 1之后，检测RA-RNTI加扰的CRC的DCI格式1_0，从而接收RAR。其中，RAR中指示了承载Msg 3的PUSCH的调度信息。类似的，PUSCH的调度信息中包括频域资源指示信息。频域资源在配置的初始上行BWP的带宽范围内进行指示。当Msg 3发生重传，PUSCH的调度信息通过临时小区RNTI(Temporary Cell RNTI，TC-RNTI)加扰的CRC的DCI格式0_0指示。
对于RedCap终端，如果沿用初始上行BWP的带宽范围，初始上行BWP的带宽配置可能超过RedCap终端支持的带宽能力，此时需要限定频域资源指示信息在初始上行BWP中所指示的频域范 围。
可选地，在示例2的一些实现方式中，上述S210具体可以是：
在该初始上行BWP的带宽大于该终端设备支持的带宽能力的情况下，该终端设备确定该第一信息传输的频域范围为该初始上行BWP的带宽中的第三带宽，且该第三带宽小于或等于该终端设备支持的带宽能力。
此种情况下，终端设备确定频域资源指示信息对应的频域带宽范围为上述方法确定的第三带宽。具体地，频域资源指示信息如下：
比特数：
Figure PCTCN2020137721-appb-000005
其中
Figure PCTCN2020137721-appb-000006
不再是配置的初始上行BWP的带宽，对于RedCap终端来说，是配置的初始上行BWP的带宽中定义的部分带宽，即第三带宽。
可选地，在示例2的一些实现方式中，上述S210具体可以是：
在该初始上行BWP的带宽大于该终端设备支持的带宽能力的情况下，该终端设备根据激活的上行BWP和该初始上行BWP的带宽中的第三带宽，确定该第一信息传输的频域范围；
其中，该第三带宽小于或等于该终端设备支持的带宽能力。
可选地，在示例2的一些实现方式中，上述S210具体可以是：
当该激活的上行BWP和该第三带宽具有相同的子载波间隔配置和相同的循环前缀(Cyclic prefix，CP)长度，并且该激活的上行BWP包括该第三带宽的所有的资源块(Resource Block，RB)，或者，该激活的上行BWP的带宽与该第三带宽为同一带宽，该终端设备确定该第一信息传输的频域范围为该第三带宽；或
当该激活的上行BWP和该第三带宽具有不同的子载波间隔配置或不同的CP长度，该终端设备确定该第一信息传输的频域范围为该激活的上行BWP中从编号上第一个RB开始的W个RB，其中，W为正整数，且W等于该第三带宽中的RB数量。
需要说明的是，当终端设备在连接态，配置了上行BWP，在随机接入过程中，在Msg 3的频域资源指示信息中，需要根据当前激活的上行BWP和初始上行BWP确定Msg 3的频域资源分配的范围，然而，由于RedCap终端在连接态的支持的带宽可能与初始接入是不同的，或者考虑到RedCap终端的带宽能力的限制，激活的上行BWP带宽小于初始上行BWP的带宽的情况。因此，对于RedCap终端，其可以基于激活的上行BWP与第三带宽的关系，确定该第一信息传输的频域范围。
可选地，在示例2中，该第三带宽位于该初始上行BWP的带宽中的中心位置，例如如图9所示，该第三带宽位于该初始上行BWP的带宽中的中心位置，且该第三带宽等于该初始上行BWP的带宽的一半。或者，该第三带宽位于该初始上行BWP的带宽中的边缘位置，例如如图10所示，该第三带宽位于该初始上行BWP的带宽中的边缘位置，且该第三带宽等于该初始上行BWP的带宽的一半。
需要说明的是，中心位置可以是第三带宽的中心频率与初始上行BWP的带宽的中心频率相同。边缘位置例如可以是第三带宽从初始上行BWP的带宽的第一个RB开始连续的带宽。
还需要说明的是，对于上行传输来说，终端设备可以采用离散傅里叶变换的正交频分复用(Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing，DFT-S-OFDM)的波形进行传输，希望在频域资源的分配上尽量连续。如果RedCap终端的Msg 3传输的频域资源位于配置的初始上行BWP的带宽中的中心部分带宽，当RedCap终端的Msg 3传输和非RedCap终端的Msg3传输在相同的时隙时，会造成该初始上行BWP的带宽的两边的带宽不能被非RedCap终端的Msg 3传输很好的利用，因此，优选地，RedCap终端的Msg 3传输的频域资源位于配置的初始上行BWP的带宽中的边缘位置。
可选地，在示例2中，该第三带宽为预配置或协议约定的，或者，该第三带宽为网络设备配置或指示的，或者，该第三带宽为该系统消息(如SIB1信息)中获取的。
需要说明的是，上述示例1和示例2可以是假定初始上行BWP和初始下行BWP为RedCap终端和非RedCap终端共用的情况。
可选地，在一些实施例中，假设为RedCap终端单独配置初始上行BWP和初始下行BWP，则会根据RedCap终端的带宽能力配置合适的初始上行BWP和初始下行BWP的带宽。从而，RedCap终端可以基于其单独配置初始上行BWP确定随机接入过程中的上行信息的传输频域资源，或者，RedCap终端可以基于其单独配置初始下行BWP确定随机接入过程中的下行信息的传输频域资源。
因此，在本申请实施例中，终端设备可以根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源，确保随机接入过程中第一信息传输的频域资源在终端设备支持的带宽能力范围内，从而，终端设备可以正确发送或接收随机接入过程中第一信息，并完成随机接入过程。
上文结合图4至图10，详细描述了本申请的终端侧实施例，下文结合图11，详细描述本申请的 网络侧实施例，应理解，网络侧实施例与终端侧实施例相互对应，类似的描述可以参照终端侧实施例。
图11是根据本申请实施例的资源确定方法300的示意性流程图，如图11所示，该方法300可以包括如下内容中的至少部分内容：
S310，网络设备根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源。
在本申请实施例中，网络设备可以根据终端设备支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源，确保随机接入过程中第一信息传输的频域资源在终端设备支持的带宽能力范围内，从而，网络设备可以正确发送或接收随机接入过程中第一信息，并完成随机接入过程。
可选地，该终端设备为降低能力终端(RedCap终端)。当然，该终端设备也可以是其他具有特定带宽能力的终端，本申请实施例对此并不限定。
可选地，该系统信息可以是SIB1信息。当然，该系统信息也可以是其他信息，本申请实施例对此并不限定。
可选地，在一些实施例中，该带宽信息包括以下中的至少一种：
控制资源集0(CORESET#0)、初始下行BWP、初始上行BWP。
可选地，作为示例3，该带宽信息包括控制资源集0和/或初始下行BWP，此种情况下，该第一信息为随机接入过程中的下行信息。
可选地，在示例3中，该第一信息包括以下至少之一：
四步随机接入过程中的第二条信息(Msg 2)，四步随机接入过程中的第四条信息(Msg 4)，两步随机接入过程中的第二条信息(Msg B)。
可选地，在示例3的一些实现方式中，上述S310具体可以是：
在该控制资源集0的带宽大于该终端设备支持的带宽能力的情况下，该网络设备确定该第一信息传输的频域范围为该控制资源集0的带宽中的第一带宽，且该第一带宽小于或等于该终端设备支持的带宽能力。
可选地，该第一带宽位于该控制资源集0的带宽中的中心位置，或者，该第一带宽位于该控制资源集0的带宽中的边缘位置。
可选地，该第一带宽为预配置或协议约定的，或者，该第一带宽为网络设备配置或指示的，或者，该第一带宽为该系统消息(如SIB1信息)中承载的信息。
可选地，在示例3的一些实现方式中，上述S310具体可以是：
在该初始下行BWP的带宽大于该终端设备支持的带宽能力的情况下，该网络设备确定该第一信息传输的频域范围为该初始下行BWP的带宽中的第二带宽，且该第二带宽小于或等于该终端设备支持的带宽能力。
可选地，该第二带宽位于该初始下行BWP的带宽中的中心位置，或者，该第二带宽位于该初始下行BWP的带宽中的边缘位置。
可选地，该第二带宽为预配置或协议约定的，或者，该第二带宽为网络设备配置或指示的，或者，该第二带宽为该系统消息(如SIB1信息)中承载的信息。
可选地，在示例3的一些实现方式中，上述S310具体可以是：
在该控制资源集0的带宽小于或等于该终端设备支持的带宽能力的情况下，该网络设备确定该第一信息传输的频域范围为该控制资源集0的带宽；或，
在该初始下行BWP的带宽小于或等于该终端设备支持的带宽能力的情况下，该网络设备确定该第一信息传输的频域范围为该初始下行BWP的带宽。
可选地，作为示例4，该带宽信息包括初始上行BWP，此种情况下，该第一信息为随机接入过程中的上行信息。
可选地，在示例4中，该第一信息包括四步随机接入过程中的第三条信息(Msg 3)。
可选地，在示例4的一些实现方式中，上述S310具体可以是：
在该初始上行BWP的带宽大于该终端设备支持的带宽能力的情况下，该网络设备确定该第一信息传输的频域范围为该初始上行BWP的带宽中的第三带宽，且该第三带宽小于或等于该终端设备支持的带宽能力。
可选地，在示例4的一些实现方式中，上述S310具体可以是：
在该初始上行BWP的带宽大于该终端设备支持的带宽能力的情况下，该网络设备根据激活的上行BWP和该初始上行BWP的带宽中的第三带宽，确定该第一信息传输的频域范围；
其中，该第三带宽小于或等于该终端设备支持的带宽能力。
可选地，在示例4的一些实现方式中，上述S310具体可以是：
当该激活的上行BWP和该第三带宽具有相同的子载波间隔配置和相同的CP长度，并且该激活的上行BWP包括该第三带宽的所有的RB，或者，该激活的上行BWP的带宽与该第三带宽为同一带宽，该网络设备确定该第一信息传输的频域范围为该第三带宽；或
当该激活的上行BWP和该第三带宽具有不同的子载波间隔配置或不同的CP长度，该网络设备确定该第一信息传输的频域范围为该激活的上行BWP中从编号上第一个RB开始的W个RB，其中，W为正整数，且W等于该第三带宽中的RB数量。
可选地，该第三带宽位于该初始上行BWP的带宽中的中心位置，或者，该第三带宽位于该初始上行BWP的带宽中的边缘位置。
可选地，该第三带宽为预配置或协议约定的，或者，该第三带宽为网络设备配置或指示的，或者，该第三带宽为该系统消息(如SIB1信息)中承载的信息。
需要说明的是，上述示例3和示例4可以是假定初始上行BWP和初始下行BWP为RedCap终端和非RedCap终端共用的情况。
可选地，在一些实施例中，假设为RedCap终端单独配置初始上行BWP和初始下行BWP，则会根据RedCap终端的带宽能力配置合适的初始上行BWP和初始下行BWP的带宽。从而，网络设备可以基于RedCap终端单独配置初始上行BWP确定随机接入过程中的上行信息的传输频域资源，或者，网络设备可以基于RedCap终端单独配置初始下行BWP确定随机接入过程中的下行信息的传输频域资源。
因此，在本申请实施例中，网络设备可以根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源，确保随机接入过程中第一信息传输的频域资源在终端设备支持的带宽能力范围内，从而，网络设备可以正确发送或接收随机接入过程中第一信息，并完成随机接入过程。
上文结合图4至图11，详细描述了本申请的方法实施例，下文结合图12至图16，详细描述本申请的装置实施例，应理解，装置实施例与方法实施例相互对应，类似的描述可以参照方法实施例。
图12示出了根据本申请实施例的终端设备400的示意性框图。如图12所示，该终端设备400包括：
处理单元410，根据终端设备支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源。
可选地，该带宽信息包括以下中的至少一种：
控制资源集0、初始下行带宽部分BWP、初始上行BWP。
可选地，该带宽信息包括控制资源集0和/或初始下行BWP，该第一信息为随机接入过程中的下行信息。
可选地，该处理单元410具体用于：
在该控制资源集0的带宽大于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该控制资源集0的带宽中的第一带宽，且该第一带宽小于或等于该终端设备支持的带宽能力；或，
在该初始下行BWP的带宽大于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该初始下行BWP的带宽中的第二带宽，且该第二带宽小于或等于该终端设备支持的带宽能力。
可选地，该第一带宽位于该控制资源集0的带宽中的中心位置，或者，该第一带宽位于该控制资源集0的带宽中的边缘位置。
可选地，该第二带宽位于该初始下行BWP的带宽中的中心位置，或者，该第二带宽位于该初始下行BWP的带宽中的边缘位置。
可选地，该第一带宽为预配置或协议约定的，或者，该第一带宽为网络设备配置或指示的，或者，该第一带宽为该系统消息中获取的。
可选地，该第二带宽为预配置或协议约定的，或者，该第二带宽为网络设备配置或指示的，或者，该第二带宽为该系统消息中获取的。
可选地，该处理单元410具体用于：
在该控制资源集0的带宽小于或等于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该控制资源集0的带宽；或，
在该初始下行BWP的带宽小于或等于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该初始下行BWP的带宽。
可选地，该第一信息包括以下至少之一：
四步随机接入过程中的第二条信息，四步随机接入过程中的第四条信息，两步随机接入过程中的第二条信息。
可选地，该带宽信息包括初始上行BWP，该第一信息为随机接入过程中的上行信息。
可选地，该处理单元410具体用于：
在该初始上行BWP的带宽大于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该初始上行BWP的带宽中的第三带宽，且该第三带宽小于或等于该终端设备支持的带宽能力。
可选地，该处理单元410具体用于：
在该初始上行BWP的带宽大于该终端设备支持的带宽能力的情况下，根据激活的上行BWP和该初始上行BWP的带宽中的第三带宽，确定该第一信息传输的频域范围；
其中，该第三带宽小于或等于该终端设备支持的带宽能力。
可选地，该处理单元410具体用于：
当该激活的上行BWP和该第三带宽具有相同的子载波间隔配置和相同的循环前缀CP长度，并且该激活的上行BWP包括该第三带宽的所有的资源块RB，或者，该激活的上行BWP的带宽与该第三带宽为同一带宽，确定该第一信息传输的频域范围为该第三带宽；或
当该激活的上行BWP和该第三带宽具有不同的子载波间隔配置或不同的CP长度，确定该第一信息传输的频域范围为该激活的上行BWP中从编号上第一个RB开始的W个RB，其中，W为正整数，且W等于该第三带宽中的RB数量。
可选地，该第三带宽位于该初始上行BWP的带宽中的中心位置，或者，该第三带宽位于该初始上行BWP的带宽中的边缘位置。
可选地，该第三带宽为预配置或协议约定的，或者，该第三带宽为网络设备配置或指示的，或者，该第三带宽为该系统消息中获取的。
可选地，该第一信息包括为四步随机接入过程中的第三条信息。
可选地，该终端设备为降低能力终端。
可选地，在一些实施例中，上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的终端设备400可对应于本申请方法实施例中的终端设备，并且终端设备400中的各个单元的上述和其它操作和/或功能分别为了实现图4所示方法200中终端设备的相应流程，为了简洁，在此不再赘述。
图13示出了根据本申请实施例的网络设备500的示意性框图。如图13所示，该网络设备500包括：
处理单元510，根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源。
可选地，该带宽信息包括以下中的至少一种：
控制资源集0、初始下行带宽部分BWP、初始上行BWP。
可选地，该带宽信息包括控制资源集0和/或初始下行BWP，该第一信息为随机接入过程中的下行信息。
可选地，该处理单元510具体用于：
在该控制资源集0的带宽大于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该控制资源集0的带宽中的第一带宽，且该第一带宽小于或等于该终端设备支持的带宽能力；或，
在该初始下行BWP的带宽大于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该初始下行BWP的带宽中的第二带宽，且该第二带宽小于或等于该终端设备支持的带宽能力。
可选地，该第一带宽位于该控制资源集0的带宽中的中心位置，或者，该第一带宽位于该控制资源集0的带宽中的边缘位置。
可选地，该第二带宽位于该初始下行BWP的带宽中的中心位置，或者，该第二带宽位于该初始下行BWP的带宽中的边缘位置。
可选地，该第一带宽为预配置或协议约定的，或者，该第一带宽为网络设备配置或指示的，或者，该第一带宽为该系统消息中承载的信息。
可选地，该第二带宽为预配置或协议约定的，或者，该第二带宽为网络设备配置或指示的，或者，该第二带宽为该系统消息中承载的信息。
可选地，该处理单元510具体用于：
在该控制资源集0的带宽小于或等于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该控制资源集0的带宽；或，
在该初始下行BWP的带宽小于或等于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该初始下行BWP的带宽。
可选地，该第一信息包括以下至少之一：
四步随机接入过程中的第二条信息，四步随机接入过程中的第四条信息，两步随机接入过程中的第二条信息。
可选地，该带宽信息包括初始上行BWP，该第一信息为随机接入过程中的上行信息。
可选地，该处理单元510具体用于：
在该初始上行BWP的带宽大于该终端设备支持的带宽能力的情况下，确定该第一信息传输的频域范围为该初始上行BWP的带宽中的第三带宽，且该第三带宽小于或等于该终端设备支持的带宽能力。
可选地，该处理单元510具体用于：
在该初始上行BWP的带宽大于该终端设备支持的带宽能力的情况下，根据激活的上行BWP和该初始上行BWP的带宽中的第三带宽，确定该第一信息传输的频域范围；
其中，该第三带宽小于或等于该终端设备支持的带宽能力。
可选地，该处理单元510具体用于：
当该激活的上行BWP和该第三带宽具有相同的子载波间隔配置和相同的循环前缀CP长度，并且该激活的上行BWP包括该第三带宽的所有的资源块RB，或者，该激活的上行BWP的带宽与该第三带宽为同一带宽，确定该第一信息传输的频域范围为该第三带宽；或
当该激活的上行BWP和该第三带宽具有不同的子载波间隔配置或不同的CP长度，确定该第一信息传输的频域范围为该激活的上行BWP中从编号上第一个RB开始的W个RB，其中，W为正整数，且W等于该第三带宽中的RB数量。
可选地，该第三带宽位于该初始上行BWP的带宽中的中心位置，或者，该第三带宽位于该初始上行BWP的带宽中的边缘位置。
可选地，该第三带宽为预配置或协议约定的，或者，该第三带宽为网络设备配置或指示的，或者，该第三带宽为该系统消息中承载的信息。
可选地，该第一信息包括为四步随机接入过程中的第三条信息。
可选地，该终端设备为降低能力终端。
可选地，在一些实施例中，上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的网络设备500可对应于本申请方法实施例中的网络设备，并且网络设备500中的各个单元的上述和其它操作和/或功能分别为了实现图11所示方法300中网络设备的相应流程，为了简洁，在此不再赘述。
图14是本申请实施例提供的一种通信设备600示意性结构图。图14所示的通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图14所示，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，如图14所示，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600具体可为本申请实施例的网络设备，并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备600具体可为本申请实施例的终端设备，并且该通信设备600可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
图15是本申请实施例的装置的示意性结构图。图15所示的装置700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图15所示，装置700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该装置700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该装置700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该装置可应用于本申请实施例中的网络设备，并且该装置可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该装置可应用于本申请实施例中的终端设备，并且该装置可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，本申请实施例提到的装置也可以是芯片。例如可以是系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图16是本申请实施例提供的一种通信系统800的示意性框图。如图16所示，该通信系统800包括终端设备810和网络设备820。
其中，该终端设备810可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备820可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。针对这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (48)

  1. 一种资源确定方法，其特征在于，包括：
    终端设备根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源。
  2. 如权利要求1所述的方法，其特征在于，所述带宽信息包括以下中的至少一种：
    控制资源集0、初始下行带宽部分BWP、初始上行BWP。
  3. 如权利要求2所述的方法，其特征在于，所述带宽信息包括控制资源集0和/或初始下行BWP，所述第一信息为随机接入过程中的下行信息。
  4. 如权利要求3所述的方法，其特征在于，所述终端设备根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源，包括：
    在所述控制资源集0的带宽大于所述终端设备支持的带宽能力的情况下，所述终端设备确定所述第一信息传输的频域范围为所述控制资源集0的带宽中的第一带宽，且所述第一带宽小于或等于所述终端设备支持的带宽能力；或，
    在所述初始下行BWP的带宽大于所述终端设备支持的带宽能力的情况下，所述终端设备确定所述第一信息传输的频域范围为所述初始下行BWP的带宽中的第二带宽，且所述第二带宽小于或等于所述终端设备支持的带宽能力。
  5. 如权利要求4所述的方法，其特征在于，
    所述第一带宽位于所述控制资源集0的带宽中的中心位置，或者，所述第一带宽位于所述控制资源集0的带宽中的边缘位置。
  6. 如权利要求4所述的方法，其特征在于，
    所述第二带宽位于所述初始下行BWP的带宽中的中心位置，或者，所述第二带宽位于所述初始下行BWP的带宽中的边缘位置。
  7. 如权利要求4或5所述的方法，其特征在于，
    所述第一带宽为预配置或协议约定的，或者，所述第一带宽为网络设备配置或指示的，或者，所述第一带宽为所述系统消息中获取的。
  8. 如权利要求4或6所述的方法，其特征在于，
    所述第二带宽为预配置或协议约定的，或者，所述第二带宽为网络设备配置或指示的，或者，所述第二带宽为所述系统消息中获取的。
  9. 如权利要求3所述的方法，其特征在于，所述终端设备根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源，包括：
    在所述控制资源集0的带宽小于或等于所述终端设备支持的带宽能力的情况下，所述终端设备确定所述第一信息传输的频域范围为所述控制资源集0的带宽；或，
    在所述初始下行BWP的带宽小于或等于所述终端设备支持的带宽能力的情况下，所述终端设备确定所述第一信息传输的频域范围为所述初始下行BWP的带宽。
  10. 如权利要求3至9中任一项所述的方法，其特征在于，所述第一信息包括以下至少之一：
    四步随机接入过程中的第二条信息，四步随机接入过程中的第四条信息，两步随机接入过程中的第二条信息。
  11. 如权利要求2所述的方法，其特征在于，所述带宽信息包括初始上行BWP，所述第一信息为随机接入过程中的上行信息。
  12. 如权利要求11所述的方法，其特征在于，所述终端设备根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源，包括：
    在所述初始上行BWP的带宽大于所述终端设备支持的带宽能力的情况下，所述终端设备确定所述第一信息传输的频域范围为所述初始上行BWP的带宽中的第三带宽，且所述第三带宽小于或等于所述终端设备支持的带宽能力。
  13. 如权利要求11所述的方法，其特征在于，所述终端设备根据其支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源，包括：
    在所述初始上行BWP的带宽大于所述终端设备支持的带宽能力的情况下，所述终端设备根据激活的上行BWP和所述初始上行BWP的带宽中的第三带宽，确定所述第一信息传输的频域范围；
    其中，所述第三带宽小于或等于所述终端设备支持的带宽能力。
  14. 如权利要求13所述的方法，其特征在于，所述终端设备根据激活的上行BWP和所述初始上行BWP的带宽中的第三带宽，确定所述第一信息传输的频域范围，包括：
    当所述激活的上行BWP和所述第三带宽具有相同的子载波间隔配置和相同的循环前缀CP长度， 并且所述激活的上行BWP包括所述第三带宽的所有的资源块RB，或者，所述激活的上行BWP的带宽与所述第三带宽为同一带宽，所述终端设备确定所述第一信息传输的频域范围为所述第三带宽；或
    当所述激活的上行BWP和所述第三带宽具有不同的子载波间隔配置或不同的CP长度，所述终端设备确定所述第一信息传输的频域范围为所述激活的上行BWP中从编号上第一个RB开始的W个RB，其中，W为正整数，且W等于所述第三带宽中的RB数量。
  15. 如权利要求12至14中任一项所述的方法，其特征在于，
    所述第三带宽位于所述初始上行BWP的带宽中的中心位置，或者，所述第三带宽位于所述初始上行BWP的带宽中的边缘位置。
  16. 如权利要求12至15中任一项所述的方法，其特征在于，
    所述第三带宽为预配置或协议约定的，或者，所述第三带宽为网络设备配置或指示的，或者，所述第三带宽为所述系统消息中获取的。
  17. 如权利要求12至16中任一项所述的方法，其特征在于，所述第一信息包括为四步随机接入过程中的第三条信息。
  18. 如权利要求1至17中任一项所述的方法，其特征在于，所述终端设备为降低能力终端。
  19. 一种资源确定方法，其特征在于，包括：
    网络设备根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源。
  20. 如权利要求19所述的方法，其特征在于，所述带宽信息包括以下中的至少一种：
    控制资源集0、初始下行带宽部分BWP、初始上行BWP。
  21. 如权利要求20所述的方法，其特征在于，所述带宽信息包括控制资源集0和/或初始下行BWP，所述第一信息为随机接入过程中的下行信息。
  22. 如权利要求21所述的方法，其特征在于，所述网络设备根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源，包括：
    在所述控制资源集0的带宽大于所述终端设备支持的带宽能力的情况下，所述网络设备确定所述第一信息传输的频域范围为所述控制资源集0的带宽中的第一带宽，且所述第一带宽小于或等于所述终端设备支持的带宽能力；或，
    在所述初始下行BWP的带宽大于所述终端设备支持的带宽能力的情况下，所述网络设备确定所述第一信息传输的频域范围为所述初始下行BWP的带宽中的第二带宽，且所述第二带宽小于或等于所述终端设备支持的带宽能力。
  23. 如权利要求22所述的方法，其特征在于，
    所述第一带宽位于所述控制资源集0的带宽中的中心位置，或者，所述第一带宽位于所述控制资源集0的带宽中的边缘位置。
  24. 如权利要求22所述的方法，其特征在于，
    所述第二带宽位于所述初始下行BWP的带宽中的中心位置，或者，所述第二带宽位于所述初始下行BWP的带宽中的边缘位置。
  25. 如权利要求22或23所述的方法，其特征在于，
    所述第一带宽为预配置或协议约定的，或者，所述第一带宽为网络设备配置或指示的，或者，所述第一带宽为所述系统消息中承载的信息。
  26. 如权利要求22或24所述的方法，其特征在于，
    所述第二带宽为预配置或协议约定的，或者，所述第二带宽为网络设备配置或指示的，或者，所述第二带宽为所述系统消息中承载的信息。
  27. 如权利要求21所述的方法，其特征在于，所述网络设备根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源，包括：
    在所述控制资源集0的带宽小于或等于所述终端设备支持的带宽能力的情况下，所述网络设备确定所述第一信息传输的频域范围为所述控制资源集0的带宽；或，
    在所述初始下行BWP的带宽小于或等于所述终端设备支持的带宽能力的情况下，所述网络设备确定所述第一信息传输的频域范围为所述初始下行BWP的带宽。
  28. 如权利要求21至27中任一项所述的方法，其特征在于，所述第一信息包括以下至少之一：
    四步随机接入过程中的第二条信息，四步随机接入过程中的第四条信息，两步随机接入过程中的第二条信息。
  29. 如权利要求20所述的方法，其特征在于，所述带宽信息包括初始上行BWP，所述第一信息为随机接入过程中的上行信息。
  30. 如权利要求29所述的方法，其特征在于，所述网络设备根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源，包括：
    在所述初始上行BWP的带宽大于所述终端设备支持的带宽能力的情况下，所述网络设备确定所述第一信息传输的频域范围为所述初始上行BWP的带宽中的第三带宽，且所述第三带宽小于或等于所述终端设备支持的带宽能力。
  31. 如权利要求29所述的方法，其特征在于，所述网络设备根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源，包括：
    在所述初始上行BWP的带宽大于所述终端设备支持的带宽能力的情况下，所述网络设备根据激活的上行BWP和所述初始上行BWP的带宽中的第三带宽，确定所述第一信息传输的频域范围；
    其中，所述第三带宽小于或等于所述终端设备支持的带宽能力。
  32. 如权利要求31所述的方法，其特征在于，所述网络设备根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源，包括：
    当所述激活的上行BWP和所述第三带宽具有相同的子载波间隔配置和相同的循环前缀CP长度，并且所述激活的上行BWP包括所述第三带宽的所有的资源块RB，或者，所述激活的上行BWP的带宽与所述第三带宽为同一带宽，所述网络设备确定所述第一信息传输的频域范围为所述第三带宽；或
    当所述激活的上行BWP和所述第三带宽具有不同的子载波间隔配置或不同的CP长度，所述网络设备确定所述第一信息传输的频域范围为所述激活的上行BWP中从编号上第一个RB开始的W个RB，其中，W为正整数，且W等于所述第三带宽中的RB数量。
  33. 如权利要求30至32中任一项所述的方法，其特征在于，
    所述第三带宽位于所述初始上行BWP的带宽中的中心位置，或者，所述第三带宽位于所述初始上行BWP的带宽中的边缘位置。
  34. 如权利要求30至33中任一项所述的方法，其特征在于，
    所述第三带宽为预配置或协议约定的，或者，所述第三带宽为网络设备配置或指示的，或者，所述第三带宽为所述系统消息中承载的信息。
  35. 如权利要求30至34中任一项所述的方法，其特征在于，所述第一信息包括为四步随机接入过程中的第三条信息。
  36. 如权利要求19至35中任一项所述的方法，其特征在于，所述终端设备为降低能力终端。
  37. 一种终端设备，其特征在于，包括：
    处理单元，用于根据终端设备支持的带宽能力和系统消息中获取的带宽信息，确定随机接入过程中第一信息传输的频域资源。
  38. 一种网络设备，其特征在于，包括：
    处理单元，用于根据终端设备支持的带宽能力和系统消息中承载的带宽信息，确定随机接入过程中第一信息传输的频域资源。
  39. 一种终端设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至18中任一项所述的方法。
  40. 一种网络设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求19至36中任一项所述的方法。
  41. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至18中任一项所述的方法。
  42. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求19至36中任一项所述的方法。
  43. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至18中任一项所述的方法。
  44. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求19至36中任一项所述的方法。
  45. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至18中任一项所述的方法。
  46. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求19至36中任一项所述的方法。
  47. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至18中任一 项所述的方法。
  48. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求19至36中任一项所述的方法。
PCT/CN2020/137721 2020-12-18 2020-12-18 资源确定方法、终端设备和网络设备 WO2022126637A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2020/137721 WO2022126637A1 (zh) 2020-12-18 2020-12-18 资源确定方法、终端设备和网络设备
CN202080105343.8A CN116261889A (zh) 2020-12-18 2020-12-18 资源确定方法、终端设备和网络设备
EP20965651.1A EP4247075A4 (en) 2020-12-18 2020-12-18 RESOURCE DETERMINATION METHOD, TERMINAL DEVICE AND NETWORK DEVICE
US18/335,967 US20230328707A1 (en) 2020-12-18 2023-06-15 Resource determination method, terminal device, and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/137721 WO2022126637A1 (zh) 2020-12-18 2020-12-18 资源确定方法、终端设备和网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/335,967 Continuation US20230328707A1 (en) 2020-12-18 2023-06-15 Resource determination method, terminal device, and network device

Publications (1)

Publication Number Publication Date
WO2022126637A1 true WO2022126637A1 (zh) 2022-06-23

Family

ID=82058884

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/137721 WO2022126637A1 (zh) 2020-12-18 2020-12-18 资源确定方法、终端设备和网络设备

Country Status (4)

Country Link
US (1) US20230328707A1 (zh)
EP (1) EP4247075A4 (zh)
CN (1) CN116261889A (zh)
WO (1) WO2022126637A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108633059A (zh) * 2017-03-25 2018-10-09 华为技术有限公司 资源配置、确定部分带宽及指示部分带宽的方法及设备
CN109644432A (zh) * 2016-12-30 2019-04-16 Oppo广东移动通信有限公司 用于随机接入的方法和装置
CN109803396A (zh) * 2017-11-17 2019-05-24 华为技术有限公司 资源分配的方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220264589A1 (en) * 2019-07-17 2022-08-18 Samsung Electronics Co., Ltd. Method and device for reporting information, method and device for receiving message
CN114071750A (zh) * 2020-08-07 2022-02-18 华为技术有限公司 频域资源的确定方法、设备及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109644432A (zh) * 2016-12-30 2019-04-16 Oppo广东移动通信有限公司 用于随机接入的方法和装置
CN108633059A (zh) * 2017-03-25 2018-10-09 华为技术有限公司 资源配置、确定部分带宽及指示部分带宽的方法及设备
CN109803396A (zh) * 2017-11-17 2019-05-24 华为技术有限公司 资源分配的方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Channel Bandwidth Signalling", 3GPP DRAFT; R2-1811132, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Gothenburg, Sweden; 20180820 - 20180824, 16 August 2018 (2018-08-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051520824 *
See also references of EP4247075A4 *

Also Published As

Publication number Publication date
EP4247075A4 (en) 2024-01-10
CN116261889A (zh) 2023-06-13
US20230328707A1 (en) 2023-10-12
EP4247075A1 (en) 2023-09-20

Similar Documents

Publication Publication Date Title
US11626947B2 (en) Communication method and communications device
AU2021215138B2 (en) Method for configuring transmission direction of time-frequency resource, and apparatus
CN113726496B (zh) 非授权频段上ssb的传输方法和设备
EP4192150A1 (en) Channel transmission method, terminal device, and network device
JP2021503791A (ja) 検出ウィンドウ指示方法及び装置
EP4161185A1 (en) Wireless communication method and terminal device
WO2021196232A1 (zh) 物理信道的资源映射方法、终端设备和网络设备
WO2021062811A1 (zh) 数据传输方法及相关设备
WO2020063596A1 (zh) 一种通信方法及装置
JP7278303B2 (ja) 上りチャネルを送受信する方法及びデバイス
WO2023082356A1 (zh) 无线通信的方法和终端设备
WO2022147797A1 (zh) 信道接入方法及设备
WO2022126637A1 (zh) 资源确定方法、终端设备和网络设备
JP2021517427A (ja) リソーススケジューリング方法、データ送信方法及びその装置、通信システム
WO2022110072A1 (zh) 无线通信的方法、终端设备和网络设备
CN114208365A (zh) 定时器设置方法及相关设备
WO2023050355A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023050146A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022150990A1 (zh) 一种无线通信的方法及装置、通信设备
WO2022094935A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023206004A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023066202A1 (zh) 参考信号的资源映射方法与装置、终端和网络设备
WO2023197154A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022082785A1 (zh) 无线通信方法、终端设备和网络设备
WO2022077346A1 (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: 20965651

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020965651

Country of ref document: EP

Effective date: 20230615

NENP Non-entry into the national phase

Ref country code: DE