# US 2026/0075394 A1 · Service function chaining system and method for mobile network

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

- Number: US 2026/0075394 A1
- Document ID: US20260075394A1
- Status: Published application
- Kind: A1
- Application number: 18/978,332
- Filed: 2024-12-12
- Published: 2026-03-12
- Earliest claimed: 2024-09-11
- Assignees: Foundation of Soongsil University-Industry Cooperation
- Applicants: Foundation of Soongsil University-Industry Cooperation
- Inventors: Young Han KIM
- Web page: https://patentgrep.com/patent/US20260075394A1

## CPC

- H04W 4/50: Service provisioning or reconfiguring
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A service function chaining device, system, and method for a mobile network. A service function chaining (SFC) apparatus located in a control plane comprises a processor; and a memory connected to the processor, wherein the memory stores program instructions, executed by the processor, to perform operations comprising receiving session information for a service from a mobile network, determining a service path for a plurality of service functions for service chaining on a data plane, and transforming and processing the session information and the service path into segment routing information and provisioning it to a classifier ingress located in a data plane and a forwarding/egress connected to an individual multi-access edge computing (MEC) hosting a service.

## Claims

### Claim 1

A service function chaining (SFC) apparatus located in a control plane comprising:
a processor; and
a memory connected to the processor,
wherein the memory stores program instructions, executed by the processor, to perform operations comprising:
receiving session information for a service from a mobile network,
determining a service path for a plurality of service functions for service chaining on a data plane, and
transforming and processing the session information and the service path into segment routing information and provisioning it to a classifier ingress located in a data plane and a forwarding/egress connected to an individual multi-access edge computing (MEC) hosting service.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the session information comprises a UE (User Equipment) IP address, a UPF (User Plane Function) TEID (Tunnel ID) and a RAN (Radio Access Network).

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the program instructions perform segment routing information transformation processing in different ways in an NSH (network service header)-based SFC with an SRv6 transport tunnel, an SRv6-based SFC with an integrated NSH service plane, and an SR-based SFC.

### Claim 4 (depends on 3)

The apparatus of claim 3, wherein the program instructions, after selecting a service path for a plurality of service functions for the service chaining, query NSH-to-service mapping information and service locator mapping information regarding the plurality of service functions.

### Claim 5 (depends on 4)

The apparatus of claim 4, wherein the NSH-to-service mapping information is mapping information between an SPI (Service Path Identifier) and an SI (Service Index), and a service, and the service locator mapping information is information of each service, an IP address and transport encapsulation mapping.

### Claim 6 (depends on 5)

The apparatus of claim 5, wherein the program instructions generate Type 1 and Type 3 routing information using the session information, the service path, the NSH-to-service mapping information and the service locator mapping information for the NSH-based SFC with the SRv6 transport tunnel,
wherein the Type 1 routing information is provisioned only to the forwarding/egress, and the Type 3 routing information is provisioned to both the classifier ingress and the forwarding/egress.

### Claim 7 (depends on 6)

The apparatus of claim 6, wherein the Type 1 routing information comprises an N3 RAN address/prefix, an N3 TEID, a UE address/prefix,
wherein the Type 3 routing information comprises a plurality of MEC information hosting a service, NSH information, NSH-to-service mapping information, service locator mapping information, service chaining IP, N6 TEID, and N3 UPF address/prefix.

### Claim 8 (depends on 4)

The apparatus of claim 4, wherein the program instructions generate Type 1 and Type 4 routing information using the session information, the service path, the NSH-to-service mapping information, and the service locator mapping information for the SRv6-based SFC with the integrated NSH service plane,
wherein the Type 1 routing information is provisioned only to the forwarding/egress, and the Type 4 routing information is provisioned to both the classifier ingress and the forwarding/egress.

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein the Type 1 routing information comprises N3 RAN address/prefix, N3 TEID, UE address/prefix,
wherein the Type 4 routing information comprises a plurality of MEC information hosting service, a service address (service order list) required for data plane flow, NSH information, NSH-to-service mapping information, service locator mapping information, service chaining IP, N6 TEID, and N3 UPF address/prefix.

### Claim 10 (depends on 4)

The apparatus of claim 4, wherein the program instructions generate Type 5 routing information provisioned only to the classifier ingress and Type 1 routing information provisioned only to the forwarding/egress by using the session information, the service path, the NSH-to-service mapping information, and the service locator mapping information for the SR-based SFC.

### Claim 11 (depends on 10)

The apparatus of claim 10, wherein the Type 1 routing information comprises N3 RAN address/prefix, N3 TEID, UE address/prefix,
wherein the Type 5 routing information comprises a plurality of MEC information hosting service, a service address (Service Order List) required for a data plane flow, a service chaining IP, N6 TEID, and N3 UPF address/prefix.

### Claim 12

A service function chaining (SFC) system located in a control plane comprising:
a service chaining path resolution system that receives session information for a service from a mobile network and determines a service path for a plurality of service functions for service chaining on a data plane; and
a session-transformed route system that transforms the session information and the service path into segment routing information and provisions it to a classifier ingress located in the data plane and a forwarding/egress connected to an individual multi-access edge computing (MEC) hosting a service.

### Claim 13 (depends on 12)

The system of claim 12 further comprises,
a service manager that stores NSH-to-service mapping information and service locator mapping information regarding the plurality of service functions.

### Claim 14

A method for performing service function chaining (SFC) in an apparatus including a processor and a memory, and located in a control plane comprising:
receiving session information for a service from a mobile network;
determining a service path for a plurality of service functions for service chaining on a data plane; and
transforming the session information and the service path into segment routing information and provisioning it to a classifier ingress located in a data plane and a forwarding/egress connected to an individual MEC (Multi-access Edge Computing) hosting a service.

### Claim 15 (depends on 14)

The method of claim 14, wherein the provisioning performing segment routing information transformation processing in different ways in an NSH (Network Service Header)-based SFC with an SRv6 transport tunnel, an SRv6-based SFC with an integrated NSH service plane, and an SR-based SFC.

### Claim 16 (depends on 15)

The method of claim 15, wherein the provisioning comprises,
querying, after selecting a service path for a plurality of service functions for the service chaining, NSH-to-service mapping information and service locator mapping information regarding the plurality of service functions.

### Claim 17 (depends on 16)

The method of claim 16, wherein the NSH-to-service mapping information is mapping information between an SPI (Service Path Identifier) and an SI (Service Index), and a service, and the service locator mapping information is information of each service, an IP address and transport encapsulation.

### Claim 18

A user terminal for service function chaining (SFC) comprising:
a wireless transceiver for transmitting and receiving a wireless signal;
a memory for storing program instructions; and
a processor for executing the program instructions and controlling the transceiver,
wherein the processor controls the wireless transceiver, so that a service function chaining (SFC) apparatus located in the control plane receives session information for a service from a mobile network, determines a service path for a plurality of service functions for service chaining, transforms and processes the session information and the service path into segment routing information, and provisions it to a classifier ingress located in a data plane and a forwarding/egress connected to an individual MEC (Multi-access Edge Computing) hosting a service, so that traffic is received through the classifier ingress and the gNB after completion of the plurality of service functions.
