WO2021031089A1 - Resource configuration method, terminal device and network device - Google Patents

Abstract

Embodiments of the present application relate to a resource configuration method, a terminal device and a network device. The method comprises: a terminal device sends configuration grant (CG) request information to a network device, the CG request information being used for requesting the network device for configuring a CG configuration that is used for sending uplink data and/or buffer status report (BSR) for the terminal device; the terminal device receives configuration information from the network device, the configuration information comprising a first CG configuration configured by the network device. The resource configuration method, the terminal device and the network device in the embodiments of the present application can improve the flexibility of the system.

Description

Resource configuration method, terminal equipment and network equipment Technical field

This application relates to the field of communications, in particular to a method for resource configuration, terminal equipment and network equipment.

Background technique

Currently, the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) is studying non-terrestrial communication network (Non-Terrestrial Network, NTN) technology. NTN generally uses satellite communication to provide communication services to ground users.

The New Radio (NR) system has higher requirements for flexibility. However, in the current NTN system, the flexibility of network equipment for resource configuration for terminal equipment is low. Therefore, how to improve the flexibility of network device configuration resources in NTN is an urgent problem to be solved.

Summary of the invention

The embodiments of the present application provide a resource configuration method, terminal device, and network device, which can improve the flexibility of network device configuration resources.

In a first aspect, a method for resource configuration is provided. The method includes: a terminal device sends configuration authorization CG request information to a network device, where the CG request information is used to request the network device to configure the terminal device for Send uplink data and/or buffer status report BSR CG configuration;

The terminal device receives configuration information sent by the network device, where the configuration information includes the first CG configuration configured by the network device.

In a second aspect, a method for resource configuration is provided, the method includes: a network device receives configuration authorization CG request information sent by a terminal device, the CG request information is used to request the network device to configure the terminal device CG configuration for sending uplink data and/or buffer status report BSR;

The network device sends configuration information to the terminal device, where the configuration information includes the first CG configuration configured by the network device.

In a third aspect, a terminal device is provided, which is used to execute the method in the foregoing first aspect or each of its implementation manners.

Specifically, the terminal device includes a functional module for executing the method in the foregoing first aspect or each implementation manner thereof.

In a fourth aspect, a network device is provided, which is configured to execute the method in the second aspect or its implementation manners.

Specifically, the network device includes a functional module for executing the method in the foregoing second aspect or each implementation manner thereof.

In a fifth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation modes.

In a sixth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned second aspect or each of its implementation modes.

In a seventh aspect, a device is provided for implementing any one of the first aspect to the second aspect or the method in each implementation manner thereof.

Specifically, the device includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the device executes any one of the above-mentioned first aspect to the second aspect or any of its implementation modes method.

Optionally, the device is a chip.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that enables a computer to execute any one of the first aspect to the second aspect or the method in each implementation manner thereof.

In a ninth aspect, a computer program product is provided, including computer program instructions, which cause a computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.

In a tenth aspect, a computer program is provided, which when running on a computer, causes the computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.

In the above technical solution, the terminal device sends the CG request information for requesting the network device to configure the CG configuration to the network device, which can avoid the problem that the terminal device needs to configure the CG but the network device has no configuration, so that the network device can flexibly configure the CG configuration for the terminal device , Which can improve the flexibility of the system.

Description of the drawings

Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application.

Figure 2 is a schematic flowchart of a terminal device requesting uplink scheduling.

Fig. 3 is a schematic flowchart of a method for resource configuration according to an embodiment of the present application.

Fig. 4 is a schematic flowchart of specific implementation of a method for resource configuration according to an embodiment of the present application.

Fig. 5 is a schematic flow chart of specific implementation of a method for resource configuration according to an embodiment of the present application.

Fig. 6 is a schematic flowchart of specific implementation of a method for resource configuration according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 9 is a schematic block diagram of a communication device according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of a chip according to an embodiment of the present application.

