A service scheduling method, device and system

Abstract

This application discloses a service scheduling method, apparatus, and system. Sub-devices negotiate power-saving and wake-up times with associated STAs, specifically when the STA should be in power-saving mode and when it should be in wake-up mode. The sub-devices then report the negotiated wake-up times to the master device. The master device then schedules relevant data for each STA based on its wake-up time. In this way, the master device can know the agreed-upon wake-up times between each sub-device and its associated STA before scheduling services for each STA, eliminating the need for frequent interaction with sub-devices to obtain their real-time status. By centrally managing the wake-up times of each STA, the master device can more efficiently schedule services for each STA at appropriate times.

Description

[0001] This application is a divisional application. The original application has the application number 202510039218.6 and the original application date is January 9, 2025. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a service scheduling method, apparatus, and system. Background Technology

[0003] With the development of communication technology, fiber optic transmission is increasingly being used in communication systems, among which fiber to the room (FTTR) is a crucial component of optical networks. An FTTR system consists of a main device and sub-devices, connected via optical fiber. The main device, acting as an optical network terminal (ONT) or optical network unit (ONU) in a passive optical network (PON), is connected to the optical line terminal (OLT) at the operator's central office via optical fiber.

[0004] In traditional energy-saving solutions, if a station (STA) enters an energy-saving state, the STA sends a message to the sub-device to indicate that the STA has entered the energy-saving state. While in energy-saving mode, the STA cannot receive data; while in wake-up mode, it can receive data. The master device needs to frequently interact with the sub-device to confirm whether the STA is currently in energy-saving or wake-up mode in order to schedule services for the STA at the appropriate time. However, this frequent interaction between the master and sub-devices results in a high implementation cost. Summary of the Invention

[0005] This application provides a service scheduling method, apparatus, and system. Before scheduling services for each STA, the master device can know in advance the STA wake-up time negotiated between each sub-device and the associated STA, without having to frequently interact with each sub-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.

[0006] Firstly, this application provides a service scheduling method. This method can be applied to fiber-to-the-room (FTTR) scenarios. In an FTTR system, the master device is also called the Main FTTR Unit (MFU), and the slave device is also called the Sub FTTR Unit (SFU). This service scheduling method is executed by the master device. Specifically, the slave device negotiates the wake-up time of the STA with the station (STA). After the slave device and the STA successfully negotiate the wake-up time, the master device receives a target wake-up time (TWT) negotiation time reporting message sent by the slave device. The TWT negotiation time reporting message indicates the negotiation result between the slave device and the STA. The negotiation result is the successful negotiation of the STA's wake-up time, which is the time the STA is in a wake-up state, also known as the STA service period. Furthermore, the master device schedules STAs that are in the STA service period or in a wake-up state.

[0007] In this implementation, the sub-device negotiates the STA's power-saving time and wake-up time with its associated STA, that is, when the STA should be in power-saving mode and when it should be in wake-up mode. The sub-device then reports the negotiated STA wake-up time to the master device. The master device then schedules the relevant data of the STA based on the STA's wake-up time. In this way, the master device can know the agreed-upon STA wake-up time between each sub-device and its associated STA before scheduling services for each STA, without needing to frequently interact with each sub-device to obtain 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.

[0008] In some possible implementations, before the master device receives the STA TWT negotiation time reporting message sent by the sub-device, the method further includes: the master device allocating a sub-device service period to the sub-device by sending a TWT negotiation time message to the sub-device. The sub-device service period is used for the sub-device to negotiate the wake-up time with the STA; that is, the sub-device and the STA negotiate the STA's wake-up time during the sub-device service period. In this implementation, the master device comprehensively considers multiple factors to allocate time slots for negotiation to each sub-device. The allocation method is more reasonable and targeted, which helps improve the efficiency and success rate of negotiation between each sub-device.

[0009] In some possible implementations, before the master device allocates a service period to the sub-device by sending a TWT negotiation time message, the method further includes: the master device receiving status information sent by the sub-device, the status information being used to support the master device in performing global wake-up time allocation. By reporting the status information to the master device, the master device can comprehensively consider various factors based on the status information, thereby allocating a service period to the sub-device more rationally.

[0010] In some possible implementations, the status information includes interference measurement information, which includes at least one of the following: the identifier of the interfering device, the operating mode of the interfering device, the operating bandwidth of the interfering device, the operating channel of the interfering device, the strength of the signal transmitted by the interfering device, and the device type of the interfering device. The master device allocates service periods for negotiation to the sub-devices based on the interference measurement information, taking into account interference avoidance, so that the negotiation between the sub-devices and the STA is not interfered with.

[0011] In some possible implementations, the status information includes at least one of the sub-device's capability parameters and operational parameters. The sub-device's capability parameters include at least one of the following: 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. The sub-device's operational parameters include at least one of the sub-device's operating frequency band, operating channel, operating channel bandwidth, and transmit power level. The master device will allocate sub-device service periods for negotiation to the sub-device more effectively by considering multiple factors based on at least one of the capability parameters and operational parameters, enabling the sub-device to negotiate with the STA at a more appropriate time.

[0012] In some possible implementations, the TWT negotiation time message includes the start time and duration of the sub-device service period, or the TWT negotiation time message includes the start and end times of the sub-device service period. This allows the sub-device to quickly determine the sub-device service period to be negotiated based directly on the content carried in the TWT negotiation time message.

[0013] In some possible implementations, the TWT negotiation time message also includes the start time and duration of the global TWT period. Alternatively, the TWT negotiation time message may also include the start and end times of the global TWT period. The global TWT period includes the sub-device service period allocated by the master device to all sub-devices. In this implementation, the master device defines the global TWT period and assigns a corresponding sub-device service period to each sub-device within each global TWT period, ensuring that each sub-device is allocated a corresponding sub-device service period within a global TWT period. This facilitates both negotiation and service transmission between each sub-device and its associated STA.

[0014] In some possible implementations, the STA service period falls within the time frame of the sub-device service period. That is, the STA service period negotiated between the sub-device and the STA, when the STA is in a wake-up state, falls within the time frame of the sub-device service period negotiated between them. In this way, by assigning completely different sub-device service periods to different sub-devices, the master device avoids interference between the negotiation processes of different sub-devices and also avoids interference between the service transmission processes of different sub-devices.

[0015] In some possible implementations, the STA TWT negotiation time reporting message includes the STA's identifier, the start time and duration of the STA service period. Alternatively, the STA TWT negotiation time reporting message includes the STA's identifier, the start time and end time of the STA service period. The start time of the STA service period is also the STA's wake-up start time, the end time of the STA service period is also the STA's wake-up end time, and the duration of the STA service period is the STA's wake-up duration. This allows the master device to quickly determine the STA's wake-up time directly based on the content carried in the STA TWT negotiation time reporting message.

