CN114339825A

CN114339825A - Semi-static scheduling method and device

Info

Publication number: CN114339825A
Application number: CN202111423964.3A
Authority: CN
Inventors: 孟凡坤
Original assignee: Ruijie Networks Co Ltd
Current assignee: Ruijie Networks Co Ltd
Priority date: 2021-11-26
Filing date: 2021-11-26
Publication date: 2022-04-12

Abstract

The application discloses a semi-static scheduling method and a semi-static scheduling device, which are used for solving the problem of wireless resource waste caused by inconsistency of a semi-static scheduling period and an actual data transmission requirement in the related technology. The method comprises the following steps: the network equipment determines the configuration of semi-static scheduling to be activated from a plurality of semi-static scheduling configurations which are distributed for the terminal in advance according to at least two requested time intervals, wherein the configuration of the semi-static scheduling to be activated is different from the configuration of the semi-static scheduling adopted by the network equipment and the terminal currently; the plurality of requests are used for indicating the network equipment to update data to be sent or the plurality of requests are used for indicating the network equipment to allocate time-frequency resources; the time interval is a time interval between any two temporally adjacent requests of the plurality of requests, and the time interval between any two temporally adjacent requests of the plurality of requests is the same; the network equipment indicates to the terminal to activate the configuration of the semi-persistent scheduling to be activated.

Description

Semi-static scheduling method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a semi-persistent scheduling method and apparatus.

Background

Semi-Persistent Scheduling (SPS) refers to configuring periodic Scheduling parameters for a terminal based on Radio Resource Control (RRC) signaling, and activating Semi-Persistent Scheduling by scrambling a Physical Downlink Control Channel (PDCCH) through a Semi-Persistent Scheduling-Radio network temporary identifier (CS-RNTI). After the semi-persistent scheduling is activated, the terminal can periodically receive downlink data at the same time-frequency resource position according to a period configured in the RRC signaling, so that the base station does not need to transmit the PDCCH signaling in each scheduling time slot, and resources of a control channel can be saved.

However, if the selected period of the semi-persistent scheduling is not reasonable, it may cause a waste of video resources or a reduction in service quality. For example, if the period of semi-persistent scheduling is too short, it may cause a Physical Downlink Shared Channel (PDSCH) and an Uplink Physical Shared Channel (PUSCH) scheduled on a part of the time slot to be padding data, which may waste time-frequency resources of the PDSCH and the PUSCH channels. On the contrary, if the period of the semi-persistent scheduling is too long, or the dynamic scheduling is still needed to transmit data between the two periods, the purpose of saving the PDCCH channel resources cannot be achieved.

Disclosure of Invention

An exemplary embodiment of the present application provides a method and an apparatus for semi-persistent scheduling, so as to solve a problem of radio resource waste caused by a mismatch between a semi-persistent scheduling period and an actual data transmission requirement in the related art.

In a first aspect, an embodiment of the present application provides a semi-persistent scheduling method, including:

the method comprises the steps that network equipment determines configuration of semi-static scheduling to be activated from a plurality of semi-static scheduling configurations which are distributed for a terminal in advance according to at least two requested time intervals, wherein the configuration of the semi-static scheduling to be activated is different from the configuration of the semi-static scheduling currently adopted by the network equipment and the terminal; the plurality of requests are used for indicating the network equipment to update data to be sent or the plurality of requests are used for indicating the network equipment to allocate time-frequency resources; the time interval is a time interval between any two temporally adjacent requests of the plurality of requests, the time interval between any two temporally adjacent requests of the plurality of requests being the same;

and the network equipment indicates the terminal to activate the configuration of the semi-static scheduling to be activated.

In the related art, a fixed semi-persistent scheduling configuration is generally adopted for one service type, and in some cases, the fixed semi-persistent scheduling may not meet the actual data transmission condition between the network device and the terminal, resulting in waste of radio resources. Based on the scheme, the network equipment can dynamically adjust the semi-static scheduling configuration according to the actual uplink and downlink data transmission condition, so that the semi-static scheduling configuration meets the actual requirement of data transmission between the network equipment and the terminal, and resource waste is avoided. In addition, since some service types, such as game services, do not have a dedicated 5G quality of service Identifier (5G QoS Identifier, 5QI) bearer, there is no semi-static scheduling configuration corresponding to such services in the network device. In the scheme provided by the application, even if the network device does not have semi-static scheduling configuration of a certain service, the semi-static scheduling configuration which can be adopted by the service can be determined according to the actual uplink and downlink data transmission condition.

