Augmented reality and multimedia service data transmission method, device and storage medium

Abstract

The present disclosure relates to an augmented reality and multimedia service data transmission method, device, and storage medium, and relates to the field of communication technologies, for making more appropriate policy decisions and resource authorizations for XRM services and providing better QoS guarantees for SDF transmission. The method includes determining an application function (AF) session request, where the AF session request includes a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group, and performing a policy decision on the AF session request based on a time threshold and the common identifier.

Description

[Technical Field]

[0001] The present disclosure relates to the field of communication technologies, and in particular to an Extend Reality and Media (XRM) service data transmission method, device, and storage medium. [Background technology]

[0002] Services such as mobile media services, cloud-based augmented reality (AR) / virtual reality (VR) and other extended reality (XR) services, cloud gaming, and video-based remote control of machines or drones will contribute increasingly large amounts of traffic to 5G networks. Among these services, extended reality and media (XRM) services (also known as multimodal services) involve multimodal data. The data flows of these services are often highly correlated; for example, audio and video flows must be synchronized, and haptics and vision must be synchronized. The data flows of these media services, the data flows between each other, and the network transmission requirements for these service data flows share several common characteristics. Effective identification and utilization of these characteristics is beneficial for network and service transmission and control, as well as for service guarantees and user experiences.

[0003] In the related technology, for XRM services, it is necessary to comprehensively consider the Quality of Service (QoS) characteristics of the service data flows related to the service, and to maintain consistency of QoS permissions between multiple service data flows of a single terminal or data flows of multiple terminals.

[0004] However, currently, a Policy Control Function (PCF) entity cannot determine the scope and size of an XRM service group, cannot accurately determine the QoS authorization requirements of an XRM service group, and cannot accurately perform QoS authorization for multiple Service Data Functions (SDFs) within an XRM group. Summary of the Invention [Problem to be solved by the invention]

[0005] To solve the problems existing in the related art, the present disclosure provides an augmented reality and multimedia service data transmission method, apparatus and storage medium. [Means for solving the problem]

[0006] According to a first aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission method performed by a core network device, the augmented reality and multimedia service data transmission method including: determining an application function (AF) session request, wherein the session request includes a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group; and performing a policy decision on the AF session request based on a time threshold and the common identifier.

[0007] According to a second aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission method performed by a Policy Control Function (PCF) entity in a core network device, the augmented reality and multimedia service data transmission method including: receiving an Application Function (AF) session request, wherein the AF session request includes a common identifier for identifying an Augmented Reality and Multimedia (XRM) Service Data Flow (SDF) group; and performing a policy decision on the AF session request based on a time threshold and the common identifier.

[0008] According to a third aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission method performed by an application function (AF) entity in a core network device, the augmented reality and multimedia service data transmission method including a step of sending an AF session request, the AF session request including a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group, the AF session request being used by a policy control function (PCF) entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.

[0009] According to a fourth aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission method performed by a core network network element function in a core network device, the augmented reality and multimedia service data transmission method including: receiving an application function (AF) session request, wherein the AF session request includes a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group; and sending the AF session request to a policy control function (PCF) entity, wherein the AF session request is used by the PCF entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.

[0010] According to a fifth aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission device, the augmented reality and multimedia service data transmission device including a determination module and an execution module, wherein the determination module is used to determine an application function (AF) session request, the session request including a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group, and the execution module is used to perform a policy decision on the AF session request based on a time threshold and the common identifier.

[0011] According to a sixth aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission device, the augmented reality and multimedia service data transmission device including a sending module, a receiving module, and an executing module, wherein the sending module is used by an application function (AF) entity to send an AF session request, the AF session request including a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group, the receiving module is used by a policy control function (PCF) entity to receive the AF session request, and the executing module is used by the PCF entity to perform a policy decision on the AF session request based on a time threshold and the common identifier.

[0012] According to a seventh aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission device, comprising: a receiving module and an executing module, wherein the receiving module is used to receive an application function (AF) session request, the AF session request including a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group, and the executing module is used to perform a policy decision on the AF session request based on a time threshold and the common identifier.

[0013] According to an eighth aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission device, the augmented reality and multimedia service data transmission device including a transmission module used to transmit an AF session request, the AF session request including a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group, and the AF session request is used by a policy control function (PCF) entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.

[0014] According to a ninth aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission device, comprising: a receiving module and a transmitting module, wherein the receiving module is used to receive an application function (AF) session request, wherein the AF session request includes a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group; and the transmitting module is used to transmit the AF session request to a policy control function (PCF) entity, wherein the AF session request is used by the PCF entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.

[0015] According to a tenth aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission device, the augmented reality and multimedia service data transmission device including a sending module, a receiving module, and an executing module, wherein the sending module is used by an application function (AF) entity to send an AF session request, the AF session request including a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group, the receiving module is used by a policy control function (PCF) entity to receive the AF session request, and the executing module is used by the PCF entity to perform a policy decision on the AF session request based on a time threshold and the common identifier.

[0016] According to an eleventh aspect of an embodiment of the present disclosure, there is provided an augmented reality and multimedia service data transmission device, comprising: a processor; and a memory for storing instructions executable by the processor, wherein the processor is used to perform the augmented reality and multimedia service data transmission method described in the first aspect or the second aspect or the third aspect or the fourth aspect and any one of the embodiments.

[0017] According to a twelfth aspect of an embodiment of the present disclosure, there is provided a storage medium having instructions stored thereon, the instructions in which, when executed by a processor of a core network device, can cause the core network device to perform the augmented reality and multimedia service data transmission method set forth in the first aspect, or the instructions in which, when executed by a processor of a Policy Control Function (PCF) entity, can cause a PCF entity to perform the augmented reality and multimedia service data transmission method set forth in the second aspect, or the instructions in which, when executed by a processor of an Application Function (AF) entity, can cause an AF entity to perform the augmented reality and multimedia service data transmission method set forth in the third aspect, or the instructions in which, when executed by a processor of a core network function network element, can cause a core network function network element to perform the augmented reality and multimedia service data transmission method set forth in the fourth aspect, or the instructions in which, when executed by processors of a PCF entity and an AF entity in a core network device, can cause a PCF entity and an AF entity to perform the augmented reality and multimedia service data transmission method set forth in the fifth aspect.

[0018] According to a thirteenth aspect of an embodiment of the present disclosure, there is provided a communication system for performing the augmented reality and multimedia service data transmission method according to the first aspect.

[0019] According to a fourteenth aspect of an embodiment of the present disclosure, there is provided a communication system including a Policy Control Function (PCF) entity for performing the method described in the second aspect, an Application Function (AF) entity for performing the method described in the third aspect, and a core network function network element for performing the method described in any one of the fourth aspects. [Effects of the Invention]

[0020] The technical solutions provided in the embodiments of the present disclosure can achieve the following beneficial effects: The PCF receives the AF session request, and the AF session request includes a common identifier for identifying the XRM SDF group, so that the PCF can determine the group to which the SDF belongs based on the common identifier. Furthermore, the PCF can combine the time threshold and perform policy decisions for AF session requests within the time threshold, so that the PCF can make more appropriate policy decisions and resource authorization for XRM services based on the time threshold and the common identifier, providing better QoS guarantees for SDF transmission and eliminating the need to repeatedly change policy decisions multiple times for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency. [Brief explanation of the drawings]

[0021] The drawings herein, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure. [Figure 1] 1 is a schematic diagram of a communication system according to an exemplary embodiment; [Figure 2] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 3] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 4] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 5] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 6] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 7] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 8] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 9] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 10] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 11] 1 is a flowchart of an augmented reality and multimedia service data transmission method according to an exemplary embodiment; [Figure 12] 1 is a block diagram of an augmented reality and multimedia service data transmission device according to an exemplary embodiment; [Figure 13] 1 is a block diagram of an augmented reality and multimedia service data transmission device according to an exemplary embodiment; [Figure 14] 1 is a block diagram of an augmented reality and multimedia service data transmission device according to an exemplary embodiment; [Figure 15] 1 is a block diagram of an augmented reality and multimedia service data transmission device according to an exemplary embodiment; [Figure 16] 1 is a block diagram of an augmented reality and multimedia service data transmission device according to an exemplary embodiment; [Figure 17]FIG. 1 is a block diagram of an apparatus used for augmented reality and multimedia service data transmission according to an exemplary embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0022] Illustrative examples are described in detail below, examples of which are illustrated in the drawings. When referring to the drawings in the following description, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following illustrative examples do not represent all embodiments consistent with the present application.

[0023] The augmented reality and multimedia service data transmission method provided in the embodiments of the present disclosure is applicable to the wireless communication system shown in Figure 1. As shown in Figure 1, a mobile station accesses a wireless access network through a wireless access network device such as a base station, and the wireless access network device and the core network device complete data backhaul and forward transmission to perform various communication services.

[0024] A wireless communication system is a network that provides wireless communication functions. Wireless communication systems may employ different communication technologies, such as code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and carrier sense multiple access with collision avoidance (CMS). Depending on factors such as network capacity, speed, and latency, networks can be classified as 2G (generation 2), 3G, 4G, or future evolutionary networks, such as 5G networks. 5G networks may also be referred to as New Radio (NR) networks. For ease of description, this disclosure may refer to wireless communication networks as networks or systems. In the present disclosure, a network may include a radio access network (RAN) and a core network (CN). The network includes network devices, which may be radio access network nodes, core network functions, etc. The radio access network nodes may be referred to as base stations. The network may provide network services to terminals through the network devices, and different operators may provide different network services to terminals, and it may be understood that different operators correspond to different operator networks.

