[go: up one dir, main page]

WO2023225959A1 - Procédé de traitement, dispositif de communication et support de stockage - Google Patents

Procédé de traitement, dispositif de communication et support de stockage Download PDF

Info

Publication number
WO2023225959A1
WO2023225959A1 PCT/CN2022/095340 CN2022095340W WO2023225959A1 WO 2023225959 A1 WO2023225959 A1 WO 2023225959A1 CN 2022095340 W CN2022095340 W CN 2022095340W WO 2023225959 A1 WO2023225959 A1 WO 2023225959A1
Authority
WO
WIPO (PCT)
Prior art keywords
bandwidth
bwp
offset value
bandwidth part
frequency domain
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/095340
Other languages
English (en)
Chinese (zh)
Inventor
王沙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Transsion Holdings Co Ltd
Original Assignee
Shenzhen Transsion Holdings Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Transsion Holdings Co Ltd filed Critical Shenzhen Transsion Holdings Co Ltd
Priority to PCT/CN2022/095340 priority Critical patent/WO2023225959A1/fr
Publication of WO2023225959A1 publication Critical patent/WO2023225959A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/20—Negotiating bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • This application relates to the field of communication technology, and specifically to a processing method, communication equipment and storage medium.
  • the maximum bandwidth set is 5MHz, that is, the maximum bandwidth of the business channel is 5MHz.
  • 20MHz bandwidth is used for the synchronization signal and physical broadcast channel block (Synchronization Signal and PBCh block, SSB) and the control resource set (CORESET), while the maximum service channel
  • the bandwidth is 5MHz, how to determine the bandwidth occupied by the service channel so as to schedule or transmit the service channel is an urgent technical problem that needs to be solved.
  • this application provides a processing method, communication equipment and storage medium to realize the scheduling or transmission of business channels.
  • this application provides a processing method that can be applied to terminal devices (such as mobile phones), including:
  • the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.
  • the first message includes at least one of the following: a first starting resource block position, a first carrier offset value, a second starting resource block position, a second carrier offset value, and a third frequency offset. value, the size of the reference bandwidth part, and indication information.
  • the first message is a main system information block and/or system message
  • the system messages include radio resource control messages and/or system information blocks.
  • determining the target bandwidth portion occupied by the traffic channel and/or the reference signal on the reference bandwidth portion according to the first message and the preset bandwidth size includes:
  • the target bandwidth part is determined on the reference bandwidth part according to the frequency domain starting position and/or the preset bandwidth size.
  • the frequency domain starting position of the traffic channel and/or the reference signal is at least one of the following:
  • a first frequency domain starting position, the first frequency domain starting position is: starting from the common reference point of the resource grid, passing through the first starting resource block position, the first carrier offset value and the The position after the third frequency offset value;
  • a second frequency domain starting position, the second frequency domain starting position is: starting from the common reference point of the resource grid, passing through the second starting resource block position and the second carrier offset value subsequent position;
  • a third frequency domain starting position which is a position starting from the frequency domain starting position of the synchronization signal block and passing through the first frequency offset value and the second frequency offset value.
  • the first message includes an index
  • the method further includes:
  • the first frequency offset value and/or the second frequency offset value are determined according to the index and the subcarrier spacing between the synchronization signal block and the reference bandwidth part.
  • the time domain position of the reference bandwidth part is determined based on the delay parameter.
  • the reference bandwidth part includes N candidate bandwidth parts, and the size of each candidate bandwidth part is the preset bandwidth size; according to the first message and the preset bandwidth size, in the reference Determine the target bandwidth portion occupied by the traffic channel and/or reference signal on the bandwidth portion, including:
  • the indication information determine the target bandwidth part among the N candidate bandwidth parts
  • the N Floor (size of the reference bandwidth part/the preset bandwidth size).
  • the number of resource blocks included in each of the candidate bandwidth parts is M, and the indication information indicates that the target bandwidth part is the kth candidate bandwidth part among the N candidate bandwidth parts. ; Including at least one of the following:
  • the target bandwidth part is the bandwidth part corresponding to the L+(k-1)*M+1th resource block to the L+k*Mth resource block in the reference bandwidth part;
  • the target bandwidth part includes the L+k+N*ith resource block in the reference bandwidth part;
  • the k is a positive integer greater than or equal to 1 and less than or equal to the N, the i is 0, 1, 2, ..., M-1 in sequence, and the M is a positive integer, so L is the number of resource blocks included between the lower edge of the reference bandwidth part and the first candidate bandwidth part.
  • this application provides a processing method that can be applied to terminal devices (such as mobile phones), including:
  • the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.
  • the frequency domain starting position and/or the bandwidth size are determined based on the first message.
  • the first message is a main system information block and/or a system message.
  • the system message includes a radio resource control message and/or a system information block.
  • the first message includes at least one of the following:
  • the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, the third frequency offset value, the size of the reference bandwidth part, and the indication information are provided.
  • the frequency domain starting position of the traffic channel and/or the reference signal is at least one of the following:
  • a first frequency domain starting position, the first frequency domain starting position is: starting from the common reference point of the resource grid, passing through the first starting resource block position, the first carrier offset value and the The position after the third frequency offset value;
  • a second frequency domain starting position, the second frequency domain starting position is: starting from the common reference point of the resource grid, passing through the second starting resource block position and the second carrier offset value subsequent position;
  • a third frequency domain starting position, the third frequency domain starting position is: starting from the frequency domain starting position of the synchronization signal block, the position after the first frequency offset value and the second frequency offset value;
  • the first message includes an index
  • the method further includes:
  • the first frequency offset value and/or the second frequency offset value are determined according to the index and the subcarrier spacing between the synchronization signal block and the reference bandwidth part.
  • the target bandwidth part occupied by the traffic channel and/or the reference signal is determined on the reference bandwidth part according to the frequency domain starting position and/or bandwidth size of the traffic channel and/or the reference signal, include:
  • the target bandwidth portion is determined over a second bandwidth portion.
  • the reference bandwidth part includes N candidate bandwidth parts, and the size of each candidate bandwidth part is the bandwidth size; the frequency domain starting position of the traffic channel and/or the reference signal is , at least one of bandwidth size and indication information, determining the target bandwidth portion occupied by the traffic channel and/or the reference signal on the reference bandwidth portion, including:
  • the indication information determine the target bandwidth part among the N candidate bandwidth parts
  • the N Floor (the size of the reference bandwidth part/the bandwidth size).
  • the number of resource blocks included in each of the candidate bandwidth parts is M, and the indication information indicates that the target bandwidth part is the kth candidate bandwidth part among the N candidate bandwidth parts. ; Including at least one of the following:
  • the target bandwidth part is the bandwidth part corresponding to the L+(k-1)*M+1th resource block to the L+k*Mth resource block in the reference bandwidth part;
  • the target bandwidth part includes the L+k+N*ith resource block in the reference bandwidth part;
  • the k is a positive integer greater than or equal to 1 and less than or equal to the N, the i is 0, 1, 2, ..., M-1 in sequence, and the M is a positive integer, so L is the number of resource blocks included between the lower edge of the reference bandwidth part and the first candidate bandwidth part.
  • this application provides a processing method that can be applied to network equipment (such as base stations), including:
  • the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.
  • the first message is a main system information block and/or a system message.
  • the system message includes a radio resource control message and/or a system information block.
  • the first message includes at least one of the following: a first starting resource block position, a first carrier offset value, a second starting resource block position, a second carrier offset value, and a third frequency offset. value, the size of the reference bandwidth part, and indication information.
  • the size of the reference bandwidth part is greater than or equal to the preset bandwidth size.
  • the time domain position of the reference bandwidth part is determined based on the delay parameter.
  • the frequency domain starting position of the traffic channel and/or the reference signal is at least one of the following:
  • a first frequency domain starting position, the first frequency domain starting position is: starting from the common reference point of the resource grid, passing through the first starting resource block position, the first carrier offset value and the The position after the third frequency offset value;
  • a second frequency domain starting position, the second frequency domain starting position is: starting from the common reference point of the resource grid, passing through the second starting resource block position and the second carrier offset value subsequent position;
  • a third frequency domain starting position which is a position starting from the frequency domain starting position of the synchronization signal block and passing through the first frequency offset value and the second frequency offset value.
  • the first message also includes an index, and the index and the subcarrier interval between the synchronization signal block and the reference bandwidth part are used to indicate the first frequency offset value and/or the third frequency offset value. 2. Frequency offset value.
  • the reference bandwidth part includes N candidate bandwidth parts, and the size of each candidate bandwidth part is the preset bandwidth size; wherein:
  • the indication information indicates that the target bandwidth part is the k-th candidate bandwidth part among the N candidate bandwidth parts
  • the N Floor (the size of the reference bandwidth part/the preset bandwidth size), and the k is a positive integer greater than or equal to 1 and less than or equal to the N.
  • the number of resource blocks included in each of the candidate bandwidth parts is M, including at least one of the following:
  • the target bandwidth part is the bandwidth part corresponding to the L+(k-1)*M+1th resource block to the L+k*Mth resource block in the reference bandwidth part;
  • the target bandwidth part includes the L+k+N*ith resource block in the reference bandwidth part;
  • the k is a positive integer greater than or equal to 1 and less than or equal to the N, the i is 0, 1, 2, ..., M-1 in sequence, and the M is a positive integer, so L is the number of resource blocks included between the lower edge of the reference bandwidth part and the first candidate bandwidth part.
  • this application provides a processing device, including:
  • a determining module configured to determine the target bandwidth portion occupied by the business channel and/or the reference signal on the reference bandwidth portion according to the first message and the preset bandwidth size
  • the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.
  • this application provides a processing device, including:
  • Determining module configured to determine the occupied area of the traffic channel and/or the reference signal on the reference bandwidth part according to at least one of the frequency domain starting position, bandwidth size, and indication information of the traffic channel and/or the reference signal. part of the target bandwidth;
  • the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.
  • this application provides a processing device, including:
  • a sending module configured to send a first message, the first message being used to indicate the frequency domain starting position of the traffic channel and/or the reference signal on the reference bandwidth part;
  • the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.
  • this application provides a communication device, including: a memory and a processor;
  • the memory is used to store program instructions
  • the processor is configured to call program instructions in the memory to execute the processing method described in any one of the first to third aspects.
  • the present application provides a computer-readable storage medium, with a computer program stored on the storage medium; when the computer program is executed, the processing as described in any one of the first to third aspects is implemented. method.
  • the network device sends a first message to the terminal device.
  • the terminal device can determine the service channel and/or reference signal according to the first message and the preset bandwidth size.
  • the portion of the target bandwidth occupied to achieve scheduling or transmission of traffic channels and/or reference signals.
  • the location of the service channel and/or the reference signal can be determined based on the first message and the preset bandwidth size.
  • the occupied target bandwidth portion implements the scheduling or transmission of traffic channels and/or reference signals.
  • Figure 1 is a schematic diagram of the hardware structure of a terminal device provided by an embodiment of the present application.
  • FIG. 2 is a communication network system architecture diagram provided by an embodiment of the present application.
  • FIG. 3 is a signaling diagram 1 of the processing method provided by the embodiment of the present application.
  • FIG. 4 is a schematic diagram of the system bandwidth and reference BWP provided by the embodiment of the present application.
  • Figure 5 is a schematic diagram 1 of determining the target BWP provided by the embodiment of the present application.
  • Figure 6 is a schematic diagram 2 of determining the target BWP provided by the embodiment of the present application.
  • Figure 7 is a schematic diagram 3 of determining the target BWP provided by the embodiment of the present application.
  • Figure 8 is a schematic diagram 4 of determining the target BWP provided by the embodiment of the present application.
  • Figure 9 is a schematic diagram 4 of determining the target BWP provided by the embodiment of the present application.
  • Figure 10 is a schematic diagram 5 of determining the target BWP provided by the embodiment of the present application.
  • Figure 11 is a schematic diagram 6 of determining the target BWP provided by the embodiment of the present application.
  • Figure 12 is a schematic diagram 7 of determining the target BWP provided by the embodiment of the present application.
  • Figure 13 is a schematic diagram 8 of determining the target BWP provided by the embodiment of the present application.
  • Figure 14 is the second signaling diagram of the processing method provided by the embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of the processing device provided by the embodiment of the present application.
  • Figure 16 is a schematic structural diagram 2 of the processing device provided by the embodiment of the present application.
  • Figure 17 is a schematic structural diagram three of the processing device provided by the embodiment of the present application.
  • Figure 18 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • first, second, third, etc. may be used herein to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • word “if” as used herein may be interpreted as “when” or “when” or “in response to determining.”
  • singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context indicates otherwise.
  • A, B, C means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C"; another example is, “ A, B or C” or "A, B and/or C” means "any of the following: A; B; C; A and B; A and C; B and C; A and B and C". Exceptions to this definition occur only when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some manner.
  • each step in the flow chart in the embodiment of the present application is displayed in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated in this article, the execution of these steps is not strictly limited in order, and they can be executed in other orders. Moreover, at least some of the steps in the figure may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and their execution order is not necessarily sequential. may be performed in turn or alternately with other steps or sub-steps of other steps or at least part of stages.
  • the words “if” or “if” as used herein may be interpreted as “when” or “when” or “in response to determination” or “in response to detection.”
  • the phrase “if determined” or “if (stated condition or event) is detected” may be interpreted as “when determined” or “in response to determining” or “when (stated condition or event) is detected )” or “in response to detecting (a stated condition or event)”.
  • step codes such as S31 and S32 are used for the purpose of describing the corresponding content more clearly and concisely, and do not constitute a substantial restriction on the sequence. Those skilled in the art may S32 will be executed first and then S31, etc., but these should be within the protection scope of this application.
  • the communication device in this application may be a terminal device (such as a mobile phone) or a network device (such as a base station).
  • a terminal device such as a mobile phone
  • a network device such as a base station
  • the terminal device may be a mobile terminal, and the mobile terminal may be implemented in various forms.
  • the mobile terminal described in this application may include mobile phones, tablet computers, notebook computers, PDAs, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable Media Player, PMP), navigation devices, Mobile terminals such as wearable devices, smart bracelets, and pedometers, as well as fixed terminals such as digital TVs and desktop computers.
  • a mobile terminal will be taken as an example.
  • the structure according to the embodiments of the present application can also be applied to fixed-type terminals.
  • the mobile terminal 100 may include: an RF (Radio Frequency, radio frequency) unit 101, a WiFi module 102, an audio output unit 103, and a /V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111 and other components.
  • RF Radio Frequency, radio frequency
  • the radio frequency unit 101 can be used to receive and send information or signals during a call. Specifically, after receiving the downlink information of the base station, it is processed by the processor 110; in addition, the uplink data is sent to the base station.
  • the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • the radio frequency unit 101 can also communicate with the network and other devices through wireless communication.
  • the above wireless communication can use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication, Global Mobile Communications System), GPRS (General Packet Radio Service, General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000 , Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access, Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access, Time Division Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division) Duplexing-Long Term Evolution, Frequency Division Duplex Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution, Time Division Duplex Long Term Evolution) and 5G, etc.
  • GSM Global System of Mobile communication, Global Mobile Communications System
  • GPRS General Packet Radio Service
  • CDMA2000 Code Division Multiple Access 2000
  • WCDMA Wideband Code Division Multiple Access
  • TD-SCDMA Time Division-Synchronous Code Division Multiple Access, Time Division Synchronous Code
  • WiFi is a short-distance wireless transmission technology.
  • the mobile terminal can help users send and receive emails, browse web pages, access streaming media, etc. through the WiFi module 102. It provides users with wireless broadband Internet access.
  • FIG. 1 shows the WiFi module 102, it can be understood that it is not a necessary component of the mobile terminal and can be omitted as needed without changing the essence of the invention.
  • the audio output unit 103 may, when the mobile terminal 100 is in a call signal receiving mode, a call mode, a recording mode, a voice recognition mode, a broadcast receiving mode, etc., receive the audio signal received by the radio frequency unit 101 or the WiFi module 102 or store it in the memory 109 The audio data is converted into audio signals and output as sound. Furthermore, the audio output unit 103 may also provide audio output related to a specific function performed by the mobile terminal 100 (eg, call signal reception sound, message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, or the like.
  • the A/V input unit 104 is used to receive audio or video signals.
  • the A/V input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042.
  • the graphics processor 1041 can process still pictures or images obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. Video image data is processed.
  • the processed image frames may be displayed on the display unit 106.
  • the image frames processed by the graphics processor 1041 may be stored in the memory 109 (or other storage media) or sent via the radio frequency unit 101 or WiFi module 102.
  • the microphone 1042 can receive sounds (audio data) via the microphone 1042 in operating modes such as a phone call mode, a recording mode, a voice recognition mode, and the like, and can process such sounds into audio data.
  • the processed audio (voice) data can be converted into a format that can be sent to a mobile communication base station via the radio frequency unit 101 for output in a phone call mode.
  • Microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated in the process of receiving and transmitting audio signals.
  • the mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor.
  • the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light.
  • the proximity sensor can turn off the display when the mobile terminal 100 moves to the ear. Panel 1061 and/or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three axes). It can detect the magnitude and direction of gravity when stationary.
  • It can be used to identify applications of mobile phone posture (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for the mobile phone, it can also be configured with fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, Other sensors such as thermometers and infrared sensors will not be described in detail here.
  • the display unit 106 is used to display information input by the user or information provided to the user.
  • the display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the user input unit 107 may be used to receive input numeric or character information, and generate key signal input related to user settings and function control of the mobile terminal.
  • the user input unit 107 may include a touch panel 1071 and other input devices 1072.
  • the touch panel 1071 also known as a touch screen, can collect the user's touch operations on or near the touch panel 1071 (for example, the user uses a finger, stylus, or any suitable object or accessory on or near the touch panel 1071 operation), and drive the corresponding connection device according to the preset program.
  • the touch panel 1071 may include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device and converts it into contact point coordinates , and then sent to the processor 110, and can receive the commands sent by the processor 110 and execute them.
  • the touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the user input unit 107 may also include other input devices 1072.
  • other input devices 1072 may include but are not limited to one or more of physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, joysticks, etc., which are not specifically discussed here. limited.
  • the touch panel 1071 can cover the display panel 1061.
  • the touch panel 1071 detects a touch operation on or near it, it is transmitted to the processor 110 to determine the type of the touch event, and then the processor 110 determines the type of the touch event according to the touch event.
  • the type provides corresponding visual output on the display panel 1061.
  • the touch panel 1071 and the display panel 1061 are used as two independent components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated. The implementation of the input and output functions of the mobile terminal is not limited here.
  • the interface unit 108 serves as an interface through which at least one external device can be connected to the mobile terminal 100 .
  • external devices may include a wired or wireless headphone port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
  • the interface unit 108 may be used to receive input (eg, data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to connect between the mobile terminal 100 and an external device. Transfer data between devices.
  • Memory 109 may be used to store software programs as well as various data.
  • the memory 109 may mainly include a storage program area and a storage data area.
  • the storage program area may store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), etc.;
  • the storage data area may Store data created based on the use of the mobile phone (such as audio data, phone book, etc.), etc.
  • memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
  • the processor 110 is the control center of the mobile terminal, using various interfaces and lines to connect various parts of the entire mobile terminal, by running or executing software programs and/or modules stored in the memory 109, and calling data stored in the memory 109 , execute various functions of the mobile terminal and process data, thereby overall monitoring the mobile terminal.
  • the processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor.
  • the application processor mainly processes the operating system, user interface, application programs, etc., and modulation
  • the demodulation processor mainly handles wireless communications. It can be understood that the above modem processor may not be integrated into the processor 110 .
  • the mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components.
  • a power supply 111 such as a battery
  • the power supply 111 may be logically connected to the processor 110 through a power management system, thereby managing charging, discharging, and power consumption management through the power management system. and other functions.
  • the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described again here.
  • FIG. 2 is an architecture diagram of a communication network system provided by an embodiment of the present application.
  • the communication network system is an LTE system of universal mobile communication technology.
  • the LTE system includes UEs (User Equipment, User Equipment) connected in sequence. )201, E-UTRAN (Evolved UMTS Terrestrial Radio Access Network, Evolved UMTS Terrestrial Radio Access Network) 202, EPC (Evolved Packet Core, Evolved Packet Core Network) 203 and the operator's IP business 204.
  • UEs User Equipment, User Equipment
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • EPC Evolved Packet Core, Evolved Packet Core Network
  • UE 201 may be the above-mentioned terminal 100, which will not be described again here.
  • E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc.
  • eNodeB2021 can be connected to other eNodeB2022 through backhaul (for example, X2 interface), eNodeB2021 is connected to EPC203, and eNodeB2021 can provide access from UE201 to EPC203.
  • backhaul for example, X2 interface
  • EPC 203 may include MME (Mobility Management Entity, mobility management entity) 2031, HSS (Home Subscriber Server, home user server) 2032, other MME 2033, SGW (Serving Gate Way, service gateway) 2034, PGW (PDN Gate Way, packet data Network Gateway) 2035 and PCRF (Policy and Charging Rules Function, policy and charging functional entity) 2036, etc.
  • MME2031 is a control node that processes signaling between UE201 and EPC203, and provides bearer and connection management.
  • HSS2032 is used to provide some registers to manage functions such as the home location register (not shown in the figure), and to save some user-specific information about service characteristics, data rates, etc. All user data can be sent through SGW2034.
  • PGW2035 can provide IP address allocation and other functions for UE 201.
  • PCRF2036 is the policy and charging control policy decision point for business data flows and IP bearer resources. It is the policy and charging execution function. The unit (not shown) selects and provides available policy and charging control decisions.
  • IP services 204 may include the Internet, Intranet, IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) or other IP services.
  • IMS IP Multimedia Subsystem, IP Multimedia Subsystem
  • FIG 3 is a signaling diagram 1 of the processing method provided by the embodiment of the present application. As shown in Figure 3, the method may include:
  • the network device sends the first message to the terminal device.
  • the terminal device in the embodiment of the present application may be an ordinary device or a light-capable device.
  • the light-capable device may include, for example, household appliances such as refrigerators, televisions, and air conditioners.
  • wearable devices such as smart watches and sports bracelets.
  • smart industrial equipment such as smart grids and smart meters, as well as low-power/low-complexity/low-cost/low-performance smartphones and some feature phones.
  • Common devices include, for example, smartphones, smart cars, etc.
  • the difference between light-capability devices and ordinary devices is not limited to the difference in device type.
  • ordinary devices in a low-power or low-performance state can also be used as light-capability devices.
  • the difference mainly lies in the current bandwidth and data rate of the device.
  • the terminal device in the embodiment of this application is a light-capability device.
  • a light-capability device if its wireless radio frequency bandwidth is maximum 20MHz and the bandwidth occupied by SSB and CORESET#0 is 20MHz, but in its business channel If one or more target bandwidth parts (BandWidth Part, BWP) are less than or equal to 20MHz, it is necessary to determine the position of the target BWP occupied by the service channel in the reference BWP occupied by SBB and CORESET#0.
  • BWP BandWidth Part
  • the network device sends the first message to the terminal device, and the terminal device schedules the service channel based on the first message.
  • the terminal device determines the target BWP occupied by the service channel and/or the reference signal on the reference BWP according to the first message and the preset bandwidth size.
  • the size of the target BWP is fixed, that is, the preset bandwidth size.
  • the preset bandwidth size may be, for example, 5 MHz, or may be any bandwidth size less than 5 MHz.
  • the size of the reference BWP is greater than or equal to 5MHz.
  • the size of the reference BWP can be 20MHz.
  • the service channel includes at least any one of a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) and a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH).
  • PUSCH Physical Uplink Shared Channel
  • PDSCH Physical Downlink Shared Channel
  • the reference signal includes a Demodulation Reference Signal (DMRS) for PDSCH, a DMRS for Physical Downlink Control Channel (PDCCH), and a Channel State Information Reference Signal (Channel State Information- Reference Signal, CSI_RS), Phase Tracking Reference Signal (PTRS), Channel Sounding Reference Signal (Sounding Reference Signal, SRS).
  • DMRS Demodulation Reference Signal
  • PDCH Physical Downlink Control Channel
  • CSI_RS Channel State Information Reference Signal
  • PTRS Phase Tracking Reference Signal
  • SRS Sounding Reference Signal
  • the reference BWP is a bandwidth portion of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier in at least one carrier is in an inactive state.
  • FIG. 4 is a schematic diagram of the system bandwidth and reference BWP provided by the embodiment of the present application. As shown in Figure 4, the system bandwidth is a total large bandwidth, including 22 RBs, namely RB0 to RB21.
  • the bandwidth part corresponding to at least one carrier is configured on the system bandwidth.
  • 4 carriers are configured on the system bandwidth, namely carrier 1, carrier 2, carrier 3 and carrier 4.
  • Each carrier is indicated by the arrow in Figure 4.
  • the bandwidth part of the carrier can be in an activated state or in an inactive state.
  • the activated bandwidth part can be used for reference signal transmission, data transmission, etc.
  • at least one carrier of the system bandwidth has a bandwidth part that is in an inactive state, and one or more carriers may have a bandwidth part that is activated.
  • carrier 1 and carrier 3 are in the activated state
  • carrier 2 and carrier 4 are in the inactive state.
  • the reference BWP in the embodiment of this application is the bandwidth part of one of at least one carrier on the system bandwidth, and the reference BWP is in an active state.
  • the reference BWP is the bandwidth portion of carrier 3. That is, the reference BWP in the embodiment of this application is related to the carriers on the system bandwidth, and the reference BWP is the bandwidth part of one of the active carriers among at least one carrier on the system bandwidth.
  • the frequency domain starting position of the service channel and/or the reference signal on the reference BWP can be determined based on the first message. According to the frequency domain starting position and /Or preset the bandwidth size to determine the target BWP on the BWP.
  • the network device sends a first message to the terminal device.
  • the terminal device can determine the service channel and/or reference signal according to the first message and the preset bandwidth size.
  • the occupied target BWP enables scheduling or transmission of traffic channels and/or reference signals.
  • the position of the target BWP in the reference BWP can be determined based on the first message and the preset bandwidth size, realizing the realization of the service channel and/or or the scheduling or transmission of reference signals.
  • a solution is introduced in which the target BWP occupied by the traffic channel and/or the reference signal can be determined through the first message and the preset bandwidth size, thereby realizing the scheduling or transmission of the traffic channel and/or the reference signal.
  • the first message and the solution of how to determine the target BWP based on the first message will be introduced in detail below with reference to specific embodiments.
  • the first message includes a master system information block (Master Information Block, MIB) and/or a system message.
  • MIB Master Information Block
  • the first frequency offset value between the SSB and CORESET#0, and the second frequency offset value between CORESET#0 and the frequency domain starting position of the traffic channel may be determined through the MIB. Then, the frequency domain starting position of the traffic channel is determined according to the first frequency offset value and the second frequency offset value.
  • CORESET#0 is the reference BWP.
  • a new solution is provided to determine the frequency domain starting position of the service channel through the existing field index in the MIB.
  • the existing field index in the MIB is PDCCH-ConfigSIB1----->controlResourceSetZero.
  • the embodiment of the present application provides a method to determine the first field index based on the existing field index in the MIB.
  • the scheme of the first frequency offset value and the second frequency offset value please refer to Table 1 to Table 4 below for details.
  • Table 1 illustrates a solution for determining the first frequency offset value and the second frequency offset value based on the MIB.
  • Table 2 illustrates a solution for determining the first frequency offset value and the second frequency offset value based on the MIB.
  • Table 3 illustrates a solution for determining the first frequency offset value and the second frequency offset value based on the MIB.
  • Table 4 illustrates a solution for determining the first frequency offset value and the second frequency offset value based on the MIB.
  • Table 4 above is just an example of how to determine the offset.
  • the specific value can be determined according to the actual application scenario, such as the specific pre-stored bandwidth size of the terminal device, the number of terminal devices, etc.
  • the row index from the field PDCCH-ConfigSIB1----->controlResourceSetZero in the MIB, and then determine the first frequency offset value and/or the second frequency according to the row index and the subcarrier spacing of the SSB and the reference BWP offset value.
  • the first frequency offset value is the frequency offset value between the SSB and the reference BWP
  • the second frequency offset value is the frequency offset value between the reference BWP and the frequency domain starting position of the traffic channel.
  • the preset corresponding relationships can be found in Table 1 to Table 4 above for examples. After the index is determined according to the MIB, it can be determined according to the subcarrier spacing between the SSB and the reference BWP which table in Table 1 to Table 4 indicates the preset corresponding relationship, so that the first frequency offset value can be further determined. and a second frequency offset value.
  • the reference BWP in the embodiment of this application is CORESET#0.
  • the reference BWP can be determined based on the first frequency offset value.
  • the second frequency offset value is the frequency offset value between the reference BWP and the frequency domain starting position of the service channel. Therefore, the frequency domain starting position of the service channel can be determined on the reference BWP according to the second frequency offset value. That is, at this time, the frequency domain starting position of the traffic channel is the third frequency domain starting position, and the third frequency domain starting position is starting from the frequency domain starting position of the SSB, passing through the first frequency offset value and the second frequency The position after the offset value.
  • the subcarrier spacing of SSB and CORESET#0 is ⁇ 30,15 ⁇ KHz
  • the default corresponding relationship is indicated by the above Table 1.
  • the field PDCCH-ConfigSIB1----->controlResourceSetZero in the MIB has a value of 0, that is, the row index is 0.
  • the first frequency offset value is 2 resource blocks (Resource Block, RB)
  • the second frequency offset value is 10 RBs.
  • the frequency domain position occupied by CORESET#0 is the frequency domain position occupied by the reference BWP. Therefore, according to Table 1 above, when the index is 0, the bandwidth occupied by the reference BWP includes 48 RBs.
  • the preset correspondence in the examples of Tables 1 to 4 may not include the correspondence between the index and the second frequency offset value, that is, the fifth column may not be included in Tables 1 to 4. That is, in addition to determining the second frequency offset value offset2 through the index in the MIB, it can also be the second preset value agreed between the terminal device and the network device, or it can be configured for the network device through the downlink control information (DCI).
  • the second frequency offset value offset2 or is a value determined by the terminal device from a limited value set according to the channel state.
  • the terminal device can select the second frequency offset value to ensure that the target BWP is close to the reference If the channel status is poor at the center or edge position of the BWP, the terminal device can select a second frequency offset value to make the target BWP close to the center position of the reference BWP.
  • the channel status may be determined based on RSRP or RSRQ.
  • the second frequency offset value offset2 may be a second preset value.
  • the second preset value may be a fixed value agreed between the network device and the terminal device, or may be a value determined from the channel state of the terminal device. A numerical value selected from a finite set of values, etc.
  • the second frequency offset value is a value configured through DCI.
  • a 2-bit field may be added to the DCI to indicate the size of the second frequency offset value offset2.
  • the newly added 2-bit field in the above DCI and the corresponding relationship between the 2-bit field and the value of offset2 are only an example and do not constitute an actual limitation.
  • a 3-bit field, a 4-bit field, etc. can be added to the DCI to indicate the size of the second frequency offset value offset2.
  • the corresponding relationship between the bit field in the DCI and the value of the second frequency offset value offset2 can also be based on Requires setting.
  • the frequency domain starting position of the service channel can be determined based on the first frequency offset value and the second frequency offset value. This process will be introduced below with reference to Figure 5.
  • Figure 5 is a schematic diagram 1 of determining the target BWP provided by the embodiment of the present application. As shown in Figure 5, the left side is the bandwidth occupied by SSB. The frequency domain starting position of the bandwidth occupied by SSB is assumed to be known, that is, in Figure 5 At L1.
  • the first frequency offset value offset1 is the frequency offset between SSB and the reference BWP occupied by CORESET#0, therefore, according to the first frequency offset value offset1 and SSB
  • the frequency domain starting position of the occupied bandwidth can be obtained by the frequency domain starting position of the reference BWP occupied by CORESET#0, which is L0 in Figure 5.
  • the size of the reference BWP occupied by CORESET#0 is 48 RBs
  • the frequency domain starting position of the reference BWP occupied by CORESET#0 is L0 in Figure 5. Therefore, according to the location of CORESET#0
  • the size of the occupied reference BWP and the corresponding starting position in the frequency domain can determine the reference BWP occupied by CORESET#0 (from L0 to L4 in Figure 5), that is, RB0-RB47 in Figure 5, a total of 48 RBs.
  • Figure 5 illustrates the scenario of using CORESET#0 as the reference BWP in initial access. It is necessary to determine the target BWP occupied by the service channel on the reference BWP determined by CORESET#0.
  • CORESET#0 which is the frequency domain starting position of the reference BWP, is determined based on the first frequency offset value and the frequency domain starting position of the bandwidth occupied by the SSB, and then based on the second frequency offset value offset2 and the reference BWP
  • the starting position of the frequency domain can determine the starting position of the frequency domain of the service channel.
  • the second frequency offset value is 10 RBs. Therefore, according to the second frequency offset value offset2, it can be determined that the frequency domain starting position of the target BWP occupied by the service channel is as shown in Figure 5 At L2, the second frequency offset value offset2 between the frequency domain starting position of the target BWP occupied by the traffic channel and the frequency domain starting position of the reference BWP is 10 RBs.
  • the size of the target BWP occupied by the traffic channel is the preset bandwidth size
  • the target BWP occupied by the service channel can be determined on the reference BWP, that is, the target BWP occupied by the service channel is the bandwidth corresponding to the preset bandwidth size starting from the corresponding third frequency domain starting position.
  • a new mapping table (i.e., Table 1 to Table 4) is provided through the existing field index in the MIB, which can be implemented without changing the size and meaning of the signaling fields in the MIB.
  • the first frequency offset value and the number of RBs occupied by CORESET#0 can be determined in the above mapping table according to the field index in the MIB, thereby determining the bandwidth corresponding to CORESET#0 and the bandwidth corresponding to CORESET#0. That is, the target BWP occupied by the business channel of ordinary equipment.
  • the embodiment of the present application adds a column to the original mapping table to reflect the relationship between the index and the second frequency offset value.
  • the first frequency offset value, the number of RBs occupied by CORESET#0, and the second frequency offset value can be determined in the above mapping table according to the field index in the MIB.
  • the bandwidth corresponding to CORESET#0 that is, the reference bandwidth part in the initial access, can be determined according to the first frequency offset value and the number of RBs occupied by CORESET#0.
  • the frequency domain starting position of the service channel of the light-capable device can be determined based on the starting position of the reference bandwidth part and the second frequency offset value, and at the same time, the reference BWP determined in CORESET#0 is combined with the preset bandwidth size of the target bandwidth part. Determine the location of the target BWP.
  • the frequency domain starting position of the target BWP occupied by the service channel is determined based on the index in the MIB, and then based on the frequency domain starting position of the target BWP occupied by the service channel and the preset bandwidth size, in Refer to the BWP solution for determining the target BWP occupied by the service channel.
  • the first message may also include system messages. The following will introduce a solution for determining the target BWP occupied by the service channel based on the system messages.
  • the system message includes the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, the third frequency offset value and the size of the reference BWP.
  • At least one item, the frequency domain starting position of the traffic channel can be determined according to at least one of the above items.
  • the system message includes a Radio Resource Control (Radio Resource Control, RRC) message and/or a System Information Block (System Information Block, SIB). That is, the RRC message includes at least one of the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, the third frequency offset value and the size of the reference BWP. item, and/or the SIB includes the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, the third frequency offset value and the size of the reference BWP at least one of.
  • RRC Radio Resource Control
  • SIB System Information Block
  • the size of the reference BWP is greater than or equal to the preset bandwidth size.
  • the reference BWP is a first BWP or a second BWP.
  • the first BWP is a BWP in the same time slot as the initial BWP
  • the second BWP is a BWP with a time slot offset from the initial BWP.
  • the size of the first BWP is greater than or equal to the preset bandwidth size
  • the size of the second BWP is greater than or equal to the preset bandwidth size
  • the terminal device determines the frequency domain starting position of the service channel according to the first message, and then determines the target occupied by the service channel on the first BWP according to the frequency domain starting position of the service channel and/or the preset bandwidth size. BWP.
  • the terminal device determines the frequency domain starting position of the service channel according to the first message, and then determines the target occupied by the service channel on the second BWP according to the frequency domain starting position of the service channel and/or the preset bandwidth size. BWP.
  • the solution of determining the target BWP occupied by the service channel on the first BWP when the BWP is the first BWP is introduced.
  • the system message includes at least one of the first starting resource block position O carrier , the first carrier offset value RB start and the third frequency offset value offset3.
  • the terminal device can use the first starting resource according to At least one of the block position O carrier , the first carrier offset value and the third frequency offset value determines the frequency domain starting position of the traffic channel.
  • the third frequency offset value offset3 can also be a third preset value agreed between the terminal device and the network device, or configured through DCI for the network device.
  • the third frequency offset value offset3 can also be a third preset value agreed between the terminal device and the network device, or configured through DCI for the network device.
  • the third frequency offset value offset3 may be a third preset value.
  • the third preset value may be a fixed value agreed between a network device and a terminal device, or may be a value based on the channel status of the terminal device. A numerical value selected from a finite set of values, etc.
  • the third frequency offset value is a value configured through DCI.
  • a 2-bit field may be added to the DCI to indicate the size of the third frequency offset value offset3.
  • the newly added 2-bit field in the above DCI and the corresponding relationship between the 2-bit field and the value of offset3 are only an example and do not constitute an actual limitation.
  • a 3-bit field, a 4-bit field, etc. may be added to the DCI to indicate the size of the third frequency offset value offset3.
  • the corresponding relationship between the bit field in the DCI and the value of the third frequency offset value offset3 may also be based on Requires setting.
  • the first starting resource block position O carrier and the first carrier offset value RB start are used to determine the frequency domain starting position of the first BWP, and the frequency domain starting position of the first BWP is the common resource grid.
  • the reference point starts passing through the first starting resource block position O carrier and the position after the first carrier offset value RB start .
  • the size of the first BWP is greater than or equal to the preset bandwidth size.
  • the preset bandwidth size is 5MHz
  • the size of the first BWP is greater than or equal to 5MHz, such as 10MHz, 20MHz, and so on.
  • the third frequency offset value is a frequency offset between the first BWP and the frequency domain starting position of the traffic channel.
  • the traffic channel may be determined based on the frequency domain starting position of the first BWP and the third frequency offset value. Frequency domain starting position. Then, based on the frequency domain starting position of the service channel and the preset bandwidth size, the target BWP occupied by the service channel is determined on the first BWP.
  • Figure 6 is a second schematic diagram of determining the target BWP provided by the embodiment of the present application. As shown in Figure 6, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start and the third frequency offset value offset3.
  • the terminal device After receiving the system message, the terminal device The frequency domain starting position of the first BWP can be determined based on the position O carrier and the first carrier offset value RB start .
  • the frequency domain starting position of the first BWP is starting from the common reference point of the resource grid (ie, L0 in Figure 6), passing through the first starting resource block position O carrier and the first carrier offset value
  • the position after RB start is L2 in Figure 6, where the offset between L0 and L1 is indicated by the first starting resource block position, and the offset between L1 and L2 is indicated by the first carrier offset value.
  • the first BWP is the frequency band corresponding to L2 to L5 in Figure 6 .
  • the frequency domain starting position of the service channel is L3 in Figure 6, and the frequency domain starting position of the service channel is The position starting from the frequency domain starting position of the first BWP and passing through the third frequency offset value.
  • the frequency domain starting position of the service channel is the first frequency domain starting position, that is, starting from the common reference point of the resource grid and passing through the first starting resource block position, the first carrier offset value and the third frequency The position after the offset value.
  • the target BWP occupied by the service channel can be determined on the first BWP according to the frequency domain starting position of the service channel and the preset bandwidth size, as indicated by the shaded part in Figure 6, the target BWP BWP is the frequency band corresponding to L3 to L4, and its bandwidth is 5MHz.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap and the second carrier offset value RB start - At least one item in redcap, the terminal device can be based on the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap and the second carrier offset value RB start - At least one item in redcap determines the frequency domain starting position of the target BWP occupied by the traffic channel.
  • the first starting resource block position and the first carrier offset value are used to determine the frequency domain starting position of the first BWP.
  • the frequency domain starting position of the first BWP is starting from the common reference point of the resource grid.
  • the first starting resource block position and the position after the first carrier offset value are used to determine the frequency domain starting position of the first BWP.
  • the size of the first BWP is greater than or equal to the preset bandwidth size.
  • the preset bandwidth size is 5MHz
  • the size of the first BWP is greater than or equal to 5MHz, such as 10MHz, 20MHz, and so on. According to the frequency domain starting position of the first BWP and the size of the first BWP, the bandwidth where the first BWP is located can be determined.
  • the second starting resource block position and the second carrier offset value are used to determine the frequency domain starting position of the bandwidth occupied by the service channel.
  • the frequency domain starting position of the bandwidth occupied by the service channel is the slave resource network.
  • the common reference point of the grid starts passing through the second starting resource block position and the position after the second carrier offset value.
  • the size of the target BWP occupied by the traffic channel is a preset bandwidth size, and the preset bandwidth size may be, for example, 5 MHz or a bandwidth size less than 5 MHz.
  • the bandwidth may be determined based on the second starting resource block position, the second carrier offset value, and the second starting resource block position. and the preset bandwidth size, determine the target BWP occupied by the traffic channel on the first BWP and the target BWP is located at the reference BWP.
  • FIG 7 is a schematic diagram 3 of determining the target BWP provided by the embodiment of the present application.
  • L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap and the second carrier offset value RB start -redcap,
  • the terminal device can determine the frequency domain starting position of the first BWP based on the first starting resource block position O carrier and the first carrier offset value RB start .
  • the frequency domain starting position of the first BWP is starting from the common reference point of the resource grid (ie, L0 in Figure 7), passing through the first starting resource block position O carrier and the first carrier offset value
  • the position after RB start that is, L2 in Figure 7, where the offset between L0 and L1 is indicated by the first starting resource block position O carrier , and the offset between L1 and L2 is indicated by the first carrier offset value RB start instruction. Since the size of the first BWP is known, for example, 20 MHz, after determining the frequency domain starting position of the first BWP, the bandwidth where the first BWP is located can be determined based on the size of the first BWP, that is, L2 in Figure 7 to the corresponding frequency band at L6.
  • the frequency domain starting position of the service channel can be determined according to the second starting resource block position O carrier -redcap and the second carrier offset value RB start -redcap.
  • the frequency domain starting position of the service channel is The second frequency domain starting position is the position starting from the common reference point of the resource grid and passing through the second starting resource block position O carrier -redcap and the second carrier offset value RB start -redcap, that is, in Figure 7 At L4.
  • the offset between L0 and L3 is indicated by the second start resource block position O carrier -redcap, and the offset between L3 and L4 is indicated by the second carrier offset value RB start -redcap
  • the target BWP occupied by the service channel can be determined on the first BWP according to the frequency domain starting position of the service channel and the preset bandwidth size, as shown in the shaded part in Figure 7.
  • the target BWP occupied by the channel is the frequency band corresponding to L4 to L5 in Figure 7, and its size may be, for example, 5 MHz.
  • the solution of determining the target BWP occupied by the traffic channel on the first BWP when the BWP is the first BWP is introduced.
  • the following will introduce a solution for determining the target BWP occupied by the service channel on the second BWP when the BWP is the second BWP.
  • the second BWP is a separate BWP#
  • the switching time, that is, K0 needs to be greater than or equal to a certain preset value, and K0 is the delay parameter.
  • the second BWP is a separate BWP#
  • the switching time, that is, K2 needs to be greater than or equal to a certain preset value, and K2 is the delay parameter.
  • the time domain position of the second BWP can be determined according to the delay parameter, and the frequency domain position of the second BWP can be determined according to the system message.
  • the system message includes at least one of the first starting resource block position O carrier , the first carrier offset value RB start and the size of the BWP.
  • the terminal device can determine the first starting resource block position O carrier according to the first starting resource block position O carrier , at least one of the first carrier offset value RB start and the size of the BWP can determine the frequency domain starting position of the second BWP, and the frequency domain starting position of the second BWP is the frequency domain starting position of the service channel position, the size of the second BWP is the preset bandwidth size, and the second BWP is the target BWP occupied by the service channel.
  • FIG 8 is a schematic diagram of determining the target BWP provided by the embodiment of the present application. As shown in Figure 8, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the frequency domain starting position of the second BWP is the position starting from the common reference point of the resource grid and passing through the first starting resource block position O carrier and the first carrier offset value RB start , that is, Figure 8
  • the time domain position of the second BWP is the time domain position determined according to the delay parameter, where the offset between L0 and L1 is indicated by the first starting resource block position O carrier , and the offset between L1 and L2 The shift is indicated by the first carrier offset value RB start .
  • the delay parameter is K0, and K0 is the delay between PDSCH and PDCCH.
  • the delay parameter is K2
  • K2 is the delay between PUSCH and PDCCH.
  • the size of the second BWP is the size of the reference BWP configured in the system message.
  • the second BWP is also the target BWP.
  • the delay parameter there is a delay between the traffic channel and the PDCCH.
  • the traffic channel and the PDCCH can overlap in the frequency domain, or they can be located in different frequency domain positions.
  • the preset bandwidth size is 5 MHz
  • the size of the second BWP is also 5 MHz.
  • the second BWP is the target BWP occupied by the service channel, that is, the corresponding bandwidth from L2 to L3 in Figure 8.
  • the second BWP is the reference BWP
  • the size of the reference BWP is the preset bandwidth size, that is, the size of the reference BWP is equal to the size of the target BWP.
  • the reference BWP is the target BWP. That is, in the solution illustrated in Figure 8, the second BWP is both the reference BWP and the target BWP.
  • the system message includes at least one of the first starting resource block position O carrier , the first carrier offset value RB start , the third frequency offset value offset3 and the size of the BWP, and the terminal device can according to The first starting resource block position O carrier , the first carrier offset value RB start , the third frequency offset value offset3 and the size of the BWP determine the frequency domain starting position of the service channel.
  • the third frequency offset value offset3 can also be a third preset value agreed between the terminal device and the network device, or configured through DCI for the network device.
  • the third frequency offset value offset3 can also be a third preset value agreed between the terminal device and the network device, or configured through DCI for the network device.
  • the first starting resource block position and the first carrier offset value are used to determine the frequency domain starting position of the second BWP.
  • the frequency domain starting position of the second BWP is starting from the common reference point of the resource grid.
  • the first starting resource block position and the position after the first carrier offset value are used to determine the frequency domain starting position of the second BWP.
  • the size of the second BWP is the size of the reference BWP indicated in the system message.
  • the third frequency offset value is a frequency offset between the second BWP and the frequency domain starting position of the traffic channel.
  • the frequency domain starting position of the second BWP and the size of the second BWP can be determined according to the frequency domain starting position of the second BWP. bandwidth, and then determine the frequency domain starting position of the service channel based on the frequency domain starting position of the second BWP and the third frequency offset value. Then, according to the frequency domain starting position of the service channel and the preset bandwidth size, the bandwidth target BWP occupied by the service channel is determined on the second BWP.
  • FIG 9 is a schematic diagram 4 of determining the target BWP provided by the embodiment of the present application.
  • L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the third frequency offset value offset3 and the size of the reference BWP.
  • the terminal device After receiving the system message, the terminal device The first starting resource block position O carrier and the first carrier offset value RB start can determine the frequency domain starting position of the second BWP.
  • the frequency domain starting position of the second BWP is the position starting from the common reference point of the resource grid and passing through the first starting resource block position O carrier and the first carrier offset value RB start , that is, Figure 9
  • the offset between L0 and L1 is indicated by the first starting resource block position O carrier
  • the offset between L1 and L2 is indicated by the first carrier offset value RB start .
  • the frequency domain starting position of the service channel can be determined.
  • the frequency domain starting position of the service channel is The position starting from the starting position of the frequency domain of the second BWP and passing through the third frequency offset value is the position L3 in Figure 9.
  • the frequency band corresponding to the second BWP is the frequency band corresponding to L2 to L5 in FIG. 9 , and its size may be, for example, 20 MHz.
  • the frequency domain starting position of the service channel is the first frequency domain starting position, that is, starting from the common reference point of the resource grid and passing through the first starting resource block position, the first carrier offset value and the third frequency The position after the offset value.
  • the target BWP occupied by the service channel can be determined on the second BWP according to the frequency domain starting position of the service channel and the preset bandwidth size, as indicated by the shaded part in Figure 9, as Corresponding frequency bands from L3 to L4.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap, and the second carrier offset value RB start - At least one of redcap and the size of the reference BWP, the terminal device can select the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, and the size of the reference BWP. At least one item of , determines the frequency domain starting position of the traffic channel.
  • the first starting resource block position and the first carrier offset value are used to determine the frequency domain starting position of the second BWP.
  • the frequency domain starting position of the second BWP is starting from the common reference point of the resource grid.
  • the first starting resource block position and the position after the first carrier offset value are used to determine the frequency domain starting position of the second BWP.
  • the size of the second BWP is the size of the reference BWP indicated in the system message. According to the frequency domain starting position of the second BWP and the size of the second BWP, the bandwidth where the second BWP is located can be determined.
  • the second starting resource block position and the second carrier offset value are used to determine the frequency domain starting position of the service channel.
  • the frequency domain starting position of the service channel is starting from the common reference point of the resource grid and passing through the third The second starting resource block position and the position after the second carrier offset value.
  • the size of the target BWP occupied by the traffic channel is a preset bandwidth size, and the preset bandwidth size may be, for example, a value less than or equal to 5 MHz.
  • the bandwidth may be determined based on the second starting resource block position, the second carrier offset value and the preset bandwidth size, and determine the target BWP occupied by the service channel on the second BWP.
  • FIG 10 is a schematic diagram 5 of determining the target BWP provided by the embodiment of the present application.
  • L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap, the second carrier offset value RB start -redcap and Referring to at least one of the BWP sizes, after receiving the system message, the terminal device can determine the frequency domain starting position of the second BWP based on the first starting resource block position O carrier and the first carrier offset value RB start .
  • the frequency domain starting position of the second BWP is the position starting from the common reference point of the resource grid and passing through the first starting resource block position O carrier and the first carrier offset value RB start , that is, Figure 10
  • the offset between L0 and L1 is indicated by the first starting resource block position O carrier
  • the offset between L1 and L2 is indicated by the first carrier offset value RB start .
  • the size of the second BWP indicated by the system message may be, for example, 20 MHz
  • the bandwidth in which the second BWP is located may be determined based on the size of the second BWP.
  • the bandwidth where the second BWP is located is the corresponding frequency band from L2 to L6.
  • the frequency domain starting position of the service channel can be determined according to the second starting resource block position O carrier -redcap and the second carrier offset value RB start -redcap.
  • the frequency domain starting position of the service channel is the second frequency domain starting position, that is, the position starting from the common reference point of the resource grid and passing through the second starting resource block position O carrier -redcap and the second carrier offset value RB start -redcap, that is, in Figure 10 at L4.
  • the offset between L0 and L3 is indicated by the second start resource block position O carrier -redcap, and the offset between L3 and L4 is indicated by the second carrier offset value RB start -redcap
  • the target BWP occupied by the service channel can be determined on the second BWP according to the frequency domain starting position of the service channel and the preset bandwidth size, as indicated by the shaded part in Figure 10, as
  • the corresponding frequency band from L4 to L5 can be 5MHz in size.
  • the first message includes indication information.
  • the reference BWP includes N candidate BWPs.
  • the size of each candidate BWP is a preset bandwidth size. According to the indication information, it can be determined among the N candidate BWPs.
  • the size of and the size of the target BWP are both represented by the number of RBs.
  • the starting position of the first BWP among the N candidate BWPs on the reference BWP is the L+1th RB. The value of L depends on the size of the protection bandwidth.
  • the subcarrier spacing corresponding to the size S of the reference bandwidth in the formula needs to be consistent with the subcarrier spacing corresponding to the size M of the target BWP, and is based on the subcarrier spacing of the target BWP. For example, if the size S of the reference BWP is 20MHz and the subcarrier spacing is 15KHz, and the size M of the target BWP is 5MHz and the subcarrier spacing is 30KHz, then the value of the reference BWP S in the formula is 51RB, not 106RB.
  • the first message is a SIB1 or RRC message.
  • the M RBs included in the candidate BWP can be adjacent or set at intervals. This implementation will be introduced below with reference to Figures 11 and 12.
  • Figure 11 is a schematic diagram 6 of determining the target BWP provided by the embodiment of the present application.
  • the position of the target BWP in the reference BWP can be indicated by adding a new bit in the first message.
  • the reference BWP and the target BWP are The subcarrier spacing is 15KHz
  • the 4 candidate BWPs are shown in the shaded part in Figure 11 .
  • the indication information indicates that the target BWP is the first candidate BWP in Figure 11; when the bit is 01, the indication information indicates that the target BWP is the second candidate BWP in Figure 11; when the bit is 10 When the bit is 11, the indication information indicates that the target BWP is the third candidate BWP in Figure 11; when the bit is 11, the indication information indicates that the target BWP is the fourth candidate BWP in Figure 11.
  • each candidate BWP M RBs included in each candidate BWP are adjacent.
  • the frequency domain position of the k-th candidate BWP is the bandwidth part corresponding to the L+(k-1)*M+1th RB to the L+k*Mth RB in the reference BWP, and the value of k is 1, 2.. ..,N.
  • the included RBs are the L+1th RB to the L+25th RB in the reference bandwidth.
  • Figure 12 is a schematic diagram 7 of determining the target BWP provided by the embodiment of the present application.
  • the position of the target BWP in the reference BWP can be indicated by adding a new bit in the first message to determine the relationship between the reference BWP and the target BWP.
  • the subcarrier spacing is 15KHz
  • the indication information indicates that the target BWP is the first candidate BWP in Figure 12; when the bit is 01, the indication information indicates that the target BWP is the second candidate BWP in Figure 12; when the bit is 10 When the bit is 11, the indication information indicates that the target BWP is the third candidate BWP in Figure 12; when the bit is 11, the indication information indicates that the target BWP is the fourth candidate BWP in Figure 12.
  • the M RBs included in each candidate BWP are not adjacent, but are arranged at intervals.
  • the RB included in the k-th candidate BWP is the L+k+N*i-th RB in the reference BWP.
  • i is 0, 1, 2, ..., M-1, and M is a positive integer. .
  • the target BWP frequency domain range is the L+1th RB, L+5th RB, .L+96th RB, and L+97th RB in the reference BWP.
  • Figure 11 and Figure 12 take the protection RBs scattered on both sides of the reference BWP as an example.
  • the protection RBs can also be concentrated at the frequency domain edge of the reference BWP, such as the upper edge or the lower edge of the frequency domain.
  • the protection RBs It can also be concentrated or partially distributed in the middle of the reference BWP or at any position in the reference BWP.
  • the position of the protection RB is different, and the value of L in the above example is different.
  • L is the number of RBs included between the lower edge of the reference BWP and the first candidate BWP.
  • the candidate BWPs can also be in the form of partial distribution of candidate BWPs, which can be understood with reference to Figure 13, for example.
  • Figure 13 is a schematic diagram eight for determining the target BWP provided by the embodiment of the present application.
  • the preset bandwidth size is 5MHz and the subcarrier spacing is 15KHz.
  • the 25 RBs are grouped. , every 5 consecutive RBs form a group of 25 RBs, and there are 25 RBs in a total of 5 consecutive 5RB groups.
  • the candidate BWP includes 25 RBs. These 25 RBs are divided into 5 parts. Each part includes 5 RBs. The 5 RBs in each part are consecutive. These 5 parts in the selected BWP are set up dispersedly.
  • Figure 14 is a signaling diagram 2 of the processing method provided by the embodiment of the present application. As shown in Figure 14, the method may include:
  • the network device sends a first message to the terminal device.
  • the first message is used to indicate the frequency domain starting position of the traffic channel and/or the reference signal on the reference bandwidth part.
  • the terminal device in the embodiment of the present application may be an ordinary device or a light-capable device.
  • the light-capable device may include, for example, household appliances such as refrigerators, televisions, and air conditioners.
  • wearable devices such as smart watches and sports bracelets.
  • smart industrial equipment such as smart grids and smart meters, as well as low-power/low-complexity/low-cost/low-performance smartphones and some feature phones.
  • Common devices include, for example, smartphones, smart cars, etc.
  • the difference between light-capability devices and ordinary devices is not limited to the difference in device type.
  • ordinary devices in a low-power or low-performance state can also be used as light-capability devices.
  • the difference mainly lies in the current bandwidth and data rate of the device.
  • the terminal device in the embodiment of this application is a light-capability device.
  • a light-capability device if its wireless radio frequency bandwidth is maximum 20MHz and the bandwidth occupied by SSB and CORESET#0 is 20MHz, but in its business channel If one or more target BWPs are less than or equal to 20MHz, you need to determine the position of the target BWP occupied by the traffic channel in the reference BWP occupied by SBB and CORESET#0.
  • the network device sends the first message to the terminal device, and the terminal device schedules the service channel based on the first message.
  • the terminal device determines the target BWP occupied by the traffic channel and/or the reference signal on the reference BWP based on at least one of the frequency domain starting position, bandwidth size, and indication information of the traffic channel and/or reference signal.
  • the size of the target BWP is fixed, for example, it can be 5 MHz, or it can be any bandwidth size less than 5 MHz.
  • the size of the reference BWP is greater than or equal to 5MHz.
  • the size of the reference BWP can be 20MHz.
  • the traffic channel includes at least any one of PUSCH and PDSCH.
  • the reference signal includes at least one of DMRS for PDSCH, DMRS for PDCCH, CSI_RS, PTRS, and SRS.
  • the reference BWP is a bandwidth portion of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier in at least one carrier is in an inactive state.
  • system bandwidth is a total large bandwidth, including 22 RBs, namely RB0 to RB21.
  • the bandwidth part corresponding to at least one carrier is configured on the system bandwidth.
  • 4 carriers are configured on the system bandwidth, namely carrier 1, carrier 2, carrier 3 and carrier 4.
  • Each carrier is indicated by the arrow in Figure 4.
  • the bandwidth part of the carrier can be in an activated state or in an inactive state.
  • the activated bandwidth part can be used for reference signal transmission, data transmission, etc.
  • at least one carrier of the system bandwidth has a bandwidth part that is in an inactive state, and one or more carriers may have a bandwidth part that is activated.
  • carrier 1 and carrier 3 are in the activated state
  • carrier 2 and carrier 4 are in the inactive state.
  • the reference BWP in the embodiment of this application is the bandwidth part of one of at least one carrier on the system bandwidth, and the reference BWP is in an active state.
  • the reference BWP is the bandwidth portion of carrier 3. That is, the reference BWP in the embodiment of the present application is related to the carriers on the system bandwidth, and the reference BWP is the bandwidth part of one of the active carriers among at least one carrier on the system bandwidth.
  • the frequency domain starting position of the target BWP on the reference BWP can be determined based on the first message, and the target BWP can be determined on the reference BWP based on the frequency domain starting position and/or bandwidth size.
  • a solution is introduced in which the target BWP occupied by the traffic channel and/or the reference signal can be determined based on the frequency domain starting position and bandwidth size of the traffic channel, thereby realizing scheduling or transmission of the traffic channel and/or reference signal.
  • the first message and the solution of how to determine the bandwidth occupied by the traffic channel and/or the reference signal based on the first message will be described in detail below with reference to specific embodiments.
  • the first message includes MIB and/or system message.
  • the first frequency offset value between the SSB and CORESET#0, and the second frequency offset value between CORESET#0 and the frequency domain starting position of the traffic channel may be determined through the MIB. Then, the frequency domain starting position of the service channel can be determined based on the first frequency offset value and the second frequency offset value.
  • CORESET#0 is the reference BWP.
  • a new solution is provided to determine the frequency domain starting position of the service channel through the existing field index in the MIB.
  • the existing field index in the MIB is PDCCH-ConfigSIB1----->controlResourceSetZero.
  • the embodiment of the present application provides a method to determine the first field index based on the existing field index in the MIB.
  • the scheme of the first frequency offset value and the second frequency offset value please refer to Table 1 to Table 4 for details.
  • the table is just an example of how to determine the offset.
  • the specific value can be determined according to the actual application scenario, such as the specific pre-stored bandwidth size of the terminal device, the number of terminal devices, etc.
  • the row index from the field PDCCH-ConfigSIB1----->controlResourceSetZero in the MIB, and then determine the first frequency offset value and/or the second frequency according to the row index and the subcarrier spacing of the SSB and the reference BWP offset value.
  • the first frequency offset value is the frequency offset value between the SSB and the reference BWP
  • the second frequency offset value is the frequency offset value between the reference BWP and the frequency domain starting position of the traffic channel.
  • the preset corresponding relationships can be found in Table 1 to Table 4 above for examples. After the index is determined according to the MIB, it can be determined according to the subcarrier spacing between the SSB and the reference BWP which table in Table 1 to Table 4 indicates the preset corresponding relationship, so that the first frequency offset value can be further determined. and a second frequency offset value.
  • the reference BWP in the embodiment of this application is CORESET#0.
  • the reference BWP can be determined based on the first frequency offset value.
  • the second frequency offset value is the frequency offset value between the reference BWP and the frequency domain starting position of the service channel. Therefore, the frequency domain starting position of the service channel can be determined on the reference BWP according to the second frequency offset value. That is, at this time, the frequency domain starting position of the traffic channel is the third frequency domain starting position, and the third frequency domain starting position is starting from the frequency domain starting position of the SSB, passing through the first frequency offset value and the second frequency The position after the offset value.
  • the preset correspondence in the examples of Tables 1 to 4 may not include the correspondence between the index and the second frequency offset value, that is, the fifth column may not be included in Tables 1 to 4. That is, in addition to being determined by the index in the MIB, the second frequency offset value offset2 can also be the second preset value agreed between the terminal device and the network device, or the second frequency offset value offset2 configured by the network device through DCI. Or it is a value determined by the terminal device from a limited value set according to the channel status.
  • the terminal device can select the second frequency offset value to ensure that the target BWP is close to the reference If the channel status is poor at the center or edge position of the BWP, the terminal device can select a second frequency offset value to make the target BWP close to the center position of the reference BWP.
  • the channel status may be determined based on RSRP or RSRQ.
  • the second frequency offset value offset2 may be a second preset value.
  • the second preset value may be a fixed value agreed between the network device and the terminal device, or may be a value determined from the channel state of the terminal device. A numerical value selected from a finite set of values, etc.
  • the second frequency offset value is a value configured through DCI.
  • a new 2-bit field can be added to the DCI to indicate the size of the second frequency offset value offset2.
  • the newly added 2-bit field in the above DCI and the corresponding relationship between the 2-bit field and the value of offset2 are only an example and do not constitute an actual limitation.
  • a 3-bit field, a 4-bit field, etc. can be added to the DCI to indicate the size of the second frequency offset value offset2.
  • the corresponding relationship between the bit field in the DCI and the value of the second frequency offset value offset2 can also be based on Requires setting.
  • the first frequency offset value between the SSB and the reference BWP occupied by CORESET#0 is determined according to the index, and the second frequency between the reference BWP occupied by CORESET#0 and the starting position of the frequency domain between the traffic channel After the offset value is determined, the frequency domain starting position of the service channel can be determined based on the first frequency offset value and the second frequency offset value. This process will be introduced below with reference to Figure 5 .
  • the left side is the bandwidth occupied by SSB.
  • the frequency domain starting position of the bandwidth occupied by SSB is assumed to be known, that is, L1 in Figure 5.
  • the first frequency offset value offset1 is the frequency offset between SSB and the reference BWP occupied by CORESET#0, therefore, according to the first frequency offset value offset1 and SSB
  • the frequency domain starting position of the occupied bandwidth can be obtained by the frequency domain starting position of the reference BWP occupied by CORESET#0, which is L0 in Figure 5.
  • the size of the reference BWP occupied by CORESET#0 is 48 RBs
  • the frequency domain starting position of the reference BWP occupied by CORESET#0 is L0 in Figure 5. Therefore, according to the location of CORESET#0
  • the size of the occupied reference BWP and the corresponding starting position in the frequency domain can determine the reference BWP occupied by CORESET#0 (from L0 to L4 in Figure 5), that is, RB0-RB47 in Figure 5, a total of 48 RBs.
  • Figure 5 illustrates the scenario of using CORESET#0 as the reference BWP in initial access.
  • the target BWP occupied by the service channel needs to be determined on the reference BWP determined by CORESET#0.
  • CORESET#0 which is the frequency domain starting position of the reference BWP, is determined based on the first frequency offset value and the frequency domain starting position of the bandwidth occupied by the SSB, and then based on the second frequency offset value offset2 and the reference BWP
  • the starting position of the frequency domain can determine the starting position of the frequency domain of the service channel.
  • the second frequency offset value is 10 RBs. Therefore, according to the second frequency offset value offset2, it can be determined that the frequency domain starting position of the target BWP occupied by the service channel is as shown in Figure 5 At L2, the second frequency offset value offset2 between the frequency domain starting position of the target BWP occupied by the traffic channel and the frequency domain starting position of the reference BWP occupied by CORESET#0 is 10 RBs.
  • the target BWP occupied by the service channel can be determined on the reference BWP based on the third frequency domain starting position and bandwidth size, that is, the service
  • the target BWP occupied by the channel is the bandwidth corresponding to the bandwidth size starting from the corresponding starting position of the third frequency domain.
  • the target BWP occupied by the business channel is from the 10th
  • the bandwidth between the beginning of the first RB and the 34th RB is represented by the shaded area in Figure 5 (from L2 to L3).
  • a new mapping table (i.e., Table 1 to Table 4) is provided through the existing field index in the MIB, which can be implemented without changing the size and meaning of the signaling fields in the MIB.
  • the first frequency offset value and the number of RBs occupied by CORESET#0 can be determined in the above mapping table according to the field index in the MIB, thereby determining the bandwidth corresponding to CORESET#0 and the bandwidth corresponding to CORESET#0. That is, the target BWP occupied by the business channel of ordinary equipment.
  • the embodiment of the present application adds a column to the original mapping table to reflect the relationship between the index and the second frequency offset value.
  • the first frequency offset value, the number of RBs occupied by CORESET#0, and the second frequency offset value can be determined in the above mapping table according to the field index in the MIB.
  • the bandwidth corresponding to CORESET#0 that is, the reference BWP in initial access, can be determined according to the first frequency offset value and the number of RBs occupied by CORESET#0.
  • the frequency domain starting position of the service channel of the light-capable device can be determined based on the frequency domain starting position of the reference BWP and the second frequency offset value.
  • the reference BWP determined in CORESET#0 is combined with the preset bandwidth size of the target BWP. Determine the location of the target BWP.
  • the frequency domain starting position of the target BWP occupied by the service channel is determined according to the index in the MIB, and then determined on the reference BWP according to the frequency domain starting position of the service channel and the bandwidth size of the target BWP.
  • the first message may also include system messages. The following will introduce a solution for determining the target BWP occupied by the service channel based on the system messages.
  • the system message includes the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, the third frequency offset value and the size of the reference BWP.
  • At least one item, the frequency domain starting position of the traffic channel can be determined according to at least one of the above items.
  • the system messages include RRC messages and/or SIBs. That is, the RRC message includes at least one of the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, the third frequency offset value and the size of the reference BWP. item, and/or the SIB includes the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, the third frequency offset value and the size of the reference BWP at least one of.
  • the size of the reference BWP is greater than or equal to the preset bandwidth size.
  • the reference BWP is a first BWP or a second BWP.
  • the first BWP is a BWP in the same time slot as the initial BWP
  • the second BWP is a BWP with a time slot offset from the initial BWP.
  • the size of the first BWP is greater than or equal to the preset bandwidth size, and the second BWP is greater than or equal to the bandwidth size.
  • the terminal device determines the frequency domain starting position of the service channel according to the first message, and then determines the target BWP occupied by the service channel on the first BWP according to the frequency domain starting position and/or bandwidth size of the service channel.
  • the terminal device determines the frequency domain starting position of the service channel according to the first message, and then determines the target BWP occupied by the service channel on the second BWP according to the frequency domain starting position and/or bandwidth size of the service channel.
  • the system message includes at least one of the first starting resource block position O carrier , the first carrier offset value RB start and the third frequency offset value offset3.
  • the terminal device can use the first starting resource according to At least one of the block position O carrier , the first carrier offset value and the third frequency offset value determines the frequency domain starting position of the traffic channel.
  • the third frequency offset value offset3 can also be a third preset value agreed between the terminal device and the network device, or configured through DCI for the network device.
  • the third frequency offset value offset3 can also be a third preset value agreed between the terminal device and the network device, or configured through DCI for the network device.
  • the first starting resource block position O carrier and the first carrier offset value RB start are used to determine the frequency domain starting position of the first BWP, and the frequency domain starting position of the first BWP is the common resource grid.
  • the reference point starts passing through the first starting resource block position O carrier and the position after the first carrier offset value RB start .
  • the size of the first BWP is greater than or equal to the bandwidth size of the target BWP.
  • the bandwidth size of the target BWP is 5 MHz
  • the size of the first BWP is greater than or equal to 5 MHz, such as 10 MHz, 20 MHz, and so on.
  • the third frequency offset value is a frequency offset between the first BWP and the frequency domain starting position of the traffic channel.
  • the traffic channel may be determined based on the frequency domain starting position of the first BWP and the third frequency offset value. Frequency domain starting position. Then, according to the frequency domain starting position and bandwidth size of the traffic channel, the target BWP occupied by the traffic channel is determined on the first BWP.
  • L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start and the third frequency offset value offset3.
  • the terminal device After receiving the system message, the terminal device The frequency domain starting position of the first BWP can be determined based on the position O carrier and the first carrier offset value RB start .
  • the frequency domain starting position of the first BWP is starting from the common reference point of the resource grid (ie, L0 in Figure 6), passing through the first starting resource block position O carrier and the first carrier offset value
  • the position after RB start is L2 in Figure 6, where the offset between L0 and L1 is indicated by the first starting resource block position, and the offset between L1 and L2 is indicated by the first carrier offset value.
  • the first BWP is the frequency band corresponding to L2 to L5 in Figure 6 .
  • the frequency domain starting position of the service channel is L3 in Figure 6, and the frequency domain starting position of the service channel is The position starting from the frequency domain starting position of the first BWP and passing through the third frequency offset value.
  • the frequency domain starting position of the service channel is the first frequency domain starting position, that is, starting from the common reference point of the resource grid and passing through the first starting resource block position, the first carrier offset value and the third frequency The position after the offset value.
  • the target BWP occupied by the service channel can be determined on the first BWP according to the frequency domain starting position and bandwidth size of the service channel. As shown in the shaded part in Figure 6, the target BWP is The bandwidth of the corresponding frequency band from L3 to L4 is 5MHz.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap and the second carrier offset value RB start - At least one item in redcap, the terminal device can be based on the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap and the second carrier offset value RB start - At least one item in redcap determines the frequency domain starting position of the target BWP occupied by the traffic channel.
  • the first starting resource block position and the first carrier offset value are used to determine the frequency domain starting position of the first BWP.
  • the frequency domain starting position of the first BWP is starting from the common reference point of the resource grid.
  • the first starting resource block position and the position after the first carrier offset value are used to determine the frequency domain starting position of the first BWP.
  • the size of the first BWP is greater than or equal to the preset bandwidth size.
  • the preset bandwidth size is 5MHz
  • the size of the first BWP is greater than or equal to 5MHz, such as 10MHz, 20MHz, and so on. According to the frequency domain starting position of the first BWP and the size of the first BWP, the bandwidth where the first BWP is located can be determined.
  • the second starting resource block position and the second carrier offset value are used to determine the frequency domain starting position of the bandwidth occupied by the service channel.
  • the frequency domain starting position of the bandwidth occupied by the service channel is the slave resource network.
  • the common reference point of the grid starts passing through the second starting resource block position and the position after the second carrier offset value.
  • the size of the target BWP occupied by the traffic channel may be, for example, 5 MHz or a bandwidth size less than 5 MHz.
  • the bandwidth may be determined based on the second starting resource block position, the second carrier offset value, and the second starting resource block position. and bandwidth size, determine the target BWP occupied by the service channel on the first BWP, and the target BWP is located at the reference BWP.
  • L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap and the second carrier offset value RB start -redcap,
  • the terminal device can determine the frequency domain starting position of the first BWP based on the first starting resource block position O carrier and the first carrier offset value RB start .
  • the frequency domain starting position of the first BWP is starting from the common reference point of the resource grid (ie, L0 in Figure 7), passing through the first starting resource block position O carrier and the first carrier offset value
  • the position after RB start that is, L2 in Figure 7, where the offset between L0 and L1 is indicated by the first starting resource block position O carrier , and the offset between L1 and L2 is indicated by the first carrier offset value RB start instruction. Since the size of the first BWP is known, for example, 20 MHz, after determining the frequency domain starting position of the first BWP, the bandwidth where the first BWP is located can be determined based on the size of the first BWP, that is, L2 in Figure 7 to the corresponding frequency band at L6.
  • the frequency domain starting position of the service channel can be determined.
  • the starting position is the second frequency domain starting position, that is, the position starting from the common reference point of the resource grid and passing through the second starting resource block position O carrier -redcap and the second carrier offset value RB start -redcap, that is, L4 in Figure 7.
  • the offset between L0 and L3 is indicated by the second start resource block position O carrier -redcap, and the offset between L3 and L4 is indicated by the second carrier offset value RB start -redcap
  • the target BWP occupied by the service channel can be determined on the first BWP according to the frequency domain starting position and bandwidth size of the service channel, as indicated by the shaded part in Figure 7.
  • the occupied target BWP is the frequency band corresponding to L4 to L5 in Figure 7, and its size may be, for example, 5 MHz.
  • the solution of determining the target BWP occupied by the traffic channel on the first BWP when the BWP is the first BWP is introduced.
  • the following will introduce a solution for determining the target BWP occupied by the service channel on the second BWP when the BWP is the second BWP.
  • the second BWP is a separate BWP#
  • the switching time, that is, K0 needs to be greater than or equal to a certain preset value, and K0 is the delay parameter.
  • the second BWP is a separate BWP#
  • the switching time, that is, K2 needs to be greater than or equal to a certain preset value, and K2 is the delay parameter.
  • the time domain position of the second BWP can be determined according to the delay parameter, and the frequency domain position of the second BWP can be determined according to the system message.
  • the system message includes at least one of the first starting resource block position O carrier , the first carrier offset value RB start and the size of the BWP.
  • the terminal device can determine the first starting resource block position O carrier according to the first starting resource block position O carrier , at least one of the first carrier offset value RB start and the size of the BWP can determine the frequency domain starting position of the second BWP, and the frequency domain starting position of the second BWP is the frequency domain starting position of the traffic channel , the size of the second BWP is the preset bandwidth size, and the second BWP is the target BWP occupied by the service channel.
  • L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the frequency domain starting position of the second BWP is the position starting from the common reference point of the resource grid and passing through the first starting resource block position O carrier and the first carrier offset value RB start , that is, Figure 8
  • the time domain position of the second BWP is the time domain position determined according to the delay parameter, where the offset between L0 and L1 is indicated by the first starting resource block position O carrier , and the offset between L1 and L2 The shift is indicated by the first carrier offset value RB start .
  • the delay parameter is K0, and K0 is the delay between PDSCH and PDCCH.
  • the delay parameter is K2
  • K2 is the delay between PUSCH and PDCCH.
  • the size of the second BWP is the size of the reference BWP configured in the system message.
  • the second BWP is also the target BWP.
  • the delay parameter there is a delay between the traffic channel and the PDCCH.
  • the traffic channel and the PDCCH can overlap in the frequency domain, or they can be located in different frequency domain positions.
  • the target BWP bandwidth size is 5 MHz
  • the size of the second BWP is also 5 MHz.
  • the second BWP is the target BWP occupied by the service channel, that is, the corresponding bandwidth from L2 to L3 in Figure 8.
  • the second BWP is the reference BWP
  • the size of the reference BWP is the preset bandwidth size, that is, the size of the reference BWP is equal to the size of the target BWP.
  • the reference BWP is the target BWP. That is, in the solution illustrated in Figure 8, the second BWP is both the reference BWP and the target BWP.
  • the system message includes at least one of the first starting resource block position O carrier , the first carrier offset value RB start , the third frequency offset value offset3 and the size of the BWP, and the terminal device can according to The first starting resource block position O carrier , the first carrier offset value RB start , the third frequency offset value offset3 and the size of the BWP determine the frequency domain starting position of the service channel.
  • the third frequency offset value offset3 can also be a third preset value agreed between the terminal device and the network device, or configured through DCI for the network device.
  • the third frequency offset value offset3 can also be a third preset value agreed between the terminal device and the network device, or configured through DCI for the network device.
  • the first starting resource block position and the first carrier offset value are used to determine the frequency domain starting position of the second BWP.
  • the frequency domain starting position of the second BWP is starting from the common reference point of the resource grid.
  • the first starting resource block position and the position after the first carrier offset value are used to determine the frequency domain starting position of the second BWP.
  • the size of the second BWP is the size of the reference BWP indicated in the system message.
  • the third frequency offset value is a frequency offset between the second BWP and the frequency domain starting position of the traffic channel.
  • the frequency domain starting position of the second BWP and the size of the second BWP can be determined according to the frequency domain starting position of the second BWP. bandwidth, and then determine the frequency domain starting position of the service channel based on the frequency domain starting position of the second BWP and the third frequency offset value. Then, according to the frequency domain starting position and bandwidth size of the service channel, the target BWP occupied by the service channel is determined on the second BWP.
  • L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the third frequency offset value offset3 and the size of the reference BWP.
  • the terminal device After receiving the system message, the terminal device The first starting resource block position O carrier and the first carrier offset value RB start can determine the frequency domain starting position of the second BWP.
  • the frequency domain starting position of the second BWP is the position starting from the common reference point of the resource grid and passing through the first starting resource block position O carrier and the first carrier offset value RB start , that is, Figure 9
  • the offset between L0 and L1 is indicated by the first starting resource block position O carrier
  • the offset between L1 and L2 is indicated by the first carrier offset value RB start .
  • the frequency domain starting position of the service channel can be determined.
  • the frequency domain starting position of the service channel is The position starting from the starting position of the frequency domain of the second BWP and passing through the third frequency offset value is the position L3 in Figure 9.
  • the frequency band corresponding to the second BWP is the frequency band corresponding to L2 to L5 in FIG. 9 , and its size may be, for example, 20 MHz.
  • the frequency domain starting position of the service channel is the first frequency domain starting position, that is, starting from the common reference point of the resource grid and passing through the first starting resource block position, the first carrier offset value and the third frequency The position after the offset value.
  • the target BWP occupied by the service channel can be determined on the second BWP according to the frequency domain starting position and bandwidth size of the service channel, as shown in the shaded part in Figure 9, which is from L3 to the frequency band corresponding to L4.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap, and the second carrier offset value RB start - At least one of redcap and the size of the reference BWP, the terminal device can select the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, and the size of the reference BWP. At least one item of , determines the frequency domain starting position of the bandwidth occupied by the traffic channel.
  • the first starting resource block position and the first carrier offset value are used to determine the frequency domain starting position of the second BWP.
  • the frequency domain starting position of the second BWP is starting from the common reference point of the resource grid.
  • the first starting resource block position and the position after the first carrier offset value are used to determine the frequency domain starting position of the second BWP.
  • the size of the second BWP is the size of the reference BWP indicated in the system message. According to the frequency domain starting position of the second BWP and the size of the second BWP, the bandwidth where the second BWP is located can be determined.
  • the second starting resource block position and the second carrier offset value are used to determine the frequency domain starting position of the bandwidth occupied by the service channel.
  • the frequency domain starting position of the bandwidth occupied by the service channel is the slave resource network.
  • the common reference point of the grid starts passing through the second starting resource block position and the position after the second carrier offset value.
  • the size of the target BWP occupied by the traffic channel may be, for example, a value less than or equal to 5 MHz.
  • the bandwidth may be determined based on the second starting resource block position, the second carrier offset value and bandwidth size, and determine the target BWP occupied by the service channel on the second BWP.
  • L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.
  • the system message includes the first starting resource block position O carrier , the first carrier offset value RB start , the second starting resource block position O carrier -redcap, the second carrier offset value RB start -redcap and Referring to at least one of the BWP sizes, after receiving the system message, the terminal device can determine the frequency domain starting position of the second BWP based on the first starting resource block position O carrier and the first carrier offset value RB start .
  • the frequency domain starting position of the second BWP is the position starting from the common reference point of the resource grid and passing through the first starting resource block position O carrier and the first carrier offset value RB start , that is, Figure 10
  • the offset between L0 and L1 is indicated by the first starting resource block position O carrier
  • the offset between L1 and L2 is indicated by the first carrier offset value RB start .
  • the size of the second BWP indicated by the system message may be, for example, 20 MHz
  • the bandwidth in which the second BWP is located may be determined based on the size of the second BWP.
  • the bandwidth where the second BWP is located is the corresponding frequency band from L2 to L6.
  • the frequency domain starting position of the service channel can be determined according to the second starting resource block position O carrier -redcap and the second carrier offset value RB start -redcap.
  • the frequency domain starting position of the service channel is the second frequency domain starting position, that is, the position starting from the common reference point of the resource grid and passing through the second starting resource block position O carrier -redcap and the second carrier offset value RB start -redcap, that is, in Figure 10 at L4.
  • the offset between L0 and L3 is indicated by the second start resource block position O carrier -redcap, and the offset between L3 and L4 is indicated by the second carrier offset value RB start -redcap
  • the target BWP occupied by the service channel can be determined on the second BWP according to the frequency domain starting position and bandwidth size of the service channel, as shown in the shaded part in Figure 10, which is from L4
  • the corresponding frequency band to L5 can be 5MHz in size.
  • the first message includes indication information.
  • the reference BWP includes N candidate BWPs.
  • the size of each candidate BWP is a preset bandwidth size. According to the indication information, it can be determined among the N candidate BWPs.
  • the size of and the size of the target BWP are both represented by the number of RBs.
  • the starting position of the first BWP among the N candidate BWPs on the reference BWP is the L+1th RB. The value of L depends on the size of the protection bandwidth.
  • the subcarrier spacing corresponding to the size S of the reference bandwidth in the formula needs to be consistent with the subcarrier spacing corresponding to the size M of the target BWP, and is based on the subcarrier spacing of the target BWP. For example, if the size S of the reference BWP is 20MHz and the subcarrier spacing is 15KHz, and the size M of the target BWP is 5MHz and the subcarrier spacing is 30KHz, then the value of the reference BWP S in the formula is 51RB, not 106RB.
  • the first message is a SIB1 or RRC message.
  • the M RBs included in the candidate BWP can be adjacent or set at intervals. This implementation will be introduced below with reference to Figures 11 and 12.
  • the position of the target BWP in the reference BWP can be indicated by adding a new bit in the first message.
  • the subcarrier spacing between the reference BWP and the target BWP is 15KHz
  • the indication information indicates that the target BWP is the first candidate BWP in Figure 11; when the bit is 01, the indication information indicates that the target BWP is the second candidate BWP in Figure 11; when the bit is 10 When the bit is 11, the indication information indicates that the target BWP is the third candidate BWP in Figure 11; when the bit is 11, the indication information indicates that the target BWP is the fourth candidate BWP in Figure 11.
  • each candidate BWP M RBs included in each candidate BWP are adjacent.
  • the frequency domain position of the k-th candidate BWP is the bandwidth part corresponding to the L+(k-1)*M+1th RB to the L+k*Mth RB in the reference BWP, and the value of k is 1, 2.. ..,N.
  • the included RBs are the L+1th RB to the L+25th RB in the reference bandwidth.
  • the position of the target BWP in the reference BWP can be indicated by adding a new bit in the first message.
  • the subcarrier spacing between the reference BWP and the target BWP is 15KHz
  • reference BWP L 3 RB protection RBs are reserved at both ends of , which is indicated by the shaded part in Figure 12 .
  • the indication information indicates that the target BWP is the first candidate BWP in Figure 12; when the bit is 01, the indication information indicates that the target BWP is the second candidate BWP in Figure 12; when the bit is 10 When the bit is 11, the indication information indicates that the target BWP is the third candidate BWP in Figure 12; when the bit is 11, the indication information indicates that the target BWP is the fourth candidate BWP in Figure 12.
  • the M RBs included in each candidate BWP are not adjacent, but are arranged at intervals.
  • the RB included in the k-th candidate BWP is the L+k+N*i-th RB in the reference BWP.
  • i is 0, 1, 2, ..., M-1, and M is a positive integer. .
  • the target BWP frequency domain range is the L+1th RB, L+5th RB, .L+96th RB, and L+97th RB in the reference BWP.
  • Figure 11 and Figure 12 take the protection RBs scattered on both sides of the reference BWP as an example.
  • the protection RBs can also be concentrated at the frequency domain edge of the reference BWP, such as the upper edge or the lower edge of the frequency domain.
  • the protection RBs It can also be concentrated or partially distributed in the middle of the reference BWP or at any position in the reference BWP.
  • the position of the protection RB is different, and the value of L in the above example is different.
  • L is the number of RBs included between the lower edge of the reference BWP and the first candidate BWP.
  • the candidate BWPs can also be in the form of partial distribution of candidate BWPs, which can be understood with reference to Figure 13, for example.
  • the network device sends a first message to the terminal device.
  • the terminal device can determine the service channel and/or the service channel on the reference BWP according to the first message and the bandwidth size.
  • the target BWP occupied by the reference signal thereby realizing the scheduling or transmission of the traffic channel and/or the reference signal.
  • the location of the service channel and/or reference signal can be determined based on the first message and the bandwidth size.
  • the occupied target BWP implements the scheduling or transmission of traffic channels and/or reference signals.
  • FIG. 15 is a schematic structural diagram of a processing device provided by an embodiment of the present application. As shown in Figure 15, the processing device 1500 includes:
  • Determining module 1501 configured to determine the target bandwidth portion occupied by the traffic channel and/or the reference signal on the reference bandwidth portion according to the first message and the preset bandwidth size;
  • the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.
  • the first message includes at least one of the following: a first starting resource block position, a first carrier offset value, a second starting resource block position, a second carrier offset value, and a third frequency offset. value, the size of the reference bandwidth part, and indication information.
  • the determination module 1501 is specifically used to:
  • the target bandwidth part is determined on the reference bandwidth part according to the frequency domain starting position and/or the preset bandwidth size.
  • the frequency domain starting position of the traffic channel and/or the reference signal is at least one of the following:
  • a first frequency domain starting position, the first frequency domain starting position is: starting from the common reference point of the resource grid, passing through the first starting resource block position, the first carrier offset value and the The position after the third frequency offset value;
  • a second frequency domain starting position, the second frequency domain starting position is: starting from the common reference point of the resource grid, passing through the second starting resource block position and the second carrier offset value subsequent position;
  • a third frequency domain starting position which is a position starting from the frequency domain starting position of the synchronization signal block and passing through the first frequency offset value and the second frequency offset value.
  • the first message includes an index
  • the determining module 1501 is also used to:
  • the first frequency offset value and/or the second frequency offset value are determined according to the index and the subcarrier spacing between the synchronization signal block and the reference bandwidth part.
  • the time domain position of the reference bandwidth part is determined based on the delay parameter.
  • the reference bandwidth part includes N candidate bandwidth parts, and the size of each candidate bandwidth part is the preset bandwidth size; the determination module 1501 is specifically used to:
  • the indication information determine the target bandwidth part among the N candidate bandwidth parts
  • the N Floor (size of the reference bandwidth part/the preset bandwidth size).
  • the number of resource blocks included in each of the candidate bandwidth parts is M, and the indication information indicates that the target bandwidth part is the kth candidate bandwidth part among the N candidate bandwidth parts. ; Including at least one of the following:
  • the target bandwidth part is the bandwidth part corresponding to the L+(k-1)*M+1th resource block to the L+k*Mth resource block in the reference bandwidth part;
  • the target bandwidth part includes the L+k+N*ith resource block in the reference bandwidth part;
  • the k is a positive integer greater than or equal to 1 and less than or equal to the N, the i is 0, 1, 2, ..., M-1 in sequence, and the M is a positive integer, so L is the number of resource blocks included between the lower edge of the reference bandwidth part and the first candidate bandwidth part.
  • the processing device provided by the embodiments of the present application can execute the technical solutions shown in the above method embodiments.
  • the implementation principles and beneficial effects are similar and will not be described again here.
  • FIG 16 is a second structural schematic diagram of a processing device provided by an embodiment of the present application. As shown in Figure 16, the processing device 1600 includes;
  • Determining module 1601 configured to determine the traffic channel and/or the reference signal on the reference bandwidth part according to at least one of the frequency domain starting position, bandwidth size, and indication information of the traffic channel and/or the reference signal. The portion of the target bandwidth occupied;
  • the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.
  • the frequency domain starting position and/or the bandwidth size are determined based on the first message; and/or the first message is a main system information block and/or a system message.
  • the first message includes at least one of the following:
  • the first starting resource block position, the first carrier offset value, the second starting resource block position, the second carrier offset value, the third frequency offset value, the size of the reference bandwidth part, and the indication information are provided.
  • the frequency domain starting position of the traffic channel and/or the reference signal is at least one of the following:
  • a first frequency domain starting position, the first frequency domain starting position is: starting from the common reference point of the resource grid, passing through the first starting resource block position, the first carrier offset value and the The position after the third frequency offset value;
  • a second frequency domain starting position, the second frequency domain starting position is: starting from the common reference point of the resource grid, passing through the second starting resource block position and the second carrier offset value subsequent position;
  • a third frequency domain starting position which is a position starting from the frequency domain starting position of the synchronization signal block and passing through the first frequency offset value and the second frequency offset value.
  • the first message includes an index
  • the determining module 1601 is also used to:
  • the first frequency offset value and/or the second frequency offset value are determined according to the index and the subcarrier spacing between the synchronization signal block and the reference bandwidth part.
  • the determination module 1601 is specifically used to:
  • the first bandwidth part Determine the portion of the target bandwidth occupied by the traffic channel;
  • a target bandwidth portion occupied by the traffic channel is determined on the second bandwidth portion.
  • the reference bandwidth part includes N candidate bandwidth parts, and the size of each candidate bandwidth part is the bandwidth size; the determination module 1601 is specifically used to:
  • the indication information determine the target bandwidth part among the N candidate bandwidth parts
  • the N Floor (the size of the reference bandwidth part/the bandwidth size).
  • the number of resource blocks included in each of the candidate bandwidth parts is M, and the indication information indicates that the target bandwidth part is the kth candidate bandwidth part among the N candidate bandwidth parts. ; Including at least one of the following:
  • the target bandwidth part is the bandwidth part corresponding to the L+(k-1)*M+1th resource block to the L+k*Mth resource block in the reference bandwidth part;
  • the target bandwidth part includes the L+k+N*ith resource block in the reference bandwidth part;
  • the k is a positive integer greater than or equal to 1 and less than or equal to the N, the i is 0, 1, 2, ..., M-1 in sequence, and the M is a positive integer, so L is the number of resource blocks included between the lower edge of the reference bandwidth part and the first candidate bandwidth part.
  • the processing device provided by the embodiments of the present application can execute the technical solutions shown in the above method embodiments.
  • the implementation principles and beneficial effects are similar and will not be described again here.
  • FIG 17 is a schematic structural diagram three of a processing device provided by an embodiment of the present application. As shown in Figure 17, the processing device 1700 includes:
  • Sending module 1701 configured to send a first message, the first message being used to indicate the frequency domain starting position of the traffic channel and/or the reference signal on the reference bandwidth part;
  • the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.
  • a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.
  • the first message is a main system information block and/or system message
  • the system messages include radio resource control messages and/or system information blocks;
  • the first message includes at least one of the following: a first starting resource block position, a first carrier offset value, a second starting resource block position, a second carrier offset value, a third frequency offset value, the Refer to the bandwidth section for size and indication information.
  • the size of the bandwidth part is greater than or equal to the preset bandwidth size
  • the time domain position of the reference bandwidth part is determined based on the delay parameter.
  • the frequency domain starting position of the traffic channel and/or the reference signal is at least one of the following:
  • a first frequency domain starting position, the first frequency domain starting position is: starting from the common reference point of the resource grid, passing through the first starting resource block position, the first carrier offset value and the The position after the third frequency offset value;
  • a second frequency domain starting position, the second frequency domain starting position is: starting from the common reference point of the resource grid, passing through the second starting resource block position and the second carrier offset value subsequent position;
  • a third frequency domain starting position which is a position starting from the frequency domain starting position of the synchronization signal block and passing through the first frequency offset value and the second frequency offset value.
  • the first message also includes an index, and the index and the subcarrier interval between the synchronization signal block and the reference bandwidth part are used to indicate the first frequency offset value and/or the third frequency offset value. 2. Frequency offset value.
  • the reference bandwidth part includes N candidate bandwidth parts, and the size of each candidate bandwidth part is the preset bandwidth size; wherein:
  • the indication information indicates that the target bandwidth part is the k-th candidate bandwidth part among the N candidate bandwidth parts
  • the N Floor (the size of the reference bandwidth part/the preset bandwidth size), and the k is a positive integer greater than or equal to 1 and less than or equal to the N.
  • the number of resource blocks included in each of the candidate bandwidth parts is M, including at least one of the following:
  • the target bandwidth part is the bandwidth part corresponding to the L+(k-1)*M+1th resource block to the L+k*Mth resource block in the reference bandwidth part;
  • the target bandwidth part includes the L+k+N*ith resource block in the reference bandwidth part;
  • the k is a positive integer greater than or equal to 1 and less than or equal to the N, the i is 0, 1, 2, ..., M-1 in sequence, and the M is a positive integer, so L is the number of resource blocks included between the lower edge of the reference bandwidth part and the first candidate bandwidth part.
  • the processing device provided by the embodiments of the present application can execute the technical solutions shown in the above method embodiments.
  • the implementation principles and beneficial effects are similar and will not be described again here.
  • Figure 18 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 180 in this embodiment can be the terminal device (or a component that can be used for the terminal device) or a network device (or a component that can be used for the network device) mentioned in the previous method embodiment.
  • the communication device 180 may be used to implement the method corresponding to the terminal device or network device described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • the communication device 180 may include one or more processors 181, which may also be called a processing unit, and may implement certain control or processing functions.
  • the processor 181 may be a general-purpose processor, a special-purpose processor, or the like. For example, it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processing unit can be used to control communication equipment, execute software programs, and process data of software programs.
  • the processor 181 may also store instructions 183 or data (eg, intermediate data).
  • the instruction 183 may be executed by the processor 181, so that the communication device 180 performs the method corresponding to the terminal device or network device described in the above method embodiment.
  • the communication device 180 may include a circuit, which may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the communication device 180 may include one or more memories 182, on which instructions 184 may be stored, which instructions may be executed on the processor 181, so that the communication device 180 executes the method described in the above method embodiment.
  • data may also be stored in the memory 182 .
  • the processor 181 and the memory 182 can be provided separately or integrated together.
  • communication device 180 may also include a transceiver 185 and/or an antenna 186.
  • the processor 181 may be called a processing unit and controls the communication device 180 (terminal device or core network device or radio access network device).
  • the transceiver 185 may be called a transceiver unit, a transceiver, a transceiver circuit, a transceiver, etc., and is used to implement the transceiver function of the communication device 180 .
  • the specific implementation process of the processor 181 and the transceiver 185 can be referred to the relevant descriptions of the above embodiments, and will not be described again here.
  • the specific implementation process of the processor 181 and the transceiver 185 can be referred to the relevant descriptions of the above embodiments, and will not be described again here.
  • the processor 181 and transceiver 185 described in this application can be implemented in IC (Integrated Circuit, integrated circuit), analog integrated circuit, RFIC (Radio Frequency Integrated Circuit, radio frequency integrated circuit), mixed signal integrated circuit, ASIC (Application Specific Integrated Circuit, application specific integrated circuit), PCB (Printed Circuit Board, printed circuit board), electronic equipment, etc.
  • IC Integrated Circuit, integrated circuit
  • RFIC Radio Frequency Integrated Circuit, radio frequency integrated circuit
  • mixed signal integrated circuit aSIC (Application Specific Integrated Circuit, application specific integrated circuit)
  • ASIC Application Specific Integrated Circuit, application specific integrated circuit
  • PCB Print Circuit Board, printed circuit board
  • electronic equipment etc.
  • the processor 181 and the transceiver 185 can also be manufactured using various integrated circuit process technologies, such as CMOS (Complementary Metal Oxide Semiconductor, complementary metal oxide semiconductor), NMOS (N Metal-Oxide-Semiconductor, N-type metal oxide semiconductor) ), PMOS (Positive channel Metal Oxide Semiconductor, P-type metal oxide semiconductor), BJT (Bipolar Junction Transistor, bipolar junction transistor), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs) wait.
  • CMOS Complementary Metal Oxide Semiconductor, complementary metal oxide semiconductor
  • NMOS N Metal-Oxide-Semiconductor, N-type metal oxide semiconductor
  • PMOS Positive channel Metal Oxide Semiconductor, P-type metal oxide semiconductor
  • BJT Bipolar Junction Transistor, bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • the communication device may be a terminal device or a network device (such as a base station).
  • the terminal device may be implemented in various forms.
  • the terminal devices described in this application may include mobile phones, tablet computers, notebook computers, PDAs, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable Media Player, PMP), navigation devices, Mobile terminals such as wearable devices, smart bracelets, and pedometers, as well as fixed terminals such as digital TVs and desktop computers.
  • the communication device is described by taking a terminal device or a network device as an example, the scope of the communication device described in this application is not limited to the above-mentioned terminal device or network device, and the structure of the communication device may not be limited to Limitations of Figure 18.
  • the communication device may be a stand-alone device or may be part of a larger device.
  • An embodiment of the present application also provides a communication system, including: a terminal device as in any of the above method embodiments; and a network device as in any of the above method embodiments.
  • An embodiment of the present application also provides a terminal device.
  • the terminal device includes: a memory and a processor; wherein a computer program is stored on the memory, and when the computer program is executed by the processor, the steps of the processing method in any of the above embodiments are implemented.
  • An embodiment of the present application also provides a network device.
  • the network device includes: a memory and a processor; wherein a computer program is stored on the memory, and when the computer program is executed by the processor, the steps of the processing method in any of the above embodiments are implemented.
  • Embodiments of the present application also provide a computer-readable storage medium.
  • a computer program is stored on the storage medium.
  • the computer program is executed by a processor, the steps of the processing method in any of the above embodiments are implemented.
  • Embodiments of the present application also provide a computer program product.
  • the computer program product includes computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to execute the methods in the above various possible implementations.
  • Embodiments of the present application also provide a chip, which includes a memory and a processor.
  • the memory is used to store a computer program.
  • the processor is used to call and run the computer program from the memory, so that the device equipped with the chip executes the above various possible implementations. Methods.
  • the units in the equipment of the embodiments of this application can be merged, divided, and deleted according to actual needs.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or that contributes to the existing technology.
  • the computer software product is stored in one of the above storage media (such as ROM/RAM, magnetic disk, optical disk), including several instructions to cause a terminal device (which can be a mobile phone, a computer, a server, a controlled terminal, or a network device, etc.) to execute the method of each embodiment of the present application.
  • a computer program product includes one or more computer instructions.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g., computer instructions may be transmitted from a website, computer, server or data center via a wired link (e.g.
  • Coaxial cable, optical fiber, digital subscriber line) or wireless means to transmit to another website, computer, server or data center.
  • Computer-readable storage media can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or other integrated media that contains one or more available media. Available media may be magnetic media (eg, floppy disks, storage disks, tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), etc.

