Apparatus and method for indicating custom operations to group members in wireless communication system

Abstract

Aspects of the disclosure relate to a method, apparatus and device for wireless communication. A first network entity may be configured to be able or operable to receive a request message from a second network entity to create a group, the group comprising at least one member. The first network entity may be configured to be capable or operable to send an indication to the at least one member based at least in part on the created group. The indication includes a custom operation uniform resource identifier (URI) indicating information associated with at least one member of the created group. The first network entity may be configured to be able or operable to send a custom operation URI to the at least one member and to send a response message to the request message to the second network entity.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically to instructing group members to perform customized operations in a wireless communication system. Background Technology

[0002] A wireless communication system may include one or more network communication devices (which may be referred to as network devices (NEs)) that support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UEs) or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, the wireless communication system can support wireless communication across various wireless access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable wireless access technologies above 5G (e.g., advanced 5G (5G-A), sixth-generation (6G), etc.). Summary of the Invention

[0003] The article “a” preceding an element is unrestricted and should be understood to mean “at least one” or “one or more” of these elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one of the following,” “one or more of the following,” or “one or two of the following”) indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0004] Various aspects of this disclosure relate to wireless communications, including improved network entities, processors, and methods for instructing group members on customized operations in a wireless communication system.

[0005] A first network entity for wireless communication is described. The first network entity can be configured, enabled, or operable to receive a request message from a second network entity for creating a group, the group including at least one member. The first network entity can be configured, enabled, or operable to send an indication to at least one member, at least in part, based on the created group. The indication includes a custom operation Uniform Resource Identifier (URI), which indicates information associated with at least one member of the created group. The first network entity can be configured, enabled, or operable to send the custom operation URI to at least one member and to send a response message to the request message to the second network entity.

[0006] A processor for wireless communication is described. The processor can be configured, enabled, or operable to receive a request message from a network entity for creating a group, the group including at least one member. The processor can be configured, enabled, or operable to send an indication to at least one member, at least in part, based on the created group. The indication includes a custom operation Uniform Resource Identifier (URI) indicating information associated with at least one member of the created group. The processor can be configured, enabled, or operable to send the custom operation URI to at least one member and to send a response message to the request message to the network entity.

[0007] A method for wireless communication, performed or executable by a first network entity, is described. The method may include: receiving from a second network entity a request message for creating a group, the group comprising at least one member. The method may include: sending an indication to at least one member, at least in part based on the created group. The indication includes a custom operation Uniform Resource Identifier (URI), the custom operation URI indicating information associated with at least one member of the created group. The method may include: sending the custom operation URI to at least one member and sending a response message to the request message to the second network entity.

[0008] A second network entity for wireless communication is described. The second network entity can be configured, is capable of, or is operable to receive a request message from a first network entity including a custom operation URI, wherein the custom operation URI indicates information associated with the second network entity.

[0009] A processor for wireless communication is described. The processor can be configured, is capable of, or is operable to receive a request message from a first network entity including a custom operation URI, wherein the custom operation URI indicates information associated with a second network entity.

[0010] A method for wireless communication, performed or executable by a second network entity, is described. The method may include: receiving from a first network entity a request message including a custom operation URI, wherein the custom operation URI indicates information associated with the second network entity. Attached Figure Description

[0011] Figure 1 Examples of wireless communication systems according to various aspects of this disclosure are illustrated;

[0012] Figure 2 An example flowchart illustrating the process of supporting collaborative learning (FL) member grouping according to various aspects of this disclosure is shown;

[0013] Figure 3 Examples of UEs according to various aspects of this disclosure are illustrated;

[0014] Figure 4 Examples of processors according to various aspects of this disclosure are illustrated;

[0015] Figure 5 Examples of NEs according to various aspects of this disclosure are illustrated;

[0016] Figure 6 The diagram illustrates a flowchart of a method performed by an NE according to various aspects of this disclosure; and

[0017] Figure 7 A flowchart illustrating another method performed by an NE according to various aspects of this disclosure is shown. Detailed Implementation

[0018] Some wireless communication systems (including one or more UEs, base stations, network entities, etc.) can support customized operations applied (e.g., using) to members selected as part of a group. In some cases, operations associated with organizing a group of devices can be inefficient, such as by using increased signaling overhead and power consumption. For example, some wireless communication systems may send individual messages to individual members selected as part of a group, resulting in higher resource usage (e.g., system bandwidth) and increased power consumption.

