Communication method and communication device

Abstract

Provided are a communication method and a communication device, relating to the field of optical communications, through which an air interface resource needing to be scheduled by any access device can be determined, and the access device can perform service transmission according to the determined air interface resource by scheduling a corresponding instruction, thereby effectively avoiding air interface collision, and improving user experience. Therefore, the plurality of communication devices are accessed orderly or concurrently, and the user experience is greatly improved. The communication method is applied to the communication device. The communication method comprises the following steps: acquiring an air interface resource demand of at least one access device; wherein the air interface resource is used for indicating the air interface resource needing to be called by at least one access device; and sending a scheduling instruction to the at least one access device based on the air interface resource demand, wherein the scheduling instruction is used for indicating the available duration of the at least one access device and the starting moment of the available duration. The embodiment of the invention is applied to optical communication.

Description

[0001] This application is a divisional application. The application number of the original application is 202411919854.X, and the original application date is December 23, 2024. 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 optical communications, and in particular to a communication method and a communication device. Background Art

[0003] Currently, with the advancement of broadband strategies, fiber-to-the-home (FTTH) penetration has reached over 90%. Broadband users often upgrade their broadband plans (usually expressed in megabits per second (Mbit / s)) to achieve a better internet experience. However, the actual internet speed users experience often falls short of the promised bandwidth (i.e., the contracted bandwidth) in their broadband plans.

[0004] Taking home networks as an example, the basic broadband packages provided by operators have a contracted bandwidth of 200 Mbit / s. However, nearly 80% of these homes still experience actual speeds far below this contracted bandwidth. For example, in scenarios with large home network coverage, such as large apartments and villas, indoor wireless data transmission can suffer from insufficient bandwidth and poor network coverage, leading to frequent network interruptions and severely impacting the user experience. To address this issue, fiber-to-the-room (FTTR) solutions—where fiber reaches every room—can be adopted. This enables home networks to achieve ultra-high contracted bandwidth and cover every corner of the home, meeting user needs. In wireless local area networks (WLANs), multiple stations (STAs) compete for resources within the communication network (referred to as the network) to transmit services to other communication devices or apparatuses. For example, STAs transmit services to access points (also known as access points, APs). In this way, channel conflicts may occur when STAs transmit services, that is, at least two STAs transmit services on the same channel at the same time, which will cause confusion in the AP reception and make it impossible to correctly receive any services sent by the STA. Usually, channel access can be performed according to the carrier sense multiple access with collision avoidance (CSMA / CA) mechanism to avoid channel conflicts. Specifically, when the STA detects that the transmission medium is idle, it will randomly wait for a period of time. If the transmission medium is still idle, it will send services (such as service data). In order to ensure the quality of communication, the AP can send an acknowledgment frame ACK to the STA after the service data transmission is completed to confirm the transmission of the service data.

[0005] Since the CSMA / CA mechanism is a decentralized channel access mechanism, air interfaces are prone to collision when multiple communication devices (including multiple APs or multiple STAs) access the channel, resulting in disordered access of multiple communication devices, performance loss, and other problems, which in turn affects user experience. Summary of the Invention

[0006] The present application provides a communication method and a communication device, which can determine the air interface resources that need to be scheduled for any access device, and through corresponding instructions, enable the access device to transmit services according to the determined air interface resources, thereby effectively avoiding air interface collisions, allowing multiple communication devices to access in an orderly or concurrent manner, and greatly improving the user experience.

[0007] In a first aspect, a communication method is provided, the communication method being applied to a communication device. The communication method includes: obtaining an air interface resource requirement of at least one access device; wherein the air interface resource requirement indicates the air interface resources to be utilized by the at least one access device; and sending a scheduling instruction to the at least one access device based on the air interface resource requirement, the scheduling instruction indicating a duration for which the at least one access device can utilize the resources and a start time of the duration.

[0008] Then, the communication method in the above scheme can determine the air interface resources that the access device (e.g., transmission service) needs to call based on the acquired air interface resource requirements. Furthermore, by sending a scheduling instruction to the access device, the access device is instructed to call based on the available time and the start time of the available time. Generally, the access device needs to call different air interface resources to transmit services, such as time resources, that is, the above-mentioned available time and the start time of the available time. Through the above scheme, the air interface resources that the access device needs to call to transmit services can be configured, thereby ensuring the transmission quality of the access device. It is not difficult to understand that many application scenarios of communication networks usually include multiple access devices. In this way, based on the above scheme, the air interface resources that multiple access devices in the network need to call can be determined based on the acquired air interface resource requirements, and by sending a scheduling instruction to the access device, the access device can transmit services according to the corresponding air interface resources. It should be noted that the embodiments of the present application do not limit the specific methods, steps, etc. for determining the air interface resources that one or more access devices need to call using the above communication method. In one possible implementation, the air interface resources required for different access devices can also be determined based on the priority of the services they transmit. This solution can then determine the air interface resources required for multiple access devices in the network based on the acquired air interface resource requirements, and control the duration of service transmission available to the access devices and the start time of that available duration through scheduling instructions, allowing multiple communication devices to access the network in an orderly or concurrent manner. This effectively avoids channel conflicts and air interface collisions that may arise when different access devices transmit services, significantly improving the user experience.

[0009] In a possible implementation manner, the air interface resource requirement is service information or signal strength between the at least one access device and other communication devices.

[0010] In a possible implementation, the start time of the usable duration is indicated by a delay time.

[0011] In a possible implementation, the delay time starts from when the at least one access device receives the scheduling instruction.

[0012] In a possible implementation, the delay time is indicated by a first field of the scheduling instruction, and the first field occupies 4 bytes.

[0013] In a possible implementation, when the first field is all FFs, the delay time indicates that the start time of the available duration is the time when the at least one access device receives the scheduling instruction.

[0014] In one possible implementation, obtaining the air interface resource requirements of at least one access device includes: receiving reporting information from at least one access device; wherein the reporting information includes a scheduling request from at least one access device, and the scheduling request is used to indicate the time resources that the at least one access device needs to call; based on the reporting information, determining the air interface resources that the at least one access device needs to call.

[0015] The above solution can then obtain the required air interface resources indicated by the access device's air interface resource requirements based on the reported information received from the access device. The reported information includes a scheduling request indicating the time resources required by the access device. Specifically, the communication device can determine the required air interface resources (i.e., the time resources required by the access device, including, for example, the required duration) indicated by the access device's air interface resource requirements based on the scheduling request in the reported information. In one possible implementation, the reported information can be reported directly by the access device to the communication device. In some examples, the reported information can also be determined by the communication device based on performance parameters transmitted by the access device. Of course, the reported information can also include other possible parameters, such as the priority of the access device's transmission service and the access device's waiting delay, which are not limited in the embodiments of the present application. Furthermore, the present application does not limit the method for obtaining the access device's reported information. Thus, based on the reported information including the scheduling request, the communication device can determine the time resources required by the access device, and then determine the required air interface resources (e.g., time resources) indicated by the access device's air interface resource requirements based on the required time resources. Then, through the above solution, the air interface resources to be called indicated by the air interface resource requirements of the access device can be configured based on the time resources to be called by the access device, so that multiple communication devices can access in an orderly or concurrent manner, ensuring the transmission quality of the access device.

