An uplink pre-scheduling method and a base station

Abstract

The application discloses an uplink pre-scheduling method and a base station. The method and the base station determine a pre-scheduling attribute of a terminal device based on a service state of the terminal device, and in response to the pre-scheduling attribute of the terminal device being a second attribute, avoid performing uplink pre-scheduling processing on the terminal device, wherein the second attribute represents that the terminal device currently does not have a pre-scheduling requirement. The application determines the pre-scheduling attribute corresponding to the terminal device based on the service state of the terminal device, and in the pre-scheduling processing, filters out the terminal device whose pre-scheduling attribute represents that the terminal device currently does not have a pre-scheduling requirement, thereby avoiding pre-scheduling processing on all terminal devices in a cell, reducing waste of pre-scheduling resources of the base station, reducing the data volume of invalid uplink data, and avoiding lifting of interference noise.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to an uplink pre-scheduling method and a base station. BACKGROUND

[0002] In the current 5G (5th Generation Mobile Communication Technology) system, for time-sensitive services, various manufacturers mostly use an uplink pre-scheduling scheme to reduce service latency.

[0003] The traditional pre-scheduling scheme performs pre-scheduling processing on all time-sensitive service UEs (User Equipment) in a cell, and the applicant finds that the pre-scheduling scheme at least has the following problems:

[0004] a. Wasting limited pre-scheduling resources of a base station, resulting in that a UE (User Equipment) that truly needs pre-scheduling often cannot be pre-scheduled in time;

[0005] b. When the uplink pre-scheduling mechanism is started, if a UE has no real data to send, it will send PADDING (padding) data, so that the amount of invalid data sent in uplink increases, and then it may cause the interference noise (IoT) to rise. SUMMARY

[0006] Therefore, the present application discloses the following technical solutions:

[0007] An uplink pre-scheduling method, comprising:

[0008] determining a pre-scheduling attribute of a terminal device based on a service state of the terminal device;

[0009] in response to the pre-scheduling attribute of the terminal device being a second attribute, avoiding performing uplink pre-scheduling processing on the terminal device;

[0010] the second attribute represents that the terminal device currently has no pre-scheduling demand.

[0011] Optionally, the method further comprises:

[0012] in response to the pre-scheduling attribute of the terminal device being a first attribute, performing uplink pre-scheduling processing on the terminal device;

[0013] the first attribute represents that the terminal device currently has pre-scheduling demand.

[0014] Optionally, the process of determining the service state of the terminal device comprises:

[0015] determining a downlink data type corresponding to downlink data of the terminal device when scheduling downlink new transmission data for the terminal device;

[0016] determining a service state of the terminal device based on the downlink data type; the service state being a first state indicating that the terminal device has initiated a service or a second state indicating that the terminal device has not initiated a service.

[0017] Optionally, the determining of the pre-scheduling attribute of the terminal device based on the service state of the terminal device comprises:

[0018] determining that the pre-scheduling attribute of the terminal device is the first attribute based on the service state of the terminal device being the first state;

[0019] determining that the pre-scheduling attribute of the terminal device is the second attribute based on the service state of the terminal device being the second state.

[0020] Optionally, the performing of the uplink pre-scheduling processing on the terminal device comprises:

[0021] obtaining a pre-scheduling control parameter configured and pre-scheduling context information corresponding to the terminal device;

[0022] determining a pre-scheduling execution parameter required for performing the uplink pre-scheduling processing on the terminal device according to at least one of the pre-scheduling control parameter and the pre-scheduling context information;

[0023] performing the uplink pre-scheduling processing on the terminal device according to the pre-scheduling execution parameter.

[0024] Optionally, the determining of the pre-scheduling execution parameter required for performing the uplink pre-scheduling on the terminal device according to at least one of the pre-scheduling control parameter and the pre-scheduling context information comprises:

[0025] determining a pre-scheduling occasion for performing the uplink pre-scheduling on the terminal device and adjustment information of a buffer occupancy value corresponding to the terminal device in the uplink pre-scheduling processing according to at least one of the pre-scheduling control parameter and the pre-scheduling context information.

[0026] Optionally, the pre-scheduling control parameter comprises at least part of a pre-configured pre-scheduling upper limit value, a pre-scheduling interval and a pre-scheduling data volume; and the pre-scheduling context information at least comprises a current actual pre-scheduling number of the terminal device.