[0019] Various aspects of this disclosure relate to improvements enabling one or more UEs, base stations, network entities, etc., to support customized operations to indicate information to group members. In some examples, one or more UEs, base stations, network entities, etc., can be configured to use a customized operation URI to indicate information to a group of devices. Alternatively or additionally, one or more UEs, base stations, network entities, etc., can be configured to transmit (e.g., send, output, indicate) customized operations to multiple devices. By using customized operations, one or more UEs, base stations, network entities, etc., can experience reduced power consumption, reduced processor utilization, reduced data utilization, and improved overall system performance.

[0020] Various aspects of this disclosure are described in the context of wireless communication systems.

[0021] Figure 1 An example of a wireless communication system 100 according to various aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a new radio (NR) network, such as a 5G network, an advanced 5G (5G-A) network, or a 5G ultra-wideband (5G-UWB) network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as time division multiplexing (TDMA), frequency division multiplexing (FDMA), or code division multiplexing (CDMA).

[0022] One or more NEs 102 may be distributed throughout a geographic area to form a wireless communication system 100. The one or more NEs 102 described herein may be, include, or may be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0023] NE 102 can provide a geographic coverage area, and NE 102 can support the services of one or more UE 104s within that geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, NE 102 can be mobile, for example, a satellite associated with an NTN. In some implementations, different geographic coverage areas associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NE 102s.

[0024] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, among other examples, UE 104 may be referred to as a unit, station, terminal, or client. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc.

[0025] UE 104 can support direct wireless communication with other UE 104s via a communication link. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, the communication link may be referred to as a sidechain. For example, UE 104 can support direct wireless communication with another UE 104 via a UE-to-UE interface (PC5 interface).

[0026] NE 102 can support communication with CN 106 or with another NE 102, or both. For example, NE 102 can interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some implementations, NE 102 can communicate directly with each other. In some other implementations, NE 102 can communicate with each other or indirectly (e.g., via CN 106). In some implementations, one or more NE 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC can communicate with one or more UE 104s via one or more other access network transport entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).

[0027] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnects to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more NEs 102 associated with CN 106.

[0028] CN 106 can communicate with the packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session with CN 106 via NE 102 (e.g., a Protocol Data Unit (PDU) session, etc.). CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. The PDU session may be an example of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0029] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, NE 102 and UE 104 can support different resource structures. For example, NE 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, NE 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 can support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 can support various frame structures based on one or more parameter sets.