In some embodiments, when the plurality of requests are for indicating that the network device allocates time-frequency resources, the plurality of requests are received from the terminal, the method further comprises:

and when the network equipment does not receive a physical shared channel (PUSCH) signaling from a terminal within a set time length, indicating the terminal to deactivate the currently adopted configuration of the semi-persistent scheduling.

In some embodiments, when the plurality of requests are used to instruct the network device to update data to be sent, the plurality of requests are generated by the network device during the process of generating the data to be sent, the method further includes:

and when the network equipment does not generate the data to be sent within a set time length, indicating the terminal to deactivate the currently adopted semi-persistent scheduling configuration.

Based on the scheme, the method covers two transmission scenes of uplink and downlink, semi-static scheduling configuration to be adopted can be determined according to data transmission conditions in the two scenes, and actual requirements of network equipment and a terminal are met. In addition, in the above scheme, if the network device determines that there is no data transmission within the set duration, the current semi-persistent scheduling configuration may be deactivated, thereby avoiding resource waste.

In some embodiments, each semi-persistent scheduled configuration of the plurality of semi-persistent scheduled configurations includes a period of the semi-persistent scheduled configuration, and the semi-persistent scheduled configuration corresponds to a number indicating that the corresponding semi-persistent scheduled configuration is activated.

Based on the above scheme, each semi-persistent configuration corresponds to a number, and the terminal may be instructed to activate the semi-persistent scheduling configuration according to the number. The problem of when configuring a plurality of sets of semi-persistent scheduling in the prior art, the terminal needs to perform blind detection to determine which set of semi-persistent scheduling configuration is adopted, so that the burden of the terminal is heavier is solved.

In some embodiments, determining the configuration of the semi-persistent scheduling to be activated from a plurality of semi-persistent scheduling configurations previously allocated to the terminal according to a plurality of requested time intervals includes:

if the time interval is the same as a semi-static scheduling period included in a first semi-static scheduling configuration in the plurality of semi-static scheduling configurations, taking the first semi-static scheduling configuration as the semi-static scheduling configuration to be activated;

if the time interval is different from a plurality of semi-static scheduling periods included in the plurality of semi-static scheduling configurations, taking a second semi-static scheduling configuration as the semi-static scheduling configuration to be activated; the configuration of the second semi-persistent scheduling includes a semi-persistent scheduling period that is a closest semi-persistent scheduling period to the time interval from among the plurality of semi-persistent scheduling periods.

In some embodiments, before indicating to the terminal to activate the configuration of the semi-persistent scheduling to be activated, the method further comprises:

and the network equipment indicates the terminal to deactivate the configuration of the currently adopted semi-static scheduling.

In a second aspect, an embodiment of the present application provides a semi-persistent scheduling apparatus, including:

a determining module, configured to determine, according to at least two requested time intervals, a configuration of semi-persistent scheduling to be activated from a plurality of semi-persistent scheduling configurations that are pre-allocated to a terminal, where the configuration of semi-persistent scheduling to be activated is different from a configuration of semi-persistent scheduling currently adopted by the network device and the terminal; the plurality of requests are used for indicating the network equipment to update data to be sent or the plurality of requests are used for indicating the network equipment to allocate time-frequency resources; the time interval is a time interval between any two temporally adjacent requests of the plurality of requests, the time interval between any two temporally adjacent requests of the plurality of requests being the same;

and the indicating module is used for indicating the terminal to activate the configuration of the semi-static scheduling to be activated.

In some embodiments, when the plurality of requests are for instructing the network device to allocate time-frequency resources, the plurality of requests are received from the terminal, the instructing module is further configured to:

and when the physical shared channel (PUSCH) signaling from the terminal is not received within a set time length, indicating the terminal to deactivate the currently adopted configuration of the semi-persistent scheduling.

In some embodiments, when the plurality of requests are used to instruct the network device to update data to be sent, the plurality of requests are generated by the network device during the process of generating the data to be sent, the instructing module is further configured to:

and when the data to be sent is not generated within a set time length, indicating the terminal to deactivate the configuration of the currently adopted semi-static scheduling.

In some embodiments, the determining module is specifically configured to:

In some embodiments, the indicating module, before indicating to the terminal to activate the configuration of the semi-persistent scheduling to be activated, is further configured to:

and indicating the terminal to deactivate the configuration of the currently adopted semi-static scheduling.

In a third aspect, an embodiment of the present application provides an electronic device, which includes a controller and a memory. The memory is used for storing computer-executable instructions, and the controller executes the computer-executable instructions in the memory to perform the operational steps of any one of the possible implementations of the method according to the first aspect by using hardware resources in the controller.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein instructions, which when executed on a computer, cause the computer to perform the method of the above-described aspects.

