CN113632561B

CN113632561B - Resource allocation method, terminal equipment and network equipment

Info

Publication number: CN113632561B
Application number: CN201980094816.6A
Authority: CN
Inventors: 付喆
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-08-19
Filing date: 2019-08-19
Publication date: 2023-10-10
Anticipated expiration: 2039-08-19
Also published as: CN113632561A; WO2021031089A1

Abstract

The embodiment of the application relates to a resource configuration method, terminal equipment and network equipment, wherein the method comprises the following steps: the method comprises the steps that terminal equipment sends configuration authorization CG request information to network equipment, wherein the CG request information is used for requesting the network equipment to configure CG configuration for sending uplink data and/or a Buffer Status Report (BSR) for the terminal equipment; the terminal equipment receives configuration information sent by the network equipment, wherein the configuration information comprises a first CG configuration configured by the network equipment. The resource configuration method, the terminal equipment and the network equipment can improve the flexibility of the system.

Description

Resource allocation method, terminal equipment and network equipment

Technical Field

The present application relates to the field of communications, and in particular, to a method for configuring resources, a terminal device, and a network device.

Background

The third generation partnership project (3rd Generation Partnership Project,3GPP) is currently researching Non-terrestrial communication network (Non-Terrestrial Network, NTN) technology, which typically employs satellite communication to provide communication services to terrestrial users.

The New Radio (NR) system has a high requirement for flexibility, however, in the NTN system, the flexibility when the network device performs resource allocation for the terminal device is low. Therefore, how to improve flexibility of configuring resources of a network device in NTN is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a resource configuration method, terminal equipment and network equipment, which can improve the flexibility of the network equipment for configuring resources.

In a first aspect, a method for resource allocation is provided, the method comprising: the method comprises the steps that terminal equipment sends configuration authorization CG request information to network equipment, wherein the CG request information is used for requesting the network equipment to configure CG configuration for sending uplink data and/or a Buffer Status Report (BSR) for the terminal equipment;

the terminal equipment receives configuration information sent by the network equipment, wherein the configuration information comprises a first CG configuration configured by the network equipment.

In a second aspect, a method of resource configuration is provided, the method comprising: the network equipment receives configuration authorization CG request information sent by the terminal equipment, wherein the CG request information is used for requesting the network equipment to configure CG configuration for sending uplink data and/or a Buffer Status Report (BSR) for the terminal equipment;

the network device sends configuration information to the terminal device, wherein the configuration information comprises a first CG configuration configured by the network device.

In a third aspect, a terminal device is provided for performing the method in the first aspect or each implementation manner thereof.

Specifically, the terminal device comprises functional modules for performing the method of the first aspect or its implementation manner.

In a fourth aspect, a network device is provided for performing the method of the second aspect or implementations thereof.

In particular, the network device comprises functional modules for performing the method of the second aspect or implementations thereof described above.

In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method in the first aspect or various implementation manners thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides an apparatus for implementing the method of any one of the first to second aspects or each implementation thereof.

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method as in any one of the first to second aspects or implementations thereof described above.

Optionally, the device is a chip.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to second aspects or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

According to the technical scheme, the terminal equipment sends the CG request information for requesting the network equipment to configure CG configuration to the network equipment, so that the problem that the terminal equipment needs to configure CG but the network equipment does not have the CG configuration can be avoided, the network equipment can flexibly configure CG configuration for the terminal equipment, and the flexibility of the system can be improved.

Drawings

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

Fig. 2 is a schematic flow chart of a terminal device requesting uplink scheduling.

Fig. 3 is a schematic flow chart of a method of resource allocation according to an embodiment of the application.

Fig. 4 is a schematic flow chart of a specific implementation of a method of resource allocation according to an embodiment of the application.

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

Fig. 6 is a schematic flow chart diagram of a specific implementation of a method of resource allocation 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 application.

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

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) systems, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), long term evolution advanced (Advanced long term evolution, LTE-a) systems, new Radio (NR) systems, evolution systems of NR systems, LTE-based access to unlicensed spectrum on unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U) systems, NR-based access to unlicensed spectrum on unlicensed spectrum (NR-U) systems, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), universal internet 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, and the like.

