KR20230116672A - Time Synchronization Service Method for Federated Learning in 5G NETWORK - Google Patents

Abstract

A time synchronization service method for federated learning within a 5G network is disclosed.
In the time synchronization service method for federated learning of user equipment (UE) in a 5G network according to an embodiment, the AIMLF provides a federated learning time synchronization service from the AIML AF. Receiving a subscription request for user equipment capabilities information; and in response to receiving the subscription request, the AIMLF transmitting the capability information to the AIML AF.

Description

Time Synchronization Service Method for Federated Learning in 5G Network {Time Synchronization Service Method for Federated Learning in 5G NETWORK}

The disclosure below relates to a time synchronization service method for federated learning within a 5G network.

A user equipment (UE) within a network (eg, a 5G network) may participate in federated learning. For the performance of federated learning, time synchronization between UEs participating in federated learning may be required.

Specifically, a parameter and / or procedure for exposing time synchronization service capability information for supporting federated learning between a UE and a 3 ^rd party application to the 5G system may be required.

The background art described above is possessed or acquired by the inventor in the process of deriving the disclosure of the present application, and cannot necessarily be said to be known art disclosed to the general public prior to the present application.

A time synchronization service providing method according to an embodiment may provide a procedure for exposing time synchronization capability information to support federated learning in a 5G system.

However, the technical challenges are not limited to the above-described technical challenges, and other technical challenges may exist.

In the time synchronization service method for federated learning of user equipment (UE) in a 5G network according to an embodiment, the AIMLF provides a federated learning time synchronization service from the AIML AF. Receiving a subscription request for user equipment capabilities information; and in response to receiving the subscription request, the AIMLF transmitting the capability information to the AIML AF.

The capability information may include availability and capability of the UE for federated learning.

The receiving may include: receiving, by the NEF, the subscription request from the AIML AF; and receiving, by the AIMLF, the subscription request from the NEF.

The transmitting may include transmitting, by the AIMLF, transmitting the capability information to the NEF; and transmitting, by the NEF, the capability information to the AIML AF.

The subscription request may include DNN and S-NSSAI.

The subscription request may further include a list of IDs of the UE.

The list may be for limiting subscription to the capability information of one or more UEs among the UEs.

1 is a diagram for explaining a 5G system according to an embodiment.
2 is a flowchart illustrating a method of exposing time synchronization capability information according to an exemplary embodiment.
3 is a flowchart illustrating a method for activating a time synchronization service according to an exemplary embodiment.
4 is a schematic block diagram of a time synchronization service device according to an embodiment.

Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only, and may be changed and implemented in various forms. Therefore, the form actually implemented is not limited only to the specific embodiments disclosed, and the scope of the present specification includes changes, equivalents, or substitutes included in the technical idea described in the embodiments.

Although terms such as first or second may be used to describe various components, such terms should only be construed for the purpose of distinguishing one component from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element.

It should be understood that when an element is referred to as being “connected” to another element, it may be directly connected or connected to the other element, but other elements may exist in the middle.

Singular expressions include plural expressions unless the context clearly dictates otherwise. In this document, "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "A Each of the phrases such as "at least one of , B, or C" may include any one of the items listed together in that phrase, or all possible combinations thereof. In this specification, terms such as "comprise" or "have" are intended to designate that the described feature, number, step, operation, component, part, or combination thereof exists, but one or more other features or numbers, It should be understood that the presence or addition of steps, operations, components, parts, or combinations thereof is not precluded.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and unless explicitly defined in this specification, it should not be interpreted in an ideal or excessively formal meaning. don't

The term "module" used in this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be an integrally constructed component or a minimal unit of components or a portion thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

The term '~unit' used in this document means software or a hardware component such as FPGA or ASIC, and '~unit' performs certain roles. However, '~ unit' is not limited to software or hardware. '~bu' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors. For example, '~unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, may include subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Functions provided within components and '~units' may be combined into smaller numbers of components and '~units' or further separated into additional components and '~units'. In addition, components and '~units' may be implemented to play one or more CPUs in a device or a secure multimedia card. Also, '~ unit' may include one or more processors.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. In the description with reference to the accompanying drawings, the same reference numerals are given to the same components regardless of reference numerals, and overlapping descriptions thereof will be omitted.

1 is a diagram for explaining a 5G system according to an embodiment. 1 may be a diagram for explaining a 5GS 100 providing a time synchronization service for federated learning of a user equipment (UE) 150.

