WO2023225959A1

WO2023225959A1 - Processing method, communication device, and storage medium

Info

Publication number: WO2023225959A1
Application number: PCT/CN2022/095340
Authority: WO
Inventors: 王沙
Original assignee: 深圳传音控股股份有限公司
Priority date: 2022-05-26
Filing date: 2022-05-26
Publication date: 2023-11-30

Abstract

Provided in the present application are a processing method, a communication device, and a storage medium, the method comprising: according to a first message and a preset bandwidth size, determining on a reference bandwidth part a target bandwidth part occupied by a service channel and/or a reference signal, the reference bandwidth part being the bandwidth part of a carrier on a system bandwidth, the system bandwidth comprising at least one carrier, and the bandwidth part of at least one carrier amongst the at least one carrier being in an inactive state. In respect of a scenario in which a reference bandwidth part is greater than or equal to a target bandwidth part occupied by a service channel, the solution of the embodiments of the present application can determine the target bandwidth part occupied by the service channel and/or a reference signal simply on the basis of a first message and a preset bandwidth size, thus realizing scheduling or transmission of the service channel.

Description

Processing method, communication equipment and storage medium

Technical field

This application relates to the field of communication technology, and specifically to a processing method, communication equipment and storage medium.

Background technique

Currently, for light equipment, the maximum bandwidth set is 5MHz, that is, the maximum bandwidth of the business channel is 5MHz.

During the process of conceiving and implementing this application, the inventor found that there are at least the following problems: 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 When 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.

The preceding description is intended to provide general background information and does not necessarily constitute prior art.

Contents of the invention

In view of the above technical problems, this application provides a processing method, communication equipment and storage medium to realize the scheduling or transmission of business channels.

In the first aspect, this application provides a processing method that can be applied to terminal devices (such as mobile phones), including:

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;

Optionally, the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, which includes at least one carrier.

Optionally, a bandwidth portion of at least one carrier among the at least one carrier is in an inactive state.

Optionally, 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.

Optionally, include at least one of the following:

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.

Optionally, 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:

Determine the frequency domain starting position of the traffic channel and/or the reference signal according to the first message;

The target bandwidth part is determined on the reference bandwidth part according to the frequency domain starting position and/or the preset bandwidth size.

Optionally, 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.

Optionally, the first message includes an index, and 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.

Optionally, the time domain position of the reference bandwidth part is determined based on the delay parameter.

Optionally, 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:

According to the indication information, determine the target bandwidth part among the N candidate bandwidth parts;

Optionally, the N=Floor (size of the reference bandwidth part/the preset bandwidth size).

Optionally, 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;

Optionally, 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.

In the second aspect, this application provides a processing method that can be applied to terminal devices (such as mobile phones), including:

Determine the target bandwidth part occupied by 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 reference signal;

Optionally, the frequency domain starting position and/or the bandwidth size are determined based on the first message.

Optionally, the first message is a main system information block and/or a system message.

Optionally, the system message includes a radio resource control message and/or a system information block.

Optionally, 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.

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;

Optionally, 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:

In response to the time domain position of the traffic channel and/or the reference signal being the same as the time domain position of the physical downlink control channel, according to the frequency domain starting position and/or the bandwidth size, on the first bandwidth part determining said target bandwidth portion; and/or,

In response to the existence of a delay between the time domain position of the traffic channel and/or the reference signal and the time domain position of the physical downlink control channel, according to the frequency domain starting position and/or the bandwidth size, The target bandwidth portion is determined over a second bandwidth portion.

Optionally, 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:

Optionally, the N=Floor (the size of the reference bandwidth part/the bandwidth size).

In the third aspect, this application provides a processing method that can be applied to network equipment (such as base stations), including:

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;

Optionally, the size of the reference bandwidth part is greater than or equal to the preset bandwidth size.

Optionally, 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.

Optionally, 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;

Optionally, 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.

Optionally, the number of resource blocks included in each of the candidate bandwidth parts is M, including at least one of the following:

In a fourth aspect, 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;

In a fifth aspect, 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;

In a sixth aspect, 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;

In a seventh aspect, 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.

In an eighth aspect, 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.

In the processing method provided by the embodiment of the present application, first the network device sends a first message to the terminal device. After receiving the first message, 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. According to the solution of the embodiment of the present application, in a scenario where the reference bandwidth part is greater than or equal to the target bandwidth part occupied by the service channel and/or the reference signal, 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.

Description of the drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to describe the embodiments. Obviously, for those of ordinary skill in the art, without exerting creative efforts, Other drawings can also be obtained from these drawings.

Figure 1 is a schematic diagram of the hardware structure of a terminal device provided by an embodiment of the present application;

Figure 2 is a communication network system architecture diagram provided by an embodiment of the present application;