[0027] The determining of the pre-scheduling occasion for performing the uplink pre-scheduling on the terminal device and the adjustment information of the buffer occupancy value corresponding to the terminal device in the uplink pre-scheduling processing according to at least one of the pre-scheduling control parameter and the pre-scheduling context information comprises:

[0028] In a case that the actual pre-scheduling number is less than the upper limit of the pre-scheduling number, a pre-scheduling occasion of a next uplink pre-scheduling processing to be performed by the terminal device is determined according to the actual pre-scheduling number and a pre-scheduling interval in the pre-scheduling control parameter;

[0029] An adjustment information of a buffer occupancy value corresponding to the terminal device in the uplink pre-scheduling processing is determined according to a pre-scheduling data amount in the pre-scheduling control parameter.

[0030] Optionally, the performing the uplink pre-scheduling processing on the terminal device according to the pre-scheduling execution parameter comprises:

[0031] triggering the uplink pre-scheduling processing on the terminal device at the pre-scheduling occasion;

[0032] adjusting the buffer occupancy value corresponding to the terminal device according to the adjustment information in the uplink pre-scheduling processing, so as to perform uplink resource allocation on the terminal device based on the adjusted buffer occupancy value in the uplink scheduling on the terminal device;

[0033] updating the pre-scheduling context information corresponding to the terminal device.

[0034] Optionally, in a case that the pre-scheduling attribute of the terminal device is the first attribute, the method further comprises:

[0035] ending the uplink pre-scheduling processing on the terminal device and adjusting the pre-scheduling attribute of the terminal device to the second attribute based on detecting that the uplink pre-scheduling processing on the terminal device meets a preset ending condition;

[0036] wherein, the ending condition is met including at least one of the following conditions:

[0037] the uplink pre-scheduling number on the terminal device reaches a set upper limit of the pre-scheduling number;

[0038] receiving uplink data sent by the terminal device.

[0039] A base station comprises:

[0040] a memory configured to store at least a set of instructions;

[0041] a processor configured to invoke and execute the set of instructions in the memory, and realize the uplink pre-scheduling method according to any one of the above by executing the set of instructions.

[0042] To sum up, the uplink pre-scheduling method and the base station disclosed in the application determine the pre-scheduling attribute of the terminal device based on the service state of the terminal device, and in response to the pre-scheduling attribute of the terminal device being the second attribute, the uplink pre-scheduling processing of the terminal device is avoided, wherein the second attribute represents that the terminal device currently does not have a pre-scheduling requirement. In the application, the pre-scheduling attribute corresponding to the terminal device is determined based on the service state of the terminal device, and in the pre-scheduling processing, the terminal device whose pre-scheduling attribute represents that it currently does not have a pre-scheduling requirement is filtered out, so as to avoid pre-scheduling processing of all terminal devices in the cell, thereby reducing the waste of pre-scheduling resources of the base station, reducing the data amount of invalid uplink data, and avoiding the lifting of interference noise. BRIEF DESCRIPTION OF DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are only embodiments of the application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of the provided drawings.

[0044] Figure 1 is a pre-scheduling principle diagram of uplink pre-scheduling;

[0045] Figure 2 is a flowchart of the uplink pre-scheduling method provided by the embodiment of the application;

[0046] Figure 3 is a flowchart of determining the pre-scheduling attribute of the terminal device provided by the embodiment of the application;

[0047] Figure 4 is another flowchart of the uplink pre-scheduling method provided by the embodiment of the application;

[0048] Figure 5 is a processing flowchart of performing uplink pre-scheduling processing on the terminal device provided by the embodiment of the application;

[0049] Figure 6 is another flowchart of the uplink pre-scheduling method provided by the embodiment of the application;

[0050] Figure 7 is a pre-scheduling timing of UE in a 2.5 ms double-period frame structure provided by the embodiment of the application;

[0051] Figure 8 is a pre-scheduling processing diagram of UE in a factory flow line-oriented service scenario provided by the embodiment of the application;

[0052] Figure 9 is a component structure diagram of the base station provided by the embodiment of the application. Detailed Implementation

