Resource processing method, communication device, and storage medium

Abstract

The application discloses a resource processing method, a communication device and a storage medium. The method comprises the following steps: receiving downlink information, and determining the available frequency domain resource position of a physical downlink shared channel according to a first strategy. The technical scheme of the application improves the effectiveness of frequency domain resource allocation, realizes flexible scheduling of frequency domain resources, and especially when the activated bandwidth part is greater than the maximum data scheduling bandwidth 5MHz, the granularity of the resource block group can be adjusted according to the actual scheduling data bandwidth, so that the scheduling flexibility is realized, the effective utilization of the frequency domain resource allocation field in the DCI is ensured, and the bit waste in the DCI is reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a resource processing method, communication device and storage medium. Background Technology

[0002] In existing uplink and downlink frequency domain resource allocation schemes, frequency domain resource allocation is defined based on the size of the active bandwidth portion. However, for the R18 enhanced lightweight terminal, the maximum bandwidth of its supported physical downlink shared channel is 5MHz, which is far smaller than the configured active bandwidth portion. If the existing frequency domain resource allocation scheme based on active bandwidth continues to be used, the following frequency domain resource allocation problems will occur:

[0003] For frequency domain resource allocation type 0, there is a problem that the granularity of resource block groups determined based on the active bandwidth portion is too large for R18 enhanced lightweight terminals, thus affecting the flexibility and effectiveness of frequency domain resource scheduling; and / or, for frequency domain resource allocation type 1, since the number of bits occupied by the frequency domain resource allocation field in the downlink control information is calculated according to the size of the active bandwidth portion, if the size of the active bandwidth portion is greater than 5MHz, there will be a problem of wasted bits in the downlink control information, which will also affect the flexibility and effectiveness of frequency domain resource scheduling.

[0004] In addition to the problem of wasted downlink control information bits due to excessively large resource block granularity, if the active bandwidth portion is greater than 5MHz, there will also be the problem of not being able to determine the effective 5MHz bandwidth frequency domain resources in the active bandwidth portion that need to be accurately received.

[0005] Therefore, the problem of how to achieve effective frequency domain resource scheduling in scenarios where the active bandwidth is greater than the maximum 5MHz bandwidth supported by the R18 enhanced lightweight terminal is an urgent problem to be solved. Summary of the Invention

[0006] The main objective of this application is to provide a resource processing method, communication device, and storage medium, which aims to improve the effectiveness of frequency domain resource allocation and realize flexible scheduling of frequency domain resources.

[0007] This application provides a resource processing method applicable to communication devices (such as mobile phones), comprising the following steps:

[0008] S20: Receive downlink information and determine the location of available frequency domain resources for the physical downlink shared channel according to the first strategy.

[0009] Optionally, there can be multiple ways to obtain or determine the first strategy. For example, the first strategy can be a preset strategy, or it can be obtained directly from the downlink information transmission, or it can be determined or generated through the content of the downlink information.

[0010] Optionally, the downlink information includes at least one of the following:

[0011] Number of transmissions; frequency domain resource allocation field that satisfies the first preset rule.

[0012] Optionally, the number of transmissions includes at least one of the following:

[0013] The number of transmissions is configured by downlink control information; the number of transmissions is related to the configuration period of the control resource set; the maximum value of the number of transmissions is related to the number of frequency domain resource groups.

[0014] Optionally, the number of frequency domain resource groups is determined by the size of the active bandwidth portion and the preset bandwidth.

[0015] Optionally, satisfying the first preset rule includes:

[0016] The frequency domain resource allocation field includes a resource block set and / or a first frequency domain resource allocation.

[0017] Optionally, the method further includes at least one of the following:

[0018] The size of the resource block set is related to the subcarrier spacing; the size of the resource block set is related to the preset bandwidth; the number of bits in the resource block set is related to the number of resource block sets in the active bandwidth; the number of bits in the resource block set is related to the representation method of the resource block sets in the active bandwidth; the number of bits allocated in the first frequency domain resource allocation is related to the frequency domain resource allocation type; the frequency domain resource position occupied by the resource block set is determined by a second preset formula related to the frequency domain position of the active bandwidth portion.

[0019] Optionally, the first strategy includes at least one of the following:

[0020] The location of available frequency domain resources for the physical downlink shared channel is determined according to a first preset formula related to the number of transmissions;

[0021] The available frequency domain resource locations of the physical downlink shared channel are determined by taking the intersection of the resource block set and the first frequency domain resource allocation in the frequency domain resource allocation field that satisfies the first preset rule.

[0022] The available frequency domain resources of the physical downlink shared channel are determined according to a preset bit truncation method;

[0023] The location of available frequency domain resources for the physical downlink shared channel is determined based on the scaling factor.

[0024] Optionally, the scaling factor is related to the active bandwidth size and / or the preset bandwidth.

[0025] This application also proposes a resource processing method applicable to communication equipment (such as a base station), comprising the following steps:

[0026] S10, send downlink information so that the terminal device can determine the location of available frequency domain resources of the physical downlink shared channel according to the first strategy.

[0027] Optionally, there can be multiple ways to obtain or determine the first strategy. For example, the first strategy can be a preset strategy, or it can be obtained directly from the downlink information transmission, or it can be determined or generated through the content of the downlink information.

[0028] Optionally, step S20 includes at least one of the following:

[0029] Send downlink information based on the wireless resource connection status;

[0030] The status is obtained based on the terminal type, and downlink information is sent.

[0031] Optionally, the downlink information includes at least one of the following:

[0032] Number of transmissions; frequency domain resource allocation field satisfying the first preset rule; downlink control information; radio resource control information; system information.

[0033] Optionally, the method further includes at least one of the following:

[0034] The number of transmissions is configured by downlink control information; the number of transmissions is related to the configuration period of the control resource set; the maximum value of the number of transmissions is related to the number of frequency domain resource groups.

[0035] Optionally, satisfying the first preset rule includes:

[0036] The frequency domain resource allocation field includes a resource block set and / or a first frequency domain resource allocation.

[0037] Optionally, the first strategy includes at least one of the following:

[0038] The location of available frequency domain resources for the physical downlink shared channel is determined according to a first preset formula related to the number of transmissions;

[0039] The available frequency domain resources of the physical downlink shared channel are determined by taking the intersection of the resource block set in the frequency domain resource allocation field and the first frequency domain resource allocation.

[0040] The available frequency domain resources of the physical downlink shared channel are determined according to a preset bit truncation method;

[0041] The location of available frequency domain resources for the physical downlink shared channel is determined based on the scaling factor.

[0042] This application also provides a resource processing apparatus, comprising:

[0043] The receiving module is used to receive downlink information and determine the location of available frequency domain resources of the physical downlink shared channel according to the first strategy.

[0044] This application also provides a resource processing apparatus, comprising:

[0045] The transmitting module is used to transmit downlink information so that the terminal device can determine the location of available frequency domain resources of the physical downlink shared channel according to the first strategy.

[0046] This application also provides a communication device, the communication device comprising: a memory, a processor, and a resource processing program stored in the memory and executable on the processor, wherein the resource processing program, when executed by the processor, implements the steps of any of the above-described resource processing methods.

[0047] This application also provides a storage medium storing a computer program that, when executed by a processor, implements the steps of any of the above-described resource processing methods.

[0048] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the steps of any of the resource processing methods described above.

[0049] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the steps of any of the above-described resource processing methods.

[0050] The technical solution of this application improves the effectiveness of frequency domain resource allocation and realizes flexible scheduling of frequency domain resources. In particular, when the active bandwidth is greater than the maximum data scheduling bandwidth by 5MHz, the granularity of the resource block group can be adjusted according to the actual scheduled data bandwidth to achieve scheduling flexibility and ensure the effective use of the frequency domain resource allocation field in the downlink control information, thereby reducing bit waste in the downlink control information. Attached Figure Description

[0051] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0052] Figure 1 A schematic diagram of the hardware structure of a mobile terminal to implement the various embodiments of this application;

[0053] Figure 2 A communication network system architecture diagram provided for an embodiment of this application;

[0054] Figure 3 This is a schematic diagram of the hardware structure of the controller 140 involved in the resource processing method embodiment of this application;

[0055] Figure 4 This is a schematic diagram of the hardware structure of the network node 150 involved in the resource processing method embodiment of this application;

[0056] Figure 5 This is a schematic diagram illustrating the interaction process between the terminal device and the network device in an embodiment of the resource processing method of this application;

[0057] Figure 6 This is a schematic diagram illustrating the allocation of frequency domain resource indexes in the embodiments of the resource processing method of this application;

