[go: up one dir, main page]

WO2024179660A1 - Optimisation de trafic xr intra-dispositif - Google Patents

Optimisation de trafic xr intra-dispositif Download PDF

Info

Publication number
WO2024179660A1
WO2024179660A1 PCT/EP2023/054848 EP2023054848W WO2024179660A1 WO 2024179660 A1 WO2024179660 A1 WO 2024179660A1 EP 2023054848 W EP2023054848 W EP 2023054848W WO 2024179660 A1 WO2024179660 A1 WO 2024179660A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
data packet
uplink scheduling
baseband processor
processor
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/EP2023/054848
Other languages
English (en)
Inventor
Rickard Ljung
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/EP2023/054848 priority Critical patent/WO2024179660A1/fr
Publication of WO2024179660A1 publication Critical patent/WO2024179660A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • the present disclosure relates to wireless communications, and in particular, to configurations for supporting low latency data communications.
  • the Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.
  • 4G Fourth Generation
  • 5G Fifth Generation
  • NR New Radio
  • Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.
  • the 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.
  • wireless communication systems such as 3 GPP technologies as a communication bearer for extended reality (XR), online gaming and other delay sensitive and/or low latency use cases may increase in the future.
  • XR extended reality
  • a wireless device may be configured to construct/collect data which needs to be transmitted by the device immediately and/or as soon as possible, e.g., up to a cloud game server or similar, e.g., for real time augmented reality, where one or more sensor data triggers an action that requires very low latency (“immediate”) upload of information to a network server, and the end user experience may be dependent on the round trip time of communication.
  • the collected sensor data triggering immediate upload may first require processing such as encoding, compression, etc.
  • a processor such as an application processor, by a digital signal processor, by a co-processor, by one or more processor core(s), by a system on a chip, etc.
  • application data e.g., “encoded”, “compressed”, etc. data
  • This data is thereafter transferred to the modem entity (e.g., baseband processor) in a wireless device for transmission over a wireless communication system, e.g., for transmission to a network node such as a radio base station.
  • such applications may generate large volumes data, which may also require encoding/compression/further processing (which requires additional computation time), prior to being transmitted to a baseband processor, radio circuitry, radio interface, antennas, etc., for low-latency transmission to a network node such as a radio base station.
  • SR scheduling request
  • DRX discontinuous reception
  • One existing scheduling scheme available for low latency scheduling of uplink data is the use of configured grants, in which the network pre-allocates resources such as a future repeated set of scheduling grants to the wireless device. This may work well for certain use cases, e.g., for clearly repeatable data transmission use cases such as a voice call with voice audio packets encoded repeatedly, but may work less well for varying data transmission situations, e.g., user-dependent XR use cases.
  • the network may be able to schedule required, tailored amounts of resources to handle the size of varying packet burst(s), only if the network node knows the time and size of the upcoming packet burst.
  • a legacy 3 GPP method includes the wireless device (e.g., UE) being configured to transmit scheduling request(s), which may in certain cases be combined or followed by buffer status report as described further below. Since protocol specifications may differ we here use the term scheduling request for any of such message where information indicative of the required data to transmit is signaled, e.g., to the network node with the purpose to get immediate transmit resources for the data allocated by the network.
  • the network node may allocate transmit resources.
  • Transmit resources may mean a set of time and frequency allocations, which may be specified as one or more time periods and one or more radio frequency ranges.
  • a resource may be denoted as a resource element or a resource block.
  • there may be an inbound latency from packet arrival to the baseband processor (modem) until the data has been transferred.
  • FIG. 1 is a timing diagram illustrating an example packet scheduling and transmission latency, in which time is shown on the X-axis.
  • FIG. 1 is based on 3GPP document Rl-2212606.
  • the wireless device may send a scheduling request (SR) after the packet is available to the wireless device modem (baseband processor).
  • SR scheduling request
  • the network node may thereafter schedule data to meet the scheduling request.
  • this process may require either a shorter (e.g., case 2) or longer (e.g., case 1) amount of time.
  • BSR refers to a Buffer status report, indicating the size of remaining data in a wireless device transmit buffer.
  • the time from data generation and encoding in the application entity (e.g., application processor) of the wireless device until suitable resources are available for transmission in the modem entity (e.g., baseband processor) of the device typically needs to be kept very short.
  • signaling adjustments to shorten the transmission latency may achieve improved latency.
  • FIG. 2 An example timing diagram according to embodiments of the present disclosure is illustrated in FIG. 2, which provides a problem formulation and illustration of how some embodiments of the present disclosure may be used to reduce total latency time, which may be performed in conjunction with other techniques.
  • Embodiments of the present disclosure may provide configurations supporting a functionality performed, e.g., in a wireless device, for reduced latency of scheduling an upcoming data communication, e.g., uplink communication.
  • a method in the wireless device may include:
  • Receiving information (e.g., at the baseband processor) from the application entity (e.g., the application processor) about an upcoming data set (and/or data packet, data stream, etc.), which may occur after the data set has started to be generated (and/or encoded, compressed, combined, etc.) in the application entity (application processor), and/or may occur before the data set is fully transferred to the modem entity (baseband processor).
  • the application entity e.g., the application processor
  • Some embodiments may advantageously provide configurations supporting an ability of the wireless device modem (baseband processor) and application entity (application processor) to share information with each other in a new way with new types of information, e.g., in order for the modem entity (baseband processor) of the wireless device to have information about upcoming data transmission requirements earlier in time, as compared to some existing systems, and to utilize that that information in reducing latency for uplink transmission of the upcoming data.
  • Some embodiments may advantageously provide configurations for the wireless device modem (baseband processor) to be able to transmit the payload data (e.g., received from the application processor) with a shorter latency from arrival at the device modem entity until completion of transmission to the network node, as compared to some existing systems.
  • the payload data e.g., received from the application processor
  • a modem (baseband processor) in a wireless device provides information to an application entity (application processor) about upcoming scheduling opportunities and, in response, receives information about one or more upcoming data set(s), which are being constructed within the application entity (application processor).
  • the modem entity may be able to transmit (e.g., to the network node) a scheduling request for a data packet in an occasion (e.g., time period, slot, symbol, etc.) prior to the packet being available to the modem entity (baseband processor) for transmission.
  • a scheduling request for a data packet in an occasion (e.g., time period, slot, symbol, etc.) prior to the packet being available to the modem entity (baseband processor) for transmission.
  • Embodiments of the present disclosure may utilize some existing 3GPP signaling, and may result in reducing or minimizing the time in between (a) receiving (from the application processor) the data packet available for transmission by the modem (baseband processor), and (b) the time of the actual transmission of the packet from the wireless device to the network node.
  • Some embodiments may advantageously provide improved data transfer latency over existing systems, e.g., for XR use cases, as some configurations and use cases may result in the data packets being transmitted to the network node earlier in time, resulting in better perceived quality of experience for an end user, such as lower latency within an XR game, as compared to existing systems.
  • Some embodiments may be a wireless device implementation which may be applied to a variety of 3GPP signaling procedures. Thus, some embodiments may be implemented without requiring any adjustment to 3GPP signaling as used in existing systems, which may advantageously enable improvements in latency without requiring support for particular 3GPP version(s).
  • a wireless device for supporting configurations for low latency data communications which includes an application processor and a baseband processor.
  • the wireless device is configured to receive, at the baseband processor, a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor.
  • a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor.
  • the wireless device is configured to, responsive to receiving the pre-data indication, transmit an uplink scheduling request to the network node based on the at least one characteristic indicated in the pre-data indication, where the uplink scheduling request is transmitted to enable an immediate (e.g., in the next time slot, symbol, etc., and/or within a short time defined, for example, by a limited number of time slots, symbols, etc.) communication of the data packet upon the baseband processor receiving the data packet from the application processor.
  • an immediate e.g., in the next time slot, symbol, etc., and/or within a short time defined, for example, by a limited number of time slots, symbols, etc.
  • the application processor is configured to determine the pre-data indication based on at least one characteristic of the data packet, and prior to transmitting the data packet to the baseband processor, transmit the pre-data indication to the baseband processor.
  • the application processor is further configured to encode (and/or cause other circuitry, such as a separate digital signal processor, to perform the encoding) the data packet prior to transmitting the data packet to the baseband processor (e.g., the data, once encoded, is ready to be transmitted to the baseband processor for transmission to the network node).
  • the baseband processor is further configured to responsive to transmission of the uplink scheduling request, receive an uplink scheduling grant from the network node, receive the data packet from the application processor, and transmit the data packet to the network node (e.g., the network node which scheduled the uplink grant, or to any other network node, host computer, other wireless device, etc., of the system), according to the uplink scheduling grant.
  • the network node e.g., the network node which scheduled the uplink grant, or to any other network node, host computer, other wireless device, etc., of the system
  • the baseband processor is further configured to receive and/or determine uplink scheduling information associated with the network node and the wireless device, and transmit the uplink scheduling information to the application processor.
  • the application processor is further configured to receive the uplink scheduling information from the baseband processor, where the determining of the pre-data indication is further based on the uplink scheduling information.
  • the uplink scheduling information includes at least one of an active mode Discontinuous Reception (DRX) pattern, and an upcoming scheduling request opportunity occurring during a period of expected active DRX.
  • the baseband processor is further configured to cause transmission of the uplink scheduling request to the network node during the upcoming scheduling request opportunity.
  • DRX Discontinuous Reception
  • the application processor is further configured to transmit an initial indication to the baseband processor indicating the initiation of an application running on the application processor, where the application is at least one of a delay sensitive application and an extended reality application, and receive, responsive to the initial indication, at least one of the uplink scheduling information from the baseband processor, and a request for the pre-data indication.
  • the application processor is further configured to, determine a time of data availability associated with an encoding of the data packet, determine an upcoming scheduling request opportunity based on the uplink scheduling information, and only transmit the pre-data indication to the baseband processor when the encoding of the data packet begins prior to the upcoming scheduling request opportunity, and the time of data availability is subsequent to the upcoming scheduling request opportunity.
  • the application processor is further configured to encode (or cause other circuitry to perform the encoding of) the data packet according to at least one of a compression algorithm, and a media codec.
  • the at least one characteristic of the data packet indicated in the pre-data indication includes at least one of a size associated with the encoding of the data packet (e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression), a time of data availability associated with the encoding of the data packet, and an encoding algorithm (which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.) associated with the data packet.
  • a size associated with the encoding of the data packet e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression
  • a time of data availability associated with the encoding of the data packet
  • an encoding algorithm which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.
  • a method implemented in a wireless device for supporting configurations for low latency data communications which includes an application processor and a baseband processor is provided.
  • the method includes receiving, at the baseband processor, a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor.
  • a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor.
  • the method further includes, responsive to receiving the predata indication, transmitting an uplink scheduling request to the network node based on the at least one characteristic indicated in the pre-data indication, where the uplink scheduling request is transmitted to enable an immediate (e.g., in the next time slot, symbol, etc., and/or within a short time defined, for example, by a limited number of time slots, symbols, etc.) communication of the data packet upon the baseband processor receiving the data packet from the application processor.
  • an immediate e.g., in the next time slot, symbol, etc., and/or within a short time defined, for example, by a limited number of time slots, symbols, etc.
  • the method further includes, at the application processor, determining the pre-data indication based on at least one characteristic of the data packet, and prior to transmitting the data packet to the baseband processor, transmitting the pre-data indication to the baseband processor.
  • the method further includes encoding (and/or causing other circuitry, such as a separate digital signal processor, to perform the encoding of) the data packet prior to transmitting the data packet to the baseband processor (e.g., the data, once encoded, is ready to be transmitted to the baseband processor for transmission to the network node).
  • the method further includes, responsive to transmission of the uplink scheduling request, receiving an uplink scheduling grant from the network node, receiving the data packet from the application processor, and transmitting the data packet to the network node (e.g., the network node which scheduled the uplink grant, or to any other network node, host computer, other wireless device, etc., of the system), according to the uplink scheduling grant.
  • the network node e.g., the network node which scheduled the uplink grant, or to any other network node, host computer, other wireless device, etc., of the system
  • the method further includes, at the baseband processor, receiving and/or determining uplink scheduling information associated with the network node and the wireless device, and transmit the uplink scheduling information to the application processor.
  • the method further includes, at the application processor, receiving the uplink scheduling information from the baseband processor, where the determining of the pre-data indication is further based on the uplink scheduling information.
  • the uplink scheduling information includes at least one of an active mode Discontinuous Reception (DRX) pattern, and an upcoming scheduling request opportunity occurring during a period of expected active DRX.
  • the method further includes, at the baseband processor, causing transmission of the uplink scheduling request to the network node during the upcoming scheduling request opportunity.
  • DRX Discontinuous Reception
  • the method further includes, at the application processor, transmitting an initial indication to the baseband processor indicating the initiation of an application running on the application processor, where the application is at least one of a delay sensitive application and an extended reality application, and receive, responsive to the initial indication, at least one of the uplink scheduling information from the baseband processor, and a request for the pre-data indication.
  • the method further includes, at the application processor, determining a time of data availability associated with an encoding of the data packet, determining an upcoming scheduling request opportunity based on the uplink scheduling information, and only transmitting the pre-data indication to the baseband processor when the encoding of the data packet begins prior to the upcoming scheduling request opportunity, and the time of data availability is subsequent to the upcoming scheduling request opportunity.
  • the method further includes encoding (or cause other circuitry to perform the encoding of) the data packet according to at least one of a compression algorithm, and a media codec.
  • the at least one characteristic of the data packet indicated in the pre-data indication includes at least one of a size associated with the encoding of the data packet (e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression), a time of data availability associated with the encoding of the data packet, and an encoding algorithm (which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.) associated with the data packet.
  • a size associated with the encoding of the data packet e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression
  • a time of data availability associated with the encoding of the data packet
  • an encoding algorithm which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.
  • a wireless communication system including a wireless device and a network node for supporting configurations for low latency data communications.
  • the wireless device includes an application processor and a baseband processor.
  • the wireless device is configured to receive, at the baseband processor, a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor.
  • the wireless device is configured to, responsive to receiving the pre-data indication, transmit an uplink scheduling request to the network node based on the at least one characteristic indicated in the pre-data indication, where the uplink scheduling request is transmitted to enable an immediate (e.g., in the next time slot, symbol, etc., or within a short time defined, for example, by a limited number of time slots, symbols, etc.) communication of the data packet upon the baseband processor receiving the data packet from the application processor.
  • the network node is configured to receive the uplink scheduling request from the wireless device.
  • the network node is configured to determine an uplink scheduling grant based on the uplink scheduling request.
  • the network node is configured to transmit the scheduling grant to the wireless device.
  • the application processor is configured to determine the pre-data indication based on at least one characteristic of the data packet, and prior to transmitting the data packet to the baseband processor, transmit the pre-data indication to the baseband processor.
  • the application processor is further configured to encode (and/or cause other circuitry, such as a separate digital signal processor, to perform the encoding) the data packet prior to transmitting the data packet to the baseband processor (e.g., the data, once encoded, is ready to be transmitted to the baseband processor for transmission to the network node).
  • the baseband processor is further configured to responsive to transmission of the uplink scheduling request, receive an uplink scheduling grant from the network node, receive the data packet from the application processor, and transmit the data packet to the network node (e.g., the network node which scheduled the uplink grant, or to any other network node, host computer, other wireless device, etc., of the system), according to the uplink scheduling grant.
  • the network node e.g., the network node which scheduled the uplink grant, or to any other network node, host computer, other wireless device, etc., of the system
  • the baseband processor is further configured to receive and/or determine uplink scheduling information associated with the network node and the wireless device, and transmit the uplink scheduling information to the application processor.
  • the application processor is further configured to receive the uplink scheduling information from the baseband processor, where the determining of the pre-data indication is further based on the uplink scheduling information.
  • the uplink scheduling information includes at least one of an active mode Discontinuous Reception (DRX) pattern, and an upcoming scheduling request opportunity occurring during a period of expected active DRX.
  • the baseband processor is further configured to cause transmission of the uplink scheduling request to the network node during the upcoming scheduling request opportunity.
  • DRX Discontinuous Reception
  • the application processor is further configured to transmit an initial indication to the baseband processor indicating the initiation of an application running on the application processor, where the application is at least one of a delay sensitive application and an extended reality application, and receive, responsive to the initial indication, at least one of the uplink scheduling information from the baseband processor, and a request for the pre-data indication.
  • the application processor is further configured to, determine a time of data availability associated with an encoding of the data packet, determine an upcoming scheduling request opportunity based on the uplink scheduling information, and only transmit the pre-data indication to the baseband processor when the encoding of the data packet begins prior to the upcoming scheduling request opportunity, and the time of data availability is subsequent to the upcoming scheduling request opportunity.
  • the application processor is further configured to encode (or cause other circuitry to perform the encoding of) the data packet according to at least one of a compression algorithm, and a media codec.
  • the at least one characteristic of the data packet indicated in the pre-data indication includes at least one of a size associated with the encoding of the data packet (e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression), a time of data availability associated with the encoding of the data packet, and an encoding algorithm (which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.) associated with the data packet.
  • a size associated with the encoding of the data packet e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression
  • a time of data availability associated with the encoding of the data packet
  • an encoding algorithm which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.
  • a method implemented in a wireless communication system including a wireless device and a network node for supporting configurations for low latency data communications.
  • the wireless device includes an application processor and a baseband processor.
  • the method includes receiving, at the baseband processor, a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor.
  • a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor.
  • the method includes, responsive to receiving the pre-data indication at the baseband processor, transmitting an uplink scheduling request to the network node based on the at least one characteristic indicated in the pre-data indication, where the uplink scheduling request is transmitted to enable an immediate (e.g., in the next time slot, symbol, etc., or within a short time defined, for example, by a limited number of time slots, symbols, etc.) communication of the data packet upon the baseband processor receiving the data packet from the application processor.
  • the method further includes, at the network node, receiving the uplink scheduling request from the wireless device, determining an uplink scheduling grant based on the uplink scheduling request, and transmitting the scheduling grant to the wireless device.
  • the method further includes, at the application processor, determining the pre-data indication based on at least one characteristic of the data packet, and prior to transmitting the data packet to the baseband processor, transmitting the pre-data indication to the baseband processor.
  • the method further includes encoding (and/or causing other circuitry, such as a separate digital signal processor, to perform the encoding of) the data packet prior to transmitting the data packet to the baseband processor (e.g., the data, once encoded, is ready to be transmitted to the baseband processor for transmission to the network node).
  • the method further includes, responsive to transmission of the uplink scheduling request, receiving an uplink scheduling grant from the network node, receiving the data packet from the application processor, and transmitting the data packet to the network node (e.g., the network node which scheduled the uplink grant, or to any other network node, host computer, other wireless device, etc., of the system), according to the uplink scheduling grant.
  • the network node e.g., the network node which scheduled the uplink grant, or to any other network node, host computer, other wireless device, etc., of the system
  • the method further includes, at the baseband processor, receiving and/or determining uplink scheduling information associated with the network node and the wireless device; and transmit the uplink scheduling information to the application processor.
  • the method further includes, at the application processor, receiving the uplink scheduling information from the baseband processor, where the determining of the pre-data indication is further based on the uplink scheduling information.
  • the uplink scheduling information includes at least one of an active mode Discontinuous Reception (DRX) pattern, and an upcoming scheduling request opportunity occurring during a period of expected active DRX.
  • the method further includes, at the baseband processor, causing transmission of the uplink scheduling request to the network node during the upcoming scheduling request opportunity.
  • DRX Discontinuous Reception
  • the method further includes, at the application processor, transmitting an initial indication to the baseband processor indicating the initiation of an application running on the application processor, where the application is at least one of a delay sensitive application and an extended reality application, and receive, responsive to the initial indication, at least one of the uplink scheduling information from the baseband processor, and a request for the pre-data indication.
  • the method further includes, at the application processor, determining a time of data availability associated with an encoding of the data packet, determining an upcoming scheduling request opportunity based on the uplink scheduling information, and only transmitting the pre-data indication to the baseband processor when the encoding of the data packet begins prior to the upcoming scheduling request opportunity, and the time of data availability is subsequent to the upcoming scheduling request opportunity.
  • the method further includes encoding (or cause other circuitry to perform the encoding of) the data packet according to at least one of a compression algorithm, and a media codec.
  • the at least one characteristic of the data packet indicated in the pre-data indication includes at least one of a size associated with the encoding of the data packet (e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression), a time of data availability associated with the encoding of the data packet, and an encoding algorithm (which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.) associated with the data packet.
  • a size associated with the encoding of the data packet e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression
  • a time of data availability associated with the encoding of the data packet
  • an encoding algorithm which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.
  • FIG. l is a timing diagram illustrating an example packet scheduling and transmission latency
  • FIG. 2 is a timing diagram illustrating examples of some embodiments of the present disclosure reducing a total latency time in conjunction with other techniques
  • FIG. 3 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG. 4 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 5 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure
  • FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure
  • FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure
  • FIG. 9 is a flowchart of an example process in a wireless device for supporting configurations for low latency data communications, according to some embodiments of the present disclosure.
  • FIG. 10 is a flowchart of an example process in a wireless communication system including a wireless device and a network node for supporting configurations for low latency data communications, according to some embodiments of the present disclosure
  • FIG. 11 is a timing diagram illustrating an example configuration according to some embodiments of the present disclosure.
  • FIG. 12 is a timing diagram illustrating another example configuration according to some embodiments of the present disclosure.
  • FIG. 13 is a block diagram illustrating an example wireless device according to some embodiments of the present disclosure.
  • FIG. 14 is a flowchart of an example process in a wireless communication system including a wireless device and a network node for supporting configurations for low latency data communications, according to some embodiments of the present disclosure
  • FIG. 15 is a signaling diagram illustrating an example embodiment for low latency data communication according to some embodiments of the present disclosure
  • FIG. 16 is a block diagram illustrating an example process flow for an application processor and baseband processor in a wireless device according to some embodiments of the present disclosure
  • FIG. 17 is a timing diagram illustrating an example configuration according to some embodiments of the present disclosure.
  • FIG. 18 is a timing diagram illustrating another example configuration according to some embodiments of the present disclosure.
  • relational terms such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term, “in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • Coupled may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • network node can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (
  • BS base station
  • wireless device or a user equipment (UE) are used interchangeably.
  • the WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD).
  • the WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.
  • D2D device to device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • Tablet mobile terminals
  • smart phone laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles
  • CPE Customer Premises Equipment
  • LME Customer Premises Equipment
  • NB-IOT Narrowband loT
  • radio network node can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
  • RNC evolved Node B
  • MCE Multi-cell/multicast Coordination Entity
  • IAB node IAB node
  • relay node access point
  • radio access point radio access point
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.
  • the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • immediate may refer to transmission being processed and transmitted, e.g., by one or more of a baseband processor, modem entity, radio circuitry, etc., within an abbreviated and/or short time period after receipt of the data from the application processor.
  • the immediate communication may imply a transmission of the data packet at an indicated transmission resource allocated by the network node to the wireless device as a response to the scheduling request.
  • immediate may be used to characterize a transmission to a network node occurring within next available uplink transport block or according to a data channel transmit opportunity indicated by a scheduling grant, for example within 100 milliseconds of receipt of data by the baseband processor.
  • the next available transport block or a transmit opportunity may in in some configurations mean an indicated transmit resource in time and/or frequency which is specifically appointed to the device as result of the transmitted scheduling request.
  • Other definitions, configurations, etc. may be used to achieve “immediate” transmission, as described herein, e.g., where “immediate” may be defined as being within 100 microseconds, 10 milliseconds, 100 milliseconds, 7 symbols, 2 slots, etc.,.
  • immediate communication may indicate that the scheduling request that is used for the transmission of a data packet incoming to the baseband processor from the application processor, is a scheduling request that corresponds to a network resource for transmission, or channel transmit opportunity, that is first available in time after the transmission of the data packet to the baseband processor.
  • immediate communication may also indicate that the scheduling request that is used for the transmission of a data packet incoming to the baseband processor from the application processor, is a scheduling request that corresponds to a network resource for transmission, or channel transmit opportunity, that is second available in time after the transmission of the data packet to the baseband processor.
  • modem entity may refer to one or more of a baseband processor, modem, radio circuitry, radio interface, antenna hardware, etc., which, for example, may receive data (e.g., data packets) from an application processor or other processing circuitry, and may prepare/process/modulate/convert/etc. the data for wireless transmission (e.g., using the antennas) to a network node (e.g., base station) or other wireless device.
  • data e.g., data packets
  • an application processor or other processing circuitry may prepare/process/modulate/convert/etc. the data for wireless transmission (e.g., using the antennas) to a network node (e.g., base station) or other wireless device.
  • network node e.g., base station
  • application entity may refer to one or more of an application processor, a general purpose central processing unit (CPU), a virtual processor, a system on a chip (SoC), a graphic processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), or other similar processing circuitry which runs and/or configures applications (e.g., XR applications), which receives, processes, encodes, compresses, generates, etc., application data, such as sensor data, video/audio/media data, motion data, etc., and which may communicate with other hardware in the wireless device, such as the “modem entity”, e.g., for transmission of the data to other entities in the network/system.
  • applications e.g., XR applications
  • modem entity e.g., for transmission of the data to other entities in the network/system.
  • FIG. 3 a schematic diagram of a communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14.
  • the access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18).
  • Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20.
  • a first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a.
  • a second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.
  • a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16.
  • a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR.
  • WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
  • the communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30.
  • the intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more subnetworks (not shown).
  • the communication system of FIG. 3 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.
  • a wireless device 22 is configured to include a data unit 32, e.g., in an application processor 31, which is which is configured for supporting low-latency data communication, according to some embodiments of the present disclosure.
  • a wireless device 22 is configured to include a scheduling unit 34, e.g., in a baseband processor 33, which is which is configured for supporting low-latency data communication, according to some embodiments of the present disclosure.
  • a network node 16 is configured to include a network configuration unit 35, which is configured for supporting low-latency data communication, according to some embodiments of the present disclosure.
  • a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities.
  • the processing circuitry 42 may include a processor 44 and memory 46.
  • the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 46 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24.
  • Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein.
  • the host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24.
  • the instructions may be software associated with the host computer 24.
  • the software 48 may be executable by the processing circuitry 42.
  • the software 48 includes a host application 50.
  • the host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the host application 50 may provide user data which is transmitted using the OTT connection 52.
  • the “user data” may be data and information described herein as implementing the described functionality.
  • the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.
  • the processing circuitry 42 of the host computer 24 may include a cloud configuration unit 54 configured to enable the service provider to observe/monitor/ control/transmit to/receive from/etc. the network node 16 and or the wireless device 22, e.g., for supporting configurations of low-latency data traffic.
  • the communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22.
  • the hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16.
  • the radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the communication interface 60 may be configured to facilitate a connection 66 to the host computer 24.
  • the connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.
  • the hardware 58 of the network node 16 further includes processing circuitry 68.
  • the processing circuitry 68 may include a processor 70 and a memory 72.
  • the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read- Only Memory).
  • the memory 72 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read- Only Memory).
  • the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection.
  • the software 74 may be executable by the processing circuitry 68.
  • the processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16.
  • Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein.
  • the memory 72 is configured to store data, programmatic software code and/or other information described herein.
  • the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.
  • processing circuitry 68 of the network node 16 may include network configuration unit 35 configured to support configurations of low-latency data traffic.
  • the communication system 10 further includes the WD 22 already referred to.
  • the WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located.
  • the radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the hardware 80 of the WD 22 further includes processing circuitry 84.
  • the processing circuitry 84 may include an application processor 31, baseband processor 33, and memory 88.
  • the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the application processor 31 and/or baseband processor 33 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 88 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22.
  • the software 90 may be executable by the processing circuitry 84.
  • the software 90 may include a client application 92.
  • the client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24.
  • an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the client application 92 may receive request data from the host application 50 and provide user data in response to the request data.
  • the OTT connection 52 may transfer both the request data and the user data.
  • the client application 92 may interact with the user to generate the user data that it provides.
  • the processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22.
  • the application processor 31 and baseband processor 33 correspond to one or more processors for performing WD 22 functions described herein.
  • the WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 90 and/or the client application 92 may include instructions that, when executed by the application processor 31, baseband processor 33, and/or processing circuitry 84, causes the processor 31, baseband processor 33, and/or processing circuitry 84 to perform the processes described herein with respect to WD 22.
  • the processing circuitry 84 of the wireless device 22 may include a data unit 32 in application processor 31 which is which is configured for supporting low-latency data communication, according to some embodiments of the present disclosure, a scheduling unit 34 in baseband processor 33, which is which is configured for supporting low-latency data communication, according to some embodiments of the present disclosure.
  • the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 3.
  • the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.
  • the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22.
  • the cellular network also includes the network node 16 with a radio interface 62.
  • the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.
  • the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16.
  • the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing, terminating, maintaining, supporting, ending, etc., receipt of a transmission from the network node 16.
  • FIGS. 3 and 4 show various “units” such as data unit 32, scheduling unit 34, network configuration unit 35, and cloud configuration unit 54 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 5 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 3 and 4, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 4.
  • the host computer 24 provides user data (Block SI 00).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02).
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04).
  • the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06).
  • the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).
  • FIG. 6 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4.
  • the host computer 24 provides user data (Block SI 10).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50.
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12).
  • the transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the WD 22 receives the user data carried in the transmission (Block SI 14).
  • FIG. 7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4.
  • the WD 22 receives input data provided by the host computer 24 (Block SI 16).
  • the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18).
  • the WD 22 provides user data (Block S120).
  • the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122).
  • client application 92 may further consider user input received from the user.
  • the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124).
  • the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
  • FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4.
  • the network node 16 receives user data from the WD 22 (Block S128).
  • the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130).
  • the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).
  • FIG. 9 is a flowchart of an example process in a wireless device 22 for supporting configurations for low latency data communications.
  • One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the application processor 31, data unit 32, baseband processor 33, and scheduling unit 34), memory 88, and/or radio interface 82.
  • Wireless device 22 is configured to receive (Block SI 34), at the baseband processor 33, a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor 31.
  • Block SI 34 Block SI 34
  • a pre-data indication indicating at least one characteristic of an upcoming data packet e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which
  • Wireless device 22 is configured to, responsive to receiving the pre-data indication, cause transmission (Block SI 36) of an uplink scheduling request to the network node 16 based on the at least one characteristic indicated in the pre-data indication, where the uplink scheduling request is transmitted to enable an immediate (e.g., in the next time slot, symbol, etc., or within a short time defined, for example, by a limited number of time slots, symbols, etc.) communication of the data packet upon the baseband processor 33 receiving the data packet from the application processor 31.
  • Block SI 36 transmission of an uplink scheduling request to the network node 16 based on the at least one characteristic indicated in the pre-data indication, where the uplink scheduling request is transmitted to enable an immediate (e.g., in the next time slot, symbol, etc., or within a short time defined, for example, by a limited number of time slots, symbols, etc.) communication of the data packet upon the baseband processor 33 receiving the data packet from the application processor 31.
  • the application processor 31 is configured to determine the pre-data indication based on at least one characteristic of the data packet, and prior to transmitting the data packet to the baseband processor 33, transmit the pre-data indication to the baseband processor 33.
  • the application processor 31 is further configured to encode (and/or cause other circuitry, such as a separate digital signal processor, to perform the encoding) the data packet prior to transmitting the data packet to the baseband processor 33 (e.g., the data, once encoded, is ready to be transmitted to the baseband processor 33 for transmission to the network node 16).
  • the baseband processor 33 is further configured to responsive to transmission of the uplink scheduling request, receive an uplink scheduling grant from the network node 16, receive the data packet from the application processor 31, and transmit the data packet to the network node 16 (e.g., the network node 16 which scheduled the uplink grant, or to any other network node 16, host computer 24, other wireless device 22, etc., of the system 10), according to the uplink scheduling grant.
  • the network node 16 e.g., the network node 16 which scheduled the uplink grant, or to any other network node 16, host computer 24, other wireless device 22, etc., of the system 10
  • the baseband processor 33 is further configured to receive and/or determine uplink scheduling information associated with the network node 16 and the wireless device 22, and transmit the uplink scheduling information to the application processor 31.
  • the application processor 31 is further configured to receive the uplink scheduling information from the baseband processor 33, where the determining of the pre-data indication is further based on the uplink scheduling information.
  • the uplink scheduling information includes at least one of an active mode Discontinuous Reception (DRX) pattern, and an upcoming scheduling request opportunity occurring during a period of expected active DRX.
  • DRX Discontinuous Reception
  • the baseband processor 33 is further configured to cause transmission of the uplink scheduling request to the network node 16 during the upcoming scheduling request opportunity.
  • the application processor 31 is further configured to transmit an initial indication to the baseband processor 33 indicating the initiation of an application running on the application processor 31, where the application is at least one of a delay sensitive application and an extended reality application, and receive, responsive to the initial indication, at least one of the uplink scheduling information from the baseband processor 33, and a request for the pre-data indication.
  • the application processor 31 is further configured to, determine a time of data availability associated with an encoding of the data packet, determine an upcoming scheduling request opportunity based on the uplink scheduling information, and only transmit the pre-data indication to the baseband processor 33 when the encoding of the data packet begins prior to the upcoming scheduling request opportunity, and the time of data availability is subsequent to the upcoming scheduling request opportunity.
  • the application processor 31 is further configured to encode (or cause other circuitry to perform the encoding of) the data packet according to at least one of a compression algorithm, and a media codec.
  • the at least one characteristic of the data packet indicated in the pre-data indication includes at least one of a size associated with the encoding of the data packet (e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression), a time of data availability associated with the encoding of the data packet, and an encoding algorithm (which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.) associated with the data packet.
  • a size associated with the encoding of the data packet e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression
  • a time of data availability associated with the encoding of the data packet
  • an encoding algorithm which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.
  • FIG. 10 is a flowchart of an example process in a wireless communication system 10 including a wireless device 22 and a network node 16 according to some embodiments of the present for supporting configurations for low latency data communications.
  • One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the application processor 31, data unit 32, baseband processor 33, and scheduling unit 34), radio interface 82 and/or memory 88, and/or by one or more elements of network node 16 such as by one or more of processing circuitry 68, processor 70 (including network configuration unit 35), radio interface 62 and/or communication interface 60.
  • Wireless device 22 is configured to receive (Block S138), at the baseband processor 33, a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor 31.
  • a pre-data indication indicating at least one characteristic of an upcoming data packet (e.g., a single data packet, a plurality of data packets, or similar data structures/data streams, which may contain, e.g., video data, audio data, extended reality data, data streams, etc.) from the application processor 31.
  • the wireless device 22 is configured to, responsive to receiving the pre-data indication, transmit (Block SI 40) an uplink scheduling request to the network node 16 based on the at least one characteristic indicated in the pre-data indication, where the uplink scheduling request is transmitted to enable an immediate (e.g., in the next time slot, symbol, etc., or within a short time defined, for example, by a limited number of time slots, symbols, etc.) communication of the data packet upon the baseband processor 33 receiving the data packet from the application processor 31.
  • the network node 16 is configured to receive (Block S142) the uplink scheduling request from the wireless device 22.
  • the network node 16 is configured to determine (Block S144) an uplink scheduling grant based on the uplink scheduling request.
  • the network node is configured to transmit (Block S146) the scheduling grant to the wireless device 22.
  • the application processor 31 is configured to determine the pre-data indication based on at least one characteristic of the data packet, and prior to transmitting the data packet to the baseband processor 33, transmit the pre-data indication to the baseband processor 33.
  • the application processor 31 is further configured to encode (and/or cause other circuitry, such as a separate digital signal processor, to perform the encoding) the data packet prior to transmitting the data packet to the baseband processor 33 (e.g., the data, once encoded, is ready to be transmitted to the baseband processor 33 for transmission to the network node 16).
  • the baseband processor 33 is further configured to responsive to transmission of the uplink scheduling request, receive an uplink scheduling grant from the network node 16, receive the data packet from the application processor 31, and transmit the data packet to the network node 16 (e.g., the network node 16 which scheduled the uplink grant, or to any other network node 16, host computer 24, other wireless device 22, etc., of the system 10), according to the uplink scheduling grant.
  • the network node 16 e.g., the network node 16 which scheduled the uplink grant, or to any other network node 16, host computer 24, other wireless device 22, etc., of the system 10
  • the baseband processor 33 is further configured to receive and/or determine uplink scheduling information associated with the network node 16 and the wireless device 22, and transmit the uplink scheduling information to the application processor 31.
  • the application processor 31 is further configured to receive the uplink scheduling information from the baseband processor 33, where the determining of the pre-data indication is further based on the uplink scheduling information.
  • the uplink scheduling information includes at least one of an active mode Discontinuous Reception (DRX) pattern, and an upcoming scheduling request opportunity occurring during a period of expected active DRX.
  • DRX Discontinuous Reception
  • the baseband processor 33 is further configured to cause transmission of the uplink scheduling request to the network node 16 during the upcoming scheduling request opportunity.
  • the application processor 31 is further configured to transmit an initial indication to the baseband processor 33 indicating the initiation of an application running on the application processor 31, where the application is at least one of a delay sensitive application and an extended reality application, and receive, responsive to the initial indication, at least one of the uplink scheduling information from the baseband processor 33, and a request for the pre-data indication.
  • the application processor 31 is further configured to, determine a time of data availability associated with an encoding of the data packet, determine an upcoming scheduling request opportunity based on the uplink scheduling information, and only transmit the pre-data indication to the baseband processor 33 when the encoding of the data packet begins prior to the upcoming scheduling request opportunity, and the time of data availability is subsequent to the upcoming scheduling request opportunity.
  • the application processor 31 is further configured to encode (or cause other circuitry to perform the encoding of) the data packet according to at least one of a compression algorithm, and a media codec.
  • the at least one characteristic of the data packet indicated in the pre-data indication includes at least one of a size associated with the encoding of the data packet (e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression), a time of data availability associated with the encoding of the data packet, and an encoding algorithm (which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.) associated with the data packet.
  • a size associated with the encoding of the data packet e.g., corresponding to the size of the data packet before encoding/compression, or to the (expected) size of the data packet after encoding/compression
  • a time of data availability associated with the encoding of the data packet
  • an encoding algorithm which may be characterized by, e.g., compression rate, computation time needed for the encoding, etc.
  • total latency may be improved, e.g., compared to existing systems, by an application entity (application processor 31) transmitting a preindication to modem entity (baseband processor 33) including information about upcoming delay sensitive data packet.
  • application entity application processor 31
  • baseband processor 33 modem entity
  • the effect is that the modem (e.g., baseband processor 33) can send scheduling requests (e.g., to network node 16, via radio interface 82, radio interface 62, etc.) at an earlier time, as compared to existing systems.
  • the time to transmit data packet burst may be reduced if the wireless device 22 is configured to send the scheduling request earlier (as compared to existing systems).
  • FIG. 11 which may correspond to an example legacy configuration
  • the data frame generation by the application processor 31 at time T1 to time T2 precedes the transmission to the modem (baseband processor 33) of the data at time T3.
  • the scheduling request is sent at time T4, and the network node 16 replies with a scheduling grant.
  • the data and BSR is transmitted at T5 and T6 according to the scheduling grant.
  • scheduling request opportunities may not be utilized prior to T3.
  • FIG. 12 which may correspond to an example modification of the legacy configuration of FIG.
  • the application processor 31 sends the pre-data indication to the baseband processor 33 regarding the data being encoded/generated/etc.
  • the baseband processor 33 determines an appropriate scheduling request for the data indicated by the pre-data indication, and causes transmission of the scheduling request to a network node 16 at time T2.
  • the data frame generation and/or encoding by the application processor 31 occurs (e.g., in parallel) and the generated/encoded data is received at baseband processor 33 at time T3.
  • the baseband processor 33 receives a scheduling grant from the network node 16 based on the scheduling request, and the data and BSR are transmitted at T4 and T5 based on the scheduling grant.
  • FIG. 13 is a block diagram illustrating an example wireless device 22 according to some embodiments of the present disclosure, which may be the wireless device 22 of FIG. 3 and/or FIG. 4.
  • the wireless device 22 includes an application entity, which may be an application processor 31 or similar entity.
  • the wireless device 22 further includes a modem entity, which may be a baseband processor 33 or similar entity, and may also include and/or interact with radio interface 82 and/or other radio/antenna hardware and/or other radio processing circuitry.
  • the application processor 31 (application entity) and baseband processor 33 (modem entity) may communicate via an interface 96, e.g., Application-Modem Application Programming Interface (API) 96, which may include/refer to the connecting hardware (e.g., wires, interconnect layers, buses, buffers, pins, etc.), software/firmware, and/or protocols for transferring signals (data, control information, etc.) between application processor 31 and baseband processor 33.
  • the application processor 31 may be configured to run one or more applications 98a, 98b, 98c, ..., 98n (collectively, Applications 98), which may be low- latency applications, such as XR, gaming, etc.
  • Baseband processor 33 may be configured to run, configure, support, and/or interface with one or more modems 100a, 100b, etc. (collectively, modems 100), which may include hardware, software, firmware, etc., for performing baseband processing operations for wireless communication, such as communicating with radio interface 82, to transmit and receive radio signals with one or more network node 16 and/or other wireless devices 22 using one or more antennas.
  • modems 100 may include hardware, software, firmware, etc., for performing baseband processing operations for wireless communication, such as communicating with radio interface 82, to transmit and receive radio signals with one or more network node 16 and/or other wireless devices 22 using one or more antennas.
  • the baseband processor 33 (e.g., via modem 100a) may be configured for 3GPP radio protocol transmission/reception, e.g., via one or more radio access protocol transmission layers, and may include transmit and receive functionalities according to one or more communication protocols, such as 3GPP NR.
  • Application 98a data may be generated in the application processor 31, and may be temporarily stored in memory 88 (e.g., one or more buffers) prior to transmission to network node 16.
  • Application 98a data may be encoded, e.g., according to one or more video/audio/media/etc. codecs, encryption algorithms, error coding algorithms, etc., prior to being transmitted from application processor 31 to baseband processor 33.
  • the application processor 31 and baseband processor 33 may be implemented on separate chips, semiconductor devices, circuitry, etc., while in other embodiments, the application processor 31 and baseband processor 33 may be implemented on the same chip, semiconductor device(s), circuitry, etc.
  • the application processor 31 and baseband processor 33 may be physically the same entity but logically separate, or they may be both logically and physically separate.
  • there may be additional chips, circuits, processors, etc. for instance, an application processor 31 and a digital signal processor (not shown), which may perform various data processing, encoding, etc., functionalities, and may provide the processed/encoded/etc. data for the baseband processor 33 to transmit to the network node 16 (e.g., via modem 100a and/or 100b, radio interface 82, etc.).
  • the signaling of scheduling requests and data transfer to the network node 16 may be performed by the baseband processor 33 (e.g., via modem 100a, radio interface 82, etc.).
  • the application processor 31 may execute one or more operating systems on which one or more applications 98 may be running.
  • the wireless device 22 application processor 31 may include/execute an XR gaming application, wherein data from the wireless device 22 may be generated depending, e.g., on an end user’s gestures and movements, environment, etc..
  • the gaming experience is likely to be worse the longer time it takes for data generated in the application processor 31, e.g., by an end user’s motion, until the data has been transferred from the wireless device 22 to network node 16, e.g., by the baseband processor 33 (via modem 100a, radio interface 82, etc.).
  • sidelink communication between two wireless devices 22 may utilize similar uplink resource scheduling techniques as applied to communication between the wireless device 22 and network node 16.
  • FIG. 14 is a flowchart illustrating an example process for low-latency traffic optimization according to some embodiments of the present disclosure.
  • a delay sensitive application 98 is started in an application entity (application processor 31).
  • the modem entity (baseband processor 33) identifies upcoming scheduling events/opportunities (Step SI 50).
  • the modem entity (baseband processor 33) sends information of upcoming scheduling events to the application entity (application processor 31) (Step SI 52).
  • a pre-data indication/information is sent from the application entity (application processor 31) to the modem entity (baseband processor 33) (Step SI 54).
  • the modem entity (baseband processor 33) utilizes pre-data information in the pre-data indication to determine and send scheduling request(s) to the network node 16 (Step SI 56).
  • the modem entity (baseband processor 33) receives the data packet from the application entity (application processor 31) according to the pre-data information (Step S158).
  • the modem entity (baseband processor 33) is scheduled to transmit resources according to the scheduling request, and transfers the data (Step SI 60).
  • the baseband processor 33 and/or application processor 31 determines whether the application session hassEpjended (Step SI 62). If not, the flow may return to Step SI 54, for additional pre-data indications for additional data streams, packets, etc. If the session has ended, then the flow may proceed to Step S164, and the application entity (application processor 31) may notify the modem entity (baseband processor 33) of the ending of the session.
  • Embodiments of the present disclosure may provide an additional traffic aware signaling mechanism between the application processor 31 and the baseband processor 33.
  • FIG. 15 is a signaling diagram illustrating an example embodiment of the present disclosure, which may correspond to one or more of the steps of FIG. 14.
  • FIG. 15 an example of the type(s) of information transferred according to the signaling mechanism for signaling between the application processor 31 and the baseband processor 33 is described. It is to be understood that the steps illustrated in the example of FIG. 15 may in practice occur in different orders, may be repeated, etc., without deviating from the present disclosure. Further, one or more steps may be omitted, e.g., the illustrated steps may occur in different orders than what is depicted in the figures.
  • the application processor 31 provides information to the baseband processor 33 about a delay sensitive application 98a initiation in Step SI 66.
  • the application processor 31 may transmit such information to the baseband processor 33 upon initiating a XR game session over a wireless communication link (e.g., wireless connection 64) with network node 16 (e.g., a base station, or, in the case of sidelink communication, another wireless device 22).
  • a wireless communication link e.g., wireless connection 64
  • network node 16 e.g., a base station, or, in the case of sidelink communication, another wireless device 22.
  • the baseband processor 33 identifies/determines information about one or more upcoming future radio resource scheduling event.
  • This may be implemented as a legacy functionality, because a wireless device 22 operating, e.g., in a 3 GPP NR system, may be informed by a serving network node 16 about at least one data scheduling opportunity upon being connected to the network.
  • the network node 16 may provide time slot information about upcoming possibilities for the wireless device 22 to transmit scheduling requests.
  • the network node 16 may provide information to the wireless device 22 about upcoming active and non-active periods for wireless device 22 power savings while the wireless device 22 is in active mode (active mode DRX pattern). These types of information may be combined in the wireless device 22 in order to identify, e.g., one or more future time slots for scheduling request transmissions which occurs during a period of expected active DRX.
  • the baseband processor 33 may transmit information about upcoming future radio resource scheduling events to the application processor 31. This step may be considered optional in some embodiments, as the application processor 31 may not need this information in some use cases or configurations.
  • this indicator of Step S168 may be used as an indicator to the application processor 31 that the baseband processor 33 may be ready to operate in this mode (e.g., low latency mode), but the application processor 31 may not necessarily use it. It may be an indicator, e.g., of whether the baseband processor 33 is in a highly active state.
  • Opportunities to transmit the scheduling request may, in some embodiments and configurations, be periodic.
  • an application processor 31 may be configured to utilize information regarding periodic scheduling request to configure sending a pre-data indication, e.g., when the application processor 31 has some information regarding uplink data which may be utilized in time for a periodic scheduling request.
  • an application processor 31 may be configured to consider the amount of time until the scheduling request to determine whether to send the pre-data indication to the baseband processor 33.
  • the application processor 31 may as a new function thereafter transmit a pre-data-indication (Step S170) to the baseband processor 33.
  • a pre-data-indication may be transmitted when a data packet has been started to be generated, but before the data packet is ready for transmission to the application processor 31.
  • the pre-data indication from the application processor 31 to the baseband processor 33 may indicate an expected time (e.g., relative time, absolute time, time slot, etc.) of the application 98a data to be available, may indicate a size of the data (e.g., number of packets, bits per packet, etc.), may indicate a latency requirement/budget/etc., and/or other information about the data.
  • the baseband processor 33 may be configured to determine whether it can use this information (i.e., the pre-data indication information) to determine and transmit scheduling requests to the network node 16.
  • the baseband processor 33 may be configured with information regarding the expected time in between the scheduling request being sent to a network node 16 until the time an uplink resource allocation and/or grant is received responsive to the scheduling request. This amount of time may be defined by a radio protocol, for example.
  • the size of a data packet may be known or predictable by the application layer (e.g., of the application processor 31), even prior to the data packet being generated.
  • the application layer e.g., of the application processor 31
  • the application processor 31 may be configured to generate and/or encode this data (e.g., the application processor 31 may have one or more data encoder units).
  • encoding may include data compression, may include combining and compression, e.g., of data from multiple sensors.
  • the application processor 31 may determine a pre-data indication, and may the indication to the baseband processor 33, e.g., as soon as the video packet is started to be generated, which may be prior to the encoding being initiated and/or prior to the encoding being complete.
  • the transmission of the pre-data indication from application processor 31 to baseband processor 33 may, in some embodiments, be conditionally triggered.
  • trigger condition may include, e.g., imposing a restriction that the pre-data indication may only be transmitted if the data packet generation has been initiated prior to an upcoming scheduling event, with the additional condition that the data packet will be available only after the event.
  • the legacy method of transmitting SR upon receiving the data may be configured/selected, for example, because there may be no benefit from the pre-indication under such condition, and the pre-indication may be omitted/restricted in the configuration when such condition is detected at the application processor 31.
  • the baseband processor 33 may utilize the pre-data indication for determining and transmitting (Step SI 72) a scheduling request to network node 16, thereby triggering data resource scheduling (e.g., for uplink data traffic) for the wireless device 22.
  • Step SI 74 Once the data from the application 98a of application processor 31 arrives to the baseband processor 33 (Step SI 74), based on the pre-data indication, when the baseband processor 33 has already transferred an appropriate scheduling request to the network node 16, it may finalize (complete) the data transmission to the network node 16 earlier than if the pre-indication had not been used.
  • a scheduling grant is received (Step SI 76) from the network node 16, and the baseband processor 33 causes transmission of the data to the network node 16 (Step SI 78) according to the scheduling grant.
  • the application processor 31 may indicate to the baseband processor 33 that the application session has ended (Step SI 80).
  • FIG. 16 is a block diagram illustrating an example process flow for an application processor 31 and baseband processor 33 in a wireless device 22 according to some embodiments of the present disclosure.
  • Application data e.g., video, audio, sensor, motion, etc. data
  • the data is generated, collected, combined, etc. and stored in a buffer 102.
  • the data is then further processed, e.g., encoded, compressed, combined, etc. by application processor 31 and/or by additional processing circuitry (Step SI 86).
  • the application processor 31 encodes the data, it is stored in buffer 104 (Step SI 87).
  • the application processor 31 determines a pre-data indication and transmits this via the App-Modem API 96a (Step SI 88) to the modem entity (baseband processor 33) via the corresponding API-Modern API 96b (Step S190).
  • the pre-data indication is received by the baseband processor 33 (Step SI 92), which utilizes the information therein to determine and transmit a scheduling request to the network node 16.
  • Step S194 the data is transferred (Step S194) to the modem entity (baseband processor 33) and stored in modem Tx buffer 106 (Step S196).
  • the baseband processor 33 and/or modem 100 receives the data (Step S198), further processes the data (e.g., further encodes it, modulates it, converts it, etc.) for transmission via radio interface 82 (and/or any other radio hardware of the wireless device 22) (Step S200) to network node 16.
  • IPC interprocessor communication
  • AT an interface 96 for the application processor 31 to interact with the baseband processor 33 to perform variety of tasks.
  • proprietary extensions of the AT commands to handle pre-data-indication signaling could be one method of implementation.
  • Other digital communication interfaces for IPC may be used, such as any digital serial interface, such as MCSI - multichannel serial interface control, etc.
  • FIG. 17 is a timing diagram illustrating techniques for low latency traffic in an application processor 31 and baseband processor 33 according to some embodiments of the present disclosure.
  • Data is generated in the application processor, and the application processor 31 determines an encoding/compression/etc. for the data. Based on the encoding/compression/etc. (e.g., how much computation time is expected encoding the data, the expected size of the data after the encoding, etc.), the application processor 31 determines a pre-data indication, and transmits this to the baseband processor 33.
  • the baseband processor 33 determines a scheduling request and transmits the scheduling request(s) at one or more scheduling request opportunity(ies). As illustrated in FIG.
  • the baseband processor 33 receives the pre-data indication, and is able to transmit the scheduling request prior to the completion of the data encoding, it will be able to transmit the data sooner than if the baseband processor 33 waited until the data encoding was complete to send the scheduling request.
  • FIG. 18 is a timing diagram which further illustrates example configurations according to some embodiments of the present disclosure.
  • an example periodic data transmission cycle e.g., a DTX cycle
  • This information may be provided from the baseband processor 33 to the application processor 31, e.g., for determining whether the pre-data indication should be sent, and determining one or more parameters for the pre-data indication and/or scheduling of the data.
  • the bottom portion of FIG. 18 illustrates in greater detail an active period, during which an indication is sent from the application processor 31 to baseband processor 33 regarding data being encoded and/or generated, and requesting an appropriate scheduling request be sent to prepare for the upcoming data.
  • the baseband processor 33 sends the scheduling request to the network node 16, and subsequently receives the data (e.g., encoded data) from the application processor 31.
  • the baseband processor 33 then transmits the (encoded) data to the network node 16 using the uplink resources allocated by the scheduling request.
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD- ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

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

Abstract

Un procédé, un système et un appareil sont divulgués. Un dispositif sans fil de la divulgation comprend un processeur d'application et un processeur de bande de base. Le processeur de bande de base est conçu pour recevoir une indication de pré-données indiquant au moins une caractéristique d'un paquet de données à venir provenant du processeur d'application et, en réponse à la réception de l'indication de pré-données, transmettre une demande de planification de liaison montante au noeud de réseau sur la base d'au moins une caractéristique indiquée dans l'indication de pré-données, la demande de planification de liaison montante étant transmise pour permettre une communication immédiate du paquet de données dès que le processeur de bande de base reçoit du processeur d'application le paquet de données.
PCT/EP2023/054848 2023-02-27 2023-02-27 Optimisation de trafic xr intra-dispositif Pending WO2024179660A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2023/054848 WO2024179660A1 (fr) 2023-02-27 2023-02-27 Optimisation de trafic xr intra-dispositif

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2023/054848 WO2024179660A1 (fr) 2023-02-27 2023-02-27 Optimisation de trafic xr intra-dispositif

Publications (1)

Publication Number Publication Date
WO2024179660A1 true WO2024179660A1 (fr) 2024-09-06

Family

ID=85410173

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/054848 Pending WO2024179660A1 (fr) 2023-02-27 2023-02-27 Optimisation de trafic xr intra-dispositif