[0016] In one possible implementation, obtaining the air interface resource requirements of at least one access device includes: obtaining service information of at least one access device; wherein the service information includes queue information of services transmitted by at least one access device; and determining the air interface resources that need to be called by at least one access device based on the service information.

[0017] Then, the above solution can obtain the air interface resources to be called as indicated by the air interface resource requirements of the access device based on the service information obtained from the access device. The service information includes queue information for the service transmitted by the access device. Furthermore, the communication device can determine the air interface resources to be called as indicated by the air interface resource requirements of the access device data based on the queue information included in the service information. In one possible implementation, the access device in the network reports the queue information of the service it transmits to the communication device, and the communication device obtains the queue information of the access device based on the received queue information. In other examples, the service information can also be determined by the communication device based on relevant information of the access device. It is not difficult to understand that the embodiments of the present application do not limit the specific method for the communication device to obtain the service information of the access device. In addition, based on the above solution, the communication device can control each frame transmitted by the access device (the air interface resources to be called) by issuing a scheduling instruction to the access device; or, it can pre-allocate the air interface resources to be called by the access device (transmission service) within a certain time period. In this way, in the above solution, based on the queue information included in the service information, the communication apparatus can determine the air interface resources to be called as indicated by the air interface resource requirements of the access device.

[0018] In one possible implementation, the above-mentioned obtaining of the air interface resource requirements of at least one access device includes: obtaining interaction information between at least one access device and other communication devices; wherein the interaction information includes the signal strength between at least one access device and other communication devices; based on the interaction information, determining the air interface resources that need to be called by at least one access device.

[0019] Then, the above scheme can obtain the air interface resources to be called as indicated by the air interface resource demand of the access device based on the obtained interaction information between the access device and other communication devices. The interaction information includes the signal strength between the access device and other communication devices. Specifically, the communication device can determine the interference situation of other surrounding communication devices on the access device based on the obtained signal strength between the access device and other communication devices. Further, based on the determined interference situation, the communication device determines the air interface resources to be called as indicated by the air interface resource demand of the access device. Of course, the embodiment of the present application does not limit the manner in which the communication device obtains the interaction information of the access device. In this way, the above scheme can determine the interference situation of other surrounding communication devices on the access device based on the signal strength included in the interaction information, thereby determining the air interface resources to be called as indicated by the air interface resource demand of the access device based on the interference situation.

[0020] In a possible implementation, the communication method further includes: receiving a device cache and a transmission rate sent by at least one access device; and determining, based on the device cache and the transmission rate, a time resource that needs to be called by the at least one access device.

[0021] Then, in the above scheme, based on the device cache and transmission rate received from the access device, the communication device can determine the time resources that the access device needs to call, that is, it can determine the scheduling request of the access device. Further, based on the other schemes mentioned above, according to the scheduling request, the communication device can determine the time resources that the access device needs to call. Of course, the communication device can also determine the time resources that the access device needs to call by other means based on the received device cache and transmission rate, and the embodiments of the present application are not limited to this. Then, the above scheme can determine the time resources that the access device needs to call based on the device cache and transmission rate sent by the access device.

[0022] In one possible implementation, obtaining service information of at least one access device includes: receiving queue information reported by at least one access device; determining service information of at least one access device based on the queue information; or obtaining queue entry information and queue exit information for service transmission of at least one access device; and determining service information of at least one access device based on the queue entry information and queue exit information.

[0023] Based on the above solution, the communication device acquires service information of the access device by: determining the service information of the access device based on queue information reported by the access device; or, the communication device collects statistics on queue entry and exit information of services transmitted by the access device to determine the queue information of the access device, and thereby determines the service information of the access device. Furthermore, based on the queue information included in the service information, the communication device can determine the air interface resources to be utilized as indicated by the air interface resource requirements of the access device. In one possible implementation, the communication device can directly determine the queue information of the access device by collecting statistics on queue entry and exit information of services transmitted by the access device within a fixed time period. Of course, the communication device can also acquire service information of the access device through other possible methods, which are not limited in the embodiments of the present application. Thus, the above solution can acquire service information of the access device across devices (requiring collaboration between the access device and the communication device), that is, acquiring service information of the access device based on the queue information reported by the access device. Alternatively, the communication device can directly acquire service information of the access device based on queue entry and exit information within a fixed time period.

[0024] In a possible implementation, the communication method further includes: sending a test message to at least one access device, where the test message is used to instruct the at least one access device to determine a signal strength with other communication devices.

[0025] Based on the above solution, the communications device can instruct the access device to determine the signal strength between itself and other communications devices by sending a test message to the access device. Furthermore, based on this signal strength, the interference situation surrounding the access device can be determined. Optionally, the signal strength includes the signal strength between the access device and the communications device. In other examples, the signal strength also includes the signal strength between the access device and one or more terminals. Specifically, the signal strength can be the signal strength between an AP and one or more surrounding STAs. Alternatively, the signal strength can be the signal strength between an AP and one or more surrounding APs. In another example, the signal strength can be the signal strength between an STA and one or more surrounding STAs (and communicated to the connected AP). Of course, this application does not limit the device form or type of other communications devices. Based on the above solution, the access device can be controlled to determine the surrounding signal strength by sending a test message to the access device. Furthermore, based on the determined signal strength, the communications device can determine interaction messages with the access device so that the communications device can obtain the air interface resources required by the access device.

[0026] In a possible implementation, the air interface resources further include one or more of the following: spectrum resources, link resources, power control information, rate control information, antenna selection information, and contention parameters.

[0027] In a possible implementation, obtaining the air interface resource requirements of at least one access device includes: obtaining the air interface resource requirements of at least one access device through a wired transmission medium.

[0028] In a possible implementation, sending a scheduling instruction to at least one access device based on air interface resource requirements includes: sending the scheduling instruction to at least one access device through a wired transmission medium based on the air interface resource requirements.

[0029] In a second aspect, a communication method is provided for use with an access device. The method includes: receiving a scheduling instruction sent by a communication device; and transmitting a service based on the scheduling instruction, wherein the scheduling instruction indicates the duration of use of the access device and the start time of the useable duration.

[0030] Then, in the above scheme, the access device can receive the scheduling instruction sent by the communication device and transmit the service based on the received scheduling instruction; wherein the scheduling instruction indicates the duration available for the access device and the starting time of the available duration. Exemplarily, the access device can determine the air interface resources required to transmit the service, that is, the time resources (including the available duration and the starting time of the available duration) by parsing the received scheduling instruction. Further, the access device can transmit the service based on the air interface resources to be called. Optionally, the access device can call all the available duration indicated by the scheduling instruction. Alternatively, the access device can also call part of the available duration indicated by the scheduling instruction according to actual needs. In one possible implementation, the communication device in the above scheme can be the communication device provided in the above embodiment of the present application, and the communication device sends the scheduling instruction to the access device based on the above method embodiment. Of course, the communication device can also be implemented by other communication devices that can achieve similar functions, and the embodiments of the present application are not limited to this. Then, the access device in the above solution can receive the scheduling instruction sent by the communication device, and then transmit the service based on the air interface resources to be called indicated by the scheduling instruction, thereby effectively improving the transmission quality of the service.

[0031] In a possible implementation, the start time of the usable duration is indicated by a delay time.

[0032] In a possible implementation, the delay time starts from when the at least one access device receives the scheduling instruction.