[0025] A mobile station (MS), which may also be called user equipment (UE), terminal, or mobile terminal (MT), is a device that provides voice and / or data connectivity to a user. For example, a terminal may be a handheld device with wireless connectivity, an in-vehicle device, or the like. Currently, some examples of terminals include a mobile phone, a pocket personal computer (PPC), a handheld personal computer, a personal digital assistant (PDA), a laptop computer, a tablet computer, a wearable device, or an in-vehicle device.

[0026] The 5G system includes devices that manage and coordinate the access and mobility-related requirements of radio access networks and terminals. For example, core network functions include a session management function (SMF), an access and mobility management function (AMF), a radio access network (RAN), a unified data management (UDM), a policy control function (PCF), a user plane function (UPF), and a user equipment (UE). Of course, the core network functions may include other types of devices, which are not further listed in the embodiments of the present disclosure.

[0027] The related entity functions according to the embodiments of the present disclosure will be described in detail below. The AF entity is responsible for interacting with the 3GPP (registered trademark) core network to provide business or services, including interactions with the NEF, interactions with the policy architecture, etc. The main function of the NEF entity is to securely expose the services and capabilities provided by 3GPP Network Functions, either internally or to third parties, and convert or translate AF interaction information and internal Network Function interaction information, such as AF service identifiers and internal 5G core network information, such as Data Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI), etc.

[0028] The AMF entity is responsible for access and mobility management, and its main functions include access and mobility related functions such as connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management, user authentication, switching, location update, etc. The primary functions of the PCF entity include policy-related functions such as formulating unified policies, providing policy control, and obtaining contract information for policy decisions from unified data management (UDR).

[0029] The UPF entity is responsible for user plane functions, and its main functions include user plane-related functions such as data packet routing and transmission, packet detection, service usage reporting, QoS processing, legal monitoring, uplink packet detection, and downlink data packet storage. The SMF entity is responsible for session management functions, and its main functions include session management (such as session establishment, modification, and release, including tunnel maintenance between the UPF and the AN), UPF selection and control, service and session continuity (SSC) mode selection, roaming, and other session-related functions.

[0030] Services such as mobile media services, cloud-based augmented reality (AR) / virtual reality (VR) and other extended reality (XR) services, cloud gaming, and video-based remote control of machines or drones will contribute increasingly large amounts of traffic to 5G networks. Among these services, extended reality and media (XRM) services (also known as multimodal services) involve multimodal data. The data flows of these services are often highly correlated; for example, audio and video flows must be synchronized, and haptics and vision must be synchronized. The data flows of these media services, the data flows between each other, and the network transmission requirements for these service data flows share several common characteristics. Effective identification and utilization of these characteristics is beneficial for network and service transmission and control, as well as for service guarantees and user experiences.

[0031] In the related technology, for XRM services, it is necessary to comprehensively consider the Quality of Service (QoS) characteristics of the service data flows related to the service, and to maintain consistency of QoS permissions between multiple service data flows of a single terminal or data flows of multiple terminals.

[0032] However, currently, a Policy Control Function (PCF) entity cannot determine the scope and size of an XRM service group, cannot accurately determine the QoS authorization requirements of an XRM service group, and cannot accurately perform QoS authorization for multiple Service Data Functions (SDFs) within an XRM group.

[0033] In view of this, an embodiment of the present disclosure provides an XRM service data transmission method, in which a PCF receives an AF session request, the AF session request including a common identifier for identifying an XRM SDF group, and the PCF can determine an XRM SDF group to which the SDF belongs based on the common identifier. Furthermore, the PCF can combine a time threshold to perform policy decisions for AF session requests within the time threshold, and the PCF can make more appropriate policy decisions and resource authorizations for XRM services based on the time threshold and the common identifier, providing better QoS guarantees for SDF transmission and eliminating the need to repeatedly change policy decisions for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.

[0034] 2 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in FIG. 2, the XRM service data transmission method is applied to a core network device and includes the following steps S11 and S12: In step S11, an AF session request is determined, and the session request includes a common identifier for identifying the XRM SDF group. Multiple SDFs of one XRM service / application belong to the same SDF group, and the common identifiers of the SDFs in one SDF group are the same.

[0035] In one embodiment, the SDFs corresponding to the common identifier correspond to the same terminal or to multiple terminals (a group of terminals).

[0036] In one embodiment, the AF session request may include information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.

[0037] In some embodiments, the AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs that belong to the same SDF group in one XRM service / application have the same XRM service identifier.

[0038] In step S12, a policy decision is made on the AF session request based on the time threshold and the common identifier.

[0039] In an embodiment of the present disclosure, a core network device determines an AF session request, and the AF session request includes a common identifier for identifying an XRM SDF group, so that the core network device can determine the XRM group to which the SDF belongs based on the common identifier. Furthermore, the core network device can combine a time threshold and perform policy decisions for AF session requests within the time threshold, so that the core network device can make more appropriate policy decisions and resource authorizations for XRM services based on the time threshold and the common identifier, provide better QoS guarantees for SDF transmission, and eliminate the need to repeatedly change policy decisions multiple times for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.

[0040] In the XRM service data transmission method provided by the embodiments of the present disclosure, the time threshold includes a time threshold determined based on a timer locally set by the core network device, or a time threshold determined based on a time value or time window included in the AF session request, or a time threshold determined based on a timer or time window in an operator policy, or a time threshold determined based on a default timer or time window in contract information, or a time threshold determined based on a timer locally set by the core network device, a time value or time window in the AF session request, a default timer or time window in the operator policy or contract information, and the priority of each type of value.

[0041] In one embodiment, the core network device may determine the time threshold based on a timer set locally by the core network device. For example, if the timer set locally by the core network device is 10 ms, the core network device may determine 10 ms, or 8 ms, or some other time value less than 10 ms as the time threshold.

[0042] In one embodiment, the AF session request includes a time value or time window, and the core network device determines the time threshold based on the time window included in the AF session request. For example, if the AF session request includes a time window of 10 ms to 30 ms, the core network device may determine that one time threshold can be checked between 10 ms and 30 ms, and may be greater than 10 ms and less than or equal to 30 ms.

[0043] In one embodiment, the core network device may determine the time threshold based on a timer or time window in an operator policy. For example, if an operator policy specifies that the timer set for an XRM service is 15 ms, when a core network device receives an AF session request for an XRM service, it can determine 15 ms as the time threshold for the SDF group of that XRM service, or a value less than 15 ms that takes network conditions into account, such as 12 ms.

[0044] In one embodiment, the time threshold is determined based on a default timer or time window in the contract information. Contract information is stored in Unified Data Management (UDM).

[0045] For example, if a core network device receives an AF session request for an XRM service and determines that the default timer in the contract request for that XRM service is 10 ms, the core network device may determine 10 ms or 8 ms (or some appropriate value less than 10 ms) as the time threshold for the SDF group for that XRM service.

[0046] In one embodiment, the core network device determines the time threshold based on the priorities of timers configured locally by the core network device, time windows, timers in operator policies, and default timers. For example, if a timer is configured locally in a core network device, a timer is configured in operator policy, a default timer is recorded in the contract information, and the AF session request received by the PCF also includes a time window, the core network device may determine the time threshold based on the priority of these timers or time windows.

[0047] The priority of each timer or time window can be determined based on pre-set rules. For example, the priority of the default timer in the contract information < the timer in the operator policy < the timer locally set by the core network device < the priority of the time window included in the AF session request. The core network device can select the timer or time window with the highest priority as the time threshold.

[0048] In the XRM service data transmission method provided by the embodiments of the present disclosure, the above step S12 of performing policy determination on the AF session request based on the time threshold and the common identifier can be realized as steps S21~S22. As shown in FIG. 3, in step S21, the core network device determines the common identifier with the same value received before reaching the time threshold. The common identifier with the same value is used to identify that multiple XRM SDFs belong to the same group.

[0049] In step S22, the core network device performs policy determination on the AF session request identified by the common identifier with the same value.

[0050] In the embodiments of the present disclosure, the core network device determines the time threshold, and before reaching the time threshold, by performing policy determination on the AF session request identified by the common identifier with the same value, the core network device can determine the SDFs belonging to the same group and perform policy determination on the SDFs in the same group. The core network device can perform more appropriate policy determination and resource permission for the XRM service and provide a more optimized QoS guarantee for SDF transmission.

[0051] In the XRM service data transmission method provided in the embodiments of the present disclosure, the policy decision includes allowing the same QoS for all SDFs in the SDF group, or generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or generating respective Policy Control and Charging (PCC) rules for each SDF and generating respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0052] The PCC rule expresses the service requirements for service quality and the billing requirements for the service. The network provides different QoS services to users based on the service type and the user's contract level, detects different service data flows, and reports the billing information such as the statistical traffic and duration to the billing center for billing.

[0053] In an embodiment of the present disclosure, after determining the XRM SDF group to which an SDF belongs, policy decisions can be made for SDFs in the same group, such as allowing the same QoS or allowing each SDF its own QoS, allowing the core network device to make more appropriate policy decisions and resource authorizations for XRM services and provide better QoS guarantees for SDF transmission.

[0054] In an XRM service data transmission method provided in an embodiment of the present disclosure, in response to receiving an AF session request including a common identifier after a time threshold, a policy decision is made for the AF session request received after the time threshold based on the policy decision made for the AF session request received before the time threshold.

[0055] In one embodiment, if the value of the common identifier in an AF session request received after the time threshold is the same as the value of the common identifier in an AF session request received before the time threshold, the same policy decisions may be made for the AF session request received after the time threshold as for the AF session request received before the time threshold.