In addition, the beneficial effects of the second aspect to the fourth aspect can be referred to as the beneficial effects of the first aspect, and are not described herein again.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application.

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

fig. 2 is a flowchart of a semi-persistent scheduling method according to an embodiment of the present application;

fig. 3 is a flowchart of a method for uplink semi-persistent scheduling according to an embodiment of the present application;

fig. 4 is a flowchart of a method for downlink semi-persistent scheduling according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an apparatus for implementing a semi-persistent scheduling method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the present application will be clearly and completely 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, but not all embodiments, of the technical solutions of the present application. All other embodiments obtained by a person skilled in the art without any inventive step based on the embodiments described in the present application are within the scope of the protection of the present application.

The terms "first" and "second" in the description and claims of the present application and the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the term "comprises" and any variations thereof, which are intended to cover non-exclusive protection. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. The "plurality" in the present application may mean at least two, for example, two, three or more, and the embodiments of the present application are not limited.

In addition, the term "and/or" herein is only one kind of association relationship describing an associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document generally indicates that the preceding and following related objects are in an "or" relationship unless otherwise specified.

In order to facilitate understanding of the semi-persistent scheduling scheme proposed in the present application, a brief description is first given of a system architecture related to the present application. Referring to fig. 1, an architecture diagram of a communication system provided in the embodiment of the present application is to be understood that the embodiment of the present application is not limited to the system shown in fig. 1, and in addition, the apparatus in fig. 1 may be hardware, or may be a structure that is functionally divided by software, or a combination of the two. As shown in fig. 1, a system architecture provided in the embodiment of the present application includes a terminal and a network device. The number of the terminals and the network devices included in the system is not limited in the embodiments of the present application. Core network equipment, not shown in fig. 1, may also be included in the communication system.

A Terminal (UE), also called a Terminal device, a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device for providing voice and/or data connectivity to a User, such as a handheld device with a wireless connection function, a vehicle-mounted device, etc. Currently, some examples of terminals are: a Mobile phone (Mobile phone), a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a wearable Device, a Virtual Reality (VR) Device, an Augmented Reality (AR) Device, a wireless terminal in Industrial Control (Industrial Control), a wireless terminal in unmanned driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety, a wireless terminal in city (smart city), a wireless terminal in smart home (smart home), and the like.

The network device related in the embodiment of the present application may also be referred to as a base station, AN Access Node or AN Access Node (AN). The base station, namely the public mobile communication base station, is an interface device for the mobile terminal to access the internet. The network device may be specifically an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a base station device (gNB) in a 5G network, which is not limited in this application.

Illustratively, the core network device not shown in fig. 1 may include an Access and Mobility Management entity (AMF), a session Management Function entity (SMF), and the like.

Currently, methods adopted by network devices to perform resource scheduling for terminals include dynamic scheduling and semi-static scheduling. The dynamic scheduling refers to that the network equipment allocates uplink and downlink time-frequency domain resources to the terminal according to a received scheduling request from the terminal. Semi-persistent scheduling refers to that network equipment can allocate semi-persistent scheduling configuration to a terminal according to the service type performed by the terminal, wherein the configuration includes a period and time-frequency domain resources allocated to the terminal. Alternatively, the network device may allocate the semi-persistent scheduling configuration to the terminal through Radio Resource Control (RRC) signaling. The network device may also indicate to activate the semi-persistent scheduling configuration to the terminal through a Physical Downlink Control Channel (PDCCH) signaling. After semi-persistent scheduling is activated, the terminal may periodically transmit and receive data on the time-frequency domain resource according to the semi-persistent scheduling configuration. Therefore, the selection of the period of the semi-static scheduling is particularly important, and if the period selection is too short, useless filling data is sent on part of the time slots; if the period selection is too long, data transmission between two periods still adopts a dynamic scheduling mode, and the purpose of saving uplink and downlink channel resources is not achieved.

In view of the above problems, the current solutions include the following two: one configuration is that the network device allocates multiple sets of semi-persistent Scheduling to the terminal, each set of configuration corresponds to a semi-persistent Scheduling-radio network temporary identifier (CS-RNTI), and the network device selects one set from the multiple sets of configuration according to the service type of the terminal. However, in this scheme, the terminal does not know which set of semi-persistent scheduling configuration the network device selects, so the terminal needs to blindly detect the PDCCH channel, which increases the burden of the terminal. Another solution is that after the network device allocates a set of semi-persistent scheduling configurations to the terminal, if it is detected that the set of configurations is not applicable to the current service type of the terminal, the network device reconfigures a set of semi-persistent scheduling configurations to the terminal to adapt to the current service type of the terminal. In this scheme, the reconfiguration takes a long time, which may cause a problem that a service currently performed by the terminal is interrupted.