Landscapes

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

Abstract

La présente demande concerne un procédé de traitement, un dispositif de communication et un support de stockage. Le procédé comprend : selon un premier message et une taille de largeur de bande prédéfinie, la détermination, sur une partie de largeur de bande de référence, d'une partie de largeur de bande cible occupée par un canal de service et/ou par un signal de référence, la partie de largeur de bande de référence étant la partie de largeur de bande d'une porteuse sur une largeur de bande système, la largeur de bande système comprenant au moins une porteuse, et la partie de largeur de bande d'au moins une porteuse parmi la ou les porteuses étant dans un état inactif. Par rapport à un scénario dans lequel une partie de largeur de bande de référence est supérieure ou égale à une partie de largeur de bande cible occupée par un canal de service, la solution des modes de réalisation de la présente demande peut déterminer la partie de largeur de bande cible, occupée par le canal de service et/ou par un signal de référence, simplement sur la base d'un premier message et d'une taille de largeur de bande prédéfinie, ce qui permet de réaliser une programmation ou une transmission du canal de service.
PCT/CN2022/095340 2022-05-26 2022-05-26 Procédé de traitement, dispositif de communication et support de stockage Ceased WO2023225959A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/095340 WO2023225959A1 (fr) 2022-05-26 2022-05-26 Procédé de traitement, dispositif de communication et support de stockage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/095340 WO2023225959A1 (fr) 2022-05-26 2022-05-26 Procédé de traitement, dispositif de communication et support de stockage

