Fine-grained time slot negotiation method, system, device and readable storage medium

Abstract

The present invention discloses a fine-grained time slot negotiation method, system, device and readable storage medium, the method specifically comprising: receiving time slot negotiation information sent by a sending node, parsing the time slot negotiation information and obtaining the client id and / or slot id contained therein, the time slot negotiation information including Sbit message, Cbit message, CRbit message, CAbit message; based on the time slot negotiation information, triggering a corresponding event interrupt and calling a processing function in response to the event interrupt from the user layer; based on the processing function, completing the time slot negotiation interaction and updating the time slot configuration. Compared with the prior art, the present invention enables the time slot negotiation itself to be adapted to more scenarios, improving the flexibility and adaptability of the solution. Furthermore, the present invention also enables the user layer to have great convenience in organizing the entire process interaction process according to different requirements in specific business scenarios.

Description

Technical Field

[0001] The present invention belongs to the technical field of electronic communications, and in particular relates to a fine-grained time slot negotiation method, system, device and readable storage medium. Background Art

[0002] The fine-grained fgu technology is led by China Mobile. Based on the Flexe flexible Ethernet technology, the granularity of hard slices is further divided from 5Gbps to 10Mbps to meet the differentiated business carrying requirements such as small bandwidth, high isolation, and high security in scenarios such as 5G+ vertical industry applications and dedicated line services.

[0003] In the prior art, the user layer can only send bandwidth increase commands and bandwidth decrease commands to start dynamic interaction. The subsequent entire set of interaction processes, such as whether to send a CRbit message after receiving an Sbit message, and when to send a Cbit message for switching the table after receiving all CAbit messages, are all handled by the chip SDK itself. The user cannot participate in the whole process and wait for the completion of the dynamic time slot negotiation.

[0004] For different equipment manufacturers, the business usage scenarios of time slot negotiation are different. Therefore, manufacturers hope to participate in the fine-grained negotiation process. For example, in the face of high-precision two-way delay scenarios, after sending the CRbit message, shorten the time of the CAbit message response timeout timer, reduce the number of retransmissions of the CRbit message, etc. These scenarios cannot be implemented on the user side under this architecture and can only be achieved by modifying the chip SDK code. Moreover, the SDK cannot predict all application scenarios in the existing network, so the code needs to be modified multiple times and multiple versions need to be maintained, which puts great pressure on delivery.

[0005] Therefore, in view of the above technical problems, it is necessary to provide a dynamically configurable time slot negotiation method.

[0006] The information disclosed in this background technology section is only intended to enhance the understanding of the overall background of the invention and should not be regarded as an acknowledgment or any form of suggestion that the information constitutes the prior art already known to a person skilled in the art. Summary of the invention

[0007] The purpose of the present invention is to provide a fine-grained time slot negotiation method, system, device and readable storage medium, which can greatly facilitate the user layer to organize the entire process interaction process and expand the applicable scenarios of time slot negotiation.

[0008] In order to achieve the above object, a technical solution provided by a specific embodiment of the present invention is as follows:

[0009] In a first aspect, the present invention provides a fine-grained time slot negotiation method, which comprises:

[0010] Receive time slot negotiation information sent by a sending node, parse the time slot negotiation information and obtain the client id and / or slot id contained therein, the time slot negotiation information including Sbit message, Cbit message, CRbit message, and CAbit message;

[0011] Based on the time slot negotiation information, trigger a corresponding event interrupt and call a processing function in response to the event interrupt from a user layer;

[0012] Based on the processing function, the time slot negotiation interaction is completed and the time slot configuration is updated.

[0013] In one or more embodiments provided by the present invention, the method further comprises:

[0014] The node at the upstream maintains a time slot comparison table, which records the client ID of the user in the adjacent downstream node, the time slot bandwidth size sent to the user in the adjacent downstream node, and the slot ID of the time slot.

[0015] In one or more implementations provided by the present invention, if the received time slot negotiation information is an Sbit message, the processing strategy of the user end in response to the time slot negotiation information includes:

[0016] Determine whether there is a user corresponding to the client id in the time slot comparison table maintained by the receiving node;

[0017] If yes, encapsulate and send a CRbit message to the sending node based on the slot id that needs to modify the bandwidth;

[0018] If not, then add the corresponding client id in the time slot comparison table, configure and record the time slot bandwidth size and the time slot id sent to the newly added user, or ignore the Sbit message.