[0056] For example, a policy decision performed by a core network device for an AF session request received before the time threshold may be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group. Then, a policy decision performed by a core network device for an AF session request received after the time threshold may similarly be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0057] In an embodiment of the present disclosure, a policy decision of a core network device for an AF session request received after the time threshold can be determined based on an AF session request before the time threshold, and efficiency is improved because the policy decision does not need to be determined again for an AF session request received after the time threshold.

[0058] The following describes the XRM service data transmission method provided in the embodiments of the present disclosure, with the PCF entity in the core network device as the execution entity.

[0059] 4 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in FIG. 4, the XRM service data transmission method is performed by a PCF entity in a core network device and includes the following steps S31 and S32:

[0060] In step S31, an AF session request is received, and the AF session request includes a common identifier for identifying an XRM SDF group. Multiple SDFs of one XRM service / application belong to the same SDF group, and the common identifiers of the SDFs in one SDF group are the same.

[0061] In one embodiment, the SDFs corresponding to a common identifier are from the same terminal or multiple terminals (a group of terminals).

[0062] In one embodiment, the AF session request may include information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.

[0063] In some embodiments, the AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs that belong to the same SDF group in one XRM service / application have the same XRM service identifier.

[0064] In step S32, a policy decision is made on the AF session request based on the time threshold and the common identifier.

[0065] In an embodiment of the present disclosure, a PCF receives an AF session request, and the AF session request includes a common identifier for identifying an XRM SDF group, so that the PCF can determine the XRM group to which the SDF belongs based on the common identifier. Furthermore, the PCF can combine a time threshold and perform policy decisions for AF session requests within the time threshold, so that the PCF can make more appropriate policy decisions and resource authorizations for XRM services based on the time threshold and the common identifier, provide better QoS guarantees for SDF transmission, and eliminate the need to repeatedly change policy decisions multiple times for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.

[0066] In the XRM service data transmission method provided by the embodiments of the present disclosure, the time threshold includes a time threshold determined based on a timer locally set by a PCF entity, or a time threshold determined based on a time value or time window included in an AF session request, or a time threshold determined based on a timer or time window in an operator policy, or a time threshold determined based on a default timer or time window in contract information, or a time threshold determined based on a timer locally set by a PCF entity, a time value or time window in an AF session request, a default timer or time window in an operator policy or contract information, and the priority of each type of value.

[0067] In one embodiment, the PCF may determine the time threshold based on a timer set locally by the PCF entity. For example, if the timer set locally by the PCF entity is 10 ms, the PCF may determine 10 ms, or 8 ms, or any other time value less than 10 ms as the time threshold.

[0068] In one embodiment, the AF session request includes a time value or time window, and the PCF determines the time threshold based on the time window included in the AF session request. For example, if the AF session request includes a time window of 10 ms to 30 ms, the PCF may determine that one time threshold can be checked between 10 ms and 30 ms, and may be greater than 10 ms and less than or equal to 30 ms.

[0069] In one embodiment, the PCF may determine the time threshold based on a timer or time window in an operator policy. For example, if an operator policy specifies that the timer set for an XRM service is 15 ms, when the PCF receives an AF session request for an XRM service, it may determine 15 ms as the time threshold for the SDF group of that XRM service, or may determine a value less than 15 ms taking into account network conditions, for example, 12 ms.

[0070] In one embodiment, the time threshold is determined based on a default timer or time window in the contract information. Contract information is stored in Unified Data Management (UDM).

[0071] For example, if a PCF receives an AF session request for an XRM service and determines that the default timer in the contract request for that XRM service is 10 ms, the PCF may determine 10 ms or 8 ms (or some other appropriate value less than 10 ms) as the time threshold for the SDF group for that XRM service.

[0072] In one embodiment, the PCF determines the time threshold based on the priorities of timers configured locally by the PCF entity, time windows, timers in operator policies and default timers. For example, if a PCF entity has a timer configured locally, a timer configured in operator policy, a default timer recorded in the contract information, and an AF session request received by the PCF also contains a time window, the PCF may determine the time threshold based on the priority of these timers or time windows.

[0073] The priority of each timer or time window can be determined based on pre-set rules. For example, the priority of the default timer in the contract information < the timer in the operator policy < the timer locally set by the PCF < the priority of the time window included in the AF session request. The PCF can select the timer or time window with the highest priority as the time threshold.

[0074] In the XRM service data transmission method provided by the embodiments of the present disclosure, the above step S32 of performing policy determination on the AF session request based on the time threshold and the common identifier can be realized as steps S41~S42. As shown in FIG. 5, in step S41, the PCF entity determines the common identifier with the same value received before reaching the time threshold. The common identifier with the same value is used to identify that multiple XRM SDFs belong to the same group.

[0075] In step S42, the PCF entity performs policy determination on the AF session request identified by the common identifier with the same value.

[0076] In the embodiments of the present disclosure, by the PCF determining the time threshold and performing policy determination on the AF session request identified by the common identifier with the same value before reaching the time threshold, the PCF can determine the SDFs belonging to the same group and perform policy determination on the SDFs in the same group. The PCF can perform more appropriate policy determination and resource permission for the XRM service and provide a more optimized QoS guarantee for SDF transmission.

[0077] In the XRM service data transmission method provided in the embodiments of the present disclosure, the policy decision includes allowing the same QoS for all SDFs in the SDF group, or generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or generating respective Policy Control and Charging (PCC) rules for each SDF and generating respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0078] The PCC rule expresses the service requirements for service quality and the billing requirements for the service. The network provides different QoS services to users based on the service type and the user's contract level, detects different service data flows, and reports the billing information such as the statistical traffic and duration to the billing center for billing.

[0079] In an embodiment of the present disclosure, after determining the XRM SDF group to which an SDF belongs, policy decisions can be made for SDFs in the same group, such as allowing the same QoS or allowing each SDF its own QoS, allowing the PCF to make more appropriate policy decisions and resource authorizations for XRM services and provide better QoS guarantees for SDF transmission.

[0080] In an XRM service data transmission method provided in an embodiment of the present disclosure, in response to receiving an AF session request including a common identifier after a time threshold, a policy decision is made for the AF session request received after the time threshold based on the policy decision made for the AF session request received before the time threshold.

[0081] In one embodiment, if the value of the common identifier in an AF session request received after the time threshold is the same as the value of the common identifier in an AF session request received before the time threshold, the same policy decisions may be made for the AF session request received after the time threshold as for the AF session request received before the time threshold.

[0082] For example, the policy decision performed by the PCF for an AF session request received before the time threshold may be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on the contract information and / or operator policy corresponding to each SDF in the SDF group. Then, the policy decision performed by the PCF for an AF session request received after the time threshold may similarly be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on the contract information and / or operator policy corresponding to each SDF in the SDF group.

[0083] In an embodiment of the present disclosure, a PCF's policy decision for an AF session request received after the time threshold can be determined based on an AF session request before the time threshold, and efficiency is improved because the policy decision does not need to be determined again for an AF session request received after the time threshold.

[0084] In the XRM service data transmission method provided in the embodiments of the present disclosure, the AF session request received by the PCF is sent directly by the AF entity, or sent by the AF entity to the NEF entity and then sent by the NEF entity to the PCF, or sent by the AF entity to a Time Sensitive Communication and Time Synchronization function (TSCTSF) entity and then sent by the TSCTSF entity to the PCF, or sent by the AF entity to the NEF and then sent by the NEF to the TSCTSF entity and then sent by the TSCTSF entity to the PCF.

[0085] If the AF is a trusted AF, it may send the AF session request directly to the PCF. If the AF is a non-trusted AF, it sends it to the PCF via the NEF and / or TSCTSF.

[0086] In the XRM service data transmission method provided in the embodiments of the present disclosure, the PCF can receive an AF session request in the following steps: (a) Setting up an AF session with required QoS procedure, (b) AF session with required QoS update procedure (c) Service specific parameter provisioning; (d) Set a policy for a future AF session.

[0087] Based on the same idea, the embodiments of the present disclosure further provide an XRM service data transmission method performed by an AF entity in a core network device.

[0088] 6 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in FIG. 6, the XRM service data transmission method is performed by an AF entity in a core network device, and includes the following step S51:

[0089] In step S51, an AF session request is sent, and the AF session request includes a common identifier for identifying an XRM SDF group and a time threshold. The AF session request is used by the PCF entity to perform policy decisions on the AF session request based on the common identifier and time threshold. Multiple SDFs of one XRM service / application belong to the same SDF group, and the common identifiers of the SDFs in one SDF group are the same.

[0090] In one embodiment, the SDFs corresponding to a common identifier are from the same terminal or multiple terminals (a group of terminals).

[0091] In one embodiment, the AF session request may include information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.

[0092] In some embodiments, the AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs that belong to the same SDF group in one XRM service / application have the same XRM service identifier.

[0093] In some embodiments, the time threshold included in the AF session request may be a time window or time value.

[0094] In some embodiments, in addition to the time threshold included in the AF session request, the PCF may determine the time threshold by a timer or time window locally set by the PCF entity, or by a timer or time window recorded in the operator policy, or by a default timer or time window in the contract information.

[0095] In one embodiment, when a timer or time window is locally set in the PCF entity, a timer or time window is also set in the operator policy, a default timer or time window is recorded in the contract information, and a time window or time value is included in the AF session request, the PCF can determine the time threshold based on the priority of these timers or time windows.

[0096] The priority of each timer or time window can be determined based on pre-set rules. For example, the priority of the default timer in the contract information < the timer in the operator policy < the timer locally set by the PCF < the priority of the time window included in the AF session request. The PCF can select the timer or time window with the highest priority as the time threshold.

