A method and apparatus for sending service messages

Abstract

This application discloses a service message transmission method and apparatus to reduce end-to-end latency in service transmission and accelerate service message transmission. The method includes: receiving a first service message, the first service message including first service characteristic information; and transmitting the first service message through a first queue according to the first service characteristic information; wherein the transmission priority of the first queue meets the transmission requirements of the first service message. This application's solution is widely applicable to fields such as communication technology, artificial intelligence, vehicle networking, and smart home networking.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and apparatus for sending service messages. Background Technology

[0002] With the rapid development of wireless broadband technology, in order to meet the requirements of wide coverage and high throughput performance of wireless broadband technology, the collaborative networking of multiple wireless devices has gradually become an industry trend. Among them, the master-slave hybrid networking is a typical example.

[0003] A master-slave hybrid network topology can include: a master access point (AP), slave APs, and workstations (STAs). STAs can transmit services to the network through slave APs or the master AP, or vice versa.

[0004] However, different STAs or the same STA transmitting different services to the network may have different end-to-end latency. Therefore, how to reduce the end-to-end latency of service transmission and improve user experience has become an urgent problem to be solved. Summary of the Invention

[0005] This application provides a service message sending method and apparatus to reduce end-to-end latency in service transmission and accelerate service message transmission.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] In a first aspect, a method for sending a service message is provided, the method comprising: receiving a first service message, the first service message including first service characteristic information; sending the first service message through a first queue according to the first service characteristic information; wherein the sending priority of the first queue satisfies the sending requirements of the first service message.

[0008] Based on the method described in the first aspect, the first service message can be sent out through the first queue according to the first service characteristic information, and the sending priority meets the sending requirements of the first service message, so that the uplink service message is sent to the main AP according to the sending priority, thereby reducing the end-to-end transmission latency of the uplink service message.

[0009] In one possible design, the method further includes: determining a first feature marker based on the service feature information of the first service message and a first relationship; sending the first service message according to the first queue corresponding to the first feature marker; the first relationship includes the correspondence between service feature information and feature markers; the feature marker is used to indicate the queue for sending the service message; different feature markers indicate queues with different priorities.

[0010] Based on this possible design, the first service message can be sent into queues of different priorities according to the corresponding first feature mark, thereby improving the transmission rate of the service message.

[0011] In one possible design, the method further includes: receiving a second service message, the second service message including second service feature information and a second feature tag; and recording the second service feature information and the second feature tag into a record of the first relationship.

[0012] Based on this possible design, the correspondence between existing service feature information and feature tags can be stored in the first relationship, so that subsequently received service packets can quickly match the corresponding feature tags and enter the priority queue for transmission, thereby improving the transmission rate of service packets.

[0013] In one possible design, the first relationship also includes a timestamp, which is used to determine the validity of the correspondence between business feature information and feature tags in the first relationship.

[0014] Based on this possible design, the validity of the correspondence between business feature information and feature tags in the first relationship can be determined according to the timestamp, ensuring that business messages are sent on the appropriate queue.

[0015] In one possible design, the method further includes: calculating the time difference between the timestamp and the current time; when the time difference is greater than or equal to a first preset time, determining that the correspondence between the business feature information and the feature tag is invalid; when the time difference is less than the first preset time, determining that the correspondence between the business feature information and the feature tag is valid.

[0016] Based on this possible design, the correspondence between invalid business feature information and feature tags can be deleted in a timely manner, saving device memory space.

[0017] In one possible design, the method further includes: receiving a third service message, the third service message including third service feature information and a third feature tag; if the third service feature information is included in the first relationship, and the feature tag corresponding to the third service feature information in the first relationship is different from the third feature tag, then updating the feature tag and / or timestamp corresponding to the third service feature information in the first relationship.

[0018] Based on this possible design, the correspondence between business feature information and feature tags in the first relationship can be updated to ensure the accuracy of the business feature information and feature tags recorded in the first relationship, so that the business message can be mapped to the appropriate queue and sent out according to the updated business feature information and feature tags.

[0019] In one possible design, the first service characteristic information includes one or more of the following: source Internet Protocol IP address, source port, destination Internet Protocol IP address, destination port, and protocol number.

[0020] Based on this possible design, the business characteristic information may include one or more parameters, which can flexibly and effectively indicate the business characteristics of the business message.

[0021] Secondly, a service message sending device is provided. In one possible design, the service message sending device includes: a receiving unit for receiving a first service message, the first service message including first service characteristic information; and a sending unit for sending the first service message through a first queue according to the first service characteristic information; wherein the sending priority of the first queue satisfies the sending requirements of the first service message.

[0022] In one possible design, the apparatus further includes a processing unit; the processing unit is configured to determine a first feature marker based on the service feature information of the first service message and a first relationship; the sending unit is further configured to send the first service message according to the first queue corresponding to the first feature marker; the first relationship includes the correspondence between service feature information and feature markers; the feature marker is used to indicate the queue for sending the service message; different feature markers indicate queues with different priorities.

[0023] In one possible design, before receiving the first service message, the receiving unit is further configured to receive a second service message, the second service message including second service feature information and a second feature tag; the processing unit is configured to record the second service feature information and the second feature tag into a record of the first relationship.

[0024] In one possible design, the first relationship also includes a timestamp, which is used to determine the validity of the correspondence between business feature information and feature tags in the first relationship.