Country Status (1)

Country Link
WO (1) WO2024179660A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190327757A1 (en) * 2017-01-06 2019-10-24 Idac Holdings, Inc. URLLC AND eMBB DATA MULTIPLEXING COMMUNICATIONS
US20220095355A1 (en) * 2020-09-18 2022-03-24 Qualcomm Incorporated Techniques for enhanced scheduling request configuration

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190327757A1 (en) * 2017-01-06 2019-10-24 Idac Holdings, Inc. URLLC AND eMBB DATA MULTIPLEXING COMMUNICATIONS
US20220095355A1 (en) * 2020-09-18 2022-03-24 Qualcomm Incorporated Techniques for enhanced scheduling request configuration

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MIN ZHU ET AL: "NR enhancement for XR capacity improvement", vol. 3GPP RAN 1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), XP052221740, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_111/Docs/R1-2211175.zip R1-2211175.docx> [retrieved on 20221107] *

Similar Documents

Publication Publication Date Title
US20210385022A1 (en) Data transmission and retransmission for semi-persistant scheduling
JP2019537857A (ja) Ｈａｒｑタイミング構成の同期制御のためのシステムおよび方法
US12075454B2 (en) Methods and devices for operating with dual connectivity
US12167441B2 (en) Multiplexing hybrid automatic repeat request feedback
CN109937555A (zh) 无线设备和网络节点的方法、这种无线设备和网络节点及其计算机程序
CN113519197A (zh) 上行链路控制信息抢占
EP3834295A1 (fr) Procédé et dispositif de rétroaction d&#39;informations d&#39;état de canal
WO2019095765A1 (fr) Procédé et appareil de transmission de liaison montante
WO2022151195A1 (fr) Procédé et appareil pour la durée de survie et la disponibilité de service de communication
US11968666B2 (en) Method and network node for coordination of configured scheduling
US20250301453A1 (en) Communication method, communication apparatus, communication system, medium, chip, and program product
CN119213824A (zh) 使用干扰消除和选择性功率控制的针对无线通信的干扰降低
US20250234349A1 (en) Methods for determining minimum scheduling offset application delay
US20240015735A1 (en) Application layer preemptive scheduling requests for ultra-low latency
US11395330B2 (en) Method and apparatus for adaptive scheduling and transmission
US20250379828A1 (en) Methods for signaling over control plane for dropping indication of extended reality traffic data
WO2024179660A1 (fr) Optimisation de trafic xr intra-dispositif
CN108347774A (zh) 数据的传输方法和装置
WO2023085995A1 (fr) Traitement du temps de survie lors d&#39;un transfert intercellulaire
WO2022253150A1 (fr) Procédé et appareil de transmission de données
EP3854163B1 (fr) Procédé et appareil pour un contrôle adaptatif de priorité entre des informations de commande et des données utilisateur
US20210400711A1 (en) Methods, radio nodes and computer readable media for enhanced grant skipping
WO2024209027A1 (fr) Signalisation de réseau et configuration de rapport d&#39;id de table de rapport d&#39;état de tampon (bsr) pour des services à débit adaptatif
US20230300819A1 (en) Uplink scheduling coordination for dual connectivity networking
US9525966B2 (en) Central scheduling multi-board architecture for wireless transceiver station

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: 23707937

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE