# US 12,225,100 B2 · System, devices and/or processes for executing service functions > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,225,100 B2 - Document ID: US12225100B2 - Status: Granted - Kind: B2 - Application number: 17/697,767 - Filed: 2022-03-17 - Published: 2023-09-21 - Granted: 2025-02-11 - Earliest claimed: 2022-03-17 - Assignees: Arm Limited - Applicants: Arm Limited - Inventors: Zijin Tao; Zaiping Bie; Song Zhu - Web page: https://patentgrep.com/patent/US12225100B2 ## CPC - H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) - H04L 45/306: {Route determination based on the nature of the carried application} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Example methods, apparatuses, and/or articles of manufacture are disclosed that may be implemented, in whole or in part, using one or more computing devices to process requests to execute instance of service functions in a service function chain. In one particular implementation, a request to execute an instance of a second service function in a service function change may be initiated prior to completion of an execution of an instance of a first service function in the service function chain. ## Claims ### Claim 1 A method comprising: responsive to one or more signals received from a communication network, initiating via a service function forwarder a request to execute an instance of a first service function in a service function chain comprising an ordered sequence of service functions to be traversed; determining in the service function forwarder a capability of a subsequent service function in the service function chain to be predictively executed; initiating via the service function forwarder a request to execute an instance of the subsequent service function in the service function chain prior to receipt in the service function forwarder of a response to the request to execute the instance of the first service function responsive to the capability of the subsequent service function to be predictively executed; and receiving in the service function forwarder the response to the request to execute the instance of the first service function and a separate response to the request to execute the instance of the first service function. ### Claim 2 (depends on 1) The method of claim 1, wherein initiating the request to execute the instance of the subsequent service function in the service function chain further comprises initiating the request to execute the instance of the subsequent service function responsive, at least in part, to one or more parameters specified in a signal packet received from the communication network. ### Claim 3 (depends on 2) The method of claim 2, wherein the one or more parameters are specified in a signal packet header. ### Claim 4 (depends on 2) The method of claim 2, wherein the one or more parameters are specified in a Network Service Header (NSH) formatted according to IETF RFC83000. ### Claim 5 (depends on 1) The method of claim 1, wherein initiation of the request to execute the instance of the subsequent service function is conditioned on attributes of received message traffic. ### Claim 6 (depends on 5) The method of claim 5, wherein the attributes of the received message traffic are determined based, at least in part, on a source IP address, destination IP address, source port identifier, destination port identifier or a protocol identifier, or a combination thereof. ### Claim 7 (depends on 1) The method of claim 1, wherein execution of the instance of the subsequent service function occurs at least partially currently with execution of the first service function. ### Claim 8 (depends on 1) The method of claim 1, wherein initiating the request to execute the instance of the subsequent service function comprises transmitting a request message, and wherein the method further comprises transmitting a message to revoke the request message responsive to receipt of a response message indicating a failure to execute the instance of the subsequent service function or a timeout condition. ### Claim 9 A computing device, comprising: a communication device to receive messages from a communication network; and one or more processors to: initiate via a service function forwarder a request to execute an instance of a first service function in a service function chain comprising an ordered sequence of service functions to be traversed responsive to one or more signals received at the communication device from the communication network; determine in the service function forwarder a capability of a subsequent service function in the service function chain to be predictively executed; initiate via the service function forwarder a request to execute an instance of a subsequent service function in the service function chain prior to receipt in the service function forwarder of a response to the request to execute the instance of the first service function responsive to the capability of the subsequent service function to be predictively executed; and receiving in the service function forwarder the response to the request to execute the instance of the first service function and a separate response to the request to execute the instance of the first service function. ### Claim 10 (depends on 9) The computing device of claim 9, wherein the request to execute the instance of the subsequent service function in the service function chain to be initiated responsive, at least in part, to one or more parameters specified in a signal packet received from the communication network. ### Claim 11 (depends on 10) The computing device of claim 10, wherein the one or more parameters are specified in a signal packet header. ### Claim 12 (depends on 10) The computing device of claim 10, wherein the one or more parameters are specified in a Network Service Header (NSH) formatted according to IETF RFC83000. ### Claim 13 (depends on 9) The computing device of claim 9, wherein initiation of the request to execute the instance of the subsequent service function to be conditioned on attributes of received message traffic. ### Claim 14 (depends on 13) The computing device of claim 13, wherein the attributes of the received message traffic to be determined based, at least in part, on a source IP address, destination IP address, source port identifier, destination port identifier or a protocol identifier, or a combination thereof. ### Claim 15 (depends on 9) The computing device of claim 9, wherein execution of the instance of the subsequent service function to occur at least partially currently with execution of the first service function. ### Claim 16 (depends on 9) The computing device of claim 9, wherein the request to execute the instance of the subsequent service function to be initiated by transmission of a request message, and wherein the one or more processors are further to initiated transmission of a message through the communication device to revoke the request message responsive to receipt of a response message indicating a failure to execute the instance of the subsequent service function or a timeout condition. ### Claim 17 An article comprising: a storage medium comprising computer-readable instructions stored thereon which are executable by one or more processors of a computing device to: initiate a request to execute via a service function forwarder an instance of a first service function in a service function chain comprising an ordered sequence of service functions to be traversed responsive to one or more signals received from a communication network; determine in the service function forwarder a capability of a subsequent service function in the service function chain to be predictively executed; initiate a request to execute via the service function forwarder an instance of a subsequent service function in the service function chain prior to receipt in the service function forwarder of a response to the request to execute the instance of the first service function responsive to the capability of the subsequent service function to be predictively executed; and receiving in the service function forwarder the response to the request to execute the instance of the first service function and a separate response to the request to execute the instance of the first service function. ### Claim 18 (depends on 17) The article of claim 17, wherein the computer-readable instructions are further executable by the one or more processors to initiate the request to execute the instance of the subsequent service function responsive, at least in part, to one or more parameters specified in a signal packet received from the communication network. ### Claim 19 (depends on 17) The article of claim 17, wherein initiation of the request to execute the instance of the subsequent service function to be conditioned on attributes of received message traffic. ### Claim 20 (depends on 19) The article of claim 19, wherein the attributes of the received message traffic are determined based, at least in part, on a source IP address, destination IP address, source port identifier, destination port identifier or a protocol identifier, or a combination thereof.