[0025] In one possible design, the processing unit is further configured to calculate the time difference between the timestamp and the current time; when the time difference is greater than or equal to a first preset time, the correspondence between the business feature information and the feature tag is determined to be invalid; when the time difference is less than the first preset time, the correspondence between the business feature information and the feature tag is determined to be valid.

[0026] In one possible design, the receiving unit is further configured to receive a third service message, the third service message including third service feature information and a third feature tag; if the third service feature information is included in the first relationship, and the feature tag corresponding to the third service feature information in the first relationship is different from the third feature tag, then the feature tag and / or timestamp corresponding to the third service feature information in the first relationship are updated.

[0027] In one possible design, the first service characteristic information includes one or more of the following: source Internet Protocol IP address, source port, destination Internet Protocol IP address, destination port, and protocol number.

[0028] The technical effects of any design method in the second aspect can be found in the first aspect or the technical effects of any possible design in the first aspect, and will not be repeated here.

[0029] Thirdly, a communication device is provided, which can be a terminal or a chip or system-on-a-chip in a terminal. The terminal includes one or more processors and one or more memories. The one or more memories are coupled to the one or more processors and are used to store computer program code, which includes computer instructions. When the one or more processors execute the computer instructions, they cause the terminal to perform the service message transmission method as described in the first aspect or any possible design of the first aspect.

[0030] Fourthly, a computer-readable storage medium is provided, which may be a readable non-volatile storage medium storing instructions that, when executed on a computer, cause the computer to perform the service message transmission method described in the first aspect or any possible design of the above aspects.

[0031] Fifthly, embodiments of this application provide a communication system that may include: a master AP, slave APs, and STAs. The communication system includes a communication device or readable storage medium as described in any one of the second to fourth aspects, and can execute the service message transmission method described in any possible design of the first aspect. Attached Figure Description

[0032] Figure 1 This is a schematic diagram of a downlink service message sending method;

[0033] Figure 2 A simplified schematic diagram of a communication system provided in an embodiment of this application;

[0034] Figure 3 A schematic diagram of a communication device provided in an embodiment of this application;

[0035] Figure 4 A flowchart illustrating a service message sending method provided in this application embodiment;

[0036] Figure 5 A flowchart illustrating yet another service message sending method provided in this application embodiment;

[0037] Figure 6 A schematic diagram illustrating a service message sending method provided in an embodiment of this application;

[0038] Figure 7 This is a schematic diagram of the composition of a communication device provided in an embodiment of this application;

[0039] Figure 8 This is a schematic diagram of the composition of a communication system provided in an embodiment of this application. Detailed Implementation

[0040] The terms "first," "second," and "third," etc., used in this application specification, claims, and the aforementioned drawings are used to distinguish different objects, not to limit a specific order.

[0041] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0042] Before introducing the embodiments of this application, some terms involved in the embodiments of this application will be explained:

[0043] Wireless Fidelity (Wi-Fi) is a wireless connectivity technology that allows personal computers, handheld devices (such as mobile phones and tablets), and other terminals to access the network. Wi-Fi is a short-to-medium range wireless technology, typically using the 2.4 GHz ultra-high frequency (UHF) or 5 GHz super-high frequency (SHF) radio frequency bands. Currently, the two available Wi-Fi standards are IEEE 802.11a and IEEE 802.11b.

[0044] In Wi-Fi technology, hybrid networking can be used to achieve wide-area, high-throughput performance. A typical hybrid networking method is the master-slave hybrid network. A master-slave hybrid network refers to a network where master access devices and slave access devices are deployed together. It should be noted that in this embodiment, the terms "master access device" and "slave AP" are relative concepts, determined based on the function and / or deployment location of the access devices. The master access device can manage the access of all or most devices in the entire local area network, integrating basic functions such as connection and forwarding, as well as service processing functions. The master access device can be deployed in a core location of the network, such as a location close to the core network. Slave access devices can cooperate with the master access device to complete service functions, forwarding packets to the next-level device. They generally integrate basic connection and forwarding functions and can be deployed at the edge of the network.

[0045] Furthermore, this application is not limited to the naming of primary access device and secondary access network device. Alternatively, the primary access network device may be called the primary access point (AP), and the secondary access network device may be called the secondary access point.

[0046] In this embodiment, the workstation (STA) can access the main AP or slave AP via Wi-Fi technology, and the services transmitted between the main AP or slave AP and the network can be called Wi-Fi multimedia (WMM) services. To optimize network communication quality and ensure a stable connection between the terminal and network resources, WMM services can be divided into the following four categories: voice (VO) services, video (VI) services, best effort (BE) services, and background (BK) services.

[0047] In this embodiment, different types of services have different latency requirements and transmission priorities. Low-latency services have higher transmission priorities, while high-latency services can have relatively lower transmission priorities. For example, among the four types of services mentioned above, VO services have higher end-to-end transmission latency requirements in the network, while BK services have lower latency requirements. Correspondingly, the transmission priority order of these four types of services can be: VO service > VI service > BE service > BK service.

