Apparatus for data transmission and wireless communication method

Abstract

A wireless communication method for data transmission, the method comprising: a functional entity receiving a first request indicating quality of service (QoS) parameters associated with a list of time windows for applying artificial intelligence (AI) / machine learning (ML) data transmission (AAMDT); the functional entity selects an AAMDT policy based on the QoS parameters.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 410,607, filed on September 27, 2022, and U.S. Provisional Application No. 63 / 411,548, filed on September 29, 2022, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication systems, and more specifically, to an apparatus and a wireless communication method for data transmission, such as a solution that supports providing higher quality of service (QoS) guarantees for planned and event-driven application layer data transmission through multiple time windows and quality-of-service (QoS) performance data analysis extensions. Background Art

[0003] In the 3rd Generation Partnership Project (3GPP) work, there are currently standardization activities to study data transmission, such as data transmission with artificial intelligence / machine learning (AI / ML). However, in current technology, data transmission and related parameter enhancements for AI / ML are still an open problem.

[0004] Therefore, there is a need for apparatus and communication methods for data transmission, such as solutions that support providing higher QoS guarantees for scheduled and event-driven application layer data transmission through multiple time windows and QoS performance data analysis extensions. Summary of the invention

[0005] The purpose of this application is to propose an apparatus and a wireless communication method for data transmission, such as supporting solutions for providing higher QoS guarantees for planned and event-driven application layer data transmission through multiple time windows and QoS performance data analysis extensions, which can solve these and other problems in the prior art, and / or meet the QoS requirements of application AI / ML data transmission.

[0006] In a first aspect of the present application, a wireless communication method for data transmission includes: a functional entity receives a first request indicating QoS parameters, which are associated with a time window list for application AI / ML data transfer (Application Artificial Intelligence / Machine Learning Data Transfer, AAMDT); the functional entity selects an AAMDT strategy based on these QoS parameters.

[0007] In a second aspect of the present application, a wireless communication method for data transmission includes: a functional entity receives a first request to create or update an AAMDT policy based on QoS parameters, which are associated with a time window list for AAMDT; the functional entity derives a set of policy and charging control (PCC) rules based on the AAMDT policy, and the set of PCC rules is used for the AAMDT.

[0008] In a third aspect of the present application, a wireless communication device includes: a transceiver configured to receive a first request indicating QoS parameters associated with a time window list for AAMDT; and a selector configured to select an AAMDT policy based on the QoS parameters.

[0009] In a fourth aspect of the present application, a wireless communication device includes: a transceiver configured to receive a first request to create or update an AAMDT policy based on QoS parameters, which are associated with a time window list for AAMDT; an exporter configured to export a set of PCC rules based on the AAMDT policy, which are used for the AAMDT.

[0010] In a fifth aspect of the present application, a network device includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The network device is configured to execute the above method.

[0011] In a sixth aspect of the present application, a non-transitory machine-readable storage medium has instructions stored thereon, which, when executed by a computer, cause the computer to perform the above method.

[0012] In a seventh aspect of the present application, a chip includes a processor configured to call and run a computer program stored in a memory so that a device equipped with the chip executes the above method.

[0013] In an eighth aspect of the present application, a computer-readable storage medium stores a computer program, which enables a computer to execute the above method.

[0014] In a ninth aspect of the present application, a computer program product includes a computer program, and the computer program enables a computer to execute the above method.

[0015] In a tenth aspect of the present application, a computer program enables a computer to execute the above method. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the embodiments of the present application or related technologies, the following figures to be described in the embodiments are briefly introduced. Obviously, the drawings are only some embodiments of the present application, and ordinary technicians in this field can obtain other drawings based on these drawings without prerequisites.

[0017] Figure 1 It is a block diagram of a functional entity according to an embodiment of the present application.

[0018] Figure 2 It is a flowchart of a wireless communication method for a functional entity to perform data transmission according to an embodiment of the present application.

[0019] Figure 3 It is a block diagram of a functional entity according to an embodiment of the present application.

[0020] Figure 4 It is a flowchart of a wireless communication method for a functional entity to perform data transmission according to an embodiment of the present application.

[0021] Figure 5 is a block diagram of a communication device according to an embodiment of the present application.

[0022] Figure 6 is a block diagram of a communication device according to an embodiment of the present application.

[0023] Figure 7 It is a block diagram of a network device according to an embodiment of the present application.

[0024] Figure 8 is a block diagram of a wireless communication architecture configured to implement some embodiments of the present application.

[0025] Fig. 9 is a flow chart of AAMDT policy negotiation for future protocol data unit (PDU) sessions to support application layer data transmission configured to implement some embodiments of the present application.

[0026] Fig.10The present invention is a flowchart of applying / updating / removing a negotiated AAMDT policy to a PDU session to support application AI / ML data transmission configured to implement some embodiments of the present application.

[0027] Fig.11 is a block diagram of an example of a computing device according to an embodiment of the present application.

[0028] Fig.12 is a block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0029] The following describes the embodiments of the present application in detail with reference to the accompanying drawings, using technical issues, structural features, achieved purposes and effects. Specifically, the terms in the embodiments of the present application are only used to describe the purpose of specific embodiments, rather than to limit the present application.

[0030] Network capacity planning is a major challenge for any mobile operator. In order to enable mobile network operators (MNOs) to assist application service providers (ASPs) in transmitting their application traffic (e.g., application artificial intelligence and machine learning (AI / ML) traffic) in a more controlled schedule to ensure the availability of network resources, application AI / ML data transmission can be of non guaranteed bit rate (non GBR) type or GBR type, and the GBR type requires some resource reservations aimed at achieving transmission performance requirements. For example, for the non-GBR type, the transmission of the model can be started at midnight and there is an amount of resources available to complete the data transmission. For example, for the GBR type, the application function (AF) can start the transmission of the model after 10 minutes and aim to complete the transmission within 1 second. This may mean setting some 5G QoS identifier (5QI), GBR, packet delay buffer (PDB) or packet loss rate (PLR) requirements for this type of traffic.

[0031] In order to enable the MNO to assist the ASP in transmitting its application AI / ML traffic in a more controlled schedule while taking into account the availability of network resources, some embodiments of the present application propose to support pre-negotiation between the AF and the 5G system (5G system, 5GS) to agree on a target time (which may be one or more windows selected from a list of time windows with expected QoS parameters). The list of time windows may be based on a previous service level agreement (Service Level Agreement, SLA) between the ASP and the MNO for traffic transmission to support planned and event-driven application AI / ML traffic. The 5G Core (5G Core, 5GC) of the 5GS may further refer to 5GC network analysis supported by support from the Network Data Analytics Function (NWDAF) and other auxiliary information to derive a list of time windows with their corresponding expected QoS parameters for data transmission.

[0032] AAMDT can support two data transmission strategies, namely, a data transmission strategy for future PDU sessions and a data transmission strategy for existing PDU sessions. Considering the data transmission requirements as described in some embodiments above, even if the initial intention of AAMDT is to support non-time-critical data during non-working hours, given the ability of AAMDT to pre-negotiate the expected data transmission schedule, data transmission strategy (e.g., data volume, one or a group of UEs, network area information, etc.), one or more AAMDT strategies can be renegotiated to enable the AF to adapt to changing network conditions and respond to event triggers. Some embodiments of the present application can utilize extensions to enhance the current AAMDT mechanism to provide higher QoS guarantees to support non-real-time application data transmission that meets the following operational behaviors: timely data transmission, event-driven (e.g., in response to threshold reports of "network performance" from NWDAF for areas of interest and time windows, UE locations, etc.) data transmission, and dynamic policy adaptation data transmission, etc.