An exemplary communication system 100 to which embodiments of the present application may be applied 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 referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Alternatively, 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, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. "terminal device" as used herein includes, but is not limited to, a connection via a wireline, such as via a public-switched telephone network (Public Switched Telephone Networks, PSTN), a digital subscriber line (Digital Subscriber Line, DSL), a digital cable, a direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (Wireless Local Area Network, WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of the other terminal device arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. Terminal devices arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal device may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved PLMN, etc.

Alternatively, direct terminal (D2D) communication may be performed between the terminal devices 120.

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

Fig. 1 illustrates one network device and two terminal devices by way of example, and the communication system 100 may alternatively include multiple network devices and may include other numbers of terminal devices within the coverage area of each network device, as embodiments of the application are not limited in this regard.

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

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. 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, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should also be appreciated 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" are used interchangeably herein.

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

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, 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 transmit. Thus, the network device may allocate physical uplink shared channel (Physical Uplink Control Channel, PUSCH) resources to the terminal device sufficient for the terminal device to send a buffer status report (Buffer Status Report, BSR).

230: the terminal device sends the BSR on the PUSCH resources allocated by the network device, thereby informing the network device of the size of the data volume that the terminal device needs to send.

Wherein, the BSR may be carried by a BSR medium access Control (Medium Access Control, MAC) Control Element (CE).

240: and the network equipment allocates proper PUSCH resources for uplink data transmission to the terminal equipment according to the BSR information reported by the terminal equipment.

250: and the terminal equipment transmits uplink data on the PUSCH resources allocated by the network equipment.

As can be seen from fig. 2, the terminal device makes the network device learn the uplink buffer data amount of the terminal device through the BSR, so that the network device can schedule the terminal device according to the data amount information provided by the terminal device.

In order to save reporting cost of the BSR, a packet reporting manner may be adopted when the terminal device reports the BSR. Each uplink logical channel may correspond to one logical channel group (Logical Channel Group, LCG), multiple uplink logical channels may correspond to the same LCG, and logical channel-to-LCG correspondence may be configured by the network device through radio resource control (Radio Resource Control, RRC) signaling. The terminal equipment reports the BSR based on the LCG. Up to 8 LCGs can be supported per terminal device in the NR.

The triggering conditions of the BSR are as follows:

1. a logical channel with higher priority of the terminal device has uplink data arriving, in which case a Regular BSR may be triggered.

2. The Padding (Padding) portion of the uplink resource allocated to the terminal device after carrying other uplink data may carry the BSR MAC CE, in which case the Padding BSR may be triggered.

3. The retransmission BSR Timer (retxBSR-Timer) times out and there is currently at least one uplink logical channel with uplink data to be transmitted, at which point the Regular BSR may be triggered.

4. The period BSR Timer (Periodic BSR-Timer) times out, at which time a period (Periodic) BSR may be triggered.

If there are multiple logical channels triggering a Regular BSR at the same time, each of these logical channels may trigger a separate Regular BSR.

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

As can also be seen from fig. 2, the terminal device applies for uplink resources to the network device through the SR. However, the network device does not know when the terminal device needs to transmit uplink data, i.e. when the terminal device will transmit SRs. Accordingly, the network device may allocate a periodic physical uplink control channel (Physical Uplink Control Channel, PUCCH) resource for transmitting SR to the terminal device, and then the network device may detect whether there is SR reporting on the already allocated SR resource.

As can be seen from the above triggering conditions for SRs, the SRs in the NR are based on logical channels. For each uplink logical channel, the network device may select whether PUCCH resources for transmitting SRs are configured for the uplink logical channel.

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

In NR, the signal transmission delay between the terminal device and the network device is small, and the waiting time from the terminal device having uplink data to the terminal device transmitting the data to the network device is generally short, which has little influence on the service delay.

Compared with the cellular network adopted by the traditional NR, the signal propagation delay between the terminal equipment and the satellite in the NTN is greatly increased. Therefore, when the terminal device has uplink data to arrive, but the terminal device does not have uplink resources for data transmission, the terminal device needs to wait for a relatively long time to send the data to the network device, so that service delay is obviously increased, and user experience is affected.

In order to alleviate the problem of uplink traffic delay, NR introduced the concept of uplink unlicensed transmission. The terminal device may transmit on a resource of a Configured Grant (CG) according to the service requirement.

Currently, NR supports two types of uplink unlicensed transmissions:

1. PUSCH transmission based on a first class of configuration grants (Configured Grant Type 1)

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

2. PUSCH transmission based on second class configuration grants (Configured Grant Type 2)

Type 2 adopts a two-step resource allocation mode: firstly, the network equipment configures transmission resources and transmission parameters including the period, repetition times, frequency hopping, HARQ process number and the like of time domain resources through RRC; a second type of configuration grant based PUSCH transmission is then activated by a physical downlink control channel (Physical Downlink Control Channel, PDCCH) scrambled with a cell radio network temporary identity (Configured Scheduling Radio Network Temporary Identifier, CS-RNTI) of the configuration schedule, and other transmission resources and transmission parameters including time domain resources, frequency domain resources, MCS, etc. are simultaneously configured. When receiving the RRC configuration parameters, the terminal equipment cannot immediately use the resources and parameters configured by the configuration parameters to carry out the PUSCH transmission, but must wait for receiving the corresponding PDCCH activation and configuring other resources and parameters to carry out the PUSCH transmission.

If the terminal equipment does not have data to be sent on the PUSCH resources of the first type or the second type CG, the terminal equipment does not send any content on the CG resources.

However, CG configuration of network device configuration does not necessarily match the requirements of the UE well. For example, if the terminal device needs to configure CG configuration and the network device is not configured, an excessive uplink service delay may be caused. For another example, if the network device configures CG for the terminal device but the CG resource is too small, delay may be increased; or CG resources are too large, which may result in waste of system resources.

In view of this, the embodiment of the present application proposes a method for configuring resources, which can improve flexibility of configuring CG for terminal devices by network devices.

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

Fig. 3 is a schematic flow chart of a method 300 of resource allocation according to an embodiment of the application. The method described in fig. 3 may be performed by a terminal device, such as the terminal device 120 shown in fig. 1, and a network device, such as the network device 110 shown in fig. 1.

It should be appreciated that the method 300 may be applied in NTN. To enhance the understanding of NTN, NTN will be described below.

NTN technology generally provides communication services to terrestrial users by means of satellite communications. Satellite communications have many unique advantages over terrestrial cellular communications. First, satellite communications are not limited by the user territory, and for example, areas such as ocean, mountain, desert, etc. that cannot be covered by general land communications cannot be normally communicated because communication devices cannot be set up or because of sparse population are not covered by the satellite communications. For satellite communications, each corner of the earth may be covered by satellite communications in theory, since one satellite may cover a larger ground surface, along with the satellite orbiting the earth. And secondly, satellite communication has great social value. Satellite communication can be covered in remote mountain areas, poor and backward countries or regions with lower cost, so that people in the regions enjoy advanced voice communication and mobile internet technology, and the digital gap between developed regions is reduced, and the development of the regions is promoted. Again, the satellite communication distance is far, and the cost of communication increases without significant increase in communication distance. And finally, the satellite communication has high stability and is not limited by natural disasters.

Communication satellites can be classified into Low Earth Orbit (LEO) satellites, medium Earth Orbit (MEO) satellites, geosynchronous Orbit (Geostationary Earth Orbit, GEO) satellites, high elliptical Orbit (High Elliptical Orbit, HEO) satellites, and the like, according to the Orbit heights. The LEO satellites and GEO satellites are mainly studied in the present stage, and the LEO satellites and GEO satellites are described below.

The LEO satellites range in altitude from 500km to 1500km, with corresponding orbital periods of about 1.5 hours to 2 hours. The signal propagation delay for single hop communications between users is typically less than 20ms. The maximum satellite viewing time was 20 minutes. The signal propagation distance is short, the link loss is less, and the requirement on the transmitting power of the user terminal is not high.

GEO satellites have an orbital altitude of 35786km and a period of 24 hours around the earth. The signal propagation delay for single hop communications between users is typically 250ms.

In order to ensure the coverage of the satellite and improve the system capacity of the whole satellite communication system, the satellite adopts multiple beams to cover the ground, and one satellite can form tens or hundreds of beams to cover the ground; a satellite beam may cover a ground area of several tens to hundreds of kilometers in diameter.

Of course, the method 300 may also be used in other communication scenarios, such as terrestrial cellular network communications, internet of vehicles communications, and the like.

As shown in fig. 3, the method 300 may include at least some of the following.

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 CG configuration for the terminal device to send uplink data and/or BSR.

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

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

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

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

Therefore, when uplink data arrives, the terminal equipment can report the BSR to the network equipment more quickly and/or send the uplink data, so that the time delay of the service to be transmitted can be reduced.

The traffic to be transmitted may be delay sensitive traffic, such as ultra-reliable low delay communication (Ultra Reliable Low Latency Communication, URLLC) traffic, time sensitive network (Time Sensitive Network, TSN) traffic. Or, the service to be transmitted may also be an enhanced mobile broadband (Enhanced Mobile Broadband, eMBB) service, a vertical industry service, a Long Term Evolution Voice-over-Term Evolution (VoLTE) service, a car networking service, and the like.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone.

The technical solutions of the embodiments of the present application are described in detail below in conjunction with three embodiments.

Example 1

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

Specifically, the CG request information may be carried in message 1 or message 3 in the random access procedure. Message 1 may be message 1 (Msg 1) in a four-step random access procedure, i.e., a random access Preamble; alternatively, message 1 may be message a (Msg a) in a two-step random access procedure.

Optionally, the CG request information may further include a CG resource period and/or a CG resource size that the terminal device desires to configure by the network device.

The terminal equipment reports the expected CG resource period and/or CG resource size to the network equipment, so that the problem that CG resources configured by the network equipment are too large or too small can be avoided, and therefore the CG configuration configured by the network equipment can be better matched with the requirements of the terminal equipment. And simultaneously, the system resources can be more efficiently utilized.

The method 300 may further include: and the terminal equipment determines the CG resource period which is expected to be configured by the network equipment according to the arrival period of the service to be transmitted and/or the time delay requirement of the service to be transmitted.

For example, if the arrival period of the traffic to be transmitted is 10ms, the CG resource period that the terminal device expects the network device to configure may be 10ms.

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

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

The traffic of the traffic to be transmitted may be historical traffic of the traffic to be transmitted. For example, the historical traffic may be historical average traffic over a period of time, e.g., the traffic of the traffic to be transmitted may be historical average traffic of the traffic to be transmitted over the last month. Still further by way of example, the historical traffic may be an average of the highest traffic and the lowest traffic over a period of time.

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

If the fluctuation range of the traffic to be transmitted is larger than the preset range, that is, the fluctuation range of the traffic to be transmitted is larger, the CG resource size of the network device configuration expected by the terminal device can be the resource size required by the terminal device to report the BSR. In this way, system resources can be saved.

For example, if the difference between the traffic volume of the traffic to be transmitted in the first month and the traffic volume in the second month is greater than the preset amplitude, the traffic volume of the traffic to be transmitted can be considered to fluctuate greatly, and the terminal device can request CG resources according to the size of the resources required for reporting the BSR.

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

Alternatively, the preset amplitude may be preset on the terminal device based on a protocol, or may be preconfigured to the terminal device by the network device, for example, may be configured through RRC signaling.

When CG request information is carried on a Preamble in a four-step random access procedure, in one possible embodiment, the preambles may be divided into 2 groups, where a group of preambles may be used to indicate that a terminal device has no need to configure CG configuration. Another set of preambles may be used to indicate to the terminal device that there is a need to configure CG configuration. The terminal device informs the network device whether the terminal device wants the network device to configure CG configuration for the terminal device by using the Preamble in one of the preambles to send to the network device when sending message 1.

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

For example, the preambles are divided into 5 groups, a first group of preambles, a second group of preambles, a third group of preambles, a fourth group of preambles, and a fifth group of preambles, respectively. The terminal equipment and the network equipment negotiate in advance a first group of preambles for indicating that the terminal equipment does not configure CG configuration requirements, a second group of preambles for indicating that the CG resource size expected by the terminal equipment is X, a third group of preambles for indicating that the CG resource size expected by the terminal equipment is Y, a fourth group of preambles for indicating that the CG resource size expected by the terminal equipment is Z, and a fifth group of preambles for indicating that the CG resource size expected by the terminal equipment is W. The terminal device sends the second group of preambles to the network device, and after the network device receives the second group of preambles, the network device can determine that the terminal device has a requirement for configuring CG configuration, and the desired CG resource size is X.

For the network device, after receiving the CG request information, the network device may determine whether to configure CG configuration for the terminal device according to the CG request information. If the network device determines that the CG configuration is configured for the terminal device, the network device may configure the first CG configuration according to the CG request information. The network device may then send configuration information to the terminal device, the configuration information including the first CG configuration.

Alternatively, the first CG configuration may be carried in message 4 (Msg 4) in a four-step random access procedure, or in message B (Msg B) in a two-step random access procedure.

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

The network device needs to ensure fair allocation of system resources, and 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 combine factors such as occupation of system resources, fairness among the terminal devices, priority of the service to be transmitted and the like to determine whether to configure CG configuration for the terminal device. For example, if the priority of the service to be transmitted of other terminal devices in the system is higher than the priority of the service to be transmitted of the terminal device, and the system resources are insufficient to allocate CG resources for the two terminal devices, the network device may not configure CG configuration for the terminal device.

If the network device determines that the CG configuration is configured for the terminal device, the network device may determine the first CG configuration according to factors such as a CG configuration request of the terminal device, an occupation condition of system resources, fairness among the terminal devices, a priority of a service to be transmitted, and the like.

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

For another example, if a larger portion of the system resources are unoccupied, the CG resource size in the first CG configuration may be equal to the CG resource size desired by the terminal device.

If the size of the resources in the first CG configuration is the size of the resources required by the terminal device to report the BSR, when the terminal device has uplink data to arrive, and triggers the BSR, the terminal device may send the BSR to the network device on the CG resources configured by the network device. After the network device receives the BSR reported by the terminal device, the network device may allocate appropriate resources to the terminal device according to the data to be transmitted of the terminal device, and instruct the terminal device to complete PUSCH transmission through dynamic scheduling signaling, such as a PDCCH scrambled by a Cell radio network temporary identifier (Cell-Radio Network Temporary Identifier, C-RNTI).

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

If the resource size in the first CG configuration is the resource size of the uplink data sent by the terminal device, when the terminal device has uplink data arrived, the terminal device may send the uplink data according to the first CG configuration.

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

The technical scheme of embodiment 1 will be exemplarily described with reference to fig. 4.

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

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

Step 3: because the terminal equipment currently has delay sensitive service, but the fluctuation of the service volume is larger, the terminal equipment carries CG request information in Msg3 (RRC connection establishment request message) to indicate that the terminal equipment has the requirement of configuring CG, and meanwhile, the Msg3 also carries the CG resource period and the CG resource size expected by the terminal equipment.

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

And, the network device transmits configuration information including the first CG configuration, which is carried in Msg4 (RRC connection setup message) of random access, to the terminal device.

Step 5: when the terminal equipment arrives uplink data and triggers the BSR, the terminal equipment sends the BSR on CG resources closest to the current moment.

Step 6: after receiving the BSR sent by the terminal equipment, the network equipment allocates proper PUSCH resources for the terminal equipment according to the data volume information provided by the terminal equipment, and indicates the uplink scheduling information of the terminal equipment through the PDCCH scrambled by the C-RNTI.

Step 7: and the terminal equipment completes uplink data transmission on the PUSCH resources distributed by the network equipment.

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

Example 2

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

The terminal device may transmit CG request information to the network device when:

(1) The terminal equipment is provided with a service to be transmitted at the current moment or predicted in a future period of time;

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

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

The terminal device may send CG request information twice in two cases: the terminal device has transmitted CG request information and the network device has received the CG request information, or the terminal device has transmitted CG request information but the network device has not received the CG request information.

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

Alternatively, the preset time interval may be preset on the terminal device by a protocol specification.

Alternatively, the preset time interval may be preconfigured by the network device to the terminal device. For example, the network device may send second RRC configuration information to the terminal device, where the second RRC configuration information may be used to configure a CG request prohibit timer (cgrequestprohibit timer) that is used to limit a minimum time interval for the terminal device to send CG request information twice.

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 transmitted the CG request information being larger than the preset time interval, it can be understood that: CG request prohibit timer has timed out. That is, the minimum time interval for limiting the terminal device to transmit CG request information twice by the CG request prohibit timer can be understood as: the terminal device may send CG request information to the network device again only if the CG request prohibit timer expires.

The terminal device may also maintain a CG request prohibit timer in the case where the network device is configured with the CG request prohibit timer. Specifically, the terminal device may start or restart the CG request prohibit timer each time CG request information is transmitted.

It should be understood that in the embodiments of the present application, "first" and "second" are merely for distinguishing between different objects, and do not limit the scope of the embodiments of the present application.

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

The terminal device may determine, according to the traffic of the service to be transmitted, the CG resource size desired to be configured by the network device.

Further, the network device may determine whether to configure CG configuration for the terminal device by combining factors such as occupation of system resources, fairness among the terminal devices, and priority of the service to be transmitted.

The technical solution of embodiment 2 is exemplarily described 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 for configuring the CG request inhibit timer, and the second RRC configuration information does not include CG configuration.

Step 2: the terminal device has a service to be transmitted, which is sensitive to time delay and has a fixed traffic, i.e. a fixed packet size. Therefore, the terminal device sends CG request information to the network device, and the CG request information further includes a CG resource period and a CG resource size expected by the terminal device.

The terminal equipment determines the CG resource period expected by the terminal equipment according to the arrival period of the service to be transmitted and the service delay requirement.

And the terminal equipment determines the CG resource size expected by the terminal equipment according to the traffic to be transmitted.

In addition, the terminal device starts a CG request prohibit timer while the terminal device transmits CG request information to the network device.

Step 3: the terminal device does not receive the CG configuration of the network device configuration.

Step 4: when the terminal equipment has uplink data, the terminal equipment does not have uplink resources available for data transmission, and the terminal equipment sends an SR to the network equipment.

Step 5: and the network equipment receives the SR and allocates the resource for sending the BSR for the terminal equipment. And then, the network equipment indicates uplink scheduling through the PDCCH.

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

Step 7: the network equipment receives the BSR, acquires the uplink data amount information of the terminal equipment, allocates PUSCH resources to the terminal equipment in a dynamic scheduling mode, and indicates the resource allocation information to the terminal equipment.

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

Step 9: and waiting until the CG request prohibition timer is overtime, the terminal equipment sends CG request information to the network equipment again. At the same time, the terminal device starts a CG prohibit timer.

Step 10: the terminal device receives configuration information from the network device, wherein the configuration information comprises a first CG configuration. The CG resource period and the CG resource size of the first CG configuration are a CG resource period and a CG resource size of a CG resource request by the terminal device, respectively.

Step 11: when the uplink data arrives, the terminal equipment sends the uplink data on the CG resource nearest to the current moment.

Example 3

In the case where 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, where the CG request information is used to request the network device to update the second CG configuration for the terminal device.

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

Alternatively, before the terminal device transmits the CG request information to the network device, the network device may transmit 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: time domain resources, frequency domain resources, time domain resource period, repetition times, MCS, HARQ process and other parameters.

In the embodiment of the present application, the terminal device may send CG request information to the network device when the following condition is satisfied:

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

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

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

case 1: the CG resource size of the second CG configuration cannot meet the transmission requirement of the service to be transmitted;

case 2: the CG resource period configured by the second CG can not meet the transmission requirement of the service to be transmitted;

case 3: the CG resource size and CG resource period of the second CG configuration may not meet the transmission requirements of the service to be transmitted.

Alternatively, the preset time interval may be preconfigured by the network device to the terminal device. For example, the network device may send the terminal device second RRC configuration information, which may be used to configure the CG request prohibit 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 transmitted the CG request information being larger than the preset time interval, it can be understood that: CG request prohibit timer has timed out.

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

After the network device receives the CG request information, it may 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 may also determine whether to update the second CG configuration for the terminal device by combining factors such as an occupation condition of system resources, fairness among the terminal devices, and priority of a service to be transmitted. If the network device determines that the second CG configuration is updated for the terminal device, the network device may further determine the updated first CG configuration by combining factors such as occupation of system resources, fairness between the terminal devices, and priority of a service to be transmitted.

The method of example 3 is described below in an exemplary manner with reference to fig. 6.

Step 1: the network device sends first RRC configuration information to the terminal device, wherein the first RRC configuration information specifically comprises:

a) And the CG resource size in the second CG configuration is determined according to the resource size required by the terminal equipment for reporting the BSR.