[0033] In a possible implementation, the delay time is indicated by a first field of the scheduling instruction, and the first field occupies 4 bytes.

[0034] In a possible implementation, when the first field is all FFs, the delay time indicates that the start time of the available duration is the time when the at least one access device receives the scheduling instruction.

[0035] In a possible implementation, the communication method further includes: sending reporting information to the communication apparatus; wherein the reporting information includes a scheduling request of the access device, and the scheduling request is used to indicate the time resources that the access device needs to call.

[0036] In a possible implementation, the communication method further includes: sending service information to the communication device; wherein the service information includes queue information of the access device.

[0037] In a possible implementation, the communication method further includes: sending interaction information between the communication device and other communication devices to the communication apparatus; wherein the interaction information includes signal strength between at least one access device and the other communication devices.

[0038] In a possible implementation, sending the reporting information to the communication device includes: sending the device buffer and transmission rate of the device to the communication device.

[0039] In a possible implementation, sending service information to the communication device includes sending queue information to the communication device.

[0040] In a possible implementation, the communication method further includes: receiving a test message sent by the communication device; and determining a signal strength with other communication devices based on the test message.

[0041] According to a third aspect, a communication device is provided. The communication device includes an interface unit and a processing unit; the processing unit is configured to obtain air interface resource requirements of at least one access device, wherein the air interface resource requirements indicate air interface resources to be utilized by the at least one access device; and the interface unit is configured to send a scheduling instruction to the at least one access device based on the air interface resource requirements obtained by the processing unit, wherein the scheduling instruction indicates a duration for which the at least one access device can use the resource and a start time of the duration for which the resource can use the resource.

[0042] In a possible implementation manner, the air interface resource requirement is service information or signal strength between the at least one access device and other communication devices.

[0043] In a possible implementation, the start time of the usable duration is indicated by a delay time.

[0044] In a possible implementation, the delay time starts from when the at least one access device receives the scheduling instruction.

[0045] In a possible implementation, the delay time is indicated by a first field of the scheduling instruction, and the first field occupies 4 bytes.

[0046] In a possible implementation, when the first field is all FFs, the delay time indicates that the start time of the available duration is the time when the at least one access device receives the scheduling instruction.

[0047] In one possible implementation, the interface unit is also used to receive reporting information from at least one access device; wherein the reporting information includes a scheduling request from at least one access device, and the scheduling request is used to indicate the time resources that need to be called by at least one access device; the processing unit is specifically used to determine the air interface resources that need to be called by at least one access device based on the reporting information received by the interface unit.

[0048] In one possible implementation, the interface unit is also used to obtain service information of at least one access device; wherein the service information includes queue information of the service transmitted by at least one access device; and the processing unit is specifically used to determine the air interface resources that need to be called by at least one access device based on the service information obtained by the interface unit.

[0049] In one possible implementation, the interface unit is also used to obtain interaction information between at least one access device and other communication devices; wherein the interaction information includes the signal strength between at least one access device and other communication devices; the processing unit is specifically used to determine the air interface resources that need to be called by at least one access device based on the interaction information obtained by the interface unit.

[0050] In one possible implementation, the interface unit is further used to receive the device cache and transmission rate sent by at least one access device; the processing unit is further used to determine the time resources that need to be called by at least one access device based on the device cache and transmission rate received by the interface unit.

[0051] In one possible implementation, the interface unit is specifically used to receive queue information reported by at least one access device; the processing unit is used to determine the service information of at least one access device based on the queue information received by the interface unit; or, the interface unit is specifically used to obtain queue entry information and queue exit information for service transmission of at least one access device; the processing unit is used to determine the service information of at least one access device based on the queue entry information and queue exit information obtained by the interface unit.

[0052] In a possible implementation manner, the communication device includes any one of the following: a gateway or an optical line terminal.

[0053] In a fourth aspect, a communication device is provided for use with an access device. The communication device includes an interface unit and a processing unit; the interface unit is configured to receive a scheduling instruction sent by the communication device; and the processing unit is configured to transmit a service according to the scheduling instruction received by the interface unit, wherein the scheduling instruction indicates the duration of time during which the access device can be used and the start time of the available time.

[0054] In a possible implementation, the start time of the usable duration is indicated by a delay time.

[0055] In a possible implementation, the delay time starts from when the at least one access device receives the scheduling instruction.

[0056] In a possible implementation, the delay time is indicated by a first field of the scheduling instruction, and the first field occupies 4 bytes.

[0057] In a possible implementation, when the first field is all FFs, the delay time indicates that the start time of the available duration is the time when the at least one access device receives the scheduling instruction.

[0058] In a possible implementation, the interface unit is further configured to send reporting information to the communication apparatus; wherein the reporting information includes a scheduling request of the access device, and the scheduling request is configured to indicate time resources that the access device needs to call.

[0059] In a possible implementation, the interface unit is further configured to send service information to the communication apparatus; wherein the service information includes queue information of the access device.

[0060] In a possible implementation, the interface unit is further configured to send interaction information between the communication device and other communication equipment to the communication apparatus; wherein the interaction information includes signal strength between at least one access device and other communication equipment.

[0061] In a possible implementation, the interface unit is further configured to send its own device buffer and transmission rate to the communication apparatus.

[0062] In a possible implementation manner, the interface unit is further configured to send queue information to the communication device.

[0063] In a possible implementation, the interface unit is further configured to receive a test message sent by the communication device; and the processing unit is further configured to determine the signal strength with other communication devices based on the test message received by the interface unit.

[0064] In a fifth aspect, a communication device is provided. The communication device may be a communication device, a module or chip within the communication device, or a chip or system-on-chip. The communication device includes a processor and an interface circuit, wherein the processor is coupled to the interface circuit; the processor is configured to control the interface circuit to execute the communication method described in any possible implementation of the first or second aspect.

[0065] In a sixth aspect, a computer-readable storage medium stores a computer program or instructions, which, when read and executed by a computer, causes the computer to execute the communication method as described in any possible implementation of the first or second aspect.

[0066] In the seventh aspect, a computer program product containing instructions is provided, the computer program product including: computer program code, which, when the computer program code is run on a computer, enables the computer to execute the communication method described in any possible implementation of the first aspect or the second aspect.

[0067] In an eighth aspect, a chip or chip system is provided, comprising: a processing circuit and an input / output interface; wherein the processing circuit is configured to execute the communication method as described in any possible implementation of the first aspect or the second aspect.

[0068] Among them, the technical effects brought about by any design method from the third aspect to the eighth aspect can refer to the technical effects brought about by different design methods in the first aspect and the second aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] Figure 1 An architectural diagram of a home network provided in an embodiment of the present application;

[0070] Figure 2 A schematic diagram of a topological structure provided in an embodiment of the present application;

[0071] Figure 3 A schematic diagram of a topological structure provided in another embodiment of the present application;

[0072] Figure 4 A schematic diagram of a topological structure provided in yet another embodiment of the present application;

[0073] Figure 5 An architectural diagram of a communication network provided in an embodiment of the present application;

[0074] Figure 6 A schematic diagram of a transmission service provided in an embodiment of the present application;

[0075] Figure 7 A schematic diagram of a communication method provided in an embodiment of the present application;

[0076] Figure 8 A schematic diagram of information transmission provided in an embodiment of the present application;

[0077] Figure 9 A schematic diagram of information transmission provided in accordance with another embodiment of the present application;

[0078] Figure 10 A schematic diagram of a communication device provided in an embodiment of the present application;

[0079] Figure 11A schematic diagram of a communication device provided in accordance with another embodiment of the present application. DETAILED DESCRIPTION

[0080] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments.

[0081] Unless otherwise defined, all technical terms used herein have the same meanings as those known to those of ordinary skill in the art. In the embodiments of the present application, words such as "first" and "second" do not limit the quantity and order. In the embodiments of the present application, "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, wherein A and B can be singular or plural.

[0082] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0083] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0084] Currently, with the advancement of broadband strategies, fiber-to-the-home penetration has reached over 90%. To achieve a better online experience, broadband users are constantly upgrading their broadband packages (typically expressed by the broadband service transmission rate in Mbit / s). However, research has found that many high-bandwidth packages (with higher service transmission rates) fail to fully utilize their capabilities. In other words, the actual speeds experienced by broadband users often fall short of the promised bandwidth (i.e., the contracted bandwidth) in their broadband packages.

[0085] Taking home networks as an example, the basic broadband packages provided by operators have a contracted bandwidth of 200Mbit / s. However, nearly 80% of home networks still experience actual network speeds far below the contracted bandwidth. It should be noted that the following embodiments of this application are not limited to home networks; for example, enterprise networks can also be used. This example only uses the home network scenario and should not limit the embodiments of this application.

[0086] For example, refer to Figure 1 As shown, an embodiment of the present application provides an architecture diagram of a home network. Figure 1As shown, the home network includes: a main FTTR device (referred to as the main FTTR, refer to Figure 1 The master FTTR 101 in the FTTR), multiple slave FTTR devices (abbreviated as slave FTTR, refer to Figure 1 The master FTTR 101 is used to connect to a plurality of slave FTTRs (including the slave FTTRs 102-1 to 102-5) and terminal devices (see the terminal 103 in the figure).

[0087] In one possible implementation, combining Figure 1 As shown, the above-mentioned home network also includes a connection device (refer to Figure 1 The connecting device 104 in the figure). Optionally, the connecting device can be an optical distribution box or a photoelectric distribution box. It is easy to understand that for the sake of convenience, only Figure 1 For example, the terminal 103 in the above-mentioned home network includes a plurality of different types of terminal devices deployed in different locations (such as different rooms) within the home, such as Figure 1 The computer, tablet, robot vacuum and virtual reality (VR) glasses shown in FIG. For another example, the above network architecture may also include more communication devices or apparatuses.

[0088] Specifically, refer to Figure 1 As shown, when this home network is deployed in a large household (such as a villa) with a large coverage area, terminals 103 deployed at different locations in the home communicate with slave FTTRs 102-3 using wireless transmission technologies, such as WLAN. However, due to the large coverage area, users may experience insufficient bandwidth and poor network coverage during network use, resulting in frequent network interruptions and a serious impact on the user's network experience.

[0089] To address this issue, FTTR, which is a solution where fiber reaches every room, can be adopted to enable the home network to achieve ultra-high contracted bandwidth and cover every corner of the home, thus meeting user needs. Figure 1 Taking the home network shown as an example, the master FTTR 101 is connected to multiple slave FTTRs (including slave FTTR 102-1 to slave FTTR 102-5) deployed in different rooms via optical fibers.

[0090] Among them, multiple STAs included in the WLAN will compete for the use of resources in the communication network (referred to as the network) to transmit services with other communication devices or communication devices, such as STA transmitting services to the AP. In this way, channel conflicts may occur when STAs transmit services, that is, at least two STAs transmit services on the same channel at the same time, which will cause confusion in the AP's reception and make it unable to correctly receive any services sent by STAs. Among them, combined with Figure 1 As shown, the aforementioned STA may be the master FTTR 101, and the aforementioned APs may be the slave FTTRs 102-1 to 102-5.

[0091] For this reason, the CSMA / CA mechanism is typically used for channel access to avoid channel conflicts. Specifically, when a STA detects that the transmission medium is idle, it will wait for a random period of time. If the transmission medium is still idle, it will send services (such as service data). To ensure communication quality and reliability, the AP can send an ACK frame to the STA after the service data transmission is completed to confirm the transmission of the service data.

[0092] Based on the above CSMA / CA mechanism, take the process of a STA sending data to an AP as an example. Specifically:

[0093] On the transmitting side: When a STA needs to transmit data on a wireless network, it checks the transmission medium's status. If no data transmission is detected, it waits for an additional period of time and then randomly selects a time slot (corresponding to a certain length of time) to continue checking. If no data is transmitted on the wireless network, it sends the data.

[0094] On the receiving end: If the receiving AP receives the complete data sent by the transmitting STA, it sends an ACK frame back to the transmitting STA. If the transmitting STA receives this ACK frame, the data transmission process is completed. If the transmitting STA does not receive the ACK frame, or the sent data is not completely received by the AP, or the ACK frame fails to be sent, in any of the above cases, the transmitting STA will wait for a period of time and then resend the last content to the receiving AP.

[0095] While the above solution can, to a certain extent, prevent channel conflicts between STAs and APs, CSMA / CA is a decentralized channel access mechanism. This makes it easy for multiple communication devices (including multiple APs or multiple STAs) to collide with each other when accessing the channel. This can lead to disordered access, performance loss, and other issues that negatively impact user experience. These issues have become a major pain point in current FTTR scenarios, impacting user experience.

[0096] Based on the above problems, in the full load transmission (full buffer) scenario of FTTR, different deployment scenarios will lead to different air interface duty cycles. Figure 2 As shown, the embodiment of the present application provides a schematic diagram of a topology structure, showing a typical exposed terminal topology structure. Figure 2 As shown, the topology includes three FTTRs (refer to Figure 2 FTTR 201 to FTTR 203).

[0097] Specifically, refer to Figure 2 As shown, FTTR 201 is within the signal coverage of FTTR 202 and FTTR 203, FTTR 202 is within the signal coverage of FTTR 201 and FTTR 203, and FTTR 203 is within the signal coverage of FTTR 201 and FTTR 202. In this topology, the FTTRs in this topology can all detect each other. Under fair air access (each FTTR has the same air interface access priority), the duty cycle of each FTTR is 33%.

[0098] For example, refer to Figure 3 As shown, the embodiment of the present application provides a schematic diagram of a topology structure, showing a typical hidden terminal topology structure. Figure 3 As shown, the topology includes three FTTRs (refer to Figure 3 FTTR 301 to FTTR 303 in the FTTR Guidelines).

[0099] Specifically, refer to Figure 3 As shown, FTTR 301 is within the signal coverage of FTTR 302, and FTTR 302 is within the signal coverage of FTTR 303. Thus, in this topology, FTTR 301 and FTTR 302 can hear each other, and FTTR 302 and FTTR 303 can also hear each other. However, FTTR 301 and FTTR 303 are hidden nodes from each other, meaning they cannot hear each other.

[0100] This results in FTTR 301 using the air interface while FTTR 302 is retreating, allowing FTTR 303 to retreat and gain access to the air interface. Repeating this process, it is not difficult to see that FTTR 302 is never able to gain access to the air interface, resulting in the air interface duty cycle of FTTR 301 and FTTR 303 being 100%, while the air interface duty cycle of FTTR 302 is 0%.

[0101] based on Figure 2The architecture shown is exemplary, with reference to Figure 4 As shown, the embodiment of the present application also provides a schematic diagram of a topology structure, showing an exposed terminal topology structure. Figure 4 As shown, the topology includes: two APs (refer to Figure 4 AP 1 and AP 2) and two STAs (refer to Figure 4 STA 1 and STA 2 in ).

[0102] In one possible implementation, the signal coverage range of AP 1 and AP 2 is both -55 decibel relative to one milliwatt (dBm). AP 1 and AP 2 can detect each other and are mutually exposed terminals. In this way, AP 1 and AP 2 cannot access the air interface at the same time. Furthermore, since the distance between STA 1 and AP 1 is -10dBm, and the distance between STA 2 and AP 2 is -10dBm, the signal to interference plus noise ratio (SINR) of STA 1 and STA 2 is high enough, so this scenario actually allows AP 1 and AP 2 to access the air interface at the same time. Therefore, in this scenario, the air interface performance in the network will be reduced by 50%.

[0103] It is not difficult to understand that whether two (or more) communication devices or communication apparatuses can access the air interface at the same time and perform concurrent operations can be determined to a certain extent based on the SINR of the communication devices or communication apparatuses.

[0104] Based on the above problems, random backoff conflicts of the air interface can usually be avoided by the following method. Specifically, the method receives service information reported by one or more node devices (i.e., access devices, such as APs) respectively through a control node, wherein the service information can indicate information about service data that the network node needs to transmit through the channel. The control node determines one or more network nodes to be scheduled in the current scheduling period based on the service information reported by the network nodes respectively. Finally, the control node sends a scheduling message to the one or more scheduled network nodes, indicating through the scheduling message that the one or more scheduled network nodes are allowed to compete for the channel.

[0105] While the above solution can avoid air interface contention to a certain extent, it is an improvement on the Enhanced Distributed Channel Access (EDCA) mechanism. Its essence is to assign different scheduling priorities to different network nodes (i.e., APs) based on service buffering. Therefore, even if each AP is allowed to be scheduled within the corresponding scheduling period, air interface contention based on the EDCA mechanism is still required. Furthermore, this solution does not involve the control node making decisions on the scheduling time of network nodes.

[0106] Based on the above problems, random backoff conflicts on the air interface can usually be avoided by coordinating the transmission and reception between the AP and other nearby APs. Specifically, the APs in the network compete for channels and inform other nearby APs after successfully competing. For example, the AP can inform other nearby APs of the successful competition status by sending shared frames to other nearby APs. Optionally, specific notification methods also include time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), spatial reuse (SR), and beamforming (BF).