[0016] In some possible implementations, the master device scheduling an STA that is in a STA service cycle or in a wake-up state includes: the master device sending a scheduling message to the sub-device, the scheduling message instructing the sub-device to send data to the STA during the STA service cycle. This ensures that the STA receives data sent by the sub-device while in a wake-up state, guaranteeing normal service scheduling and reception.

[0017] Secondly, this application provides a service scheduling method applicable to FTTR scenarios. In the FTTR system, the master device is also referred to as MFU, and the slave device is also referred to as SFU. This service scheduling method is executed by the slave device. Specifically, the slave device negotiates with the STA to determine the STA's wake-up time. After the slave device and the STA successfully negotiate the STA's wake-up time, the slave device sends a STA TWT negotiation time reporting message to the master device. The STA TWT negotiation time reporting message is used to indicate the negotiation result between the slave device and the STA. The STA that is in its service cycle or in a wake-up state is scheduled by the master device.

[0018] In some possible implementations, before the sub-device sends the STA TWT negotiation time reporting message to the master device, the method further includes: the sub-device receiving 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, and the sub-device service period being used for the sub-device to negotiate the wake-up time with the STA.

[0019] In some possible implementations, before the sub-device receives the TWT negotiation time message sent by the master device, the method further includes: the sub-device sending status information to the master device, the status information being used to support the master device in performing global wake-up time allocation.

[0020] In some possible implementations, the status information includes interference measurement information, which includes at least one of the following: the identifier of the interference device, the operating mode of the interference device, the operating bandwidth of the interference device, the operating channel of the interference device, the strength of the signal transmitted by the interference device, and the device type of the interference device.

[0021] In some possible implementations, the status information includes at least one of the sub-device's capability parameters and operating parameters. The sub-device's capability parameters include at least one of the sub-device's supported protocol version number, supported frequency bands, supported SSIDs, and supported transmit power levels. The sub-device's operating parameters include at least one of the sub-device's operating frequency band, operating channel, operating channel bandwidth, and transmit power level.

[0022] In some possible implementations, the TWT negotiation time message includes the start time and duration of the sub-device service cycle, or the TWT negotiation time message includes the start time and end time of the sub-device service cycle.

[0023] In some possible implementations, the TWT negotiation time message may also include the start time and duration of the global TWT cycle, or the TWT negotiation time message may also include the start and end times of the global TWT cycle. The global TWT cycle includes the sub-device service cycle allocated by the master device to all sub-devices.

[0024] In some possible implementations, the STA service period is within the time frame of the sub-device service period.

[0025] In some possible implementations, the STA TWT negotiation time reporting message includes the STA identifier, the start time and duration of the STA service period, or the STA TWT negotiation time reporting message includes the STA identifier, the start time and end time of the STA service period.

[0026] In some possible implementations, the method further includes: the sub-device receiving a scheduling message sent by the master device, the scheduling message being used to instruct the sub-device to send data to the STA during the STA service period.

[0027] Thirdly, embodiments of this application provide a master device, which can be an MFU in an FTTR system. The master device includes a transceiver unit and a processing unit. The transceiver unit is used to: receive a STA TWT negotiation time reporting message sent by the sub-device after the sub-device successfully negotiates the STA's wake-up time with the STA. The STA TWT negotiation time reporting message is used to indicate the negotiation result between the sub-device and the STA. The processing unit is used to: schedule STAs that are in the STA service cycle or in the wake-up state.

[0028] In some possible implementations, before receiving the STA TWT negotiation time reporting message sent by the sub-device, the transceiver unit is further configured to: allocate a sub-device service period to the sub-device by sending a TWT negotiation time message 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 implementations, before allocating a service period for a sub-device by sending a TWT negotiation time message to the sub-device, the transceiver unit is also configured to: receive status information sent by the sub-device, the status information being used to support the master device in performing global wake-up time allocation.

[0030] In some possible implementations, the status information includes interference measurement information, which includes at least one of the following: the identifier of the interference device, the operating mode of the interference device, the operating bandwidth of the interference device, the operating channel of the interference device, the strength of the signal transmitted by the interference device, and the device type of the interference device.

[0031] In some possible implementations, the status information includes at least one of the sub-device's capability parameters and operating parameters. The sub-device's capability parameters include at least one of the following: the protocol version number supported by the sub-device, the frequency band supported by the sub-device, the number of SSIDs supported by the sub-device, and the transmit power level supported by the sub-device. The sub-device's operating parameters include at least one of the following: the sub-device's operating frequency band, the sub-device's operating channel, the sub-device's operating channel bandwidth, and the sub-device's transmit power level.

[0032] In some possible implementations, the TWT negotiation time message includes the start time and duration of the sub-device service cycle, or the TWT negotiation time message includes the start time and end time of the sub-device service cycle.

[0033] In some possible implementations, the TWT negotiation time message may also include the start time and duration of the global TWT cycle. Alternatively, the TWT negotiation time message may also include the start and end times of the global TWT cycle. The global TWT cycle includes the sub-device service cycle allocated by the master device to all sub-devices.

[0034] In some possible implementations, the STA service period is within the time frame of the sub-device service period.

[0035] In some possible implementations, the STA TWT negotiation time reporting message includes the STA's identifier, the start time and duration of the STA service period. Alternatively, the STA TWT negotiation time reporting message includes the STA's identifier, the start time and end time of the STA service period.

[0036] In some possible implementations, the transceiver unit is also configured to: send a scheduling message to the sub-device, the scheduling message being used to instruct the sub-device to send data to the STA during the STA service period.

[0037] Fourthly, this application provides a sub-device, which can be an SFU in an FTTR system. The sub-device includes a transceiver unit and a processing unit. The processing unit is used to negotiate the wake-up time of the STA with the STA. The transceiver unit is used to send a STA TWT negotiation time reporting message to the master device after the sub-device successfully negotiates the STA's wake-up time. The STA TWT negotiation time reporting message is used to indicate the negotiation result between the sub-device and the STA. The STA, which is in a service cycle or in a wake-up state, is scheduled by the master device.

[0038] In some possible implementations, before sending the STA TWT negotiation time reporting message to the master device, the transceiver unit is also used 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, and the sub-device service period being used for the sub-device to negotiate the wake-up time with the STA.

[0039] In some possible implementations, before receiving the TWT negotiation time message sent by the master device, the transceiver unit is also used 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.