[0019] In one or more implementations provided by the present invention, if the received time slot negotiation information is a CRbit message, the user end responds to the processing strategy of the time slot negotiation information, including:

[0020] If responding to the CRbit message, encapsulating the client id and slot id corresponding to the CRbit message into a CAbit message and sending it to the sending node;

[0021] If the CRbit message is not responded to, the CRbit message is ignored.

[0022] In one or more implementations provided by the present invention, if the received time slot negotiation information is a CAbit message, the user end responds to the processing strategy of the time slot negotiation information, including:

[0023] If the number of CRbit messages sent by this node is the same as the number of CAbit messages received in reply to the CRbit message, a Cbit message is sent to the sending node;

[0024] If the number of the CRbit message sent by the node is inconsistent with the number of the CAbit message received in reply to the CRbit message, the node waits for the next round of CAbit messages until the waiting time threshold is reached.

[0025] In a second aspect, the present invention provides a fine-grained time slot negotiation method, which includes:

[0026] Register multiple interrupt event types and interrupt event processing strategies, wherein the interrupt event types correspond to the interrupt event processing strategies one by one, and convert the interrupt event processing strategies into corresponding interrupt processing functions;

[0027] Receiving a reported interruption event, and if the interruption event belongs to a preset interruption event type, interrupting the negotiation process;

[0028] In response to the callback instruction of the receiving end node, the receiving end node calls the event processing function corresponding to the interrupt event.

[0029] In one or more embodiments provided by the present invention, the method further comprises:

[0030] If the reported interruption event contains a CRbit message, the user attribute corresponding to the client id in the interruption event is recorded, and the receiving node is selected whether to respond to the CRbit message;

[0031] If the reported interruption event includes a CAbit message, determine whether the client id and slot id corresponding to the interruption event are responses to the CRbit message sent by this node, and determine whether the number of CRbit messages sent by this node is consistent with the number of responses received.

[0032] In a third aspect, the present invention further includes a fine-grained time slot negotiation system, comprising:

[0033] A receiving module, used to receive the time slot negotiation information sent by the sending node, parse the time slot negotiation information and obtain the client id and / or slot id contained therein, wherein the time slot negotiation information includes an Sbit message, a Cbit message, a CRbit message, and a CAbit message;

[0034] An interrupt module, configured to trigger a corresponding event interrupt based on the time slot negotiation information and to call a processing function in response to the event interrupt from a user layer;

[0035] The processing module is used to complete the time slot negotiation interaction and update the time slot configuration based on the processing function.

[0036] In a fourth aspect, the present invention also includes a fine-grained time slot negotiation system, comprising:

[0037] A registration module, used to register multiple interrupt event types and interrupt event processing strategies and convert the interrupt event processing strategies into corresponding interrupt processing functions, wherein the interrupt event types correspond to the interrupt event processing strategies one by one;

[0038] An acquisition module, configured to receive a reported interruption event, and if the interruption event belongs to a preset interruption event type, interrupt the negotiation process;

[0039] The response module is used to respond to the callback instruction of the receiving end node, so that the receiving end node calls the event processing function corresponding to the interrupt event.

[0040] In a fifth aspect, the present invention provides a computer device, comprising: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the fine-grained time slot negotiation method by executing the computer instructions.

[0041] Compared with the prior art, the fine-grained time slot negotiation method provided by the present invention divides a whole set of fine-grained handshake processes in the prior art, and by configuring interrupt events, it is possible to interrupt and insert a processing function provided by the user end in the negotiation process, and to perform subsequent processes of negotiation based on the processing function. In different usage scenarios, users can adjust the processing function. Compared with the complexity of recoding the SDK, the adjustment of the processing function is more convenient and effective. The time slot negotiation itself can be adapted to more scenarios, improving the flexibility and adaptability of the solution. Furthermore, the present invention also makes it extremely convenient for the user layer to assemble the entire process interaction process according to different requirements in specific business scenarios.

[0042] On the other hand, in the fine-grained time slot negotiation method provided by the present invention, for the chip SDK, only an interrupt processing function is executed, and no attention is paid to the specific processing of the message in the processing function. This can protect the privacy and security of the user layer to the greatest extent, and is suitable for different users at the same time, reflecting the openness and security required by the dynamic interaction process. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1 is a schematic diagram of a fine-grained time slot negotiation scenario in one embodiment of the present invention;

