CN113632561A

CN113632561A - Resource configuration method, terminal equipment and network equipment

Info

Publication number: CN113632561A
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: 2021-11-09
Anticipated expiration: 2039-08-19
Also published as: CN113632561B; 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: a terminal device sends a CG request message for configuration authorization to a network device, wherein the CG request message is used for requesting the network device to configure a CG configuration for sending uplink data and/or a Buffer Status Report (BSR) for the terminal device; 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 device and the network device in the embodiment of the application can improve the flexibility of the system.

Description

Resource configuration method, terminal equipment and network equipment

Technical Field

The present application relates to the field of communications, and in particular, to a resource configuration method, a terminal device, and a network device.

Background

Currently, the third Generation Partnership Project (3 GPP) is studying Non-Terrestrial communication Network (NTN) technology, and the NTN generally provides communication services to Terrestrial users by means of satellite communication.

A New Radio (NR) system has a high requirement for flexibility, however, in an NTN system, the flexibility of a network device configuring resources for a terminal device is low at present. Therefore, how to improve the flexibility of the network device configuration resources in the NTN is an urgent problem to be solved.

Disclosure of Invention

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

In a first aspect, a method for resource configuration is provided, where the method includes: a terminal device sends a CG request message for configuration authorization to a network device, wherein the CG request message is used for requesting the network device to configure a CG configuration for sending uplink data and/or a Buffer Status Report (BSR) for the terminal device;

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 for resource configuration is provided, the method including: network equipment receives configuration authorization CG request information sent by terminal equipment, wherein the CG request information is used for requesting the network equipment to configure CG configuration for sending uplink data and/or 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.

In a third aspect, a terminal device is provided, configured to perform the method in the first aspect or each implementation manner thereof.

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

In a fourth aspect, a network device is provided for performing the method of the second aspect or its implementation manners.

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

In a fifth aspect, a terminal device is provided that includes 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 each implementation manner thereof.

In a sixth aspect, a network device is provided that includes 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 of the second aspect or each implementation mode thereof.

In a seventh aspect, an apparatus is provided for implementing the method in any one of the first to second aspects or implementations thereof.

Specifically, the apparatus includes: a processor configured to call and run the computer program from the memory, so that the apparatus on which the apparatus is installed performs the method according to any one of the first aspect to the second aspect or the implementation manner thereof.

Optionally, the device is a chip.

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

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

A tenth aspect provides a computer program that, 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 the CG configuration to the network equipment, so that the problem that the CG configuration is required to be configured by the terminal equipment but the network equipment is not configured can be avoided, the network equipment can flexibly configure the 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 diagram of a method for resource configuration according to an embodiment of the present application.

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

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