[0030] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. The first parameter set (e.g., μ=0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the normal cyclic prefix. In some implementations, the first set of parameters (e.g., ) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. The second parameter set (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third parameter set (e.g., μ =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. The fourth parameter set (e.g., μ =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth parameter set (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0031] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0032] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ=4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of time slots used for a subframe can depend on the parameter set. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the parameter set. It should be understood that for a first parameter set (e.g., ...) associated with a first subcarrier spacing (e.g., 15 kHz) ... μ The reference of =0 can be used interchangeably between subframes and time slots.

[0033] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency ranges specified as FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, NE 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by NE 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other devices or apparatuses, for short-range, high data rate capabilities.

[0034] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the following: the first parameter set (e.g., μ =0), which includes a 15 kHz subcarrier spacing; the second parameter set (e.g., μ =1), which includes a 30 kHz subcarrier spacing; the third parameter set (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with the following: a third parameter set (e.g., μ=2), which includes a 60 kHz subcarrier spacing; the fourth parameter set (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.

[0035] For various reasons, such as machine learning (ML) models or applied data analytics enabling (ADAE) service analytics, the Artificial Intelligence Machine Learning (AIML) Enablement (AIMLE) server can be used to create FL member groups. To create such groups, the AIMLE server can evaluate different factors to select candidate participants to configure the FL member group. After the FL member group is created, the AIMLE server can designate candidates as FL members, who can be AIMLE clients, and / or the AIMLE server can indicate information about the group and its members.

[0036] FL group management can be described as overriding AIML capabilities to enable group management of entities acting as FL clients at the application enablement layer. FL group management may involve creating, monitoring, and / or updating FL member groups based on AIML operations, which may be based on: analytical events and / or services performed by the ADAE server (ADAES), or vertical application layer (VAL) requirements for FL support services.

[0037] An example process for using AIMLE to support FL member grouping can be applied by a specific VAL request, a machine learning (ML) model identifier (ID), or an ADAE analytics ID.

[0038] Prerequisites for supporting FL member grouping may include: the VAL server being connected to the AIMLE server and / or candidate and / or selected FL members being registered to the FL member registry based on their capabilities.

[0039] Figure 2 An example of a process flowchart 200 supporting FL member grouping according to various aspects of this disclosure is illustrated. Process flowchart 200 can implement various aspects of the wireless communication system 100. For example, process flowchart 200 may include FL member 202, ML repository 204, AIMLE server 206, and VAL server 208, which may be referenced herein. Figure 1Examples of one or more entities described. In the following description of process flowchart 200, one or more operations or signaling performed by FL member 202, ML repository 204, AIMLE server 206, and / or VAL server 208 may be performed or signaled in a different order than the example order shown, or one or more operations or signaling performed by FL member 202, ML repository 204, AIMLE server 206, and / or VAL server 208 may be performed or signaled at a different time than the example time shown. Some operations or signaling may be omitted, or other operations or signaling may be added. Furthermore, although FL member 202, ML repository 204, AIMLE server 206, and / or VAL server 208 are shown as performing operations of process flowchart 200, some aspects of some operations may also be performed by other entities of process flowchart 200 or entities not shown in process flowchart 200, or any combination thereof.

[0040] At 210, VAL server 208 can send (e.g., output, send, forward) and AIMLE server 206 can receive request messages to support a process. In some examples, the process may include creating a group comprising at least one member. Therefore, the request message may be a request to create a group comprising at least one member. For example, VAL server 208 can send and AIMLE server 206 can receive a request for FL member group support for supporting the FL process. In some configurations, AIMLE server 206 may receive FL member group support requests from VAL server 208 due to ML model or ADAE service analysis.

[0041] At 212, AIMLE server 206 may determine at least one requirement for creating a group, at least in part, based on (or in response to) a received request message, that the group includes one or more required (e.g., preferred, identified, selected) FL members for a corresponding ML task (e.g., ML model training, inference job identifier). The FL aggregator may be the same as VAL server 208 or AIMLE server 206, at least in part, based on the request message. At least one requirement (e.g., need) for creating the FL member group may be at least in part based on a corresponding AIMLE service area or a corresponding ML task for the AIMLE service area, wherein at least in part according to the received request message, one or more ML tasks are expected to be executed. AIMLE server 206 may evaluate various aspects, conditions, and availability to select candidate participants to configure the FL member group.

[0042] At 214, AIMLE server 206 can retrieve (e.g., obtain, retrieve) one or more available FL members from ML repository 204 for a corresponding ML task (e.g., ML model training, inference job identifier). ML repository 204 can be a centralized or distributed storage device, where FL members are stored and retrieved by AIMLE server 206, for example. Based on the information received by AIMLE server 206, AIMLE server 206 can select one or more FL members for a group of ML tasks.

[0043] At 216, AIMLE server 206 may configure an FL member group based at least in part on one or more of the available FL members or selected FL members. One or more criteria for determining the FL members of an FL member group may be based at least in part on one or more capabilities of the FL members, or whether the candidate members are static (e.g., fixed) or dynamic (e.g., mobile) nodes and their availability, and / or the proximity of each member among them.

[0044] At 218, AIMLE server 206 may send (e.g., notification, inform) and (candidate) FL member 202 (e.g., if the candidate includes a VAL UE, then it includes an AIMLE client) may receive indications of group identifiers and group member identifiers for ML model identifiers and / or analysis identifiers (e.g., at least in part based on the request message received at 210). Furthermore, AIMLE server 206 may indicate candidate FL members that could be AIMLE clients and / or information about that group and its members.

[0045] At 220, in response to the request message, AIMLE server 206 can send and VAL server 208 can receive a response message. For example, AIMLE server 206 can request VAL to send an FL member group support response, and VAL server 208 can receive an FL member group support response indicating group creation and group information.

[0046] Some of the implementations described in this paper can be used to describe federated learning services, define APIs including resources and data models for the service, and / or specify OpenAPI in YAML format for the service.

[0047] Federation learning services can enable AIMLE capabilities to create, monitor, and update FL member groups, including AIMLE clients, based on AIML service operations. Because AIML service operations apply to a given service area, and because of AIMLE client availability and other factors, AIMLE clients can enter or leave FL member groups, which may cause the AIMLE server to instruct AIMLE clients on updates for the FL member groups.

[0048] Table 1 shows an example of a service operation defined for the AIML_FederatedLearning API. Table 1: Operations for federated learning services

[0049] In some configurations, an Indicate_FL_Member_Group may exist. This can provide a general description of the service operation. Furthermore, FL member information associated with the FL member group can be indicated using the Indicate_FL_Member_Group service operation.

[0050] To update FL member information associated with an FL member group, the AIMLE server can send an HTTP POST request with the pattern "{apiRoot} / aiml-fl / ". <apiversion>The request-URI is “ / indicate” and the body contains the data type IndFlMember.

[0051] After receiving an HTTP POST request, the AIML client can: a) Verify the identity of the AIMLE server and determine whether the AIMLE server is authorized to provide information about the FL member group; and b) If the AIMLE server: 1) If unauthorized, the AIMLE client should respond to the AIMLE server with the appropriate error status code; or 2) If authorized, then the AIMLE client: i) The AIMLE server should be responded to using the HTTP "204 No Content" status code; and ii) HTTP POST requests should be processed and served.