[0097] In the embodiments of the present disclosure, by the AF sending an AF session request including a common identifier and a time threshold, the PCF can perform policy decision on the AF session request based on the time threshold and the common identifier, so that more appropriate policy decision and resource permission can be performed on the XRM service, better QoS guarantee can be provided for the SDF transmission, there is no need to repeatedly change the policy decision for multiple SDFs belonging to the same XRM SDF group, and the permission efficiency can be improved.

[0098] In the XRM service data transmission method provided in the embodiment of the present disclosure, the AF session requests are used to perform policy decisions on AF session requests identified by a common identifier with the same value received before a time threshold is reached by a PCF entity, and the common identifier with the same value is used to identify multiple XRM service data flows (SDFs) as belonging to the same group.

[0099] In the XRM service data transmission method provided in the embodiments of the present disclosure, the policy decision includes allowing the same QoS for all SDFs in the SDF group, or generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or generating respective PCC rules for each SDF and generating respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0100] The PCC rule expresses the service requirements for service quality and the billing requirements for the service. The network provides different QoS services to users based on the service type and the user's contract level, detects different service data flows, and reports the billing information such as the statistical traffic and duration to the billing center for billing.

[0101] In an embodiment of the present disclosure, after determining the XRM SDF group to which an SDF belongs, the PCF can make policy decisions such as allowing the same QoS for SDFs in the same group or allowing each SDF its own QoS, so that the PCF can make more appropriate policy decisions and resource authorizations for XRM services and provide better QoS guarantees for SDF transmission.

[0102] In the XRM service data transmission method provided in the embodiment of the present disclosure, a policy decision for an AF session request having a common identifier sent after a time threshold is determined based on a policy decision for an AF session request sent before the time threshold.

[0103] In one embodiment, if the value of the common identifier in an AF session request sent after the time threshold is the same as the value of the common identifier in an AF session request sent before the time threshold, the policy decision for the AF session request sent after the time threshold may be the same as the policy decision for the AF session request sent before the time threshold.

[0104] For example, the policy decision for an AF session request sent by the AF before the time threshold may be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on the contract information and / or operator policy corresponding to each SDF in the SDF group. Then, the policy decision for an AF session sent by the AF after the time threshold may similarly be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on the contract information and / or operator policy corresponding to each SDF in the SDF group.

[0105] In an embodiment of the present disclosure, a policy decision for an AF session request sent by an AF after the time threshold can be determined based on an AF session request before the time threshold, eliminating the need for the PCF to re-determine a policy decision for an AF session request received after the time threshold, thereby improving efficiency.

[0106] In the XRM service data transmission method provided in the embodiment of the present disclosure, the AF sends an AF session request to at least one functional entity of a PCF entity, an NEF entity, and a TSCTSF entity.

[0107] In one embodiment, if the AF is a trusted AF, the AF may send the AF session request directly to the PCF. If the AF is a non-trusted AF, the AF sends it to the PCF via the NEF and / or TSCTSF.

[0108] In the XRM service data transmission method provided in the embodiments of the present disclosure, the PCF can receive an AF session request in the following steps: (a) Setting up an AF session with required QoS procedure, (b) AF session with required QoS update procedure (c) Service specific parameter provisioning; (d) Set a policy for a future AF session.

[0109] Based on the same idea, the embodiments of the present disclosure further provide an XRM service data transmission method performed by a core network function network element in a core network device.

[0110] 7 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in FIG. 7, the XRM service data transmission method is performed by a core network function network element in a core network device, and includes the following steps S61 and S62.

[0111] In step S61, an AF session request is received, and the AF session request includes a common identifier for identifying an XRM SDF group and a time threshold. Multiple SDFs of one XRM service / application belong to the same SDF group, and the common identifiers of the SDFs in one SDF group are the same.

[0112] In one embodiment, the SDFs corresponding to a common identifier are from the same terminal or multiple terminals (a group of terminals).

[0113] In one embodiment, the AF session request may further include information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.

[0114] In some embodiments, the AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs that belong to the same SDF group in one XRM service / application have the same XRM service identifier.

[0115] In step S62, an AF session request is sent to a PCF entity, and the AF session request is used by the PCF entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.

[0116] In some embodiments, the time threshold included in the AF session request may be a time window or time value.

[0117] In some embodiments, in addition to the time threshold included in the AF session request, the PCF may determine the time threshold according to a timer or time window configured locally by the PCF entity, or according to a timer or time window recorded in operator policy, or according to a default timer or time window in contract information.

[0118] In one embodiment, a timer or time window is locally set in the PCF entity, a timer or time window is also set in the operator policy, a default timer or time window is also recorded in the contract information, and a time window or time value is included in the AF session request. The PCF can determine a time threshold based on the priorities of these timers or time windows.

[0119] The priority of each timer or time window can be determined based on pre-set rules. For example, the priority of the default timer in the contract information < the timer in the operator policy < the timer locally set by the PCF < the priority of the time window included in the AF session request. The PCF can select the timer or time window with the highest priority as the time threshold.

[0120] In the embodiments of the present disclosure, when a core network function network element receives an AF session request including a common identifier and a time threshold and sends the AF session request to the PCF, the PCF can perform policy decision on the AF session request based on the time threshold and the common identifier. Therefore, more appropriate policy decision and resource permission can be performed on the XRM service, better QoS guarantee can be provided for the SDF transmission, and it is not necessary to repeat the change of multiple policy decisions for multiple SDFs belonging to the same XRM SDF group, and the permission efficiency can be improved.

[0121] In the XRM service data transmission method provided in the embodiments of the present disclosure, the AF session request is used to perform policy decision on the AF session request identified by the same value of the common identifier received before the PCF entity reaches the time threshold. The common identifier with the same value is used to identify that multiple XRM service data flows (SDFs) belong to the same group.

[0122] In the XRM service data transmission method provided in the embodiments of the present disclosure, the policy decision includes allowing the same QoS for all SDFs in the SDF group, or generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or generating a respective PCC rule for each SDF and generating a respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0123] The PCC rule expresses the service requirements for service quality and the billing requirements for the service. The network provides different QoS services to users based on the service type and the user's contract level, detects different service data flows, and reports the billing information such as the statistical traffic and duration to the billing center for billing.

[0124] In an embodiment of the present disclosure, after determining the XRM SDF group to which the SDF belongs, the PCF can make policy decisions such as allowing the same QoS for SDFs in the same group or allowing each SDF to have its own QoS, thereby enabling the PCF to make more appropriate policy decisions and resource authorizations for XRM services and provide better QoS guarantees for SDF transmission.

[0125] In the XRM service data transmission method provided in the embodiment of the present disclosure, a policy decision for an AF session request having a common identifier sent after a time threshold is determined based on a policy decision for an AF session request sent before the time threshold.

[0126] In one embodiment, if the value of the common identifier in an AF session request sent after the time threshold is the same as the value of the common identifier in an AF session request sent before the time threshold, the policy decision for the AF session request sent after the time threshold may be the same as the policy decision for the AF session request sent before the time threshold.

[0127] For example, the policy decision for an AF session request sent by the AF before the time threshold may be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on the contract information and / or operator policy corresponding to each SDF in the SDF group. Then, the policy decision for an AF session sent by the AF after the time threshold may similarly be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on the contract information and / or operator policy corresponding to each SDF in the SDF group.

[0128] In an embodiment of the present disclosure, a policy decision for an AF session request sent by an AF after the time threshold can be determined based on an AF session request before the time threshold, and efficiency is improved because the PCF does not need to re-determine a policy decision for an AF session request received after the time threshold.

[0129] In the XRM service data transmission method provided in the embodiments of the present disclosure, the core network function network element includes an NEF entity and / or a TSCTSF entity.

[0130] In one embodiment, if the AF is a non-trusted AF, the AF sends to the PCF via the NEF and / or TSCTSF.

[0131] In the XRM service data transmission method provided in the embodiments of the present disclosure, the core network function network element can send and receive an AF session request in the following manner: (a) Setting up an AF session with required QoS procedure, (b) AF session with required QoS update procedure (c) Service specific parameter provisioning; (d) Set a policy for a future AF session.

[0132] The following describes an XRM service data transmission method according to an embodiment of the present disclosure, taking the interaction process of each entity in a core network device as an example. FIG. 8 is a flowchart of an XRM service data transmission method according to an exemplary embodiment, and as shown in FIG. 8, it includes the following steps S71 to S73.

[0133] In step S71, the AF entity sends an AF session request, and the AF session request includes a common identifier for identifying the XRM SDF group. Multiple SDFs of one XRM service / application belong to the same SDF group, and the common identifiers of the SDFs in one SDF group are the same.

[0134] In one embodiment, the SDFs corresponding to the common identifier correspond to the same terminal or to multiple terminals (a group of terminals).

[0135] In one embodiment, the AF session request may further include information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.

[0136] In some embodiments, the AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs that belong to the same SDF group in one XRM service / application have the same XRM service identifier.

[0137] In step S72, the PCF entity receives the AF session request. In step S73, the PCF entity performs a policy decision on the AF session request based on the time threshold and the common identifier.

[0138] In an embodiment of the present disclosure, an AF entity sends an AF session request, and the AF session request includes a common identifier for identifying an XRM SDF group. Therefore, after receiving the AF session request, the PCF entity can determine the XRM group to which the SDF belongs based on the common identifier. Furthermore, the PCF entity can combine a time threshold and perform policy decisions for AF session requests within the time threshold. Therefore, the PCF entity can make more appropriate policy decisions and resource authorizations for XRM services based on the time threshold and the common identifier, providing better QoS guarantees for SDF transmission and eliminating the need to repeatedly change policy decisions multiple times for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.

