WO2024098417A1 - 资源处理方法、通信设备及存储介质 - Google Patents
资源处理方法、通信设备及存储介质 Download PDFInfo
- Publication number
- WO2024098417A1 WO2024098417A1 PCT/CN2022/131528 CN2022131528W WO2024098417A1 WO 2024098417 A1 WO2024098417 A1 WO 2024098417A1 CN 2022131528 W CN2022131528 W CN 2022131528W WO 2024098417 A1 WO2024098417 A1 WO 2024098417A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- frequency domain
- domain resource
- shared channel
- physical downlink
- resource allocation
- Prior art date
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 33
- 238000004891 communication Methods 0.000 title claims abstract description 28
- 238000013468 resource allocation Methods 0.000 claims abstract description 152
- 238000000034 method Methods 0.000 claims abstract description 80
- 230000005540 biological transmission Effects 0.000 claims description 94
- 230000004913 activation Effects 0.000 claims description 24
- 238000004590 computer program Methods 0.000 claims description 19
- 239000002699 waste material Substances 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 23
- 230000006870 function Effects 0.000 description 20
- 101150096310 SIB1 gene Proteins 0.000 description 15
- 238000013507 mapping Methods 0.000 description 13
- 230000008569 process Effects 0.000 description 13
- 230000000737 periodic effect Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 8
- 238000007726 management method Methods 0.000 description 5
- 230000004044 response Effects 0.000 description 5
- 101001121408 Homo sapiens L-amino-acid oxidase Proteins 0.000 description 4
- 102100026388 L-amino-acid oxidase Human genes 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000004364 calculation method Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000003213 activating effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 101000827703 Homo sapiens Polyphosphoinositide phosphatase Proteins 0.000 description 1
- 101150071746 Pbsn gene Proteins 0.000 description 1
- 102100023591 Polyphosphoinositide phosphatase Human genes 0.000 description 1
- 101100012902 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) FIG2 gene Proteins 0.000 description 1
- 101100233916 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) KAR5 gene Proteins 0.000 description 1
- 230000001133 acceleration Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000001186 cumulative effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 229920001690 polydopamine Polymers 0.000 description 1
- 238000010079 rubber tapping Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001629 suppression Effects 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
Definitions
- the present application relates to the field of communication technology, and in particular to a resource processing method, communication equipment and storage medium.
- the frequency domain resource allocation is defined based on the size of the activation bandwidth part.
- the maximum bandwidth of the physical downlink shared channel supported is 5MHz, which is much smaller than the size of the configured activation bandwidth part.
- frequency domain resource allocation type 1 For frequency domain resource allocation type 0, there is a problem that the resource block group granularity determined based on the activated bandwidth part is too large for the R18 enhanced light capability terminal, which in turn affects 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 activated bandwidth part, if the size of the activated bandwidth part is greater than 5MHz, there will be a problem of waste of the number of bits in the downlink control information, which will also affect the flexibility and effectiveness of frequency domain resource scheduling.
- the activated bandwidth portion is larger than 5MHz, there will also be a problem of being unable to determine the effective 5MHz bandwidth frequency domain resources in the activated bandwidth portion that need to be accurately received.
- the main purpose of this application is to provide a resource processing method, a communication device and a storage medium, aiming to improve the effectiveness of frequency domain resource allocation and realize flexible scheduling of frequency domain resources.
- the present application provides a resource processing method, which can be applied to a communication device (such as a mobile phone), comprising the steps of:
- the first strategy may be a preset strategy, or may be directly obtained by sending downlink information, or may be determined or generated through content in the downlink information.
- the downlink information includes at least one of the following:
- the number of transmissions 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 period of the control resource set; and the maximum value of the number of transmissions is related to the number of frequency domain resource groupings.
- the number of frequency domain resource groupings is determined by the size of the activated bandwidth portion and the preset bandwidth.
- 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.
- the method further comprises 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 of the resource block set is related to the number of resource block sets in the activated bandwidth; the number of bits of the resource block set is related to the representation of the resource block set in the activated bandwidth; the number of bits of 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 activated bandwidth part.
- the first strategy includes at least one of the following:
- the available frequency domain resource position of the physical downlink shared channel is determined according to the scaling factor.
- the scaling factor is related to the activation bandwidth size and/or the preset bandwidth.
- the present application also proposes a resource processing method, which can be applied to a communication device (such as a base station), comprising the steps of:
- the first strategy may be a preset strategy, or may be directly obtained by sending downlink information, or may be determined or generated through content in the downlink information.
- step S20 includes at least one of the following:
- the downlink information includes at least one of the following:
- the method further comprises 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 groupings.
- 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.
- the first strategy includes at least one of the following:
- the available frequency domain resource position of the physical downlink shared channel is determined according to the scaling factor.
- the present application also provides a resource processing device, comprising:
- 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.
- the present application also provides a resource processing device, comprising:
- the sending module is used to send downlink information so that the terminal determines the location of available frequency domain resources of the physical downlink shared channel according to the first strategy.
- the present application also provides a communication device, which includes: a memory, a processor, and a resource processing program stored in the memory and executable on the processor, wherein the resource processing program implements steps of any of the above-mentioned resource processing methods when executed by the processor.
- the present application also provides a storage medium, on which a computer program is stored.
- a computer program is stored.
- the steps of any of the above-mentioned resource processing methods are implemented.
- An embodiment of the present application further provides a computer program product, which includes a computer program code.
- the computer program code When the computer program code is executed on a computer, the computer executes any of the steps of the resource processing method described above.
- An embodiment of the present application also provides a chip, including a memory and a processor, the memory is used to store computer programs, and the processor is used to call and run the computer programs from the memory, so that a device equipped with the chip executes steps of any of the above-mentioned resource processing methods.
- the technical solution of the present application improves the effectiveness of frequency domain resource allocation and realizes flexible scheduling of frequency domain resources.
- the activated bandwidth portion is larger than the maximum data scheduling bandwidth of 5 MHz
- the granularity of the resource block group can be adjusted according to the actual scheduled data bandwidth to achieve scheduling flexibility and ensure effective utilization of the frequency domain resource allocation field in the downlink control information, thereby reducing bit waste in the downlink control information.
- FIG1 is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application.
- FIG2 is a diagram of a communication network system architecture provided in an embodiment of the present application.
- FIG3 is a schematic diagram of the hardware structure of the controller 140 involved in the resource processing method embodiment of the present application.
- FIG4 is a schematic diagram of the hardware structure of the network node 150 involved in the resource processing method embodiment of the present application.
- FIG5 is a schematic diagram of the interaction process between a terminal device and a network device in an embodiment of the resource processing method of the present application
- FIG6 is a schematic diagram of frequency domain resource index occupancy allocation involved in an embodiment of a resource processing method of the present application.
- FIG7 is a schematic diagram of frequency domain resources included in the first RB set involved in the resource processing method embodiment of the present application.
- FIG8 is a schematic diagram of frequency domain resources included in the second RB set involved in the resource processing method embodiment of the present application.
- FIG9 is a schematic diagram of frequency domain resources included in the third RB set involved in the resource processing method embodiment of the present application.
- FIG10 is a schematic diagram of frequency domain resources included in the fourth RB set involved in the resource processing method embodiment of the present application.
- FIG11 is a schematic diagram of frequency domain resources included in the fifth RB set involved in the embodiment of the resource processing method of the present application.
- FIG. 12 is a schematic diagram of frequency domain scheduling of a physical downlink shared channel of an R18 enhanced light capability terminal involved in an embodiment of a resource processing method of the present application;
- FIG. 13 is a schematic diagram of frequency domain scheduling of a physical downlink shared channel of another R18 enhanced light capability terminal involved in an embodiment of a resource processing method of the present application;
- FIG14 is a schematic diagram of a bandwidth reception diagram before bit truncation corresponding to a conventional device
- 15 is a schematic diagram of a bandwidth reception diagram after intercepting bits corresponding to an R18 enhanced light capability terminal in an embodiment of the present application;
- FIG16 is a schematic diagram of a frequency domain mapping resource position of a 5 MHz physical downlink shared channel involved in an embodiment of the resource processing method of the present application;
- FIG. 17 is another schematic diagram of the frequency domain mapping resource position of the 5 MHz physical downlink shared channel involved in the resource processing method embodiment of the present application.
- first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
- first information may also be referred to as the second information
- second information may also be referred to as the first information.
- word “if” as used herein can be interpreted as “at the time of -- or "when" or "in response to determination”.
- singular forms “one”, “one” and “the” are intended to also include plural forms, unless there is an opposite indication in the context.
- A, B, C means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C
- A, B or C or "A, B and/or C” means "any of the following: A; B; C; A and B; A and C; B and C; A and B and C”.
- An exception to this definition will only occur when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.
- the words “if” and “if” may be interpreted as “at the time of” or “when” or “in response to determining” or “in response to detecting”, depending on the context.
- the phrases “if it is determined” or “if (stated condition or event) is detected” may be interpreted as “when it is determined” or “in response to determining” or “when detecting (stated condition or event)” or “in response to detecting (stated condition or event)", depending on the context.
- step codes such as S10 and S20 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the sequence.
- S20 When implementing the step, those skilled in the art may execute S20 first and then S10, etc., but these should all be within the scope of protection of this application.
- module means, “component” or “unit” used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, “module”, “component” or “unit” can be used in a mixed manner.
- the communication equipment mentioned in this application can be a terminal device (such as a mobile terminal, specifically a mobile phone) or a network device (such as a base station).
- a terminal device such as a mobile terminal, specifically a mobile phone
- a network device such as a base station
- the terminal device can be implemented in various forms.
- the terminal device described in this application can include smart terminals such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminals such as digital TVs and desktop computers.
- smart terminals such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc.
- PDAs portable media players
- navigation devices wearable devices
- smart bracelets smart bracelets
- pedometers etc.
- fixed terminals such as digital TVs and desktop computers.
- FIG1 is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present 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.
- RF Radio Frequency
- the radio frequency unit 101 can be used for receiving and sending signals during information transmission or calls. Specifically, after receiving the downlink information of the base station, it is sent to the processor 110 for processing; in addition, the uplink data is sent to the base station.
- the radio frequency unit 101 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
- the radio frequency unit 101 can also communicate with the network and other devices through wireless communication.
- the above-mentioned 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.
- 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
- 5G etc.
- WiFi is a short-range wireless transmission technology.
- the mobile terminal can help users send and receive emails, browse web pages, and access streaming media through the WiFi module 102, which provides users with wireless broadband Internet access.
- FIG1 shows the WiFi module 102, it is understandable that it is not a necessary component of the mobile terminal and can be omitted as needed without changing the essence of the invention.
- the audio output unit 103 can convert the audio data received by the RF unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output it as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, etc. Moreover, the audio output unit 103 can also provide audio output related to a specific function performed by the mobile terminal 100 (for example, a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.
- the A/V input unit 104 is used to receive audio or video signals.
- the A/V input unit 104 may include a graphics processor (GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode.
- the processed image frame can be displayed on the display unit 106.
- the image frame processed by the graphics processor 1041 can be stored in the memory 109 (or other storage medium) or sent via the radio frequency unit 101 or the WiFi module 102.
- the microphone 1042 can receive sound (audio data) via the microphone 1042 in the operation modes such as the telephone call mode, the recording mode, the voice recognition mode, etc., and can process such sound into audio data.
- the processed audio (voice) data can be converted into a format output that can be sent to a mobile communication base station via the radio frequency unit 101 in the case of the telephone call mode.
- the microphone 1042 can implement various types of noise elimination (or suppression) algorithms to eliminate (or suppress) noise or interference generated in the process of receiving and sending audio signals.
- the mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors.
- the light sensor includes an ambient light sensor and a proximity sensor.
- the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light
- the proximity sensor can turn off the display panel 1061 and/or the backlight when the mobile terminal 100 is moved to the ear.
- the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary.
- sensors such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc.
- the display unit 106 is used to display information input by the user or information provided to the user.
- the display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
- LCD liquid crystal display
- OLED organic light-emitting diode
- the user input unit 107 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile terminal.
- the user input unit 107 may include a touch panel 1071 and other input devices 1072.
- the touch panel 1071 also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 1071 or near the touch panel 1071 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program.
- the touch panel 1071 may include two parts: a touch detection device and a touch controller.
- the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 110, and can receive and execute the command sent by the processor 110.
- the touch panel 1071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave.
- the user input unit 107 may further include other input devices 1072.
- the other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, a function key (such as a volume control key, a switch key, etc.), a trackball, a mouse, a joystick, etc., which are not specifically limited here.
- a function key such as a volume control key, a switch key, etc.
- a trackball such as a mouse, a joystick, etc.
- the touch panel 1071 may cover the display panel 1061.
- the touch panel 1071 detects a touch operation on or near it, it is transmitted to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event.
- the touch panel 1071 and the display panel 1061 are used as two independent components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to implement the input and output functions of the mobile terminal, which is not limited here.
- the interface unit 108 serves as an interface through which at least one external device can be connected to the mobile terminal 100.
- 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, etc.
- the interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.
- the memory 109 can be used to store software programs and various data.
- the memory 109 can mainly include a program storage area and a data storage area.
- the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.;
- the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc.
- the memory 109 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.
- the processor 110 is the control center of the mobile terminal. It uses various interfaces and lines to connect various parts of the entire mobile terminal. It executes various functions of the mobile terminal and processes data by running or executing software programs and/or modules stored in the memory 109, and calling data stored in the memory 109, so as to monitor the mobile terminal as a whole.
- the processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor.
- the application processor mainly processes the operating system, user interface, and application programs
- the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 110.
- the mobile terminal 100 may also include a power supply 111 (such as a battery) for supplying power to various components.
- a power supply 111 (such as a battery) for supplying power to various components.
- the power supply 111 may be logically connected to the processor 110 via a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system.
- the mobile terminal 100 may further include a Bluetooth module, etc., which will not be described in detail herein.
- the communication network system is an LTE system of universal mobile communication technology.
- the LTE system includes UE (User Equipment) 201, E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, EPC (Evolved Packet Core) 203 and the operator's IP service 204, which are connected in sequence.
- UE User Equipment
- E-UTRAN Evolved UMTS Terrestrial Radio Access Network
- EPC Evolved Packet Core
- UE201 may be the above-mentioned terminal 100, which will not be described in detail here.
- E-UTRAN 202 includes eNodeB 2021 and other eNodeBs 2022 , etc.
- eNodeB 2021 may be connected to other eNodeBs 2022 via a backhaul (eg, an X2 interface), and eNodeB 2021 is connected to EPC 203 , and eNodeB 2021 may provide UE 201 with access to EPC 203 .
- a backhaul eg, an X2 interface
- EPC203 may include MME (Mobility Management Entity) 2031, HSS (Home Subscriber Server) 2032, other MMEs 2033, SGW (Serving Gate Way) 2034, PGW (PDN Gate Way) 2035 and PCRF (Policy and Charging Rules Function) 2036.
- MME 2031 is a control node that processes signaling between UE 201 and EPC 203, providing bearer and connection management.
- HSS 2032 is used to provide some registers to manage functions such as home location register (not shown in the figure), and save some user-specific information such as service features and data rates. All user data can be sent through SGW2034.
- PGW2035 can provide IP address allocation and other functions for UE 201.
- PCRF2036 is the policy and charging control policy decision point for service data flow and IP bearer resources. It selects and provides available policy and charging control decisions for the policy and charging execution functional unit (not shown in the figure).
- IP service 204 may include the Internet, intranet, IMS (IP Multimedia Subsystem) or other IP services.
- IMS IP Multimedia Subsystem
- Fig. 3 is a schematic diagram of the hardware structure of a controller 140 provided in the present 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, and its implementation principle and beneficial effects are similar, which will not be repeated here.
- 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.
- Fig. 4 is a schematic diagram of the hardware structure of a network node 150 provided by the present application.
- 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, and its implementation principle and beneficial effects are similar, which will not be repeated here.
- 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.
- the above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium.
- the above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (English: processor) to perform some steps of the methods of various embodiments of the present application.
- RB Resource Block, resource block
- RBG Resource Block Groups, resource block group
- RB set Resource Block set, resource block set
- FDRA Frequency domain resource assignment, frequency domain resource allocation
- SIB1 system Information Block 1, system information block 1;
- USS UE-specific search space, UE specific search space;
- BWP Bandwidth Part.
- BWP is a new concept introduced by NR, which is designed to adapt to various types of terminals. Because NR is a high-bandwidth system, not all terminals can use this high bandwidth, so this small bandwidth system can be used.
- BWP is equivalent to dividing the 5G spectrum into many small blocks within a certain period of time. Each BWP can use different parameter sets, such as the bandwidth, subcarrier spacing and other control parameters of each BWP can be different;
- CORESET Control Resource set, control resource set;
- RRC Radio Reource Control, radio resource control
- MSB Most Significant Bit, the most significant bit
- LSB Least Significant Bit, least significant bit
- PDSCH Physical Downlink Shared Channel, physical downlink shared channel
- DCI Downlink Control Information, downlink control information
- RIV Resource Indication Value, resource indication value
- SI-RNTI System Information Radio-Network Temporary Identifier, system message radio network temporary identifier
- CRB Common Resource Block, common resource block
- PRB Physical Resource Block, physical resource block.
- the embodiment of the present application proposes a resource processing method, including the steps of:
- the network device sends downlink information
- 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.
- the resource processing method of the embodiment of the present application can be applied to a terminal device (such as a mobile phone) (hereinafter referred to as a terminal), and can also be applied to a network device (such as a base station).
- a terminal device such as a mobile phone
- a network device such as a base station
- the downlink information is sent by the network device, and after the terminal receives the downlink information sent by the network device, it 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.
- the available frequency domain resource position may be an available frequency domain resource position of a physical downlink shared channel of an R18 enhanced light capability terminal.
- the network device may send downlink information to the terminal side according to the wireless resource connection status and/or the terminal type acquisition status.
- the terminal type acquisition status refers to whether a base station corresponding to a current serving cell knows the terminal type.
- the terminal types may include a traditional terminal, an R17 light capability device terminal, and an R18 enhanced light capability terminal.
- the downlink information includes at least one of the following:
- Downlink control information Downlink control information; Radio resource control information; System information.
- the downlink information further includes at least one of the following: number of transmissions; and a frequency domain resource allocation field that satisfies a first preset rule.
- the embodiment of the present application 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 period of the control resource set; the maximum value of the number of transmissions is related to the number of frequency domain resource groupings.
- the number of frequency domain resource groupings is determined by the size of the activated bandwidth portion and the preset bandwidth.
- the preset bandwidth is determined by the bandwidth of a maximum physical downlink shared channel that can be processed by the R18 enhanced light capability terminal.
- satisfying the first preset rule includes: the frequency domain resource allocation field includes a resource block set and a first frequency domain resource allocation.
- the method also 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 of the resource block set is related to the number of resource block sets in the activated bandwidth; the number of bits of the resource block set is related to the representation method of the resource block set in the activated bandwidth.
- 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 activated bandwidth part.
- the number of bits of the first frequency domain resource allocation is related to the frequency domain resource allocation type.
- the first strategy may be a preset strategy, or may be directly obtained by sending downlink information, or may be determined or generated through content in the downlink information.
- the first strategy includes at least one of the following:
- the scaling factor is related to the activation bandwidth size and the preset bandwidth.
- the first strategy is related to the wireless resource connection state of the terminal and/or whether the base station knows the terminal type to which the terminal belongs.
- the radio resource connection state includes an RRC connected state, an RRC idle state and an RRC inactive state.
- the first strategy can be: determining the available frequency domain resource location of the physical downlink shared channel of the R18 enhanced lightweight capability terminal according to a first preset formula related to the number of transmissions.
- the number of transmissions refers to the number of repetitions of the current periodic physical downlink shared channel transmission within the period.
- the number of transmissions may be obtained from a transmission number field in the downlink control information
- the number of transmissions may also be obtained according to a control resource set configuration in the radio resource control information or the system information;
- the value of the number of transmissions can be determined by the number of times the control resource set appears in the period. If the period of the physical downlink shared channel is 160ms, if subframe 0 of radio frame 0 is used as the starting position of the period, the 160ms period of the physical downlink shared channel refers to all subframes from radio frame 0 to radio frame 16. The number of times the control resource set associated with the periodic physical downlink shared channel appears in the 160ms period can be obtained according to the control resource set configuration in the radio resource control information or the system information, and then the number of times the physical downlink shared channel appears in the 160ms period can be obtained.
- the number of transmissions may also depend on UE implementation.
- the UE takes the physical downlink shared channel received at the start position of each period point as the first transmission, and the cumulative count is the physical downlink shared channel transmission number of the current reception.
- the first preset formula is determined by the number of transmissions, a frequency domain resource allocation field satisfying a first preset rule, and/or a preset bandwidth.
- the frequency domain resource allocation field satisfying the first preset rule may be located in the downlink control information.
- the frequency domain position of the periodic transmission service in the BWP is obtained according to the RIV value corresponding to the frequency domain resource allocation field that meets the first preset rule in the downlink information, such as the starting position of the frequency domain resource, the number of continuous RBs of the frequency domain resource, or the frequency domain mapping position of the resource block group.
- the number D of continuous RBs corresponding to the preset bandwidth is obtained according to the downlink information or pre-configuration information.
- the D consecutive RB indexes that can be processed by the terminal during the G-th transmission are calculated.
- the number of transmission times and the percentage of the frequency domain resource allocation field are processed as follows:
- the frequency domain resource allocation field is located in the downlink control information and has a bit number of in, It is the number of RBs occupied by CORESET#0 or the number of RBs occupied by the initial downlink bandwidth.
- the percentage thereof is related to the maximum number of transmissions required for the periodic service to meet the coverage requirement within one period.
- the SIB1 transmission period is 160ms
- the maximum number of transmissions required to complete the complete or accurate reception of SIB1 is 5, then the number of bits occupied by the transmission times field in the downlink control information is 3, of which "000" is the first transmission of SIB1 within the 160ms period, "001" is the second transmission within the 160ms period, and so on;
- the maximum number of transmissions required to complete the complete or accurate reception of SIB1 is 4, then the number of bits occupied by the transmission times field in the downlink control information is 2, of which "00" is the first transmission of SIB1 within the 160ms period, "01” is the second transmission within the 160ms period, and so on.
- the maximum number of transmissions required for the periodic service to complete the coverage requirement within one period is determined by ceil (activated bandwidth portion size/pre-bandwidth size).
- the number of transmissions is obtained according to the control resource set configuration in the radio resource control information or the system information, the number of transmissions does not occupy any downlink signaling.
- the 160 ms period of the physical downlink shared channel refers to all subframes from radio frame 0 to radio frame 16.
- the control resource set configuration in the radio resource control information or the system information the number of times the control resource set associated with the periodic physical downlink shared channel appears in the 160 ms period can be obtained, and then the number of times the physical downlink shared channel appears in the 160 ms period can be obtained.
- the UE takes the physical downlink shared channel received at the start of each period point as the first transmission, and accumulates the number of physical downlink shared channel transmissions for the current reception.
- 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.
- the number of transmissions and the number of frequency domain resource groups of the physical downlink shared channel are non-interleavedly mapped, which means that the first physical downlink shared channel reception can receive the first group of frequency domain resource positions, the second physical downlink shared channel reception can receive the second group of frequency domain resource positions, and so on.
- the specific implementation of the UE determining the frequency domain resource position of the physical downlink shared channel according to the first preset formula related to the number of transmissions is as follows:
- Step 1 Get the current transmission number G of the periodic service SIB1, that is, get that this time slot is the Gth transmission of SIB1;
- Step 2 Obtain the RB start and L RBs of SIB1 in the activated bandwidth part according to the RIV value corresponding to the frequency domain resource allocation field in the SI-RNTI scrambled DCI, where RB start is the frequency domain starting position of SIB1 in the activated bandwidth part and L RBs is the frequency domain continuous resource block length of SIB1 in the activated bandwidth part;
- Step 3 Calculate the frequency domain starting RB index of the R18 enhanced light capability terminal according to a first preset formula related to the number of transmissions.
- the first preset formula related to the number of transmissions can be expressed as follows:
- RB′ start (RB start + (T-1)*D) mod (L RBs + RB start );
- D is the number of consecutive RBs corresponding to the preset bandwidth
- T is the number of frequency domain resource groups of the physical downlink shared channel, and if the number of transmissions and the number of frequency domain resource groups of the physical downlink shared channel adopt non-interleaved mapping, then T is equal to the number of transmissions G;
- the preset bandwidth is determined by the bandwidth of a maximum physical downlink shared channel that can be processed by the R18 enhanced light capability terminal.
- the D consecutive RB indexes of the R18 enhanced light capability terminal are obtained as follows:
- D is related to the subcarrier spacing.
- the preset bandwidth as 5 MHz as an example
- the number of continuous RBs D that can be processed by the R18 enhanced light capability terminal each time is shown in the following Table 1:
- Subcarrier spacing is 15KHz
- Subcarrier spacing is 30KHz 25RB 11RB/12RB(PRACH)
- the CORESET#0 bandwidth is 48RB
- the PDSCH frequency domain resource allocation type is 1
- the RIV value corresponding to the frequency domain resource allocation field in the DCI is 861. According to the RIV value and the following formula:
- RB′ start (RB start + (G-1)*D) mod (L RBs + RB start )
- the 25 consecutive RB indexes of the R18 enhanced light capability terminal are: 2, 3, 4, ..., 26, as shown in FIG6 .
- RB′ start (RB start + (G-1)*D) mod (L RBs + RB start )
- the 25 consecutive RB indexes of the R18 enhanced light capability terminal are: 27, 28, ..., 33, 0, 1, ..., 17.
- RB index 0 corresponds to the first RB index in the activated BWP.
- the number of transmissions and the number of frequency domain resource receiving groups of the physical downlink shared channel are interleaved and mapped.
- the number of transmissions and the number of frequency domain resource receiving groups of the physical downlink shared channel are interleavedly mapped, which means that the first physical downlink shared channel reception may be the reception of the Mth group of frequency domain resource positions, and the second physical downlink shared channel reception may be the reception of the Nth group of frequency domain resource positions, where M and N are not necessarily consecutively grouped frequency domain resource positions, and both M and N correspond to the parameter T in the first preset formula in the above step 3.
- the terminal when the terminal initially accesses 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 the number of transmissions of the physical downlink shared channel currently transmitted based on the number of transmissions, and then the terminal can also complete the complete reception of the periodic transmission service based on the frequency domain reception scheme related to the number of transmissions without modifying the number of bits and mapping rules of the existing frequency domain resource allocation field.
- This scheme can ensure the effective compatibility of lightweight capability devices and traditional devices, and can also ensure that lightweight capability devices can achieve complete reception of periodic services in limited bandwidth scenarios, and can also ensure the scheduling flexibility of lightweight capability devices.
- the first strategy may be: the UE determines the available frequency domain resource position of the physical downlink shared channel of the R18 enhanced lightweight capability terminal based on 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.
- satisfying the first preset rule includes at least one of the following:
- the frequency domain resource allocation field includes a resource block set and a first frequency domain resource allocation
- the frequency domain resource allocation field includes only the first frequency domain resource allocation.
- the frequency domain resource allocation field satisfying the first preset rule may be located in the DCI
- the resource block set takes the X most significant bit (MSB) bits in the frequency domain resource allocation field;
- the first frequency domain resource allocation takes the Y least significant bit (LSB) bits in the frequency domain resource allocation field;
- 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
- the number of bits X occupied by the resource block set is related to at least one of the activation bandwidth size, the bandwidth size of the maximum physical downlink shared channel supported by the UE, or the subcarrier spacing;
- the resource block set may also be configured by radio resource control information or system information;
- the maximum number of resource blocks included in the resource block set is related to the subcarrier spacing.
- UE determines the available frequency domain resource position of the physical downlink shared channel of the R18 enhanced light capability terminal according to 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:
- the frequency domain resource position occupied by the physical downlink shared channel in the above-determined resource block set is determined according to 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.
- 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 activated bandwidth part.
- the UE determines the resource block set where the frequency domain resources of the physical downlink shared channel are located according to 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 according to the frequency domain resource allocation type and Y least significant bits of the physical downlink shared channel.
- the number of bits in the frequency domain resource allocation field in the DCI is: X+Y bits, wherein the X most significant bits provide the location of the resource block set, and the Y least significant bits provide the specific available RB index within the specified resource block set.
- the number of bits corresponding to X is related to the number of resource block sets in the activated bandwidth and the representation method of the resource block sets in the activated bandwidth. For example, assuming that the number of resource block sets in the activated bandwidth is 6, if the number of resource block sets in the activated bandwidth that needs to be represented at each moment is greater than 1, then X takes a value of 6; if the number of resource block sets in the activated bandwidth that needs to be represented at each moment is 1, then X takes a value of 3.
- 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, 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, the value of Y is If the frequency domain resource allocation type of the physical downlink shared channel is 'dynamicSwitch', the value of Y is And its most significant bit is used to determine whether it is resource allocation type 0 or resource allocation type 1.
- P is the RBG granularity determined by the newly added radio resource control parameter resourceAllocationType1GranularityDCI-1-0-r17, The starting position of the frequency domain resources for a given resource block set
- the radio resource control parameter resourceAllocationType1GranularityDCI-1-0-r17 is:
- resourceAllocationType1GranularityDCI-1-0-r17 ⁇ n2,n4 ⁇ .
- the frequency domain resource allocation type of the physical downlink shared channel is configured as 'dynamicSwitch'
- '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.
- the value of P is less than or equal to the resource block group size corresponding to the activated bandwidth.
- the problem of excessive granularity of resource block group allocation due to excessive activation bandwidth can be solved, which causes the waste of frequency domain resources and the problem of frequency domain scheduling flexibility.
- the "frequency domain resource allocation" field in the DCI only includes the first frequency domain resource allocation, and the frequency domain position of the resource block set is determined by a wireless resource control message, a system message or a pre-configuration, then the number of bits occupied by the "frequency domain resource allocation” field in the DCI is Y, and the specific value of Y is the same as the definition in the implementation in which the "frequency domain resource allocation" field in the DCI includes both the resource block set and the first frequency domain resource allocation.
- the number of RBs corresponding to different subcarrier spacing scenarios is determined according to the preset bandwidth.
- the number of RBs in a resource block set is or
- 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 activated bandwidth part, wherein the second preset formula is a calculation formula for the start and end CRB indexes of each resource block set.
- Method 1 The second preset formula corresponding to the CRB index at the beginning and end of each RB set is as follows:
- s is the index of RB set
- the number of RBs contained in each RB set is calculated using the following formula:
- the number of RBs contained in the RB set is The number of RBs included in the activated bandwidth is
- the activation bandwidth includes RB sets, and the frequency domain resources included in each RB set are shown in FIG7 .
- the second preset formula corresponding to the CRB index of each RB set start and end is as follows:
- s is the index of RB set
- the number of RBs contained in each RB set is calculated using the following formula:
- the number of RBs contained in the RB set is The number of RBs included in the activated bandwidth is For example, the activation bandwidth is RB sets, and the frequency domain resources included in each RB set are shown in FIG8 .
- the second preset formula corresponding to the CRB index of each RB set start and end is as follows:
- s is the index of RB set
- the number of RBs contained in each RB set is calculated using the following formula:
- the number of RBs contained in the RB set is The number of RBs included in the activated bandwidth is
- the activation bandwidth is RB sets, and the frequency domain resources contained in each RB set are shown in Figure 9:
- the second preset formula corresponding to the CRB index of each RB set start and end is as follows:
- x is a certain RB set in the middle and the number of RBs it contains is:
- s is the index of RB set, The number of RBs contained in each RB set is calculated using the following formula:
- the number of RBs contained in the RB set is The number of RBs included in the activated bandwidth is
- the activation bandwidth is RB sets, and the frequency domain resources contained in each RB set are shown in Figure 10:
- the second preset formula corresponding to the CRB index at the beginning and end of each RB set must satisfy the following design:
- Step 1 Set the guard band in RB set
- the number of RBs contained in the guard band is RBs
- Step 2 Determine the position of the guard band in the activation bandwidth portion, such as the guard band is located at the highest frequency edge of the activation bandwidth portion, the guard band is located at the lowest frequency edge of the activation bandwidth portion, or any position in the middle of the activation bandwidth portion.
- Step 3 After deducting the RB where the guard band is located in the activated bandwidth part, divide it equally and divide it from low to high in the frequency domain. If the guard band is located at the highest frequency edge of the activated bandwidth part, the CRB index corresponding to RB 0 in the activated bandwidth part is the starting CRB index of the first RB set, and the RBs in the activated bandwidth part are The corresponding CRB index is the end CRB index of the first RB set, activating the RB in the bandwidth part The corresponding CRB index is the starting CRB index of the Xth RB set, activating the RB in the bandwidth part The corresponding CRB index is the end CRB index of the Xth RB set, and so on.
- the frequency domain resources included in each RB set are shown in FIG11.
- the scenario where the guard band is located at the lowest frequency edge of the activated bandwidth part or at any position in the middle of the activated bandwidth part is similar to the scenario where the guard band is located at the highest frequency edge of the activated bandwidth part. Both are to select continuous RBs after deducting the RB where the guard band is located and dividing them equally. RBs are regarded as an RB set.
- the number of RBs contained in the RB set is The number of RBs included in the activated bandwidth is For example, the activation bandwidth is RB sets.
- the terminal receives the frequency domain resource allocation field in the downlink control information, it first determines the resource block set index where the physical downlink shared channel of the R18 enhanced light capability terminal is located according to any one of the above five methods, and then determines the specific resource block index of the physical downlink shared channel of the R18 enhanced light capability 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 position of the physical downlink shared channel of the R18 enhanced light capability terminal in the BWP can be determined.
- the frequency domain resource allocation field includes both the resource block set and the first frequency domain resource allocation and the frequency domain resource allocation field is "010100101001", wherein 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.
- the physical downlink shared channel frequency domain resource allocation type is 0 and the definition of RB set is as described in method 5 as an example for explanation:
- the size of the activated bandwidth is 106 RB
- the preset bandwidth is 5 MHz
- the subcarrier spacing of the physical downlink shared channel is 15 kHz.
- the number of RBs in an RB set can be known.
- a new wireless resource control parameter resourceAllocationType1GranularityDCI-1-0-r17 is added to determine that the value of P is 2, and take the frequency domain resource allocation type of the physical downlink shared channel as 1 and the definition of RB set as method 5 as an example, assume that the frequency domain resource allocation field includes both 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 bits are '010', and the lowest 13 bits of the first frequency domain resource allocation bits are '1001010000101', then according to the resource block set index bits, the resource block set index of the physical downlink shared channel is 3, and according to the first frequency domain resource allocation bits, the index of the available resource block group in the specified resource set can be obtained.
- each resource block group (RBG) is obtained according to the following steps:
- Step 1 The first RBG size is
- Step 2 Since So the last RBG size is 2;
- Step 3 The size of other RBGs is also 2.
- the first RBG includes 1 RB
- the other RBGs include 2 RBs.
- the available PRBs are: PRB 75, PRB 80, PRB 81, PRB 84, PRB 85, PRB 94, PRB 95, PRB 98, and PRB 99.
- the scheme of "determining the available frequency domain resource position of the physical downlink shared channel according to the first strategy" in this application can be used to determine the effective frequency domain resource position of the R18 enhanced light capability terminal in the activated BWP, thereby achieving the effectiveness and flexibility of frequency domain resource scheduling.
- the embodiment of the present application can save DCI bits compared to the existing protocol.
- the size of the activated bandwidth is 106 RB
- the preset bandwidth is 5 MHz
- the subcarrier spacing of PDSCH is 15 kHz.
- the solution of "determining the available frequency domain resource position of the physical downlink shared channel according to the first strategy" in this application can reduce the bit waste in the DCI to achieve the effectiveness of frequency domain resource scheduling.
- the scheme of the present application can use the intersection of the resource block set and the frequency domain resource allocation field to determine the effective frequency domain resource scheduling range of the R18 enhanced light capability terminal in the scenario where the base station knows the type of terminal equipment, but 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 light capability terminal, resulting in the activation bandwidth portion being greater than the preset bandwidth.
- This scheme can determine the effective frequency domain resource position of the R18 enhanced light capability terminal in the activated BWP when the activation bandwidth portion is greater than the maximum physical downlink shared channel bandwidth supported by the R18 enhanced light capability terminal, thereby achieving the effectiveness and flexibility of frequency domain resource scheduling, while saving the number of occupied bits of the frequency domain resource allocation field in the DCI, and solving the problem of excessive granularity of resource block group allocation caused by excessive bandwidth, thereby ensuring effective and flexible scheduling of frequency domain resources of the R18 enhanced light capability terminal.
- 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 capability terminal according to a preset bit interception method.
- the preset method of intercepting bits includes: intercepting 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 starting position, frequency domain continuous length or effective resource block group position of the effective frequency domain resources of the lightweight capability device by intercepting the obtained lowest bit.
- the frequency domain resource allocation field is located in downlink control information.
- the preset bandwidth is determined by the bandwidth of a maximum physical downlink shared channel that can be processed by the R18 enhanced light capability terminal.
- UE determines the available frequency domain resource position of the physical downlink shared channel of the R18 enhanced light capability terminal according to a preset interception bit method
- the number of bits required for the frequency domain resources of the terminal is determined according to the preset bandwidth size and the frequency domain resource mapping type of the physical downlink shared channel;
- At least one of the starting position of the frequency domain resources of the terminal, the number of continuous RBs or the position of the valid resource block group is determined according to the intercepted bit information and the frequency domain resource mapping type of the physical downlink shared channel.
- the lowest bit of the frequency domain resource allocation field that meets the preset bandwidth requirement is intercepted, and the preset bandwidth is 5 MHz as an example, and the specific implementation is as follows:
- the size of the activated bandwidth portion is 52 RB
- the subcarrier spacing of the physical downlink shared channel is 15 KHz
- the number of RBs corresponding to the 5 MHz preset bandwidth is 25 RBs.
- frequency domain resource allocation type 1 is used, according to the preset bandwidth size of 5MHz, it can be known that the number of bits required for frequency domain resource allocation of R18 enhanced light capability terminals is That is, the lowest 9 bits need to be intercepted for frequency domain resource allocation of the R18 enhanced light capability terminal. That is, if the bits of the frequency domain resource allocation field in the DCI are "10110110001", the R18 enhanced light capability terminal will receive the frequency domain resources that meet the preset bandwidth of the R18 enhanced light capability terminal according to the lowest 9 bits "110110001".
- the specific frequency domain position of the R18 enhanced light capability terminal may be calculated according to the following formula:
- the conventional device calculates its frequency domain resource position in the activated bandwidth portion according to the 11 bits "10110110001".
- the resource block group size is calculated as follows:
- the first RBG size is a first RBG size
- the last RBG size is if and P otherwise,
- the remaining RBG sizes are: P.
- the offset value of the activated bandwidth part on the system bandwidth is configured by high-level parameters.
- the size of the activated bandwidth portion is configured by high-level parameters.
- the size of the first and last RBG is 2, and the size of the remaining 12 RBGs is 4; according to the bits "10010110110001" of the frequency domain resource allocation field in the DCI and the lowest 7 bits "0110001" intercepted by the R18 enhanced light capability terminal, the available frequency domain resources of the traditional device and the R18 enhanced light capability terminal as shown in Figures 14 and 15 can be obtained respectively.
- Figure 14 shows the available frequency domain resources before the interception of the bits corresponding to the traditional device
- Figure 15 shows the available frequency domain resources after the interception of the bits corresponding to the R18 enhanced light capability terminal.
- the background color in the figure indicates the specific available RB positions.
- this solution does not change the size and meaning of the "frequency domain resource allocation" field in the existing DCI. It adopts the method of intercepting the low bits to obtain the 5MHz frequency domain resource location information of the R18 enhanced lightweight capability terminal, ensuring that the frequency domain resources of the physical downlink shared channel are limited to the 5MHz bandwidth, realizing the effective allocation of frequency domain resources and the flexible scheduling of frequency domain resources.
- the first strategy when the terminal is in a radio resource control connection state and/or the base station knows the terminal device type, the first strategy may be: the UE determines the available frequency domain resource position of the physical downlink shared channel according to the scaling factor.
- the scaling factor is related to the activation bandwidth size and the preset bandwidth.
- the preset bandwidth is determined by the bandwidth of a maximum physical downlink shared channel that can be processed by the R18 enhanced light capability terminal.
- UE determines the available frequency domain resource position of the physical downlink shared channel according to the scaling factor is described as follows:
- a scaling factor is determined according to the activation bandwidth and the preset bandwidth size
- the frequency domain resource starting RB index and the number of consecutive RBs corresponding to the activated bandwidth are obtained according to the RIV value corresponding to the frequency domain resource allocation field in the downlink control information;
- the frequency domain resource starting RB index and the number of consecutive RBs corresponding to the activated bandwidth are corrected according to the scaling factor to be the frequency domain resource starting RB index and the number of consecutive RBs corresponding to the preset bandwidth size;
- the available frequency domain resource position of the physical downlink shared channel of the light capability device is determined according to the frequency domain resource starting RB index and the number of consecutive RBs corresponding to the preset bandwidth size.
- the UE may adopt a proportional scaling method to determine the frequency domain resource location according to a preset principle related to the activation bandwidth, the preset bandwidth, and the RIV.
- the specific implementation method is as follows:
- Step 1 Determine the frequency domain resource start position RB start and the frequency domain resource duration L RBs corresponding to the activated bandwidth part according to the RIV value in the frequency domain resource allocation;
- step 1 satisfies the following formula:
- the preset bandwidth size is the maximum physical downlink shared channel bandwidth size supported by the R18 enhanced light capability terminal;
- the preset bandwidth may be 5 MHz.
- RIV can also be combined with RB set to understand the frequency domain resource mapping of the physical downlink shared channel. If the index of the resource block set is represented by 3 bits ‘010’, the above method calculates the location of the frequency domain resource mapping of the physical downlink shared channel as shown in Figure 17 (this solution requires the addition of X bits of resource block set indication).
- This solution does not change the number of bits of the frequency domain resource allocation field in the existing DCI, and ensures flexible and effective scheduling of R18 enhanced lightweight capability terminals through effective frequency domain resource scaling.
- the UE may also determine the physical downlink shared channel frequency domain resource location of the R18 enhanced light capability terminal in combination with the fourth scenario and the second scenario, specifically including:
- Step 1 Determine the position of the resource block set available to the R18 enhanced light capability terminal in the activated bandwidth according to the definition method of the resource block set and the acquisition method of the resource block set position in the second scenario;
- Step 2 Determine the effective frequency domain position in the resource block set that can be used for physical downlink shared channel scheduling of the R18 enhanced light capability terminal according to the method of obtaining the scaling factor in the fourth scenario.
- the activated bandwidth portion in the fourth scenario may be converted using a resource block set instead.
- the methods described in the second scenario, the third scenario, and the fourth scenario can all be reasonably combined to determine the location of available frequency domain resources for the R18 enhanced lightweight capability terminal.
- the embodiment of the present application determines the available frequency domain resource position of the physical downlink shared channel of the R18 enhanced lightweight capability terminal according to the first strategy, thereby improving the effectiveness of frequency domain resource allocation and realizing flexible scheduling of frequency domain resources.
- the activated bandwidth portion is larger 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, as well as to ensure the effective use of the frequency domain resource allocation field in the DCI and reduce bit waste in the DCI.
- the terminal may perform frequency domain resource allocation according to the determined available frequency domain resource positions.
- the present application also provides a resource processing device, including:
- 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.
- the first strategy may be a preset strategy, or may be directly obtained by sending downlink information, or may be determined or generated through content in the downlink information.
- the downlink information includes at least one of the following:
- the number of transmissions 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 period of the control resource set; and the maximum value of the number of transmissions is related to the number of frequency domain resource groupings.
- the number of frequency domain resource groupings is determined by the size of the activated bandwidth portion and/or a preset bandwidth.
- 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.
- the resource processing device 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 of the resource block set is related to the number of resource block sets in the activated bandwidth; the number of bits of the resource block set is related to the representation method of the resource block set in the activated bandwidth.
- the number of bits of the first frequency domain resource allocation is related to the frequency domain resource allocation type.
- the first strategy includes at least one of the following:
- the available frequency domain resource position of the physical downlink shared channel is determined according to the scaling factor.
- the scaling factor is related to the activation bandwidth size and the preset bandwidth.
- 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 activated bandwidth part.
- the present application also provides a resource processing device, including:
- the sending module is used to send downlink information so that the terminal determines the location of available frequency domain resources of the physical downlink shared channel according to the first strategy.
- the first strategy may be a preset strategy, or may be directly obtained by sending downlink information, or may be determined or generated through content in the downlink information.
- the sending module is further used to send downlink information according to the wireless resource connection status.
- the sending module is further configured to send downlink information according to the terminal type acquisition status.
- the downlink information includes at least one of the following: number of transmissions; a frequency domain resource allocation field that satisfies a first preset rule.
- the downlink information includes at least one of the following: downlink control information; wireless resource control information; system information.
- the resource processing device further 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 period of the control resource set; and the maximum value of the number of transmissions is related to the number of frequency domain resource groupings.
- 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.
- the first strategy includes at least one of the following:
- the embodiment of the present 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, wherein the resource processing program implements the resource processing method described in any of the above embodiments when executed by the processor.
- the communication device mentioned in the present application may be a terminal device (such as a smart terminal, specifically a mobile phone) or a network device (such as a base station), and the specific reference needs to be clarified in the context.
- An embodiment of the present application further provides a storage medium, on which a computer program is stored.
- the computer program is executed by a processor, the resource processing method as described in any of the above embodiments is implemented.
- An embodiment of the present application further provides a computer program product, which includes a computer program code.
- the computer program code runs on a computer, the computer executes the methods in the above various possible implementation modes.
- An embodiment of the present application also provides a chip, including a memory and a processor, wherein 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 equipped with the chip executes the methods in various possible implementation modes as described above.
- the units in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.
- the technical solution of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) as above, and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, a controlled terminal, or a network device, etc.) to execute the method of each embodiment of the present application.
- a storage medium such as ROM/RAM, magnetic disk, optical disk
- a terminal device which can be a mobile phone, a computer, a server, a controlled terminal, or a network device, etc.
- a computer program product includes one or more computer instructions.
- a computer program instruction When a computer program instruction is loaded and executed on a computer, a process or function according to an embodiment of the present application is generated in whole or in part.
- the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
- Computer instructions may be stored in a storage medium or transmitted from one storage medium to another storage medium.
- computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means.
- the storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. Available media may be magnetic media (e.g., floppy disk, storage disk, tape), optical media (e.g., DVD), or semiconductor media (e.g., solid-state storage disk Solid State Disk (SSD)), etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请公开了一种资源处理方法、通信设备和存储介质,该方法包括:接收下行信息,根据第一策略确定物理下行链路共享信道的可用频域资源位置。本申请技术方案提高了频域资源分配的有效性,实现了频域资源的灵活调度,尤其是在激活带宽部分大于最大数据调度带宽5MHz时,可以根据实际调度的数据带宽调整资源块组的粒度,以实现调度灵活性,以及保证DCI中的频域资源分配字段的有效利用,减少DCI中的比特浪费。
Description
本申请涉及通信技术领域,尤其涉及一种资源处理方法、通信设备及存储介质。
现有上、下行频域资源分配方案中,频域资源分配是基于激活带宽部分大小定义的,而对于R18增强轻型能力终端,其支持的物理下行链路共享信道最大带宽是5MHz,远远小于配置的激活带宽部分大小。如果继续沿用现有基于激活带宽的频域资源分配方案会出现如下频域资源分配问题:
对于频域资源分配类型0,存在基于激活带宽部分确定的资源块组粒度对于R18增强轻型能力终端过大的问题,进而影响频域资源调度的灵活性和有效性;和/或,对于频域资源分配类型1,由于下行链路控制信息中的频域资源分配字段所占的比特数目是按照激活带宽部分大小计算的,如果激活带宽部分大小大于5MHz,则会出现下行链路控制信息中比特数目浪费的问题,进而也会影响频域资源调度的灵活性和有效性。
除了资源块组粒度过大,下行链路控制信息比特浪费的问题,如果激活带宽部分大于5MHz,还会出现无法确定需要准确接收的激活带宽部分中有效5MHz带宽频域资源的问题。
所以如何实现激活带宽部分大于R18增强轻型能力终端支持的最大5MHz带宽场景下的有效频域资源调度的问题是亟需待解决的问题。
本申请的主要目的在于提供一种资源处理方法、通信设备及存储介质,旨在提高频域资源分配的有效性,实现频域资源的灵活调度。
本申请提供一种资源处理方法,可应用于通信设备(如手机),包括步骤:
S20,接收下行信息,根据第一策略确定物理下行链路共享信道的可用频域资源位置。
可选地,第一策略的获取或确定的方式可以有多种,比如,第一策略可以是预设的策略,也可以是由下行信息发送直接得到,或者是通过下行信息中的内容确定或生成得到。
可选地,所述下行信息包括以下至少一项:
传输次数;满足第一预设规则的频域资源分配字段。
可选地,所述传输次数包括以下至少一项:
所述传输次数由下行链路控制信息配置;所述传输次数与控制资源集的配置周期有关;所述传输次数的最大取值与频域资源分组组数有关。
可选地,所述频域资源分组组数由激活带宽部分大小和预设带宽确定。
可选地,所述满足第一预设规则包括:
所述频域资源分配字段包括资源块集和/或第一频域资源分配。
可选地,所述方法还包括以下至少一项:
所述资源块集的大小与子载波间隔有关;所述资源块集大小与所述预设带宽有关;所述资源块集的比特数目与激活带宽中资源块集数目有关;所述资源块集的比特数目与激活带宽中资源块集表示方式有关;所述第一频域资源分配的比特数目与频域资源分配类型有关;所述资源块集所占的频域资源位置由与激活带宽部分频域位置有关的第二预设公式确定。
可选地,所述第一策略包括以下至少一项:
根据与传输次数相关的第一预设公式确定物理下行链路共享信道的可用频域资源位置;
根据所述资源块集和满足第一预设规则的频域资源分配字段中的第一频域资源分配取交集确定物理下行链路共享信道的可用频域资源位置;
根据预设截取比特的方式确定物理下行链路共享信道的可用频域资源位置;
根据缩放因子确定物理下行链路共享信道的可用频域资源位置。
可选地,所述缩放因子与激活带宽大小和/或所述预设带宽有关。
本申请还提出一种资源处理方法,可应用于通信设备(如基站),包括步骤:
S10,发送下行信息,以使终端根据第一策略确定物理下行链路共享信道的可用频域资源位置。
可选地,第一策略的获取或确定的方式可以有多种,比如,第一策略可以是预设的策略,也可以是由下行信息发送直接得到,或者是通过下行信息中的内容确定或生成得到。
可选地,所述步骤S20包括以下至少一项:
根据无线资源连接状态发送下行信息;根据终端类型获取状态发送下行信息。
可选地,所述下行信息包括以下至少一项:
传输次数;满足第一预设规则的频域资源分配字段;下行链路控制信息;无线资源控制信息;系统信息。
可选地,所述方法还包括以下至少一项:
所述传输次数由下行链路控制信息配置;所述传输次数与控制资源集的配置周期有关;所述传输次数的最大取值与频域资源分组组数有关。
可选地,所述满足第一预设规则包括:
所述频域资源分配字段包括资源块集和/或第一频域资源分配。
可选地,所述第一策略包括以下至少一项:
根据与传输次数相关的第一预设公式确定物理下行链路共享信道的可用频域资源位置;
根据频域资源分配字段中的资源块集和第一频域资源分配取交集确定物理下行链路共享信道的可用频域资源位置;
根据预设截取比特的方式确定物理下行链路共享信道的可用频域资源位置;
根据缩放因子确定物理下行链路共享信道的可用频域资源位置。
本申请还提供一种资源处理装置,包括:
接收模块,用于接收下行信息,根据第一策略确定物理下行链路共享信道的可用频域资源位置。
本申请还提供一种资源处理装置,包括:
发送模块,用于发送下行信息,以使终端根据第一策略确定物理下行链路共享信道的可用频域资源位置。
本申请还提供一种通信设备,所述通信设备包括:存储器、处理器及存储在所述存储器上并可在所述处理器上运行的资源处理程序,所述资源处理程序被所述处理器执行时实现如任一上述的资源处理方法的步骤。
本申请还提供一种存储介质,所述存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现如任一上述的资源处理方法的步骤。
本申请实施例还提供一种计算机程序产品,计算机程序产品包括计算机程序代码,当计算机程序代码在计算机上运行时,使得计算机执行如任一上述的资源处理方法的步骤。
本申请实施例还提供一种芯片,包括存储器和处理器,存储器用于存储计算机程序,处理器用于从存储器中调用并运行计算机程序,使得安装有芯片的设备执行如任一上述的资源处理方法的步骤。
本申请技术方案提高了频域资源分配的有效性,实现了频域资源的灵活调度,尤其是在激活带宽部分大于最大数据调度带宽5MHz时,可以根据实际调度的数据带宽调整资源块组的粒度,以实现调度灵活性,以及保证下行链路控制信息中的频域资源分配字段的有效利用,减少下行链路控制信息中的比特浪费。
此处的附图被并入说明书中并构成本说明书的一部分,示出了符合本申请的实施例,并与说明书一起用于解释本申请的原理。为了更清楚地说明本申请实施例的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,对于本领域普通技术人员而言,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1为实现本申请各个实施例的一种移动终端的硬件结构示意图;
图2为本申请实施例提供的一种通信网络系统架构图;
图3为本申请资源处理方法实施例涉及的控制器140的硬件结构示意图;
图4为本申请资源处理方法实施例涉及的网络节点150的硬件结构示意图;
图5为本申请资源处理方法实施例终端设备与网络设备的交互流程示意图;
图6为本申请资源处理方法实施例涉及的频域资源索引占用分配示意图;
图7为本申请资源处理方法实施例涉及的第一种RB set所包含的频域资源示意图;
图8为本申请资源处理方法实施例涉及的第二种RB set所包含的频域资源示意图;
图9为本申请资源处理方法实施例涉及的第三种RB set所包含的频域资源示意图;
图10为本申请资源处理方法实施例涉及的第四种RB set所包含的频域资源示意图;
图11为本申请资源处理方法实施例涉及的第五种RB set所包含的频域资源示意图;
图12为本申请资源处理方法实施例涉及的一种R18增强轻型能力终端的物理下行链路共享信道频域调度示意图;
图13为本申请资源处理方法实施例涉及的另一种R18增强轻型能力终端的物理下行链路共享信道频域调度示意图;
图14为传统设备对应的截取比特前的带宽接收示意图示意图;
图15为本申请实施例中R18增强轻型能力终端对应的截取比特后的带宽接收示意图示意图;
图16为本申请资源处理方法实施例涉及的5MHz物理下行链路共享信道的一种频域映射资源位置示意图;
图17为本申请资源处理方法实施例涉及的5MHz物理下行链路共享信道的另一种频域映射资源位置示意图。
本申请目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。通过上述附图,已示出本申请明确的实施例,后文中将有更详细的描述。这些附图和文字描述并不是为了通过任何方式限制本申请构思的范围,而是通过参考特定实施例为本领域技术人员说明本申请的概念。
本申请的实施方式
这里将详细地对示例性实施例进行说明,其示例表示在附图中。下面的描述涉及附图时,除非另有表示,不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反,它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下, 由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素,此外,本申请不同实施例中具有同样命名的部件、特征、要素可能具有相同含义,也可能具有不同含义,其具体含义需以其在该具体实施例中的解释或者进一步结合该具体实施例中上下文进行确定。
应当理解,尽管在本文可能采用术语第一、第二、第三等来描述各种信息,但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如,在不脱离本文范围的情况下,第一信息也可以被称为第二信息,类似地,第二信息也可以被称为第一信息。取决于语境,如在此所使用的词语"如果"可以被解释成为"在……时"或"当……时"或"响应于确定"。再者,如同在本文中所使用的,单数形式“一”、“一个”和“该”旨在也包括复数形式,除非上下文中有相反的指示。应当进一步理解,术语“包含”、“包括”表明存在所述的特征、步骤、操作、元件、组件、项目、种类、和/或组,但不排除一个或多个其他特征、步骤、操作、元件、组件、项目、种类、和/或组的存在、出现或添加。本申请使用的术语“或”、“和/或”、“包括以下至少一个”等可被解释为包括性的,或意味着任一个或任何组合。例如,“包括以下至少一个:A、B、C”意味着“以下任一个:A;B;C;A和B;A和C;B和C;A和B和C”,再如,“A、B或C”或者“A、B和/或C”意味着“以下任一个:A;B;C;A和B;A和C;B和C;A和B和C”。仅当元件、功能、步骤或操作的组合在某些方式下内在地互相排斥时,才会出现该定义的例外。·
应该理解的是,虽然本申请实施例中的流程图中的各个步骤按照箭头的指示依次显示,但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明,这些步骤的执行并没有严格的顺序限制,其可以以其他的顺序执行。而且,图中的至少一部分步骤可以包括多个子步骤或者多个阶段,这些子步骤或者阶段并不必然是在同一时刻执行完成,而是可以在不同的时刻执行,其执行顺序也不必然是依次进行,而是可以与其他步骤或者其他步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
取决于语境,如在此所使用的词语“如果”、“若”可以被解释成为“在……时”或“当……时”或“响应于确定”或“响应于检测”。类似地,取决于语境,短语“如果确定”或“如果检测(陈述的条件或事件)”可以被解释成为“当确定时”或“响应于确定”或“当检测(陈述的条件或事件)时”或“响应于检测(陈述的条件或事件)”。
需要说明的是,在本文中,采用了诸如S10、S20等步骤代号,其目的是为了更清楚简要地表述相应内容,不构成顺序上的实质性限制,本领域技术人员在具体实施时,可能会先执行S20后执行S10等,但这些均应在本申请的保护范围之内。
应当理解,此处所描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
在后续的描述中,使用用于表示元件的诸如“模块”、“部件”或者“单元”的后缀仅为了有利于本申请的说明,其本身没有特定的意义。因此,“模块”、“部件”或者“单元”可以混合地使用。
本申请中提及的通信设备,可以是终端设备(如移动终端,具体如手机),也可以是网络设备(如基站),具体所指,需要结合上下文加以明确。
可选地,终端设备可以以各种形式来实施。例如,本申请中描述的终端设备可以包括诸如手机、平板电脑、笔记本电脑、掌上电脑、个人数字助理(Personal Digital Assistant,PDA)、便捷式媒体播放器(Portable Media Player,PMP)、导航装置、可穿戴设备、智能手环、计步器等智能终端,以及诸如数字TV、台式计算机等固定终端。
后续描述中将以移动终端为例进行说明,本领域技术人员将理解的是,除了特别用于移动目的的元件之外,根据本申请的实施方式的构造也能够应用于固定类型的终端。
请参阅图1,其为实现本申请各个实施例的一种移动终端的硬件结构示意图,该移动终端100可以包括:RF(Radio Frequency,射频)单元101、WiFi模块102、音频输出单元103、A/V(音频/视频)输入单元104、传感器105、显示单元106、用户输入单元107、接口单元108、存储器109、处理器110、以及电源111等部件。本领域技术人员可以理解,图1中示出的移动终端结构并不构成对移动终端的限定,移动终端可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
下面结合图1对移动终端的各个部件进行具体的介绍:
射频单元101可用于收发信息或通话过程中,信号的接收和发送,具体的,将基站的下行信息接收后,给处理器110处理;另外,将上行的数据发送给基站。通常,射频单元101包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外,射频单元101还可以通过无线通信与网络和其他设备通信。上述无线通信可以使用任一通信标准或协议,包括但不限于GSM(Global System of Mobile communication,全球移动通讯系统)、GPRS(General Packet Radio Service,通用分组无线服务)、CDMA2000(Code Division Multiple Access 2000,码分多址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,分时双工长期演进)和5G等。
WiFi属于短距离无线传输技术,移动终端通过WiFi模块102可以帮助用户收发电子邮件、浏览网页和访问流式媒体等,它为用户提供了无线的宽带互联网访问。虽然图1示出了WiFi模块102,但是可以理解的是,其并不属于移动终端的必须构成,完全可以根据需要在不改变发明的本质的范围内而省略。
音频输出单元103可以在移动终端100处于呼叫信号接收模式、通话模式、记录模式、语音识别模式、广播接收模式等等模式下时,将射频单元101或WiFi模块102接收的或者在存储器109中存储的音频数据转换成音频信号并且输出为声音。而且,音频输出单元103还可以提供与移动终端100执行的特定功能相关的音频输出(例如,呼叫信号接收声音、消息接收声音等等)。音频输出单元103可以包括扬声器、蜂鸣器等等。
A/V输入单元104用于接收音频或视频信号。A/V输入单元104可以包括图形处理器(Graphics Processing Unit,GPU)1041和麦克风1042,图形处理器1041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元106上。经图形处理器1041处理后的图像帧可以存储在存储器109(或其它存储介质)中或者经由射频单元101或WiFi模块102进行发送。麦克风1042可以在电话通话模式、记录模式、语音识别模式等等运行模式中经由麦克风1042接收声音(音频数据),并且能够将这样的声音处理为音频数据。处理后的音频(语音)数据可以在电话通话模式的情况下转换为可经由射频单元101发送到移动通信基站的格式输出。麦克风1042可以实施各种类型的噪声消除(或抑制)算法以消除(或抑制)在接收和发送音频信号的过程中产生的噪声或者干扰。
移动终端100还包括至少一种传感器105,比如光传感器、运动传感器以及其他传感器。可选地,光传感器包括环境光传感器及接近传感器,可选地,环境光传感器可根据环境光线的明暗来调节显示面板1061的亮度,接近传感器可在移动终端100移动到耳边时,关闭显示面板1061和/或背光。作为运动传感器的一种,加速计传感器可检测各个方向上(一般为三轴)加速度的大小,静止时可检测出重力的大小及方向,可用于识别手机姿态的应用(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等;至于手机还可配置的指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等其他传感器,在此不再赘述。
显示单元106用于显示由用户输入的信息或提供给用户的信息。显示单元106可包括显示面板1061,可以采用液晶显示器(Liquid Crystal Display,LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板1061。
用户输入单元107可用于接收输入的数字或字符信息,以及产生与移动终端的用户设置以及功能控制有关的键信号输入。可选地,用户输入单元107可包括触控面板1071以及其他输入设备1072。触控面板1071,也称为触摸屏,可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板1071上或在触控面板1071附近的操作),并根据预先设定的程式驱动相应的连接装置。触控面板1071可包括触摸检测装置和触摸控制器两个部分。可选地,触摸检测装置检测用户的触摸方位,并检测触摸操作带来的信号,将信号传送给触摸控制器;触摸控制器从触摸检测装置上接收触摸信息,并将它转换成触点坐标,再送给处理器110,并能接收处理器110发来的命令并加以执行。此外,可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板1071。除了触控面板1071,用户输入单元107还可以包括其他输入设备1072。可选地,其他输入设备1072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆等中的一种或多种,具体此处不做限定。
可选地,触控面板1071可覆盖显示面板1061,当触控面板1071检测到在其上或附近的触摸操作后,传送给处理器110以确定触摸事件的类型,随后处理器110根据触摸事件的类型在显示面板1061上提供相应的视觉输出。虽然在图1中,触控面板1071与显示面板1061是作为两个独立的部件来实现移动终端的输入和输出功能,但是在某些实施例中,可以将触控面板1071与显示面板1061集成而实现移动终端的输入和输出功能,具体此处不做限定。
接口单元108用作至少一个外部装置与移动终端100连接可以通过的接口。例如,外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元108可以用于接收来自外部装置的输入(例如,数据信息、电力等等)并且将接收到的输入传输到移动终端100内的一个或多个元件或者可以用于在移动终端100和外部装置之间传输数据。
存储器109可用于存储软件程序以及各种数据。存储器109可主要包括存储程序区和存储数据区,可选地,存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功 能等)等;存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外,存储器109可以包括高速随机存取存储器,还可以包括非易失性存储器,例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器110是移动终端的控制中心,利用各种接口和线路连接整个移动终端的各个部分,通过运行或执行存储在存储器109内的软件程序和/或模块,以及调用存储在存储器109内的数据,执行移动终端的各种功能和处理数据,从而对移动终端进行整体监控。处理器110可包括一个或多个处理单元;优选的,处理器110可集成应用处理器和调制解调处理器,可选地,应用处理器主要处理操作系统、用户界面和应用程序等,调制解调处理器主要处理无线通信。可以理解的是,上述调制解调处理器也可以不集成到处理器110中。
移动终端100还可以包括给各个部件供电的电源111(比如电池),优选的,电源111可以通过电源管理系统与处理器110逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
尽管图1未示出,移动终端100还可以包括蓝牙模块等,在此不再赘述。
为了便于理解本申请实施例,下面对本申请的移动终端所基于的通信网络系统进行描述。
请参阅图2,图2为本申请实施例提供的一种通信网络系统架构图,该通信网络系统为通用移动通信技术的LTE系统,该LTE系统包括依次通讯连接的UE(User Equipment,用户设备)201,E-UTRAN(Evolved UMTS Terrestrial Radio Access Network,演进式UMTS陆地无线接入网)202,EPC(Evolved Packet Core,演进式分组核心网)203和运营商的IP业务204。
可选地,UE201可以是上述终端100,此处不再赘述。
E-UTRAN202包括eNodeB2021和其它eNodeB2022等。可选地,eNodeB2021可以通过回程(backhaul)(例如X2接口)与其它eNodeB2022连接,eNodeB2021连接到EPC203,eNodeB2021可以提供UE201到EPC203的接入。
EPC203可以包括MME(Mobility Management Entity,移动性管理实体)2031,HSS(Home Subscriber Server,归属用户服务器)2032,其它MME2033,SGW(Serving Gate Way,服务网关)2034,PGW(PDN Gate Way,分组数据网络网关)2035和PCRF(Policy and Charging Rules Function,政策和资费功能实体)2036等。可选地,MME2031是处理UE201和EPC203之间信令的控制节点,提供承载和连接管理。HSS2032用于提供一些寄存器来管理诸如归属位置寄存器(图中未示)之类的功能,并且保存有一些有关服务特征、数据速率等用户专用的信息。所有用户数据都可以通过SGW2034进行发送,PGW2035可以提供UE 201的IP地址分配以及其它功能,PCRF2036是业务数据流和IP承载资源的策略与计费控制策略决策点,它为策略与计费执行功能单元(图中未示)选择及提供可用的策略和计费控制决策。
IP业务204可以包括因特网、内联网、IMS(IP Multimedia Subsystem,IP多媒体子系统)或其它IP业务等。
虽然上述以LTE系统为例进行了介绍,但本领域技术人员应当知晓,本申请不仅仅适用于LTE系统,也可以适用于其他无线通信系统,例如GSM、CDMA2000、WCDMA、TD-SCDMA、5G以及未来新的网络系统(如6G)等,此处不做限定。
基于上述移动终端硬件结构以及通信网络系统,提出本申请各个实施例。
图3为本申请提供的一种控制器140的硬件结构示意图。该控制器140包括:存储器1401和处理器1402,存储器1401用于存储程序指令,处理器1402用于调用存储器1401中的程序指令执行上述方法实施例一中控制器所执行的步骤,其实现原理以及有益效果类似,此处不再进行赘述。
可选地,上述控制器还包括通信接口1403,该通信接口1403可以通过总线1404与处理器1402连接。处理器1402可以控制通信接口1403来实现控制器140的接收和发送的功能。
图4为本申请提供的一种网络节点150的硬件结构示意图。该网络节点150包括:存储器1501和处理器1502,存储器1501用于存储程序指令,处理器1502用于调用存储器1501中的程序指令执行上述方法实施例一中首节点所执行的步骤,其实现原理以及有益效果类似,此处不再进行赘述。
可选地,上述控制器还包括通信接口1503,该通信接口1503可以通过总线1504与处理器1502连接。处理器1502可以控制通信接口1503来实现网络节点150的接收和发送的功能。
上述以软件功能模块的形式实现的集成的模块,可以存储在一个计算机可读取存储介质中。上述软件功能模块存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)或处理器(英文:processor)执行本申请各个实施例方法的部分步骤。
本实施例涉及的技术术语:
RB:Resource Block,资源块;
RBG:Resource Block Groups,资源块组;
RB set:Resource Block set,资源块集;
FDRA:Frequency domain resource assignment,频域资源分配;
SIB1:system Information Block 1,系统信息块1;
CSS:Common search space,公共搜索空间;
USS:UE-specific search space,UE特定搜索空间;
BWP:Bandwidth Part,带宽部分。BWP是NR引入的新概念,旨在适应各种不同类型的终端。因为NR是高带宽的系统,并不是所有的终端都可以应用这种高带宽,所以可以使用这种小带宽系统。 BWP相当于把5G的频谱在一定的时间内划分成了很多的小块,每个BWP可以使用不同的参数集如每个BWP的带宽、子载波间隔以及其他控制参数都可以不同;
CORESET:Control Resource set,控制资源集;
RRC:Radio Reource Control,无线资源控制;
MSB:Most Significant Bit,最高有效位;
LSB:Least Significant Bit,最低有效位;
PDSCH:Physical Downlink Shared Channel,物理下行链路共享信道;
DCI:Downlink Control Information,下行链路控制信息;
RIV:Resource Indication Value,资源指示值;
SI-RNTI:System Information Radio-Network Temporary Identifier,系统消息无线网络临时标识符;
CRB:Common Resource Block,公共资源块;
PRB:Physical Resource Block,物理资源块。
参照图5所示,本申请实施例提出一种资源处理方法,包括步骤:
S10,网络设备发送下行信息;
S20,终端设备接收下行信息,根据第一策略确定物理下行链路共享信道的可用频域资源位置。
本申请实施例资源处理方法可以应用于终端设备(如手机)(以下简称终端),也可以应用于网络设备(如基站)。
可选地,下行信息由网络设备下发,终端接收到网络设备下发的下行信息后,基于接收的下行信息并根据第一策略确定物理下行链路共享信道的可用频域资源位置。
可选地,可用频域资源位置可以为R18增强轻型能力终端的物理下行链路共享信道的可用频域资源位置。
可选地,网络设备可以根据无线资源连接状态向终端侧和/或终端类型获取状态发送下行信息。
可选地,所述终端类型获取状态是指当前服务小区对应的基站是否知道终端类型。
可选地,所述终端类型可以包括传统终端、R17轻型能力设备终端和R18增强轻型能力终端。
可选地,所述下行信息包括以下至少一项:
下行链路控制信息;无线资源控制信息;系统信息。
可选地,所述下行信息还包括以下至少一项:传输次数;满足第一预设规则的频域资源分配字段。
可选地,本申请实施例方案还包括以下至少一项:所述传输次数由下行链路控制信息配置;所述传输次数与控制资源集的配置周期有关;所述传输次数的最大取值与频域资源分组组数有关。
可选地,所述频域资源分组组数由激活带宽部分大小和预设带宽确定。
可选地,所述预设带宽由R18增强轻型能力终端可以处理的最大物理下行链路共享信道的带宽确定。
可选地,所述满足第一预设规则包括:所述频域资源分配字段包括资源块集和第一频域资源分配。
可选地,所述方法还包括以下至少一项:所述资源块集的大小与子载波间隔有关;所述资源块集大小与所述预设带宽有关;所述资源块集的比特数目与激活带宽中资源块集数目有关;所述资源块集的比特数目与激活带宽中资源块集表示方式有关。
可选地,所述资源块集所占的频域资源位置由与激活带宽部分频域位置有关的第二预设公式确定。
可选地,所述第一频域资源分配的比特数目与频域资源分配类型有关。
可选地,第一策略的获取或确定的方式可以有多种,比如,第一策略可以是预设的策略,也可以是由下行信息发送直接得到,或者是通过下行信息中的内容确定或生成得到。
可选地,所述第一策略包括以下至少一项:
根据与传输次数相关的第一预设公式确定物理下行链路共享信道的可用频域资源位置;根据所述资源块集和满足第一预设规则的频域资源分配字段中的第一频域资源分配取交集确定物理下行链路共享信道的可用频域资源位置;根据预设截取比特的方式确定物理下行链路共享信道的可用频域资源位置;根据缩放因子确定物理下行链路共享信道的可用频域资源位置。
可选地,所述缩放因子与激活带宽大小及所述预设带宽有关。
可选地,所述第一策略与终端所处的无线资源连接状态和/或基站是否知道终端所属终端类型有关。
可选地,无线资源连接状态包括RRC连接态、RRC空闲态和RRC非激活态。
以下结合不同场景,对本实施例中第一策略及实施例的具体实现进行详细阐述:
可选地,作为第一种场景,当终端初始接入时(终端进入RRC连接态之前)和/或基站未知终端类型时,第一策略可以为:根据与传输次数相关的第一预设公式确定R18增强轻型能力终端的物理下行链路共享信道的可用频域资源位置。
可选地,传输次数是指当前周期性物理下行链路共享信道传输是周期内的第几次重复传输。
可选地,传输次数可以由下行链路控制信息中的传输次数字段获得;
可选地,传输次数还可以根据无线资源控制信息或系统信息中的控制资源集配置获得;
可选地,若物理下行链路共享信道为周期性业务,传输次数取值可以为控制资源集在周期中出现的次数确定。如若物理下行链路共享信道的周期为160ms,若以无线帧0的子帧0为周期的起始位置,则物理下行链路共享信道的160ms周期是指无线帧0到无线帧16的所有子帧。根据无线资源控制信息或系统信息中的控制资源集配置可以获取与周期性物理下行链路共享信道相关联的控制资源集在这160ms周期内出现的次数,进而获得物理下行链路共享信道在160ms周期内出现的次数。
可选地,传输次数还可以取决于UE实现。
可选地,若传输次数取决于UE实现,则UE以每个周期点开始位置接收到的物理下行链路共享信道为第一次传输,累积计数当前的接收是第几次物理下行链路共享信道传输。
可选地,第一预设公式由传输次数、满足第一预设规则的频域资源分配字段和/或预设带宽确定。
可选地,满足第一预设规则的频域资源分配字段可以位于下行链路控制信息。
可选地,根据第一策略“根据与传输次数相关的第一预设公式确定R18增强轻型能力终端的物理下行链路共享信道的可用频域资源位置”的具体实施方式阐述如下:
首先,根据下行信息中的满足第一预设规则的频域资源分配字段对应的RIV值获得周期性传输业务在BWP的频域位置,如频域资源开始位置、频域资源持续RB个数或资源块组的频域映射位置。
其次,根据下行信息或预配置信息获取预设带宽对应的连续RB个数D。
最后,根据所述频域位置及与传输次数有关的第一预设公式,计算第G次传输时,终端可处理的D个连续RB索引。
可选地,传输次数和频域资源分配字段所占比特数目处理如下:
若传输次数由下行链路控制信息中的传输次数字段获得,则其所占比特数目与周期性业务在一个周期内需要完成覆盖需求所需要的最大传输次数有关。
比如,SIB1传输周期为160ms,每20ms有一次SIB1传输时机,且需要完成SIB1完整或准确接收需要的最大传输次数是5,则下行链路控制信息中的传输次数字段所占的比特数目为3,其中“000”为SIB1在160ms周期内的首次传输,“001”为160ms周期内第二次传输,以此类推;需要完成SIB1完整或准确接收需要的最大传输次数是4,则下行链路控制信息中的传输次数字段所占的比特数目为2,其中“00”为SIB1在160ms周期内的首次传输,“01”为160ms周期内第二次传输,以此类推。
可选地,周期性业务在一个周期内需要完成覆盖需求所需要的最大传输次数由ceil(激活带宽部分大小/预带宽大小)确定。
若传输次数是根据无线资源控制信息或系统信息中的控制资源集配置获得,则传输次数不占用任何下行信令。
可选地,若物理下行链路共享信道的周期为160ms,若以无线帧0的子帧0为周期的起始位置,则物理下行链路共享信道的160ms周期是指无线帧0到无线帧16的所有子帧。根据无线资源控制信息或系统信息中的控制资源集配置可以获取与周期性物理下行链路共享信道相关联的控制资源集在这160ms周期内出现的次数,进而获得物理下行链路共享信道在160ms周期内出现的次数。
若传输次数取决于UE实现,则UE以每个周期点开始位置接收到的物理下行链路共享信道为第一次传输,累计计数当前的接收是第几次物理下行链路共享信道传输。
一种实现方式中,传输次数与物理下行链路共享信道频域资源组数采用非交织映射。
可选地,传输次数与物理下行链路共享信道频域资源组数采用非交织映射,是指第一次物理下行链路共享信道接收可以接收第一组频域资源位置,第二次物理下行链路共享信道接收可以接收第二组频域资源位置,以此类推。
以周期性业务SIB1为例,UE根据与传输次数相关的第一预设公式确定物理下行链路共享信道的频域资源位置的具体实现如下:
步骤1:获取周期性业务SIB1当前的传输次数G,也即获得本时隙是SIB1的第G次传输;
步骤2:根据SI-RNTI加扰的DCI中的频域资源分配字段对应的RIV值获得SIB1在激活带宽部分的RB
start和L
RBs,其中,RB
start为SIB1在激活带宽部分的频域开始位置和L
RBs为SIB1在激活带宽部分的频域持续资源块长度;
步骤3:根据与传输次数相关的第一预设公式计算R18增强轻型能力终端的频域起始RB索引,与传输次数相关的第一预设公式可以表示如下:
RB′
start=(RB
start+(T-1)*D)mod(L
RBs+RB
start);
其中,D为预设带宽对应的连续RB个数,T为物理下行链路共享信道频域资源组数,若传输次数与物理下行链路共享信道频域资源组数采用非交织映射,则T与传输次数G相等;
可选地,预设带宽由R18增强轻型能力终端可以处理的最大物理下行链路共享信道的带宽确定。
根据上述公式获得R18增强轻型能力终端的D个连续RB索引如下:
RB′
start、(RB′
start+1)mod(L
RBs+RB
start)、........、(RB′
start+D-1)mod(L
RBs+RB
start)。
可选地,D与子载波间隔有关,以预设带宽为5MHz为例,R18增强轻型能力终端每次可处理的连续RB数D如下表1所示:
表1、R18增强轻型能力终端每次可处理的连续RB数D
子载波间隔为15KHz | 子载波间隔为30KHz |
25RB | 11RB/12RB(PRACH) |
设物理下行链路共享信道子载波间隔为15KHz,5MHz预设带宽对应的连续RB数D=25RB,CORESET#0带宽为48RB,PDSCH频域资源分配类型为1,DCI中频域资源分配字段对应的RIV值为861,根据RIV值和下述公式:
else
可选地,若本时隙SIB1的传输次数G=1,根据
RB′
start=(RB
start+(G-1)*D)mod(L
RBs+RB
start)
=(2+(1-1)*25)mod(32+2)
=2
可得,R18增强轻型能力终端的25个连续RB索引为:2、3、4、......、26,参照图6所示。
若传输次数G=2,根据
RB′
start=(RB
start+(G-1)*D)mod(L
RBs+RB
start)
=(2+(2-1)*25)mod(32+2)
=27;
可得,R18增强轻型能力终端的25个连续RB索引为:27、28、......、33、0、1、......、17。
需要注意的是:上述的RB索引都是以激活带宽部分为基准的,也即RB索引0对应激活BWP中的第一个RB索引。
另一种实现方式中,传输次数与物理下行链路共享信道频域资源接收组数采用交织映射。
可选地,传输次数与物理下行链路共享信道的频域资源接收组数采用交织映射,是指第一次物理下行链路共享信道接收可以是接收第M组频域资源位置,第二次物理下行链路共享信道接收可以是接收第N组频域资源位置,其中M和N不一定是连续分组的频域资源位置,且M和N均对应于上述步骤3中第一预设公式中的参数T。
相较于现有技术,本实施例方案中,当终端初始接入时和/或基站尚未获知终端设备类型时,针对某些周期性传输业务,比如SIB1,终端可以根据传输次数确定当前传输的物理下行链路共享信道是第 几次传输,进而终端在不修改现有频域资源分配字段比特数目和映射规则的前提下,也可以根据与传输次数有关的频域接收方案完成周期性传输业务的完整接收。本方案可以保证轻型能力设备和传统设备的有效兼容,也能保证轻型能力设备在有限带宽场景下实现周期性业务的完整接收,还能保证轻型能力设备的调度灵活性。
可选地,作为第二种场景,在终端处于RRC连接态和/或基站已知终端设备类型时,第一策略可以为:UE根据资源块集和满足第一预设规则的频域资源分配字段中的第一频域资源分配取交集确定R18增强轻型能力终端的物理下行链路共享信道的可用频域资源位置。
可选地,满足第一预设规则包括以下至少一项:
所述频域资源分配字段包括资源块集和第一频域资源分配;
所述频域资源分配字段仅包括第一频域资源分配。
可选地,满足第一预设规则的频域资源分配字段可以位于DCI中;
可选地,资源块集取频域资源分配字段中的X最高有效位(MSB)比特;第一频域资源分配取频域资源分配字段中的Y最低有效位(LSB)比特;
可选地,第一频域资源分配所占的比特数目Y与物理下行链路共享信道的频域资源分配类型有关;
可选地,所述资源块集所占的比特数目X与激活带宽大小、UE支持的最大物理下行链路共享信道的带宽大小或子载波间隔中的至少一项有关;
可选地,资源块集也可以由无线资源控制信息或系统信息配置;
可选地,资源块集包含的最大资源块数目与子载波间隔有关。
可选地,一种实施方式中,根据第一策略“UE根据资源块集和满足第一预设规则的频域资源分配字段中的第一频域资源分配取交集确定R18增强轻型能力终端的物理下行链路共享信道的可用频域资源位置”的具体实施方式阐述如下:
首先,根据X个资源块集比特确定物理下行链路共享信道频域资源所在的资源块集位置;
其次,根据物理下行链路共享信道的频域资源分配类型和所述频域资源分配字段中的Y个第一频域资源分配比特确定物理下行链路共享信道在上述确定的资源块集中所占的频域资源位置。
可选地,所述资源块集所占的频域资源位置由与激活带宽部分频域位置有关的第二预设公式确定。
一种实现方式中,若DCI中的“频域资源分配”字段同时包括资源块集和第一频域资源分配,且资源块集占据“频域资源分配”字段的X个最高有效位比特,第一频域资源分配占据“频域资源分配”字段的Y个最低有效位比特,则UE根据X个最高有效位比特确定物理下行链路共享信道频域资源所在的资源块集,再根据物理下行链路共享信道的频域资源分配类型和Y最低有效位比特确定物理下行链路共享信道在资源块集中的具体频域RB位置,具体实现如下:
设DCI中的频域资源分配字段比特数目为:X+Y比特,其中,X个最高有效位比特提供资源块集的位置,Y个最低有效位比特提供指定资源块集内的具体可用的RB索引。
可选地,X对应的比特数目与激活带宽中资源块集数目和激活带宽中资源块集表示方式有关,比如,设激活带宽中资源块集数目为6,若每个时刻需要表示的激活带宽中资源块集的数目大于1个,则X取值为6,若每个时刻需要表示的激活带宽中资源块集的数目为1个,则X取值为3。
可选地,Y对应的比特数目与频域资源分配类型有关,比如,若物理下行链路共享信道的频域资源映射类型为频域资源分配类型0,则Y取值为
若物理下行链路共享信道的频域资源映射类型为频域资源分配类型1,则Y取值为
若物理下行链路共享信道的频域资源分配类型为'dynamicSwitch',则Y取值为
且其最高1比特用于确定是资源分配类型0还是资源分配类型1。其中,
为资源块集包含的连续RB数目,P为新增的无线资源控制参数 resourceAllocationType1GranularityDCI-1-0-r17确定的RBG粒度,
为给定的资源块集的频域资源开始位置
可选地,无线资源控制参数resourceAllocationType1GranularityDCI-1-0-r17为:
resourceAllocationType1GranularityDCI-1-0-r17={n2,n4}。
可选地,若物理下行链路共享信道的频域资源分配类型被配置为'dynamicSwitch',若第一频域资源分配的最高比特为0,则表示'dynamicSwitch'指示当前的PDSCH的频域资源分配类型为频域资源分配类型0;若第一频域资源分配的最高比特为1,则表示'dynamicSwitch'指示当前的物理下行链路共享信道的频域资源分配类型为频域资源分配类型1。
可选地,P取值小于或等于激活带宽对应的资源块组大小。如此便可解决由于激活带宽部分过大导致的资源块组分配粒度过大的问题造成的频域资源浪费,以及频域调度调度灵活性问题。
另一种实现方式中,若DCI中的“频域资源分配”字段仅包括第一频域资源分配,且资源块集频域位置由无线资源控制消息、系统消息或预配置确定,则DCI中的“频域资源分配”字段所占的比特数目为Y,Y的具体取值与DCI中的“频域资源分配”字段同时包括资源块集和第一频域资源分配的实现方式中的定义相同。
下面将对资源块集的具体定义进行详细阐述:
首先,根据预设带宽确定不同子载波间隔场景下对应的RB数目。
其次,根据资源块集是否需要保护带或不满足资源块集最大资源块数目的剩余资源块的不同处理方式给出以下5种不同的资源块集(下述公式中用RB set表示)的定义方法:
可选地,资源块集所占的频域资源位置由与激活带宽部分频域位置有关的第二预设公式确定,其中,第二预设公式为每个资源块集开始和结束的CRB索引的计算公式。
方法1:每个RB set开始和结束的CRB索引对应的第二预设公式如下:
方法2:
每个RB set开始和结束的CRB索引对应的第二预设公式如下:
或
方法3:
每个RB set开始和结束的CRB索引对应的第二预设公式如下:
方法4:
每个RB set开始和结束的CRB索引对应的第二预设公式如下:
方法5:
每个RB set开始和结束的CRB索引对应的第二预设公式需满足如下设计:
步骤1:在RB set中设置保护带;
步骤2:确定保护带位于激活带宽部分的位置,如保护带位于激活带宽部分的最高频边缘、保护带位于激活带宽部分的最低频边缘或激活带宽部分的中间任意位置。
步骤3:激活带宽部分中扣除保护带所在的RB后进行均分,按照频域由低到高进行划分,如若保护带位于激活带宽部分的最高频边缘,则激活带宽部分中的RB 0对应的CRB索引为第一个RB set的开始CRB索引,激活带宽部分中的RB
对应的CRB索引为第一个RB set的结束的CRB索引,激活带宽部分中的RB
对应的CRB索引为第X个RB set的开始CRB索引,激活带宽部分中的RB
对应的CRB索引为第X个RB set的结束的CRB索引,以此类推。
可选地,各RB set所包含的频域资源如图11所示。保护带位于激活带宽部分的最低频边缘或激活带宽部分的中间任意位置的场景与保护带位于激活带宽部分的最高频边缘的场景类似,都是扣除保护带所在的RB后进行均分后,选取连续的
个RB作为一个RB set。
可选地,终端接收到下行链路控制信息中的频域资源分配字段后,先根据上述5种方法中的任一种确定R18增强轻型能力终端的物理下行链路共享信道所在的资源块集索引,再根据物理下行链路共享信道频域资源分配类型和第一频域资源分配确定R18增强轻型能力终端的物理下行链路共享信道在指定的资源块集中的具体的资源块索引,最后,便可确定R18增强轻型能力终端的物理下行链路共享信道在BWP中的具体频域资源位置。
以下根据上述方法5确定物理下行链路共享信道的频域资源位置进行举例如下:
一种实现方式中,以物理下行链路共享信道频域资源分配类型为1且RB set的定义如方法5为例, 设频域资源分配字段同时包含资源块集和第一频域资源分配且频域资源分配字段为“010100101001”,其中最高3比特的资源块集索引比特为‘010’,最低9比特的第一频域资源分配比特为‘100101001’,则根据资源块集索引比特可得PDSCH所在的资源块集索引为3,根据第一频域资源分配比特可得第一频域资源分配对应的RIV值为297,可选地,根据以下公式:
else
可得R18增强轻型能力终端的物理下行链路共享信道在索引为3的资源块集中的频域资源开始位置RB
start=2,持续的资源块数目L
RBs=15,最终,可得R18增强轻型能力终端的物理下行链路共享信道的可用PRB索引为:PRB77~PRB91,具体如图12所示。
另一种实现方式中,以物理下行链路共享信道频域资源分配类型为0且RB set的定义如方法5所述为例进行阐述:
设激活带宽部分大小为106RB,预设带宽为5MHz,物理下行链路共享信道的子载波间隔为15KHz,则根据物理下行链路共享信道子载波间隔为15KHz可知一个RB set的RB数目
根据激活带宽部分大小和预设带宽大小可知,RB set总数为
若每个时刻仅需指示一个RB set,则资源块集索引指示所需的比特数目X=3,设新增RRC参数resourceAllocationType1GranularityDCI-1-0-r17确定的P取值为2,则根据一个RB set包含的RB数目和P的取值可得第一频域资源所需的比特数目为
可选地,设新增无线资源控制参数resourceAllocationType1GranularityDCI-1-0-r17确定P取值为2,以物理下行链路共享信道频域资源分配类型为1且RB set的定义如方法5为例,设频域资源分配字段同时包含资源块集和第一频域资源分配且“频域资源分配”字段为“010 1001010000101”,其中最高3bit的资源块集索引比特为‘010’,最低13比特的第一频域资源分配比特为‘1001010000101’,则根据资源块集索引比特可得物理下行链路共享信道所在的资源块集索引为3,根据第一频域资源分配比特可得指定资源集内的可用资源块组索引。
可选地,每个资源块组(RBG)包含的RB数目根据以下步骤获得:
步骤3:其他RBG大小也为2。
简言之,第一个RBG包含1个RB,其他RBG均包含2个RB。
事实上,根据上述资源块组计算和资源块集指示获得的R18增强轻型能力终端的物理下行链路共享信道的可用频域资源如图13所示:
即可用PRB为:PRB 75、PRB 80、PRB 81、PRB 84、PRB 85、PRB 94、PRB 95、PRB 98、PRB 99。
因此,在激活带宽部分大于R18增强轻型能力终端支持的最大数据调度带宽5MHz时,通过本申请中“根据第一策略确定物理下行链路共享信道的可用频域资源位置”的方案,可以确定R18增强轻型能力终端在激活BWP中的有效频域资源位置,实现频域资源调度的有效性和灵活性。
此外,本申请实施例方案相较于现有协议可以节省DCI比特。
下面以物理下行链路共享信道的频域资源分配类型为1,且RB set的定义如方法5所述为例进行阐述:
设激活带宽部分大小为106RB,预设带宽为5MHz,PDSCH的子载波间隔为15KHz,则根据物理下行链路共享信道子载波间隔为15KHz可知,一个RB set的RB数目
根据激活带宽部分大小和预设带宽大小可知,RB set总数为
若每个时刻仅需指示一个RB set,则RB set索引指示所需的比特数目X=3。又因为第一频域资源所需的比特数目
所以,若资源块集和第一频域资源分配位于DCI中的频域资源分配字段,则DCI中的频域资源分配字段所占的比特数目为X+Y=3+9=12比特;若DCI中的频域资源分配字段中仅包含第一频域资源分配,则DCI中的频域资源分配字段所占的比特数目为Y=9比特。
因此,在激活带宽部分大于R18增强轻型能力终端支持的最大数据调度带宽5MHz时,通过本申请中“根据第一策略确定物理下行链路共享信道的可用频域资源位置”的方案可以减少DCI中的比特浪费,以实现频域资源调度的有效性。
相较现有技术,本申请方案,在基站已知终端设备类型,但由于需要传输的控制信道资源所占用的带宽大于R18增强轻型能力终端所支持的最大物理下行链路共享信道带宽而导致激活带宽部分大于预设带宽的场景下,可以采用资源块集和频域资源分配字段的交集确定R18增强轻型能力终端的有效频域资源调度范围。本方案可以在激活带宽部分大于R18增强轻型能力终端所支持的最大物理下行链路共享信道带宽时,确定R18增强轻型能力终端在激活BWP中的有效频域资源位置,实现频域资源调度的有效性和灵活性,同时可以节省DCI中频域资源分配字段的占用比特数目,也可以解决带宽部分过大而导致的资源块组分配粒度过大的问题,进而可以保证R18增强轻型能力终端频域资源的有效及灵活调度。
可选地,作为第三种场景,在终端处于无线资源控制连接态和/或基站已知终端设备类型时,第一策略可以为:UE根据预设截取比特的方式确定R18增强轻型能力终端的物理下行链路共享信道的可用频域资源位置。
可选地,预设截取比特的方式包括:截取所述频域资源分配字段中的符合预设带宽需求的最低比特位,并通过截取获得的最低比特位确定轻型能力设备有效频域资源的频域开始位置、频域持续长度或有效资源块组位置中的至少一项。
可选地,所述频域资源分配字段位于下行链路控制信息中。
可选地,预设带宽由R18增强轻型能力终端可以处理的最大物理下行链路共享信道的带宽确定。
可选地,一种实施方式中,根据第一策略“UE根据预设截取比特的方式确定R18增强轻型能力终端的物理下行链路共享信道的可用频域资源位置”的具体实施方式阐述如下:
首先,根据预设带宽大小和物理下行链路共享信道的频域资源映射类型确定终端的频域资源所需的比特数目;
其次,截取频域资源分配字段中的最低的符合终端的频域资源所需的比特数目的比特;
最后,根据截取获得的比特信息以及物理下行链路共享信道的频域资源映射类型确定终端的频域资源的起始位置、连续RB数目或有效资源块组位置中的至少一项。
一种实施方式中,截取频域资源分配字段的符合预设带宽需求的最低比特位,以预设带宽为5MHz举例,具体实现如下:
假设激活带宽部分大小为52RB,物理下行链路共享信道的子载波间隔为15KHz,5MHz预设带宽对应的RB数目为25RB。
若采用频域资源分配类型1,根据预设带宽大小为5MHz,可知R18增强轻型能力终端频域资源分配所需的比特数目为
也即需截取最低9比特用于R18增强轻型能力终端频域资源分配,即若DCI中的频域资源分配字段的比特为“10110110001”,则R18增强轻型能力终端按照最低9比特“110110001”进行R18增强轻型能力终端的满足预设带宽的频域资源接收。
可选地,可以按照如下公式计算获得R18增强轻型能力终端的具体频域位置:
else
事实上,截取比特前,传统设备按照11比特“10110110001”计算其在激活带宽部分中的频域资源位置。
可选地,传统设备的频域资源映射的开始位置RB
start=1,频域资源持续长度为L
RBs=29;截取最低9比特“110110001”后,R18增强轻型能力终端在激活带宽部分中的可用的频域资源开始位置变为:RB
start=17,频域资源持续长度为:L
RBs=9。
若采用频域资源分配类型0,高层参数pdsch-Config的rbg-Size取值为config1,则根据激活带宽部分大小为52RB和下表2可得资源块组大小P=4。
表2:Nominal RBG size P
Bandwidth Part Size | Configuration 1 | Configuration 2 |
1–36 | 2 | 4 |
37–72 | 4 | 8 |
73–144 | 8 | 16 |
145–275 | 16 | 16 |
可选地,资源块组大小采用如下方式进行计算:
其他剩余的RBG大小为:P。
设
则根据上述公式可知,第一个和最后一个RBG大小为2,其余12个RBG大小均为4;根据DCI中的频域资源分配字段的比特“10010110110001”及R18增强轻型能力终端截取的最低7比特“0110001”可分别获得如图14和图15所示的传统设备和R18增强轻型能力终端的可用频域资源。图14为传统设备对应的截取比特前的可用频域资源,图15为R18增强轻型能力终端对应的截取比特后的可用频域资源,图中标注底色的为具体可用的RB位置。
相较于现有技术,本方案不改变现有DCI中“频域资源分配”字段的大小和含义,采用截取低位的方式获取R18增强轻型能力终端的5MHz频域资源位置信息,保证物理下行链路共享信道的频域资源限制在5MHz带宽内,实现频域资源的有效分配并实现频域资源的灵活调度。
可选地,作为第四种场景,在终端处于无线资源控制连接态和/或基站已知终端设备类型时,第一策略可以为:UE根据缩放因子确定物理下行链路共享信道的可用频域资源位置。
可选地,所述缩放因子与激活带宽大小及所述预设带宽有关。
可选地,预设带宽由R18增强轻型能力终端可以处理的最大物理下行链路共享信道的带宽确定。
可选地,一种实施方式中,根据第一策略“UE根据缩放因子确定物理下行链路共享信道的可用频域资源位置”的具体实施方式阐述如下:
首先,根据激活带宽和预设带宽大小确定缩放因子;
其次,根据下行链路控制信息中的频域资源分配字段对应的RIV值获取激活带宽对应的频域资源起始RB索引和连续RB数目;
然后,根据缩放因子修正激活带宽对应的频域资源起始RB索引和连续RB数目为预设带宽大小对应的频域资源起始RB索引和连续RB数目;
最后,根据预设带宽大小对应的频域资源起始RB索引和连续RB数目确定轻型能力设备的物理下行链路共享信道的可用频域资源位置。
一种实施方式中,UE可以采用等比例缩放方式,根据与激活带宽和预设带宽、以及RIV有关的预设原则确定频域资源位置,具体实现方式如下:
步骤1:根据频域资源分配中RIV值确定激活带宽部分对应的频域资源开始位置RB
start和频域资源持续长度L
RBs;
步骤3:确定预设带宽部分的频域资源位置:根据RB′
start=RB
start/K,L′
RBs=L
RBs/K确定预设带宽频域资源开始位置RB′
start和连续RB数目L′
RBs,其中,L'
RBs不超过
可选地,步骤1的计算方式:满足如下公式:
else
可选地,预设带宽大小为R18增强轻型能力终端支持的最大物理下行链路共享信道带宽大小;
可选地,预设带宽可以为5MHz。
举例如下:
假设激活带宽大小
物理下行链路共享信道的子载波间隔为15KHz,预设带宽5MHz对应的RB数为25,由于
所以K=4。设DCI中频域资源分配字段对应的RIV值为4138,可知RB
start=4,L
RBs=40,根据RB′
start=RB
start/K=4/4=1,L′
RBs=L
RBs/K=10,可得R18增强轻型能力终端的5MHz物理下行链路共享信道的频域映射资源位置如图16所示。
此种RIV的理解方式也可以结合RB set进行物理下行链路共享信道频域资源映射的理解,若资源块集的索引采用3比特‘010’表示,则上述方式计算获得物理下行链路共享信道频域资源映射位置为 如图17所示(此方案需要新增X比特的资源块集的指示)。
本方案不改变现有DCI中频域资源分配字段的比特数目,且通过有效的频域资源缩放保证R18增强轻型能力终端的灵活有效调度。
可选地,作为第五种场景,在终端处于无线资源控制连接态和/或基站已知终端设备类型时,UE还可以结合第四种场景和第二种场景共同确定R18增强轻型能力终端的物理下行链路共享信道频域资源位置,具体包括:
步骤1:根据第二种场景中资源块集的定义方式和资源块集位置的获取方式确定R18增强轻型能力终端可用的资源块集在激活带宽中的位置;
步骤2:根据第四种场景中获取缩放比例因子的方式确定资源块集中具体可用于R18增强轻型能力终端的物理下行链路共享信道调度的有效频域位置。
可选地,第四种场景中的激活带宽部分可以用资源块集替代进行换算。
同理,上述第二种场景、第三种场景、第四种场景中阐述的方法均可通过合理的结合进行R18增强轻型能力终端可用频域资源位置的确定。
通过上述实施例描述,结合5种场景可知,本申请实施例根据第一策略确定R18增强轻型能力终端的物理下行链路共享信道的可用频域资源位置,提高了频域资源分配的有效性,实现了频域资源的灵活调度,尤其是在激活带宽部分大于最大数据调度带宽5MHz时,可以根据实际调度的数据带宽调整资源块组的粒度,以实现调度灵活性,以及保证DCI中的频域资源分配字段的有效利用,减少DCI中的比特浪费。
后续,终端可以根据确定的可用频域资源位置进行频域资源分配。
本申请实施例还提供一种资源处理装置,包括:
接收模块,用于接收下行信息,根据第一策略确定物理下行链路共享信道的可用频域资源位置。
可选地,第一策略的获取或确定的方式可以有多种,比如,第一策略可以是预设的策略,也可以是由下行信息发送直接得到,或者是通过下行信息中的内容确定或生成得到。
可选地,所述下行信息包括以下至少一项:
传输次数;满足第一预设规则的频域资源分配字段。
可选地,所述传输次数包括以下至少一项:
所述传输次数由下行链路控制信息配置;所述传输次数与控制资源集的配置周期有关;所述传输次数的最大取值与频域资源分组组数有关。
可选地,所述频域资源分组组数由激活带宽部分大小和/或预设带宽确定。
可选地,所述满足第一预设规则包括:
所述频域资源分配字段包括资源块集和/或第一频域资源分配。
可选地,所述资源处理装置还包括以下至少一项:
所述资源块集的大小与子载波间隔有关;所述资源块集大小与所述预设带宽有关;所述资源块集的比特数目与激活带宽中资源块集数目有关;所述资源块集的比特数目与激活带宽中资源块集表示方式有关。
可选地,所述第一频域资源分配的比特数目与频域资源分配类型有关。
可选地,所述第一策略包括以下至少一项:
根据与传输次数相关的第一预设公式确定物理下行链路共享信道的可用频域资源位置;
根据所述资源块集和满足第一预设规则的频域资源分配字段中的第一频域资源分配取交集确定物理下行链路共享信道的可用频域资源位置;
根据预设截取比特的方式确定物理下行链路共享信道的可用频域资源位置;
根据缩放因子确定物理下行链路共享信道的可用频域资源位置。
可选地,所述缩放因子与激活带宽大小及所述预设带宽有关。
可选地,所述资源块集所占的频域资源位置由与激活带宽部分频域位置有关的第二预设公式确定。
本申请实施例还提供一种资源处理装置,包括:
发送模块,用于发送下行信息,以使终端根据第一策略确定物理下行链路共享信道的可用频域资源位置。
可选地,第一策略的获取或确定的方式可以有多种,比如,第一策略可以是预设的策略,也可以是由下行信息发送直接得到,或者是通过下行信息中的内容确定或生成得到。
可选地,发送模块还用于根据无线资源连接状态发送下行信息。
可选地,发送模块还用于根据终端类型获取状态发送下行信息。
可选地,所述下行信息包括以下至少一项:传输次数;满足第一预设规则的频域资源分配字段。
可选地,所述下行信息包括以下至少一项:下行链路控制信息;无线资源控制信息;系统信息。
可选地,所述资源处理装置还包括以下至少一项:
所述传输次数由下行链路控制信息配置;所述传输次数与控制资源集的配置周期有关;所述传输次数的最大取值与频域资源分组组数有关。
可选地,所述满足第一预设规则包括:所述频域资源分配字段包括资源块集和/或第一频域资源分配。
可选地,所述第一策略包括以下至少一项:
根据与传输次数相关的第一预设公式确定物理下行链路共享信道的可用频域资源位置;根据频域资源分配字段中的资源块集和第一频域资源分配取交集确定物理下行链路共享信道的可用频域资源位置;根据预设截取比特的方式确定物理下行链路共享信道的可用频域资源位置;根据缩放因子确定物理下行链路共享信道的可用频域资源位置。
本申请实施例还提供一种通信设备,包括:存储器、处理器及存储在所述存储器上并可在所述处理器上运行的资源处理程序,所述资源处理程序被所述处理器执行时实现如上述任一实施例中所述的资源处理方法。本申请中提及的通信设备,可以是终端设备(如智能终端,具体如手机),也可以是网络设备(如基站),具体所指,需要结合上下文加以明确。
本申请实施例还提供一种存储介质,所述存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现如上述任一实施例中所述的资源处理方法。
在本申请实施例提供的通信设备和存储介质的实施例中,可以包含任一上述资源处理方法实施例的全部技术特征,说明书拓展和解释内容与上述方法的各实施例基本相同,在此不再做赘述。
本申请实施例还提供一种计算机程序产品,计算机程序产品包括计算机程序代码,当计算机程序代码在计算机上运行时,使得计算机执行如上各种可能的实施方式中的方法。
本申请实施例还提供一种芯片,包括存储器和处理器,存储器用于存储计算机程序,处理器用于从存储器中调用并运行计算机程序,使得安装有芯片的设备执行如上各种可能的实施方式中的方法。
可以理解,上述场景仅是作为示例,并不构成对于本申请实施例提供的技术方案的应用场景的限定,本申请的技术方案还可应用于其他场景。例如,本领域普通技术人员可知,随着系统架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
上述本申请实施例序号仅仅为了描述,不代表实施例的优劣。
本申请实施例方法中的步骤可以根据实际需要进行顺序调整、合并和删减。
本申请实施例设备中的单元可以根据实际需要进行合并、划分和删减。
在本申请中,对于相同或相似的术语概念、技术方案和/或应用场景描述,一般只在第一次出现时进行详细描述,后面再重复出现时,为了简洁,一般未再重复阐述,在理解本申请技术方案等内容时,对于在后未详细描述的相同或相似的术语概念、技术方案和/或应用场景描述等,可以参考其之前的相关详细描述。
在本申请中,对各个实施例的描述都各有侧重,某个实施例中没有详述或记载的部分,可以参见其它实施例的相关描述。
本申请技术方案的各技术特征可以进行任意的组合,为使描述简洁,未对上述实施例中的各个技术特征所有可能的组合都进行描述,然而,只要这些技术特征的组合不存在矛盾,都应当认为是本申请记载的范围。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在如上的一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,被控终端,或者网络设备等)执行本申请每个实施例的方法。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时,全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络,或者其他可编程装置。计算机指令可以存储在存储介质中,或者从一个存储介质向另一个存储介质传输,例如,计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质,(例如,软盘、存储盘、磁带)、光介质(例如,DVD),或者半导体介质(例如固态存储盘Solid State Disk(SSD))等。
以上仅为本申请的优选实施例,并非因此限制本申请的专利范围,凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换,或直接或间接运用在其他相关的技术领域,均同理包括在本申请的专利保护范围内。
Claims (15)
- 一种资源处理方法,其中,所述方法包括步骤:S20,接收下行信息,根据第一策略确定物理下行链路共享信道的可用频域资源位置。
- 如权利要求1所述的方法,其中,所述下行信息包括以下至少一项:传输次数;满足第一预设规则的频域资源分配字段。
- 如权利要求2所述的方法,其中,所述传输次数包括以下至少一项:所述传输次数由下行链路控制信息配置;所述传输次数与控制资源集的配置周期有关;所述传输次数的最大取值与频域资源分组组数有关。
- 如权利要求3所述的方法,其中,所述频域资源分组组数由激活带宽部分大小和预设带宽确定。
- 如权利要求4所述的方法,其中,所述满足第一预设规则包括:所述频域资源分配字段包括资源块集和第一频域资源分配。
- 如权利要求5所述的方法,其中,还包括以下至少一项:所述资源块集的大小与子载波间隔有关;所述资源块集大小与所述预设带宽有关;所述资源块集的比特数目与激活带宽中资源块集数目有关;所述资源块集的比特数目与激活带宽中资源块集表示方式有关;所述第一频域资源分配的比特数目与频域资源分配类型有关;所述资源块集所占的频域资源位置由与激活带宽部分频域位置有关的第二预设公式确定。
- 如权利要求1至6中任一项所述的方法,其中,所述第一策略包括以下至少一项:根据与传输次数相关的第一预设公式确定物理下行链路共享信道的可用频域资源位置;根据所述资源块集和满足第一预设规则的频域资源分配字段中的第一频域资源分配取交集确定物理下行链路共享信道的可用频域资源位置;根据预设截取比特的方式确定物理下行链路共享信道的可用频域资源位置;根据缩放因子确定物理下行链路共享信道的可用频域资源位置。
- 如权利要求7所述的方法,其中,所述缩放因子与激活带宽大小及所述预设带宽有关。
- 一种资源处理方法,其中,所述方法包括步骤:S10,发送下行信息,以使终端根据第一策略确定物理下行链路共享信道的可用频域资源位置。
- 如权利要求9所述的方法,其中,所述步骤S10包括以下至少一项:根据无线资源连接状态发送下行信息;根据终端类型获取状态发送下行信息。
- 如权利要求10所述的方法,其中,所述下行信息包括以下至少一项:传输次数;满足第一预设规则的频域资源分配字段;下行链路控制信息;无线资源控制信息;系统信息。
- 如权利要求11所述的方法,其中,包括以下至少一项:所述传输次数由下行链路控制信息配置;所述传输次数与控制资源集的配置周期有关;所述传输次数的最大取值与频域资源分组组数有关;所述满足第一预设规则包括:所述频域资源分配字段包括资源块集和第一频域资源分配。
- 如权利要求9至12中任一项所述的方法,其中,所述第一策略包括以下至少一项:根据与传输次数相关的第一预设公式确定物理下行链路共享信道的可用频域资源位置;根据频域资源分配字段中的资源块集和第一频域资源分配取交集确定物理下行链路共享信道的可用频域资源位置;根据预设截取比特的方式确定物理下行链路共享信道的可用频域资源位置;根据缩放因子确定物理下行链路共享信道的可用频域资源位置。
- 一种通信设备,其中,所述通信设备包括:存储器、处理器及存储在所述存储器上并可在所述处理器上运行的资源处理程序,所述资源处理程序被所述处理器执行时实现如权利要求1或9所述的资源处理方法的步骤。
- 一种存储介质,其中,所述存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现如权利要求1或9所述的资源处理方法的步骤。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/131528 WO2024098417A1 (zh) | 2022-11-11 | 2022-11-11 | 资源处理方法、通信设备及存储介质 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/131528 WO2024098417A1 (zh) | 2022-11-11 | 2022-11-11 | 资源处理方法、通信设备及存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024098417A1 true WO2024098417A1 (zh) | 2024-05-16 |
Family
ID=91031798
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/131528 WO2024098417A1 (zh) | 2022-11-11 | 2022-11-11 | 资源处理方法、通信设备及存储介质 |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2024098417A1 (zh) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111565461A (zh) * | 2019-02-14 | 2020-08-21 | 夏普株式会社 | 由用户设备执行的方法以及用户设备 |
CN112583558A (zh) * | 2019-09-30 | 2021-03-30 | 维沃移动通信有限公司 | 资源配置方法、终端设备及网络设备 |
WO2021159514A1 (zh) * | 2020-02-14 | 2021-08-19 | Oppo广东移动通信有限公司 | 资源分配方法、装置及可读存储介质 |
JP2022003773A (ja) * | 2018-03-27 | 2022-01-11 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | 周波数領域リソース配分のシグナリング |
CN114071766A (zh) * | 2020-08-05 | 2022-02-18 | 维沃移动通信有限公司 | 资源调度方法、装置及设备 |
-
2022
- 2022-11-11 WO PCT/CN2022/131528 patent/WO2024098417A1/zh unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2022003773A (ja) * | 2018-03-27 | 2022-01-11 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | 周波数領域リソース配分のシグナリング |
CN111565461A (zh) * | 2019-02-14 | 2020-08-21 | 夏普株式会社 | 由用户设备执行的方法以及用户设备 |
CN112583558A (zh) * | 2019-09-30 | 2021-03-30 | 维沃移动通信有限公司 | 资源配置方法、终端设备及网络设备 |
WO2021159514A1 (zh) * | 2020-02-14 | 2021-08-19 | Oppo广东移动通信有限公司 | 资源分配方法、装置及可读存储介质 |
CN114071766A (zh) * | 2020-08-05 | 2022-02-18 | 维沃移动通信有限公司 | 资源调度方法、装置及设备 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210168834A1 (en) | Determining method, terminal, and network device | |
US20220141690A1 (en) | Transmission method and communication device | |
WO2021093754A1 (zh) | 上行资源确定方法、指示方法、终端和网络设备 | |
WO2020192547A1 (zh) | 信息传输、接收方法、终端及网络侧设备 | |
WO2021088799A1 (zh) | 资源分配方法、装置、用户设备、网络设备及介质 | |
US20210314999A1 (en) | Method for Configured Grant Configuration, Terminal, and Network-Side Device | |
EP4395409A1 (en) | Control method, communication device, and storage medium | |
CN111615197B (zh) | 资源调整方法及设备 | |
CN109445945B (zh) | 应用程序的内存分配方法、移动终端、服务器及存储介质 | |
CN111970738B (zh) | 一种网络切换控制方法、设备及计算机可读存储介质 | |
WO2021057896A1 (zh) | 上行传输方法及终端 | |
WO2023221831A1 (zh) | 处理方法、通信设备及存储介质 | |
CN111836311B (zh) | 能力协商方法、终端及网络设备 | |
WO2017193268A1 (zh) | 上行数据传输方法、终端设备和网络设备 | |
WO2024098417A1 (zh) | 资源处理方法、通信设备及存储介质 | |
CN113556217B (zh) | 通信方法、网络设备、终端设备及存储介质 | |
CN110087290B (zh) | 功耗管控方法、终端以及计算机可读存储介质 | |
CN116582232B (zh) | 监听方法、通信设备及存储介质 | |
WO2024050835A1 (zh) | 处理方法、通信设备及存储介质 | |
WO2024050834A1 (zh) | 处理方法、通信设备及存储介质 | |
WO2023133693A1 (zh) | 通信方法、通信设备以及存储介质 | |
WO2024065318A1 (zh) | 处理方法、通信设备及存储介质 | |
WO2023216036A1 (zh) | 处理方法、通信设备及存储介质 | |
WO2024145923A1 (zh) | 控制方法、通信设备及存储介质 | |
WO2023230874A1 (zh) | 处理方法、通信设备及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22964885 Country of ref document: EP Kind code of ref document: A1 |