Figure 3 is a signaling diagram 1 of the processing method provided by the embodiment of the present application;

Figure 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;

Figure 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.

The realization of the purpose, functional features and advantages of the present application will be further described with reference to the embodiments and the accompanying drawings. Through the above-mentioned drawings, clear embodiments of the present application have been shown, which will be described in more detail below. These drawings and text descriptions are not intended to limit the scope of the present application's concepts in any way, but are intended to illustrate the application's concepts for those skilled in the art with reference to specific embodiments.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the appended claims.

It should be noted that, in this document, the terms "comprising", "comprises" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or device that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in the process, method, article or apparatus. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, the application may be implemented differently. Components, features, and elements with the same names in the examples may have the same meaning or may have different meanings. Their specific meanings need to be determined based on their interpretation in the specific embodiment or further combined with the context of the specific embodiment.

It should be understood that although the terms 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. For example, without departing from the scope of this document, the first information may also be called second information, and similarly, the second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to determining." Furthermore, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising" and "including" indicate the presence of stated features, steps, operations, elements, components, items, categories, and/or groups, but do not exclude one or more other features, steps, operations, The presence, occurrence, or addition of elements, components, items, categories, and/or groups. The terms "or", "and/or", "including at least one of the following", etc. used in this application may be interpreted as inclusive or mean any one or any combination. For example, "including at least one of the following: 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.

It should be understood that although 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.

Depending on the context, 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." Similarly, depending on the context, 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)".

It should be noted that in this article, 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.

It should be understood that the specific embodiments described here are only used to explain the present application and are not used to limit the present application.

In the subsequent description, the use of suffixes such as "module", "component" or "unit" used to represent elements is only to facilitate the description of the present application and has no specific meaning in itself. Therefore, "module", "component" or "unit" may be used interchangeably.

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). The specific meaning needs to be clarified based on the context.

The terminal device may be a mobile terminal, and the mobile terminal may be implemented in various forms. For example, 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.

In the following description, a mobile terminal will be taken as an example. Those skilled in the art will understand that, in addition to elements specifically used for mobile purposes, the structure according to the embodiments of the present application can also be applied to fixed-type terminals.

Please refer to Figure 1, which is a schematic diagram of the hardware structure of a mobile terminal that implements various embodiments of the present application. 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. Those skilled in the art can understand that the structure of the mobile terminal shown in Figure 1 does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown in the figure, or some components may be combined, or different components may be used. layout.

The following is a detailed introduction to each component of the mobile terminal in conjunction with Figure 1:

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. Generally, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, transceiver, coupler, low noise amplifier, duplexer, etc. In addition, 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.

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. Although 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. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, 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. As a kind of motion sensor, 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.

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. Optionally, 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. Optionally, 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. In addition, the touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Optionally, 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.

Optionally, the touch panel 1071 can cover the display panel 1061. When 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. Although in Figure 1, 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 . For example, 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. Optionally, 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. In addition, 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. Optionally, 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. Preferably, 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.

Although not shown in FIG. 1 , the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described again here.

In order to facilitate understanding of the embodiments of the present application, the communication network system on which the mobile terminal of the present application is based is described below.

Please refer to Figure 2. Figure 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.

Optionally, UE 201 may be the above-mentioned terminal 100, which will not be described again here.

E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc. Optionally, 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.

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. Optionally, 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.

Although the above introduction takes the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but also can be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA and future new Network systems (such as 5G), etc. are not limited here.

Based on the above-mentioned mobile terminal hardware structure and communication network system, various embodiments of the present application are proposed.

Figure 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:

S31. 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. For example, it may include wearable devices such as smart watches and sports bracelets. For example: 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. For example, 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.

Optionally, the terminal device in the embodiment of this application is a light-capability device. For 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.

Optionally, the network device sends the first message to the terminal device, and the terminal device schedules the service channel based on the first message.

S32: 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.

Optionally, the size of the target BWP is fixed, that is, the preset bandwidth size. Optionally, the preset bandwidth size may be, for example, 5 MHz, or may be any bandwidth size less than 5 MHz.

Optionally, the size of the reference BWP is greater than or equal to 5MHz. Optionally, the size of the reference BWP can be 20MHz.

Optionally, 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).

Optionally, 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).

Optionally, the reference BWP is a bandwidth portion of a carrier on the system bandwidth, which includes at least one carrier.

Optionally, a bandwidth portion of at least one carrier in at least one carrier is in an inactive state.

For example, the relationship between system bandwidth and reference BWP can be understood with reference to Figure 4. Figure 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. For example, in Figure 4, 4 carriers are configured on the system bandwidth, namely carrier 1, carrier 2, carrier 3 and carrier 4. Each carrier The bandwidth part is indicated by the arrow in Figure 4.