Referring to FIG. 1 , according to an embodiment, a 5GS 100 may include an AIML AF 110 and an AIMLF 130. The 5GS 100 may provide a time synchronization service for federated learning using the AIML AF 110 and/or the AIMLF 130. 5GS (100) can activate and deactivate the time synchronization service.

For the time synchronization service, the AIML AF (100) can subscribe to UE capabilities information (eg, UE availability, UE capabilities) and / or 5GS (100) there is. For example, the AIML AF 100 may directly transmit a subscription request to the AIMLF 130. For another example, the AIML AF 100 may transmit a subscription request to the AIMLF 130 through the NEF (eg, the NEF 220 of FIGS. 2 and 3). Each of the AIML AF 100 and NEF 220 may discover and select the AIMLF 130 based on a specific procedure (eg, the procedure described in Section 6.3.24 of 3GPP TS 23.501).

The subscription request of the AIML AF 100 includes DNN (data network name), S-NSSAI (single-network slice selection assistance information), and / or UE ID list (user equipment identities list) (eg, UE group ID) can do. The UE ID list may be for limiting subscription to specific UEs.

The AIML AF 100 may use (or reuse) TSC assistance information (TSCAI). TSCAI can be used to describe TSC traffic characteristics (time sensitive communication traffic characteristics). TSCAI may include and/or use the following information (eg, information described in 3GPP TS 23.501).

[Table 1]

AIMLF 130 may support a service-based interface (SBI). The AIMLF 130 may receive a request for time synchronization service from the AIML AF 100 using SBI. The AIMLF 130 may configure parameters for the time synchronization service based on the subscription request received from the AIML AF 100.

The AIMLF 130 may expose the 5GS 100 and/or UE capability information associated with the time synchronization service to the AIML AF 100. For example, AIMLF 130 may directly expose UE capability information and/or 5GS to AIML AF 100. For another example, the AIMLF 130 may expose (or transmit) UE capability information and/or 5GS 100 to the AIML AF 100 through the NEF 220. Exposed information (eg, UE capability information, 5GS information) may include a UE ID list, FL time synchronization distribution methods (eg, 5G clock sync, 5G clock quality).

To control the time synchronization service, the AIMLF 130 may use time synchronization parameters associated with the time synchronization service transmitted from the AIML AF 100. The time synchronization parameter may be transmitted directly from the AIML AF 100 or through the NEF 220. The AIMLF 100 may use (or reuse) TSC assistance information (TSCAI). TSCAI can be used to describe TSC traffic characteristics (time sensitive communication traffic characteristics).

AIMLF 130 may support the following functionality.

- A federated learning time synchronization service request from the PCF (eg, PCF1 250 in FIGS. 2 and 3, PCF2 260 in FIG. 3) and/or the UE 150 is sent to the AIML AF session (sessions) (e.g., sessions between AIMLF 130 and PCF 250, 260) associating

- Functions related to QoS and TSC assistance container (e.g. creation of TSC assistance container, determination of 5GS delay)

According to one embodiment, SBI based services may be specified for the AIMLF 130. For example, the following services may be specified.

- Naimlf_TimeSynchronization

One. Provides support for time synchronization services

2. Allow configuration of UEs and/or 5GC (5G core) for time synchronization service

- Naimlf_QoSand TSCAssitance

One. Allow NF consumer (network function consumer) to provide QoS parameters and/or information to create TSC Assistance Container

2 is a flowchart illustrating a method of exposing time synchronization capability information according to an exemplary embodiment.

Referring to FIG. 2 , according to an embodiment, operations 205 to 280 may be sequentially performed, but are not limited thereto. For example, two or more operations may be performed in parallel. For another example, one or more actions may be omitted.

In operation 205, the AIML AF 210 (eg, the AIML AF 110 of FIG. 1 ) provides UE capability information (eg, UE availability, UE capabilities) and/or A subscription and/or Nnef_TimeSynchronization_CapsSubscribe Request may be transmitted to a 5GS (eg, 5GS 100 in FIG. 1 ). The AIML AF 210 may provide an associated notification target address of the AIML AF 210 through a request (eg, Nnef_TimeSynchronization_CapsSubscribe Request).

The request of the AIML AF 210 may include DNN, S-NSSAI, and/or AIML AF service identifier (AIML AF-service-identifier). If the AIML AF 210 request does not include the DNN and/or S-NSSAI, the NEF 220 may determine the DNN and/or S-NSSAI using the AIML AF service identifier.