[0045] Figure 2 is a flow chart of a fine-grained time slot negotiation method in one embodiment of the present invention;

[0046] Figure 3 is a structural block diagram of a fine-grained time slot negotiation system in one embodiment of the present invention;

[0047] Figure 4 is a structural block diagram of an electronic device in one embodiment of the present invention;

[0048] Figure 5 It is a schematic diagram of the process of reducing the bandwidth of small-granular time slots in the prior art;

[0049] Figure 6 is a flow chart of a fine-grained time slot negotiation method in another embodiment of the present invention;

[0050] Figure 7 is a structural block diagram of a fine-grained time slot negotiation system in another embodiment of the present invention;

[0051] Figure 8 is a schematic diagram of bandwidth increase adjustment in one embodiment of the present invention;

[0052] Fig. 9 It is a schematic diagram of bandwidth reduction adjustment in one embodiment of the present invention. DETAILED DESCRIPTION

[0053] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0054] Unless explicitly stated otherwise, throughout the specification and claims, the term “comprise” or variations such as “include” or “comprising”, etc., will be understood to include the stated elements or components but not to exclude other elements or components.

[0055] There are methods for time slot negotiation in the prior art, specifically: Figure 5 As shown, it is a flow chart of reducing the bandwidth of small-granular time slots in the prior art. The PE node sends the message related to the time slot adjustment to the P1 node by encapsulating the adjusted client id and slot id information into a CRbit message. One CRbit message represents the time slot adjustment of the slot in a client. Multiple time slot adjustments require sending multiple CRbit messages. After the P1 node receives the CRbit message with a value of 1 in the receiving end overhead, the time slot to be adjusted is written into the backup table, and the client id and slot id information is encapsulated into a CAbit message and sent back to the PE, indicating that this overhead message can be confirmed to be adjusted. After the PE node confirms that the information and number of the CAbit message are received, the Cbit message is sent. The node switches the table in the next multi-frame header, and the new time slot takes effect. After receiving the Cbit message, the P1 node also switches the table in the next multi-frame header and receives the message with the new time slot table. The dynamic negotiation process ends.

[0056] However, in this technical solution, almost all the message sending and receiving and time slot negotiation processes are handled by the SDK, so the user has relatively little control over the negotiation process. In special business scenarios such as high-precision two-way delay, since the SDK code cannot adapt to all application scenarios in the existing network, it will cause problems such as poor solution adaptability and few adaptation environments. At the same time, under the above architecture, this problem can only be alleviated by modifying the SDK code and maintaining multiple versions, but the SDK code is difficult to modify and cannot take care of all situations.

[0057] The inventor of the present invention has found the main shortcomings of the prior art, and based on the shortcomings of the prior art, has proposed a new technical implementation idea: the negotiation process is divided according to the sending and receiving of messages. The event at the division point is set as an interrupt event. After the corresponding message is uploaded, the negotiation process is interrupted through a preset interrupt function interface. By calling back the event processing function of the user end for the event, the processing strategy of the user end in response to the event in the implementation environment is executed.

[0058] Please refer to Figure 1 , which is a schematic diagram of an application scenario of the fine-grained time slot negotiation method provided by the present invention under an implementation mode, and the scenario specifically includes: a receiving node 101, a sending node 102 and a user terminal 103.

[0059] It should be noted that communication connections are provided between the receiving node 101, the sending node 102 and the user terminal 103, and the communication network derived from the above communication connection may include various connection types, including but not limited to: wired connection, wireless connection or optical fiber cable connection, etc. At the same time, the communication network may be a local area network, a metropolitan area network, a wide area network or any combination of the three.

[0060] It is understandable that the bandwidth adjustment of fgu is actually completed by step-by-step adjustment between adjacent nodes. In the present invention, the negotiation process is divided, and after receiving the corresponding overhead information, the receiving node 101 parses the overhead information and encapsulates it as an interruption event report. After the negotiation process is interrupted, the negotiation process is continued by calling back the corresponding processing function of the user end.

[0061] In the implementation manner of the present invention, the side receiving the overhead information is regarded as the receiving node 101, and the side sending the overhead information is regarded as the sending node 102. That is, in the process of mutual message transmission, the receiving node 101 and the sending node 102 are only used to define the sending and receiving parties for a certain overhead information, and do not specifically refer to a certain fixed node.