b) CG requests prohibit timers.

Step 2: the terminal device has a service to be transmitted, which is sensitive to time delay and has a fixed traffic, i.e. a fixed packet size. Thus, the terminal device sends CG request information to the network device requesting the network device to update the second CG configuration for the terminal device.

The CG request information further includes a CG resource size expected by the terminal device, where the CG resource size expected by the terminal device is determined according to a traffic volume of a service to be transmitted.

Step 4: when the terminal equipment has uplink data to arrive, the terminal equipment transmits a BSR to the network equipment by utilizing CG resources in the second CG configuration.

Step 5: the network equipment receives the BSR, acquires uplink data amount information of the terminal equipment, distributes PUSCH resources for the terminal equipment in a dynamic scheduling mode according to the uplink data amount information provided by the terminal equipment, and indicates resource distribution information to the terminal equipment.

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

Step 7: and waiting until the CG request prohibition timer is overtime, the terminal equipment sends CG request information to the network equipment again to request the network equipment to update the second CG configuration for the terminal equipment. At the same time, the terminal device starts a CG prohibit timer.

Step 8: the terminal device receives configuration information from the network device, wherein the configuration information comprises a first CG configuration. The CG resource period and the CG resource size of the first CG configuration are a CG resource period and a CG resource size of a CG resource request by the terminal device, respectively.