[0040] In some possible implementations, the status information includes interference measurement information, which includes at least one of the following: the identifier of the interference device, the operating mode of the interference device, the operating bandwidth of the interference device, the operating channel of the interference device, the strength of the signal transmitted by the interference device, and the device type of the interference device.

[0041] In some possible implementations, the status information includes at least one of the sub-device's capability parameters and operating parameters. The sub-device's capability parameters include at least one of the sub-device's supported protocol version number, supported frequency bands, supported SSIDs, and supported transmit power levels. The sub-device's operating parameters include at least one of the sub-device's operating frequency band, operating channel, operating channel bandwidth, and transmit power level.

[0042] In some possible implementations, the TWT negotiation time message includes the start time and duration of the sub-device service cycle, or the TWT negotiation time message includes the start time and end time of the sub-device service cycle.

[0043] In some possible implementations, the TWT negotiation time message may also include the start time and duration of the global TWT cycle, or the TWT negotiation time message may also include the start and end times of the global TWT cycle. The global TWT cycle includes the sub-device service cycle allocated by the master device to all sub-devices.

[0044] In some possible implementations, the STA service period is within the time frame of the sub-device service period.

[0045] In some possible implementations, the STA TWT negotiation time reporting message includes the STA identifier, the start time and duration of the STA service period, or the STA TWT negotiation time reporting message includes the STA identifier, the start time and end time of the STA service period.

[0046] In some possible implementations, the transceiver unit is also configured to: receive a scheduling message sent by the master device, the scheduling message being used to instruct the sub-device to send data to the STA during the STA service period.

[0047] Fifthly, embodiments of this application provide a master device that includes instructions that, when executed by the master device, cause the master device to perform the method described in any embodiment of the first aspect.

[0048] In a sixth aspect, embodiments of this application provide a sub-device that includes instructions that, when executed by the sub-device, cause the sub-device to perform the method as described in any embodiment of the second aspect.

[0049] In a seventh aspect, embodiments of this application provide a master device, which includes a processor and an interface. The interface is used to transmit and receive signals, and the processor is used to execute the method described in any embodiment of the first aspect.

[0050] Eighthly, embodiments of this application provide a sub-device, which includes a processor and an interface. The interface is used to transmit and receive signals, and the processor is used to perform the method described in any embodiment of the second aspect.

[0051] In a ninth aspect, embodiments of this application provide a communication system comprising a master device as described in any embodiment of the third aspect, the fifth aspect, or the seventh aspect, and at least one sub-device as described in any embodiment of the fourth aspect, the sixth aspect, or the eighth aspect, wherein the master device communicates with at least one sub-device.

[0052] In a tenth aspect, embodiments of this application provide a chip for performing the methods described in any of the first or second aspects.

[0053] In one aspect, this application provides a computer-readable storage medium storing instructions that, when executed by a computer, cause the method described in any of the embodiments of the first or second aspect to be implemented.

[0054] In a twelfth aspect, this application provides a computer program product including program instructions that, when executed, implement the method described in any of the embodiments of the first or second aspect above. Attached Figure Description

[0055] Figure 1 This is a schematic diagram of a possible WLAN network architecture in an embodiment of this application;

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

[0057] Figure 3 This is a schematic diagram of the FTTR system architecture;

[0058] Figure 4 A flowchart of a service scheduling method provided in an embodiment of this application;

[0059] Figure 5 Another flowchart of the service scheduling method provided in the embodiments of this application;

[0060] Figure 6 This is a schematic diagram illustrating how the master device allocates service cycles to each sub-device in an embodiment of this application.

[0061] Figure 7 This is a schematic diagram of the structure of the main device in one embodiment of this application;

[0062] Figure 8 This is a schematic diagram of another structure of the main device in an embodiment of this application;

[0063] Figure 9 This is a schematic diagram of the structure of a sub-device in an embodiment of this application;

[0064] Figure 10 This is a schematic diagram of another structure of the sub-device in the embodiments of this application. Detailed Implementation

[0065] This application provides a service scheduling method, apparatus, and system. The service scheduling method can be applied to fiber-to-the-room (FTTR) scenarios. Before scheduling services for each STA, the master device can know in advance the STA wake-up time negotiated between each sub-device and its associated STA, eliminating the need for frequent interaction with each sub-device to obtain 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 appropriate times.

[0066] It should be understood that the terms "an embodiment," "an implementation," "an embodiment," or "an example" used throughout the specification mean that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, the phrases "in an embodiment," "an implementation," "an embodiment," or "an example" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0067] Furthermore, the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information. And, unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects. Furthermore, the terms "comprising" and "having" in the embodiments, claims, and drawings of this application are not exclusive. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the listed steps or modules and may also include steps or modules not listed.

[0068] See Figure 1 The diagram illustrates a possible WLAN network architecture. The wireless local area network (WLAN) architecture includes a wireless controller (also referred to as a "control node" in this embodiment), wireless access points (also referred to as "network nodes" in this embodiment), and terminal devices. The wireless controller is used to configure services and radio frequency for the access points. The wireless access point (AP) is used to provide service access to associated STAs. Terminal devices, acting as STAs, can be associated with the access point.

[0069] Terminal devices can include mobile phones (or "cellular" phones), computers with mobile terminal devices, portable, pocket-sized, handheld, and computer-embedded mobile devices, etc. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and other devices. Terminal devices can also be computers, tablets, e-readers, and smart home devices such as smart TVs and smart speakers. As an example and not a limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices or smart wearable devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Wearable smart devices in a broad sense include those that are feature-rich, large in size, and can perform all or part of their functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets, smart helmets, and smart jewelry for vital sign monitoring.

[0070] With the development of communication technology, fiber optic transmission is increasingly being used in communication systems, among which fiber to the room (FTTR) is a crucial component of optical networks. An FTTR system consists of a main device and sub-devices, connected via optical fiber. The main device, acting as an optical network terminal (ONT) or optical network unit (ONU) in a passive optical network (PON), is connected to the optical line terminal (OLT) at the operator's central office via optical fiber.

[0071] Figure 2This is a schematic diagram of a fiber-to-the-home / office (FTTH / O) system architecture. It connects upstream network-side equipment (such as switches and routers) and downstream ONTs via an optical distribution network (ODN). The ODN includes passive optical splitters for optical power distribution, a trunk fiber connecting the passive optical splitters and the OLT, and branch fibers connecting the passive optical splitters and ONTs. When transmitting downlink signals, the downlink signal sent by the OLT is transmitted to each ONT through the splitter, and the ONT selectively receives the downlink data belonging to itself from the downlink signal. When transmitting uplink signals, the uplink signals sent by N ONTs are combined into a single optical signal by the splitter and transmitted to the OLT.