Fig. 6 is a schematic flowchart of a specific implementation of a method for 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 present application.

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

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, a LTE Frequency Division Duplex (FDD) System, a LTE Time Division Duplex (TDD) System, a Long Term Evolution (Advanced) System, a New Radio (NR) System, an Evolution System of an NR System, a to-be-unlicensed-spectrum (LTE-to-be-unlicensed-spectrum) System, a to-be-unlicensed-spectrum (NR) System, a GSM-to-be-unlicensed-spectrum (GSM) System, a CDMA-System, a WCDMA System, a GPRS-Radio (GPRS) System, a LTE-to-be-unlicensed-spectrum (LTE-to-be-unlicensed-spectrum, a LTE-to-be-unlicensed-spectrum (NR) System, a GSM-to-be-capable-spectrum (NR) System, a GSM-to-be-capable-spectrum (LTE-to-be-capable-free-spectrum (NR) System, UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Wireless Local Area Network (WLAN), Wireless Fidelity (WiFi), next generation communication system, or other communication system.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted 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 Public Land Mobile Network (PLMN) for future evolution, or the like.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a 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 another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment 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 (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

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

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

Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that a device having a communication function in a network/system in the embodiments 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 having a communication function, and the network device 110 and the terminal device 120 may be the 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 other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

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

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

Based on the current NR standard, when the terminal device has uplink data to arrive but the terminal device has no uplink resource for data transmission, as shown in fig. 2, the terminal device needs to go through 5 steps to transmit the uplink data to the network device.

210: the terminal device sends a 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. Therefore, the network device may allocate Physical Uplink Shared Channel (PUSCH) resources to the terminal device, where the resources are sufficient for the terminal device to send a Buffer Status Report (BSR).

230: the terminal equipment sends the BSR on the PUSCH resource allocated by the network equipment, thereby informing the network equipment of the size of the data volume which needs to be sent by the terminal equipment.

The BSR may be carried by a BSR Media Access Control (MAC) Control Element (CE).

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

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

As can be seen from fig. 2, the terminal device makes the network device know 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 the reporting overhead of the BSR, the terminal device may adopt a packet reporting mode when reporting the BSR. Each uplink Logical Channel may correspond to a Logical Channel Group (LCG), multiple uplink Logical channels may correspond to the same LCG, and a correspondence relationship between a Logical Channel and an LCG may be configured by a network device through Radio Resource Control (RRC) signaling. And the terminal equipment reports the BSR based on the LCG. Each terminal device in the NR can support up to 8 LCGs.

The triggering conditions for BSR are several:

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

2. The Padding (Padding) part of the uplink resource allocated to the terminal device after the terminal device has carried other uplink data may carry the BSR MAC CE, and in this case, the Padding BSR may be triggered.

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

4. The Periodic BSR Timer times out, at which time the Periodic BSR may be triggered.

If multiple logical channels trigger Regular BSRs simultaneously, each of these logical channels may trigger a separate Regular BSR.

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

As can also be seen from fig. 2, the terminal device applies for the uplink resource from 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 the SR. Therefore, the network device may allocate a periodic Physical Uplink Control Channel (PUCCH) resource for transmitting the SR to the terminal device, and then the network device may detect whether there is an SR report on the allocated SR resource.

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

When one uplink logical channel triggers SR, if the network device configures a PUCCH resource for SR transmission for the uplink logical channel, the terminal device may send the SR on the PUCCH resource for SR transmission 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 when uplink data arrives at the terminal device to when the terminal device sends 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, thereby causing a significant increase in service delay and affecting user experience.

In order to alleviate the problem of uplink service delay, NR introduces the concept of uplink grant-free transmission. The terminal device may transmit on a resource Configured with a Grant (CG) according to the service requirement.

Currently, NR supports two types of uplink unlicensed transmissions:

1. PUSCH transmission based on first Type configuration Grant (Configured Grant Type 1)

The network device configures, through RRC signaling, all transmission resources and transmission parameters including time domain resources, frequency domain resources, time domain resource periods, Modulation and Coding Scheme (MCS), repetition times, frequency hopping, HARQ (Hybrid Automatic Repeat Request) process number, and the like. After receiving the RRC configuration, the terminal device may immediately use the configured transmission parameters to perform PUSCH transmission on the configured time-frequency resources.

2. PUSCH (physical uplink shared channel) transmission based on second-Type configuration Grant (Configured Grant Type 2)

Type 2 adopts a two-step resource configuration mode: firstly, configuring transmission resources and transmission parameters including the period, the repetition times, the frequency hopping, the HARQ process number and the like of time domain resources by network equipment through RRC; and then activating a second type of PUSCH transmission based on configuration authorization by a Physical Downlink Control Channel (PDCCH) scrambled by using a Configured scheduled Radio Network Temporary Identifier (CS-RNTI), and simultaneously configuring other transmission resources and transmission parameters including time domain resources, frequency domain resources, MCS and the like. When receiving the RRC configuration parameters, the terminal device cannot immediately use the resources and parameters configured by the configuration parameters to perform PUSCH transmission, and must wait for receiving corresponding PDCCH activation and configuring other resources and parameters to perform PUSCH transmission.

If the terminal device has no data to transmit on the PUSCH resources of the first or second CG type, the terminal device will not transmit anything on the resources of the CG.

However, the CG configuration of the 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 does not, uplink traffic delay may be too large. For another example, if the network device configures a CG to the terminal device but the CG resource is too small, the delay may be increased; or, if CG resources are too large, system resources will be wasted.

In view of this, the present application provides a resource configuration method, which can improve the flexibility of configuring a CG for a terminal device by a network device.

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 diagram of a method 300 of resource configuration according to an embodiment of the present application. The method described in fig. 3 may be performed by a terminal device, such as terminal device 120 shown in fig. 1, and a network device, such as network device 110 shown in fig. 1.

It is understood that the method 300 may be applied in NTN. To enhance the understanding of the NTN, the following description will be made.

NTN technology generally provides communication services to terrestrial users by means of satellite communication. Satellite communications have many unique advantages over terrestrial cellular communications. First, satellite communication is not limited by the user region, and for example, general terrestrial communication cannot cover regions such as the sea, mountain, desert, and the like, and normal communication cannot be performed in these regions because communication equipment cannot be installed or communication coverage is not performed because of sparseness of population. For satellite communication, since one satellite can cover a large ground and the satellite can orbit the earth, theoretically every corner of the earth can be covered by satellite communication. Second, satellite communication has great social value. Satellite communication can be covered in remote mountainous areas, poor and laggard countries or areas with lower cost, so that people in the areas can enjoy advanced voice communication and mobile internet technology, the digital gap between the areas is favorably reduced and developed, and the development of the areas is promoted. Thirdly, the satellite communication distance is far, and the cost of communication is not obviously increased when the communication distance is increased. And finally, the satellite communication has high stability and is not limited by natural disasters.

Communication satellites may be classified into Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Orbit (GEO) satellites, High-elliptic Orbit (HEO) satellites, and the like, according to the height of the orbits. The main research in the present phase is the LEO satellite and GEO satellite, which are described below.

LEO satellites have an altitude ranging from 500km to 1500km, with a corresponding orbital period of about 1.5 hours to 2 hours. The signal propagation delay for inter-user single-hop communications is typically less than 20 ms. The maximum satellite visibility time is 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.

The GEO satellite had an orbital altitude of 35786km and a period of 24 hours of rotation around the earth. The signal propagation delay for inter-user single-hop communications is typically 250 ms.

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 dozens of or even hundreds of beams to cover the ground; one satellite beam may cover a ground area 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 communication, vehicle networking communication, and so on.

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

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

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

And 330, the terminal equipment receives configuration information sent by the network equipment, wherein the configuration information comprises the first CG configuration of the network equipment configuration.

Among other things, 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, when the terminal device has traffic to be transmitted at the current time or within a first time period after the current time, the terminal device may transmit CG request information to the network device.

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

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

It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone.

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

Example 1

The terminal device 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(Msg1) 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 configured by the network device desired by the terminal device.

The terminal device reports the expected CG resource period and/or the size of the CG resource to the network device, so that the problem that the CG resource configured by the network device is too large or too small can be avoided, and the CG configuration configured by the network device can better match the requirement of the terminal device. And at the same time, system resources can be more efficiently utilized.

The method 300 may further include: and the terminal equipment determines the CG resource period configured by the expected 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 configured by the network device expected by the terminal device may be 10 ms.

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

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

The traffic volume of the service to be transmitted may be historical traffic volume of the service to be transmitted. Illustratively, the historical traffic volume may be a historical average traffic volume over a period of time, for example, the traffic volume of the service to be transmitted may be a historical average traffic volume of the service to be transmitted over the last month. As another 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 service to be transmitted may be the traffic of the service to be transmitted estimated by the terminal device.

If the fluctuation range of the traffic of the service to be transmitted is greater than the preset range, that is, the fluctuation of the traffic of the service to be transmitted is relatively large, the CG resource size expected by the terminal device to be configured by the network device may be the resource size required by the terminal device to report the BSR. Thus, system resources can be saved.

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

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

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

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

In another possible embodiment, the preambles may be divided into N groups, with N being greater than 2. One group of N groups of preambles can be used for indicating that the terminal device is not configured with the requirement of CG configuration, and other N-1 groups of preambles in the N groups of preambles can be used for indicating the CG resource period and/or the CG resource size configured by the network device expected by the terminal device. Specifically, the terminal device and the network device may negotiate a CG resource period and/or a CG resource size expected by the terminal device and indicated by each of the other N-1 sets of preambles in the N sets of preambles in advance.

For example, the preambles are divided into 5 groups, which are the first group of preambles, the second group of preambles, the third group of preambles, the fourth group of preambles and the fifth group of preambles respectively. The method comprises the steps that a first group of preambles are negotiated in advance by the terminal equipment and the network equipment and used for indicating the requirement that the terminal equipment is not configured with CG configuration, a second group of preambles is used for indicating that the size of CG resources expected by the terminal equipment is X, a third group of preambles is used for indicating that the size of the CG resources expected by the terminal equipment is Y, a fourth group is used for indicating that the size of the CG resources expected by the terminal equipment is Z, and a fifth group of preambles is used for indicating that the size of the CG resources expected by the terminal equipment is W. And the terminal equipment sends the second group of preambles to the network equipment, and after the network equipment receives the second group of preambles, the terminal equipment can be determined to have the requirement for configuring the CG configuration, and the expected 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 to configure the CG configuration for the terminal device, the network device may configure the first CG configuration according to the CG request information. After that, the network device may send configuration information to the terminal device, where the configuration information includes the first CG configuration.

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

As an 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, it is not possible to allocate too many resources to a certain terminal device. Therefore, the network device may further determine whether to configure CG configuration for the terminal device, according to the occupation of system resources, fairness among terminal devices, priority of the service to be transmitted, and other factors. 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 resource is not enough to allocate CG resources to 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 the CG configuration request of the terminal device, the occupation condition of system resources, fairness between the terminal devices, priority of a service to be transmitted, and the like.

For example, if a large 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 resource size in the first CG configuration is the resource size required by the terminal device to report the BSR, when the terminal device has uplink data to reach and triggers the BSR, the terminal device may send the BSR to the network device on the CG resource configured by the network device. After receiving the BSR reported by the terminal device, the Network device may allocate an appropriate resource to the terminal device according to the data amount to be transmitted of the terminal device, and instruct the terminal device to complete PUSCH transmission through a dynamic scheduling signaling, such as a PDCCH scrambled by a 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 terminal device for transmitting the uplink data, when the terminal device has uplink data arriving, the terminal device may transmit the uplink data according to the first CG configuration.

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

The following describes an exemplary embodiment of embodiment 1 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 (RAR), to the terminal device.

And step 3: because the terminal device currently has a delay sensitive service, but the traffic fluctuation is large, the terminal device carries CG request information in Msg3(RRC connection establishment request message), indicating that the terminal device has a CG configuration requirement, and simultaneously, Msg3 also carries a CG resource period and a CG resource size expected by the terminal device.

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

And, the network device sends configuration information including the first CG configuration to the terminal device, the configuration information being carried in a random access Msg4(RRC connection setup message).

And 5: when uplink data arrives at the terminal equipment and a BSR is triggered, the terminal equipment sends the BSR on the CG resource closest to the current time.

Step 6: after receiving the BSR sent by the terminal equipment, the network equipment allocates a proper PUSCH resource 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.

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

It should be understood that, in 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 the CG configuration.

The terminal device may transmit the CG request information to the network device when the following condition is satisfied:

(1) the terminal equipment has a service to be transmitted at the current moment or in a future period of time in a forecast manner;

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

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

There may be two situations when the terminal device sends the CG request information twice: the terminal device transmits the CG request information and the network device receives the CG request information, or the terminal device transmits the CG request information but the network device does not receive the CG request information.

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

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

Alternatively, the preset time interval may be pre-configured by the network device to the terminal device. Illustratively, the network device may send the terminal device with second RRC configuration information, where the second RRC configuration information may be used to configure a CG request prohibit timer (CGRequestProhibitTimer), and the CG request prohibit timer is used to limit a minimum time interval between two transmissions of the CG request information by the terminal device.

In this case, for the case where the time interval between the current time and the time when the terminal device last transmitted the CG request information in the above-mentioned condition (3) is greater than the preset time interval, it can be understood that: the CG request prohibit timer has timed out. That is, the CG request prohibit timer is used to limit the minimum time interval between two transmissions of CG request information by the terminal device, and can be understood as: only in the case where the CG request prohibit timer has expired, the terminal apparatus may transmit the CG request information to the network apparatus again.

The terminal device may also maintain the CG request prohibit timer in a 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 the CG request information is transmitted.

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

The terminal device may determine a CG resource period configured by the network device expected by the terminal device 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 the CG resource size configured by the desired network device according to the traffic volume of the service to be transmitted.

Further, the network device may determine whether to configure CG configuration for the terminal device, according to the occupation of system resources, fairness between terminal devices, priority of the service to be transmitted, and other factors.

The following describes an exemplary embodiment of example 2 with reference to fig. 5.

Step 1: the network device sends second RRC configuration information to the terminal device, the second RRC configuration information being used for configuring the CG request prohibit timer, and the CG configuration is not included in the second RRC configuration information.

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

The terminal equipment determines the expected CG resource period of 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 size of the CG resource expected by the terminal equipment according to the traffic to be transmitted.

Further, the terminal device starts a CG request prohibit timer at the same time as the terminal device transmits CG request information to the network device.

And step 3: the CG configuration of the network device configuration is not received by the terminal device.

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

And 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 resource allocated by the network device.

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

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

And step 9: when the CG request prohibition timer times out, the terminal device transmits CG request information to the network device 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 the first CG configuration. The CG resource cycle and the CG resource size configured by the first CG are respectively the CG resource cycle and the CG resource size requested by the terminal equipment.

Step 11: and when the terminal equipment has uplink data, the terminal equipment transmits the uplink data on the CG resource closest to the current moment.

Example 3

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

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

Optionally, before the terminal device sends the CG request information to the network device, the network device may send 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 conditions are satisfied:

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

The second CG configuration does not meet the transmission requirement of the service to be transmitted, and may include but is not limited to at least one of the following cases:

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

case 2: the CG resource cycle 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 configured by the second CG cannot meet the transmission requirement of the service to be transmitted.

Alternatively, the preset time interval may be pre-configured by the network device to the terminal device. Illustratively, 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 case where the time interval between the current time and the time when the terminal device last transmitted the CG request information in the above-mentioned condition (3) is greater than the preset time interval, it can be understood that: the 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, that is, the first RRC configuration information includes the second CG configuration, and may also be used to configure the CG request prohibit timer.

After receiving the CG request message, the network device may determine whether to update the second CG configuration for the terminal device according to the CG request message. 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, according to the occupation of system resources, fairness among terminal devices, priority of the service to be transmitted, and other factors. If the network device determines to update the second CG configuration for the terminal device, the network device may further determine the updated first CG configuration in combination with factors such as an occupation condition of system resources, fairness among the terminal devices, priority of a service to be transmitted, and the like.

The method of example 3 is exemplified below with reference to fig. 6.

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

a) and configuring a second CG, wherein 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) The CG requests a prohibit timer.

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

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

And 4, step 4: and when the terminal equipment has uplink data, the terminal equipment transmits BSR to the network equipment by utilizing the CG resource in the second CG configuration.

And 5: the network equipment receives the BSR, acquires the uplink data volume information of the terminal equipment, allocates PUSCH resources to the terminal equipment in a dynamic scheduling mode according to the uplink data volume information provided by the terminal equipment, and indicates the resource allocation information to the terminal equipment.

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

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

And 8: the terminal device receives configuration information from the network device, wherein the configuration information comprises the first CG configuration. The CG resource cycle and the CG resource size configured by the first CG are respectively the CG resource cycle and the CG resource size requested by the terminal equipment.

And step 9: and when the terminal equipment has uplink data, the terminal equipment transmits the uplink data on the CG resource closest to the current moment.

In the technical solution of embodiment 3, when the CG configuration configured by the network device for the terminal device cannot meet the transmission requirement of the service to be transmitted of the terminal device, the terminal device sends information requesting for updating the CG configuration to the network device, so that the updated CG configuration of the network device can better meet the service requirement of the terminal device. And at the same time, system resources can be more efficiently utilized.

It should be understood that although embodiments 1-3 are described above separately, this does not mean that embodiments 1-3 are independent and that the descriptions of the various embodiments may be referred to one another. For example, the description related to embodiment 1 can be applied to embodiment 2 and embodiment 3. For the sake of brevity, the embodiments of the present application are not described more than necessary in 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 the CG configuration to the network equipment, so that the problem that the CG configuration is required to be configured by the terminal equipment but the network equipment is not configured can be avoided, the network equipment can flexibly configure the CG configuration for the terminal equipment, and the flexibility of a system can be improved.

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

For example, the various features described in the foregoing detailed description may be combined in any suitable manner without contradiction, and various combinations that may be possible are not described in this application in order to avoid unnecessary repetition.

For example, various embodiments of the present application may be arbitrarily combined with each other, and the same should be considered as the disclosure of the present application as long as the concept of the present application is not violated.

It should be understood that, in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Having described the method of resource allocation according to the embodiment of the present application in detail above, a communication apparatus according to the embodiment of the present application will be described below with reference to fig. 7 to 9, and the 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 of an embodiment of the present application. As shown in fig. 7, the terminal apparatus 400 includes:

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

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

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

Optionally, in this 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 400 desires to configure by the network device.

Optionally, in this 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 the service to be transmitted and/or a delay requirement of the service to be transmitted.

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

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

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

Optionally, in this 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 this 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 this embodiment of the present application, the CG request information is carried in message 1 or message 3 in the random access procedure

Optionally, in this 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 media access control element MAC CE.

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

the communication unit 410 has not sent the CG request message to the network device, or a time interval between a current time and a time when the communication unit 410 last sent the CG request message is greater than a preset time interval, where the preset time interval is a minimum time interval between two times of sending the CG request messages by the communication unit 410.

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

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

the communication unit 410 has not sent the CG request message to the network device, or a time interval between a current time and a time when the communication unit 410 last sent the CG request message is greater than a preset time interval, where the preset time interval is a minimum time interval between two times of sending the CG request message by the communication unit 410.

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

Optionally, in this embodiment of the present application, the communication unit 410 is further configured to: 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 times of sending the CG request information by the communication unit 410.

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

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

It should be understood that the terminal device 400 may correspond to the terminal device in the method 300, and corresponding operations of the terminal device in the method 300 may be implemented, which are not described herein again 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 authorization CG request information sent by a terminal device, where the CG request information is used to request that the network device 500 configures, for the terminal device, a CG configuration for sending uplink data and/or a buffer status report BSR;

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

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

Optionally, in this 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 this embodiment of the application, the communication unit 510 is specifically configured to include: and when the terminal equipment has a service to be transmitted at the current time or in a first time period after the current time, receiving the CG request information sent by the terminal equipment.

Optionally, in this 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 desires to configure by the network device.

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

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

Optionally, in this 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 this embodiment of the present application, the CG request information is carried in message 1 or message 3 in a random access procedure

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

the communication unit 510 does not receive the CG request information sent by the terminal device, or a time interval between a current time and a 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 a minimum time interval when the communication unit 510 receives the CG request information twice.

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

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

the communication unit 510 does not receive the CG request information sent by the terminal device, or a time interval between a current time and a time when the communication unit 510 last sent the CG request information is greater than a preset time interval, where the preset time interval is a minimum time interval between two times of receiving the CG request information by the communication unit 510.

Optionally, in this embodiment of the 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 this 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 sending the CG request information twice by the terminal equipment.

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 structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 shown in fig. 9 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 9, the communication device 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present 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 specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 630 may include a transmitter and a receiver, among others. The transceiver 630 may further include one or more antennas.

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

Optionally, the communication device 600 may specifically be a terminal device in the embodiment of the present application, and the communication device 600 may implement a corresponding process implemented by the terminal device in each method in the embodiment of the present application, which is not described herein again 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 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

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

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 transmitted 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 the other devices or chips.

Optionally, the apparatus may be applied to the terminal device in the embodiment of the present application, and the apparatus may implement the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the apparatus may be applied to the network device in the embodiment of the present application, and the apparatus may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

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

It should be understood that the processor of the embodiments 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 performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed 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 directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus 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 memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the 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 in 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 configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 820 may be configured to implement the corresponding function implemented by the network device in the foregoing method, which is not described herein again for brevity.

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

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

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

Embodiments of the present application also provide a computer program product comprising computer program instructions.

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

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

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

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 implementation. 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 is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into 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 such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by 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

A method of resource allocation, the method comprising:

a terminal device sends a CG request message for configuration authorization to a network device, wherein the CG request message is used for requesting the network device to configure a CG configuration for sending uplink data and/or a Buffer Status Report (BSR) for the terminal device;

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 method of claim 1, wherein the terminal device sends a configuration authorization (CG) request message to a network device, comprising:

and when the terminal equipment has service transmission at the current time or in a first time period after the current time, the terminal equipment sends the CG request information to the network equipment.
The method according to claim 1 or 2, wherein the CG request information further comprises CG resource period and/or CG resource size configured by the network device desired by the terminal device.
The method of claim 3, further comprising:

and 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 method according to claim 3 or 4, characterized in that the method further comprises:

and the terminal equipment determines the size of the CG resource according to the traffic of the service to be transmitted.
The method of claim 5, wherein if a fluctuation range of the traffic volume of the service to be transmitted is greater than a preset range, the CG resource size is a resource size required by the terminal device to report BSR.
The method of claim 5, wherein the CG resource size is the traffic volume of the service to be transmitted if a fluctuation range of the traffic volume of the service to be transmitted is less than or equal to a preset range.
The method of claim 7, further comprising:

and when the uplink data arrives, the terminal equipment sends the uplink data according to the first CG configuration.
The method according to any of claims 1 to 8, wherein the terminal device sends a configuration authorization (CG) request message to a network device, comprising:

and the terminal equipment sends the CG request information to the network equipment in the random access process.
The method of claim 9, wherein the CG request information is carried in message 1 or message 3 of the random access procedure.
The method according to any of claims 1 to 8, wherein the CG request information is carried in Radio Resource Control (RRC) signaling or Media Access Control (MAC) Control Element (CE) when the terminal device is in a connected state.
The method of claim 11, wherein the sending, by the terminal device, the CG request message to the network device comprises:

the terminal device sends the CG request information to the network device when the following conditions are met:

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

the terminal device does not send the CG request information to the network device, or the time interval between the current time and the time when the terminal device sends the 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 the CG request information twice.
The method of claim 11, wherein the CG request information is configured to request the network device to update the second CG configuration for the terminal device if the network device has configured the second CG configuration for the terminal device.
The method of claim 13, wherein the sending, by the terminal device, the CG request message to the network device comprises:

the terminal device sends the CG request information to the network device when the following conditions are met:

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

the terminal device does not send the CG request information to the network device, or the time interval between the current time and the time when the terminal device sends the 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 the CG request information twice.
The method according to claim 13 or 14, wherein before the terminal device sends CG request information to a network device, the method further comprises:

the terminal device receives first RRC configuration information sent by the network device, wherein the first RRC configuration information comprises the second CG configuration.
The method according to any one of claims 11 to 15, characterized in that it comprises:

the terminal device receives second RRC configuration information sent by the network 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 the minimum time interval of sending CG request information twice by the terminal device.
The method of claim 16, further comprising:

and the terminal equipment starts or restarts the CG request prohibition timer when the CG request information is sent.
The method according to any of claims 1 to 17, applied in a non-terrestrial communication network, NTN.
A method of resource allocation, the method comprising:

network equipment receives configuration authorization CG request information sent by terminal equipment, wherein the CG request information is used for requesting the network equipment to configure CG configuration for sending uplink data and/or 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.
The method of claim 19, further comprising:

and the network equipment determines whether to configure CG configuration for the terminal equipment or not based on the CG request information.
The method of claim 20, further comprising:

and 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.
The method according to any one of claims 19 to 21, wherein the network device receives configuration authorization, CG, request information sent by a terminal device, and comprises:

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, the network equipment receives the CG request information sent by the terminal equipment.
The method according to any of claims 19 to 22, wherein the CG request information further comprises CG resource period and/or CG resource size configured by the network device desired by the terminal device.
The method of claim 23, wherein if a fluctuation range of a traffic volume of a service to be transmitted of the terminal device is greater than a preset range, the CG resource size is a resource size required by the terminal device to report a BSR.
The method of claim 23, wherein the CG resource size is the traffic volume size of the service to be transmitted, 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 method of claim 25, further comprising:

and when the uplink data arrives, the network equipment receives the uplink data according to the first CG configuration.
The method according to any of claims 19 to 26, wherein the CG request information is carried in message 1 or message 3 in a random access procedure.
The method according to any of claims 19 to 26, 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 connected state.
The method of claim 28, wherein the network device receives a configuration authorization (CG) request message sent by a terminal device, and wherein the CG request message comprises:

when the following conditions are met, the network equipment receives the CG request information sent by the terminal equipment:

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

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 receives the CG request information last time is larger than a preset time interval, wherein the preset time interval is the minimum time interval when the network device receives the CG request information twice.
The method of claim 28, wherein the CG request information is configured to request the network device to update the second CG configuration for the terminal device if the network device has configured the second CG configuration for the terminal device.
The method of claim 30, wherein the network device receives a configuration authorization (CG) request message sent by a terminal device, and comprises:

when the following conditions are met, the network equipment receives the CG request information sent by the terminal equipment:

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 sends the CG request information last time is larger than a preset time interval, wherein the preset time interval is the minimum time interval when the network device receives the CG request information twice.
The method of claim 30 or 31, wherein before the network device receives the CG request message, 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.
The method of any one of claims 28 to 32, further comprising:

the network device sends second RRC configuration information to the terminal device, 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 sending CG request information twice by the terminal device.
A terminal device, comprising:

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

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

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, sending the CG request information to the network equipment.
The terminal device according to claim 34 or 35, wherein the CG request information further comprises CG resource period and/or CG resource size that the terminal device expects the network device to configure.
The terminal device of claim 36, wherein the terminal device further comprises:

and the processing unit is used for determining 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 device according to claim 36 or 37, wherein the terminal device further comprises:

and the processing unit is used for determining the size of the CG resource according to the traffic of the service to be transmitted.
The terminal device of claim 38, wherein if a fluctuation range of the traffic volume of the service to be transmitted is greater than a preset range, the CG resource size is a resource size required by the terminal device to report BSR.
The terminal device of claim 38, wherein the CG resource size is the traffic volume size of the service to be transmitted, if the fluctuation amplitude of the traffic volume of the service to be transmitted is less than or equal to a preset amplitude.
The terminal device of claim 40, wherein the communication unit is further configured to:

and when the uplink data arrives, sending the uplink data according to the first CG configuration.
The terminal device according to any of claims 34 to 41, wherein the communication unit is specifically configured to:

and in the random access process, sending the CG request information to the network equipment.
The terminal device of claim 42, wherein the CG request information is carried in message 1 or message 3 of the random access procedure.
The terminal device according to any of claims 34 to 41, wherein the CG request information is carried in radio resource control, RRC, signaling or media Access control, MAC, CE when the terminal device is in a connected state.
The terminal device of claim 44, wherein the communication unit is specifically configured to:

transmitting the CG request information to the network device when the following conditions are satisfied:

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

the communication unit does not send the CG request information to the network device, or the time interval between the current time and the time when the communication unit sends the CG request information last time is larger than a preset time interval, wherein the preset time interval is the minimum time interval when the communication unit sends the CG request information twice.
The terminal device of claim 44, wherein the CG request information is configured to request the network device to update the second CG configuration for the terminal device if the network device has configured the second CG configuration for the terminal device.
The terminal device of claim 46, wherein the communication unit is specifically configured to:

transmitting the CG request information to the network device when the following conditions are satisfied:

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

the communication unit does not send the CG request information to the network device, or the time interval between the current time and the time when the communication unit sends the CG request information last time is larger than a preset time interval, wherein the preset time interval is the minimum time interval when the communication unit sends the CG request information twice.
The terminal device according to claim 46 or 47, wherein before the communication unit sends CG request information to the network device, the communication unit is further configured to:

receiving first RRC configuration information sent by the network equipment, wherein the first RRC configuration information comprises the second CG configuration.
The terminal device according to any of claims 44-48, wherein the communication unit is further configured 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 sending CG request information twice by the communication unit.
The terminal device of claim 49, wherein 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.
The terminal device according to any of claims 34-50, wherein the terminal device is in a non-terrestrial communication network (NTN).
A network device, comprising:

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

the communication unit is further configured to send configuration information to the terminal device, where the configuration information includes a first CG configuration configured by the network device.
The network device of claim 52, wherein the network device further comprises:

and the processing unit is used for determining whether the CG configuration is configured for the terminal equipment or not based on the CG request information.
The network device of claim 53, wherein the processing unit 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.
The network device according to any of claims 52 to 54, wherein the communication unit is specifically configured to include:

and when the terminal equipment has a service to be transmitted at the current time or in a first time period after the current time, receiving the CG request information sent by the terminal equipment.
The network device according to any of claims 52 to 55, wherein the CG request information further comprises a CG resource period and/or a CG resource size that the terminal device expects the network device to configure.
The network device of claim 56, wherein the CG resource size is a resource size required by the terminal device to report BSR if a fluctuation range of a traffic volume of a service to be transmitted of the terminal device is greater than a preset range.
The network device according to claim 56, wherein the CG resource size is the traffic volume size of the service to be transmitted, 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 network device of claim 58, wherein the communication unit is further configured to:

and when the uplink data arrives, receiving the uplink data according to the first CG configuration.
The network device of any of claims 52 to 59, wherein the CG request information is carried in message 1 or message 3 in a random access procedure.
The network device according to any of claims 52 to 59, wherein the CG request information is carried in radio resource control, RRC, signaling or media Access control, MAC, CE when the terminal device is in a connected state.
The network device of claim 61, wherein the communication unit is specifically configured to:

receiving the CG request information sent by the terminal equipment when the following conditions are met:

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

the communication unit does not receive the CG request information sent by the terminal equipment, or the time interval between the current time and the time when the communication unit receives the CG request information last time is larger than a preset time interval, wherein the preset time interval is the minimum time interval when the communication unit receives the CG request information twice.
The network device of claim 61, wherein the CG request information is configured to request the network device to update the second CG configuration for the terminal device if the network device has configured the second CG configuration for the terminal device.
The network device of claim 63, wherein the communication unit is specifically configured to:

receiving the CG request information sent by the terminal equipment when the following conditions are met:

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

the communication unit does not receive the CG request information sent by the terminal equipment, or the time interval between the current time and the time when the communication unit sends the CG request information last time is larger than a preset time interval, wherein the preset time interval is the minimum time interval when the communication unit receives the CG request information twice.
The network device of claim 63 or 64, wherein before the communication unit receives the CG request message, 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.
The network device of any one of claims 61-65, 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 sending CG request information twice by the terminal equipment.
A terminal device, comprising: a processor and a memory, the memory for storing a computer program, the processor for invoking and executing the computer program stored in the memory, performing the method of any one of claims 1 to 18.
A network device, comprising: a processor and a memory, the memory for storing a computer program, the processor for invoking and executing the computer program stored in the memory, performing the method of any one of claims 19 to 33.
An apparatus, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 18.
An apparatus, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 19 to 33.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 18.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 19 to 33.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 18.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 19 to 33.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 18.
A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 19-33.