[0048] When the network transmits different types of services to the STA, it can send them to the STA according to the transmission priority of different services. For example, Figure 1 This is a diagram illustrating the network sending downlink service packets to the STA. (Refer to...) Figure 1 The process may include the following steps: ① The network sends downlink service packets to the primary AP. ② After receiving the downlink service packets, the primary AP identifies the service type of the received downlink service packets and adds different feature tags to downlink service packets of different categories. These feature tags are used to identify the transmission priority of the service packets. ③ The primary AP sends the downlink service packets with added feature tags to the secondary AP via wired or wireless transmission. For example, when transmitting wirelessly, the primary AP can send the downlink service packets to the secondary AP through the WMM queue corresponding to the feature tags carried in the downlink service packets, based on the feature tags. ④ After receiving the downlink service packets from the primary AP, the secondary AP sends the downlink service packets to the STA through the WMM queue corresponding to the feature tags carried in the downlink service packets, based on the feature tags.

[0049] Figure 1 The steps shown support sending downlink service packets to STAs according to transmission priority between the AP and STA, thereby improving the transmission rate of downlink service packets. However, for uplink service packets, there is no corresponding transmission method to send uplink service packets to the network according to transmission priority, and the accelerated end-to-end transmission of service packets in the uplink cannot be guaranteed.

[0050] To accelerate the transmission of uplink service packets, embodiments of this application provide a service packet transmission method. This method may include: after receiving a first service packet including first service characteristic information from an AP, sending the first service packet through a first queue that meets the transmission requirements of the first service packet, based on the first service characteristic information. In this way, the AP can send the received service packets through corresponding priority queues, effectively reducing the end-to-end transmission latency of service packets and achieving accelerated transmission.

[0051] It should be noted that in the embodiments of this application, uplink service messages and downlink service messages are relative concepts. Uplink service messages can refer to service messages sent from STA to the network, and downlink service messages can refer to service messages sent from the network to STA.

[0052] The method for sending service messages provided in the embodiments of this application will now be described with reference to the accompanying drawings.

[0053] The service message transmission method provided in this application can be applied to various communication systems that support master-slave hybrid networking, such as: Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, Wireless Fidelity (Wi-Fi) systems, future communication systems, or systems integrating multiple communication systems, etc., and this application does not limit the application. 5G can also be referred to as New Radio (NR).

[0054] The service message sending method provided in this application embodiment can be applied to various communication scenarios, such as one or more of the following communication scenarios: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), machine type communication (MTC), massive machine type communication (mMTC), device to device (D2D), vehicle to everything (V2X), vehicle to vehicle (V2V), and Internet of Things (IoT).

[0055] The following is based on Figure 2 Taking the communication system shown as an example, the service message sending method provided in this application embodiment is described. For example, refer to... Figure 2 The communication system can include a master-slave hybrid network, which can have a master AP and multiple slave APs. STAs can access the master AP or slave APs via Wi-Fi technology. STAs can include user Wi-Fi terminals, such as mobile phones and tablets. STAs can transmit services to the network through slave APs or the master AP, or STAs can transmit services to the network through the master AP.

[0056] The following is about Figure 2 The network elements or devices involved in the communication system shown are introduced.

[0057] STA can be terminal equipment, user equipment (UE), mobile station (MS), or mobile terminal (MT), etc. Specifically, the terminal can be a mobile phone, tablet computer, or computer with wireless transceiver capabilities. It can also be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, a smart home, or an in-vehicle terminal, etc. In the embodiments of this application, the device used to implement the function of the STA can be the STA itself, or it can be a device that supports the STA in implementing this function, such as a chip system. This device can be installed in the STA or used in conjunction with the STA. The following describes the service message transmission method provided in the embodiments of this application, taking the STA as an example of the device used to implement the function of the STA.

[0058] The primary AP and secondary AP are used to implement at least one of the following functions of STA: resource scheduling, radio resource management, and radio access control. Specifically, the primary AP and secondary AP can include any of the following nodes: base station, radio access point, transmission receive point (TRP), transmission point (TP), evolved Node B (gNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home-evolved Node B, or home Node B (HNB)), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP), and some other access node. In this application embodiment, the device for implementing the function of a slave AP can be a slave AP itself; it can also be a device capable of supporting the slave AP in implementing this function, such as a chip system. This device can be installed in the slave AP or used in conjunction with the slave AP. In the technical solutions provided in this application embodiment, the device for implementing the function of a slave AP is described using a slave AP as an example.

[0059] It should be noted that the above Figure 2 The names of network elements and interfaces between them in the architecture are just examples. In actual implementations, the names of network elements and interfaces between them can be other names, and this application does not impose specific limitations on them. It should be noted that... Figure 2 This is just an example framework diagram. Figure 2 The number of nodes included and the access method of the STAs are unrestricted. Except... Figure 2 In addition to the functional nodes shown, other nodes may also be included, such as core network equipment, etc., without restriction.

[0060] In practical implementation, Figure 2 The network elements shown, such as STA and AP, can adopt... Figure 3 The shown composition or includes Figure 3 The components shown. Figure 3This is a schematic diagram of the structure of a communication device 300 provided in an embodiment of this application. When the communication device 300 has the STA function described in the embodiment of this application, the communication device 300 can be an STA or a chip or system-on-a-chip in an STA. When the communication device 300 has the AP function described in the embodiment of this application, the communication device 300 can be a AP or a chip or system-on-a-chip in a AP.

[0061] like Figure 3 As shown, the communication device 300 may include a processor 301, a communication line 302, and a communication interface 303. Furthermore, the communication device 300 may also include a memory 304. The processor 301, memory 304, and communication interface 303 can be connected via the communication line 302.

[0062] The processor 301 can be a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 301 can also be other devices with processing capabilities, such as circuits, devices, or software modules.