[0053] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0054] The UE's uplink data transmission process is as follows: When the UE needs to transmit uplink data, it sends an SR (Scheduling Request) to the base station. After receiving the SR, the base station allocates certain resources for the UE to send a BSR (Buffer Status Report). The UE sends the BSR, reporting the range of data volume to be transmitted to the base station. Based on the data volume reported by the UE, the base station allocates appropriate resources for the UE to transmit data. In current 5G systems, for latency-sensitive services, various manufacturers typically adopt uplink pre-scheduling schemes to reduce service latency. Uplink pre-scheduling means that the user terminal does not need to go through the scheduling request and buffer status report process to apply for uplink resources from the base station to transmit uplink data. Instead, the base station pre-sends an uplink authorization to the UE (the uplink authorization indicates the uplink resources that the UE can use to transmit uplink data). The UE directly transmits data through the pre-allocated uplink resources. Specifically, as follows... Figure 1 As shown.

[0055] The applicant found that in traditional pre-scheduling schemes, base stations cannot effectively determine pre-scheduling strategies for different UEs. Instead, based on the low latency requirements of latency-sensitive services, they perform indiscriminate pre-scheduling processing on all UEs of latency-sensitive services (such as all UEs in a cell covering a factory assembly line service of a private network base station). This results in a waste of base station pre-scheduling resources, as well as an increase in the amount of invalid data transmitted uplink and an increase in interference noise.

[0056] Therefore, this application discloses an uplink pre-scheduling method and a base station to solve at least some of the technical problems of traditional pre-scheduling schemes. This method can be applied to base stations, and the base station using this method can be a public network base station or a private network base station, without limitation. The public network base station or private network base station uses this method to execute an uplink pre-scheduling process based on pre-scheduling judgment for UEs (UEs of time-latency sensitive services) within its covered cell area.

[0057] The processing procedure of the uplink pre-scheduling method disclosed in this application is as follows: Figure 2 As shown, it specifically includes:

[0058] Step 201, determining a pre-scheduling attribute of the terminal device based on a service state of the terminal device.

[0059] The terminal device is UE, and can be, but is not limited to, a smart phone, a tablet computer, a telephone watch and the like of various types which can communicate with a corresponding base station through a mobile network (such as 4G / 5G and the like).

[0060] Further, the terminal device in the embodiment of the application is a terminal device in a time delay sensitive service scenario.

[0061] The pre-scheduling attribute of the terminal device is a first attribute representing that the terminal device in the time delay sensitive service scenario currently has a pre-scheduling requirement, or a second attribute representing that the terminal device in the time delay sensitive service scenario currently does not have a pre-scheduling requirement.

[0062] That is, in actual application, for a service scenario facing multiple UEs and being time delay sensitive, such as a factory pipeline service scenario facing multiple UEs, through the method of the application, an uplink pre-scheduling process based on pre-scheduling judgment can be performed on each UE in the scenario. In the uplink pre-scheduling process based on the method of the application, first, the service state of the terminal device is determined, and then the pre-scheduling attribute of the terminal device is determined according to the service state of the terminal device, see Figure 3 The process can be further implemented as:

[0063] Step 301, when scheduling downlink new transmission data for the terminal device, determining a downlink data type corresponding to downlink data of the terminal device.

[0064] Step 302, determining a service state of the terminal device based on the corresponding downlink data type; the service state of the terminal device is a first state representing that the terminal device has initiated a service or a second state representing that the terminal device has not initiated a service.

[0065] Applicant has found that in the three transmission modes AM (acknowledgment mode), UM (non-acknowledgment mode) and TM (transparent mode) of the RLC layer of the UE, the same mode is adopted at any time for uplink and downlink, that is, the uplink and downlink modes of the UE RLC are equal, and the service in this scenario is initiated by the UE. Based on this, the embodiment of the application determines the service state of the UE, that is, whether the UE initiates a service, through the downlink data type of the RLC of the UE.

[0066] Specifically, when scheduling downlink new data transmission for the UE, it is determined whether the RLC downlink data of the UE is of the DATA type in the AM mode (the RLC is usually configured in the AM mode during actual service). If the RLC downlink data of the UE is of the DATA type in the AM mode, it indicates that the UE has initiated service, and the UE needs to be preferentially scheduled to guarantee low service latency. Accordingly, the service state of the UE is determined as a first state indicating that the UE has initiated service. Conversely, if the RLC downlink data of the UE is not of the DATA type in the AM mode, the service state of the UE is determined as a second state indicating that the UE has not initiated service.

[0067] In step 303, based on the service state of the terminal device being the first state, the pre-scheduling attribute of the terminal device is determined as the first attribute.

[0068] In step 304, based on the service state of the terminal device being the second state, the pre-scheduling attribute of the terminal device is determined as the second attribute.