[0033] Some embodiments may refer to extensions of AAMDT, and some embodiments may refer to application AI / ML data transmission (i.e., AAMDT). In some embodiments, the enhancement proposed by the solution is to extend the current AAMDT data transmission time window negotiation (i.e., desired time window and desTimeInt, etc.) to support more than one AAMDT data transmission time window when the AF requests more than one AAMDT data transmission time window during the AAMDT transmission policy negotiation with the 5GC. The AF can then select a specific negotiated AAMDT transmission policy corresponding to a specific time window to proceed with the AAMDT data transmission.

[0034] Further, in some embodiments, key performance indicators (KPIs) may be defined for QoS performance of data transmission to support application AI / ML traffic, i.e., splitting AI / ML reasoning, AI / ML model downloading, and federated learning (FL) learning. In order to utilize the existing / current AAMDT mechanism as described above to support non-real-time application traffic, it is necessary to extend the AAMDT transmission policy to support additional QoS parameters beyond the defined traffic capacity of each user equipment (UE). The following additional QoS parameters proposed in some embodiments of the present application will be added to the AAMDT transmission policy to support application AI / ML traffic, and these additional QoS parameters may include at least one of the following:

[0035] 1. Overall average and maximum packet delay budget for UL / DL per UE per time window.

[0036] 2. The overall average and maximum packet loss rate of UL / DL for each UE in each time window.

[0037] 3. Guaranteed and maximum traffic rates for UL / DL per UE per time window.

[0038] Note: The QoS parameters for uplink (UL) and downlink (DL) may not be equal.

[0039] In some embodiments, the Policy Control Function (PCF) may refer to the "network performance" analysis from the NWDAF to determine the candidate list of the AAMDT policy. In order to assist the PCF to better estimate the QoS parameters of the AAMDT policy, some embodiments of the present application propose to enhance the "network performance" analysis with an added set of input parameters so that the NWDAF can derive performance statistics and predictions for the set of QoS parameters between UEs.

[0040] Figure 1An example of a functional entity 100 according to an embodiment of the present application is shown. The functional entity 100 is configured to implement some embodiments of the present application. Some embodiments of the present application can be implemented into the functional entity 100 using any appropriately configured hardware and / or software. The functional entity 100 may include a memory 101, a transceiver 102, and a processor 103 coupled to the memory 101 and the transceiver 102. The processor 103 may be configured to implement the functions, processes and / or methods proposed in this specification. The radio interface protocol layer may be implemented in the processor 103. The memory 101 is operatively coupled to the processor 103 and stores various information to operate the processor 103. The transceiver 102 is operatively coupled to the processor 103, and the transceiver 102 transmits and / or receives radio signals. The processor 103 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. The memory 101 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage devices. The transceiver 102 may include a baseband circuit to process radio frequency signals. When the embodiment is implemented in software, the techniques described in this specification may be implemented using modules (e.g., processes, functions, etc.) that perform the functions described in this specification. These modules may be stored in the memory 101 and executed by the processor 103. The memory 101 may be implemented within the processor 103 or outside the processor 103, in which case these modules may be communicatively coupled to the processor 103 via various means known in the art.

[0041] In some embodiments, the memory 101 stores executable instructions that, when executed by the processor 103, cause the processor 103 to implement operations including: receiving a first request indicating QoS parameters associated with a time window list for AAMDT; selecting an AAMDT policy based on the QoS parameters. This can solve these and other problems in the prior art, and / or meet QoS requirements for application AI / ML data transmission.

[0042] Figure 2 A wireless communication method for a functional entity to perform data transmission according to an embodiment of the present application is shown. Figure 2It is an example of a communication method 200 for data transmission according to an embodiment of the present application. The communication method 200 for data transmission is configured to implement some embodiments of the present application. Some embodiments of the present application can be implemented into the communication method 200 for data transmission using any appropriately configured hardware and / or software. In some embodiments, the communication method 200 for data transmission includes: operation 202, the functional entity receives a first request, the first request indicates QoS parameters, and the QoS parameters are associated with a time window list for AAMDT; and operation 204, the functional entity selects an AAMDT policy based on these QoS parameters. This can solve these and other problems in the prior art, and / or meet the QoS requirements for application AI / ML data transmission.

[0043] In some embodiments, the functional entity is a Policy Control Function (PCF) entity. In some embodiments, the first request is an AAMDT policy control request, and the first request is a request from an Application Function (AF) via a Network Exposure Function (NEF) entity. In some embodiments, the method further includes: the functional entity requests a network performance analysis associated with these QoS parameters. In some embodiments, the AAMDT policy is selected based on the network performance analysis. In some embodiments, the method further includes: the functional entity sends the AAMDT transmission policy. In some embodiments, the AAMDT transmission policy is sent to the AF. Optionally, in some embodiments, the AAMDT transmission policy is sent to the AF via the NEF.

[0044] In some embodiments, the method further includes: the functional entity receives a second request to create or update an AAMDT policy. In some embodiments, the second request is an AF request, and the AAMDT policy is associated with an AAMDT for a protocol data unit (PDU) session, which is served by the functional entity. In some embodiments, the method further includes: the functional entity attempts to authorize the second request. In some embodiments, the method further includes: the functional entity retrieves the AAMDT policy from a user data repository (User Data Repository, UDR) entity. In some embodiments, the method further includes: the functional entity derives a set of policy and charging control (PCC) rules based on the AAMDT policy, and the set of PCC rules is used for AAMDT. In some embodiments, the method further includes: the functional entity initiates a session management (SM) policy association modification with a session management function (SMF) entity based on the set of PCC rules. In some embodiments, the QoS parameters include an aggregated bit rate (GBR) and at least one of a packet delay buffer (PDB), a packet loss rate (PLR), and a traffic rate.

[0045] Figure 3An example of a functional entity 300 according to an embodiment of the present application is shown. The functional entity 300 is configured to implement some embodiments of the present application. Some embodiments of the present application can be implemented in the functional entity 300 using any appropriately configured hardware and / or software. The functional entity 300 may include a memory 301, a transceiver 302, and a processor 303 coupled to the memory 301 and the transceiver 302. The processor 303 may be configured to implement the functions, processes and / or methods proposed in this specification. The radio interface protocol layer may be implemented in the processor 303. The memory 301 is operatively coupled to the processor 303 and stores various information to operate the processor 303. The transceiver 302 is operatively coupled to the processor 303, and the transceiver 302 transmits and / or receives radio signals. The processor 303 may include an ASIC, other chipsets, logic circuits and / or data processing devices. The memory 301 may include ROM, RAM, flash memory, a memory card, a storage medium and / or other storage devices. The transceiver 302 may include a baseband circuit to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described herein. These modules may be stored in memory 301 and executed by processor 303. Memory 301 may be implemented within processor 303 or external to processor 303, in which case these modules may be communicatively coupled to processor 303 via various means known in the art.

[0046] In some embodiments, the memory 301 stores executable instructions that, when executed by the processor 303, cause the processor 303 to implement operations including: receiving a first request to create or update an AAMDT policy based on QoS parameters associated with a time window list for the AAMDT; and deriving a set of PCC rules based on the AAMDT policy, the set of PCC rules being used for the AAMDT. This can solve these and other problems in the prior art, and / or meet QoS requirements for application AI / ML data transmission.