[0139] In the XRM service data transmission method provided in the embodiments of the present disclosure, the time threshold includes a time threshold determined based on a timer locally set by a core network device, or a time threshold determined based on a time value or time window included in an AF session request, or a time threshold determined based on a timer or time window in an operator policy, or a time threshold determined based on a default timer or time window in contract information, or a time threshold determined based on a timer locally set by a core network device, a time value or time window in an AF session request, a default timer or time window in an operator policy or contract information, and the priority of each type of value.

[0140] In the XRM service data transmission method provided in the embodiment of the present disclosure, the above step S73 in which the PCF entity makes a policy decision on the AF session request based on the time threshold and the common identifier can be realized as steps S81 to S82. As shown in Figure 9, in step S81, the PCF entity determines the common identifier of the same value received before the time threshold is reached. A common identifier with the same value is used to identify multiple XRM SDFs as belonging to the same group. In step S82, the PCF entity performs policy decisions on AF session requests identified by the common identifier of the same value.

[0141] In an embodiment of the present disclosure, the PCF entity determines a time threshold and performs policy decisions on AF session requests identified by a common identifier with the same value before the time threshold is reached, thereby allowing the PCF entity to determine SDFs that belong to the same group and make policy decisions on SDFs in the same group, thereby allowing the PCF entity to make more appropriate policy decisions and resource authorizations for XRM services and provide better QoS guarantees for SDF transmission.

[0142] In the XRM service data transmission method provided in the embodiments of the present disclosure, the policy decision includes: the PCF entity granting the same QoS to all of the SDFs in the SDF group; or the PCF entity SDF generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the group; or the PCF entity generating respective Policy Control and Charging (PCC) rules for each SDF and generating respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0143] The PCC rule expresses the service requirements for service quality and the billing requirements for the service. The network provides different QoS services to users based on the service type and the user's contract level, detects different service data flows, and reports the billing information such as the statistical traffic and duration to the billing center for billing.

[0144] In an embodiment of the present disclosure, after determining the XRM SDF group to which an SDF belongs, policy decisions can be made for SDFs in the same group, such as allowing the same QoS or allowing each SDF its own QoS, so that the core network device can make more appropriate policy decisions and resource authorizations for XRM services and provide better QoS guarantees for SDF transmission.

[0145] In the XRM service data transmission method provided in the embodiment of the present disclosure, in response to receiving an AF session request including a common identifier after the time threshold, the PCF entity performs a policy decision on the AF session request received after the time threshold based on the policy decision performed on the AF session request received before the time threshold.

[0146] In one embodiment, if the value of the common identifier in an AF session request received by a PCF entity after the time threshold is the same as the value of the common identifier in an AF session request received before the time threshold, the PCF entity may perform the same policy decision on the AF session request received after the time threshold as on an AF session request received before the time threshold.

[0147] For example, a policy decision performed by a PCF entity for an AF session request received before the time threshold may be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group. Then, a policy decision performed by a PCF entity for an AF session request received after the time threshold may similarly be to generate a respective PCC rule for each SDF and a respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0148] In an embodiment of the present disclosure, a policy decision of a PCF entity for an AF session request received after the time threshold can be determined based on an AF session request before the time threshold, and efficiency is improved because the policy decision does not need to be determined again for an AF session request received after the time threshold.

[0149] In the XRM service data transmission method provided in the embodiments of the present disclosure, the AF session request can be transmitted in the following steps: (a) Setting up an AF session with required QoS procedure, (b) AF session with required QoS update procedure (c) Service specific parameter provisioning; (d) Set a policy for a future AF session.

[0150] Hereinafter, the XRM service data transmission method provided in the embodiment of the present disclosure will be described in detail by taking step (a): Setting up an AF session with required QoS procedure as an example, as shown in FIG. 10 . 1. The AF sends an AF session request, for example, creating an AF session request through an AF session with a QoS creation request. The AF session request includes a common identifier for identifying an SDF group of an XRM service, and SDFs with the same common identifier value belong to the same XRM service. In one embodiment, the AF session request further includes a time window. In one embodiment, the AF session request further includes information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters. 2. The NEF authorizes the AF session request. If the AF is an untrusted AF, the AF sends the AF session request to the PCF via the NEF. In one embodiment, the NEF performs related mappings, including mapping from an identifier for identifying the XRM service (AF service identifier) ​​to a DNN and S-NSSAI, mapping from external applications to Core Network (CN) application identifiers, mapping from external UE identifiers to UE identifiers in the CN (e.g., Subscriber Permanent Identifier (SUPI)) based on the UDM contract information, and mapping from external to internal XRM service group identifiers based on the UDM contract information. 3. The NEF authorizes the AF session request and, based on the parameters provided by the AF, decides whether to call the TSCTSF or directly access the PCF. These signaling steps are the same as those for establishing an AF session with the required QoS program described in TS 23.502, Clause 4.15.6.6. The PCF receives the AF session request sent by the AF from the NEF or TSCTSF. The NEF triggers a policy authorization create request (Npcf_PolicyAuthorization_Create request) and sends the AF session request to the PCF, which then executes the policy decision for the AF session. 4. The PCF makes policy decisions. The PCF can determine updated or new policy decision information that needs to be sent to the SMF.

[0151] In one embodiment, the PCF determines the common identifiers of the same value that were received before the time threshold was reached and performs policy decisions on the AF session requests identified by the common identifiers of the same value.

[0152] The time threshold may be determined based on a timer locally configured by the PCF entity, or based on a time window included in the AF session request, or based on a timer in an operator policy, or based on a default timer in the contract information, or based on the priority of the timer locally configured by the PCF entity, the time window, the timer in the operator policy, and the default timer.

[0153] The policy decision performed by the PCF for AF session requests identified by the same value of the common identifier may be to allow the same QoS for SDFs in the SDF group, or to generate the same PCC rule for each SDF and generate the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or to generate a respective PCC rule for each SDF and generate a respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0154] Additionally, the PCF receives an AF session request including the common identifier after the time threshold and performs a policy decision on the AF session request received after the time threshold based on the policy decision performed on the AF session request received before the time threshold.

[0155] 5. The PCF responds to the NEF's policy authorization creation request. 6. The NEF sends an AF session response message with the QoS created to the AF, and the AF session response message contains an authorization result, which is used to inform the AF whether the AF session request is authorized or not. 7. The PCF initiates an SM policy association change request (PCC rule (QoS monitoring policy)) to the SMF.