Step 9: when the uplink data arrives, the terminal equipment sends the uplink data on the CG resource nearest to the current moment.

According to the technical scheme of embodiment 3, when the CG configuration configured by the network equipment for the terminal equipment cannot meet the transmission requirement of the service to be transmitted of the terminal equipment, the terminal equipment sends information for requesting to update the CG configuration to the network equipment, so that the updated CG configuration of the network equipment can better meet the service requirement of the terminal equipment. And simultaneously, the system resources can be more efficiently utilized.

It should be understood that although embodiments 1 to 3 are described above separately, this does not mean that embodiments 1 to 3 are independent, and the descriptions of the respective embodiments may be referred to each other. For example, the relevant description in embodiment 1 may be applied to embodiment 2 and embodiment 3. For brevity of content, embodiments of the present application will not be described too much for embodiments 2 and 3.

According to the embodiment of the application, the terminal equipment sends the CG request information for requesting the network equipment to configure CG to the network equipment, so that the problem that the terminal equipment needs to configure CG but the network equipment does not configure can be avoided, the network equipment can flexibly configure CG to the terminal equipment, and the flexibility of the system can be improved.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings, but the present application is not limited to the specific details of the above embodiments, and various simple modifications can be made to the technical solution of the present application within the scope of the technical concept of the present application, and all the simple modifications belong to the protection scope of the present application.