[0069] If the service state of the UE is the first state, it indicates that the UE has initiated service. Accordingly, the pre-scheduling attribute of the UE (for example, a certain UE in a factory pipeline service scenario) is determined as the first attribute indicating that the UE currently has a pre-scheduling requirement. Conversely, if the service state of the UE is the second state, it indicates that the UE has not initiated service. In this case, the pre-scheduling attribute of the UE is determined as the second attribute indicating that the UE currently does not have a pre-scheduling requirement.

[0070] Optionally, in an embodiment, a linked list, referred to as a pre-scheduling linked list in this embodiment, can be created, and the identifier of the UE with the first state (i.e., having a pre-scheduling requirement) is put into the pre-scheduling linked list. The UE with the second state (i.e., not having a pre-scheduling requirement) is not added to the pre-scheduling linked list. Specifically, but not limited to, the C-RNTI (Cell-Radio Network Temporary Identifier, cell radio network temporary identifier) of the UE can be put into the pre-scheduling linked list, and the information of each UE having a pre-scheduling requirement is stored and managed through the pre-scheduling linked list.

[0071] For the UE added to the pre-scheduling linked list, the pre-scheduling attribute of the UE is defaulted as the first attribute. For the UE not added to the pre-scheduling linked list, the pre-scheduling attribute of the UE is defaulted as the second attribute.

[0072] But not limited to this, in other embodiments, the corresponding attribute value can also be directly configured / associated for the UE to indicate whether the UE has a pre-scheduling requirement.

[0073] In step 202, in response to the pre-scheduling attribute of the terminal device being the second attribute, uplink pre-scheduling processing is avoided for the terminal device.

[0074] If it is determined that the pre-scheduling attribute of the UE is the second attribute representing that the UE currently does not have a pre-scheduling requirement, the UE is not subjected to the uplink pre-scheduling processing in response to the second attribute of the UE, that is, in the pre-scheduling processing, the UE with the pre-scheduling attribute of the second attribute is filtered out to avoid the uplink pre-scheduling of the UE, such as avoiding the uplink pre-scheduling of the UE not added to the pre-scheduling linked list in the factory pipeline service scenario or avoiding the uplink pre-scheduling of the UE with the configured attribute value of the second attribute, so as to save the pre-scheduling resource of the base station.

[0075] In summary, the method of the embodiment of the application determines the pre-scheduling attribute of the terminal device based on the service state of the terminal device, and avoids the uplink pre-scheduling processing of the terminal device in response to the pre-scheduling attribute of the terminal device being the second attribute, where the second attribute represents that the terminal device currently does not have a pre-scheduling requirement. The application determines the pre-scheduling attribute corresponding to the terminal device based on the service state of the terminal device, and filters out the terminal device with the pre-scheduling attribute representing that the terminal device currently does not have a pre-scheduling requirement in the pre-scheduling processing, so as to avoid the pre-scheduling processing of all terminal devices in the cell, thereby reducing the waste of the pre-scheduling resource of the base station, reducing the data amount of the invalid uplink data, and avoiding the lifting of the interference noise.

[0076] In an embodiment, referring to Figure 4 The uplink pre-scheduling method flowchart provided by the application can further include the following processing:

[0077] Step 203, in response to the pre-scheduling attribute of the terminal device being the first attribute, performing the uplink pre-scheduling processing on the terminal device.

[0078] The first attribute represents that the terminal device, i.e., the UE, currently has a pre-scheduling requirement.

[0079] In response to the pre-scheduling attribute of the UE being the first attribute, performing the uplink pre-scheduling processing on the UE, such as performing the uplink pre-scheduling on the UE added to the pre-scheduling linked list in the factory pipeline service scenario or performing the uplink pre-scheduling on the UE with the configured attribute value of the first attribute, referring to Figure 5 The process can be further implemented as:

[0080] Step 501, obtaining the configured pre-scheduling control parameter and the pre-scheduling context information corresponding to the terminal device.