For any carrier, 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. In this embodiment of the present application, 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. For example, in Figure 4, carrier 1 and carrier 3 are in the activated state, and 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. For example, in Figure 4, 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.

After obtaining the first message, since the size of the target BWP is the preset bandwidth size, 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.

In the processing method provided by the embodiment of the present application, first the network device sends a first message to the terminal device. After receiving the first message, 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. According to the solution of the embodiment of the present application, in the scenario where the reference BWP is greater than or equal to the target BWP occupied by the service channel, 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.

In the above embodiment, 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.

Optionally, the first message includes a master system information block (Master Information Block, MIB) and/or a system message.

Optionally, 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. In this embodiment, CORESET#0 is the reference BWP.

In the embodiment of this application, 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. For the different subcarrier intervals of SSB and CORESET#0, the embodiment of the present application provides a method to determine the first field index based on the existing field index in the MIB. For 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.

Assume that the subcarrier intervals of SSB and CORESET#0 are {30,15}KHz respectively. Table 1 below illustrates a solution for determining the first frequency offset value and the second frequency offset value based on the MIB.

Table 1

Assume that the subcarrier intervals of SSB and CORESET#0 are {15,15}KHz respectively. Table 2 below illustrates a solution for determining the first frequency offset value and the second frequency offset value based on the MIB.

Table 2

Assume that the subcarrier intervals of SSB and CORESET#0 are {15,30}KHz respectively. Table 3 below illustrates a solution for determining the first frequency offset value and the second frequency offset value based on the MIB.

table 3

Assume that the subcarrier intervals of SSB and CORESET#0 are {30,30}KHz respectively. Table 4 below illustrates a solution for determining the first frequency offset value and the second frequency offset value based on the MIB.

Table 4

Optionally, 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.

Optionally, determine 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. Optionally, the first frequency offset value is the frequency offset value between the SSB and the reference BWP, and the second frequency offset value is the frequency offset value between the reference BWP and the frequency domain starting position of the traffic channel.

There is a preset correspondence between the first frequency offset value and the index and the subcarrier spacing between the SSB and the reference BWP. There is also a preset correspondence between the second frequency offset value and the index and the subcarrier spacing between the SSB and the reference BWP. , 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. Optionally, the reference BWP in the embodiment of this application is CORESET#0.

Since the first frequency offset value is the frequency offset value between the SSB and the reference BWP, 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.

Let’s introduce it with a concrete example. Assuming that the subcarrier spacing of SSB and CORESET#0 is {30,15}KHz, the default corresponding relationship is indicated by the above Table 1. Assume that the field PDCCH-ConfigSIB1----->controlResourceSetZero in the MIB has a value of 0, that is, the row index is 0. According to Table 1 above, it can be seen that the first frequency offset value is 2 resource blocks (Resource Block, RB), and the second frequency offset value is 10 RBs. During initial access, 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.

Optionally, 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.

Optionally, when the second frequency offset value is a value determined by the terminal device from a limited value set according to the channel status, if the channel status is good, 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. Alternatively, the channel status may be determined based on RSRP or RSRQ.

Optionally, 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.

Optionally, the second frequency offset value is a value configured through DCI. For example, a 2-bit field may be added to the DCI to indicate the size of the second frequency offset value offset2. For example, when the new 2-bit field is 00, it means offset2=2RB. When the new 2-bit field is 01, it means offset2=5RB. When the new 2-bit field is 10, it means offset2=6RB. When the new 2-bit field is 11, it means offset2=10RB, and so on. It should be noted that 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. For example, 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.

Determining the first frequency offset value between the SSB and the reference BWP occupied by CORESET#0 according to the index, and the second frequency offset between the reference BWP occupied by CORESET#0 and the starting position of the frequency domain of the traffic channel After the 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.

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.

After determining the first frequency offset value offset1 according to the index, since 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.

According to Table 1 above, it can be seen that the size of the reference BWP occupied by CORESET#0 is 48 RBs, and 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. As mentioned above, 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.

When the index is 0, according to Table 1 above, it can be seen that 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.

Since the size of the target BWP occupied by the traffic channel is the preset bandwidth size, after determining the third frequency domain starting position of the target BWP occupied by the business channel, based on the third frequency domain starting position and 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.

For example, in Figure 5, taking the sub-carrier spacing of the business channel as 15KHz and the preset bandwidth size as 5MHz, it is equivalent to a target bandwidth size of 25 RBs. Therefore, the target BWP occupied by the business channel starts from the 10th RB. The bandwidth between the 34th RB and the 34th RB is represented by the shaded area in Figure 5 (from L2 to L3).

In the embodiment of this application, 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. Coexistence of different types of terminal equipment. For ordinary equipment, 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.

For lightweight 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. Then, 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.

In the embodiment of Figure 5, it is introduced that 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. In addition to the MIB, 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.