[0058] Figure 7 This is a schematic diagram of the frequency domain resources included in the first type of RB set involved in the resource processing method embodiments of this application;

[0059] Figure 8 This is a schematic diagram of the frequency domain resources included in the second type of RB set involved in the resource processing method embodiments of this application;

[0060] Figure 9 This is a schematic diagram of the frequency domain resources included in the third RB set involved in the resource processing method embodiments of this application;

[0061] Figure 10 This is a schematic diagram of the frequency domain resources included in the fourth RB set involved in the resource processing method embodiments of this application;

[0062] Figure 11 This is a schematic diagram of the frequency domain resources included in the fifth type of RB set involved in the resource processing method embodiments of this application;

[0063] Figure 12 This is a schematic diagram of the physical downlink shared channel frequency domain scheduling of an R18 enhanced lightweight terminal according to an embodiment of the resource processing method of this application;

[0064] Figure 13 This application relates to another embodiment of the resource processing method for a physical downlink sharing system for an R18 enhanced lightweight terminal.

[0065] Figure 14This is a schematic diagram illustrating the bandwidth reception before bit truncation for traditional equipment.

[0066] Figure 15 This is a schematic diagram of the bandwidth reception after bit truncation for the R18 enhanced lightweight capability terminal in this application embodiment;

[0067] Figure 16 This is a schematic diagram of the frequency domain mapping resource location of a 5MHz physical downlink shared channel involved in the resource processing method embodiments of this application;

[0068] Figure 17 This is a schematic diagram of another frequency domain mapping resource location for the 5MHz physical downlink shared channel involved in the resource processing method embodiments of this application.

[0069] The realization of the objectives, functional features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0070] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0071] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0072] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, may be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used in this application, may be interpreted as inclusive, or mean any one or any combination thereof. For example, "including at least one of the following: A, B, C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Similarly, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Exceptions to this definition only occur when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0073] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0074] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0075] It should be noted that step designations such as S10 and S20 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S20 first and then S10, etc., but these should all be within the protection scope of this application.

[0076] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0077] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0078] The communication equipment mentioned in this application may be a terminal device (such as a mobile terminal, specifically a mobile phone) or a network device (such as a base station). The specific meaning needs to be clarified in the context.

[0079] Optionally, the terminal device can be implemented in various forms. For example, the terminal devices described in this application may include smart terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, and fixed terminals such as digital TVs and desktop computers.

[0080] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to the embodiments of this application can also be applied to fixed-type terminals.

[0081] Please see Figure 1 This is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application. The mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that... Figure 1 The mobile terminal structure shown does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0082] The following is combined with Figure 1 A detailed introduction to each component of the mobile terminal:

[0083] The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, and a duplexer. Furthermore, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), and 5G, etc.

[0084] WiFi is a short-range wireless transmission technology. Mobile terminals, through the WiFi module 102, can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 1 WiFi module 102 is shown, but it is understood that it is not a necessary component of a mobile terminal and can be omitted as needed without changing the nature of the invention.

[0085] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, etc. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0086] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0087] 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 ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0088] 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.

[0089] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Optionally, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to processor 110, and can receive and execute commands sent by processor 110. In addition, 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 the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being specifically limited here.

[0090] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 based on the type of touch event. Although in Figure 1 In this embodiment, the touch panel 1071 and the display panel 1061 are two independent components to realize the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.

[0091] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more elements within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.

[0092] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0093] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of 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 handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.

[0094] 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 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0095] although Figure 1 As not shown, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0096] To facilitate understanding of the embodiments of this application, the communication network system on which the mobile terminal of this application is based is described below.

[0097] Please see Figure 2 , Figure 2 This application provides a communication network system architecture diagram. The communication network system is an LTE system based on the universal mobile communication technology. The LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and the operator's IP services 204, which are connected in sequence.

[0098] Optionally, UE201 can be the aforementioned terminal 100, which will not be described in detail here.

[0099] E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc. Optionally, eNodeB2021 can connect to other eNodeB2022 via backhaul (e.g., X2 interface), and eNodeB2021 connects to EPC203, providing access from UE201 to EPC203.

[0100] EPC203 may include MME (Mobility Management Entity) 2031, HSS (Home Subscriber Server) 2032, other MMEs 2033, SGW (Serving Gateway) 2034, PGW (Packet Data Network Gateway) 2035, and PCRF (Policy and Charging Rules Function) 2036, etc. Optionally, MME2031 is the control node that handles signaling between UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as the Home Location Register (not shown in the figure) and stores user-specific information such as service characteristics and data rates. All user data can be sent through SGW2034. PGW2035 can provide UE 201 IP address allocation and other functions. PCRF2036 is the policy and charging control decision point for service data flow and IP bearer resources. It selects and provides available policy and charging control decisions for the policy and charging enforcement function unit (not shown in the figure).

[0101] IP services 204 may include the Internet, intranet, IMS (IP Multimedia Subsystem), or other IP services.

[0102] Although the above description uses 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 to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., without limitation.

[0103] Based on the above-described mobile terminal hardware structure and communication network system, various embodiments of this application are proposed.

[0104] Figure 3 This is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0105] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0106] Figure 4 This application provides a schematic diagram of the hardware structure of a network node 150. The network node 150 includes a memory 1501 and a processor 1502. The memory 1501 is used to store program instructions, and the processor 1502 is used to call the program instructions in the memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0107] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0108] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0109] Technical terms used in this embodiment:

[0110] RB: Resource Block;

[0111] RBG: Resource Block Groups;

[0112] RB set: Resource Block set;

[0113] FDRA: Frequency domain resource assignment;

[0114] SIB1: System Information Block 1;

[0115] CSS: Common search space;

[0116] USS: UE-specific search space;

[0117] BWP: Bandwidth Part. BWP is a new concept introduced by NR, designed to adapt to various types of terminals. Because NR is a high-bandwidth system, not all terminals can utilize this high bandwidth, so this low-bandwidth system can be used. BWP essentially divides the 5G spectrum into many small blocks within a certain time frame, and each BWP can use different parameter sets, such as different bandwidth, subcarrier spacing, and other control parameters.

[0118] CORESET: Control Resource set;

[0119] RRC: Radio Resource Control;

[0120] MSB: Most Significant Bit;

[0121] LSB: Least Significant Bit;

[0122] PDSCH: Physical Downlink Shared Channel;

[0123] DCI: Downlink Control Information;

[0124] RIV: Resource Indication Value;

[0125] SI-RNTI: System Information Radio-Network Temporary Identifier;

[0126] CRB: Common Resource Block;

[0127] PRB: Physical Resource Block.

[0128] Reference Figure 5 As shown in the figure, this application proposes a resource processing method, including the following steps:

[0129] S10, the network device sends downlink information;

[0130] S20, the terminal device receives downlink information and determines the location of available frequency domain resources of the physical downlink shared channel according to the first strategy.

[0131] The resource processing method of this application embodiment can be applied to terminal devices (such as mobile phones) (hereinafter referred to as terminals) or network devices (such as base stations).

[0132] Optionally, the downlink information is sent by the network device. After receiving the downlink information sent by the network device, the terminal determines the location of available frequency domain resources of the physical downlink shared channel based on the received downlink information and according to the first strategy.

[0133] Optionally, the available frequency domain resource location can be the available frequency domain resource location of the physical downlink shared channel of the R18 enhanced lightweight terminal.

[0134] Optionally, the network device may send downlink information to the terminal device based on the wireless resource connection status and / or terminal type.

[0135] Optionally, the terminal type acquisition status refers to whether the base station corresponding to the current serving cell knows the terminal type.

[0136] Optionally, the terminal type may include a traditional terminal, an R17 Light Capability Device terminal, and an R18 Enhanced Light Capability Device terminal.

[0137] Optionally, the downlink information includes at least one of the following:

[0138] Downlink control information; radio resource control information; system information.

[0139] Optionally, the downlink information may further include at least one of the following: number of transmissions; frequency domain resource allocation field that satisfies a first preset rule.

[0140] Optionally, the embodiments of this application further include at least one of the following: the number of transmissions is configured by downlink control information; the number of transmissions is related to the configuration period of the control resource set; and the maximum value of the number of transmissions is related to the number of frequency domain resource groups.

[0141] Optionally, the number of frequency domain resource groups is determined by the size of the active bandwidth portion and the preset bandwidth.

[0142] Optionally, the preset bandwidth is determined by the bandwidth of the maximum physical downlink shared channel that the R18 enhanced lightweight terminal can handle.

