Methods, Devices, and Computer-Readable Media for Service Chaining

Abstract

A method, device, and computer-readable medium for service chaining are provided. Dynamic service chaining is implemented, and a service chaining request is sent from an application. The device determines a service chain based on the profile of the application. In addition, implicit service chain subscription is implemented. Thus, a more flexible service chain is achieved. In addition, the management of service chains related to NF services is implemented.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to communication technologies, and more particularly to methods, devices, and computer-readable media for service chaining. Background Art

[0002] In recent communication networks, new technologies for service chaining have been proposed. Service chaining is a set of emerging technologies and processes that enables operators to dynamically configure network services in software without changing the network at the hardware level. By routing traffic according to a "service graph", service chaining meets the requirements of network optimization by better utilizing resources and monetizing by providing services tailored to customer-specific needs. Summary of the Invention

[0003] Generally, embodiments of the present disclosure relate to a method for service chaining and a corresponding communication device.

[0004] In a first aspect, embodiments of the present disclosure provide a device. The device includes at least one processor; and a memory coupled to the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the device to: at the device, receive from another device a request for a service chain for an application served by the another device. The service chain includes at least one service associated with the application and configured by an NEF device. The device is further caused to obtain a profile of the service chain, the profile including an identification of the application and a list of services for the application. The device is further caused to determine a target service chain based on the profile and the request.

[0005] In a second aspect, embodiments of the present disclosure provide a device. The device includes at least one processor; and a memory coupled to the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the device to: at another device, send to an NEF device a request for a service chain for an application served by the another device. The service chain includes at least one service associated with the application and configured by the another device. The device is further caused to receive from the another device a response to the request, the response indicating a target service chain that is determined based on a profile and the request, the profile including an identification of the application and a list of services for the application.

[0006] In a third aspect, embodiments of the present disclosure provide a device. The device includes at least one processor; and a memory coupled to the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the device to: at the device, determine whether a profile of a service chain for an application needs to be updated, the profile including an identification of the application and a list of services for the application. The device is further caused to update the profile based on a predetermined profile template in response to the profile needing to be updated.

[0007] In a fourth aspect, embodiments of the present disclosure provide a method. The method includes, at an NEF device, receiving from a communication device a request for a service chain for an application served by the communication device. The service chain includes at least one service associated with the application and configured by the NEF device. The method further includes obtaining a profile of the service chain, the profile including an identification of the application and a service list for the application. The method further includes determining a target service chain based on the profile and the request.

[0008] In a fifth aspect, embodiments of the present disclosure provide a method. The method includes, at a communication device, sending to an NEF device a request for a service chain for an application served by the communication device. The service chain includes at least one service associated with the application and configured by the NEF device. The method further includes receiving from the NEF device a response to the request, the response indicating a target service chain that is determined based on a profile and the request, the profile including an identification of the application and a service list for the application.

[0009] In a sixth aspect, embodiments of the present disclosure provide a method. The method includes, at an NRF device, determining whether a profile of a service chain for an application needs to be updated, the profile including an identification of the application and a service list for the application. The method further includes updating the profile based on a predetermined profile template in response to the profile needing to be updated.

[0010] In a seventh aspect, embodiments of the present disclosure provide an apparatus. The apparatus includes means for receiving, at an NEF device, from a communication device a request for a service chain for an application served by the communication device. The service chain includes at least one service associated with the application and configured by the NEF device. The apparatus further includes means for obtaining a profile of the service chain, the profile including an identification of the application and a service list for the application. The apparatus further includes means for determining a target service chain based on the profile and the request.

[0011] In an eighth aspect, embodiments of the present disclosure provide an apparatus. The apparatus includes means for sending, at a communication device, to an NEF device a request for a service chain for an application served by the communication device, the service chain including at least one service associated with the application and configured by the NEF device. The apparatus further includes means for receiving from the NEF device a response to the request, the response indicating a target service chain that is determined based on a profile and the request, the profile including an identification of the application and a service list for the application.

[0012] In a ninth aspect, an embodiment of the present disclosure provides an apparatus. The apparatus includes means for determining, at an NRF device, whether a profile of a service chain for an application needs to be updated. The profile includes an identification of the application and a list of services for the application. The apparatus further includes means for updating the profile based on a predetermined profile template in response to the profile needing to be updated.

[0013] In a seventh aspect, an embodiment of the present disclosure provides a computer-readable medium. The computer-readable medium stores instructions that, when executed by at least one processing unit of a machine, cause the machine to implement the method according to the fourth, fifth, or sixth aspect.

[0014] Other features and advantages of embodiments of the present disclosure will also be apparent from reading the following description of specific embodiments in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Embodiments of the present disclosure are presented by way of example and their advantages are explained in more detail below with reference to the accompanying drawings, in which

[0016] Figure 1 a schematic diagram of a service chain is shown;

[0017] Figure 2 a schematic diagram of the architecture of a service function chain is shown;

[0018] Figure 3 a schematic diagram of a communication system according to an embodiment of the present disclosure is shown;

[0019] Figure 4 a schematic diagram of the interaction between devices according to an embodiment of the present disclosure is shown;

[0020] Figure 5A a schematic diagram of a service chain according to an embodiment of the present disclosure is shown;

[0021] Figure 5B a schematic diagram of a device according to an embodiment of the present disclosure is shown;

[0022] Figure 6 a flowchart of a method implemented at a communication device according to an embodiment of the present disclosure is shown;

[0023] Figure 7 a flowchart of a method implemented at a communication device according to an embodiment of the present disclosure is shown;

[0024] Figure 8 a flowchart of a method implemented at a communication device according to an embodiment of the present disclosure is shown;

[0025] Figure 9AA schematic diagram showing the interaction between devices according to an embodiment of the present disclosure;

[0026] Figure 9B A schematic diagram showing the interaction between devices according to an embodiment of the present disclosure;

[0027] Figure 10 A schematic diagram showing a device according to an embodiment of the present disclosure; and

[0028] Figure 11 A block diagram showing an example computer-readable medium according to some embodiments of the present disclosure.

[0029] In all the figures, the same or similar reference numerals denote the same or similar elements. Detailed Description

[0030] The subject matter described herein will now be discussed with reference to several example embodiments. It should be understood that the discussion of these embodiments is only for enabling those skilled in the art to better understand and thus implement the subject matter described herein, without imposing any limitation on the scope of the subject matter.

[0031] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the example embodiments. As used herein, the singular forms "a", "an" and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "includes" and / or "including" when used herein specify the presence of the stated features, integers, steps, operations, elements and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0032] It should also be noted that in some alternative implementations, the indicated functions / actions may not occur in the order indicated in the figures. For example, two functions or actions shown consecutively may actually be executed simultaneously, or sometimes in the reverse order, depending on the functions / actions involved.

[0033] As used herein, the term "communication network" refers to a network that follows any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any suitable generation communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocol, and / or any other protocol known or developed in the future.

