CN118740731A - Business processing method and business processing device - Google Patents

Abstract

The invention provides a service processing method and a service processing device, and belongs to the technical field of edge calculation. The service processing method is applied to the edge computing platform and comprises the following steps: transmitting an SFC request to a service controller, wherein the SFC request comprises an SFC description, and the SFC description comprises a service function SF type and a forwarding sequence of SF of a target application request; receiving an SFC response returned by the service controller, wherein the SFC response comprises an SFC forwarding path, and the SFC forwarding path is generated according to the IP address of the SF or SF agent requested by the target application and the forwarding sequence; and encapsulating the flow forwarded by the user plane function to the target application into SRv messages, and sending the SRv messages to the first SF or SF agent on the SFC forwarding path associated with the target application. The technical scheme of the invention can reduce the complexity of configuration SFC and improve the operation and maintenance efficiency.

Description

Business processing method and business processing device

Technical Field

The present invention relates to the field of edge computing technology, and in particular to a business processing method and a business processing device.

Background Art

The 5G network was designed with support for edge computing in mind. The 5G core network supports the separation of the control plane and the user plane. The UPF (user plane network element) can be flexibly deployed to the edge of the network to realize the data plane functions of 5G edge computing. Control plane functions such as PCF (policy control function) and SMF (session management function) can be deployed centrally. The 5G core network SMF selects the UPF close to the terminal to achieve local routing establishment and data diversion; 5G local diversion methods include UL-CL (Uplink Classifier) method and Branching Point (branching point) method. 5G edge computing also supports LADN (Local Area Data Network) local access method. PCF provides QoS (quality of service) control strategy and billing strategy for local data. The edge computing platform can provide a variety of services for edge applications to call. Common services include general services such as databases and message middleware, DNS (domain name system), bandwidth management, and industry services such as cloud games. The APP (application) of the vertical industry is deployed to the virtual machine or container of the edge computing node, and the services of the edge computing platform can be called by calling the API (application programming interface) of the edge computing platform.

The vertical industry services vary greatly, so the business requirements also vary greatly. When the vertical industry APP in the edge scenario has SFC (Service Function Chain) requirements, as shown in Figure 1, the traffic sent from the UE (terminal) to the APP is generally diverted to the business resource pool, and SFC is implemented in the business resource pool. This SFC implementation has nothing to do with ECP (Edge Computing Platform). The control plane of SFC is executed by the business controller, and the data plane is executed by the business function. SFC can generally be implemented through PBR (Policy-based Routing). This solution has certain limitations. When configuring SFC, it is necessary to configure it hop by hop on each business node based on each SFC business flow according to the forwarding path of the traffic. When the SFC is expanded, its configuration complexity also increases, resulting in difficulties in operation and maintenance.

Summary of the invention

The technical problem to be solved by the present invention is to provide a business processing method and a business processing device, which can reduce the complexity of configuring SFC and improve operation and maintenance efficiency.

To solve the above technical problems, the embodiments of the present invention provide the following technical solutions:

On the one hand, an embodiment of the present invention provides a service processing method, which is applied to an edge computing platform, including:

Sending a service function chain SFC request to the service controller, wherein the SFC request includes an SFC description, and the SFC description includes a service function SF type requested by the target application and a forwarding order of the SF;

receiving an SFC response returned by the service controller, wherein the SFC response includes an SFC forwarding path, wherein the SFC forwarding path is generated according to the IP address of the SF or SF proxy requested by the target application and the forwarding sequence;

The traffic forwarded by the user plane function to the target application is encapsulated into an SRv6 message, and the SRv6 message is sent to the first SF or SF proxy on the SFC forwarding path associated with the target application.

In some embodiments, before sending the SFC request to the service controller, the method further includes:

receiving an SFC service call request of the target application, wherein the SFC service call request includes an identifier of the target application and the SFC description;

An SFC service call response is returned to the target application.

In some embodiments, before returning the SFC service call response to the target application, the method further includes:

Determining the SFC service subscribed by the target application according to the identifier of the target application;

Authentication and SFC application programming interface API call authorization are performed with the target application.

In some embodiments, before receiving the SFC response returned by the service controller, the method further includes:

Mutual authentication and authorization are performed with the business controller.

The embodiment of the present invention further provides a service processing method, which is applied to a service controller, comprising:

Receive a service function chain SFC request from the edge computing platform, where the SFC request includes an SFC description, where the SFC description includes a service function SF type requested by a target application and a forwarding order of the SF;

Selecting a SF or SF proxy according to the SFC description, and generating an SFC forwarding path using the IP address of the selected SF or SF proxy;

An SFC response is sent to the edge computing platform, where the SFC response includes the SFC forwarding path.

In some embodiments, the SFC description further includes a traffic processing requirement, and the method further includes:

The selected SF or SF proxy is configured with a policy according to the traffic processing requirement.

In some embodiments, before sending the SFC response to the edge computing platform, the method further includes:

Mutual authentication and authorization are performed with the edge computing platform.

In some embodiments, before receiving a service function chain SFC request from an edge computing platform, the method further includes:

receiving a first registration request sent by the SF and a second registration request sent by the SF agent, wherein the first registration request includes information of the SF, the second registration request includes information of the SF agent, the information of the SF includes at least one of the following: its own IP address, whether it supports the SRv6 protocol, whether it is associated with a certain SF agent, resource specifications, and provided service types, and the information of the SF agent includes at least one of the following: its own IP address, support for the SRv6 protocol, and the IP address of the proxy SF;

The information of the SF agent is associated with the information of the corresponding SF and stored.

In some embodiments, selecting a SF or a SF proxy according to the SFC description includes:

Selecting the SF requested by the target application in the SFC description;

If the SF does not support SRv6, a SF agent corresponding to the SF is selected.

The embodiment of the present invention further provides a service processing device, which is applied to an edge computing platform and includes a processor and a transceiver.

The transceiver is used to send a service function chain SFC request to the service controller, the SFC request includes an SFC description, and the SFC description includes the service function SF type requested by the target application and the forwarding order of the SF; receive an SFC response returned by the service controller, the SFC response includes an SFC forwarding path, and the SFC forwarding path is generated according to the IP address of the SF or SF agent requested by the target application, and the forwarding order; encapsulate the traffic forwarded by the user plane function to the target application into an SRv6 message, and send the SRv6 message to the first SF or SF agent on the SFC forwarding path associated with the target application.

The embodiment of the present invention further provides a service processing device, which is applied to a service controller and includes a processor and a transceiver.

The transceiver is used to receive a service function chain SFC request of the edge computing platform, wherein the SFC request includes an SFC description, and the SFC description includes a service function SF type requested by a target application and a forwarding order of the SF;

The processor is used for selecting a SF or a SF proxy according to the SFC description, and generating an SFC forwarding path using the IP address of the selected SF or SF proxy;

The transceiver is also used to send an SFC response to the edge computing platform, where the SFC response includes the SFC forwarding path.

The embodiment of the present invention further provides a service processing system, including:

The edge computing platform is used to send a service function chain SFC request to the service controller, wherein the SFC request includes an SFC description, wherein the SFC description includes the service function SF type requested by the target application and the forwarding order of the SF; receive an SFC response returned by the service controller, wherein the SFC response includes an SFC forwarding path, wherein the SFC forwarding path is generated according to the IP address of the SF or SF agent requested by the target application and the forwarding order; encapsulate the traffic forwarded from the user plane function to the target application into an SRv6 message, and send the SRv6 message to the first SF or SF agent on the SFC forwarding path associated with the target application;

The service controller is used to receive the SFC request of the edge computing platform, wherein the SFC request includes an SFC description; select an SF or SF agent according to the SFC description, and generate an SFC forwarding path using the IP address of the selected SF or SF agent; and send an SFC response to the edge computing platform, wherein the SFC response includes the SFC forwarding path.

An embodiment of the present invention further provides a business processing device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor; when the processor executes the program, the business processing method described above is implemented.

An embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps in the business processing method described above are implemented.

The embodiments of the present invention have the following beneficial effects:

In the above scheme, the edge computing platform and the business controller collaborate, the business controller parses the SFC description, configures the relevant business functions, and sends the SFC forwarding path to the edge computing platform; the edge computing platform obtains the SFC forwarding path, and encapsulates and forwards the SRv6 message according to the SFC forwarding path. Through the technical solution of this embodiment, it is possible to provide service calls for applications, and by utilizing the flexible routing characteristics of SRv6, the provision of SFC services becomes very flexible and is no longer limited to individual business resource pool providers. It can enhance user perception, reduce the complexity of configuring SFC, and improve operation and maintenance efficiency. The technical solution of this embodiment does not require changes to the existing network, and can reduce deployment costs.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of providing SFC services in existing edge scenarios;

FIG2 is a schematic diagram of providing SFC services based on ECP in an edge scenario according to an embodiment of the present invention;

FIG3 is a schematic diagram of a process of applying an edge computing platform to call an SFC service according to an embodiment of the present invention;

4 is a schematic diagram of a process of implementing an SFC service by an ECP collaborating with a service controller, a service function, and a service function agent according to an embodiment of the present invention;

5 is a schematic diagram of the structure of a service processing device according to an embodiment of the present invention;

FIG. 6 is a schematic diagram showing the composition of a service processing device according to an embodiment of the present invention.

DETAILED DESCRIPTION

In order to make the technical problems, technical solutions and advantages to be solved by the embodiments of the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

The embodiments of the present invention provide a service processing method and a service processing device, which can reduce the complexity of configuring SFC and improve operation and maintenance efficiency.

An embodiment of the present invention provides a service processing method, which is applied to an edge computing platform, including:

Sending a service function chain SFC request to the service controller, wherein the SFC request includes an SFC description, and the SFC description includes a service function SF type requested by the target application and a forwarding order of the SF;

receiving an SFC response returned by the service controller, wherein the SFC response includes an SFC forwarding path, wherein the SFC forwarding path is generated according to the IP address of the SF or SF proxy requested by the target application and the forwarding sequence;

The traffic forwarded by the user plane function to the target application is encapsulated into an SRv6 message, and the SRv6 message is sent to the first SF or SF proxy on the SFC forwarding path associated with the target application.

In this embodiment, the edge computing platform collaborates with the service controller on the SFC control plane to obtain the SFC forwarding path sent by the service controller; the edge computing platform encapsulates the IP address of the service function SF involved in the service chain into the SRv6 message on the SFC data plane, and transmits the application data along the service chain path through SRv6 on the SFC data plane. It does not need to be configured on each service node in turn, and relies on the flexibility of SRv6, which also makes the implementation of SFC on the data plane very flexible.

FIG2 is a schematic diagram of an edge scenario providing SFC services based on ECP in an embodiment of the present invention. As shown in FIG2 , in this embodiment, the edge computing platform ECP has SFC services and can be called by authorized applications (APP). The SFC services include the following items:

SFC service registration: SFC services can be registered on EPC, making them discoverable by other services or applications;

SFC service call: SFC service can be called by edge applications;

SFC control plane capability: The SFC service can collaborate with the business controller, send the SFC description to the business controller, and obtain the IP address of each business function on the business chain required by the APP from the business controller;

SFC-related message encapsulation (SFC data plane capability): After receiving a message from a terminal (UE) to an APP and identifying the SFC service that the APP has signed up for, the IP address corresponding to each service function in the service chain is used as an identifier based on the IP address of the SFC-related service function obtained previously, and the IP addresses are arranged in the order of the service chains. The SRv6 message is encapsulated and forwarded to the first service function on the SFC in the service resource pool;

Storage function: It can store SFC-related information, including SFC contract information, SFC description, information on the SFC forwarding path corresponding to the SFC service, APP identification, APP IP address, etc.