[0062] For example, a downstream node sends a time slot increase adjustment notification to an adjacent upstream node. At this time, the sender of the overhead information is the downstream node, and the receiver is the upstream node. Therefore, at this time, the downstream node is the corresponding sending node 102, and the upstream node is the corresponding receiving node 101; after the upstream node responds to the time slot increase adjustment notification, it sends a corresponding time slot adjustment request to the downstream node. At this time, the overhead information is an internship adjustment request, the sender becomes the upstream node, and the receiver becomes the downstream node. Therefore, at this time, the downstream node becomes the receiving node 101, and the upstream node becomes the sending node 102.

[0063] The user terminal 103 is used to enable the user to perform the relevant configurations necessary to implement the fine-grained time slot negotiation described in the present invention, including but not limited to editing the event processing strategy based on the event type, converting the event processing strategy into an event processing function that can be called, and establishing a corresponding relationship between the event processing function and the corresponding time type.

[0064] It should be noted that in the fine-grained time slot negotiation method provided by the present invention, the user terminal 103 not only serves as a platform for parameter setting, but also participates in the implementation process of the scheme. Specifically, if the overhead information received by the receiving node 102 is a CRbit message, the user terminal 103 needs to record the user attributes corresponding to the client id in the interruption event in the locally maintained soft table, and select whether the receiving node responds to the CRbit message; if the overhead information received by the receiving node 102 is a CAbit message, the user terminal 103 needs to determine whether the client id and slot id corresponding to the interruption event are a response to the CRbit message issued by this node, and determine whether the CRbit message issued by this node is consistent with the number of responses received.

[0065] It should also be noted that the user terminal 103 is installed with a computer software program that matches the fine-grained time slot negotiation method provided by this method; the user terminal 103 may include but is not limited to a desktop computer (PC), a desktop computer, a smart phone, a handheld computer, a tablet computer, a personal digital assistant (PDA), and other portable electronic devices or wearable electronic devices, and the embodiments of the present invention do not limit the above contents.

[0066] In addition, the fine-grained time slot negotiation method of the embodiment of the present invention can be applied to the fine-grained time slot negotiation system of the embodiment of the present invention. The fine-grained time slot negotiation system can be configured in a terminal. The terminal can include but is not limited to a PC (Personal Computer), a PDA (tablet computer), a smart phone, a smart wearable device, and the like.

[0067] Please refer to Figure 2 FIG. 1 is a flow chart of fine-grained time slot negotiation in one embodiment of the present invention. The fine-grained time slot negotiation method specifically includes the following steps:

[0068] S201: receiving time slot negotiation information sent by a sending node, parsing the time slot negotiation information and obtaining the client ID and / or slot ID contained therein;

[0069] It should be noted that the time slot negotiation information includes Sbit messages, Cbit messages, CRbit messages, and CAbit messages; specifically, the Sbit message represents a signal from the downstream node to the upstream node requesting the start of the bandwidth increase adjustment process, also known as a time slot increase adjustment notification; the CRbit message represents a time slot adjustment request signal sent by the upstream node to the downstream node; the CAbit message represents a time slot adjustment response signal sent by the downstream node to the upstream node, which is used to respond to the CRbit message sent by the upstream node; the Cbit message represents a time slot validity indication signal sent by the upstream node to the downstream node, and is issued when the number of CRbit messages sent by the upstream node is consistent with the number of CAbit messages sent by the downstream node in response to the above CRbit messages.

[0070] During the time slot negotiation process, fgu completes the negotiation adjustment section by section by transmitting basic unit overhead information between adjacent nodes. The bandwidth adjustment process is divided into two types: bandwidth increase adjustment and bandwidth reduction adjustment. The bandwidth increase adjustment process is completed by first increasing the channel bandwidth and then increasing the effective bandwidth of the service. Figure 8 As shown in FIG. 1 , the bandwidth increase adjustment process is as follows: the network management sends service bandwidth adjustment information to all nodes on the service path, and the service sink PE node starts to increase the channel bandwidth hop by hop toward the upstream node. After the ingress channel bandwidth of the source PE node is adjusted, the effective bandwidth of the service is increased.