[0063] Communication line 302 is used to transmit information between the components included in communication device 300.

[0064] Communication interface 303 is used to communicate with other devices or other communication networks. These other communication networks can be Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. Communication interface 303 can be a radio frequency module, transceiver, or any device capable of communication.

[0065] Memory 304 is used to store instructions. These instructions can be computer programs.

[0066] The memory 304 can be a read-only memory (ROM) or other type of static storage device that can store static information and / or instructions; it can also be a random access memory (RAM) or other type of dynamic storage device that can store information and / or instructions; it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage, magnetic disk storage medium or other magnetic storage device. Optical disc storage includes compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.

[0067] It should be noted that the memory 304 can exist independently of the processor 301, or it can be integrated with the processor 301. The memory 304 can be used to store instructions, program code, or some data, etc. The memory 304 can be located inside or outside the communication device 300, without limitation. The processor 301 is used to execute the instructions stored in the memory 304 to implement the service message transmission method provided in the following embodiments of this application.

[0068] In one example, processor 301 may include one or more CPUs, for example Figure 3 CPU0 and CPU1 are included. As an optional implementation, the communication device 300 includes multiple processors, for example, besides... Figure 3 In addition to processor 301, it may also include processor 307.

[0069] As an optional implementation, the communication device 300 also includes an output device 305 and an input device 306. The input device 306 is a keyboard, mouse, microphone, or joystick, etc., and the output device 305 is a display screen, speaker, etc.

[0070] It should be noted that the communication device 300 can be a desktop computer, laptop computer, network server, mobile phone, tablet computer, wireless terminal, embedded device, chip system, or other device. Figure 3 Equipment with a similar structure. Furthermore... Figure 3 The structural composition shown does not constitute a limitation on the device for sending service messages, except... Figure 3 In addition to the components shown, the service message sending device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0071] The following is combined with Figure 2 The communication system shown describes the service message transmission method provided in the embodiments of this application. The devices in the following embodiments may have... Figure 3 The components are shown. The actions, terminology, etc., involved in the various embodiments of this application can be referenced interchangeably without limitation. The message names or parameter names in the messages exchanged between devices in the embodiments of this application are merely examples; other names can be used in specific implementations without limitation. For example, "queue" in the following embodiments can be replaced with "priority queue" or "WMM queue," etc.

[0072] Figure 4 A flowchart illustrating a service message sending method provided in this application embodiment, the method can be... Figure 2 Any of the operations can be executed from the AP, for example, by... Figure 2 Executed from AP1, such as Figure 4 As shown, the method may include:

[0073] Step 401: Receive the first service message from the AP.

[0074] The first service message can refer to the uplink service message sent by the STA to the network. This STA can be... Figure 2 In any STA connected to the AP, for example, the first service message can be Figure 2 STA11 sends service messages from AP1.

[0075] The first service message may include first service characteristic information. This first service characteristic information can be used to indicate the service source, destination, and communication protocol used during transmission, thereby ensuring the integrity and reliability of the service message transmission and preventing packet loss. For example, the first service characteristic information may include one or more of the following: source Internet Protocol (IP) address, source port, destination IP address, destination port, and protocol number. The descriptions of the source IP address, source port, destination IP address, destination port, and protocol number are as described in existing texts and will not be repeated here.

[0076] It should be noted that the embodiments of this application are not limited to the naming of business feature information. Business feature information can also be named five-tuple information, such as the first business feature information can be named the first five-tuple information, the second business feature information can be named the second five-tuple information, and so on.

[0077] For example, receiving the first service message from the AP may include: receiving the first service message sent by the STA from the AP via Wi-Fi technology; or receiving the first service message sent by the STA via other wireless access technologies (such as Long Term Evolution (LTE) technology) or wired access technologies.

[0078] Step 402: The AP sends the first service message out through the first queue based on the first service characteristic information.

[0079] The first queue can be one of multiple queues in the AP used for sending service packets. The first queue can be used to send a first service packet, and its sending priority satisfies the sending requirements of the first service packet. These requirements may include one or more of the following: transmission latency requirements and quality of service (QoS). For example, the multiple queues in the AP used for sending service packets may include a first queue, a second queue, a third queue, a fourth queue, etc. Different queues support the sending of different types of service packets, and different queues have different sending priorities. The sending priority of a queue can be determined based on the sending requirements of the service packets it supports. For example, if a queue supports a high demand for service packets, its sending priority is high; if a queue supports a low demand for service packets, its sending priority is low.

[0080] For example, suppose the first queue supports VO service, the second queue supports VI service, the third queue supports BE service, and the fourth queue supports BK service. The order of the four service message sending requirements is: VO service > VI service > BE service > BK service. Therefore, the priority order of the corresponding queues is: first queue > second queue > third queue > fourth queue.

[0081] For example, sending the first service packet out through the first queue from the AP based on the first service feature information may include: the AP determining a first feature tag based on the service feature information of the first service packet and a first relationship, such as the AP using the service feature information of the first service packet as an index to query the first relationship and find the first feature tag that matches the service feature information of the first service packet; the AP sending the first service packet to the network according to the first queue corresponding to the first feature tag or sending the first service packet to the network through the main AP.

