[go: up one dir, main page]

WO2025077533A1 - Procédé et système de transmission de trafic à faible latence - Google Patents

Procédé et système de transmission de trafic à faible latence Download PDF

Info

Publication number
WO2025077533A1
WO2025077533A1 PCT/CN2024/119427 CN2024119427W WO2025077533A1 WO 2025077533 A1 WO2025077533 A1 WO 2025077533A1 CN 2024119427 W CN2024119427 W CN 2024119427W WO 2025077533 A1 WO2025077533 A1 WO 2025077533A1
Authority
WO
WIPO (PCT)
Prior art keywords
low
latency
latency service
service
txop
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/119427
Other languages
English (en)
Chinese (zh)
Inventor
殷晓雪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Clourney Semiconductor
Original Assignee
Clourney Semiconductor
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Clourney Semiconductor filed Critical Clourney Semiconductor
Publication of WO2025077533A1 publication Critical patent/WO2025077533A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H04W72/512—Allocation or scheduling criteria for wireless resources based on terminal or device properties for low-latency requirements, e.g. URLLC

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular to a low-latency service transmission method and system.
  • Wi-Fi standards have been committed to improving the peak rate and capacity of the network.
  • previous Wi-Fi standards cannot guarantee network latency stability and low latency performance.
  • Some emerging applications such as telemedicine, virtual reality (VR), industrial control, logistics, and robotics, have strict requirements on network latency, requiring the network to be able to transmit large amounts of data in real time and with predictability.
  • many IoT applications also require the network to support massive device access. For this type of low-latency traffic, the network needs to be able to transmit data in a very short time to ensure the smoothness and real-time nature of the user experience. If the network latency is too high, users may encounter problems such as screen freezes, intermittent sound, and operation failures, which will affect the normal operation of the business.
  • Wi-Fi protocols are constantly being improved and optimized to improve network performance and flexibility.
  • Wi-Fi8 takes ultra-high reliability (UHR) of data transmission as its core goal. How to improve the reliability of low-latency service transmission by designing a UHR solution is an issue that needs to be solved urgently.
  • An embodiment of the present application provides a low-latency service transmission method, including: identifying whether the service currently to be transmitted is a low-latency service; and giving priority to the identified low-latency service.
  • Another embodiment of the present application provides a low-latency service transmission system, including: an access point AP and a station, wherein the access point AP and the station are used to jointly execute the low-latency service transmission method as described above.
  • the service to be transmitted identifies whether the service to be transmitted is a low-latency service; and gives priority to the identified low-latency service, including: creating an independent highest-priority access category for the low-latency service in advance and setting the EDCA parameters of the access category; determining whether the service to be transmitted is a low-latency service based on the access category of the service to be transmitted; and giving priority to the identified low-latency service according to the EDCA parameters of the corresponding access category.
  • the low-latency service includes at least: predictable low-latency service and event-driven low-latency service; the pre-creation of an independent highest-priority access category for the low-latency service and setting the EDCA parameters of the access category includes: pre-setting access categories for the predictable low-latency service and the event-driven low-latency service, respectively, and EDCA parameters of the access categories; wherein the priority of the access category of the event-driven low-latency service is higher than the priority of the access category of the predictable low-latency service.
  • the identified low-latency services are given priority, including: mapping the access category of the identified low-latency services to the existing access category with the highest priority; and giving priority to the identified low-latency services according to the EDCA parameters of the mapped access category.
  • the method when mapping the access category of the low-latency service to the existing access category with the highest priority, the method also includes: reconfiguring the EDCA parameters of the mapped access category; giving priority to the identified low-latency service according to the EDCA parameters of the mapped access category, including: giving priority to the identified low-latency service according to the reconfigured EDCA parameters of the mapped access category.
  • the low-latency service includes at least: predictable low-latency service and event-driven low-latency service; the reconfiguration of the EDCA parameters of the mapped access category includes: after mapping the access categories of the predictable low-latency service and the event-driven low-latency service respectively, the EDCA parameters of the two mapped access categories are reconfigured differently, so that the event-driven low-latency service has a higher priority than the access category of the predictable low-latency service.
  • the EDCA parameters include an identification bit for indicating whether the current access category can be allocated with low-latency services; mapping the access category of the identified low-latency services to an existing access category with a higher priority includes: mapping the access category of the identified low-latency services to an existing access category with a higher priority indicated by the identification bit as an access category to which low-latency services can be allocated.
  • the prioritizing of the identified low-latency services includes: presetting a parameter for describing the delay that the low-latency services can bear. Time threshold and data volume threshold; mapping the access category of the identified low-latency service to the existing access category according to the relationship between the maximum time value and the maximum data volume value of the tolerable delay indicated in the configuration information of the low-latency service and the time threshold and the data volume threshold; wherein, the smaller the time value is than the time threshold, and/or the larger the data volume value is than the data volume threshold, the higher the priority of the corresponding existing access category mapped thereto; giving priority to the identified low-latency service according to the EDCA parameters of the mapped access category.
  • the identified low-latency service is given priority, including: the TXOP holder immediately inserts the transmission of the low-latency service after completing the transmission of the non-low-latency service being transmitted, and then receives a BA containing feedback of the non-low-latency service replied by the receiving end of the non-low-latency service.
  • the BA replied by the receiving end and received by the TXOP holder also includes feedback of the low-latency service.
  • the TXOP holder completes the transmission of the non-low-latency service, and then further includes: the TXOP holder requests the receiving end of the non-low-latency service to suspend BA feedback, and after the low-latency service transmission is completed and the BA fed back by the receiving end of the low-latency service is obtained, the TXOP holder sends a BAR to the receiving end of the non-low-latency service in order to obtain the BA fed back by the receiving end.
  • the identified low-latency service is given priority, including: after receiving the data packet of the low-latency service, the TXOP holder immediately interrupts the currently transmitted non-low-latency service and starts transmitting the low-latency service. After the transmission is completed, according to the delay requirement of the interrupted non-low-latency service, if there is no timeout, the interrupted non-low-latency service continues to be transmitted; if there is a timeout, the interrupted non-low-latency service is retransmitted.
  • the identified low-latency service is given priority processing, including: the AP sends a first preemption indication to the site to instruct the site to interrupt the non-low-latency service that the AP is transmitting; the site sends confirmation information of the first preemption indication to the AP; after the AP receives the confirmation information of the first preemption indication, it starts to transmit the low-latency service to the receiving end.
  • the identified low-latency service is given priority processing, including: the station sends a first preemption request to the AP to request the AP to agree that the station preempts the current TXOP; if the AP agrees that the station preempts the current TXOP, the AP will interrupt the transmission of the non-low-latency service with the station and send a second preemption indication to the station, and the station starts to send low-latency services to the AP after receiving the second preemption indication; if the AP does not agree that the station preempts the current TXOP, the AP ignores the first preemption request and continues to transmit the non-low-latency service with the station.
  • the identified low-latency service is given priority, including: the third-party site sends a second preemption request to the AP in the TXOP to request the AP to agree to the third-party site preempting the current TXOP; if the AP agrees to the third-party site preempting the current TXOP, the AP will interrupt the transmission of non-low-latency services between the sites in the TXOP and send a second preemption indication to the third-party site, and the third-party site starts to send low-latency services to the AP after receiving the second preemption indication; if the AP does not agree to the third-party site preempting the current TXOP, the AP ignores the second preemption request and continues to transmit non-low-latency services between the sites in the TXOP.
  • preemption request and the preemption indication are sent as separate control frames or management frames, or are sent attached to other control frames or management frames.
  • the identified low-latency services are given priority, including: the AP prioritizes the low-latency services to be transmitted at each station according to the maximum time value and maximum data volume value of the tolerable delay of the low-latency services to be transmitted by each station, and sends a second preemption indication to the corresponding stations in order from high to low priority, and after receiving the second preemption indication, each station starts to send low-latency services to the AP in turn.
  • the identified low-latency service is given priority, including: the AP sends a second preemption indication to the station that competes for the channel based on a preset competition strategy to instruct the station to start sending low-latency services to the AP, and sends an interruption indication to the station that is currently transmitting non-low-latency services to instruct the station to suspend the current transmission of non-low-latency services or prohibit participating in channel competition.
  • the method further includes: if there is still margin in the current TXOP, continuing to transmit the interrupted non-low-latency service; if the current TXOP is exhausted, retransmitting the interrupted non-low-latency service.
  • the backoff window of the non-low-latency service is configured to be smaller than the backoff window before the interruption, and/or the access category of the non-low-latency service is mapped to the access category with the highest priority.
  • the identified low-latency service is given priority, including: retransmitting the low-latency service that failed to transmit, and the number of retransmissions is not greater than a retransmission number threshold.
  • the identification The low-latency service transmitted is given priority, and it also includes: the station transmitting the low-latency service sends a first preemption request to the AP to request the AP to agree that the station preempts the next TXOP, and after the request is agreed, continues to transmit the low-latency service in the next TXOP.
  • the identified low-latency service is given priority, and also includes: the station transmitting the low-latency service competes for the subsequent TXOP within the current TXOP to continue transmitting the low-latency service in the subsequent TXOP.
  • the priority processing of the identified low-latency service also includes: the station transmitting the low-latency service sends a first sharing request to the AP to request the AP to agree to share the remainder of the preempted TXOP for the AP or other stations to transmit data.
  • the priority processing of the identified low-latency services includes: in the orthogonal frequency division multiplexing mechanism of downlink multi-users, the access point AP prioritizes the allocation of resource units or spatial streams to the site to receive the low-latency service, and completes the transmission of the low-latency service with the site based on the prioritized resource units or spatial streams.
  • the priority processing of the identified low-latency services includes: in the uplink multi-user orthogonal frequency division multiplexing mechanism, the access point AP allocates resources to each site based on the cache status feedback BSR obtained from each site; wherein, resource units are preferentially allocated to sites that contain information about low-latency services in the BSR; sites that need to be allocated resources are notified through trigger frames, and the service transmission is completed with each site based on the allocated resource units.
  • the method of transmitting information about low-latency services based on BSR includes: adding a bit indicating low-latency services in the BSR control subfield format; when the bit is configured as a preset value, the service corresponding to the high-priority access category indicated in the ACI high subfield is a low-latency service, and the corresponding Queue Size High corresponds to the queue length of the low-latency service; when the bit is configured as a non-preset value, it indicates that there is no low-latency service in the queue; wherein the preset value is 1 or 0.
  • the method of transmitting information of low-latency services based on BSR includes: creating an independent access category with the highest priority for low-latency services in advance; adding relevant bits of the access category for the low-latency services in ACI bitmap and ACI High of the BSR control subfield format, and updating the mapping table of the ACI bitmap.
  • the access category of the low-latency service includes: an access category of event-driven low-latency service and an access category of predictable low-latency service, and the priority of the access category of the event-driven low-latency service is higher than the priority of the access category of the predictable low-latency service.
  • the priority processing of the identified low-latency services includes: in the random access mechanism in the uplink multi-user orthogonal frequency division multiplexing, the access point AP allows the station to transmit the low-latency service to directly select the minimum value of OCW from the trigger frame sent by the access point AP to perform a backoff step, or the access point AP configures a separate OCW value for the station to transmit the low-latency service, so that the station competes for resources successfully, so that the station completes the transmission of the low-latency service with the access point AP based on the resource unit competed for.
  • FIG1 is a specific flow chart of a low-latency data transmission method provided by an embodiment of the present application.
  • FIG2 is a specific flow chart 2 of a low-latency data transmission method provided by an embodiment of the present application.
  • FIG3 is an EDCA parameter set element diagram 1 provided by an embodiment of the present application.
  • FIG4 is a diagram of the AC_LL Parameter Record fields provided in one embodiment of the present application.
  • FIG5 is a diagram of a mapping relationship between ACI and AC provided by an embodiment of the present application.
  • FIG6 is a multi-user EDCA parameter set element diagram provided by an embodiment of the present application.
  • FIG7 is a specific flow chart 3 of a low-latency data transmission method provided by an embodiment of the present application.
  • FIG8 is a second diagram of an EDCA parameter set element provided by an embodiment of the present application.
  • FIG9 is a schematic diagram 1 of low-latency service transmission provided by an embodiment of the present application.
  • FIG10 is a second schematic diagram of low-latency service transmission provided by an embodiment of the present application.
  • FIG11 is a third schematic diagram of low-latency service transmission provided by an embodiment of the present application.
  • FIG12 is a fourth schematic diagram of low-latency service transmission provided by an embodiment of the present application.
  • FIG13 is a fifth schematic diagram of low-latency service transmission provided by an embodiment of the present application.
  • FIG14 is a diagram of a structure of a preemption indication frame provided by an embodiment of the present application.
  • FIG15 is a second diagram of a preemption indication frame structure provided by an embodiment of the present application.
  • An embodiment of the present application relates to a low-latency service transmission method. As shown in FIG1 , the low-latency service transmission method provided by this embodiment includes the following steps.
  • this application based on the EDCA of the existing WiFi system, can identify in advance whether the service to be transmitted is a low-latency service, distinguish between low-latency services and non-low-latency services, and avoid conflicts and interference between different types of services, thereby ensuring the stability of low-latency service transmission. If the service to be transmitted is confirmed to be a low-latency service, the identified low-latency service will be processed first, thereby ensuring Transmission quality and stability of low-latency services.
  • AC_LL Low Latency
  • AC_VO voice service
  • AC_VI video service
  • AC_BE best effort
  • AC_BK background traffic
  • the service to be transmitted is a low-latency service according to the access category of the service to be transmitted. That is, it is determined whether the access category of the service to be transmitted is AC_LL. If so, it is determined that the service to be transmitted is a low-latency service; if not, it is determined that the service to be transmitted is not a low-latency service.
  • Step 203 Prioritize the identified low-delay services according to the EDCA parameters of their corresponding access categories.
  • AC_LL has the smallest contention window: CWmin (minimum contention window) and CWmax (maximum contention window), that is, CWmin[AC_LL] ⁇ CWmin[AC_VO], CWmax[AC_LL] ⁇ CWmax[AC_VO], thereby reducing the collision probability and backoff time when competing for the channel.
  • CWmin[AC_VO] (aCWmin+1)/4-1
  • CWmax[AC_VO] (aCWmin+1)/2-1.
  • the configuration of EDCA parameter set element should also be updated, and the fields corresponding to AC_LL need to be added as shown in Figure 3, where the AC_LL Parameter Record field has the same structure as other AC types, as shown in Figure 4.
  • the mapping of ACI (AC Index) to AC also needs to add 1 bit to AC_LL, as shown in Figure 5.
  • the fields of AC_LL should also be added synchronously, as shown in Figure 6, where the structure of MU AC_LL Parameter Record is the same as other access types.
  • the low-latency service includes at least: a predictable low-latency service and an event-driven low-latency service.
  • the execution process corresponding to the above step 201 can be: setting access categories and EDCA parameters of access categories for predictable low-latency services and event-driven low-latency services respectively in advance; wherein the priority of the access category of the event-driven low-latency service is higher than the priority of the access category of the predictable low-latency service.
  • low-latency services can be further subdivided into predictable low-latency services and event-driven low-latency services (also called bursty low-latency services) according to their characteristics and needs.
  • event-driven low-latency services also called bursty low-latency services
  • the AC_LL category it can also be further divided into two subcategories, corresponding to predictable low-latency services and event-driven low-latency services, that is, access categories and EDCA parameters of access categories can be set in advance for predictable low-latency services and event-driven low-latency services.
  • the above embodiment of the present application creates an independent access category with the highest priority for low-latency services in advance and sets the EDCA parameters of the access category.
  • the low-latency service is preferentially processed according to the EDCA parameters corresponding to the newly defined access category of the low-latency service.
  • the low-latency service reduces the waiting time before competing for the channel through the shortest AIFS, reduces the collision probability and backoff time when competing for the channel through the smallest contention window, and allows multiple data frames to be sent continuously through the longest TXOP, thereby improving throughput and efficiency.
  • Another embodiment of the present application relates to a low-latency service transmission method, as shown in Figure 7.
  • the low-latency service transmission method in this embodiment can serve as a supplementary embodiment of the aforementioned embodiment, and the specific contents are as follows.
  • Step 301 Map the identified access category of the low-latency service to the existing access category with the highest priority.
  • AC_VO voice service
  • AC_VI video service
  • AC_BE best effort
  • AC_BK background traffic
  • AC_VO has the highest priority among the above four ACs
  • low-latency services can be mapped to the highest priority access category AC_VO.
  • the low-latency service will also use the EDCA parameters corresponding to AC_VO, including AIFS, CWmin, CWmax, TXOP limit, etc.
  • Step 302 Prioritize the identified low-latency services according to the mapped EDCA parameters of the access category.
  • the low-latency services when the identified low-latency services are given priority according to the EDCA parameters of the mapped access category AC_VO, the low-latency services have the EDCA parameters of AC_VO, namely, a shorter AIFS and a smaller CWmin/CWmax to reduce waiting time and collision probability and improve transmission success rate; a longer TXOP to allow continuous transmission of multiple data frames to improve throughput and efficiency.
  • the low-latency service transmission method in this embodiment further includes:
  • step 302 giving priority to the identified low-latency services according to the EDCA parameters of the mapped access category is specifically as follows:
  • the identified low-latency services are given priority according to the reconfigured EDCA parameters of the mapped access categories.
  • more stringent EDCA parameters are also configured for the low-latency service mapped to AC_VO.
  • the parameter values can refer to the following method: AISFN ⁇ 2; CWmin[AC_VO] ⁇ (aCWmin+1)/4-1; CWmax[AC_VO] ⁇ (aCWmin+1)/2-1; and TXOP limit is not less than the original TXOP limit of AC_VO, where TXOP limit is the parameter value of TXOP, representing the maximum time to occupy the channel (without contention).
  • TXOP limit is the parameter value of TXOP, representing the maximum time to occupy the channel (without contention).
  • the low-latency service includes at least: a predictable low-latency service and an event-driven low-latency service.
  • the execution steps for reconfiguring the EDCA parameters of the mapped access categories may be: after mapping the access categories of the predictable low-latency service and the event-driven low-latency service respectively, the EDCA parameters of the two mapped access categories are reconfigured differently so that the event-driven low-latency service has a higher priority than the access category of the predictable low-latency service.
  • low-latency services can be further subdivided into predictable low-latency services and event-driven low-latency services (also referred to as bursty low-latency services) according to their characteristics and needs.
  • predictable low-latency services since their transmission time and data volume are fixed or known, corresponding resources can be allocated and scheduled in advance.
  • event-driven low-latency services since their transmission time and data volume are random or unknown, resources need to be allocated and scheduled immediately when they occur.
  • the EDCA parameters of the two mapped access categories can be reconfigured differently, and the priority of the access category of the event-driven low-latency service can be set higher than the priority of the access category of the predictable low-latency service.
  • step 301 may be:
  • the access category of the identified low-latency service is mapped to an existing access category whose identification bit indicates that the low-latency service can be allocated and has a higher priority.
  • a higher access category refers to an access category with a higher priority than the access category originally corresponding to the low-latency service.
  • the EDCA parameter contains an identification bit for indicating whether the current access category can be allocated with a low-latency service.
  • the identification bit is a reserved bit in each AC parameter record in the existing EDCA parameter set element, which is used to indicate whether the low-latency service can be allocated in the current access type. Therefore, the reserved bit in each AC parameter record in the existing EDCA parameter set element can be reused. As shown in Figure 8, when the Low Latency Indication is 1, it means that the current AC allows low-latency services with a lower priority than it to be mapped to the current AC category.
  • AC_VO is higher than AC_VI, higher than AC_BE, and higher than AC_BK.
  • Low-latency services are allocated to higher-priority ACs based on their own delay requirements, rather than being mapped based on the configured TID.
  • the STA can classify the data packets of the current low-latency service into the AC_VI category. If the Low Latency Indication of AC_VO is also 1 at this time, the STA can consider mapping to AC_VO or AC_VI according to the emergency situation of the current low-latency service. On the contrary, if the Low Latency Indication is 0, it means that the current AC category does not support cross-category low-latency service mapping.
  • step 102 may include the following steps:
  • the time threshold and data volume threshold used to describe the tolerable delay of the low-latency service are preset; the identified low-latency service is identified according to the relationship between the maximum time value and the maximum data volume value of the tolerable delay indicated in the configuration information of the low-latency service and the time threshold and the data volume threshold.
  • the access category of the late service is mapped to the existing access category;
  • the identified low-latency services are processed preferentially according to the EDCA parameters of the mapped access category.
  • Solution 2 When the maximum tolerable delay of the low-latency service is less than LatencyTh, and the amount of low-latency service data is greater than LLPacketSizeTh, the access category (AC) mapped to the low-latency service can be upgraded.
  • AC access category
  • the low-latency service that meets both of the above conditions should be mapped to AC_BK, and if the Low Latency Indication of AC_VI is 1, the mapped access category of the low-latency service can be raised to AC_VI.
  • Solution 3 When either the condition that the maximum delay that the low-latency service can bear is less than LatencyTh or the condition that the data volume of the low-latency service is greater than LLPacketSizeTh is met, the access category (AC) mapped to the low-latency service can be upgraded by one level; when both conditions are met, the access category (AC) mapped to the low-latency service can be upgraded by two levels. For example, if a low-latency service that meets both conditions should be mapped to AC_BK, and if the Low Latency Indication of AC_VO is 1, the mapped access category (AC) of the low-latency service can be upgraded to AC_VO.
  • the low-latency service can try to map to the next higher priority access category, or stop cross-category mapping, that is, continue to map to the access category it should be mapped to.
  • this embodiment maps the access category of the identified low-latency service to the existing access category with the highest priority, and gives priority to the identified low-latency service according to the EDCA parameters of the mapped access category. It can provide the highest priority and optimal resource allocation for the low-latency service, ensure the transmission quality and stability of the low-latency service, and avoid the degradation of user experience and service interruption due to excessive network delay. At the same time, it can provide the low-latency service with a shorter waiting time and a smaller collision probability, reduce the number of retransmissions and retransmission delays of data frames, save transmission time and bandwidth resources, provide the low-latency service with longer transmission opportunities and greater throughput, and adapt to low-latency services of different types and scales.
  • Another embodiment of the present application relates to a low-latency service transmission method.
  • the low-latency service transmission method in this embodiment is a supplement to the aforementioned embodiment.
  • This embodiment involves low-latency service transmission when low-latency services are generated on different devices.
  • the specific contents are as follows.
  • the low-latency service transmission method is as follows:
  • the step of giving priority to the identified low-latency service may include:
  • the TXOP holder After the TXOP holder completes the transmission of the non-low-latency service being transmitted, it immediately inserts the transmission of the low-latency service, and then receives the BA containing the feedback of the non-low-latency service replied by the receiving end of the non-low-latency service.
  • a TXOP holder which can be an AP or a non-AP STA
  • the TXOP holder immediately inserts the transmission of the low-latency service after completing the transmission of the non-low-latency service being transmitted, and then receives the BA (Block ACK) containing feedback of the non-low-latency service replied by the receiving end of the non-low-latency service.
  • BA Block ACK
  • the BA replied by the receiving end and received by the TXOP holder also includes feedback of the low-latency service.
  • the transmitter should include low-latency services when sending Block Ack Request (BAR).
  • the receiver's BA should also include feedback on low-latency services, that is, low-latency services and non-low-latency services only need to reply to one BA.
  • the AP Access Point
  • STA1 Serving Tx-latency data packet
  • STA1 Station
  • STA1 combines the reception results of the non-low-latency data packet and the low-latency data packet in the same BA and feeds them back to the AP.
  • the TXOP holder transmits After the non-low-latency service being transmitted is completed, it also includes:
  • the TXOP holder requests the receiving end of the non-low-latency service to suspend the feedback of BA. After the low-latency service transmission is completed and the BA fed back by the receiving end of the low-latency service is obtained, the TXOP holder sends a BAR to the receiving end of the non-low-latency service in order to obtain the BA fed back by the receiving end.
  • the AP if the AP has a low-latency data packet to send to another STA, STA1 suspends BA feedback, and after the low-latency service transmission is completed, the AP sends a BAR to STA1 to request BA feedback.
  • the identified low-latency service is preferentially processed, including:
  • the TXOP holder After receiving the data packet of the low-latency service, the TXOP holder immediately interrupts the currently transmitted non-low-latency service and starts transmitting the low-latency service. After the transmission is completed, according to the delay requirement of the interrupted non-low-latency service, if there is no timeout, the interrupted non-low-latency service will continue to be transmitted. If there is a timeout, the interrupted non-low-latency service will be retransmitted.
  • the TXOP responder When the low-latency service is a low-latency service sent by the TXOP responder, that is, when the TXOP responder (which can be an AP or a non-AP STA) receives a data packet sent by the TXOP holder and encounters a burst of low-latency service data packets that need to be sent immediately, the TXOP responder needs to complete the reception and reply of the data packet within the channel resources granted by the TXOP holder, while also considering the transmission of the low-latency service data packet.
  • the low-latency service transmission method is as follows:
  • the identified low-latency service is preferentially processed, including:
  • the AP sends a first preemption indication to the site to instruct the site to interrupt the non-low-latency service that the AP is transmitting; the site sends confirmation information of the first preemption indication to the AP; after receiving the confirmation information of the first preemption indication, the AP starts to transmit the low-latency service to the receiving end.
  • AP when the TXOP responder is AP, as shown in FIG11 , AP is receiving data from TXOP holder STA1 at this time, and AP has a low-latency service data packet to transmit to STA1. Since STA1 has the current TXOP, AP cannot send a data packet directly, but needs to first notify STA1 that it has a low-latency service that needs to be transmitted first. Therefore, AP needs to send a preemption indication (PreEmptInd) to STA1, informing STA1 that it has a low-latency service that needs to preempt the current TXOP, and requires STA1 to interrupt its current transmission. STA1 receives PreEmptInd and replies with an acknowledgment message (ACK) to AP.
  • PreEmptInd preemption indication
  • ACK acknowledgment message
  • the purpose of the preemption indication is mainly to notify the device that has a low-latency service to transmit that it can transmit the low-latency service. After receiving the preemption indication, after SIFS (Short Inter-Frame Space) duration, the low-latency service can be transmitted. Similarly, if the target of the AP's low-latency service data packet is another STA (station), such as STA2, the content and sending method of the preemption indication are the same as the above process, and this application will not repeat them here.
  • the preemption indication PreEmptInd can be sent as a separate control frame or management frame (such as Action Frame), or it can be attached to other control frames (such as CTS) or management frames. This application does not impose any specific restrictions on the sending form of the preemption request (PreEmptReq) and the preemption indication (PreEmptInd).
  • the identified low-latency service is preferentially processed, including:
  • the station sends a first preemption request to the AP to request the AP to agree that the station preempts the current TXOP;
  • the AP If the AP agrees that the station preempts the current TXOP, the AP will interrupt the transmission of non-low-latency services between the AP and the station and send a second preemption indication to the station. After receiving the second preemption indication, the station starts to send low-latency services to the AP.
  • the AP ignores the first preemption request and continues to transmit non-low-latency traffic between the station and the AP.
  • the TXOP responder is a non-AP STA
  • STA1 has a low-latency service data packet to transmit to the AP, but the TXOP holder is the AP.
  • STA1 needs to send a preemption request (PreEmptReq) to the AP, requesting the AP to agree to preempt the current TXOP.
  • the AP can decide whether to agree to the preemption based on its own strategy. If the preemption is agreed, the AP needs to send a preemption indication PreEmptInd to the requesting STA1, and notify the current TXOP holder to interrupt the transmission.
  • PreEmptReq can be sent as a separate control frame or management frame (such as Action Frame), or it can be attached to other control frames (such as RTS) or management frames.
  • the PreEmptInd fed back by the AP can be sent as a separate control frame or management frame (such as Action Frame), or it can be attached to other control frames (such as CTS) or management frames.
  • This application does not impose any specific restrictions on the sending form of the preemption request (PreEmptReq) and the preemption indication (PreEmptInd).
  • the identified low-latency service is preferentially processed, including:
  • the third-party station sends a second preemption request to the AP in the TXOP to request the AP to agree that the third-party station preempts the current TXOP;
  • the AP If the AP agrees that the third-party station preempts the current TXOP, the AP will interrupt the transmission of non-low-latency services between the stations in the TXOP and send a second preemption indication to the third-party station. After receiving the second preemption indication, the third-party station starts to send low-latency services to the AP.
  • the AP If the AP does not agree that the third-party station preempts the current TXOP, the AP ignores the second preemption request and continues to transmit non-low-latency traffic with the stations in the TXOP.
  • the low-latency service comes from a third-party station (STA), that is, the low-latency service is neither the TXOP holder nor the TXOP
  • STA third-party station
  • AP is transmitting data to STA1.
  • STA2 has a low-latency service data packet to transmit to AP.
  • STA2 needs to send a preemption request (PreEmptReq) to AP, requesting AP to agree to preempt the current TXOP.
  • PreEmptReq preemption request
  • AP can decide whether to agree to preempt according to its own strategy. If the preemption is agreed, AP needs to send a preemption consent feedback PreEmptInd to the requesting STA2.
  • PreEmptReq can be sent as a separate control frame or management frame (such as Action Frame), or it can be attached to other control frames (such as RTS) or management frames.
  • the PreEmptInd fed back by AP can be sent as a separate control frame or management frame (such as Action Frame), or it can be attached to other control frames (such as CTS) or management frames.
  • This application does not impose specific restrictions on the sending form of the preemption request (PreEmptReq) and the preemption indication (PreEmptInd).
  • the design of the preemption request (PreEmptReq) and the preemption indication (PreEmptInd) may be specifically performed with reference to the following settings.
  • the preemption indication frame structure can refer to Figure 14.
  • the Frame Control field is used to identify the frame type and subtype, as well as other control bits. There are two options for frame type and subtype:
  • Solution 1 Use the preemption indication frame as a control frame (such as CTS), then the frame type field should be configured as 01 and the subtype should be configured as 0000.
  • Solution 2 Use the preemption indication frame as a management frame (such as Action Frame).
  • the frame type field should be configured as 00 and the subtype as 0111.
  • the Duration field is used to specify the duration of the low-latency service data packet in microseconds; the RA field is used to specify the MAC address of the receiving device; the TA field is used to specify the MAC address of the sending device; and the Control Info field is used to carry other control information, such as latency requirement information, OMI (Operation mode Indication) information, and SM (Spatial Multiplexing) power save parameters.
  • the Control Info field is optional and is configured according to the needs of the low-latency service. Among them, the latency requirement of the low-latency service is the latest acceptable transmission time for the low-latency service. If the working mode needs to be switched, the OMI information can be included in the Control Info field to indicate the target working mode and other parameters. If the relevant parameters of SM power save need to be updated, the SM power save element can be included in the Control Info field to indicate the sleep and wake-up cycle between the AP and the STA.
  • the TA field can be omitted to save bandwidth and reduce latency.
  • the frame format can be as shown in Figure 15.
  • the preemption indication can be attached to the existing frame for transmission to reduce additional overhead. For example, if the TXOP holder has a control frame such as RTS or BAR to transmit at this time, the preemption indication can be attached to the control frame for transmission together without sending a separate preemption indication frame.
  • the main purpose of the preemption request is to inform the TXOP holder or AP that it has a low-latency service to transmit, and inform the data volume of the low-latency service, as well as the recommended working mode, SM Power save and other parameter configurations. If the TXOP holder or AP agrees to preempt the transmission of the low-latency service, it will send PreEmptInd to indicate that it agrees to the preemption operation and give the corresponding parameter configuration.
  • the preemption request PreEmptReq Similar to the preemption indication PreEmptInd, the preemption request PreEmptReq also has two forms. One is sent as an independent frame. The format of the preemption request frame is similar to that in FIG14 . The difference lies in the configuration of the Frame control field. In the frame format of the preemption request PreEmptReq, the Frame Control field is used to identify the frame type and subtype, as well as other control bits. There are two schemes for the frame type and subtype:
  • Solution 1 Use the preemption request frame as a control frame (such as RTS frame, Request to Send), then the frame type field should be configured as 01 and the subtype should be configured as 0001.
  • a control frame such as RTS frame, Request to Send
  • Solution 2 Use the preemption request frame as a management frame (such as an Action Frame).
  • the frame type field should be configured as 00 and the subtype as 1111.
  • the preemption request PreEmptReq can be attached to the existing frame for transmission to reduce additional overhead.
  • the preemption request can be attached to the current control frame for transmission, without sending a separate preemption request frame.
  • the identified low-latency service is preferentially processed, including:
  • the AP prioritizes the low-latency services to be transmitted at each site according to the maximum time value and maximum data volume value of the tolerable delay of the low-latency services to be transmitted at each site, and sends a second preemption indication to the corresponding site in order from high to low priority. After receiving the second preemption indication, each site starts to send low-latency services to the AP in turn.
  • the devices with low-latency services to be transmitted uniformly send preemption requests (PreEmptReq) to the AP, that is, when there are at least two sites that send the first preemption request to the AP at the same time, the AP prioritizes the low-latency services to be transmitted at each site according to the maximum time value and maximum data volume value of the tolerable delay of the low-latency services to be transmitted at each site, and sends a second preemption indication to the corresponding site in order from high to low priority. After receiving the second preemption indication, each site starts to send low-latency services to the AP in turn.
  • PreEmptReq preemption requests
  • the urgency of the low-latency service can be judged by multiple factors such as the delay information in PreEmptReq, whether the low-latency service is a predictable low-latency service (predictable low latency traffic) or an event-driven low-latency service (event-based low latency traffic), and the data volume of the low-latency service.
  • the judgment method is similar to the method described in the above embodiment.
  • the AP side can determine the order of low-latency service processing based on the following two judgment results: set two thresholds, LatencyTh is used to judge the urgency of low-latency services, that is, when the maximum tolerable delay configured by the low-latency service is less than LatencyTh, it means that the low-latency service is more urgent; set the second threshold LLPacketSizeTh, when the low-latency service When the data volume is greater than LLPacketSizeTh, it means that the low-latency service data volume is large and needs to be processed with priority.
  • LatencyTh is used to judge the urgency of low-latency services, that is, when the maximum tolerable delay configured by the low-latency service is less than LatencyTh, it means that the low-latency service is more urgent
  • set the second threshold LLPacketSizeTh when the low-latency service When the data volume is greater than LLPacketSizeTh, it means that the low-latency service data volume is large and needs to be processed with priority.
  • the identified low-latency service is preferentially processed, including:
  • the AP sends a second preemption indication to the station that competes for the channel based on a preset competition strategy to instruct the station to start sending low-latency services to the AP, and sends an interruption indication to the station that is currently transmitting non-low-latency services to instruct the station to suspend the current transmission of non-low-latency services or prohibit participating in channel competition.
  • the device with low-latency service competes for the channel according to the competition strategy of the prior art (802.11be), that is, when there are at least two stations that send the first preemption request to the AP at the same time, the device that competes for the channel transmits data packets of the low-latency service.
  • the AP can send an interrupt indication to the device without low-latency service to suspend transmission or instruct it not to participate in channel competition.
  • the interrupt indication can be attached to the beacon frame (Beacon) or other broadcast frame for transmission.
  • the low-latency service transmission method also includes: if there is still a margin in the current TXOP, continue to transmit the interrupted non-low-latency service; if the current TXOP is exhausted, retransmit the interrupted non-low-latency service.
  • a corresponding remediation mechanism is required to ensure the data integrity and reliability of the preempted services.
  • the reason for the retransmission of the interrupted non-low-latency service is that the resources are preempted by the low-latency service, not because of the bad channel conditions or other inherent factors, for the retransmission of the data packets of the non-low-latency service, in order to minimize the negative impact of the preemption, it can be assigned a higher priority and retransmitted first.
  • the backoff window of the non-low-latency service is configured to be smaller than the backoff window before the interruption, and/or the access category of the non-low-latency service is mapped to the access category with the highest priority.
  • a smaller backoff window CW (smaller than the backoff window before the interruption) can be configured for the non-low-latency service so that the non-low-latency service has a greater probability of competing for the right to channel access and completing the transmission.
  • the priority of the interrupted non-low-latency service is mapped to the access category with the highest priority, namely AC_VO.
  • the low-latency service will also use the EDCA parameters corresponding to AC_VO, including AIFS, CWmin, CWmax, TXOP limit, etc.
  • the method of assigning a higher priority to the non-low-latency service whose retransmission is interrupted can be similar to the above-mentioned method of assigning the highest priority to the low-latency service. It is only necessary to replace the low-latency service in the above scheme with the interrupted non-low-latency service in this embodiment, and this application will not be repeated here.
  • the identified low-latency service is given priority, including: retransmitting the low-latency service that failed to transmit, and the number of retransmissions is not greater than a retransmission threshold.
  • the low-latency service device seizes the channel and transmits data, there may also be a transmission failure.
  • this embodiment imposes certain restrictions on the retransmission mechanism of the low-latency service.
  • the number of retransmissions is not greater than the retransmission threshold. For example, a maximum retransmission threshold LLRetryLimit can be set for the low-latency service. If the number of retransmissions of the low-latency service exceeds the threshold, the low-latency service will stop retransmission and release channel resources to allow other services to have a chance to transmit.
  • LLRetryLimit There are two ways to configure the maximum retransmission threshold LLRetryLimit.
  • One is to use the existing parameter in the current system: dot11ShortRetryLimit, but it should be noted that the configuration of this parameter for the low-latency service should be different from that for the non-low-latency service, for example, the number of retransmissions of the low-latency service can be higher.
  • Another configuration method is to configure the number of retransmissions for the low-latency service alone, for example, define a new parameter dot11LLShortRetryLimit for the retransmission of the low-latency service alone.
  • a latency requirement interval or threshold can be set. If the latency requirement of the current low-latency service is less than the threshold, or within a certain interval, a higher LLRetryLimit value is configured.
  • low-latency service equipment is allowed to change parameter configurations such as MCS (Modulation and Coding Scheme) and OMI to adapt to changes in channel quality and reduce the bit error rate and packet loss rate of data packets, but it will also reduce the transmission rate and throughput.
  • MCS Modulation and Coding Scheme
  • OMI OMI
  • the identified low-latency service is given priority, which also includes: the station transmitting the low-latency service sends a first preemption request to the AP to request the AP to agree to the station preempting the next TXOP, and after the request is approved, continues to transmit the low-latency service in the next TXOP.
  • the identified low-latency service is given priority, which also includes: the station transmitting the low-latency service sends a first sharing request to the AP to request the AP to agree to share the remaining room in the occupied TXOP for the AP or other stations to transmit data.
  • the device transmitting low-latency services/stations transmitting low-latency services send the first preemption request in the current TXOP to request the AP to agree that the station preempt the next TXOP, and after the request is agreed, reserve the following TXOP and continue to transmit low-latency services in the next TXOP.
  • STA2 can send PreEmptReq in the AP's TXOP, reserve the following TXOP, and send low-latency data packets in the following TXOP. If there is still room in the TXOP after the low-latency data packet is transmitted, the TXOP can be shared with the AP or other STAs to transmit data.
  • the above settings can ensure that low-latency service devices have priority in transmitting data in the next TXOP, avoiding the overhead and uncertainty of competing for the channel again.
  • the identified low-latency service is given priority, which also includes: the station transmitting the low-latency service competes for the subsequent TXOP within the current TXOP to continue transmitting the low-latency service in the subsequent TXOP.
  • the station transmitting the low-latency service starts to compete for the subsequent transmission opportunity within the current TXOP.
  • the competition strategy can be as described in the above embodiment: configure a higher priority AC for the low-latency service or classify it into a new AC with the highest priority, so that it has a shorter backoff time, a shorter AIFS and a longer TXOP limit in the competition channel, so that it has a greater probability of competing for the subsequent transmission opportunity and can send more data frames.
  • the TXOP can be shared with the AP or other STAs to transmit data, thereby reducing the time for the low-latency service device to wait for the next TXOP to start, and there is no need to send additional preemption requests.
  • the above-mentioned embodiments of the present application take into account the situations that may arise during the transmission of low-latency services and design the preemption strategy, conflict handling and retransmission mechanism of low-latency services during the preemption process of low-latency services, so as to ensure the reliability of low-latency service transmission while also ensuring the data integrity and reliability of the preempted services and channel resources, avoid wasting extra waiting time, save channel resources, reduce the computing burden and control complexity of the AP, and improve the robustness and scalability of the system.
  • Another embodiment of the present application relates to a low-latency service transmission method. This embodiment is a supplement to the aforementioned embodiment and specifically relates to the following contents.
  • the AP uses orthogonal frequency division multiplexing (OFDMA) technology to divide the channel into multiple resource units (RUs), allowing different terminals to occupy different RUs to achieve multi-user parallel transmission.
  • OFDMA orthogonal frequency division multiplexing
  • the AP can optimize the allocation of RU resources from a global perspective during uplink and downlink transmission.
  • the identified low-latency services are prioritized, including:
  • the access point AP preferentially allocates resource units RU or spatial streams to the station to receive low-latency services, and completes the transmission of low-latency services with the station based on the preferentially allocated resource units or spatial streams.
  • the AP when the AP has multiple data frames to be sent to multiple STAs respectively, it is up to the AP to decide how to allocate RU or spatial streams to different STAs. If the AP side has low-latency services to transmit at this time, the AP side should preferentially allocate RU or stream to the STA to receive low-latency services.
  • the identified low-latency services are given priority, including:
  • the access point AP allocates resources to each site based on the buffer status feedback BSR obtained from each site; among them, resource units are preferentially allocated to sites that contain information about low-latency services in the BSR; sites that need to be allocated resources are notified through trigger frames, and service transmission is completed with each site based on the allocated resource units.
  • the AP can actively request or passively collect the terminal's cache status (i.e., BSR feedback).
  • BSR feedback i.e., BSR feedback
  • the AP performs global resource allocation based on the BSR information, and after the allocation is completed, it initiates a transmission process through the trigger frame mechanism.
  • the AP can send a BSR to inform the AP.
  • the AP can prioritize the allocation of RUs or spatial streams to the STA with low-latency services to be sent, and notify each STA that needs to be allocated resources through the trigger frame.
  • a method for transmitting information of a low-latency service based on a BSR includes:
  • a bit indicating low-latency service is added in the BSR control subfield format.
  • the service corresponding to the high-priority access category indicated in the ACI high subfield is a low-latency service, and the corresponding Queue Size High corresponds to the queue length of the low-latency service.
  • the bit is configured as a non-preset value, it indicates that there is no low-latency service in the queue.
  • the preset value is 1 or 0.
  • the ACI high subfield in the existing BSR control subfield format specifies the high priority AC determined by the STA. For a STA with a low priority service to be transmitted, this field should specify the AC corresponding to the low priority service, and the corresponding Queue Size High should also configure the Queue size corresponding to the low priority service.
  • the ACI Bitmap subfield corresponds to four different access categories, namely: B0 corresponds to AC_BE, B1 corresponds to AC_BK, B2 corresponds to AC_VI, and B3 corresponds to AC_VO.
  • 1 bit can be added to the BSR control subfield format to indicate the low-latency service Low Latency Indication (the bit indicating the low-latency service). That is, if the Low Latency Indicationsubfield is 1, it means that the service corresponding to the high-priority AC indicated in the ACI high subfield is a low-latency service, and the corresponding Queue Size High also corresponds to the queue length of the low-latency service. If the Low Latency Indicationsubfield is 0, it means Indicates that there is no low latency service in the queue.
  • the BSR control subfield format is shown in Figure 18. It should be noted that regarding the configuration of the Low latency indication subfield, considering the forward compatibility of the WiFi protocol, if this parameter is not configured, it means that special processing for low latency services is not supported.
  • a method for transmitting information of a low-latency service based on a BSR includes: creating an independent access category with the highest priority for the low-latency service in advance;
  • an independent access category AC_LL with the highest priority is created for low-latency services in advance, and the EDCA parameters of the access category are set.
  • the corresponding BSR control subfield format should also be adjusted accordingly.
  • the access category of low-latency services needs to be added to the ACI bitmap, and the corresponding ACI High should also add the ACI corresponding to the low-latency service access category. Therefore, the ACI bitmap and ACI High need to increase 1 bit each.
  • the mapping of the ACI bitmap also needs to be updated accordingly: B0 corresponds to AC_BE, B1 corresponds to AC_BK, B2 corresponds to AC_VI, B3 corresponds to AC_VO, and B4 corresponds to AC_LL.
  • the access categories of low-latency services may include: an access category of event-driven low-latency services and an access category of predictable low-latency services, and the priority of the access category of event-driven low-latency services is higher than the priority of the access category of predictable low-latency services. That is, the two TIDs corresponding to the access type AC_LL of the low-latency service may be respectively predictable low-latency services and event-driven low-latency services, and the event-driven low-latency services should have a higher priority than the predictable low-latency services.
  • the 802.11ax standard also provides an optional random access mechanism (UORA: Uplink OFDMA Random Access). Under this mechanism, the allocation of RU resources in the uplink UL-OFDMA link is not controlled by the AP, but is obtained by the terminal through UORA competition. This access mechanism does not rely on the terminal to feedback BSR information in real time.
  • UORA Uplink OFDMA Random Access
  • the identified low-latency services are given priority, including:
  • the access point AP allows the station to transmit low-latency services to directly select the minimum value of OCW from the trigger frame sent by the access point AP to perform the backoff step, or the access point AP configures a separate OCW value for the station to transmit low-latency services, so that the station can successfully compete for resources, so that the station can complete the transmission of low-latency services with the access point AP based on the resource unit competed for.
  • a frequency domain backoff technology i.e., OFDMA back-off, OBO
  • the AP first sends a trigger frame.
  • the OCW (OFDMA contention window) field in the trigger frame indicates the range of the contention window and identifies the RU resources that can be used for random access (i.e., eligible RA-RUs, RUs that can be used for Random Access).
  • the interrupt selects a random number in the OCW and subtracts its own random number from the number of RUs that can be contested in this round until the result is 0. If the terminal gets 0 after subtraction, it means that the competition is successful and a RU is randomly selected for occupation. If the terminal does not get 0 after subtraction, it means that the competition has failed, and this value is retained and subtracted in the next round.
  • the association identifier is a unique identifier assigned to a STA by the AP when the AP establishes a connection with the STA.
  • the AID field is also included in the User Info field of the trigger frame (each RU has an AID indication). The AID field indicates whether the RU is available for random access, including:
  • AID 0, it means that the RU is used for random access by one or more associated terminals;
  • the AP can configure a specific dedicated RU for the STA to use.
  • the specific method is as follows: First, the STA needs to send an indication of the low-latency service to notify the AP that it has a low-latency service to send.
  • the indication of the low-latency service can be sent to the AP based on the BSR as described above, or the method of preemption request PreEmptReq designed in Example 2 can be used to inform the AP that it has a low-latency service to send and requires the allocation of a dedicated RU.
  • the AP can also configure dedicated RU resources for such STA based on the transmission of historical services, for example, if a STA often transmits low-latency services, or if the current low-latency service is a predictable low-latency service.
  • the above embodiment of the present application combines the transmission of low-latency services with orthogonal frequency division multiplexing (OFDMA) technology, and adds 1 bit in the BSR control subfield format to indicate low-latency services or add new access categories in the uplink and downlink multi-user OFDMA operations, so that the AP can preferentially allocate RUs to the received low-latency services based on the received information.
  • STAs that have low-latency services to process further ensure the reliability of low-latency service transmission under orthogonal frequency division multiplexing.
  • Another embodiment of the present application relates to a low-latency service transmission system, including an access point AP and a station, wherein the access point AP and the station are used to jointly execute the low-latency service transmission method recorded in any of the above embodiments.
  • the specific implementation of the low-latency service transmission method has been recorded in the above embodiments, and this application will not repeat it here.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Les modes de réalisation de la présente demande relèvent du domaine des communications. Sont divulgués un procédé et un système de transmission de trafic à faible latence. Le procédé consiste à : identifier si un trafic actuel à transmettre est un trafic à faible latence ; et effectuer un traitement de priorité sur le trafic à faible latence identifié. Dans les solutions de la présente demande, savoir si le trafic à transmettre est un trafic à faible latence est pré-identifié, de telle sorte qu'un trafic à faible latence et un trafic n'étant pas à faible latence sont distingués, et s'il est confirmé que le trafic à transmettre est un trafic à faible latence, un traitement de priorité est effectué sur le trafic à faible latence identifié.
PCT/CN2024/119427 2023-10-10 2024-09-18 Procédé et système de transmission de trafic à faible latence Pending WO2025077533A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202311314412.8A CN117336876B (zh) 2023-10-10 2023-10-10 低延迟业务传输方法及系统
CN202311314412.8 2023-10-10

Publications (1)

Publication Number Publication Date
WO2025077533A1 true WO2025077533A1 (fr) 2025-04-17

Family

ID=89289956

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/119427 Pending WO2025077533A1 (fr) 2023-10-10 2024-09-18 Procédé et système de transmission de trafic à faible latence

Country Status (2)

Country Link
CN (1) CN117336876B (fr)
WO (1) WO2025077533A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117336876B (zh) * 2023-10-10 2025-01-03 上海云攀半导体有限公司 低延迟业务传输方法及系统
CN120282303A (zh) * 2024-01-08 2025-07-08 华为技术有限公司 一种基于抢占传输的数据传输的方法及装置
US20250254726A1 (en) * 2024-02-02 2025-08-07 Samsung Electronics Co., Ltd. Procedures for low latency traffic in wireless local area networks
WO2025185462A1 (fr) * 2024-03-06 2025-09-12 Mediatek Inc. Réduction de puissance proportionnelle d'accès au canal pour des transmissions à faible latence dans des communications sans fil
CN120958934A (zh) * 2024-03-14 2025-11-14 北京小米移动软件有限公司 数据帧传输方法、通信设备、站点设备及通信系统
CN117915444B (zh) * 2024-03-19 2024-06-07 南京云程半导体有限公司 低延时业务的节能方法、接入点及存储介质
CN119095111B (zh) * 2024-08-16 2025-08-12 南京云程半导体有限公司 低延时业务传输方法、接入点设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220272580A1 (en) * 2019-08-19 2022-08-25 Lg Electronics Inc. Novel access category for low latency
CN115315019A (zh) * 2021-05-07 2022-11-08 联发科技（新加坡）私人有限公司 在无线网络中使用edca信道接入技术的优先信道接入方法
WO2023072584A1 (fr) * 2021-10-29 2023-05-04 Sony Group Corporation Dispositifs de communication et procédés de troncature txop
CN116746247A (zh) * 2020-12-22 2023-09-12 佳能株式会社 利用低延迟可靠流量管理edca参数
CN117336876A (zh) * 2023-10-10 2024-01-02 上海云攀半导体有限公司 低延迟业务传输方法及系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2555142B (en) * 2016-10-21 2019-09-04 Canon Kk Enhanced management of ACs in multi-user EDCA transmission mode in wireless networks
WO2020197260A1 (fr) * 2019-03-25 2020-10-01 엘지전자 주식회사 Procédé et dispositif pour effectuer une communication à faible latence dans un système de réseau local sans fil
EP4213446A4 (fr) * 2020-10-14 2024-01-24 Huawei Technologies Co., Ltd. Puce wifi, dispositif wifi et procédé de planification de files d'attente
CN114430591A (zh) * 2020-10-14 2022-05-03 华为技术有限公司 Wi-Fi芯片、Wi-Fi设备及队列调度方法
EP4238379A1 (fr) * 2020-10-30 2023-09-06 Sony Group Corporation Dispositifs et procédés de communication
WO2022147723A1 (fr) * 2021-01-07 2022-07-14 北京小米移动软件有限公司 Procédé et dispositif de communication
WO2022260424A1 (fr) * 2021-06-09 2022-12-15 엘지전자 주식회사 Procédé et dispositif de rapport d'état de tampon dans un système lan sans fil
EP4492892A1 (fr) * 2022-03-09 2025-01-15 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et dispositif de communication sans fil
US20230208774A1 (en) * 2023-01-04 2023-06-29 Intel Corporation Preemption for low latency application

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220272580A1 (en) * 2019-08-19 2022-08-25 Lg Electronics Inc. Novel access category for low latency
CN116746247A (zh) * 2020-12-22 2023-09-12 佳能株式会社 利用低延迟可靠流量管理edca参数
CN115315019A (zh) * 2021-05-07 2022-11-08 联发科技（新加坡）私人有限公司 在无线网络中使用edca信道接入技术的优先信道接入方法
WO2023072584A1 (fr) * 2021-10-29 2023-05-04 Sony Group Corporation Dispositifs de communication et procédés de troncature txop
CN117336876A (zh) * 2023-10-10 2024-01-02 上海云攀半导体有限公司 低延迟业务传输方法及系统

Also Published As

Publication number Publication date
CN117336876A (zh) 2024-01-02
CN117336876B (zh) 2025-01-03

Similar Documents

Publication Publication Date Title
CN117336876B (zh) 低延迟业务传输方法及系统
US12081449B2 (en) QoS management for multi-user and single user EDCA transmission mode in wireless networks
JP7427170B2 (ja) 時間内及び周波数内ｒｔａパケット重複
JP7352695B2 (ja) リソースユニットを実装するｉｅｅｅ８０２．１１ネットワークにおける修復された公平性
JP2022174246A (ja) アクセス方法及び装置
US7058074B2 (en) Unified channel access for supporting quality of service (QoS) in a local area network
US7843819B1 (en) Protocol for wireless multi-channel access control
JP7334847B2 (ja) 無線ローカルエリアネットワーク（ｗｌａｎ）局におけるｒｔａキュー管理
JP2023547129A (ja) 通信デバイスおよび方法
CN113875272B (zh) 实时应用
US10028306B2 (en) Method and device for data communication in a network
JP7679488B2 (ja) Ｒｔａトラフィックとのｅｄｃａ ｔｘｏｐの共有
GB2560540A (en) Queues management for multi-user and single user edca transmission mode in wireless networks
JP7695372B2 (ja) 無線ネットワークにおける低遅延データ送信を管理するための方法および装置
CN118140523A (zh) 用于txop截断的通信设备和方法
JP4821270B2 (ja) 許容遅延時間を考慮した無線アクセス制御方法、アクセスポイント、端末及びプログラム
US20230209554A1 (en) User equipment and base station
CN117896852A (zh) 低延迟业务链路映射方法、多连接设备及存储介质
CN113747602B (zh) 一种通信方法及装置
CN119095111B (zh) 低延时业务传输方法、接入点设备及存储介质
WO2008012789A1 (fr) Procédé de communication sans fil à latence réduite possédant une latence réduite et une performance accrue de portée et de transfert entre différentes stations émettrices
GB2635348A (en) Adaptive deferred EDCA for low latency traffic in communication networks
CN118612770A (zh) 能力模式调整方法、装置、站点设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24876352

Country of ref document: EP

Kind code of ref document: A1