Granted Patent B2

US 12,603,849 · App. 18/397,337 · Granted Apr 14, 2026

Inventors: Yoonseon Han (Suwon-si, KR); Dongmyung Kim (Suwon-si, KR); Sunghwan Kim (Suwon-si, KR); Younggyoun Moon (Suwon-si, KR)

Assignee: Samsung Electronics Co., Ltd.

H04L47/6205H04L47/32

Abstract

Claims (91)

1 . A method performed by a first network entity in a wireless communication system, the method comprising:

receiving, from a second network entity, a first message including first information for generating an action buffer, wherein the first information includes at least one of a type of the action buffer, a size of the action buffer, or an identifier of the action buffer;

receiving, from the second network entity, a second message including second information for adding of at least one action to multiple memories assigned to the action buffer created based on the first information; and

performing an action corresponding to an address of memory for an input packet, wherein the action among the at least one action is stored in the memory.

2 . The method of claim 1 ,

wherein the first information further includes information indicating an operation in case that the multiple memories assigned to the action buffer are full, and

wherein the operation includes at least one of ignoring the at least one action, removing an action stored longest in the action buffer, or removing an action most recently stored in the action buffer.

3 . The method of claim 1 ,

wherein the first information further includes information indicating an operation in case that the multiple memories assigned to the action buffer are empty, and

wherein the operation includes at least one of dropping the input packet, performing a preconfigured default action, waiting, or requesting, to the second network entity, an indication for processing the input packet.

4 . The method of claim 1 , further comprising:

receiving, from the second network entity, a third message indicating at least one of adding, removing, or modifying a flow entry,

wherein the flow entry includes a match field and at least one instruction field,

wherein the first network entity is a software defined network (SDN) switch,

wherein the second network entity is an SDN controller, and

wherein the first network entity and the second network entity are connected via an SDN protocol.

5 . The method of claim 1 , further comprising:

receiving, from the second network entity, a fourth message including configuration information on a flow rule,

wherein the flow rule includes a packet detection rule (PDR) field and an indirect action rule (IAR) field,

wherein the first network entity is a user plane function (UPF) entity,

wherein the second network entity is a session management function (SMF) entity, and

wherein the first network entity and the second network entity are connected via a packet forwarding control protocol (PFCP).

6 . A method performed by a second network entity in a wireless communication system, the method comprising:

transmitting, to a first network entity, a first message including first information for generating an action buffer, wherein the first information includes at least one of a type of the action buffer, a size of the action buffer, or an identifier of the action buffer; and

transmitting, to the first network entity, a second message including second information for adding of at least one action to multiple memories assigned to the action buffer created based on the first information,

wherein, an action corresponding to an address of memory for an input packet, wherein the arbitrary action among the at least one action is stored in the memory.

7 . The method of claim 6 ,

wherein the first information further includes information indicating an operation in case that the multiple memories assigned to the action buffer are full, and

wherein the operation includes at least one of ignoring the at least one action, removing an action stored longest in the action buffer, or removing an action most recently stored in the action buffer.

8 . The method of claim 6 ,

wherein the first information further includes information indicating an operation in case that the multiple memories assigned to the action buffer are empty, and

wherein the operation includes at least one of dropping the input packet, performing a preconfigured default action, waiting, or requesting to the second network entity an indication for processing the input packet.

9 . The method of claim 6 , further comprising:

transmitting, to the first network entity, a third message indicating at least one of adding, removing, or modifying a flow entry,

wherein the flow entry includes a match field and at least one instruction field,

wherein the first network entity is a software defined network (SDN) switch,

wherein the second network entity is an SDN controller, and

wherein the first network entity and the second network entity are connected via an SDN protocol.

10 . The method of claim 6 , further comprising:

transmitting, to the first network entity, a fourth message including configuration information on a flow rule,

wherein the flow rule includes a packet detection rule (PDR) field and an indirect action rule (IAR) field,

wherein the first network entity is a user plane function (UPF) entity,

wherein the second network entity is a session management function (SMF) entity, and

wherein the first network entity and the second network entity are connected via a packet forwarding control protocol (PFCP).

11 . A first network entity comprising:

at least one processor; and

at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the first network entity to:

receive, from a second network entity, a first message including first information for generating an action buffer, wherein the first information includes at least one of a type of the action buffer, a size of the action buffer, or an identifier of the action buffer,

receive, from the second network entity, a second message including second information for adding of at least one action to multiple memories assigned to the action buffer created based on the first information, and

perform an action corresponding to an address of memory for an input packet, wherein the action among the at least one action is stored in the memory.

12 . The first network entity of claim 11 ,

wherein the first information further includes information indicating an operation in case that the multiple memories assigned to the action buffer are full, and wherein the operation includes at least one of ignoring the at least one action, removing an action stored longest in the action buffer, or removing an action most recently stored in the action buffer.

13 . The first network entity of claim 11 ,

wherein the first information further includes information indicating an operation in case that the multiple memories assigned to the action buffer are empty, and

wherein the operation includes at least one of dropping the input packet, performing a preconfigured default action, waiting, or requesting, to the second network entity, an indication for processing the input packet.

14 . The first network entity of claim 11 , wherein the instructions further cause the first network entity to:

receive, from the second network entity, a third message indicating at least one of adding, removing, or modifying a flow entry,

wherein the flow entry includes a match field and at least one instruction field,

wherein the first network entity is a software defined network (SDN) switch,

wherein the second network entity is an SDN controller, and

wherein the first network entity and the second network entity are connected via an SDN protocol.

15 . The first network entity of claim 11 , wherein the instructions further cause the first network entity to:

receive, from the second network entity, a fourth message including configuration information on a flow rule,

wherein the flow rule includes a packet detection rule (PDR) field and an indirect action rule (IAR) field,

wherein the first network entity is a user plane function (UPF) entity,

wherein the second network entity is a session management function (SMF) entity, and

wherein the first network entity and the second network entity are connected via a packet forwarding control protocol (PFCP).

16 . A second network entity comprising:

at least one processor; and

at least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the second network entity to:

transmit, to a first network entity, a first message including first information for generating an action buffer, wherein the first information includes at least one of a type of the action buffer, a size of the action buffer, or an identifier of the action buffer, and

transmit, to the first network entity, a second message including second information for adding of at least one action to multiple memories assigned to the action buffer created based on the first information, and

wherein, an action corresponding to an address of memory for an input packet, wherein the action among the at least one action is stored in the memory.

17 . The second network entity of claim 16 ,

wherein the first information further includes information indicating an operation in case that the multiple memories assigned to the action buffer are full, and

wherein the operation includes at least one of ignoring the at least one action, removing an action stored longest in the action buffer, or removing an action most recently stored in the action buffer.

18 . The second network entity of claim 16 ,

wherein the first information further includes information indicating an operation in case that the multiple memories assigned to the action buffer are empty, and

wherein the operation includes at least one of dropping the input packet, performing a preconfigured default action, waiting, or requesting to the second network entity an indication for processing the input packet.

19 . The second network entity of claim 16 , wherein the instructions further cause the second network entity to:

transmit, to the first network entity, a third message indicating at least one of adding, removing, or modifying a flow entry,

wherein the flow entry includes a match field and at least one instruction field,

wherein the first network entity is a software defined network (SDN) switch,

wherein the second network entity is an SDN controller, and

wherein the first network entity and the second network entity are connected via an SDN protocol.

20 . The second network entity of claim 16 , wherein the instructions further cause the second network entity to:

transmit, to the first network entity, a fourth message including configuration information on a flow rule,

wherein the flow rule includes a packet detection rule (PDR) field and an indirect action rule (IAR) field,

wherein the first network entity is a user plane function (UPF) entity,

wherein the second network entity is a session management function (SMF) entity, and

wherein the first network entity and the second network entity are connected via a packet forwarding control protocol (PFCP).

Assignments (1)

Priority Claims (1)

Continuity (1)

References Cited (13)