WO2017206085A1

WO2017206085A1 - Method and device for determining scheduling manner for terminal device in communication system

Info

Publication number: WO2017206085A1
Application number: PCT/CN2016/084200
Authority: WO
Inventors: 胡亨捷; 张军; 刘亚林
Original assignee: 华为技术有限公司
Priority date: 2016-05-31
Filing date: 2016-05-31
Publication date: 2017-12-07

Abstract

Provided are a method and device for determining a scheduling manner for a terminal device in a communication system capable of solving a technical problem of high signaling overheads and a long delay resulting from adoption of dynamic scheduling in a power distribution network. The method for determining a scheduling manner for a terminal device in a communication system comprises: receiving a communication identifier of a terminal device; determining, according to the communication identifier, a type of the terminal device; and determining, according to the type of the terminal device, whether to adopt a semi-persistent scheduling manner for the terminal device.

Description

Method and device for determining terminal device scheduling mode in communication system

Technical field

The present invention relates to the field of mobile communication technologies, and in particular, to a method and a device for determining a scheduling manner of a terminal device in a communication system.

Background technique

With the completion of the large-scale construction of the transmission grid of the power grid, the investment focus of the grid will be transferred from the transmission grid to the distribution network. In the distribution network, in view of the requirements of the distribution automation and the active distribution network, there will be a large number of periodic reporting services, such as periodically reporting the status information of the power distribution equipment, active distribution network wide-area relay protection, etc. business. Especially for the active distribution network wide-area relay protection service, the generated data packets are relatively small, the data packet size is fixed, the transmission frequency is high, and the one-way communication delay is required to be small, which puts higher requirements on the communication network.

At present, the distribution network can realize communication through various methods such as next-generation fiber access technology (xPON) or wireless broadband network. Among them, wireless broadband networks have very high construction cost and deployment flexibility compared with fiber-optic cable networks. The big advantage, therefore, the wireless broadband network, especially the Long Term Evolution (LTE) system, is more and more widely used in the communication of the distribution network.

At present, for various terminal devices in the distribution network, the base station generally allocates the scheduling resources for the terminal devices. For example, the default allocation is to allocate dynamic scheduling resources. In fact, different terminal devices may be different. The requirements, such as the terminal equipment used to complete the active distribution network wide-area relay protection service, the active distribution network wide-area relay protection service requires a small delay of one-way communication, and if dynamic scheduling is adopted, each time Scheduling requires the interaction of scheduling signaling. Therefore, the signaling overhead is large, and the scheduling delay is also increased. Obviously, the requirement of one-way communication delay of the wide-area relay protection service of the active distribution network cannot be met.

Summary of the invention

The embodiment of the invention provides a method and a device for determining a scheduling mode of a terminal device in a communication system, which are used to allocate a more suitable scheduling mode for different terminal devices.

In a first aspect, a method for determining a scheduling manner of a terminal device in a first communication system is provided. The method may include: receiving a communication identifier of the terminal device, determining a type of the terminal device according to the communication identifier, and determining whether the device is determined according to the type of the terminal device. The terminal device adopts a semi-static scheduling manner, or determines a scheduling manner adopted by the terminal device according to the type of the terminal device.

The method can be applied to a network device of a communication system, such as an MME, and the MME can determine the type of the terminal device according to the communication identifier of the terminal device, so that it can be determined according to the type of the terminal device whether to adopt a semi-static scheduling manner for the terminal device, or the MME. After determining the type of the terminal device, the scheduling mode adopted for the terminal device may be determined according to the type of the terminal device. For example, for a terminal device in a distribution network that needs to perform a large number of periodically reported services, such as a terminal device of an active distribution network wide-area relay protection service, such terminal devices can be set to require semi-persistent scheduling. A device that performs scheduling, so that the terminal device can be scheduled in a semi-persistent scheduling manner. The semi-static scheduling mode can save a large amount of signaling overhead compared to the dynamic scheduling mode, and at the same time, reduces the interaction of scheduling signaling. The process also reduces the delay of the communication, and can satisfy the service demand of the distribution network as much as possible. For example, the demand for the one-way communication delay of the active distribution network wide-area relay protection service can be met as much as possible. According to the manner provided by the embodiment of the present invention, a corresponding scheduling manner can be set according to the type of the terminal device in advance, so that different scheduling modes can be adopted for different terminal devices, which are more flexible and can better satisfy different terminal devices and Different business needs.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the communication system further includes another network device, such as a PCRF, and determining the type of the terminal device according to the communication identifier may be implemented by: Sending a policy request message to another network device of the at least two network devices, where the policy request message carries a communication identifier, and receives information for indicating a type of the terminal device that is sent by another network device in response to the policy request message.

For example, the correspondence between the communication identifier and the type of the terminal device may be stored in the PCRF, and then the MME may determine the type of the terminal device by sending a policy request message to the PCRF, so that there is no need to correspond the communication identifier to the type of the terminal device. The relationship is stored locally, reducing the burden on the local.

With reference to the first aspect, in a second possible implementation manner of the first aspect, determining a type of the terminal device according to the communication identifier may be implemented by: according to a correspondence between the stored communication identifier and a type of the terminal device, Determine the type of terminal device.

For example, the correspondence between the communication identifier and the type of the terminal device can be stored locally, and the MME can determine the type of the terminal device by querying the correspondence between the locally stored communication identifier and the type of the terminal device, without performing with other devices. The interaction is simple, and the efficiency of determining the type of the terminal device is high.

In conjunction with the first possible implementation of the first aspect, in a third possible implementation manner of the first aspect, the communications system may further include another network device, such as a PCRF, and the method may further include: receiving And information sent by another network device in response to the policy request message for indicating a period in which the terminal device sends the data packet.

If the correspondence between the communication identifier and the type of the terminal device further includes a period in which the terminal device transmits the data packet, the PCRF may also use the indication in addition to the information indicating the type of the terminal device to the MME. The information about the period in which the terminal device sends the data packet is sent to the MME, so that if the MME determines to adopt semi-persistent scheduling for the terminal device, the MME may select to determine the period in which the terminal device transmits the data packet as the scheduling period for semi-persistent scheduling of the terminal device. .

With reference to the first aspect, in a fourth possible implementation manner of the first aspect, the period in which the terminal device sends the data packet may be determined according to the communication identifier, for example, by using the following manner: the stored communication identifier and the type of the terminal device. The correspondence between the terminals can also determine the period during which the terminal device transmits the data packet.

If the correspondence between the communication identifier and the type of the terminal device further includes a period in which the terminal device sends the data packet, for example, the correspondence between the communication identifier and the type of the terminal device may be stored locally, then the MME queries the locally stored communication by querying Corresponding relationship between the identifier and the type of the terminal device, in addition to determining the type of the terminal device, determining the period in which the terminal device sends the data packet, without interacting with other devices, and obtaining the terminal device through one query The type and the period in which the terminal device sends the data packet is simpler to implement.

With reference to the third possible implementation manner of the first aspect or the fourth possible implementation manner, in a fifth possible implementation manner of the first aspect, determining whether to adopt semi-persistent scheduling for the terminal device according to the type of the terminal device After the mode, if the semi-persistent scheduling mode is adopted for the terminal device according to the type of the terminal device, the scheduling period for semi-persistent scheduling of the terminal device may be determined as the period during which the terminal device sends the data packet.

If it is determined that the semi-persistent scheduling mode is adopted for the terminal device, the MME may determine the period in which the terminal device sends the data packet as a scheduling period for semi-persistent scheduling of the terminal device, so that the scheduling period of the terminal device and the terminal device send the data packet. The cycles are matched. When the terminal device wants to send a data packet, it can just have available transmission resources, and the terminal device can better implement data transmission.

With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, after determining whether to adopt a semi-static scheduling manner for the terminal device according to the type of the terminal device, the access network may be received. The service request message sent by the device, the access network device is, for example, a base station, and the service request message may be used by the terminal device to request to transmit a data packet, and send a response message to the access network device. If the semi-persistent scheduling mode is adopted for the terminal device according to the type of the terminal device, the response message may carry information indicating that the terminal device uses the semi-persistent scheduling mode for scheduling, and is used to indicate that the terminal device is semi-static. Information about the scheduled scheduling period.

If the MME determines that the terminal device adopts a semi-persistent scheduling mode, the MME may indicate the information used to indicate that the terminal device uses the semi-persistent scheduling mode to perform scheduling, and is used to indicate that the terminal device performs semi-persistent scheduling. The information of the scheduling period is sent to the access network device, so that the access network device can perform semi-persistent scheduling on the terminal device to ensure that the terminal device transmits data normally.

In a second aspect, a method for determining a scheduling manner of a terminal device in a second communication system is provided. The method may include: receiving a policy request message sent by another network device in the communication system, where the policy request message carries a communication identifier of the terminal device, according to The communication identifier determines the type of the terminal device, and transmits information indicating the type of the terminal device to the other network device. The communication system may include at least two network devices, and the other network device may be one of at least two network devices. device.

The method can be applied to a network device of a communication system, such as a PCRF. For example, a correspondence between a communication identifier and a type of a terminal device can be stored locally in the PCRF, and then the PCRF can send another message according to a policy request message sent by another network device. The network device sends information indicating the type of the terminal device, so that another network device may determine whether to adopt a semi-static scheduling manner for the terminal device according to the type of the terminal device, or another network device may determine the type of the terminal device, The scheduling mode adopted by the terminal device is determined according to the type of the terminal device. Another network device is for example an MME.