In view of this, embodiments of the present application provide a method and an apparatus for semi-persistent scheduling, where a network device may allocate multiple sets of semi-persistent scheduling configurations to a terminal in advance, and indicate to the terminal to activate a set of semi-persistent scheduling configurations adapted to a service type of a current terminal according to a time interval of a scheduling request sent by the terminal or a time interval of downlink data generated by the terminal. The semi-static scheduling configuration is adaptively adjusted according to the data transmission condition between the terminal and the terminal, and resource waste is avoided.

First, in order to understand the solution proposed by the present application, referring to fig. 2, a flowchart of a semi-persistent scheduling method provided in an embodiment of the present application specifically includes:

201, the network device determines a semi-persistent scheduling configuration to be activated from a plurality of semi-persistent scheduling configurations allocated to the terminal in advance according to at least two requested time intervals.

The semi-static scheduling configuration to be activated is different from the semi-static scheduling configuration adopted by the current terminal. The time interval of the at least two requests refers to a time interval between any two of the at least two requests that are adjacent in the time domain, and the time intervals between any two of the plurality of requests that are adjacent in the time domain are the same. For example, the time interval between a request received at a first time and a request received at a second time is the same as the time interval between a request received at the second time and a request received at a third time.

Alternatively, the number of requests may be preset. For example, the network device may preset that, when 10 requests are received and the time interval between any two time-domain adjacent requests of the 10 requests is the same, the semi-persistent scheduling configuration to be activated is determined according to the time interval between any two time-domain adjacent requests of the 10 requests.

As a possible implementation manner, the multiple requests may be scheduling requests sent by the terminal to the network device, and the scheduling requests are used for instructing the network device to allocate time-frequency resources. As another possible implementation manner, the plurality of requests may also be used to instruct the network device to update the data to be sent.

202, the network device indicates to the terminal to activate the semi-persistent scheduling configuration to be activated.

Optionally, after determining the to-be-activated semi-persistent scheduling configuration from the plurality of sets of pre-allocated semi-persistent scheduling configurations according to the plurality of requested time intervals, the network device may send indication information to the terminal to indicate the terminal to activate the to-be-activated semi-persistent scheduling configuration. Further, the terminal can periodically transmit and receive data on the corresponding time-frequency resource according to the activated semi-persistent scheduling configuration.

Based on the scheme, the network equipment can dynamically adjust the semi-static scheduling configuration according to the actual uplink and downlink data transmission condition, so that the semi-static scheduling configuration meets the actual requirement of data transmission between the network equipment and the terminal, and resource waste is avoided. In addition, since some service types, such as game services, do not have dedicated 5QI bearers, there is no semi-static scheduling configuration corresponding to such services in the network device. In the scheme provided by the application, even if the network device does not have semi-static scheduling configuration of a certain service, the semi-static scheduling configuration which can be adopted by the service can be determined according to the actual uplink and downlink data transmission condition.

In some embodiments, the semi-persistent scheduling configuration may include a period of semi-persistent scheduling and time-frequency domain resources allocated by the network device for the terminal. As an optional manner, the network device may allocate multiple sets of semi-persistent scheduling configurations to the terminal when the terminal accesses, where multiple periods included in the multiple sets of semi-persistent scheduling configurations may cover periods of data bearers of periodic services that may be created by all terminals. As an example, the network device may count data bearer periods corresponding to different service types, and then generate a plurality of different semi-persistent scheduling periods according to the counted periods, where each semi-persistent scheduling period corresponds to a set of semi-persistent scheduling configurations. Optionally, the network device may also allocate a CS-RNTI for the terminal when the terminal accesses. Optionally, the network device may issue multiple sets of semi-persistent scheduling configurations allocated to the terminal and the CS-RNTI to the terminal through RRC signaling. As an example, each of the multiple sets of semi-persistent scheduling configurations issued by the network device may have a corresponding number.