[0071] The bandwidth reduction adjustment process is completed by first reducing the effective bandwidth of the service and then reducing the channel bandwidth. Fig. 9 As shown in FIG. 1 , the bandwidth reduction adjustment process is as follows: the network management sends service bandwidth adjustment information to all nodes on the service path, first reducing the effective bandwidth of the service, and then the source PE node of the service starts to reduce the channel bandwidth hop by hop to the downstream node. After the egress channel bandwidth of the sink PE node is adjusted, the whole process is completed.

[0072] Furthermore, the present invention interrupts the negotiation process to segment the negotiation flow. In each segmented negotiation flow, since the time slot negotiation information sent by the sending node is different, the time slot configuration adjustment information that the receiving node expects to obtain after receiving the corresponding overhead information is also different.

[0073] For example, when the information sent by the sending node is an Sbit message, the message indicates that the current sending node needs to increase the bandwidth. Therefore, when the receiving node receives the corresponding Sbit message, it needs to parse and obtain the corresponding user number client id that needs to adjust the bandwidth. The receiving node does not pay attention to the relevant content of the slot id in the Sbit message. When the message sent by the sending node is a CRbit message, it means that the user terminal supports the time slot increase adjustment announcement received by the node in response, or the bandwidth corresponding to the downstream node needs to be reduced at this time. Therefore, the CRbit message must contain the client id and slot id involved in the bandwidth modification. When the receiving node receives the CRbit message, it needs to parse and obtain the corresponding client id and slot id. Further, when the overhead information received by the receiving node is a CAbit message, the user terminal needs to determine whether the current CAbit message is a reply to the CRbit message sent by this node. The judgment is based on the client id and slot id carried in the CAbit message. Therefore, the receiving node needs to parse the corresponding client id and slot id when receiving the CAbit message.

[0074] S202: Based on the time slot negotiation information, trigger a corresponding event interrupt and call a processing function in response to the event interrupt from the user layer.

[0075] In one embodiment of the present invention, after the receiving direction interrupt callback registers the soft interrupt event in the SDK, the user layer generates different processing strategies based on the different types of interrupt events, and registers the event processing function based on the processing strategy. That is, the event processing function corresponds to the type of interrupt event one by one. After uploading the corresponding interrupt event, by identifying the type of interrupt event, the event processing function corresponding to the event can be called back, and by executing the called back event processing function, the subsequent process of time slot negotiation continues.

[0076] Specifically, for different implementation environments, the processing strategies configured for different event types may be the same or different, and the embodiments of the present invention do not limit the configuration of the processing strategies. In an exemplary embodiment of the present invention, if an interrupt is inserted when receiving the time slot negotiation information as an Sbit message, the user end responds to the processing strategy of the time slot negotiation information, including: determining whether there is a user corresponding to the client id in the time slot comparison table maintained by the receiving node; if so, encapsulating and sending a CRbit message to the sending node of the Sbit message based on the slot id whose bandwidth needs to be modified; if not, adding the corresponding client id to the time slot comparison table, configuring and recording the time slot bandwidth size and the slot id of the time slot sent to the newly added user; or ignoring the Sbit message.

[0077] It should be noted that the upstream node maintains a time slot comparison table, which records the client ID of the user in the adjacent downstream node, the time slot bandwidth size sent to the user in the adjacent downstream node, and the slot ID of the time slot. When the sending node sends an Sbit message, it indicates that the user corresponding to the client ID on its node needs to increase the bandwidth. However, at this time, the client ID may or may not exist in the time slot comparison table maintained by the receiving node. If the user is a newly created user and the user has not been allocated any bandwidth, the user may not be recorded in the adjacent upstream node.

[0078] Since receiving the Sbit message does not require any action for the current chip status, when the client id in the received Sbit message does not exist in the time slot comparison table of the receiving endpoint, the received Sbit message and the client id are encapsulated into an event. After reporting the interrupt, the user encapsulated in the interrupt function may ignore the Sbit message. Conversely, if the user layer recognizes the newly added user, the corresponding client id can also be added to the time slot comparison table on the receiving node side, and the time slot bandwidth size and the slot id of the time slot sent to the newly added user can be configured and recorded.

[0079] On the other hand, when the client id in the received Sbit message exists in the receiving endpoint time slot comparison table, the user can still make a decision to ignore the received S message based on the actual usage environment. However, the CRbit message can also be encapsulated and sent to the sending node based on the slot id that needs to modify the bandwidth.