[0052] AIML_FederatedLearning can use the AIML_FederatedLearning API. The API URI for AIML_FederatedLearning can be: {apiRoot} / <apiname> / <apiversion>.

[0053] The request URI used in an HTTP request can have the following resource URI structure: {apiRoot} / <apiname> / <apiversion> / <apispecificsuffixes>It has the following components: {apiRoot} can be set, <apiname>It can be "aiml-fl". <apiversion>It can be "v1", and / or <apispecificsuffixes>It can be set. In some configurations, the service producer (e.g., <NF or entity such as UAE server>) plays the role of the SCEF, and the service consumer (e.g., <provide examples of service consumers>) plays the role of the SCS / AS.

[0054] A service can have neither resources nor methods. There can also be custom operations without associated resources. The structure of a custom operation URI for the AIML_FederatedLearning API is shown in Table 2. Table 2

[0055] Table 3 provides an overview of the custom operations and applicable HTTP methods defined for the AIML_FederatedLearning API. Table 3: Custom Operations Without Associated Resources

[0056] A custom operation in which the AIML server indicates to the AIML client as an FL member and / or information associated with an FL member group can support the custom operation URI " / indicate", as shown in Table 3.

[0057] This custom operation can support the response data structures and response codes in Tables 4 to 7. Table 4: Data Structures Supported by the POST Request Ontology on This Resource Table 5: Data Structures Supported by the POST Response Ontology on This Resource Table 6: Headers Supported by the 307 Response Code on This Resource Table 7: Headers Supported by the 308 Response Code on This Resource

[0058] There can be an application data model supported by the API.

[0059] Table 8 specifies the data types defined for the AIML_FederatedLearning API. Table 8: AIML_FederatedLearning API Specific Data Types

[0060] Table 9 specifies the data types that can be reused by the AIML_FederatedLearning API. Table 9: Data Types Reused by the AIML_FederatedLearning API

[0061] Structured data type clauses can define the structures to be used in resource representations.

[0062] Table 10 corresponds to IndFlMember. Table 10: Definition of type IndFlMember

[0063] Table 11 corresponds to FlMemberType. Table 11: Definition of type FlMemberType

[0064] It can contain simple data types and enumerations that can be referenced from data structures.

[0065] Table 12 corresponds to simple data types. Table 12: Simple Data Types

[0066] The ValUeInfo enumeration can represent information about the availability, constraints, and roles of a VAL UE, as shown in Table 13. Table 13: Enumeration of ValUeInfo

[0067] For the AIML_FederatedLearning API, there may be no data type describing alternative data types or combinations of data types.

[0068] It can exist in the binary data types detailed in Table 14. Table 14: Binary Data Types

[0069] The AIML_FederatedLearning API supports HTTP error responses. It supports protocol errors and application errors for HTTP status codes.

[0070] There may be no specific procedure for the AIML_FederatedLearning API.

[0071] Table 15 lists the application errors defined for the AIML_FederatedLearning API. Table 15: Application Errors

[0072] As shown in Table 16, optional features may exist for the AIML_FederatedLearning API. These can be negotiated using extensibility mechanisms. Table 16: Supported Features

[0073] In one example, the AIML_FederatedLearning API can be as follows: OpenAPI: 3.0.0 info: title: AIML_FederatedLearning version: 1.0.0 description: | API for Federated Learning Service. © <2024> , 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI,TSDSI, TTA, TTC). All rights reserved. externalDocs: description:> 3GPP TS 24.560 V<0.2.0; Artificial Intelligence Machine Learning (AIML) Services – Service enabler Architecture Layer for Verticals (SEAL) ProtocolSpecification; Stage 3. url: http: / / www.3gpp.org / ftp / Specs / archive / 24_series / 24.560 / servers: - url: '{apiRoot} / aiml-fl / v1' variables: apiRoot: default: https: / / example.com description: apiRoot as defined in clause 5.2.4 of 3GPP TS29.122 security: - {} - oAuth2ClientCredentials: [] paths: / indicate: post: summary: Indicates FL member information on FL member group operationId: IndicateFLMemberInfo tags: - FL member information requestBody: required: true content: application / json: schema: $ref: '# / components / schemas / IndFlMember' responses: '204': description: No Content (Success) '307': $ref: 'TS29122_CommonData.yaml# / components / responses / 307' '308': $ref: 'TS29122_CommonData.yaml# / components / responses / 308' '400': $ref: 'TS29122_CommonData.yaml# / components / responses / 400' '401': $ref: 'TS29122_CommonData.yaml# / components / responses / 401' '403': $ref: 'TS29122_CommonData.yaml# / components / responses / 403' '404': $ref: 'TS29122_CommonData.yaml# / components / responses / 404' '411': $ref: 'TS29122_CommonData.yaml# / components / responses / 411' '413': $ref: 'TS29122_CommonData.yaml# / components / responses / 413' '415': $ref: 'TS29122_CommonData.yaml# / components / responses / 415' '429': $ref: 'TS29122_CommonData.yaml# / components / responses / 429' '500': $ref: 'TS29122_CommonData.yaml# / components / responses / 500' '503': $ref: 'TS29122_CommonData.yaml# / components / responses / 503' default: $ref: 'TS29122_CommonData.yaml# / components / responses / default' components: securitySchemes: oAuth2ClientCredentials: type: oauth2 flows: clientCredentials: tokenUrl: '{tokenUrl}' scopes: {} schemas: IndFlMember: description: Indicates the FL member the information on FLmember. type: object properties: serverId: type: string description: Identifier of the indicating AIMLE server valServiceId: type: string description: Identifier of the VAL service for which thegrouping indication is applied. mlModelId: type: string description: Identifier of the ML model for which theindication is applied. analyticsId: type: string description:> Identifier of the ADAE service analytics, the FL groupingis based on, if the FL process is used for that ADAE service analytics. flGroupId: type: array items: $ref: '# / components / schemas / FlMemberType' minItems: 1 description:> Identifier of the AIMLE created FL group for the FLprocess. required: - serverId - flGroupId oneOf: - required: [valServiceId] - required: [mlModelId] - required: [analyticsId] FlMemberType: description: Identifier of FL group. type: object properties: flMemberId: type: string description: Identifier of the FL members flMemberAddr: $ref: 'TS29549_SS_NetworkResourceAdaptation.yaml# / components / schemas / ValUeAddrInfo' description: Address information of the FL members flMemberInfo: $ref: '# / components / schemas / ValUeInfo' # Simple data types and Enumerations ValUeInfo: anyOf: - type: string enum: - AVAILABILITY - CONSTRAINT - ROLE - type: string description:> This string provides Information on the FL member. description: | Represents the information regarding availability, constraint, and role of the VAL UE. Possible values ​​are: - AVAILABILITY: Indicates the availability of the VAL UE. - CONSTRAINT: Indicates the constraint of the VAL UE. - ROLE: Indicates the role and type of the VAL UE.

[0074] Figure 3 An example of a UE 300 according to various aspects of this disclosure is illustrated. UE 300 may include a processor 302, a memory 304, a controller 306, and a transceiver 308. The processor 302, memory 304, controller 306, or transceiver 308, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0075] Processor 302, memory 304, controller 306, or transceiver 308, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured or otherwise supporting components for performing the functions described in this disclosure.

[0076] Processor 302 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, field-programmable gate array (FPGA), or any combination thereof). In some implementations, processor 302 may be configured to operate memory 304. In some other implementations, memory 304 may be integrated into processor 302. Processor 302 may be configured to execute computer-readable instructions stored in memory 304 to cause UE 300 to perform various functions of this disclosure.

[0077] Memory 304 may include volatile or non-volatile memory. Memory 304 may store computer-readable, computer-executable code, including instructions that, when executed by processor 302, cause UE 300 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 304 or another type of memory. Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0078] In some implementations, processor 302 and memory 304 coupled to processor 302 can be configured to cause UE 300 to perform one or more UE functions described herein (e.g., instructions stored in memory 304 are executed by processor 302). For example, according to the examples disclosed herein, processor 302 can support wireless communication at UE 300. For example, processor 302 coupled to memory 304 can be configured to cause UE 300 to perform various actions described herein.

[0079] Controller 306 can manage input and output signals for UE 300. Controller 306 can also manage peripheral devices not integrated into UE 300. In some implementations, controller 306 can utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, controller 306 can be implemented as part of processor 302.

[0080] In some implementations, UE 300 may include at least one transceiver 308. In other implementations, UE 300 may have more than one transceiver 308. Transceiver 308 may represent a wireless transceiver. Transceiver 308 may include one or more receiver chains 310, one or more transmitter chains 312, or a combination thereof.

[0081] Receiver chain 310 can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, receiver chain 310 may include one or more antennas for receiving signals over the air or via a wireless medium. Receiver chain 310 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 310 may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 310 may include at least one decoder for decoding / processing the demodulated signal to receive transmitted data.

[0082] Transmitter chain 312 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 312 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 312 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 312 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0083] Figure 4 An example of a processor 400 according to various aspects of this disclosure is illustrated. Processor 400 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 400 may include a controller 402 configured to perform various operations according to the examples described herein. Processor 400 may optionally include at least one memory 404, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 400 may optionally include one or more arithmetic logic units (ALUs) 406. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0084] Processor 400 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset or included in the processor chipset (e.g., processor 400)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0085] Controller 402 can be configured to manage and coordinate various operations of processor 400 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 400 to support various operations according to the examples described herein. For example, controller 402 can operate as a control unit of processor 400 to generate control signals that manage the operation of various components of processor 400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0086] Controller 402 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 404 and determine subsequent instructions(s) to be executed, enabling processor 400 to support various operations according to the examples described herein. Controller 402 may be configured to track the memory addresses of instructions associated with memory 404. Controller 402 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 402 may be configured to interpret instructions and determine control signals to be output to other components of processor 400, enabling processor 400 to support various operations according to the examples described herein. Additionally or alternatively, controller 402 may be configured to manage data flow within processor 400. Controller 402 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 400.

[0087] Memory 404 may include one or more caches (e.g., memory or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc., native to or included in processor 400). In some implementations, memory 404 may reside within or on the processor chipset (e.g., native to processor 400). In some other implementations, memory 404 may reside external to the processor chipset (e.g., remote from processor 400).

[0088] Memory 404 may store computer-readable, computer-executable code, including instructions that, when executed by processor 400, cause processor 400 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 402 and / or processor 400 may be configured to execute computer-readable instructions stored in memory 404 to cause processor 400 to perform various functions. For example, processor 400 and / or controller 402 may be coupled to or coupled to memory 404, and processor 400, controller 402, and memory 404 may be configured to perform the various functions described herein. In some examples, processor 400 may include multiple processors, and memory 404 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0089] One or more ALUs 406 can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALUs 406 may reside within or on a processor chipset (e.g., processor 400). In some other implementations, one or more ALUs 406 may reside outside the processor chipset (e.g., processor 400). One or more ALUs 406 can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 406 can receive input operands and an opcode that determines the operation to be performed. One or more ALUs 406 are configured with a variety of logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALUs 406 may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALUs 406 to handle conditional operations, comparisons, and bitwise operations.

[0090] Based on the examples disclosed herein, processor 400 may support wireless communication. Processor 400 may be configured or operable to support components for performing the various operations described herein. For example, processor 400 may be configured, capable, or operable to: receive from an NE a request message for creating a group, the group comprising at least one member; send an indication to at least one member, at least in part based on the created group, wherein the indication includes a custom operation Uniform Resource Identifier (URI) indicating information associated with at least one member of the created group; send the custom operation URI to at least one member of the created group; and send a response message to the request message to a network entity. Additionally or alternatively, processor 400 may be configured, capable, or operable to receive from a first NE a request message including a custom operation URI, wherein the custom operation URI indicates information associated with a second NE.

[0091] Figure 5 An example of an NE 500 according to various aspects of this disclosure is illustrated. The NE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, memory 504, controller 506, or transceiver 508, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0092] Processor 502, memory 504, controller 506 or transceiver 508, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC) or other programmable logic device, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure.

[0093] Processor 502 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some implementations, processor 502 may be configured to operate memory 504. In some other implementations, memory 504 may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory 504 to cause NE 500 to perform various functions of this disclosure. For example, processor 502 coupled to memory 504 may be configured such that NE 500 (e.g., a first NE): receives a request message from a second NE for creating a group, the group including at least one member; sends an instruction to at least one member, at least in part based on the created group, wherein the instruction includes a custom operation Uniform Resource Identifier (URI) indicating information associated with at least one member of the created group; sends the custom operation URI to at least one member of the created group; and sends a response message to the request message to a second network entity. Alternatively or concurrently, the processor 502 coupled to the memory 504 may be configured such that the NE 500 receives from the first NE a request message including a custom operation URI, wherein the custom operation URI indicates indication information associated with the NE 500.

[0094] In some implementations, the custom action URI includes a mapped HTTP POST request. In some implementations, the custom action URI indicates one or more of the following: a group identifier, an identifier of at least one member of the group, or a reason for creating the group.

[0095] In some implementations, the first NE can be an AIML server, and the second NE can be an AIML server or a VAL server. In some implementations, at least one member of the created group is selected for AI / ML tasks.

[0096] In some implementations, the request message includes a request to support the process. In some implementations, the process may include one or more operations, actions, tasks, etc. In some implementations, the process includes creating a group with one or more members. In some implementations, the group is created at least in part based on a request to support the process. In some implementations, a processor 502 coupled to memory 504 may be configured such that NE 500 (e.g., a first NE) evaluates the process and at least one requirement for selecting one or more members for the group. In some implementations, the group is created at least in part based on the evaluated process and at least one evaluated requirement.

[0097] In some implementations, this instruction includes the API URI. In some implementations, the API URI includes the API root, API name, and API version.

[0098] Memory 504 may include volatile or non-volatile memory. Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 502, cause NE 500 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 504 or another type of memory. Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates the transfer of computer programs from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0099] In some implementations, processor 502 and memory 504 coupled to processor 502 can be configured such that NE 500 performs one or more RAN functions described herein (e.g., instructions stored in memory 504 are executed by processor 502). For example, according to the examples disclosed herein, processor 502 can support wireless communication at NE 500.

[0100] Controller 506 can manage input and output signals for the NE 500. Controller 506 can also manage peripheral devices not integrated into the NE 500. In some implementations, controller 506 can utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, controller 506 can be implemented as part of processor 502.

[0101] In some implementations, the NE 500 may include at least one transceiver 508. In other implementations, the NE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

[0102] Receiver chain 510 can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, receiver chain 510 may include one or more antennas for receiving signals over the air or via a wireless medium. Receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 510 may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 510 may include at least one decoder for decoding / processing the demodulated signal to receive transmitted data.

[0103] Transmitter chain 512 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 512 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0104] Figure 6 A flowchart of method 600 according to various aspects of this disclosure is illustrated. The operation of method 600 can be implemented by a first NE (e.g., an AIML server, a VAL server) described herein. In some implementations, the first NE can execute an instruction set to control the functional elements of a processor to perform the described functions. It should be noted that the method described herein describes one possible implementation, and these operations and steps can be rearranged or otherwise modified, and other implementations are also possible.

[0105] At 602, the method may include: receiving a request message from a second NE to create a group, the group comprising at least one member. The operation at 602 can be performed according to the examples described herein. In some implementations, aspects of the operation at 602 may be derived from references... Figure 5 The NE is used to execute this.

[0106] At 604, the method may include: sending an indication to at least one member, at least in part based on the created group, wherein the indication includes a custom action Uniform Resource Indicator (URI) indicating information associated with at least one member of the created group. The 604 operation can be performed according to the examples described herein. In some implementations, aspects of the 604 operation may be derived from references... Figure 5 The NE is used to execute this.

[0107] At position 606, the method may include sending a custom operation URI to at least one member of the created group. The operation at position 606 can be performed according to the examples described herein. In some implementations, aspects of the operation at position 606 can be found in the references. Figure 5 The NE is used to execute this.

[0108] At 608, the method may include sending a response message to the request message to the second NE. The operation at 608 can be performed according to the examples described herein. In some implementations, aspects of the operation at 608 can be found in the references. Figure 5 The NE is used to execute this.

[0109] Figure 7 A flowchart of another method 700 according to various aspects of this disclosure is illustrated. The operation of method 700 can be implemented by a second network element (e.g., an AIML server, a VAL server) described herein. In some implementations, the second NE can execute an instruction set to control the functional elements of the processor to perform the described functions. It should be noted that the method described herein describes one possible implementation, and these operations and steps can be rearranged or otherwise modified, and other implementations are also possible.

[0110] At 702, the method may include: receiving from a first NE a request message including a custom operation URI, wherein the custom operation URI indicates information associated with a second NE. The operation at 702 can be performed according to the examples described herein. In some implementations, aspects of the operation at 702 may be derived from references... Figure 5 The NE is used to execute this.

[0111] It should be noted that the method described in this paper describes one possible implementation, and these operations and steps can be rearranged or otherwise modified, and other implementations are also possible.

[0112] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.< / apispecificsuffixes> < / apiversion> < / apiname> < / apispecificsuffixes> < / apiversion> < / apiname> < / apiversion> < / apiname> < / apiversion>

Claims

1. A first network entity, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the first network entity: Receive a request message from a second network entity to create a group, the group including at least one member; At least in part based on the created group, an instruction is sent to the at least one member, wherein the instruction includes a custom operation Uniform Resource Identifier (URI), the custom operation URI indicating information associated with the at least one member of the created group; Send the custom operation URI to at least one member of the created group; and A response message is sent to the second network entity, at least in part based on the request message.

2. The first network entity of claim 1, wherein the customized operation URI includes a mapped Hypertext Transfer Protocol (HTTP) POST request.

3. The first network entity of claim 1, wherein the customized operation URI indicates one or more of the following: an identifier of the group, an identifier of the at least one member of the group, or a reason for creating the group.

4. The first network entity according to claim 1, wherein: The first network entity includes an AI / ML-enabled AIMLE server; and The second network entity includes an AIML server or a vertical application layer VAL server.

5. The first network entity of claim 1, wherein at least one member of the created group is selected for an artificial intelligence / machine learning (AI / ML) task.

6. The first network entity according to claim 1, wherein: The request message includes requests to support the process. The process includes creating the group with one or more members, and The group is created at least in part based on the request used to support the process.

7. The first network entity of claim 6, wherein the at least one processor is further configured to cause the first network entity to: The process of evaluation and at least one requirement for selecting one or more members for the group shall be assessed. The group is created at least in part based on the evaluated process and the evaluated at least one requirement.

8. The first network entity of claim 1, wherein the indication includes an application programming interface (API) URI, and wherein the API URI includes an API root, an API name, and an API version.

9. A method performed by a first network entity, the method comprising: Receive a request message from a second network entity to create a group, the group including at least one member; At least in part based on the created group, an instruction is sent to the at least one member, wherein the instruction includes a custom operation uniform resource indicator URI, the custom operation URI indicating information associated with the at least one member of the created group; Send the customized operation URI to at least one member of the group; and Send a response message to the request message to the second network entity.

10. The method of claim 9, wherein the customized operation URI includes a mapped Hypertext Transfer Protocol (HTTP) POST request.

11. The method of claim 9, wherein the customized operation URI includes one or more of the following: an identifier of the group, an identifier of the at least one member of the group, or a reason for creating the group.

12. The method of claim 9, wherein: The first network entity includes an AI / ML-enabled AIMLE server; and The second network entity includes an AIML server or a vertical application layer VAL server.

13. The method of claim 9, wherein the at least one member of the group is selected for an artificial intelligence / machine learning (AI / ML) task.

14. A second network entity, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the second network entity: Receive a request message from a first network entity that includes a custom operation Uniform Resource Identifier (URI), wherein the custom operation URI indicates information associated with the second network entity, and wherein the custom operation URI includes a mapped Hypertext Transfer Protocol (HTTP) POST request.

15. A method performed by a second network entity, the method comprising: Receive a request message from a first network entity that includes a custom operation Uniform Resource Identifier (URI), wherein the custom operation URI indicates information associated with the second network entity, and wherein the custom operation URI includes a mapped Hypertext Transfer Protocol (HTTP) POST request.

Images