A service scheduling method, device and system

Abstract

The embodiment of the present application discloses a service scheduling method, device and system. The sub-device negotiates the energy-saving time and the wake-up time of the associated STA, that is, negotiates when the STA is in the energy-saving state and when the STA is in the wake-up state. Then, the sub-device reports the negotiated wake-up time of the STA to the master device. Further, the master device schedules the related data of the STA according to the wake-up time of the STA. In this way, the master device can know the STA wake-up time negotiated by the sub-device and the associated STA before scheduling the service of each STA, and does not need to frequently interact with each sub-device to know the real-time state of each STA. The master device can more efficiently schedule the service of each STA at the appropriate time by centrally controlling the wake-up time of each STA.

Description

[0001] This application is a divisional application, the original application's application number is 202510039218.6, the original application's original date is January 9, 2025, and the original application's entire content is incorporated by reference in this application. TECHNICAL FIELD

[0002] The present application relates to the field of communication, in particular to a service scheduling method, device and system. BACKGROUND

[0003] With the development of communication technology, optical fiber transmission is more and more widely used in communication systems, and fiber to the room (FTTR) is an important part of optical networks. The FTTR system includes a main device and a sub device, and the main device and the sub device are connected by an optical fiber. The main device is an optical network terminal (ONT) in a passive optical network (PON), which can also be called an optical network unit (ONU), and is connected to an optical line terminal (OLT) at the operator's end through an optical fiber.

[0004] In a traditional energy-saving scheme, if a station (STA) enters an energy-saving state, the STA will send a message to the sub device to indicate that the STA enters the energy-saving state. When the STA is in the energy-saving state, it cannot receive data, and when the STA is in the wake-up state, it can receive data. The main device needs to frequently interact with the sub device to confirm whether the STA is currently in the energy-saving state or the wake-up state, so as to schedule services for the STA at the appropriate time, but the frequent interaction between the main device and the sub device leads to a high implementation cost of the scheme. SUMMARY

[0005] The embodiments of the present application provide a service scheduling method, device and system. Before scheduling services for each STA, the main device can know the STA wake-up time negotiated by each sub device and the associated STA in advance, without the need to frequently interact with each sub device to know the real-time state of each STA. The main device can more efficiently schedule services for each STA at the appropriate time by centrally controlling the wake-up time of each STA.

[0006] In a first aspect, an embodiment of the present application provides a service scheduling method. The service scheduling method can be applied to a fiber to the room (FTTR) scenario. In the FTTR system, a master device is also referred to as a main FTTR unit (MFU), and a slave device is also referred to as a sub FTTR unit (SFU) in the FTTR system. The service scheduling method is performed by the master device. Specifically, the slave device negotiates a wake-up time of a station (STA) with the STA. After the slave device successfully negotiates the wake-up time of the STA with the STA, the master device receives a STA target wake time (TWT) negotiation time reporting message sent by the slave device. The STA TWT negotiation time reporting message is used to indicate a negotiation result of the slave device and the STA. The negotiation result is that the slave device successfully negotiates the wake-up time of the STA with the STA. The wake-up time of the STA is a time during which the STA is in a wake-up state. The wake-up time of the STA can also be referred to as a STA service period. Then, the master device schedules the STA in the STA service period or in the wake-up state.

[0007] In this embodiment, the slave device negotiates an energy-saving time and a wake-up time of the STA with the associated STA, that is, negotiates when the STA is in an energy-saving state and when the STA is in a wake-up state. Then, the slave device reports the negotiated wake-up time of the STA to the master device. Then, the master device schedules related data of the STA according to the wake-up time of the STA. In this way, before scheduling services of the STAs, the master device can know the wake-up time of the STA negotiated by each slave device and the associated STA, without frequently interacting with each slave device to know real-time states of each STA. The master device can more efficiently schedule services of each STA at a suitable time by centrally controlling the wake-up time of each STA.

[0008] In some possible embodiments, before the master device receives the STA TWT negotiation time reporting message sent by the slave device, the method further includes: the master device assigns a slave device service period to the slave device by sending a TWT negotiation time message to the slave device. The slave device service period is used for the slave device to negotiate the wake-up time with the STA, that is, the slave device and the STA negotiate the wake-up time of the STA in the slave device service period. In this embodiment, the master device centrally assigns a period for negotiation to each slave device by comprehensively considering multiple factors. The assignment manner is more reasonable and more targeted, which is beneficial to improving the efficiency and success rate of negotiation of each slave device.

[0009] In some possible implementation manners, before the master device allocates the sub-device service period for the sub-device by sending the TWT negotiation time message to the sub-device, the method further includes: receiving, by the master device, state information sent by the sub-device, the state information being used to support the master device to perform global wake-up time allocation. The sub-device reports the state information to the master device, so that the master device can comprehensively consider multiple aspects according to the state information, and thus more reasonably allocates the sub-device service period for the sub-device.

[0010] In some possible implementation manners, the state information includes interference measurement information, and the interference measurement information includes at least one of an identifier of an interference device, an operating mode of the interference device, an operating frequency bandwidth of the interference device, an operating channel of the interference device, a signal transmission strength of the interference device, and a device type of the interference device. The master device allocates the sub-device service period for the sub-device according to the interference measurement information from the aspect of avoiding interference, so that the sub-device can negotiate with the STA without interference.

[0011] In some possible implementation manners, the state information includes at least one of a capability parameter and an operating parameter of the sub-device. The capability parameter of the sub-device includes at least one of a protocol version number supported by the sub-device, a frequency band supported by the sub-device, a number of service set identifiers (SSIDs) supported by the sub-device, and a transmission power level supported by the sub-device. The operating parameter of the sub-device includes at least one of an operating frequency band of the sub-device, an operating channel of the sub-device, an operating channel bandwidth of the sub-device, and a transmission power level of the sub-device. The master device allocates the sub-device service period for the sub-device according to the at least one of the capability parameter and the operating parameter from multiple aspects, so that the sub-device can negotiate with the STA at a more suitable time period.

[0012] In some possible implementation manners, the TWT negotiation time message includes a start time and a time length of the sub-device service period, or the TWT negotiation time message includes a start time and an end time of the sub-device service period. The sub-device can quickly determine the sub-device service period for negotiation according to the content carried in the TWT negotiation time message.

[0013] In some possible implementation, the TWT negotiation time message further includes a start time and a duration of the global TWT period. Alternatively, the TWT negotiation time message further includes a start time and an end time of the global TWT period. The global TWT period includes a sub-device service period allocated by the master device to all sub-devices. In this implementation, the master device formulates the global TWT period, and allocates a corresponding sub-device service period to each sub-device in each global TWT period, so that each sub-device can be allocated a corresponding sub-device service period in one global TWT period, which is conducive to giving consideration to the negotiation and traffic transmission between each sub-device and the associated STA.

[0014] In some possible implementation, the STA service period is within the time range of the sub-device service period, that is, the STA service period in which the STA negotiated with the sub-device is in an awake state is within the time range of the sub-device service period negotiated by the sub-device and the STA. In this way, the master device allocates completely different sub-device service periods to different sub-devices, which on one hand avoids interference between the negotiation processes of different sub-devices, and on the other hand avoids interference between the traffic transmission processes of different sub-devices.

[0015] In some possible implementation, the STA TWT negotiation time reporting message includes an identifier of the STA, a start time and a duration of the STA service period. Alternatively, the STA TWT negotiation time reporting message includes an identifier of the STA, a start time and an end time of the STA service period. The start time of the STA service period is also the start time of the STA being in an awake state, the end time of the STA service period is also the end time of the STA being in an awake state, and the duration of the STA service period is also the duration of the STA being in an awake state. This enables the master device to quickly determine the awake time of the STA according to the content carried by the STA TWT negotiation time reporting message.

[0016] In some possible implementation, the master device scheduling the STA in the STA service period or in an awake state includes: the master device sending a scheduling message to the sub-device, the scheduling message being used to indicate that the sub-device is allowed to send data to the STA in the STA service period. This enables the STA to receive data sent by the sub-device in an awake state, and ensures that traffic can be normally scheduled and received.

[0017] In a second aspect, the embodiments of the present application provide a service scheduling method, which can be applied to an FTTR scenario. In the system of the FTTR, a master device is also referred to as an MFU, and a slave device is also referred to as an SFU. The service scheduling method is executed by the slave device. Specifically, the slave device negotiates with a STA to determine the wake-up time of the STA. After the slave device successfully negotiates with the STA to determine the wake-up time of the STA, the slave device sends an STA TWT negotiation time reporting message to the master device. The STA TWT negotiation time reporting message is used to indicate the negotiation result of the slave device and the STA. The STA in the service period of the STA or in the wake-up state is scheduled by the master device.

[0018] In some possible implementation manners, before the slave device sends the STA TWT negotiation time reporting message to the master device, the method further includes: receiving, by the slave device, a TWT negotiation time message sent by the master device. The TWT negotiation time message is used to allocate a slave device service period to the slave device. The slave device service period is used for the slave device to negotiate the wake-up time with the STA.