In some embodiments, after allocating multiple sets of semi-persistent scheduling configurations for the terminal, the network device may detect the uplink and downlink data transmission conditions, and determine which set of semi-persistent scheduling configuration is specifically adopted according to the data transmission conditions. As an alternative, the network device may determine the semi-static scheduling configuration to be activated according to the time interval between the plurality of requests. The time interval of the plurality of requests refers to a time interval between any two temporally adjacent requests of the plurality of requests. In one possible case, the plurality of requests may be scheduling requests received by the network device from the terminal for instructing the network device to allocate time-frequency domain resources. In another possible case, the plurality of requests may be generated by the network device when generating the downlink data to be transmitted, and used for instructing the network device to transmit the downlink data.

Optionally, each set of semi-persistent scheduling configuration includes a semi-persistent scheduling period, and when determining the semi-persistent scheduling configuration to be activated according to a plurality of requested time intervals, the network device may adopt the following manner: in a possible case, if the network device may determine that the time interval is the same as a period of semi-persistent scheduling included in a first semi-persistent scheduling configuration of the plurality of sets of semi-persistent scheduling configurations, the network device may use the first semi-persistent scheduling configuration as the semi-persistent scheduling configuration to be activated. In another possible case, if the network device may determine that the time interval is different from a semi-persistent scheduling period included in any one of the plurality of sets of semi-persistent scheduling configurations, the network device may use the semi-persistent scheduling configuration corresponding to the semi-persistent scheduling period closest to the time interval as the semi-persistent scheduling configuration to be activated. For example, the time interval between the plurality of requests determined by the network device is 10 seconds, the period of the semi-persistent scheduling included in any one of the plurality of sets of semi-persistent scheduling configurations allocated to the terminal is not 10 seconds, but the period of the semi-persistent scheduling included in the second semi-persistent scheduling configuration in the plurality of sets of semi-persistent scheduling configurations is 9.8 seconds, and then the network device may use the second semi-persistent scheduling configuration as the semi-persistent scheduling configuration to be activated. In another possible case, if the network device determines that the time interval is different from a semi-persistent scheduling period included in any one of the plurality of sets of semi-persistent scheduling configurations, a new semi-persistent scheduling configuration may be created according to the time interval, and the newly created semi-persistent scheduling configuration is sent to the terminal through an RRC signaling as the semi-persistent scheduling configuration to be activated. Optionally, the network device may also delete the semi-persistent scheduling configuration originally allocated to the terminal to save resources. Further, after the network device determines the semi-persistent scheduling configuration to be activated according to the time intervals of the multiple requests and determines that the semi-persistent scheduling configuration to be activated is not the semi-persistent scheduling configuration currently adopted by the terminal and the network device, the network device may indicate to the terminal to activate the semi-persistent scheduling configuration to be activated.

As an optional manner, each set of semi-persistent scheduling configuration in the plurality of sets of semi-persistent scheduling configurations allocated to the terminal by the network device has a corresponding number, and the network device may instruct the terminal to activate the semi-persistent scheduling configuration to be activated by sending the number of the semi-persistent scheduling configuration to be activated to the terminal. As an example, the network device may send PDCCH signaling including the number of the semi-persistent scheduling configuration to be activated to the terminal to instruct the terminal to activate the semi-persistent scheduling configuration to be activated. Optionally, the network device may also use the CS-RNTI to scramble PDCCH signaling sent to the terminal, and since the CS-RNTI is pre-allocated to the terminal by the network device, the CS-RNTI is used to scramble the PDCCH signaling, that is, the PDCCH signaling is sent to the terminal when the PDCCH signaling is indicated.

In some embodiments, before indicating to the terminal to activate the semi-persistent scheduling configuration to be activated, the network device may further indicate to the terminal to deactivate the semi-persistent scheduling configuration currently adopted by the terminal. For example, the network device may send PDCCH signaling carrying the number of the semi-persistent scheduling configuration currently adopted by the terminal and the network device to the terminal to instruct the terminal to deactivate the semi-persistent scheduling configuration currently adopted.

In order to further understand the semi-persistent scheduling scheme proposed in the present application, the following describes the scheme of the present application with reference to a specific scenario.

Scene one: and transmitting uplink data.

In a scenario one, the network device may allocate multiple sets of uplink semi-persistent scheduling configurations to the terminal when the terminal is accessed, where uplink semi-persistent scheduling periods included in each set of semi-persistent scheduling periods are different, and each set of uplink semi-persistent scheduling configurations corresponds to one number. Optionally, the network device may send multiple sets of uplink semi-persistent scheduling configurations allocated to the terminal through RRC signaling. Further, the network device may monitor a plurality of time intervals of the scheduling requests for requesting the time-frequency domain resource, which are sent by the terminal, and select the uplink semi-persistent scheduling configuration to be activated from the plurality of sets of uplink semi-persistent scheduling configurations according to the time intervals when it is determined that the time intervals between any two adjacent scheduling requests in the time domain are the same among the scheduling requests reaching the set number. For a specific process of determining to-be-activated uplink semi-persistent scheduling configuration according to the time interval, reference may be made to the description in the foregoing embodiment, and details are not described here again. Still further, the network device may indicate to the terminal to activate the uplink semi-persistent scheduling configuration to be activated, for example, the network device may indicate by sending a PDCCH signaling carrying a number of the uplink semi-persistent scheduling configuration to be activated.