[0080] The present invention interrupts the original fixed negotiation process through the above technical means, and uses the decision of the user layer as the basis for negotiation, so that the fine-grained time slot negotiation solution can be applied to different implementation environments. The increase in the proportion of user decisions also reduces the pressure of SDK writing, which reduces the pressure of solution delivery, but improves flexibility.

[0081] Similarly, if an interrupt is inserted when the received time slot negotiation information is a CRbit message, the user end responds to the processing strategy of the time slot negotiation information, including: if responding to the CRbit message, encapsulating the clientid and slot id corresponding to the CRbit message into a CAbit message and sending it to the sending node; if not responding to the CRbit message, ignoring the CRbit message. If an interrupt is inserted when the received time slot negotiation information is a CAbit message, the user end responds to the processing strategy of the time slot negotiation information, including: if the number of CRbit messages sent by this node is consistent with the number of CAbit messages received in reply to the CRbit message, sending a Cbit message to the sending node; if the number of CRbit messages sent by this node is inconsistent with the number of CAbit messages received in reply to the CRbit message, waiting for the next round of CAbit messages until the waiting time threshold is reached.

[0082] The setting of the waiting time threshold is used to prevent one side node from being in a waiting state for a long time and interfering with the subsequent negotiation process. When a node waits for a period of time greater than or equal to the corresponding waiting time threshold, the message received in this round of negotiation is discarded and the negotiation is deemed to have failed.

[0083] S203: Based on the processing function, complete the time slot negotiation interaction and update the time slot configuration.

[0084] As described above, the processing function is generated based on the user's processing strategy for different interruption events. The callback and application of the processing function can be implemented based on the callback function, which is not limited in the embodiment of the present invention.

[0085] Please refer to Figure 6 FIG. 1 is a flow chart of fine-grained time slot negotiation in another embodiment of the present invention. The fine-grained time slot negotiation method specifically includes the following steps:

[0086] S601: register multiple interrupt event types and interrupt event processing strategies, wherein the interrupt event types correspond to the interrupt event processing strategies one by one, and convert the interrupt event processing strategies into corresponding interrupt processing functions;

[0087] It should be noted that the negotiation process can be divided into different stages for different usage scenarios, and some processes that do not require special processing in the current environment may not be divided, so as to reduce the load pressure of the user terminal and improve the fluency of the negotiation process to a certain extent. The embodiment of the present invention does not limit the specific division method of the negotiation process.

[0088] For example, in one implementation scenario, the bandwidth that can be allocated upstream is small. Therefore, when receiving an Sbit message, a prudent judgment is required. At this time, only the reception of the Sbit message can be set as an interrupt event. When the upstream node receives the Sbit message, an interrupt is triggered. Based on the user side, it is decided whether to ignore the message or respond to the message, and then the corresponding processing function is called back to continue the subsequent negotiation process.

[0089] It should also be noted that the interrupt event processing strategy is converted into a corresponding interrupt processing function, that is, the processing strategy of the corresponding time is converted into a function that can be called, identified and executed. For example, the user can encapsulate the above strategy processing flow in the interrupt processing function. The embodiment of the present invention does not limit the conversion method.

[0090] S602: receiving a reported interruption event, and if the interruption event belongs to a preset interruption event type, interrupting the negotiation process;

[0091] It should be noted that before the negotiation process starts, the SDK will register the soft interrupt time based on the segmentation of the time slot negotiation process in response to user instructions. Then, at the segmentation point corresponding to the negotiation process, the corresponding time slot configuration adjustment information and time slot negotiation information are encapsulated as interrupt events and uploaded. If the uploaded event information is identified as a preset interrupt event, the central processor is notified through the preset function interface to perform interrupt processing, so as to realize the active triggering of the time slot negotiation interrupt.

[0092] S603: In response to the callback instruction of the receiving end node, the receiving end node calls the event processing function corresponding to the interrupt event.

[0093] It should be noted that, in one implementation mode, the same interrupt event may correspond to multiple event processing functions. Therefore, before calling back the event processing function corresponding to the interrupt event, the user layer will also participate in determining which event processing function to call back corresponding to the interrupt event based on internal and / or external factors such as the macro situation and usage environment.