Optionally, 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.

Optionally, 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.

Optionally, the size of the reference BWP is greater than or equal to the preset bandwidth size.

Optionally, the reference BWP is a first BWP or a second BWP. Optionally, the first BWP is a BWP in the same time slot as the initial BWP, and the second BWP is a BWP with a time slot offset from the initial BWP.

Optionally, the size of the first BWP is greater than or equal to the preset bandwidth size, and the size of the second BWP is greater than or equal to the preset bandwidth size.

Optionally, 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.

Optionally, 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.

First, 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.

In an implementation manner, 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.

Optionally, in addition to being configured through system messages (including RRC messages or SIBs), 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.

Optionally, 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.

Optionally, the third frequency offset value is a value configured through DCI. For example, a 2-bit field may be added to the DCI to indicate the size of the third frequency offset value offset3. For example, when the new 2-bit field is 00, it means offset3=2RB. When the new 2-bit field is 01, it means offset3=5RB. When the new 2-bit field is 10, it means offset3=6RB. When the new 2-bit field is 11, it means offset3=10RB, and so on. It should be noted that 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. For example, 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.

Optionally, 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 .

Optionally, the size of the first BWP is greater than or equal to the preset bandwidth size. For example, if 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.

Optionally, the third frequency offset value is a frequency offset between the first BWP and the frequency domain starting position of the traffic channel. After determining the frequency domain starting position of the first BWP based on the first starting resource block position and the first carrier offset value, 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. The following will be introduced in conjunction with Figure 6.

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.

In the example of Figure 6, 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. 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 .

For example, in Figure 6, 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 . Then, according to the frequency domain starting position L2 of the first BWP and the third frequency offset value offset3, it can be determined that 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.

To sum up, 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.

After determining the frequency domain starting position of the service channel, 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.

In one implementation, 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.

Optionally, 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.

Optionally, the size of the first BWP is greater than or equal to the preset bandwidth size. For example, if 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.

Optionally, 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.

Optionally, 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.

Optionally, after determining the bandwidth where the first BWP is located based on the first starting resource block position, the first carrier offset value, and the size of the first BWP, 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. The following will be introduced in conjunction with Figure 7.

Figure 7 is a schematic diagram 3 of determining the target BWP provided by the embodiment of the present application. As shown in Figure 7, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.

In the example of Figure 7, 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, After receiving the system message, 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 .

For example, in Figure 7, 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.

Then 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. As shown in Figure 7, 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

After determining the frequency domain starting position of the service channel, 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.

In the above embodiment, 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.

Optionally, 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.

Optionally, 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.

In an implementation manner, 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.

Figure 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.

In the example of Figure 8, 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 At L2 in , 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 .

Optionally, when the traffic channel is PDSCH, the delay parameter is K0, and K0 is the delay between PDSCH and PDCCH.

Optionally, when the traffic channel is PUSCH, the delay parameter is K2, and K2 is the delay between PUSCH and PDCCH.

In the example of FIG. 8 , the size of the second BWP is the size of the reference BWP configured in the system message. At the same time, because the size of the second BWP is the preset bandwidth size, the second BWP is also the target BWP. Through the delay parameter, there is a delay between the traffic channel and the PDCCH. At this time, the traffic channel and the PDCCH can overlap in the frequency domain, or they can be located in different frequency domain positions. In the solution illustrated in Figure 8, the preset bandwidth size is 5 MHz, and 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. In the solution illustrated in Figure 8, the second BWP is the reference BWP, and 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. At this time, 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.

In one implementation, 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.

Optionally, in addition to being configured through system messages (including RRC messages or SIB1), 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.

Optionally, 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.

Optionally, the size of the second BWP is the size of the reference BWP indicated in the system message.

Optionally, the third frequency offset value is a frequency offset between the second BWP and the frequency domain starting position of the traffic channel. After determining the frequency domain starting position of the second BWP according to the first starting resource block position and the first carrier offset value, 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. The following will be introduced in conjunction with Figure 9.

Figure 9 is a schematic diagram 4 of determining the target BWP provided by the embodiment of the present application. As shown in Figure 9, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.

In the example of Figure 9, 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. 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.

For example, in Figure 9, 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 At L2 in , 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 . Then, based on the frequency domain starting position of the second BWP (at L2 in Figure 9) and the third frequency offset value offset3, 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.

After determining the frequency domain starting position of the service channel, 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.

In one implementation, 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.

Optionally, 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.

Optionally, 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.

Optionally, 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.

Optionally, after determining the bandwidth of the second BWP based on the first starting resource block position, the first carrier offset value, and the size of the second BWP, 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. The following will be introduced in conjunction with Figure 10.

Figure 10 is a schematic diagram 5 of determining the target BWP provided by the embodiment of the present application. As shown in Figure 10, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.