With reference to the second aspect, in the first possible implementation manner of the second aspect, determining the type of the terminal device according to the communication identifier may be implemented by: sending a query request message to the network device that stores the power information database, and querying the request The message carrying the communication identifier, the network device storing the power information database may be one of the at least two network devices, and the network device storing the power information database and the network device transmitting the policy request message are not the same network device, receiving the storage The network device of the power information database responds to the query request message with information indicating the type of the terminal device. The information in the at least one terminal device may be stored in the power information database, where the information of each terminal device may include a type of the terminal device and a communication identifier of the terminal device, that is, between the communication identifier and the type of the terminal device. The correspondence relationship is understood as information of the terminal device, and the information of each terminal device may include the communication identifier of the terminal device and the type of the terminal device.

The power information database can be maintained by the power grid staff, for example. Therefore, the information of the terminal equipment stored in the power information base may be relatively large, and the coverage is relatively comprehensive. The power information database is searched to determine the type of the terminal equipment, and the success rate found is also found. It is relatively high.

With reference to the second aspect, in the second possible implementation manner of the second aspect, determining the type of the terminal device according to the communication identifier may also be implemented by: correspondingly according to the stored communication identifier and the type of the terminal device , determine the type of terminal device.

That is, the correspondence between the communication identifier and the type of the terminal device, or the information of the terminal device, may also be stored locally, so that the PCRF can directly learn the type of the terminal device by querying locally, without interacting with other devices. , reducing the interaction process between devices, making the query The process is simpler and more efficient.

In conjunction with the first possible implementation of the second aspect, in a third possible implementation manner of the second aspect, the method may further include: receiving, by the network device that stores the power information database, the message that is sent in response to the query request message Information for indicating a period in which the terminal device transmits a data packet. The information in the at least one terminal device may be stored in the power information database, where the information of each terminal device includes the type of the terminal device and the communication identifier of the terminal device, and the information of each terminal device or the information of some terminal devices is further The period in which the terminal device sends the data packet, that is, the correspondence between the communication identifier and the type of the terminal device can be understood as the information of the terminal device, and the information of each terminal device can include the communication identifier of the terminal device and the terminal. The type of the device, the information of some of the terminal devices or the information of all the terminal devices may further include a period in which the terminal device transmits the data packet.

The power information database can be maintained by the power grid staff, for example. Therefore, the information of the terminal equipment stored in the power information base may be relatively large, and the coverage is relatively comprehensive. The power information database is searched to determine the type of the terminal equipment, and the success rate found is also found. It is relatively high. If the network device storing the power information database determines the information of the terminal device by searching the power information database and further includes the period in which the terminal device sends the data packet, the network device storing the power information database may also send the period in which the terminal device sends the data packet to The PCRF is configured to facilitate the subsequent MME to determine a scheduling period for semi-persistent scheduling of the terminal device. For example, if the MME determines to adopt a semi-persistent scheduling manner for the terminal device, then one option of the MME is to determine the period in which the terminal device sends the data packet as A scheduling period for semi-persistent scheduling of terminal devices.

With reference to the second aspect, in a fourth possible implementation manner of the second aspect, the period in which the terminal device sends the data packet is further determined according to the communication identifier, for example, by: storing the communication identifier and the terminal device according to the The correspondence between the types also determines the period in which the terminal device transmits the data packet.

That is, the correspondence between the communication identifier and the type of the terminal device, or the information of the terminal device, may also be stored locally in the PCRF, so that the PCRF can directly learn the type of the terminal device by querying locally, without performing with other devices. Interaction, reducing the interaction process between devices, making The query process is simpler and more efficient. If the PCRF determines the information of the terminal device by searching locally, and further includes the period in which the terminal device sends the data packet, the period in which the terminal device sends the data packet may be acquired together, so that the subsequent MME determines the scheduling period for semi-persistent scheduling of the terminal device. For example, if the MME determines to adopt a semi-persistent scheduling mode for the terminal device, one option of the MME is to determine the period in which the terminal device transmits the data packet as a scheduling period for semi-persistent scheduling of the terminal device.

With reference to the third possible implementation manner of the second aspect, or the fourth possible implementation manner, in the fifth possible implementation manner of the second aspect, after determining the type of the terminal device according to the communication identifier, according to the communication identifier If the period in which the terminal device sends the data packet is determined, the information indicating the period in which the terminal device sends the data packet may also be sent to another network device.

The period in which the terminal device transmits the data packet is sent to another network device, and the other network device is, for example, an MME, so that the MME can be determined to determine a scheduling period in which the terminal device adopts semi-persistent scheduling. For example, if the MME determines to adopt a semi-persistent scheduling mode for the terminal device, the MME may select a period in which the terminal device sends the data packet as a scheduling period for semi-persistent scheduling of the terminal device, so that the terminal device sends the data packet. The period coincides with the scheduling period of the terminal device, so that the terminal device can normally transmit data and reduce system delay.

In a third aspect, a method for determining a scheduling manner of a terminal device in a third communication system is provided. The method may include: transmitting, to a network device, a communication identifier of the terminal device to determine a type of the terminal device, and receiving, by the network device, an indication for sending The information of the type of the terminal device determines whether the semi-persistent scheduling mode is adopted for the terminal device according to the information indicating the type of the terminal device, or determines the scheduling mode adopted by the terminal device according to the type of the terminal device.

The method can be applied to a network device in a communication system, such as a base station, and the base station can determine the type of the terminal device according to the communication identifier of the terminal device, so that it can be determined according to the type of the terminal device whether to adopt a semi-static scheduling manner for the terminal device, or a base station. After determining the type of the terminal device, the scheduling mode adopted for the terminal device may be determined according to the type of the terminal device. For example, for a terminal device in a distribution network that needs to perform a large number of periodically reported services, such as a terminal device of an active distribution network wide-area relay protection service, such terminal devices can be set to be required to be semi-static. A scheduling device that performs scheduling, so that such terminal devices can be scheduled in a semi-persistent scheduling manner. The semi-static scheduling mode can save a large amount of signaling overhead compared to the dynamic scheduling mode, and at the same time, the scheduling signaling is reduced. The interaction process reduces the communication delay and can meet the service requirements of the distribution network as much as possible. For example, it can satisfy the requirement of the one-way communication delay of the active distribution network wide-area relay protection service.

In conjunction with the third aspect, in a first possible implementation manner of the third aspect, before the sending the communication identifier of the terminal device to the network device, the connection request sent by the terminal device may be received, and the attach request carries the communication identifier.

That is, the base station can determine the type of the terminal device in the process of attaching the terminal device, thereby determining the manner of scheduling the terminal device, so that the terminal device can be directly scheduled by using the scheduling mode suitable for the terminal device after the terminal device is attached.

With the first possible implementation of the third aspect, in a second possible implementation manner of the third aspect, the sending the communication identifier of the terminal device to the network device may be implemented by: determining that the terminal device adopts periodicity When the data packet is sent, the communication identifier is sent to the network device.

For example, the base station may not adopt semi-persistent scheduling for the terminal device, and may adopt a dynamic scheduling mode. Then, the base station may monitor the process of sending the data packet by the terminal device, and if it is determined that the terminal device is transmitting the data packet in a periodic manner, Then, the base station can determine the type of the terminal device by sending a communication identifier to the network device, so that it can be determined whether to change the scheduling manner of the terminal device, such as an MME. In this way, even if the base station does not initially adopt the semi-static scheduling mode for the terminal device, if the terminal device is found to meet the semi-persistent scheduling requirement in the middle, the type of the terminal device can be further confirmed, and if the terminal device is determined according to the type of the terminal device, The device adopts semi-persistent scheduling, and the base station can change the scheduling mode of the terminal device, so that the scheduling mode is more in line with the characteristics of the terminal device, and can also save system overhead to a certain extent.

With reference to the third aspect or the first possible implementation manner or the second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the information according to the type used to indicate the terminal device After determining whether the semi-persistent scheduling mode is adopted for the terminal device, if it is determined that the terminal device adopts the semi-static scheduling mode, the terminal device is sent to indicate that the terminal device performs the semi-persistent scheduling mode. Information for scheduling, and information for indicating a scheduling period for semi-persistent scheduling of the terminal device.

If the base station determines to adopt the semi-persistent scheduling mode for the terminal device, the base station can make the terminal device know that the semi-persistent scheduling mode is to be adopted, and also let the terminal device know the scheduling period of the semi-persistent scheduling, so that the terminal device can according to the scheduling period. To send a packet.

With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, information for indicating scheduling in a semi-persistent scheduling manner is sent to the terminal device, and After the information about the scheduling period of the semi-persistent scheduling is performed, the terminal device may receive the uplink scheduling request message sent by the terminal device, and allocate the transmission resource in the semi-static scheduling mode to the terminal device according to the uplink scheduling request message.

After the base station determines that the terminal device is semi-statically scheduled, and the semi-persistent scheduling information is also notified to the terminal device, the base station may perform scheduling on the terminal device by using a semi-static scheduling manner.

In a fourth aspect, a network device in a first communication system is provided, such as an MME, the network device can include a memory, a first receiver, and a processor. The memory may be used to store instructions required by the processor to perform a task, the first receiver may be configured to receive a communication identifier of the terminal device, the processor may be configured to execute an instruction stored in the memory, and determine a type of the terminal device according to the communication identifier. And determining whether to adopt a semi-static scheduling manner for the terminal device according to the type of the terminal device, or determining a scheduling manner adopted by the terminal device according to the type of the terminal device.

In conjunction with the fourth aspect, in a first possible implementation manner of the fourth aspect, the network device may further include a first transmitter and a second receiver, where the communication system may include another network device, such as a PCRF. The determining, by the processor, the type of the terminal device according to the communication identifier, may be implemented by: sending, by the first sender, a policy request message to another network device of the at least two network devices, where the policy request message may carry the communication identifier, and the second The receiver receives information sent by another network device in response to the policy request message indicating the type of the terminal device.

