KR20230031132A - Method for sfc support of edgeapp and device performing the same - Google Patents

Abstract

A method for SFC support of EDGEAPP and a device for performing the same are disclosed. A service function chain support method according to one embodiment may include: an operation of receiving a service routing configuration request; an operation of generating a service routing path in response to the service routing configuration request; and an operation of controlling traffic delivery by serially calling service APIs constituting the service routing path.

Description

Method for SFC support of EDGEAPP and device for performing it {METHOD FOR SFC SUPPORT OF EDGEAPP AND DEVICE PERFORMING THE SAME}

The disclosure below relates to a method for SFC support of EDGEAPP and an apparatus for performing the same.

Edge computing technology for transmitting data using an edge server is being discussed. Edge computing technology may include multi-access edge computing (MEC) or fog computing (FOC). Edge computing technology is a technology that provides data to an electronic device through a location geographically close to the electronic device, for example, a separate server (eg, edge data network, MEC server, or mobile edge host) installed inside or near a base station. can mean For example, applications that require low latency among applications installed on electronic devices do not go through a server located in an external data network (DN) (eg, Internet), but are installed at an edge installed in a geographically close location. Data can be sent and received through the server.

Services using edge computing technology (eg, MEC-based services or edge computing services) are being discussed, and research and development on electronic devices are being conducted to support edge computing services. For example, an application of an electronic device may transmit/receive edge computing-based data between an edge server (or an application of the edge server) and an application layer.

As research and development to support edge computing services progress, the edge data network (e.g., MEC server) that provides edge computing services satisfies the latency requirements of the service while using MEC system resources. Plans for efficient operation are being discussed. For example, a method of relocating edge computing services to terminals in a hierarchical edge data network is being studied.

The background art described above is possessed or acquired by the inventor in the process of deriving the disclosure of the present application, and cannot necessarily be said to be known art disclosed to the general public prior to the present application.

Depending on the closedness of the existing mobile communication network, it is difficult to utilize network information services for external MEC applications and link between systems, so 5G MEC technology is limited to network operator-led use, and the spread effect of the 5G+ convergence service industry may be limited. In order to spread the 5G+ convergence service industry, it is necessary to share network resources and services within the 5G network and to support service APIs provided (or exposed) by third-party service providers on the 5G MEC platform. In addition, in the EDGEAPP structure, the service API required by EAS can be repeatedly called centrally and then the final transmission can be processed. In this case, problems such as traffic increase due to service API transmission/reception, processing delay, and EAS load may occur.

Embodiments can directly control and support registration, search, and call for service APIs exposed by EAS (edge application server) on the 5G platform.

Embodiments can reduce delay and load due to repeated transmission/reception by chaining service function chaining to service APIs requiring EAS and sequentially passing traffic to the next processing function.

Embodiments enable service APIs provided by third-party service providers to be utilized at the network edge, enabling network operators to provide service platforms, localize service call traffic to the network edge, and enable MEC platforms to actively control traffic. can make it

However, the technical challenges are not limited to the above-described technical challenges, and other technical challenges may exist.

A method for supporting a service function chain according to an embodiment includes receiving a service routing configuration request, generating a service routing path in response to the service routing configuration request, and configuring the service routing path. It may include an operation of controlling the delivery of traffic by calling service APIs in a chain.

The service API may be a service API that requires an edge application server (EAS) that has transmitted the service routing configuration request.

The service API may include one or more of service APIs provided by an edge enabler server (EES) or service APIs provided by the EAS and other EASs, or a combination of two or more.

Traffic processed by the called service API may be sequentially delivered to the next processing function.

The next processing function may be a service function, EAS or EEC.

The method may further include setting a service routing rule corresponding to the service routing path.

The creating operation may include configuring the service routing path based on a service function chain rule.

The service function chain rule may include application traffic characteristics, application traffic characteristics, target API information required for invocation, an order of target APIs required for invocation, and service KPIs for API invocation. there is.

The service routing path may be configured by including traffic classification rules, traffic forwarding/redirection rules, and necessary service KPIs.

The method may further include requesting 5GC to set up a 3GPP transport layer path to adjust traffic along the service routing path.