[0081] The pre-scheduling control parameter includes, but is not limited to, at least part of parameters of a pre-scheduling times upper limit value, a pre-scheduling interval and a pre-scheduling data volume pre-configured by the base station for each UE in the same service scenario based on service characteristics. The pre-scheduling times upper limit value refers to a maximum number of times of uplink pre-scheduling allowed by the base station to perform on the UE in one pre-scheduling event of each UE. In the pre-scheduling control parameter, each pre-scheduling corresponding to the pre-scheduling times upper limit value is configured with a corresponding pre-scheduling interval and a pre-scheduling data volume. The pre-scheduling intervals corresponding to different pre-scheduling times can be the same or different, and similarly, the pre-scheduling data volumes corresponding to different pre-scheduling times can be the same or different, and no limitation is made in this regard. In the same case, the pre-scheduling intervals and the pre-scheduling data volumes corresponding to different pre-scheduling times can be uniformly configured.

[0082] The pre-scheduling context information of the UE at least includes the actual pre-scheduling times of the UE at present, and in addition, can include, but is not limited to, the pre-scheduling interval, the pre-scheduling data volume and other information corresponding to each pre-scheduling.

[0083] In the embodiment based on the pre-scheduling linked list, the pre-scheduling context information corresponding to the UE can be optionally written into the linked list for storage, and is associated with the corresponding UE identifier in the linked list. The UE with pre-scheduling demand and the pre-scheduling context information corresponding thereto are stored and managed through the linked list.

[0084] Step 502, determining the pre-scheduling execution parameter required for performing the uplink pre-scheduling processing on the terminal device according to at least one of the obtained pre-scheduling control parameter and the pre-scheduling context information.

[0085] Optionally, after the base station is normally started, in response to the pre-scheduling attribute of the UE being the first attribute, the pre-scheduling control parameter of the UE configured by the base station and the pre-scheduling context information corresponding to the UE are obtained, and the pre-scheduling occasion for performing the uplink pre-scheduling on the UE and the adjustment information of the BO (Buffer Occupy, buffer occupancy value) of the UE in the uplink pre-scheduling processing are determined according to at least one of the pre-scheduling control parameter and the pre-scheduling context information, to obtain the pre-scheduling execution parameter required for performing the uplink pre-scheduling on the UE.

[0086] Further, in a case that the actual pre-scheduling number of times to the UE is less than the upper limit value of the pre-scheduling number of times in the pre-scheduling control parameter, a pre-scheduling interval to be used by the next to-be-executed uplink pre-scheduling processing is determined according to the actual pre-scheduling number of times to the UE, and a pre-scheduling occasion of the next to-be-executed uplink pre-scheduling processing to the UE is determined based on the pre-scheduling interval to be used. Specifically, the pre-scheduling time slot of the UE can be calculated according to the corresponding pre-scheduling interval, and used as the pre-scheduling occasion of the UE. In a pre-scheduling event to the UE, if it is the first pre-scheduling, the corresponding pre-scheduling interval refers to the uplink scheduling number of times from when the UE is put into the pre-scheduling linked list (or from when the pre-scheduling attribute of the UE is configured as the first attribute) to the first pre-scheduling, otherwise, if it is not the first pre-scheduling, the corresponding pre-scheduling interval refers to the uplink scheduling number of times between the last pre-scheduling and the next to-be-executed pre-scheduling (i.e., the current to-be-executed pre-scheduling).

[0087] Meanwhile, according to the corresponding pre-scheduling data amount in the pre-scheduling control parameter, adjustment information of the corresponding BO value of the UE in the current to-be-executed uplink pre-scheduling processing is determined, so as to realize adjustment of the corresponding BO value of the UE.

[0088] Step 503, performing uplink pre-scheduling processing on the terminal device according to the determined pre-scheduling execution parameter.

[0089] After that, the uplink pre-scheduling processing is performed on the terminal device according to the determined pre-scheduling execution parameter.

[0090] Specifically, it is determined whether the current uplink scheduling time slot is consistent with the pre-scheduling time slot of the UE calculated in the pre-scheduling execution parameter. If they are consistent, the current uplink scheduling time slot is the pre-scheduling time slot of the UE, and the uplink pre-scheduling process of the UE is triggered at this time slot to perform the uplink pre-scheduling of the UE, including but not limited to: adjusting the corresponding BO value of the UE according to the adjustment information of the BO value of the UE in the pre-scheduling execution parameter, so as to allocate uplink resources to the UE based on the adjusted BO value in the uplink scheduling of the UE, and updating the pre-scheduling context information corresponding to the UE.

