Service scheduling method, device and system

Abstract

The embodiment of the invention discloses a service scheduling method, device and system. The sub-device will negotiate a power saving time and a wake-up time for the STA with the associated STA, i.e. When the STA is in a power saving state and when to handle a wake-up state. And then, the sub-device reports the negotiated wake-up time of the STA to the master device. And further, the master device schedules related data of the STA according to the wake-up time of the STA. Thus, before performing service scheduling on each STA, the master device can acquire the STA wake-up time negotiated by each sub-device and the associated STA in advance, and does not need to frequently interact with each sub-device to acquire the real-time state of each STA. The master device can more efficiently perform service scheduling on each STA at a proper time by centrally managing and controlling the wake-up time of each STA.

Description

[0001] This application is a divisional application. The application number of the original application is 202510039218.6, and the original application date is January 9, 2025. The entire content of the original application is incorporated into this application by reference. Technical Field

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

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

[0004] In traditional energy-saving solutions, when a station (STA) enters an energy-saving state, it sends a message to a slave device to instruct it to do so. While in this state, the STA cannot receive data, but can receive data while awake. The master device needs to frequently interact with the slave device to confirm whether the STA is currently in this state, allowing it to schedule services at the appropriate time. However, this frequent interaction between the master and slave devices results in a high implementation cost. Summary of the Invention

[0005] The embodiments of the present application provide a service scheduling method, apparatus, and system. Before a master device schedules services for each STA, it can obtain in advance the STA wake-up time agreed upon by each sub-device and the associated STA, without the need to frequently interact with each sub-device to obtain the real-time status of each STA. By centrally controlling the wake-up time of each STA, the master device can more efficiently schedule services for each STA at the appropriate time.

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

[0007] In this implementation, the sub-device negotiates with the associated STA about the STA's energy-saving and wake-up times—that is, when the STA is in an energy-saving state and when it wakes up. The sub-device then reports the negotiated STA wake-up time to the master device. The master device then schedules the STA's data based on the STA's wake-up time. This allows the master device to know the STA wake-up time agreed upon between each sub-device and its associated STA before scheduling services for each STA. This eliminates the need for frequent interaction with each sub-device to learn about each STA's real-time status. By centrally managing each STA's wake-up time, 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 allocates a sub-device service period to the sub-device by sending a TWT negotiation time message to the sub-device, and 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 wake-up time of the STA during the sub-device service period. In this implementation, the master device will comprehensively consider various factors and centrally allocate a time period for negotiation to each sub-device. The allocation method is more reasonable and targeted, which is conducive to improving the efficiency and success rate of the negotiation of each sub-device.

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

[0010] In some possible implementations, the status information includes interference measurement information, which includes at least one of an identifier of the interfering device, an operating mode of the interfering device, an operating bandwidth of the interfering device, an operating channel of the interfering device, strength of a signal transmitted by the interfering device, and a device type of the interfering device. Based on the interference measurement information, the master device allocates a sub-device service period for negotiation to the sub-device to avoid interference, thereby ensuring that negotiation between the sub-device and the STA is not interfered with.

[0011] In some possible implementations, the status information includes at least one of the capability parameters and operating 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. The operating parameters of the sub-device include at least one of the operating frequency band of the sub-device, the operating channel of the sub-device, the operating channel bandwidth of the sub-device, and the transmit power level of the sub-device. The master device will allocate a sub-device service period for negotiation to the sub-device in a more targeted manner based on multiple considerations based on at least one of the capability parameters and the operating parameters, so that the sub-device can negotiate with the STA at a more appropriate time period.

[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 time and end time of the sub-device service period, so that the sub-device can quickly determine the sub-device service period for negotiation directly based on the content carried by 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 cycle. Alternatively, the TWT negotiation time message also includes the start time and end time of the global TWT cycle. The global TWT cycle includes the sub-device service period assigned by the master device to all sub-devices. In this implementation, the master device formulates a global TWT cycle and provides a sub-device service period corresponding to each sub-device within each global TWT cycle, so that each sub-device can be allocated a corresponding sub-device service period within a global TWT cycle, which is conducive to balancing the negotiation and service transmission between each sub-device and the associated STA.

[0014] In some possible implementations, the STA service period falls within the time range of the slave device service period. That is, the STA service period negotiated between the slave device and the STA, when the STA is in the awake state, falls within the time range of the negotiated slave device service period. In this way, by assigning completely different slave device service periods to different slave devices, the master device avoids interference between the negotiation processes of different slave 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 identifier, the start time and duration of the STA service period. Alternatively, the STA TWT negotiation time reporting message includes the STA identifier, the start time and end time of the STA service period. The start time of the STA service period is also the STA wake-up start time, the end time of the STA service period is also the STA wake-up end time, and the duration of the STA service period is also the STA wake-up duration. This allows the master device to quickly determine the STA wake-up time directly based on the content carried in the STA TWT negotiation time reporting message.

[0016] In some possible implementations, scheduling a STA during a STA service period or in an awake state by a master device includes: the master device sending a scheduling message to a slave device, the scheduling message being used to instruct the slave device to allow data transmission to the STA during the STA service period. This allows the STA to receive data sent by the slave device while in an awake state, thereby ensuring normal service scheduling and reception.

[0017] On the second aspect, an embodiment of the present application provides a service scheduling method, which can be applied to FTTR scenarios. In the FTTR system, the main device is also called MFU, and the sub-device is also called SFU. The service scheduling method is executed by the sub-device. Specifically, the sub-device negotiates with the STA to determine the wake-up time of the STA. After the sub-device successfully negotiates the wake-up time of the STA with the STA, the sub-device sends a STA TWT negotiation time reporting message to the main device, and the STA TWT negotiation time reporting message is used to indicate the negotiation result between the sub-device and the STA. Among them, the STA that is in the STA service period or in the awake state is scheduled by the main device.

[0018] In some possible implementations, before the sub-device sends the STA TWT negotiation time reporting message to the main device, the method also includes: the sub-device receives the TWT negotiation time message sent by the main device, the TWT negotiation time message is used to allocate a sub-device service period to the sub-device, and the sub-device service period is 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 main device, the method further includes: the sub-device sends status information to the main device, where the status information is used to support the main device in executing global wake-up time allocation.

[0020] In some possible implementations, the status information includes interference measurement information, and the interference measurement information includes at least one of an identification of the interfering device, an operating mode of the interfering device, an operating bandwidth of the interfering device, an operating channel of the interfering device, the strength of a signal sent by the interfering device, and a device type of the interfering device.

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

[0022] 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 time and end time of the sub-device service period.

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

[0024] In some possible implementations, the STA service period is within the time range 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 cycle, or the STA TWT negotiation time reporting message includes the STA identifier, the start time and end time of the STA service cycle.

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

[0027] In a third aspect, an embodiment of the present application provides a master device, which can be an MFU in an FTTR system. The master device includes a transceiver unit and a processing unit. The transceiver unit is used to: when the sub-device successfully negotiates the STA's wake-up time with the STA, receive the STA TWT negotiation time reporting message sent by the sub-device, and 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 the STA that is in the STA service period or in the awake state.

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

[0029] In some possible implementations, before allocating a sub-device service period to the sub-device by sending a TWT negotiation time message to the sub-device, the transceiver unit is further used to: receive status information sent by the sub-device, where the status information is used to support the main device to perform global wake-up time allocation.

[0030] In some possible implementations, the status information includes interference measurement information, and the interference measurement information includes at least one of an identification of the interfering device, an operating mode of the interfering device, an operating bandwidth of the interfering device, an operating channel of the interfering device, the strength of a signal sent by the interfering device, and a device type of the interfering device.

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

[0032] 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 time and end time of the sub-device service period.

[0033] 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 also includes the start time and end time of the global TWT period. The global TWT period includes the sub-device service period assigned by the master device to all sub-devices.

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

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

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

[0037] Fourthly, embodiments of the present application provide a sub-device, which may be an SFU in an FTTR system. The sub-device includes a transceiver unit and a processing unit. The processing unit is configured to negotiate with the STA the STA's wake-up time. The transceiver unit is configured to send a STA TWT negotiation time report message to the master device after the sub-device successfully negotiates the STA's wake-up time with the STA. The STATWT negotiation time report message indicates the negotiation result between the sub-device and the STA. The STA in the STA service period or in the awake 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 is used to allocate a sub-device service period to the sub-device, and the sub-device service period is 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 further used to: send status information to the master device, where the status information is used to support the master device in executing global wake-up time allocation.

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

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

[0042] 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 time and end time of the sub-device service period.

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

[0044] In some possible implementations, the STA service period is within the time range 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 cycle, or the STA TWT negotiation time reporting message includes the STA identifier, the start time and end time of the STA service cycle.

[0046] In some possible implementations, the transceiver unit is further configured to: receive a scheduling message sent by the master device, where the scheduling message is used to instruct the slave device to allow sending data to the STA during the STA service period.

[0047] In a fifth aspect, an embodiment of the present application provides a main device, which includes instructions. When the instructions are executed by the main device, the main device executes the method described in any implementation method of the first aspect.

[0048] In a sixth aspect, an embodiment of the present application provides a sub-device, which includes instructions. When the instructions are executed by the sub-device, the sub-device executes the method described in any implementation method of the second aspect.

[0049] In a seventh aspect, an embodiment of the present application provides a main device, which includes a processor and an interface, the interface is used to send and receive signals, and the processor is used to execute the method described in any implementation method of the first aspect.

[0050] In an eighth aspect, an embodiment of the present application provides a sub-device, which includes a processor and an interface, the interface is used to send and receive signals, and the processor is used to execute the method described in any implementation method of the second aspect.

[0051] In the ninth aspect, an embodiment of the present application provides a communication system, which includes a main 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, and the main device communicates with the at least one sub-device.

[0052] In the tenth aspect, an embodiment of the present application provides a chip, which is used to execute the method described in any implementation method of the first aspect or the second aspect.

[0053] In the eleventh aspect, the present application provides a computer-readable storage medium having instructions stored thereon. When the instructions are executed by a computer, the method described in any embodiment of the first aspect or the second aspect is implemented.

[0054] In a twelfth aspect, the present application provides a computer program product, which includes program instructions. When the computer program product is executed, it is used to implement the method introduced in any embodiment of the first or second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 This is a schematic diagram of a possible WLAN network architecture according to an embodiment of the present 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 the service scheduling method provided in an embodiment of the present application;

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

[0060] Figure 6 This is a schematic diagram of a master device allocating a sub-device service period to each sub-device in an embodiment of the present application;

[0061] Figure 7 This is a structural diagram of a main device in an embodiment of the present application;

[0062] Figure 8 This is another structural diagram of the main device in the embodiment of the present application;

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

[0064] Figure 10 This is another structural diagram of the sub-device in the embodiment of the present application. DETAILED DESCRIPTION

[0065] Embodiments of the present application provide a service scheduling method, apparatus, and system applicable to fiber-to-the-room (FTTR) scenarios. Before scheduling services for each STA, a master device can pre-determine the STA wake-up time agreed upon between each slave device and its associated STA, eliminating the need for frequent interaction with each slave device to obtain the real-time status of each STA. By centrally managing each STA's wake-up time, the master device can more efficiently schedule services for each STA at the appropriate time.

[0066] It should be understood that “one embodiment”, “one implementation”, “one implementation method” or “one example” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, “in one embodiment”, “an implementation method”, “one implementation method” or “in an example” appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the 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 the present application.

[0067] Additionally, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " herein generally indicates that the associated objects are in 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 that 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. Furthermore, unless otherwise indicated, ordinal numbers such as "first" and "second" in the embodiments of this application are used to distinguish between multiple objects and are not intended to limit the order, timing, priority, or importance of multiple objects. Furthermore, the terms "including" and "having" in the embodiments of this application, the claims, and the accompanying drawings 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 that are not listed.

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

[0069] Terminal devices may include mobile phones (or "cellular" phones), computers with mobile terminal devices, portable, pocket-sized, handheld, or computer-built mobile devices, etc. For example, 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 may also be computers, tablet computers, e-readers, etc., or smart home devices such as smart TVs and smart speakers. As an example and not a limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices or smart wearable devices, etc., which are a general term for wearable devices that are intelligently designed and developed using wearable technology for everyday wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets for vital sign monitoring, smart helmets, smart jewelry, etc.

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

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

[0072] Building on FTTH / O, to address signal coverage issues within home or office networks (such as wireless local area network (WLAN) signals), optical fiber can be extended further into the home. Optical terminals providing WLAN signals are installed inside the home, shortening the distance between the user terminal and the wireless access point (AP) and improving signal quality. This technology is known as fiber to the room (FTTR).

[0073] Figure 3 This is a diagram of the FTTR system architecture. The OLT in FTTH / O is deployed in a central equipment room, while the ONT is deployed in homes or offices. The master device in the FTTR network serves as both the ONT in the FTTH network and the upstream device for the FTTR sub-devices, managing them. Sub-devices in the FTTR can be deployed in various rooms in a home or office, providing signals to user terminals. Sub-devices have both ONT and wireless access point functions.

[0074] Multiple sub-devices can be deployed in an FTTR, each connected to a master device via an optical splitter. The master device centrally manages and configures all sub-devices. The master device can also be called the "master gateway," "master optical modem," or "Main FTTR Unit (MFU)." Sub-devices can also be called "slave gateway," "slave optical modem," or "sub-FTTR Unit (SFU)."

[0075] It should be noted that the present 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 the multiple sub-devices. Figure 2In the FTTH / O scenario shown in FIG, the master device may be an OLT and the slave device may be an ONU. 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 the embodiment of the present application, the master device can obtain in advance the STA wake-up time agreed upon by each slave device and the associated STA before scheduling services for each STA, without the need to frequently interact with each slave device to obtain the real-time status of each STA. By centrally controlling 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 describes in detail the service scheduling method for FTTR provided by the embodiments of the present application in conjunction with the accompanying drawings. It should be noted that the embodiments of the present application do not limit the number of sub-devices that communicate with the main device. The following embodiments only use the main device interacting with two sub-devices as an example. These two sub-devices are respectively denoted as sub-device 1 and sub-device 2. The interaction between more sub-devices and the main device is similar.

[0077] Figure 4 A flowchart of a service scheduling method provided in an embodiment of the present application. The specific process of the service scheduling method is described in detail below. It should be noted that the interaction between the master device and the sub-device regarding service scheduling may include multiple stages, for example, 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, during the synchronization stage, the sub-device negotiates with the STA for the STA's wake-up time and reports the negotiation results to the master device. During the time assignment stage, the master device allocates time for service scheduling based on the negotiation results reported by each sub-device, so that each sub-device sends data to the STA during the time period scheduled by the master device. Optionally, during the initialization stage, the master device allocates a time period (SFU service period) for negotiation to each sub-device based on status information such as interference measurement information, capability parameters, and / or operating parameters reported by each sub-device, so that during the synchronization stage, each sub-device negotiates with the STA for the STA's wake-up time according to the time period allocated by the master device. The following first describes the interaction processes between the master device and sub-device 1 and sub-device 2 during the synchronization stage and the time assignment stage, respectively.

[0078] 101. Slave device 1 negotiates with STA1 about the wake-up time of STA1.

[0079] It should be noted that the working state of STA can be divided into energy-saving state and awake state. STA can send and receive data normally in the awake state, and will suspend data sending and receiving when switching to the energy-saving state. Among them, the time when STA is in the energy-saving state can be called energy-saving time, and the time when STA is in the awake state can be called wake-up time or STA service cycle. In order to improve the energy-saving efficiency of STA, a target wake time (TWT) energy-saving mechanism is defined, that is, the sub-device and STA can negotiate the energy-saving time and wake-up time of STA. In the embodiment of the present application, in the synchronization phase, sub-device 1 can be associated with at least one STA including STA1. Among the STAs associated with sub-device 1, there may be STAs that support negotiation and there may be STAs that do not support negotiation. Taking STA1 supporting negotiation with sub-device 1 as an example, sub-device 1 negotiates with STA1 about STA1's wake-up time and energy-saving time. If the negotiation is successful, sub-device 1 can know STA1's wake-up time and energy-saving time in advance, which is equivalent to sub-device 1 knowing in advance when STA1 is in the awake state and when it is in the energy-saving state. For a STA that does not support negotiation with the sub-device 1, the STA will notify the sub-device 1 only when it switches between the energy-saving state and the awake state. The sub-device 1 cannot know the awakening time and energy-saving time of the STA in advance.

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

[0081] During the synchronization phase, after the sub-device 1 negotiates with STA1 on the wake-up time and energy-saving time of STA1, the sub-device 1 sends a message 1-1 to the master device. The message 1-1 is used to indicate the wake-up time 1 of STA1, where the wake-up time 1 of STA1 can also be understood as the period 1 when STA1 is in the awake state. The wake-up time 1 of STA1 is also called the STA1 service period. It should be understood that, considering that the master device knows the wake-up time 1 of STA1 in order to schedule services for STA1 at the wake-up time 1, the sub-device 1 needs to report the wake-up time 1 of STA1 to the master device through the message 1-1. As for whether the energy-saving time 1 of STA1 needs to be reported to the master device, there is no restriction. The message 1-1 can also be called the STA TWT negotiation time reporting message.

[0082] It should be noted that the embodiment of the present application does not limit the specific format of message 1-1, and message 1-1 may include multiple fields.

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

[0084] Table 1

[0085] Field Name Field length Field Description STA logo 6 STA logo BSSID of the child device 6 BSSID used by the slave device to negotiate the wake-up time with the STA Start time of the STA service period 4 Indicates the start time of the STA service period within the TWT period STA service cycle duration 4 Indicates the duration of the STA service period within the TWT period, in us

[0086] Table 2 below provides another example of fields that may be included in message 1-1, along with the length and definition of each field. The STA in Table 2 below may be STA1, and the sub-device in Table 2 below may 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. The start time and end time of the STA service period are equivalent to knowing the duration of the STA service period, which is equivalent to indicating the STA's wake-up time through the start time and end time of the STA service period.

[0087] Table 2

[0088] Field Name Field length Field Description STA logo 6 STA logo BSSID of the child device 6 BSSID used by the slave device to negotiate the wake-up time with the STA Start time of the STA service period 4 Indicates the start time of the STA service period within the TWT period End time of the STA service period 4 Indicates the end time of the STA service period within the TWT period

[0089] As an example, the "start time of the STA service period" in Table 1 and Table 2 may be the absolute time of the wake-up start time negotiated between STA1 and sub-device 1. As another example, the "start time of the STA service period" in Table 1 and Table 2 may also be a relative time relative to the start time of the global TWT period, and the unit of the relative time may be us.

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

[0091] It should be noted that in some possible scenarios, message 1-1 may also carry only 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 only includes the STA identifier and the start time of the STA service period, which is equivalent to indicating the wake-up start time of the STA, and is sufficient to provide the master device with valid reference information to schedule services at the appropriate time. For another example, message 1-1 only includes the STA identifier and the duration of the STA service period, which is equivalent to indicating the wake-up duration of the STA, and is sufficient to provide the master device with valid reference information to schedule services 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. The same applies to the formats of other messages transmitted between the master device and the slave device. In other words, each table provided in the embodiment of the present application is only some possible examples, and those skilled in the art can flexibly transform them on this basis. For example, the byte length of each field in the table can be changed. For another example, the indication content corresponding to the value of each field can also be changed. Taking the fields in Table 1 as an example, the length of each field can be flexibly set; alternatively, the length of each field can also be measured in bits.

[0093] 103. Slave device 2 negotiates with STA2 about the wake-up time of STA2.

[0094] During the synchronization phase, sub-device 2 can associate with at least one STA, including STA2. Some of these STAs may support negotiation, while others may not. For example, if STA2 supports negotiation with sub-device 2, sub-device 2 negotiates with STA2 for STA2's wake-up time and power-saving time. If the negotiation is successful, sub-device 2 will know STA2's wake-up time and power-saving time in advance. This means that sub-device 2 can know in advance when STA2 is awake and in power-saving states. For STAs that do not support negotiation with sub-device 2, the STA will notify sub-device 2 only when it switches between power-saving and awake states. Sub-device 2 cannot know the STA's wake-up time and power-saving time in advance.

[0095] It should be noted that the embodiments of the present application do not limit whether the wake-up time negotiated by STA1 and STA2 are identical. For example, the wake-up time negotiated by STA1 and STA2 can be identical; in another example, the wake-up time negotiated by STA1 and STA2 can be completely different; or in 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 identical depends primarily 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 identical or partially overlap, which helps improve 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 do 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 scheduled by the master device for STA1 and STA2 do not interfere with each other during transmission.

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

[0097] In the synchronization phase, after the sub-device 2 negotiates with STA2 on the wake-up time and energy-saving time of STA2, the sub-device 2 sends a message 2-1 to the master device. The message 2-1 is used to indicate the wake-up time 2 of STA2, wherein the wake-up time 2 of STA2 can also be understood as the period 2 when STA2 is in the awake state. The wake-up time 2 of STA2 is also called the STA2 service cycle. It should be understood that, considering that the master device knows the wake-up time 2 of STA2 in order to schedule services for STA2 at the wake-up time 2, the sub-device 2 needs to report the wake-up time 2 of STA2 to the master device through the message 2-1. As for whether the energy-saving time 2 of STA2 needs to be reported to the master device, there is no restriction. 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 the above-mentioned message 1-1. For details, please refer to the above-mentioned introduction to the format of message 1-1, which will not be repeated here.

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

[0099] After the master device receives message 1-1 sent by sub-device 1, it can learn STA1's wake-up time 1, and then 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 indicate that sub-device 1 is allowed to send data to STA1 at STA1's wake-up time 1 (STA1 service cycle). Message 1-2 can also be called a scheduling message. Among them, the master device can send the data that needs to be transmitted to STA1 to sub-device 1 in advance. After receiving message 1-2, sub-device 1 obtains permission to send data to STA1. Sub-device 1 can then choose whether to send the data to STA1 based on actual conditions. For example, if the channel of sub-device 1 is idle, data can be sent to STA1 immediately. For another example, if the channel of sub-device 1 is busy, it is necessary to wait until the channel is idle before sending data to STA1.

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

[0101] In one possible implementation manner 1, the master device may send message 1-2 to slave device 1 in advance before STA1's wake-up time 1 arrives, and use fields defined in message 1-2 to indicate that slave device 1 is allowed to send data to STA1 at STA1's wake-up time 1. In another possible implementation manner 2, the master device sends message 1-2 to slave device 1 when STA1's wake-up time 1 arrives, and use message 1-2 to indicate that slave device 1 is allowed to send data to STA1 at STA1's wake-up time 1.

[0102] It should be noted that the embodiment of the present application does not limit the specific format of message 1-2, and message 1-2 may include multiple fields.

[0103] Table 3 below provides a list of fields that may be included in Message 1-2, along with the length and definition of each field. 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 STA MAC Addresses, STA MAC Address, and Priority.

[0104] It should be noted that the "delay time" field in message 1-2 indicates the delay time of the time when the scheduling control takes effect relative to the time when message 1-2 is received. For example, in the above-mentioned embodiment 1, the master device sends message 1-2 to sub-device 1 in advance before the wake-up time 1 of STA1 arrives, and the "delay time" field in message 1-2 indicates how long after the sub-device 1 receives the message 1-2, it is allowed to send data to STA1. For another example, in the above-mentioned embodiment 2, the master device sends message 1-2 to sub-device 1 when the wake-up time 1 of STA1 arrives, and the "delay time" field in message 1-2 indicates that the sub-device 1 is allowed to send data to STA1 immediately after receiving the 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 when the wake-up time 1 of STA1 arrives.

[0105] It should also be noted that the specific duration indicated by the "Content 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 "Content Window Duration" field in message 1-2 should be within the duration of STA1's wake-up time 1 to ensure that STA1 receives data in the awake state. For example, if the "Scheduling Type" field in message 1-2 indicates that one-time contention is allowed, then sub-device 1 can decide the duration of sending data to STA1 based on STA1's wake-up time 1. For another example, if the "Scheduling Type" field in message 1-2 indicates that air interface contention is allowed within a specific period of time, then sub-device 1 can send data to STA1 based on the specific duration indicated by the "Content 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 slave 2, the master device learns STA1's wake-up time 2. It can then schedule STA2's data according to STA2's wake-up time 2 during the time allocation phase. Specifically, the master device can send message 2-2 to slave 2, indicating that slave 2 is permitted to send data to STA2 during STA2's wake-up time 2 (STA2's service period). Message 2-2 is also called a scheduling message. The master device can pre-send data to slave 2 to ensure that slave 2 receives permission to send data to STA2. Sub-device 2 can then choose whether to send the data to STA2 based on the actual situation. For example, if slave 2's channel is idle, it can immediately send data to STA2. Alternatively, if its channel is busy, it may wait until the channel is 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. For details, please refer to the above description of the format of message 1-2 and will not be repeated here.

[0110] It should be noted that in Figure 4 In the synchronization phase or time allocation phase of the illustrated embodiment, there is no clear timing relationship between the interaction process between the master device and sub-device 1 and the interaction process between the master device and sub-device 2. For example, the interaction process between the master device and sub-device 1 may be executed first, or the interaction process between the master device and sub-device 2 may be executed first, or the interaction process between the master device and sub-device 1 and the interaction process between the master device and sub-device 2 may 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 may also allocate a time period (sub-device 1 service period) for sub-device 1 to negotiate with STA1, and a time period (sub-device 2 service period) for sub-device 2 to negotiate with STA2. This allows sub-device 1 to negotiate STA1's wake-up time with STA1 according to the time period allocated by the master device during the synchronization phase, and allows sub-device 2 to negotiate STA2's wake-up time with STA2 according to the time period allocated by the master device during the synchronization phase. The master device will comprehensively consider various factors and centrally allocate time periods for negotiation to each sub-device. This allocation method is more reasonable and targeted, which helps avoid mutual interference between the negotiations of each sub-device and also helps improve the efficiency and success rate of the negotiations of each sub-device. The relevant content of the initialization phase is introduced in detail below.

[0112] Figure 5 Another flow chart of the service scheduling method provided in the embodiment of the present application. Figure 5 As shown, the service scheduling method provided in the embodiment of the present application also includes the following steps.

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

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

[0115] Figure 6 Schematic diagram of the master device allocating a sub-device service period to each sub-device in the embodiment of the present application. Figure 6 As shown, the start time of the global TWT cycle refers to the delay time from the sub-device receiving the message to the global TWT cycle; 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 used by the sub-device to negotiate the TWT service cycle with the STA within the TWT cycle; 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; the STA service cycle duration refers to the wake-up time negotiated between the STA associated with the sub-device and the sub-device.

[0116] In one possible implementation, the master device establishes a global TWT cycle and assigns a corresponding sub-device service cycle to each sub-device, including sub-device 1 and sub-device 2, within each global TWT cycle. This allows each sub-device to be assigned a corresponding sub-device service cycle within a global TWT cycle, which is beneficial for balancing the negotiation and service transmission between each sub-device and the 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] The embodiments of the present application do not limit the specific allocation method of the service periods of each sub-device within the global TWT period. Taking the service period of sub-device 1 and the service period of sub-device 2 as an example, the service period of sub-device 1 and the service period of sub-device 2 can be two completely different sub-device service periods, or the service period of sub-device 1 and the service period of sub-device 2 can also partially overlap or completely overlap. As an example, the main device allocates corresponding sub-device service periods to each sub-device in an evenly distributed manner, that is, the duration of the sub-device service periods corresponding to each sub-device is the same, and the sub-device service periods corresponding to each sub-device are staggered in time. As another example, the main device receives status information reported by each sub-device, and the main device allocates corresponding sub-device service periods to each sub-device in a targeted manner based on the reported status information. This will be introduced below with reference to specific examples.

[0118] In a possible scenario, taking sub-device 1 and sub-device 2 as an example, the interaction between sub-device 1 and STA1 and the interaction between sub-device 2 and STA2 constitute mutual interference. Figure 6 As shown, the service period assigned by the master device to sub-device 1 and sub-device 2 can be completely different sub-device service periods. Furthermore, STA1's wake-up time 1 (STA1 service period) is within the range of sub-device 1's service period, and STA2's wake-up time 2 (STA2 service period) is within the range of sub-device 2's service period. In this way, by assigning completely different sub-device service periods to sub-device 1 and sub-device 2, the master device avoids interference between the negotiation process between sub-device 1 and STA1, and between sub-device 2 and STA2, and also avoids interference between the service transmission process between sub-device 1 and STA1, and between sub-device 2 and STA2.

[0119] It should be noted that the embodiment of the present application does not limit the specific format of messages 1-3, and messages 1-3 may include multiple fields.

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

[0121] Table 4

[0122] Field Name Field length Field Description The start time of the sub-device service cycle 4 Indicates the start time of the sub-device service cycle The duration of the sub-device service cycle 4 Indicates the duration of the sub-device service cycle, in us

[0123] Table 5 below provides another example of fields that may be included in messages 1-3, along with the length and definition of each field. The sub-device in Table 5 may be sub-device 1. As shown in Table 5, message 1-3 includes the start time and end time of sub-device 1's service period. Knowing the start and end times of sub-device 1's service period is equivalent to knowing the duration of sub-device 1's service period, effectively indicating the sub-device 1 service period using the start and end times of sub-device 1's service period.

[0124] Table 5

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

[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 specifically be the absolute time of the start time of the sub-device service period. As another example, the start time of the sub-device service period can also be a relative time relative to the start time of the global TWT period, and the unit of the relative time can be us. Table 6 below provides another type of fields that may be included in message 1-3 based on Table 4, the length and definition of each field, and 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 (Start time of global TWT period) and the duration of the global TWT period (Cycle time ofglobal TWT period), and the global TWT period is indicated by the start time of the global TWT period and the duration of the global TWT period. 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 of the global TWT cycle and the end time of the global TWT cycle, which is equivalent to indicating the global TWT cycle by the start time of the global TWT cycle and the end time of the global TWT cycle. The corresponding table display is no longer provided here.

[0127] Table 6

[0128]

[0129] As an example, the "start time of the global TWT cycle" in Table 6 can be the absolute time of the start time of the global TWT cycle. As another example, the "start time of the global TWT cycle" in Table 6 can also be the delayed time relative to the time when messages 1-3 are received. In other words, the time point that is delayed for a period of time after the sub-device 1 receives messages 1-3 is the start time of the global TWT cycle. The "start time of the global TWT cycle" field can also be called the "delayed effective time field", which is used to indicate the time when messages 1-3 are delayed to take effect on sub-device 1. The unit can be us. If the field value is all FF, it means that it takes effect immediately.

[0130] It should be noted that the above-mentioned 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 all refer to specific time points or moments, not time periods.

[0131] In some possible scenarios, messages 1-3 may also carry only some of the fields shown in Table 4, Table 5 or Table 6. The specific fields carried depend on the actual application scenario and are not limited here. For example, messages 1-3 only include the start time of the sub-device service cycle, which is equivalent to indicating the start time of the negotiation between the sub-device and the STA, and is sufficient to provide the sub-device with valid reference information to negotiate at the appropriate time. For another example, messages 1-3 only include the duration of the sub-device service cycle, which is equivalent to indicating the duration of the negotiation between the sub-device and the STA, and is sufficient to provide the sub-device with valid reference information to negotiate at the appropriate time. For another example, messages 1-3 only include the start time of the global TWT cycle and the duration of the global TWT cycle, which is equivalent to indicating the time when all sub-devices can negotiate with the STA, so that each sub-device can negotiate within the specified time, which is conducive to taking into account the negotiation between each sub-device and the associated STA.

[0132] Optionally, before the main device sends message 1-3 to sub-device 1, sub-device 1 is also used to execute step 108 to report status information to the main device, so that the main device can more specifically allocate the corresponding sub-device 1 service period to sub-device 1 based on the status information reported by sub-device 1. Step 108 is introduced below.

[0133] 108. Slave device 1 sends message 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 an interfering device interfering with sub-device 1. The master device then allocates a sub-device 1 service period to sub-device 1 based on the interference measurement information. It should be noted that the interfering device interfering with sub-device 1 can be another sub-device or a STA, and the specifics are not limited here. The interference measurement information of the interfering device interfering with sub-device 1 primarily reflects which devices may interfere with sub-device 1. The master device allocates a sub-device 1 service period to sub-device 1 with the goal of avoiding interference. For example, if sub-device 2 is an interfering device interfering with sub-device 1, and the master device learns from messages 1-4 that sub-device 2 is interfering with sub-device 1, the sub-device 1 service period and the sub-device 2 service period allocated by the master device to sub-device 1 are completely different. During 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 embodiment of the present application does 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 the fields that may be included in messages 1-4, along with the length and definition of each field. 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 result field further includes the following fields: MAC address of the measured device, MAC address of the measuring device, operating bandwidth of the measured device, operating mode of the measured device, operating channel of the measured device, interference signal strength, type of the measured device, and signal-to-noise ratio (SNR) on the receiving side. It should be understood that the "measured device" in Table 7 is the interfering device, and the information associated with the "measured device" is information about the interfering device. The "MAC address of the measured device" is an identifier of the measured device, and may also be identified by other means such as the "AID of the measured device," which is not limited here. For example, based on the MAC address of the measured device 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. The same applies to the formats 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 some possible examples, and those skilled in the art can flexibly transform them based on this. For example, the byte length of each field in the table can be changed. For another example, the indication content corresponding to the value of each field can also be changed. Taking the "Type of Measured Device" in Table 7 as an example, the indication contents corresponding to the values of 0 and 1 of the "Type of Measured Device" may be swapped; alternatively, any other value may be used to indicate the above contents; alternatively, the field length of the "Type of Measured Device" may be multiple bytes; alternatively, the field length of the "Type of Measured Device" may be measured in bits, and the field length of the type of interfering device "Type of Measured Device" may be 1 bit or multiple bits. Taking the example of the field length of "Type of Measured Device" including 1 bit, a bit value of 0 indicates that the measured device is an AP, and a bit value of 1 indicates that the measured device is an STA, or a bit value of 0 indicates that the measured device is an STA, and a bit value of 1 indicates that the measured device is an AP.

[0141] In another possible scenario, messages 1-4 sent by sub-device 1 to the master device include at least one of sub-device 1's capability parameters and operating parameters. The master device then assigns a service period to sub-device 1 based on at least one of the capability parameters and operating parameters of sub-device 1. It should be noted that the capability parameters of sub-device 1 indicate the capabilities supported or possessed by sub-device 1, while the operating parameters of sub-device 1 indicate the parameters of sub-device 1 in its actual operating state. Depending on the actual situation, the operating parameters of sub-device 1 may be the same as the capability parameters of sub-device 1, or may be different from the capability parameters of sub-device 1.

[0142] As an example, the master device may determine the duration of the sub-device 1 service period assigned to sub-device 1 based on at least one of the capability parameters and operating parameters of sub-device 1. For example, if sub-device 1 has a higher transmit power level or a larger number of antennas, the duration of the sub-device 1 service period assigned to sub-device 1 may also be longer; conversely, if sub-device 1 has a higher transmit power level or a smaller number of antennas, the duration of the sub-device 1 service period assigned to sub-device 1 may also be shorter.

[0143] As another example, the master device may determine whether mutual interference occurs between sub-devices based on at least one of the capability parameters and operating parameters reported by each device, so as to allocate a sub-device service period to each sub-device to avoid interference. For example, the master device may determine whether mutual interference occurs between sub-devices based on the frequency band reported by each sub-device.

[0144] It should be noted that the embodiment of the present application does not limit the specific content of the capability parameters and the specific format of messages 1-4. Messages 1-4 may include multiple fields. Table 8 below provides the content that the capability parameters may include.

[0145] Table 8 below provides the fields that may be included in a message 1-4, the length and definition of each field. 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 parameter, frequency band 2 capability parameter, ..., frequency band N capability parameter. Taking the "frequency band 1 capability parameter" field as an example, the "frequency band 1 capability parameter" field further includes the following fields: frequency band sequence number, frequency band, number of supported service set identifiers (SSIDs), supported transmit power level, number of transmitting antennas, number of receiving antennas, and bandwidth. Among them, the "WMCI version number" can also be understood as the protocol version number supported by the sub-device, and the "number of frequency bands" is used to indicate the number of fields starting from field 4, that is, the number of frequency band capability parameters.

[0146] Table 8

[0147]

[0148]

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

[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: Band Number, SSID Length, SSID, Password Length, Password, Encryption Mode, Authentication Mode, WPA Encryption Mode, WPA Authentication Mode, IEEE11i Encryption Mode, IEEE11i Authentication Mode, Band Selection, Channel, Channel Width, and Transmit Power Level. The "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 slave device 2.

[0155] In the initialization phase before the synchronization phase and the time allocation phase, the master device allocates a sub-device 2 service period for negotiating with STA2 to sub-device 2, and the master device sends a message 2-3 to sub-device 2, which is used to instruct sub-device 2 to negotiate with STA2 for STA2's wake-up time 2 (STA2 service period) during the sub-device 2 service period. Furthermore, in the synchronization phase, sub-device 2 negotiates with STA2 for STA2's wake-up time 2 (STA2 service period) during the sub-device 2 service period. It should be noted that the way the master device allocates the sub-device 2 service period to sub-device 2 is similar to the way the master device allocates the sub-device 1 service period to sub-device 1 in the above step 107, and the format of message 2-3 is similar to that of message 1-3 in step 107. For details, please refer to the relevant introduction of step 107 above, which will not be repeated here. Message 2-3 can also be called a TWT negotiation time message.

[0156] Optionally, before the main device sends message 2-3 to sub-device 2, sub-device 2 is also used to execute step 110 to report status information to the main device, so that the main device can more specifically allocate the corresponding sub-device 2 service period to sub-device 2 according to the status information reported by sub-device 2. Step 110 is introduced below.

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

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

[0159] It should be noted that in Figure 5 During the initialization phase of the illustrated embodiment, there is no clear timing relationship between the interaction process between the master device and sub-device 1 and the interaction process between the master device and sub-device 2. For example, the interaction process between the master device and sub-device 1 may be executed first, or the interaction process between the master device and sub-device 2 may be executed first, or the interaction process between the master device and sub-device 1 and the interaction process between the master device and sub-device 2 may be executed simultaneously.

[0160] It should be noted that, considering the actual application, some STAs support negotiation of STA wake-up time with sub-devices, while some STAs do not support negotiation of STA wake-up time with sub-devices. STAs that support negotiation of 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 negotiation of STA wake-up time with sub-devices can be called non-TWT users. In the time allocation stage, the master device can schedule TWT users and non-TWT users separately. For example, the master device prioritizes scheduling TWT users and then schedules non-TWT users. Specifically, Figure 5 Step 111 and step 112 in the illustrated embodiment.

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

[0162] Specifically, after the master device receives message 1-1 sent by slave device 1, it can learn the wake-up time of STA1 (STA1 service cycle). The master device can schedule STA1 in the awake state during the STA1 service cycle. Then, the master device sends message 1-2 to slave device 1 to indicate that slave device 1 is allowed to send data to STA1 during the STA1 service cycle. Similarly, after the master device receives message 2-1 sent by slave device 2, it can learn the wake-up time of STA2 (STA2 service cycle). The master device can schedule STA2 in the awake state during the STA2 service cycle. Then, the master device sends message 2-2 to slave device 2 to indicate that slave device 2 is allowed to send data to STA2 during the STA2 service cycle.

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

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

[0165] Figure 7 This is a structural diagram of the main device in the embodiment of the present application. Figure 7 As shown, the master device includes a processing unit 201 and a transceiver unit 202. Specifically, the transceiver unit 202 is used to perform the above Figure 4 or Figure 5 In the embodiment shown, the master device performs the message sending and receiving operations. The processing unit 201 is used to perform the above Figure 4 or Figure 5 In the illustrated embodiment, in addition to the sending and receiving of messages, other operations of the master device, for example, the processing unit 201 can perform operations such as decision making and message generation.

[0166] Figure 8 This is another structural diagram of the main device in the embodiment of the present application. Figure 8 As shown, the main device includes a processor 301 and an interface 302, and the processor 301 and the interface 302 are connected to each other through a line. It should be noted that the interface 302 is used to perform the above Figure 4 or Figure 5 In the embodiment shown, the master device performs the message sending and receiving operation. The processor 301 is used to execute the above Figure 4 or Figure 5In the illustrated embodiment, in addition to message transmission and reception, other operations of the master device, for example, the processor 301 may perform operations such as decision-making and message generation. In some possible implementations, the processor 301 includes the aforementioned processing unit 201, and the interface 302 includes the aforementioned transceiver unit 202. Optionally, the master device may further 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 the embodiment of this application. 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 Figure 4 or Figure 5 In the embodiment shown, the sub-device performs the message sending and receiving operation. The processing unit 401 is used to perform the above Figure 4 or Figure 5 In the illustrated embodiment, other operations of the sub-devices besides message sending and receiving are shown.

[0168] Figure 10 This is another structural diagram of the sub-device in the embodiment of the present application. Figure 10 As shown, the sub-device includes a processor 501 and an interface 502, and the processor 501 and the interface 502 are connected to each other through a line. It should be noted that the interface 502 is used to perform the above Figure 4 or Figure 5 In the embodiment shown, the sub-device performs the message sending and receiving operation. The processor 501 is used to execute the above Figure 4 or Figure 5 In the illustrated embodiment, other operations of the sub-device besides message sending and receiving. In some possible implementations, the processor 501 includes the aforementioned processing unit 401, and the interface 502 includes the aforementioned transceiver unit 402. Optionally, the main device may further include a memory 503, wherein the memory 503 is used to store program instructions and data.

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

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

[0171] An embodiment of the present application further provides a computer-readable storage medium, comprising a program or instructions, which, when executed on a computer, enables implementation of the method as performed in the above method embodiment.

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

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

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

[0175] In the above embodiments, all or part of them can be implemented by software, hardware, firmware or any combination thereof.

[0176] When implemented using hardware, the method provided in the embodiments of the present application may be implemented without reading software code or instructions. For example, it may be implemented by a CPU, DSP, ASIC, FPGA, other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.

[0177] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function of the embodiment of the present application is executed in whole or in part. 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 instruction can be stored in a computer-readable storage medium or transmitted via 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 that integrates one or more available media. Available media can be magnetic media, such as a floppy disk, a hard disk, or a magnetic tape; it can also be an optical medium, such as a digital versatile disc (DVD); it can also be a semiconductor medium, such as a solid-state drive (SSD).

[0178] Finally, it should be noted that the above are only specific embodiments of this application, but the scope of protection of this application is not limited to them. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A service scheduling method, characterized in that: include: The sub-device sends a site STA target wake-up time TWT negotiation time reporting message to the main device, and the STA TWT negotiation time reporting message includes the identifier of the STA, the start time and duration of the STA service cycle. The STA TWT negotiation time reporting message is used to indicate the negotiation result between the sub-device and the STA, wherein the STA in the STA service cycle or in the awake state is scheduled by the main device.

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

3. The method according to claim 2, characterized in that Before the sub-device receives the TWT negotiation time message sent by the master device, the method further includes: The sub-device sends status information to the main device, where the status information is used to support the main 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 or 4, characterized in that The status information includes 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 SSID supported by the sub-device, and the transmission power level supported by the sub-device.

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

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 period includes the sub-device service period allocated by the master device to all sub-devices.

9. The method according to any one of claims 2 to 8, 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 to 9, characterized in that Before the sub-device sends the site STA target wake-up time TWT negotiation time reporting message to the main device, the method further includes: The sub-device negotiates with the STA a wake-up time of the STA.

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

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

13. The method according to any one of claims 1 to 12, characterized in that The master device is an MFU, and the slave device is an SFU.

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

15. A sub-device, characterized in that: The sub-device includes a transceiver unit; The transceiver unit is used to send a site STA target wake-up time TWT negotiation time reporting message to the main device, wherein the STA TWT negotiation time reporting message includes the identifier of the STA, the start time and duration of the STA service cycle, and the STATWT negotiation time reporting message is used to indicate the negotiation result between the sub-device and the STA. The STA in the STA service cycle or in the awake state is scheduled by the main device.

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

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

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

19. The device according to claim 17 or 18, characterized in that The status information includes 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 SSID supported by the sub-device, and the transmission power level supported by the sub-device.

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

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 period includes the sub-device service period allocated by the master device to all sub-devices.

23. The device according to any one of claims 16 to 22, 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 15 to 23, characterized in that The sub-device further includes a processing unit, and the processing unit is configured to negotiate with the STA a wake-up time of the STA.

25. The device according to any one of claims 15 to 24, characterized in that The transceiver unit is further configured to receive a scheduling message sent by the master device.

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

27. The apparatus according to any one of claims 15 to 26, characterized in that The master device is an MFU, and the slave device is an SFU.

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

29. A sub-device, characterized in that: The sub-device comprises instructions, which, when executed by the sub-device, cause the sub-device to perform the method according to any one of claims 1 to 14.

30. A communication system, characterized in that: The device comprises a main device and at least one sub-device according to any one of claims 15 to 29, wherein the main device communicates with the at least one sub-device.

31. A chip, characterized in that: The chip is configured to execute the method according to any one of claims 1 to 14.

Images