In some embodiments, the network device may continue to detect the time interval between scheduling requests from the terminal after the first activation of the uplink semi-persistent scheduling. And when the time interval between any two adjacent scheduling requests in the time domain in the scheduling requests reaching the set number is determined to be the same, selecting one set of uplink semi-static scheduling configuration from a plurality of sets of uplink semi-static scheduling configurations configured in advance according to the time interval, and then judging whether the uplink semi-static scheduling configuration of the set of uplink semi-static scheduling configuration is the same as the uplink semi-static scheduling configuration adopted by the terminal currently. If the uplink semi-static scheduling configuration is the same as the to-be-activated uplink semi-static scheduling configuration, no operation is performed, and if the uplink semi-static scheduling configuration is not the same as the to-be-activated uplink semi-static scheduling configuration, the uplink semi-static scheduling configuration is used as a new to-be-activated uplink semi-static scheduling configuration. Further, the network device may first instruct the terminal to deactivate the currently adopted uplink semi-persistent scheduling configuration, and then instruct the terminal to activate the newly determined uplink semi-persistent scheduling configuration to be activated. The terminal can periodically transmit uplink data at the set resource location according to the uplink semi-persistent scheduling period in the newly activated uplink semi-persistent scheduling.

In some embodiments, if the network device does not receive the PUSCH signaling from the terminal within the set duration, it may also indicate to deactivate the currently employed uplink semi-persistent scheduling configuration to the terminal. For example, when the network device receives the PUSCH signaling periodically at the corresponding time-frequency domain resource location according to the period included in the currently adopted uplink semi-persistent scheduling configuration, the network device may not receive the PUSCH signaling for multiple times (that is, all the results of the multiple times are Discontinuous Transmission (DTX)), and then instruct the terminal to deactivate the currently adopted uplink semi-persistent scheduling configuration.

For convenience of understanding, referring to fig. 3, a flow of an uplink semi-persistent scheduling method in scenario one is described with a specific embodiment.

301, the network device continuously receives scheduling requests from the terminals.

The network device determines 302 that a time interval between any two temporally adjacent scheduling requests of the plurality of scheduling requests is the same.

Alternatively, the network device may preset the number of scheduling requests. For example, the network device sets that 10 scheduling requests are received, and the time interval between any two of the 10 scheduling requests that are adjacent in the time domain is the same.

303, the network device determines the uplink semi-persistent scheduling configuration to be activated from multiple sets of uplink semi-persistent scheduling configurations pre-allocated to the terminal according to the time interval.

The multiple sets of uplink semi-persistent scheduling configurations can be allocated to the terminal when the terminal accesses the network device. Each set of uplink semi-persistent scheduling configuration has a corresponding number, and uplink semi-persistent scheduling periods included in each set of uplink semi-persistent scheduling configuration are different.

Optionally, if the time interval is the same as an uplink semi-persistent scheduling period included in one of the plurality of sets of uplink semi-persistent scheduling configurations, the set of uplink semi-persistent scheduling configurations is used as the uplink semi-persistent scheduling configuration to be activated. If the time interval is different from the uplink semi-persistent scheduling period included in any one of the plurality of sets of configurations, the uplink semi-persistent scheduling configuration corresponding to the uplink semi-persistent scheduling period closest to the time interval may be selected as the uplink semi-persistent scheduling configuration to be activated.

304, the network device determines whether the uplink semi-persistent scheduling configuration to be activated is the same as the uplink semi-persistent scheduling configuration currently adopted by the terminal.

If the two are the same, the network device does not perform any operation.

If not, continue to step 305.

305, the network device indicates to the terminal to deactivate the currently adopted uplink semi-persistent scheduling configuration.

Specifically, the network device may send PDCCH signaling scrambled with the CS-RNTI to the terminal, where the PDCCH signaling carries a number of the currently adopted uplink semi-persistent scheduling configuration.

And 306, the network equipment indicates to activate the uplink semi-persistent scheduling configuration to be activated to the terminal.