[0094] In an exemplary embodiment of the present invention, if the reported interruption event includes a CR, the user attributes corresponding to the client id in the interruption event are recorded, and the receiving node is selected whether to respond to the CR based on factors such as the allocatable bandwidth of the upstream node; if there is no response, the current negotiation fails and waits for the next negotiation.

[0095] If the reported interruption event contains CA, it is necessary to determine whether the client id and slotid corresponding to the interruption event are responses to the CR issued by this node, and whether the number of CRs issued by this node is consistent with the number of responses received, and then decide whether to enter the next negotiation process.

[0096] Please refer to Figure 3 As shown, based on the same inventive concept as the aforementioned fine-grained time slot negotiation method, an embodiment of the present invention provides a fine-grained time slot negotiation system 300 , which includes: a receiving module 301 , an interrupt module 302 and a processing module 303 .

[0097] Specifically, the receiving module 301 is used to receive the time slot negotiation information sent by the sending node, parse the time slot negotiation information and obtain the client id and / or slot id contained therein, and the time slot negotiation information includes Sbit message, Cbit message, CRbit message, and CAbit message; the interrupt module 302 is used to trigger the corresponding event interrupt based on the time slot negotiation information and call the processing function in response to the event interrupt from the user layer; the processing module 303 is used to complete the time slot negotiation interaction based on the processing function, and update the time slot configuration.

[0098] Please refer to Figure 7 As shown, based on the same inventive concept as the fine-grained time slot negotiation method in another embodiment described above, the present invention provides another fine-grained time slot negotiation system 700 , which includes: a registration module 701 , an acquisition module 702 and a response module 703 .

[0099] Specifically, the registration module 701 is used to register multiple interrupt event types and interrupt event processing strategies and convert the interrupt event processing strategies into corresponding interrupt processing functions, and the interrupt event types correspond to the interrupt event processing strategies one by one; the acquisition module 702 is used to receive reported interrupt events, and if the interrupt event belongs to a preset interrupt event type, the interrupt negotiation process is interrupted; the response module 703 is used to respond to the callback instruction of the receiving end node, so that the receiving end node calls the event processing function corresponding to the interrupt event.

[0100] Please refer to Figure 4 As shown, an embodiment of the present invention further provides an electronic device 400, which includes at least one processor 401, a memory 402 (for example, a non-volatile memory), a memory 403, and a communication interface 404, and the at least one processor 401, the memory 402, the memory 403, and the communication interface 404 are connected together via a bus 405. At least one processor 401 is used to call at least one program instruction stored or encoded in the memory 402, so that the at least one processor 401 performs various operations and functions of the fine-grained time slot negotiation method described in various embodiments of this specification.

[0101] In an embodiment of the present specification, the electronic device 400 may include, but is not limited to, a personal computer, a server computer, a workstation, a desktop computer, a laptop computer, a notebook computer, a mobile electronic device, a smart phone, a tablet computer, a cellular phone, a personal digital assistant (PDA), a handheld device, a messaging device, a wearable electronic device, a consumer electronic device, and the like.

[0102] An embodiment of the present invention further provides a computer-readable medium carrying computer-executable instructions. When the computer-executable instructions are executed by a processor, they can be used to implement various operations and functions of the fine-grained time slot negotiation method described in various embodiments of this specification.

[0103] The computer-readable medium in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device.

[0104] In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, device, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0105] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0106] The present invention is described with reference to flowcharts and / or block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as a combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0107] The foregoing description of specific exemplary embodiments of the present invention is for the purpose of illustration and demonstration. These descriptions are not intended to limit the present invention to the precise form disclosed, and it is clear that many changes and variations can be made based on the above teachings. The purpose of selecting and describing the exemplary embodiments is to explain the specific principles of the present invention and its practical application, so that those skilled in the art can realize and utilize various different exemplary embodiments of the present invention and various different selections and changes. The scope of the present invention is intended to be limited by the claims and their equivalents.

[0108] It will be apparent to those skilled in the art that the invention is not limited to the details of the exemplary embodiments described above and that the invention can be implemented in other specific forms without departing from the spirit or essential features of the invention. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description, and it is intended that all variations falling within the meaning and scope of the equivalent elements of the claims be included in the invention. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

[0109] In addition, it should be understood that although the present specification is described according to implementation modes, not every implementation mode contains only one independent technical solution. This description of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment may also be appropriately combined to form other implementation modes that can be understood by those skilled in the art.

Claims