[0019] In some possible implementation manners, before the slave device receives the TWT negotiation time message sent by the master device, the method further includes: sending, by the slave device, state information to the master device. The state information is used to support the master device to perform global wake-up time allocation.

[0020] In some possible implementation manners, the state information includes interference measurement information. The interference measurement information includes at least one of the following: an identifier of an interference device, an operating mode of the interference device, an operating frequency width of the interference device, an operating channel of the interference device, a signal strength sent by the interference device, and a device type of the interference device.

[0021] In some possible implementation manners, the state information includes at least one of the following: a capability parameter and an operating parameter of the slave device. The capability parameter of the slave device includes at least one of the following: a protocol version number supported by the slave device, a frequency band supported by the slave device, an SSID supported by the slave device, and a transmission power level supported by the slave device. The operating parameter of the slave device includes at least one of the following: an operating frequency band of the slave device, an operating channel of the slave device, an operating channel frequency width of the slave device, and a transmission power level of the slave device.

[0022] In some possible implementation manners, the TWT negotiation time message includes a start time and a time length of the slave device service period, or the TWT negotiation time message includes a start time and an end time of the slave device service period.

[0023] In some possible implementation manners, the TWT negotiation time message further comprises a start time and a time length of the global TWT period, or the TWT negotiation time message further comprises a start time and an end time of the global TWT period. The global TWT period comprises a sub-device service period allocated by the master device to all sub-devices.

[0024] In some possible implementation manners, the STA service period is within a time range of the sub-device service period.

[0025] In some possible implementation manners, the STA TWT negotiation time reporting message comprises an identifier of the STA, a start time and a time length of the STA service period, or the STA TWT negotiation time reporting message comprises an identifier of the STA, a start time and an end time of the STA service period.

[0026] In some possible implementation manners, the method further comprises: receiving, by the sub-device, a scheduling message sent by the master device, the scheduling message being used to indicate that the sub-device is allowed to send data to the STA in the STA service period.

[0027] In a third aspect, an embodiment of the present application provides a master device, which can be an MFU in an FTTR system. The master device comprises a transceiver unit and a processing unit. The transceiver unit is configured to: receive, when a sub-device successfully negotiates a wake-up time with a STA, a STA TWT negotiation time reporting message sent by the sub-device, the STA TWT negotiation time reporting message being used to indicate a negotiation result of the sub-device with the STA. The processing unit is configured to: schedule the STA in a STA service period or in a wake-up state.

[0028] In some possible implementation manners, before receiving the STA TWT negotiation time reporting message sent by the sub-device, the transceiver unit is further configured to: allocate, by sending a TWT negotiation time message to the sub-device, a sub-device service period to the sub-device, the sub-device service period being used for the sub-device to negotiate the wake-up time with the STA.

[0029] In some possible implementation manners, before allocating, by sending the TWT negotiation time message to the sub-device, the sub-device service period to the sub-device, the transceiver unit is further configured to: receive state information sent by the sub-device, the state information being used to support the master device to perform global wake-up time allocation.

[0030] In some possible implementation manners, the state information comprises interference measurement information, and the interference measurement information comprises at least one of an identifier of an interference device, an operating mode of the interference device, an operating bandwidth of the interference device, an operating channel of the interference device, a signal strength of a signal sent by the interference device, and a device type of the interference device.

[0031] In some possible implementation manners, the status information comprises at least one of a capability parameter and an operating parameter of the sub-device. The capability parameter of the sub-device comprises at least one of a protocol version number supported by the sub-device, a frequency band supported by the sub-device, a number of SSIDs supported by the sub-device, and a transmit power level supported by the sub-device. The operating parameter of the sub-device comprises at least one of an operating frequency band of the sub-device, an operating channel of the sub-device, an operating channel bandwidth of the sub-device, and a transmit power level of the sub-device.

[0032] In some possible implementation manners, the TWT negotiation time message comprises a start time and a duration of the sub-device service period, or the TWT negotiation time message comprises a start time and an end time of the sub-device service period.

[0033] In some possible implementation manners, the TWT negotiation time message further comprises a start time and a duration of a global TWT period. Alternatively, the TWT negotiation time message further comprises a start time and an end time of the global TWT period. The global TWT period comprises a sub-device service period allocated by the master device to all sub-devices.

[0034] In some possible implementation manners, the STA service period is within a time range of the sub-device service period.

[0035] In some possible implementation manners, the STA TWT negotiation time reporting message comprises an identifier of the STA, a start time and a duration of the STA service period. Alternatively, the STA TWT negotiation time reporting message comprises an identifier of the STA, a start time and an end time of the STA service period.

[0036] In some possible implementation manners, the transceiver is further configured to: send, to the sub-device, a scheduling message, the scheduling message being used to instruct the sub-device to send data to the STA in the STA service period.

[0037] In a fourth aspect, an embodiment of the present application provides a sub-device, which can be an SFU in an FTTR system. The sub-device comprises a transceiver and a processing unit. The processing unit is configured to: negotiate, with a STA, a wake-up time of the STA. The transceiver is configured to: after the sub-device successfully negotiates the wake-up time of the STA, send, to a master device, a STA TWT negotiation time reporting message, the STA TWT negotiation time reporting message being used to indicate a negotiation result of the sub-device and the STA. The STA is scheduled by the master device in a STA service period or in a wake-up state.

[0038] In some possible implementation, before sending the STA TWT negotiation time report message to the master device, the transceiver is further configured to: receive a TWT negotiation time message sent by the master device, the TWT negotiation time message being used to allocate a sub-device service period for the sub-device, the sub-device service period being used for the sub-device to negotiate a wake-up time with the STA.

[0039] In some possible implementation, before receiving the TWT negotiation time message sent by the master device, the transceiver is further configured to: send state information to the master device, the state information being used to support the master device to perform global wake-up time allocation.

[0040] In some possible implementation, the state information includes interference measurement information, and the interference measurement information includes at least one of an identifier of an interference device, an operating mode of the interference device, an operating bandwidth of the interference device, an operating channel of the interference device, a signal strength of a signal sent by the interference device, and a device type of the interference device.

[0041] In some possible implementation, the state information includes at least one of a capability parameter and an operating parameter of the sub-device. The capability parameter of the sub-device includes at least one of a protocol version number supported by the sub-device, a frequency band supported by the sub-device, an SSID supported by the sub-device, and a transmission power level supported by the sub-device. The operating parameter of the sub-device includes at least one of an operating frequency band of the sub-device, an operating channel of the sub-device, an operating channel bandwidth of the sub-device, and a transmission power level of the sub-device.

[0042] In some possible implementation, the TWT negotiation time message includes a start time and a time length of the sub-device service period, or the TWT negotiation time message includes a start time and an end time of the sub-device service period.

[0043] In some possible implementation, the TWT negotiation time message further includes a start time and a time length of a global TWT period, or the TWT negotiation time message further includes a start time and an end time of the global TWT period. The global TWT period includes sub-device service periods allocated by the master device to all sub-devices.

[0044] In some possible implementation, the STA service period is within a time range of the sub-device service period.

[0045] In some possible implementation, the STA TWT negotiation time report message includes an identifier of the STA, a start time and a time length of the STA service period, or the STA TWT negotiation time report message includes an identifier of the STA, a start time and an end time of the STA service period.

[0046] In some possible implementation manners, the transceiver unit is further configured to receive a scheduling message sent by the master device, the scheduling message being used to instruct the slave device to send data to the STA in the STA service period.

[0047] In a fifth aspect, an embodiment of the present application provides a master device, the master device comprising instructions, when the instructions are executed by the master device, causing the master device to perform the method according to any of the embodiments of the first aspect.

[0048] In a sixth aspect, an embodiment of the present application provides a slave device, the slave device comprising instructions, when the instructions are executed by the slave device, causing the slave device to perform the method according to any of the embodiments of the second aspect.

[0049] In a seventh aspect, an embodiment of the present application provides a master device, the master device comprising a processor and an interface, the interface being configured to transceive signals, and the processor being configured to perform the method according to any of the embodiments of the first aspect.

[0050] In an eighth aspect, an embodiment of the present application provides a slave device, the slave device comprising a processor and an interface, the interface being configured to transceive signals, and the processor being configured to perform the method according to any of the embodiments of the second aspect.

[0051] In a ninth aspect, an embodiment of the present application provides a communication system, the communication system comprising at least one slave device according to any of the embodiments of the fourth aspect, the sixth aspect or the eighth aspect, and a master device according to any of the embodiments of the third aspect, the fifth aspect or the seventh aspect, the master device being configured to communicate with the at least one slave device.

[0052] In a tenth aspect, an embodiment of the present application provides a chip, the chip being configured to perform the method according to any of the embodiments of the first aspect or the second aspect.

[0053] In an eleventh aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium storing instructions, when the instructions are executed by a computer, causing the method according to any of the embodiments of the first aspect or the second aspect to be implemented.