For example, the specific features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various possible combinations are not described further.

As another example, any combination of the various embodiments of the present application may be made without departing from the spirit of the present application, which should also be regarded as the disclosure of the present application.

It should be understood that, in the various method embodiments of the present application, the sequence number of each process described above does not mean that the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Having described the method of resource allocation in detail in accordance with an embodiment of the present application, a communication apparatus according to an embodiment of the present application will be described below with reference to fig. 7 to 9, and technical features described in the method embodiment are applicable to the following apparatus embodiments.

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

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

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

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

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

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

Optionally, in an embodiment of the present application, the terminal device 400 further includes: and the processing unit 420 is configured to determine the CG resource size according to the traffic volume of the traffic to be transmitted.

Optionally, in the embodiment of the present application, if the fluctuation range of the traffic 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 the embodiment of the present application, if the fluctuation range of the traffic volume of the traffic to be transmitted is smaller than or equal to a preset range, the CG resource size is the traffic volume of the traffic to be transmitted.

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

Optionally, in an embodiment of the present application, the communication unit 410 is specifically configured to: and in the random access process, sending the CG request information to the network equipment.

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

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

Optionally, in an embodiment of the present application, the communication unit 410 is specifically configured to: transmitting the CG request information to the network device when: at the current moment, the network device does not configure CG configuration for the terminal device 400;