The service resource pool is a logical concept, which consists of multiple service functions, which can be deployed in a virtualized manner or in a physical device manner. All service functions are managed by the service controller, including the service function registering with the service controller (reporting IP address, whether to support SRv6 protocol, etc.), the service function receiving policies from the service controller and executing the policies of the service controller; the service function receiving statistical requests from the service controller and reporting the operating status to the service controller, etc.

In some embodiments, before sending the SFC request to the service controller, the method further includes:

receiving an SFC service call request of the target application, wherein the SFC service call request includes an identifier of the target application and the SFC description;

An SFC service call response is returned to the target application.

In this embodiment, after the target application sends an SFC service call request to the ECP, the ECP sends an SFC request to the service controller; the SFC service call request includes the target application identifier and the SFC description, the SFC description includes the service function SF type requested by the target application and the forwarding order of the SF, and the ECP forwards the SFC description to the service controller, so that the service controller can parse the SFC description and provide an SFC forwarding path corresponding to the SFC description. Through this embodiment, the SFC service can be provided for the target application.

FIG3 is a flow chart of an application calling an SFC service of an edge computing platform according to an embodiment of the present invention. As shown in FIG3 , the target application calling the SFC service of the edge computing platform includes the following steps:

Step 1: APP sends an SFC service call request to ECP, including API (application programming interface) type, APP identifier, SFC description, etc. In this embodiment, the API type is SFC service; SFC description includes SF type and forwarding order, and SFC description may also include traffic processing requirements, such as prohibiting access to a certain URL (Uniform Resource Locator);

Step 2: ECP checks whether the APP has signed the SFC service. If so, it goes to step 3; otherwise, it returns a request failure message to the APP.

Step 3: Mutual authentication between ECP and APP can be based on certificates. For example, ECP and APP both apply for certificates from the operator CA, exchange certificates between ECP and APP, and use the trusted root certificate to authenticate the certificate signature, thereby proving that their identities are trustworthy;

Step 4: After successful authentication, the SFC API call authorization is performed between ECP and APP, which can be implemented based on the Oath 2.0 mechanism. For example, using the Oath 2.0 protocol, after ECP authenticates the APP, it sends a token to the APP. The APP requests the ECP to call the API service, which carries the token. After ECP authenticates the token, it allows the APP to call the service;

Step 5: APP initiates an SFC service call request to ECP, carrying the authorization certificate;

Step 6: The SFC service of ECP sends an SFC service call response to the APP.

In some embodiments, before receiving the SFC response returned by the service controller, the method further includes:

Mutual authentication and authorization are performed with the service controller, so that the security of the SFC service can be guaranteed, and the ECP and the service controller can communicate based on a secure channel.

The embodiment of the present invention further provides a service processing method, which is applied to a service controller, comprising:

Receive a service function chain SFC request from the edge computing platform, where the SFC request includes an SFC description, where the SFC description includes a service function SF type requested by a target application and a forwarding order of the SF;

Selecting a SF or SF proxy according to the SFC description, and generating an SFC forwarding path using the IP address of the selected SF or SF proxy;

An SFC response is sent to the edge computing platform, where the SFC response includes the SFC forwarding path.

In this embodiment, the edge computing platform collaborates with the service controller, the service controller receives and parses the SFC description, configures the relevant service functions, and sends the SFC forwarding path to the edge computing platform, so that the edge computing platform can obtain the SFC forwarding path, and encapsulate and forward SRv6 messages according to the SFC forwarding path. Through the technical solution of this embodiment, it is possible to provide service calls for applications, and by utilizing the flexible routing characteristics of SRv6, the provision of SFC services becomes very flexible, no longer limited to individual service resource pool providers, which can enhance user perception, reduce the complexity of configuring SFC, and improve operation and maintenance efficiency.

In some embodiments, the SFC description further includes a traffic processing requirement, and the method further includes:

The selected SF or SF agent is configured with a policy according to the traffic processing requirement. For example, if the traffic processing requirement is that the SF needs to discard traffic with source IP address A, destination IP address B, port 8080, and protocol HTTP, then a corresponding policy can be configured for the SF according to the traffic processing requirement, so that the SF performs a discard action when receiving traffic that meets the "source IP address A, destination IP address B, port 8080, and protocol HTTP". In addition, before configuring the policy, you need to check whether it conflicts with the existing policy on SF. For example, if the existing policy on SF is not to discard the traffic with source IP address A and destination IP address B, then you cannot configure the policy of "discarding the traffic with source IP address A, destination IP address B, port 8080, and protocol HTTP" for SF; if the existing policy on SF does not conflict with the policy of "discarding the traffic with source IP address A, destination IP address B, port 8080, and protocol HTTP", then you can configure the policy of "discarding the traffic with source IP address A, destination IP address B, port 8080, and protocol HTTP" for SF.

In some embodiments, before sending the SFC response to the edge computing platform, the method further includes:

Mutual authentication and authorization are performed with the edge computing platform to ensure the security of the SFC service, so that the ECP and the business controller can communicate based on a secure channel.

In some embodiments, before receiving a service function chain SFC request from an edge computing platform, the method further includes:

receiving a first registration request sent by the SF and a second registration request sent by the SF agent, wherein the first registration request includes information of the SF, the second registration request includes information of the SF agent, the information of the SF includes at least one of the following: its own IP address, whether it supports the SRv6 protocol, whether it is associated with a certain SF agent, resource specifications, and provided service types, and the information of the SF agent includes at least one of the following: its own IP address, support for the SRv6 protocol, and the IP address of the proxy SF;

The information of the SF agent is associated with the information of the corresponding SF and stored.

In this embodiment, the service function is managed by the service controller, and the service function and the service function agent register with the service controller, including reporting their own IP address, whether to support the SRv6 protocol, etc.

In some embodiments, selecting a SF or a SF proxy according to the SFC description includes:

Selecting the SF requested by the target application in the SFC description;

If the SF does not support SRv6, a SF agent corresponding to the SF is selected.

In this embodiment, if the SF requested by the target application in the SFC description supports SRv6, the SF can be selected; if the SF requested by the target application in the SFC description does not support SRv6, the SF agent corresponding to the SF can be selected, wherein the SF agent needs to support SRv6. This embodiment provides SFC services through SRv6, and uses the flexible routing characteristics of SRv6 to make the provision of SFC services very flexible.

The embodiment of the present invention further provides a business processing system, as shown in FIG4 , including an edge computing platform, a business controller, a business function and a business function, and the ECP collaborates with the business controller, the business function and the business function agent to implement the SFC service, specifically including the following steps:

Step 1: After the ECP returns the SFC response to the APP, the ECP sends an SFC request to the service controller, which includes the IP address of the APP, the APP identifier, and the SFC description. The SFC description includes the SF type and forwarding order. The SFC description may also include traffic processing requirements, etc. The ECP can interact by calling the northbound interface of the service controller.

Before step 1, SF completes registration with the service controller, including sending IP address, whether SRv6 protocol is supported, resource specifications (such as CPU, memory size, throughput, etc.), and service types provided (such as firewall, load balancing, etc.) to the service controller, which are recorded and saved by the service controller. When the SF proxy registers with the service controller, the information sent includes its own IP address, support for SRv6 protocol, IP address of the proxy SF, etc. The service controller associates and stores the SFproxy information with the information of the SF it proxies.

Step 2: ECP and the business controller perform mutual authentication, and the business controller authorizes ECP to call the SFC service of the northbound interface.

The two can authenticate each other based on certificates. For example, both ECP and business controller apply for certificates from the operator CA. ECP and business controller exchange certificates and use trusted root certificates to authenticate the certificate signatures to prove their identities are credible. After authentication, a secure channel is established for communication. SFC API call authorization is performed between ECP and business controller, which can be implemented based on the Oath 2.0 mechanism. For example, using the Oath 2.0 protocol, after the business controller authenticates the ECP, it sends a token to the ECP. The ECP requests the business controller to call the API service, carrying the token. After the business controller authenticates the token, it allows the ECP to call the service.