[0156] As described in step 4, the SMF generates QoS monitoring configurations for the UPF (and for the RAN) based on the QoS policy decisions from the PCF. 8. The SMF returns an SM policy association change response to the PCF. 9. The SMF initiates an N4 session change request (QoS monitoring configuration) to the UPF. 10. After receiving the QoS monitoring configuration, the UPF enables measurement and reporting. The UPF responds to the SMF. 11. For changes requested by the SMF, the SMF invokes and transmits the communication N1N2 message ([N2 SM Information] (PDU Session ID, QFI, QoS Configuration Profile, QoS Monitoring Configuration), N1 SM Container). 12. The AMF can send an N2 ((SM information received by N2 from the SMF), NAS message (PDU session ID, N1 SM container (PDU session change command)) message to the (R)AN. After receiving the QoS monitoring configuration, the RAN enables event measurement and reporting. 13. The UE and RAN perform resource configuration. 14. The (R)AN can confirm the N2 PDU session request by sending an N2 PDU session confirmation message to the AMF. 15. The AMF forwards the N2 SM information received from the AN to the SMF via the PDU session update SM context service operation. 16. The SMF returns a PDU session update SM context response. 17-18. The SMF can update the UPF's N4 session regarding the PDU session change by sending an N4 session change request message to the UPF. Then, the PCF receives the QoS monitoring report and sends a notification to the AF.

[0157] Hereinafter, the XRM service data transmission provided in the embodiment of the present disclosure will be described in detail by taking the procedure (b): Service specific parameter provisioning procedure as an example, as shown in FIG. 11 . 0, some or all of the UEs for XRM service or multimode data service are registered with the network, and a PCF is selected to complete the AM session association. The PCF subscribes to the UDM for notification of changes in contract information for the XRM service or multimode data service based on the policies and QoS requirements of the XRM service. 1. The AF triggers the XRM service parameter service and creates an AF session request, where the AF session request includes information such as a common identifier, a UE address or identifier, and an XRM service identifier. In one embodiment, the AF session request includes time window information.

[0158] The AF provides XRM service or multiple data service specific parameters to one or more UEs related to the service via the XRM Service Parameter Service. The AF session request includes information such as a common identifier, service parameters, UE or UE group, and event subscription.

[0159] The Service Description identifies an XRM service or XRM data service and can be identified by a combination of DNN and S-NSSAI, or an XRM ID, or can be represented by an AF Service Identifier or an External Application Identifier.

[0160] Service Parameters: Information about policies and QoS-determined AF guidelines related to XRM services or multi-mode data services. Rule lists associating XRM service or multiple data service application program traffic, parameters such as UE policies, common identifiers or group identifiers, DNN and S-NSSAI groups, SSC modes, and selection priorities for corresponding rules (e.g., candidate QoS parameter priorities, time threshold priorities, access type or route selection priorities, etc.).

[0161] UE or UE Group: A single UE or multiple UEs (Group UE) related to the XRM service or multi-mode data service associated with the AF request. Subscription to events: An AF can subscribe to notifications of SM policy results or the execution and modification of AM or UE policies, or to events of XRM service data flows.

[0162] If the AF needs to update and delete the corresponding request or subscription, it may initiate the AF Session Request Update and Delete procedure via the service.

[0163] 2. The AF sends the request to the NEF. The NEF accepts the AF request. The NEF performs related mappings, including mapping from an identifier for identifying an XRM service or XRM data service (AF service identifier) ​​to a DNN and S-NSSAI, mapping from an external application to a CN application identifier, mapping from an external UE identifier to a CN UE identifier (e.g., SUPI) based on the UDM contract information, and mapping from external to internal XRM service group identifiers based on the UDM contract information. 3. The NEF stores the requested information in the UDR (for example, as service characteristic parameter information in the application program data). In one embodiment, the NEF may improve the corresponding service parameters based on local settings.

[0164] In one embodiment, the NEF may combine operator policy and contract information to determine whether the requested service characteristics can be granted for XRM services or multi-mode data services for a single UE or a group of UEs, and store the corresponding parameters in the UDR.

[0165] For example, when multiple UEs are involved, the NEF sends relevant service parameters to the PCFs, and each PCF determines or updates the corresponding authorization, policy, and rules. The PCF stores the corresponding information in the UDR based on the authorization result of the request (supporting single PCF and multiple PCF scenarios).

[0166] In a multiple UE scenario, the contract data of UE group members can be associated by XRM service indication or Group ID / Common ID.

[0167] The AF or PCF can subscribe to related XRM service or multi-mode data related event triggers via the NEF, such as QoS monitoring reports, service QoS updates, UE repositioning, PCF changes, etc. By receiving the reports from the NEF, the AF or PCF obtains the corresponding notifications and performs subsequent application requirement or QoS rule updates.

[0168] 4. The NEF returns a create request response message to the AF. In step 0, if the PCF performs a contract information update notification after the UE registration, the AF requests the UDR contract information update, so the subsequent steps are performed. 5. PCF receives the UDR contract information change notification. 6. The PCF sends the UE policy to the UE. 7. If the AF subscribes to an execution notification that notifies the XRM service-related policy, the PCF sends the related execution result to the AF via the NEF. At the same time, if there is a change in the related contract parameters, the PCF updates the change in the UDR and triggers the serving PCF of other UEs related to the XRM service group to perform policy changes and adjustments. 8. After receiving the notification, the NEF first performs mapping of internal and external related parameters, and then sends the related report to the AF.

[0169] In an embodiment of the present disclosure, the PCF determines a time threshold and executes policy decisions for SDFs with the same value of common identifiers received within the time threshold, thereby providing better QoS guarantees for SDF transmission and eliminating the need to repeatedly change policy decisions multiple times for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.

[0170] Those skilled in the art will understand that the various embodiments / examples of the present disclosure can be used in combination with the previously described examples or alone. Whether used alone or in combination with the previously described examples, the principles of implementation are the same. In the examples of the present disclosure, some examples are described as being used together. Of course, those skilled in the art will understand that such examples do not limit the examples of the present disclosure.

[0171] Based on the same idea, the embodiment of the present disclosure further provides an XRM service data transmission device.

[0172] It should be understood that the XRM service data transmission device provided in the embodiments of the present disclosure includes hardware structures and / or software modules corresponding to the execution of each function to realize the above functions. By combining the units and algorithm steps of each example disclosed in the embodiments of the present disclosure, the embodiments of the present disclosure can be realized in the form of hardware or a combination of hardware and computer software. Whether a function is implemented in the form of hardware or in the form of computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to realize the described functions depending on each specific application, but such realization should not be considered beyond the scope of the technical solution of the embodiments of the present disclosure.

[0173] 12 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to FIG. 12, the XRM service data transmission device 100 includes: a determination module 101 and an execution module 102. The determination module 101 is used to determine an application function (AF) session request, where the session request includes a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group. The enforcement module 102 is used to enforce a policy decision on the AF session request based on the time threshold and the common identifier.

[0174] In one embodiment, the time threshold includes a time threshold determined based on a timer locally set by the core network device, or a time threshold determined based on a time value or time window included in the AF session request, or a time threshold determined based on a timer or time window in an operator policy, or a time threshold determined based on a default timer or time window in the contract information, or a time threshold determined based on the priority of a timer locally set by the core network device, a time value or time window included in the AF session request, a timer or time window in an operator policy, and a default timer or time window in the contract information.

[0175] In one embodiment, performing a policy decision on an AF session request based on a time threshold and the common identifier includes determining common identifiers of the same value received before the time threshold is reached, where the common identifiers of the same value are used to identify multiple XRM service data flows (SDFs) as belonging to the same group of service data flows, and performing a policy decision on the AF session requests identified by the common identifiers of the same value.

[0176] In one embodiment, the policy decision includes allowing the same quality of service (QoS) for SDFs in the SDF group, or generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or generating respective policy control and charging (PCC) rules for each SDF and generating respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0177] In one embodiment, the enforcement module 102 is used to, in response to receiving an AF session request including the common identifier after the time threshold, execute a policy decision for the AF session request received after the time threshold based on a policy decision executed for the AF session request received before the time threshold.

[0178] 13 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to FIG. 13, the XRM service data transmission device 200 includes a receiving module 201 and an executing module 202. The receiving module 201 is used to receive an application function (AF) session request, and the AF session request includes a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group. The enforcement module 202 is used to enforce a policy decision on the AF session request based on a time threshold and a common identifier.

[0179] In one embodiment, the time threshold comprises a time threshold determined based on a timer locally set by a Policy Control Function (PCF) entity, or a time threshold determined based on a time value or time window included in the AF session request, or a time threshold determined based on a timer or time window in an operator policy, or a time threshold determined based on a default timer or time window in contract information, or a time threshold determined based on the priority of a timer or time window locally set by the PCF entity, a time value or time window included in the AF session request, a timer or time window in an operator policy, and a default timer or time window in contract information.

[0180] In one embodiment, the enforcement module 102 is used to determine the same-value common identifiers received before the time threshold is reached, and the same-value common identifiers are used to identify multiple XRM service data flows (SDFs) as belonging to the same group and to perform policy decisions on AF session requests identified by the same-value common identifiers.

[0181] In one embodiment, the policy decision includes allowing the same Quality of Service (QoS) for SDFs in the SDF group, or generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or generating respective Policy Control and Charging (PCC) rules for each SDF and generating respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0182] In one embodiment, the enforcement module 102 is used to, in response to receiving an AF session request including the common identifier after the time threshold, execute a policy decision for the AF session request received after the time threshold based on a policy decision executed for the AF session request received before the time threshold.

[0183] In one embodiment, the receiving module 101 is used to receive an AF session request sent by an AF entity or at least one functional entity of a Network Published Function (NEF) entity, a Time Sensitive Communication and Time Synchronization Function (TSCTSF) entity.

[0184] 14 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to FIG. 14, the XRM service data transmission device 300 includes a sending module 301. The sending module 301 is used to send an AF session request, where the AF session request includes a common identifier and a time threshold for identifying an Augmented Reality and Multimedia (XRM) service data flow (SDF) group, and the AF session request is used by a Policy Control Function (PCF) entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.

[0185] In one embodiment, the AF session request is used to perform policy decisions on AF session requests identified by a common identifier of the same value received before the PCF entity reaches a time threshold, and the common identifier of the same value is used to identify multiple XRM service data flows (SDFs) as belonging to the same group.

[0186] In one embodiment, the policy decision includes allowing the same quality of service (QoS) for SDFs in the SDF group, or generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or generating respective policy control and charging (PCC) rules for each SDF and generating respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0187] In one embodiment, policy decisions for AF session requests with a common identifier sent after the time threshold are determined based on policy decisions for AF session requests sent before the time threshold.

[0188] In one embodiment, the sending module 301 is used to send an AF session request to at least one functional entity of a Policy Control Function (PCF) entity, a Network Publication Function (NEF) entity, and a Time Sensitive Communication and Time Synchronization Function (TSCTSF) entity.

[0189] 15 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to FIG. 15, the XRM service data transmission device 400 includes a receiving module 401 and a sending module 402. The receiving module 401 is used to receive an application function (AF) session request, where the AF session request includes a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group. The sending module 402 is used to send an AF session request to a Policy Control Function (PCF) entity, which uses the AF session request to perform a policy decision on the AF session request based on a common identifier and a time threshold.

[0190] In one embodiment, the AF session requests are used to perform policy decisions for AF session requests identified by a common identifier of the same value received before the PCF entity reaches the time threshold, and the common identifier of the same value is used to identify multiple XRM service data flows (SDFs) as belonging to the same group.

[0191] In one embodiment, the policy decision includes granting the same Quality of Service (QoS) to SDFs in the SDF group, or generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or generating respective Policy Control and Charging (PCC) rules for each SDF and generating respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0192] In one embodiment, policy decisions for AF session requests with a common identifier sent after the time threshold are determined based on policy decisions for AF session requests sent before the time threshold.

[0193] In one embodiment, the core network device includes a Network Exposure Function (NEF) entity and / or a Time Sensitive Communications and Time Synchronization Function (TSCTSF) entity.

[0194] 16 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to FIG. 16, the XRM service data transmission device 500 includes a sending module 501, a receiving module 502, and an executing module 503. The sending module 501 is used by an application function (AF) entity to send an AF session request, and the AF session request includes a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group. The receiving module 502 is used by a policy control function (PCF) entity to receive an AF session request, and the executing module 503 is used by the PCF entity to execute a policy decision on the AF session request based on a time threshold and a common identifier.