[0054] In a twelfth aspect, an embodiment of the present application provides a computer program product, the computer program product comprising program instructions, when the computer program product is executed, being configured to implement the method according to any of the embodiments of the first aspect or the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0055] Figure 1 FIG. 1 is a schematic diagram of a possible WLAN network architecture in an embodiment of the present application;

[0056] Figure 2 FIG. 2 is a schematic diagram of a system architecture of FTTH / O;

[0057] Figure 3 System architecture diagram for FTTR;

[0058] Figure 4 Flow chart of the service scheduling method provided by the embodiment of the present application;

[0059] Figure 5 Another flow chart of the service scheduling method provided by the embodiment of the present application;

[0060] Figure 6 Schematic diagram of the main device allocating service periods of the sub-devices to the sub-devices in the embodiment of the present application;

[0061] Figure 7 Schematic diagram of the main device in the embodiment of the present application;

[0062] Figure 8 Another schematic diagram of the main device in the embodiment of the present application;

[0063] Figure 9 Schematic diagram of the sub-device in the embodiment of the present application;

[0064] Figure 10 Another schematic diagram of the sub-device in the embodiment of the present application. DETAILED DESCRIPTION

[0065] The embodiment of the present application provides a service scheduling method, device and system, and the service scheduling method can be applied to a fiber to the room (FTTR) scenario. Before scheduling services of each STA, a main device can know STA wake-up times negotiated by each sub-device and an associated STA in advance, without frequently interacting with each sub-device to know real-time states of each STA, and the main device can more efficiently schedule services of each STA at a suitable time by centrally controlling the wake-up times of each STA.

[0066] It should be understood that the "one embodiment", "one implementation", "one implementation" or "one example" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment", "one implementation", "one implementation" or "in one example" appearing throughout the specification does not necessarily mean the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0067] In addition, the terms "system" and "network" are often used interchangeably herein. The term "and / or", used herein only describes an associated relationship, which means that there can be three relationships, for example, A and / or B, which means that A exists alone, A and B exist together, and B exists alone. In addition, the character " / " generally represents an "or" relationship between the associated objects. It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that the determination of B according to A does not mean that B is determined only according to A, but B can also be determined according to A and / or other information. In addition, unless otherwise stated, the ordinal numbers "first", "second", etc. mentioned in the embodiments of the present application are used to distinguish a plurality of objects, and are not used to limit the order, time sequence, priority or importance of the plurality of objects. In addition, the terms "include" and "have" in the embodiments of the present application, claims and drawings are not exclusive. For example, a process, method, system, product or device including a series of steps or modules is not limited to the listed steps or modules, and can also include steps or modules that are not listed.

[0068] Referring to Figure 1 As shown in the figure, it is a possible WLAN network architecture diagram, which includes a wireless controller (also referred to as a "control node" in the embodiments of the present application), a wireless access point (also referred to as a "network node" in the embodiments of the present application) and a terminal device in the wireless local area network (WLAN) network architecture. The wireless controller is used for service configuration and radio frequency configuration of the access point. The wireless access point can be simply referred to as an access point (AP). The AP is used to provide service access for the associated STA. The terminal device as the STA can be associated with the access point.