the communication unit 410 does not send CG request information to the network device, or a time interval between a current time and a time when the communication unit 410 last sends CG request information is greater than a preset time interval, where the preset time interval is a minimum time interval when the communication unit 410 sends CG request information twice.

Alternatively, in the embodiment of the present application, in the case where the network device has configured a second CG configuration for the terminal device 400, the CG request information is used to request the network device to update the second CG configuration for the terminal device 400.

Optionally, in an embodiment of the present application, the communication unit 410 is specifically configured to: transmitting the CG request information to the network device when: the second CG configuration does not meet the transmission requirements of the service to be transmitted;

the communication unit 410 does not send CG request information to the network device, or a time interval between a current time and a time when the communication unit 410 last sends CG request information is greater than a preset time interval, where the preset time interval is a minimum time interval when the communication unit 410 sends the CG request information twice.

Optionally, in an embodiment of the present application, before the communication unit 410 sends CG request information to a network device, the communication unit 410 is further configured to: and receiving first RRC configuration information sent by the network equipment, wherein the first RRC configuration information comprises the second CG configuration.

Optionally, in an embodiment of the present application, the communication unit 410 is further configured to: and receiving second RRC configuration information sent by the network device, where the second RRC configuration information is used to configure a CG request prohibit timer, and the CG request prohibit timer is used to limit a minimum time interval between two transmissions of the CG request information by the communication unit 410.

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

Optionally, in an 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 a terminal device in the method 300, and the corresponding operation of the terminal device in the method 300 may be implemented, which is not described herein for brevity.

Fig. 8 shows a schematic block diagram of a network device 500 of an embodiment of the application. As shown in fig. 8, the network device 500 includes:

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

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

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

Optionally, in an embodiment of the present application, the processing unit 520 is further configured to: and if the CG configuration is determined to be configured for the terminal equipment, determining the first CG configuration based on the CG request.

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

Optionally, in an embodiment of the present application, 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.

Optionally, in the embodiment of the present application, if the fluctuation range of the traffic 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 the embodiment of the present application, if the fluctuation range of the traffic volume of the service to be transmitted of the terminal device is smaller than or equal to the preset range, the CG resource size is the traffic volume of the service to be transmitted.

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

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

Optionally, in an embodiment of the present application, the communication unit 510 is specifically configured to: receiving the CG request information sent by the terminal device when the following conditions are satisfied: at the current moment, the network device 500 does not configure CG configuration for the terminal device;

the time interval between the current time and the time when the communication unit 510 last receives the CG request information is greater than a preset time interval, where the preset time interval is the minimum time interval when the communication unit 510 receives the CG request information twice.

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

Optionally, in an embodiment of the present application, the communication unit 510 is specifically configured to: receiving the CG request information sent by the terminal device when the following conditions are satisfied: the second CG configuration does not meet the transmission requirement of the service to be transmitted of the terminal equipment;

the time interval between the current time and the time when the communication unit 510 last sends the CG request information is greater than a preset time interval, where the preset time interval is the minimum time interval when the communication unit 510 receives the CG request information twice.

Optionally, in an embodiment of the present application, before the communication unit 510 receives the CG request information, the communication unit 510 is further configured to: and sending first RRC configuration information to the terminal equipment, wherein the first RRC configuration information comprises the second CG configuration.

Optionally, in an embodiment of the present application, the communication unit 510 is further configured to: and sending second RRC configuration information to the terminal equipment, wherein the second RRC configuration information is used for configuring a CG request prohibition timer, and the CG request prohibition timer is used for limiting the minimum time interval of the terminal equipment for sending 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 the corresponding operations of the network device in the method 300 may be implemented, which are not described herein for brevity.

Fig. 9 is a schematic block diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 shown in fig. 9 comprises a processor 610, from which the processor 610 may call and run a computer program to implement the method in an embodiment of the application.

Optionally, as shown in fig. 9, the communication device 600 may further comprise a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the method in an embodiment of the application.

The memory 620 may be a separate device from the processor 610 or may be integrated into 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, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.

Optionally, the communication device 600 may be specifically a network device according to the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the network device in each method according to the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 600 may be specifically a terminal device in the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 10 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 700 shown in fig. 10 includes a processor 710, and the processor 710 may call and execute a computer program from a memory to implement the method in an embodiment of the present application.

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

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

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

Optionally, the apparatus 700 may further comprise an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the apparatus may be applied to a terminal device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the apparatus may be applied to a network device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Alternatively, the apparatus 800 may be a chip. It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 11 is a schematic block diagram of a communication system 800 provided by 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.

The terminal device 810 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 820 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

The embodiment of the application also provides a computer readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the terminal device in each method in the embodiment of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of resource allocation, the method comprising:

the method comprises the steps that terminal equipment sends configuration authorization CG request information to network equipment, wherein the CG request information is used for requesting the network equipment to configure CG configuration for sending uplink data and/or a Buffer Status Report (BSR) for the terminal equipment;

the terminal equipment receives configuration information sent by the network equipment, wherein the configuration information comprises a first CG configuration configured by the network equipment; wherein the terminal device sends configuration authorization CG request information to a network device, including:

when the terminal equipment has a service to be transmitted at the current moment or in a first time period after the current moment, the terminal equipment sends the CG request information to the network equipment; 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 further comprises the steps of:

the terminal equipment determines the CG resource period according to the arrival period of the service to be transmitted and/or the time delay requirement of the service to be transmitted;