The event filter is a UE ID(s) identified by an external group identifier that further defines a subset of target UE(s) (e.g., GPSI(s)). s)) and/or a list of groups of UE(s). If the request of the AIML AF 210 does not include the UE ID(s) and/or external group identifier, the request of the AIML AF 210 has a PDU session using DNN and S-NSSAI. Any UE can be targeted. The NEF 220 may include GPSI(s) and/or an external group identifier in a request of the AIML AF 210 and pass it to the AIMLF 230.

The event filter may include one or more of a requested PTP instance type, a requested transport protocol for PTP, and a requested PTP profile.

When the NEF 220 processes the request of the AIML AF 210, the AIML AF service identifier may be used to authenticate the Naimlf_TimeSynchronization_CapsSubscribe Request.

If the AIML AF 210 request does not include the UE ID(s) list and/or external group identifier, the NEF 210 may reject the request based on the AIML AF service identifier and/or DNN/S-NSSAI. can

To unsubscribe from the UE capability information for time synchronization for the list of UE(s), the AIML AF 210 invokes the Nnef_TimeSynchronization_CapsUnsubscribe service operation and invokes a subscription correlation ID (subscription correlation ID). ID) can be provided.

In operation 210, in the case of Naimlf_TimeSynchronization_Caps_Subscribe, the NEF 220 may find and select the AIMLF 230 based on a specific procedure (eg, the procedure described in section 6.3.24 of 3GPP TS 23.501). The NEF 220 may invoke the Naimlf_TimeSynchronization_CapsSubscribe Request service operation to the AIMLF 230.

In the case of Naimlf_TimeSynchronization_Caps_Unsubscribe, the NEF 220 determines the AIMLF 230 using the subscription correlation ID and interacts with the AIMLF 230 by triggering the Naimlf_TimeSynchronization_Caps_Unsubscribe Request message. )can do.

In operation 215, a network function service consumer (eg, the AIMLF 230) may insert a data record into the UDR 240. For example, the NF service consumer may insert a new application data record into UDR 240. The NF service consumer may update data stored in the UDR 240.

In operation 220, the AIMLF 230 may acknowledge execution of Naimlf_TimeSynchronization_CapsSubscribe to a requester (eg, NEF 220). Acknowledgment may include a subscription correlation ID used to cancel and/or modify a subscription.

In operation 225, the NEF 220 may grant execution of Nnef_TimeSynchronization_CapsSubscribe to the requestor (eg, the AIML AF 210). Acknowledgment may include a subscription correlation ID used to cancel and/or modify a subscription.

In operation 230, based on a previous subscription to a notification procedure or a local configuration policy of UDR 240, UDR 240 sends data (eg, UDR 240's Addition, modification, and/or deletion of data) may be notified to a network function (NF) service consumer.

In operation 235, PCF1 250 may inform an NF service consumer (eg, UDR 240) of subscribed events.

In operation 240, upon establishment of a protocol data unit (PDU) session, the PCF1 250 configures the PDU session to time synchronization service based on the local configuration from the SMF and/or a 5GS bridge information event. influence can be determined. PCF1 (250) may call the Npcf_PolicyAuthorization_Notify service operation to AIMLF (230). The Npcf_PolicyAuthorization_Notify service operation may include the UE address and/or DNN/S-NSSAI of the PDU session.

PCF1 250 may register with the BSF. The AIMLF 230 may invoke the Npcf_PolicyAuthorization_Create Request message to the PCF1 250. AIMLF 230 may store the DNN/S-NSSAI and/or IP address received from PCF1 250 and may store SUPI received from BSF. AIMLF 230 may associate the DNN, S-NSSAI, IP address, and/or SUPI with the AF session.

If PMIC/UMIC information (eg PMIC/UMIC information from DS-TT or NW-TT) is available in PCF1 250, PCF1 250 sends the PMIC/UMIC information to AIMLF 230 calling Npcf_PolicyAuthorization_Notify. can report.

At operation 245, as part of the Npcf_PolicyAuthorization_Update request, AIMLF 230 retrieves (g)PTP capabilities (e.g., from DS-TT) using a specific procedure (e.g., the procedure described in section K.2.1 of 3GPP TS 23.501). (g) PTP capability) can be determined. If AIMLF 230 has not determined (g)PTP capabilities from NW-TT, AIMLF 230 uses a specific procedure (e.g., the procedure described in section K.2.1 of TS 23.501) to determine (g) ) PTP capabilities can be determined.