[0047] Figure 4 A communication method for data transmission by a functional entity according to an embodiment of the present application is shown. Figure 4It is an example of a communication method 400 for data transmission according to an embodiment of the present application. The communication method 400 for data transmission is configured to implement some embodiments of the present application. Some embodiments of the present application can be implemented into the communication method 400 for data transmission using any appropriately configured hardware and / or software. In some embodiments, the communication method 400 for data transmission includes: operation 402, a functional entity receives a first request to create or update an AAMDT policy based on QoS parameters, which are associated with a time window list for AAMDT; and operation 404, the functional entity derives a set of PCC rules based on the AAMDT policy, and this set of PCC rules is used for the AAMDT. This can solve these and other problems in the prior art, and / or meet the QoS requirements for application AI / ML data transmission.

[0048] In some embodiments, the functional entity is a PCF entity. In some embodiments, the first request is an AF request, and the AAMDT policy is associated with AAMDT for a PDU session, and the PDU session is served by the functional entity. In some embodiments, the method further includes: the functional entity attempts to authorize the second request. In some embodiments, the method further includes: the functional entity retrieves the AAMDT policy from a user data repository (UDR) entity. In some embodiments, the method further includes: the functional entity initiates a session management (SM) policy association modification with a session management function (SMF) entity based on the set of PCC rules.

[0049] In some embodiments, the method further includes: the functional entity receives a second request indicating the QoS parameters. In some embodiments, the method further includes: the functional entity selects an AAMDT policy based on the QoS parameters. In some embodiments, the second request is an AAMDT policy control request, and the second request is a request from an application function (AF) and via a network open function (NEF) entity. In some embodiments, the method further includes: the functional entity requests a network performance analysis associated with the QoS parameters. In some embodiments, the AAMDT policy is selected based on the network performance analysis. In some embodiments, the method further includes: the functional entity sends an AAMDT transmission policy. In some embodiments, the AAMDT transmission policy is sent to the AF. Optionally, in some embodiments, the AAMDT transmission policy is sent to the AF via the NEF. In some embodiments, the QoS parameters include an aggregate bit rate (GBR) and at least one of a packet delay buffer (PDB), a packet loss rate (PLR), and a traffic rate.

[0050] Figure 5 A communication device according to an embodiment of the present application is shown. Figure 5In some embodiments, the communication device 500 includes: a transceiver 501 configured to receive a first request indicating QoS parameters associated with a time window list for AAMDT; and a selector 502 configured to select an AAMDT policy based on the QoS parameters. This can solve these and other problems in the prior art, and / or meet the QoS requirements for application AI / ML data transmission.

[0051] In some embodiments, the wireless communication device 500 is a policy control function (PCF) entity. In some embodiments, the first request is an AAMDT policy control request, and the first request is a request from the AF and via the NEF entity. In some embodiments, the selector 502 is also configured to request a network performance analysis associated with these QoS parameters. In some embodiments, the AAMDT policy is selected based on the network performance analysis. In some embodiments, the transceiver 501 is also configured to send an AAMDT transmission policy. In some embodiments, the AAMDT transmission policy is sent to the AF. Optionally, in some embodiments, the AAMDT transmission policy is sent to the AF via the NEF. In some embodiments, the transceiver 501 is also configured to receive a second request to create or update the AAMDT policy.

[0052] In some embodiments, the second request is an AF request, and the AAMDT policy is associated with an AAMDT for a PDU session, which is served by the wireless communication device 500. In some embodiments, the selector 502 is further configured to attempt to authorize the second request. In some embodiments, the selector 502 is further configured to retrieve the AAMDT policy from a user data repository (UDR) entity. In some embodiments, the selector 502 is further configured to derive a set of PCC rules based on the AAMDT policy, and the set of PCC rules is used for the AAMDT. In some embodiments, the selector 502 is further configured to initiate a session management (SM) policy association modification with a session management function (SMF) entity based on the set of PCC rules. In some embodiments, the QoS parameters include an aggregate bit rate (GBR) and at least one of a packet delay buffer (PDB), a packet loss rate (PLR), and a traffic rate.

[0053] Figure 6 A communication device according to an embodiment of the present application is shown. Figure 6It is shown that in some embodiments, the communication device 600 includes: a transceiver 601, configured to receive a first request to create or update an AAMDT policy based on QoS parameters, which are associated with a time window list for AAMDT; an exporter 602, configured to export a set of PCC rules based on the AAMDT policy, which are used for the AAMDT. This can solve these and other problems in the prior art, and / or meet the QoS requirements of AI / ML data transmission.

[0054] In some embodiments, the wireless communication device 600 is a PCF entity. In some embodiments, the first request is an AF request and the AAMDT policy is associated with AAMDT for a PDU session that is served by the wireless communication device 600. In some embodiments, the exporter 602 is further configured to attempt to authorize the second request. In some embodiments, the exporter 602 is further configured to retrieve the AAMDT policy from a user data repository (UDR) entity. In some embodiments, the exporter 602 is further configured to initiate a session management (SM) policy association modification with a session management function (SMF) entity based on the set of PCC rules. In some embodiments, the transceiver 601 is further configured to receive a second request that indicates the QoS parameters. In some embodiments, the exporter 602 is further configured to select the AAMDT policy based on the QoS parameters.

[0055] In some embodiments, the second request is an AAMDT policy control request, and the second request is a request from the AF and via the NEF entity. In some embodiments, the exporter 602 is further configured to request a network performance analysis associated with these QoS parameters. In some embodiments, the AAMDT policy is selected based on the network performance analysis. In some embodiments, the transceiver 601 is further configured to send an AAMDT transmission policy. In some embodiments, the AAMDT transmission policy is sent to the AF. Optionally, in some embodiments, the AAMDT transmission policy is sent to the AF via the NEF. In some embodiments, these QoS parameters include an aggregate bit rate (GBR) and at least one of a packet delay buffer (PDB), a packet loss rate (PLR), and a traffic rate.

[0056] Figure 7An example of a network device 700 according to an embodiment of the present application is shown. The network device 700 is configured to implement some embodiments of the present application. Some embodiments of the present application can be implemented in the network device 700 using any appropriately configured hardware and / or software. The network device 700 may include a memory 701, a transceiver 702, and a processor 703 coupled to the memory 701 and the transceiver 702. The processor 703 may be configured to implement the functions, processes and / or methods proposed in this specification. The radio interface protocol layer may be implemented in the processor 703. The memory 701 is operatively coupled to the processor 703 and stores various information to operate the processor 703. The transceiver 702 is operatively coupled to the processor 703, and the transceiver 702 transmits and / or receives radio signals. The processor 703 may include an ASIC, other chipsets, logic circuits and / or data processing devices. The memory 701 may include ROM, RAM, flash memory, memory card, storage medium and / or other storage devices. The transceiver 702 may include a baseband circuit to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described herein. These modules may be stored in the memory 701 and executed by the processor 703. The memory 701 may be implemented within the processor 703 or external to the processor 703, in which case these modules may be communicatively coupled to the processor 703 via various means known in the art.

[0057] In some embodiments, the memory 701 stores executable instructions that, when executed by the processor 703, cause the processor 703 to implement operations including: receiving a first request indicating QoS parameters associated with a list of time windows for AAMDT; and selecting an AAMDT policy based on the QoS parameters. In some embodiments, the memory 701 stores executable instructions that, when executed by the processor 703, cause the processor 703 to implement operations including: receiving a first request to create or update an AAMDT policy based on QoS parameters associated with a list of time windows for AAMDT; and deriving a set of PCC rules based on the AAMDT policy, which set of PCC rules is used for the AAMDT. In some embodiments, the network device 700 is configured to perform the above method. This can solve these and other problems in the prior art, and / or meet the QoS requirements for application AI / ML data transmission.