Fig. 11 is a schematic block diagram of a communication system according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, and Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE ( LTE-based access to unlicensed spectrum, LTE-U system, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, Universal Mobile Telecommunication System (UMTS), global interconnection Microwave access (Worldwide Interoperability for Microwave Access, WiMAX) communication systems, wireless local area networks (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, WiFi), next-generation communication systems or other communication systems, etc.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or called a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.

The communication system 100 also includes at least one terminal device 120 located within the coverage area of the network device 110. The "terminal equipment" used here includes but is not limited to connection via wired lines, such as via public switched telephone networks (PSTN), digital subscriber lines (Digital Subscriber Line, DSL), digital cables, and direct cable connections ; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and/or another terminal device that is set to receive/send communication signals; and/or Internet of Things (IoT) equipment. A terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal" or a "mobile terminal". Examples of mobile terminals include, but are not limited to, satellites or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio phone transceivers Electronic device. Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of PLMN, etc.

Optionally, direct terminal connection (Device to Device, D2D) communication may be performed between the terminal devices 120.

Optionally, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

Figure 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.

Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.

It should be understood that the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the application.

It should also be understood that the communication system 100 shown in FIG. 1 may also be an NTN system, that is, the network device 110 in FIG. 1 may be a satellite.

It should be understood that the terms "system" and "network" in this article are often used interchangeably in this article.

Based on the current NR standard, when the terminal device has uplink data arriving, but the terminal device does not have uplink resources for data transmission, as shown in Figure 2, the terminal device needs to go through 5 steps to send these uplink data to the network device.

210: The terminal device sends a scheduling request (Scheduling Request, SR) to the network device to request uplink resources from the network device.

220: The network device receives the SR and knows that the terminal device needs uplink resources for transmitting uplink data, but the network device does not know how much uplink data the terminal device needs to send. Therefore, the network device can allocate enough physical uplink shared channel (PUSCH) resources for the terminal device to send a buffer status report (Buffer Status Report, BSR) to the terminal device.

230: The terminal device sends the BSR on the PUSCH resource allocated by the network device, thereby notifying the network device of the amount of data that the terminal device needs to send.

Among them, the BSR can be carried by the BSR Medium Access Control (MAC) control element (CE).

240: The network device allocates appropriate PUSCH resources for uplink data transmission to the terminal device according to the BSR information reported by the terminal device.

250: The terminal device transmits uplink data on the PUSCH resource allocated by the network device.

It can be seen from Figure 2 that the terminal device enables the network device to learn the amount of uplink buffered data of the terminal device through the BSR, so that the network device can schedule the terminal device according to the data volume information provided by the terminal device.

In order to save the BSR reporting overhead, the terminal device can adopt a packet reporting method when reporting the BSR. Each uplink logical channel can correspond to a logical channel group (Logical Channel Group, LCG), multiple uplink logical channels can correspond to the same LCG, and the correspondence between logical channels and LCGs can be controlled by network equipment through radio resources (Radio Resource Control, RRC) signaling configuration. The terminal equipment reports the BSR based on the LCG. Each terminal device in NR can support up to 8 LCGs.

The triggering conditions of BSR are as follows:

1. A logical channel with a higher priority of the terminal device has uplink data arrival. In this case, a regular (Regular) BSR can be triggered.

2. The padding part of the uplink resource allocated to the terminal device after carrying other uplink data can carry the BSR MAC CE. In this case, the padding BSR can be triggered.

3. The retransmission BSR timer (retxBSR-Timer) has timed out, and there is currently at least one uplink logical channel with uplink data to be sent. At this time, the Regular BSR can be triggered.

4. The periodic BSR timer (periodicBSR-Timer) expires, and the periodic (Periodic) BSR can be triggered at this time.

If multiple logical channels trigger the Regular BSR at the same time, each of these logical channels can trigger a separate Regular BSR.

If a terminal device triggers a Regular BSR, but the terminal device does not have uplink resources for transmitting new data or the uplink resources allocated to the terminal device for transmitting new data cannot carry the data of the uplink logical channel that triggers the Regular BSR, then The terminal triggers SR.

It can also be seen from Figure 2 that the terminal device applies for uplink resources from the network device through the SR. However, the network device does not know when the terminal device needs to send uplink data, that is, it does not know when the terminal device will send the SR. Therefore, the network device can allocate periodic physical uplink control channel (PUCCH) resources for transmitting the SR to the terminal device, and then the network device can detect whether there is an SR report on the allocated SR resources.

It can be seen from the above-mentioned SR trigger condition that the SR in NR is based on logical channels. For each uplink logical channel, the network device can choose whether to configure the PUCCH resource for transmitting SR for the uplink logical channel.

In the case that an uplink logical channel triggers SR, if the network device configures the uplink logical channel with PUCCH resources for transmitting SR, the terminal device can send the SR on the PUCCH resource for transmitting SR corresponding to the logical channel . Otherwise, the terminal device can initiate random access.

In NR, the signal transmission delay between terminal equipment and network equipment is relatively small. The waiting time from when the terminal equipment has uplink data to when the terminal equipment sends these data to the network equipment is generally short, which has an impact on service delay. Not big.

Compared with the cellular network adopted by traditional NR, the signal propagation delay between the terminal equipment and the satellite in NTN has increased significantly. Therefore, when the terminal device has uplink data arriving, but the terminal device does not have uplink resources for data transmission, the terminal device needs to wait a relatively long time before sending these data to the network device, which results in a significant increase in service delay. Affect user experience.

In order to alleviate the problem of uplink service delay, NR introduced the concept of uplink unlicensed transmission. The terminal device can transmit on the resources of the Configured Grant (CG) according to business requirements.

Currently, NR supports the following two types of uplink unauthorized transmission:

1. PUSCH transmission based on the first type of configuration authorization (Configured Grant Type 1)

The network equipment configures through RRC signaling including time domain resources, frequency domain resources, time domain resource cycle, modulation and coding scheme (Modulation and Coding Scheme, MCS), number of repetitions, frequency hopping, hybrid automatic repeat request (Hybrid Automatic Repeat Request, HARQ) All transmission resources and transmission parameters including the number of processes. After receiving the RRC configuration, the terminal device can immediately use the configured transmission parameters to perform PUSCH transmission on the configured time-frequency resources.

2. PUSCH transmission based on the second type of configuration authorization (Configured Grant Type 2)

Type 2 adopts a two-step resource configuration method: First, the network device configures the transmission resources and transmission parameters including the period of time domain resources, the number of repetitions, the frequency hopping, the number of HARQ processes, etc. through RRC; then the cell scheduled by the configuration is used Radio Network Temporary Identifier (Configured Scheduling Radio Network Temporary Identifier, CS-RNTI) scrambled Physical Downlink Control Channel (PDCCH) activates the second type of PUSCH transmission based on configuration authorization, and is configured to include time domain resources at the same time Frequency domain resources, other transmission resources and transmission parameters such as MCS. When receiving the RRC configuration parameters, the terminal device cannot immediately use the resources and parameters configured by the configuration parameters for PUSCH transmission, but must wait for the corresponding PDCCH activation and configuration of other resources and parameters before PUSCH transmission.

If the terminal device has no data to send on the PUSCH resource of the first or second type of CG, the terminal device will not send any content on the resource of the CG.

However, the CG configuration configured by the network equipment does not necessarily match the UE's requirements well. For example, if the terminal device needs to be configured with a CG configuration but the network device is not configured, it will cause excessive uplink service delay. For another example, if the network device configures the terminal device with a CG, but the CG resource is too small, it will increase the delay; or if the CG resource is too large, it will cause a waste of system resources.

In view of this, the embodiment of the present application proposes a resource configuration method, which can improve the flexibility of the network device to configure the CG for the terminal device.

It should be understood that, in the embodiments of the present application, the terms "CG" and "CG configuration" are often used interchangeably herein.

FIG. 3 is a schematic flowchart of a method 300 for resource configuration according to an embodiment of the present application. The method described in FIG. 3 may be executed by a terminal device and a network device. The terminal device may be, for example, the terminal device 120 shown in FIG. 1, and the network device may be, for example, the network device 110 shown in FIG. 1.

It should be understood that the method 300 can be applied to NTN. In order to deepen the understanding of NTN, NTN will be introduced below.

NTN technology generally uses satellite communication to provide communication services to ground users. Compared with terrestrial cellular network communication, satellite communication has many unique advantages. First of all, satellite communication is not restricted by the user area. For example, ordinary terrestrial communication cannot cover areas such as oceans, mountains, deserts, etc. As communication equipment cannot be installed or communication coverage is not available due to sparse population, normal communication cannot be carried out in these areas. As for satellite communications, since a satellite can cover a larger ground and the satellite can orbit the earth, theoretically every corner of the earth can be covered by satellite communications. Secondly, satellite communication has greater social value. Satellite communication can be covered at a lower cost in remote mountainous areas, poor and backward countries or regions, so that people in these areas can enjoy advanced voice communication and mobile Internet technology, which is conducive to narrowing the digital gap with developed areas and promoting The development of these areas. Third, the satellite communication distance is long, and the communication distance increases and the cost of communication does not increase significantly. Finally, the stability of satellite communication is high, and it is not restricted by natural disasters.

According to different orbital heights, communication satellites can be divided into Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites, and high High Elliptical Orbit (HEO) satellites, etc. At the current stage, the main research is LEO satellite and GEO satellite. The following is an explanation of LEO satellite and GEO satellite.

The altitude range of LEO satellites is 500km-1500km, and the corresponding orbital period is about 1.5 hours to 2 hours. The signal propagation delay of single-hop communication between users is generally less than 20ms. The maximum satellite viewing time is 20 minutes. The signal propagation distance is short, the link loss is small, and the requirement for the transmission power of the user terminal is not high.

The orbital height of the GEO satellite is 35786km, and the rotation period around the earth is 24 hours. The signal propagation delay of single-hop communication between users is generally 250ms.

In order to ensure satellite coverage and increase the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. A satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover tens to hundreds of kilometers in diameter. Ground area.

Of course, the method 300 can also be used in other communication scenarios, such as terrestrial cellular network communication, Internet of Vehicles communication, and so on.

As shown in FIG. 3, the method 300 may include at least part of the following content.

310. The terminal device sends CG request information to the network device, where the CG request information is used to request the network device to configure the terminal device with a CG configuration for sending uplink data and/or BSR.

320. The network device receives the CG request information sent by the terminal device.

330. The terminal device receives configuration information sent by the network device, where the configuration information includes the first CG configuration configured by the network device.

Wherein, the CG configuration may include but is not limited to at least one of the following: time domain resources, frequency domain resources, period of time domain resources, number of repetitions, MCS, HARQ process and other parameters.

Optionally, when the terminal device has a service to be transmitted at the current moment or in the first time period after the current moment, the terminal device may send the CG request information to the network device.

In this way, when uplink data arrives, the terminal device can report the BSR and/or send the uplink data to the network device more quickly, thereby reducing the delay of the service to be transmitted.

Among them, the service to be transmitted may be a delay-sensitive service, such as an ultra-reliable low-latency communication (URLLC) service and a time-sensitive network (Time Sensitive Network, TSN) service. Alternatively, the service to be transmitted may also be an Enhanced Mobile Broadband (eMBB) service, a vertical industry service, a Voice over Long-Term Evolution (VoLTE) service, an Internet of Vehicles service, etc.

It should be understood that the term "and/or" in this article is only an association relationship describing the associated objects, indicating that there can be three types of relationships, for example, A and/or B can mean: A alone exists, and both A and B exist. , There are three cases of B alone.

Hereinafter, the technical solutions of the embodiments of the present application will be described in detail with reference to three embodiments.

Example 1

The terminal device can send CG request information to the network device during the random access process to assist the network device in configuring the CG configuration.

Specifically, the CG request information may be carried in message 1 or message 3 in the random access process. Message 1 may be message 1 (Msg1) in the four-step random access process, that is, the random access preamble; or, message 1 may be message A (Msg A) in the two-step random access process.

Optionally, the CG request information may also include the CG resource period and/or the CG resource size that the terminal device expects the network device to configure.

The terminal device reports the expected CG resource period and/or the size of the CG resource to the network device. In this way, the problem of too large or too small CG resources configured by the network device can be avoided, so that the CG configuration configured by the network device can better match the terminal Equipment requirements. At the same time, system resources can be used more efficiently.

The method 300 may further include: the terminal device determines the CG resource period that the network device is expected to configure according to the arrival period of the service to be transmitted and/or the delay requirement of the service to be transmitted.

For example, if the arrival period of the service to be transmitted is 10 ms, the terminal device expects the CG resource period configured by the network device to be 10 ms.

For another example, if the delay requirement of the service to be transmitted is 5 ms, the terminal device expects the CG resource period configured by the network device to be 5 ms.

The method 300 may further include: the terminal device determines the size of the CG resource expected to be configured by the network device according to the service volume of the service to be transmitted.

Wherein, the service volume of the service to be transmitted may be the historical service volume of the service to be transmitted. Exemplarily, the historical service volume may be a historical average service volume within a period of time. For example, the service volume of the service to be transmitted may be the historical average service volume of the service to be transmitted in the most recent month. Illustratively again, the historical traffic volume may be the average value of the highest traffic volume and the lowest traffic volume in a period of time.

Or, the service volume of the service to be transmitted may be the service volume of the service to be transmitted estimated by the terminal device.

If the fluctuation range of the service volume of the service to be transmitted is greater than the preset range, that is, the service volume of the service to be transmitted fluctuates greatly, the terminal device expects that the CG resource size configured by the network device can be the resource size required for the terminal device to report the BSR. In this way, system resources can be saved.

For example, if the difference between the business volume of the business to be transmitted in the first month and the business volume in the second month is greater than the preset range, it can be considered that the business volume of the business to be transmitted fluctuates greatly, and the terminal equipment can report to the BSR The required resource size to request CG resources.

If the fluctuation range of the service volume of the service to be transmitted is less than or equal to the preset range, that is, the service volume of the service to be transmitted is relatively fixed, the terminal device expects the size of the CG resource configured by the network device to be the service volume of the service to be transmitted.

Optionally, the preset amplitude may be preset on the terminal device based on a protocol, or pre-configured to the terminal device by the network device, for example, it may be configured through RRC signaling.

When the CG request information is carried in the preamble in the four-step random access process, in a possible embodiment, the preamble can be divided into two groups, and one group of the preamble can be used to indicate that the terminal device does not have a requirement for CG configuration configuration . The other group of Preamble can be used to indicate that the terminal device has a requirement to configure CG configuration. When sending the message 1, the terminal device sends the preamble in one of the preambles to the network device to inform the network device whether the terminal device wants the network device to configure the CG configuration for it.

In another possible embodiment, the preamble can be divided into N groups, where N is greater than 2. One group of preambles in the N group of preambles can be used to indicate that the terminal device does not have a requirement for CG configuration, and the other N-1 groups of preambles in the N group of preambles can be used to indicate the CG resource period and/or CG that the terminal device expects the network device to configure Resource size. Specifically, the terminal device and the network device may negotiate in advance the CG resource period and/or CG resource size expected by the terminal device indicated by each group of preambles in the other N-1 groups of preambles in the N group of preambles.

For example, the preamble is divided into 5 groups, namely the first group of preamble, the second group of preamble, the third group of preamble, the fourth group of preamble, and the fifth group of preamble. The terminal device and the network device negotiate in advance. The first group of Preamble is used to indicate that the terminal device does not have a requirement for CG configuration. The second group of Preamble is used to indicate that the terminal device expects a CG resource size of X. The third group of Preamble is used to indicate the terminal device. The expected CG resource size is Y, the fourth group is used to indicate the CG resource size expected by the terminal device is Z, and the fifth group Preamble is used to indicate the CG resource size expected by the terminal device is W. The terminal device sends the second set of Preambles to the network device. After receiving the second set of Preambles, the network device can determine that the terminal device has a requirement for configuring CG configuration, and the expected CG resource size is X.

For the network device, after receiving the CG request information, the network device can determine whether to configure the CG configuration for the terminal device according to the CG request information. If the network device determines to configure the CG configuration for the terminal device, the network device may configure the first CG configuration according to the CG request information. After that, the network device may send configuration information to the terminal device, and the configuration information includes the first CG configuration.

Optionally, the first CG configuration may be carried in the message 4 (Msg4) in the four-step random access process, or in the message B (MsgB) in the two-step random access process.

As an example, the network device may determine the first CG configuration according to the CG resource period and the CG resource size expected by the terminal device.

Network equipment needs to ensure a fair distribution of system resources. If there are too many terminal devices in the system, too many resources cannot be allocated to a certain terminal device. Therefore, the network device can further determine whether to configure the CG configuration for the terminal device based on factors such as the occupation of system resources, the fairness between terminal devices, and the priority of the service to be transmitted. For example, if the priority of the service to be transmitted by other terminal devices in the system is higher than the priority of the service to be transmitted by the terminal device, and the system resources are insufficient to allocate CG resources to the two terminal devices, the network device may not provide the terminal Device configuration CG configuration.

If the network device determines to configure the CG configuration for the terminal device, the network device can determine the first CG according to factors such as the CG configuration request of the terminal device, the occupancy of system resources, the fairness between terminal devices, the priority of the service to be transmitted, etc. Configuration.

For example, if a larger part of the system resources is already occupied, the size of the CG resource in the first CG configuration may be smaller than the size of the CG resource expected by the terminal device.

For another example, if a larger part of the system resources is not occupied, the CG resource size in the first CG configuration may be equal to the CG resource size expected by the terminal device.

If the resource size in the first CG configuration is the resource size required for the terminal device to report the BSR, when the terminal device has uplink data arriving and the BSR is triggered, the terminal device can send the BSR to the network device on the CG resource configured by the network device. After receiving the BSR reported by the terminal device, the network device can allocate appropriate resources to the terminal device according to the amount of data to be transmitted by the terminal device, and use dynamic scheduling signaling, such as the Cell-Radio Network Temporary Identifier (Cell-Radio Network Temporary Identifier, C -RNTI) The scrambled PDCCH indicates the terminal equipment to complete PUSCH transmission.

It can be seen that the terminal device will not report the SR to the network device.

If the resource size in the first CG configuration is the resource size for the terminal device to send uplink data, when the terminal device has uplink data arriving, the terminal device may send the uplink data according to the first CG configuration.

Optionally, the terminal device may send the BSR and/or uplink data on the CG resource closest to the current moment.

The technical solution of Embodiment 1 will be exemplified below with reference to FIG. 4.

Step 1: The terminal device sends the Msg1 of the random access process to the network device.

Step 2: In response to Msg1, the network device sends Msg2, that is, a random access response (Random Access Response, RAR) to the terminal device.

Step 3: Since the terminal device currently has delay-sensitive services, but the business volume fluctuates greatly, the terminal device carries the CG request information in the Msg3 (RRC connection establishment request message), indicating that the terminal device has a requirement to configure CG, and Msg3 It also carries the CG resource period and CG resource size expected by the terminal device.

Step 4: The network device determines to configure the CG for the terminal device according to the CG request information sent by the terminal device. In addition, the resource period of the first CG configuration configured by the network device is the CG resource period expected by the terminal device, and the resource size is determined according to the BSR, MAC, and CE size.

In addition, the network device sends configuration information including the first CG configuration to the terminal device, and the configuration information is carried in the random access Msg4 (RRC connection establishment message).

Step 5: When the terminal device has uplink data arrival and the BSR is triggered, the terminal device sends the BSR on the CG resource closest to the current moment.

Step 6: After receiving the BSR sent by the terminal device, the network device allocates appropriate PUSCH resources to the terminal device according to the data volume information provided by the terminal device, and instructs the terminal device to uplink scheduling information through the PDCCH scrambled by the C-RNTI.

Step 7: The terminal device completes uplink data transmission on the PUSCH resource allocated by the network device.

It should be understood that in the above 7 steps, steps 1 to 4 are random access procedures, and steps 5 to 7 are uplink scheduling procedures.

Example 2

The terminal device in the connected state can send CG request information to the network device through RRC signaling or MAC CE to assist the network device in configuring the CG configuration.

When the following conditions are met, the terminal device can send CG request information to the network device:

(1) The terminal equipment will have services to be transmitted at the current time or predicted in the future;

(2) The network device does not configure the CG configuration for the terminal device at the current moment;

(3) The terminal device has not sent CG request information to the network device, or the time interval between the current time and the time when the terminal device last sent the CG request information is greater than the preset time interval.

There are two situations in which the terminal device sends CG request information twice: the terminal device sends the CG request information and the network device receives the CG request information, or the terminal device sends the CG request information but the network device does not receive the CG Request information.

The preset time interval is the minimum time interval for the terminal device to send the CG request information twice.

Optionally, the preset time interval may be preset on the terminal device according to the protocol.

Optionally, the preset time interval may be pre-configured by the network device to the terminal device. Exemplarily, the network device may send second RRC configuration information to the terminal device. The second RRC configuration information may be used to configure a CG request prohibition timer (CGRequestProhibitTimer). The CG request prohibition timer is used to restrict the terminal device from sending CG requests twice The minimum time interval for information.

In this case, for the time interval between the current time in the above-mentioned condition (3) and the time when the terminal device last sent CG request information is greater than the preset time interval, it can be understood as: CG request prohibition timing The device has timed out. In other words, the CG request prohibition timer is used to limit the minimum time interval for the terminal device to send CG request information twice, which can be understood as: only when the CG request prohibition timer expires, the terminal device can send CG to the network device again Request information.

In the case that the network device is configured with the CG request prohibition timer, the terminal device may also maintain the CG request prohibition timer. Specifically, the terminal device may start or restart the CG request prohibition timer every time the CG request information is sent.

It should be understood that in the embodiments of the present application, “first” and “second” are only used to distinguish different objects, but do not limit the scope of the embodiments of the present application.

Optionally, the CG request information may also include the CG resource period and/or the CG resource size that the terminal device expects the network device to configure.

The terminal device may determine the CG resource period that the terminal device expects the network device to configure according to the arrival period of the service to be transmitted and/or the delay requirement of the service to be transmitted.

The terminal device can determine the size of the CG resource expected to be configured by the network device according to the service volume of the service to be transmitted.

For the network device, after receiving the CG request information, the network device can determine whether to configure the CG configuration for the terminal device according to the CG request information. If the network device determines to configure the CG configuration for the terminal device, the network device may configure the first CG configuration according to the CG request information. After that, the network device may send configuration information to the terminal device, and the configuration information includes the first CG configuration.

As an example, the network device may determine the first CG configuration according to the CG resource period and the CG resource size expected by the terminal device.

Further, the network device can determine whether to configure the CG configuration for the terminal device in combination with factors such as the occupation of system resources, the fairness between terminal devices, and the priority of the service to be transmitted.

If the network device determines to configure the CG configuration for the terminal device, the network device can determine the first CG according to factors such as the CG configuration request of the terminal device, the occupancy of system resources, the fairness between terminal devices, the priority of the service to be transmitted, etc. Configuration.

The technical solution of Embodiment 2 will be exemplified below with reference to FIG. 5.

Step 1: The network device sends second RRC configuration information to the terminal device. The second RRC configuration information is used to configure a CG request prohibition timer, and the second RRC configuration information does not include the CG configuration.

Step 2: The terminal equipment has a waiting transmission service to arrive, the service is sensitive to delay, and the service volume is fixed, that is, the data packet size is fixed. Therefore, the terminal device sends CG request information to the network device, and the CG request information also includes the CG resource period and CG resource size expected by the terminal device.

Among them, the terminal device determines the CG resource period expected by the terminal device according to the arrival period and service delay requirements of the service to be transmitted.

The terminal device determines the size of the CG resource expected by the terminal device according to the service volume to be transmitted.

In addition, while the terminal device sends the CG request information to the network device, the terminal device starts the CG request prohibition timer.

Step 3: The terminal device does not receive the CG configuration configured by the network device.

Step 4: When the terminal device has uplink data arriving, the terminal device has no uplink resources available for data transmission, and the terminal device sends an SR to the network device.

Step 5: The network device receives the SR and allocates resources for sending the BSR to the terminal device. After that, the network device instructs uplink scheduling through the PDCCH.

Step 6: The terminal device receives the scheduling signaling from the network device, and sends the BSR on the resource allocated by the network device.

Step 7: The network device receives the BSR, learns the uplink data volume information of the terminal device, and allocates PUSCH resources to the terminal device by means of dynamic scheduling, and indicates the resource allocation information to the terminal device.

Step 8: The terminal equipment transmits uplink data on the resource indicated by the dynamic scheduling signaling.

Step 9: After the CG request prohibition timer expires, the terminal device sends the CG request information to the network device again. At the same time, the terminal device starts the CG prohibit timer.

Step 10: The terminal device receives configuration information from the network device, and the configuration information includes the first CG configuration. Wherein, the CG resource period and the CG resource size configured by the first CG are respectively the CG resource period and the CG resource size requested by the terminal device.

Step 11: When the terminal device has uplink data arriving, the terminal device sends the uplink data on the CG resource closest to the current moment.

Example 3

In the case that the network device has configured the second CG configuration for the terminal device, the terminal device in the RRC connected state may send CG request information to the network device. The CG request information is used to request the network device to update the second CG configuration for the terminal device.

Optionally, the terminal device may send the CG request information to the network device through RRC signaling or MAC CE.

Optionally, before the terminal device sends the CG request information to the network device, the network device may send the first RRC configuration information to the terminal device, where the first RRC configuration information includes the second CG configuration.

Wherein, the second CG configuration may include, but is not limited to, at least one of the following: time domain resources, frequency domain resources, period of time domain resources, number of repetitions, MCS, HARQ process and other parameters.

In the embodiment of the present application, when the following conditions are met, the terminal device may send CG request information to the network device:

(1) The terminal equipment will have services to be transmitted at the current time or predicted in the future;

(2) The second CG configuration does not meet the transmission requirements of the service to be transmitted;

(3) The terminal device has not sent CG request information to the network device, or the time interval between the current time and the time when the terminal device last sent the CG request information is greater than the preset time interval.

Wherein, the second CG configuration does not meet the transmission requirements of the service to be transmitted, which may include but is not limited to at least one of the following situations:

Case 1: The size of the CG resource configured by the second CG cannot meet the transmission requirements of the service to be transmitted;

Case 2: The CG resource period configured by the second CG cannot meet the transmission requirements of the service to be transmitted;

Situation 3: Neither the size of the CG resource configured by the second CG nor the CG resource period can meet the transmission requirements of the service to be transmitted.

Optionally, the preset time interval may be preset on the terminal device according to the protocol.

Optionally, the preset time interval may be pre-configured by the network device to the terminal device. Exemplarily, the network device may send the second RRC configuration information to the terminal device, and the second RRC configuration information may be used to configure the CG request prohibition timer.

In this case, for the time interval between the current time in the above-mentioned condition (3) and the time when the terminal device last sent CG request information is greater than the preset time interval, it can be understood as: CG request prohibition timing The device has timed out.

It should be understood that the first RRC configuration information and the second RRC configuration information may be the same information, that is, the first RRC configuration information includes the second CG configuration, and may also be used to configure the CG request prohibition timer.

After receiving the CG request information, the network device can determine whether to update the second CG configuration for the terminal device according to the CG request information. If the network device determines to update the second CG configuration for the terminal device, the network device may determine the updated first CG configuration according to the CG request information.

Further, the network device can also determine whether to update the second CG configuration for the terminal device in combination with factors such as the occupation of system resources, the fairness between terminal devices, and the priority of the service to be transmitted. If the network device determines to update the second CG configuration for the terminal device, the network device can further determine the updated first CG configuration based on factors such as the occupation of system resources, the fairness between terminal devices, and the priority of the service to be transmitted .

Hereinafter, the method of Embodiment 3 will be exemplified in conjunction with FIG. 6.

Step 1: The network device sends first RRC configuration information to the terminal device, where the first RRC configuration information specifically includes:

a) The second CG configuration, where the CG resource size in the second CG configuration is determined according to the resource size required by the terminal device to report the BSR.

b) CG requests to disable the timer.

Step 2: The terminal equipment has a waiting transmission service to arrive, the service is sensitive to delay, and the service volume is fixed, that is, the data packet size is fixed. Therefore, the terminal device sends CG request information to the network device to request the network device to update the second CG configuration for the terminal device.

The CG request information also includes the size of the CG resource expected by the terminal device. The size of the CG resource expected by the terminal device is determined according to the size of the service volume of the service to be transmitted.

In addition, while the terminal device sends the CG request information to the network device, the terminal device starts the CG request prohibition timer.

Step 3: The terminal device does not receive the CG configuration configured by the network device.

Step 4: When the terminal device has uplink data arriving, the terminal device uses the CG resource in the second CG configuration to send the BSR to the network device.

Step 5: The network device receives the BSR, learns the uplink data volume information of the terminal device, and allocates PUSCH resources to the terminal device through dynamic scheduling according to the uplink data volume information provided by the terminal device, and indicates the resource allocation information to the terminal device.

Step 6: The terminal equipment transmits uplink data on the resources indicated by the dynamic scheduling signaling.

Step 7: When the CG request prohibition timer expires, the terminal device again sends CG request information to the network device to request the network device to update the second CG configuration for the terminal device. At the same time, the terminal device starts the CG prohibit timer.

Step 8: The terminal device receives configuration information from the network device, and the configuration information includes the first CG configuration. Wherein, the CG resource period and the CG resource size configured by the first CG are respectively the CG resource period and the CG resource size requested by the terminal device.

Step 9: When the terminal device has uplink data arriving, the terminal device sends the uplink data on the CG resource closest to the current moment.

In the technical solution of Embodiment 3, when the CG configuration configured by the network device for the terminal device cannot meet the transmission requirements of the service to be transmitted by the terminal device, the terminal device sends a request to update the CG configuration information to the network device, so that the updated network device CG configuration can better meet the business needs of terminal equipment. At the same time, system resources can be used more efficiently.

It should be understood that although Embodiment 1 to Embodiment 3 are described above separately, this does not mean that Embodiment 1 to Embodiment 3 are independent, and the description of each embodiment may refer to each other. For example, the related description in Embodiment 1 can be applied to Embodiment 2 and Embodiment 3. For the sake of brevity of content, the embodiment of the present application does not describe Embodiment 2 and Embodiment 3 too much.

In the embodiment of the application, the terminal device sends the CG request information for requesting the network device to configure the CG configuration to the network device, which can avoid the problem that the terminal device needs to configure the CG but the network device has no configuration, so that the network device can flexibly configure the CG for the terminal device Configuration, which can improve the flexibility of the system.

The preferred embodiments of the present application are described in detail above with reference to the accompanying drawings. However, the present application is not limited to the specific details in the above-mentioned embodiments. Within the scope of the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application. These simple variants all belong to the protection scope of this application.

For example, the specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, this application no longer discusses various possible combinations. Explain separately.

For another example, various different implementations of this application can also be combined arbitrarily, as long as they do not violate the idea of this application, they should also be regarded as the content disclosed in this application.

It should be understood that, in the various method embodiments of the present application, the size of the sequence number of the foregoing processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not be implemented in this application. The implementation process of the example constitutes any limitation.

The resource configuration method according to the embodiment of the present application is described in detail above. The communication device according to the embodiment of the present application will be described below in conjunction with FIG. 7 to FIG. 9. The technical features described in the method embodiment are applicable to the following device embodiments.

FIG. 7 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG. 7, the terminal device 400 includes:

The communication unit 410 is configured to send configuration authorization CG request information to a network device, where the CG request information is used to request the network device to configure the terminal device 400 with a CG configuration for sending uplink data and/or a buffer status report BSR.

The communication unit 410 is further configured to receive configuration information sent by the network device, where the configuration information includes the first CG configuration configured by the network device.

Optionally, in this embodiment of the present application, the communication unit 410 is specifically configured to: send to the network device when the terminal device 400 has a service to be transmitted at the current moment or in the first time period after the current moment The CG request information.

Optionally, in the embodiment of the present application, the CG request information further includes the CG resource period and/or the CG resource size that the terminal device 400 expects the network device to configure.

Optionally, in the embodiment of the present application, the terminal device 400 further includes a processing unit 420, configured to determine the delay requirement of the service to be transmitted according to the arrival period of the service to be transmitted and/or CG resource cycle.

Optionally, in this embodiment of the present application, the terminal device 400 further includes a processing unit 420, configured to determine the size of the CG resource according to the service volume of the service to be transmitted.

Optionally, in this embodiment of the application, if the fluctuation range of the service volume of the service to be transmitted is greater than a preset range, the CG resource size is the resource size required by the terminal device to report the BSR.

Optionally, in this embodiment of the application, if the fluctuation range of the service volume of the service to be transmitted is less than or equal to a preset range, the size of the CG resource is the service volume of the service to be transmitted.

Optionally, in this embodiment of the present application, the communication unit 410 is further configured to send the uplink data according to the first CG configuration when the uplink data arrives.

Optionally, in this embodiment of the present application, the communication unit 410 is specifically configured to send the CG request information to the network device in a random access process.

Optionally, in this embodiment of the present application, the CG request information is carried in message 1 or message 3 in the random access process

Optionally, in the embodiment of the present application, when the terminal device is in a connected state, the CG request information is carried in radio resource control RRC signaling or media access control control unit MAC CE.

Optionally, in this embodiment of the present application, the communication unit 410 is specifically configured to send the CG request information to the network device when the following conditions are met: the network device does not give the terminal device at the current moment 400 configuration CG configuration;

The communication unit 410 has not sent CG request information to the network device, or the time interval between the current moment and the time when the communication unit 410 last sent the CG request information is greater than a preset time interval, and the preset time The interval is the minimum time interval for the communication unit 410 to send CG request information twice.

Optionally, in the embodiment of the present application, in the case that the network device has configured the second CG configuration for the terminal device 400, the CG request information is used to request the network device to be the terminal device 400 Update the second CG configuration.

Optionally, in this embodiment of the application, the communication unit 410 is specifically configured to send the CG request information to the network device when the following conditions are met: the second CG configuration does not meet the requirements of the service to be transmitted Transmission requirements;

The communication unit 410 has not sent CG request information to the network device, or the time interval between the current moment and the time when the communication unit 410 last sent the CG request information is greater than a preset time interval, and the preset time The interval is the minimum time interval for the communication unit 410 to send the CG request information twice.

Optionally, in this embodiment of the present application, before the communication unit 410 sends the CG request information to the network device, the communication unit 410 is further configured to: receive the first RRC configuration information sent by the network device, The first RRC configuration information includes the second CG configuration.

Optionally, in this embodiment of the application, the communication unit 410 is further configured to: receive second RRC configuration information sent by the network device, where the second RRC configuration information is used to configure a CG request prohibition timer, so The CG request prohibition timer is used to limit the minimum time interval for the communication unit 410 to send the CG request information twice.

Optionally, in this embodiment of the present application, the terminal device 400 further includes a processing unit 420, configured to start or restart the CG request prohibition timer when the CG request information is sent.

Optionally, in this embodiment of the present application, the terminal device 400 is in a non-terrestrial communication network NTN.

It should be understood that the terminal device 400 may correspond to the terminal device in the method 300, and can implement the corresponding operations of the terminal device in the method 300. For brevity, details are not described herein again.

FIG. 8 shows a schematic block diagram of a network device 500 according to an embodiment of the present application. As shown in FIG. 8, the network device 500 includes:

The communication unit 510 is configured to receive configuration authorization CG request information sent by a terminal device, where the CG request information is used to request the network device 500 to configure the terminal device with a CG for sending uplink data and/or a buffer status report BSR Configuration

The communication unit 510 is further configured to send configuration information to the terminal device, where the configuration information includes the first CG configuration configured by the network device 500.

Optionally, in this embodiment of the present application, the network device 500 further includes: a processing unit 520, configured to determine whether to configure a CG configuration for the terminal device based on the CG request information.

Optionally, in the embodiment of the present application, the processing unit 520 is further configured to: if it is determined to configure a CG configuration for the terminal device, determine the first CG configuration based on the CG request.

Optionally, in the embodiment of the present application, the communication unit 510 is specifically configured to include: when the terminal device has a service to be transmitted at the current time or in the first time period after the current time, receiving the terminal device The sent CG request information.

Optionally, in the embodiment of the present application, the CG request information further includes the CG resource period and/or the CG resource size that the terminal device expects the network device to configure.

Optionally, in this embodiment of the application, if the fluctuation range of the service volume of the service to be transmitted of the terminal device is greater than a preset range, the CG resource size is the resource size required by the terminal device to report the BSR.

Optionally, in this embodiment of the application, if the fluctuation range of the service volume of the service to be transmitted of the terminal device is less than or equal to the preset range, the CG resource size is the service volume of the service to be transmitted .

Optionally, in the embodiment of the present application, the communication unit 510 is further configured to: when the uplink data arrives, receive the uplink data according to the first CG configuration.

Optionally, in this embodiment of the application, the CG request information is carried in message 1 or message 3 in the random access process

Optionally, in the embodiment of the present application, when the terminal device is in a connected state, the CG request information is carried in radio resource control RRC signaling or media access control control unit MAC CE.

Optionally, in this embodiment of the present application, the communication unit 510 is specifically configured to: receive the CG request information sent by the terminal device when the following conditions are met: the network device 500 does not give the Terminal equipment configuration CG configuration;

The communication unit 510 has not received the CG request information sent by the terminal device, or the time interval between the current time and the time when the communication unit 510 last received the CG request information is greater than a preset time interval, the preset The time interval is the minimum time interval for the communication unit 510 to receive CG request information twice.

Optionally, in the embodiment of the present application, in the case that the network device 500 has configured the second CG configuration for the terminal device, the CG request information is used to request the network device 500 to be the terminal device Update the second CG configuration.

Optionally, in the embodiment of the present application, the communication unit 510 is specifically configured to: receive the CG request information sent by the terminal device when the following conditions are met: the second CG configuration does not satisfy the terminal Transmission requirements of the equipment to be transmitted;

The communication unit 510 has not received the CG request information sent by the terminal device, or the time interval between the current moment and the time when the communication unit 510 last sent the CG request information is greater than a preset time interval, the preset The time interval is the minimum time interval for the communication unit 510 to receive CG request information twice.

Optionally, in this embodiment of the present application, before the communication unit 510 receives the CG request information, the communication unit 510 is further configured to: send first RRC configuration information to the terminal device, and the first RRC configuration information The RRC configuration information includes the second CG configuration.

Optionally, in the embodiment of the present application, the communication unit 510 is further configured to send second RRC configuration information to the terminal device, where the second RRC configuration information is used to configure a CG request prohibition timer, and the The CG request prohibition timer is used to limit the minimum time interval for the terminal device to send the CG request information twice.

It should be understood that the network device 500 may correspond to the network device in the method 300, and can implement the corresponding operations of the network device in the method 300. For brevity, details are not described herein again.

FIG. 9 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application. The communication device 600 shown in FIG. 9 includes a processor 610, and the processor 610 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 9, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

The memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.

Optionally, as shown in FIG. 9, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, details are not repeated here. .

Optionally, the communication device 600 may specifically be a terminal device of an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the terminal device in each method of the embodiment of the present application. For brevity, details are not repeated here. .

Fig. 10 is a schematic structural diagram of a device according to an embodiment of the present application. The apparatus 700 shown in FIG. 10 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 10, the apparatus 700 may further include a memory 720. Wherein, the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

The memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.

Optionally, the device 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

Optionally, the device 700 may further include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the device can be applied to the terminal device in the embodiment of the present application, and the device can implement the corresponding process implemented by the terminal device in the various methods of the embodiment of the present application. For brevity, details are not described herein again.

Optionally, the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application. For brevity, details are not described herein again.

Optionally, the device 800 may be a chip. It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip.

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.

FIG. 11 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. As shown in FIG. 11, the communication system 800 includes a terminal device 810 and a network device 820.

Wherein, the terminal device 810 can be used to implement the corresponding function implemented by the terminal device in the above method, and the network device 820 can be used to implement the corresponding function implemented by the network device in the above method. For brevity, it will not be repeated here. .

The embodiment of the present application also provides a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, here No longer.

The embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Repeat it again.

Optionally, the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, it is not here. Repeat it again.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the terminal device in the embodiment of the present application. When the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

Optionally, the computer program can be applied to the network device in the embodiment of the present application. When the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , I won’t repeat it here.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims (76)

A method for resource allocation, characterized in that the method includes: The terminal device sends configuration authorization CG request information to the network device, where the CG request information is used to request the network device to configure the terminal device with a CG configuration for sending uplink data and/or a buffer status report BSR; The terminal device receives configuration information sent by the network device, where the configuration information includes the first CG configuration configured by the network device. The method according to claim 1, wherein the terminal device sending configuration authorization CG request information to the network device comprises: When the terminal device has a service to be transmitted at the current moment or in the first time period after the current moment, the terminal device sends the CG request information to the network device. The method according to claim 1 or 2, wherein the CG request information further includes a CG resource period and/or a CG resource size that the terminal device expects the network device to configure. The method according to claim 3, wherein the method further comprises: The terminal device determines the CG resource period according to the arrival period of the service to be transmitted and/or the delay requirement of the service to be transmitted. The method according to claim 3 or 4, wherein the method further comprises: The terminal device determines the size of the CG resource according to the service volume of the service to be transmitted. The method according to claim 5, wherein if the fluctuation range of the service volume of the service to be transmitted is greater than a preset range, the size of the CG resource is the size of the resource required by the terminal device to report the BSR. The method according to claim 5, wherein if the fluctuation range of the service volume of the service to be transmitted is less than or equal to a preset range, the size of the CG resource is the service volume of the service to be transmitted. The method according to claim 7, wherein the method further comprises: When the uplink data arrives, the terminal device sends the uplink data according to the first CG configuration. The method according to any one of claims 1 to 8, wherein the terminal device sending configuration authorization CG request information to the network device comprises: The terminal device sends the CG request information to the network device during the random access process. The method according to claim 9, wherein the CG request information is carried in message 1 or message 3 in the random access process. The method according to any one of claims 1 to 8, wherein when the terminal device is in a connected state, the CG request information is carried in radio resource control RRC signaling or media access control control unit MAC In CE. The method according to claim 11, wherein the sending of the CG request information by the terminal device to the network device comprises: When the following conditions are met, the terminal device sends the CG request information to the network device: The network device does not configure the CG configuration for the terminal device at the current moment; The terminal device has not sent CG request information to the network device, or the time interval between the current time and the time when the terminal device last sent the CG request information is greater than a preset time interval, and the preset time interval is The minimum time interval for the terminal device to send CG request information twice. The method according to claim 11, wherein the CG request information is used to request the network device to be the terminal device when the network device has configured a second CG configuration for the terminal device Update the second CG configuration. The method according to claim 13, wherein the sending of the CG request information by the terminal device to the network device comprises: When the following conditions are met, the terminal device sends the CG request information to the network device: The second CG configuration does not meet the transmission requirements of the service to be transmitted; The terminal device has not sent CG request information to the network device, or the time interval between the current time and the time when the terminal device last sent the CG request information is greater than a preset time interval, and the preset time interval is The minimum time interval for the terminal device to send CG request information twice. The method according to claim 13 or 14, characterized in that, before the terminal device sends CG request information to the network device, the method further comprises: The terminal device receives first RRC configuration information sent by the network device, where the first RRC configuration information includes the second CG configuration. The method according to any one of claims 11 to 15, wherein the method comprises: The terminal device receives second RRC configuration information sent by the network device, where the second RRC configuration information is used to configure a CG request prohibition timer, and the CG request prohibition timer is used to restrict the terminal device from sending CG twice The minimum time interval for requesting information. The method of claim 16, wherein the method further comprises: The terminal device starts or restarts the CG request prohibition timer after sending the CG request information. The method according to any one of claims 1 to 17, wherein the method is applied in a non-terrestrial communication network NTN. A method for resource allocation, characterized in that the method includes: The network device receives configuration authorization CG request information sent by the terminal device, where the CG request information is used to request the network device to configure the terminal device with a CG configuration for sending uplink data and/or a buffer status report BSR; The network device sends configuration information to the terminal device, where the configuration information includes the first CG configuration configured by the network device. The method of claim 19, wherein the method further comprises: The network device determines whether to configure a CG configuration for the terminal device based on the CG request information. The method of claim 20, wherein the method further comprises: If it is determined to configure the CG configuration for the terminal device, the network device determines the first CG configuration based on the CG request. The method according to any one of claims 19 to 21, wherein the receiving, by the network device, the configuration authorization CG request information sent by the terminal device comprises: When the terminal device has a service to be transmitted at the current moment or in the first time period after the current moment, the network device receives the CG request information sent by the terminal device. The method according to any one of claims 19 to 22, wherein the CG request information further includes a CG resource period and/or CG resource size that the terminal device expects the network device to configure. The method according to claim 23, wherein if the fluctuation range of the service volume of the service to be transmitted of the terminal device is greater than a preset range, the size of the CG resource is the size of the resource required by the terminal device to report the BSR . The method according to claim 23, wherein if the fluctuation range of the service volume of the service to be transmitted of the terminal device is less than or equal to the preset range, the CG resource size is the service volume of the service to be transmitted The amount of size. The method of claim 25, wherein the method further comprises: When the uplink data arrives, the network device receives the uplink data according to the first CG configuration. The method according to any one of claims 19 to 26, wherein the CG request information is carried in message 1 or message 3 in the random access process. The method according to any one of claims 19 to 26, wherein when the terminal device is in a connected state, the CG request information is carried in radio resource control RRC signaling or media access control unit MAC In CE. The method according to claim 28, wherein the receiving, by the network device, the configuration authorization CG request information sent by the terminal device comprises: When the following conditions are met, the network device receives the CG request information sent by the terminal device: The network device does not configure the CG configuration for the terminal device at the current moment; The network device has not received the CG request information sent by the terminal device, or the time interval between the current time and the time when the network device last received the CG request information is greater than a preset time interval, the preset time interval It is the minimum time interval for the network device to receive CG request information twice. The method according to claim 28, wherein, in the case that the network device has configured a second CG configuration for the terminal device, the CG request information is used to request the network device to be the terminal device Update the second CG configuration. The method according to claim 30, wherein the receiving, by the network device, the configuration authorization CG request information sent by the terminal device comprises: When the following conditions are met, the network device receives the CG request information sent by the terminal device: The second CG configuration does not meet the transmission requirement of the service to be transmitted of the terminal device; The network device has not received the CG request information sent by the terminal device, or the time interval between the current time and the time when the network device last sent the CG request information is greater than a preset time interval, the preset time interval It is the minimum time interval for the network device to receive CG request information twice. The method according to claim 30 or 31, wherein before the network device receives the CG request information, the method further comprises: The network device sends first RRC configuration information to the terminal device, where the first RRC configuration information includes the second CG configuration. The method according to any one of claims 28 to 32, wherein the method further comprises: The network device sends second RRC configuration information to the terminal device, where the second RRC configuration information is used to configure a CG request prohibition timer, and the CG request prohibition timer is used to restrict the terminal device from sending CG requests twice The minimum time interval for information. A terminal device, characterized in that it comprises: The communication unit is configured to send configuration authorization CG request information to a network device, where the CG request information is used to request the network device to configure the terminal device with a CG configuration for sending uplink data and/or a buffer status report BSR; The communication unit is further configured to receive configuration information sent by the network device, where the configuration information includes the first CG configuration configured by the network device. The terminal device according to claim 34, wherein the communication unit is specifically configured to: When the terminal device has a service to be transmitted at the current moment or in the first time period after the current moment, the CG request information is sent to the network device. The terminal device according to claim 34 or 35, wherein the CG request information further includes a CG resource period and/or a CG resource size that the terminal device expects the network device to configure. The terminal device according to claim 36, wherein the terminal device further comprises: The processing unit is configured to determine the CG resource period according to the arrival period of the service to be transmitted and/or the delay requirement of the service to be transmitted. The terminal device according to claim 36 or 37, wherein the terminal device further comprises: The processing unit is configured to determine the size of the CG resource according to the service volume of the service to be transmitted. The terminal device according to claim 38, wherein if the fluctuation range of the service volume of the service to be transmitted is greater than a preset range, the size of the CG resource is the size of the resource required by the terminal device to report the BSR. The terminal device according to claim 38, wherein if the fluctuation range of the service volume of the service to be transmitted is less than or equal to a preset range, the size of the CG resource is the service volume of the service to be transmitted. The terminal device according to claim 40, wherein the communication unit is further configured to: When the uplink data arrives, send the uplink data according to the first CG configuration. The terminal device according to any one of claims 34 to 41, wherein the communication unit is specifically configured to: In the random access process, the CG request information is sent to the network device. The terminal device according to claim 42, wherein the CG request information is carried in message 1 or message 3 in the random access process. The terminal device according to any one of claims 34 to 41, wherein when the terminal device is in a connected state, the CG request information is carried in a radio resource control RRC signaling or a media access control control unit MAC CE. The terminal device according to claim 44, wherein the communication unit is specifically configured to: When the following conditions are met, send the CG request information to the network device: The network device does not configure the CG configuration for the terminal device at the current moment; The communication unit has not sent CG request information to the network device, or the time interval between the current time and the time when the communication unit last sent the CG request information is greater than a preset time interval, and the preset time interval is The minimum time interval for the communication unit to send CG request information twice. The terminal device according to claim 44, wherein, in the case that the network device has configured the second CG configuration for the terminal device, the CG request information is used to request the network device to be the terminal device The device updates the second CG configuration. The terminal device according to claim 46, wherein the communication unit is specifically configured to: When the following conditions are met, send the CG request information to the network device: The second CG configuration does not meet the transmission requirements of the service to be transmitted; The communication unit has not sent CG request information to the network device, or the time interval between the current time and the time when the communication unit last sent the CG request information is greater than a preset time interval, and the preset time interval is The minimum time interval for the communication unit to send CG request information twice. The terminal device according to claim 46 or 47, wherein before the communication unit sends CG request information to the network device, the communication unit is further configured to: Receiving first RRC configuration information sent by the network device, where the first RRC configuration information includes the second CG configuration. The terminal device according to any one of claims 44 to 48, wherein the communication unit is further configured to: Receive second RRC configuration information sent by the network device, where the second RRC configuration information is used to configure a CG request prohibition timer, and the CG request prohibition timer is used to limit the minimum of two CG request information sent by the communication unit time interval. The terminal device of claim 49, wherein the terminal device further comprises: The processing unit is configured to start or restart the CG request prohibition timer after sending the CG request information. The terminal device according to any one of claims 34 to 50, wherein the terminal device is in a non-terrestrial communication network NTN. A network device, characterized by comprising: The communication unit is configured to receive configuration authorization CG request information sent by a terminal device, where the CG request information is used to request the network device to configure the terminal device with a CG configuration for sending uplink data and/or a buffer status report BSR; The communication unit is further configured to send configuration information to the terminal device, where the configuration information includes the first CG configuration configured by the network device. The network device according to claim 52, wherein the network device further comprises: The processing unit is configured to determine whether to configure a CG configuration for the terminal device based on the CG request information. The network device according to claim 53, wherein the processing unit is further configured to: If it is determined that the CG configuration is configured for the terminal device, the first CG configuration is determined based on the CG request. The network device according to any one of claims 52 to 54, wherein the communication unit is specifically configured to include: When the terminal device has a service to be transmitted at the current moment or in the first time period after the current moment, receiving the CG request information sent by the terminal device. The network device according to any one of claims 52 to 55, wherein the CG request information further includes a CG resource period and/or a CG resource size that the terminal device expects the network device to configure. The network device according to claim 56, wherein if the fluctuation range of the service volume of the service to be transmitted of the terminal device is greater than a preset range, the size of the CG resource is the resource required by the terminal device to report the BSR size. The network device according to claim 56, wherein if the fluctuation range of the service volume of the service to be transmitted of the terminal device is less than or equal to the preset range, the size of the CG resource is the size of the service to be transmitted The size of the business. The network device according to claim 58, wherein the communication unit is further configured to: When the uplink data arrives, receive the uplink data according to the first CG configuration. The network device according to any one of claims 52 to 59, wherein the CG request information is carried in message 1 or message 3 in the random access process. The network device according to any one of claims 52 to 59, wherein when the terminal device is in a connected state, the CG request information is carried in a radio resource control RRC signaling or a media access control control unit MAC CE. The network device according to claim 61, wherein the communication unit is specifically configured to: When the following conditions are met, receive the CG request information sent by the terminal device: The network device does not configure the CG configuration for the terminal device at the current moment; The communication unit has not received the CG request information sent by the terminal device, or the time interval between the current time and the time when the communication unit last received the CG request information is greater than a preset time interval, the preset time interval This is the minimum time interval for the communication unit to receive CG request information twice. The network device according to claim 61, wherein the CG request information is used to request the network device to be the terminal device when the network device has configured a second CG configuration for the terminal device The device updates the second CG configuration. The network device according to claim 63, wherein the communication unit is specifically configured to: When the following conditions are met, receive the CG request information sent by the terminal device: The second CG configuration does not meet the transmission requirement of the service to be transmitted of the terminal device; The communication unit has not received the CG request information sent by the terminal device, or the time interval between the current time and the time when the communication unit last sent the CG request information is greater than a preset time interval, the preset time interval This is the minimum time interval for the communication unit to receive CG request information twice. The network device according to claim 63 or 64, wherein before the communication unit receives the CG request information, the communication unit is further configured to: Sending first RRC configuration information to the terminal device, where the first RRC configuration information includes the second CG configuration. The network device according to any one of claims 61 to 65, wherein the communication unit is further configured to: Sending second RRC configuration information to the terminal device, where the second RRC configuration information is used to configure a CG request prohibition timer, and the CG request prohibition timer is used to limit the minimum time for the terminal device to send CG request information twice interval. A terminal device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute as claimed in claims 1 to 18. Any one of the methods. A network device, characterized by comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute the computer program as in claims 19 to 33 Any one of the methods. An apparatus, characterized by comprising: a processor, configured to call and run a computer program from a memory, so that the device installed with the chip executes the method according to any one of claims 1 to 18. An apparatus, characterized by comprising: a processor, configured to call and run a computer program from a memory, so that the device installed with the chip executes the method according to any one of claims 19 to 33. A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 1 to 18. A computer-readable storage medium, characterized in that it is used to store a computer program that enables a computer to execute the method according to any one of claims 19 to 33. A computer program product, characterized by comprising computer program instructions, which cause a computer to execute the method according to any one of claims 1 to 18. A computer program product, characterized by comprising computer program instructions, which cause a computer to execute the method according to any one of claims 19 to 33. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 18. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 19 to 33.

Images