AIMLF 230 composes time synchronization capabilities for DS-TT/UE(s) connected to NW-TT based on DS-TT(s) and capability information received from NW-TT can do. If the Naimlf_TimeSynchronization_CapsSubscribe Request includes an event filter having one or more of the requested PTP instance type, the requested transport protocol for the PTP, and the requested PTP profile, AIMLF 230 considers DS-TT and/or NW-TT with time synchronization capability as part of the time synchronization capability set reported to NEF 220 and/or AIML AF 210 ( can consider).

At operation 250, AIMLF 230 may send Naimlf_TimeSynchronization_CapsNotify to NEF 220. Nflstsf_TimeSynchronization_CapsNotify may include time synchronization capabilities (composed in operation 245). For example, Naimlf_TimeSynchronization_CapsNotify is one or more user-plane node ID(s), a list of UE ID(s) associated with the user-plane node ID(s), and/or a user-plane node ID(s). It may include time synchronization capabilities for a set of DS-TT(s) connected to. The user plane node ID may identify the NW-TT associated with the UE/DS-TT(s).

At operation 255, NEF 220 may send Nnef_TimeSynchronization_CapsNotify to AIML AF 210. Nnef_TimeSynchronization_CapsNotify may be transmitted together with a time synchronization capability event.

Operations 260 to 285 may be substantially the same as operations 240 to 255 . A redundant description thereof will be omitted.

3 is a flowchart illustrating a method for activating a time synchronization service according to an exemplary embodiment.

Referring to FIG. 3 , according to an embodiment, operations 305 to 355 may be sequentially performed, but are not limited thereto. For example, two or more operations may be performed in parallel. For another example, one or more actions may be omitted.

In operation 305, the AIML AF 210 may create a time synchronization service configuration for a PTP instance by invoking a Nnef_TimeSynchronization_ConfigCreate service operation. A request (eg, Nnef_TimeSynchronization_ConfigCreate Request) of the AIML AF 210 may include time synchronization parameters (eg, time synchronization parameters in Table 4.15.9.3-1 of 3GPP TS 23.502). The request of the AIML AF 210 is a user plane node ID and a user plane node ID as a reference for the AIML AF session and the target of the UE(s) (eg, the UE 150 of FIG. It may include a subscription correlation ID.

At operation 310, the NEF 220 may authorize the request of the AIML AF 210. After approval, NEF 220 may call the Naimlf_TimeSynchronization_ConfigCreate service operation with AIMLF 230. For example, NEF 220 may call the Naimlf_TimeSynchronization_ConfigCreate service operation using parameters received from AIML AF 210. According to one embodiment, the AIML AF 210 may directly call a service (eg, time synchronization service) together with the AIMLF 230. The AIML AF 210 may be part of an operator's trust domain.

At operation 315, AIMLF 230 may respond with a Naimlf_TimeSynchronization_ConfigCreate Response. The Naimlf_TimeSynchronization_ConfigCreate Response may include a PTP instance reference.

At operation 320, NEF 210 may respond with a Nnef_TimeSynchronization_ConfigCreate Response. Nnef_TimeSynchronization_ConfigCreate Response may include a reference to time synchronization service configuration (eg, PTP instance reference).

In operations 320 and 330, the AIMLF 230 uses the user-plane node ID and/or subscription correlation ID to map corresponding AF sessions and/or The target UE(s) can be determined. A user-plane node ID and/or a subscription correlation ID may be information included in Naimlf_TimeSynchronization_ConfigCreate. AIMLF 230 uses the parameters included in the Naimlf_TimeSynchronization_ConfigCreate Request (eg, requested PTP instance type, transport protocol, and PTP profile) to use the user plane node Among all AF sessions associated with the user-plane node ID and subscription correlation ID (e.g., user-plane node ID and subscription correlation ID included in the Naimlf_TimeSynchronization_ConfigCreate Request), the corresponding AF session (corresponding AF session) and suitable DS-TT may be determined.

At operation 335, AIMLF 230 may notify NEF 210 with the Naimlf_TimeSynchronization_ConfigUpdateNotify service operation. The response of the AIMLF 230 may include a current state of time synchronization service configuration and/or a PTP instance reference.

At operation 340, NEF 210 may notify AIML AF 210 with a Nnef_TimeSynchronization_ConfigUpdateNotify service operation. The response of the NEF 210 may include the current state of time synchronization service setup and/or a PTP instance reference.

Operations 345 to 355 may be substantially the same as operations 325 to 340 . A redundant description thereof will be omitted.

According to an embodiment, time synchronization service parameters (eg, parameters described in 3GPP TS 23.502) may be used as shown in the table below for the time synchronization service.

[Table 2]

4 is a schematic block diagram of a time synchronization service device according to an embodiment.

Referring to FIG. 4 , a device 400 may be a network entity of a 5GS (eg, 5GS 100 of FIG. 1 ). For example, the device 400 may include AIML AFs 110 and 210, NEFs 220, AIMLFs 130 and 230, UDRs 240, and/or PCFs 250, 260) and may be substantially the same. Device 400 may include a processor 420 and a memory 440 .