A method for supporting a service function chain according to an embodiment includes an operation of generating a service routing path in response to a service routing configuration request for serially calling a service API required by an edge application server (EAS); It may include an operation of setting a service routing rule corresponding to the service routing path, and an operation of controlling traffic transfer by serially calling service APIs constituting the service routing path.

The service API may include one or more of service APIs provided by an edge enabler server (EES) or service APIs provided by the EAS and other EASs, or a combination of two or more.

Traffic processed by the called service API may be sequentially delivered to the next processing function.

The next processing function may be a service function, EAS or EEC.

The creating operation may include configuring the service routing path based on a service function chain rule.

The service function chain rule may include application traffic characteristics, application traffic characteristics, target API information required for invocation, an order of target APIs required for invocation, and service KPIs for API invocation. there is.

The service routing path may be configured by including traffic classification rules, traffic forwarding/redirection rules, and necessary service KPIs.

The method may further include requesting 5GC to set up a 3GPP transport layer path to adjust traffic along the service routing path.

A method for supporting a service function chain according to an embodiment includes an operation of generating a service routing path in response to a service routing configuration request for serially calling a service API required by an edge application server (EAS); An operation of setting a service routing rule corresponding to the service routing path, an operation of requesting a 5GC to set up a 3GPP transport layer path to adjust traffic along the service routing path, and a service API constituting the service routing path It may include an operation of controlling the transfer of traffic by calling in a chain.

1 is a diagram schematically illustrating a network environment for supporting an edge computing service according to an exemplary embodiment.
2 is a diagram for explaining a service function chaining operation in a network environment for supporting an edge computing service according to an embodiment.
3 is a flowchart illustrating an operation of configuring a service routing path in an EDGEAPP architecture and transferring traffic according to the service routing path according to an embodiment.
4 shows a schematic block diagram of an apparatus according to an embodiment.

실시예들에 대한 특정한 구조적 또는 기능적 설명들은 단지 예시를 위한 목적으로 개시된 것으로서, 다양한 형태로 변경되어 구현될 수 있다. 따라서, 실제 구현되는 형태는 개시된 특정 실시예로만 한정되는 것이 아니며, 본 명세서의 범위는 실시예들로 설명한 기술적 사상에 포함되는 변경, 균등물, 또는 대체물을 포함한다.

Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only, and may be changed and implemented in various forms. Therefore, the form actually implemented is not limited only to the specific embodiments disclosed, and the scope of the present specification includes changes, equivalents, or substitutes included in the technical idea described in the embodiments.

Although terms such as first or second may be used to describe various components, such terms should only be construed for the purpose of distinguishing one component from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element.

It should be understood that when an element is referred to as being “connected” to another element, it may be directly connected or connected to the other element, but other elements may exist in the middle.

Singular expressions include plural expressions unless the context clearly dictates otherwise. In this document, "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "A Each of the phrases such as "at least one of , B, or C" may include any one of the items listed together in that phrase, or all possible combinations thereof. In this specification, terms such as "comprise" or "have" are intended to designate that the described feature, number, step, operation, component, part, or combination thereof exists, but one or more other features or numbers, It should be understood that the presence or addition of steps, operations, components, parts, or combinations thereof is not precluded.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and unless explicitly defined in this specification, it should not be interpreted in an ideal or excessively formal meaning. don't

The term '~unit' used in this specification means software or a hardware component such as FPGA or ASIC, and '~unit' performs certain roles. However, '~ unit' is not limited to software or hardware. '~bu' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors. For example, '~unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, may include subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Functions provided within components and '~units' may be combined into smaller numbers of components and '~units' or further separated into additional components and '~units'. In addition, components and '~units' may be implemented to play one or more CPUs in a device or a secure multimedia card. Also, '~ unit' may include one or more processors.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. In the description with reference to the accompanying drawings, the same reference numerals are given to the same components regardless of reference numerals, and overlapping descriptions thereof will be omitted.

1 is a diagram schematically illustrating a network environment for supporting an edge computing service according to an exemplary embodiment.

Referring to FIG. 1, a network environment 10 (eg 3GPP 5G MEC platform (EDGEAPP)) includes a terminal 100 and a 3 ^rd generation partnership project (3GPP) network (eg 3GPP core network) 200 , an edge data network 300, and an edge configuration server (ECS) (eg, an edge data network configuration server) 400. The network environment 10 may not be limited to the configurations 100 to 400 shown in FIG. 1 .

Each component included in the network environment 10 may mean a physical entity unit or a software or module unit that performs an individual function. Components included in the network environment 10 may be referred to as entities or functions.

The terminal 100 may refer to a device used by a user. For example, the terminal 100 may mean a user equipment (UE), a remote terminal, a wireless terminal, or a user device. The terminal 100 may include all types of electronic devices.

The terminal 100 may include one or more application clients (AC) and edge enabler clients (EEC). The terminal 100 may further include a 3GPP communication layer (not shown). AC may also be referred to as a UE application (UE App) or a client application. EEC 120 may also be referred to as MEL (MEC enabling layer).

The terminal 100 may execute (or drive) one or more ACs. ACs may require different network services, such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLC), or massive machine type communication (mMTC). AC is the data transmission rate of the terminal 100, latency (or speed), reliability, the number of terminals 100 accessed to the network, the network access period of the terminal 100, and You can request different network services based on one or more of your average data usage.

AC may mean a basic application pre-installed in the terminal 100 or an application provided by a third party. AC may mean a client application program driven in the terminal 100 for a specific application service. Within the terminal 100, several ACs may be driven. One or more of the ACs may be used to provide edge computing services from the edge data network 300 to the terminal 100 . AC is the client side of MEC application and can exchange service data through interaction with EAS. For example, AC is an application installed and executed in the terminal 100 and may provide a function of transmitting and receiving data through the edge data network 300 . AC may mean application software (or module) executed on the terminal 100 to use functions provided by one or more specific EAS (eg, edge applications).

EEC may mean a layer that performs an operation within the terminal 100 that enables the terminal 100 to use edge computing services. The EEC determines which AC (eg UE App) can use the edge computing service, and configures a network interface so that the data of the AC of the terminal 100 can be delivered to the edge data network 300 that provides the edge computing service. You can perform a linking action. EEC can search and discover EAS.

In addition, the EEC may perform an operation for establishing a data connection for the terminal 100 to use the edge computing service with the 3GPP communication layer. The 3GPP communication layer may mean a layer that performs a modem operation for using a mobile communication system, establishes a wireless connection for data communication, registers the terminal 100 in the mobile communication system, and transmits data to the mobile communication system. It can play a role in establishing a connection for transmission and sending and receiving data.

The 3GPP network 200 is a wireless communication system conforming to the standards of the 3rd Generation Partnership Project (3GPP), and is connected to the terminal 100 to provide a wireless communication service to the terminal 100. The 3GPP network 200 may include, but is not limited to, a 3rd generation (3G) network, an LTE network, an LTE-A network, and a next-generation network (5G or NR). It may also include a configured network.

The 3GPP network 200 may include a radio access network (RAN) (not shown) and a core network (not shown). The RAN is a network directly connected to the terminal 100, and may be an infrastructure that provides wireless access to the terminal 100. The RAN may include a plurality of base stations, and the plurality of base stations may perform communication through an interface formed between them. At least some of the interfaces between the plurality of base stations may be wired or wireless. A base station may be referred to as a gNode B, an eNode B, a Node B, a base station (BS), a radio access unit, a base station controller, a node on a network, or other terms having equivalent technical meaning. The core network may process data and control signals for the terminal 100 transmitted and received through the RAN. The core network controls user planes and control planes, processes mobility, manages subscriber information, billing, and communicates with other types of systems (eg, long term evolution (LTE) systems). It can perform various functions such as interlocking. In order to perform the various functions described above, the core network may include a plurality of functionally separated entities having different network functions (NFs). For example, the core network includes user plane function (UPF), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), network exposure function (NEF), user data management (UDM) , a network data analysis function (NWDAF), or a gateway mobile location center (GMLC), or any combination thereof.

UPF may provide a data path (or data plane) between the terminal 100 and the edge data network 300 . The UPF may serve as a gateway to deliver data (or data packets) transmitted and received by the terminal.

The terminal 100 and the edge data network 300 may transmit and receive data (or data packets) to each other through UPF. A data network (DN) may exist between the edge data network 300 and the UPF.

The UPF may be located close to the edge data network 300 to support the edge computing service to the terminal 100, and deliver data packets of the terminal 100 to the edge data network 300 with low delay or edge data Data packets of the network 300 can be delivered to the terminal 100 with low delay.

The UPF may provide a data path between the terminal 100 and the edge data network 300 using a data network connected to the Internet. UPF may route data packets to be delivered to the Internet among data packets transmitted by the terminal 100 through a data network between the service server 400 and the terminal 100 .

The NEF may be an NF that exposes capabilities and services of NFs of the 3GPP network 200 to the outside. The NEF is connected to an external server (e.g., the edge data network 300) and forwards information about events occurring in the NF inside the 3GPP network 200 to the external server, or transmits information about events requested by the external server to the internal server. It can perform the function of forwarding to NF. For example, functions and services exposed to the outside by the NEF include location-related event reporting of the terminal 100, session-related event reporting of the terminal 100, and mobility management of the terminal 100 (mobility management) event reporting, etc. An external server can subscribe to functions and services exposed by NEF and access those functions and services.

The edge data network 300 may refer to a server to which the terminal 100 accesses to use edge computing services. The edge data network 300 may be disposed within a base station of the 3GPP network 200 to which the terminal 100 is connected or located geographically close to the base station. The edge data network 300 may be referred to as an MEC server, an MEC host, an edge computing server, a mobile edge host, an edge computing platform, and the like. can

The edge data network 300 may include one or more edge application servers (EAS) and one or more edge enabler servers (EES).

The edge data network 300 may execute (or drive) one or more EAS. EAS may be referred to as an edge application, MEC application (MEC App), or ME (MEC) App. EAS may refer to an application application (or application server) provided by a third party (eg, a service provider) within the edge data network 300 that provides edge computing services. EAS may be used to establish a data session with an AC in order to transmit and receive data related to the AC. EAS can establish a data session with AC. A data session may refer to a communication path formed for the AC and EAS of the terminal 100 to transmit and receive data.

The edge data network 300 may provide virtual resources to edge applications (eg, EAS). For example, the virtual resource may include one or more of a computing resource, a storage resource, and a network resource (eg, network bandwidth) that can be used by the EAS. EAS may be executed (or driven) as a virtual machine.

EES may be referred to as a mobile edge computing platform (MEC platform), a mobile edge platform (MEP), a platform, and the like.

EES can provide functions required for the execution of EAS. For example, the EES may provide an edge computing service for the EAS to the terminal 100 or provide a function or environment for the EAS to consume the edge computing service. In addition, the EES may perform traffic control or DNS (Domain Name System) handling.

Edge computing service may collectively refer to procedures and information-related services required to use edge applications (eg, EAS). Edge computing services may be provided or consumed by EES and/or EAS. For example, the EAS may provide an edge computing service to the terminal 100 or use an edge computing service provided by the EES to provide the edge computing service to the terminal 100 . In addition, the EES may provide the EAS with an edge computing service that the EAS may use to provide the edge computing service to the terminal 100 . That is, the edge computing service may refer to a service provided by the edge data network 300 or EAS to the terminal 100 or a service provided by the EES and usable by the EAS.

EES can provide edge computing services to EAS. For example, the EES may provide EAS with various types of information (eg, data, content, terminal location information, caching data, subscribed service information, etc.) according to the provided edge computing service. EAS may provide edge computing services to the terminal 100 using edge computing services provided by EES. For example, the EAS may provide the edge computing service to the terminal 100 based on information provided by the EES as the edge computing service. The edge computing service provided to the terminal 100 may be a service required for the terminal 100 to drive an application client (eg, provision of data necessary for driving an application client).

EES may include MEC service (not shown) and service registry (not shown). The MEC service may provide edge computing services to EAS included in the edge data network 300 . MEC services can be implemented as software or modules that can perform individual functions. The service registry may provide information about edge computing services available in the edge data network 300 .

The EES may internally register the EAS when an instance of the EAS is created. EES may register EAS and store information related to EAS. EAS-related information stored by the EES includes information on edge computing services that the EAS intends to provide to the terminal 100, etc., and whether the edge computing services are required or optional services for the EAS. information may be included.

The EAS may perform service registration of a new edge computing service in the EES, update an already registered edge computing service, or search for an edge computing service registered in the EES. The EAS may provide information about the edge computing service to be registered or updated to the EES while registering or updating the edge computing service in the EES. EES can register edge computing services in the service registry.

The EES may deliver information about edge computing services registered in the service registry to the EAS in the edge data network 300 . For example, EES may deliver a list of edge computing services registered in a service registry to EAS. In addition, the EES may deliver information about the availability of edge computing services registered in the service registry or newly registered to the EAS.

EAS may subscribe to edge computing services registered in the service registry. EAS may subscribe to edge computing services by transmitting subscription request information for edge computing services to EES. Subscribing to the edge computing service by the EAS may mean continuously receiving edge computing services or information about the edge computing services from the EES.

The ECS may provide support functions for the terminal 100 to connect with the EES. The ECS 400 may be referred to as an edge data network management server, a configuration server, and the like, and functions of a mobile edge platform manager (MEPM) or a multi-access edge orchestrator (MEO). can be done The ECS 400 may mean a MEC management proxy (MMP) server or a Domain Name System (DNS) server.

The ECS 400 may refer to an initial access server through which the terminal 100 may receive edge data network configuration information for using the edge computer service. The ECS 400 may be aware of the deployment of edge data networks, and the terminal 100 accesses the ECS 400 and provides configuration information necessary for using the edge computing service, for example, an edge that needs to be accessed at a specific location. Information about the data network may be provided.

The ECS 400 may perform a function of providing edge data network configuration information to the EEC of the terminal 100. For example, with the edge data network configuration information, the terminal 100 accesses (connects) the edge data network 300 using service area information (eg, information on an edge data network providing services to a predetermined area, etc.) ) and information for establishing a connection with the EES 330 (eg, information for identifying an edge data network, etc.).

2 is a diagram for explaining a service function chaining operation in a network environment for supporting an edge computing service according to an embodiment.

In the network environment 10 (eg 3GPP 5G MEC platform (EDGEAPP)), an end to end service (eg MEC service) is to be delivered through a service function chaining operation can Delivery of an end-to-end service allows multiple service functions to be linked together. The service function chaining operation may refer to an operation of connecting and transmitting several service functions in chain (or all at once) to provide an end-to-end service (eg, MEC service). . For example, service function chaining operations may include operations such as traffic routing, steering, and forwarding.

A service function chain for a 5G network may include one or more service functions. For example, the service function chain includes firewall function, NAT, antimalware, parental control, DDoS protection, TCP proxy, and load balancer. , KPI monitoring, and video optimization, or one or more service functions, or a combination of two or more, but is not necessarily limited thereto.

The service function may be a service function provided by EES (eg, a network operator) and/or EAS (eg, a third service provider), and may be provided (eg, distributed) as a service API. The edge data network 300 (eg, EAS, EES) may process service function chaining operations (eg, traffic routing, steering, forwarding) in the data plane. .

EES or EAS (s) (eg, the first EAS, the second EAS) may provide a service API as a service function. EAS can be executed by invoking one or more service functions. The EES may include a service routing controller and a service routing handler. EES may provide service routing controller and service routing handler functionality for service function chaining operation.

The service routing controller may determine routing rules for constructing a service routing path for application traffic (eg, specific application traffic) based on a request (or demand) of EAS or 5GC. A service routing path may be named a service function chain, a service function path, and/or a service function chain path. A routing rule may refer to a combination of actual addresses (eg, EAS and/or EES addresses) that instantiate a service function chain.

Service routing controllers can enforce routing rules on service routing handlers.

The service routing controller provides routing rules (eg, EAS, Service API, EES) based on mobility, relocation, availability, and instantiation of edge data network 300 entities (eg, EAS, Service API, EES). You can dynamically update (or change) existing (or corresponding, existing) routing rules.

The service routing controller is responsible for monitoring results of service KPI(s) (e.g., performance, throughput, delay, etc.), load balancing, resource efficiency, and traffic optimization. Based on this, routing rules (eg, existing (or corresponding, existing) routing rules) can be dynamically updated.

The service routing controller configures the transport layer (e.g. 5G CN) route configuration to 5GC (e.g. 5G Core) to steer application traffic according to the determined service routing path (along UP connectivity). ) can be requested.

