System and method for leader election and traffic routing in telecommunication system

Abstract

Systems and methods for dynamic leader election in telecommunications systems (e.g., 3GPP 5G or 6G systems). The dynamic leader election refers to selecting a device from a group of devices as a leader device and routing traffic to the selected leader device. This approach allows the leader election demand to be provided to the system by an external entity.

Description

Technical Field

[0001] This disclosure generally pertains to, for example, the 5th generation (5 th generation (5G) or 6th generation (6G) th Telecommunication systems for generation (6G) systems, particularly systems and methods for leader device election and related traffic routing in these telecommunications systems. Background Technology

[0002] For some applications (e.g., peer-to-peer gaming), and in telecommunications network environments, it may be necessary to route traffic to a leader device within a group of devices (e.g., acting as a game host). This traffic is application-related and is called application traffic. Application traffic originates from or originates from one or more traffic sources (TSs), each of which can be an application server (AS) or a device. In some scenarios, the devices in this group are the TSs that generate at least a portion of the application traffic. The leader needs to be dynamically selected from the group of devices based on several factors, such as device status (e.g., remaining battery power, computing resource availability) and network status (throughput, latency). In different scenarios, the leader is dynamically elected or selected from the group of devices based on these factors (e.g., different devices taking turns acting as game hosts in peer-to-peer games). The device elected as the leader is called the leader device. Given the current shortcomings in this area, there is an urgent need to develop systems and methods for implementing such dynamic leader election in telecommunications systems (e.g., 5G or 6G systems).

[0003] The aforementioned leader election problem can be viewed as a traffic routing problem, where traffic is routed to the selected device. The Third Generation Partnership Project (3GPP) rd The characteristics of how application functions (AFs) in 5G systems, as defined in the 3GPP Generation Partnership Project, influence traffic routing allow AFs to affect the traffic routing decisions of session management functions (SMFs) by providing traffic routing requests. These traffic routing requests are then passed to the policy control function (PCF), which converts them into policies and sends them to the relevant SMFs.

[0004] In 3GPP 5G systems, the impact of Application Request (AF) on traffic routing is limited to traffic routing to the data network (DN), where traffic demand indicates a list of potential application locations to which traffic should be routed. These potential application locations are represented by data network access identifiers (DNAIs), which identify locations that can access the DN. When the Service Provider Function (SMF) selects a user plane path (including user plane function (UPF)) to route traffic, the SMF also selects the DNAI. User plane path selection and DNAI selection can be performed jointly to improve user plane efficiency. However, this feature is not yet applicable to the problem addressed in this invention, which requires routing traffic to devices, rather than to DNAIs (e.g., locations identified by the DNAI).

[0005] Therefore, there is a need for leader election systems and methods that eliminate or mitigate one or more limitations of existing technologies.

[0006] The purpose of providing this background information is to disclose information that the applicant believes may be relevant to this disclosure. It is neither necessary nor appropriate to acknowledge that any of the foregoing information constitutes prior art relative to this invention. Summary of the Invention

[0007] This disclosure provides systems and methods for supporting dynamic leader election within a group of devices. For example, network functions in a 3GPP 5G or 6G network are used to elect a leader from this group. Additionally, data plane path management operations are initiated or performed by these network functions to support interaction with the elected leader.

[0008] The technical effect of the various embodiments is to develop and provide systems and methods for supporting dynamic leader election in telecommunications systems (e.g., 5G or 6G systems). Dynamic leader election refers to selecting a device as a leader device from a set of potential (candidate) devices. Traffic is then routed from other devices (called traffic sources) to the selected leader device, which may be mobile devices, server devices, etc., or combinations thereof. The leader can process the traffic and respond to other devices or additional devices. The traffic may be associated with one or more specific applications.

[0009] According to an embodiment, a method is provided for execution in a communication network. The method includes the following operations performed by a first function, which may be a traffic coordination function (TCF). The method includes receiving one or more policies indicating parameters for leader election of a group of devices. The method includes performing the leader election based on the policies to elect a member of the group of devices as a leader device. The method includes initiating a data plane path management operation to route selected traffic to the leader device.

[0010] In some embodiments, the method includes a second function (which may be a policy control function (PCF)): receiving a request to perform the leader election on the group of devices; and sending one or more policies generated based on the request to the first function. In some embodiments, the request includes traffic information for identifying the selected traffic, for routing the selected traffic to the leader device. In some embodiments, the request includes device information for identifying the group of devices. In some embodiments, the request includes device information for identifying one or more traffic sources that generate the selected traffic. In some embodiments, the request includes a leader election indication indicating that the leader election will be performed. In some embodiments, the request includes traffic source selection information indicating whether all devices indicated by the device information are capable of acting as traffic sources. In some embodiments, the request includes information indicating validity conditions specifying the time, location, or both of the time and location at which the first function will perform the leader election. In some embodiments, the request includes information indicating validity conditions specifying the time, location, or both of the time and location at which the first function will perform the selection of traffic sources. In some embodiments, the leader election indication includes information about whether the leader election will be performed in one iteration or in multiple iterations. In some embodiments, the leader election instruction includes leader election criteria to be followed or considered during the leader election. In some embodiments, the leader election criteria include one or more of the following: computing power, remaining battery power, data availability, and data sufficiency. In some embodiments, the leader election instruction also indicates that the selected traffic will be routed to the leader device. In some embodiments, the group of devices is different from, the same as, or overlaps with the one or more traffic sources.

[0011] In some embodiments, the method further includes: a third function (which may be an application function (AF)) sending the request to the second function.

[0012] In some embodiments, the selected traffic includes data plane traffic from one or more traffic sources. In some embodiments, the selected traffic is identified based on one or a combination of: a source address, a destination address, and one or more port numbers. In some embodiments, the data plane path management operation includes: selecting a data plane path to the leader device, or selecting a data plane path from the traffic sources that generated the selected traffic, or configuring one or more data plane functions to process the selected traffic, or a combination thereof. In some embodiments, the one or more data plane functions include data plane functions operating as data plane anchors (DPAs) of the leader device. In some embodiments, the one or more data plane functions include data plane functions operating as DPAs of one or more of the traffic sources.

[0013] In some embodiments, the method further includes: the first function selecting one or more traffic sources from the set of devices or from another set of devices, the traffic sources being potential sources of the selected traffic.

[0014] In some embodiments, the leader election is performed with at least partial consideration of the current or statistical network state or network conditions, the state of the members of the group of devices, or a combination thereof.

[0015] In some embodiments, the data plane path management operation includes initiating a notification to the member of the group of devices regarding the member being selected as the leader device. In some embodiments, the data plane path management operation includes initiating (e.g., via messaging, which could be a request, command, etc., from TCF to PMF) the operation of a path management function (PMF) to configure one or more data plane functions (DPFs) to detect and process selected traffic and route the selected traffic to the leader device. In some embodiments, the notification regarding the member being selected as the leader device is included in a non-access stratum (NAS) message sent to the member of the group of devices via a radioaccess network (RAN). In some embodiments, the PMF is integrated with the first function.

[0016] In some embodiments, the data plane path management operation includes (e.g., via messaging) initiating a path management function (PMF) to select a data plane (DP) path for routing selected traffic from one or more traffic sources to the leader device, routing traffic from the leader device to the one or more traffic sources, or both. In some embodiments, the method further includes the PMF selecting the DP path.

[0017] In some embodiments, the method includes: after the PMF configures the one or more DPFs, the first function sending (or otherwise initiating) a notification to the leader device regarding data communication expected to involve the selected traffic and be routed to the leader device, regarding the leader device being able to initiate data communication, or regarding both. In some embodiments, the notification is included in a non-access stratum (NAS) message sent to the leader device via a radio access network (RAN).

[0018] In some embodiments, the method includes: after configuring the one or more DPFs, the first function sending (or otherwise initiating) a notification to one or more traffic sources regarding whether the traffic source can now perform data communication conforming to the selected traffic and whether the selected traffic will be routed to the leader device, whether the traffic source can now expect to receive data traffic from the leader device, or both. In some embodiments, the notification is included in one or more non-access stratum (NAS) messages sent to the traffic source via a radio access network (RAN).

[0019] In some embodiments, the method includes: the first function receiving a notification from the leader device that the leader device has been determined to cease acting as the leader device; and in response to the notification that the leader device has been determined to cease acting as the leader device, initiating the next iteration of leader device selection and associated data path management. In some embodiments, the notification is included in a non-access stratum (NAS) message sent to the traffic source via the radio access network (RAN).

[0020] In some embodiments, configuring the DPF includes configuring the DPF to perform destination address translation in packets of selected traffic. The destination address translation facilitates routing the packets to the leader device while masking the leader device's address from the source of the packets in the selected traffic. In some embodiments, configuring the DPF includes configuring the DPF to perform source address translation in packets of return traffic from the leader device. The source address translation facilitates routing the return packets while masking the leader device's address from the destination of the packets in the return traffic. In some embodiments, this configuration is performed based on address translation information indicating the destination address translation, the source address translation, or both, and the address translation information originates from or is received from a second function (e.g., a policy control function (PCF)). In some embodiments, the address translation information indicates one or more network addresses to be translated, and one or more translated network addresses to be translated from the one or more network addresses. The method may also include the DPF performing the destination address translation, the source address translation, or both.

[0021] In some embodiments, configuring the DPF includes configuring the DPF to perform traffic gating to drop traffic originating from devices other than a selected traffic source. This configuration can be performed based on traffic gating information indicating the network address of the device other than the selected traffic source, and the traffic gating information can originate from or be received from a second function (e.g., a policy control function (PCF)). The method may further include the DPF performing such traffic gating.

[0022] In some embodiments, the method includes: initiating a notification to an appropriate member of the group of devices regarding the member being selected as the leader device.

[0023] According to an embodiment, another method is provided for execution in a communication network. The method includes the following operations performed by a first function, such as a traffic coordination function (TCF). The method includes initiating a notification to a device belonging to a group of devices regarding the device being selected as a leader device. The method includes, for example, initiating operations of a path management function (PMF) via messaging to configure one or more data plane functions (DPFs) to detect and process selected traffic and route the selected traffic to the leader device.

[0024] Various embodiments of the above method may be provided, such as those described above with respect to the first method, or those described elsewhere herein.

[0025] According to an embodiment, a first function is provided, such as a traffic coordination function (TCF) in a communication network. The first function includes processing electronics and network interfaces. Here and elsewhere, the function may include hardware resources, such as processing electronics and network interfaces, because the function is instantiated using such hardware resources. The first function is used to receive one or more policies indicating parameters for leader election of a group of devices. The first function is used to perform the leader election to elect a member of the group of devices as a leader device based on the policies. The first function is used (e.g., after the leader election) to initiate a data plane path management operation to route selected traffic to the leader device.

[0026] According to an embodiment, a system in a communication network is provided, including the first function described above and one or more additional functions. Different functions can be instantiated using the same or different hardware resources. The additional functions may include a second function (e.g., a policy control function (PCF)) for receiving a request to perform the leader election on the group of devices and sending the one or more policies generated based on the request to the first function. The additional functions may include a third function, such as an application function (AF), for sending the request to the second function. The additional functions may include a path management function (PMF). The data plane path management operation may include, for example, initiating a path management function (PMF) operation via messaging to select a data plane (DP) path for routing the selected traffic from one or more traffic sources to the leader device, routing traffic from the leader device to the one or more traffic sources, or both. Furthermore, the PMF may be used to select the DP path.

[0027] The additional functionality may include one or more data plane functions (DPFs). The data plane path management operation may include initiating a notification to the members of the group of devices regarding the selection of the member as the leader device. The data plane path management operation may include, for example, initiating a path management function (PMF) via messaging to configure the one or more data plane functions (DPFs) to detect and process selected traffic and route the selected traffic to the leader device. The DPF may be used to perform address translation, traffic gating, or both.

[0028] According to an embodiment, a first function in a communication network, such as a traffic coordination function (TCF), is provided, including processing electronics and network interfaces. The first function is used to initiate notifications to devices belonging to a group of devices regarding the selection of said device as a leader device. The first function is also used to initiate the operation of a path management function (PMF) to configure one or more data plane functions (DPFs) to detect and process selected traffic and route said selected traffic to the leader device.

[0029] According to an embodiment, a system in a communication network is provided, including the first function described above and one or more additional functions. The additional functions may include the PMF, wherein the PMF is used to select the DP path. The additional functions may include the DPF, wherein configuring the DPF includes configuring the DPF to perform address translation, traffic gating, or both, wherein the DPF is used to perform address translation, traffic gating, or both.

[0030] Other aspects of the above-described functions and systems can be provided, such as those similar to those aspects of the methods described above.

[0031] According to an embodiment, an electronic device in a communication network is provided, the device including a processor, a network interface, and a memory, and for performing one or more of the methods described herein. According to an embodiment, a system of such electronic devices is provided, which are networked together and used to interact to perform one or more of the methods described herein.

[0032] According to embodiments of this disclosure, a computer program product is provided, including (e.g., a non-transitory) computer-readable medium storing statements and instructions that, when executed by one or more computer processors, cause the computer processors to perform the methods described above. The computer processor may be part of one or more electronic devices (e.g., network entities) as described herein.

[0033] Embodiments have been described above in conjunction with aspects of the present invention, and these embodiments can be implemented based on these aspects. Those skilled in the art will understand that embodiments can be implemented in conjunction with the aspects described therein, but may also be implemented together with other embodiments of that aspect. It will be apparent to those skilled in the art that embodiments are mutually exclusive or incompatible. Some embodiments may be described in conjunction with one aspect, but may also be applicable to other aspects, as will be apparent to those skilled in the art. Attached Figure Description

[0034] Further features and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, wherein:

[0035] Figure 1 A system including various networking functions and networking devices according to embodiments of the present disclosure is shown.

[0036] Figure 2 A set of devices, data plane functions, traffic sources, and leader devices are shown according to exemplary embodiments of the present disclosure.

[0037] Figure 3 The operation of various network functions related to AF requests according to embodiments of this disclosure is illustrated.

[0038] Figure 4 Various network functions and devices are illustrated to implement embodiments of this disclosure.

[0039] Figure 5 An electronic device that can be used to perform operations according to an embodiment of the present disclosure is shown.

[0040] It should be noted that similar features are identified by similar reference numerals throughout the accompanying drawings. Detailed Implementation

[0041] This disclosure relates to dynamic leader election among a group of devices. This may be applicable to scenarios involving peer-to-peer traffic between devices, such as supporting a specific application (e.g., peer-to-peer gaming). Traffic can be associated with the application and explicitly indicated in its data packets (e.g., by including a specific network address as the destination address). In some such applications, a leader device exists that receives traffic from other devices and can also send traffic to other devices. For example, the devices can be wireless terminal devices, such as user equipment (UE), M2M devices, MTC devices, IoT devices, servers, network functions, etc.

[0042] As used herein, the term "leader" refers to a role that can be assigned to the first device in a group of devices so that the first device is selected or elected as the leader. Once the first device is assigned the leader role, the first device becomes the leader device. Therefore, the device is referred to as being selected as the leader or elected as the leader. The leader role can then be moved from the first device to a second device in the group of devices so that the second device becomes the leader device, and the first device ceases to be the leader device.

[0043] Leader election can refer to the process of electing a device as a leader (i.e., selecting a device as the leader). It can also be considered the process of assigning a leader role to a device, making that device the leader device. Leader election can be performed on a group of devices. Accordingly, a device in that group is elected (selected) as the leader, i.e., assigned the leader role. The leader role can move among devices in that group, allowing the leader device to change dynamically.

[0044] For ease of description, various illustrative embodiments in which a single group of devices exists are given. A leader device is selected from this group of devices, and the leader device receives traffic from some traffic sources. Traffic sources are generally also considered to belong to the same group of devices, i.e., other devices in the same group. However, other embodiments are also considered. For example, the leader device may be selected from a first group of devices (referred to as a potential leader or equivalent candidate leader), while traffic sources or other associated devices may belong to a second group of devices (referred to as candidate traffic sources) or be selected from the second group of devices. Traffic sources may be called potential traffic sources because they may generate traffic, but they do not necessarily generate traffic, even if they are selected from a group of candidate traffic sources. The first group of devices (where members are candidate leaders) and the second group of devices (where members are candidate traffic sources) may be the same (completely identical), different (independent of each other), overlapping (have one or more common members), or non-overlapping (have no common members). Traffic sources may be selected from the second group of devices.

[0045] In various embodiments, the leader device receives traffic from a traffic source. The leader device is selected from the first group of devices as described above. According to various embodiments, the traffic is application-associated or related, and the leader device acts as an application server associated with the application and processes the traffic. The traffic may include information indicating application association, for example, by including a specific network address as a destination address (and possibly a specific port number as a destination port) in its data packets, and may be identified or detected accordingly in other traffic. The first group of devices can be considered as potential (or candidate) locations for the application, i.e., potential locations where the application server associated with the application is located, or simply, potential application servers associated with the application.

[0046] According to various embodiments, an application function (AF) can request to perform a leader election by sending an AF request. The AF request includes a leader election requirement. The AF request is sent to the policy control function (PCF), which translates the request into a policy to be followed (i.e., generates a policy based on the request). The PCF sends the generated policy to the traffic coordination function (TCF), which accordingly elects a leader (e.g., selects a leader device). The TCF instructs the path management function (PMF) to route traffic to the leader (leader device). The PMF accordingly selects and configures data plane paths. Leader election can be performed in multiple iterations, such as periodically or intermittently. The TCF can receive notifications from the current leader device, based on which it determines whether the current iteration of leader election is complete, whether to begin the next iteration of leader election, or both. Although the terms "TCF," "PCF," "AF," etc., are used herein for clarity, it should be understood that these names can be changed and these functions can be replaced by equivalent functions. Thus, TCF can be a first function, PCF can be a second function, AF can be a third function, and so on.

[0047] The PMF configures the leader device's anchor data plane function (DPF), also known as the data plane anchor (DPA), to route traffic destined for the leader to the leader device. The PMF also configures one or more anchor DPFs (also known as one or more DPAs) for other (non-leader) devices (in other words, traffic sources), such that traffic originating from those other devices and destined for the leader is routed to the leader device's anchor DPF. A device's DPA (such as the leader or non-leader device described above) can be associated with that device's session (e.g., a PDU session in a 5G system) used to transport traffic. In this case, the DPA is session-specific and is also called a session anchor (e.g., a PDU session anchor (PSA) in a 5G system). The leader device's DPA routes traffic (i.e., traffic destined for the leader) to the leader device along the data plane (DP) path connecting the leader device and its DPA. As described above, when the leader device's DPA is associated with the leader device's session, the DP path is associated with that session. It should be noted that "leader" is a role, and the leader role can be assigned to the first device (in other words, the first device is selected or elected as the leader). Once the first device is assigned the leader role, the first device becomes the leader device. The leader role can then be moved from the first device to the second device, making the second device the leader device, and the first device ceases to be the leader device.

[0048] In various embodiments, after the TCF makes a leader election decision, that is, selects a device as the leader, the TCF notifies the device of the leader election decision. In other words, the TCF notifies the device that it has been elected as the leader.

[0049] The PCF generates policies based on the AF request. These policies include information identifying the traffic and information about the traffic routing requirements. The PCF sends the policies to the TCF, which serves the devices associated with the identified traffic (e.g., generating / originating from or receiving it). The TCF performs leader election in one or more iterations based on these policies. In each iteration, the TCF selects a device as the leader from a set of devices (i.e., candidate leaders, which may include some or all of the devices associated with the identified traffic) and performs actions such as... Figure 4 The data plane path (re)selection process is shown in the diagram.

[0050] Figure 1A system provided according to an embodiment of this disclosure is illustrated. The system includes a device 105 (e.g., a UE), a radio access network (RAN) 110, a core network (CN), and a DN 114. The CN includes a control plane and a data plane. The control plane includes the following control plane functions: NEF 120, PCF 122, NSF 124, TCF 126, and PMF 128. The data plane includes a data plane function (DPF) 130. In some embodiments, such as when the system is a 3GPP 5G system, the data plane is referred to as the user plane. DN 114 includes an application server (AS) 132. The system also includes an application function (AF) 134. The AF 134 interacts with the control plane of the CN to access or provide services. In some embodiments, such as when the AF 134 is located in a trust domain, the AF 134 is allowed to interact directly with the relevant control plane functions (e.g., NSF 124, PCF 122). In some embodiments, for example, when AF 134 is not located in the trust domain, AF 134 is not allowed to interact directly with the control plane functions, but interacts indirectly with the control plane functions through NEF 120.

[0051] According to various embodiments, the following description Figure 1 Further details on the various components (such as functions).

[0052] NEF 120 can perform functions such as, but not limited to, the disclosure of network information, analytics, capabilities, and events; secure configuration of information from external applications (e.g., AF) to the system; and internal-to-external information conversion. In some embodiments, NEF corresponds to the NEF in a 3GPP 5G system.

[0053] PCF 122 may perform functions such as, but not limited to, supporting a unified policy framework to manage network behavior, making policy decisions and providing the resulting policy rules to one or more control plane functions for enforcement, and accessing subscription information and application data related to policy decisions in one or more network storage functions (e.g., NSF). In some embodiments, this policy control function (PCF) corresponds to the PCF in a 3GPP 5G system. In some embodiments, the PCF may correspond to an aspect of the 5G PCF.

[0054] NSF 135 can implement functions such as, but not limited to, the storage and retrieval of subscription data, the storage and retrieval of policy data, the storage and retrieval of structured data for public disclosure, the storage and retrieval of application data (including packet flow descriptions (PFDs) for application detection, information associated with AF requests, and device group information for group management), and so on. In some embodiments, NSF corresponds to the unified data repository (UDR) in the 3GPP 5G system. In some embodiments, NSF may correspond to an aspect of the 5G UDR.

[0055] TCF 126 makes traffic routing decisions and coordinates traffic routes, as described elsewhere in this document. In some embodiments, TCF is integrated with PMF 128. In some embodiments, TCF is integrated with PCF 122. For example, the integrated functions may be the same entity. In some embodiments, TCF is a separate network function, distinct from PMF 128 and PCF 122. TCF interacts with device 105 through interface 126a, shown by dashed lines. Interface 126a can be considered a non-access stratum (NAS) interface. Interface 126a is connected to RAN 110. In some embodiments, interface 126a is also connected to one or more other network functions, such as PMF, AMF in a 3GPP 5G system, or a combination thereof.

[0056] PMF 128 can perform functions such as, but not limited to, selecting and controlling the DPF, maintaining / configuring data plane topology or paths, establishing and releasing data plane tunnels, configuring traffic forwarding at the DPF to apply local switching or packet forwarding, configuring traffic steering at the DPF to route traffic to appropriate destinations, etc. PMF configures DPF 130 via the T4 interface shown. In some embodiments, PMF corresponds to the session management function (SMF) in a 3GPP 5G system. PMF interacts with the device via the interface shown by dashed line 128a. Interface 128a can be considered a non-access stratum (NAS) interface. Interface 128a is connected to the RAN. In some embodiments, interface 128a is also connected to another network function, such as the AMF in a 3GPP 5G system. Figure 1 (Not shown in the image). This other network function is located between the RAN and PMF. In some embodiments, the PMF may correspond to one aspect of the 5G SMF.

[0057] DPF 130 can perform functions such as, but not limited to, acting as an interconnection point for DN 114, acting as an anchor point for device 105 in DP, routing / forwarding packets, enforcing policy rules (e.g., traffic gating, redirection, flow control), performing traffic marking in uplink and downlink, performing packet buffering and data notification triggering, and performing packet detection (e.g., application detection). In some embodiments, the data plane corresponds to the user plane of a 3GPP 5G system, and the DPF corresponds to the UPF (User Plane Function) in a 3GPP 5G system.

[0058] As described above, control plane functions and DPFs can be logical network functions; each of them can be instantiated at one or more network locations, resulting in one or more instances. When the RAN implements the functionality of a logical network function (either a control plane function or a DPF), the logical network function is considered to be instantiated at a RAN node. A network location can refer to a data center or a RAN node. There may be more than one instance of a logical network function at the same network location. In the various embodiments disclosed in this invention, selecting or reselecting a logical network function corresponds to selecting or reselecting an instance of a network function.

[0059] Device 105 is connected to the CN via RAN 110. The device is served by RAN nodes in the RAN, meaning it has a radio connection to the RAN nodes. The device's serving RAN node is connected to a DPF (actually an instance of a DPF) via a data plane (DP) path. An instance of a DPF is the device's anchor point in the data plane and can be called a DPA. The data plane path is associated with device 105; the data plane path includes the serving RAN node, the DPA, and one or more other instances of the DPF, if possible. When other DPF instances are included in the data plane path, they are positioned along the data plane path between the serving RAN node and the DPA, connecting the serving RAN node and the DPA. The serving RAN node is connected to the DPF instances in the data plane path via a T3 interface. Two adjacent DPF instances in the data plane path are connected via a T9 interface.

[0060] DN 114 can be a physical DN (including one or more application servers, such as AS 132, or associated with it), with the DPA connected to the DN via a T6 interface. DN 114 can also be a virtual DN (e.g., it does not include or is not associated with any application server). DN 114 can correspond to an application or application scenario, and the DNN can be used to identify the application or application scenario.

[0061] Specific embodiments of this disclosure will now be described. In this embodiment, when implementing an application, traffic (also known as data traffic) is routed to a leader in a group of devices. This traffic is application-related and is referred to as application traffic. Application traffic originates from or is sent from one or more traffic sources (TSs), each of which may be an application server (AS) or a device. In some embodiments, a device in this group (or another group of devices) is a TS that generates at least a portion of the application traffic.

[0062] Leader selection can be performed based on requests from the AF associated with the application, as described below.

[0063] Each device in this group is associated with a data plane path used to transmit application traffic. This data plane path can be associated with a session of the corresponding device (e.g., a PDU session in a 5G system). If a device is elected leader, application traffic is routed to that device's DPA and then transmitted to that device along the associated data plane path. If the device is not elected leader, it can generate at least a portion of the application traffic, and this portion of the application traffic is transmitted along the associated data plane path to that device's DPA, and then routed or forwarded from that device's DPA to the leader device's DPA.

[0064] Figure 2 This embodiment illustrates a group of four devices (device 1 202, device 2 204, device 3 206, and device 4 208) and their associated data plane paths 212, 214, 216, and 218. Data plane paths 212 and 214 associated with devices 1 202 and 204 share DPF1 222 as a DPA. Data paths 216 and 218 associated with devices 3 206 and 4 208 share DPF2 224 as a DPA. Device 1 202 is elected as the leader. Figure 2As shown, each of Device 2 204, Device 3 206, and Device 4 208 can act as a TS, generating at least a portion of the application traffic. AS 132 in DN 114 can also act as a TS and generate at least a portion of the application traffic. Therefore, data traffic (e.g., application traffic) can be routed from one, some, or all of Device 2 204, Device 3 206, Device 4 208, and AS 132 to Leader Device 202. The application traffic generated by Device 3 206 and Device 4 208 is routed to DPF2 224 along their data plane paths 216 and 218, respectively. DPF2 224 forwards / routes application traffic to DPF1 222 (i.e., the DPA of the Leader Device). As the DPA of Device 1, DPF1 222 also receives application traffic generated from Device 2 204. DPF1 222 sends application traffic received from device 2 204 and application traffic received from DPF2 224 along data plane path 212 of device 1 to device 1 202.

[0065] Equipment (e.g., Figure 2 The data plane path of device 1, device 2, device 3, or device 4 in a 3GPP 5G system can be associated with the device's session (e.g., a PDU session in a 3GPP 5G system), and the data plane path can be selected and configured during session establishment. A device can request to establish a session by sending a session establishment request to the system (e.g., to the TCF or PMF). The session establishment request may include information identifying the device, information identifying the DN (e.g., DNN), network slice information (which can be used to select a network slice), etc. If the request is sent to the TCF, the TCF may send at least some of the information in the request to the PMF so that the PMF can establish a data plane path. If the request is sent to the PMF, the PMF may send at least some of the information in the request to the TCF so that the TCF takes the device into account when performing traffic coordination related to the DN, network slice, or a combination thereof. The session is associated with an application. The application can be identified by information identifying the DN, network slice information, or a combination thereof.

[0066] Devices in a group of devices (e.g., the group of devices described above) can access an application through the device's data plane path and send or receive application-related traffic (i.e., a portion of the application traffic described above) along the data plane path. The data plane path includes data plane functions that act as the device's data plane anchor (DPA). The data plane path is managed by a path management function (PMF) and, as described above, can be associated with a device's session, which is associated with an application. The device is considered to be served by the application's PMF, which is referred to as the application's device-serving PMF. Similarly, the session is considered to be served by a PMF, which is referred to as the session's serving PMF. Another device in the group of devices or a session of another device may also be served by a PMF, or by a different PMF of the application. In some embodiments, all devices in the group are served by a PMF.

[0067] When the TCF and PMF are not integrated, the PMF can notify the TCF that it is serving a device for the application, or a session for the device associated with the application. The PMF can notify the TCF of this by sending a message to the TCF containing information identifying the device, the session, and the application. In some embodiments, the relationship between the PMF and the device, i.e., the device for which the PMF is serving the application, is maintained in the network binding function (NBF). The NBF can store a mapping between devices (e.g., identified by a device ID) and the PMFs (e.g., identified by an application ID) of the application (e.g., identified by an application ID). In some embodiments, the relationship between the PMF and the device's session, i.e., the session for which the PMF is serving the session, is maintained in the NBF. The NBF can store a mapping between sessions (e.g., identified by a session ID) and PMFs (e.g., identified by a PMF ID). The NBF can also store an application ID that identifies the application associated with the session. In some embodiments, the application ID is in the form of a DNN, a network slice ID, or a combination thereof. TCF can subscribe to the mappings of applications received from NBF (i.e., mappings between devices and PMFs or between sessions and PMFs, as described above).

[0068] The embodiments provide configurations for leader election requirements, for example, as described below and as follows. Figure 3As shown above, the AF can request a leader election for the group of devices, where a device is elected (in other words, selected) as the leader of the group, causing application traffic to be routed to the leader device through the data plane. Leader election can be performed in one or more iterations. In each iteration, a device is selected from the group as the current leader, and application traffic is routed to the leader device. Different devices may be selected as leaders in different iterations. Accordingly, the corresponding leader device may be different at different times, and therefore application traffic will be routed to different devices at different times. Different iterations can be performed sequentially, one after another. Leader election can be performed by the traffic coordination function (TCF).

[0069] When AF requests a leader election, it sends (e.g.) Figure 3 Operation 301) in the process is called an AF request. An AF request may include some or all of the following information: traffic information, device information, leader election instructions, traffic source selection information, and information about validity conditions. This information may be described as follows.

[0070] Traffic information identifies application traffic and, in some embodiments, identifies the application. Traffic information may include a DNN and possible network slice information (which can be used to select network slices), or an AF-Service-Identifier (AF-Service-Identifier, i.e., an identifier of the service represented by the AF in issuing a request). When the AF-Service-Identifier is included in the traffic information, the AF-Service-Identifier is mapped, for example, by the NEF to the target DNN and possible network slice information. When the NEF processes an AF request, it can use the AF-Service-Identifier to authorize the AF request. Traffic information may include application identifiers or traffic filtering information (e.g., IP 5 tuples). Application identifiers identify, reference, or correspond to an application (processing DP traffic) and can be used by the DPF to detect application traffic. Traffic information can be used to identify selected traffic so that selected traffic (e.g., data plane traffic) is routed to the leader device. Selected traffic is traffic determined to be suitable for routing to the leader device and may be associated with an application being supported. In various embodiments, selected traffic may be identified based on one or a combination of: source address, destination address, and one or more port numbers. For example, based on... Figure 4 Operation 409: Select traffic for transmission.

[0071] Device information identifies a first group of devices. Device information may also identify a second group of devices. The first group includes candidate leaders, i.e., devices that can be selected as leaders. The second group includes candidate traffic sources, i.e., devices that can be selected as traffic sources. Application traffic originating from devices selected as traffic sources is authorized traffic and will be routed to the leader. Application traffic originating from devices not selected as traffic sources is unauthorized and will not be routed to the leader (e.g., it will be dropped). In various embodiments, the first and second groups of devices can be identical (completely identical), different (not completely identical), overlapping (having one or more common members), or non-overlapping (independent of each other, with no common members).

[0072] In some embodiments, a first group of devices (i.e., candidate leaders) is considered and identified as potential (or candidate) locations for the application, and a second group of devices (i.e., candidate traffic sources) is considered and identified as devices from which their traffic will be routed (here, traffic refers to application traffic identified in the traffic information). Device information includes information identifying the first group of devices and information identifying the second group of devices.

[0073] Each of some or all devices in a group of devices identified in the device information (whether it's the first group or the second group) can be identified as a corresponding individual device. Individual devices can be identified using device IDs or addresses (e.g., IP address / prefix, MAC address). Some or all devices in this group can be identified together as a device group. Device groups can be identified using group IDs. This group of devices can include any device accessing the application. Therefore, for this group of devices (e.g., the first group of devices or the second group of devices), the device information (more specifically, the information identifying the group of devices in the device information) can include a list of one or more device IDs, a list of one or more addresses, a list of one or more group IDs, and information indicating any device accessing the application (e.g., a special group ID or a special device ID). The device IDs or group IDs in the device information can be external IDs, i.e., external device IDs or external group IDs, in which case, when NEF processes an AF request, NEF can map them to internal IDs, i.e., internal device IDs or internal group IDs. In some embodiments, for a device or group of devices identified in the device information, the device information may indicate that the device or group of devices (i.e., any device in the device group) is a candidate leader or a candidate traffic source or both (i.e., belongs to a first group, a second group, or both groups).

[0074] The leader election instruction instructs that a device (e.g., as the leader) should be selected from the candidate leaders identified in the device information, and that application traffic identified in the traffic information and belonging to the traffic source should be routed to the selected device (i.e., the leader device). In some embodiments, the leader election instruction is considered or regarded as a traffic routing requirement. In some embodiments, when a candidate leader is considered a potential location for an application, leader election may refer to the selection of a public application location, and the leader election instruction implies that a public application location (i.e., the leader device) should be selected from the potential locations of the application (i.e., the candidate leader) of the traffic source so that the application traffic of the traffic source is routed to the public application location. The traffic sources mentioned above include some or all of the candidate traffic sources identified in the device information and may be determined as a result of the traffic source selection described below (e.g., with...). Figure 3 (Association in operation 303.2). The leader election instruction may include information indicating whether a leader election should (will) be performed in one or more iterations. This information may also indicate the number of iterations / times in which a leader election should be performed, which is an integer value not less than 1 (e.g., equal to or greater than 1). This information may be optional and may be omitted in some embodiments. When this information is not present in the leader election instruction, it may imply that the number of iterations / times is set to a predetermined default value, such as 1.

[0075] The leader election instruction may include information about leader election criteria. This information may specify factors that should be followed or considered when electing a leader (i.e., selecting a leader device). For example, the information may specify the type of device the leader should be. Or, for example, the information may specify the minimum capabilities the leader should possess (e.g., in terms of computing power, remaining battery power, data availability, or sufficiency). Or, for example, the information may specify the location the leader should be in (e.g., one or more location areas). This information may specify one or more such factors. In some embodiments, the information specifies the device to be elected as leader by including information identifying the device (e.g., device ID, network address). Among the candidate leaders identified in the device information, the eligible device specified in that information can be elected as leader. The information about leader election criteria may specify how long or with what probability an eligible device can be elected as leader. In some embodiments, the information about leader election criteria specifies that each eligible device is equally likely to be elected as leader. When leader election is performed over multiple iterations, the information about leader election criteria may be for all iterations or for each iteration, and should be followed or considered in the corresponding leader election iteration. The information about leader election criteria is optional.

[0076] Traffic source selection information may include traffic source selection requirements that indicate how to select devices as traffic sources from candidate traffic sources identified in the device information. Traffic source selection requirements may specify a minimum, maximum, or exact number of devices to be selected as traffic sources. Traffic source selection requirements may specify a threshold (or range) at which the total amount of data available at the selected traffic source should or should not be lower than or higher than the threshold (or range) (or within the threshold (or range)). Traffic source selection information may also indicate whether a traffic source needs to be reselected in each iteration of leader election. Traffic source selection information may indicate that all candidate traffic sources identified in the device information should be selected as traffic sources. Traffic source selection information may be optional and may be omitted in some embodiments. In various embodiments, if this information is absent (i.e., not present), it may imply, for example, that all candidate traffic sources identified in the device information should be selected as traffic sources. When it is indicated that all candidate traffic sources should be selected as traffic sources (e.g., as indicated in the traffic source selection information or as implied by the absence of the traffic source selection information), traffic source selection (e.g., Figure 3 Operation 303.2 in the text can be considered as not being executed, or equivalently, executed by simply selecting all candidate traffic sources.

[0077] In various embodiments, the TCF selects (e.g., based on traffic source selection information) Figure 3 In operation 303.2), one or more devices from the candidate traffic sources identified in the device information are selected as traffic sources. The DPF performs traffic gating to drop application traffic originating from any device not selected as a traffic source. Selecting one or more devices as traffic sources may require compliance with traffic source selection requirements. In various embodiments, if no candidate traffic sources are identified in the device information, the TCF will not select a traffic source (e.g., it will not perform...). Figure 3 (Operation 303.2 in the code), and DPF will not perform flow gating.

[0078] Information regarding one or more validity conditions specifies the conditions under which a leader election will be performed (e.g., when, where, or both). This information may include information regarding temporal validity conditions, spatial validity conditions, or both. Information regarding temporal validity conditions specifies when a leader election should be performed by specifying one or more time intervals or one or more durations. Information regarding spatial validity conditions may specify one or more valid regions where a leader election should be performed. For example, this information may indicate that a leader election should be performed only for devices located within one or more specified valid regions; that is, a leader device should be selected from candidate leaders identified by the device information and located within one or more specified valid regions. Valid regions in the spatial validity condition information can be represented by region IDs, which the NEF can map to one or more cell IDs when processing an AF request. The TCF can perform the election, for example, based on the leader election instruction and one or more validity conditions specified in the information regarding one or more validity conditions (e.g., ...). Figure 3 Operation 303.1) Selection of the leader device.

[0079] Similarly, information regarding the conditions under which traffic source selection will be performed can also be specified. This information can be included in information regarding validity conditions or elsewhere. This information can be included in AF requests (e.g., the AF request described above), policies generated by PCF, etc., or combinations thereof. Information regarding the conditions under which traffic source selection will be performed can, for example, specify when traffic source selection should be performed by specifying a time interval. Information regarding the conditions under which traffic source selection will be performed can, for example, specify where traffic source selection should be performed by specifying the spatial location or region where candidate traffic sources should be located to qualify as candidates. Such regions can be represented using region IDs. Typically, the above information can be referred to as information indicating validity conditions that specify (e.g., TCF) the time, location, or both of time and location for performing traffic source selection.

[0080] Figure 3 The operation of AF, PCF, and TCF in relation to an AF request is illustrated according to embodiments of this disclosure. An AF request may be a request to perform a leader election on a group of devices in order to route relevant traffic to the leader device via the data plane.

[0081] In operation 301, the AF sends a request from AF 134 to PCF 122. In some embodiments, the AF request is sent directly or indirectly (e.g., via NEF 120) to the PCF. When the AF is in a trusted domain, or when direct interaction between the AF and the PCF is permitted, the AF request can be sent directly to the PCF without the involvement of the NEF. When the AF is not in a trusted domain, or when direct interaction between the AF and the PCF is not permitted, the AF can be sent to the PCF via the NEF. That is, the AF sends the AF request to the NEF, and the NEF then sends the AF request to the PCF. Before sending the AF request to the PCF, the NEF can perform information mapping such that when the AF request is sent to the PCF, the AF request includes mapped information (i.e., information mapped from the information in the AF request received by the NEF from the AF). The AF request may be a request to perform leader election for a group of devices.

[0082] In some embodiments, the AF request is sent to NSF 135 (directly or via NEF 120), and NSF stores the AF request as application data. PCF 122 receives application-related data from an NSF subscription. NSF provides the AF request to PCF based on the subscription. In some embodiments, PCF performs a subscription when it receives a request for an application-related policy (e.g., from TCF). In some embodiments, AF sends the AF request to NEF 120, and NEF sends the AF request to NSF. Before sending the AF request to PCF, NEF may perform information mapping such that when the AF request is sent to NSF, the AF request includes mapped information (i.e., information mapped from the information in the AF request received by NEF from AF).

[0083] When NEF 120 is involved in the transmission of an AF request from AF to PCF as described above, NEF can process the AF request before sending it to the next network entity (e.g., PCF 122 or NSF 135). When processing the AF request, NEF can perform information mapping, whereby NEF replaces or updates portions of the information in the AF request with mapped information so that the next network entity receives the AF request with the mapped information. For example, NEF can map the AF-Service-Identifier to the DNN and possible network slice information, map external IDs to internal IDs, and map area IDs to cell IDs, as described above.

[0084] Upon receiving an AF request, PCF 122 generates one or more policies based on (or according to) the AF request. These policies may include traffic information, device information, leader election instructions, traffic source selection information, information regarding one or more validity conditions, or a combination thereof. In operation 302, PCF provides (sends) one or more policies to TCF 126. The one or more policies indicate parameters for leader election of a group of devices.

[0085] According to one or more policies, TCF 126 coordinates traffic routing for devices identified in the device information, as shown in operation 303. Alternatively, operation 303 may be referred to as performing a leader election to elect a member of a group of devices as the leader device. Leader election 303 includes sub-operation 303.1, which relates to selecting the leader device. Leader election may also include sub-operation 303.2, which relates to selecting a traffic source. Leader election may also include sub-operation 303.3, which relates to managing the data plane path. In various embodiments, sub-operations 303.2, 303.3, or both may be optional or may be omitted.

[0086] In Operation 303.1, TCF 126 selects a leader device; that is, the TCF selects a device as the leader from the candidate leaders identified in the device information. For example, the TCF identifies one or more eligible devices among the candidate leaders based on leader election instructions (e.g., more specifically, information about leader election criteria). There may be one or more eligible devices. Among the one or more eligible devices, the TCF selects one device as the leader. The selected device is called the leader device.

[0087] In operation 303.2, TCF 126 selects a traffic source. The TCF can select some or all of the candidate traffic sources identified in the device information as traffic sources. In some embodiments, if a device is both a candidate leader and a candidate traffic source identified in the device information, and if the device is selected as the leader by the TCF, the TCF may not select that device as a traffic source.

[0088] When selecting a leader device (Operation 303.1) and / or when selecting a traffic source (Operation 303.2), the TCF may consider network conditions (e.g., throughput, latency) and device conditions (e.g., energy levels, computing power levels, availability or sufficiency of application-related data) to optimize network and device performance. For example, this may include operations to avoid network congestion (e.g., network locations such as DPFs with low throughput) and balance energy consumption on devices. The TCF may obtain (receive) information about current or statistical network conditions (e.g., throughput and / or packet latency at individual DPFs) from network functions (e.g., NWDAF in 3GPP 5G systems) and consider this information when performing leader election. The TCF may obtain (receive) information about device conditions from individual devices, such as information about their status provided by each device when requesting session establishment and periodically updating its status, and consider this information when performing the selection of a leader device and / or traffic source. The TCF may obtain or receive network conditions and consider this information when performing the selection of a leader device and / or traffic source.

[0089] In Operation 303.3, the TCF manages the data plane paths used for the leader device (selected in Operation 303.1) and traffic sources (selected in Operation 303.2). Management enables application traffic to be routed to the leader device, and during traffic routing, address translation can be performed to convert application addresses to leader addresses and / or traffic gating can be performed to drop unauthorized traffic (i.e., application traffic originating from devices not selected as traffic sources). The TCF can perform actions such as... Figure 4 The process shown and further described below is used to perform this management (i.e., operation 303.3), in which the TCF can interact with the PMF, the leader device, and one or more traffic sources. Therefore, the TCF initiates a data plane path management operation to route selected traffic to the leader device.

[0090] Managing data plane paths may include selecting a data plane path to the leader device. Managing data plane paths may include selecting a data plane path from traffic sources that generate selected traffic. The selected data plane path is used to route selected traffic from the traffic source to the leader device, from the leader device to the traffic source, or both. Managing data plane paths may include configuring one or more data plane functions that process the selected traffic. Such data plane functions may include one or both of the following: a data plane function operating as a data plane anchor (DPA) of the leader device; a data plane function operating as a DPA of one or more traffic sources. Managing data plane paths may include initiating PMF operations to select a data plane path, configure data plane functions, etc.

[0091] It should be noted that, Figure 3 Operation 303 (including sub-operations 303.1, 303.2, and 303.3) can be executed iteratively, i.e., executed multiple times in sequence. Each time (i.e., each iteration) operation 303 is executed, application traffic can be routed to the selected leader device. Different leader devices and / or different sets of traffic sources can be selected in different iterations.

[0092] This disclosure relates to managing a data plane path for a group of devices. This group of devices includes, for example, devices composed of... Figure 3 The associated embodiments identify one or more candidate leaders and one or more candidate traffic sources through the device information described. More specifically, the TCF 126 manages the data plane paths for the leader device and one or more traffic sources to route application traffic to the leader device. Application traffic is generated by... Figure 3 The traffic information described in the associated embodiments is used for identification. The leader device is selected or elected (e.g., in...). Figure 3 In Operation 303.1) it is the device that is the leader among one or more candidate leaders. When the TCF manages the data plane path (e.g., in... Figure 3 In operation 303.3, the TCF performs, for example... Figure 4 The process shown and described below involves a device 450 that is the selected leader device (in other words, the elected leader). A traffic source (TS) 456 is a network entity (e.g., a device or AS) that sends at least a portion of the application traffic. In some embodiments, the TS is selected from one or more candidate traffic sources (e.g., in...). Figure 3 The device in operation 303.2. In some embodiments, DPF1 452 and DPF2 454 are the same network entity. In some embodiments, operation 405 occurs before operation 404. In some embodiments, operations 403 and 405 are combined. In some embodiments, operation 406 occurs before operation 404.

[0093] For more details, please refer to [link / reference]. Figure 4In operation 401, TCF 126 notifies device 450 of the application's leader election decision by sending a notification message to the device. For example, when the device is a radio device such as a UE, the notification message can be transmitted to the device via the RAN. In this case, the notification message can be a NAS message sent to the device or included in a NAS message sent to the device. The NAS message can be generated by (and therefore sent from) TCF 126 or generated by (and therefore sent from) another network function (e.g., PMF 128, or a network function managing mobility such as AMF in a 3GPP 5G system). When the NAS message is generated by another network function, TCF 126 sends the notification message to that other network function, which includes the notification message in the NAS message before sending it to the device.

[0094] This notification message indicates the leader device selection, meaning device 450 has been selected as the leader. (It can be...) Figure 3 In operation 303.1, a leader device is selected. This notification message may include information identifying the application (e.g., DNN or application ID).

[0095] The notification message can also indicate that traffic associated with the application (e.g., application traffic identified by the traffic information mentioned above) will be routed (transmitted) to device 450.

[0096] In operation 401, device 450 may send a response to TCF 126. For example, when a notification message is transmitted to the device via the RAN, the response may be transmitted to the TCF via the RAN, in which case the response may be included in a NAS message sent from the device to the RAN. The RAN may send NAS messages to TCF 126 directly or indirectly through another network function (e.g., PMF 128 or a network function that manages mobility (such as AMF in a 3GPP 5G system)).

[0097] The response can be either positive or negative. A positive response acknowledges the leader election decision, meaning the device agrees to become or act as the leader (i.e., assume the leader role). A negative response indicates that the device rejects or does not accept the leader election decision; in other words, the device does not agree to become or act as the leader.

[0098] The response includes information indicating whether it is a positive or negative response. If the response is positive, the process continues to operation 402. If the response is negative, the process stops, and the TCF can perform leader device selection again (e.g., Figure 3 In step 303.1), TCF 126 selects a different device as the leader.

[0099] In some embodiments, TCF 126 sends a notification message to the device via PMF 128, and device 450 sends a response to TCF 126 via PMF 128. When RAN is involved in transmitting the notification message and response, RAN is located between PMF and device. When PMF is involved in this step, information identifying the application may be included or added to the message by PMF (e.g., if the message sent from TCF to PMF does not include information identifying the application).

[0100] In operation 402, TCF 126 notifies PMF 128 of the leader election decision, i.e., device 450 has been elected as the leader of the application, by sending a message to PMF. The message sent to PMF indicates that device 450 has been elected as the leader and includes information identifying device 450. The message sent to PMF may also include information identifying the application (e.g., DNN or application ID). In some embodiments, operation 402 may be integrated into operation 401 when PMF is involved (e.g., causing TCF 126 to notify PMF 128 of the leader election decision, and then PMF to notify device 450 of the leader election decision). According to this operation, such as according to operations 404 and 406, PMF can be initiated to configure one or more DPFs.

[0101] The TCF can perform Operation 402 by providing a traffic routing request to the PMF. The traffic routing request can be generated by the TCF based on one or more policies received by the TCF from or originating from the PCF (e.g., in...). Figure 3 In operation 302). In operation 402, the message sent from the TCF to the PMF may include information describing the traffic routing request. In some embodiments, when the TCF and PCF are integrated (e.g., when the PCF implements the functionality of the TCF), the TCF (or PCF, due to integration) can provide the traffic routing request by providing one or more policies to the PMF. One or more policies are based on information in the AF request (e.g., in...). Figure 3 The information generated in operation 301 includes information describing the traffic routing requirements. This information may include one or more of the following: information about the leader, information about the traffic, information about one or more traffic sources, information about traffic gating, and information about address translation, which will be further described below.

[0102] The information about the leader indicates that device 450 is the leader device and may include information identifying device 450 (e.g., device ID or network address). The information about the leader may also indicate that application traffic identified in the information about traffic should be routed to device 450.

[0103] Information about traffic can identify application traffic. In some embodiments, the information about traffic also indicates that application traffic should be routed to a leader device identified in the information about the leader. The information about traffic can indicate that traffic including one or more specific addresses as destination addresses and / or one or more specific port numbers as destination port numbers is application traffic. One or more specific addresses and / or one or more specific port numbers are referred to as application addresses and are included in the information about traffic. In some embodiments, the information about traffic includes TCF 126 in... Figure 3 The traffic information received in operation 302, or included in the traffic information.

[0104] Information about one or more traffic sources may include information identifying the traffic sources (e.g., one or more IDs or a list of one or more network addresses). One or more traffic sources may include TCF 126 in... Figure 3 Operation 303.2 involves selecting one or more devices from one or more candidate traffic sources. One or more candidate traffic sources are accessed via TCF 126. Figure 3 The device information received in operation 302 is used for identification. In some embodiments, information about one or more traffic sources is part of the device information, i.e., it is included in the device information. In some embodiments, information about one or more traffic sources is mapped from the device information. In some embodiments, information about one or more traffic sources is the same as the device information.

[0105] Information about traffic gating, also known as traffic gating information, can indicate specific traffic, for example, that some of the traffic identified by the traffic gating information should be dropped or not allowed. Specific traffic may originate from one or more devices, also called gating devices, and include one or more network addresses of the gating devices as source addresses. In this case, specific traffic may be indicated by one or more network addresses of the gating devices (as source addresses). One or more network addresses may be included in or mapped from the traffic gating information. For example, the traffic gating information may include a list of one or more IDs identifying one or more gating devices, and network addresses are mapped from the list of one or more IDs. The IDs in the list of one or more IDs may be IDs identifying a single gating device or IDs identifying multiple gating devices (e.g., a group of gating devices). The aforementioned gating devices may be identified by device information (which...) Figure 3 The candidate traffic source identified in one or more candidate traffic sources (received by TCF 126 in operation 302) and not selected by TCF 126 as one or more traffic sources (e.g., in Figure 3 (In operation 303.2).

[0106] Information regarding address translation, also known as address translation information, may indicate that a destination address in application traffic identified in the information about traffic should be translated to another network address. In some embodiments, the destination address is an application address, which is included / used in the information about traffic to identify the application traffic. Another network address is associated with the leader device 450 and is referred to as the leader address. This information may include the destination address. This information may also include the leader address. In some embodiments, the leader address is included in the information about the leader to identify the leader device 450. In some embodiments, the address translation information does not include the leader address and may indicate that a leader address should be assigned. In this case, the PMF will assign the leader address, for example, as described in operations 404 and 406. The address translation information may include the network addresses to be translated and the network addresses to which these network addresses are to be translated.

[0107] In various embodiments, the address translation described above may include destination address translation. In this case, the destination address in the data packet is translated; for example, for a data packet originating from a traffic source (and pointing to a leader), the destination address of the data packet is changed from the application address to the leader address. In various embodiments, the address translation described above may include source address translation. In this case, the source address in the data packet is translated; for example, for a data packet originating from a leader (and pointing to a traffic source), the source address of the data packet is changed from the leader address to the application address. The application address in the destination address translation or source address translation is included / used in information about the traffic to identify the application traffic.

[0108] When the information regarding address translation includes the leader's address, in Figure 3 In operation 302, TCF 126 can allocate a leader address based on the information received from PCF 122, or in Figure 3 In operation 302, TCF 126 can receive the leader address from PCF 122. Based on information regarding address translation, as described in operations 404 and 406, PMF can instruct / configure DPF (e.g., DPF1 452 or DPF2 454) to perform address translation for application traffic. Accordingly, the DPF is used to detect and process selected traffic and route it to the leader device.

[0109] Furthermore, in operation 402, PMF 128 can respond to TCF 126 to acknowledge message reception. For example, this response can be optional when operation 407 is performed as an acknowledgment.

[0110] In operation 403, PMF 128 (re)selects a data plane path for device 450 based on the message (and information within the message) received from TCF 126 in operation 402. The data plane path connects the device and DPF1 452 and will be used to transfer application traffic from DPF1 452 to device 450. As described above, the data plane path can be associated with a session of device 450 (e.g., a PDU session in a 3GPP 5G system).

[0111] When (re)selecting a data plane path for device 450, PMF 128 selects DPF1 452 as the device's DPA and includes DPF1 in the data plane path. During the (re)selection of a data plane path for device 450, the PMF may consider data plane paths associated with one or more traffic sources identified in information about one or more traffic sources to ensure data plane efficiency. In various embodiments, this step may be optional or omitted.

[0112] In operation 404, PMF 128 configures the DPA of device 450 to detect application traffic and route it to device 450 along the data plane path. The data plane path connects device 450 and the device's DPA. The device's DPA is DPF1 452; the data plane path is selected by the PMF, for example, in operation 403.

[0113] PMF 128 can generate one or more packet detection rules based on information about the traffic (received from TCF 126 in operation 402). In operation 404, PMF provides one or more packet detection rules to DPF1 452. Then (for example, in operation 409.4), DPF1 452 will detect application traffic according to one or more packet detection rules.

[0114] In some embodiments, when DPF2 454 is configured / instructed (operation 406) to perform address translation (e.g., in operation 409.2), where DPF2 translates or replaces a destination address (which is an application address, as described above) in application traffic with another network address (which is a leader address, as described above), one or more packet detection rules provided to DPF1 452 include the leader address and indicate that traffic including the leader address as the destination address is application traffic or part of application traffic. The leader address may be included (specified) in the address translation information received by PMF 128 (in operation 402), or PMF 128 may assign a leader address. In some embodiments, when DPF2 454 is not configured / instructed to perform address translation, one or more packet detection rules provided to DPF1 452 include one or more application addresses and indicate that traffic including any one of the one or more application addresses as the destination address is application traffic or part of application traffic. One or more application addresses may be included (specified) in the traffic information.

[0115] In operation 405, when traffic source (TS) 456 is a device, PMF 128 in operation 402 selects a (re)data plane path for TS 456 based on the message received from TCF 126 (and the information in the message). The data plane path connects TS and DPF2 454 and will be used to transfer application traffic from TS to DPF2.

[0116] When (re)selecting a data plane path for TS 456, PMF 128 may select DPF2 454 as the DP anchor (DPA) of TS 456 and include DPF2 in the data plane path. PMF 128 may consider the device's data plane path during (re)selection of the TS's data plane path (e.g., it may be selected in operation 403) to contribute to data plane efficiency. In various embodiments, this step may be optional or omitted.

[0117] In some embodiments, PMF 128 performs operations 405 and 403 together, for example, simultaneously before operation 404.

[0118] In operation 406, PMF 128 configures DPF2 454 to detect application traffic and route it to DPF1 452 via a data plane path connecting DPF1 and DPF2. The data plane path may include one or more data plane tunnels. For example, in operations 403 or 405, the data plane path may be selected by the PMF, and in operations 404 and 406, for example, it is configured by the PMF. DPF2 454 can then detect the application traffic and route it accordingly (e.g., in operation 409.3) to DPF1 452.

[0119] DPF2 454 receives application traffic from TS 456. If TS is a device, DPF2 receives application traffic along the data plane path connecting TS and DPF2. PMF 128 selects a data plane path for TS, and this data plane path includes DPF2 as the DP anchor point of TS. When PMF selects a data plane path, PMF selects DPF2 as the DP anchor point of TS and includes it in the data plane path. In operation 405, PMF can select a data plane path for TS.

[0120] In various embodiments, PMF 128 may generate one or more packet detection rules based on information about the traffic (received from TCF 126 in operation 402). In operation 406, PMF 128 provides one or more packet detection rules to DPF2 454. Then (e.g., in operation 409.2), DPF2 454 detects application traffic according to the one or more packet detection rules. The one or more packet detection rules provided to DPF2 454 include one or more application addresses and indicate that traffic including any one of the one or more application addresses as a destination address is application traffic or part of application traffic. One or more application addresses may be included (specified) in the information about the traffic.

[0121] Based on the address translation information (received from TCF 126 in operation 402), as part of operation 404 or 406, PMF 128 may instruct or configure DPFs (i.e., DPF1 452 or DPF2 454, respectively) to perform (operation 409.4 or 409.2) address translation of application traffic. In some embodiments, the PMF instructs / configures only one of DPF1 452 and DPF2 454 to perform address translation of application traffic.

[0122] PMF 128 can generate one or more address translation rules based on address translation information, and provides one or more address translation rules to the DPF (i.e., DPF1 452 or DPF2 454) when configuring the DPF (in operations 404 or 406 respectively) to perform address translation for application traffic. The one or more address translation rules instruct the translation of a destination address to a translated network address, or replace the destination address with a translated network address. The destination address is the application address included in the traffic information (used to identify application traffic), and may also be included in one or more address translation rules. The translated network address is the leader address and is included in one or more address translation rules. The leader address may be included in the address translation information or generated by PMF 128, as further described below.

[0123] In some embodiments, a leader address is associated with device 450. In some embodiments, during operation 402, PMF 128 receives the leader address from TCF 126 (e.g., as part of information about the leader, more specifically, as the network address identifying device 450 in the information about the leader). In some embodiments, the leader address is assigned by PMF 128 based on information about address translation. For example, the PMF assigns the leader address when the information about address translation indicates that a leader address should be assigned, or when the information about address translation does not include a leader address.

[0124] According to one or more address translation rules, the DPF (i.e., DPF1 452 or DPF2 454) performs address translation of application traffic (in operations 404 or 406, respectively), wherein, before routing the application traffic (in operations 409.5 or 409.3, respectively), the DPF translates the destination address in the application traffic to the leader address, or replaces the destination address with the leader address. Therefore, when the DPF routes application traffic, the application traffic includes the leader address as the destination address. In some embodiments, the destination address before address translation is included in one or more address translation rules.

[0125] Based on information regarding traffic gating (received from TCF 126 in operation 402, also known as traffic gating information), PMF 128 may instruct or configure DPFs (e.g., DPF1 452 or DPF2 454) to perform traffic gating on application traffic (e.g., in operations 404 or 406, respectively). In some embodiments, the PMF instructs or configures only one of DPF1 452 and DPF2 454 to perform traffic gating on application traffic.

[0126] PMF 128 can generate one or more traffic gating rules based on information about traffic gating, and provide one or more rules to the DPF (i.e., DPF1452 or DPF2 454) when instructing / configuring (i.e., in operations 404 or 406 respectively) the DPF to perform traffic gating on application traffic. One or more traffic gating rules indicate that specific traffic originating from one or more gating devices should be dropped or not allowed. One or more traffic gating rules may include information identifying specific traffic, such as one or more network addresses (as source addresses) of one or more gating devices, which may be devices other than the selected traffic source. One or more network addresses may be included in the information about traffic gating. In some embodiments, one or more network addresses are mapped from the information about traffic gating. For example, the information about traffic gating may include a list of one or more IDs identifying one or more gating devices, and network addresses are mapped from the list of one or more IDs. The IDs in the list of one or more IDs may be IDs identifying a single gating device or IDs identifying multiple gating devices (e.g., a group of gating devices). The aforementioned gating devices may be determined by device information (which is...) Figure 3 The candidate traffic source identified in one or more candidate traffic sources (received by TCF 126 in operation 302) and not selected by TCF 126 as one or more traffic sources (e.g., in Figure 3 (In operation 303.2). Based on one or more traffic gating rules, the DPF performs traffic gating on application traffic (in operation 409.2 or 409.4), wherein the DPF identifies and discards specific traffic within the application traffic. The DPF detects application traffic (in operation 409.2 or 409.4) based on one or more packet detection rules received from PMF 128 (i.e., in operation 404 or 406), as described elsewhere in this disclosure.

[0127] In operation 407, PMF 128 notifies TCF 126 that the data plane has been configured according to the traffic routing requirements (received in operation 402). For example, when the leader address is assigned by the PMF, the notification sent to the TCF may include the leader address. For example, when the PMF does not send a response to the TCF in operation 402, the notification sent to the TCF may serve as a response or acknowledgment to a message received from the TCF in operation 402.

[0128] In operation 408 (including sub-operations 408.1, 408.2, or both), after receiving notification from PMF 128, TCF 126 determines that the data plane is ready. TCF triggers application-related data communication. During data communication, TS 456 sends application traffic.

[0129] In sub-operation 408.1, TCF 126 sends a notification to device 450. This notification may include information identifying the application (e.g., a DNN or application ID). The notification instructs device 450 that the device may begin application-related data communication, or that the device may expect to receive application-related or associated data traffic (i.e., the traffic is expected), or a combination thereof. Sub-operation 408.1 may include a leader address and indicate whether to report local computing status (as associated with a supported application). For example, TCF includes the leader address in the notification sent to device 450. Based on the notification, in operation 409.5, device 450 identifies data traffic including the leader address (as the destination address) as application traffic and accepts and processes the data traffic. TCF further instructs in the notification sent to device 450 to report local computing status. Based on this notification, device 450 reports its local computing status in operation 410. Local computing status may indicate whether application-related local computing is complete, or how much has been completed, for example, expressed as a percentage or ratio.

[0130] If device 450 is a wireless device, the notification can be sent to the device via the RAN, and this notification can be included in a non-access stratum (NAS) message. The NAS message is sent to the RAN, which then transmits it to the device. The NAS message can be generated by (and therefore sent from) TCF 126 or generated by (and therefore sent from) another network function (e.g., PMF 128, or a network function managing mobility such as AMF in a 3GPP 5G system). In the case where the NAS message is generated by another network function, the TCF sends a notification to that other network function, which includes or indicates the notification in the NAS message before sending it.

[0131] In sub-operation 408.2, TCF 126 sends a notification to TS 456. This notification may include information identifying the application (e.g., a DNN or application ID). The notification may indicate that the TS has been selected as the traffic source for the application. The notification may also indicate to the TS that it can begin application-related data communication, or that the TS can expect to receive application-related or associated data traffic (i.e., the traffic is expected), or both. Sub-operation 408.2 may include the leader address. Therefore, the notification may indicate that the TS can now perform data communication conforming to the selected traffic, and that the selected traffic will be routed to the leader.

[0132] If TS 456 is a radio device, the notification is transmitted to TS via RAN, and is included in a non-access stratum (NAS) message. The NAS message is sent to RAN, and RAN transmits the NAS message to TS456. The NAS message can be generated by (and thus sent from) TCF 126 or by another network function (e.g., PMF128, or a network function managing mobility such as AMF in a 3GPP 5G system)). In the case where the NAS message is generated by another network function, TCF sends the notification to that other network function, which includes the notification in the NAS message before sending it.

[0133] If TS 456 is AS, then TCF 126 sends the notification to the AF that subscribes to the notification. In some embodiments, the AF is... Figure 1 In AF 134, and when AF requests to perform a leader election, in Figure 3 In operation 301, AF subscribes to the notification. For example, Figure 3 The AF request in Operation 301 can instruct the AF to subscribe to the notification. Figure 3 In operation 302, one or more policies sent from PCF 122 to TCF 126 accordingly instruct the AF to subscribe to the notification. Notifications sent from the TCF can be... Figure 3 The network exposure function (NEF) 120 is transmitted to the AF. After receiving the notification, the AF can in turn notify AS 132 to start data communication.

[0134] In operation 409, for example, due to a triggering event from TCF 126 in operation 408, application-related data communication occurs between TS 456 and device 450. In operation 409, application-related data traffic is transmitted between TS 456 and device 450 via DPF1 452 and DPF2 454.

[0135] In sub-operation 409.1, TS 456 sends application traffic (which includes protocol data units (PDUs)). The application traffic is sent to DPF2 454. If TS is a device, the application traffic is sent to DPF2 along the TS's data plane path (which can be selected by the PMF in operation 405), the data plane path passing through the RAN.

[0136] In sub-operation 409.2, DPF2 454 detects application traffic and processes the application traffic according to the configuration or instructions received from PMF 128 (operation 406).

[0137] DPF2 454 detects application traffic based on one or more packet detection rules received in Operation 406. When processing application traffic, DPF2 can perform address translation based on one or more address translation rules received in Operation 406. One or more address translation rules indicate that the destination address should be translated to or replaced with the leader address. The leader address is included in one or more address translation rules. When performing address translation, DPF2 translates the destination address in the application traffic to the leader address indicated by one or more address translation rules, or replaces the destination address with the leader address indicated by one or more address translation rules. Therefore, when DPF2 routes application traffic (e.g., in Operation 409.3), the application traffic includes the leader address as the destination address.

[0138] In operation 409.3, DPF2 454 routes (sends) application traffic to DPF1 452 via a data plane path (including one or more data plane tunnels) connecting DPF2 and DPF1. The data plane path can be selected by PMF 128, for example, in operations 403 or 405, and configured by PMF 128, for example, in operations 404 and 406.

[0139] In sub-operation 409.4, DPF1 452 detects application traffic and processes the application traffic according to the configuration / instructions (operation 404) received from PMF 128.

[0140] DPF1 452 detects application traffic based on one or more packet detection rules received in Operation 404. When processing application traffic, DPF1 can perform address translation based on one or more address translation rules received in Operation 404. One or more address translation rules indicate that the destination address should be translated to or replaced with the leader address. The leader address is included in one or more address translation rules. When performing address translation, DPF1 translates the destination address in the application traffic to the leader address indicated by one or more address translation rules, or replaces the destination address with the leader address indicated by one or more address translation rules. Therefore, when DPF1 routes (e.g., in sub-operation 409.5) application traffic, the application traffic includes the leader address as the destination address. Because the address is changed, rather than provided to the source, destination address translation can help route packets to the leader while masking the leader's address from the source of these packets.

[0141] In sub-operation 409.5, DPF1 452 routes (sends) application traffic to device 450 along the device's data plane path. In operation 403, PMF 128 can select the data plane path.

[0142] In sub-operation 409.6, device 450 sends data traffic. The data traffic may be generated by the device based on the application traffic received in operation 409.5. The data traffic includes a leader address as the source network address. The data traffic is routed along the device's data plane path to DPF1 452. In operation 403, PMF 128 may select a data plane path for the device. In some embodiments, the data traffic includes an application address as the source address; the application address is an application address included in or used in information about the traffic to identify the application traffic (as described in operation 402). In some embodiments, the data traffic includes a leader address as the source address. In operation 401 or 408.1, the leader address may be provided to device 450.

[0143] In operation 404, DPF1 452 processes data traffic according to configuration or instructions received from PMF 128. In some embodiments, the data traffic includes a leader address as a source address, and when processing the data traffic, DPF1 may perform an address translation that is the reverse of the address translation performed in sub-operations 409.2 or 409.4. This address translation is called reverse address translation, and is also described above as source address translation. DPF1 may perform reverse address translation (i.e., source address translation) according to one or more rules, which are received in operation 404 and referred to as one or more reverse address translation rules (equivalently, one or more source address translation rules). One or more reverse address translation rules indicate that a source address matching the leader address should be translated into or replaced with an application address, which is an application address included or used in information about the traffic to identify the application traffic, as described in operation 402. One or more reverse address translation rules include application addresses. One or more reverse address translation rules may also include the leader address. When performing reverse address translation (ROC), DPF1 translates the source address (matching the leader address) in data traffic to the application address indicated in one or more ROC rules, or replaces the source address with the application address indicated in one or more ROC rules. Therefore, when DPF1 routes data traffic (e.g., in sub-operation 409.7), the data traffic includes the application address as the source address. ROC translation (i.e., source address translation) can facilitate the routing of return packets while masking the leader device's address from the destination of the return traffic packets.

[0144] In sub-operation 409.7, DPF1 452 sends data traffic to DPF2 454 via a data plane path (including one or more data plane tunnels). The data plane path can be selected by PMF 128, for example, in operations 403 or 405, and configured by PMF, for example, in operations 404 and 406. The data plane path can be the same as the one used in sub-operation 409.3.

[0145] In operation 406, DPF2 454 processes data traffic according to the configuration / instructions received from PMF 128. When processing data traffic, DPF2 can perform the reverse address translation described above, the opposite of the address translation performed in sub-operations 409.2 or 409.4. DPF2 can perform reverse address translation according to one or more reverse address translation rules described above. In this case, in operation 406, DPF2 receives one or more reverse address translation rules from PMF 128. When performing reverse address translation, DPF2 translates the source address (matching the leader address) in the data traffic to the application network address indicated in one or more reverse address translation rules, or replaces the source address with the application network address indicated in one or more reverse address translation rules. Therefore, when DPF2 routes data traffic (e.g., in sub-operation 409.8), the data traffic includes the application address as the source address.

[0146] In some embodiments, only one of DPF1 452 and DPF2 454 receives one or more reverse address translation rules from PMF 128 and performs reverse address translation accordingly. For example, in operation 404, PMF 128 provides one or more reverse address translation rules to DPF1 452, or in operation 406, it provides one or more reverse address translation rules to DPF2 454.

[0147] In sub-operation 409.8, DPF2 454 sends data traffic to TS 456. If TS is a device, the data traffic is sent to DPF2 along the data plane path of TS (which can be selected by PMF 128 in operation 405).

[0148] At a given time, device 450 can determine that it no longer needs to act as (stop acting as) the leader and notify TCF 126 of this determination. At operation 410, the device sends this notification to the TCF, for example, the notification is included in a NAS message. Accordingly, the notification indicates that device 450 has determined to stop acting as the leader of the application (i.e., receiving application traffic) and that the current iteration of coordinated traffic routing or leader election (operation 303) for that application has been completed. The notification may include information identifying the application (e.g., DNN or application ID). Based on this notification, TCF 126 can perform the next iteration of coordinated traffic routing (or leader election) for the application. Figure 3 (Operation 303 in the text). In some embodiments, the notification is first sent to PMF 128, and then PMF forwards the notification to TCF 126. In some embodiments, PMF includes information identifying the application in the notification before forwarding it to TCF. Operation 410 may indicate the local computing status of the leader device. Based on the local computing status, TCF may evaluate termination conditions and determine whether to perform a new iteration of coordinated traffic routing or leader election based on the evaluation results and associated data path management (Operation 303). For example, the termination condition may be that among the candidate leaders identified in the device information (described in Operation 301), the proportion of devices that have been elected as leaders and are in a specific state (e.g., local computing related to the application is complete, or complete to a specific percentage or ratio) is greater than or not less than a threshold. If the evaluation results indicate that the termination condition is met, TCF terminates the leader election (without performing a new iteration of leader election); otherwise, TCF performs a new iteration of coordinated traffic routing. The termination condition may be described in the AF request (Operation 301) and the policy sent to TCF (Operation 302). For example, the leader election indication in the AF request may include information describing the termination condition. The information describing the termination conditions specifies the threshold and the specific state. The policy sent to the TCF includes a leader election instruction, which in turn includes information describing the termination conditions.

[0149] It should be noted that the TCF can perform network address translation, traffic gating, or both, based on policies generated by the PCF based on AF requests. This execution can be performed via operations 402, 404, 405, 409.2, and 409.4. For example, address translation can be omitted when operation 408.2 includes an indication of the leader address. Address translation can swap the address associated with a supported application, or the address associated with a generic leader device, with the address of the current leader device. Depending on the traffic gating, traffic from unselected traffic sources can be discarded, or only traffic from selected traffic sources can be retained, or both.

[0150] It should be noted that the TCF coordinates data communication between the leader device and the traffic source, for example, through operations 401, 402, 408.1, 408.2 and 410.

[0151] In view of the above disclosure, the embodiments provide configurations for leader election requirements. The technical effect of these embodiments is that they allow the AF request system to perform leader election on traffic, thereby routing traffic to the leader (a device dynamically selected by the system).

[0152] Further considering the above disclosure, the embodiments provide leader election, including providing a notification instructing the election decision, a notification of termination of the leader state of the device, or both. The technical effect of these embodiments is to facilitate the synchronization of the device's system with the selected leader device and the AF associated with the leader election decision. In this way, a leader can be dynamically elected, and traffic routing can be managed effectively.

[0153] Furthermore, taking into account the above disclosure, the embodiments provide management of data plane paths to support traffic routing to the leader, including traffic gating and address translation (and reverse address translation). The technical effect of these embodiments is that only authorized traffic is allowed to be routed to the leader without exposing the leader device's identity information.

[0154] Figure 5 This is a schematic diagram of an electronic device 700 according to different embodiments of the present disclosure, which can perform any or all of the methods and features described herein, explicitly or implicitly. For example, a computer with network capabilities can be used as the electronic device 700.

[0155] As shown, the device includes processing electronics in the form of a processor 710 (e.g., a central processing unit (CPU), or a dedicated processor such as a graphics processing unit (GPU), or other such processing units), memory 720, non-transient mass storage 730, I / O interface 740, network interface 750, and transceiver 760, all communicatively coupled via a bidirectional bus 770. According to some embodiments, any or all of the elements shown, or only a subset of the elements shown, may be used. Furthermore, the device 700 may contain multiple instances of some elements, such as multiple processors, multiple memories, or multiple transceivers. Additionally, elements of the hardware device may be directly coupled to other elements without requiring a bidirectional bus. Other processing electronics (e.g., integrated circuits, application-specific integrated circuits, field-programmable gate arrays, digital circuits, analog circuits, etc., or combinations thereof) may be used to perform the required logical operations as a complement or alternative to the processor and memory. The processing electronics may include one or more of semiconductor chips and semiconductor dies. Some processing electronics can operate without external memory, for example, when the electronics are hardwired to operate in a specific manner.

[0156] Memory 720 may include any type of non-transitory memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or any combination thereof. Mass storage element 730 may include any type of non-transitory storage device, such as a solid-state drive, hard disk drive, disk drive, optical disk drive, USB drive, or any computer program product configured to store data and machine-executable program code. According to some embodiments, memory 720 or mass storage 730 may record statements and instructions executable by processor 710 thereon for performing any of the above-described method operations.

[0157] It should be understood that although specific embodiments of the technology have been described herein for illustrative purposes, various modifications may be made without departing from the scope of the technology. Therefore, the specification and drawings are simply to be regarded as a description of the invention as defined by the appended claims, and are contemplated to cover any and all modifications, variations, combinations, or equivalents falling within the scope of the invention. Specifically, computer program products, program elements, or program storage or storage devices (such as magnetic or optical wires, magnetic tape, or optical discs, etc.) are provided within the scope of this technology for storing machine-readable signals, for controlling the operation of a computer according to the method of this technology, and / or for constructing some or all of its components in a system according to this technology.

[0158] The actions associated with the methods described herein can be implemented as coded instructions in a computer program product. In other words, a computer program product is a computer-readable medium on which software code is recorded to perform the method when the computer program product is loaded into memory and executed on the microprocessor of a wireless communication device.

[0159] Furthermore, each operation of this method can be executed on any computing device (e.g., personal computer, server, PDA, etc.) and is performed based on one or more program elements, modules, or objects generated from any programming language (e.g., C++, Java, etc.), or a portion thereof. Additionally, each operation can be performed by dedicated hardware or circuit modules designed for this purpose, or by files or objects implementing each operation.

[0160] Based on the description of the above embodiments, the present invention can be implemented solely in hardware, or it can be implemented using software and necessary general-purpose hardware platforms. Based on this understanding, the technical solution of the present invention can be embodied in the form of a software product. The software product can be stored in a non-volatile or non-transitory storage medium, such as a compact disk read-only memory (CD-ROM), a USB flash drive, or a removable hard drive. The software product includes numerous instructions that enable a computer device (personal computer, server, or network device) to perform the methods provided in the embodiments of the present invention. For example, such execution may correspond to the simulation of logical operations as described herein. According to embodiments of the present invention, the software product may additionally or alternatively include multiple instructions that enable a computer device to perform operations for configuring or programming digital logic devices.

[0161] Although the invention has been described with reference to specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the invention. Therefore, the specification and drawings are simply to be regarded as a description of the invention as defined by the appended claims, and are contemplated to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the invention.

[0162] Embodiments have been described above in conjunction with aspects of the present invention, and these embodiments can be implemented based on these aspects. Those skilled in the art will understand that embodiments can be implemented in conjunction with the aspects described therein, but may also be implemented together with other embodiments of that aspect. It will be apparent to those skilled in the art that embodiments are mutually exclusive or incompatible. Some embodiments may be described in conjunction with one aspect, but may also be applicable to other aspects, as will be apparent to those skilled in the art.

Claims

1. A method in a communication network, the method comprising a first function (TCF): Receive one or more policies, which indicate parameters for leader election of a group of devices; The leader election is performed based on one or more of the strategies to elect a member of the group of devices as the leader device; Initiate a data plane path management operation to route selected traffic to the leader device.

2. The method according to claim 1, further comprising a second function: Receive a request to perform the leader election on the group of devices; Send the one or more strategies generated based on the request to the first function.

3. The method according to claim 2, wherein, The request includes one or more of the following: Traffic information used to identify the selected traffic, and used to route the selected traffic to the leader device; Equipment information used to identify the group of devices; Device information used to identify one or more traffic sources that generate the selected traffic; The instruction will execute the leader election instruction; Traffic source selection information indicates whether all devices indicated by the device information are capable of acting as the traffic source; Information indicating validity conditions, the validity conditions specifying the time, location, or both time and location at which the first function will perform the leader election; Information indicating validity conditions, which specify the time, location, or both time and location at which the first function will perform the selection of the traffic source.

4. The method according to claim 3, wherein, The leader election instruction includes information about whether the leader election will be performed in one iteration or over multiple iterations.

5. The method according to claim 3, wherein, The leader election instructions include the leader election criteria to be followed or considered during the leader election process.

6. The method according to claim 5, wherein, The leader election criteria include one or more of the following: computing power, remaining battery power, data availability, and data sufficiency.

7. The method according to claim 3, wherein, The leader election instruction also instructs that the selected traffic be routed to the leader device.

8. The method according to claim 3, wherein, The group of devices may be different from, the same as, or overlap with the one or more traffic sources.

9. The method according to any one of claims 2 to 8, further comprising a third function: Send the request to the second function.

10. The method according to any one of claims 1 to 9, wherein, The selected traffic includes data plane traffic from one or more traffic sources.

11. The method according to any one of claims 1 to 10, wherein, The selected traffic is identified based on one or a combination of the following: source address, destination address, and one or more port numbers.

12. The method according to any one of claims 1 to 11, wherein, The data plane path management operation includes: selecting a data plane path to the leader device, or selecting a data plane path from the traffic source that generates the selected traffic, or configuring one or more data plane functions to process the selected traffic, or a combination thereof.

13. The method according to claim 12, wherein, The one or more data plane functions include one or both of the following: a data plane function operating as a data plane anchor (DPA) of the leader device; a data plane function operating as a DPA of one or more traffic sources.

14. The method according to any one of claims 1 to 13, further comprising the first function: One or more traffic sources are selected from the set of devices or from another set of devices, wherein the traffic sources are potential sources of the selected traffic.

15. The method according to any one of claims 1 to 14, wherein, The leader election is performed by taking into account at least part of the current or statistical network state or conditions, the state of the members of the group of devices, or a combination thereof.

16. The method according to any one of claims 1 to 15, wherein, The data plane path management operations include: Initiate a notification to the member in the group of devices, the notification being about the member being selected as the leader device; The path management function (PMF) is initiated via messaging to configure one or more data plane functions (DPF) to detect and process selected traffic and route the selected traffic to the leader device.

17. The method according to claim 16, wherein, The notification that the member has been selected as the leader device is included in a non-access stratum (NAS) message sent to the member of the group of devices via the radio access network (RAN).

18. The method according to claim 16 or 17, wherein, The PMF is integrated with the first function.

19. The method according to any one of claims 1 to 18, wherein, The data plane path management operations include: The operation of the Path Management Function (PMF) is initiated via messaging to select a Data Plane (DP) path for routing the selected traffic from one or more traffic sources to the leader device, routing traffic from the leader device to the one or more traffic sources, or both.

20. The method of claim 19, further comprising: The PMF selects the DP path.

21. The method of claim 16, further comprising: After the PMF configures the one or more DPFs, the first function sends a notification to the leader device regarding expected data communication involving the selected traffic and routed to the leader device, regarding the leader device being able to initiate data communication, or regarding both.

22. The method according to claim 21, wherein, The notification is included in a non-access stratum (NAS) message sent to the leader device via the radio access network (RAN).

23. The method according to claim 16, 21 or 22, further comprising: After configuring the one or more DPFs, the first function sends a second notification to one or more traffic sources, the second notification stating that the traffic source can now perform data communication conforming to the selected traffic and that the selected traffic will be routed to the leader device, that the traffic source can now expect to receive data traffic from the leader device, or both.

24. The method according to claim 23, wherein, The traffic source can now perform data communication conforming to the selected traffic and the selected traffic will be routed to the leader device; the traffic source can now expect to receive data traffic from the leader device; or the second notification regarding both of the above is included in one or more non-access stratum (NAS) messages sent to the traffic source via the radio access network (RAN).

25. The method according to any one of claims 1 to 24, further comprising the first function: Subsequently, a third notification is received from the leader device, the third notification stating that the leader device has determined to cease acting as the leader device; In response to the notification that the leader device has been determined to cease acting as the leader device, the next iteration of leader device selection and associated data path management is initiated.

26. The method according to claim 25, wherein, The notification from the leader device that the leader device has determined to cease acting as the leader device is included in a non-access stratum (NAS) message sent to the traffic source via the radio access network (RAN).

27. The method according to any one of claims 16 and 21 to 23, wherein, Configuring the DPF includes configuring the DPF to perform one or both of the following: The destination address translation in the selected traffic packets helps route the packets to the leader device while masking the leader device's address from the source of the selected traffic packets; Source address translation in packets of return traffic from the leader device, which facilitates the routing of the return packets while masking the leader device's address from the destination of the return traffic packets.

28. The method according to claim 27, wherein, The configuration is executed based on address translation information, which indicates the target address translation, the source address translation, or both, and the address translation information originates from a second function that is separate from or integrated with the first function.

29. The method according to claim 28, wherein, The address translation information indicates one or more network addresses to be translated, and one or more translated network addresses to be translated from the one or more network addresses.

30. The method of claim 27, further comprising: The DPF performs the destination address translation, the source address translation, or both.

31. The method according to any one of claims 16, 21 to 23, and 27 to 30, wherein, Configuring the DPF includes configuring the DPF to perform traffic gating to drop traffic originating from devices other than the selected traffic source.

32. The method according to claim 31, wherein, The configuration is executed based on traffic gating information, which indicates the network address of the device other than the selected traffic source, and the traffic gating information originates from the second function.

33. The method of claim 32, further comprising: The DPF performs the flow gating.

34. The method according to claim 1, further comprising: A notification is sent to the members of the group of devices regarding the member being selected as the leader device.

35. A method in a communication network, the method comprising a first function: Initiate a notification to devices belonging to a group of devices regarding the selection of the leader device; The path management function (PMF) is initiated via messaging to configure one or more data plane functions (DPF) to detect and process selected traffic and route the selected traffic to the leader device.

36. The method according to claim 35, wherein, The notification that the device has been selected as the leader device is included in a non-access stratum (NAS) message sent to the device in the group of devices via the radio access network (RAN).

37. The method according to claim 35 or 36, wherein, The PMF is integrated with the first function.

38. The method according to claim 35, wherein, The selected traffic includes data plane traffic from one or more traffic sources.

39. The method according to any one of claims 35 to 37, wherein, The selected traffic is identified based on one or a combination of the following: source address, destination address, and one or more port numbers.

40. The method according to any one of claims 35 to 39, further comprising: The first function initiates the operation of the PMF via messaging to select a data plane (DP) path for routing the selected traffic from one or more traffic sources to the leader device, routing traffic from the leader device to the one or more traffic sources, or both.

41. The method of claim 40, further comprising: The PMF selects the DP path.

42. The method according to any one of claims 35 to 41, further comprising: After configuring the one or more DPFs, the first function sends a notification to the leader device regarding data communication expected to involve the selected traffic and be routed to the leader device, regarding the leader device being able to initiate data communication, or regarding both.

43. The method according to claim 42, wherein, The notification regarding anticipated data communication involving the selected traffic and routed to the leader device, the notification regarding the leader device being able to initiate data communication, or the notification regarding both are included in a non-access stratum (NAS) message sent to the leader device via the radio access network (RAN).

44. The method of any one of claims 35 to 43, further comprising, after configuring the one or more DPFs, the first function sending a notification to one or more traffic sources regarding the traffic sources now being able to perform data communication conforming to the selected traffic and the selected traffic being routed to the leader device, regarding the traffic sources now being expected to receive data traffic from the leader device, or regarding both of the above.

45. The method according to claim 44, wherein, The notification that the traffic source can now perform data communication conforming to the selected traffic and that the selected traffic will be routed to the leader device, that the traffic source can now expect to receive data traffic from the leader device, or that the notification regarding both of the above is included in one or more non-access stratum (NAS) messages sent to the traffic source via the radio access network (RAN).

46. ​​The method according to any one of claims 35 to 45, further comprising the first function: Subsequently, a notification is received from the leader device that the leader device has determined to cease acting as the leader device; In response to the notification that the leader device has been determined to cease acting as the leader device, the next iteration of leader device selection and associated data path management is initiated.

47. The method according to claim 46, wherein, The notification from the leader device that the leader device has determined to cease acting as the leader device is included in a non-access stratum (NAS) message sent to the traffic source via the radio access network (RAN).

48. The method according to any one of claims 35 to 47, wherein, Configuring the DPF includes configuring the DPF to perform one or both of the following: The destination address translation in the selected traffic packets helps route the packets to the leader device while masking the leader device's address from the source of the selected traffic packets; Source address translation in packets of return traffic from the leader device, which facilitates the routing of the return packets while masking the leader device's address from the destination of the return traffic packets.

49. The method according to claim 48, wherein, The configuration is executed based on address translation information, which indicates the target address translation, the source address translation, or both, and the address translation information originates from a second function.

50. The method according to claim 49, wherein, The address translation information indicates one or more network addresses to be translated, and one or more translated network addresses to be translated from the one or more network addresses.

51. The method of claim 48, further comprising: The DPF performs the destination address translation, the source address translation, or both.

52. The method according to any one of claims 35 to 51, wherein, Configuring the DPF includes configuring the DPF to perform traffic gating to drop traffic originating from devices other than the selected traffic source.

53. The method according to claim 52, wherein, The configuration is executed based on traffic gating information, which indicates the network address of the device other than the selected traffic source, and the traffic gating information originates from the second function.

54. The method according to claim 52 or 53, further comprising: The DPF performs the flow gating.

55. A first function in a communication network, comprising processing electronics and a network interface, and for: Receive one or more policies, which indicate parameters for leader election of a group of devices; The leader election is performed based on one or more of the strategies to elect a member of the group of devices as the leader device; Initiate a data plane path management operation to route selected traffic to the leader device.

56. A system in a communication network, comprising: The first function as described in claim 55; The second function is used for: Receive a request to perform the leader election on the group of devices; Send the one or more strategies generated based on the request to the first function.

57. The system of claim 55 further includes an application function (AF) for sending the request to the second function.

58. The system according to claim 56 or 57 further includes a path management function (PMF), wherein: The data plane path management operation includes: initiating a path management function (PMF) operation via messaging to select a data plane (DP) path for routing the selected traffic from one or more traffic sources to the leader device, routing traffic from the leader device to the one or more traffic sources, or both; The PMF is used to select the DP path.

59. The system according to any one of claims 56 to 58, further comprising one or more data plane functions (DPF), wherein, The data plane path management operations include: Initiate a notification to the member in the group of devices, the notification being about the member being selected as the leader device; The operation of the Path Management Function (PMF) is initiated via messaging to configure the one or more Data Plane Functions (DPF) to detect and process selected traffic and route the selected traffic to the leader device. The DPF is used to perform address translation, flow gating, or both.

60. A first function in a communication network, comprising processing electronics and a network interface, and for: Initiate a notification to devices belonging to a group of devices regarding the selection of the leader device; Initiate Path Management Function (PMF) operations to configure one or more Data Plane Functions (DPFs) to detect and process selected traffic and route the selected traffic to the leader device.

61. A system in a communication network, comprising: The first function as described in claim 60; The PMF is used to select the DP path.

62. The system of claim 61, further comprising the DPF, wherein, Configuring the DPF includes configuring the DPF to perform address translation, traffic gating, or both, wherein the DPF is used to perform the address translation, traffic gating, or both.

Images