[0058] Figure 8 A wireless communication architecture configured to implement some embodiments presented herein is shown. Figure 8It is shown that in some embodiments, in the wireless communication architecture, network functions communicate with each other through a service-based interface in a core network (CN). The UE can communicate with the core network to establish control signaling and enable the UE to use services from the CN. Examples of control signaling functions are registration, connection and mobility management, authentication and authorization, session management, etc. After the control signaling has been established, the UE can use the user plane function to send data to a data network (DN) (e.g., the Internet) and receive data from the DN.

[0059] In some examples, the wireless communication architecture may include the following network functions (NF): authentication server function (AUSF), access and mobility management function (AMF), data network (DN) (such as operator service, Internet access or third-party service), network exposure function (NEF), network repository function (NRF), network slice specific and independent non-public network (SNPN) authentication and authorization function (NSSAAF), network slice selection function (NSSF), policy control function (PCF), session management function (SMF), unified data management (UDM), user plane function (UPF), application function (AF), user equipment (UE), (radio) access network ((R)AN), etc.

[0060] The following description emphasizes Figure 8 Some of the capabilities of the network function (NF) involved in control signaling.

[0061] Access and Mobility Function (AMF): The UE sends N1 messages to the AMF through the RAN node to perform control plane signaling such as registration, connection management, mobility management, access authentication and authorization, etc.

[0062] Session Management Function (SMF): The SMF is responsible for session management involving establishment of PDU sessions to allow the UE to send data to a Data Network (DN) such as the Internet or to an application server and other session management related functions.

[0063] Policy and Control Function (PCF): PCF provides a policy framework for managing network behavior, accessing subscription information to make policy decisions, etc.

[0064] Authentication Service Function (AUSF): AUSF supports authentication of UEs for 3GPP and untrusted non-3GPP accesses.

[0065] Unified Data Management / Repository (UDM / UDR): UDM / UDR supports 3GPP AKA authentication credential generation, user identity processing, subscription management and storage, etc.

[0066] Network Slice Selection Function (NSSF): NSSF is involved in various aspects of network slice management, such as selecting a network slice instance for a UE, managing NSSAI, etc.

[0067] Network Repository Function (NRF): NRF supports service discovery functionality in 5G networks.

[0068] Network Exposure Function (NEF): NEF supports opening up capabilities and events in the core network to third parties, application functions (AF), edge computing, etc.

[0069] The RAN node provides communication access from the UE to the core network for control plane and user plane communications. The UE establishes a PDU session with the CN to send data traffic on the user plane through the (R)AN and UPF nodes of the 5G System (5GS). Uplink traffic is sent by the UE and downlink traffic is received by the UE using the established PDU session. Data traffic flows between the UE and the DN through the intermediate nodes (R)AN and UPF.

[0070] Example:

[0071] The intent of some embodiments of the present application is to extend the existing AAMDT data transmission mechanism to support planned and event-driven application AI / ML data transmission. Some embodiments of the present application may describe an extension to the AAMDT transmission strategy. The extension includes the ability to negotiate a list of time windows between the AF and the 5GC instead of just one time window currently defined. The extension also includes enhanced support for additional QoS parameters, not just the aggregate bit rate, specifically, such as the average and maximum packet delay for UL / DL, the average and maximum packet loss rate for UL / DL, and the guaranteed and maximum traffic rate for UL / DL.

[0072] Some embodiments of the present application also propose to enhance network performance analysis by NWDAF to support additional QoS performance analysis for at least one of the new QoS parameters (i.e., PDB, PLR, and traffic rate, etc.) as described below. PCF can subscribe to such analysis to assist in its decision to derive the AAMDT transmission policy for the selected time window.

[0073] 1. Overall average and maximum packet delay budget for UL / DL per UE per time window.

[0074] 2. The overall average and maximum packet loss rate of UL / DL for each UE in each time window.

[0075] 3. Overall average, minimum and maximum traffic rates of UL / DL per UE per time window.

[0076] Some embodiments of the present application also update the existing AAMDT negotiation process to support the ability of the AF to request an AAMDT time window list and additional QoS parameters. In addition, it clarifies the existing process of how the AIML AF discovers its serving NEF and the need for the NEF to authenticate / authorize the AIML AF. Finally, the solution clarifies the process of how AAMDT can be applied to existing or future PDU sessions.

[0077] In some examples, one or more negotiated AAMDT policies can be provided by the PCF to the AF via the NEF. The AF can select one of the one or more negotiated AAMDT policies and notify the PCF of the selected AAMDT transmission policy together with the AAMDT transmission reference ID. Before the expected time window for applying AI / ML data transmission begins, the AF can initiate an AF request to the PCF to apply the selected AAMDT transmission policy to the PDU session of the selected target UE. The PCF can determine the appropriate PCC rules based on the negotiated AAMDT transmission policy for each of these PDU sessions.

[0078] Example: Extension of the AAMDT mechanism to support application layer data transfer

[0079] In some examples, in order to enable the AF to indicate a desired list of time windows for AAMDT, the input parameters of Nnef_AAMDTPNegotiation_Create are extended to support a desired list of time windows and additional QoS parameters (e.g., PDB, PLR, etc.) for specific application AI / ML data transmission requested by the AF. The current AAMDT data transmission policy does not support separate QoS parameters other than the maximum aggregate bit rate. Some embodiments of the present application propose to enhance the AAMDT transmission policy to be used as an AAMDT transmission policy with at least one of the following additional QoS parameters:

[0080] 1. Average and maximum packet delay for UL / DL per UE per time window.

[0081] 2. The average and maximum packet loss rate of UL / DL for each UE in each time window.

[0082] 3. Guaranteed and maximum traffic rates for UL / DL per UE per time window.

[0083] In some examples, during the AAMDT transmission policy negotiation and before the activation process, the PCF can subscribe to the NWDAF for network performance analysis to collect performance statistics and derive performance predictions for these QoS parameters. Based on the analysis report, the PCF can propose to renegotiate the AAMDT transmission policy before activating the corresponding AAMDT time window.

[0084] In some examples, to enhance network performance analysis to report predictions of QoS performance, the solution proposes to add the following input parameters to the network performance analysis together with the performance data of the UE collected from the AF as shown in Table 1 below, so as to enable the NWDAF to derive an extended network performance analysis for a set of QoS performance statistics and predictions corresponding to a specific time window: i.e., an identification of the target application for analyzing the information, i.e., the application ID, and the corresponding IP address / FQDN.

[0085] Table 1: Performance data from AF

[0086] Based on the above input parameters, in some examples, NWDAF can directly subscribe to "performance data from AF" for trusted AF by calling Naf_EventExposure_Subscribe service (event ID = performance data, event filtering information = area of ​​interest, application ID), or indirectly subscribe to "performance data from AF" for untrusted AF via NEF by calling Nnef_EventExposure_Subscribe service (event ID = performance data, event filtering information = area of ​​interest, application ID), wherein NEF converts the area of ​​interest into a geographic area identifier, so as to derive performance statistics and prediction indicators for the following new QoS parameters, wherein the following new QoS parameters correspond to exemplary specific expected time windows:

[0087] 1. Maximum / average packet delay for UL / DL per UE per time window.

[0088] 2. Maximum / average packet loss rate of UL / DL per UE in each time window.

[0089] 3. Maximum / minimum / average traffic rate of UL / DL per UE per time window.

[0090] In some examples, the PCF may reference such performance analysis information to derive PCC rules for a UE that participates in AAMDT operations.

[0091] Example: AAMDT negotiation for future PDU sessions to support application layer data transfer

[0092] Some examples are presented to further clarify how to leverage the existing AAMDT procedures for negotiation of future background data transfers to support application data transfers.Before establishing a PDU session to support AAMDT within a specific time window, the AF initiates a request to its serving NEF to (renegotiate) the AAMDT policy that would have been pre-provisioned in the UDR.

[0093] Fig. 9 AAMDT policy negotiation is shown for future PDU sessions to support application layer data transmission configured to implement some embodiments presented herein. Fig. 9 The process shown may support negotiation for future background data transmission and / or the AAMDT mechanism as proposed in some embodiments of the present application. The following description focuses on changes to the current process:

[0094] Prior to the transmission of application AI / ML data within a specific time window, the AF negotiates with the 5G Core an AAMDT transmission policy that applies to its given application AI / ML data transmission corresponding to an authorized third party (i.e., the AF). The AF is required to discover its serving NEF using a mechanism as predefined in the 3GPP specification, if the AF has not already done so.

[0095] Fig. 9 The process shown may include at least one of the following operations. These operations may be performed in parallel or sequentially.

[0096] In step 1a, the parameter list of the Nnef_AAMDTNegotiation_Create request from the AF may include a list of desired time windows, and the AI / ML AF may also include latency and reliability requirements for specific application AI / ML operations as in some embodiments above.

[0097] In step 1b, the NEF may authenticate the AF and authorize the AAMDT request from the AF. If the given AF is not authenticated and authorized, the NEF may reject the AF's request through a Nnef_AAMDTNegotiation_Create response and skip the following steps.

[0098] In step 2, the parameter list of the Npcf_AAMDTPolicyControl_Create request from the AF may include a list of desired time windows, and the NEF includes added latency and reliability requirements for specific application AI / ML operations, if these requirements have been received from the AF.

[0099] QoS parameters such as PDB and PLR may also be provided by the UDR to the PCF as part of the AAMDT policy in step 4. This step may occur if the PCF (or another PCF) has received delay and reliability requirements from the AF / NEF in a previous AAMDT negotiation of these requirements, which are described in the form of QoS parameters such as PDB and PLR and stored in the UDR.

[0100] In steps 5 and 6, the PCF refers to the requested QoS requirements specified by the AF. As described in the current step 5, the PCF can subscribe to the NWDAF to request network area information and network performance analysis, which is for the performance of the QoS parameter group for each expected time window from the list. The PCF can determine QoS parameters such as PDB, PLR based on the QoS requirements from the AF for the corresponding expected time window, and the corresponding expected time window can be based on the report of the network performance analysis to be included in the set of AAMDT transmission policies. The PCF can also invalidate some old AAMDT transmission policies. The PCF sends the final set of AAMDT transmission policies to the AF via the NEF together with the AAMDT transmission reference ID.

[0101] After AAMDT transmission policy negotiation, if the AF decides to select another AAMDT transmission policy (e.g., data rate reduction, relaxation of delay constraints for scheduled and event-driven traffic, etc.), the AF may trigger step 8 to update the corresponding PCF via the NEF with support for the newly selected AAMDT transmission policy.

[0102] In step 12, additional QoS parameters may be added by the PCF to the UDR as part of the updated AAMDT policy.

[0103] Example: Activate or update / remove AAMDT transmission policy to a PDU session

[0104] Some examples may describe two ways to apply a negotiated AAMDT transmission policy for a given application AI / ML data transmission to a PDU session of a given UE, namely, (a) activating the AAMDT transmission policy as described in clause 4.2 above to the PDU session; and (b) adding the PDU session of the target UE to the desired AAMDT time window by applying the AAMDT transmission policy.

[0105] In some examples, in order to activate a previously negotiated AAMDT transmission policy to a PDU session to support application AI / ML data transmission, the AF triggers Npcf_PolicyAuthorization_Create / Update via the NEF or directly to the PCF before the expected time window for AAMDT transmission begins. The AF can discover the PCF via the BSF (possibly via the NEF) by calling Nbsf_Management_Discovery. In both cases, the PCF can utilize the negotiated AAMDT transmission policy to generate PCC rules to support the establishment of future PDU sessions. Further details on how to apply the previously negotiated AAMDT transmission policy can refer to the predefined methods in the 3GPP specifications.

[0106] In some examples, if a PDU session has already been established and the AF wishes to apply / update / delete an AAMDT transmission policy to such an existing PDU session so that a separate UE supports application AI / ML data transmission, the AF directly calls the Npcf_PolicyAuthorization_Create / Update service to the PCF (via the N5 interface). The AF can discover the PCF via the BSF by calling Nbsf_Management_Discovery. The AF also provides the AAMDT reference ID along with the AF session information to the PCF serving the PDU session. The PCF authorizes the AF request. If the PCF determines that the AF cannot be authorized, the PCF rejects the AF request. Once the PCF authorizes the AF request, and if the AF requests to apply or update the PDU session using the AAMDT transmission policy, the PCF retrieves the corresponding AAMDT transmission policy from the UDR to derive the PCC rules for AAMDT based on the transmission policy. In addition, the AF can specify separate QoS parameters that are different from the AAMDT transmission policy. The PCF then updates the SMF with the corresponding new PCC rules, where the SM policy association modification process initiated by the PCF can be predefined in the 3GPP specification. Further details on how the AF applies the AAMDT transmission policy to an existing session may be predefined in the 3GPP specifications.

[0107] In some examples, if the AF wishes to remove the AAMDT transport policy for a PDU session for a given UE, the AF invokes the Npcf_PolicyAuthorization_Delete service directly to the PCF. The AF also provides the AAMDT reference ID along with the AF session information to the PCF serving the PDU session. The PCF authorizes the AF request as described above before removing the PDU session from AAMDT.

[0108] Fig.10 The application / update / remove of negotiated AAMDT policies to a PDU session is shown to support application AI / ML data transmission configured to implement some embodiments presented herein. Fig.10 The process shown may include at least one of the following operations. These operations may be performed in parallel or sequentially.

[0109] Step 1. If the AF decides to apply / update / delete the AAMDT policy for a given application AI / ML data transmission for a PDU session, the AF shall provide the AAMDT reference ID together with the AF session information to the PCF serving the PDU session (via the N5 interface) for the target UE when the data transmission is about to start. Note that the AF may need to discover the serving PCF of the UE via the NEF with the support of the BSF. The Npcf_PolicyAuthorization_Create / Update / Delete service may be predefined in the 3GPP specification and used to authorize AF requests and for creating a policy for the PDU session to which the AF session is bound as requested by the authorized AF. More specifically, the added latency and reliability requirements may be predefined in the 3GPP specification and included in the AI / ML AF request.

[0110] Step 2. PCF authorizes AF request.

[0111] Step 3. If the PCF determines that the AF cannot be authorized, the PCF rejects the AF request by including the rejection in the Npcf_PolicyAuthorization_Create / Update / Delete response. Skip all subsequent steps below.