Specifically, the network device may send PDCCH signaling scrambled with the CS-RNTI to the terminal, where the PDCCH signaling carries a number of the uplink semi-persistent scheduling configuration to be activated.

Scene two: and (5) downlink data transmission.

In scenario two, the network device may allocate multiple sets of downlink semi-persistent scheduling configurations to the terminal when the terminal accesses the network device. Specifically, reference may be made to the description in the above scenario one, and details are not described herein again. Further, the network device may count a time interval of an update request generated when the downlink data is generated, where the update request is used to instruct the network device to update the downlink data to be sent. As an example, the update request may be sent by a Radio Link Control (RLC) layer in the network device to a Media Access Control (MAC) layer of the network device when downlink data needs to be transmitted, and is used to instruct the MAC layer to update the downlink data to be transmitted. The network device (or the MAC layer of the network device) may count time intervals of a plurality of update requests, and when it is determined that the time intervals between any two update requests adjacent in the time domain in a set number of update requests are the same, may determine, according to the time intervals, a downlink semi-persistent scheduling configuration to be activated from a plurality of sets of downlink semi-persistent scheduling configurations allocated to the terminal in advance. For a specific process of determining the to-be-activated downlink semi-persistent scheduling configuration, reference may be made to the description in the scenario one, and details are not described herein again.

Further, the network device may determine whether the determined to-be-activated downlink semi-persistent scheduling configuration is the same as the downlink semi-persistent scheduling configuration currently adopted by the terminal, and if not, the network device may first instruct the terminal to deactivate the currently-adopted downlink semi-persistent scheduling configuration, and then instruct the terminal to activate the determined to-be-activated downlink semi-persistent scheduling configuration. For a specific process of activation and deactivation, reference may be made to the description in the foregoing embodiments, and details are not described here.

In some embodiments, if the MAC layer of the network device does not receive the update request from the RLC layer within the set time duration, the MAC layer may also instruct the terminal to deactivate the currently adopted downlink semi-persistent scheduling configuration.

Next, referring to fig. 4, a flowchart of a method for downlink semi-persistent scheduling in a scenario two according to the embodiment of the present application is provided. For convenience of understanding, in fig. 4, a method for describing downlink semi-persistent scheduling in conjunction with each layer of a network device specifically includes:

401, the MAC layer continuously receives update requests from the RLC layer.

The update request is used for indicating the MAC layer to update the downlink data to be transmitted.

402, the MAC layer determines that the time interval between any two temporally adjacent requests of the plurality of update requests is the same.

Alternatively, the MAC layer may predefine the number of received update requests. For example, the MAC layer is set to receive 10 update requests from the RLC layer, and the time interval between any two temporally adjacent update requests among the 10 update requests is the same.

And 403, the MAC layer determines a downlink semi-persistent scheduling configuration to be activated from multiple sets of downlink semi-persistent scheduling configurations allocated to the terminal in advance according to the time interval.

The specific process may refer to step 303 in fig. 3, which is not described herein again.

404, the MAC layer determines whether the downlink semi-persistent scheduling configuration to be activated is the same as the downlink semi-persistent scheduling configuration currently adopted by the terminal.

If so, the MAC layer does nothing.

If not, continue with step 405.

405, the MAC layer indicates to the terminal to deactivate the currently adopted downlink semi-persistent scheduling configuration.

Referring to step 305 in fig. 3, the detailed description is omitted here.

406, the MAC layer indicates to the terminal to activate the to-be-activated downlink semi-persistent scheduling configuration.

Referring to step 306 in fig. 3, the detailed description is omitted here.

Based on the same concept as the method described above, referring to fig. 5, an embodiment of the present application further provides an apparatus 500 for implementing a semi-persistent scheduling method. The apparatus 500 is capable of performing the various steps of the above-described method, and will not be described in detail herein to avoid repetition. The apparatus 500 comprises: a determination module 501 and an indication module 502.

A determining module 501, configured to determine, according to at least two requested time intervals, a configuration of a to-be-activated semi-persistent scheduling from a plurality of semi-persistent scheduling configurations that are pre-allocated to a terminal, where the configuration of the to-be-activated semi-persistent scheduling is different from a configuration of semi-persistent scheduling currently adopted by the network device and the terminal; the plurality of requests are used for indicating the network equipment to update data to be sent or the plurality of requests are used for indicating the network equipment to allocate time-frequency resources; the time interval is a time interval between any two temporally adjacent requests of the plurality of requests, the time interval between any two temporally adjacent requests of the plurality of requests being the same;

an indicating module 502, configured to indicate to the terminal to activate the configuration of the to-be-activated semi-persistent scheduling.