[0072] Building upon FTTH / O, to address signal coverage issues (such as wireless LAN (WLAN) signals) in home or office networks, fiber optic cables can be extended further into the room. Optical terminal equipment providing WLAN signals is installed inside the room, thus reducing the distance between the user terminal and the wireless access point (AP) and improving signal quality. This technology is called Fiber to the Room (FTTR).

[0073] Figure 3 This is a schematic diagram of the FTTR system architecture. In FTTH / O, the OLT is deployed in the central equipment room, while the ONT is deployed in homes or offices. The master device in the FTTR network acts as both the ONT in the FTTH network and the upstream device for the FTTR sub-devices, managing them. The sub-devices in FTTR can be deployed in various rooms of homes or offices to provide signal to user terminals. The sub-devices possess ONT functionality and can also function as wireless access points (APs).

[0074] Multiple sub-devices can be deployed in an FTTR system, each connected to the main device via an optical splitter. The main device can manage and configure all sub-devices centrally. The main device can also be called a "main gateway," "main optical modem," or "main FTTR unit (MFU)," while sub-devices can be called "slave gateways," "slave optical modems," or "slave FTTR units (SFU)," etc.

[0075] It should be noted that this application can be applied to any point-to-multipoint (P2MP) communication system, which specifically includes a master device and multiple sub-devices, and the master device can collaboratively manage multiple sub-devices. For example, in... 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 a STA can be divided into a power-saving state and a wake-up state. In the wake-up state, the STA can transmit and receive data normally; when the STA switches to the power-saving state, data transmission and reception will be suspended. The time the STA is in the power-saving state can be called the power-saving time, and the time the STA is in the wake-up state can be called the wake-up time or STA service cycle. To improve the power-saving efficiency of the STA, a target wake time (TWT) power-saving mechanism is defined, that is, the sub-device and the STA can negotiate the power-saving time and wake-up time of the STA. In the embodiments of this application, during the synchronization phase, the sub-device 1 can be associated with at least one STA, including STA1. Among the STAs associated with the sub-device 1, there may be STAs that support negotiation and STAs that do not support negotiation. Taking STA1 supporting negotiation with the sub-device 1 as an example, the sub-device 1 negotiates the wake-up time and power-saving time of STA1 with STA1. If the negotiation is successful, the sub-device 1 can know the wake-up time and power-saving time of STA1 in advance, which is equivalent to the sub-device 1 knowing in advance when STA1 is in the wake-up state and when it is in the power-saving state. For STAs that do not support negotiation with sub-device 1, the STA will only notify sub-device 1 when switching between power-saving state and wake-up state. Sub-device 1 cannot know the wake-up time and power-saving time of the STA in advance.

[0080] 102. Sub-device 1 sends message 1-1 to master device.

[0081] During the synchronization phase, after sub-device 1 negotiates the wake-up time and power-saving time of STA1, sub-device 1 sends message 1-1 to the master device. Message 1-1 indicates the wake-up time 1 of STA1. The wake-up time 1 of STA1 can also be understood as the period 1 during which STA1 is in a wake-up state, also referred to as the STA1 service cycle. It should be understood that, considering the master device needs to know the wake-up time 1 of STA1 to schedule services for STA1 at that wake-up time, sub-device 1 needs to report the wake-up time 1 of STA1 to the master device via message 1-1. Whether the power-saving time 1 of STA1 needs to be reported to the master device is not limited. Message 1-1 can also be called the STA TWT negotiation time reporting message.

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

[0083] Table 1 below provides a list of fields that may be included in message 1-1, the length of each field, and their definitions. In Table 1, STA can be STA1, and sub-device can be sub-device 1. As shown in Table 1, message 1-1 includes the STA identifier, the sub-device's basic service set identifier (BSSID), 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 STA's wake-up start time, and the duration of the STA service period is the STA's wake-up duration. The STA's wake-up time is indicated by the start time and the duration of the STA service period.

[0084] Table 1

[0085] Field Name Field length Field Description STA logo 6 STA logo BSSID of sub-device 6 The sub-device negotiates the wake-up time BSSID with the STA. Start time of STA service period 4 Indicates the start time of the STA service cycle within the TWT cycle. STA service cycle duration 4 Indicates the duration of the STA service cycle within the TWT period, in microseconds (µs).

[0086] Table 2 below provides another possible set of fields that may be included in message 1-1, the length of each field, and its definition. In Table 2, STA can be STA1, and sub-device can be sub-device 1. As shown in Table 2, message 1-1 includes the STA identifier, the sub-device's BSSID, 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 STA's wake-up start time, and the end time of the STA service period is also the STA's wake-up end time. Knowing the start and end times of the STA service period is equivalent to knowing the duration of the STA service period; it's like using the start and end times of the STA service period to indicate the STA's wake-up time.

[0087] Table 2

[0088] Field Name Field length Field Description STA logo 6 STA logo BSSID of sub-device 6 The sub-device negotiates the wake-up time BSSID with the STA. Start time of STA service period 4 Indicates the start time of the STA service cycle within the TWT cycle. End time of STA service period 4 Indicates the end time of the STA service cycle within the TWT cycle.

[0089] As an example, the "Start Time of STA Service Cycle" in Tables 1 and 2 can be the absolute time of the wake-up start time negotiated between STA1 and sub-device 1. As another example, the "Start Time of STA Service Cycle" in Tables 1 and 2 can also be a relative time relative to the start time of the global TWT cycle, and the unit of this relative time can be microseconds (µs).

[0090] It should be understood that the STA identifier mentioned above can be the STA's media access control (MAC) address or the STA's association identifier (AID), etc., and is not specifically limited here. The BSSID field for the sub-devices in Tables 1 and 2 is optional. For example, if sub-device 1 provides multiple Wi-Fi networks corresponding to multiple BSSIDs, the BSSID of sub-device 1 can indicate the Wi-Fi network that STA1 accesses. The start time and end time of the STA service period mentioned above refer to specific points in time, not time periods.

[0091] It should be noted that in some possible scenarios, message 1-1 may only carry some of the fields shown in Table 1 or Table 2. The specific fields carried depend on the actual application scenario and are not limited here. For example, message 1-1 may only include the STA identifier and the start time of the STA service period, which is equivalent to indicating the STA's wake-up start time and is sufficient to provide the master device with effective reference information for service scheduling at the appropriate time. As another example, message 1-1 may only include the STA identifier and the duration of the STA service period, which is equivalent to indicating the STA's wake-up duration and is also sufficient to provide the master device with effective reference information for service scheduling at the appropriate time.