[0112] Step 4 to Step 5. Once the PCF authorizes the AF request, if the AF requests to create or update an AAMDT policy for a given PDU session, the PCF retrieves the corresponding AAMDT policy from the UDR to derive PCC rules for AAMDT based on the pre-provisioned transport policy, which may include a Flock QoS policy consideration with minimum QoS requirements. In addition, the AF may specify an additional QoS policy to replace the AAMDT policy for a given PDU session.

[0113] Step 6. The PCF updates the SMF using the corresponding new PCC rules, where the SM policy association modification process initiated by the PCF is predefined in the 3GPP specification.

[0114] Further details on how PCC rules are applied to future or existing PDU sessions may be predefined in the 3GPP specifications.

[0115] Example: QoS sustainability and user data congestion analysis support for AAMDT warning notifications

[0116] In some examples, to ensure that sufficient network resources are available to support AAMDT when the transmission window is approaching, the solution proposes to extend the AAMDT warning notification process predefined in the 3GPP specification to extend to utilize QoS sustainability analysis as predefined in the 3GPP specification to evaluate the possibility of QoS changes in a future analysis target period in a specific area. The proposed updates to the predefined 3GPP specification can be shown in "bold italics" below.

[0117] In summary, in order to enable MNOs to assist ASPs in transmitting their application AI / ML traffic in a more controlled schedule taking into account the availability of network resources, some embodiments of the present application propose to extend the existing AAMDT mechanism to support pre-negotiation between AF and 5G system (5GS) to agree on a target time window, which is selected from a list of time windows with expected QoS performance that meets the QoS requirements of specific application AI / ML data transmission. The current AAMDT mechanism only supports negotiation of a single desired time window. In addition, the current AAMDT mechanism only supports aggregate bit rate and does not support other QoS parameters (i.e., packet delay buffer, packet loss rate, and packet flow rate). Some embodiments of the present application propose a new mechanism called AAMDT to support negotiation of a list of time windows between AF and 5GC, where the list of desired time windows can be based on a previous service level agreement (SLA) between ASP and MNO for traffic transmission to support planned and event-driven application AI / ML traffic. In addition, in some embodiments, each of these requested desired time windows may not only be associated with an aggregate bit rate, but instead, they are associated with specific QoS parameters requested by the AF (i.e., packet delay buffer, packet loss rate, and packet flow rate). In addition, in order to be able to highly guarantee that the 5G system can grant the expected time window for the request of the AF, wherein the request of the AF is for the application AI / ML data transmission with the required QoS parameters, some embodiments of the present application propose to expand the existing network performance analysis from the NWDAF to support the QoS performance analysis of additional QoS parameters (i.e., packet delay buffering, packet loss rate, and packet flow rate) so as to derive a list of expected time windows with their corresponding QoS performance. Such analysis reports can help assist the PCF to derive appropriate PCC rules for the corresponding PDU session requested by the AF to support specific application AI / ML data transmission.

[0118] The commercial benefits of some embodiments are as follows. 1. Solve problems and other problems in the prior art. 2. Meet the QoS requirements of application AI / ML data transmission. Some embodiments of the present application can be used in many applications. Some embodiments of the present application are used by the following: chipset suppliers, video system development suppliers, automobile manufacturers (including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc.), drones (unmanned aerial vehicles), smart phone manufacturers, communication equipment for public safety purposes, AR / VR / MR equipment manufacturers (such as games, conferences / seminars, educational purposes). Some embodiments of the present application are a combination of "techniques / processes" that can be adopted in video standards to create final products. Some embodiments of the present application propose technical mechanisms. At least one proposed solution, method, system and device of some embodiments of the present application can be used for current and / or new / future standards for communication systems such as UE, base station, network equipment and / or communication systems. Compatible products follow at least one proposed solution, method, system and device of some embodiments of the present application. The proposed solutions, methods, systems and devices are widely used in UE, base station, network equipment and / or communication systems. With the implementation of at least one proposed solution, method, system and apparatus of some embodiments of the present application, at least one modification / improvement of the method and apparatus for data transmission is considered for standardization.

[0119] Fig.11 is an example of a computing device 1100 according to an embodiment of the present application. Any suitable computing device can be used to perform the operations described herein. For example, Fig.11 The present invention can be implemented using any suitably configured hardware and / or software. Figures 1 to 10 An example of a computing device 1100 of the apparatus and / or method shown in . In some embodiments, the computing device 1100 can include a processor 1112 that is communicatively coupled to a memory 1114 and executes computer executable program code and / or accesses information stored in the memory 1114. The processor 1112 may include a microprocessor, an application specific integrated circuit ("ASIC"), a state machine, or other processing device. The processor 1112 can include any of a plurality of processing devices, including a processing device. Such a processor may include a computer-readable medium storing instructions, or may communicate with a computer-readable medium storing instructions that, when executed by the processor 1112, cause the processor to perform the operations described herein.

[0120] Memory 1114 can include any suitable non-transient computer-readable medium. Computer-readable media can include any electronic, optical, magnetic or other storage device that can provide computer-readable instructions or other program codes to the processor. Non-limiting examples of computer-readable media include disks, memory chips, ROMs, RAMs, ASICs, configured processors, optical storage devices, tapes or other magnetic storage devices, or any other medium from which a computer processor can read instructions. Instructions can include processor-specific instructions generated by a compiler and / or interpreter from a code written in any suitable computer programming language, including, for example, C, C++, C#, visual basic, java, python, perl, javascript, and actionscript.

[0121] The computing device 1100 may also include a bus 1116. The bus 1116 may communicatively couple one or more components of the computing device 1100. The computing device 1100 may also include a plurality of external or internal devices, such as input or output devices. For example, the computing device 1100 is shown as having an input / output ("I / O") interface 1118 that may receive input from one or more input devices 1120 or provide output to one or more output devices 1122. One or more input devices 1120 and one or more output devices 1122 may be communicatively coupled to the I / O interface 1118. The communicative coupling may be achieved via any suitable means (e.g., connection via a printed circuit board, connection via a cable, communication via wireless transmission, etc.). Non-limiting examples of the input device 1120 include a touch screen (e.g., one or more cameras for imaging a touch area or a pressure sensor for detecting pressure changes caused by a touch), a mouse, a keyboard, or any other device capable of generating input events in response to a physical action of a user of the computing device. Non-limiting examples of output device 1122 include a liquid crystal display (LCD) screen, an external monitor, speakers, or any other device that can be used to display or otherwise present output generated by the computing device.

[0122] The computing device 1100 can execute program code that configures the processor 1112 to perform the above Figures 1 to 10 One or more of the operations described in some embodiments shown in . The program code may reside in the memory 1114 or any suitable computer-readable medium and may be executed by the processor 1112 or any other suitable processor.

[0123] The computing device 1100 can also include at least one network interface device 1124. The network interface device 1124 can include any device or group of devices suitable for establishing a wired or wireless data connection to one or more data networks 1128. Non-limiting examples of the network interface device 1124 include an Ethernet adapter, a modem, etc. The computing device 1100 can transmit messages as electrical or optical signals via the network interface device 1124.

[0124] Fig.12 1 is a block diagram of an example of a communication system 1200 according to an embodiment of the present application. The embodiments described herein may be implemented into the communication system 1200 using any appropriately configured hardware and / or software. Fig.12 A communication system 1200 is shown, which includes a radio frequency (RF) circuit 1210, a baseband circuit 1220, an application circuit 1230, a memory / storage device 1240, a display 1250, a camera 1260, a sensor 1270, and an input / output (I / O) interface 1280 that are coupled to each other as shown.