[0107] While the above solution can achieve distributed sharing of air interface resources (including time and spectrum resources) between APs, thereby avoiding air interface conflicts to a certain extent, it does not centrally configure air interface resources in the network. Relying on a distributed approach, it is impossible to accurately determine which nearby APs require air interface resource allocation, nor is it easy to determine how many nearby APs will receive the status of a successful contention. Therefore, this solution's air interface resource sharing efficiency is low. Furthermore, the above solution cannot update the network topology in real time, resulting in inaccurate air interface resource allocation.

[0108] To address the above issues, the following solution can be employed. Specifically, the solution includes: a device (e.g., a first device) receives an uplink scheduling request from another device (e.g., a second device), the uplink scheduling request including uplink buffer information determined based on uplink data to be transmitted by the other device. Furthermore, the first device generates an uplink bandwidth allocation message based on interference information between multiple devices connected to it and the uplink buffer information, the uplink bandwidth allocation message being used to indicate uplink resources allocated to the second device.

[0109] Through the above solution, when a device (i.e., the first device) is connected to multiple devices, resources can be scheduled for a device (i.e., the second device) among the multiple devices through the one device, thereby reducing latency. However, the above solution mainly focuses on scenarios where passive optical networks (PON) and wireless transmission technologies are jointly applied for service transmission. For example, when encountering air interface interference (for example, when other terminal devices transmit services to the optical network used in the solution) and other similar scenarios, the above solution will not be able to effectively ensure the implementation effect.

[0110] Based on the above, for example, refer to Figure 5 As shown, the embodiment of the present application provides an architecture diagram of a communication network. Figure 5 As shown, the communication network includes: a communication device (refer to Figure 5 Communication device 401 in), multiple access devices (refer to Figure 5 AP 402-1 to AP 402-3) and multiple terminal devices (refer to Figure 5 STAs 403-1 to 403-6 in FIG. 1 ). Communication device 401 is connected to APs 402-1 to 402-3, respectively. AP 402-1 is connected to STAs 403-1 and 403-2, respectively. AP 402-2 is connected to STAs 403-3 and 403-4, respectively. AP 402-3 is connected to STAs 403-5 and 403-6, respectively.

[0111] Optional, see Figure 5 As shown, multiple terminal devices can be STAs, that is, Figure 5 Of course, the terminal device may also be other types of devices, which are not limited in the embodiments of the present application. It is easy to understand that for ease of description, only the terminal device is used here. Figure 5 The architecture shown is taken as an example, and the embodiments of the present application should not be limited to this. Figure 5 As shown, the above communication network also includes multiple obstacles (refer to Figure 5 ). Optionally, obstacles A to E may be walls, or other structures capable of achieving similar functions.

[0112] In one possible implementation, the above-mentioned communication device 401 can be implemented by a centralized scheduler (CS). Optionally, the above-mentioned communication device includes any of the following: a gateway or an optical line terminal. Of course, the above-mentioned communication device can also be integrated into the upper-layer device connected to the AP. For example, the communication device can be integrated into an optical line terminal (OLT) and deployed through the OLT deployed in the network. For another example, the communication device can also be integrated into a gateway. Combined with Figure 1 As shown, the communication device can be deployed through a master FTTR (or slave FTTR) deployed in the network.

[0113] Optionally, the communication device can be connected to other communication devices or communication devices in the network through wired or wireless connection methods such as optical fiber, network cable, and air interface, and the embodiments of the present application do not limit this. Of course, the embodiments of the present application do not limit the device form, specific deployment location, and connection medium of the communication device, and this should not constitute a limitation on the embodiments of the present application.

[0114] Combine Figure 5 As shown, communication device 401 can centrally allocate corresponding air interface resources to each AP (including APs 402-1 through 402-3). Optionally, the air interface resources include time resources. Each AP transmits services and data according to the air interface resources allocated by communication device 401. Furthermore, each AP can also schedule uplink transmissions for connected STAs. This ensures that APs and STAs in the network can transmit in an orderly manner, thereby ensuring transmission quality within the network.

[0115] Optionally, the communication device 401 can control one or more access devices in the network through different communication protocols, such as point-to-point (P2P) or point-to-multipoint (P2MP) communication protocols.

[0116] In a possible implementation, the air interface resources further include one or more of the following: spectrum resources, link resources, power control information, rate control information, antenna selection information, and contention parameters.