A service routing handler can classify application traffic between EEC/EAS/service APIs (or service functions).

The service routing handler may determine a service routing path (eg, a specific service routing path) for incoming application traffic based on routing rules provided by the service routing controller.

A service routing handler forwards (eg forwarding/redirecting).

As shown in FIG. 2, in the network environment 10 (eg, 3GPP 5G MEC platform (EDGEAPP)), the first EAS includes service API(s) (eg, service function SF1), service Functions (SF2) and service functions (SF3) may not be processed for final transmission after repeated centralized calls. The required service API(s) (e.g. service function (SF1), service function (SF2), service function (SF3)) are serialized along the service routing path by the EES (e.g. service routing controller, service routing handler). is invoked, traffic (eg, application traffic) may be sequentially forwarded to the next processing function (eg, service function, AC, EAS, and/or EEC). For example, the service function SF1 and the service function SF2 are service functions provided by EES (eg service API), and the service function SF3 is a service function provided by the second EAS (eg service API). API) may be The edge data network 300 (eg, EAS, EES) calls service APIs requiring EAS (eg, the first EAS) in chain (Service function chaining), sequentially forwards traffic to the next processing function, and repeats transmission and reception. Delay and load can be reduced.

3 is a flowchart illustrating an operation of configuring a service routing path in an EDGEAPP architecture and transferring traffic according to the service routing path according to an embodiment.

For convenience of description, it is assumed in FIG. 3 that the service API requiring the first EAS (EAS#1) includes the service function SF1, the service function SF2, and the service function SF3 shown in FIG. do.

In operation 511, the first EAS (EAS#1) may transmit a service routing configuration request (eg, a service routing configuration request) to the service routing controller of the EES. The service routing configuration request may be for chaining service API calls requiring the first EAS (EAS#1).

Before starting to send application traffic through the service routing path (or service function chain path), the first EAS (EAS#1) determines the service function chain rules (e.g. ingress application traffic characteristics, egress Service based on application traffic characteristics, information of target API(s) required for invocation, order of target API(s) required for invocation, service KPI for API invocation, etc.) You can ask the EES to configure a routing path. The service function chain rule may refer to a call repair of a service function (API), and may include ingress/exit characteristics, API characteristics, and the like. The service function chain rule may be a logical configuration corresponding to service/application logic. The service routing configuration request may be to cause the EES to configure a service routing path based on service function chain rules.

At operation 512, the service routing controller of the EES may create (eg, construct) a service routing path. For example, a service routing controller can configure a service routing path based on routing rules by discovering an EAS that exposes a service API. A service API may be a service function required to execute a requested service routing path (eg, a service function chain) while meeting the requested service KPIs.

At operation 513, the service routing handler of the EES may apply service routing rules corresponding to the service routing path. The service routing controller in EES provides a configured service routing path, including traffic classification rules, traffic forwarding/redirection rules, and required service KPIs, to inject service routing rules into service routing handlers. can be enforced.

In a distributed deployment, multiple EESs can be deployed and service routing handlers (or service routing handler functions) can be provided in a distributed manner. Accordingly, the Service Routing Controller of the EES will configure the Service Routing Path to the Remote Service Routing Handler of the other EES(s) that maintains the target EAS/EES Service API(s) in the Remote Service Area. (enforce) can.

The service routing controller of EES monitors mobility, relocation, availability, instantiation of EDN entities (e.g. EAS, service API, EES, etc.), and monitoring results of service KPIs (e.g. performance, performance, throughput, delay, etc.), load balancing, resource efficiency, and traffic optimization, based on at least one or a combination of two or more thereof, the already configured service routing path may be updated. The updated service routing path may be further enforced in the service routing handler(s).

At operation 514, the Service Routing Controller of the EES sends the 3GPP transport layer (eg, 5G CN) path to steer the application traffic along the service function path (eg, along the UP connectivity). Settings can be requested from 5GC.

In operation 535, the service routing controller of the EES may transmit a service routing configuration response (eg, result of service routing path construction) to the first EAS (EAS#1). there is.

In operations 536 and 537, if the requested service routing path is successfully configured, the application server of the first EAS (EAS#1) sends application traffic according to the request of the UE or application logic (eg, application logic of the application server). transmission can begin.

In operation 558, the first EAS (EAS#1) may forward (eg, forward) application traffic received from the local application server (eg, the application server of the first EAS (EAS#1)) to the corresponding EES.

In operation 559, upon receiving the application traffic, the service routing handler of the EES may forward (eg, forward) the application traffic to the second EAS (EAS#2) at a next hop along the service routing path. At this time, the service routing handler of the EES forwards the application traffic to the second EAS (EAS#2) at the next hop along the service routing path, based on the traffic classification rules configured by the service routing controller. ) to classify application traffic.

In operation 570, upon receiving the application traffic, the second EAS (EAS#2) may transfer (eg, forward) the received application traffic to a service function (eg, a local service function). In operations 571 and 572, the service function of the second EAS (EAS#2) may process the received application traffic and respond with a service function execution result (eg, application logic execution result).

In operation 593, the second EAS (EAS#2) may respond to the EES by forwarding application traffic that is a service function execution result.

In operation 594, upon receiving the application traffic, the service routing handler of the EES may forward the application traffic to the UE via the 3GPP transport layer at a next hop along the service routing path. At this time, the service routing handler classifies ingress application traffic based on the traffic classification rules configured by the service routing controller to forward the application traffic to the EAS at the next hop along the service routing path. can If the received application traffic is determined to be egress application traffic (i.e., the application traffic is the execution result of an entire step along the service routing path, and the next hop is the UE), the service routing handler Application traffic may be forwarded to the UE through the 3GPP transport layer.

4 shows a schematic block diagram of an apparatus according to an embodiment.

Referring to FIG. 4 , according to an embodiment, a device 600 (eg, a server device) may be substantially the same as the EAS and/or EES described with reference to FIGS. 1 to 3 . The device 600 may include a memory 610 and a processor 630 .

According to various embodiments, the memory 610 may store instructions (eg, programs) executable by the processor 630 . For example, the instructions may include instructions for executing an operation of the processor 630 and/or an operation of each component of the processor 630 .

According to various embodiments, the memory 610 may be implemented as a volatile memory device or a nonvolatile memory device. The volatile memory device may be implemented as dynamic random access memory (DRAM), static random access memory (SRAM), thyristor RAM (T-RAM), zero capacitor RAM (Z-RAM), or twin transistor RAM (TTRAM). Non-volatile memory devices include electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic RAM (MRAM), spin-transfer torque (STT)-MRAM (conductive bridging RAM), and conductive bridging RAM (CBRAM). , FeRAM (Ferroelectric RAM), PRAM (Phase change RAM), Resistive RAM (RRAM), Nanotube RRAM (Polymer RAM (PoRAM)), Nano Floating Gate Memory Memory (NFGM)), holographic memory, molecular electronic memory device (Molecular Electronic Memory Device), and/or Insulator Resistance Change Memory.

According to various embodiments, the processor 630 may execute computer readable codes (eg, software) stored in the memory 610 and instructions triggered by the processor 530 . The processor 630 may be a hardware-implemented data processing device having a circuit having a physical structure for executing desired operations. Target operations may include, for example, code or instructions included in a program. A data processing unit implemented in hardware includes, for example, a microprocessor, a central processing unit, a processor core, a multi-core processor, and a multiprocessor. , Application-Specific Integrated Circuit (ASIC), and Field Programmable Gate Array (FPGA).

According to various embodiments, an operation performed by the processor 630 is substantially the same as that of the EAS and/or EES described with reference to FIGS. 1 to 3 . Accordingly, detailed descriptions will be omitted.

The embodiments described above may be implemented as hardware components, software components, and/or a combination of hardware components and software components. For example, the devices, methods and components described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate (FPGA). array), programmable logic units (PLUs), microprocessors, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and software applications running on the operating system. A processing device may also access, store, manipulate, process, and generate data in response to execution of software. For convenience of understanding, there are cases in which one processing device is used, but those skilled in the art will understand that the processing device includes a plurality of processing elements and/or a plurality of types of processing elements. It can be seen that it can include. For example, a processing device may include a plurality of processors or a processor and a controller. Other processing configurations are also possible, such as parallel processors.

Software may include a computer program, code, instructions, or a combination of one or more of the foregoing, which configures a processing device to operate as desired or processes independently or collectively. You can command the device. Software and/or data may be any tangible machine, component, physical device, virtual equipment, computer storage medium or device, intended to be interpreted by or provide instructions or data to a processing device. , or may be permanently or temporarily embodied in a transmitted signal wave. Software may be distributed on networked computer systems and stored or executed in a distributed manner. Software and data may be stored on computer readable media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium. A computer readable medium may store program instructions, data files, data structures, etc. alone or in combination, and program instructions recorded on the medium may be specially designed and configured for the embodiment or may be known and usable to those skilled in the art of computer software. there is. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floptical disks. - includes hardware devices specially configured to store and execute program instructions, such as magneto-optical media, and ROM, RAM, flash memory, and the like. Examples of program instructions include high-level language codes that can be executed by a computer using an interpreter, as well as machine language codes such as those produced by a compiler.

The hardware device described above may be configured to operate as one or a plurality of software modules to perform the operations of the embodiments, and vice versa.

As described above, although the embodiments have been described with limited drawings, those skilled in the art can apply various technical modifications and variations based on this. For example, the described techniques may be performed in an order different from the method described, and/or components of the described system, structure, device, circuit, etc. may be combined or combined in a different form than the method described, or other components may be used. Or even if it is replaced or substituted by equivalents, appropriate results can be achieved.

Therefore, other implementations, other embodiments, and equivalents of the claims are within the scope of the following claims.

Claims (19)

In the service function chain support method,
receiving a service routing configuration request;
generating a service routing path in response to the service routing configuration request; and
Controlling traffic delivery by serially calling service APIs constituting the service routing path
Including, how.
According to claim 1,
Wherein the service API is a service API that requires an edge application server (EAS) that sent the service routing configuration request.
According to claim 2,
The service API,
A method comprising at least one service API provided by an edge enabler server (EES) or a service API provided by the EAS and other EAS, or a combination of two or more.
According to claim 1,
Traffic processed by the called service API is sequentially delivered to the next processing function.
According to claim 1,
Wherein the next processing function is a service function, EAS or EEC.
According to claim 1,
Setting a service routing rule corresponding to the service routing path
Further comprising a method.
According to claim 1,
The generating operation is
constructing the service routing path based on service function chain rules;
Including, how.
According to claim 7,
The service function chain rule,
A method comprising application traffic characteristics, application traffic characteristics, information of a target API required for invocation, an order of target APIs required for invocation, and service KPIs for API invocation.
According to claim 1,
The service routing path,
A method comprising a traffic classification rule, a traffic forwarding/redirection rule, and a required service KPI.
According to claim 1,
Requesting 5GC to set up a 3GPP transport layer path to adjust traffic along the service routing path
Further comprising a method.
In the service function chain support method,
generating a service routing path in response to a service routing configuration request for serially calling service APIs required by an edge application server (EAS);
setting a service routing rule corresponding to the service routing path; and
Controlling traffic delivery by serially calling service APIs constituting the service routing path
Including, how.
According to claim 11,
The service API,
A method comprising at least one service API provided by an edge enabler server (EES) or a service API provided by the EAS and other EAS, or a combination of two or more.
According to claim 11,
Traffic processed by the called service API is sequentially delivered to the next processing function.
According to claim 11,
Wherein the next processing function is a service function, EAS or EEC.
According to claim 11,
The generating operation is
constructing the service routing path based on service function chain rules;
Including, how.
According to claim 15,
The service function chain rule,
A method comprising application traffic characteristics, application traffic characteristics, information of a target API required for invocation, an order of target APIs required for invocation, and service KPIs for API invocation.
According to claim 11,
The service routing path,
A method comprising a traffic classification rule, a traffic forwarding/redirection rule, and a required service KPI.
According to claim 11,
Requesting 5GC to set up a 3GPP transport layer path to adjust traffic along the service routing path
Further comprising a method.
In the service function chain support method,
generating a service routing path in response to a service routing configuration request for serially calling service APIs required by an edge application server (EAS);
setting a service routing rule corresponding to the service routing path;
requesting a 5GC to establish a 3GPP transport layer path to adjust traffic along the service routing path; and
Controlling traffic delivery by serially calling service APIs constituting the service routing path
Including, how.

Images