Step 3: After authentication and authorization are successful, the service controller parses the received SFC description and selects the SF according to the SFC description. For SFs that do not support SRv6, the corresponding SF proxy must be selected; for SFs that support SRv6, there is no need to select SFproxy. The service controller sends an SFC response to the ECP, which contains the SFC forwarding path, that is, the IP addresses of the SFs or SF proxies arranged in the forwarding order in the SFC description.

Step 4: After receiving the SFC response, the ECP associates and stores the SFC forwarding path related to the SFC contained in the SFC response with the SFC service contract information of the APP.

Step 5. The service controller configures policies for the SF that needs to process traffic according to the traffic processing requirements in the SFC description. For example, if the traffic processing requirement is that the SF needs to discard traffic with source IP address A, destination IP address B, port 8080, and protocol HTTP, then the corresponding policy can be configured for the SF according to the traffic processing requirement, so that the SF performs the discard action when receiving traffic that meets the "source IP address A, destination IP address B, port 8080, and protocol HTTP". In addition, before configuring the policy, you need to check whether it conflicts with the existing policy on SF. For example, if the existing policy on SF is not to discard the traffic with source IP address A and destination IP address B, then you cannot configure the policy of "discarding the traffic with source IP address A, destination IP address B, port 8080, and protocol HTTP" for SF; if the existing policy on SF does not conflict with the policy of "discarding the traffic with source IP address A, destination IP address B, port 8080, and protocol HTTP", then you can configure the policy of "discarding the traffic with source IP address A, destination IP address B, port 8080, and protocol HTTP" for SF.

Step 6: UPF forwards the traffic from UE to APP to ECP according to the diversion strategy.

Step 7: After receiving the traffic, ECP determines whether the APP has signed up for the SFC service based on the APP's IP address or identifier. If the APP has signed up for the SFC service, it searches for the SFC forwarding path corresponding to the SFC service signed by the APP, and encapsulates the received message into an SRv6 message based on the IP addresses of the SF and SF proxy in the SFC forwarding path.

Step 8: ECP forwards the SRv6 packet to the first SF or SF proxy on the SFC path.

Step 9: After receiving the traffic, SF processes it according to the configured policy, such as discarding the traffic with source IP address A and destination IP address B. After receiving the traffic, SF proxy decapsulates the SRv6 message and forwards it to the associated SF. After processing the traffic according to the configured policy, the SF returns the traffic to SF proxy. SF proxy performs subsequent segment routing encapsulation and forwards it.

When SF or SF proxy forwards the message to the next hop and finds that it is the last endpoint of the SRv6 segment route, it decapsulates the SRv6 message and then forwards it to APP.

In this embodiment, the ECP provides SFC services, and the APP calls the SFC services. The SFC control plane service of the ECP collaborates with the business controller to obtain relevant information of the SFC forwarding path; the business controller parses the SFC description, configures relevant business functions, and implements the construction of the SFC control plane; the SFC data plane service of the EPC performs SRv6 message encapsulation and forwarding according to the SFC forwarding path to implement the functions of the SFC data plane. This embodiment can provide service calls for the APP, and use the flexible routing features provided by SRv6 to make the provision of SFC services very flexible, not limited to individual business resource pool providers, improve user perception, reduce the complexity of configuring the SFC, and improve operation and maintenance efficiency. This embodiment does not change the existing network and can be deployed quickly.

The embodiment of the present invention further provides a service processing device, which is applied to an edge computing platform, as shown in FIG5 , and includes a processor 22 and a transceiver 21.

The transceiver 21 is used to send a service function chain SFC request to the service controller, the SFC request includes an SFC description, and the SFC description includes the service function SF type requested by the target application and the forwarding order of the SF; receive an SFC response returned by the service controller, the SFC response includes an SFC forwarding path, and the SFC forwarding path is generated according to the IP address of the SF or SF agent requested by the target application, and the forwarding order; encapsulate the traffic forwarded by the user plane function to the target application into an SRv6 message, and send the SRv6 message to the first SF or SF agent on the SFC forwarding path associated with the target application.

In some embodiments, the transceiver 21 is further configured to receive an SFC service call request from the target application, wherein the SFC service call request includes an identifier of the target application and the SFC description; and return an SFC service call response to the target application.

In some embodiments, the processor 22 is further configured to determine that the target application has signed up for an SFC service based on an identifier of the target application; and perform authentication and SFC application programming interface API call authorization with the target application.

In some embodiments, the processor 22 is further configured to perform mutual authentication and authorization with the service controller.

The embodiment of the present invention further provides a service processing device, which is applied to a service controller, as shown in FIG5 , and includes a processor 22 and a transceiver 21.

The transceiver 21 is used to receive a service function chain SFC request of the edge computing platform, wherein the SFC request includes an SFC description, and the SFC description includes a service function SF type requested by a target application and a forwarding order of the SF;

The processor 22 is used for selecting a SF or a SF proxy according to the SFC description, and generating a SFC forwarding path using the IP address of the selected SF or SF proxy;

The transceiver 21 is further used to send an SFC response to the edge computing platform, where the SFC response includes the SFC forwarding path.

In some embodiments, the processor 22 is further configured to perform policy configuration on the selected SF or SF proxy according to the traffic processing requirement.

In some embodiments, the processor 22 is also used to perform mutual authentication and authorization with the edge computing platform.

In some embodiments, the transceiver 21 is further used to receive a first registration request sent by the SF and a second registration request sent by the SF agent, the first registration request includes information of the SF, the second registration request includes information of the SF agent, the information of the SF includes at least one of the following: its own IP address, whether to support the SRv6 protocol, whether to associate with a certain SF agent, resource specifications, and the type of service provided, and the information of the SF agent includes at least one of the following: its own IP address, support for the SRv6 protocol, and the IP address of the proxy SF; the information of the SF agent is associated with the information of the corresponding SF and stored.

In some embodiments, the processor 22 is further configured to select a SF requested by the target application in the SFC description; if the SF does not support SRv6, select a SF agent corresponding to the SF.

An embodiment of the present invention also provides a business processing device, as shown in Figure 6, including a memory 31, a processor 32, and a computer program stored in the memory 31 and executable on the processor 32; when the processor 32 executes the program, the business processing method described above is implemented.

An embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps in the business processing method described above are implemented.

Computer readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage terminal devices to be detected or any other non-transmission media that can be used to store information that can be accessed by the computer terminal device to be detected. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carriers.

The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims (14)

1. A service processing method, characterized in that it is applied to an edge computing platform, comprising: Sending a service function chain SFC request to the service controller, wherein the SFC request includes an SFC description, and the SFC description includes a service function SF type requested by the target application and a forwarding order of the SF; receiving an SFC response returned by the service controller, wherein the SFC response includes an SFC forwarding path, wherein the SFC forwarding path is generated according to the IP address of the SF or SF proxy requested by the target application and the forwarding sequence; The traffic forwarded by the user plane function to the target application is encapsulated into an SRv6 message, and the SRv6 message is sent to the first SF or SF proxy on the SFC forwarding path associated with the target application. 2. The service processing method according to claim 1, characterized in that before sending the SFC request to the service controller, the method further comprises: receiving an SFC service call request of the target application, wherein the SFC service call request includes an identifier of the target application and the SFC description; An SFC service call response is returned to the target application. 3. The service processing method according to claim 2, characterized in that before returning the SFC service call response to the target application, the method further comprises: Determining the SFC service subscribed by the target application according to the identifier of the target application; Authentication and SFC application programming interface API call authorization are performed with the target application. 4. The service processing method according to claim 1, characterized in that before receiving the SFC response returned by the service controller, the method further comprises: Mutual authentication and authorization are performed with the business controller. 5. A service processing method, characterized in that it is applied to a service controller, comprising: Receive a service function chain SFC request from the edge computing platform, where the SFC request includes an SFC description, where the SFC description includes a service function SF type requested by a target application and a forwarding order of the SF; Selecting a SF or SF proxy according to the SFC description, and generating an SFC forwarding path using the IP address of the selected SF or SF proxy; An SFC response is sent to the edge computing platform, where the SFC response includes the SFC forwarding path. 6. The service processing method according to claim 5, wherein the SFC description further includes a traffic processing requirement, and the method further includes: The selected SF or SF proxy is configured with a policy according to the traffic processing requirement. 7. The service processing method according to claim 5, characterized in that before sending the SFC response to the edge computing platform, the method further comprises: Mutual authentication and authorization are performed with the edge computing platform. 8. The service processing method according to claim 5, characterized in that before receiving the service function chain SFC request of the edge computing platform, the method further comprises: receiving a first registration request sent by the SF and a second registration request sent by the SF agent, wherein the first registration request includes information of the SF, the second registration request includes information of the SF agent, the information of the SF includes at least one of the following: its own IP address, whether it supports the SRv6 protocol, whether it is associated with a certain SF agent, resource specifications, and provided service types, and the information of the SF agent includes at least one of the following: its own IP address, support for the SRv6 protocol, and the IP address of the proxy SF; The information of the SF agent is associated with the information of the corresponding SF and stored. 9. The service processing method according to claim 8, wherein the selecting the SF or SF agent according to the SFC description comprises: Selecting the SF requested by the target application in the SFC description; If the SF does not support SRv6, a SF agent corresponding to the SF is selected. 10. A service processing device, characterized in that it is applied to an edge computing platform, comprising a processor and a transceiver, The transceiver is used to send a service function chain SFC request to the service controller, the SFC request includes an SFC description, and the SFC description includes the service function SF type requested by the target application and the forwarding order of the SF; receive an SFC response returned by the service controller, the SFC response includes an SFC forwarding path, and the SFC forwarding path is generated according to the IP address of the SF or SF agent requested by the target application, and the forwarding order; encapsulate the traffic forwarded by the user plane function to the target application into an SRv6 message, and send the SRv6 message to the first SF or SF agent on the SFC forwarding path associated with the target application. 11. A service processing device, characterized in that it is applied to a service controller, comprising a processor and a transceiver, The transceiver is used to receive a service function chain SFC request of the edge computing platform, wherein the SFC request includes an SFC description, and the SFC description includes a service function SF type requested by a target application and a forwarding order of the SF; The processor is used for selecting a SF or a SF proxy according to the SFC description, and generating an SFC forwarding path using the IP address of the selected SF or SF proxy; The transceiver is also used to send an SFC response to the edge computing platform, where the SFC response includes the SFC forwarding path. 12. A business processing system, comprising: The edge computing platform is used to send a service function chain SFC request to the service controller, wherein the SFC request includes an SFC description, wherein the SFC description includes the service function SF type requested by the target application and the forwarding order of the SF; receive an SFC response returned by the service controller, wherein the SFC response includes an SFC forwarding path, wherein the SFC forwarding path is generated according to the IP address of the SF or SF agent requested by the target application and the forwarding order; encapsulate the traffic forwarded from the user plane function to the target application into an SRv6 message, and send the SRv6 message to the first SF or SF agent on the SFC forwarding path associated with the target application; The service controller is used to receive the SFC request of the edge computing platform, wherein the SFC request includes an SFC description; select an SF or SF agent according to the SFC description, and generate an SFC forwarding path using the IP address of the selected SF or SF agent; and send an SFC response to the edge computing platform, wherein the SFC response includes the SFC forwarding path. 13. A business processing device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor; characterized in that when the processor executes the program, the business processing method according to any one of claims 1 to 9 is implemented. 14. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the program implements the steps in the business processing method according to any one of claims 1 to 9.