[0117] Specifically, according to Figure 5 The architecture shown is able to determine the interference relationship between multiple STAs. Figure 5As shown, since there are two obstacles (i.e., obstacle A and obstacle B) between STA 403-1 and STA 403-4, the interference is small, and the SINR between STA 403-1 and STA 403-4 is high enough, STA 403-1 and STA 403-4 can access the air interface at the same time. Similarly, there are two obstacles between STA 403-3 and STA 403-4, and STA 403-3 and STA 403-5, and the interference is small and the SINR is high enough, so they can also access the air interface at the same time. In this way, the above-mentioned STA 403-1 and STA 403-4, STA 403-3 and STA 403-4, and STA 403-3 and STA 403-5 can be concurrent (including downlink concurrency and uplink concurrency, i.e., simultaneous reception or simultaneous transmission). Furthermore, the communication device 401 can centrally allocate corresponding air interface resources to each AP (including AP 402-1 to AP 402-3), so that multiple STAs that have less mutual interference and can be concurrent can be transmitted concurrently, and the time slots of multiple STAs that have greater mutual interference and cannot be transmitted concurrently are staggered.

[0118] For example, refer to Figure 6 The figure shows the process of AP 402-1, AP 402-2, and AP 402-3 transmitting services to multiple terminal devices (i.e., STA 403-1 to STA 403-6). The arrows following the APs represent the timeline, with the sequence from left to right indicating the chronological order. A trigger (Tri) symbol indicates a change in the AP trigger during service transmission, resulting in a change in the AP's transmission state. For example, the AP's transmission direction changes from downlink to uplink.

[0119] Specific, combined Figure 6 As shown, for AP 402-1:

[0120] In the downlink direction, AP 402-1 first transmits data to STA 403-1 (this process is represented on the timeline as toSTA 403-1). AP 402-1 then transmits data to STA 403-2 (this process is represented on the timeline as toSTA 403-2). Tri 11 triggers a change in the transmission direction between AP 402-1 and STA 403-1. In the uplink direction, AP 402-1 receives data transmitted by STA 403-1 (this process is represented on the timeline as fromSTA 403-1). Tri 12 triggers a change in the transmission direction between AP 402-1 and STA 403-2. AP 402-1 receives data transmitted by STA 403-2 (this process is represented on the timeline as fromSTA 403-2).

[0121] In the downlink direction, AP 402-2 first transmits data to STA 403-4 (this process is represented on the timeline as toSTA 403-4). AP 402-2 then transmits data to STA 403-3 (this process is represented on the timeline as toSTA 403-2). Tri 21 triggers a change in the transmission direction between AP 402-2 and STA 403-3. In the uplink direction, AP 402-2 will receive data transmitted by STA 403-3 (this process is represented on the timeline as fromSTA 403-3). Tri 22 triggers a change in the transmission direction between AP 402-2 and STA 403-4. AP 402-2 receives data transmitted by STA 403-4 (this process is represented on the timeline as fromSTA 403-4).

[0122] In the downlink direction, AP 402-3 first transmits data to STA 403-5 (this process is represented on the timeline as toSTA 403-5). AP 402-3 then transmits data to STA 403-6 (this process is represented on the timeline as toSTA 403-6). Tri 31 triggers a change in the transmission direction between AP 402-3 and STA 403-5. In the uplink direction, AP 402-3 will receive data transmitted by STA 403-5 (this process is represented on the timeline as from STA 403-1). Tri 32 triggers a change in the transmission direction between AP 402-3 and STA 403-6. AP 402-3 then receives data transmitted by STA 403-6 (this process is represented on the timeline as from STA 403-6). Based on the above process, the embodiment of the present application can allocate air interface resources during the transmission process of one or more APs in the network through a communication device, so that the AP can transmit services based on the allocated air interface resources, effectively avoiding problems such as channel conflicts and air interface collisions, and ensuring the transmission quality of the network. It should be noted that Figure 5 The illustrated architecture includes only one communication device (communication device 401), which directly allocates resources to the connected AP. The scheduling method included in the above process can be called two-level scheduling, that is, the communication device centrally makes scheduling decisions (including allocating air interface resources), and the AP directly executes the scheduling decisions.

[0123] In other examples, such as scenarios where an AP needs to transmit multiple services, three-level scheduling is also implemented. Specifically, in the uplink direction, an intermediate node aggregates information about one or more transmission services of the AP, and the communication device then makes scheduling decisions. In the downlink direction, the intermediate node processes the communication device's scheduling decisions, decomposing them into valid information that the AP can parse, and then executing them. Of course, the hierarchical type at which the communication device schedules the AP can also be other possible network architecture types, and the embodiments of this application are not limited thereto.

[0124] Optionally, the intermediate node can be implemented by a collaborative scheduler integrated with the AP. To a certain extent, the collaborative scheduler can also configure the air interface resources for the integrated AP transmission services. For example, when the collaborative scheduler aggregates information on one or more transmission services of the AP and determines that the AP has a relatively small number of transmission services, the collaborative scheduler can implement the functions of the communication device in the above process and configure the air interface resources required by the AP, eliminating the need for step-by-step reporting to the centralized scheduler for scheduling.

[0125] Based on the above architecture, for example, refer to Figure 7 As shown, the embodiment of the present application provides a schematic diagram of a communication method. Figure 7 , the communication method provided in the embodiment of the present application is described in detail. Figure 5 Taking the architecture shown as an example, the communication method provided by the embodiment of the present application is described through a communication device and an access device, but this does not limit the communication method provided by the embodiment of the present application. Figure 5 The architecture shown illustrates the communication method provided in the embodiments of the present application.

[0126] It is not difficult to understand that the embodiments of the present application can be applied to a variety of application scenarios. For example, scenarios including multi-user orthogonal frequency division multiple access (OFDMA) and multi-user multiple input multiple output (MU-MIMO). In the following embodiments, combined with Figure 5 As shown, the communication device is communication device 401 and the access device is AP 402-1. This is not intended to limit the embodiments of the present application. Of course, the access device in the embodiments of the present application can be implemented by any AP from AP 403-1 to AP 403-3, and the embodiments of the present application do not limit this.

[0127] The following combination Figure 7The communication method provided in the embodiment of the present application is described, including steps 601 to 602, as follows:

[0128] Step 601: The communication device obtains the air interface resource requirements of the access device.

[0129] Combine Figure 7 As shown, the communication device obtains the air interface resource requirements of the access device; wherein the air interface resource requirements are used to indicate the air interface resources that need to be called by at least one access device. Figure 5 As shown, the communication device 401 determines the air interface resources that the AP 402-1 needs to call based on the air interface resource requirements.

[0130] Optionally, the air interface resources also include one or more of the following: spectrum resources, link resources, power control information, rate control information, antenna selection information, and competition parameters.

[0131] Specifically, the communication device obtains the air interface resource requirement indicating the air interface resource that the access device needs to call, including:

[0132] Method 1: The communication device receives reporting information from an access device; wherein the reporting information includes a scheduling request from the access device, and the scheduling request is used to indicate a time resource that needs to be called by at least one access device; based on the reporting information, the air interface resource that needs to be called by the access device is determined.

[0133] In some examples, the scheduling request also includes information such as smart antennas, transmit power, and antenna selection information reporting and control. The time resources required for the access device to be deployed, as indicated in the scheduling request, include the duration of the deployment. This duration is also referred to as the scheduling duration and can be converted to air interface time.

[0134] Optionally, the scheduling duration includes: a minimum value of 0, a maximum value of 0xfffffff, or a maximum value defined by other protocols. For example, the scheduling duration may be 5.4 milliseconds (ms).