1. A fine-grained time slot negotiation method, characterized in that: include: Receive time slot negotiation information sent by a sending node, parse the time slot negotiation information and obtain the clientid and / or slot id contained therein, the time slot negotiation information including Sbit message, Cbit message, CRbit message, and CAbit message; Based on the time slot negotiation information, trigger a corresponding event interrupt and call a processing function in response to the event interrupt from a user layer; Based on the processing function, the time slot negotiation interaction is completed and the time slot configuration is updated.

2. The fine-grained time slot negotiation method according to claim 1, characterized in that: The method further comprises: The node at the upstream maintains a time slot comparison table, which records the clientid of the user in the adjacent downstream node, the time slot bandwidth size sent to the user in the adjacent downstream node, and the slotid of the time slot.

3. The fine-grained time slot negotiation method according to claim 2, characterized in that: If the received time slot negotiation information is an Sbit message, the user end responds to the processing strategy of the time slot negotiation information, including: Determine whether there is a user corresponding to the clientid in the time slot comparison table maintained by the receiving node; If yes, then encapsulate and send a CRbit message to the sending node based on the slotid that needs to modify the bandwidth; If not, then add the corresponding clientid in the time slot comparison table, configure and record the time slot bandwidth size and the time slot slotid sent to the newly added user, or ignore the Sbit message.

4. The fine-grained time slot negotiation method according to claim 1, characterized in that: If the received time slot negotiation information is a CRbit message, the user end responds to the processing strategy of the time slot negotiation information, including: If responding to the CRbit message, encapsulating the client id and slot id corresponding to the CRbit message into a CAbit message and sending it to the sending node; If the CRbit message is not responded to, the CRbit message is ignored.

5. The fine-grained time slot negotiation method according to claim 1, characterized in that: If the received time slot negotiation information is a CAbit message, the user end responds to the processing strategy of the time slot negotiation information, including: If the number of CRbit messages sent by this node is the same as the number of CAbit messages received in reply to the CRbit message, a Cbit message is sent to the sending node; If the number of the CRbit message sent by the node is inconsistent with the number of the CAbit message received in reply to the CRbit message, the node waits for the next round of CAbit messages until the waiting time threshold is reached.

6. A fine-grained time slot negotiation method, characterized in that: include: Register multiple interrupt event types and interrupt event processing strategies, wherein the interrupt event types correspond to the interrupt event processing strategies one by one, and convert the interrupt event processing strategies into corresponding interrupt processing functions; Receiving a reported interruption event, and if the interruption event belongs to a preset interruption event type, interrupting the negotiation process; In response to the callback instruction of the receiving end node, the receiving end node calls the event processing function corresponding to the interrupt event.

7. The fine-grained time slot negotiation method according to claim 1, characterized in that: The method further comprises: If the reported interruption event contains a CRbit message, the user attribute corresponding to the client id in the interruption event is recorded, and the receiving node is selected whether to respond to the CRbit message; If the reported interruption event includes a CAbit message, it is determined whether the client id and slotid corresponding to the interruption event are responses to the CRbit message sent by this node, and whether the number of CRbit messages sent by this node is consistent with the number of responses received.

8. A fine-grained time slot negotiation system, characterized in that: include: A receiving module, used to receive the time slot negotiation information sent by the sending node, parse the time slot negotiation information and obtain the clientid and / or slotid contained therein, wherein the time slot negotiation information includes an Sbit message, a Cbit message, a CRbit message, and a CAbit message; An interrupt module, configured to trigger a corresponding event interrupt based on the time slot negotiation information and to call a processing function in response to the event interrupt from a user layer; The processing module is used to complete the time slot negotiation interaction and update the time slot configuration based on the processing function.

9. A fine-grained time slot negotiation system, characterized in that: include: A registration module, used to register multiple interrupt event types and interrupt event processing strategies and convert the interrupt event processing strategies into corresponding interrupt processing functions, wherein the interrupt event types correspond to the interrupt event processing strategies one by one; An acquisition module, used for receiving a reported interruption event, and if the interruption event belongs to a preset interruption event type, interrupting the negotiation process; The response module is used to respond to the callback instruction of the receiving end node, so that the receiving end node calls the event processing function corresponding to the interrupt event.

10. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the fine-grained time slot negotiation method according to any one of claims 1 to 7 by executing the computer instructions.

Images