With reference to the fourth aspect, in a second possible implementation manner of the fourth aspect, the processor is configured to determine a type of the terminal device according to the communication identifier, and may also be implemented by: between the stored communication identifier and the type of the terminal device Correspondence, determine the type of terminal device.

In conjunction with the first possible implementation of the fourth aspect, the third possible implementation in the fourth aspect In the current mode, the processor may be further configured to: receive, by the second receiver, information that is sent by another network device, in response to the policy request message, for indicating a period in which the terminal device sends the data packet.

With reference to the fourth aspect, in a fourth possible implementation manner of the fourth aspect, the processor may further determine, according to the communication identifier, a period in which the terminal device sends the data packet, for example, in the following manner: according to the stored communication identifier and the terminal The correspondence between the types of devices also determines the period during which the terminal device transmits the data packets.

In conjunction with the third possible implementation manner of the fourth aspect, or the fourth possible implementation manner, in a fifth possible implementation manner of the fourth aspect, the processor may be further configured to: determine whether, according to the type of the terminal device After the semi-persistent scheduling mode is adopted for the terminal device, if the semi-persistent scheduling mode is adopted for the terminal device according to the type of the terminal device, the scheduling period for semi-persistent scheduling of the terminal device is determined as the period during which the terminal device sends the data packet.

In conjunction with the fifth possible implementation of the fourth aspect, in a sixth possible implementation manner of the fourth aspect, the network device may further include a second transmitter. The first receiver may be further configured to: after determining whether the terminal device adopts a semi-static scheduling manner according to the type of the terminal device, receive a service request message sent by the access network device, where the service request message is used by the terminal device to request to transmit data. The second transmitter may be configured to: send a response message to the access network device. If the processor determines to use the semi-static scheduling mode for the terminal device according to the type of the terminal device, the response message carries information for indicating that the terminal device uses the semi-persistent scheduling mode for scheduling, and is used to indicate that the terminal device is semi-static. Information about the scheduled scheduling period.

In a fifth aspect, a network device in a second communication system is provided, such as a PCRF, which network device can include a memory, a first receiver, a processor, and a first transmitter. The memory may be used to store instructions required by the processor to perform tasks, the first receiver may be configured to receive a policy request message, the policy request message may carry a communication identifier of the terminal device, and the processor may be configured to perform execution of the memory storage, according to the communication The identification determines the type of the terminal device, and the first transmitter can be configured to transmit information indicating the type of the terminal device to another network device in the communication system. The communication system may include at least two network devices, and the other network device may be one of the at least two network devices, such as an MME.

In conjunction with the fifth aspect, in a first possible implementation manner of the fifth aspect, the network device may further include a second receiver and a second transmitter. The determining, by the processor, the type of the terminal device according to the communication identifier, may be implemented by: sending, by the second sender, a query request message to the network device that stores the power information database, where the query request message may carry the communication identifier, and the power information database is stored The network device may be one of the at least two network devices, and the network device that stores the power information database and the network device that sends the policy request message are not the same network device, and then receives the stored power information library through the second receiving module. The network device responds to the query request message with information indicating the type of the terminal device. The information in the at least one terminal device may be stored in the power information database, where the information of each terminal device includes a type of the terminal device and a communication identifier of the terminal device.

With reference to the fifth aspect, in a second possible implementation manner of the fifth aspect, the determining, by the processor, the type of the terminal device according to the communication identifier may also be implemented by: between the stored communication identifier and the type of the terminal device Correspondence relationship determines the type of the terminal device.

In conjunction with the first possible implementation of the fifth aspect, in a third possible implementation manner of the fifth aspect, the processor is further configured to: receive, by the second receiver, a network device response that stores the power information database The information sent by the query request message for indicating the period in which the terminal device sends the data packet. The information in the at least one terminal device may be stored in the power information database, where the information of each terminal device includes the type of the terminal device and the communication identifier of the terminal device, and the information of each terminal device or the information of some terminal devices is further Including the period in which the terminal device sends a data packet.

With reference to the fifth aspect, in a fourth possible implementation manner of the fifth aspect, the processor is further configured to determine, according to the communication identifier, a period in which the terminal device sends the data packet, for example, by using the following manner: The correspondence between the type of the terminal device and the type of the terminal device is also determined.

In conjunction with the third possible implementation manner of the fifth aspect, or the fourth possible implementation manner, in a fifth possible implementation manner of the fifth aspect, the first transmitter may be further configured to: After determining the type of the terminal device, if the processor further determines, according to the communication identifier, the period in which the terminal device sends the data packet, sending, to the other network device, the terminal device to send the data. Information about the period of the package.

In a sixth aspect, an access network device is provided, such as a base station, and the access network device can include a memory, a first transmitter, a first receiver, and a processor. The memory may be used to store instructions required by the processor to perform a task, and the first transmitter may be configured to send a communication identifier of the terminal device to the network device to determine a type of the terminal device, where the first receiver may be configured to receive the network device to send The information indicating the type of the terminal device, the processor may be configured to execute the instruction of the memory storage, determine whether to adopt the semi-static scheduling manner for the terminal device according to the information indicating the type of the terminal device, or determine according to the type of the terminal device The scheduling method adopted by the terminal device.

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the access network device may further include a second receiver, where the second receiver may be configured to: send the terminal to the network device at the first transmitter Before the communication identifier of the device, the connection request sent by the terminal device is received, and the attachment request carries the communication identifier.

In conjunction with the first possible implementation of the sixth aspect, in a second possible implementation manner of the sixth aspect, the first transmitter may be configured to: if the processor determines that the terminal device sends the data packet in a periodic manner, Send a communication ID to the network device.

With reference to the sixth aspect or the first possible implementation manner or the second possible implementation manner of the sixth aspect, in a third possible implementation manner of the sixth aspect, the access network device may further include the second sending The second transmitter may be configured to: after the processor determines, according to information indicating a type of the terminal device, whether to adopt a semi-static scheduling manner for the terminal device, if the processor determines to adopt a semi-static scheduling manner for the terminal device, The terminal device sends information indicating that scheduling is performed in a semi-persistent scheduling manner, and information indicating a period in which the terminal device transmits the data packet.

In conjunction with the third possible implementation of the sixth aspect, in a fourth possible implementation manner of the sixth aspect, the access network device may further include a second receiver, where the second receiver may be used to: The second transmitter sends the information indicating the scheduling in the semi-persistent scheduling manner to the terminal device, and the information indicating the period of the data packet sent by the terminal device, and then receives the uplink scheduling request message sent by the terminal device, and the processor can also use the And: allocating the transmission resource in the semi-static scheduling mode to the terminal device according to the uplink scheduling request message.

In a seventh aspect, there is provided a network device in a third communication system, the network device comprising means for performing the method of any of the first aspect or the first aspect.

In an eighth aspect, a network device in a fourth communication system is provided, the network device comprising a module for performing the method of any one of the second aspect or the second aspect.

In a ninth aspect, there is provided another access network device, the access network device comprising means for performing the method of any one of the third aspect or the third aspect.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments of the present invention will be briefly described below. It is obvious that the following drawings are only some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

FIG. 1A is a networking diagram of a possible LTE system; FIG.

FIG. 1B is a network architecture diagram of another possible LTE system according to an embodiment of the present disclosure;

2 is a possible flowchart of a method for determining a scheduling mode of a terminal device in a first communication system according to an embodiment of the present disclosure;

FIG. 3 is a possible flowchart of a method for determining a scheduling manner of a terminal device in a second communication system according to an embodiment of the present disclosure;

4 is a possible flowchart of a method for determining a scheduling manner of a terminal device in a third communication system according to an embodiment of the present invention;

FIG. 5 is a flowchart of a possible method for determining a type of a terminal device according to an embodiment of the present invention;

FIG. 6 is a flowchart of a possible method for a base station to determine a scheduling manner of a terminal device according to an embodiment of the present disclosure;

FIG. 7 is a possible flowchart of a method for a terminal device to send a data packet according to a semi-persistent scheduling manner according to an embodiment of the present disclosure;

8A-8C are several possible structural diagrams of a first core network device according to an embodiment of the present invention. intention;

9A-9B are schematic diagrams of two possible structures of a second core network device according to an embodiment of the present invention;

10A-10B are schematic diagrams of two possible structures of an access network device according to an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of a first core network device according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of a second core network device according to an embodiment of the present disclosure;

FIG. 13 is a schematic structural diagram of an access network device according to an embodiment of the present disclosure.

detailed description

The technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without departing from the inventive scope are the scope of the embodiments of the present invention.

The techniques described herein may be used in various communication systems, such as LTE systems, 4.5G systems, or 5G systems, as well as other such communication systems or evolved systems that will emerge in the future. In addition, the technology described herein may be mainly applied to a power system, that is, the terminal device may include a terminal device deployed in the power system, for example, may include a terminal device deployed in a distribution network, and may include, for example, being deployed in a power distribution network. In the non-power system, the technology described in the present invention is not limited, and the method of the present invention is not limited. .

Hereinafter, some of the terms in the embodiments of the present invention will be explained to facilitate understanding by those skilled in the art.

1) A terminal device, which is a device that provides voice and/or data connectivity to a user, for example, may include a handheld device with wireless connectivity, or a processing device connected to a wireless modem. The terminal device can be connected to the core network via a Radio Access Network (RAN) Communication, exchange of voice and/or data with the RAN. The terminal device may include a UE, a wireless terminal device, a mobile terminal device, a Subscriber Unit, a Subscriber Station, a Mobile Station, a Mobile Station, a Remote Station, and a Pickup Station. Access Point (AP), Remote Terminal, Access Terminal, User Terminal, User Agent, User Device, etc. For example, it may include a mobile phone (or "cellular" phone), a computer with a mobile terminal device, a dedicated terminal device in a distribution network, such as a secondary device in a distribution network, such as various power meters, Electrical protection devices, or DC power supplies, portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices.

