Apparatus and wireless communication method for session group

Abstract

A wireless communication method for a session group includes a network open function (NEF) receiving an AF session creation request from an application function (AF), where the AF session creation request is associated with an AF session group and one or more Quality of Service (QoS) parameters; the NEF divides the AF session creation request into one or more first requests, where the one or more first requests are associated with one or more user equipments (UEs).

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 63 / 444,773, filed on February 10, 2023, which is incorporated by reference in its entirety into this disclosure. Technical Field

[0002] The present disclosure relates to the field of communication systems, and more particularly, to an apparatus and wireless communication method for a conversation group, such as supporting quality-of-service (QoS) flow resource allocation and QoS monitoring for an application function (AF) conversation group. Background Art

[0003] Currently, the 3rd Generation Partnership Project (3GPP) is working on standardization activities for Application Function (AF) sessions. However, in the prior art, an AF can only request resource allocation and QoS monitoring for a single AF session. Enhancements to AF session groups and related parameters remain unclear. Therefore, there is a need for apparatus and communication methods for session groups, such as those that support QoS flow resource allocation and QoS monitoring for AF session groups. Summary of the Invention

[0004] The present disclosure aims to provide an apparatus and wireless communication method for a session group, such as supporting QoS flow resource allocation and QoS monitoring for an AF session group, to address these and other issues in the prior art and / or reduce signaling overhead between the AF and a network such as the 5G core network (5GC). The present disclosure aims to reduce signaling overhead between the AF and a network such as the 5G core network (5GC).