[0082] The first relationship can include the correspondence between service feature information and feature tags, where there is a one-to-one correspondence between them. This first relationship can be stored locally on the slave AP. Initially, the first relationship is empty. The correspondence between service feature information and feature tags can be determined by the master AP through the identification of downlink service packets. The master AP then sends the service feature information and its corresponding feature tags to the slave AP in the downlink service packets. When the slave AP receives the downlink service packets from the master AP carrying the service feature information and its corresponding feature tags, it stores / preserves the correspondence between the service feature information and the feature tags in the first relationship. Thus, the slave AP reuses and stores the identification results from the master AP. Specifically, the process of the slave AP generating the first relationship can be referred to below. Figure 5 As described in steps 502 to 504.

[0083] In one possible design, the first relation can be a feature library that stores business feature information and feature tags in tabular form. For example, the first relation can be as shown in Table 1. Referring to Table 1, the first relation can include multiple records, each of which includes the correspondence between business feature information and feature tags. In another possible design, the first relation can be a database that stores business feature information and feature tags in array form, such as the array {Source IP: 10.10.10.10, Source Port: 123, Destination IP: 192.168.3.3, Destination Port: 456, Protocol Number 2, Feature Tag: 0x01}.

[0084] Among them, the feature marker can be used to indicate the sending priority of a service message or the priority of the queue sending the service message. Different feature markers indicate different queue priorities. The feature marker can be the index of its corresponding queue, or it can be the priority marker of its corresponding column, etc.

[0085] Table 1

[0086]

[0087] It should be noted that Table 1 is an exemplary table. In addition to the correspondence between business feature information and feature tags shown in Table 1, other information may be included without restriction.

[0088] For example, taking the first relationship as shown in Table 1 and the feature tag corresponding to queue 1 as 0x01, if after receiving an uplink service message from the AP, the service feature information of the uplink service message is parsed as {source IP: 10.10.10.10, source port: 123, destination IP: 192.168.3.3, destination port: 456, protocol number 2}, the AP can look up Table 1 to find the feature tag corresponding to this service feature information as 0x01, and send it out according to queue 1 marked by 0x01.

[0089] based on Figure 4 The method shown can send the service message through the corresponding sending queue according to the service characteristics information of the service message, so that the downlink service message is sent to the workstation according to the sending priority, and the uplink service message is sent to the main AP according to the sending priority. This reduces the end-to-end transmission latency of the service message and achieves a bidirectional acceleration effect for the transmission of the service message.

[0090] In this embodiment of the application, the first relationship is not limited to the correspondence between business feature information and feature markers, but may also include timestamps and other information. The timestamp can be used to record the time when the correspondence between business feature information and feature markers is saved in the first relationship. The validity of the correspondence between business feature information and feature markers can be determined based on the timestamp, so that the AP can delete and / or update the correspondence between business feature information and feature markers in the first relationship based on the timestamp.

[0091] For example, the first relationship may include one or more records. Each record may include the correspondence between business feature information and feature tags, and may also include a timestamp, which is used to determine the validity of the record or the validity of the correspondence between business feature information and feature tags in the record or the validity of the feature tags in the record.

[0092] Taking a first relationship including a first record, where the first record includes a timestamp and a correspondence between business feature information and feature tags, and the first record can be any record in the first relationship, the following possible design can be used in this application embodiment to determine the validity of the first record: Calculate the time difference between the timestamp included in the first record in the first relationship and the current time from the AP. If the time difference is greater than or equal to a first preset time, determine that the first record is invalid; if the time difference is less than the first preset time, determine that the first record is valid. Further, delete the invalid record corresponding to the timestamp from the first relationship from the AP.

[0093] For example, the AP can periodically calculate the time difference between a timestamp and the current time based on the calculation cycle. This calculation cycle can be preset as needed and is not limited. For instance, the AP can use a timer to set the calculation cycle to 5 seconds, meaning it calculates the time difference between the timestamp of the first record in the first relation and the current time every 5 seconds. The AP can also set a first preset time of 7 seconds. If the AP obtains a time difference of 3 seconds after the first calculation, which is less than the first preset time, then the first record is considered valid at the current time, and the AP continues to retain the first record containing that timestamp in the first relation. After the next calculation cycle, the AP obtains a time difference of 8 seconds after the second calculation, which is greater than the first preset time. This means the first record is invalid at the current time, and the AP deletes the invalid record corresponding to that timestamp from the first relation.

[0094] The first preset time can be set as needed and is not limited. For example, the first preset time can be set by the user according to the system load. For instance, when the communication system is heavily loaded, a shorter first preset time can be set so that invalid records can be deleted from the AP in a timely manner, ensuring the communication transmission rate.

[0095] For example, taking Table 2 below as an example of the first relationship, compared to Table 1 above, the first relationship can also include timestamps t1, t2, t3, and t4. These timestamps correspond to the business feature information and feature tags of each row and are used to record the storage time of the correspondence between business feature information and feature tags. To determine the validity of the record corresponding to timestamp t1 in the relationship shown in Table 2, taking the first preset time as T1 as an example, assuming that the current time when the AP determines the validity of the record is t2, the time difference Δt obtained from the AP is Δt = t2 - t1. If Δt is greater than or equal to T1, the record corresponding to t1 is invalid, and the AP can delete it from Table 2.

[0096] Table 2

[0097]

[0098] It should be noted that Table 2 is an exemplary table, and there is no limit to the number of records included in Table 2. In addition to the correspondence between business feature information and feature tags shown in Table 2, other information may also be included.

[0099] Optionally, during communication, the demand for sending service messages may be dynamically updated, and the queue for sending service messages may need to be adjusted in a timely manner. In order to ensure that service messages are sent on the appropriate queue, the slave AP also needs to update the correspondence between service feature information and feature tags in the first relationship in a timely manner according to the identification result of the master AP, so as to ensure the accuracy of the service feature information and feature tags recorded in the first relationship, and so that the service messages are mapped to the appropriate queue and sent out according to the updated service feature information and feature tags.

[0100] Specifically, the method for updating the correspondence between service feature information and feature tag in the first relationship from the AP may include: receiving a third service message from the AP, the third service message including third service feature information and a third feature tag; if the third service feature information is included in the first relationship, and the feature tag corresponding to the third service feature information in the first relationship is different from the third tag, then updating the feature tag and / or timestamp corresponding to the third service feature information in the first relationship.

[0101] The third service message can be a downlink service message received by the slave AP from the master AP. The master AP can identify the service type of the third service message sent by the network, determine its transmission priority according to the transmission requirements of the service type, and send the third feature tag used to indicate the transmission priority in the third service message to the slave AP.

[0102] For example, taking the first relationship as shown in Table 2 above and the feature marker corresponding to queue 1 as 0x01, after receiving the uplink service message from the AP, the service feature information of the uplink service message is parsed as {source IP: 10.10.10.10, source port: 123, destination IP: 192.168.3.3, destination port: 456, protocol number 2}, and the above service feature information and the corresponding feature marker 0x01 are stored in the record of the first relationship. Assuming this record is valid, the downlink service packet received by the AP at time t5 includes service characteristic information {source IP: 10.10.10.10, source port: 123, destination IP: 192.168.3.3, destination port: 456, protocol number 2} and a feature marker of 0x05. Looking up Table 2 on the AP, the service characteristic information {source IP: 10.10.10.10, source port: 123, destination IP: 192.168.3.3, destination port: 456, protocol number 2} is found. If the feature marker 0x01 corresponding to {Source IP: 10.10.10.10, Source Port: 123, Destination IP: 192.168.3.3, Destination Port: 456, Protocol No. 2} is different from the feature marker 0x05 carried in the downlink service message, then based on the feature marker and timestamp in the first record, the feature marker corresponding to the service feature information {Source IP: 10.10.10.10, Source Port: 123, Destination IP: 192.168.3.3, Destination Port: 456, Protocol No. 2} is updated to 0x05 and the original timestamp t1 is updated to t5. The updated record is shown in Table 3.

[0103] Table 3

[0104]

[0105] It should be noted that Table 3 is an example table, and there is no limit to the number of records included in Table 3. In addition to the correspondence between business feature information and feature tags shown in Table 3, other information may also be included.

[0106] The following example uses a WMM queue, combined with... Figure 5 right Figure 4 The method shown will be described in detail:

[0107] Figure 5 A flowchart of a service message sending method provided in an embodiment of this application is shown below. Figure 5 As shown, the method may include:

[0108] Step 501: The network sends the second service message to the main AP.

[0109] Among them, the network can be Figure 1 The network shown. The main AP can be Figure 1 Any AP accessing the network.

[0110] The second service message can be a service message sent from the network, also known as a downlink service message. This second service message may include second service characteristic information. The parameters included in the second service characteristic information have the same types as those included in the first service characteristic information, but their values ​​may differ, which will not be elaborated upon here. In addition to the second service characteristic information, the second service message may also include a service type identifier, which can be used to identify the service type to which the second service message belongs / corresponds.

[0111] For example, the network can send a second service message to the main AP via wired media such as optical fiber or wireless communication.

[0112] Step 502: The main AP receives the second service message and identifies the service type of the second service message.

[0113] For example, the second service message includes a service type identifier, and the main AP can identify the service type of the second service message based on the service type identifier.

[0114] Step 503: The primary AP sends the secondary AP with the second feature tag corresponding to the service type of the second service message in the second service message.

[0115] In this embodiment of the application, the main AP stores the correspondence between service types and feature tags. For example, the feature tag corresponding to VO service is 0×01, the feature tag corresponding to VI service is 0×02, the feature tag corresponding to BE service is 0×03, and the feature tag corresponding to BK service is 0×04, as shown in Table 4.

[0116] Table 4

[0117] Business type Feature markers VO 0×01 VI 0×02 BE 0×03 BK 0×04

[0118] Step 504: Receive a second service message carrying second service feature information and second feature tag from the AP, and store the second service feature information and second feature information in the first relationship.

[0119] It should be noted that steps 501 to 504 are described using a single downlink service message as an example. It can be understood that multiple downlink service messages can be sent by referring to steps 501 to 504. If multiple service feature information and the correspondence between feature tags are obtained from the AP during the process of multiple downlink service messages, the correspondence between the multiple service feature information and feature tags is recorded in the first relationship.

[0120] Step 505: Send from AP to STA via the WMM queue corresponding to the second feature tag.

[0121] Step 506: The STA sends the first service message to the AP.

[0122] The description of the first service message and the process of the STA sending the first service message can be referred to in step 401, and will not be repeated here.

[0123] Step 507: Receive the first service message carrying the first service characteristic information from the AP.

[0124] The description of the first business characteristic information and the execution process of step 507 are as shown in step 401, and will not be repeated here.

[0125] Step 508: Using the first service feature information as an index, query the first relationship from the AP. If the first service feature information exists in the first relationship and matches the first feature tag corresponding to the first service feature information, then proceed to step 509. Otherwise, if the first service feature information does not exist in the first relationship, then send the first service message to the main AP or the network according to the existing technology.

[0126] Step 509: The AP sends the first service packet to the master AP through the WMM queue corresponding to the first feature tag.

[0127] Step 510: The main AP sends the first service message to the network.

[0128] It should be noted that, Figure 5 The steps in the instructions are optional; you can perform some or all of them without restriction.

[0129] based on Figure 5 The method shown enables the AP to send downlink service packets to the workstation according to the sending priority, and at the same time enables the AP to send uplink service packets to the main AP according to the sending priority, thereby reducing the end-to-end transmission latency of service packets and achieving a bidirectional acceleration effect for service packet transmission.

[0130] For example, Figure 6 To execute Figure 5 The diagram shown illustrates the service message transmission method. Figure 6The process can be summarized as follows: ① The network sends downlink service packets to the primary AP. ② Upon receiving the downlink service packets, the primary AP identifies the service type and adds different feature tags to different categories of downlink service packets. These feature tags are used to identify the transmission priority of the service packets. ③ The primary AP sends the downlink service packets with added feature tags to the secondary AP via wired or wireless transmission. For example, when transmitting wirelessly, the primary AP can send the downlink service packets to the secondary AP through the WMM queue corresponding to the feature tags carried in the downlink service packets. ④ After receiving the downlink service packets from the primary AP, the secondary AP parses the service feature information and feature tags of the service packets and stores the correspondence between the service feature information and feature tags in the secondary AP, such as in the feature library shown in Table 1. ⑤ The secondary AP sends the downlink service packets to the STA through the WMM queue corresponding to the feature tags carried in the downlink service packets. ⑥ The STA sends uplink service packets to the secondary AP. ⑦ The secondary AP matches the service feature information of the uplink service packets with the corresponding feature tags in the secondary AP's feature library. ⑧ The AP sends the uplink service packet to the primary AP through the WMM queue corresponding to the matching feature tag. ⑨ The primary AP sends the uplink service packet to the network.

[0131] and Figure 1 compared to, Figure 6 The steps shown support sending downlink service packets to STAs according to their sending priority between AP and STA, and also support sending uplink service packets to the main AP according to their sending priority between AP and main AP. This can simultaneously improve the transmission rate of both downlink and uplink service packets, reduce the end-to-end transmission latency of service packets, and enhance the overall service packet transmission acceleration effect.

[0132] The above primarily describes the solution provided by the embodiments of this application from the perspective of interaction between various nodes. It is understood that each node, such as the AP and STA, includes corresponding hardware structures and / or software modules to execute the aforementioned functions. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein, the methods of the embodiments of this application can be implemented in hardware, software, or a combination of hardware and computer software. Whether a function is executed in a hardware or software-driven manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0133] This application embodiment can divide the AP and STA into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0134] Figure 7 A structural diagram of a service message sending device 700 is shown. This service message sending device 700 can be a slave AP, and it can be used to perform the functions of the slave AP involved in the above embodiments. As one possible implementation, Figure 7 The service message sending device 700 shown includes: a receiving unit 701, a processing unit 702, and a sending unit 703.

[0135] In one possible design, the receiving unit 701 is used to obtain service characteristic information from the service message. The service characteristic information includes one or more of the following: source Internet Protocol (IP) address, source port, destination Internet Protocol (IP) address, destination port, and protocol number. For example, the receiving unit 701 may support the communication device 700 in executing steps 504 and 507.

[0136] Processing unit 702 is configured to determine a first feature marker based on the service feature information of the first service message and the first relationship, and to record the second service feature information and the second feature marker into a record of the first relationship, and to calculate the time difference between the timestamp and the current time. For example, processing unit 702 may support communication device 700 in executing steps 504 and 508.

[0137] The sending unit 703 is used to send the uplink service message through a first queue according to the service characteristic information of the uplink service message. The sending priority of the first queue meets the sending requirements of the uplink service message. For example, the sending unit 703 can support the communication device 700 to execute steps 505 and 509.

[0138] The processing unit may be a processor or a controller. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0139] Specifically, the above Figures 2-6All relevant details regarding the steps involved in the illustrated method embodiment can be found in the functional descriptions of the corresponding functional modules, and will not be repeated here. The communication device 700 is used to execute... Figures 2-6 The method shown in the diagram has the same functionality as the business message sending method described above, and therefore can achieve the same effect.

[0140] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be a terminal of any of the foregoing embodiments, such as an internal storage unit including a data sending end and / or a data receiving end, like a hard disk or memory of the terminal. The computer-readable storage medium can also be an external storage device of the terminal, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal. Further, the computer-readable storage medium can include both the internal storage unit and the external storage device of the terminal. The computer-readable storage medium is used to store the computer program and other programs and data required by the terminal. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0141] Figure 8 A structural diagram of a communication system provided in an embodiment of this application is shown below. Figure 8 As shown, the communication system may include: STA1, STA2, slave AP, and master AP.

[0142] In one example, the AP receives a first service message, which includes first service characteristic information; based on the first service characteristic information, the first service message is sent out through a first queue; the sending priority of the first queue meets the sending requirements of the first service message.