2) a network device, for example, including an access network device and a core network device, the access network device, for example, including a base station (for example, an access point), specifically may refer to an access network that passes through one or more sectors on an air interface. A device that communicates with a wireless terminal device. The base station can be used to convert the received radio frame to an Internet Protocol (IP) packet as a router between the wireless terminal device and the rest of the access network, wherein the remainder of the access network can include an IP network. The base station can also coordinate attribute management of the air interface. For example, the base station may be a Radio Network Controller (RNC) or a Base Station Controller (BSC), or may be an evolved base station in an evolved LTE system (LTE-Advanced, LTE-A). (NodeB or eNB or e-NodeB, evolutional Node B), the embodiment of the present invention is not limited.

The core network device includes, for example, a mobility management network element, and the mobility management network element includes, for example, a Mobility Management Entity (MME), or may also include other device types. The core network device may also include, for example, a Policy and Charging Rules Function (PCRF). Of course, the core network device may also include other possible devices, which are not limited in the embodiment of the present invention.

3) Dynamic scheduling mode. This resource scheduling mode needs to generate scheduling signaling once per subframe, and the terminal needs to read scheduling signaling every time the subframe is received. This scheduling method is more suitable for resource allocation and management of non-real-time services (such as HyperText Transfer Protocol (HTTP) services). It can effectively utilize the channel conditions fed back by the terminal device for resources. Scheduling, the method is more flexible. However, because each subframe needs to be scheduled, the signaling overhead is large.

4) Semi-Persistent Scheduling (SPS), which can also be called semi-persistent scheduling or semi-persistent scheduling. Unlike the dynamic scheduling, each transmission time interval (TTI) allocates radio resources to the terminal device. The SPS allows the radio resources to be semi-statically configured and periodically allocated to a specific terminal device. Briefly, the eNodeB can specify the radio resource used by the terminal device in a physical downlink control channel (PDCCH) that is scrambled by a certain TTI using a Cell Radio Network Temporary Identifier (C-RNTI), for example, It is called an SPS resource, and the terminal device uses the SPS resource to receive or transmit data packets every one cycle, and the eNodeB does not need to schedule the terminal device every cycle. Since the SPS has the characteristics of “one allocation, multiple use”, it is not necessary to schedule resources for the terminal device in each TTI, thereby reducing the PDCCH overhead. In general, the SPS is applicable to services with small data packets and fixed data packets, and needs to be periodically performed, which can effectively save signaling overhead.

5) The terms "system" and "network" in the embodiments of the present invention may be used interchangeably. "Multiple" means two or more. "and/or", describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately. In addition, the character "/", unless otherwise specified, generally indicates that the contextual object is an "or" relationship.

Referring to FIG. 1A, a networking architecture of a possible LTE system to which the embodiment of the present invention is applied is introduced. In FIG. 1, the terminal device can communicate with the base station, and the terminal device can have, for example, a Subscriber Identity Module (SIM) card, and an International Mobile Subscriber Identification Number (IMSI) stored in the SIM card. The number can be used as the communication identifier of the terminal device. Alternatively, the terminal device may have other possible communication identifiers as long as the communication identifier can be used to distinguish different terminal devices in the LTE system.

The base station can be respectively connected to a Serving GateWay (SGW) and an MME, and the MME can be respectively connected to the HSS and the SGW, and the SGW can be connected to the Packet Data Network (Packet Data Network). GateWay, PGW) connection, PGW can be connected to PCRF, in addition, PGW can access the grid service system through IP network.

FIG. 1B is a networking architecture of another possible LTE system according to an embodiment of the present invention. Different from FIG. 1A, the PCRF can also be connected to the power information library, or the PCRF can be connected to the network device storing the power information library.