Publications (1)

Publication Number Publication Date
WO2023225959A1 true WO2023225959A1 (fr) 2023-11-30

Family

ID=88918152

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/095340 Ceased WO2023225959A1 (fr) 2022-05-26 2022-05-26 Procédé de traitement, dispositif de communication et support de stockage

Country Status (1)

Country Link
WO (1) WO2023225959A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190357238A1 (en) * 2018-05-18 2019-11-21 Comcast Cable Communications, Llc Cross-Carrier Scheduling with Multiple Active Bandwidth Parts
CN110786045A (zh) * 2017-06-16 2020-02-11 韩国电子通信研究院 通信系统中用于支持宽带载波的带宽设定方法
CN110875808A (zh) * 2018-08-30 2020-03-10 维沃移动通信有限公司 系统信息传输方法、网络设备及终端
CN111491379A (zh) * 2017-05-05 2020-08-04 华为技术有限公司 资源分配的方法、用户设备和网络设备
CN114363967A (zh) * 2018-06-21 2022-04-15 华为技术有限公司 一种通信方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111491379A (zh) * 2017-05-05 2020-08-04 华为技术有限公司 资源分配的方法、用户设备和网络设备
CN110786045A (zh) * 2017-06-16 2020-02-11 韩国电子通信研究院 通信系统中用于支持宽带载波的带宽设定方法
US20190357238A1 (en) * 2018-05-18 2019-11-21 Comcast Cable Communications, Llc Cross-Carrier Scheduling with Multiple Active Bandwidth Parts
CN114363967A (zh) * 2018-06-21 2022-04-15 华为技术有限公司 一种通信方法及装置
CN110875808A (zh) * 2018-08-30 2020-03-10 维沃移动通信有限公司 系统信息传输方法、网络设备及终端