[0034] Embodiments of the present disclosure can be applied to various communication systems. Considering the rapid development of communications, there will of course also be future types of communication technologies and systems in which the present disclosure can be embodied. The scope of the present disclosure should not be limited to the above systems. For purposes of illustration, embodiments of the present disclosure will be described with reference to a 5G communication system.

[0035] As used herein, the term "network device" includes, but is not limited to, a base station (BS), a gateway, a registration management entity, and other suitable devices in a communication system. The term "base station" or "BS" refers to a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low-power node (such as a femto, pico, etc.).

[0036] As used herein, the term "terminal device" includes, but is not limited to, a "user equipment (UE)" and other suitable terminal devices capable of communicating with a network device. For example, a "terminal device" may refer to a terminal, a mobile terminal (MT), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT).

[0037] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0038] (a) Only hardware circuit implementations (such as only in analog and / or digital circuitry), and

[0039] (b) A combination of hardware circuits and software, such as (where applicable):

[0040] (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and

[0041] (ii) Any part of a (multiple) hardware processors with software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to cause a device (such as a mobile phone or a server) to perform various functions), and

[0042] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a part of (multiple) microprocessors, which require software (e.g., firmware) to operate, but the software may not be present when not needed for operation.

[0043] The definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also encompasses implementations of only hardware circuits or processors (or multiple processors) or a part of a hardware circuit or processor and their (or their) accompanying software and / or firmware. The term circuitry also encompasses (for example and if applicable to a particular claim element) a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network devices.

[0044] As described above, techniques for service chaining have been proposed. Service chaining provides a very flexible way for more intelligent and agile management of network services. Figure 1 A schematic diagram of service chaining is shown. Service 101, Service 102, Service 103, Service 104, Service 105, Service 106, Service 107, and Service 108 are connected via a network to other services. For example, Figure 1 Three service chains are shown. Service chain 1010 may include Service 101, Service 102, Service 103, and Service 104. Service chain 1020 may include Service 101, Service 102, Service 105, Service 106, and Service 108. Service chain 1030 may include Service 101, Service 105, Service 106, and Service 107.

[0045] Service chaining has many use cases, which are well-known throughout the industry. Most importantly, service chaining is a horizontal capability that can support an infinite number of use cases. Table 1 below is just some examples:

[0046] Table 1

[0047]

[0048]

[0049] In addition, the Service Function Chain (SFC) is an architecture being developed in the IETF. Figure 2 An example of the SFC architecture is shown. In recent research, the 5G system architecture is defined as a service-based architecture, that is, a system architecture in which system functions are implemented by a set of network functions (NFs) providing services to other authorized NFs to access their services.

[0050] An NF service is a type of capability that is opened by an NF as an NF service producer to other authorized NFs as NF service consumers through a service-based interface. An NF service can support one or more NF service operations.

[0051] The NF can provide different functions and thus provide different NF services. Each of the NF services provided by the NF should be self - contained and be operated and managed independently of other NF services provided by the same NF (e.g., for extension, repair).

[0052] The control - plane NFs within the 5G core network can expose their capabilities as services via their service - based interfaces, and the services can be reused by the control - plane core network (CN) NFs.

[0053] NF service discovery enables the CN NF to discover the (multiple) NF instances that provide the (multiple) expected NF services. Generally, the Network Repository Function (NRF) supports the following functions: receiving NF discovery requests from NF instances and providing the information of the discovered NF instances (discovered) to the NF instances; maintaining the NF profiles of the available NF instances and the services they support. Table 2 below shows some examples of NRF service operations.

[0054] [[ID=⑨]]Table 2

[0055]

[0056]

[0057] To correctly maintain the information of the available NF instances and the services they support, each NF instance notifies the NRF of the list of NF services it supports. When an NF instance is about to be shut down normally in a controlled manner or disconnected from the network, it can also deregister from the NRF. The external exposure of network capabilities (supported by the Network Exposure Function (NEF)) is shown in Table 3 below regarding the NF services provided by the NEF. The term "Network Exposure Function" as used in this document refers to providing a method to securely expose the services and capabilities provided by 3GPP network functions and supporting the exposure of capabilities and events, the secure provision of information from external applications to the 3GPP network, and the transformation of internal / external information.

[0058] Table 3

[0059]

[0060]

[0061] Recently, there are many applications in the current communication system. However, the application support of the current 5G system is far from meeting the application requirements. Therefore, there is a large gap that should be filled.

[0062] The current 5G system cannot support applications to fully utilize the existing service capabilities of the network, such as security, firewall, intrusion prevention, deep packet inspection (DPI), HTTP header enrichment, data optimization and capture, etc. It requires applications to provide all necessary service functions by themselves, not to mention providing dynamic services based on changes in 5G network conditions. Besides the double efforts on both the application and the network, it is difficult for applications to change themselves in a timely manner to respond to market demands. In addition, considering that the VAS (value-added service) functions change dynamically with the deployment of more and more new VAS NFs, dynamic service chain management in the 5G system should also be supported. Monetizing the 5G network resources of operators may also be a big problem. If this problem is not solved, operators will lose many revenue opportunities.

[0063] According to an embodiment of the present disclosure, a dynamic service chain is implemented, and a service chain request is transmitted from an application. Thus, a more flexible service chain is achieved. In addition, according to an embodiment of the present invention, the management of the service chain related to the NF service is also implemented.

[0064] Figure 3 A schematic diagram of a communication system 300 in which embodiments of the present disclosure can be implemented is shown. The communication system 300, as part of a communication network, includes a device 310 (hereinafter also referred to as "NEF device 310") capable of supporting network exposure functions. The communication system 300 includes devices 320-1, 320-2, ……, 320-N (collectively referred to as "communication devices 320") that serve applications. The communication system 300 may also include a device 330 (referred to as "NRF device 330") capable of supporting network repository functions. It should be understood that the communication system 300 may also include other elements omitted for clarity. It should be understood that Figure 3 The number of terminal devices and network devices shown is given for illustrative purposes and does not represent any limitation.

[0065] The communication in the communication system 300 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local area network communication protocols such as those of the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol known currently or to be developed in the future. In addition, the communication can utilize any suitable wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexer (FDD), time division duplexer (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDMA), and / or any other technology known currently or to be developed in the future.

[0066] Figure 4 FIG. shows a schematic diagram of an interaction 400 according to an embodiment of the present disclosure. The interaction 400 can be implemented at any suitable device. For illustrative purposes only, the interaction 400 is described as being implemented at the NEF device 310, the communication device 320-1, and the NRF device 330.

[0067] The communication device 320-1 sends 405 a request for a service chain for an application to the NEF device 310. The application is served by the communication device 320-1. The request can include one or any combination of the following: an identifier of the application; information for identifying the traffic for the service chain; the requested service chain; an acceptable charging rate for the requested service chain. The service chain can include one or more services associated with the application and can be configured by the NEF device 310. In this way, the application can request a service chain, which improves the flexibility of the service chain. Figure 5A FIG. shows a schematic diagram of the requested service chain. The service chain 510 can include identification information of the services 510-1 and 510-3. After the services are added, the flow can be transmitted to the data network 520.