In some embodiments, when the plurality of requests are for instructing the network device to allocate time-frequency resources, the plurality of requests are received from the terminal, the instructing module 502 is further configured to:

In some embodiments, when the plurality of requests are used to instruct the network device to update data to be sent, the plurality of requests are generated by the network device in a process of generating the data to be sent, the instructing module 502 is further configured to:

In some embodiments, the determining module 501 is specifically configured to:

In some embodiments, the indicating module 502 is further configured to, before indicating to the terminal to activate the configuration of the semi-persistent scheduling to be activated:

Fig. 6 shows a schematic structural diagram of an electronic device 600 provided in an embodiment of the present application. The electronic device 600 in this embodiment of the application may further include a communication interface 603, where the communication interface 603 is, for example, a network port, and the electronic device may transmit data through the communication interface 603, for example, the communication interface 603 may implement part of the functions of the indication module 502 in fig. 5.

In the embodiment of the present application, the memory 602 stores instructions executable by the at least one controller 601, and the at least one controller 601 may be configured to perform the steps of the method by executing the instructions stored in the memory 602, for example, the controller 601 may implement the functions of the determining module 501 and the functions of the indicating module 502 in fig. 5.

The controller 601 is a control center of the electronic device, and may connect various parts of the whole electronic device by using various interfaces and lines, by executing or executing instructions stored in the memory 602 and calling data stored in the memory 602. Alternatively, the controller 601 may include one or more processing units, and the controller 601 may integrate an application controller and a modem controller, wherein the application controller mainly handles an operating system, application programs, and the like, and the modem controller mainly handles wireless communication. It will be appreciated that the modem controller described above may not be integrated into the controller 601. In some embodiments, the controller 601 and the memory 602 may be implemented on the same chip, or in some embodiments, they may be implemented separately on separate chips.

The controller 601 may be a general-purpose controller, such as a Central Processing Unit (CPU), digital signal controller, application specific integrated circuit, field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, and may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. The general controller may be a microcontroller or any conventional controller or the like. The steps executed by the data statistics platform disclosed in the embodiments of the present application may be directly executed by a hardware controller, or may be executed by a combination of hardware and software modules in the controller.

The memory 602, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 602 may include at least one type of storage medium, and may include, for example, a flash Memory, a hard disk, a multimedia card, a card-type Memory, a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Programmable Read Only Memory (PROM), a Read Only Memory (ROM), a charge Erasable Programmable Read Only Memory (EEPROM), a magnetic Memory, a magnetic disk, an optical disk, and so on. The memory 602 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 602 in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.

By programming the controller 601, for example, the code corresponding to the training method of the neural network model described in the foregoing embodiment may be fixed in the chip, so that the chip can execute the steps of the training method of the neural network model when running.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a controller of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the controller of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A semi-persistent scheduling method, comprising:

2. The method of claim 1, wherein the plurality of requests are received from the terminal when the plurality of requests are for indicating that the network device allocates time-frequency resources, the method further comprising:

3. The method of claim 1, wherein when the plurality of requests are for instructing the network device to update data to be sent, the plurality of requests are generated by the network device during generation of the data to be sent, the method further comprising:

4. The method of any one of claims 1-3, wherein each semi-persistent scheduled configuration of the plurality of semi-persistent scheduled configurations comprises a period of the each semi-persistent scheduled configuration, and wherein the each semi-persistent scheduled configuration corresponds to a number indicating activation of the corresponding semi-persistent scheduled configuration.

5. The method of claim 4, wherein determining the configuration of the semi-persistent scheduling to be activated from among a plurality of configurations of semi-persistent scheduling previously allocated to the terminal according to a plurality of requested time intervals comprises:

6. A semi-persistent scheduling apparatus, comprising:

7. The apparatus of claim 6, wherein when the plurality of requests are for indicating that the network device allocates time-frequency resources, the plurality of requests are received from the terminal, the means for indicating is further configured to:

8. The apparatus of claim 6, wherein when the plurality of requests are for instructing the network device to update data to be sent, the plurality of requests are generated by the network device during generation of the data to be sent, the instructing module is further configured to:

9. The apparatus of any one of claims 6-8, wherein each semi-persistent scheduled configuration of the plurality of semi-persistent scheduled configurations comprises a period of the each semi-persistent scheduled configuration, and wherein the each semi-persistent scheduled configuration corresponds to a number indicating activation of the corresponding semi-persistent scheduled configuration.

10. The apparatus of claim 9, wherein the determination module is specifically configured to: