# US 2021/0176302 A1 · Apparatus and method for establishing connection and clat aware affinity (caa)-based scheduling in multi-core processor

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0176302 A1
- Document ID: US20210176302A1
- Status: Published application
- Kind: A1
- Application number: 17/250,554
- Filed: 2019-08-02
- Published: 2021-06-10
- Earliest claimed: 2018-08-03
- Assignees: Samsung Electronics Co., Ltd.
- Applicants: Samsung Electronics Co., Ltd.
- Inventors: Chhaya BHARTI; Madhan Raj KANAGARATHINAM; Rohit Shankar LINGAPPA; Gyanchandani MONTY; Jaekwang HAN; Karthikeyan A.; Milim LEE; Sandesh Kumar SRIVASTAVA; Wangkeun OH
- Web page: https://patentgrep.com/patent/US20210176302A1

## CPC

- H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30)
- H04L 69/167: Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 (translation of Internet protocol [IP] addresses H04L61/2503)
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- H04L 61/251: between different IP versions
- H04L 61/4511: using domain name system [DNS]
- H04L 69/22: Parsing or analysis of headers
- H04L 67/1029: using data related to the state of servers by a load balancer
- 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

Embodiments herein provide a method for CLAT Aware Affinity (CAA)-based scheduling by a user equipment (UE) (100) comprising a multi-core processor (120). The method includes a CAA scheduler (180) at the user equipment (100) receiving a packet and determining a path characteristic of the packet. Further, the method includes the CAA scheduler (180) determining, at least one of a IPv4 connection and a IPv6 connection based the path characteristic of the packet; and establishing a connection to at least one of an IPv4 server and an IPv6 server based on the determined at least one of the IPv4 connection and the IPv6 connection. Further, the method includes the CAA scheduler (180) classifying the packet into at least one class and scheduling the packet on at least one core of the multi-core processor (120) based on the at least one class.

## Claims

### Claim 1

A method for establishing a connection and Customer side translator (CLAT) Aware Affinity (CAA)-based scheduling by an user equipment (UE) (100) comprising a multi-core processor (120), comprising:
receiving, by a CAA scheduler (180) at the user equipment (100), a packet;
determining, by the CAA scheduler (180), a path characteristic of the packet;
determining, by the CAA scheduler (180), at least one of a IPv4 connection and a IPv6 connection based the path characteristic of the packet; and
establishing, by the CAA scheduler (180), a connection to at least one of an IPv4 server and an IPv6 server based on the determined at least one of the IPv4 connection and the IPv6 connection.

### Claim 2 (depends on 1)

The method of claim 1, wherein establishing, by the CAA scheduler (180), the connection to at least one of the IPv4 server and the IPv6 server comprises:
performing, by the CAA scheduler, one of:
connecting to the IPv4 server in response to determining that an IPv6 server is not available,
connecting to the IPv6 server only in response to determining that a performance of the IPv6 server and a performance of the IPv4 server are equal,
connecting to the IPv4 server in response to determining that the performance of the IPv4 server is better than the performance of the IPv6 server.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
classifying, by the CAA scheduler (180), the packet into at least one class; and
scheduling, by the CAA scheduler (180), the packet on at least one core of the multi-core processor (120) based on the at least one class.

### Claim 4 (depends on 3)

The method of claim 3, wherein classifying, by the CAA scheduler (180), the packet into at least one class comprises:
determining whether an IP header of the packet comprises one of an IPv4 prefix IP address and an IPV6 prefix IP address; and
classifying the packet into one category of:
a Class A category in response to determining that the IP header of the packet comprises IPV4 prefix IP address,
a Class B category in response to determining that the IP header of the packet comprises IPV6 prefix IP address, and
a Class C category in response to determining that the IP header of the packet neither comprises IPv4 prefix IP address nor IPV6 prefix IP address.

### Claim 5 (depends on 4)

The method of claim 4, wherein the Class A category indicates a forwarded packet or a local packet between the CLAT and applications having a IPv4 header.

### Claim 6 (depends on 4)

The method of claim 4, wherein the Class B category indicates actual or live air packets between RMNET and PLAT with a synthesized IPv6 header.

### Claim 7 (depends on 4)

The method of claim 4, wherein the Class C category indicates packets with direct IPv6 header
or local socket communication inside the user equipment (100).

### Claim 8 (depends on 3)

The method of claim 3, wherein scheduling, by the CAA scheduler (180), the packet on at least one core of the multi-core processor (120) based on the at least one class comprises:
determining whether the packet is classified into one of the Class A category, the Class B category and the Class C category;
creating one of:
a high priority queue and marking the packet in the high priority queue in response to determining that the packet is classified into the Class A category,
an intermediate priority queue and marking the packet in the intermediate priority queue in response to determining that the packet is classified into the Class B category,
a low priority queue and marking the packet in the low priority queue in response to determining that the packet is classified into the Class C category, and,
scheduling, by the CAA scheduler (180), the packet on at least one core of the multi-core processor (120) from one of the high priority queue, the intermediate priority queue, and the low priority queue.

### Claim 9 (depends on 8)

The method of claim 8, wherein scheduling, by the CAA scheduler (180), the packet on at least one core of the multi-core processor (120) based on one of the high priority queue, the intermediate priority queue, and the low priority queue comprises:
monitoring operational conditions of the multi-core processor (120);
modifying a CPU affinity of the multi-core processor (120) based on the operational conditions and one of the high priority queue, the intermediate priority queue, and the low priority queue; and
scheduling the packet on at least one core of the multi-core processor based on the modification.

### Claim 10 (depends on 9)

The method of claim 9, wherein the operational conditions comprises at least one of a CPU load, a CPU Frequency, a current CPU affinity, a Receive Packet Steering (RPS), and CAA cross layer parameters.

### Claim 11 (depends on 10)

The method of claim 10, wherein the CAA cross layer parameters comprises at least one of radio information of the user equipment, battery information of the user equipment, display information of the user equipment, Radio Interface Layer Daemon (RILD) information, and Network Daemon (NETD) information.

### Claim 12 (depends on 8)

The method of claim 8, wherein scheduling, by the CAA scheduler (180), the packet on at least one core of the multi-core processor (120) based on one of the high priority queue, the intermediate priority queue, and the low priority queue comprises:
modifying a CPU affinity of the multi-core processor (120) based on one of the high priority queue, the intermediate priority queue, and the low priority queue; and
scheduling the packet on at least one core of the multi-core processor (120) based on the modification.

### Claim 13

A user equipment (100) for establishing a connection and customer side translator (CLAT) Aware Affinity (CAA)-based scheduling, comprising:
a memory (170);
a multi-core processor (120); and
a CAA scheduler (180), coupled to the multi-core processor and the memory, configured to:
receive at the user equipment (100) a packet;
determine a path characteristic of the packet;
determine at least one of a IPv4 connection and a IPv6 connection based the path characteristic of the packet; and
establish a connection to at least one of an IPv4 server and an IPv6 server based on the determined at least one of the IPv4 connection and the IPv6 connection.

### Claim 14 (depends on 9)

The user equipment (100) of claim 9, wherein the CAA scheduler (180) is configured to establish the connection to at least one of the IPv4 server and the IPv6 server comprises:
perform one of:
connect to the IPv4 server in response to determining that an IPv6 server is not available,
connect to the IPv6 server only in response to determining that a performance of the IPv6 server and a performance of the IPv4 server are equal,
connect to the IPv4 server in response to determining that the performance of the IPv4 server is better than the performance of the IPv6 server.

### Claim 15 (depends on 9)

The user equipment (100) of claim 9, wherein the CAA scheduler (180) is further configured to:
classify the packet into at least one class; and
schedule the packet on at least one core of the multi-core processor (120) based on the at least one class.
