# US 2021/0345181 A1 · Methods for Transmitting and Receiving Data in 5G NR Device Based on Data/Service Tagging from Application Processor > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0345181 A1 - Document ID: US20210345181A1 - Status: Published application - Kind: A1 - Application number: 17/374,406 - Filed: 2021-07-13 - Published: 2021-11-04 - Earliest claimed: 2018-10-30 - Assignees: Apple Inc. - Applicants: Apple Inc. - Inventors: Murtaza A. Shikari; Sethuraman Gurumoorthy; Srinivasan Nimmala; Srirang A. Lovlekar - Web page: https://patentgrep.com/patent/US20210345181A1 ## CPC - H04W 24/08: Testing, {supervising or monitoring} using real traffic - H04W 28/24: Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service] - H04L 12/16: Arrangements for providing special services to substations - H04L 12/56: {Packet switching systems} - H04L 45/24: Multipath - H04L 47/19: at layers above the network layer (network arrangements for networked applications for scheduling or organising the servicing of application requests H04L67/60) - H04W 8/04: Registration at HLR or HSS [Home Subscriber Server] - H04W 16/14: Spectrum sharing arrangements {between different networks} - H04W 24/02: Arrangements for optimising operational condition - H04W 24/04: Arrangements for maintaining operational condition - H04W 28/0215: {based on user or device properties, e.g. MTC-capable devices (services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51)} - H04W 28/0236: {radio quality, e.g. interference, losses or delay} - H04W 28/0252: {per individual bearer or channel (dynamic wireless traffic scheduling H04W72/12)} - H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)} - H04W 28/0273: {adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP] (wireless network protocols or protocol adaptations to wireless operation, e.g. wireless application protocol H04W80/00)} - H04W 28/0278: {using buffer status reports (dynamic wireless traffic scheduling definition H04W72/12)} - H04W 28/0967: {Quality of Service [QoS] parameters} - H04W 28/10: Flow control {between communication endpoints} - H04W 72/1268: of uplink data flows - H04W 72/51: based on terminal or device properties - H04W 72/542: using measured or perceived quality - H04W 76/11: Allocation or use of connection identifiers - H04W 76/16: Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer - H04W 76/27: Transitions between radio resource control [RRC] states - G06F 15/163: Interprocessor communication - H04L 5/001: {the frequencies being arranged in component carriers} - H04L 5/0023: {Time-frequency-space} - H04L 5/006: {Quality of the received signal, e.g. BER, SNR, water filling} - H04L 5/0091: {Signalling for the administration of the divided path, e.g. signalling of configuration information} - H04L 2012/5631: {Resource management and allocation} - H04L 2012/5638: {Services, e.g. multimedia, GOS, QOS} - H04W 36/00692: {using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO] (allocation of physical resources in CoMP or in CA H04L5/0035)} - H04W 48/16: Discovering, processing access restriction or access information - H04W 80/12: Application layer protocols, e.g. WAP [Wireless Application Protocol] - H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Techniques and devices for service-specific tagging of data by an application processor (AP) of a user equipment device (UE). A first indication may be sent from the UE to a baseband processor (BB) of the UE of one or more quality of service preferences for an upcoming data session, and the BB may configure one or more layers of the BB according to the quality of service preferences. The BB may further communicate with a network to establish protocols for the quality of service preferences. The BB may determine one or more network conditions, and may transmit feedback from the BB to the AP related to the determined network conditions. In response, the AP may send a second indication of one or more updated quality of service preferences to the BB based at least in part on the feedback received from the BB. ## Claims ### Claim 1 A method for operating a user equipment device (UE), comprising: identifying a data flow to be transmitted using redundancy above a packet data convergence protocol (PDCP) layer; establishing a first connection for the data flow, wherein the first connection utilizes a New Radio (NR) 3rd Generation Partnership Project (3GPP) air interface; establishing a second connection for the data flow, wherein the second connection utilizes a Long Term Evolution (LTE) 3GPP air interface; and transmitting the data flow over the first connection and the second connection. ### Claim 2 (depends on 1) The method of claim 1, wherein the data flow is an internet protocol (IP) data flow. ### Claim 3 (depends on 1) The method of claim 1, wherein the data flow comprises an ultra-reliable low latency communication (URLLC). ### Claim 4 (depends on 1) The method of claim 1, wherein the first connection and the second connection use different security keys. ### Claim 5 (depends on 1) The method of claim 1, wherein data packets of the data flow for the first and second connections are duplicated by a baseband processor of the UE. ### Claim 6 (depends on 1) The method of claim 1, wherein the data flow is associated with a health care application executing on the UE. ### Claim 7 (depends on 1) The method of claim 1, wherein establishing the first and second connections for the data flow is performed responsive to a determination that the data flow is tagged with an ultra-reliable flag. ### Claim 8 A user equipment device (UE), comprising: an antenna; a radio operably coupled to the antenna; and a processor operably coupled to the radio; wherein the antenna, radio, and processor are configured to: identify a data flow to be transmitted using redundancy above a packet data convergence protocol (PDCP) layer; establish a first connection for the data flow, wherein the first connection utilizes a New Radio (NR) 3rd Generation Partnership Project (3GPP) air interface; establish a second connection for the data flow, wherein the second connection utilizes a Long Term Evolution (LTE) 3GPP air interface; and transmit the data flow over the first connection and the second connection. ### Claim 9 (depends on 8) The UE of claim 8, wherein the data flow is an internet protocol (IP) data flow. ### Claim 10 (depends on 8) The UE of claim 8, wherein the data flow comprises an ultra-reliable low latency communication (URLLC). ### Claim 11 (depends on 8) The UE of claim 8, wherein the first connection and the second connection use different security keys. ### Claim 12 (depends on 8) The UE of claim 8, wherein data packets of the data flow for the first and second connections are duplicated by a baseband processor of the UE. ### Claim 13 (depends on 8) The UE of claim 8, wherein the data flow is associated with a health care application executing on the UE. ### Claim 14 (depends on 8) The UE of claim 8, wherein establishing the first and second connections for the data flow is performed responsive to a determination that the data flow is tagged with an ultra-reliable flag. ### Claim 15 A computer-readable non-transitory memory medium comprising program instructions that, when executed by a processor of a user equipment device (UE), cause the UE to: identify a data flow to be transmitted using redundancy above a packet data convergence protocol (PDCP) layer; establish a first connection for the data flow, wherein the first connection utilizes a New Radio (NR) 3rd Generation Partnership Project (3GPP) air interface; establish a second connection for the data flow, wherein the second connection utilizes a Long Term Evolution (LTE) 3GPP air interface; and transmit the data flow over the first connection and the second connection. ### Claim 16 (depends on 15) The computer-readable non-transitory memory medium of claim 15, wherein the data flow is an internet protocol (IP) data flow. ### Claim 17 (depends on 15) The computer-readable non-transitory memory medium of claim 15, wherein the data flow comprises an ultra-reliable low latency communication (URLLC). ### Claim 18 (depends on 15) The computer-readable non-transitory memory medium of claim 15, wherein the first connection and the second connection use different security keys. ### Claim 19 (depends on 15) The computer-readable non-transitory memory medium of claim 15, wherein data packets of the data flow for the first and second connections are duplicated by a baseband processor of the UE. ### Claim 20 (depends on 15) The computer-readable non-transitory memory medium of claim 15, wherein establishing the first and second connections for the data flow is performed responsive to a determination that the data flow is tagged with an ultra-reliable flag.