[0091] The adjusted BO value represents the estimated amount of subsequent uplink data to be transmitted by the UE, and is used as the basis for the base station to allocate and allocate uplink resources to the UE in the subsequent uplink scheduling stage (after the uplink pre-scheduling of the UE is completed, the uplink scheduling stage of the UE is entered). Optionally, the adjusted BO value can be the corresponding pre-scheduling data amount in the pre-scheduling control parameter, or it can have a certain redundancy compared to the pre-scheduling data amount, which is not limited in this regard.

[0092] The update of the pre-scheduling context information corresponding to the UE at least includes the update of the actual pre-scheduling times of the UE currently, and in addition, the pre-scheduling time slot and the pre-scheduling data volume corresponding to the uplink pre-scheduling of the current time can be added to the pre-scheduling context information.

[0093] After adjusting the BO value corresponding to the UE, the base station enters the scheduling stage of the UE, and in the scheduling stage, the required resource volume is divided and allocated to the UE according to the adjusted BO value corresponding to the UE, and the UE is waited to send uplink data based on the allocated resources, without the UE applying for uplink resources for uplink data transmission to the base station through the processes of scheduling request, buffer status report, etc.

[0094] The resources allocated by the base station to the UE for uplink data transmission based on the adjusted BO value include but are not limited to CCE (Control Channel Element), RB (Resource Block) and other uplink resources.

[0095] The embodiment realizes targeted uplink pre-scheduling of only the terminal device with pre-scheduling demand by responding to the first attribute of the pre-scheduling attribute of the terminal device, and avoids uplink pre-scheduling of the terminal device with the second attribute, thereby reducing the waste of pre-scheduling resources of the base station, reducing the data volume of invalid uplink data, and avoiding the lifting of interference noise.

[0096] In an embodiment, referring to Figure 6 The uplink pre-scheduling method provided by the embodiment can further include the following processing:

[0097] In step 204, based on detecting that the uplink pre-scheduling processing of the terminal device meets the preset end condition, the uplink pre-scheduling processing of the terminal device is ended, and the pre-scheduling attribute of the terminal device is adjusted to the second attribute.

[0098] The specific judgment can be whether the current uplink pre-scheduling times of the UE reaches the pre-scheduling times upper limit value in the pre-scheduling control parameter, and / or whether the uplink data sent by the UE is received. If the current uplink pre-scheduling times of the UE reaches the pre-scheduling times upper limit value, and / or the uplink data sent by the UE is received, it is determined that the uplink pre-scheduling processing of the terminal device meets the end condition.

[0099] In response to the uplink pre-scheduling process for the UE meeting the termination condition, the uplink pre-scheduling process for the UE ends, and the UE's pre-scheduling attribute is adjusted from the first attribute to the second attribute. Optionally, the attribute adjustment for the UE can be achieved by removing the UE's identifier from the pre-scheduling list, or by modifying / updating the pre-scheduling attribute value of the UE. There are no restrictions on this.

[0100] For example, see Figure 7 In a 2.5ms dual-cycle frame structure (one radio frame is 10ms), Figure 7 In a complete frame structure (where the horizontal axis represents a time slot, and one coordinate point represents one time slot), when configuring the 30kHz subcarrier spacing, if the pre-scheduling interval corresponding to the first pre-scheduling is set to 2 (referring to the interval for uplink scheduling, i.e., there are two uplink scheduling events in between), and the pre-scheduling interval corresponding to the second pre-scheduling is set to 1, with a maximum of 2 pre-scheduling events, if the UE triggers the first pre-scheduling in time slot (1, 0) and the UE identifier has already been added to the pre-scheduling list based on the pre-determination that the UE has initiated a service, then the pre-scheduling timing is as follows: Figure 7 As shown, pre-scheduling is triggered again at (5, 0). At this time, since the number of pre-schedulings has reached the set upper limit of the number of pre-schedulings, which is 2, the uplink pre-scheduling of the UE ends in response to the number of pre-schedulings reaching the set upper limit, and the UE is removed from the pre-scheduling list. When the UE is removed from the pre-scheduling list, the UE may have completed its current service (for example, it may have completed its current service based on the second pre-scheduling) or it may not have completed its current service, depending on the actual service situation.

[0101] This embodiment, by promptly terminating the uplink pre-scheduling of terminal devices that meet the preset termination conditions, and by adjusting the pre-scheduling attributes of such terminal devices (adjusting them to the second attribute), can further reduce the occupation of base station pre-scheduling resources for latency-sensitive service scenarios, making the allocation of base station pre-scheduling resources more reasonable and efficient.

[0102] The following provides an application example of the method of this application; see [link to application example]. Figure 8 This example scenario is a latency-sensitive business scenario for factory production lines in 5G applications. The business in this scenario has the following characteristics:

[0103] a. Multiple UEs, typically 60-100 UEs;

[0104] b. Services are usually initiated by the UE, and in a single service process, data may be transferred multiple times between the UE and the BS (BaseStation).

[0105] c. Business latency is sensitive, and a minimum latency of around 13ms is generally required;

[0106] d, strong service burstiness, high concurrency.

[0107] For the above service scenarios or similar scenarios that meet the above characteristics, based on the method of the application, it is identified whether each UE in the service scenario of the factory assembly line has initiated a service at present, the identifier of each UE that has initiated a service is added to the pre-scheduling linked list, so that each UE that has initiated a service is assigned a first attribute, and each UE that has not initiated a service is not added to the pre-scheduling linked list, so that each UE that has not initiated a service is assigned a second attribute. Only the UE that has initiated a service, i.e., has been added to the pre-scheduling linked list, is assigned a first attribute, is pre-scheduled in uplink, and the UE that has not been added to the pre-scheduling linked list, i.e., is assigned a second attribute, is not pre-scheduled in uplink. The UE in the uplink pre-scheduling state is detected in real time to determine whether it meets a preset ending condition, and when it meets the preset ending condition, the uplink pre-scheduling of the UE is ended, and the pre-scheduling attribute of the UE is dynamically adjusted to a second attribute.

[0108] The example avoids pre-scheduling in uplink for the UE in the factory assembly line service scenario that is assigned a second attribute, and timely ends the uplink pre-scheduling of the UE that meets the preset ending condition, thereby reducing the waste of pre-scheduling resources of the base station from multiple dimensions as much as possible, reducing the data volume of invalid data in uplink, and avoiding the lifting of interference noise.

[0109] Corresponding to the above uplink pre-scheduling method, the application also discloses a base station, which can be a public network base station or a private network base station, and the component structure thereof is as shown in Figure 9 at least includes:

[0110] a memory 10 for storing at least a set of instructions;

[0111] The instruction set can be implemented in the form of a computer program.

[0112] a processor 20 for calling and executing the instruction set in the memory, and realizing the uplink pre-scheduling method as described in any of the above embodiments by executing the instruction set.

[0113] The processor 20 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices.

[0114] In addition, the base station can also include a communication interface, a communication bus, and other components. The memory, the processor, and the communication interface complete communication with each other through the communication bus.

[0115] To sum up, the uplink pre-scheduling method and the base station provided by the embodiments of the present application have at least the following advantages compared with the prior art:

[0116] 1. The pre-scheduling of the UE can be automatically and timely determined according to the service condition of the UE;

[0117] 2. The pre-scheduling of the UE can be automatically and timely closed according to the pre-scheduling context and the pre-scheduling control parameter of the UE;

[0118] 3. Through 1-2 above, the waste of the pre-scheduling resource of the base station can be further reduced, the number of invalid scheduling and the data amount of invalid uplink data can be reduced, and the interference noise can be avoided to be lifted up while the pre-scheduling resource of the base station is effectively utilized to guarantee the service delay requirement of the UE.

[0119] It should be noted that each of the embodiments in the present specification is described in a progressive manner, and each embodiment focuses on the difference from other embodiments. The same or similar parts of each embodiment can be referred to.

[0120] For the convenience of description, the above system or device is described as various modules or units described respectively in terms of functions. Of course, in the implementation of the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0121] From the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software and the necessary general hardware platform. Based on this understanding, the technical solutions of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute the methods described in each embodiment or some parts of the embodiments of the present application.

[0122] Finally, it needs to be pointed out that, in this document, relational terms such as first, second, third, and fourth and the like can only be used to distinguish one entity or action from another entity or action, without necessarily requiring or implying any actual relationship or order between or among such entities or actions. Moreover, the terms "comprises", "comprising", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.

[0123] The above description is merely preferred embodiments of the present application, and it is obvious to those skilled in the art that, without departing from the principles of the present application, a number of improvements and refinements can be made, and these improvements and refinements should also be considered as falling within the scope of the present application.

Claims

1. An uplink pre-scheduling method, comprising: determining a downlink data type corresponding to downlink data of a terminal device when scheduling the downlink new transmission data of the terminal device; determining a service state of the terminal device based on the downlink data type, including: if the downlink data type is a DATA type in an AM mode, determining the service state of the terminal device as a first state representing that the terminal device has initiated a service; if the downlink data type is not a DATA type in the AM mode, determining the service state of the terminal device as a second state representing that the terminal device has not initiated the service; determining a pre-scheduling attribute of the terminal device based on the service state of the terminal device, the pre-scheduling attribute of the terminal device being used to represent whether the terminal device currently has a pre-scheduling requirement; in response to the pre-scheduling attribute of the terminal device being a second attribute, avoiding performing uplink pre-scheduling processing on the terminal device; the second attribute representing that the terminal device currently does not have the pre-scheduling requirement.

2. The method of claim 1, further comprising: in response to the pre-scheduling attribute of the terminal device being a first attribute, performing uplink pre-scheduling processing on the terminal device; the first attribute representing that the terminal device currently has the pre-scheduling requirement.

3. The method of claim 2, wherein the determining the pre-scheduling attribute of the terminal device based on the service state of the terminal device comprises: based on the service state of the terminal device being the first state, determining the pre-scheduling attribute of the terminal device as the first attribute; and based on the service state of the terminal device being the second state, determining the pre-scheduling attribute of the terminal device as the second attribute.

4. The method of claim 2, wherein the performing uplink pre-scheduling processing on the terminal device comprises: obtaining a pre-scheduling control parameter configured and pre-scheduling context information corresponding to the terminal device; determining a pre-scheduling execution parameter required for performing uplink pre-scheduling processing on the terminal device according to at least one of the pre-scheduling control parameter and the pre-scheduling context information; and performing uplink pre-scheduling processing on the terminal device according to the pre-scheduling execution parameter.

5. The method of claim 4, wherein the determining the pre-scheduling execution parameter required for performing uplink pre-scheduling on the terminal device according to at least one of the pre-scheduling control parameter and the pre-scheduling context information comprises: determining a pre-scheduling occasion and adjustment information of a buffer occupancy value corresponding to the terminal device in uplink pre-scheduling processing according to at least one of the pre-scheduling control parameter and the pre-scheduling context information.

6. The method of claim 5, wherein the pre-scheduling control parameter comprises at least part of a pre-configured pre-scheduling upper limit value, a pre-scheduling interval, and a pre-scheduling data amount; and the pre-scheduling context information at least comprises an actual pre-scheduling number of the terminal device at present. ​ ​ ​ ​ ​ ​ determining, according to at least one of the pre-scheduling control parameter and the pre-scheduling context information, a pre-scheduling timing for performing uplink pre-scheduling on the terminal device and adjustment information of a buffer occupancy value corresponding to the terminal device in uplink pre-scheduling processing, comprises: in a case that the actual pre-scheduling times is less than the pre-scheduling upper limit value, determining, according to the actual pre-scheduling times and a pre-scheduling interval in the pre-scheduling control parameter, a pre-scheduling timing of next uplink pre-scheduling processing to be performed on the terminal device; determining, according to a pre-scheduling data amount in the pre-scheduling control parameter, adjustment information of a buffer occupancy value corresponding to the terminal device in uplink pre-scheduling processing.

7. The method of claim 6, wherein performing uplink pre-scheduling processing on the terminal device according to the pre-scheduling execution parameter comprises: triggering uplink pre-scheduling processing on the terminal device at the pre-scheduling timing; adjusting, in the uplink pre-scheduling processing, the buffer occupancy value corresponding to the terminal device according to the adjustment information, so as to allocate uplink resources to the terminal device based on the adjusted buffer occupancy value in uplink scheduling on the terminal device; updating the pre-scheduling context information corresponding to the terminal device.

8. The method of claim 2, wherein in a case that the pre-scheduling attribute of the terminal device is the first attribute, the method further comprises: ending uplink pre-scheduling processing on the terminal device and adjusting the pre-scheduling attribute of the terminal device to the second attribute based on detecting that the uplink pre-scheduling processing on the terminal device meets a preset ending condition; wherein meeting the ending condition comprises meeting at least one of the following conditions: the uplink pre-scheduling times on the terminal device reaches a set pre-scheduling upper limit value; receiving uplink data sent by the terminal device.

9. A base station, comprising: a memory configured to store at least a set of instructions; a processor configured to invoke and execute the set of instructions in the memory, and implement the uplink pre-scheduling method according to any one of claims 1-8 by executing the set of instructions.

Images