[0143] Optionally, satisfying the first preset rule includes: the frequency domain resource allocation field includes a resource block set and a first frequency domain resource allocation.

[0144] Optionally, the method further includes at least one of the following: the size of the resource block set is related to the subcarrier spacing; the size of the resource block set is related to the preset bandwidth; the number of bits in the resource block set is related to the number of resource block sets in the active bandwidth; and the number of bits in the resource block set is related to the representation method of the resource block sets in the active bandwidth.

[0145] Optionally, the frequency domain resource location occupied by the resource block set is determined by a second preset formula related to the frequency domain location of the activated bandwidth portion.

[0146] Optionally, the number of bits allocated in the first frequency domain resource allocation is related to the frequency domain resource allocation type.

[0147] Optionally, there can be multiple ways to obtain or determine the first strategy. For example, the first strategy can be a preset strategy, or it can be obtained directly from the downlink information transmission, or it can be determined or generated through the content of the downlink information.

[0148] Optionally, the first strategy includes at least one of the following:

[0149] The available frequency domain resource location of the physical downlink shared channel is determined according to a first preset formula related to the number of transmissions; the available frequency domain resource location of the physical downlink shared channel is determined by taking the intersection of the resource block set and the first frequency domain resource allocation in the frequency domain resource allocation field that satisfies the first preset rule; the available frequency domain resource location of the physical downlink shared channel is determined according to a preset bit truncation method; and the available frequency domain resource location of the physical downlink shared channel is determined according to a scaling factor.

[0150] Optionally, the scaling factor is related to the active bandwidth size and the preset bandwidth.

[0151] Optionally, the first strategy is related to the wireless resource connection status of the terminal and / or whether the base station knows the terminal type to which the terminal belongs.

[0152] Optionally, the wireless resource connection state includes RRC connected state, RRC idle state, and RRC inactive state.

[0153] The following section provides a detailed explanation of the first strategy and its specific implementation in this embodiment, considering different scenarios:

[0154] Optionally, as a first scenario, when the terminal initially accesses the network (before the terminal enters the RRC connection state) and / or the base station does not know the terminal type, the first strategy can be: determine the available frequency domain resource location of the physical downlink shared channel of the R18 enhanced lightweight terminal according to a first preset formula related to the number of transmissions.

[0155] Optionally, the number of transmissions refers to how many times the current periodic physical downlink shared channel transmission is repeated within the period.

[0156] Optionally, the number of transmissions can be obtained from the transmission count field in the downlink control information;

[0157] Optionally, the number of transmissions can also be obtained based on the control resource set configuration in the radio resource control information or system information;

[0158] Optionally, if the physical downlink shared channel is a periodic service, the transmission count can be determined by the number of times the control resource set appears in the period. For example, if the period of the physical downlink shared channel is 160ms, and the period starts at subframe 0 of radio frame 0, then the 160ms period of the physical downlink shared channel refers to all subframes from radio frame 0 to radio frame 16. Based on the control resource set configuration in the radio resource control information or system information, the number of times the control resource set associated with the periodic physical downlink shared channel appears in this 160ms period can be obtained, thus determining the total number of times the physical downlink shared channel appears in the 160ms period.

[0159] Optionally, the number of transmissions can also depend on the UE implementation.

[0160] Optionally, if the number of transmissions depends on the UE implementation, the UE takes the physical downlink shared channel received at the beginning of each cycle point as the first transmission, and accumulates the count of which physical downlink shared channel transmission the current reception is.

[0161] Optionally, the first preset formula is determined by the number of transmissions, the frequency domain resource allocation field that satisfies the first preset rule, and / or the preset bandwidth.

[0162] Optionally, the frequency domain resource allocation field that satisfies the first preset rule can be located in the downlink control information.

[0163] Optionally, the specific implementation of the first strategy, "determining the available frequency domain resource location of the physical downlink shared channel of the R18 enhanced lightweight terminal according to a first preset formula related to the number of transmissions," is described below:

[0164] First, the frequency domain position of the periodic transmission service in the BWP is obtained based on the RIV value corresponding to the frequency domain resource allocation field that meets the first preset rule in the downlink information, such as the frequency domain resource start position, the number of continuous RBs of the frequency domain resource, or the frequency domain mapping position of the resource block group.

[0165] Secondly, the number of consecutive RBs D corresponding to the preset bandwidth is obtained based on the downlink information or pre-configuration information.

[0166] Finally, based on the frequency domain position and a first preset formula related to the number of transmissions, the D consecutive RB indices that the terminal can process during the Gth transmission are calculated.

[0167] Optionally, the proportion of transmission count and frequency domain resource allocation fields is processed as follows:

[0168] The frequency domain resource allocation field is located in the downlink control information, and its number of bits is [number missing]. in, It refers to the number of RBs occupied by CORESET#0 or the number of RBs occupied by the initial downlink bandwidth portion.

[0169] If the number of transmissions is obtained from the transmission count field in the downlink control information, then its percentage is related to the maximum number of transmissions required for a periodic service to complete its coverage requirements within a period.

[0170] For example, if the SIB1 transmission period is 160ms, with one SIB1 transmission opportunity every 20ms, and the maximum number of transmissions required to complete or accurately receive SIB1 is 5, then the number of bits occupied by the transmission count field in the downlink control information is 3, where "000" represents the first SIB1 transmission within the 160ms period, "001" represents the second transmission within the 160ms period, and so on. If the maximum number of transmissions required to complete or accurately receive SIB1 is 4, then the number of bits occupied by the transmission count field in the downlink control information is 2, where "00" represents the first SIB1 transmission within the 160ms period, "01" represents the second transmission within the 160ms period, and so on.

[0171] Optionally, the maximum number of transmissions required for a periodic service to complete its coverage requirement within a period is determined by ceil (active bandwidth portion size / pre-bandwidth size).

[0172] If the number of transmissions is obtained based on the control resource set configuration in the radio resource control information or system information, then the number of transmissions does not consume any downlink signaling.

[0173] Optionally, if the period of the physical downlink shared channel is 160ms, and if the starting position of the period is subframe 0 of radio frame 0, then the 160ms period of the physical downlink shared channel refers to all subframes from radio frame 0 to radio frame 16. Based on the control resource set configuration in the radio resource control information or system information, the number of times the control resource set associated with the periodic physical downlink shared channel appears within this 160ms period can be obtained, thereby obtaining the number of times the physical downlink shared channel appears within the 160ms period.

[0174] If the number of transmissions depends on the UE implementation, then the UE takes the physical downlink shared channel received at the beginning of each cycle point as the first transmission, and accumulates the count of which physical downlink shared channel transmission the current reception is.

[0175] In one implementation, the number of transmissions and the number of frequency domain resource groups of the physical downlink shared channel are mapped non-interleaved.

[0176] Optionally, the number of transmissions and the number of frequency domain resource groups of the physical downlink shared channel are mapped in a non-interleaved manner, meaning that the first physical downlink shared channel reception can receive the first group of frequency domain resource locations, the second physical downlink shared channel reception can receive the second group of frequency domain resource locations, and so on.

[0177] Taking the periodic service SIB1 as an example, the specific implementation of the UE determining the frequency domain resource location of the physical downlink shared channel according to the first preset formula related to the number of transmissions is as follows:

[0178] Step 1: Obtain the current transmission count G of periodic service SIB1, that is, obtain the Gth transmission of SIB1 in this time slot;

[0179] Step 2: Obtain the RB of SIB1 in the active bandwidth portion based on the RIV value corresponding to the frequency domain resource allocation field in the SI-RNTI scrambled DCI. start and L RBs , among which, RB start The frequency domain start position of SIB1 in the active bandwidth portion and L RBs The length of the frequency domain persistent resource block for SIB1 in the active bandwidth portion;

[0180] Step 3: Calculate the frequency domain starting RB index of the R18 enhanced lightweight terminal according to the first preset formula related to the number of transmissions. The first preset formula related to the number of transmissions can be expressed as follows:

[0181] RB′ start =(RB) start +(T-1)*D)mod(L RBs +RB start );

[0182] Where D is the number of consecutive RBs corresponding to the preset bandwidth, and T is the number of frequency domain resource groups of the physical downlink shared channel. If the number of transmissions and the number of frequency domain resource groups of the physical downlink shared channel are mapped in a non-interleaved manner, then T is equal to the number of transmissions G.

[0183] Optionally, the preset bandwidth is determined by the bandwidth of the maximum physical downlink shared channel that the R18 enhanced lightweight terminal can handle.

[0184] Based on the above formula, the D consecutive RB indices of the R18 enhanced lightweight capability terminal are obtained as follows:

[0185] RB′ start 、(RB′ start +1)mod(L RBs +RB start ),......,(RB′ start +D-1)mod(L RBs +RB start ).

[0186] Optionally, D is related to the subcarrier spacing. Taking a preset bandwidth of 5MHz as an example, the number of consecutive RBs D that the R18 enhanced lightweight terminal can process each time is shown in Table 1 below:

[0187] Table 1. Number of consecutive RBDs that the R18 enhanced lightweight capability terminal can process per cycle

[0188] The subcarrier spacing is 15 kHz. The subcarrier spacing is 30kHz. 25RB 11RB / 12RB (PRACH)

[0189] Assuming the physical downlink shared channel subcarrier spacing is 15kHz, the number of consecutive RBs corresponding to the 5MHz preset bandwidth is D = 25RB, the CORESET#0 bandwidth is 48RB, the PDSCH frequency domain resource allocation type is 1, and the RIV value corresponding to the frequency domain resource allocation field in the DCI is 861, based on the RIV value and the following formula:

[0190]

[0191] RB can be obtained start =2,L RBs =32, where, The size of the activated BWP.

[0192] Optionally, if the number of transmissions G in this time slot SIB1 is 1, according to

[0193] RB′ start =(RB) start +(G-1)*D)mod(L RBs +RB start )

[0194] = (2 + (1 - 1) * 25) mod (32 + 2)

[0195] =2

[0196] Therefore, the 25 consecutive RB indices of the R18 enhanced lightweight capability terminal are: 2, 3, 4, ..., 26, as shown in the reference. Figure 6 As shown.

[0197] If the number of transmissions G = 2, according to

[0198] RB′ start =(RB) start +(G-1)*D)mod(L RBs +RB start )

[0199] = (2 + (2 - 1) * 25) mod (32 + 2)

[0200] =27;

[0201] Therefore, the 25 consecutive RB indices of the R18 enhanced lightweight capability terminal are: 27, 28, ..., 33, 0, 1, ..., 17.

[0202] It should be noted that the above RB indices are based on the active bandwidth portion, that is, RB index 0 corresponds to the first RB index in the active BWP.

[0203] In another implementation, the number of transmissions and the number of receiver groups for the physical downlink shared channel frequency domain resources are interleaved.

[0204] Optionally, the number of transmissions and the number of frequency domain resource reception groups of the physical downlink shared channel are interleaved. This means that the first physical downlink shared channel reception can be the reception of the Mth group of frequency domain resource locations, and the second physical downlink shared channel reception can be the reception of the Nth group of frequency domain resource locations. Here, M and N are not necessarily consecutive groups of frequency domain resource locations, and M and N both correspond to the parameter T in the first preset formula in step 3 above.

[0205] Compared to existing technologies, in this embodiment, when the terminal initially accesses the network and / or the base station has not yet learned the type of the terminal device, for certain periodic transmission services, such as SIB1, the terminal can determine which transmission is being performed on the physical downlink shared channel based on the number of transmissions. Therefore, without modifying the existing frequency domain resource allocation field bit count and mapping rules, the terminal can complete the full reception of periodic transmission services based on the frequency domain reception scheme related to the number of transmissions. This solution ensures effective compatibility between lightweight capability devices and traditional devices, guarantees the full reception of periodic services by lightweight capability devices in limited bandwidth scenarios, and ensures the scheduling flexibility of lightweight capability devices.

[0206] Optionally, as a second scenario, when the terminal is in RRC connected state and / or the base station knows the terminal device type, the first strategy can be: the UE determines the available frequency domain resource location of the physical downlink shared channel of the R18 enhanced lightweight terminal by taking the intersection of the resource block set and the first frequency domain resource allocation in the frequency domain resource allocation field that satisfies the first preset rule.

[0207] Optionally, satisfying the first preset rule includes at least one of the following:

[0208] The frequency domain resource allocation field includes a resource block set and a first frequency domain resource allocation;

[0209] The frequency domain resource allocation field only includes the first frequency domain resource allocation.

[0210] Optionally, the frequency domain resource allocation field that satisfies the first preset rule can be located in the DCI;

[0211] Optionally, the resource block set takes the most significant bit (MSB) of X from the frequency domain resource allocation field; the first frequency domain resource allocation takes the least significant bit (LSB) of Y from the frequency domain resource allocation field.

[0212] Optionally, the number of bits Y occupied by the first frequency domain resource allocation is related to the frequency domain resource allocation type of the physical downlink shared channel;

[0213] Optionally, the number of bits X occupied by the resource block set is related to at least one of the following: the active bandwidth size, the bandwidth size of the maximum physical downlink shared channel supported by the UE, or the subcarrier spacing;

[0214] Alternatively, the resource block set can also be configured by radio resource control information or system information;

[0215] Optionally, the maximum number of resource blocks contained in the resource block set is related to the subcarrier spacing.

[0216] Optionally, in one embodiment, the specific implementation of the first strategy "the UE determines the location of available frequency domain resources for the physical downlink shared channel of the R18 enhanced lightweight terminal by taking the intersection of the resource block set and the first frequency domain resource allocation in the frequency domain resource allocation field that satisfies the first preset rule" is described as follows:

[0217] First, the location of the resource block set containing the frequency domain resources of the physical downlink shared channel is determined based on X resource block set bits;

[0218] Secondly, the frequency domain resource location of the physical downlink shared channel in the aforementioned determined resource block set is determined based on the frequency domain resource allocation type of the physical downlink shared channel and the Y first frequency domain resource allocation bits in the frequency domain resource allocation field.

[0219] Optionally, the frequency domain resource location occupied by the resource block set is determined by a second preset formula related to the frequency domain location of the activated bandwidth portion.

[0220] In one implementation, if the "Frequency Domain Resource Allocation" field in the DCI includes both a resource block set and a first frequency domain resource allocation, and the resource block set occupies X most significant bits of the "Frequency Domain Resource Allocation" field, while the first frequency domain resource allocation occupies Y least significant bits of the "Frequency Domain Resource Allocation" field, then the UE determines the resource block set where the physical downlink shared channel frequency domain resources are located based on the X most significant bits, and then determines the specific frequency domain RB position of the physical downlink shared channel in the resource block set based on the frequency domain resource allocation type of the physical downlink shared channel and the Y least significant bits. The specific implementation is as follows:

[0221] Suppose that the number of bits in the frequency domain resource allocation field in DCI is X+Y bits, where X most significant bits provide the location of the resource block set, and Y least significant bits provide the specific available RB index within the specified resource block set.

[0222] Optionally, the number of bits corresponding to X is related to the number of resource block sets in the active bandwidth and the representation method of the resource block sets in the active bandwidth. For example, if the number of resource block sets in the active bandwidth is 6, and the number of resource block sets in the active bandwidth that need to be represented at each time is greater than 1, then X takes the value of 6. If the number of resource block sets in the active bandwidth that need to be represented at each time is 1, then X takes the value of 3.

[0223] Optionally, the number of bits corresponding to Y is related to the frequency domain resource allocation type. For example, if the frequency domain resource mapping type of the physical downlink shared channel is frequency domain resource allocation type 0, then the value of Y is... If the frequency domain resource mapping type of the physical downlink shared channel is frequency domain resource allocation type 1, then the value of Y is... If the frequency domain resource allocation type of the physical downlink shared channel is 'dynamicSwitch', then Y takes the value of Furthermore, its highest bit is used to determine whether it is resource allocation type 0 or resource allocation type 1. Among these, Where P is the number of consecutive redundancies (RBs) contained in the resource block set, and P is the RBG granularity determined by the newly added radio resource control parameter resourceAllocationType1GranularityDCI-1-0-r17. This represents the start position of the frequency domain resources for a given set of resource blocks.

[0224] Optionally, the radio resource control parameter resourceAllocationType1GranularityDCI-1-0-r17 is:

[0225] resourceAllocationType1GranularityDCI-1-0-r17={n2, n4}.

[0226] Optionally, if the frequency domain resource allocation type of the physical downlink shared channel is configured as 'dynamicSwitch', if the highest bit of the first frequency domain resource allocation is 0, it means that 'dynamicSwitch' indicates that the frequency domain resource allocation type of the current PDSCH is frequency domain resource allocation type 0; if the highest bit of the first frequency domain resource allocation is 1, it means that 'dynamicSwitch' indicates that the frequency domain resource allocation type of the current physical downlink shared channel is frequency domain resource allocation type 1.

[0227] Optionally, the value of P can be less than or equal to the size of the resource block group corresponding to the active bandwidth. This solves the problem of wasted frequency domain resources caused by excessively large resource block group allocation granularity due to an excessively large active bandwidth, as well as the problem of frequency domain scheduling flexibility.

[0228] In another implementation, if the "Frequency Domain Resource Allocation" field in the DCI only includes the first frequency domain resource allocation, and the frequency domain location of the resource block set is determined by the radio resource control message, system message, or pre-configuration, then the number of bits occupied by the "Frequency Domain Resource Allocation" field in the DCI is Y. The specific value of Y is the same as the definition in the implementation where the "Frequency Domain Resource Allocation" field in the DCI simultaneously includes both the resource block set and the first frequency domain resource allocation.

[0229] The specific definition of a resource block set will be explained in detail below:

[0230] First, determine the number of RBs corresponding to different subcarrier spacing scenarios based on the preset bandwidth.

[0231] Optionally, taking a preset bandwidth of 5MHz as an example, the number of RBs in a resource block set for a carrier with a subcarrier spacing of 15kHz is... For a carrier with a subcarrier spacing of 30kHz, the number of resource blocks (RBs) in a resource block set. or

[0232] Secondly, based on the different handling methods for resource block sets (represented by RB set in the following formulas) depending on whether the resource block set requires a protection band or the remaining resource blocks that do not meet the maximum number of resource blocks in the resource block set, the following five different definition methods for resource block sets are given:

[0233] Optionally, the frequency domain resource location occupied by the resource block set is determined by a second preset formula related to the frequency domain location of the active bandwidth portion, wherein the second preset formula is a calculation formula for the CRB index at the beginning and end of each resource block set.

[0234] Method 1: The second preset formula corresponding to the CRB indices at the beginning and end of each RB set is as follows:

[0235]

[0236] Where s is the index of the RB set, The number of RBs contained in each RB set is calculated using the following formula:

[0237]

[0238] The number of RBs contained in the RB set is The number of RBs included in the active bandwidth is For example, the activation bandwidth includes a total of There are several RB sets, and the frequency domain resources contained in each RB set are illustrated as follows: Figure 7 As shown.

[0239] Method 2:

[0240] The second preset formula corresponding to the CRB indices at the beginning and end of each RB set is as follows:

[0241]

[0242] or

[0243]

[0244] Where s is the index of the RB set, The number of RBs contained in each RB set is calculated using the following formula:

[0245]

[0246] The number of RBs contained in the RB set is The number of RBs included in the active bandwidth is For example, the total activation bandwidth is Each RB set contains frequency domain resources such as... Figure 8 As shown.

[0247] Method 3:

[0248] The second preset formula corresponding to the CRB indices at the beginning and end of each RB set is as follows:

[0249]

[0250] Where s is the index of the RB set, The number of RBs contained in each RB set is calculated using the following formula:

[0251]

[0252] The number of RBs contained in the RB set is The number of RBs included in the active bandwidth is For example, the total activation bandwidth is... Each RB set contains frequency domain resources such as... Figure 9 As shown:

[0253] Method 4:

[0254] The second preset formula corresponding to the CRB indices at the beginning and end of each RB set is as follows:

[0255]

[0256] Where x is a certain RB set in the middle and the number of RBs it contains is: s is the index of the RB set. The number of RBs contained in each RB set is calculated using the following formula:

[0257]

[0258] The number of RBs contained in the RB set is The number of RBs included in the active bandwidth is For example, the total activation bandwidth is... Each RB set contains frequency domain resources such as... Figure 10 As shown:

[0259] Method 5:

[0260] The second preset formula corresponding to the CRB index at the beginning and end of each RB set must satisfy the following design:

[0261] Step 1: Set the guard band in the RB set;

[0262] Optionally, the protective strip contains RBs of number 1. One RB;

[0263] Step 2: Determine the location of the guard band within the active bandwidth, such as the guard band being located at the highest frequency edge of the active bandwidth, the lowest frequency edge of the active bandwidth, or any position in the middle of the active bandwidth.

[0264] Step 3: After deducting the RB containing the guard band from the active bandwidth, divide it evenly according to the frequency domain from low to high. If the guard band is located at the highest frequency edge of the active bandwidth, then the CRB index corresponding to RB 0 in the active bandwidth is the starting CRB index of the first RB set. The corresponding CRB index is the end CRB index of the first RB set, activating the bandwidth portion. The corresponding CRB index is the starting CRB index of the Xth RBset, activating the bandwidth portion. The corresponding CRB index is the CRB index of the end of the Xth RB set, and so on.

[0265] Optionally, the frequency domain resources contained in each RB set are as follows: Figure 11 As shown. The scenario where the guard band is located at the lowest frequency edge or any position in the middle of the active bandwidth is similar to the scenario where the guard band is located at the highest frequency edge of the active bandwidth. Both scenarios involve subtracting the RB containing the guard band, dividing the bandwidth evenly, and then selecting continuous... Each RB is considered as an RB set.

[0266] The number of RBs contained in the RB set is The number of RBs included in the active bandwidth is For example, the total activation bandwidth is... RB set.

[0267] Optionally, after receiving the frequency domain resource allocation field in the downlink control information, the terminal first determines the resource block set index where the physical downlink shared channel of the R18 enhanced lightweight terminal is located according to any of the five methods mentioned above. Then, it determines the specific resource block index of the physical downlink shared channel of the R18 enhanced lightweight terminal in the specified resource block set according to the frequency domain resource allocation type of the physical downlink shared channel and the first frequency domain resource allocation. Finally, the specific frequency domain resource location of the physical downlink shared channel of the R18 enhanced lightweight terminal in the BWP can be determined.

[0268] The following example illustrates how to determine the frequency domain resource location of the physical downlink shared channel using method 5 described above:

[0269] In one implementation, taking the physical downlink shared channel frequency domain resource allocation type as 1 and the RB set definition as in Method 5 as an example, suppose the frequency domain resource allocation field simultaneously contains the resource block set and the first frequency domain resource allocation, and the frequency domain resource allocation field is "010100101001", where the highest 3 bits of the resource block set index bits are '010', and the lowest 9 bits of the first frequency domain resource allocation bits are '100101001'. Then, according to the resource block set index bits, the resource block set index where the PDSCH is located is 3, and according to the first frequency domain resource allocation bits, the RIV value corresponding to the first frequency domain resource allocation is 297. Optionally, according to the following formula:

[0270]

[0271] The frequency domain resource start position RB of the physical downlink shared channel of the R18 enhanced lightweight terminal can be obtained in the resource block set with index 3. start =2, the number of persistent resource blocks L RBs =15. Finally, the available PRB indices for the physical downlink shared channel of the R18 enhanced lightweight terminal are: PRB77~PRB91, as detailed below. Figure 12 As shown.

[0272] Another implementation method is illustrated using the example of a physical downlink shared channel frequency domain resource allocation type of 0 and an RB set defined as described in method 5:

[0273] Assuming the active bandwidth is 106 RBs, the preset bandwidth is 5MHz, and the subcarrier spacing of the physical downlink shared channel is 15kHz, then the number of RBs in an RB set can be determined based on the 15kHz subcarrier spacing of the physical downlink shared channel. Based on the size of the activated bandwidth portion and the preset bandwidth size, the total number of RB sets is: If only one RB set needs to be indicated at each time point, then the number of bits required for the resource block set index indication is X = 3. Assuming the newly added RRC parameter resourceAllocationType1GranularityDCI-1-0-r17 determines P to be 2, then based on the number of RBs contained in an RB set and the value of P, the number of bits required for the first frequency domain resource can be obtained as follows:

[0274] Optionally, assuming the newly added radio resource control parameter resourceAllocationType1GranularityDCI-1-0-r17 determines that P is 2, taking the physical downlink shared channel frequency domain resource allocation type as 1 and the RB set definition as in Method 5 as an example, assuming the frequency domain resource allocation field simultaneously includes the resource block set and the first frequency domain resource allocation, and the "frequency domain resource allocation" field is "010 1001010000101", where the highest 3 bits of the resource block set index bit is '010', and the lowest 13 bits of the first frequency domain resource allocation bit is '1001010000101', then according to the resource block set index bit, the index of the resource block set where the physical downlink shared channel is located can be obtained as 3, and according to the first frequency domain resource allocation bit, the index of the available resource block group within the specified resource set can be obtained.

[0275] Optionally, the number of RBs contained in each resource block group (RBG) is obtained according to the following steps:

[0276] Step 1: The size of the first RGB is

[0277] Step 2: Due to Therefore, the size of the last RBG is 2;

[0278] Step 3: The size of the other RBGs is also 2.

[0279] In short, the first RBG contains 1 RB, and all other RBGs contain 2 RBs.

[0280] In fact, based on the above resource block group calculation and resource block set indication, the available frequency domain resources of the physical downlink shared channel of the R18 enhanced lightweight terminal are as follows: Figure 13 As shown:

[0281] The available PRBs are: PRB 75, PRB 80, PRB 81, PRB 84, PRB 85, ​​PRB 94, PRB 95, PRB 98, and PRB 99.

[0282] Therefore, when the activated bandwidth is greater than the maximum data scheduling bandwidth of 5MHz supported by the R18 enhanced lightweight terminal, the effective frequency domain resource location of the R18 enhanced lightweight terminal in the activated BWP can be determined by the scheme of "determining the available frequency domain resource location of the physical downlink shared channel according to the first strategy" in this application, thereby realizing the effectiveness and flexibility of frequency domain resource scheduling.

[0283] Furthermore, the solution proposed in this application can save DCI bits compared to existing protocols.

[0284] The following explanation uses the example of a physical downlink shared channel with frequency domain resource allocation type 1 and RB set defined as described in Method 5:

[0285] Assuming the active bandwidth is 106 RBs, the preset bandwidth is 5MHz, and the PDSCH subcarrier spacing is 15kHz, then based on the physical downlink shared channel subcarrier spacing of 15kHz, the number of RBs in an RB set is... Based on the size of the activated bandwidth portion and the preset bandwidth size, the total number of RB sets is: If only one RB set needs to be indicated at each time point, then the number of bits required for the RB set index indication is X = 3. Furthermore, the number of bits required for the first frequency domain resource... Therefore, if the resource block set and the first frequency domain resource allocation are located in the frequency domain resource allocation field of the DCI, the number of bits occupied by the frequency domain resource allocation field in the DCI is X+Y=3+9=12 bits; if the frequency domain resource allocation field in the DCI only contains the first frequency domain resource allocation, the number of bits occupied by the frequency domain resource allocation field in the DCI is Y=9 bits.

[0286] Due to the limited number of bits occupied by the frequency domain resource allocation field in the DCI of the existing protocol for frequency domain allocation Therefore, by adopting the RBset definition method in this application, the minimum number of DCI bits that can be saved is 13-12=1 bit, and the maximum number of bits that can be saved is 13-9=4 bits.

[0287] Therefore, when the active bandwidth is greater than the maximum data scheduling bandwidth of 5MHz supported by the R18 enhanced lightweight terminal, the scheme of "determining the available frequency domain resource location of the physical downlink shared channel according to the first strategy" in this application can reduce bit waste in DCI and achieve the effectiveness of frequency domain resource scheduling.

[0288] Compared to existing technologies, the solution in this application, when the base station knows the type of terminal equipment, but the active bandwidth is greater than the preset bandwidth because the bandwidth occupied by the control channel resources to be transmitted is greater than the maximum physical downlink shared channel bandwidth supported by the R18 enhanced lightweight terminal, can determine the effective frequency domain resource scheduling range of the R18 enhanced lightweight terminal by using the intersection of the resource block set and the frequency domain resource allocation field. This solution can determine the effective frequency domain resource position of the R18 enhanced lightweight terminal in the active BWP when the active bandwidth is greater than the maximum physical downlink shared channel bandwidth supported by the R18 enhanced lightweight terminal, achieving effectiveness and flexibility in frequency domain resource scheduling. It also saves bits occupied by the frequency domain resource allocation field in the DCI and solves the problem of excessively large resource block group allocation granularity caused by excessively large bandwidth, thereby ensuring effective and flexible scheduling of the frequency domain resources of the R18 enhanced lightweight terminal.

[0289] Optionally, as a third scenario, when the terminal is in the radio resource control connection state and / or the base station knows the terminal device type, the first strategy can be: the UE determines the available frequency domain resource location of the physical downlink shared channel of the R18 enhanced lightweight terminal according to a preset bit truncation method.

[0290] Optionally, the preset bit extraction method includes: extracting the lowest bit in the frequency domain resource allocation field that meets the preset bandwidth requirements, and determining at least one of the frequency domain start position, frequency domain duration, or effective resource block group position of the effective frequency domain resources of the lightweight capability device by extracting the lowest bit.

[0291] Optionally, the frequency domain resource allocation field is located in the downlink control information.

[0292] Optionally, the preset bandwidth is determined by the bandwidth of the maximum physical downlink shared channel that the R18 enhanced lightweight terminal can handle.

[0293] Optionally, in one embodiment, the specific implementation of the first strategy "the UE determines the available frequency domain resource location of the physical downlink shared channel of the R18 enhanced lightweight terminal according to a preset bit truncation method" is described below:

[0294] First, the number of bits required for the terminal's frequency domain resources is determined based on the preset bandwidth size and the frequency domain resource mapping type of the physical downlink shared channel;

[0295] Secondly, extract the lowest number of bits from the frequency domain resource allocation field that meet the frequency domain resource requirements of the terminal;

[0296] Finally, based on the intercepted bit information and the frequency domain resource mapping type of the physical downlink shared channel, at least one of the following is determined: the starting position of the terminal's frequency domain resources, the number of consecutive RBs, or the position of the effective resource block group.

[0297] In one implementation, the lowest bit of the frequency domain resource allocation field that meets the preset bandwidth requirement is extracted. Taking a preset bandwidth of 5MHz as an example, the specific implementation is as follows:

[0298] Assuming the active bandwidth is 52 RBs, the subcarrier spacing of the physical downlink shared channel is 15 kHz, and the number of RBs corresponding to the 5 MHz preset bandwidth is 25 RBs.

[0299] If frequency domain resource allocation type 1 is adopted, and the preset bandwidth is 5MHz, the number of bits required for frequency domain resource allocation of the R18 enhanced lightweight terminal is: That is, the lowest 9 bits need to be extracted for frequency domain resource allocation of the R18 enhanced lightweight terminal. That is, if the bits of the frequency domain resource allocation field in the DCI are "10110110001", then the R18 enhanced lightweight terminal will receive frequency domain resources that meet the preset bandwidth according to the lowest 9 bits "110110001".

[0300] Alternatively, the specific frequency domain location of the R18 enhanced lightweight terminal can be calculated using the following formula:

[0301]

[0302] In fact, before truncation, traditional devices calculate the frequency domain resource position in the active bandwidth part according to the 11-bit "10110110001".

[0303] Optionally, the starting position RB of the frequency domain resource mapping of the conventional device start =1, the duration of the frequency domain resource is L RBs =29; After truncating the lowest 9 bits "110110001", the starting position of the available frequency domain resources in the active bandwidth portion of the R18 enhanced lightweight terminal becomes: RB start =17, the duration of the frequency domain resource is: L RBs =9.

[0304] If frequency domain resource allocation type 0 is adopted, and the rbg-Size value of the higher-layer parameter pdsch-Config is config1, then according to the active bandwidth part size of 52RB and Table 2 below, the resource block group size P = 4 can be obtained.

[0305] Table 2: Nominal RBG size P

[0306]

[0307]

[0308] Alternatively, the resource block group size can be calculated as follows:

[0309] The first RBG is of size

[0310] The last RBG is [size]

[0311] The remaining RBG size is: P.

[0312] in, The offset of the active bandwidth portion from the system bandwidth is configured by higher-level parameters. To activate the bandwidth portion size.

[0313] set up According to the above formula, the first and last RBGs are 2 bits in size, while the remaining 12 RBGs are all 4 bits in size. Based on the bits "10010110110001" in the frequency domain resource allocation field of the DCI and the lowest 7 bits "0110001" truncated by the R18 enhanced lightweight terminal, the following can be obtained: Figure 14 and Figure 15 The available frequency domain resources for the conventional equipment and the R18 enhanced lightweight capability terminal are shown. Figure 14 For traditional devices, the available frequency domain resources before bit truncation are... Figure 15 The available frequency domain resources after bit truncation for the R18 enhanced lightweight terminal are shown in the figure. The specific available RB locations are marked with background color.

[0314] Compared to existing technologies, this solution does not change the size and meaning of the "frequency domain resource allocation" field in the existing DCI. It uses the method of truncating the low bits to obtain the 5MHz frequency domain resource location information of the R18 enhanced lightweight terminal, ensuring that the frequency domain resources of the physical downlink shared channel are limited to 5MHz bandwidth, thereby realizing the effective allocation of frequency domain resources and the flexible scheduling of frequency domain resources.

[0315] Optionally, as a fourth scenario, when the terminal is in a radio resource control connected state and / or the base station knows the terminal device type, the first strategy can be: the UE determines the location of available frequency domain resources of the physical downlink shared channel according to the scaling factor.

[0316] Optionally, the scaling factor is related to the active bandwidth size and the preset bandwidth.

[0317] Optionally, the preset bandwidth is determined by the bandwidth of the maximum physical downlink shared channel that the R18 enhanced lightweight terminal can handle.

[0318] Optionally, in one embodiment, the specific implementation of the first strategy "UE determines the location of available frequency domain resources of the physical downlink shared channel based on the scaling factor" is described below:

[0319] First, determine the scaling factor based on the active bandwidth and the preset bandwidth size;

[0320] Secondly, based on the RIV value corresponding to the frequency domain resource allocation field in the downlink control information, the starting RB index and the number of consecutive RBs of the frequency domain resource corresponding to the active bandwidth are obtained.

[0321] Then, based on the scaling factor, the starting RB index and the number of consecutive RBs of the frequency domain resource corresponding to the activation bandwidth are corrected to the starting RB index and the number of consecutive RBs of the frequency domain resource corresponding to the preset bandwidth size.

[0322] Finally, the available frequency domain resource locations of the physical downlink shared channel of the lightweight capability device are determined based on the starting RB index and the number of consecutive RBs corresponding to the preset bandwidth size.

[0323] In one implementation, the UE can use a proportional scaling method to determine the frequency domain resource location based on preset principles related to the active bandwidth, preset bandwidth, and RIV. The specific implementation method is as follows:

[0324] Step 1: Determine the starting position (RB) of the frequency domain resource corresponding to the active bandwidth portion based on the RIV value in the frequency domain resource allocation. start and frequency domain resource duration L RBs ;

[0325] Step 2: Determine the scaling factor K: If the active bandwidth is greater than the preset bandwidth, then K is a value in the set {1,2,4,8} that satisfies... Otherwise, K = 1.

[0326] Step 3: Determine the frequency domain resource location of the preset bandwidth portion: based on RB′ start =RB start / K,L′ RBs =L RBs / K determines the start position of the preset bandwidth frequency domain resource RB′ start and the number of consecutive RBs L′ RBs , where L' RBs No more than

[0327] Optionally, the calculation method for step 1 satisfies the following formula:

[0328]

[0329]

[0330] Optionally, the preset bandwidth size is the maximum physical downlink shared channel bandwidth supported by the R18 enhanced lightweight terminal;

[0331] Optionally, the preset bandwidth can be 5MHz.

[0332] For example:

[0333] Assuming activation bandwidth size The subcarrier spacing of the physical downlink shared channel is 15kHz, and the preset bandwidth of 5MHz corresponds to 25 RBs. Therefore, K = 4. Assuming the RIV value corresponding to the frequency domain resource allocation field in DCI is 4138, we know that RB... start =4, L RBs =40, according to RB′ start =RB start / K=4 / 4=1,L′ RBs =L RBs With / K=10, the frequency domain mapping resource location of the 5MHz physical downlink shared channel for the R18 enhanced lightweight terminal can be obtained as follows: Figure 16 As shown.

[0334] This understanding of RIV can also be combined with the understanding of physical downlink shared channel frequency domain resource mapping using RB set. If the index of the resource block set is represented by 3 bits '010', then the physical downlink shared channel frequency domain resource mapping position calculated in the above method is as follows: Figure 17 As shown (this scheme requires an indication of an additional X bits of resource block set).

[0335] This solution does not change the number of bits in the frequency domain resource allocation field of the existing DCI, and ensures flexible and effective scheduling of R18 enhanced lightweight terminals through effective frequency domain resource scaling.

[0336] Optionally, as a fifth scenario, when the terminal is in the radio resource control connected state and / or the base station knows the terminal equipment type, the UE can also combine the fourth and second scenarios to jointly determine the physical downlink shared channel frequency domain resource location of the R18 enhanced lightweight terminal, specifically including:

[0337] Step 1: Determine the location of the resource block set available to the R18 enhanced lightweight terminal in the active bandwidth based on the definition method and acquisition method of the resource block set in the second scenario;

[0338] Step 2: Determine the effective frequency domain location in the resource block set that can be used for physical downlink shared channel scheduling of R18 enhanced lightweight terminal based on the method of obtaining the scaling factor in the fourth scenario.

[0339] Alternatively, the activation bandwidth portion in the fourth scenario can be replaced by a resource block set for conversion.

[0340] Similarly, the methods described in the second, third, and fourth scenarios above can all be combined appropriately to determine the available frequency domain resource locations for R18 enhanced lightweight terminal.

[0341] As described in the above embodiments and in conjunction with the five scenarios, it can be seen that the embodiments of this application determine the available frequency domain resource location of the physical downlink shared channel of the R18 enhanced lightweight terminal according to the first strategy, which improves the effectiveness of frequency domain resource allocation and realizes flexible scheduling of frequency domain resources. In particular, when the active bandwidth is greater than the maximum data scheduling bandwidth of 5MHz, the granularity of the resource block group can be adjusted according to the actual scheduled data bandwidth to achieve scheduling flexibility and ensure the effective use of the frequency domain resource allocation field in the DCI, thereby reducing bit waste in the DCI.

[0342] Subsequently, the terminal can allocate frequency domain resources based on the determined available frequency domain resource locations.

[0343] This application embodiment also provides a resource processing apparatus, including:

[0344] The receiving module is used to receive downlink information and determine the location of available frequency domain resources of the physical downlink shared channel according to the first strategy.

[0345] Optionally, there can be multiple ways to obtain or determine the first strategy. For example, the first strategy can be a preset strategy, or it can be obtained directly from the downlink information transmission, or it can be determined or generated through the content of the downlink information.

[0346] Optionally, the downlink information includes at least one of the following:

[0347] Number of transmissions; frequency domain resource allocation field that satisfies the first preset rule.

[0348] Optionally, the number of transmissions includes at least one of the following:

[0349] The number of transmissions is configured by downlink control information; the number of transmissions is related to the configuration period of the control resource set; the maximum value of the number of transmissions is related to the number of frequency domain resource groups.

[0350] Optionally, the number of frequency domain resource groups is determined by the size of the active bandwidth portion and / or a preset bandwidth.

[0351] Optionally, satisfying the first preset rule includes:

[0352] The frequency domain resource allocation field includes a resource block set and / or a first frequency domain resource allocation.

[0353] Optionally, the resource processing apparatus further includes at least one of the following:

[0354] The size of the resource block set is related to the subcarrier spacing; the size of the resource block set is related to the preset bandwidth; the number of bits in the resource block set is related to the number of resource block sets in the active bandwidth; the number of bits in the resource block set is related to the representation method of the resource block sets in the active bandwidth.

[0355] Optionally, the number of bits allocated in the first frequency domain resource allocation is related to the frequency domain resource allocation type.

[0356] Optionally, the first strategy includes at least one of the following:

[0357] The location of available frequency domain resources for the physical downlink shared channel is determined according to a first preset formula related to the number of transmissions;

[0358] The available frequency domain resource locations of the physical downlink shared channel are determined by taking the intersection of the resource block set and the first frequency domain resource allocation in the frequency domain resource allocation field that satisfies the first preset rule.

[0359] The available frequency domain resources of the physical downlink shared channel are determined according to a preset bit truncation method;

[0360] The location of available frequency domain resources for the physical downlink shared channel is determined based on the scaling factor.

[0361] Optionally, the scaling factor is related to the active bandwidth size and the preset bandwidth.

[0362] Optionally, the frequency domain resource location occupied by the resource block set is determined by a second preset formula related to the frequency domain location of the activated bandwidth portion.

[0363] This application embodiment also provides a resource processing apparatus, including:

[0364] The transmitting module is used to transmit downlink information so that the terminal device can determine the location of available frequency domain resources of the physical downlink shared channel according to the first strategy.

[0365] Optionally, there can be multiple ways to obtain or determine the first strategy. For example, the first strategy can be a preset strategy, or it can be obtained directly from the downlink information transmission, or it can be determined or generated through the content of the downlink information.

[0366] Optionally, the transmitting module is also used to transmit downlink information based on the wireless resource connection status.

[0367] Optionally, the sending module is also used to obtain the status based on the terminal type and send downlink information.

[0368] Optionally, the downlink information includes at least one of the following: number of transmissions; frequency domain resource allocation field that satisfies a first preset rule.

[0369] Optionally, the downlink information includes at least one of the following: downlink control information; radio resource control information; system information.

[0370] Optionally, the resource processing apparatus further includes at least one of the following:

[0371] The number of transmissions is configured by downlink control information; the number of transmissions is related to the configuration period of the control resource set; the maximum value of the number of transmissions is related to the number of frequency domain resource groups.

[0372] Optionally, satisfying the first preset rule includes: the frequency domain resource allocation field includes a resource block set and / or a first frequency domain resource allocation.

[0373] Optionally, the first strategy includes at least one of the following:

[0374] The available frequency domain resource locations of the physical downlink shared channel are determined according to a first preset formula related to the number of transmissions; the available frequency domain resource locations of the physical downlink shared channel are determined by taking the intersection of the resource block set in the frequency domain resource allocation field and the first frequency domain resource allocation; the available frequency domain resource locations of the physical downlink shared channel are determined according to a preset bit truncation method; and the available frequency domain resource locations of the physical downlink shared channel are determined according to a scaling factor.

[0375] This application also provides a communication device, including: a memory, a processor, and a resource processing program stored in the memory and executable on the processor. When executed by the processor, the resource processing program implements the resource processing method as described in any of the above embodiments. The communication device mentioned in this application can be a terminal device (such as a smart terminal, specifically a mobile phone) or a network device (such as a base station); the specific meaning needs to be clarified in the context.

[0376] This application also provides a storage medium storing a computer program, which, when executed by a processor, implements the resource processing method as described in any of the above embodiments.

[0377] In the embodiments of the communication device and storage medium provided in this application, all the technical features of any of the above-described resource processing method embodiments may be included. The extended and explanatory content of the specification is basically the same as that of the embodiments of the above methods, and will not be repeated here.

[0378] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the methods described in the various possible implementations above.

[0379] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.

[0380] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0381] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0382] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0383] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0384] In this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions are generally described in detail only when they appear for the first time. When they appear again, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions that are not described in detail later can be referred to their previous relevant detailed descriptions.

[0385] In this application, the descriptions of the various embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0386] The technical features of the present application can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.

[0387] 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 necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the methods of each embodiment of this application.

[0388] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, storage disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0389] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A resource processing method, characterized in that, The method includes the following steps: S20, Receive downlink information and determine the location of available frequency domain resources of the physical downlink shared channel in the preset bandwidth according to the first strategy; The downlink information includes the number of transmissions in the radio resource control information. The number of transmissions is used to determine the location of available frequency domain resources in the physical downlink shared channel. The preset bandwidth is determined by the bandwidth of the maximum physical downlink shared channel that the R18 enhanced lightweight terminal can handle; When the subcarrier spacing of the physical downlink shared channel is 15kHz, the number of RBs corresponding to the 5MHz preset bandwidth is 25RBs; When the subcarrier spacing of the physical downlink shared channel is 30kHz, the number of RBs corresponding to the 5MHz preset bandwidth is 12RBs.

2. The method as described in claim 1, characterized in that, The downlink information also includes at least one of the following: Frequency domain resource allocation fields that satisfy the first preset rule; Downlink control information; Wireless resource control information; System information.

3. The method as described in claim 2, characterized in that, It also includes at least one of the following: The number of transmissions is configured by downlink control information; The number of transmissions is related to the configuration cycle of the control resource set; The maximum number of transmissions is related to the number of frequency domain resource packets; The condition of satisfying the first preset rule includes at least one of the following: The frequency domain resource allocation field only includes the first frequency domain resource allocation; The frequency domain resource allocation field includes a resource block set and a first frequency domain resource allocation.

4. The method as described in claim 3, characterized in that, It also includes at least one of the following: The number of frequency domain resource groups is determined by the size of the active bandwidth portion and the preset bandwidth; The size of the resource block set is related to the subcarrier spacing; The size of the resource block set is related to the preset bandwidth; The number of bits in the resource block set is related to the number of resource block sets in the active bandwidth; The number of bits in the resource block set is related to the way the resource block set is represented in the active bandwidth; The number of bits allocated in the first frequency domain resource allocation is related to the frequency domain resource allocation type; The frequency domain resource location occupied by the resource block set is determined by a second preset formula related to the frequency domain location of the activated bandwidth portion.

5. The method as described in claim 4, characterized in that, Determining the location of available frequency domain resources for the physical downlink shared channel according to the first strategy includes at least one of the following: The location of available frequency domain resources for the physical downlink shared channel is determined according to a first preset formula related to the number of transmissions; The location of available frequency domain resources for the physical downlink shared channel is determined by taking the intersection of the resource block set and the first frequency domain resource allocation. The available frequency domain resources of the physical downlink shared channel are determined according to a preset bit truncation method; The location of available frequency domain resources for the physical downlink shared channel is determined based on the scaling factor.

6. The method as described in claim 5, characterized in that, It also includes at least one of the following: The scaling factor is related to the active bandwidth size and the preset bandwidth; The representation of resource block sets in the activated bandwidth includes at least one of the following: The number of resource block sets in the active bandwidth that needs to be represented at each moment is greater than 1; The number of resource block sets in the active bandwidth that needs to be represented at each moment is 1.

7. A resource processing method, characterized in that, The method includes the following steps: S10, send downlink information so that the terminal device can determine the location of available frequency domain resources of the physical downlink shared channel in the preset bandwidth according to the first strategy; The downlink information includes the number of transmissions in the radio resource control information. The number of transmissions is used to determine the location of available frequency domain resources in the physical downlink shared channel. The preset bandwidth is determined by the bandwidth of the maximum physical downlink shared channel that the R18 enhanced lightweight terminal can handle; When the subcarrier spacing of the physical downlink shared channel is 15kHz, the number of RBs corresponding to the 5MHz preset bandwidth is 25RBs; When the subcarrier spacing of the physical downlink shared channel is 30kHz, the number of RBs corresponding to the 5MHz preset bandwidth is 12RBs.

8. The method as described in claim 7, characterized in that, Step S10 includes at least one of the following: Send downlink information based on the wireless resource connection status; The status is obtained based on the terminal type, and downlink information is sent.

9. The method as described in claim 8, characterized in that, The downlink information includes at least one of the following: Frequency domain resource allocation fields that satisfy the first preset rule; Downlink control information; Wireless resource control information; System information.

10. The method as described in claim 9, characterized in that, It also includes at least one of the following: The number of transmissions is configured by downlink control information; The number of transmissions is related to the configuration cycle of the control resource set; The maximum number of transmissions is related to the number of frequency domain resource packets; The condition of satisfying the first preset rule includes at least one of the following: The frequency domain resource allocation field only includes the first frequency domain resource allocation; The frequency domain resource allocation field includes a resource block set and a first frequency domain resource allocation.

11. The method as described in claim 10, characterized in that, It also includes at least one of the following: The number of frequency domain resource groups is determined by the size of the active bandwidth portion and the preset bandwidth; The size of the resource block set is related to the subcarrier spacing; The size of the resource block set is related to the preset bandwidth; The number of bits in the resource block set is related to the number of resource block sets in the active bandwidth; The number of bits in the resource block set is related to the way the resource block set is represented in the active bandwidth; The number of bits allocated in the first frequency domain resource allocation is related to the frequency domain resource allocation type; The frequency domain resource location occupied by the resource block set is determined by a second preset formula related to the frequency domain location of the activated bandwidth portion.

12. The method as described in claim 11, characterized in that, The terminal device determines the location of available frequency domain resources for the physical downlink shared channel according to the first strategy, including at least one of the following: The terminal device determines the location of available frequency domain resources of the physical downlink shared channel according to a first preset formula related to the number of transmissions; The terminal device determines the location of available frequency domain resources for the physical downlink shared channel by taking the intersection of the resource block set and the first frequency domain resource allocation; The terminal device determines the location of available frequency domain resources for the physical downlink shared channel according to a preset bit truncation method; The terminal device determines the location of available frequency domain resources for the physical downlink shared channel based on the scaling factor.

13. The method as described in claim 12, characterized in that, It also includes at least one of the following: The scaling factor is related to the active bandwidth size and the preset bandwidth; The representation of resource block sets in the activated bandwidth includes at least one of the following: The number of resource block sets in the active bandwidth that needs to be represented at each moment is greater than 1; The number of resource block sets in the active bandwidth that needs to be represented at each moment is 1.

14. A communication device, characterized in that, The communication device includes: a memory, a processor, and a resource processing program stored in the memory and executable on the processor, wherein the resource processing program, when executed by the processor, implements the steps of the resource processing method as described in any one of claims 1 to 13.

15. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the steps of the resource processing method as described in any one of claims 1 to 13.

Images