In the example of Figure 10, 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 .

For example, in Figure 10, 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 At L2 in , 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 . Since the size of the second BWP indicated by the system message may be, for example, 20 MHz, after determining the starting position of the second BWP in the frequency domain, the bandwidth in which the second BWP is located may be determined based on the size of the second BWP. In Figure 10, the bandwidth where the second BWP is located is the corresponding frequency band from L2 to L6.

Then, 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. As shown in Figure 10, 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

After determining the frequency domain starting position of the service channel, 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.

In one implementation, 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. Frequency domain position of the target BWP, optionally, N=Floor(S/M), S is the size of the reference bandwidth, M is the size of the target BWP (that is, the preset bandwidth size), Floor means rounding down, reference BWP 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. For example, when the protection bandwidth at the lower edge of the reference BWP is 0 RBs, then L=0. For example, when the protection bandwidth at the lower edge of the reference BWP is 3 RBs, then L=3, etc. . The value of L can also be determined using a formula, for example, L=(S mod M)/2.

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.

Optionally, the first message is a SIB1 or RRC message.

Assume that the size of the target BWP is M RBs, then for any candidate BWP, 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. As shown in Figure 11, the position of the target BWP in the reference BWP can be indicated by adding a new bit in the first message. Assume that the reference BWP and the target BWP are The subcarrier spacing is 15KHz, the reference BWP size is 20MHz=106RB, and the target BWP size is 5MHz=25RB, then N=Floor(106/25)=4, L=(106mod25)/2=3, that is, the reference BWP includes N = 4 candidate BWPs, which one of the 4 candidate BWPs is the target BWP is indicated by 2 bits. The 4 candidate BWPs are shown in the shaded part in Figure 11 .

When the bit is 00, 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.

In the example of FIG. 11, 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.

In Figure 11, the reference BWP size S=106RB, the default bandwidth size M=25, L=(106mod25)/2=3, if the target BWP is the first candidate BWP, that is, k=1, then the target BWP 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. As shown in Figure 12, 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 reference BWP size is 20MHz=106RB, and the target BWP size is 5MHz=25RB as an example, then N=Floor(106/25)=4, L=(106mod25)/2=3, then the reference BWP It includes N=4 candidate BWPs, indicated by 2 bits, and L=3RB protection RBs are reserved at both ends of the reference BWP, which is indicated by the shaded part in Figure 12.

When the bit is 00, 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.

In the example of FIG. 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. Optionally, i is 0, 1, 2, ..., M-1, and M is a positive integer. .

In Figure 12, the number of protection RBs is L=3, the reference BWP contains N=4 candidate BWPs, and the number of RBs included in the candidate BWP is M=25. Taking the first candidate BWP as the target BWP as an example, that is, k= 1 is used as an example, 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. In fact, 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. For example, the protection RB is concentrated on the upper edge of the reference BWP, then L=0, that is, the value of L depends on the number of protection RBs on the lower edge of the reference BWP. L is the number of RBs included between the lower edge of the reference BWP and the first candidate BWP.

In addition to the distribution form of adjacent RBs and the form separated by N RBs as shown in Figure 11, 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. As shown in Figure 13, the preset bandwidth size is 5MHz and the subcarrier spacing is 15KHz. Then there are 25 RBs in the 5MHz bandwidth. 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. Taking the reference BWP as 20MHz=106 RBs and the subcarrier spacing as 15KHz as an example, then N=Floor(106 /25)=The distribution of 4 candidate BWPs is shown in Figure 13. For any candidate BWP, 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:

S141. 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.

Optionally, the terminal device in the embodiment of this application is a light-capability device. For 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.

S142: 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.

Optionally, 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.

Optionally, the traffic channel includes at least any one of PUSCH and PDSCH.

Optionally, the reference signal includes at least one of DMRS for PDSCH, DMRS for PDCCH, CSI_RS, PTRS, and SRS.

For example, the relationship between system bandwidth and reference BWP can be understood with reference to Figure 4. As shown in Figure 4, the system bandwidth is a total large bandwidth, including 22 RBs, namely RB0 to RB21.

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. For example, in Figure 4, 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.

After obtaining the first message, 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.

In the above embodiment, 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.

Optionally, the first message includes MIB and/or system message.

Optionally, 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. In this embodiment, CORESET#0 is the reference BWP.

In the embodiment of this application, 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. For the different subcarrier intervals of SSB and CORESET#0, the embodiment of the present application provides a method to determine the first field index based on the existing field index in the MIB. For the scheme of the first frequency offset value and the second frequency offset value, please refer to Table 1 to Table 4 for details.

Optionally, 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.

Let’s introduce it with a concrete example. Assuming that the subcarrier spacing of SSB and CORESET#0 is {30,15}KHz, the default corresponding relationship is indicated by the above Table 1. Assume that the field PDCCH-ConfigSIB1----->controlResourceSetZero in the MIB has a value of 0, that is, the row index is 0. According to Table 1 above, it can be seen that the first frequency offset value is 2 RBs, and the second frequency offset value is 10 RBs. During initial access, the frequency domain position occupied by CORESET#0 is the frequency domain position occupied by the reference BWP. Therefore, according to Table 1 above, it can be seen that when the index is 0, the frequency domain position occupied by the reference BWP (i.e. CORESET#0) The bandwidth includes 48 RBs.

Optionally, 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.

Optionally, the second frequency offset value is a value configured through DCI. For example, a new 2-bit field can be added to the DCI to indicate the size of the second frequency offset value offset2. For example, when the new 2-bit field is 00, it means offset2=2RB. When the new 2-bit field is 01, it means offset2=5RB. When the new 2-bit field is 10, it means offset2=6RB. When the new 2-bit field is 11, it means offset2=10RB, and so on. It should be noted that 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. For example, 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 .

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, L1 in Figure 5.

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. As mentioned above, 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.

When the index is 0, according to Table 1 above, it can be seen that 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.

After determining the third frequency domain starting position of the target BWP occupied by the service channel, 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.

For example, in Figure 5, taking the sub-carrier spacing of the business channel as 15KHz as an example and the bandwidth size of the target BWP as 5MHz, it is equivalent to a target bandwidth size of 25 RBs. Therefore, 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).

For lightweight 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. Then, 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. At the same time, 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.

In the embodiment of Figure 5, it is introduced that 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 target BWP scheme occupied by the traffic channel. In addition to the MIB, 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.

Optionally, 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.

Optionally, 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.

Optionally, 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.

Optionally, 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.

First, the solution of determining the bandwidth occupied by the service channel on the first BWP when the BWP is the first BWP is introduced.

Optionally, the size of the first BWP is greater than or equal to the bandwidth size of the target BWP. For example, if 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.

Optionally, the third frequency offset value is a frequency offset between the first BWP and the frequency domain starting position of the traffic channel. After determining the frequency domain starting position of the first BWP based on the first starting resource block position and the first carrier offset value, 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. The following will be introduced in conjunction with Figure 6.

As shown in Figure 6, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.

After determining the frequency domain starting position of the service channel, 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.

Optionally, 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.

Optionally, after determining the bandwidth where the first BWP is located based on the first starting resource block position, the first carrier offset value, and the size of the first BWP, 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. The following will be introduced in conjunction with Figure 7.

As shown in Figure 7, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.

Then according to the second start resource block position O _carrier -redcap and the second carrier offset value RB _start -redcap, the frequency domain starting position of the service channel can be determined. As shown in Figure 7, the frequency domain of the bandwidth occupied by the service channel 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

After determining the frequency domain starting position of the service channel, 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.

In an implementation manner, 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.

As shown in Figure 8, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.

In the example of FIG. 8 , the size of the second BWP is the size of the reference BWP configured in the system message. At the same time, because the size of the second BWP is the bandwidth size, the second BWP is also the target BWP. Through the delay parameter, there is a delay between the traffic channel and the PDCCH. At this time, the traffic channel and the PDCCH can overlap in the frequency domain, or they can be located in different frequency domain positions. In the solution illustrated in Figure 8, the target BWP bandwidth size is 5 MHz, and 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. In the solution illustrated in Figure 8, the second BWP is the reference BWP, and 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. At this time, 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.

Optionally, the third frequency offset value is a frequency offset between the second BWP and the frequency domain starting position of the traffic channel. After determining the frequency domain starting position of the second BWP according to the first starting resource block position and the first carrier offset value, 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. The following will be introduced in conjunction with Figure 9.

As shown in Figure 9, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.

After determining the frequency domain starting position of the service channel, 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.

In one implementation, 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.

Optionally, the size of the target BWP occupied by the traffic channel may be, for example, a value less than or equal to 5 MHz.

Optionally, after determining the bandwidth of the second BWP based on the first starting resource block position, the first carrier offset value, and the size of the second BWP, 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. The following will be introduced in conjunction with Figure 10.

As shown in Figure 10, L0 is the common reference point of the resource grid, and its corresponding frequency domain position is known.

After determining the frequency domain starting position of the service channel, 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.

Optionally, the first message is a SIB1 or RRC message.

As shown in Figure 11, the position of the target BWP in the reference BWP can be indicated by adding a new bit in the first message. Assume that the subcarrier spacing between the reference BWP and the target BWP is 15KHz, and the size of the reference BWP is 20MHz=106RB. The BWP size is 5MHz=25RB, then N=Floor(106/25)=4, L=(106mod25)/2=3, that is, the reference BWP includes N=4 candidate BWPs, and 4 candidates are indicated by 2 bits Which of the BWPs is the target BWP? See the shaded part in Figure 11 for the four candidate BWPs.