Optionally, the power information database may be used to manage the terminal devices in the power grid. For example, the power information library may store information of all terminal devices or some terminal devices in the power grid, and the information of each terminal device may include the terminal device. a communication identifier, an identification number (ID) of the terminal device, and a type of the terminal device, wherein the type of the terminal device may include, for example, a relay protection device or a measurement device, etc., as long as it is a primary device in the distribution network and/or The type of the secondary device may be the type of the terminal device. The primary device may include, for example, a relay protection device, a DC power supply device, a voltmeter, an ammeter, or a power meter, and the secondary device may include, for example, a feeder terminal unit (FTU) and a power distribution terminal unit ( Distribution Terminal Unit (DTU), or Equipment Terminal Unit (TTU). Optionally, if the terminal device is a device that needs to periodically report the service, the information of the terminal device that is stored in the power information database may further include a period in which the terminal device sends the data packet when periodically reporting the service. For example, the power information database may store one or more management tables, and one or more entries may be included in the management table, and each entry may store information of one terminal device in the power grid. For a terminal device, as long as the communication identifier of the terminal device or the ID of the terminal device is known, it is convenient to query the power information database for other possible information of the terminal device, such as the type of the terminal device. Alternatively, the power information base may be maintained by the power grid company, and the information of the terminal equipment in the power grid may be entered by the power grid company.

The terminal device in FIG. 1A and FIG. 1B may be a common terminal device, or may be a terminal device deployed in a power system, such as a terminal device deployed in a distribution network, such as in a distribution network. A primary device or a secondary device. For example, if the functions of the primary device and the secondary device can be integrated into one device, the terminal device can also be such a device.

The method provided by the embodiment of the present invention is described below with reference to the accompanying drawings.

Referring to FIG. 2, a method for determining a scheduling manner of a terminal device in a first communication system is provided. The method may be applied to the architecture of FIG. 1A or FIG. 1B, and the process of the method is described as follows:

Step 201: Receive a communication identifier of the terminal device.

Step 202: Determine a type of the terminal device according to the communication identifier.

Step 203: Determine whether to adopt a semi-static scheduling manner for the terminal device according to the type of the terminal device. Or determining a scheduling manner adopted by the terminal device according to the type of the terminal device.

Referring to FIG. 3, a method for determining a scheduling manner of a terminal device in a second communication system is provided. The method may be applied to the architecture of FIG. 1A or FIG. 1B. The process of the method is described as follows:

Step 301: Receive a policy request message sent by another network device in the communication system, where the policy request message carries a communication identifier of the terminal device.

Step 302: Determine a type of the terminal device according to the communication identifier.

Step 303: Send information indicating the type of the terminal device to another network device; wherein the communication system includes at least two network devices, and the other network device is one of the at least two network devices.

Referring to FIG. 4, a method for determining a scheduling manner of a terminal device in a third communication system is provided. The method may be applied to the architecture of FIG. 1A or FIG. 1B. The process of the method is described as follows:

Step 401: Send a communication identifier of the terminal device to the network device to determine a type of the terminal device.

Step 402: Receive information that is sent by the network device to indicate the type of the terminal device.

Step 403: Determine whether to adopt a semi-static scheduling manner for the terminal device according to the information used to indicate the type of the terminal device. Or determining a scheduling manner adopted by the terminal device according to the type of the terminal device.

Optionally, the type of the terminal device may also be referred to as the service type of the terminal device.

Optionally, the terminal device may include a common terminal device, or may also include a terminal device in the power system.

For example, the methods of Figures 2, 3, and 4 may be performed by different network devices, or may be performed by other possible devices. For example, another network device mentioned in step 303 in FIG. 3 may be a network device that performs the method of FIG. 2. For example, the network device mentioned in FIG. 4 may also be implemented in FIG. 2. The method of the network device.

For example, if the device performing the method of FIG. 2 is a network device, the network device may be a core network device, or may be an access network device. For example, if the network device is a core network device, the network device may be used. It is called a first core network device, for example, the first core network device may be an MME, or may be other possible core network devices.

For example, if the device that performs the method of FIG. 3 is a network device, the network device may be a core network device, or may be an access network device. For example, if the network device is a core network device, the network device may be used. It is called a second core network device, for example, the second core network device may be a PCRF, or may be other possible core network devices.

For example, if the device performing the method of FIG. 4 is a network device, the network device may be a core network device, or may be an access network device. For example, if the network device is an access network device, the access network The device may be a base station or other possible access network devices.

Similarly, the network device that performs the method of FIG. 3 may also be a core network device or an access network device, and the network device that performs the method of FIG. 4 may also be a core network device or an access network device.

Figures 2, 3 and 4 show the corresponding methods, which are described below with a few examples. In the following description, the device that performs the method of FIG. 2 is the first core network device, the device that performs the method of FIG. 3 is the second core network device, and the device that performs the method of FIG. 3 is the access network device. . In the following example, the UE in the first core network device is the MME, the second core network device is the PCRF, the access network device is the base station, and the terminal device is the active distribution network wide area relay protection service.

example 1

Please refer to FIG. 5, which is an example of determining the type of the terminal device.

1. The UE performs an attach procedure. For example, when the UE is just powered on, an attach procedure is required. Then the UE sends an attach request.

2. After receiving the Attach Request sent by the UE, the base station sends an initial UE message to the MME, and the MME can acquire the communication identifier of the UE. After obtaining the communication identifier of the UE, the MME can complete the processes of authentication, encryption, and the like. If the UE is configured with a SIM card, for example, the communication identifier of the UE is, for example, the IMSI number of the UE, or the communication identifier of the UE may be other possible. information.

Optionally, step 1 may occur when the radio resource control (RRC) connection establishment is completed. For example, when the RRC connection setup is complete, the UE may send an RRC connection setup complete (RRCConnectionSetupComplete) message to the base station, where the RRCConnectionSetupComplete message is received. The Attach request may include a non-access stratum (NAS) layer. The base station may send an Initial UE message to the MME, where the Attach request may be carried in the Initial UE Message.

3. The MME determines the type of the UE according to the communication identifier of the UE.

Optionally, the MME determines the type of the UE according to the communication identifier of the UE, and may have different manners, which are respectively introduced below.

The first way:

Optionally, the information of one or more terminal devices may be stored in the MME in advance, and the information of the terminal device may include the communication identifier of the terminal device, the ID of the terminal device, and the type of the terminal device, optionally, if The terminal device is a device that needs to perform a periodic reporting service, and the information of the terminal device may further include a period in which the terminal device sends a data packet when periodically reporting the service.

In this manner, after obtaining the communication identifier of the UE, the MME may perform a local query to determine whether the communication identifier of the UE is stored locally. If the communication identifier of the UE is stored locally, the MME may obtain the locally stored UE. Other information, for example, may acquire the ID of the UE stored locally, the type of the UE, and the like. Optionally, if the period in which the UE sends the data packet is also stored locally, the MME may also obtain a period in which the UE sends the data packet according to the communication identifier of the UE.

The second way:

The MME may send a policy request message to the PCRF through the SGW and the PGW. The policy request message may carry information such as the communication identifier of the UE. The PCRF may obtain information such as the type of the UE according to the communication identifier of the UE, and may obtain information such as the type of the UE. The MME sends the information to the MME, so that the MME acquires the type of the UE. Figure 5 takes this as an example. Optionally, if the PCRF acquires the period in which the UE sends the data packet in addition to the type of the UE, the PCRF may also send the data packet to the UE. The MME sends the MME so that the MME can obtain the period in which the UE sends the data packet.

After obtaining the type of the terminal device, the MME may determine the scheduling mode of the terminal device, or determine the scheduling mode adopted by the terminal device according to the type of the terminal device. Optionally, the MME may pre-store the correspondence between the type of the terminal device and the scheduling mode of the terminal device, and the MME only knows the scheduling mode of the terminal device as long as it knows the type of the terminal device. For example, the scheduling mode of some types of primary devices and/or secondary devices in the distribution network stored in the MME is a semi-static scheduling mode.

Optionally, for the first mode and the second mode, the MME may be used separately. For example, the MME may be pre-configured to use the first mode or the second mode, or the first mode and the second mode may be used together. For example, the MME may first use the first mode. In this manner, the MME only needs to obtain information such as the type of the terminal device according to the local storage, and does not need to perform excessive interaction with the network device such as the PCRF. The transmission resource is saved. If the communication identifier of the terminal device is not queried in the first manner, that is, the MME may not store the information of the terminal device, the MME may continue to use the second mode, that is, obtain by the PCRF, and increase the acquisition terminal device. The way of information further ensures that information such as the type of terminal device can be obtained.

Optionally, the PCRF obtains information such as the type of the UE according to the communication identifier of the UE, and may also be implemented in different manners.

Mode 1: Optionally, the information of one or more terminal devices may be stored in the PCRF in advance, and the information of the terminal device may include the communication identifier of the terminal device, the ID of the terminal device, and the type of the terminal device, optionally If the terminal device is a device that needs to periodically report the service, the information of the terminal device may further include a period in which the terminal device sends a data packet when periodically reporting the service.

In this manner, after receiving the communication identifier of the UE sent by the MME, the PCRF may perform a local query to determine whether the communication identifier of the UE is stored locally. If the communication identifier of the UE is stored locally, the PCRF may obtain the local storage. Other information of the UE, for example, may obtain the ID of the UE stored locally, the type of the UE, and the like. Optionally, if the period in which the UE sends the data packet is also stored locally, the PCRF may also obtain the period in which the UE sends the data packet according to the communication identifier of the UE. PCRF can The information of the acquired UE is sent to the MME by using the PGW and the SGW, for example, including the type of the UE, or the type of the UE, the period during which the UE sends the data packet, and the like.

Mode 2: The PCRF may send a query request message to the network device that stores the power information database, where the query request message may carry information such as the communication identifier of the UE, and the network device that stores the power information database may be in the power information database according to the communication identifier of the UE. The information about the type of the UE is queried, and information about the type of the acquired UE is sent to the PCRF, so that the PCRF acquires information such as the type of the UE. Figure 5 takes this as an example. Optionally, if the period in which the UE sends the data packet is also stored in the power information database, the network device that stores the power information database may acquire the period in which the UE sends the data packet in addition to the type of the UE, and then the power is stored. The network device of the information base can also send the period in which the UE sends the data packet to the PCRF, so that the PCRF can acquire the period in which the UE sends the data packet. The PCRF may send the acquired information of the UE to the MME through the PGW and the SGW, for example, including the type of the UE, or the type of the UE, the period in which the UE sends the data packet, and the like.

Optionally, for mode 1 and mode 2, the PCRF may be used separately. For example, the PCRF may be pre-configured to use the first mode or the second mode, or the first mode and the second mode may be used together, for example, PCRF. The first method can be used first. In this way, the PCRF only needs to obtain information such as the type of the terminal device according to the local storage, and does not need to perform excessive interaction with the network device storing the power information database, which is relatively simple. The transmission resource is saved. If the communication identifier of the terminal device is not queried in the first manner, that is, the PCRF may not store the information of the terminal device, the PCRF may continue to use the second mode, that is, the network device that stores the power information database. To obtain, because the information stored in the power information database may be more, the possibility of acquiring the information of the terminal device is greater, which may increase the success rate of acquiring the information of the terminal device, and further ensure that information such as the type of the terminal device can be obtained. Thereby, suitable scheduling can be performed on the terminal device.

5 is an example in which the MME adopts the second mode and the PCRF adopts mode 2, that is, step 3 of FIG. 5 is that the MME sends a policy request message to the PCRF, and step 4 is that the PCRF sends a query request message to the network device that stores the power information database. Step 5: The network device that stores the power information database sends the queried UE type to the PCRF, and the network device that stores the power information database in step 5 can also send the UE to send the data packet to the PCRF. Step 6 is PCRF. Send the type of the UE to the MME and send the UE The period of the packet. Among them, the network device storing the power information database is shown as the network device 1 in FIG.

Optionally, FIG. 5 only introduces some steps related to the embodiment of the present invention in the attach procedure of the UE, and does not fully describe the entire attach process of the UE. Those skilled in the art naturally know that the steps introduced in FIG. 5 are respectively UE. Which steps in the attach process, as well as which steps the unattached steps in Figure 5 are included, should be known to the UE.

Example 2

Example 1 describes how the MME determines the type of the UE, and can determine the scheduling mode of the UE according to the type of the UE. Example 2 describes how the base station learns the scheduling mode of the UE. See Figure 6.

The UE initiates a service request (Service Request) message, and the service request message may be used to request to transmit a data packet. The service request message may carry the communication identifier of the UE, and may also carry the service type of the service to which the data packet requested to be transmitted belongs. And other information. The UE may forward the service request message to the MME through the base station.

Optionally, the service request message may be a service request message that is initiated by the UE for the first time. The initial initiation of the service request message may be, for example, a service request message that is first initiated by the UE after the attachment is completed. For example, the service is used as an example. The request message may also be a service request message initiated by the UE at any time. For example, the UE may initiate multiple service request messages after the attachment is completed, and the service request message may be any service request message initiated by the UE.

2. The MME determines that the type of the UE for the call is a relay protection device.

Optionally, the MME may store a correspondence between the type of the terminal device and the scheduling mode of the terminal device, and the MME may determine, according to the type of the terminal device, a scheduling manner used by the UE. Optionally, the MME may further store a correspondence between the communication identifier of the terminal device and the type of the terminal device. After receiving the service request message, the MME may first determine the type of the terminal device according to the communication identifier of the terminal device carried in the service request message. Then, according to the type of the terminal device, the scheduling mode that should be adopted for the terminal device is determined.

3. The MME sends a response message to the base station for the service request message, and the response message may be, for example, an Initial Context Setup Request message.

Optionally, if the MME determines, according to the type of the UE, that the UE is a device that needs to be scheduled in a semi-persistent scheduling manner, the MME may carry the initial context setup request to indicate that the UE is scheduled by using a semi-persistent scheduling manner. The information, and may also carry information indicating a scheduling period for semi-persistent scheduling of the UE.

Optionally, if the MME determines that the UE is a device that needs to be scheduled in a semi-persistent scheduling manner, the MME may obtain a period in which the UE sends a data packet, or the MME may have obtained the process in the step shown in step 1. The period in which the UE sends the data packet, for example, the MME may have obtained the period in which the UE sends the data packet according to the locally stored information of the UE, or the MME has received the period in which the PCRF sends the data packet according to the policy request message.

Then, the MME may determine the period in which the UE sends the data packet as a scheduling period for semi-persistent scheduling of the UE, for example, N milliseconds, where N is an integer greater than 0. In this way, the moment when the UE needs to send the data packet is exactly the time when the UE can send the data packet, and the UE can be scheduled in a timely manner.

4. The base station sends an RRC Connection Reconfiguration (RRCConnectionReconfiguration) message to the UE to perform bearer reconfiguration on the UE. The identifier of the semi-persistent scheduling mode may be configured for the UE, that is, the information for indicating the scheduling in the semi-persistent scheduling mode is sent to the UE. For example, the identifier of the semi-persistent scheduling mode may be an SPS C-RNTI, and may be configured for the UE. The scheduling period of the semi-persistent scheduling is to send information to the UE for indicating the period in which the UE sends the data packet, for example, the scheduling period is N milliseconds.

5. The UE saves the identifier of the semi-persistent scheduling mode configured by the base station and the scheduling period for performing semi-persistent scheduling. For example, the identifier of the semi-persistent scheduling mode is SPS C-RNTI, and the scheduling period of semi-persistent scheduling is N milliseconds.

6. The UE returns an RRC Connection Reconfiguration Complete message (RRCConnectionReconfigurationComplete) message to the base station to confirm that the RRC connection reconfiguration has been completed.

Example 3

Example 1 describes how the MME determines the scheduling mode of the UE according to the type of the UE. In the example 2, the base station learns the scheduling mode of the UE and configures the scheduling mode of the UE to the UE. Example 3 describes how the UE is based on the examples 1 and 2. Semi-static scheduling mode sends data packets, that is, after the UE is attached, how to semi-static The scheduling method sends a packet. See Figure 7.

If the UE needs to send a data packet to the base station, the UE may send an uplink scheduling request message to the base station, for example, the uplink scheduling request message is a scheduling request, and the UE sends a Buffer Status Report message to the base station. In order to inform the base station of the size of the data packet stored in the current UE's uplink buffer (Buffer), thereby assisting the base station to perform uplink scheduling resource calculation.

In the first step, the base station performs the first semi-persistent scheduling on the UE, that is, the base station needs to allocate semi-statically scheduled resources to the UE.

2. The base station allocates corresponding time-frequency resources to the UE in a semi-persistent scheduling mode and a scheduling period of N milliseconds, and informs the UE of the allocated time-frequency resources.

For example, the base station may inform the UE of the allocated time-frequency resources through an uplink grant (UL Grant) message.

3. After receiving the UL Grant message, the UE activates the semi-persistent scheduling mode, and transmits the time-frequency resources allocated by the base station to the base station data packet.

For example, the UE may send a data packet by using a UL data message. Moreover, the data packets to be sent by the UE may be sent by using a UL data message, and may be sent once every N milliseconds through the time-frequency resource allocated by the base station.

For example, the example 1 to the example 3 are all based on the attachment process of the terminal device. In an actual application, the process of determining the type of the terminal device to schedule the terminal device in the embodiment of the present invention is not limited to the terminal device. The attaching process may be, for example, a process performed after the terminal device is attached, for example, before the terminal device initiates any service request message, or when the terminal device initiates any service request message, the method provided by the embodiment of the present invention may be performed. Program.

For example, after the terminal device in the active distribution network wide-area relay protection service is attached, the access network device can schedule the terminal device in a conventional manner. For example, the general conventional mode is a dynamic scheduling mode. The terminal device initiates a service request message to the access network device, and the access network device schedules the terminal device by using a dynamic scheduling manner, and receives the data packet sent by the terminal device. Optionally, the access network device can monitor the sending process of the terminal device. For example, after the access network device monitors the preset duration, the access device can determine the law of sending the data packet by the terminal device, for example, the terminal device sends the Whether the time for sending a data packet is irregular or always sent according to a certain period. For example, if the terminal device always sends a data packet according to a certain period, whether the size of the data packet sent by the terminal device is relatively fixed each time, For example, if the access network device determines through monitoring that the terminal device always sends a data packet according to a certain period, or determines by monitoring that the terminal device always sends a data packet according to a certain period, and compares the size of each sent data packet. The access network device can send the communication identifier of the terminal device to the first core network device, so as to obtain the type of the terminal device by performing the method provided by the embodiment of the present invention, for example, the access network device obtains the terminal device. After the type is determined, the terminal device is configured to be scheduled by the semi-persistent scheduling mode, and the access network device may change the scheduling mode of the terminal device, and then re-schedule the terminal device by using a semi-static scheduling mode. Monitoring of access network equipment can also be applied to the terminal equipment in a suitable manner. Line dispatch, try to save transmission resources, it is possible to try to meet the needs of different services. If the access network device obtains the type of the terminal device, and determines that the terminal device is not a device that needs to be scheduled by using a semi-persistent scheduling mode, the access network device may continue to use the dynamic scheduling mode to schedule the terminal device.

Because the fixed-packet period and the size of the transmitted data packet are fixed, the semi-persistent scheduling mode can reduce the overhead of control information, and does not generate additional scheduling delay due to dynamic scheduling, which reduces the end-to-end transmission delay. Compared with the dynamic scheduling mode, the semi-static scheduling mode has a higher priority than the dynamic scheduling mode. The semi-static scheduling mode uses less efficient time-frequency resources than the dynamic scheduling mode. Enabling the semi-static scheduling mode may reduce the utilization efficiency of time-frequency resources, and some violate the original intention of the dynamic scheduling resource pool design of the LTE system. Therefore, for the application of the grid business, it is more inclined to adopt a semi-static scheduling method for a service with a fixed delivery period and a fixed data packet size, while other services try to adopt a dynamic scheduling method. For example, in the case of a distribution network, if a terminal device is preset as a terminal device that needs to be scheduled by a semi-persistent scheduling mode, the terminal device may be considered to require a one-way delay and the transmitted data packet is The size is relatively fixed, and the frequency of sending packets is relatively high. For example, in general, the relay protection device has these requirements, or it can be considered that the terminal device not only has the above requirements, but also the service performed by the terminal device may be important, then Such terminal equipments are guaranteed to be semi-statically scheduled to meet the requirements of the corresponding services. For example, the requirements of the active distribution network wide-area relay protection service can be met as much as possible. If the terminal device is not pre-configured for a terminal device, the terminal device needs to be scheduled by the semi-persistent scheduling mode, or the terminal device that is not required to be scheduled by the semi-persistent scheduling mode is preset for a terminal device. Or pre-setting a terminal device as a terminal device that needs to be scheduled by a dynamic scheduling manner. Generally, the service performed by the device may not be very important, or may not have a requirement for one-way delay. So high, such as the sensor in the distribution network, it is generally sent periodically when sending data packets, and the size of the data packet is relatively fixed, the packet transmission frequency may be relatively high, but its requirement for one-way delay may not be too High, then for this kind of equipment, you can continue to use dynamic scheduling to schedule, and try to leave semi-static scheduling to more demanding terminal equipment to meet the basic requirements of LTE system while meeting the needs of different services. .

The device provided by the embodiment of the present invention is described below with reference to the accompanying drawings.

Referring to FIG. 8A, based on the same inventive concept, a network device in a first communication system is provided, which may include a memory 801, a processor 802, and a first receiver 803.

The processor 802 may include, for example, a central processing unit (CPU) or an application specific integrated circuit (ASIC), and may include one or more integrated circuits for controlling program execution, and may include using a field programmable gate. A hardware circuit developed by a Field Programmable Gate Array (FPGA) may include a baseband chip.

The number of memories 801 may be one or more. The memory 801 may include a Read Only Memory (ROM), a Random Access Memory (RAM), and a disk storage, and the like. The memory 801 can be used to store instructions required by the processor 802 to perform tasks, and can also be used to store data.

The first receiver 803 can be used for network communication with an external device, and is mainly used for communicating with an access network device, for example, by using a network such as an Ethernet, a radio access network, a wireless local area network, or a wired network and an access network device. Communication.

The memory 801 and the first receiver 803 can be connected to the processor 802 via the bus 800 (Fig. 8A as an example), or can also be connected to the processor 802 through a dedicated connection line.

Optionally, referring to FIG. 8B, the network device may further include a first transmitter 804 and a second receiver 805, where the first transmitter 804 and the second receiver 805 can be used for network communication with an external device, where The first transmitter 804 is mainly used for communicating with the core network device, for example, for communicating with the second core network device as described above, and the second receiver 805 is mainly for communicating with the core network device, for example, It can also be used to communicate with the second core network device as described above. For example, the first transmitter 804 and the second receiver 805 can communicate with the core network through a network such as Ethernet, a wireless access network, a wireless local area network, or a wired network. The device communicates.

The memory 801, the first receiver 803, the first transmitter 804, and the second receiver 805 may be connected to the processor 802 through the bus 800 (as shown in FIG. 8B), or may be connected to the processor through a dedicated connection line. 802 connection.

Optionally, referring to FIG. 8C, the network device may further include a second transmitter 806, where the second transmitter 806 can be used for network communication with an external device, for example, mainly for communicating with the access network device, for example, The two transmitters 806 can communicate with the access network devices through a network such as Ethernet, a radio access network, a wireless local area network, or a wired network.

The memory 801, the first receiver 803, the first transmitter 804, the second receiver 805, and the second transmitter 806 may be connected to the processor 802 via the bus 800 (as shown in FIG. 8C), or may also be specialized. The connection line is connected to the processor 802.

Optionally, the first transmitter 804 and the second transmitter 806 may be two independent functional modules, or may be the same functional module, that is, may be combined into one transmitter, the first receiver 803 and the second receiving. The 805 can be two independent functional modules, or can be the same functional module, that is, can be combined into one receiver.

By programming the processor 802, the code corresponding to the method shown above is solidified into the chip, thereby enabling the chip to perform the method shown in the previous embodiment while it is running. How to design and program the processor 802 is a technique well known to those skilled in the art, and details are not described herein.

The network device can be used to perform the method described above with respect to Figures 2-7, and can be, for example, a first core network device as previously described. Therefore, for the functions implemented by each unit in the device, etc., reference can be made. As described in the previous method section, I will not repeat them.

Referring to FIG. 9A, based on the same inventive concept, a network device in a second communication system is provided. The device may include a memory 901, a processor 902, a first receiver 903, and a first transmitter 904.

The processor 902 may include, for example, a CPU or an ASIC, and may include one or more integrated circuits for controlling program execution, may include hardware circuits developed using an FPGA, and may include a baseband chip.

The number of memories 901 may be one or more. The memory 901 may include a ROM, a RAM, and a disk storage, and the like. The memory 901 can be used to store instructions required by the processor 902 to perform tasks, and can also be used to store data.

The first receiver 903 can be used for network communication with an external device, and is mainly used for communicating with a core network device, for example, can be used for communication by the first core network device as described above, and the first transmitter 904 can Used for network communication with an external device, mainly for communicating with a core network device, for example, for communication with a first core network device as described above, such as a first receiver 903 and a first transmitter 904 It can communicate with core network devices through networks such as Ethernet, wireless access networks, wireless LANs, or wired networks.

The memory 901, the first receiver 903, and the first transmitter 904 may be coupled to the processor 902 via the bus 900 (as exemplified in FIG. 9A), or may be coupled to the processor 902 via a dedicated connection line.

Optionally, referring to FIG. 9B, the network device may further include a second receiver 905 and a second transmitter 906. Both the second receiver 905 and the second transmitter 906 can be used for network communication with an external device, for example. The second receiver 905 and the second transmitter 906 can be mainly used to communicate with the network device storing the power information library as described above, for example, the second receiver 905 and the second transmitter 906 can be connected via Ethernet, wireless. A network or a wired network such as an access network or a wireless local area network communicates with a network device that stores a power information base as described above.

The memory 901, the first receiver 903, the first transmitter 904, the second receiver 905, and the second transmitter 906 may be connected to the processor 902 via the bus 900 (as shown in FIG. 9B), or may also be specialized. The connection line is connected to the processor 902.

Optionally, the first receiver 903 and the second receiver 905 may be two independent functional modules, or may be the same functional module, and may be combined into one receiver, the first transmitter 904 and the second sending. The 906 may be two functional modules that are independent of each other, or may be the same functional module, and may be combined into one transmitter.

By programming the processor 902, the code corresponding to the method shown above is solidified into the chip, thereby enabling the chip to perform the method shown in the previous embodiment while it is running. How to design and program the processor 902 is a technique known to those skilled in the art, and details are not described herein again.

The network device may be used to perform the method described in FIG. 3, FIG. 5 to FIG. 7, and may be, for example, a second core network device as described above. Therefore, for the functions and the like implemented by the units in the network device, reference may be made to the description of the previous method part, and details are not described herein.

Referring to FIG. 10A, based on the same inventive concept, an access network device is provided. The access network device may include a memory 1001, a processor 1002, a first receiver 1003, and a first transmitter 1004.

The processor 1002 may include, for example, a CPU or an ASIC, and may include one or more integrated circuits for controlling program execution, may include hardware circuits developed using an FPGA, and may include a baseband chip.

The number of memories 1001 may be one or more. The memory 1001 may include a ROM, a RAM, and a disk storage, and the like. The memory 1001 can be used to store instructions required by the processor 1002 to perform tasks, and can also be used to store data.

The first receiver 1003 can be used for network communication with an external device, mainly for communicating with a core network device, for example, can be used for communication by the first core network device as described above, and the first transmitter 1004 can be used for Network communication with an external device, mainly for communicating with a core network device, for example, for communication with a first core network device as described above, for example, the first receiver 1003 and the first transmitter 1004 can pass A network or a wired network such as an Ethernet, a wireless access network, or a wireless local area network communicates with a core network device.

The memory 1001, the first receiver 1003, and the first transmitter 1004 may be connected to the processor 1002 via the bus 1000 (as shown in FIG. 10A), or may be connected to the processor 1002 through a dedicated connection line.

Optionally, referring to FIG. 10B, the access network device may further include a second receiver 1005. Optionally, referring to FIG. 10B, the access network device may further include a second transmitter 1006. Both the second receiver 1005 and the second transmitter 1006 can be used for network communication with an external device. For example, the second receiver 1005 and the second transmitter 1006 can be mainly used to communicate with the terminal device, for example, the second receiver 1005. And the second transmitter 1006 can communicate with the terminal device through a network such as an Ethernet, a wireless access network, or a wireless local area network.

The memory 1001, the first receiver 1003, the first transmitter 1004, the second receiver 1005, and the second transmitter 1006 may be connected to the processor 1002 via the bus 1000 (as shown in FIG. 10B), or may also be specialized. The connection line is connected to the processor 1002.

Optionally, the first receiver 1003 and the second receiver 1005 may be two independent functional modules, or may be the same functional module, that is, may be combined into one receiver, the first transmitter 1004 and the second sending. The device 1006 can be two independent functional modules, or can be the same functional module, that is, can be combined into one transmitter.

By design programming the processor 1002, the code corresponding to the method shown above is solidified into the chip, thereby enabling the chip to perform the method shown in the previous embodiment while it is running. How to design and program the processor 1002 is a technique well known to those skilled in the art, and details are not described herein again.

The access network device may be used to perform the method described in FIG. 2, FIG. 4 to FIG. 7, and may be, for example, an access network device as described above. Therefore, for the functions and the like implemented by the units in the device, reference may be made to the description of the previous method section, and details are not described herein.

Referring to FIG. 11, based on the same inventive concept, a network device in a third communication system is provided. The network device may include a first receiving module 1101 and a processing module 1102.

Optionally, the network device may further include a first sending module 1103 and a second receiving module 1104.

Optionally, the network device may further include a second sending module 1105.

Wherein, each module introduced as above is shown in FIG. 11, and obviously, FIG. 11 is only a possible structural diagram of the device.

In a practical application, the physical device corresponding to the first receiving module 1101 may be the first receiver 803 in FIG. 8A, FIG. 8B or FIG. 8C, and the physical device corresponding to the processing module 1102 may be FIG. 8A and FIG. 8B. Or the processor 802 in FIG. 8C, the physical device corresponding to the first sending module 1103 may be the first transmitter 804 in FIG. 8B or FIG. 8C, and the physical device corresponding to the second receiving module 1104 may be in FIG. 8B or FIG. 8C. The second receiver 804, the physical device corresponding to the second sending module 1105, may be the second transmitter 806 in FIG. 8C.

The network device can be used to perform the method described above with respect to Figures 2-7, and can be, for example, a first core network device as previously described. Therefore, for the functions and the like implemented by the units in the network device, reference may be made to the description of the previous method part, and details are not described herein.

Referring to FIG. 12, based on the same inventive concept, a network device in a fourth communication system is provided. The network device may include a first receiving module 1201, a processing module 1202, and a first sending module 1203.

Optionally, the network device may further include a second receiving module 1204 and a second sending module 1205.

Wherein, each module introduced as above is shown in FIG. 12, then obviously, FIG. 12 is only a possible structural diagram of the network device.

In a practical application, the physical device corresponding to the first receiving module 1201 may be the first receiver 903 in FIG. 9A or FIG. 9B, and the physical device corresponding to the processing module 1202 may be the processor 902 in FIG. 9A or FIG. 8B. The physical device corresponding to the sending module 1203 may be the first transmitter 904 in FIG. 9A or FIG. 9B, and the physical device corresponding to the second receiving module 1204 may be the second receiver 905 in FIG. 9B, and the second sending module 1205 corresponds to The physical device may be the second transmitter 906 in Figure 9B.

Referring to FIG. 13, based on the same inventive concept, another access network device is provided. The access network device may include a first receiving module 1301, a processing module 1302, and a first sending module 1303.

Optionally, the access network device may further include a second receiving module 1304.

Optionally, the access network device may further include a second sending module 1305.

Wherein, each module introduced as above is shown in FIG. 13, and obviously, FIG. 13 is only a possible structural diagram of the access network device.

In a practical application, the physical device corresponding to the first receiving module 1301 may be FIG. 10A or FIG. 10B. The first receiver 1003, the physical device corresponding to the processing module 1302 may be the processor 1002 in FIG. 10A or FIG. 10B, and the physical device corresponding to the first sending module 1303 may be the first transmitter in FIG. 10A or FIG. 10B. 1004. The physical device corresponding to the second receiving module 1304 may be the second receiver 1005 in FIG. 10B, and the physical device corresponding to the second sending module 1305 may be the second transmitter 1006 in FIG. 10B.

The access network device may be used to perform the method described in FIG. 2, FIG. 4 to FIG. 7, and may be, for example, an access network device as described above. Therefore, for the functions and the like implemented by the units in the access network device, reference may be made to the description of the previous method part, and details are not described herein.

Alternatively, FIGS. 8A-13 are only possible schematic diagrams of the device, wherein the location of each module does not represent an actual situation.

In the embodiment of the present invention, the type of the terminal device may be determined according to the communication identifier of the terminal device, so that whether the terminal device adopts a semi-static scheduling manner according to the type of the terminal device, for example, a large number of cycles are required for the distribution network. The terminal equipment of the serviced service, such as the terminal equipment of the active distribution network wide-area relay protection service, may be set to a device that needs to be scheduled in a semi-persistent scheduling manner, so that half of the terminal equipment can be used. The static scheduling mode performs scheduling. The semi-static scheduling mode can save a large amount of signaling overhead compared to the dynamic scheduling mode. At the same time, because the interaction process of the scheduling signaling is reduced, the communication delay is reduced, and the communication delay can be satisfied as much as possible. The business needs of the distribution network, for example, can satisfy the demand of the one-way communication delay for the active distribution network wide-area relay protection service. According to the manner provided by the embodiment of the present invention, a corresponding scheduling manner can be set according to the type of the terminal device in advance, so that different scheduling modes can be adopted for different terminal devices, which are more flexible and can better satisfy different terminal devices and Different business needs.

In the present invention, it should be understood that the disclosed apparatus and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit or unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed. Another point, the mutual coupling or direct coupling or communication shown or discussed The letter connection may be an indirect coupling or communication connection through some interface, device or unit, and may be in electrical or other form.

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

The functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may also be an independent physical module.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the technical solution of the present invention may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device, such as a personal computer. , a server, or a network device or the like, or a processor performs all or part of the steps of the method of the various embodiments of the present invention. The foregoing storage medium includes: a universal serial bus flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, and the like, which can store program codes.

The above embodiments are only used to describe the technical solutions of the present invention in detail, but the description of the above embodiments is only for the purpose of facilitating the understanding of the embodiments of the present invention, and should not be construed as limiting the embodiments of the present invention. Variations or substitutions that may be readily conceived by those skilled in the art are intended to be included within the scope of the present invention.

Claims

A method for determining a scheduling mode of a terminal device in a communication system, comprising:

Receiving a communication identifier of the terminal device;

Determining a type of the terminal device according to the communication identifier;

Determining whether to adopt a semi-static scheduling manner for the terminal device according to the type of the terminal device.
The method of claim 1, wherein the communication system further comprises another network device, determining the type of the terminal device according to the communication identifier, comprising:

Sending a policy request message to the another network device, where the policy request message carries the communication identifier;

Receiving, by the another network device, information indicating a type of the terminal device in response to the policy request message.
The method of claim 2, wherein the method further comprises:

And receiving, by the another network device, information, in response to the policy request message, indicating a period in which the terminal device sends a data packet.
The method according to claim 3, further comprising: after determining whether to apply the semi-static scheduling mode to the terminal device according to the type of the terminal device, further comprising:

If it is determined that the semi-persistent scheduling mode is adopted for the terminal device according to the type of the terminal device, determining that the scheduling period for semi-persistent scheduling of the terminal device is a period for the terminal device to send a data packet.
The method according to claim 4, further comprising: after determining whether to apply the semi-static scheduling mode to the terminal device according to the type of the terminal device, further comprising:

Receiving a service request message sent by the access network device; the service request message is used by the terminal device to request to transmit a data packet;

Sending a response message to the access network device, where the response message is used to indicate that the terminal device is used in a half manner, if the semi-static scheduling mode is adopted for the terminal device according to the type of the terminal device. Static scheduling mode for scheduling information and for indicating to the terminal Information on the scheduling period for semi-persistent scheduling.
A method for determining a scheduling mode of a terminal device in a communication system, comprising:

Receiving a policy request message sent by another network device in the communication system, where the policy request message carries a communication identifier of the terminal device;

Determining a type of the terminal device according to the communication identifier;

Transmitting, to the another network device, information indicating a type of the terminal device; wherein the communication system includes at least two network devices, the another network device is one of the at least two network devices Internet equipment.
The method of claim 6, wherein determining the type of the terminal device according to the communication identifier comprises:

Sending a query request message to the network device that stores the power information database, where the query request message carries the communication identifier; the network device storing the power information database is one of the at least two network devices;

Receiving, by the network device storing the power information database, information for indicating a type of the terminal device, which is sent in response to the query request message; the power information database stores information of at least one terminal device, wherein each The information of the terminal device includes the type of the terminal device and the communication identifier of the terminal device.
The method of claim 7 wherein the method further comprises:

Receiving, by the network device storing the power information database, information for indicating a period in which the terminal device transmits a data packet, in response to the query request message; information of each terminal device stored in the power information database or The information of some terminal devices also includes the period in which the terminal device sends the data packet.
The method according to claim 8, wherein after determining the type of the terminal device according to the communication identifier, the method further comprises:

And determining, according to the communication identifier, a period in which the terminal device sends a data packet, sending, to the another network device, information indicating a period in which the terminal device sends a data packet.
A method for determining a scheduling mode of a terminal device in a communication system, comprising:

Transmitting, by the network device, a communication identifier of the terminal device to determine a type of the terminal device;

Receiving information sent by the network device for indicating a type of the terminal device;

Determining whether to adopt a semi-static scheduling manner for the terminal device according to the information for indicating the type of the terminal device.
The method of claim 10, further comprising: before transmitting the communication identifier of the terminal device to the network device, the method further comprising:

Receiving an attach request sent by the terminal device, where the attach request carries the communication identifier.
The method of claim 11, wherein the transmitting the communication identifier of the terminal device to the network device comprises:

And if it is determined that the terminal device sends the data packet in a periodic manner, sending the communication identifier to the network device.
The method according to any one of claims 10 to 12, further comprising: after determining whether to apply the semi-static scheduling mode to the terminal device according to the information for indicating the type of the terminal device, further comprising:

If it is determined that the semi-persistent scheduling mode is adopted for the terminal device, sending, to the terminal device, information for indicating scheduling in a semi-persistent scheduling manner, and a scheduling period for indicating semi-persistent scheduling of the terminal device information.
The method according to claim 13, wherein the information for indicating scheduling in a semi-persistent scheduling manner and the scheduling period for instructing semi-static scheduling of the terminal device are sent to the terminal device After the information, it also includes:

Receiving an uplink scheduling request message sent by the terminal device;

And allocating the transmission resource in the semi-static scheduling mode to the terminal device according to the uplink scheduling request message.
A network device in a communication system, comprising:

a first receiving module, configured to receive a communication identifier of the terminal device;

And a processing module, configured to determine, according to the communication identifier, a type of the terminal device, and determine, according to the type of the terminal device, whether to adopt a semi-static scheduling manner for the terminal device.
The network device according to claim 15, wherein the network device further comprises a first sending module and a second receiving module, the communication system further comprising another network device; the processing module is configured to The communication identifier determines the type of the terminal device, including:

Sending, by the first sending module, a policy request message to the another network device, where the policy request message carries the communication identifier;

Receiving, by the second receiving module, information that is sent by the another network device and is used to indicate a type of the terminal device in response to the policy request message.
The network device according to claim 16, wherein the processing module is further configured to:

And receiving, by the second receiving module, information that is sent by the another network device and is used to indicate a period in which the terminal device sends a data packet in response to the policy request message.
The network device according to claim 17, wherein the processing module is further configured to:

After determining, according to the type of the terminal device, whether the semi-persistent scheduling mode is adopted for the terminal device, if it is determined according to the type of the terminal device that the semi-persistent scheduling mode is adopted for the terminal device, determining to perform the terminal device The scheduling period of the semi-persistent scheduling is a period in which the terminal device sends a data packet.
The network device according to claim 18, wherein the network device further comprises a second sending module;

The first receiving module is further configured to: after the processing module determines, according to the type of the terminal device, whether to adopt a semi-static scheduling manner for the terminal device, receive a service request message sent by the access network device; The request message is used by the terminal device to request to transmit a data packet;

The second sending module is configured to: send a response message to the access network device, where the processing module determines to adopt a semi-persistent scheduling manner on the terminal device according to the type of the terminal device, where the response is The message carries information indicating that the terminal device is scheduled in a semi-persistent scheduling manner and information indicating a scheduling period for semi-persistent scheduling of the terminal device.
A network device in a communication system, comprising:

a first receiving module, configured to receive a policy request message, where the policy request message carries a communication identifier of the terminal device;

a processing module, configured to determine, according to the communication identifier, a type of the terminal device;

a first sending module, configured to send information indicating a type of the terminal device to another network device in the communication system; wherein the communication system includes at least two network devices, and the another network device Is one of the at least two network devices.
The network device according to claim 20, wherein the network device further comprises a second receiving module and a second sending module; the processing module is configured to determine the type of the terminal device according to the communication identifier, including :

And sending, by the second sending module, a query request message to the network device that stores the power information database, where the query request message carries the communication identifier; and the network device that stores the power information database is the at least two network devices One of the network devices;

Receiving, by the second receiving module, the information that is sent by the network device that stores the power information database in response to the query request message for indicating a type of the terminal device; the power information database stores at least one terminal Information of the device, wherein the information of each terminal device includes the type of the terminal device and the communication identifier of the terminal device.
The network device according to claim 21, wherein the processing module is further configured to:

Receiving, by the second receiving module, the information that is sent by the network device that stores the power information database in response to the query request message to indicate that the terminal device sends a data packet; the power information database stores The information of each terminal device or the information of a part of the terminal device further includes a period in which the terminal device transmits the data packet.
The network device according to claim 22, wherein the first sending module is further configured to:

After the processing module determines the type of the terminal device according to the communication identifier, if the processing module further determines, according to the communication identifier, a period in which the terminal device sends a data packet, then the other network device is sent to the another network device. Sending information indicating a period in which the terminal device transmits a data packet.
An access network device, comprising:

a first sending module, configured to send a communication identifier of the terminal device to the network device, to determine a type of the terminal device;

a first receiving module, configured to receive information that is sent by the network device to indicate a type of the terminal device;

And a processing module, configured to determine, according to the information used to indicate the type of the terminal device, whether to adopt a semi-static scheduling manner for the terminal device.
The access network device according to claim 24, wherein the access network device further comprises a second receiving module;

The second receiving module is configured to: before the first sending module sends the communication identifier of the terminal device to the network device, receive an attach request sent by the terminal device, where the attach request carries the communication identifier.
The access network device according to claim 25, wherein the first sending module is configured to:

And if the processing module determines that the terminal device sends the data packet in a periodic manner, sending the communication identifier to the network device.
The access network device according to any one of claims 24 to 26, wherein the access network device further comprises a second sending module;

The second sending module is configured to: after the processing module determines, according to the information indicating the type of the terminal device, whether to adopt a semi-static scheduling manner for the terminal device, if the processing module determines that the The terminal device adopts a semi-persistent scheduling mode, and sends information indicating that scheduling is performed in a semi-persistent scheduling manner, and information indicating a period in which the terminal device sends a data packet.
The access network device according to claim 27, wherein the access network device further comprises a second receiving module;

The second receiving module is configured to send, by the second sending module, information for indicating scheduling in a semi-persistent scheduling manner to the terminal device, and information for indicating a period in which the terminal device sends a data packet After receiving the uplink scheduling request message sent by the terminal device;

The processing module is further configured to allocate, according to the uplink scheduling request message, the transmission resource in the semi-static scheduling mode to the terminal device.