[0195] In one embodiment, the time threshold comprises a time threshold determined based on a timer locally configured by the PCF entity, or a time threshold determined based on a time value or time window included in the AF session request, or a time threshold determined based on a timer or time window in an operator policy, or a time threshold determined based on a default timer or time window in the contract information, or a time threshold determined based on the priority of a timer locally configured by the PCF entity, a time value or time window included in the AF session request, a timer or time window in an operator policy, and a default timer or time window in the contract information.

[0196] In one embodiment, the execution module 503 is used by the PCF entity to determine common identifiers of the same value received before a time threshold is reached, the common identifiers of the same value are used to identify multiple XRM service data flows (SDFs) as belonging to the same group of service data flows, and the PCF entity executes policy decisions on AF session requests identified by the common identifiers of the same value.

[0197] In one embodiment, the policy decision includes the PCF entity granting the same quality of service (QoS) to the SDFs in the SDF group, or the PCF entity generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group, or the PCF entity generating respective policy control and charging (PCC) rules for each SDF and generating respective QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in the SDF group.

[0198] In one embodiment, the enforcement module 503, in response to receiving an AF session request including the common identifier after the time threshold, enforces a policy decision for the AF session request received after the time threshold based on a policy decision the PCF entity enforced for the AF session request received before the time threshold.

[0199] In one embodiment, the sending module 501 is used by the AF to send an AF session request to at least one of a Network Publish Function (NEF) entity, a Time Sensitive Communication and Time Synchronization Function (TSCTSF) entity, and a PCF entity.

[0200] In one embodiment, the receiving module 502 is used by the PCF to receive an AF session request sent by an AF entity or at least one functional entity of a Network Published Function (NEF) entity, a Time Sensitive Communication and Time Synchronization Function (TSCTSF) entity.

[0201] Regarding the apparatus of the above embodiment, the specific manner in which each module performs the operation is explained in detail in the embodiment of the method, and therefore will not be described in detail here.

[0202] 17 is a block diagram of an apparatus 600 used for augmented reality and multimedia service data transmission according to an exemplary embodiment. For example, the apparatus 600 can be provided as a server. Referring to FIG. 17, the apparatus 600 includes a processing component 622 including one or more processors and a memory resource represented by memory 632 for storing instructions executable by the processing component 622, such as an application program. The application program stored in the memory 632 can include one or more modules, each corresponding to a group of instructions. The processing component 622 is also configured to execute instructions for performing the above-described method.

[0203] The device 600 may further include a power component 626 configured to perform power management of the device 600, a wired or wireless network interface 650 configured to connect the device 600 to a network, and an input / output (I / O) interface 658. The device 600 may operate based on an operating system stored in the memory 632, for example, Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0204] An exemplary embodiment further provides a non-transitory computer-readable storage medium containing instructions, such as a memory 632 containing instructions, that may be executed by the processing component 622 of the device 600 to complete the method. For example, the non-transitory computer-readable storage medium may include a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0205] Furthermore, in this disclosure, it should be understood that "plurality" refers to two or more, as well as other quantifiers. "And / or" represents a relational relationship between related objects and indicates that a three-way relationship may exist. For example, A and / or B may refer to three cases: A occurring alone, A and B occurring simultaneously, or B occurring alone. The singular forms "a," "the," and "the" are intended to include the plural unless the context clearly dictates otherwise.

[0206] Furthermore, it should be understood that the meaning of words such as "in response to," "for example," etc., referred to in this disclosure may vary depending on the context and the actual usage scenario. For example, the word "in response to" as used herein may be interpreted as "when," or "if," or "if," or "then."

[0207] Furthermore, while terms such as "first" and "second" are used to describe various pieces of information, it should be understood that such information should not be limited to these terms. These terms are used only to distinguish between the same types of information and do not indicate a particular order or importance. In fact, terms such as "first" and "second" may be used interchangeably. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of this disclosure.

[0208] Additionally, although the embodiments of the present disclosure illustrate operations in a particular order in the figures, it should be understood that this does not require the operations to be performed in the particular order or sequential order shown, or that all of the operations shown must be performed to achieve a desired result. In certain environments, multitasking and parallel processing may be advantageous.

[0209] Those skilled in the art will readily be able to devise other embodiments of the present disclosure from a study of this specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure, which variations, uses, or adaptations follow the general principles of the present disclosure and include common general knowledge or ordinary technical means in the art that are not disclosed in the present disclosure.

[0210] It should be understood that the present disclosure is not limited to the exact configurations described above and illustrated in the drawings, and that various modifications and changes are possible without departing from the scope thereof, which is limited only by the appended claims.

Claims

1. 1. An augmented reality and multimedia service data transmission method performed by a core network device, comprising: determining an Application Function (AF) session request, wherein the session request includes a common identifier for identifying an Augmented Reality and Multimedia (XRM) Service Data Flow (SDF) group; and performing a policy decision on the AF session request based on a time threshold and the common identifier.

1. A data transmission method for augmented reality and multimedia services, comprising:

2. The time threshold is: a time threshold determined based on a timer locally configured by the core network device; or a time threshold determined based on a time value or time window included in the AF Session Request; or a time threshold determined based on a timer or time window in operator policy; or A time threshold determined based on a default timer or time window in the contract information, or a time threshold determined based on the priority of a timer locally set by the core network device, a time value or time window included in the AF session request, a timer or time window in the operator policy, and a default timer or time window in the contract information; The augmented reality and multimedia service data transmission method according to claim 1 .

3. performing a policy decision on the AF session request based on the time threshold and the common identifier, determining a common identifier of the same value received before the time threshold is reached, the common identifier of the same value being used to identify that multiple XRM service data flows (SDFs) belong to the same group of service data flows; and performing a policy decision on AF session requests identified by the same value common identifier.

3. The method for transmitting data for augmented reality and multimedia services according to claim 1 or 2.

4. The policy decision may be: Allowing the same Quality of Service (QoS) for the SDFs in the SDF group; or generating the same QoS for each SDF in the SDF group based on contract information and / or operator policies corresponding to each SDF; or generating respective Policy Control and Charging (PCC) rules for each SDF in the SDF group based on contract information and / or operator policies corresponding to each SDF, and generating respective QoS rules for each SDF; The method for transmitting data for augmented reality and multimedia services according to claim 3.

5. The augmented reality and multimedia service data transmission method includes: and, in response to receiving an AF session request including the common identifier after the time threshold, performing a policy decision on the AF session request received after the time threshold based on a policy decision performed on an AF session request received before the time threshold.

5. The method for transmitting data for augmented reality and multimedia services according to claim 3 or 4.

6. 1. An augmented reality and multimedia service data transmission method performed by a Policy Control Function (PCF) entity in a core network device, comprising: receiving an Application Function (AF) session request, wherein the AF session request includes a common identifier for identifying an Augmented Reality and Multimedia (XRM) Service Data Flow (SDF) group; and performing a policy decision on the AF session request based on a time threshold and the common identifier.

1. A data transmission method for augmented reality and multimedia services, comprising:

7. The time threshold is: a time threshold determined based on a timer configured locally by the Policy Control Function (PCF) entity; or a time threshold determined based on a time value or time window included in the AF Session Request; or a time threshold determined based on a timer or time window in operator policy; or A time threshold determined based on a default timer or time window in the contract information, or a time threshold determined based on the priority of a timer locally configured by the PCF entity, a time value or time window included in the AF session request, a timer or time window in the operator policy, and a default timer or time window in the contract information; The method for transmitting data for augmented reality and multimedia services according to claim 6.

8. performing a policy decision on the AF session request based on the time threshold and the common identifier, determining a common identifier of the same value received before the time threshold is reached, the common identifier of the same value being used to identify that multiple XRM service data flows (SDFs) belong to the same group of service data flows; and performing a policy decision on AF session requests identified by the same value common identifier.

8. The method for transmitting data for augmented reality and multimedia services according to claim 6 or 7.

9. The policy decision may be: Allowing the same Quality of Service (QoS) for the SDFs in the SDF group; or generating the same QoS for each SDF in the SDF group based on contract information and / or operator policies corresponding to each SDF; or generating respective Policy Control and Charging (PCC) rules for each SDF according to contract information and / or operator policies corresponding to each SDF in the SDF group, and generating respective QoS rules for each SDF; The method for transmitting data for augmented reality and multimedia services according to claim 8.

10. The augmented reality and multimedia service data transmission method includes: and, in response to receiving an AF session request including the common identifier after the time threshold, performing a policy decision on the AF session request received after the time threshold based on a policy decision performed on an AF session request received before the time threshold.

10. Augmented reality and multimedia service data transmission method according to claim 8 or 9.

11. The step of receiving an AF session request includes: receiving an AF session request sent by an AF entity or at least one functional entity of a Network Exposure Function (NEF) entity, a Time Sensitive Communications and Time Synchronization Function (TSCTSF) entity; The method for transmitting data for augmented reality and multimedia services according to claim 6.

12. 1. An augmented reality and multimedia service data transmission method performed by an Application Function (AF) entity in a core network device, comprising: transmitting an AF session request, wherein the AF session request includes a common identifier and a time threshold for identifying an Augmented Reality and Multimedia (XRM) Service Data Flow (SDF) group, and the AF session request is used by a Policy Control Function (PCF) entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.

1. A data transmission method for augmented reality and multimedia services, comprising:

13. The AF session request is used to perform policy decisions on AF session requests identified by a common identifier with the same value received by the PCF entity before the time threshold is reached, and the common identifier with the same value is used to identify multiple XRM service data flows (SDFs) belonging to the same group. The method for transmitting data for augmented reality and multimedia services according to claim 12.