The memory 440 may store instructions (or programs) executable by the processor 420 . For example, the instructions may include instructions for executing an operation of the processor 420 and/or an operation of each component of the processor 420 .

The processor 420 may process data stored in the memory 440 . Processor 420 may execute computer readable code (eg, software) stored in memory 440 and instructions invoked by processor 420 .

The processor 420 may be a hardware-implemented data processing device having a circuit having a physical structure for executing desired operations. For example, desired operations may include codes or instructions included in a program.

For example, a data processing unit implemented in hardware includes a microprocessor, a central processing unit, a processor core, a multi-core processor, and a multiprocessor. , Application-Specific Integrated Circuit (ASIC), and Field Programmable Gate Array (FPGA).

Operations performed by the processor 420 include AIML AFs 110 and 210, NEFs 220, AIMLFs 130 and 230, UDRs 240, and/or PCFs 250 described with reference to FIGS. 1 to 3. , 260) may be substantially the same as the operation. Accordingly, detailed descriptions will be omitted.

The embodiments described above may be implemented as hardware components, software components, and/or a combination of hardware components and software components. For example, the devices, methods and components described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate (FPGA). array), programmable logic units (PLUs), microprocessors, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and software applications running on the operating system. A processing device may also access, store, manipulate, process, and generate data in response to execution of software. For convenience of understanding, there are cases in which one processing device is used, but those skilled in the art will understand that the processing device includes a plurality of processing elements and/or a plurality of types of processing elements. It can be seen that it can include. For example, a processing device may include a plurality of processors or a processor and a controller. Other processing configurations are also possible, such as parallel processors.

Software may include a computer program, code, instructions, or a combination of one or more of the foregoing, which configures a processing device to operate as desired or processes independently or collectively. You can command the device. Software and/or data may be any tangible machine, component, physical device, virtual equipment, computer storage medium or device, intended to be interpreted by or provide instructions or data to a processing device. , or may be permanently or temporarily embodied in a transmitted signal wave. Software may be distributed on networked computer systems and stored or executed in a distributed manner. Software and data may be stored on computer readable media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium. A computer readable medium may store program instructions, data files, data structures, etc. alone or in combination, and program instructions recorded on the medium may be specially designed and configured for the embodiment or may be known and usable to those skilled in the art of computer software. there is. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floptical disks. - includes hardware devices specially configured to store and execute program instructions, such as magneto-optical media, and ROM, RAM, flash memory, and the like. Examples of program instructions include high-level language codes that can be executed by a computer using an interpreter, as well as machine language codes such as those produced by a compiler.

The hardware device described above may be configured to operate as one or a plurality of software modules to perform the operations of the embodiments, and vice versa.

As described above, although the embodiments have been described with limited drawings, those skilled in the art can apply various technical modifications and variations based on this. For example, the described techniques may be performed in an order different from the method described, and/or components of the described system, structure, device, circuit, etc. may be combined or combined in a different form than the method described, or other components may be used. Or even if it is replaced or substituted by equivalents, appropriate results can be achieved.

Therefore, other implementations, other embodiments, and equivalents of the claims are within the scope of the following claims.

Claims (7)

In a time synchronization service method for federated learning of user equipment (UE) in a 5G network,
AIMLF receiving a subscription request for user equipment capabilities information for FL time synchronization service (federated learning time synchronization service) from AIML AF; and
In response to receiving the subscription request, the AIMLF transmitting the capability information to the AIML AF
Including, method.
According to claim 1,
The ability information,
Availability and capability of the UE for federated learning
Including method
According to claim 1,
In the receiving step,
NEF receiving the subscription request from the AIML AF; and
Receiving, by the AIMLF, the subscription request from the NEF
Including, method.
According to claim 1,
The sending step is
transmitting, by the AIMLF, the capability information to the NEF; and
Transmitting, by the NEF, the capability information to the AIML AF
Including, method.
According to claim 1,
The subscription request is
DNN and S-NSSAI
Including, method.
According to claim 5,
The subscription request is
List of IDs of the UE
Further comprising a method.
According to claim 6,
The above list is
For limiting subscription to the capability information of one or more UEs among the UEs.

Images