[0135] Optionally, the reported information may also include service priority, waiting delay and other information, which is not limited in the embodiments of the present application.

[0136] In a possible implementation, the access device can determine its own scheduling request through calculation, that is, determine the time resources to be called indicated by the scheduling request. Figure 8 As shown, the access device reports the time resources to be called to the communication device by sending reporting information to the communication device.

[0137] Method 2: The communication device obtains service information of the access device; wherein the service information includes queue information or service cache information, or service flow information of the service transmitted by the access device; based on the service information, the air interface resources that the access device needs to call are determined.

[0138] Optionally, the above service information also includes rate selection information, etc. The service information may also include service buffer information or service flow information. The service buffer information includes downlink service buffer (indicating downlink buffer size) and uplink service buffer (indicating uplink buffer size).

[0139] In one possible implementation, refer to Figure 9 As shown, the communication device receives the queue information reported by the access device (refer to Figure 9 Based on the queue information, the service information of the access device is determined.

[0140] In other examples, the communication device can obtain queue entry and exit information for service transmission by an access device, and determine service information of the access device based on the queue entry and exit information. For example, the communication device can collect statistics on queue entry information (including the number of queue entry) and queue exit information of the access device over a long period of time to obtain queue information of the access device.

[0141] Method 3: The communication device obtains interaction information between the access device and other communication devices; wherein the interaction information includes the signal strength between the access device and other communication devices; based on the interaction information, determines the air interface resources that the access device needs to call.

[0142] In one possible implementation, a communication device sends a test message to an access device, instructing the access device to determine the signal strength between the access device and other communication devices. Furthermore, the access device obtains interaction information between the access device and the other communication devices based on the signal strength, and further determines the interference situation around the access device based on the signal strength.

[0143] Optionally, the signal strength includes the signal strength between the access device and other nearby access devices. For another example, the signal strength includes the signal strength between the access device and other nearby terminal devices. Signal strength is also called interference signal strength, which is the received signal strength indicator (RSSI) strength of the interference source detected by the access device, measured in dBm.

[0144] Step 602: The communication device sends a scheduling instruction to the access device.

[0145] Combine Figure 7As shown, the communication device sends a scheduling instruction to the access device based on the air interface resource demand, and the scheduling instruction is used to indicate the duration of the access device and the start time of the duration of the access device. Figure 5 As shown, the communication device 401 sends a scheduling instruction to the AP 402-1, indicating the duration of time that the AP 402-1 can use and the start time of the duration of time that the AP 402-1 can use, based on the air interface resource demand.

[0146] Optionally, the scheduling instruction includes a scheduling instruction for the access device in a downlink direction and a scheduling instruction for the access device in an uplink direction.

[0147] In conjunction with step 601, the communication device determines the air interface resources that the access device needs to utilize based on the service information. Thus, the scheduling instructions sent by the communication device to the access device can control the air interface resources (e.g., including the time resources to be utilized) that the access device needs to utilize on a per-frame basis, or can pre-allocate the air interface resources that the access device needs to utilize on a periodic basis.

[0148] In one possible implementation, the scheduling instructions can be refreshed in real time based on the refresh of the received scheduling request. It is easy to understand that the timing of reporting the scheduling request and the scheduling instructions can be decoupled. That is, the communication device does not have to configure the scheduling request of one access device before reporting another scheduling request. Instead, the scheduling instructions to be sent are adjusted (i.e., refreshed) after the communication device recognizes that the received scheduling request has been refreshed.

[0149] Furthermore, the aforementioned scheduling instructions can include a specific time. For example, it can be a precise time. Of course, the aforementioned scheduling instructions can also be a time interval. This ensures that access devices in the network can access the network in an orderly manner. At the same time, it also ensures the concurrency of access devices in the network.

[0150] As an example, the scheduling instruction may indicate the start time of the available time by a timestamp. For example, the access device reads the timestamp (a specific time) in the scheduling instruction and can determine the start time of the available time.

[0151] As an example, the scheduling instruction may indicate the start time of the usable duration by the end time. For example, the access device may obtain the start time of the usable duration by subtracting the usable duration from the end time.

[0152] As an example, the scheduling instruction can indicate the start time of the available duration through a delay time (or offset time), or indicate the delay time for the scheduling control to take effect through a delay time, and the unit can be microseconds. The delay time can be counted from the time the access device receives the scheduling instruction. After the delay time indicated by the scheduling instruction, the access device can determine the start time of the available duration (the time when the scheduling control takes effect). For example, if the delay time in the scheduling instruction is 5 microseconds, the access device starts counting 5 microseconds after receiving the scheduling instruction, and can determine the start time of the available duration (or the time when the scheduling control takes effect).

[0153] The first field in the scheduling instruction can indicate the delay time, which occupies 4 bytes. When the first field is all FF, it means that the scheduling control takes effect immediately (or the start time of the available time is the moment when the access device receives the scheduling instruction), that is, the delay time is 0.

[0154] The time when the access device receives the scheduling instruction may be the time when the access device receives the scheduling instruction through the optical interface, or the time when the access device processes the scheduling instruction internally (software or hardware) and identifies the delay time.

[0155] Based on the above steps 601 and 602, access devices can transmit in an orderly manner, thereby avoiding the uncertainty caused by channel conflicts caused by competing channels on the service transmission of access devices. Alternatively, access devices can also be orderly and concurrent, thereby improving the concurrency performance of the network. Through the above communication method, the air interface resources to be scheduled for any access device can be determined, and by calling the corresponding instructions, the access device can transmit services according to the determined air interface resources, thereby effectively avoiding air interface collisions and enabling multiple communication devices to access in an orderly or concurrent manner, greatly improving the user experience.

[0156] For example, refer to Figure 10 As shown, the embodiment of the present application also provides a schematic diagram of a communication device. For the sake of convenience, in the following embodiments of the present application, the communication device is identified as a communication device 10, which should not be used to limit the embodiments of the present application. Figure 10 As shown, the communication device 10 includes: an interface unit 1001 and a processing unit 1002. The processing unit 1002 is configured to determine the air interface resource requirements of at least one access device; the air interface resources are used to indicate the air interface resources that the at least one access device needs to utilize; the interface unit 1001 is configured to send a scheduling instruction to the at least one access device based on the air interface resource requirements obtained by the processing unit 1002, wherein the scheduling instruction is used to indicate the duration for which the at least one access device can use the resources and the start time of the duration for which the resources can be used.

[0157] In one possible implementation, the interface unit 1001 is also used to receive reporting information from at least one access device; wherein the reporting information includes a scheduling request from at least one access device, and the scheduling request is used to indicate the time resources that need to be called by at least one access device; the processing unit 1002 is specifically used to determine the air interface resources that need to be called by at least one access device based on the reporting information received by the interface unit 1001.

[0158] In one possible implementation, the interface unit 1001 is also used to obtain service information of at least one access device; wherein the service information includes queue information of the service transmitted by at least one access device; the processing unit 1002 is specifically used to determine the air interface resources that need to be called by at least one access device based on the service information obtained by the interface unit 1001.

[0159] In one possible implementation, the interface unit 1001 is also used to obtain interaction information between at least one access device and other communication devices; wherein the interaction information includes the signal strength between at least one access device and other communication devices; the processing unit 1002 is specifically used to determine the air interface resources that need to be called by at least one access device based on the interaction information obtained by the interface unit 1001.

[0160] In one possible implementation, the interface unit 1001 is also used to receive the device cache and transmission rate sent by at least one access device; the processing unit 1002 is also used to determine the time resources that need to be called by at least one access device based on the device cache and transmission rate received by the interface unit 1001.

[0161] In one possible implementation, the interface unit 1001 is specifically used to receive queue information reported by at least one access device; the processing unit 1002 is used to determine the service information of at least one access device based on the queue information received by the interface unit 1001; or, the interface unit 1001 is specifically used to obtain queue entry information and queue exit information for service transmission of at least one access device; the processing unit 1002 is used to determine the service information of at least one access device based on the queue entry information and queue exit information obtained by the interface unit 1001.

[0162] In a possible implementation manner, the communication device includes any one of the following: a gateway or an optical line terminal.

[0163] The interface unit 1001 is further configured to execute the communication method described in step 601; the processing unit 1002 is further configured to execute the communication method described in step 602. It is understood that the communication device can directly refer to the above Figure 7 The description of the various functions and effects in the communication method shown will not be repeated here.

[0164] For example, refer to Figure 11 As shown, the embodiment of the present application also provides a schematic diagram of a communication device, which is applied to an access device. For ease of explanation, in the following embodiments of the present application, the communication device is identified as a communication device 20, which should not be used to limit the embodiments of the present application. Figure 11 As shown, the communication device 20 includes: an interface unit 1101 and a processing unit 1102. The interface unit 1101 is configured to receive a scheduling instruction sent by the communication device; the processing unit 1102 is configured to transmit a service according to the scheduling instruction received by the interface unit 1101, wherein the scheduling instruction is used to indicate the duration of time during which the access device can be used and the start time of the available time.

[0165] In a possible implementation, the interface unit 1101 is further configured to send reporting information to the communication apparatus; wherein the reporting information includes a scheduling request of the access device, and the scheduling request is configured to indicate a time resource that the access device needs to call.

[0166] In a possible implementation, the interface unit 1101 is further configured to send service information to the communication apparatus; wherein the service information includes queue information of the access device.

[0167] In a possible implementation, the interface unit 1101 is further configured to send interaction information between the communication apparatus and other communication devices to the communication device; wherein the interaction information includes signal strength between at least one access device and other communication devices.

[0168] In a possible implementation, the interface unit 1101 is further configured to send its own device buffer and transmission rate to the communication apparatus.

[0169] In a possible implementation, the interface unit 1101 is further configured to send queue information to the communication device.

[0170] In a possible implementation, the interface unit 1101 is further configured to receive a test message sent by a communication device; and the processing unit 1102 is further configured to determine the signal strength with other communication devices based on the test message received by the interface unit 1101 .

[0171] It is understood that the communication device can directly refer to the above Figure 7 The description of the various functions and effects in the communication method shown will not be repeated here.

[0172] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). In an embodiment of the present application, the computer may include the device described above.

[0173] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0174] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that: Applied to a communication device, the communication method includes: Obtaining service information of at least one access device; A scheduling instruction is sent to the at least one access device based on the service information, where the scheduling instruction is used to allocate air interface resources to the at least one access device, where the air interface resources include an offset time.

2. The communication method according to claim 1, wherein: The offset time is indicated by the first field of the scheduling instruction, and the first field occupies 4 bytes.

3. The communication method according to claim 2, wherein: The start time is the offset time after the at least one access device receives the scheduling instruction.

4. The communication method according to claim 3, wherein: The first field is all FFs, indicating that the start time is the time when the at least one access device receives the scheduling instruction.

5. The communication method according to any one of claims 1 to 4, characterized in that: The service information includes: service cache information and / or service flow information of the at least one access device.

6. The communication method according to any one of claims 1 to 5, characterized in that: The acquiring of service information of the at least one access device includes: receiving queue information reported by the at least one access device; determining service information of the at least one access device based on the queue information; or, Obtaining queue entry information and queue exit information for service transmission by the at least one access device; Based on the queue enqueue information and the queue dequeue information, service information of the at least one access device is determined.

7. A communication method, characterized in that: Applied to an access device, the communication method includes: receiving a dispatch instruction sent by a communication device; The service is transmitted according to the scheduling instruction, wherein the scheduling instruction is used to allocate air interface resources to the access device, and the air interface resources include an offset time.

8. The communication method according to claim 7, wherein: The offset time is indicated by the first field of the scheduling instruction, and the first field occupies 4 bytes.

9. The communication method according to claim 8, wherein: The start time is the offset time after the access device receives the scheduling instruction.

10. The communication method according to claim 9, wherein: The first field is all FFs, indicating that the start time is the time when the access device receives the scheduling instruction.

11. The communication method according to any one of claims 7 to 10, characterized in that: The communication method further includes: Sending service information to the communication device; wherein the service information includes service cache information or service flow information.

12. The communication method according to any one of claims 7 to 11, characterized in that: The sending of service information to the communication device includes: Send queue information to the communication device, or send queue enqueue information and queue dequeue information for service transmission to the communication device.

13. A communication device, characterized in that: including an interface unit and a processing unit; The processing unit is configured to obtain service information of at least one access device; The interface unit is used to send a scheduling instruction to the at least one access device based on the service information, where the scheduling instruction is used to allocate air interface resources to the at least one access device, and the air interface resources include an offset time.

14. The communication device according to claim 13, wherein: The offset time is indicated by the first field of the scheduling instruction, and the first field occupies 4 bytes.

15. The communication device according to claim 14, wherein: The start time is the offset time after the at least one access device receives the scheduling instruction. The communication device according to claim 15 , wherein: The first field is all FFs, indicating that the start time is the time when the at least one access device receives the scheduling instruction.

17. The communication device according to any one of claims 13 to 16, characterized in that: The service information includes: service cache information and / or service flow information of the at least one access device.

18. The communication device according to any one of claims 13 to 17, characterized in that: The processing unit is configured to: receiving queue information reported by the at least one access device; determining service information of the at least one access device based on the queue information; or, Obtaining queue entry information and queue exit information for service transmission by the at least one access device; Based on the queue enqueue information and the queue dequeue information, service information of the at least one access device is determined.

19. An access device, characterized in that: including an interface unit and a processing unit; The interface unit is configured to receive a scheduling instruction sent by a communication device; The processing unit is configured to transmit a service according to the scheduling instruction received by the interface unit, wherein the scheduling instruction is used to allocate air interface resources to the access device, and the air interface resources include an offset time.

20. The access device according to claim 19, wherein: The offset time is indicated by the first field of the scheduling instruction, and the first field occupies 4 bytes.

21. The access device according to claim 20, characterized in that: The start time is the offset time after the access device receives the scheduling instruction.

22. The access device according to claim 21, characterized in that: The first field is all FFs, indicating that the start time is the time when the access device receives the scheduling instruction.

23. The access device according to any one of claims 19 to 22, characterized in that: The interface unit is further used for: Sending service information to the communication device; wherein the service information includes service cache information or service flow information.

24. The access device according to any one of claims 19 to 23, characterized in that: The interface unit is used to: Send queue information to the communication device, or send queue enqueue information and queue dequeue information for service transmission to the communication device.

Images