the terminal equipment determines the CG resource size according to the traffic volume of the service to be transmitted;

If the fluctuation range of the traffic volume of the traffic to be transmitted is larger than a preset range, the CG resource size is the resource size required by the terminal equipment to report the BSR; if the fluctuation amplitude of the traffic volume of the traffic to be transmitted is smaller than or equal to a preset amplitude, the CG resource size is the traffic volume of the traffic to be transmitted; wherein,

the method further comprises the steps of:

when the uplink data arrives, the terminal equipment sends the uplink data according to the first CG configuration;

the method is applied to a non-terrestrial communication network NTN.

2. The method of claim 1, wherein the terminal device transmitting configuration grant CG request information to a network device, comprising:

and the terminal equipment sends the CG request information to the network equipment in the random access process.

3. The method of claim 2, wherein the CG request information is carried in message 1 or message 3 in the random access procedure.

4. The method according to claim 1, wherein the CG request information is carried in radio resource control, RRC, signaling or medium access control, MAC, CE, cells when the terminal device is in a connected state.

5. The method of claim 4, wherein the terminal device transmitting the CG request information to the network device comprises:

the terminal device transmits the CG request information to the network device when:

at the current moment, the network equipment does not configure CG configuration for the terminal equipment;

the terminal device does not send CG request information to the network device, or the time interval between the current time and the time when the terminal device sends CG request information last time is larger than a preset time interval, wherein the preset time interval is the minimum time interval when the terminal device sends CG request information twice.

6. The method according to claim 4, wherein the CG request information is for requesting the network device to update the second CG configuration for the terminal device, in case the network device has configured a second CG configuration for the terminal device.

7. The method of claim 6, wherein the terminal device transmitting the CG request information to the network device comprises:

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

8. The method according to claim 6 or 7, characterized in that before the terminal device sends CG request information to a network device, the method further comprises:

the terminal equipment receives first RRC configuration information sent by the network equipment, wherein the first RRC configuration information comprises the second CG configuration.

9. The method according to any one of claims 4 to 8, characterized in that the method comprises:

the terminal equipment receives second RRC configuration information sent by the network equipment, wherein the second RRC configuration information is used for configuring a CG request prohibition timer, and the CG request prohibition timer is used for limiting the minimum time interval of the terminal equipment for sending the CG request information twice.

10. The method according to claim 9, wherein the method further comprises:

And when the terminal equipment finishes sending the CG request information, starting or restarting the CG request prohibition timer.

11. A method of resource allocation, the method comprising:

the network equipment receives configuration authorization CG request information sent by the terminal equipment, wherein the CG request information is used for requesting the network equipment to configure CG configuration for sending uplink data and/or a Buffer Status Report (BSR) for the terminal equipment;

the network equipment sends configuration information to the terminal equipment, wherein the configuration information comprises a first CG configuration configured by the network equipment; wherein the method further comprises:

the network equipment determines whether to configure CG configuration for the terminal equipment based on the CG request information;

if the CG configuration is determined to be configured for the terminal equipment, the network equipment determines the first CG configuration based on the CG request; wherein,

the network device receives CG request information for configuration authorization sent by a terminal device, including:

when the terminal equipment has a service to be transmitted at the current moment or in a first time period after the current moment, the network equipment receives the CG request information sent by the terminal equipment; wherein the method comprises the steps of

The CG request information also comprises CG resource period and/or CG resource size which the terminal equipment expects the network equipment to configure; wherein,

if the fluctuation range of the traffic volume of the service to be transmitted of the terminal equipment is larger than the preset range, the CG resource size is the resource size required by the terminal equipment to report the BSR; if the fluctuation range of the traffic volume of the service to be transmitted of the terminal equipment is smaller than or equal to the preset range, the CG resource size is the traffic volume of the service to be transmitted; wherein the method comprises the steps of

The method further comprises the steps of:

when the uplink data arrives, the network equipment receives the uplink data according to the first CG configuration;

the method is applied to a non-terrestrial communication network NTN.

12. The method of claim 11, wherein the CG request information is carried in message 1 or message 3 during random access.

13. The method according to claim 11, wherein the CG request information is carried in radio resource control, RRC, signaling or medium access control, MAC, CE, cells when the terminal device is in a connected state.

14. The method according to claim 13, wherein the network device receiving the configuration grant CG request information sent by the terminal device includes:

The network device receives the CG request information sent by the terminal device when the following condition is satisfied:

the network device does not receive 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 receives the CG request information is greater than a preset time interval, where the preset time interval is the minimum time interval when the network device receives the CG request information twice.

15. The method according to claim 14, wherein the CG request information is for requesting the network device to update the second CG configuration for the terminal device, in case the network device has configured a second CG configuration for the terminal device.

16. The method according to claim 15, wherein the network device receiving the configuration grant CG request information sent by the terminal device includes:

the second CG configuration does not meet the transmission requirement of the service to be transmitted of the terminal equipment;

The network device does not receive 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 sends the CG request information is greater than a preset time interval, where the preset time interval is the minimum time interval when the network device receives the CG request information twice.

17. The method according to claim 15 or 16, 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, wherein the first RRC configuration information comprises the second CG configuration.

18. The method according to any one of claims 11 to 17, further comprising:

the network device sends second RRC configuration information to the terminal device, wherein the second RRC configuration information is used for configuring a CG request prohibition timer, and the CG request prohibition timer is used for limiting a minimum time interval for the terminal device to send CG request information twice.

19. A terminal device, comprising:

a communication unit, configured to send configuration authorization CG request information by a network device, where the CG request information is configured to request the network device to configure CG configuration for sending uplink data and/or a buffer status report BSR for the terminal device;

The communication unit is further configured to receive configuration information sent by the network device, where the configuration information includes a first CG configuration configured by the network device; wherein, the communication unit is specifically configured to:

when the terminal equipment has a service to be transmitted at the current moment or in a first time period after the current moment, sending the CG request information to the network equipment; 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; wherein,

the terminal device further comprises a processing unit:

the processing unit is configured to determine the CG resource period according to an arrival period of a service to be transmitted and/or a delay requirement of the service to be transmitted, and

the processing unit is used for determining the CG resource size according to the traffic of the service to be transmitted; wherein,

The communication unit is further configured to:

when the uplink data arrives, sending the uplink data according to the first CG configuration; wherein the method comprises the steps of

The terminal equipment is in a non-terrestrial communication network NTN.

20. Terminal device according to claim 19, characterized in that the communication unit is specifically adapted to:

and in the random access process, sending the CG request information to the network equipment.

21. The terminal device according to claim 20, wherein the CG request information is carried in message 1 or message 3 in the random access procedure.

22. The terminal device according to claim 19, wherein the CG request information is carried in radio resource control, RRC, signaling or medium access control, MAC, CE when the terminal device is in a connected state.

23. The terminal device according to claim 22, wherein the communication unit is specifically configured to:

transmitting the CG request information to the network device when:

the communication unit does not send CG request information to the network device, or a time interval between a current time and a time when the communication unit sends CG request information last time is greater than a preset time interval, where the preset time interval is a minimum time interval when the communication unit sends CG request information twice.

24. The terminal device according to claim 22, wherein the CG request information is for requesting the network device to update the second CG configuration for the terminal device, in case the network device has configured the second CG configuration for the terminal device.

25. Terminal device according to claim 24, characterized in that the communication unit is specifically adapted to:

transmitting the CG request information to the network device when:

26. The terminal device according to claim 24 or 25, wherein before the communication unit transmits CG request information to the network device, the communication unit is further configured to:

and receiving first RRC configuration information sent by the network equipment, wherein the first RRC configuration information comprises the second CG configuration.

27. The terminal device according to any of the claims 22 to 26, characterized in that the communication unit is further adapted to:

and receiving second RRC configuration information sent by the network equipment, wherein the second RRC configuration information is used for configuring a CG request prohibition timer, and the CG request prohibition timer is used for limiting the minimum time interval of the communication unit for sending the CG request information twice.

28. The terminal device according to claim 27, characterized in that the terminal device further comprises:

and the processing unit is used for starting or restarting the CG request prohibition timer when the CG request information is sent.

29. A network device, comprising:

a communication unit for receiving configuration authorization CG request information sent by a terminal device, wherein the CG request information is used for requesting

The network equipment is used for configuring CG configuration for sending uplink data and/or Buffer Status Report (BSR) for the terminal equipment;

the communication unit is further configured to send configuration information to the terminal device, where the configuration information includes a first CG configuration configured by the network device; wherein,

the network device further comprises a processing unit:

the processing unit is used for determining whether to configure CG configuration for the terminal equipment based on the CG request information;

The processing unit is further configured to: if the CG configuration is determined to be configured for the terminal equipment, determining the first CG configuration based on the CG request; wherein,

the communication unit is specifically configured to include:

when the terminal equipment has a service to be transmitted at the current moment or in a first time period after the current moment, receiving the CG request information sent by the terminal equipment; wherein,

the CG request information also comprises CG resource period and/or CG resource size which the terminal equipment expects the network equipment to configure;

if the fluctuation range of the traffic volume of the service to be transmitted of the terminal equipment is larger than the preset range, the CG resource size is the resource size required by the terminal equipment to report the BSR; if the fluctuation range of the traffic volume of the service to be transmitted of the terminal equipment is smaller than or equal to the preset range, the CG resource size is the traffic volume of the service to be transmitted; wherein the communication unit is further configured to:

when the uplink data arrives, receiving the uplink data according to the first CG configuration; wherein the method comprises the steps of

The network device is in a non-terrestrial communication network NTN.

30. The network device of claim 29, wherein the CG request information is carried in message 1 or message 3 during random access.

31. The network device of claim 29, wherein the CG request information is carried in radio resource control, RRC, signaling or medium access control, MAC, CE when the terminal device is in a connected state.

32. The network device according to claim 31, wherein the communication unit is specifically configured to:

receiving the CG request information sent by the terminal device when the following conditions are satisfied:

the communication unit does not receive 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 receives the CG request information is greater than a preset time interval, where the preset time interval is the minimum time interval when the communication unit receives the CG request information twice.

33. The network device of claim 31, wherein the CG request information is for requesting the network device to update a second CG configuration for the terminal device if the network device has configured the second CG configuration for the terminal device.

34. The network device of claim 33, wherein the communication unit is specifically configured to:

the communication unit does not receive 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 sends the CG request information is greater than a preset time interval, where the preset time interval is the minimum time interval when the communication unit receives the CG request information twice.

35. The network device according to claim 33 or 34, wherein before the communication unit receives the CG request information, the communication unit is further configured to:

and sending first RRC configuration information to the terminal equipment, wherein the first RRC configuration information comprises the second CG configuration.

36. The network device of any one of claims 31 to 35, wherein the communication unit is further configured to:

and sending second RRC configuration information to the terminal equipment, wherein the second RRC configuration information is used for configuring a CG request prohibition timer, and the CG request prohibition timer is used for limiting the minimum time interval of the terminal equipment for sending the CG request information twice.

37. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory, to perform the method according to any of claims 1 to 10.

38. A network device, comprising: a processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory for executing the method as claimed in claim 11 to claim 11

18.

39. An apparatus, comprising: a processor for calling and running a computer program from a memory, causing a chip-mounted device to perform the method of any one of claims 1 to 10.

40. An apparatus, comprising: a processor for calling and running a computer program from a memory, causing a chip-mounted device to perform the method of any of claims 11 to 18.

41. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 10.

42. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 11 to 18.