[0092] This application does not limit the length of each field in message 1-1, nor does it limit the indication content corresponding to the value of each field in message 1-1. Similarly, it applies to the format of other messages transmitted between the master device and the slave device. In other words, each table provided in the embodiments of this application is only a few possible examples, and those skilled in the art can make flexible modifications based on them. For example, the byte length of each field in the table can be changed. Or, the indication content corresponding to the value of each field can also be changed. Taking the fields in Table 1 as examples, the length of each field can be flexibly set; or, the length of each field can also be measured in bits.

[0093] 103. Sub-device 2 negotiates with STA2 to determine STA2's wake-up time.

[0094] During the synchronization phase, sub-device 2 can associate with at least one STA, including STA2. Among the STAs associated with sub-device 2, some may support negotiation, while others may not. Taking STA2 supporting negotiation with sub-device 2 as an example, sub-device 2 negotiates STA2's wake-up time and power-saving time with STA2. If the negotiation is successful, sub-device 2 can know STA2's wake-up time and power-saving time in advance, which is equivalent to sub-device 2 knowing in advance when STA2 is in a wake-up state and when it is in a power-saving state. For STAs that do not support negotiation with sub-device 2, the STA will only notify sub-device 2 when switching between a power-saving state and a wake-up state; sub-device 2 cannot know the wake-up time and power-saving time of such STAs in advance.

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

[0096] 104. Sub-device 2 sends message 2-1 to master device.

[0097] During the synchronization phase, after sub-device 2 negotiates the wake-up time and power-saving time of STA2 with STA2, sub-device 2 sends message 2-1 to the master device. Message 2-1 indicates the wake-up time 2 of STA2. The wake-up time 2 of STA2 can also be understood as the period 2 during which STA2 is in a wake-up state, also known as the STA2 service cycle. It should be understood that, considering the master device needs to know the wake-up time 2 of STA2 to schedule services for STA2 at that time, sub-device 2 needs to report the wake-up time 2 of STA2 to the master device via message 2-1. Whether the power-saving time 2 of STA2 needs to be reported to the master device is not limited. Message 2-1 can also be called the STA TWT negotiation time reporting message. It should be noted that the format of message 2-1 is similar to that of message 1-1 above; please refer to the above description of the format of message 1-1 for details, which will not be repeated here.

[0098] 105. The master device sends message 1-2 to the slave device 1.

[0099] After receiving message 1-1 from sub-device 1, the master device can determine STA1's wake-up time 1. Therefore, the master device can schedule STA1's data according to STA1's wake-up time 1 during the time allocation phase. Specifically, the master device can send message 1-2 to sub-device 1 to instruct sub-device 1 to allow data transmission to STA1 during STA1's wake-up time 1 (STA1's service cycle). Message 1-2 can also be called a scheduling message. The master device can send the data it needs to transmit to STA1 to sub-device 1 in advance. After receiving message 1-2, sub-device 1 obtains permission to send data to STA1 and can then choose whether to send the data to STA1 based on the actual situation. For example, if sub-device 1's channel is idle, it can immediately send data to STA1. Or, if sub-device 1's channel is busy, it needs to wait until the channel becomes idle before sending data to STA1.

[0100] It should be noted that message 1-2 serves two purposes: firstly, it instructs sub-device 1 to allow data transmission to STA1; secondly, it instructs sub-device 1 to allow data transmission to STA1 during STA1's wake-up time 1 (STA1's service cycle). For example, message 1-2 could adopt the message format used by the master device to schedule data transmission to the STA, where some fields in this format instruct sub-device 1 to allow data transmission to STA1, and other fields in this format instruct sub-device 1 to allow data transmission to STA1 during STA1's wake-up time 1.

[0101] In one possible implementation 1, the master device can send message 1-2 to the slave device 1 before the wake-up time 1 of STA1 arrives, instructing the slave device 1, through fields defined in message 1-2, that the slave device 1 is permitted to send data to STA1 during 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, instructing the slave device 1, through message 1-2, that the slave device 1 is permitted to send data to STA1 during the wake-up time 1 of STA1.

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

[0103] Table 3 below provides a list of fields that may be included in message 1-2, the length of each field, and its 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 for STAs, MAC address of STAs, and priority.

[0104] It should be noted that the "delay time" field in message 1-2 indicates the delay time between the effective time of scheduling control and the time of receiving message 1-2. For example, in embodiment 1 above, the master device sends message 1-2 to the slave device 1 before the wake-up time 1 of STA1 arrives, and the "delay time" field in message 1-2 indicates how long after receiving message 1-2 the slave device 1 is allowed to send data to STA1. As another example, in embodiment 2 above, the master device sends message 1-2 to the slave device 1 when the wake-up time 1 of STA1 arrives, and the "delay time" field in message 1-2 indicates that the slave device 1 is allowed to immediately send data to STA1 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 1-2 should be at the time 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 above Figure 4 In the illustrated embodiment, in some possible scenarios, during the initialization phase, the master device can also allocate a time slot (service cycle of sub-device 1) for negotiation with STA1 to sub-device 1, and a time slot (service cycle of sub-device 2) for negotiation with STA2 to sub-device 2. This allows sub-device 1 to negotiate the wake-up time of STA1 with STA1 according to the time slot allocated by the master device during the synchronization phase, and allows sub-device 2 to negotiate the wake-up time of STA2 with STA2 according to the time slot allocated by the master device during the synchronization phase. The master device comprehensively considers multiple factors to allocate time slots for negotiation to each sub-device, resulting in a more reasonable and targeted allocation method. This helps avoid mutual interference between sub-devices during negotiation and also improves the efficiency and success rate of negotiation between sub-devices. The relevant content of the initialization phase will be described in detail below.

[0112] Figure 5 Another flowchart illustrating the service scheduling method provided in this application embodiment. Figure 5 As shown in the embodiments of this application, the service scheduling method further includes the following steps.

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

[0114] During the initialization phase, prior to the synchronization and time allocation phases, the master device allocates a negotiation time slot 1 for sub-device 1 to negotiate with STA1. The master device sends messages 1-3 to sub-device 1, instructing sub-device 1 to negotiate STA1's wake-up time 1 during negotiation time slot 1. Then, during the synchronization phase, sub-device 1 negotiates STA1's wake-up time 1 with STA1 during negotiation time slot 1. Negotiation time slot 1 can also be referred to as sub-device 1's service period, and messages 1-3 can be referred to as TWT negotiation time messages.