As shown in Figure 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 size of the reference BWP is 20MHz=106RB, and the target BWP Taking the size of 5MHz=25RB as an example, then N=Floor(106/25)=4, L=(106mod25)/2=3, then the reference BWP includes N=4 candidate BWPs, indicated by 2 bits, reference BWP L = 3 RB protection RBs are reserved at both ends of , which is indicated by the shaded part in Figure 12 .

As shown in Figure 13, the default bandwidth size is 5MHz and the subcarrier spacing is 15KHz. Then there are 25 RBs in the 5MHz bandwidth. The 25 RBs are grouped. Every 5 consecutive RBs form a group of 25 RBs. 25 There are 5 consecutive 5RB groups of RBs. Taking the reference BWP as 20MHz=106 RBs and the subcarrier spacing as 15KHz as an example, then N=Floor(106/25)=4 candidate BWPs are distributed as shown in Figure 13 Show. For any candidate BWP, 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.

In the processing method provided by the embodiment of the present application, first the network device sends a first message to the terminal device. After receiving the first message, 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. According to the solution of the embodiment of the present application, in the scenario where the reference BWP occupied by SSB and CORESET#0 is greater than or equal to the target BWP occupied by the service channel, 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.

Figure 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;

Optionally, the determination module 1501 is specifically used to:

Optionally, the first message includes an index, and the determining module 1501 is also used to:

Optionally, 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 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 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;

Optionally, 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.

Optionally, the first message includes at least one of the following:

Optionally, the first message includes an index, and the determining module 1601 is also used to:

Optionally, the determination module 1601 is specifically used to:

In response to the time domain position of the traffic channel and/or the reference signal being the same as the time domain position of the physical downlink control channel, according to the frequency domain starting position and/or the bandwidth size, on the first bandwidth part Determine the portion of the target bandwidth occupied by the traffic channel; and/or,

In response to the existence of a delay between the time domain position of the traffic channel and/or the reference signal and the time domain position of the physical downlink control channel, according to the frequency domain starting position and/or the bandwidth size, A target bandwidth portion occupied by the traffic channel is determined on the second bandwidth portion.

Optionally, 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:

Figure 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;

Optionally, include at least one of the following:

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.

Optionally, include at least one of the following:

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.

Figure 18 is a schematic structural diagram of a communication device provided by an embodiment of the present application. As shown in Figure 18, 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, and the central processing unit can be used to control communication equipment, execute software programs, and process data of software programs.

Optionally, the processor 181 may also store instructions 183 or data (eg, intermediate data). Optionally, 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.

Optionally, the communication device 180 may include a circuit, which may implement the functions of sending or receiving or communicating in the foregoing method embodiments.

Optionally, 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.

Optionally, data may also be stored in the memory 182 . The processor 181 and the memory 182 can be provided separately or integrated together.

Optionally, 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 .

Optionally, 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. 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.

In this application, the communication device may be a terminal device or a network device (such as a base station). The specific needs are determined according to the context. In addition, the terminal device may be implemented in various forms. For example, 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.

Although in the above description of the embodiments, 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. When the computer program is executed by a processor, the steps of the processing method in any of the above embodiments are implemented.

In the embodiments of terminal equipment, network equipment and computer-readable storage media provided by the embodiments of this application, all technical features of any of the above-mentioned processing method embodiments can be included. The expanded and explanatory content of the description is basically the same as that of each embodiment of the above-mentioned method. They are the same and will not be repeated here.

Embodiments of the present application also provide a computer program product. The computer program product includes 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 above serial numbers of the embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

The steps in the methods of the embodiments of this application can be sequence adjusted, combined, and deleted according to actual needs.

The units in the equipment of the embodiments of this application can be merged, divided, and deleted according to actual needs.

In this application, the same or similar terms, concepts, technical solutions and/or application scenario descriptions are generally only described in detail the first time they appear. When they appear again later, for the sake of simplicity, they are generally not described again. When understanding the technical solutions and other content of this application, for the same or similar term concepts, technical solutions and/or application scenario descriptions that are not described in detail later, you can refer to the relevant previous detailed descriptions.

In this application, each embodiment is described with its own emphasis. For parts that are not detailed or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

The technical features of the technical solution of the present application can be combined in any way. In order to simplify the description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, all possible combinations can be used. It should be considered to be within the scope of description in this application.

Through the above description of the embodiments, those skilled in the art can clearly understand that 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. Based on this understanding, 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.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When computer program instructions are loaded and executed on a computer, processes or functions according to embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. 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 (such as infrared, wireless, microwave, etc.) 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.

The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the description and drawings of the present application may be directly or indirectly used in other related technical fields. , are all equally included in the patent protection scope of this application.

Claims

A processing method, characterized by including:

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;

Wherein, the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, the system bandwidth includes at least one carrier, and the bandwidth part of at least one carrier among the at least one carrier is in an inactive state.
The method according to claim 1, characterized in that 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, third frequency offset value, size of the reference bandwidth part, and indication information.
The method according to claim 2, characterized in that it includes at least one of the following:

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 method according to claim 2, wherein 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:

Determine the frequency domain starting position of the traffic channel and/or the reference signal according to the first message;

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 method according to claim 4, characterized in that 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 method of claim 5, wherein the first message includes an index, and 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 method according to any one of claims 4 to 6, characterized in that the time domain position of the reference bandwidth part is determined according to a delay parameter.
The method according to any one of claims 2 to 6, characterized in that the reference bandwidth part includes N candidate bandwidth parts, and the size of each candidate bandwidth part is the preset bandwidth size. ; Determining 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, including:

According to the indication information, determine the target bandwidth part among the N candidate bandwidth parts;

Wherein, the N=Floor(S/M), where the S is the size of the reference bandwidth part, and the M is the preset bandwidth size.
The method according to claim 8, characterized in that 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 N candidate bandwidth parts. The kth candidate bandwidth part in; includes 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;

Wherein, the k is a positive integer greater than or equal to 1 and less than or equal to N, the i is 0, 1, 2, ..., M-1 in sequence, the M is a positive integer, and the L is the number of resource blocks included between the lower edge of the reference bandwidth part and the first candidate bandwidth part.
A processing method, characterized by including:

Determine the target bandwidth part occupied by 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 reference signal;

Wherein, the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, the system bandwidth includes at least one carrier, and the bandwidth part of at least one carrier among the at least one carrier is in an inactive state.
The method according to claim 10, characterized in that the frequency domain starting position and/or the bandwidth size are determined according to a first message; and/or the first message is a main system information block and/or system information.
The method according to claim 11, characterized in that 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, third frequency offset value, the size of the reference bandwidth part, and the indication information.
The method according to any one of claims 10 to 12, characterized in that 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 method according to claim 13, wherein the first message includes an index, and 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 method according to any one of claims 10 to 12, characterized in that the service is determined on the reference bandwidth part according to the frequency domain starting position and/or bandwidth size of the service channel and/or the reference signal. The portion of the target bandwidth occupied by the channel and/or the reference signal includes:

In response to the time domain position of the traffic channel and/or the reference signal being the same as the time domain position of the physical downlink control channel, according to the frequency domain starting position and/or the bandwidth size, on the first bandwidth part determining said target bandwidth portion; and/or,

In response to the existence of a delay between the time domain position of the traffic channel and/or the reference signal and the time domain position of the physical downlink control channel, according to the frequency domain starting position and/or the bandwidth size, The target bandwidth portion is determined over a second bandwidth portion.
The method according to any one of claims 10 to 12, characterized in that the reference bandwidth part includes N candidate bandwidth parts, and the size of each of the candidate bandwidth parts is the bandwidth size; Determine the target bandwidth part occupied by 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 reference signal. ,include:

According to the indication information, determine the target bandwidth part among the N candidate bandwidth parts;

Wherein, the N=Floor (the size of the reference bandwidth part/the bandwidth size).
The method according to claim 16, characterized in that 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 N candidate bandwidth parts. The kth candidate bandwidth part in; includes 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;

Wherein, the k is a positive integer greater than or equal to 1 and less than or equal to N, the i is 0, 1, 2, ..., M-1 in sequence, the M is a positive integer, and the L is the number of resource blocks included between the lower edge of the reference bandwidth part and the first candidate bandwidth part.
A processing method, characterized by including:

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;

Wherein, the reference bandwidth part is the bandwidth part of a carrier on the system bandwidth, the system bandwidth includes at least one carrier, and the bandwidth part of at least one carrier among the at least one carrier is in an inactive state.
The method according to claim 18, characterized in that it includes at least one of the following:

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 Reference the size and indication information of the bandwidth part;

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 method according to claim 18 or 19, characterized in that 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 method according to claim 20, characterized in that the first message further 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 second frequency offset value.
The method according to claim 19, characterized in that 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;

Wherein, 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 method according to claim 22, characterized in that 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;

Wherein, the k is a positive integer greater than or equal to 1 and less than or equal to N, the i is 0, 1, 2, ..., M-1 in sequence, the M is a positive integer, and the L is the number of resource blocks included between the lower edge of the reference bandwidth part and the first candidate bandwidth part.
A communication device, characterized by 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 according to any one of claims 1 to 23.
A computer-readable storage medium, characterized in that a computer program is stored on the storage medium. When the computer program is executed, the processing method according to any one of claims 1 to 23 is implemented.