[0125] Application circuit 1230 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (such as graphics processors, application processors). The processor may be coupled to a memory / storage device and configured to execute instructions stored in the memory / storage device to enable various applications and / or operating systems to run on the system. Communication system 1200 is capable of executing program code that configures application circuit 1230 to perform the above-mentioned Figures 1 to 10 One or more of the operations described. The program code may reside in the application circuit 1230 or any suitable computer-readable medium and may be executed by the application circuit 1230 or any other suitable processor.

[0126] The baseband circuit 1220 may include circuits, such as but not limited to one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuit may handle various radio control functions that may enable communication with one or more radio networks via RF circuits. The radio control functions may include but are not limited to signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuit may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit may support communications with an evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), and wireless personal area networks (WPAN). An embodiment in which the baseband circuit is configured to support radio communications of more than one wireless protocol may be referred to as a multi-mode baseband circuit.

[0127] In various embodiments, the baseband circuit 1220 may include circuits that operate using signals that are not strictly considered to be in the baseband frequency. For example, in some embodiments, the baseband circuit may include circuits that operate using signals having an intermediate frequency, which is between the baseband frequency and the radio frequency. The RF circuit 1210 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, the RF circuit may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. In various embodiments, the RF circuit 1210 may include circuits that operate using signals that are not strictly considered to be in the radio frequency. For example, in some embodiments, the RF circuit may include circuits that operate using signals having an intermediate frequency, which is between the baseband frequency and the radio frequency.

[0128] In various embodiments, the above Figures 1 to 10The transmitter circuit, control circuit or receiver circuit discussed in the apparatus and / or method shown in the embodiment may be embodied in whole or in part in one or more of the RF circuit, baseband circuit and / or application circuit. As used herein, "circuit" may refer to, may be part of or may include an ASIC, electronic circuit, processor (shared, dedicated or group) and / or memory (shared, dedicated or group) that executes one or more software or firmware programs, combinational logic circuits and / or other suitable hardware components that provide the functions described. In some embodiments, the electronic device circuit may be implemented in one or more software or firmware modules, or the functions associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuit, application circuit and / or memory / storage device may be implemented together on a system on a chip (system on a chip, SOC). The memory / storage device 1240 may be used to load and store data and / or instructions, for example, for the system. The memory / storage for one embodiment may include any combination of suitable volatile memory (such as dynamic random access memory (DRAM)) and / or non-volatile memory (such as flash memory).

[0129] In various embodiments, the I / O interface 1280 may include one or more user interfaces designed to implement the interaction between the user and the system and / or a peripheral component interface designed to implement the interaction between the peripheral component and the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (universal serial bus, USB) port, an audio jack, and a power interface. In various embodiments, the sensor 1270 may include one or more sensing devices to determine environmental conditions and / or location information related to the system. In some embodiments, the sensor may include, but is not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be a part of or interact with a baseband circuit and / or an RF circuit to communicate with a component of a positioning network (e.g., a global positioning system (global positioning system, GPS) satellite).

[0130] In various embodiments, the display 1250 may include a display such as a liquid crystal display and a touch screen display. In various embodiments, the communication system 1200 may be a mobile computing device, such as but not limited to a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smart phone, AR / VR glasses, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

[0131] It is understood by those of ordinary skill in the art that each of the units, algorithms, and steps described and disclosed in the embodiments of the present application is implemented using electronic hardware or a combination of software and electronic hardware for a computer. Whether the function is run in hardware or in software depends on the conditions of the application and the design requirements of the technical solution. Those of ordinary skill in the art can use different ways to implement the functions of each specific application, and such implementation should not exceed the scope of the present application. It is understood by those of ordinary skill in the art that since the working processes of the above-mentioned systems, devices, and units are basically the same, reference can be made to the working processes of the systems, devices, and units in the above-mentioned embodiments. For ease of description and simplicity, these working processes will not be described in detail.

[0132] It is understood that the disclosed systems, devices and methods in the embodiments of the present application can be implemented in other ways. The above embodiments are exemplary only. The division of units is based only on logical functions, and there are other divisions in the implementation. Multiple units or components can be combined or integrated in another system. It is also possible to omit or skip some features. On the other hand, the mutual coupling, direct coupling or communication coupling shown or discussed is operated indirectly or communicatively in the form of electrical, mechanical or other types through some ports, devices or units.

[0133] The units used as separate components for explanation are physically separated or not physically separated. The units used for display are physical units or not physical units, i.e. located in one place or distributed on multiple network units. Some or all of the units are used according to the purpose of the embodiment. In addition, each functional unit in each embodiment can be integrated into a physically independent processing unit, or can be integrated into one processing unit with two or more units.

[0134] If the software functional unit is implemented, used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical solution proposed in the present application can be implemented substantially or partially in the form of a software product. Alternatively, a part of the technical solution that is beneficial to conventional technology can be implemented in the form of a software product. The software product in the computer is stored in a storage medium that includes multiple commands for a computing device (such as a personal computer, a server or a network device) to run all or some of the steps disclosed by the embodiments of the present application. The storage medium includes a USB disk, a mobile hard disk, a ROM, a RAM, a floppy disk or other types of media capable of storing program code.

[0135] While the present application has been described in connection with what is considered to be the most practical and preferred embodiment, it is to be understood that the application is not limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

1. A wireless communication method for data transmission, characterized in that: The method comprises: The functional entity receives a first request indicating a quality of service QoS parameter, wherein the QoS parameter is associated with a time window list for application of artificial intelligence AI / machine learning ML data transmission AAMDT; The functional entity selects an AAMDT policy based on the QoS parameters.

2. The method according to claim 1, characterized in that The functional entity is a Policy Control Function (PCF) entity.

3. The method according to claim 1 or 2, characterized in that: The first request is an AAMDT policy control request, and the first request is a request from an application function AF and via a network exposure function NEF entity.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The functional entity requests a network performance analysis associated with the QoS parameter.

5. The method according to claim 4, characterized in that The AAMDT strategy is selected based on the network performance analysis.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The functional entity sends the AAMDT transmission policy.

7. The method according to claim 6, characterized in that The AAMDT transmission policy is sent to the Application Function AF.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: The functional entity receives a second request to create or update the AAMDT policy.

9. The method according to claim 8, characterized in that The second request is an application function AF request, the AAMDT policy is associated with AAMDT for a protocol data unit PDU session, the PDU being serviced by the functional entity.

10. The method according to claim 8 or 9, characterized in that: The method further comprises: The functional entity attempts to authorize the second request.

11. The method according to any one of claims 8 to 10, characterized in that The method further comprises: The functional entity retrieves the AAMDT policy from the User Data Repository UDR entity.

12. The method according to claim 11, characterized in that The method further comprises: The functional entity derives a set of policy and charging control PCC rules based on the AAMDT policy, and the set of PCC rules is used for the AAMDT.

13. The method according to claim 12, characterized in that The method further comprises: The functional entity initiates a session management (SM) policy association modification with a session management function (SMF) entity based on the set of PCC rules.

14. The method according to any one of claims 1 to 13, characterized in that The QoS parameters include an aggregate bit rate GBR and at least one of a packet delay buffer PDB, a packet loss rate PLR ​​and a traffic rate.