[0005] In a first aspect of the present disclosure, a wireless communication method for a session group includes: a network exposure function (NEF) receiving an AF session creation request from an application function (AF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and the NEF dividing the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipment (UE).

[0006] In a second aspect of the present disclosure, a wireless communication method for a session group includes: an application function (AF) sends an AF session creation request to a network exposure function (NEF), wherein the AF session creation request is associated with the AF session group and one or more quality of service (QoS) parameters; and requesting the NEF to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments (UEs).

[0007] In a third aspect of the present disclosure, a wireless communication device includes: a receiver configured to receive an AF session creation request from an application function (AF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and an executor configured to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments (UEs).

[0008] In a fourth aspect of the present disclosure, a wireless communication device includes: a transmitter, the transmitter being configured to send an application function (AF) session creation request to a network exposure function (NEF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and an executor, the executor being configured to request the NEF to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments (UEs).

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

[0010] In a sixth aspect of the present disclosure, a non-transitory machine-readable storage medium stores instructions, which, when executed by a computer, cause the computer to perform the above method.

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

[0012] In an eighth aspect of the present disclosure, a computer-readable storage medium stores a computer program for causing a computer to execute the above method.

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

[0014] In a tenth aspect of the present disclosure, a computer program causes a computer to execute the above method. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present disclosure or related technologies, the following briefly introduces the drawings described in the embodiments. Obviously, these drawings are only some embodiments of the present disclosure, and those skilled in the art can derive other drawings based on these drawings without inventive work.

[0016] Figure 1 is a block diagram of functional entities according to an embodiment of the present disclosure.

[0017] Figure 2 The present invention is a flowchart of a wireless communication method for a conversation group executed by a functional entity according to an embodiment of the present disclosure.

[0018] Figure 3 is a block diagram of functional entities according to an embodiment of the present disclosure.

[0019] Figure 4 The present invention is a flowchart of a wireless communication method for a conversation group executed by a functional entity according to an embodiment of the present disclosure.

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

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

[0022] Figure 7 is a block diagram of a network device according to an embodiment of the present disclosure.

[0023] Figure 8 is a block diagram illustrating a wireless communication architecture for implementing some embodiments proposed in the present disclosure.

[0024] Figure 9 is a flow chart illustrating an AF session group supporting QoS resource allocation and / or QoS monitoring for implementing some embodiments proposed in the present disclosure.

[0025] Figure 10 is a block diagram of an example of a computing device according to an embodiment of the present disclosure.

[0026] Figure 11 is a block diagram of a communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0027] The following describes in detail the technical points, structural features, objectives and effects of the embodiments of the present disclosure in conjunction with the accompanying drawings. Specifically, the terms in the embodiments of the present disclosure are only used to describe the purpose of specific embodiments, rather than to limit the present disclosure.

[0028] Some embodiments of the present disclosure introduce new Network Exposure Function (NEF) services to support network resource allocation and various QoS monitoring operations for AF session groups, which are established for a group of UEs selected by the AF. If authorization is obtained from the policy control function (PCF), each AF session in the group of UEs is allocated the same set of QoS resources requested by the AF. If QoS monitoring is also requested for the group, the group of QoS flows of the corresponding UEs in the group that participate in the same application will be monitored based on the request of the AF. The AF specifies one or more QoS parameters to be measured to indicate the type of QoS monitoring measurement (e.g., delay, jitter and / or data rate, etc.).

[0029] The NEF service coordinates the AF request for the AF session group and the response and notification of the corresponding 5G core network (5GC) network function (NF) between the AF and the 5GC. More specifically, the NEF verifies the authenticity of the AF's request, divides the AF's request for the AF session group into separate N5 requests, and identifies the appropriate service PCF of the UE for the AF session within the group to process the N5 request. The UE's service PCF further authorizes the N5 request before continuing to derive the policy and charging control (PCC) rules for the target QoS flow indicated in the AF's request. The UE's service PCF performs PCC rule binding with the target QoS flow requested by the AF, and with the support of the UE's service session management function (SMF), the PCF updates the N4 policy corresponding to the QoS resources and QoS monitoring configuration indicated to the UE's service user plane function (UPF).

[0030] When the AF requests QoS monitoring of the data rate of the group of QoS flows for the AF session group, the AF may also request monitoring of a group of QoS flows based on a specified maximum aggregate throughput, which is the group maximum bit rate (Group-MBR) threshold and is included in the AF request. If Group-MBR Monitoring is requested, the group for QoS monitoring of data rate reporting may be sent to the AF only when the aggregate bit rate exceeds the Group-MBR threshold. Otherwise, the group for QoS monitoring of data rate reporting may be sent to the AF based on the reporting frequency.

[0031] Table 1 below describes the mapping between the four types of new NEF service requests and N5 service requests.

[0032] Table 1

[0033] The group-MBR threshold is described as follows: The group-MBR threshold provides an upper limit on the aggregate bit rate of all GBR QoS flows corresponding to a set of protocol data unit (PDU) sessions of UEs participating in a group of transmissions (e.g., Federated Learning (FL) operations) with the user plane active. The anchor user plane function (UPF) of the group of transmissions (e.g., FL operations) measures the aggregate bit rate on the QoS flows selected by the group according to the group-MBR threshold provided by the associated anchor session management function (SMF) of the corresponding group of PDU sessions supporting the group of transmissions. The group-MBR is provided by the AF to initiate group-MBR monitoring for the set of QoS flows of a set of PDU sessions supporting a set of concurrent transmissions.

[0034] In the case of group QoS monitoring, the NEF shall only support either group-MBR monitoring or group reporting for the data rate of a single QoS flow, but not both. NOTE 1: If a group-MBR threshold is provided, the QoS parameter(s) to be measured indicate the provided bit rate. NOTE 2: When event reporting is used for group-MBR monitoring, the NEF shall provide a QoS flow data rate report for the group of UEs to the AF only if the group-MBR threshold is exceeded.

[0035] Figure 1An example of a functional entity 100 according to an embodiment of the present disclosure is shown. The functional entity 100 is configured to implement some embodiments of the present disclosure. Some embodiments of the present disclosure can be implemented in 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 proposed functions, processes, and / or methods described in this specification. The layers of the wireless interface protocol may be implemented in the processor 103. The memory 101 is operably coupled to the processor 103 and stores various information to operate the processor 103. The transceiver 102 is operably coupled to the processor 103, and the transceiver 102 transmits and / or receives wireless 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 the present disclosure may be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in the present disclosure. The modules may be stored in the memory 101 and executed by the processor 103. The memory 101 may be implemented inside the processor 103 or outside the processor 103, in which case the memory 101 may be communicatively coupled to the processor 103 via various means known in the art.

[0036] 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, by a network exposure function (NEF), an AF session creation request from an application function (AF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and dividing, by the NEF, the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments (UEs). This can address these and other issues in the prior art and / or reduce signaling overhead between the AF and a network such as a 5G core network (5GC).

[0037] Figure 2 A wireless communication method for a conversation group performed by a functional entity according to an embodiment of the present disclosure is shown. Figure 2is an example of a communication method 200 for a conversation group according to an embodiment of the present disclosure. The communication method 200 for a conversation group is configured to implement some embodiments of the present disclosure. Some embodiments of the present disclosure can be implemented into the communication method 200 for a conversation group using any appropriately configured hardware and / or software. In some embodiments, the communication method 200 for a conversation group includes: operation 202, a network exposure function (NEF) receives an AF session creation request from an application function (AF), wherein the AF session creation request is associated with an AF conversation group and one or more quality of service (QoS) parameters; and operation 204, the NEF divides the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipment (UE). This can solve these and other problems in the prior art and / or reduce the signaling overhead between the AF and a network such as a 5G core network (5GC).

[0038] In some embodiments, the one or more QoS parameters are associated with the AF session group. In some embodiments, the method further comprises the NEF mapping the one or more first requests into one or more second requests to one or more policy control function (PCF) entities. In some embodiments, the one or more second requests are one or more N5 requests. In some embodiments, the method further comprises the NEF determining one or more PCF entities serving the one or more UEs. In some embodiments, the AF session creation request comprises a set of UE addresses, an AF identifier (ID), flow description information, an external application ID, a QoS reference, one or more QoS parameters and / or one or more service requirements.

[0039] In some embodiments, the method further includes the AF requesting the NEF to allocate QoS dedicated resources and / or perform QoS monitoring for the AF session group. In some embodiments, the method further includes the NEF reporting one or more QoS flow-level events to the AF corresponding to the AF session group. In some embodiments, the method further includes the AF requesting the NEF to revoke the AF session group. In some embodiments, the method further includes the AF requesting the NEF to update a UE list for the AF session group, one or more service requirements for the AF session group, and / or a type of QoS monitoring operation.

[0040] Figure 3An example of a functional entity 300 according to an embodiment of the present disclosure is shown. Functional entity 300 is configured to implement some embodiments of the present disclosure. Some embodiments of the present disclosure can be implemented in functional entity 300 using any appropriately configured hardware and / or software. Functional entity 300 may include memory 301, transceiver 302, and a processor 303 coupled to memory 301 and transceiver 302. Processor 303 may be configured to implement the proposed functions, processes, and / or methods described in this specification. The layers of the wireless interface protocol may be implemented in processor 303. Memory 301 is operably coupled to processor 303 and stores various information to operate processor 303. Transceiver 302 is operably coupled to processor 303, and transceiver 302 transmits and / or receives wireless signals. Processor 303 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. Memory 301 may include read-only memory (ROM), random access memory (RAM), flash memory, a memory card, a storage medium, and / or other storage devices. Transceiver 302 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described in this disclosure may be implemented through modules (e.g., procedures, functions, etc.) that perform the functions described in this disclosure. The modules may be stored in memory 301 and executed by processor 303. Memory 301 may be implemented internally or externally to processor 303, in which case memory 301 may be communicatively coupled to processor 303 via various means known in the art.

[0041] In some embodiments, the memory 301 stores executable instructions, which, when executed by the processor 303, cause the processor 303 to implement operations, including: an application function (AF) sending an AF session creation request to a network exposure function (NEF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and requesting the NEF to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipment (UE).

[0042] Figure 4 A communication method for a conversation group performed by a functional entity according to an embodiment of the present disclosure is shown. Figure 4is an example of a communication method 400 for a conversation group according to an embodiment of the present disclosure. The communication method 400 for a conversation group is configured to implement some embodiments of the present disclosure. Some embodiments of the present disclosure can be implemented into the communication method 400 for a conversation group using any appropriately configured hardware and / or software. In some embodiments, the communication method 400 for a conversation group includes: operation 402, an application function (AF) sends an AF session creation request to a network exposure function (NEF), wherein the AF session creation request is associated with an AF conversation group and one or more quality of service (QoS) parameters; and operation 404, requesting the NEF to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipment (UE). This can solve these and other problems in the prior art and / or reduce the signaling overhead between the AF and a network such as a 5G core network (5GC).

[0043] In some embodiments, the one or more QoS parameters are associated with the AF session group. In some embodiments, the method further comprises requesting the NEF to map the one or more first requests into one or more second requests to one or more Policy Control Function (PCF) entities. In some embodiments, the one or more second requests are one or more N5 requests. In some embodiments, the method further comprises requesting the NEF to determine one or more PCF entities serving the one or more UEs. In some embodiments, the AF session creation request comprises a set of UE addresses, an AF identifier (ID), flow description information, an external application ID, a QoS reference, one or more QoS parameters and / or one or more service requirements.

[0044] In some embodiments, the method further includes requesting the NEF to allocate QoS dedicated resources and / or perform QoS monitoring for the AF session group. In some embodiments, the method further includes requesting the NEF to report one or more QoS flow-level events to the AF corresponding to the AF session group. In some embodiments, the method further includes requesting the NEF to revoke the AF session group. In some embodiments, the method further includes requesting the NEF to update a UE list for the AF session group, one or more service requirements for the AF session group, and / or a type of QoS monitoring operation.

[0045] Figure 5 A communication device according to an embodiment of the present disclosure is shown. Figure 5In some embodiments, a communication device 500 includes a receiver 501 and an executor 502. The receiver 501 is configured to receive an AF session creation request from an application function (AF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and the executor 502 is configured to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments (UEs). This can solve these and other problems in the prior art and / or reduce signaling overhead between the AF and a network such as a 5G core network (5GC).

[0046] In some embodiments, one or more QoS parameters are associated with an AF session group. In some embodiments, the executor 502 is configured to map the one or more first requests into one or more second requests to one or more policy control function (PCF) entities. In some embodiments, the one or more second requests are one or more N5 requests. In some embodiments, the executor 502 is configured to determine one or more PCF entities serving one or more UEs. In some embodiments, the AF session creation request includes a set of UE addresses, an AF identifier (ID), flow description information, an external application ID, a QoS reference, one or more QoS parameters, and / or one or more service requirements.

[0047] In some embodiments, the executor 502 is configured to allocate QoS dedicated resources for the AF session group and / or perform QoS monitoring. In some embodiments, the executor 502 is configured to report one or more QoS flow-level events to the AF corresponding to the AF session group. In some embodiments, the executor 502 is configured to revoke the AF session group. In some embodiments, the executor 502 is configured to update the UE list of the AF session group, one or more service requirements for the AF session group, and / or the type of QoS monitoring operation.

[0048] Figure 6 A communication device according to an embodiment of the present disclosure is shown. Figure 6 In some embodiments, a communication device 600 includes a transmitter 601 and an executor 602. The transmitter 601 is configured to send an application function (AF) session creation request to a network exposure function (NEF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters. The executor 602 is configured to request the NEF to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipment (UE). This can solve these and other problems in the prior art and / or reduce signaling overhead between the AF and a network such as a 5G core network (5GC).

[0049] In some embodiments, one or more QoS parameters are associated with an AF session group. In some embodiments, the executor 602 is configured to request the NEF to map the one or more first requests into one or more second requests to one or more policy control function (PCF) entities. In some embodiments, the one or more second requests are one or more N5 requests. In some embodiments, the executor 602 is configured to determine one or more PCF entities serving one or more UEs. In some embodiments, the AF session creation request includes a set of UE addresses, an AF identifier (ID), flow description information, an external application ID, a QoS reference, one or more QoS parameters, and / or one or more service requirements.

[0050] In some embodiments, the executor 602 is configured to allocate QoS dedicated resources for the AF session group and / or perform QoS monitoring. In some embodiments, the executor 602 is configured to report one or more QoS flow-level events to the AF corresponding to the AF session group. In some embodiments, the executor 602 is configured to revoke the AF session group. In some embodiments, the executor 602 is configured to update the UE list of the AF session group, one or more service requirements for the AF session group, and / or the type of QoS monitoring operation.

[0051] Figure 7An example of a network device 700 according to an embodiment of the present disclosure is shown. The network device 700 is configured to implement some embodiments of the present disclosure. Some embodiments of the present disclosure 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 proposed functions, processes, and / or methods described in this specification. The layers of the wireless interface protocol may be implemented in the processor 703. The memory 701 is operably coupled to the processor 703 and stores various information to operate the processor 703. The transceiver 702 is operably coupled to the processor 703, and the transceiver 702 transmits and / or receives wireless signals. The processor 703 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. The memory 701 may include read-only memory (ROM), random access memory (RAM), flash memory, a memory card, a storage medium, and / or other storage devices. The transceiver 702 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described in this disclosure may be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in this disclosure. The modules may be stored in the memory 701 and executed by the processor 703. The memory 701 may be implemented internally or externally to the processor 703, in which case the memory 701 may be communicatively coupled to the processor 703 via various means known in the art.

[0052] 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, by a network exposure function (NEF), an AF session creation request from an application function (AF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and the NEF dividing the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments (UEs). In some embodiments, the memory 701 stores executable instructions that, when executed by the processor 703, cause the processor 703 to implement operations including: sending, by an application function (AF), an AF session creation request to the network exposure function (NEF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and requesting the NEF to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments (UEs). This can address these and other issues in the prior art and / or reduce signaling overhead between the AF and a network such as a 5G core network (5GC).

[0053] Figure 8 A wireless communication architecture configured to implement some embodiments presented in this disclosure is shown. Figure 8 In some embodiments, network functions communicate with each other via a service-based interface in a core network (CN) in a wireless communication architecture. A user equipment (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 then utilize user plane functions to send and receive data to and from a data network (DN) (e.g., the Internet).

[0054] In some examples, the wireless communication architecture may include the following network functions (NFs): authentication server function (AUSF), access and mobility management function (AMF), data network (DN) (e.g., operator service, Internet access, or third-party service), network exposure function (NEF), network repository function (NRF), network slice-specific and 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.

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

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

[0057] Session Management Function (SMF): The SMF is responsible for the session management involved in establishing a PDU session 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.

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

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

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

[0061] Network Slice Selection Function (NSSF): NSSF involves aspects of network slice management, such as selecting network slice instances for UEs and managing network slice selection assistance information (NSSAI).

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

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

[0064] RAN nodes provide communication access from the UE to the core network for both control 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.

[0065] Example:

[0066] Figure 9 is a flow chart illustrating an AF session group supporting QoS resource allocation and / or QoS monitoring for implementing some embodiments proposed in the present disclosure. Figure 9 The flowchart shown includes at least one of the following steps.

[0067] Step 1: The AF controlling the operation of the AF session group invokes the Nnef_GroupOfAFSessionWithQoS_Create / Update / Revoke request to the 5G core network through the support of the NEF to allocate, update or revoke resource allocation and / or QoS monitoring for a group of QoS flows for a selected group of UEs. The group of QoS flows corresponds to a PDU session of a group of UEs, and the PDU session of the group of UEs can be selected to provide services for a group of data transmissions for a specific application (e.g., FL operation).

[0068] In step 1, if the AF is to establish resource allocation for an initial UE group that may or may not include UEs requesting a specific QoS monitoring operation, it calls the Nnef_GroupOfAFSessionWithQoS_Create request to the NEF, which includes the UE address group, AF identifier, flow description information or external application identifier, QoS reference or separate QoS parameters, alternative service requirements (such as Technical Specification ， TS) 23.503 clause 6.1.3.22, DNN, S-NSSAI). Optionally, the time period or traffic volume for the requested QoS may be included in the AF request. Instead of providing a QoS reference, the UE may provide one or more of the following individual QoS parameters: requested 5GS latency (optional), requested priority (optional), requested guaranteed bit rate, requested maximum bit rate, maximum burst size, and requested packet error rate. One (or more) QoS parameters to be measured (optional). Group-MBR threshold for group-MBR monitoring (optional). Regardless of whether a QoS reference or individual QoS parameters is used to formulate the AF request, the AF may also provide one or more of the following parameters describing the traffic characteristics: flow direction, burst arrival time at the UE (uplink), or burst arrival time at the UPF (downlink). NOTE 1: If a group-MBR threshold is provided, the one (or more) QoS parameters to be measured indicate that a guaranteed bit rate should be provided. NOTE 2: When event reporting is used for group-MBR monitoring, the NEF provides the AF with a QoS flow data rate report for the group of UEs only when the group-MBR threshold is exceeded.

[0069] In step 1, if the AF wishes to update the list of UEs in the group and / or update resource allocations and / or the type of QoS monitoring, the AF initiates an Nnef_GroupOfAFSessionWithQoS_Update request to the NEF to update reserved resources. This request includes the UE address group, AF identifier, transaction reference ID, flow description information, QoS reference or separate QoS parameters, and alternative service requirements (as described in TS 23.503, section 6.1.3.22). The transaction reference ID provided in the AF session with the required QoS update request message is set to the transaction reference ID assigned by the NEF. Instead of providing a QoS reference, the UE may provide one or more of the following separate QoS parameters: requested 5GS latency (optional), requested priority (optional), requested guaranteed bit rate, requested maximum bit rate, maximum burst size, and requested packet error rate. Whether formulating the AF request using a QoS reference or separate QoS parameters, the AF may also provide one or more of the following parameters describing traffic characteristics: flow direction, burst arrival time at the UE (uplink) or burst arrival time at the UPF (downlink), and one (or more) QoS parameters to be measured (optional). Group-MBR threshold for group-MBR monitoring (if required). The optional alternative service request provided by the AF shall contain a QoS reference or one (or more) requested alternative QoS parameter sets in the order of precedence specified in clause 6.1.3.22 of TS23.503. NOTE 1: If a group-MBR threshold is provided, the one (or more) QoS parameter indications to be measured shall provide the guaranteed bit rate. NOTE 2: When event reporting is used for group-MBR monitoring, the NEF shall provide the QoS flow data rate report for the group of UEs to the AF only if the group-MBR threshold is exceeded.

[0070] In step 1, if the AF revokes the AF session group, it initiates a Nnef_GroupOfAFSessionWithQoS_Revoke request by including the transaction reference ID allocated to the AF by the NEF for the corresponding target group.

[0071] Steps 2 and 3: The NEF authorizes the AF request. The NEF divides the AF request containing the UE list into a request from a single UE to the BSF or a request from a group of UEs served by the same BSF. The NEF determines the address of the corresponding serving PCF of the UE based on local configuration, or the NEF uses the Nbsf_Management Discovery service operation to find the address of the serving PCF of the UE.

[0072] Steps 4 and 5: Once the serving PCF(s) for a UE(s) are identified, the NEF maps the AF's request into a separate N5 request to each UE's serving PCF. The UE's serving PCF authorizes the NEF request and responds to the NEF with an Npcf_PolicyAuthorization response based on the success or failure of the authorization.

[0073] In steps 4 and 5, A. If the AF requests Nnef_GroupofAFSession_Create to establish an AF session group with resource allocation for a group of UEs, the NEF requests the serving PCF of the individual UE to derive the required QoS parameters for the PCC rules based on the information provided by the NEF, and determines (according to the PCF configuration) whether the QoS is allowed, and notifies the NEF of the result. Refer to step 4 described in TS23.502 Section 4.15.6.6 for further description of how the UE's serving PCF derives the PCC rules for the UE's serving SMF when the UE's serving PCF receives a QoS reference or separate QoS parameters from the AF via the NEF.

[0074] In steps 4 and 5, A. If Nnef_GroupOfAFSession_Create also includes the QoS parameters to be measured and the group-MBR threshold, the NEF requests the PCF to initiate a QoS monitoring event for data rate monitoring for a specific QoS flow as specified in TS23.502 clause 5.2.26, and the NEF calls the Npcf_PolicyAuthorization_Create request to the PCF and includes the UE IP address, DNN and S-NSSAI, application identifier, flow description information as described in TS23.503 clause 6.1.3.6 or external application identifier, QoS reference or separate QoS parameters to be measured as described in TS23.503 clause 6.1.3.22, flow direction, reporting frequency, reporting target (i.e., NEF), DNN, S-NSSAI, transaction reference ID, and optional alternative service requirements (containing one or more prioritized QoS reference parameters or requested alternative QoS parameter sets). NOTE 1: If a group-MBR threshold is provided, then the QoS parameter(s) to be measured indicate that a guaranteed bit rate should be provided. NOTE 2: When event reporting is used for group-MBR monitoring, the NEF shall provide the QoS flow data rate report for the group of UEs to the AF only if the group-MBR threshold is exceeded.

[0075] In steps 4 and 5, B. If the AF requests Nnef_GroupofAFSession_Revoke for a group of AF sessions, the NEF calls the Npcf_PolicyAuthorization_Delete service to the group of UE's respective serving PCFs. The NEF notifies each UE's serving PCF to delete the N4 policy by referencing the AF transaction ID. The UE's serving PCF responds to the NEF based on the authorization status requested by the NEF.

[0076] In steps 4 and 5, C. If the AF requests Nnef_GroupOfAFSessionWithQoS_Update to update the list of UEs in the group for resource allocation, the NEF refers to the local context corresponding to the list of UEs in the group and determines which new UE to add to the group, which existing UE to delete from the group and / or which existing UE to update by calling one or more of the following Npcf_PolicyAuthorization procedures:

[0077] 1. If the AF session group update request involves adding a new UE to a group with resource allocation, the NEF may initiate Npcf_PolicyAuthorization_Create to the PCF for the corresponding UE as described in A above.

[0078] 2. If the AF session group update request involves removing an existing UE from the group, the NEF may initiate Npcf_PolicyAuthorization_Delete to the PCF for the corresponding UE as described in B above.

[0079] 3. If the AF session group update request involves updating the QoS resources or QoS monitoring or both of the existing UEs in the group, the NEF initiates an Npcf_PolicyAuthorization_Update to the UE's serving PCF. The PCF processes the Npcf_PolicyAuthorization_Update request similarly to the group AF session creation request described in A above.

[0080] Step 6: NEF aggregates the authorization responses from PCF and sends Nnef_AFGroupOfSessionsWithQoS create / update / revoke responses corresponding to the previous group AF session request to AF. The NEF's combined response provides a specific success or failure response corresponding to each UE.

[0081] Steps 7 and 8: If the Npcf_PolicyAuthorization_Create / Update request from the NEF is authorized by the PCF, and the PCF determines that the policy information that the SMF needs to update, the PCF issues an Npcf_SMPolicyControl_UpdateNotify request containing the PDU session update policy information in accordance with the PCF-initiated SM Policy Association Modification procedure described in Section 4.16.5.2 of TS23.502. If the Npcf_PolicyAuthorization_Delete request from the NEF is authorized by the PCF, the PCF triggers the Npcf_SMPolicyControl_Delete service operation to the SMF.

[0082] Steps 9 and 10: If the SMF receives the creation or update of the PDU session policy information provided by the PCF as described in step 7 above, the SMF initiates the N4 session modification process to update the N4 session context of the existing PDU session at the UPF as described in section 4.4.1.3 of TS23.502. The updated N4 session may require the SMF to initiate the request to trigger the QoS monitoring event for data rate monitoring specified in section 5.2.26 of TS23.502 for the target QoS flow. If the SMF receives the deletion of the policy information of the PDU session, the SMF notifies the PDU session anchor (PSA) UPF to terminate the QoS monitoring event for data rate monitoring for the target QoS flow. The SMF confirms the PCF request through the Npcf_SMPolicyControl_UpdateNotify response.

[0083] Step 11: When receiving the PCF request, the SMF then provides PSAUPF to remove the report, or periodically initiates a report of data rate monitoring to the NEF via Nupf_EventExposure_Notify according to the reporting frequency.

[0084] Step 12: If the SMF indicates a QoS monitoring event for data rate monitoring, the UPF periodically reports the bit rate of the target QoS flow to the NEF; otherwise, if the SMF cancels the QoS monitoring event for data rate monitoring, the UPF terminates the UPF report.

[0085] Step 13: If a data rate monitoring report for a QoS monitoring event for a specific QoS flow is received from the UPF and the group-MBR threshold is provided by a previous Nnef_GroupOfAFSessionWithQoS request, the NEF sums the bit rates of all active QoS flows for the duration of the reporting frequency. If the given application artificial intelligence / machine learning (AI / ML) traffic is asymmetric, bit rate aggregation is performed for uplink and downlink separately; otherwise, bit rate aggregation is performed for only one of the uplink or downlink. Therefore, the NEF compares the aggregated bit rate of the uplink or downlink with the group-MBR threshold for the uplink or downlink accordingly. If the group-MBR threshold is not provided, the NEF collects all UPF QoS monitoring reports for the duration of the reporting frequency.

[0086] Step 14: NEF notifies the application AI / ML AF of the collected UPF QoS monitoring report along with the AF transaction reference ID via Nnef_AFGroupOfSessionsWithQoS_Notify only when the aggregate bit rate exceeds the group-MBR threshold specified by the AF; otherwise, NEF always notifies the AF of the collected UPF QoS monitoring report along with the AF transaction reference ID.

[0087] Step 15: The AF may take traffic conditioning measures based on the Group-MBR monitoring report (e.g., requesting the 5G Core to apply traffic gating to specific QoS flows, such as requesting the 5GC to block some flows), or may decide not to take any action other than using it for its own statistics or billing. The decision to perform it locally is outside the scope of this procedure.

[0088] The UPF QoS monitoring events for data rate monitoring continue until the AF terminates group-MBR monitoring. The UPF continues to periodically conduct QoS monitoring events for data rate monitoring for a given QoS flow and report them to the NEF at the reporting frequency described in steps 11-12 above. If the AF wishes to terminate group-MBR monitoring, the AF sends an Nnef_AFGroupOfSessionsWithQoS_Revoke request including the AF transaction reference ID to the NEF.

[0089] Table 2 shows the new NEF services and operations.

[0090] Nnef_GroupOfAFSessionWithQoS service

[0091] Overview

[0092] In addition to supporting QoS resource allocation for a group of UEs, this service is also used to support subscription and notification of QoS monitoring events for data rate monitoring for a group of QoS flows, as described in TS 23.502 clause 5.2.26.

[0093] Nnef_GroupOfAFSessionWithQoS_Create service operation

[0094] Service Operation Name: Nnef_GroupOfAFSessionWithQoS Create

[0095] Description: The consumer requests the network to allocate QoS dedicated resources for a specific AF session group and possibly perform QoS monitoring (e.g., delay, jitter, bit rate or group-MBR).

[0096] Input, required: AF identifier, UE address (ie IP address) list, flow description information as described in TS23.503 clause 6.1.3.6 or external application identifier, QoS reference as described in TS23.503 clause 6.1.3.22 or individual QoS parameters.

[0097] Input, optional: time period, traffic size, alternative service requirement (containing one or more prioritized QoS reference parameters or requested alternative QoS parameter set), one (or more) QoS parameters to be measured, group-MBR threshold, reporting frequency, reporting target and optional indication of local event notification as described in TS23.503 clause 6.1.3.21, DNN (if available), S-NSSAI (if available), flow direction.

[0098] NOTE 1: If Group-MBRThreshold is provided, then the QoS parameter(s) to be measured indicate that a guaranteed bit rate should be provided.

[0099] NOTE 2: When event reporting is used for group-MBR monitoring, the NEF provides the AF with a QoS flow data rate report for the group of UEs only when the group-MBR threshold is exceeded.

[0100] Output, required: Transaction reference ID, corresponding to the success or failure result of the request for one (or more) individual UEs in the list.

[0101] Output (optional): None.

[0102] Nnef_GroupOfAFSessionWithQoS_Notify service operation

[0103] Service Operation Name: Nnef_GroupOfAFSessionWithQoS_Notify

[0104] Description: The NEF reports one (or more) QoS flow-level events to the users corresponding to the AF session group.

[0105] Input, required: Transaction reference ID, Delivery report for the event defined in TS23.503 clause 6.1.3.18.

[0106] NOTE: When event reporting is used for group-MBR monitoring, the NEF provides the AF with a QoS flow data rate report for the group of UEs only when the group-MBR threshold is exceeded.

[0107] Input, optional: Include the Group-MBR Monitoring Report when delivery reporting is used for Group-MBR Monitoring.

[0108] Output, required: None.

[0109] Output (optional): None.

[0110] Nnef_GroupOfAFSessionWithQoS_Revoke service operation

[0111] Service Operation Name: Nnef_GroupOfAFSessionWithQoS_Revoke

[0112] Description: The user requests the network to cancel the AF session group.

[0113] Input, required: Transaction reference ID.

[0114] Input, optional: None.

[0115] Output, required: transaction reference ID, corresponding to the success or failure result of the request for a single UE.

[0116] Output (optional): None.

[0117] Nnef_GroupAFSessionWithQoS_Update service operation

[0118] Service Operation Name: Nnef_GroupOfAFSessionWithQoS_Update

[0119] Description: The user requests the network to update the list of UEs (identified by IP address) of the AF session group, one (or more) service requirements of the AF session group and / or one (or more) additional alternative service requirements and / or the type of QoS monitoring operation.

[0120] Input, required: transaction reference ID, AF identifier, UE address (ie IP address) list, flow description information as described in TS23.503 clause 6.1.3.6 or external application identifier.

[0121] Input, optional: QoS reference or individual QoS parameters as described in TS23.503 clause 6.1.3.22, time period, traffic size, alternative service requirement (containing one or more prioritized QoS reference parameters or requested alternative QoS parameter sets), one (or more) QoS parameters to be measured, group-MBR threshold, reporting frequency, reporting target and optionally an indication of local event notification as described in TS23.503 clause 6.1.3.21, flow direction.

[0122] NOTE 1: If Group-MBRThreshold is provided, then the QoS parameter(s) to be measured indicate that a guaranteed bit rate should be provided.

[0123] NOTE 2: When event reporting is used for group-MBR monitoring, the NEF provides the AF with a QoS flow data rate report for the group of UEs only when the group-MBR threshold is exceeded.

[0124] Output, required: transaction reference ID, operation execution result success or failure result.

[0125] Output (optional): None.

[0126] In summary, some embodiments of the present disclosure introduce new NEF services to support network resource allocation and various QoS monitoring operations for AF session groups, which are established for a group of UEs selected by the AF. If PCF authorization is obtained, each AF session in the group of UEs is allocated the same set of QoS resources requested by the AF. If QoS monitoring is also requested for the group, the group of QoS flows of the corresponding UEs participating in the same application in the group will be monitored according to the request of the AF. The AF specifies one or more QoS parameters to be measured to indicate the type of QoS monitoring measurement (for example, delay, jitter and / or data rate, etc.). By applying the solutions proposed in some embodiments of the present disclosure, the signaling overhead between the AF and the 5GC can be reduced.

[0127] The commercial benefits of some embodiments are as follows. 1. Solve problems and other issues in the existing technology. 2. Reduce signaling overhead between the AF and networks such as the 5G Core Network (5GC). Some embodiments of the present disclosure can be used in many applications. Some embodiments of the present disclosure are used by chipset vendors, video system development vendors, automotive manufacturers including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc., drones (unmanned aerial vehicles), smartphone manufacturers, communication devices for public safety purposes, and AR / VR / MR device manufacturers (e.g., for gaming, conferences / seminars, and educational purposes). Some embodiments of the present disclosure are combinations of "techniques / processes" that can be adopted in video standards to create final products. Some embodiments of the present disclosure propose technical mechanisms. At least one solution, method, system, and apparatus proposed in some embodiments of the present disclosure can be used in current and / or new / future standards for communication systems (such as UEs, base stations, network devices, and / or communication systems). Compatible products comply with at least one solution, method, system, and apparatus proposed in some embodiments of the present disclosure. The proposed solutions, methods, systems, and apparatus are widely used in UEs, base stations, network devices, and / or communication systems. With the implementation of at least one proposed solution, method, system, and apparatus of some embodiments of the present disclosure, at least one modification / improvement of the method and apparatus for conversation groups is considered for standardization.

[0128] Figure 10 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, Figure 10 The present invention may be implemented using any suitably configured hardware and / or software. Figures 2 to 9 , an example of a computing device 1100 that may be used to implement the apparatus and / or method shown in . In some embodiments, the computing device 1100 may 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 may include any of a plurality of processing devices, including one processing device. Such a processor may include, or may be in communication with, a computer-readable medium storing instructions that, when executed by the processor 1112, cause the processor to perform the operations described herein.

[0129] Memory 1114 can include any suitable non-transitory 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 code to the processor. Non-limiting examples of computer-readable media include disks, memory chips, ROM, RAM, 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 code written in any suitable computer programming language, including, for example, C, C++, C#, Visual Basic, Java, Python, Perl, JavaScript, and ActionScript.

[0130] 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 multiple 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 can receive input from one or more input devices 1120 or provide output to one or more output devices 1122. The one or more input devices 1120 and the one or more output devices 1122 can be communicatively coupled to the I / O interface 1118. The communicative coupling can 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 input devices 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 physical actions 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.

[0131] The computing device 1100 can execute program code that configures the processor 1112 to perform the above Figures 2 to 9 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.

[0132] 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.

[0133] Figure 11 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 in the communication system 1200 using any appropriately configured hardware and / or software. Figure 11 A communication system 1200 is shown that includes at least radio frequency (RF) circuitry 1210, baseband circuitry 1220, application circuitry 1230, memory / storage 1240, display 1250, camera 1260, sensor 1270, and input / output (I / O) interface 1280 coupled to one another as shown.

[0134] The 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 specialized 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. The communication system 1200 is capable of executing program code that configures the application circuit 1230 to perform the above-mentioned instructions. Figures 2 to 9 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.

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

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

[0137] In various embodiments, the above Figures 2 to 9The transmitter circuit, control circuit or receiver circuit discussed in the apparatus and / or method shown in can 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" can refer to, can be part of or can 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 circuit and / or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuit can be implemented in one or more software or firmware modules, or the functions associated with the circuit can 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 can be implemented together on a system on chip (SOC). The memory / storage device 1240 can be used to load and store data and / or instructions for the system, for example. 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).

[0138] In various embodiments, the I / O interface 1280 may include one or more user interfaces designed to enable user interaction with the system and / or a peripheral component interface designed to enable interaction between a 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 (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 part of or interact with a baseband circuit and / or RF circuit to communicate with components of a positioning network (e.g., a global positioning system (GPS) satellite).

[0139] 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.

[0140] Those skilled in the art will appreciate 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 software depends on the conditions of the application and the design requirements of the technical solution. Those skilled in the art may use different methods to implement the functions of each specific application, and such implementations should not exceed the scope of this application. Those skilled in the art will appreciate that since the working processes of the above-mentioned systems, devices, and units are substantially the same, reference may 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.

[0141] 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 merely exemplary. The division of units is based solely on logical functions, and other divisions may exist in implementation. Multiple units or components can be combined or integrated into another system. It is also possible to omit or skip some features. On the other hand, the mutual coupling, direct coupling, or communicative coupling shown or discussed can be operated indirectly or communicatively through some ports, devices, or units in an electrical, mechanical, or other manner.

[0142] The units used as separate components for explanation may be physically separate or not. The units used for display may be physical units or not, i.e., located in one place or distributed across multiple network units. Some or all of the units may be used depending on 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 a processing unit with two or more units.

[0143] 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 this application can be basically or partially implemented in the form of a software product. Alternatively, a part of the technical solution that is beneficial to traditional technology can be implemented in the form of a software product. The software product in the computer is stored in a storage medium, which 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 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.

[0144] 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 that may be made without departing from the scope of the broadest interpretation of the appended claims.

Claims

1. A wireless communication method for a conversation group, comprising: The network exposure function NEF receives an AF session creation request from the application function AF, wherein the AF session creation request is associated with the AF session group and one or more quality of service (QoS) parameters; and The NEF divides the AF session creation request into one or more first requests, where the one or more first requests are associated with one or more user equipments UE.

2. The method according to claim 1, wherein The one or more QoS parameters are associated with the AF session group.

3. The method according to claim 1 or 2, further comprising: The NEF maps the one or more first requests into one or more second requests to one or more policy control function (PCF) entities.

4. The method according to claim 3, wherein: The one or more second requests are one or more N5 requests.

5. The method according to claim 3 or 4, further comprising: The NEF determines the one or more PCF entities serving the one or more UEs.

6. The method according to any one of claims 1 to 5, wherein The AF session creation request includes a set of UE addresses, an AF identifier ID, flow description information, an external application ID, a QoS reference, the one or more QoS parameters and / or one or more service requirements.

7. The method according to any one of claims 1 to 6, further comprising: The AF requests the NEF to allocate QoS dedicated resources for the AF session group, and / or the AF requests the NEF to perform QoS monitoring.

8. The method according to any one of claims 1 to 7, further comprising: The NEF reports one or more QoS flow level events to the AF corresponding to the AF session group.

9. The method according to any one of claims 1 to 8, further comprising: The AF requests the NEF to cancel the AF session group.

10. The method according to any one of claims 1 to 9, further comprising: The AF requests the NEF to update a UE list of the AF session group, one or more service requirements for the AF session group, and / or a type of QoS monitoring operation.

11. A wireless communication method for a conversation group, comprising: The application function AF sends an AF session creation request to the network exposure function NEF, wherein the AF session creation request is associated with the AF session group and one or more quality of service QoS parameters; and The NEF is requested to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments UE.

12. A wireless communication device comprising: a receiver configured to receive an AF session creation request from an application function AF, wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and An executor is configured to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments UE.

13. A wireless communication device comprising: a transmitter configured to send an application function (AF) session creation request to a network exposure function (NEF), wherein the AF session creation request is associated with an AF session group and one or more quality of service (QoS) parameters; and An executor is configured to request the NEF to divide the AF session creation request into one or more first requests, wherein the one or more first requests are associated with one or more user equipments UE.

14. A network device comprising: Memory; transceiver; as well as a processor coupled to the memory and the transceiver; The network device is configured to execute the method according to any one of claims 1 to 10 or the method according to claim 11. 15 . A non-transitory machine-readable storage medium storing instructions, which, when executed by a computer, cause the computer to perform the method according to claim 1 or the method according to claim 11 .

16. A chip, comprising: A processor configured to call and run a computer program stored in a memory, so as to enable a device equipped with the chip to perform the method according to any one of claims 1 to 10 or the method according to claim 11.

Images