[0115] Figure 6 This is a schematic diagram illustrating how the master device allocates service cycles to each sub-device in an embodiment of this application. For example... Figure 6 As shown, the start time of the global TWT cycle refers to the delay time from when the sub-device receives a message to when the global TWT cycle begins; the global TWT cycle length refers to the duration of each TWT cycle; the sub-device service cycle start time refers to the start time of the sub-device service cycle within the TWT cycle; the sub-device service cycle duration refers to the duration within the TWT cycle that the sub-device uses to negotiate the TWT service cycle with the STA; the STA service cycle start time refers to the start time of the wake-up time actually negotiated between the STA associated with the sub-device and the sub-device; and the STA service cycle duration refers to the wake-up duration negotiated between the STA associated with the sub-device and the sub-device.

[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 a list of fields that may be included in messages 1-3, the length of each field, and their definitions. The sub-device in Table 4 can be sub-device 1. As shown in Table 4, messages 1-3 include the start time of the SFU service period and the duration of the SFU service period. The start time and duration of the SFU service period indicate the service period of sub-device 1.

[0121] Table 4

[0122] Field Name Field length Field Description Start time of sub-device service cycle 4 Indicator sub-device service cycle start time Duration of sub-device service cycle 4 Indicates the duration of the sub-device's service cycle, in microseconds (µs).

[0123] Table 5 below provides another set of fields that may be included in messages 1-3, the length of each field, and their definitions. The sub-device in Table 5 can be sub-device 1. As shown in Table 5, messages 1-3 include the start time and end time of the service period for sub-device 1. Knowing the start and end times of the service period for sub-device 1 is equivalent to knowing the duration of the service period for sub-device 1; it's like indicating the service period for sub-device 1 using the start and end times of the service period for sub-device 1.

[0124] Table 5

[0125] Field Name Field length Field Description Start time of sub-device service cycle 4 Indicator sub-device service cycle start time End time of sub-device service cycle 4 Indicates the end time of the service cycle of the sub-device.

[0126] It should be noted that in the examples provided in Tables 4 and 5, the start time of the sub-device service period can be an absolute time. As another example, the start time of the sub-device service period can also be a relative time relative to the start time of the global TWT period, and the unit of this relative time can be microseconds (µs). Table 6 below provides another set of fields that may be included in messages 1-3, along with the length and definition of each field, based on Table 4. The sub-device in Table 6 can be sub-device 1. As shown in Table 6, based on Table 4, messages 1-3 also include the start time of the global TWT period and the cycle time of the global TWT period. The global TWT period is indicated by the start time and cycle time of the global TWT period, and the start time of the sub-device service period can be a time deviation relative to the start time of the global TWT period. It should be understood that messages 1-3 may also include the start time and end time of the global TWT cycle, which is equivalent to indicating the global TWT cycle through the start time and end time of the global TWT cycle. The corresponding table is not provided here.

[0127] Table 6

[0128]

[0129] As an example, the "Start Time of Global TWT Cycle" in Table 6 can be an absolute start time of the global TWT cycle. As another example, the "Start Time of Global TWT Cycle" in Table 6 can also be a delay relative to the time messages 1-3 are received. In other words, the start time of the global TWT cycle is the point in time after a certain delay from the time sub-device 1 receives messages 1-3. The "Start Time of Global TWT Cycle" field can also be called the "Delayed Effective Time Field," used to indicate the time delay before messages 1-3 take effect on sub-device 1. The unit can be microseconds (µs). If the field value is all FF, it indicates immediate effectiveness.

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

[0131] In some possible scenarios, messages 1-3 may only carry some of the fields shown in Tables 4, 5, or 6. The specific fields carried depend on the actual application scenario and are not limited here. For example, messages 1-3 may only include the start time of the sub-device service period, which is equivalent to indicating the start time for the sub-device to negotiate with the STA, providing sufficient reference information for the sub-device to negotiate at the appropriate time. Similarly, messages 1-3 may only include 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, also providing sufficient reference information for the sub-device to negotiate at the appropriate time. Furthermore, messages 1-3 may only include the start time and duration of the global TWT period, which is equivalent to indicating the time when all sub-devices can negotiate with the STA, ensuring that each sub-device can negotiate within the specified time, thus facilitating negotiations between each sub-device and its associated STA.

[0132] Optionally, before the master device sends messages 1-3 to the sub-device 1, the sub-device 1 is also used to perform step 108 to report status information to the master device, so that the master device can allocate the corresponding sub-device 1 service cycle to the sub-device 1 more specifically according to the status information reported by the sub-device 1. Step 108 is described below.

[0133] 108. Sub-device 1 sends messages 1-4 to the master device.

[0134] In one possible scenario, messages 1-4 sent by sub-device 1 to the master device include interference measurement information of interfering devices that interfere with sub-device 1. The master device allocates service cycles to sub-device 1 based on this interference measurement information. It should be noted that the interfering devices can be other sub-devices or STAs; the specifics are not limited here. The interference measurement information of the interfering devices mainly reflects which devices will interfere with sub-device 1. The master device allocates service cycles to sub-device 1 with the aim of avoiding interference. For example, if sub-device 2 is an interfering device that interferes with sub-device 1, and the master device learns from messages 1-4 that sub-device 2 is an interfering device, then the service cycles allocated to sub-device 1 and sub-device 2 by the master device are two completely different sub-device service cycles. In the subsequent synchronization and time allocation phases, the interaction between sub-device 1 and STA1 will not be interfered with by the interaction between sub-device 2 and STA2.

[0135] It should be noted that the embodiments of this application do not limit the specific content of the interference measurement information of the interference device and the specific format of messages 1-4. Messages 1-4 may include multiple fields.

[0136] Table 7 below provides a list of fields that may be included in messages 1-4, the length of each field, and their definitions. As shown in Table 7, messages 1-4 include the following fields: number of frequency bands, frequency band, measurement frame power, number of channel measurement results, and channel measurement results. The channel measurement results field further includes the following fields: MAC address of the device under test (DUT), MAC address of the measuring device, operating bandwidth of the DUT, operating mode of the DUT, operating channel of the DUT, interference signal strength, type of the DUT, and signal-to-noise ratio (SNR) at the receiving end. It should be understood that the "DUT" in Table 7 is the interference device, and the information related to the "DUT" is the information of the interference device. The "MAC address of the DUT" is an identifier for the DUT, but it can also be identified by other methods such as the "AID of the DUT," which is not limited here. For example, based on the MAC address of the DUT and the strength of the interference signal in messages 1-4, the master device can determine whether to allocate a service period to sub-device 1 to avoid interference.

[0137] Table 7

[0138]

[0139]

[0140] This application does not limit the length of each field in messages 1-4, nor does it limit the indication content corresponding to the value of each field in messages 1-4. Similarly, it applies to the format of other messages transmitted between the master device and the slave device. In other words, each table provided in the embodiments of this application is merely a few possible examples, and those skilled in the art can make flexible modifications based on them. For example, the byte length of each field in the table can be changed. Or, for example, the indication content corresponding to the value of each field can also be changed. Taking the "Type of Device Under Measure" in Table 7 as an example, the indication content corresponding to the values ​​of 0 and 1 in "Type of Device Under Measure" can be interchanged; or, any other arbitrary value can be used to indicate the above content; or, the field length of "Type of Device Under Measure" can be multiple bytes; or, the field length of "Type of Device Under Measure" can be measured in bits. The field length of "Type of Device Under Measure" for the type of interfering device can be 1 bit or more bits. Taking the field length of "Type of Device Under Measure" including 1 bit as an example, a bit value of 0 indicates that the device under Measure is AP, a bit value of 1 indicates that the device under Measure is STA, or a bit value of 0 indicates that the device under Measure is STA, and a bit value of 1 indicates that the device under Measure is AP.

[0141] In another possible scenario, messages 1-4 sent by sub-device 1 to master device include at least one parameter among sub-device 1's capability parameters and operational parameters. Master device assigns service cycles to sub-device 1 based on at least one of these parameters. It should be noted that sub-device 1's capability parameters indicate the capabilities that sub-device 1 supports or possesses, while sub-device 1's operational parameters indicate the parameters of sub-device 1 in its actual operating state. Depending on the actual situation, sub-device 1's operational parameters may be the same as or different from its capability parameters.

[0142] As an example, the master device can determine the duration of the service period allocated to the sub-device 1 based on at least one of the sub-device 1's capability parameters and operating parameters. For instance, if the sub-device 1 has a higher transmit power level or more antennas, the duration of the service period allocated to the sub-device 1 will be longer; conversely, if the sub-device 1 has a higher transmit power level or fewer antennas, the duration of the service period allocated to the sub-device 1 will be shorter.

[0143] As another example, the master device can determine whether there is mutual interference between the sub-devices based on at least one of the capability parameters and operating parameters reported by each device, so as to allocate service cycles to each sub-device from the perspective of avoiding interference. For example, the master device can determine whether there is mutual interference between the sub-devices based on the frequency bands reported by each sub-device.

[0144] It should be noted that the embodiments of this application do not limit the specific content of the capability parameters and the specific format of messages 1-4. Messages 1-4 may include multiple fields, and Table 8 below provides the possible contents of the capability parameters.

[0145] Table 8 below provides a list of fields that may be included in messages 1-4, the length of each field, and their definitions. As shown in Table 8, messages 1-4 include the following fields: WLAN Management and Control Interface (WMCI) version number, 802.11 version number, number of frequency bands, frequency band 1 capability parameters, frequency band 2 capability parameters, ..., frequency band N capability parameters. Taking the "frequency band 1 capability parameters" field as an example, the "frequency band 1 capability parameters" field further includes the following fields: frequency band number, frequency band, number of supported service set identifiers (SSIDs), supported transmit power level, number of transmit antennas, number of receive antennas, and bandwidth. The "WMCI version number" can also be understood as the protocol version number supported by the sub-device, and the "number of frequency bands" indicates the number of fields starting from field 4, i.e., how many frequency band capability parameters are available.

[0146] Table 8

[0147]

[0148]

[0149] It should be noted that the embodiments of this application do not limit the specific content of the working parameters and the specific format of messages 1-4. Messages 1-4 may include multiple fields, and Table 9 below provides the possible contents of the working parameters.

[0150] Table 9 below provides a list of fields that may be included in messages 1-4, along with the length and definition of each field. As shown in Table 9, messages 1-4 include the following fields: frequency band number, SSID length, SSID, password length, 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, and transmit power level. The "frequency band selection" field indicates the current operating frequency band of sub-device 1, and the "channel" field indicates the current operating channel of sub-device 1.

[0151] Table 9

[0152]

[0153]

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

[0155] During the initialization phase, prior to the synchronization and time allocation phases, the master device allocates a service period for sub-device 2 to negotiate with STA2. The master device sends message 2-3 to sub-device 2, instructing sub-device 2 to negotiate STA2's wake-up time 2 (STA2 service period) with STA2 during its service period. Then, during the synchronization phase, sub-device 2 negotiates STA2's wake-up time 2 (STA2 service period) with STA2 during its service period. It should be noted that the master device allocates the service period to sub-device 2 in a similar way to the master device allocating the service period to sub-device 1 in step 107 above. Furthermore, message 2-3 has a similar format to message 1-3 in step 107; please refer to the relevant description in step 107 above for details, which will not be repeated here. Message 2-3 can also be called the TWT negotiation time message.

[0156] Optionally, before the master device sends messages 2-3 to the sub-device 2, the sub-device 2 is also used to perform step 110 to report status information to the master device, so that the master device can allocate the corresponding sub-device 2 service cycle to the sub-device 2 more specifically according to the status information reported by the sub-device 2. Step 110 is described below.

[0157] 110. Sub-device 2 sends message 2-4 to master device.

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

[0159] It should be noted that, in Figure 5 In the initialization 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.

[0160] It should be noted that, considering practical applications, some STAs support negotiating STA wake-up time with sub-devices, while others do not. STAs that support negotiating STA wake-up time with sub-devices can be called TWT users; for example, STA1 and STA2 in the above embodiment are TWT users. STAs that do not support negotiating STA wake-up time with sub-devices can be called non-TWT users. During the time allocation phase, the master device can schedule TWT users and non-TWT users separately. For example, the master device may prioritize scheduling TWT users and then schedule non-TWT users, as detailed below. Figure 5 Steps 111 and 112 in the illustrated embodiment.

[0161] 111. The main equipment scheduler is a TWT user in the STA service cycle.

[0162] Specifically, after receiving message 1-1 from sub-device 1, the master device can determine the wake-up time of STA1 (STA1 service cycle). The master device can schedule STA1 to be awake during the STA1 service cycle. Therefore, the master device sends message 1-2 to sub-device 1 to instruct sub-device 1 to allow data transmission to STA1 during the STA1 service cycle. Similarly, after receiving message 2-1 from sub-device 2, the master device can determine the wake-up time of STA2 (STA2 service cycle). The master device can schedule STA2 to be awake during the STA2 service cycle. Therefore, the master device sends message 2-2 to sub-device 2 to instruct sub-device 2 to allow data transmission to STA2 during the STA2 service cycle.

[0163] 112. Main equipment scheduling for non-TWT users.

[0164] Specifically, taking STA3 as an example of a non-TWT user, STA3 is associated with sub-device 3. When STA3 switches to wake-up state, sub-device 3 notifies the master device, and the master device then schedules STA3, which is in wake-up state. For example, the master device sends a scheduling message to sub-device 3 to instruct sub-device 3 to allow data to be sent to STA3.

[0165] Figure 7 This is a schematic diagram of the structure of the main device in one embodiment of this application. Figure 7 As shown, the main device includes a processing unit 201 and a transceiver unit 202. Specifically, the transceiver unit 202 is used to perform the above-described... Figure 4 or Figure 5 In the illustrated embodiment, the master device performs message sending and receiving operations. The processing unit 201 is used to execute the above... Figure 4 or Figure 5 In the illustrated embodiment, in addition to message sending and receiving, other operations of the master device, such as the processing unit 201 performing decision-making and message generation operations, are also included.

[0166] Figure 8 This is a schematic diagram of another structure of the main device in an embodiment of this application. For example... Figure 8 As shown, the main device includes a processor 301 and an interface 302, which are interconnected via a cable. It should be noted that the interface 302 is used to perform the aforementioned... Figure 4 or Figure 5 In the illustrated embodiment, the master device performs message sending and receiving operations. Processor 301 is used to execute the above... Figure 4 or Figure 5In the illustrated embodiment, in addition to message sending and receiving, other operations of the master device include, for example, the processor 301 can perform operations such as decision-making and message generation. In some possible implementations, the processor 301 includes the processing unit 201 described above, and the interface 302 includes the transceiver unit 202 described above. Optionally, the master device may also include a memory 303, wherein the memory 303 is used to store program instructions and data.

[0167] Figure 9 This is a schematic diagram of the structure of a sub-device in an embodiment of this application. For example... Figure 9 As shown, the sub-device includes a processing unit 401 and a transceiver unit 402. Specifically, the transceiver unit 402 is used to perform the above-described... Figure 4 or Figure 5 In the illustrated embodiment, the sub-device performs message sending and receiving operations. The processing unit 401 is used to execute the above... Figure 4 or Figure 5 The embodiments shown illustrate other operations of the sub-device besides message sending and receiving.

[0168] Figure 10 This is a schematic diagram of another structure of the sub-device in an embodiment of this application. For example... Figure 10 As shown, the sub-device includes a processor 501 and an interface 502, which are interconnected via a wire. It should be noted that the interface 502 is used to perform the above-described... Figure 4 or Figure 5 The illustrated embodiment demonstrates message sending and receiving operations performed by the sub-device. Processor 501 is used to execute the above... Figure 4 or Figure 5 The illustrated embodiment includes operations of the sub-device other than message sending and receiving. In some possible implementations, processor 501 includes the processing unit 401 described above, and interface 502 includes the transceiver unit 402 described above. Optionally, the main device may further include memory 503, wherein memory 503 is used to store program instructions and data.

[0169] This application also provides a chip. The chip integrates circuitry for implementing the functions of the processor 301 or processor 501 described above, and one or more interfaces. As an example, the chip integrates a memory. As another example, when the chip does not integrate a memory, it can be connected to an external memory via the interface. The chip can perform the method steps of any one or more of the foregoing embodiments. Alternatively, the chip can implement the actions performed by the processing and transmission device in the foregoing embodiments based on program code stored in the memory.

[0170] As an example, the chip in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor, any conventional processor, or a processing circuit that implements a specific function.

[0171] This application also provides a computer-readable storage medium including a program or instructions that, when run on a computer, cause the method performed as described in the above method embodiments to be implemented.

[0172] It should be understood that the processor mentioned in the embodiments of this application can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in 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 this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor, any conventional processor, or a processing circuit that implements a specific function.

[0174] In embodiments of this application, the memory may be random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium may reside in an ASIC. Additionally, the ASIC may reside in a network device or a terminal device. Alternatively, the processor and storage medium may exist as discrete components in the network device or terminal device.

[0175] In the above embodiments, it can be implemented entirely or partially by software, hardware, firmware, or any combination thereof.

[0176] When implemented in hardware, the methods provided in this application embodiment may be implemented without reading software code or instructions. For example, they may be implemented using a CPU, DSP, ASIC, FPGA, other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.

[0177] When implemented using software, it can be implemented entirely or partially in the form of a computer program product. A computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, all or part of the processes or functions of the embodiments of this application are performed. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable device. The computer program or instructions can be stored in or transmitted through a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a Digital Versatile Disc (DVD); or it can be a semiconductor medium, such as a solid-state disk (SSD).

[0178] Finally, it should be noted that the above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A service scheduling method, characterized in that, include: The master device receives a STA target wake-up time (TWT) negotiation time reporting message sent by the sub-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 master device schedules the STAs that are in the STA service cycle or in the wake-up state.

2. The method according to claim 1, characterized in that, Before the master device receives the STA TWT negotiation time reporting message sent by the slave device, the method further includes: The master device allocates a service period to the sub-device by sending a TWT negotiation time message. 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 master device allocates a service period to the sub-device by sending a TWT negotiation time message to the sub-device, the method further includes: The master device receives status information sent by the sub-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, The STAs that the master device schedules during the STA service cycle or in a wake-up state include: The master device sends a scheduling message to the slave device.

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

12. 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.

13. 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.

14. A main device, characterized in that, The main equipment includes a transceiver unit and a processing unit; The transceiver unit is used to: receive a STA target wake-up time (TWT) negotiation time reporting message sent by the sub-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 processing unit is used to schedule the STA that is in the STA service cycle or in the wake-up state.

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

16. The device according to claim 15, characterized in that, Before allocating a service period for the sub-device by sending the TWT negotiation time message to the sub-device, the transceiver unit is further configured to: receive status information sent by the sub-device, the status information being used to support the master device in performing global wake-up time allocation.

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

18. The device according to claim 16, 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.

19. The device according to any one of claims 14-18, 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.

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

21. The 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 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 device according to any one of claims 15-18, characterized in that, The STA service period is within the time range of the sub-device service period.

24. The device according to any one of claims 14-18, characterized in that, The transceiver unit is also used to: receive scheduling messages sent by the master device.

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

26. The device according to any one of claims 14-18, characterized in that, The main device is an MFU, and the sub-device is an SFU.

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

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

29. A chip, characterized in that, The chip includes a processor and an interface, the processor being configured to perform the method as described in any one of claims 1 to 13.

Images