14. The policy decision may be: Allowing the same Quality of Service (QoS) for the SDFs in the SDF group; or generating the same QoS for each SDF in the SDF group based on contract information and / or operator policies corresponding to each SDF; or generating respective Policy Control and Charging (PCC) rules for each SDF in the SDF group based on contract information and / or operator policies corresponding to each SDF, and generating respective QoS rules for each SDF; 14. Augmented reality and multimedia service data transmission method according to claim 12 or 13.

15. a policy decision for an AF session request having a common identifier transmitted after the time threshold is determined based on a policy decision for an AF session request transmitted before the time threshold. The method for transmitting data for augmented reality and multimedia services according to claim 12.

16. The step of sending an AF session request includes: sending an AF session request to at least one functional entity of a Policy Control Function (PCF) entity, a Network Publishing Function (NEF) entity, and a Time Sensitive Communications and Time Synchronization Function (TSCTSF) entity; The method for transmitting data for augmented reality and multimedia services according to claim 15.

17. 1. An augmented reality and multimedia service data transmission method performed by a core network function network element in a core network device, comprising: receiving an Application Function (AF) session request, the AF session request including a common identifier and a time threshold for identifying an Augmented Reality and Multimedia (XRM) Service Data Flow (SDF) group; sending the AF session request to a Policy Control Function (PCF) entity, the AF session request being used by the PCF entity to perform a policy decision on the AF session request based on the common identifier and a time threshold.

1. A data transmission method for augmented reality and multimedia services, comprising:

18. The AF session request is used to perform policy decisions on AF session requests identified by a common identifier with the same value received before the PCF entity reaches the time threshold, and the common identifier with the same value is used to identify multiple XRM service data flows (SDFs) belonging to the same group. The method for transmitting data for augmented reality and multimedia services according to claim 17.

19. The policy decision may be: Allowing the same Quality of Service (QoS) for the SDFs in the SDF group; or generating the same QoS for each SDF in the SDF group based on contract information and / or operator policies corresponding to each SDF; or generating respective Policy Control and Charging (PCC) rules for each SDF in the SDF group based on contract information and / or operator policies corresponding to each SDF, and generating respective QoS rules for each SDF; 19. Augmented reality and multimedia service data transmission method according to claim 17 or 18.

20. a policy decision for an AF session request having a common identifier transmitted after the time threshold is determined based on a policy decision for an AF session request transmitted before the time threshold.

20. The method of claim 19, wherein the data transmission method is for augmented reality and multimedia services.

21. The core network function network element includes a Network Exposure Function (NEF) entity and / or a Time Sensitive Communications and Time Synchronization Function (TSCTSF) entity; The method for transmitting data for augmented reality and multimedia services according to claim 17.

22. 1. An augmented reality and multimedia service data transmission method, comprising: an application function (AF) entity sending an AF session request, wherein the AF session request includes a common identifier for identifying an Augmented Reality and Multimedia (XRM) Service Data Flow (SDF) group; a Policy Control Function (PCF) entity receiving the AF session request; and a PCF entity performing a policy decision on the AF session request based on a time threshold and the common identifier.

1. A data transmission method for augmented reality and multimedia services, comprising:

23. The time threshold is: a time threshold determined based on a timer configured locally by said PCF entity; or a time threshold determined based on a time value or time window included in the AF Session Request; or a time threshold determined based on a timer or time window in operator policy; or A time threshold determined based on a default timer or time window in the contract information, or a time threshold determined based on the priority of a timer locally configured by the PCF entity, a time value or time window included in the AF session request, a timer or time window in the operator policy, and a default timer or time window in the contract information; 23. The method of claim 22, wherein the data transmission method is for augmented reality and multimedia services.

24. The PCF entity performing a policy decision on the AF session request based on a time threshold and the common identifier, a PCF entity determining common identifiers of the same value received before the time threshold is reached, the common identifiers of the same value being used to identify that multiple XRM service data flows (SDFs) belong to the same group of service data flows; and a PCF entity performing a policy decision on an AF session request identified by the same value of the common identifier.

24. Augmented reality and multimedia service data transmission method according to claim 22 or 23.

25. The policy decision may be: the PCF entity grants the same Quality of Service (QoS) to the SDFs in said SDF group, or the PCF entity generates the same QoS for each SDF in the SDF group based on contract information and / or operator policies corresponding to each SDF; or The PCF entity generates respective Policy Control and Charging (PCC) rules for each SDF in the SDF group based on contract information and / or operator policies corresponding to each SDF, and generates respective QoS rules for each SDF.

25. The method of claim 24, wherein the data transmission method is for augmented reality and multimedia services.

26. and in response to receiving an AF session request including the common identifier after the time threshold, the PCF entity performs a policy decision on the AF session request received after the time threshold based on a policy decision performed on the AF session request received before the time threshold.

26. Augmented reality and multimedia service data transmission method according to claim 24 or 25.

27. The step of the Application Function (AF) entity sending an AF session request includes: an AF entity sending an AF session request to at least one of a Network Exposure Function (NEF) entity, a Time Sensitive Communications and Time Synchronization Function (TSCTSF) entity, and a PCF entity; 23. The method of claim 22, wherein the data transmission method is for augmented reality and multimedia services.

28. The step of receiving the AF session request by the Policy Control Function (PCF) entity includes: a PCF entity receiving an AF session request sent by an AF entity or at least one functional entity of a Network Exposure Function (NEF) entity, a Time Sensitive Communications and Time Synchronization Function (TSCTSF) entity; 23. The method of claim 22, wherein the data transmission method is for augmented reality and multimedia services.

29. An augmented reality and multimedia service data transmission device, comprising: a decision module and an execution module; The determination module is used to determine an application function (AF) session request, wherein the session request includes a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group; the enforcement module is used to enforce a policy decision on the AF session request based on a time threshold and the common identifier.

1. An augmented reality and multimedia service data transmission device comprising:

30. An augmented reality and multimedia service data transmission device, comprising: a receiving module and an executing module; The receiving module is used to receive an application function (AF) session request, and the AF session request includes a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group; the enforcement module is used to enforce a policy decision on the AF session request based on a time threshold and the common identifier.

1. An augmented reality and multimedia service data transmission device comprising:

31. An augmented reality and multimedia service data transmission device, comprising: a transmitting module used to transmit an AF session request, the AF session request including a common identifier and a time threshold for identifying an Augmented Reality and Multimedia (XRM) Service Data Flow (SDF) group, the AF session request being used by a Policy Control Function (PCF) entity to perform a policy decision on the AF session request based on the common identifier and the time threshold; 1. An augmented reality and multimedia service data transmission device comprising:

32. An augmented reality and multimedia service data transmission device, comprising: including a receiving module and a transmitting module, The receiving module is used to receive an application function (AF) session request, wherein the AF session request includes a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group; the sending module is used to send the AF session request to a Policy Control Function (PCF) entity, the AF session request being used by the PCF entity to perform a policy decision on the AF session request based on the common identifier and a time threshold.

1. An augmented reality and multimedia service data transmission device comprising:

33. An augmented reality and multimedia service data transmission device, comprising: including a sending module, a receiving module and an executing module; The sending module is used by an application function (AF) entity to send an AF session request, and the AF session request includes a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group; The receiving module is used by a Policy Control Function (PCF) entity to receive the AF session request; the enforcement module is used by a PCF entity to enforce a policy decision on the AF session request based on a time threshold and the common identifier.

1. An augmented reality and multimedia service data transmission device comprising:

34. An augmented reality and multimedia service data transmission device, comprising: a processor; a memory for storing instructions executable by the processor; the processor is configured to execute the augmented reality and multimedia service data transmission method according to any one of claims 1 to 5, or the augmented reality and multimedia service data transmission method according to any one of claims 6 to 11, or the augmented reality and multimedia service data transmission method according to any one of claims 12 to 16, or the augmented reality and multimedia service data transmission method according to any one of claims 17 to 21, or the augmented reality and multimedia service data transmission method according to any one of claims 22 to 28, 1. An augmented reality and multimedia service data transmission device comprising:

35. A storage medium on which instructions are stored, When the instructions on the storage medium are executed by a processor of a core network device, the core network device can be caused to perform the augmented reality and multimedia service data transmission method of any one of claims 1 to 5; or when the instructions on the storage medium are executed by a processor of a Policy Control Function (PCF) entity, the PCF entity can be caused to perform the augmented reality and multimedia service data transmission method of any one of claims 6 to 11; or when the instructions on the storage medium are executed by a processor of an Application Function (AF) entity, the AF entity can be caused to perform the augmented reality and multimedia service data transmission method of any one of claims 12 to 16; or when the instructions on the storage medium are executed by a processor of a core network function network element, the core network function network element can be caused to perform the augmented reality and multimedia service data transmission method of any one of claims 17 to 21; or when the instructions on the storage medium are executed by processors of a PCF entity and an AF entity in a core network device, the PCF entity and the AF entity can be caused to perform the augmented reality and multimedia service data transmission method of any one of claims 22 to 28. A storage medium characterized by:

36. 1. A communication system comprising: Used to carry out the augmented reality and multimedia service data transmission method according to any one of claims 1 to 5, A communication system comprising:

37. 1. A communication system comprising: A Policy Control Function (PCF) entity for performing the Augmented Reality and Multimedia Service Data Transmission Method according to any one of claims 6 to 11; An Application Function (AF) entity for executing the Augmented Reality and Multimedia Service Data Transmission Method according to any one of claims 12 to 16; a core network function network element for performing the augmented reality and multimedia service data transmission method according to any one of claims 17 to 21; A communication system comprising:

Images