[0069] The terminal device can include a mobile phone (or called a "cellular" phone), a computer with a mobile terminal device, a portable, pocket-sized, handheld, computer-embedded mobile device, etc. For example, a personal communication service (PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and the like. The terminal device can also be a computer, a tablet computer, an e-book reader, and the like, or a smart home device, such as a smart television, a smart speaker, and the like. As an example but not limitation, in the embodiments of the present application, the terminal device can also be a wearable device. The wearable device can also be referred to as a wearable smart device or a smart wearable device, etc., which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes, etc. The wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. The wearable device is not only a hardware device, but also a device that realizes powerful functions through software support and data interaction, cloud interaction. The broad sense of wearable smart devices includes devices with full functions, large sizes, and the ability to realize complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and devices that focus on a certain application function and need to be used with other devices such as smart phones, such as various smart wristbands, smart helmets, smart jewelry, etc. for monitoring vital signs.

[0070] With the development of communication technology, optical fiber transmission is more and more widely used in communication systems, and fiber to the room (FTTR) is an important part of the optical network. The FTTR system includes a main device and a sub device, and the main device and the sub device are connected through an optical fiber. The main device is an optical network terminal (ONT) in a passive optical network (PON), and can also be referred to as an optical network unit (ONU), and is connected to an optical line terminal (OLT) at an operator end through an optical fiber.

[0071] Figure 2Fig. 1 is a schematic diagram of a system architecture for fiber to the home / office (FTTH / O). The network side device (such as a switch, a router, etc.) connected upstream is connected to an ONT via an optical distribution network (ODN). The ODN includes a passive optical splitter for optical power distribution, a trunk fiber connected between the passive optical splitter and an OLT, and branch fibers connected between the passive optical splitter and the ONT. When transmitting a downstream signal, the downstream signal transmitted by the OLT is transmitted to each ONT via the optical splitter, and the ONT selectively receives the downstream data belonging to itself in the downstream signal. When transmitting an upstream signal, the upstream signals transmitted by the N ONTs are combined by the optical splitter into one optical signal and transmitted to the OLT.

[0072] On the basis of FTTH / O, in order to solve the problem of signal coverage (such as a wireless local area network (WLAN) signal) in a home or office network, the optical fiber can be further extended to a room. An optical terminal device providing a WLAN signal is installed in the room, so that the distance between the user terminal and the access point (AP) is reduced, and the signal quality is improved. This technology is referred to as fiber to the room (FTTR).

[0073] Figure 3 Fig. 2 is a schematic diagram of a system architecture for FTTR. The OLT in FTTH / O is deployed in a central machine room, and the ONT is deployed in a home or office. The main device in the FTTR network acts as the ONT in the FTTH network and as the upstream device of the FTTR sub-device, and manages the sub-device. The sub-device in the FTTR can be deployed in each room in the home or office area to provide a signal for a user terminal. The sub-device has the function of the ONT, and can also have the function of a wireless AP.

[0074] In the FTTR, multiple sub-devices can be deployed, and each sub-device is connected to the main device via an optical splitter. The main device can uniformly manage and configure all the sub-devices. The main device can also be referred to as a "main gateway", a "main optical modem", or a "main FTTR unit (MFU)", and the sub-device can also be referred to as a "slave gateway", a "slave optical modem", or a "sub-FTTR unit (SFU)".

[0075] It should be noted that the present application can be applied to any point to multi-point (P2MP) communication system, which specifically includes a main device and multiple sub-devices, and the main device can cooperatively manage the multiple sub-devices. For example, in the FTTR system architecture shown in Fig. 2, the main device can be an ONT in the FTTH / O system architecture, and the sub-devices can be FTTR devices. Figure 2In the FTTH / O scenario shown, the master device can be an OLT, and the slave device can be an ONU. For example, in... Figure 3 In the FTTR scenario shown, the master device can be an MFU, and the slave device can be an MFU. In the service scheduling method for FTTR provided in this application embodiment, before scheduling services for each STA, the master device can know in advance the STA wake-up time negotiated between each slave device and the associated STA, without needing to frequently interact with each slave device to know the real-time status of each STA. By centrally managing the wake-up time of each STA, the master device can more efficiently schedule services for each STA at the appropriate time.

[0076] The following detailed description, in conjunction with the accompanying drawings, illustrates the service scheduling method for FTTR provided in this application. It should be noted that this application does not limit the number of sub-devices communicating with the master device. The following embodiments only illustrate the interaction between the master device and one or two sub-devices, referred to as sub-device 1 and sub-device 2. The interaction methods between more sub-devices and the master device are similar.

[0077] Figure 4 This is a flowchart of a service scheduling method provided in an embodiment of this application. The specific flow of the service scheduling method is described in detail below. It should be noted that the interaction between the master device and the sub-devices regarding service scheduling may include multiple stages, such as an initialization stage, a synchronization stage, and a time assignment stage. The initialization stage precedes the synchronization stage, and the synchronization stage precedes the time assignment stage. Specifically, in the synchronization stage, the sub-device negotiates the wake-up time of the STA with the STA and reports the negotiation result to the master device. In the time assignment stage, the master device allocates the service scheduling time according to the negotiation results reported by each sub-device, so that each sub-device sends data to the STA during the time period arranged by the master device. Optionally, in the initialization stage, the master device allocates a time period (SFU service cycle) for negotiation to each sub-device based on the interference measurement information, capability parameters, and / or operating parameters reported by each sub-device, so that during the synchronization stage, each sub-device negotiates the wake-up time of the STA with the STA according to the time period allocated by the master device. The interaction flow between the master device and sub-device 1 and sub-device 2 in the synchronization stage and the time assignment stage, respectively, is described below.

[0078] 101. Sub-device 1 negotiates with STA1 to determine STA1's wake-up time.

[0079] It should be noted that the working state of the STA can be divided into an energy saving state and a wake-up state, the STA can normally perform data transmission and reception in the wake-up state, and the STA suspends data transmission and reception when switching to the energy saving state. The time when the STA is in the energy saving state can be referred to as energy saving time, and the time when the STA is in the wake-up state can be referred to as wake-up time or STA service period. In order to improve the energy saving efficiency of the STA, an energy saving mechanism of target wake time (TWT) is defined, that is, the sub-device and the STA can negotiate the energy saving time and the wake-up time of the STA. In the synchronization stage, the sub-device 1 can be associated with at least one STA including the STA 1, and among the STAs associated with the sub-device 1, there can be STAs supporting negotiation and STAs not supporting negotiation. Taking the STA 1 supporting negotiation with the sub-device 1 as an example, the sub-device 1 negotiates the wake-up time and the energy saving time of the STA 1 with the STA 1, and if the negotiation is successful, the sub-device 1 can know the wake-up time and the energy saving time of the STA 1 in advance, which means that the sub-device 1 can know when the STA 1 is in the wake-up state and when the STA 1 is in the energy saving state in advance. For the STA that does not support negotiation with the sub-device 1, the STA notifies the sub-device 1 only when the STA switches between the energy saving state and the wake-up state, and the sub-device 1 cannot know the wake-up time and the energy saving time of the STA in advance.

[0080] 102. The sub-device 1 sends a message 1-1 to the master device.

[0081] In the synchronization stage, after the sub-device 1 negotiates the wake-up time and the energy saving time of the STA 1 with the STA 1, the sub-device 1 sends a message 1-1 to the master device, and the message 1-1 is used to indicate the wake-up time 1 of the STA 1. It should be understood that the wake-up time 1 of the STA 1 can also be understood as the period 1 when the STA 1 is in the wake-up state, and the wake-up time 1 of the STA 1 is also referred to as the STA 1 service period. It should be understood that the master device can know the wake-up time 1 of the STA 1 in order to schedule the STA 1 in the wake-up time 1, and therefore the sub-device 1 needs to report the wake-up time 1 of the STA 1 to the master device through the message 1-1, and whether the energy saving time 1 of the STA 1 needs to be reported to the master device is not limited. The message 1-1 can also be referred to as an STA TWT negotiation time reporting message.

[0082] It should be noted that the specific format of the message 1-1 is not limited in the embodiments of the present application, and the message 1-1 can include multiple fields.

[0083] Table 1 below provides fields that can be included in a message 1-1, the length of each field, and the definition, the STA in Table 1 below can be STA1, and the sub-device in Table 1 below can be sub-device 1. As shown in Table 1, the message 1-1 includes the identification of the STA, the basic service set identifier (BSSID) of the sub-device, the start time of the STA service period, and the duration of the STA service period. The start time of the STA service period is also the start time of the STA’s wake-up, and the duration of the STA service period is also the duration of the STA’s wake-up. The STA’s wake-up time is indicated by the start time of the STA service period and the duration of the STA service period.

[0084] Table 1

[0085] Field name Field length Field description Identification of the STA 6 Identification of the STA BSSID of the sub-device 6 BSSID of the sub-device negotiating the wake-up time with the STA Start time of the STA service period 4 Indication of the start time of the STA service period within the TWT period Duration of the STA service period 4 Indication of the duration of the STA service period within the TWT period, in us

[0086] Table 2 below provides fields that can be included in another message 1-1, the length of each field, and the definition, the STA in Table 2 below can be STA1, and the sub-device in Table 2 below can be sub-device 1. As shown in Table 2, the message 1-1 includes the identification of the STA, the BSSID of the sub-device, the start time of the STA service period, and the end time of the STA service period. The start time of the STA service period is also the start time of the STA’s wake-up, and the end time of the STA service period is also the end time of the STA’s wake-up. The duration of the STA service period is equivalent to the start time of the STA service period and the end time of the STA service period, which is equivalent to the STA’s wake-up time being indicated by the start time of the STA service period and the end time of the STA service period.

[0087] Table 2

[0088] Field name Field length Field description Identification of the STA 6 Identification of the STA BSSID of the sub-device 6 BSSID of the sub-device negotiating the wake-up time with the STA Start time of the STA service period 4 Indication of the start time of the STA service period within the TWT period End time of the STA service period 4 Indication of the end time of the STA service period within the TWT period

[0089] As an example, the “start time of the STA service period” in Table 1 and Table 2 can be an absolute time of the start time of the STA’s wake-up negotiated by STA1 and sub-device 1. As another example, the “start time of the STA service period” in Table 1 and Table 2 can also be a relative time with respect to the start time of the global TWT period, and the unit of the relative time can be us.

[0090] It should be understood that the identifier of the STA can be a media access control (MAC) address of the STA or an association identifier (AID) of the STA, and the like, and is not limited herein. The BSSID field of the sub-device in Table 1 and Table 2 is an optional field. For example, the sub-device 1 provides a plurality of Wi-Fi networks corresponding to a plurality of BSSIDs, and the BSSID of the sub-device 1 can indicate the Wi-Fi network accessed by the STA 1. The start time of the STA service period and the end time of the STA service period refer to specific time points or instants, and are not time periods.

[0091] It should be noted that in some possible scenarios, the message 1-1 can also carry only part of the fields shown in Table 1 or Table 2, and what field is carried depends on the actual application scenario, and is not limited herein. For example, the message 1-1 only includes the identifier of the STA and the start time of the STA service period, which is equivalent to indicating the wake-up start time of the STA, and also provides effective reference information for the master device to perform service scheduling at an appropriate time. For another example, the message 1-1 only includes the identifier of the STA and the length of the STA service period, which is equivalent to indicating the wake-up length of the STA, and also provides effective reference information for the master device to perform service scheduling at an appropriate time.

[0092] The present application does not limit the length of each field in the message 1-1, nor does it limit the indication content corresponding to the value of each field in the message 1-1, and the same applies to the format of other messages transmitted between the master device and the sub-device. In other words, each table provided in the embodiments of the present application is only some possible examples, and those skilled in the art can make flexible changes on this basis. For example, the byte length of each field in the table can be changed. For another example, the indication content corresponding to the value of each field can also be changed. Taking the fields in Table 1 as an example, the length of each field can be flexibly set, or the length of each field can also be measured in bits.

[0093] 103、The sub-device 2 negotiates the wake-up time of the STA 2 with the STA 2.

[0094] In the synchronization stage, the sub-device 2 can be associated with at least one STA including the STA 2, and the STAs associated with the sub-device 2 can include STAs supporting negotiation or STAs not supporting negotiation. Taking the STA 2 supporting negotiation with the sub-device 2 as an example, the sub-device 2 negotiates the wake-up time and the energy-saving time of the STA 2 with the STA 2. If the negotiation is successful, the sub-device 2 can learn the wake-up time and the energy-saving time of the STA 2 in advance, which means that the sub-device 2 can learn when the STA 2 is in the wake-up state and when the STA 2 is in the energy-saving state in advance. For the STA not supporting negotiation with the sub-device 2, the STA notifies the sub-device 2 only when the STA switches between the energy-saving state and the wake-up state, and the sub-device 2 cannot learn the wake-up time and the energy-saving time of the STA in advance.

[0095] It should be noted that the application embodiments do not limit whether the wake-up time negotiated by the STA 1 and the wake-up time negotiated by the STA 2 are the same. For example, the wake-up time negotiated by the STA 1 and the wake-up time negotiated by the STA 2 can be completely the same. For another example, the wake-up time negotiated by the STA 1 and the wake-up time negotiated by the STA 2 can be completely different. For another example, the wake-up time negotiated by the STA 1 and the wake-up time negotiated by the STA 2 can partially overlap. It should be understood that whether the wake-up time negotiated by the STA 1 and the wake-up time negotiated by the STA 2 are the same mainly depends on whether the interaction between the sub-device 1 and the STA 1 interferes with the interaction between the sub-device 2 and the STA 2. As an example, the interaction between the sub-device 1 and the STA 1 and the interaction between the sub-device 2 and the STA 2 do not interfere with each other, the wake-up time 1 negotiated by the STA 1 and the wake-up time 2 negotiated by the STA 2 can be completely the same or partially overlap, which is beneficial to improving the negotiation efficiency of multiple STAs as a whole. As another example, the interaction between the sub-device 1 and the STA 1 and the interaction between the sub-device 2 and the STA 2 interfere with each other, the wake-up time 1 negotiated by the STA 1 and the wake-up time 2 negotiated by the STA 2 can be completely different, so that the data of the STA 1 and the data of the STA 2 scheduled by the master device will not interfere with each other in transmission.

[0096] 104、The sub-device 2 sends a message 2-1 to the master device.

[0097] In the synchronization phase, after the sub-device 2 negotiates the wake-up time and the energy-saving time of the STA 2 with the STA 2, the sub-device 2 sends a message 2-1 to the master device, where the message 2-1 is used to indicate the wake-up time 2 of the STA 2. The wake-up time 2 of the STA 2 can also be understood as the period 2 in which the STA 2 is in the wake-up state, and the wake-up time 2 of the STA 2 is also referred to as the service period of the STA 2. It should be understood that the master device needs to know the wake-up time 2 of the STA 2 in order to schedule the service of the STA 2 in the wake-up time 2, and therefore the sub-device 2 needs to report the wake-up time 2 of the STA 2 to the master device through the message 2-1, and whether the energy-saving time 2 of the STA 2 needs to be reported to the master device is not limited. The message 2-1 can also be referred to as an STA TWT negotiation time reporting message. It should be noted that the format of the message 2-1 is similar to that of the message 1-1, and details can be referred to the above description of the format of the message 1-1, which will not be described here.

[0098] 105、The master device sends a message 1-2 to the sub-device 1.

[0099] After the master device receives the message 1-1 sent by the sub-device 1, the master device can know the wake-up time 1 of the STA 1, and then the master device can schedule the data of the STA 1 according to the wake-up time 1 of the STA 1 in the time allocation phase. Specifically, the master device can send a message 1-2 to the sub-device 1 to indicate that the sub-device 1 is allowed to send data to the STA 1 in the wake-up time 1 of the STA 1 (the service period of the STA 1), and the message 1-2 can also be referred to as a scheduling message. Wherein, the master device can send the data to be transmitted to the STA 1 to the sub-device 1 in advance, and the sub-device 1 obtains the permission to send data to the STA 1 after receiving the message 1-2, and the sub-device 1 can select whether to send the data to the STA 1 according to the actual situation. For example, the channel of the sub-device 1 is idle, and the data can be immediately sent to the STA 1. For another example, the channel of the sub-device 1 is busy, and the data needs to be sent to the STA 1 when the channel is idle.

[0100] It should be noted that the message 1-2 is used to indicate that the sub-device 1 is allowed to send data to the STA 1, and the message 1-2 is also used to indicate that the sub-device 1 is allowed to send data to the STA 1 in the wake-up time 1 of the STA 1 (the service period of the STA 1). For example, the message 1-2 can adopt the message format used by the master device to schedule the data of the STA, part of the fields in the message format are used to indicate that the sub-device 1 is allowed to send data to the STA 1, and another part of the fields in the message format are used to indicate that the sub-device 1 is allowed to send data to the STA 1 in the wake-up time 1 of the STA 1.

[0101] In one possible implementation 1, the master device can send message 1-2 to the slave device 1 in advance before the wake-up time 1 of STA1, and indicate by a field defined in message 1-2 that the slave device 1 is allowed to send data to STA1 at the wake-up time 1 of STA1. In another possible implementation 2, the master device sends message 1-2 to the slave device 1 when the wake-up time 1 of STA1 arrives, and indicates by message 1-2 that the slave device 1 is allowed to send data to STA1 at the wake-up time 1 of STA1.

[0102] It should be noted that the specific format of message 1-2 is not limited in the embodiments of the present application, and message 1-2 can include multiple fields.

[0103] Table 3 below provides the fields that can be included in message 1-2, the length of each field, and the definition. As shown in Table 3, message 1-2 includes the following fields: scheduling type, scheduling mode, delay time, contention window duration, termination type, number of MAC addresses of STAs, MAC address of STA, and priority.

[0104] It should be noted that the "delay time" field in message 1-2 indicates the delay time of the time when the scheduling control takes effect relative to the time when message 1-2 is received. For example, in the above-mentioned implementation 1, the master device sends message 1-2 to the slave device 1 in advance before the wake-up time 1 of STA1, and indicates by the "delay time" field in message 1-2 how long after the slave device 1 receives message 1-2 the slave device 1 is allowed to send data to STA1. For another example, in the above-mentioned implementation 2, the master device sends message 1-2 to the slave device 1 when the wake-up time 1 of STA1 arrives, and indicates by the "delay time" field in message 1-2 that the slave device 1 is allowed to send data to STA1 immediately after receiving message 1-2. It should be understood that the specific delay time indicated by the "delay time" field in message 1-2 depends on the wake-up time 1 of STA1, in other words, the specific delay time indicated by the "delay time" field in message 1-2 should be at the time when the wake-up time 1 of STA1 arrives.

[0105] It should also be noted that the specific duration indicated by the "Contentment Window Duration" field in Message 1-2 depends on the wake-up time 1 of STA1. In other words, the specific duration indicated by the "Contentment Window Duration" field in Message 1-2 should be within the duration of the wake-up time 1 of STA1 to ensure that STA1 receives data while awake. For example, if the "Schedule Type" field in Message 1-2 indicates that one-time contention is allowed, then sub-device 1 can decide the duration for which it sends data to STA1 based on the wake-up time 1 of STA1. As another example, if the "Schedule Type" field in Message 1-2 indicates that air interface contention is allowed for a specific period of time, then sub-device 1 can send data to STA1 based on the specific duration indicated by the "Contentment Window Duration" field in Message 1-2.

[0106] Table 3

[0107]

[0108] 106. The master device sends message 2-2 to the slave device.

[0109] After receiving message 2-1 from sub-device 2, the master device can determine the wake-up time 2 of STA1. Therefore, the master device can schedule the data from STA2 according to STA2's wake-up time 2 during the time allocation phase. Specifically, the master device can send message 2-2 to sub-device 2 to instruct it to send data to STA2 during STA2's wake-up time 2 (STA2's service cycle). Message 2-2 can also be called a scheduling message. The master device can send the data it needs to transmit to STA2 to sub-device 2 in advance. After receiving message 2-2, sub-device 2 obtains permission to send data to STA2 and can then choose whether to send the data to STA2 based on the actual situation. For example, if sub-device 2's channel is idle, it can send data to STA2 immediately. Or, if sub-device 2's channel is busy, it needs to wait until the channel becomes idle before sending data to STA2. It should be noted that the format of message 2-2 is similar to that of message 1-2 described above; please refer to the description of message 1-2's format above for details, which will not be repeated here.

[0110] It should be noted that, in Figure 4 In the synchronization or time allocation phase of the illustrated embodiment, there is no explicit timing relationship between the interaction processes between the master device and sub-device 1 and between the master device and sub-device 2. For example, the interaction process between the master device and sub-device 1 can be executed first, or the interaction process between the master device and sub-device 2 can be executed first, or the interaction processes between the master device and sub-device 1 and between the master device and sub-device 2 can be executed simultaneously.

[0111] Based on the aboveFigure 4 In the illustrated embodiment, in some possible scenarios, in the initialization stage, the master device can also allocate a period (sub-device 1 service period) negotiated with STA1 to sub-device 1 and a period (sub-device 2 service period) negotiated with STA2 to sub-device 2, so that sub-device 1 negotiates the wake-up time of STA1 with STA1 according to the period allocated by the master device in the synchronization stage, and sub-device 2 negotiates the wake-up time of STA2 with STA2 according to the period allocated by the master device in the synchronization stage. The master device can allocate the period for negotiation to each sub-device in a centralized manner according to various factors, and the allocation manner is more reasonable and targeted, which is beneficial to avoiding mutual interference between the negotiations of the sub-devices and improving the efficiency and success rate of the negotiations of the sub-devices. The related content of the initialization stage is described in detail below.

[0112] Figure 5 Another flowchart of the service scheduling method provided by the embodiment of the application is shown in FIG. 7. As shown in the figure, the service scheduling method provided by the embodiment of the application further includes the following steps. Figure 5

[0113] 107. The master device sends message 1-3 to sub-device 1.

[0114] In the initialization stage before the synchronization stage and the time allocation stage, the master device allocates a negotiation period 1 for sub-device 1 to negotiate with STA1, and sends message 1-3 to sub-device 1, which is used to instruct sub-device 1 to negotiate the wake-up time 1 of STA1 with STA1 in the negotiation period 1. Further, in the synchronization stage, sub-device 1 negotiates the wake-up time 1 of STA1 with STA1 in the negotiation period 1. The negotiation period 1 can also be referred to as a sub-device 1 service period, and message 1-3 can also be referred to as a TWT negotiation time message.

[0115] Figure 6 A schematic diagram of the master device allocating a sub-device service period to each sub-device in the embodiment of the application is shown in FIG. 8. As shown in the figure, the start time of the global TWT period refers to the delay time from receiving a message by a sub-device to the global TWT period; the global TWT period length refers to the length of each TWT period; the start time of the sub-device service period refers to the start time of the sub-device service period in the TWT period; the sub-device service period length refers to the length of the sub-device service period in the TWT period; the start time of the STA service period refers to the start time of the wake-up time actually negotiated by a STA associated with a sub-device and the sub-device; and the STA service period length refers to the wake-up length negotiated by the STA associated with the sub-device and the sub-device. Figure 6

[0116] ​​In one possible implementation, the master device defines a global TWT cycle and assigns a service cycle to each sub-device, including sub-device 1 and sub-device 2, within each global TWT cycle. This ensures that each sub-device is allocated a corresponding service cycle within a global TWT cycle, which is beneficial for balancing negotiation and service transmission between each sub-device and its associated STA. In other words, a sub-device service cycle includes the sub-device 1 service cycle used by sub-device 1 to negotiate with STA1, the sub-device 2 service cycle used by sub-device 2 to negotiate with STA2, and so on.

[0117] This application does not limit the specific allocation method of the service cycles of each sub-device within the global TWT cycle. Taking the service cycles of sub-device 1 and sub-device 2 as examples, the service cycles of sub-device 1 and sub-device 2 can be two completely different sub-device service cycles, or the service cycles of sub-device 1 and sub-device 2 can partially overlap or completely overlap. As an example, the master device allocates the corresponding sub-device service cycles to each sub-device in an average allocation manner, that is, the duration of the sub-device service cycles corresponding to each sub-device is the same, and the sub-device service cycles corresponding to each sub-device are staggered in time. As another example, the master device receives the status information reported by each sub-device, and the master device allocates the corresponding sub-device service cycles to each sub-device in a targeted manner according to the reported status information. The following is a description with specific examples.

[0118] In one possible scenario, taking sub-device 1 and sub-device 2 as examples, the interaction between sub-device 1 and STA1 and the interaction between sub-device 2 and STA2 constitute mutual interference. For example... Figure 6 As shown, the service cycles allocated by the master device to sub-device 1 and sub-device 2 can be two completely different sub-device service cycles. Furthermore, STA1's wake-up time 1 (STA1 service cycle) falls within the range of sub-device 1's service cycle, and STA2's wake-up time 2 (STA2 service cycle) falls within the range of sub-device 2's service cycle. In this way, by allocating completely different sub-device service cycles to sub-device 1 and sub-device 2, the master device avoids interference between the negotiation processes of sub-device 1 and STA1 and between sub-device 2 and STA2, and also avoids interference between the service transmission processes of sub-device 1 and STA1 and between sub-device 2 and STA2.

[0119] It should be noted that the specific format of messages 1-3 is not limited in the embodiments of this application, and messages 1-3 may include multiple fields.

[0120] Table 4 below provides fields that can be included in message 1-3, the length of each field, and the definition, the sub-device in Table 4 can be sub-device 1. As shown in Table 4, the start time of SFU service period and the duration of SFU service period are included in message 1-3. The start time of SFU service period and the duration of SFU service period indicate the sub-device 1 service period.

[0121] Table 4

[0122] Field name Field length Field description Start time of the sub-device service period 4 Indication of the start time of the sub-device service period Duration of the sub-device service period 4 Indication of the duration of the sub-device service period, in us

[0123] Table 5 below provides fields that can be included in message 1-3, the length of each field, and the definition, the sub-device in Table 5 can be sub-device 1. As shown in Table 5, the start time of sub-device 1 service period and the end time of sub-device 1 service period are included in message 1-3. The start time of sub-device 1 service period and the end time of sub-device 1 service period are equivalent to the duration of sub-device 1 service period, which is equivalent to indicating the sub-device 1 service period by the start time of sub-device 1 service period and the end time of sub-device 1 service period.

[0124] Table 5

[0125] Field name Field length Field description Start time of the sub-device service period 4 Indication of the start time of the sub-device service period End time of the sub-device service period 4 Indication of the end time of the sub-device service period

[0126] It should be noted that in the examples provided in Table 4 and Table 5, the start time of the sub-device service period can be an absolute time of the start time of the sub-device service period. As another example, the start time of the sub-device service period can also be a relative time with respect to the start time of the global TWT period, and the unit of the relative time can be us. Table 6 below provides another example of the fields that can be included in the message 1-3, the length of each field and the definition on the basis of Table 4, and the sub-device in Table 6 can be the sub-device 1. As shown in Table 6, on the basis of Table 4, the message 1-3 further includes the start time of the global TWT period and the cycle time of the global TWT period, the start time of the global TWT period and the cycle time of the global TWT period are used to indicate the global TWT period, and the start time of the sub-device service period can be a time offset with respect to the start time of the global TWT period. It should be understood that the start time of the global TWT period and the end time of the global TWT period can also be included in the message 1-3, which is equivalent to indicating the global TWT period by the start time of the global TWT period and the end time of the global TWT period, and a corresponding table is not provided here.

[0127] Table 6

[0128]

[0129] As an example, the start time of the global TWT period in Table 6 can be an absolute time of the start time of the global TWT period. As another example, the start time of the global TWT period in Table 6 can also be a delay time with respect to the time when the message 1-3 is received, in other words, the time point that is delayed for a period of time from the time point when the sub-device 1 receives the message 1-3 is the start time of the global TWT period. The start time of the global TWT period field can also be referred to as a delay effective time field, which is used to indicate the time when the message 1-3 is delayed effective on the sub-device 1, and the unit can be us. If the field takes a value of all FF, it means immediate effect.

[0130] It should be noted that the start time of the sub-device service period, the end time of the sub-device service period and the start time of the global TWT period described above all refer to specific time points or time instants, and not time periods.

[0131] In some possible scenarios, messages 1-3 can also only carry part of the fields shown in Table 4, Table 5, or Table 6, and what fields are carried depends on actual application scenarios, which are not limited herein. For example, message 1-3 only includes the start time of the sub-device service period, which is equivalent to indicating the start time of the negotiation between the sub-device and the STA, and also provides effective reference information for the sub-device to negotiate at a suitable time. For another example, message 1-3 only includes the duration of the sub-device service period, which is equivalent to indicating the duration of the negotiation between the sub-device and the STA, and also provides effective reference information for the sub-device to negotiate at a suitable time. For yet another example, message 1-3 only includes the start time of the global TWT period and the duration of the global TWT period, which is equivalent to indicating the time during which all sub-devices can negotiate with the STA, so that each sub-device can negotiate within the specified time, which is conducive to taking into account the negotiation between each sub-device and the associated STA.

[0132] Optionally, before the master device sends message 1-3 to the sub-device 1, the sub-device 1 is further configured to perform step 108 to report state information to the master device, so that the master device can more targetedly allocate the corresponding sub-device 1 service period to the sub-device 1 according to the state information reported by the sub-device 1. The step 108 is described below.

[0133] 108. The sub-device 1 sends message 1-4 to the master device.

[0134] In a possible scenario, the message 1-4 sent by the sub-device 1 to the master device includes interference measurement information of an interference device that interferes with the sub-device 1, and the master device allocates the sub-device 1 service period to the sub-device 1 according to the interference measurement information of the interference device that interferes with the sub-device 1. It should be noted that the interference device that interferes with the sub-device 1 can be another sub-device or the STA, and the specific content is not limited herein. The interference measurement information of the interference device that interferes with the sub-device 1 mainly reflects which devices will interfere with the sub-device 1, and the master device will consider avoiding interference when allocating the sub-device 1 service period to the sub-device 1. For example, the sub-device 2 is an interference device that interferes with the sub-device 1, and the master device learns from the message 1-4 that the sub-device 2 is an interference device that interferes with the sub-device 1. Then, the master device allocates a sub-device 1 service period to the sub-device 1 and a sub-device 2 service period to the sub-device 2, which are two completely different sub-device service periods. In the subsequent synchronization stage and time allocation stage, the interaction between the sub-device 1 and the STA 1 will not be interfered with by the interaction between the sub-device 2 and the STA 2.

[0135] It should be noted that the specific content of the interference measurement information of the interference device and the specific format of the message 1-4 are not limited in the embodiments of the present application. The message 1-4 can include multiple fields.

[0136] Table 7 below provides the fields that can be included in the message 1-4, the length of each field, and the definition. As shown in Table 7, the message 1-4 includes the following fields: number of frequency bands, frequency bands, measured frame power, number of channel measurement results, and channel measurement results. The channel measurement results field further includes the following fields: MAC of the measured device, MAC of the measuring device, operating frequency bandwidth of the measured device, operating mode of the measured device, operating channel of the measured device, interference signal strength, type of the measured device, and signal to noise ratio (SNR) of the receiving side. It should be understood that the "measured device" in Table 7 is also the interfering device, and the information related to the "measured device" is the information of the interfering device. The "MAC of the measured device" is an identifier of the measured device, which can also be identified by "AID of the measured device" or other ways, which are not limited here. For example, the master device can determine whether to allocate the sub-device 1 with a service period of the sub-device 1 from the aspect of avoiding interference according to the MAC of the measured device in the message 1-4 and the strength of the interference signal.

[0137] Table 7

[0138]

[0139]

[0140] The present application does not limit the length of each field in the message 1-4, nor does it limit the indication content corresponding to the value of each field in the message 1-4. Similarly, the format of other messages transmitted between the master device and the sub-device is also applicable. In other words, each table provided in the embodiments of the present application is only some possible examples, and those skilled in the art can make flexible changes on this basis. For example, the byte length of each field in the table can be changed. For another example, the indication content corresponding to the value of each field can also be changed. Taking the "type of the measured device" in Table 7 as an example, the indication content corresponding to the values 0 and 1 of the "type of the measured device" can be exchanged; or other arbitrary values can be used to indicate the above-mentioned content; or the field length of the "type of the measured device" can be multiple bytes; or the field length of the "type of the measured device" can be measured in bits, and the field length of the "type of the measured device" can be 1 bit or multiple bits. Taking the field length of the "type of the measured device" including 1 bit as an example, the bit value 0 represents the measured device as an AP, and the bit value 1 represents the measured device as a STA, or the bit value 0 represents the measured device as a STA, and the bit value 1 represents the measured device as an AP.

[0141] In another possible scenario, the message 1-4 sent by the slave device 1 to the master device includes at least one of a capability parameter and an operating parameter of the slave device 1, and the master device allocates a slave device 1 service period to the slave device 1 according to the at least one of the capability parameter and the operating parameter of the slave device 1. It should be noted that the capability parameter of the slave device 1 is used to indicate a capability supported or possessed by the slave device 1, and the operating parameter of the slave device 1 is used to indicate a parameter of the slave device 1 in an actual operating state. According to actual conditions, the operating parameter of the slave device 1 can be the same as the capability parameter of the slave device 1, or the operating parameter of the slave device 1 can be different from the capability parameter of the slave device 1.

[0142] As an example, the master device can determine a duration of the slave device 1 service period allocated to the slave device 1 according to the at least one of the capability parameter and the operating parameter of the slave device 1. For example, if the slave device 1 has a high transmit power level or a large number of antennas, the duration of the slave device 1 service period allocated to the slave device 1 is also long; otherwise, if the slave device 1 has a low transmit power level or a small number of antennas, the duration of the slave device 1 service period allocated to the slave device 1 is also short.

[0143] As another example, the master device can determine whether interference is formed between devices according to the at least one of the capability parameter and the operating parameter reported by each device, so as to allocate a slave device service period to each slave device from the aspect of avoiding interference. For example, the master device determines whether interference is formed between devices according to the frequency band reported by each slave device.

[0144] It should be noted that the specific content of the capability parameter and the specific format of the message 1-4 are not limited in the embodiments of the present application. The message 1-4 can include multiple fields, and Table 8 provides possible contents of the capability parameter.

[0145] Table 8 below provides possible fields included in the message 1-4, the length of each field, and the definition. As shown in Table 8, the message 1-4 includes the following fields: a WLAN management and control interface (WMCI) version number, an 802.11 version number, a frequency band number, a frequency band 1 capability parameter, a frequency band 2 capability parameter, …, and a frequency band N capability parameter. Taking the “frequency band 1 capability parameter” field as an example, the “frequency band 1 capability parameter” field further includes the following fields: a frequency band sequence number, a frequency band, a number of supported service set identifiers (SSIDs), a supported transmit power level, a number of transmit antennas, a number of receive antennas, and a frequency width. The “WMCI version number” can also be understood as a protocol version number supported by the slave device, and the “frequency band number” is used to indicate the number of fields starting from field 4, that is, the number of capability parameters of frequency bands.

[0146] Table 8

[0147]

[0148]

[0149] It should be noted that the embodiments of the present application do not limit the specific content of the working parameters and the specific format of the messages 1-4. The messages 1-4 can include multiple fields. Table 9 below provides the content that the working parameters can include.

[0150] Table 9 below provides the fields that can be included in the message 1-4, the length of each field and the definition. As shown in Table 9, the message 1-4 includes the following fields: frequency band sequence number, SSID length, SSID, password (Password) length, password (Password), encryption mode, authentication mode, WPA encryption mode, WPA authentication mode, IEEE 11i encryption mode, IEEE 11i authentication mode, frequency band selection, channel, channel bandwidth, transmission power level, etc. Among them, the "frequency band selection" field is used to indicate the current working frequency band of the sub device 1, and the "channel" field is used to indicate the current working channel of the sub device 1.

[0151] Table 9

[0152]

[0153]

[0154] 109、The master device sends the message 2-3 to the sub device 2.

[0155] In the initialization stage before the synchronization stage and the time allocation stage, the master device allocates a sub device 2 service period for the sub device 2 to negotiate with the STA 2. The master device sends the message 2-3 to the sub device 2, which is used to instruct the sub device 2 to negotiate the wake-up time 2 (STA 2 service period) of the STA 2 with the STA 2 in the sub device 2 service period. Further, in the synchronization stage, the sub device 2 negotiates the wake-up time 2 (STA 2 service period) of the STA 2 with the STA 2 in the sub device 2 service period. It should be noted that the way the master device allocates the sub device 2 service period to the sub device 2 is similar to the way the master device allocates the sub device 1 service period to the sub device 1 in the above step 107, and the format of the message 2-3 is similar to that of the message 1-3 in the step 107. For details, please refer to the related description of the above step 107, which will not be described here. The message 2-3 can also be called a TWT negotiation time message.

[0156] Optionally, before the master device sends the message 2-3 to the slave device 2, the slave device 2 is further configured to perform step 110 to report state information to the master device, so that the master device can more specifically assign a corresponding service period of the slave device 2 to the slave device 2 according to the state information reported by the slave device 2. The step 110 will be described below.

[0157] 110. The slave device 2 sends a message 2-4 to the master device.

[0158] It should be noted that the content carried by the message 2-4 is similar to the content carried by the message 1-4 in the step 108 described above, and the format of the message 2-4 is similar to the format of the message 1-4 in the step 108. For details, please refer to the related description of the step 108 described above, which will not be repeated here.

[0159] It should be noted that in the initialization phase of the embodiment shown in Figure 5 There is no explicit timing relationship between the interaction process between the master device and the slave device 1 and the interaction process between the master device and the slave device 2 in the initialization phase of the embodiment shown in the figure. For example, the interaction process between the master device and the slave device 1 can be performed first, or the interaction process between the master device and the slave device 2 can be performed first, or the interaction process between the master device and the slave device 1 and the interaction process between the master device and the slave device 2 can be performed simultaneously.

[0160] It should be noted that in actual applications, some STAs support negotiating STA wake-up time with a slave device, and some STAs do not support negotiating STA wake-up time with a slave device. The STA that supports negotiating STA wake-up time with a slave device can be referred to as a TWT user, for example, the STA 1 and the STA 2 in the embodiment described above are TWT users. The STA that does not support negotiating STA wake-up time with a slave device can be referred to as a non-TWT user. In the time allocation phase, the master device can schedule TWT users and non-TWT users respectively, for example, the master device can preferentially schedule TWT users, and then schedule non-TWT users. For details, please refer to the steps 111 and 112 in the embodiment shown in Figure 5

[0161] 111. The master device schedules the TWT user in the STA service period.

[0162] ​Specifically, after receiving the message 1-1 sent by the sub-device 1, the master device can learn the wake-up time (STA1 service period) of STA1, and the master device can schedule STA1 in the wake-up state in the STA1 service period. Then, the master device sends the message 1-2 to the sub-device 1 to indicate that the sub-device 1 is allowed to send data to STA1 in the STA1 service period. Similarly, after receiving the message 2-1 sent by the sub-device 2, the master device can learn the wake-up time (STA2 service period) of STA2, and the master device can schedule STA2 in the wake-up state in the STA2 service period. Then, the master device sends the message 2-2 to the sub-device 2 to indicate that the sub-device 2 is allowed to send data to STA2 in the STA2 service period.

[0163] 112. The master device schedules the non-TWT user.

[0164] Specifically, taking the non-TWT user as STA3 for example, STA3 is associated with the sub-device 3, and when STA3 switches to the wake-up state, the sub-device 3 notifies the master device, and then the master device schedules STA3 in the wake-up state. For example, the master device sends a scheduling message to the sub-device 3 to indicate that the sub-device 3 is allowed to send data to STA3.

[0165] Figure 7 Fig. 1 shows a structure of the master device in an embodiment of the present application. As shown in the figure, the master device includes a processing unit 201 and a transceiver unit 202. Specifically, the transceiver unit 202 is configured to perform the message transceiving operation of the master device in the above-mentioned Figure 7 or Figure 4 embodiment. The processing unit 201 is configured to perform other operations of the master device in the above-mentioned Figure 5 or Figure 4 embodiment except for the message transceiving operation, for example, the processing unit 201 can perform operations such as decision-making and message generation. Figure 5

[0166] Fig. 2 shows another structure of the master device in an embodiment of the present application. As shown in the figure, the master device includes a processor 301 and an interface 302, and the processor 301 and the interface 302 are connected to each other through a line. It should be noted that the interface 302 is configured to perform the message transceiving operation of the master device in the above-mentioned Figure 8 or Figure 8 embodiment. The processor 301 is configured to perform other operations of the master device in the above-mentioned Figure 4 or Figure 5 embodiment except for the message transceiving operation, for example, the processor 301 can perform operations such as decision-making and message generation. Figure 4 Figure 5 ​In addition to the messaging operations of the slave device in the embodiments, the processor 501 is configured to perform other operations of the slave device. In some possible implementation, the processor 501 comprises the processing unit 401, and the interface 502 comprises the transceiver unit 402. Optionally, the slave device further comprises a memory 503, where the memory 503 is configured to store program instructions and data.

[0167] Figure 9 Fig. 4 shows a schematic diagram of a structure of a slave device in some embodiments of the present application. As shown in Fig. 4, the slave device comprises a processing unit 401 and a transceiver unit 402. Specifically, the transceiver unit 402 is configured to perform the messaging operations of the slave device in the embodiments. Figure 9 Figure 4 Figure 5 In addition to the messaging operations of the slave device in the embodiments, the processing unit 401 is configured to perform other operations of the slave device. Figure 4 Figure 5

[0168] Figure 10 Fig. 5 shows another schematic diagram of a structure of a slave device in some embodiments of the present application. As shown in Fig. 5, the slave device comprises a processor 501 and an interface 502, where the processor 501 and the interface 502 are connected to each other through a line. It is to be noted that the interface 502 is configured to perform the messaging operations of the slave device in the embodiments. The processor 501 is configured to perform other operations of the slave device in the embodiments. Figure 10 Figure 4 Figure 5 In addition to the messaging operations of the slave device in the embodiments, the processor 501 is configured to perform other operations of the slave device. In some possible implementation, the processor 501 comprises the processing unit 401, and the interface 502 comprises the transceiver unit 402. Optionally, the slave device further comprises a memory 503, where the memory 503 is configured to store program instructions and data. Figure 4 Figure 5

[0169] The chip in the embodiments of the present application further comprises a circuit and one or more interfaces for implementing the functions of the processor 301 or the processor 501. As an example, the chip comprises a memory. As another example, when the chip does not comprise a memory, the chip can be connected to an external memory through the interface. The chip can complete the method steps of any one or more of the preceding embodiments. Alternatively, the chip implements the actions performed by the transmission device in the embodiments according to the program code stored in the memory.

[0170] ​​​​​​​​As an example, the processor in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor, and can also be a processing circuit that implements specific functions.

[0171] The embodiments of the present application also provide a computer readable storage medium, including a program or instructions, when the program or instructions are executed on a computer, the program or instructions cause the computer to implement the method performed by the above method embodiments.

[0172] It should be understood that the processor mentioned in the embodiments of the present application can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor, which is implemented by reading software codes stored in a memory. The memory can exist independently and be connected to the processor, or the memory can be integrated with the processor.

[0173] As an example, the processor in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor, and can also be a processing circuit that implements specific functions.

[0174] The memory of the embodiments of the present application can be random access memory (RAM), flash memory, read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), register, hard disk, mobile hard disk, CD-ROM, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Of course, the storage medium can be a component of the processor. The processor and the storage medium can be located in an ASIC. The ASIC can be located in a network device or terminal device. Of course, the processor and the storage medium can also exist as separate components in a network device or terminal device.

[0175] In the above embodiments, the implementation can be achieved wholly or partially by software, hardware, firmware, or any combination thereof.

[0176] When implemented by using hardware, the method provided by the embodiments of the present application can be implemented without reading software code or instructions, for example, by using a CPU, DSP, ASIC, FPGA, other programmable logic device, transistor logic device, hardware component, or any combination thereof.

[0177] When implemented by using software, the implementation can be achieved wholly or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, the processes or functions of the embodiments of the present application are executed wholly or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable apparatus. The computer programs or instructions can be stored in a computer-readable storage medium or transmitted by a computer-readable storage medium. The computer-readable storage medium can be any available medium accessible by a computer or a data storage device such as a server integrated with one or more available media. The available medium can be a magnetic medium, for example, a floppy disk, a hard disk, a magnetic tape; an optical medium, for example, a digital versatile disc (DVD); or a semiconductor medium, for example, a solid state disk (SSD).

[0178] Finally, it should be noted that the above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical range disclosed by the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A service scheduling method, characterized in that, include: The sub-device sends a Station Target Wake-up Time (TWT) negotiation time reporting message to the master device. The STA TWT negotiation time reporting message includes the identifier of the STA, the start time and duration of the STA service period, and is used to indicate the negotiation result between the sub-device and the STA. The STA that is in the STA service period or in the wake-up state is scheduled by the master device.

2. The method according to claim 1, characterized in that, Before the sub-device sends the STA TWT negotiation time reporting message to the master device, the method further includes: The sub-device receives a TWT negotiation time message sent by the master device. The TWT negotiation time message is used to allocate a sub-device service period to the sub-device. The sub-device service period is used for the sub-device to negotiate the wake-up time with the STA.

3. The method according to claim 2, characterized in that, Before the sub-device receives the TWT negotiation time message sent by the master device, the method further includes: The sub-device sends status information to the master device, and the status information is used to support the master device in performing global wake-up time allocation.

4. The method according to claim 3, characterized in that, The status information includes interference measurement information.

5. The method according to claim 3, characterized in that, The status information includes the capability parameters of the sub-device; the capability parameters of the sub-device include at least one of the protocol version number supported by the sub-device, the frequency band supported by the sub-device, the number of Service Set Identifiers (SSIDs) supported by the sub-device, and the transmit power level supported by the sub-device.

6. The method according to any one of claims 2-5, characterized in that, The TWT negotiation time message includes the start time and duration of the sub-device service cycle.

7. The method according to claim 6, characterized in that, The TWT negotiation time message also includes the start time and duration of the global TWT cycle.

8. The method according to claim 7, characterized in that, The global TWT cycle includes the sub-device service cycle allocated by the master device to all sub-devices.

9. The method according to any one of claims 2-5, characterized in that, The STA service period is within the time range of the sub-device service period.

10. The method according to any one of claims 1-5, characterized in that, Before the sub-device sends the Station Target Wake-up Time (TWT) negotiation time reporting message to the master device, the method further includes: The sub-device negotiates the wake-up time of the STA with the STA.

11. The method according to any one of claims 1-5, characterized in that, The method further includes: The sub-device receives the scheduling message sent by the master device.

12. The method according to claim 11, characterized in that, The scheduling message is used to instruct the sub-device to send data to the STA during the STA service period.

13. The method according to any one of claims 1-5, characterized in that, The main device is an MFU, and the sub-device is an SFU.

14. The method according to any one of claims 1-5, characterized in that, The main device and the sub-device are connected via optical fiber.

15. A sub-device for service scheduling, characterized in that, The sub-device includes a transceiver unit; The transceiver unit is used to: send a STA target wake-up time (TWT) negotiation time reporting message to the master device. The STA TWT negotiation time reporting message includes the identifier of the STA, the start time and duration of the STA service period. The STA TWT negotiation time reporting message is used to indicate the negotiation result between the sub-device and the STA. The STA that is in the STA service period or in the wake-up state is scheduled by the master device.

16. The sub-device according to claim 15, characterized in that, Before sending the STA TWT negotiation time reporting message to the master device, the transceiver unit is further configured to: receive the TWT negotiation time message sent by the master device, the TWT negotiation time message being used to allocate a sub-device service period to the sub-device, the sub-device service period being used for the sub-device to negotiate the wake-up time with the STA.

17. The sub-device according to claim 16, characterized in that, Before receiving the TWT negotiation time message sent by the master device, the transceiver unit is further configured to: send status information to the master device, the status information being used to support the master device in performing global wake-up time allocation.

18. The sub-device according to claim 17, characterized in that, The status information includes interference measurement information.

19. The sub-device according to claim 17, characterized in that, The status information includes the capability parameters of the sub-device; the capability parameters of the sub-device include at least one of the protocol version number supported by the sub-device, the frequency band supported by the sub-device, the number of Service Set Identifiers (SSIDs) supported by the sub-device, and the transmit power level supported by the sub-device.

20. The sub-device according to any one of claims 16-19, characterized in that, The TWT negotiation time message includes the start time and duration of the sub-device service cycle.

21. The sub-device according to claim 20, characterized in that, The TWT negotiation time message also includes the start time and duration of the global TWT cycle.

22. The sub-device according to claim 21, characterized in that, The global TWT cycle includes the sub-device service cycle allocated by the master device to all sub-devices.

23. The sub-device according to any one of claims 16-19, characterized in that, The STA service period is within the time range of the sub-device service period.

24. The sub-device according to any one of claims 15-19, characterized in that, The sub-device further includes a processing unit, which is used to negotiate the wake-up time of the STA with the STA.

25. The sub-device according to any one of claims 15-19, characterized in that, The transceiver unit is also used to: receive scheduling messages sent by the master device.

26. The sub-device according to claim 25, characterized in that, The scheduling message is used to instruct the sub-device to send data to the STA during the STA service period.

27. The sub-device according to any one of claims 15-19, characterized in that, The main device is an MFU, and the sub-device is an SFU.

28. The sub-device according to any one of claims 15-19, characterized in that, The main device and the sub-device are connected via optical fiber.

29. A communication system, characterized in that, It includes a master device and at least one sub-device as described in any one of claims 15-28, wherein the master device communicates with the at least one sub-device.

30. A chip, characterized in that, The chip includes circuitry and one or more interfaces, the circuitry being configured to perform the method as described in any one of claims 1 to 14.

Images