15. A wireless communication method for data transmission, characterized in that: The method comprises: The functional entity receives a first request to create or update an application artificial intelligence AI / machine learning ML data transmission AAMDT policy based on a quality of service QoS parameter, wherein the QoS parameter is associated with a time window list for AAMDT; The functional entity derives a set of policy and charging control PCC rules based on the AAMDT policy, and the set of PCC rules is used for the AAMDT.

16. The method according to claim 15, characterized in that The functional entity is a Policy Control Function (PCF) entity.

17. The method according to claim 15 or 16, characterized in that The first request is an application function AF request, the AAMDT policy is associated with AAMDT for a protocol data unit PDU session, the PDU session is served by the functional entity.

18. The method according to any one of claims 15 to 17, characterized in that The method further comprises: The functional entity attempts to authorize the second request.

19. The method according to any one of claims 15 to 18, characterized in that The method further comprises: The functional entity retrieves the AAMDT policy from a User Data Repository UDR entity.

20. The method according to any one of claims 15 to 19, characterized in that The method further comprises: The functional entity initiates a session management (SM) policy association modification with a session management function (SMF) entity based on the set of PCC rules.

21. The method according to any one of claims 15 to 20, characterized in that The method further comprises: The functional entity receives a second request, the second request indicating the QoS parameter.

22. The method according to any one of claims 15 to 21, characterized in that The method further comprises: The functional entity selects the AAMDT policy based on the QoS parameters.

23. The method according to claim 21 or 22, characterized in that The second request is an AAMDT policy control request, and the second request is a request from an application function AF via a network exposure function NEF entity.

24. The method according to any one of claims 15 to 23, characterized in that The method further comprises: The functional entity requests a network performance analysis associated with the QoS parameter.

25. The method according to claim 24, characterized in that The AAMDT strategy is selected based on the network performance analysis.

26. The method according to any one of claims 15 to 25, characterized in that The method further comprises: The functional entity sends the AAMDT transmission policy.

27. The method according to claim 26, characterized in that The AAMDT transmission policy is sent to the Application Function AF.

28. The method according to any one of claims 15 to 27, characterized in that The QoS parameters include an aggregate bit rate GBR and at least one of a packet delay buffer PDB, a packet loss rate PLR ​​and a traffic rate.

29. A wireless communication device, characterized in that: The wireless communication device comprises: A transceiver configured to receive a first request indicating a quality of service QoS parameter associated with a time window list for application artificial intelligence AI / machine learning ML data transmission AAMDT; A selector is configured to select an AAMDT policy based on the QoS parameters.

30. The wireless communication device according to claim 29, wherein: The wireless communication device is a policy control function PCF entity.

31. The wireless communication device according to claim 29 or 30, characterized in that: The first request is an AAMDT policy control request, and the first request is a request from an application function AF and via a network exposure function NEF entity.

32. The wireless communication device according to any one of claims 29 to 31, characterized in that: The selector is further configured to request a network performance analysis associated with the QoS parameters.

33. The wireless communication device according to claim 32, characterized in that The AAMDT strategy is selected based on the network performance analysis.

34. The wireless communication device according to any one of claims 29 to 33, characterized in that: The transceiver is further configured to transmit an AAMDT transmission policy.

35. The wireless communication device according to claim 34, characterized in that The AAMDT transmission policy is sent to the Application Function AF.

36. The wireless communication device according to any one of claims 29 to 35, characterized in that: The transceiver is further configured to receive a second request to create or update the AAMDT policy.

37. The wireless communication device according to claim 36, wherein: The second request is an application function AF request, and the AAMDT policy is associated with AAMDT for a protocol data unit PDU session, and the PDU session is served by the wireless communication device.

38. The wireless communication device according to claim 36 or 37, characterized in that: The selector is further configured to attempt to authorize the second request.

39. The wireless communication device according to any one of claims 36 to 38, characterized in that: The selector is also configured to retrieve the AAMDT policy from a user data repository UDR entity.

40. The wireless communication device according to claim 39, wherein: The selector is further configured to derive a set of policy and charging control (PCC) rules based on the AAMDT policy, the set of PCC rules being used for the AAMDT.

41. The wireless communication device according to claim 40, characterized in that The selector is further configured to initiate a session management (SM) policy association modification with a session management function (SMF) entity based on the set of PCC rules.

42. The wireless communication device according to any one of claims 29 to 41, characterized in that: The QoS parameters include an aggregate bit rate GBR and at least one of a packet delay buffer PDB, a packet loss rate PLR ​​and a traffic rate.

43. A wireless communication device, characterized in that: The wireless communication device comprises: A transceiver configured to receive a first request to create or update an application artificial intelligence (AI) / machine learning (ML) data transmission (AAMDT) policy based on a quality of service (QoS) parameter, the QoS parameter being associated with a time window list for AAMDT; The exporter is configured to export a set of policy and charging control PCC rules based on the AAMDT policy, wherein the set of PCC rules is used for the AAMDT.

44. The wireless communication device according to claim 43, characterized in that The wireless communication device is a policy control function PCF entity.

45. The wireless communication device according to claim 43 or 44, characterized in that: The first request is an application function AF request, and the AAMDT policy is associated with AAMDT for a protocol data unit PDU session, and the PDU session is served by the wireless communication device.

46. ​​The wireless communication device according to any one of claims 43 to 45, characterized in that: The exporter is further configured to attempt to authorize the second request.

47. The wireless communication device according to any one of claims 43 to 46, characterized in that: The exporter is also configured to retrieve the AAMDT policy from a user data repository UDR entity.

48. The wireless communication device according to any one of claims 43 to 47, characterized in that: The exporter is further configured to initiate a session management (SM) policy association modification with a session management function (SMF) entity based on the set of PCC rules.

49. The wireless communication device according to any one of claims 43 to 48, characterized in that: The transceiver is further configured to receive a second request indicating the QoS parameter.

50. The wireless communication device of any one of claims 43 to 49, wherein the exporter is further configured to select the AAMDT policy based on the QoS parameters.

51. The wireless communication device according to claim 49 or 50, characterized in that: The second request is an AAMDT policy control request, and the second request is a request from an application function AF via a network exposure function NEF entity.

52. The wireless communication device according to any one of claims 43 to 51, characterized in that: The exporter is further configured to request a network performance analysis associated with the QoS parameters.

53. The wireless communication device according to claim 52, characterized in that The AAMDT strategy is selected based on the network performance analysis.

54. The wireless communication device according to any one of claims 43 to 53, characterized in that: The transceiver is further configured to transmit an AAMDT transmission policy.

55. The wireless communication device according to claim 54, characterized in that The AAMDT transmission policy is sent to the Application Function AF.

56. The wireless communication device according to any one of claims 43 to 55, characterized in that: The QoS parameters include an aggregate bit rate GBR and at least one of a packet delay buffer PDB, a packet loss rate PLR ​​and a traffic rate.

57. A network device, characterized in that: The network equipment includes: Memory; Transceiver; a processor coupled to the memory and the transceiver; The network device is configured to perform the method according to any one of claims 1 to 28.

58. A non-transitory machine-readable storage medium, characterized in that The non-transitory machine-readable storage medium has instructions stored thereon that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 28.

59. A chip, characterized in that: The chip comprises: A processor, wherein the processor is configured to call and run a computer program stored in a memory so as to enable a device equipped with the chip to perform a method as claimed in any one of claims 1 to 28.

60. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which enables a computer to execute the method according to any one of claims 1 to 28.

61. A computer program product, characterized in that The computer program product comprises a computer program, which causes a computer to execute the method according to any one of claims 1 to 28.

62. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 28.

Images