Similar Documents

Publication Publication Date Title
CN116600402B (zh) 处理方法、通信设备及存储介质
WO2023213257A1 (fr) Procédé de transmission de données, dispositif de communication et support de stockage
EP4195804A1 (fr) Procédé de traitement, dispositif de communication, système de communication et support de stockage
WO2023082688A1 (fr) Procédé de mise à jour de cycle de radiomessagerie, dispositif de communication, système de communication, et support de stockage
WO2023221831A1 (fr) Procédé de traitement, dispositif de communication, et support de stockage
WO2025050769A2 (fr) Procédé de commande, dispositif de communication et support de stockage lisible par ordinateur
WO2023225959A1 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2023066341A1 (fr) Procédé et appareil de configuration d'informations, dispositif côté réseau et terminal
WO2024026652A1 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2023230874A1 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2025051287A2 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2024036613A1 (fr) Procédés de traitement, dispositif de communication et support d'enregistrement
WO2024164225A1 (fr) Procédé de détermination de paramètre de transmission, dispositif de communication et support d'enregistrement
WO2024229832A1 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2024020949A1 (fr) Procédé de traitement d'informations, dispositif de communication et support de stockage
WO2023221129A1 (fr) Procédé de détection de canal, dispositif, et support de stockage
WO2025098536A2 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2025190433A2 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2023216036A1 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2025153119A2 (fr) Procédé de surveillance, dispositif de communication et support de stockage
WO2025050748A1 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2025051284A9 (fr) Procédé de traitement, dispositif de communication et support de stockage
WO2025153118A2 (fr) Procédé de détermination, dispositif de communication et support de stockage
CN118489288A (zh) 处理方法、通信设备及存储介质
CN120456064A (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: 22943159

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 09/04/2025)