[0068] In some embodiments, the request can also include an indicator for indicating whether the service is mandatory or optional. In a scenario where a service should be released from the service chain, the identifier of the service marked as optional can be selected. For example, if the current charging rate exceeds the acceptable charging rate or the service function is overloaded, the service marked as optional can be removed from the service chain. Alternatively, the request can be blank, which means that the communication device 320-1 wants a service chain recommendation from the NEF device 310.

[0069] By way of example only, Figure 5B FIG. shows a schematic diagram of the NEF device 310. The NEF device can include a service chain management module 3010, a service chain advisor module 3020, and a smart charging management module 3030. It should be noted that the NEF device 310 can also include other modules. The service chain management module 3010 can receive a request for a service chain from the communication device 320-1 and process the request. Details of this module will be given later.

[0070] Referring again to Figure 4, the NEF device 310 (e.g., the service chain management module 3010) can verify 406 whether the communication device 320-1 is authorized to request a service chain. If the NEF device 310 verifies that the communication device 320-1 is authorized, then the NEF device 310 (e.g., the service chain management module 3010) obtains 410 the profile of the service chain. The profile includes the identification of the application and the list of services for the application. In some embodiments, the profile can be retrieved from a database accessible to the NEF device 310. Alternatively, the NEF device 310 can send 415 another request to the NRF device 330 to obtain the profile from the NRF device 330. The NRF device 330 can send 420 another response including the profile to the NEF device 310.

[0071] The profile can include one or any combination of the following: available services; the charging rate for each service; mandatory services to be added to the service chain for an application defined by the operator based on network knowledge; the operator-defined service chain for an application defined by the operator based on network knowledge; or available service chain functions. If the availability of a parameter is conditionally dependent on another parameter, its availability criterion should be associated with that parameter.

[0072] The NEF device 310 determines 425 the target service chain based on the profile and the request. In some embodiments, the NEF device 310 can determine the target service based on the connection condition between the first device and the communication device. For example, if the request is empty, the NEF device 310 can determine one or more non-congested services as the target service chain.

[0073] In some embodiments, the NEF device 310 can determine whether the service chain is valid based on the profile. For example, if the identification of one or more services in the request is shown as available in the profile, the NEF device 310 can determine that the service chain is valid. Alternatively or additionally, if the charging rate threshold in the profile meets the acceptable charging rate in the request, the NEF device 310 can determine that the service chain is valid. In other embodiments, if one or more mandatory services in the request are not missing, the NEF device 310 can determine that the service chain is valid. If the service chain is valid, the NEF device 310 can determine the requested service chain as the target service chain.

[0074] In some embodiments, the request may include a predefined policy for the service, e.g., a set of service chain rules for defining both criteria and service chain operations based on different connection conditions. Once the predefined policy is accepted, the NEF device 310 can determine the target service chain accordingly based on the predefined policy. For example, the predefined policy may include any one or combination of the following: providing different service chains for different services; providing different service chains once the rate is changed; introducing another service into the service chain if a certain predefined event occurs (e.g., malicious attack, network congestion); or removing a service from the service chain if the service is not needed after the connection condition changes.

[0075] The NEF device 310 may send a 430 response to the communication device 320-1. The request indicates the target chain. In some embodiments, there may be some negotiation between the NEF device 310 and the communication device 320-1. The NEF device 310 may send a candidate service chain to the communication device 320-1.

[0076] In some embodiments, the NEF device 310 (e.g., the service chain consultation module 3020) may provide one or more candidate service chains. For example, the NEF device 310 may provide a candidate service chain including service 510-1 and service 510-2.

[0077] For example, if the network detects an application service and there is no service chain for it or the service chain is inappropriate based on network knowledge, the NEF device 310 may provide a candidate service chain. Alternatively, if a new service is introduced into the network, the NEF device 310 may provide a candidate service chain. In other embodiments, a certain predefined criterion may be matched (e.g., the network detects a malicious attack, network congestion, or a lower quality of service (QoS) of the application, and the NEF device 310 may provide a candidate service chain). In additional embodiments, if the service availability changes (e.g., idle / low billing rate), the NEF device 310 may provide a candidate service chain. Alternatively, if the application service chain profile is updated, the NEF device 310 may provide a candidate service chain. The NRF device 330 may generate 430 profiles and / or update 435 profiles. Details regarding the generation and / or update of profiles will be given later.

[0078] In this way, dynamic service chain management in the 5G service-based architecture and applications can request service chains from the 5G network. In addition, the duplication of work for applications to implement services that can be provided by the network is eliminated. It also enables the application to focus only on the unique functions it should provide for the end user and the service chain controlled by the application in the 5G network. Once the network conditions change, the service chain can be dynamically changed based on the application requirements. It is much easier and faster to add or remove functions for the application.

[0079] Figure 6 FIG. 600 is a flowchart of a method according to an embodiment of the present disclosure. The method 600 may be implemented at any suitable device. For illustrative purposes only, the method 600 is described as being implemented at the NEF device 310.

[0080] At block 610, the NEF device 310 receives a request for a service chain for an application to the NEF device 310. The application is served by the communication device 320-1. The request may include one or any combination of the following: an identifier of the application; information for identifying the traffic for the service chain; the requested service chain; an acceptable charging rate for the requested service chain. The service chain may include one or more services associated with the application and may be configured by the NEF device 310.

[0081] In some embodiments, the request may also include an indicator for indicating whether the service is mandatory or optional. In a scenario where a service should be released from the service chain, the identifier of the service marked as optional may be selected. For example, if the current charging rate exceeds the acceptable charging rate or the service function is overloaded, the service marked as optional may be removed from the service chain. Alternatively, the request may be blank, which means that the communication device 320-1 wants a service chain suggestion from the NEF device 310.

[0082] At block 620, the NEF device 310 obtains a profile of the service chain. The profile includes an identifier of the application and a list of services for the application. In some embodiments, the NEF device 310 may verify whether the communication device 320-1 is authorized to request the service chain. In some embodiments, the profile may be obtained from a database accessible to the NEF device 310. Alternatively, the NEF device 310 may send another request to the NRF device 330 to obtain the profile from the NRF device 330. The NRF device 330 may send another response to the NEF device 310 including the profile.

[0083] The profile may include one or any combination of the following: available services; a charging rate for each service; mandatory services to be added to the service chain for applications defined by the operator based on network knowledge; operator-defined service chains for applications defined by the operator based on network knowledge; or available service chain functions. If the availability of a parameter is conditionally dependent on another parameter, its availability criterion should be associated with that parameter.

[0084] At block 630, the NEF device 310 determines a target service chain based on the profile and the request. In some embodiments, the NEF device 310 may determine the target service based on the connection condition between the first device and the communication device. For example, if the request is empty, the NEF device 310 may determine one or more non-congested services as the target service chain.

[0085] In some embodiments, the NEF device 310 may determine whether a service chain is valid based on a profile. For example, if the identification of one or more services in the request is shown as available in the profile, the NEF device 310 may determine that the service chain is valid. Alternatively or additionally, if the billing rate threshold in the profile meets the acceptable billing rate in the request, the NEF device 310 may determine that the service chain is valid. In other embodiments, if one or more services mandated in the request are not missing, the NEF device 310 may determine that the service chain is valid. If the service chain is valid, the NEF device 310 may determine the requested service chain as the target service chain.

[0086] In some embodiments, the request may include a predefined policy for the service, e.g., a set of service chain rules for defining both criteria and service chain operations based on different connection conditions. Once the predefined policy is accepted, the NEF device 310 may accordingly determine the target service chain based on the predefined policy. For example, the predefined policy may include any one or combination of the following: providing different service chains for different services; providing different service chains once the rate is changed; introducing another service into the service chain if a certain predefined event (e.g., malicious attack, network congestion) occurs; or removing a service from the service chain if the service is not needed after the connection condition changes.

[0087] In some embodiments, the NEF device 310 sends a response to the communication device 320-1. The request indicates the target chain. In some embodiments, there may be some negotiation between the NEF device 310 and the communication device 320-1. The NEF device 310 may send a candidate service chain to the communication device 320-1.

[0088] In some embodiments, the NEF device 310 may provide one or more candidate service chains. For example, the NEF device 310 may provide a candidate service chain including service 510-1 and service 510-2.

[0089] For example, if the network detects an application service and there is no service chain for it or the service chain is inappropriate based on network knowledge, the NEF device 310 may provide a candidate service chain. Alternatively, if a new service is introduced into the network, the NEF device 310 may provide a candidate service chain. In other embodiments, a certain predefined criterion may be met (e.g., the network detects a malicious attack, network congestion, or a low quality of service (QoS) of an application, and the NEF device 310 may provide a candidate service chain). In additional embodiments, if the service availability changes (e.g., idle / low billing rate), the NEF device 310 may provide a candidate service chain. Alternatively, if the application service chain profile is updated, the NEF device 310 may provide a candidate service chain. In some embodiments, if the state of the communication device changes, e.g., the communication device 320-1 does not pay for the service chain, the NEF device 310 may send a candidate service chain.

[0090] In some embodiments, an apparatus (e.g., the NEF device 310) for performing method 600 may include corresponding components for performing the corresponding steps in method 600. These components may be implemented in any suitable manner. For example, it may be implemented by circuitry or software modules.

[0091] In some embodiments, the apparatus includes components for receiving, from a communication device, a request for a service chain for an application served by the communication device, the service chain including at least one service associated with the application and configured by the NEF device; components for obtaining a profile of the service chain, the profile including an identification of the application and a list of services for the application; and components for determining a target service chain based on the profile and the request.

[0092] In some embodiments, the apparatus includes components for transmitting, to the communication device, a response to the request, the response indicating the target service chain.

[0093] In some embodiments, the request includes at least one of the following: an identification of the application, information for identifying the service of the service chain, an acceptable billing rate for the service chain, or an identification of at least one service.

[0094] In some embodiments, the components for obtaining a profile of the service chain include: components for determining whether the communication device is authorized to request a service chain; and components for obtaining the profile from a database accessible to the NEF device in response to determining that the communication device is authorized to request a service chain.

[0095] In some embodiments, the components for obtaining a profile of a service chain include: a component for determining whether a communication device is authorized to request a service chain; a component for sending another request for the profile to an NRF device in response to determining that the communication device is authorized to request a service chain; and a component for receiving another response to the another request including the profile from the NRF device.

[0096] In some embodiments, the components for determining a target service chain include: a component for determining the target service chain based on conditions of a network connection.

[0097] In some embodiments, the components for determining a target service chain include: a component for obtaining a predetermined policy of the service chain from a request; and a component for determining the target service chain based on network connection conditions and the predetermined policy.

[0098] In some embodiments, the components for determining a target service chain include: a component for determining whether the service chain is valid based on a profile; and a component for determining the service chain as the target service chain in response to determining that the service chain is valid.

[0099] In some embodiments, the components for determining that the service chain is valid include: a component for determining that the service chain is valid in response to the availability of an identifier of at least one service; a component for determining that the service chain is valid in response to a rate threshold in the profile meeting an acceptable rate in the request; or a component for determining that the service chain is valid in response to at least one service in the request not being lost.

[0100] In some embodiments, the apparatus further includes: a component for transmitting a candidate service chain to a communication device in response to at least one of the following: the profile is updated, a new service is added, there is no available service chain for an application, or the state of the communication device is changed.

[0101] In some embodiments, the apparatus further includes: a component for receiving dynamic charging information from a fourth device connected to a NEF device; a component for determining a new rate for an application based on the dynamic charging information; and a component for sending the new rate to the communication device in a response.

[0102] Figure 7 A flowchart of a method 700 according to an embodiment of the present disclosure is shown. Method 700 may be implemented at any suitable device. For illustrative purposes only, method 700 is described as being implemented at a communication device 320-1.

[0103] At block 710, communication device 320-1 sends a request for a service chain for an application served by communication device 320-1. The service chain includes one or more services associated with the application and configured by NEF device 310.

[0104] In some embodiments, the request may further include an indicator for indicating whether the service is mandatory or optional. In a scenario where a service should be released from the service chain, the identity of a service marked as optional may be selected. For example, if the current billing rate exceeds the acceptable billing rate or the service function is overloaded, the service marked as optional may be removed from the service chain. Alternatively, the request may be blank, indicating that the communication device 320-1 wants a service chain recommendation from the NEF device 310.

[0105] In some embodiments, the request may include a predefined policy for the service, e.g., a set of service chain rules for defining both criteria and service chain operations based on different connection conditions.

[0106] At block 720, the communication device 320-1 receives a response to the request. The response indicates a target chain determined based on the profile and the request. The profile includes the identity of the application and a list of services for the application.

[0107] The profile may include one or any combination of the following: available services; the billing rate for each service; mandatory services to be added to the service chain for an application defined by the operator based on network knowledge; the operator-defined service chain for an application defined by the operator based on network knowledge; or available service chain functions. If the availability of a parameter is conditionally dependent on another parameter, its availability criterion should be associated with that parameter.

[0108] In some embodiments, the communication device 320-1 may receive one or more candidate service chains. For example, if the network detects application traffic and there is no service chain for it or the service chain is inappropriate based on network knowledge, the communication device 320-1 may receive candidate service chains. Alternatively, if a new service is introduced into the network, the communication device 320-1 may receive candidate service chains. In other embodiments, some predefined criteria may be matched (e.g., the network detects a malicious attack, network congestion, or service quality (QoS) detected by the network for an application, and the communication device 320-1 may receive candidate service chains). In additional embodiments, if the service availability changes (e.g., idle / low billing rate), the communication device 320-1 may receive candidate service chains. Alternatively, if the profile is updated, the communication device 320-1 may receive candidate service chains. In some embodiments, if the state of the communication device changes, e.g., the communication device 320-1 has not paid for the service chain, the communication device 320-1 may receive candidate service chains.

[0109] In some embodiments, the communication device 320-1 may receive information on a new charging rate. In other embodiments, the communication device 320-1 may also determine whether a target service chain is acceptable. For example, the communication device 320-1 may determine whether the charging rate in the response is acceptable. If the target service chain is acceptable, the communication device 320-1 may transmit an acknowledgement of the response. In other embodiments, if the target service chain is not acceptable, the communication device 320-1 may transmit another request to the service chain. For example, the another request may include a new acceptable charging rate.

[0110] In some embodiments, an apparatus (e.g., communication device 320) for performing method 700 may include corresponding components for performing the corresponding steps in method 700. These components may be implemented in any suitable manner. For example, it may be implemented by circuitry or software modules.

[0111] In some embodiments, the apparatus includes components for sending a request for a service chain for an application served by the communication device to a NEF device, the service chain including at least one service associated with the application and configured by the NEF device; and components for receiving a response to the request from the NEF device, the response indicating a target service chain, the target service chain being determined based on a profile and the request, the profile including an identification of the application and a service list for the application.

[0112] In some embodiments, the request includes at least one of the following: an identification of the application, information on the service for identifying the service chain, an acceptable charging rate for the service chain, or an identification of at least one service.

[0113] In some embodiments, the apparatus further includes components for receiving a candidate service chain from the NEF device in response to at least one of the following: the profile is updated, a new service is added, or there is no available service chain for the application.

[0114] In some embodiments, the apparatus further includes components for receiving information on a new charging rate from the communication device; and components for determining a new acceptable charging rate based on the information on the new charging rate.

[0115] In some embodiments, the apparatus further includes components for determining whether the target service chain is acceptable; and components for transmitting an acknowledgement of the response in response to the target service chain being acceptable.

[0116] In some embodiments, the apparatus further includes components for determining whether the target service chain is acceptable; and components for transmitting another request for the service chain for the application in response to the target service chain being unacceptable.

[0117] Figure 8FIG. 800 is a flowchart of a method 800 according to an embodiment of the present disclosure. The method 800 may be implemented at any suitable device. For illustrative purposes only, the method 800 is described as being implemented at the NRF device 330.

[0118] At block 810, the NRF device 330 determines at the NRF device whether the profile of the service chain for an application needs to be updated. The profile may include any one or any combination of the following: service NF type, which identifies the type of service provided by the VAS NF, such as firewall, WAN and application acceleration, deep packet inspection (DPI), lawful interception (LI), server load balancing, NAT44, NAT64, NPTv6, HOST_ID injection, HTTP header enrichment function, TCP optimizer, etc.; service NF name, which is another implementation of the VASNF type and is defined by the service NF provider to distinguish the same type of service NF providers of other vendors; service capability information, which indicates the capabilities of the NF in terms of computing capabilities (i.e., CPU, memory, network) and service capabilities, such as the supported protocols; the supported (multiple) applications, which indicate the identities of the applications that can be supported.

[0119] In some embodiments, if there is a state change in the services in the service chain, the NRF device 330 determines that the profile of the service chain for the application needs to be updated. The state change may include the registration of a service. Alternatively or additionally, the state change may include the update of a service. In other embodiments, the state change may further include the deregistration of a service.

[0120] Alternatively or additionally, if there is a state change in the supported applications, the NRF device 330 determines that the profile of the service chain for the application needs to be updated.

[0121] In other embodiments, if an update request is received from a communication device, the NRF device 330 determines that the profile of the service chain for the application needs to be updated. In some embodiments, if a predefined profile template is changed, the NRF device 330 determines that the profile of the service chain for the application needs to be updated.

[0122] In some embodiments, if the NF capabilities exceed a predefined threshold (i.e., meet the service criteria), the service NF should be included in the service chain profile. In another example, if the NF billing rate is lower than a predefined threshold, the service NF should be included in the service chain profile.

[0123] In some embodiments, the service NF list may also be configured based on changes in the application capabilities. For example, if the application supports new capabilities (e.g., virtual reality video), the service NF type list and the mandatory service NF type list may also be changed.

[0124] At block 820, the NRF device 330 updates the profile based on a predetermined profile template. The predetermined profile template can include any one or any combination of the following: an identifier of an application, a list of application capabilities, or a list of services for the application. In some embodiments, if there is no profile, the NRF device 330 can generate a profile based on the predetermined template.

[0125] For the scenario of profile generation, i.e., supporting a new application or other NFs requesting a profile for a new application identifier, the NRF device 330 can fill in the available service NFs based on the profile template and the available service NFs registered on the NRF device 330. Alternatively, if no specific profile template is defined for an application, a default profile template can be used to generate the profile.

[0126] The available service chain function is also included in the profile. Then, the communication device can contact the service chain function to apply the service chain for the requested application.

[0127] For the scenario of profile update, such as service registration, if the newly registered service NF meets the profile template, the NRF device 330 can add the newly registered service NF to the existing profile.

[0128] In some embodiments, the NRF device 330 sends the updated profile to the communication device 320-1. The NRF device 330 can send the updated profile to an NF consumer device (e.g., the NEF device 310) that sends a request for the updated profile. Alternatively, the NRF device 330 can send the updated profile to the NEF device 310 that has previously subscribed to the profile. In some embodiments, upon request of an NF consumer (e.g., the NEF device 310), the NRF device 330 can provide the profile by invoking the NRF discovery service (i.e., Nnrf_NFDiscovery) or a new service dedicated to service change management. Alternatively, the NRF device 330 can notify an NF consumer (e.g., the NEF device 310) that has subscribed to changes in the service chain profile by invoking the NRF NFStatusNotify service or a new service dedicated to service change management.

[0129] In some embodiments, the NRF device 330 can also support implicit service chain information subscription. The NRF device 330 can receive a registration request from the NEF device 310. The registration request can include an identifier of an application. The NRF device 330 can determine that the NEF device 310 subscribes to the profile of the application. The NRF device 330 can transmit a registration response to the NEF device 310. The registration response can include the profile of the application.

[0130] In some embodiments, if the profile is changed / updated, the NRF device 330 may send a notification for notifying that the profile of the service chain has been changed. The notification may also include the updated profile of the service chain. In other embodiments, if the NRF device 330 receives an unsubscribe request from the first device 310, the NRF device 330 may determine that the NEF device 310 unsubscribes from the profile of the application.

[0131] In some embodiments, as described above, the NF consumer device may request a service chain profile and the NRF 330 may determine the next hop based on the service chain profile.

[0132] In other embodiments, the NF consumer device may provide more information in the request (e.g., the service identifier of the application and / or the identifier of the application), and the NRF 330 may directly provide another service as the next hop based on the network information associated with the application. For example, the network information may include the service chain profile it maintains. The network information may include other network information.

[0133] In some embodiments, the NRF 330 may generate and / or update the profile of the application based on a request received from an NF consumer device (e.g., a VAS NF device). The request may include one of the following: a registration request, an unsubscribe request, or an update request. If the NRF 330 receives a registration request from the NF consumer device, the NRF 330 may determine that the NF consumer device is capable of providing services for the application. If the NRF 330 receives an unsubscribe request from the NF consumer device, the NRF 330 may determine that the NF consumer device is no longer capable of providing services for the application. If the NRF 330 receives an update request from the NF consumer device, the NRF 330 may determine that the NF consumer device is updated to provide services for the application. The NRF 330 may generate and / or update the profile based on the request. For example, the NRF 330 may add the NF consumer device as a service provider to the profile. Alternatively, when the NRF 330 unsubscribes from the NRF 330, the NRF 330 may remove the NF consumer device from the profile. In another embodiment, the NRF 330 may update the profile because the NF consumer device is updated.

[0134] In some embodiments, an apparatus (e.g., the NRF device 330) for performing method 800 may include corresponding components for performing the corresponding steps in method 800. These components may be implemented in any suitable manner. For example, it may be implemented by circuitry or software modules.

[0135] In some embodiments, the apparatus includes components for determining, at an NRF device, whether a profile of a service chain for an application needs to be updated, the profile including an identification of the application and a list of services for the application; and components for updating the profile based on a predetermined profile template in response to the profile needing to be updated.

[0136] In some embodiments, the apparatus includes components for transmitting the updated profile to a NEF device associated with the service chain.

[0137] In some embodiments, the components for determining whether the profile needs to be updated include: components for determining that the profile needs to be updated in response to at least one of the following: a change in the state of a service in the service chain, the change in state including at least one of the following: registration of a service, update of a service, deregistration of a service; a change in the state of the supported application; receipt of an update request from a communication device; or the predetermined profile template being changed.

[0138] In some embodiments, the predetermined profile template includes at least one of the following: an identification of the application, a list of application capabilities, or a list of services for the application.

[0139] In some embodiments, the components for sending the updated profile to a communication device include: components for receiving, from the communication device, a request triggering an update of the profile; and components for sending a response to the request, the response including the updated profile.

[0140] In some embodiments, the request includes at least one of the following: a discovery request for the service chain, or a subscription request for the service chain.

[0141] In some embodiments, the components for transmitting the updated profile to a communication device include: components for determining that the communication device is associated with the service chain; and components for sending a response to the request, the response including the updated profile.

[0142] In some embodiments, the apparatus further includes: components for receiving, from another device, a registration request including an identification of the application; components for determining that the other device subscribes to the profile of the application; and components for sending a registration response to the registration request, the registration request including the profile of the application.

[0143] In some embodiments, the apparatus further includes: components for sending a notification indicating that the profile has been updated in response to determining that the profile has been updated.

[0144] In some embodiments, the apparatus further includes: components for receiving, from another device, a deregistration request including an identification of the application; and components for determining that the other device unsubscribes from the profile of the application.

[0145] In some embodiments, the apparatus further includes components for obtaining at least one of the following from a request: an identifier of an application and a service identifier for the application; and components for determining a service for the application based on network information associated with the application.

[0146] In some embodiments, the apparatus further includes: components for receiving another request from another network function (NF) consumer device, the another request including one of the following: a registration request, a deregistration request, or an update request; components for determining, based on the another request, that the another NF consumer device is capable of providing services for another application; and components for generating another profile for the another application based on the another request.

[0147] Figure 9A A schematic diagram showing interactions between devices according to an embodiment of the present disclosure is shown.

[0148] The NEF device 310 sends a request 905 for a profile to the NRF device 330. In some embodiments, the communication device 320-1 may trigger the NEF device 310 to request a profile. For example, the Nnrf_NFDiscovery service operation may be used to support the discovery of service chain related information associated with an application. In some embodiments, the NEF device 310 may send a request of Nnrf_NFDiscovery_Request including an identifier of the application. This request triggers the generation / update of a profile.

[0149] Alternatively, the above process may also be implemented using a new request service operation dedicated to service chain management for the same purpose. For example, in a scenario where the service chain requests are processed from the NEF device 3101, once the NEF device 310 identifies that there is no profile for the application, the service chain discovery process may apply for the generation / update of a profile.

[0150] In other embodiments, NRF service operations (i.e., Nnrf_NFManagement_NFStatusSubscribe, Nnrf_NFManagement_NFStatusNotify, and Nnrf_NFManagement_NFStatusUnsubscribe) may be used to support the subscription / notification of service chain information. It enables the NEF device 310 to subscribe to service chain information based on one or more target application identifiers.

[0151] Alternatively, the above process may also be implemented using a new subscription / notification service operation dedicated to service chain management for the same purpose.

[0152] The NRF device 330 sends 910 a response to the NRF device 330. The response indicates the profile. For example, the profile may be sent to the communication device 310 in the response to the Nnrf_NFDiscovery_Request. In addition to requesting / subscribing to the profile, the enhanced interface may also be used to directly request / subscribe to the serving NF status in the 5G network.

[0153] In order to improve the efficiency of providing dynamic service chain information to the NEF device 310, an implicit service chain information request / subscription mechanism may be used. For example, Figure 9B A schematic diagram illustrating interaction regarding implicit service chain information subscription between devices according to an embodiment of the present disclosure is shown.

[0154] In some embodiments, during NF registration at the NRF device 330, if indicated in the NF profile that service chaining is supported, service chaining processing will also be implicitly triggered on the NRF device 330. The NEF device 310 may send 930 a registration request (e.g., Nnrf_NFManagment_NFRegister_request). The registration request may include an identification of the application. The registration request may also include other parameters of the service chain, such as the service NF type and the service NF name.

[0155] In some embodiments, the NRF device 330 may process the registration request and service chain profile associated with the process. The NRF device 330 may determine 940 that the NEF device 310 subscribes to the profile. The NRF device 330 may send 950 a registration response to the NEF device. The registration response includes the service chain profile. In some embodiments, the application identifier (or other service chain parameters, such as VAS NF type, VAS NF name, etc.) may also be provided in the registration response.

[0156] The NRF device 330 may update 960 the service chain profile. If the subscribed service chain profile is updated, the NRF device 330 may send a notification. In some embodiments, the NEF device 310 may send a deregistration request. The NRF device may determine that the NEF device 310 unsubscribes from the application profile. In this way, the implicit nature of the subscription service chain information is achieved, thereby avoiding the need to send additional signaling.

[0157] Figure 10FIG. 0 is a simplified block diagram of a device 1000 suitable for implementing embodiments of the present disclosure. The device 1000 may be implemented at the NEF device 310. The device 1000 may also be implemented at the communication device 320-1. The device 1000 may also be implemented at the NRF device 330. As shown, the device 1000 includes one or more processors 1010, one or more memories 1020 coupled to the (multiple) processors 1010, and one or more transmitters and / or receivers (TX / RX) 1040 coupled to the processor 1010.

[0158] The processor 1010 may be of any type suitable for the local technical network and, by way of non-limiting example, may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 1000 may have multiple processors, such as an application specific integrated circuit chip that is clocked in time subordinate to a synchronous master processor.

[0159] The memory 1020 may be of any type suitable for the local technical network and may be implemented using any suitable data storage technology, by way of non-limiting example, such as a non-transitory computer-readable storage medium, a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, a fixed memory, and a removable memory.

[0160] The memory 1020 stores at least a portion of the program 1030. The device 1000 may load the program 1030 from a computer-readable medium into the RAM for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, a hard disk, a CD, a DVD, etc. Figure 11 An example of a computer-readable medium 1100 in the form of a CD or DVD is shown. The program 1030 is stored on the computer-readable medium.

[0161] The TX / RX 1040 is for two-way communication. The TX / RX 1040 has at least one antenna to facilitate communication, but in practice the access nodes mentioned in this application may have multiple antennas. The communication interface may represent any interface required to communicate with other network elements.

[0162] It is assumed that the program 1030 includes program instructions that, when executed by the associated processor 1010, enable the device 1000 to operate in accordance with embodiments of the present disclosure, as discussed herein with reference to Figures 4 to 9B That is, the embodiments of the present disclosure may be implemented by computer software executable by the processor 1010 of the device 1000, or by hardware, or by a combination of software and hardware.

[0163] Although this specification contains many specific implementation details, these should not be construed as limitations on any disclosure or on the scope of any claimed invention, but rather as descriptions of features that may be specific to particular embodiments of a particular disclosure. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination within a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented separately or in any suitable sub-combination in multiple embodiments. Moreover, although the above features may be described as acting in certain combinations and even initially claimed as such, one or more claimed features of a combination can be deleted under certain circumstances, and the claimed combination can be directed to a sub-combination or a variation of a sub-combination.

[0164] Similarly, although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Under certain circumstances, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the foregoing embodiments should not be understood as required in all embodiments. It should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0165] When read in conjunction with the accompanying drawings, various modifications and adaptations of the foregoing exemplary embodiments of the present disclosure will be apparent to those of ordinary skill in the relevant art in view of the foregoing description. Any and all such modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure. Moreover, those of ordinary skill in the art to which these embodiments of the present disclosure pertain, having the benefit of the foregoing description and the teachings presented in the related drawings, will be able to conceive of other embodiments of the present disclosure as set forth herein.

[0166] Accordingly, it should be understood that the embodiments of the present disclosure are not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a general and descriptive sense only and not for purposes of limitation.

Claims

1. A Network Exposure Function (NEF) device, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions that, when executed by the at least one processor, cause the NEF device to: receive, from a communication device, a request for a service chain for an application served by the communication device, the service chain including at least one service associated with the application and configured by the NEF device; obtain a profile of the service chain, the profile including an identification of the application and a service list for the application; and dynamically determine a target service chain based on the profile and the request in response to a change in the condition of a network connection.

2. The NEF device according to claim 1, wherein the request includes at least one of the following: the identification of the application, information for identifying the service of the service chain, an acceptable charging rate for the service chain, or the identification of the at least one service.

3. The NEF device according to claim 1, wherein the NEF device is caused to obtain the profile of the service chain by: sending another request for the profile to a Network Repository Function (NRF) device in response to determining that the communication device is authorized to request the service chain; and receiving, from the NRF device, another response to the another request including the profile.

4. The NEF device according to claim 1, wherein the NEF device is caused to determine the target service chain by: determining the target service chain based on a predetermined policy of the service chain, the predetermined policy being obtained from the request; in response to determining that the request is empty, determining the target service chain based on one or more services in the service list of the profile; or in response to determining that the service chain is valid, determining the service chain as the target service chain.

5. The NEF device according to claim 4, wherein the NEF device is caused to determine the target service chain by: determining that the service chain is valid in response to the identification of the at least one service being available; determining that the service chain is valid in response to a charging rate threshold in the profile meeting the acceptable charging rate in the request; or determining that the service chain is valid in response to the at least one service in the request not being lost.

6. The NEF device according to claim 1, wherein the NEF device is further caused to: send the target service chain to the communication device; and send a candidate service chain to the communication device in response to at least one of the following: the profile is updated, a new service is added, there is no available service chain for the application, or the state of the communication device is changed.

7. The NEF device according to claim 1, wherein the NEF device is further caused to: receive dynamic charging information from a Network Repository Function (NRF) device connected to the NEF device; determine a new charging rate for the application based on the dynamic charging information; and send the new charging rate to the communication device in the response.

8. A communication device, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions which, when executed by the at least one processor, cause the communication device to: send a request for a service chain for an application served by the communication device to a Network Exposure Function (NEF) device, the service chain including at least one service associated with the application and configured by the NEF device; and receive, from the NEF device, a response to the request, the response indicating a target service chain that is dynamically determined based on a profile and the request in response to a change in the condition of a network connection, the profile including an identification of the application and a list of services for the application.

9. The communication device according to claim 8, wherein the request includes at least one of the following: the identification of the application, information for identifying the traffic of the service chain, an acceptable charging rate for the service chain, or the identification of the at least one service.

10. The communication device according to claim 8, wherein the communication device is further caused to: receive a candidate service chain from the NEF device in response to at least one of the following: the profile is updated, a new service is added, or there is no available service chain for the application.

11. The communication device according to claim 8, wherein the communication device is further caused to: send an acknowledgement of the response in response to the target service chain being acceptable; or send another request for the service chain of the application in response to the target service chain being unacceptable.

12. A Network Repository Function (NRF) device, comprising: at least one processor; and a memory coupled to the at least one processor, the memory storing instructions which, when executed by the at least one processor, cause the NRF device to: determine that a profile for a service chain for an application needs to be updated, the profile including an identification of the application and a list of services for the application; and in response to determining that the profile needs to be updated, update the profile based on a predetermined profile template, wherein the profile is used to dynamically determine a target service chain for the application in response to a change in the condition of a network connection.

13. The NRF device according to claim 12, wherein the NRF device is caused to determine that the profile needs to be updated by: determining that the profile needs to be updated in response to at least one of the following: a change in the state of a service in the service chain, the state change including at least one of the following: registration of the service, update of the service, deregistration of the service; a change in the state of the supported application; receiving an update request from a Network Function (NF) consumer device; or the predetermined profile template is changed.

14. The NRF device according to claim 12, wherein the predetermined profile template includes at least one of the following: the identification of the application, a list of application capabilities, or a list of services for the application.

15. The NRF device according to claim 12, wherein the NRF device is further caused to send an updated profile to a network function (NF) consumer device by: Receiving a request from the NF consumer device to trigger an update of the profile; and Sending a response to the request, the response including the updated profile.

16. The NRF device according to claim 15, wherein the NRF device is further caused to: Receive a registration request from a network function (NF) consumer device, the registration request including the identification of the application; Determine that the NF consumer device subscribes to the profile of the application; Send a registration response to the registration request, the registration request including the profile of the application; In response to determining that the profile is updated, send a notification for notifying that the profile is updated.

17. The NRF device according to claim 16, wherein the NRF device is further caused to: Receive an unregistration request from the NF consumer device, the registration request including the identification of the application; and Determine that the NF consumer device cancels the subscription to the profile of the application.

18. The NRF device according to claim 15, wherein the NRF device is further caused to: Obtain at least one of the following from the request: the identification of the application and the service identification for the application; and Determine the service for the application based on the network information associated with the application.

19. The NRF device according to claim 12, wherein the NRF device is further caused to: Receive another request from another network function (NF) consumer device, the another request including one of the following: a registration request, an unregistration request, or an update request; Determine based on the another request that the another NF consumer device is capable of providing a service for another application; And Generate another profile of the another application based on the another request.

20. A method for communication, comprising: At a network exposure function (NEF) device, receiving a request for a service chain of an application served by the communication device, the service chain including at least one service associated with the application and configured by the NEF device; Obtaining a profile of the service chain, the profile including the identification of the application and a service list for the application; And In response to a change in the condition of the network connection, dynamically determining a target service chain based on the profile and the request.

21. The method according to claim 20, wherein the request includes at least one of the following: The identification of the application, Information for identifying the service of the service chain, The acceptable charging rate of the service chain, or The identification of the at least one service.

22. The method according to claim 20, wherein obtaining the profile of the service chain includes: In response to determining that the communication device is authorized to request the service chain, sending another request for the profile to a network repository function (NRF) device; And Receiving, from the NRF device, another response to the another request including the profile.

23. The method according to claim 20, wherein determining the target service chain includes: Determining the target service chain based on a predetermined policy of the service chain, the predetermined policy being obtained from the request; In response to determining that the request is empty, determining the target service chain based on one or more services in the service list of the profile, or In response to determining that the service chain is valid, determining the service chain as the target service chain.

24. The method according to claim 23, wherein determining that the service chain is valid includes: Determining that the service chain is valid in response to the identification of the at least one service being available; Determining that the service chain is valid in response to a billing rate threshold in the profile meeting an acceptable billing rate in the request; Or Determining that the service chain is valid in response to none of the at least one service in the request being lost.

25. The method according to claim 20, further comprising: Sending the target service chain to the communication device; And Sending a candidate service chain to the communication device in response to at least one of the following: The profile is updated, A new service is added, There is no available service chain for the application, or The state of the communication device is changed.

26. The method according to claim 20, further comprising: Receiving dynamic billing information from a network repository function (NRF) device connected to the NEF device; Determining a new billing rate for the application based on the dynamic billing information; And Sending the new billing rate to the communication device.

27. A method for communication, comprising: Sending a request for a service chain for an application served by a communication device to a network exposure function (NEF) device, the service chain including at least one service associated with the application and configured by the NEF device; And Receiving, from the NEF device, a response to the request, the response indicating a target service chain that is dynamically determined based on a profile and the request in response to a change in network connection conditions, the profile including an identification of the application and a service list for the application.

28. The method according to claim 27, wherein the request includes at least one of the following: The identification of the application, Information for identifying the service of the service chain, An acceptable billing rate of the service chain, or The identification of the at least one service.

29. The method according to claim 27, further comprising: Receiving a candidate service chain from the NEF device in response to at least one of the following: The profile is updated, A new service is added, or There is no available service chain for the application.

30. The method according to claim 27, further comprising: Sending an acknowledgement of the response in response to the target service chain being acceptable; Or Sending another request for the service chain of the application in response to the target service chain being unacceptable.

31. A method for communication, comprising: At a Network Repository Function (NRF) device, it is determined that a profile for a service chain of an application needs to be updated, the profile including an identification of the application and a list of services for the application; and in response to the profile needing to be updated, updating the profile based on a predetermined profile template, wherein the profile is used to dynamically determine a target service chain for the application in response to a change in the condition of a network connection.

32. The method according to claim 31, wherein determining that the profile needs to be updated includes: determining that the profile needs to be updated in response to at least one of the following: a change in the state of a service in the service chain, the change in state including at least one of the following: registration of the service, update of the service, deregistration of the service; a change in the state of the supported application; receiving an update request from a Network Function (NF) consumer device; or the predetermined profile template being changed.

33. The method according to claim 31, wherein the predetermined profile template includes at least one of the following: the identification of the application, a list of application capabilities, or a list of services for the application.

34. The method according to claim 31, wherein sending the updated profile to a Network Exposure Function (NEF) device includes: receiving, from the NEF device, a request triggering the update of the profile; and sending a response to the request, the response including the updated profile.

35. The method according to claim 31, further comprising: receiving a registration request from a Network Exposure Function (NEF) device, the registration request including the identification of the application; determining that the NEF device subscribes to the profile of the application; sending a registration response to the registration request, the registration request including the profile of the application; in response to determining that the profile is updated, sending a notification for notifying that the profile is updated.

36. The method according to claim 35, further comprising: receiving a deregistration request from the NEF device, the registration request including the identification of the application; and determining that the NEF device cancels the subscription to the profile of the application.

37. The method according to claim 34, wherein the NRF device is further caused to: obtain at least one of the following from the request: the identification of the application and a service identifier for the application; and determine a service for the application based on network information associated with the application.

38. The method according to claim 31, further comprising: receiving another request from another Network Function (NF) consumer device, the another request including one of the following: a registration request, a deregistration request, or an update request; determining, based on the another request, that the another NF consumer device is capable of providing a service for another application; and generating another profile for the another application based on the another request.

39. A computer-readable medium storing instructions that, when executed by at least one processing unit of a machine, cause the machine to execute the method according to any one of claims 20 - 38.

40. A Network Exposure Function (NEF) apparatus, comprising: means for receiving, from a communication apparatus, a request for a service chain for an application served by the communication apparatus, the service chain including at least one service associated with the application and configured by the NEF apparatus; means for obtaining a profile of the service chain, the profile including an identifier of the application and a service list for the application; and means for dynamically determining a target service chain based on the profile and the request in response to a change in a condition of a network connection.

41. A communication apparatus, comprising: means for sending, to a Network Exposure Function (NEF) apparatus, a request for a service chain for an application served by the communication apparatus, the service chain including at least one service associated with the application and configured by the NEF apparatus; and means for receiving, from the NEF apparatus, a response to the request, the response indicating a target service chain that is dynamically determined based on a profile and the request in response to a change in a condition of a network connection, the profile including an identifier of the application and a service list for the application.

42. A Network Repository Function (NRF) apparatus, comprising: means for determining, at the NRF apparatus, that a profile of a service chain for an application needs to be updated, the profile including an identifier of the application and a service list for the application; and means for updating the profile based on a predetermined profile template in response to the profile needing to be updated, wherein the profile is used to dynamically determine a target service chain for the application in response to a change in a condition of a network connection.

Images