[0143] In another example, the AP receives a second service message, which includes second service feature information and a second feature tag; the second service feature information and the second feature tag are recorded in a record of the first relationship.

[0144] In another example, the AP is used to receive a third service message, which includes third service feature information and a third feature tag. If the third service feature information is included in the first relation, and the feature tag corresponding to the third service feature information in the first relation is different from the third feature tag, then the feature tag and / or timestamp corresponding to the third service feature information in the first relation are updated.

[0145] The specific execution actions of STA1 and / or STA2 are as follows: Figure 5 The actions related to the STA in the method shown are explained in the specific execution actions of the main AP. Figure 5 The actions of the main AP in the method shown will not be elaborated upon.

[0146] Unless otherwise specified, the term "transmission" in the embodiments of this application refers to bidirectional transmission, encompassing the actions of sending and / or receiving. Specifically, "transmission" in the embodiments of this application includes sending data, receiving data, or both sending and receiving data. In other words, data transmission here includes uplink and / or downlink data transmission. Data may include channels and / or signals; uplink data transmission refers to uplink channel and / or uplink signal transmission, and downlink data transmission refers to downlink channel and / or downlink signal transmission. The terms "network" and "system" in the embodiments of this application refer to the same concept; a communication system is a communication network.

[0147] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0148] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0149] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0150] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0151] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device, such as a microcontroller, chip, or processor, to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

Claims

1. A method for sending service messages, characterized in that, The method includes: Receive a first service message, the first service message including first service feature information; Based on the first service feature information, the first service message is sent out through the first queue, including: determining a first feature marker based on the service feature information of the first service message and a first relationship; sending the first service message according to the first queue corresponding to the first feature marker; the first relationship includes the correspondence between service feature information and feature markers; the feature marker is used to indicate the queue for sending the service message; different feature markers indicate queues with different priorities; the sending priority of the first queue meets the sending requirements of the first service message; Receive a third service message, the third service message including third service feature information and a third feature marker; If the third service feature information is included in the first relationship, and the feature tag corresponding to the third service feature information in the first relationship is different from the third feature tag, then update the feature tag and / or timestamp corresponding to the third service feature information in the first relationship.

2. The method according to claim 1, characterized in that, Before receiving the first service message, the method further includes: Receive a second service message, the second service message including second service feature information and a second feature tag; The second business feature information and the second feature tag are recorded in a record of the first relationship.

3. The method according to claim 1 or 2, characterized in that, The first relationship also includes a timestamp, which is used to determine the validity of the correspondence between business feature information and feature tags in the first relationship.

4. The method according to claim 3, characterized in that, The method further includes: Calculate the time difference between the timestamp and the current time; When the time difference is greater than or equal to a first preset time, the correspondence between the business feature information and the feature marker is determined to be invalid. When the time difference is less than a first preset time, the correspondence between the business feature information and the feature tag is determined to be valid.

5. The method according to claim 1 or 2, characterized in that, The first service feature information includes one or more of the following: source Internet Protocol IP address, source port, destination Internet Protocol IP address, destination port, and protocol number.

6. A service message sending device, characterized in that, The service message sending device includes: A receiving unit is configured to receive a first service message, wherein the first service message includes first service characteristic information; The sending unit is configured to send the first service message through a first queue according to the first service feature information; the sending priority of the first queue satisfies the sending requirements of the first service message. The device also includes a processing unit; The processing unit is used to determine a first feature marker based on the service feature information of the first service message and the first relationship; The sending unit is further configured to send the first service message according to the first queue corresponding to the first feature marker; The first relationship includes the correspondence between service feature information and feature tags; the feature tags are used to indicate the queue for sending service messages; different feature tags indicate queues with different priorities; The receiving unit is also configured to receive a third service message, the third service message including third service feature information and a third feature marker; If the third service feature information is included in the first relationship, and the feature tag corresponding to the third service feature information in the first relationship is different from the third feature tag, then update the feature tag and / or timestamp corresponding to the third service feature information in the first relationship.

7. The apparatus according to claim 6, characterized in that, Before receiving the first service message, the receiving unit is further configured to receive a second service message, the second service message including second service feature information and a second feature tag; The processing unit is used to record the second business feature information and the second feature tag into a record of the first relationship.

8. The apparatus according to claim 6 or 7, characterized in that, The first relationship also includes a timestamp, which is used to determine the validity of the correspondence between business feature information and feature tags in the first relationship.

9. The apparatus according to claim 8, characterized in that, The processing unit is also used to calculate the time difference between the timestamp and the current time. When the time difference is greater than or equal to a first preset time, the correspondence between the business feature information and the feature marker is determined to be invalid. When the time difference is less than a first preset time, the correspondence between the business feature information and the feature tag is determined to be valid.

10. The apparatus according to claim 6 or 7, characterized in that, The first service feature information includes one or more of the following: source Internet Protocol IP address, source port, destination Internet Protocol IP address, destination port, and protocol number.

11. A communication device, characterized in that, The communication device includes one or more processors and a communication interface, wherein the one or more processors and the communication interface are used to support the communication device in performing the service message sending method as described in any one of claims 1-5.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions that, when executed on a computer, cause the computer to perform the service message transmission method as described in any one of claims 1-5.

13. A communication system, characterized in that, The communication system includes a service message sending device as described in any one of claims 6-10, and is capable of executing the service message sending method as described in any one of claims 1-5.

Images