Augmented reality and multimedia service data transmission method, apparatus, 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 particularly to an extended reality and multimedia (XRM) service data transmission method, apparatus, and storage medium.

Background Art

[0002] Services such as mobile media services, extended reality (XR) such as cloud augmented reality (AR) / virtual reality (VR), cloud games, and remote control of machines or drones based on video contribute increasingly more traffic for the 5G network. Among these, extended reality and multimedia (XRM) services (also referred to as multimodal services) involve multimodal data. Each service data flow in the multimodal data often has a strong correlation. For example, it is necessary to synchronize the audio flow and the video flow, and it is necessary to synchronize the tactile and visual senses, etc. Such media service data flows themselves, between each data flow, and the requirements for the network transmission of these service data flows have several common characteristics. The effective identification and utilization of these characteristics are helpful for the transmission and control of the network and services, and are also helpful for service guarantee and user experience.

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

[0004] However, currently, the Policy Control Function (PCF) entity cannot determine the scope and size of an XRM service group, nor can it accurately determine the QoS authorization requirements for an XRM service group, nor can it accurately perform QoS authorization for multiple Service Data Functions (SDFs) within an XRM group. [Overview of the project] [Problems that the invention aims to solve]

[0005] To address problems present in related technologies, this disclosure provides augmented reality and multimedia service data transmission methods, apparatus, and storage media. [Means for solving the problem]

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

[0007] A second embodiment of the embodiments of the present disclosure provides an augmented reality and multimedia services data transmission method performed by a policy control function (PCF) entity in a core network device, the augmented reality and multimedia services data transmission method comprising the steps of receiving an application function (AF) session request, the AF session request including a common identifier for identifying an augmented reality and multimedia (XRM) services 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, an augmented reality and multimedia services data transmission method is provided, which is performed by an application function (AF) entity in a core network device, the augmented reality and multimedia services data transmission method comprising the step of sending an AF session request, the AF session request comprising a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) services 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] A fourth embodiment of the embodiments of the present disclosure provides an augmented reality and multimedia services data transmission method performed by a core network element function in a core network device, the augmented reality and multimedia services data transmission method comprising the steps of receiving an application function (AF) session request, the AF session request comprising a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) services data flow (SDF) group, and transmitting 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 the time threshold.

[0010] According to a fifth aspect of the embodiments of the present disclosure, an augmented reality and multimedia services data transmission device is provided, comprising a decision module and an execution module, wherein the decision module is used to determine an application function (AF) session request, the session request includes a common identifier for identifying an augmented reality and multimedia (XRM) services 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, an augmented reality and multimedia services data transmission device is provided, comprising a transmit module, a receive module, and an execute module, wherein the transmit module is used by an application function (AF) entity to transmit an AF session request, the AF session request includes a common identifier for identifying an augmented reality and multimedia (XRM) services data flow (SDF) group, the receive module is used by a policy control function (PCF) entity to receive the AF session request, and the execute 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 the embodiments of the present disclosure, an augmented reality and multimedia services data transmission device is provided, comprising a receiving module and an execution module, wherein the receiving module is used to receive application function (AF) session requests, the AF session requests include a common identifier for identifying augmented reality and multimedia (XRM) services data flow (SDF) groups, and the execution module is used to perform policy decisions on the AF session requests based on a time threshold and the common identifier.

[0013] According to an eighth aspect of an embodiment of the present disclosure, an augmented reality and multimedia services data transmission device is provided, comprising a transmission module used to transmit an AF session request, the AF session request comprising a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) services 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.

[0014] According to a ninth aspect of an embodiment of the present disclosure, an augmented reality and multimedia services data transmission device is provided, comprising a receiving module and a transmitting module, wherein the receiving module is used to receive an application function (AF) session request, the AF session request comprising a common identifier and a time threshold for identifying an augmented reality and multimedia (XRM) services data flow (SDF) group, the transmitting module is used to transmit 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 the time threshold.

[0015] According to a tenth embodiment of the embodiments of the present disclosure, an augmented reality and multimedia services data transmission device is provided, comprising a transmit module, a receive module, and an execute module, wherein the transmit module is used by an application function (AF) entity to transmit an AF session request, the AF session request includes a common identifier for identifying an augmented reality and multimedia (XRM) services data flow (SDF) group, the receive module is used by a policy control function (PCF) entity to receive the AF session request, and the execute 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 embodiment of the embodiments of the present disclosure, an augmented reality and multimedia services data transmission device is provided, 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 services data transmission method described in the first, second, third, or fourth embodiment and any one embodiment.

[0017] According to a twelfth aspect of the embodiments of this disclosure, a storage medium is provided which stores instructions, wherein when the instructions in the storage medium are executed by the processor of a core network device, the core network device can be made to execute the augmented reality and multimedia service data transmission method described in the first aspect; or when the instructions in the storage medium are executed by the processor of a policy control function (PCF) entity, the PCF entity can be made to execute the augmented reality and multimedia service data transmission method described in the second aspect; or when the instructions in the storage medium are executed by the processor of an application function (AF) entity, the AF entity can be made to execute the augmented reality and multimedia service data transmission method described in the third aspect; or when the instructions in the storage medium are executed by the processor of a core network function network element, the core network function network element can be made to execute the augmented reality and multimedia service data transmission method described in the fourth aspect; or when the instructions in the storage medium are executed by the processors of the PCF entity and AF entity in the core network device, the PCF entity and AF entity can be made to execute the augmented reality and multimedia service data transmission method described in the fifth aspect.

[0018] According to a thirteenth embodiment of the embodiments of this disclosure, a communication system is provided for performing the augmented reality and multimedia service data transmission method described in the first embodiment.

[0019] A fourteenth embodiment of the embodiments of the present disclosure provides a communication system comprising a policy control function (PCF) entity for performing the method described in the second embodiment, an application function (AF) entity for performing the method described in the third embodiment, and a core network function network element for performing the method described in any one of the fourth embodiments. [Effects of the Invention]

[0020] The technical solutions provided in the embodiments of this disclosure can achieve the following beneficial effects. The PCF receives AF session requests, which include a common identifier to identify the XRM SDF group. Based on this common identifier, the PCF can determine which group the SDF belongs to. Furthermore, the PCF can combine this with time thresholds to make policy decisions for AF session requests within those time thresholds. Therefore, based on the time thresholds and common identifiers, the PCF can make more appropriate policy decisions and resource authorizations for XRM services, providing better QoS assurance for SDF transmissions and improving authorization efficiency by eliminating the need to repeatedly change policy decisions for multiple SDFs belonging to the same XRM SDF group. [Brief explanation of the drawing]

[0021] The drawings provided herein are incorporated herein by reference, form part thereof, and illustrate embodiments consistent with the present disclosure, and are used together with the specification to illustrate the principles of the present disclosure. [Figure 1] This is a schematic diagram of a communication system according to one exemplary embodiment. [Figure 2] This is a flowchart of an augmented reality and multimedia service data transmission method according to one exemplary embodiment. [Figure 3] This is a flowchart of an augmented reality and multimedia service data transmission method according to one exemplary embodiment. [Figure 4] It is a flowchart of an extended reality and multimedia service data transmission method according to an exemplary embodiment. [Figure 5] It is a flowchart of an extended reality and multimedia service data transmission method according to an exemplary embodiment. [Figure 6] It is a flowchart of an extended reality and multimedia service data transmission method according to an exemplary embodiment. [Figure 7] It is a flowchart of an extended reality and multimedia service data transmission method according to an exemplary embodiment. [Figure 8] It is a flowchart of an extended reality and multimedia service data transmission method according to an exemplary embodiment. [Figure 9] It is a flowchart of an extended reality and multimedia service data transmission method according to an exemplary embodiment. [Figure 10] It is a flowchart of an extended reality and multimedia service data transmission method according to an exemplary embodiment. [Figure 11] It is a flowchart of an extended reality and multimedia service data transmission method according to an exemplary embodiment. [Figure 12] It is a block diagram of an extended reality and multimedia service data transmission apparatus according to an exemplary embodiment. [Figure 13] It is a block diagram of an extended reality and multimedia service data transmission apparatus according to an exemplary embodiment. [Figure 14] It is a block diagram of an extended reality and multimedia service data transmission apparatus according to an exemplary embodiment. [Figure 15] It is a block diagram of an extended reality and multimedia service data transmission apparatus according to an exemplary embodiment. [Figure 16] It is a block diagram of an extended reality and multimedia service data transmission apparatus according to an exemplary embodiment. [Figure 17]This is a block diagram of an apparatus used for augmented reality and multimedia service data transmission according to one exemplary embodiment. [Modes for carrying out the invention]

[0022] The following describes exemplary embodiments in detail, which are illustrated in the drawings. Where the drawings are referenced in the following description, unless otherwise indicated, the same numbers in different drawings represent identical or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application.

[0023] The augmented reality and multimedia service data transmission method provided in the embodiments of this disclosure is applicable to the wireless communication system shown in Figure 1. As shown in Figure 1, a mobile station accesses the wireless access network via a wireless access network device such as a base station, and the wireless access network device and 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 functionality. Wireless communication systems can employ various communication technologies, including 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. Depending on factors such as network capacity, speed, and latency, networks can be classified as 2G (generation) networks, 3G networks, 4G networks, or future advanced networks, such as 5G networks. 5G networks may also be called New Radio (NR). For convenience of explanation, this disclosure may refer to wireless communication networks as networks or systems. In this disclosure, a network may include a radio access network (RAN) and a core network (CN). The network may include network devices, which may be radio access network nodes, core network functions, etc. A radio access network node may also be called a base station. The network may provide network services to terminals via network devices, and different operators may provide different network services to terminals, and different operators may correspond to different operator networks.

[0025] A mobile station (MS), also known as 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 or in-vehicle device with wireless connectivity. Some examples of terminals today include smartphones, pocket personal computers (PPCs), handheld computers, personal digital assistants (PDAs), laptops, tablet computers, wearable devices, or in-vehicle devices.

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

[0027] The relevant entity functions related to the embodiments of this disclosure will be described in detail below. AF entities are responsible for interacting with the 3GPP® core network to provide business or service, including interactions with NEFs and policy architectures. The main functions of the NEF entity include securely exposing services and capabilities provided by 3GPP network functions, including internal or third-party disclosure, and converting or translating information that interacts with AF and internal network function interaction information, such as AF service identifiers and internal 5G core network information, such as Data Network Name (DNN) and Single Network Slice Selection Assistance Information (S-NSSAI).

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

[0029] The UPF entity is responsible for user plane functions, including user plane-related functions such as routing and transmission of data packets, packet discovery, service usage reporting, QoS processing, legitimacy monitoring, uplink packet discovery, and storage of downlink data packets. The SMF entity is responsible for session management functions, and its main functions include session management (establishing, modifying, and releasing sessions, including maintaining the tunnel between UPF and AN), UPF selection and control, service and session continuity (SSC) mode selection, and roaming, among other session-related functions.

[0030] Services such as mobile media services, extended reality (XR) including cloud augmented reality (AR) / virtual reality (VR), cloud gaming, and video-based remote control of machines or drones will contribute an increasing amount of traffic to 5G networks. Among these, extended reality and multimedia (XRM) services (also called multimodal services) involve multimodal data. Each service data flow in multimodal data is often strongly interconnected, for example, audio and video flows need to be synchronized, and haptic and visual data need to be synchronized. There are several common characteristics in the data flows of such media services themselves, between each data flow, and in the requirements for network transmission of these service data flows. Effective identification and utilization of these characteristics will be useful for network and service transmission and control, as well as for service assurance and user experience.

[0031] In related technologies, XRM services require a comprehensive consideration of the Quality of Service (QoS) characteristics of the service data flow related to the service, and it is necessary to maintain consistency in QoS permissions between multiple service data flows from a single terminal or between data flows from multiple terminals.

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

[0033] In view of this, embodiments of the present disclosure provide an XRM service data transmission method in which 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 SDF group to which the SDF belongs based on the common identifier. Furthermore, the PCF can combine time thresholds to perform policy decisions for AF session requests within the time thresholds, so that the PCF can make more appropriate policy decisions and resource authorizations for XRM services based on the time thresholds and common identifiers, providing better QoS assurance for SDF transmissions and improving authorization efficiency by eliminating the need to repeatedly change policy decisions for multiple SDFs belonging to the same XRM SDF group.

[0034] Figure 2 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in Figure 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 for a single XRM service / application belong to the same SDF group, and the common identifier of SDFs within that SDF group is the same.

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

[0036] In one embodiment, an 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, an AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs belonging to the same SDF group in a single XRM service / application will have the same XRM service identifier.

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

[0039] In the embodiments of this disclosure, the core network device determines AF session requests, which include a common identifier for identifying XRM SDF groups. Based on this common identifier, the core network device can determine the XRM group to which an SDF belongs. Furthermore, the core network device can combine time thresholds to perform policy decisions on AF session requests within the time thresholds. Based on the time thresholds and the common identifier, the core network device can make more appropriate policy decisions and resource authorizations for XRM services, providing better QoS assurance for SDF transmissions and improving authorization efficiency by eliminating the need to repeatedly change policy decisions for multiple SDFs belonging to the same XRM SDF group.

[0040] In the XRM service data transmission method provided by 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 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 the 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.

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

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

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

[0044] In one embodiment, the time threshold is determined based on the 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 10ms, the core network device can determine 10ms or 8ms (or any appropriate value less than 10ms) as the time threshold for the SDF group of that XRM service.

[0046] In one embodiment, the core network device determines a time threshold based on timers locally configured by the core network device, time windows, timers in operator policies, and the priority of default timers. For example, if a timer is set locally on the core network device, a timer is also set in the 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 can determine a 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, performs policy determination on the AF session request identified by the common identifier with the same value, so that 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 the SDF transmission.

[0051] In the XRM service data transmission method provided in the embodiments of this disclosure, policy determination includes allowing the same QoS for all SDFs in an SDF group, generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in an 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 an SDF group.

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

[0053] In the embodiments of this disclosure, after determining the XRM SDF group to which an SDF belongs, policy decisions can be made for SDFs within the same group, such as allowing the same QoS or allowing each SDF its own QoS. This allows the core network device to make more appropriate policy decisions and resource allocations for XRM services and provide better QoS assurance for SDF transmissions.

[0054] In the XRM service data transmission method provided in the embodiments of this disclosure, in response to the receipt of an AF session request containing 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 of an AF session request received after the time threshold is the same as the value of the common identifier of an AF session request received before the time threshold, the same policy decision can 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 made by the core network device for an AF session request received before the time threshold might be to generate a PCC rule for each SDF and a QoS for each SDF, based on the contract information and / or operator policy corresponding to each SDF in the SDF group. Similarly, a policy decision made by the core network device for an AF session request received after the time threshold might also be to generate a PCC rule for each SDF and a QoS for each SDF, based on the contract information and / or operator policy corresponding to each SDF in the SDF group.

[0057] In embodiments of this disclosure, the policy decision of the core network device for AF session requests received after a time threshold can be determined based on AF session requests received before the time threshold, and efficiency is improved because there is no need to determine the policy decision again for AF session requests received after the time threshold.

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

[0059] Figure 4 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in Figure 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 32.

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

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

[0062] In one embodiment, an 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, an AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs belonging to the same SDF group in a single XRM service / application will have the same XRM service identifier.

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

[0065] In the embodiments of this disclosure, the PCF receives an AF session request, which includes a common identifier for identifying an XRM SDF group. Based on this common identifier, the PCF can determine which XRM group the SDF belongs to. Furthermore, the PCF can combine time thresholds to make policy decisions for AF session requests within the time thresholds. Based on the time thresholds and the common identifier, the PCF can make more appropriate policy decisions and resource authorizations for XRM services, providing better QoS assurance for SDF transmissions and improving authorization efficiency by eliminating the need to repeatedly change policy decisions for multiple SDFs belonging to the same XRM SDF group.

[0066] In the XRM service data transmission method provided by 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 can determine a time threshold based on a timer set locally by the PCF entity. For example, if a timer locally set by a PCF entity is 10ms, the PCF can determine 10ms, 8ms, or any other time value less than 10ms as the time threshold.

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

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

[0070] In one embodiment, the time threshold is determined based on the 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 10ms, the PCF can determine 10ms or 8ms (or any appropriate value less than 10ms) as the time threshold for the SDF group of that XRM service.

[0072] In one embodiment, the PCF determines a time threshold based on the timers, time windows, timers in the operator policy, and default timer priorities set locally by the PCF entity. For example, if a timer is set locally in a PCF entity, a timer is also set in the operator policy, a default timer is recorded in the contract information, and an AF session request received by the PCF also includes a time window, the PCF can determine a 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 a plurality of 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 of the same group. The PCF can perform more appropriate policy determination and resource authorization on 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 this disclosure, policy determination includes allowing the same QoS for all SDFs in an SDF group, generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in an 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 an SDF group.

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

[0079] In the embodiments of this disclosure, after determining the XRM SDF group to which an SDF belongs, a policy decision can be made for the SDFs within the same group, such as allowing the same QoS or allowing each SDF to have its own QoS. This allows the PCF to make more appropriate policy decisions and resource allocations for XRM services and provide better QoS assurance for SDF transmissions.

[0080] In the XRM service data transmission method provided in the embodiments of this disclosure, in response to the receipt of an AF session request containing 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 of an AF session request received after the time threshold is the same as the value of the common identifier of an AF session request received before the time threshold, the same policy decision can 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, a policy decision made by PCF for an AF session request received before the time threshold might be to generate a PCC rule for each SDF and a QoS for each SDF, based on the contract information and / or operator policy corresponding to each SDF in the SDF group. Similarly, a policy decision made by PCF for an AF session request received after the time threshold might also be to generate a PCC rule for each SDF and a QoS for each SDF, based on the contract information and / or operator policy corresponding to each SDF in the SDF group.

[0083] In the embodiments of this disclosure, the PCF policy decision for AF session requests received after the time threshold can be determined based on AF session requests received before the time threshold, and efficiency is improved because there is no need to determine the policy decision again for AF session requests received after the time threshold.

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

[0085] If the AF is a trusted AF, it can send AF session requests directly to the PCF. If the AF is an untrusted AF, it sends requests to the PCF via the NEF and / or TSCTSF.

[0086] In the XRM service data transmission method provided in the embodiments of this disclosure, the PCF can receive an AF session request in the following procedure. (a) Setting up an AF session with required QoS procedure, (b) AF session procedures that require a QoS update process. (c) Procedure for setting service-specific parameters, (d) Procedure for setting a policy for a future AF session.

[0087] Based on the same concept, embodiments of this disclosure further provide methods for transmitting XRM service data performed by AF entities in a core network device.

[0088] Figure 6 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in Figure 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, which includes a common identifier and a time threshold to identify the XRM SDF group. AF session requests are used by PCF entities to make policy decisions regarding AF session requests based on a common identifier and time threshold. Multiple SDFs for a single XRM service / application belong to the same SDF group, and the common identifier of SDFs within that SDF group is the same.

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

[0091] In one embodiment, an 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, an AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs belonging to the same SDF group in a single XRM service / application will 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 a 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 determination on the AF session request based on the time threshold and the common identifier, so that more appropriate policy determination 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 determination multiple times 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 embodiments of this disclosure, an AF session request is used to perform a policy decision on AF session requests identified by a common identifier of the same value that were received before the PCF entity reached a time threshold. The common identifier of the same value is used to identify that multiple XRM service data flows (SDFs) belong to the same group.

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

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

[0101] In the embodiments of this disclosure, after determining the XRM SDF group to which an SDF belongs, the PCF can make policy decisions such as granting the same QoS to all SDFs within the same group or granting each SDF its own QoS. This allows the PCF to make more appropriate policy decisions and resource allocations for XRM services and provide better QoS assurance for SDF transmissions.

[0102] In the XRM service data transmission method provided in the embodiments of this disclosure, the policy determination of an AF session request having a common identifier, transmitted after a time threshold, is determined based on the policy determination of an AF session request transmitted before the time threshold.

[0103] In one embodiment, if the value of the common identifier of an AF session request sent after the time threshold is the same as the value of the common identifier of 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 determination for an AF session request sent by AF before the time threshold involves generating a PCC rule for each SDF and a QoS for each SDF, based on the contract information and / or operator policy corresponding to each SDF in the SDF group. Similarly, the policy determination for an AF session sent by AF after the time threshold may involve generating a PCC rule for each SDF and a QoS for each SDF, based on the contract information and / or operator policy corresponding to each SDF in the SDF group.

[0105] In embodiments of this disclosure, the policy decision for AF session requests sent by AF after a time threshold can be determined based on AF session requests made before the time threshold, eliminating the need for PCF to re-determine the policy for AF session requests received after the time threshold, thus improving efficiency.

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

[0107] In one embodiment, if the AF is a trusted AF, the AF can send an AF session request directly to the PCF. If the AF is an untrusted 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 this disclosure, the PCF can receive an AF session request in the following procedure. (a) Setting up an AF session with required QoS procedure, (b) AF session procedures that require a QoS update process. (c) Procedure for setting service-specific parameters, (d) Procedure for setting a policy for a future AF session.

[0109] Based on the same concept, embodiments of this disclosure further provide methods for transmitting XRM service data performed by core network functional network elements in a core network device.

[0110] Figure 7 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in Figure 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, which includes a common identifier and a time threshold for identifying the XRM SDF group. Multiple SDFs for a single XRM service / application belong to the same SDF group, and the common identifier of SDFs within that SDF group is the same.

[0112] In one embodiment, the SDF corresponding to the common identifier is 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, an AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs belonging to the same SDF group in a single XRM service / application will have the same XRM service identifier.

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

[0116] In some embodiments, the time threshold included in the AF session request may be a time window or a 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 by a timer or time window set locally 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.

[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 also 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 determination on the AF session request based on the time threshold and the common identifier. Therefore, more appropriate policy determination and resource authorization can be performed for 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 determinations for multiple SDFs belonging to the same XRM SDF group, and the authorization efficiency can be improved. [[ID=⑨]]

[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 determination 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 this disclosure, policy determination includes allowing the same QoS for all SDFs in an SDF group, generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in an SDF group, or generating a PCC rule for each SDF and a QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in an SDF group.

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

[0124] In the embodiments of this disclosure, after determining the XRM SDF group to which an SDF belongs, the PCF can make policy decisions such as granting the same QoS to all SDFs within the same group or granting each SDF its own QoS. This allows the PCF to make more appropriate policy decisions and resource allocations for XRM services and provide better QoS assurance for SDF transmissions.

[0125] In the XRM service data transmission method provided in the embodiments of this disclosure, the policy determination of an AF session request having a common identifier, transmitted after a time threshold, is determined based on the policy determination of an AF session request transmitted before the time threshold.

[0126] In one embodiment, if the value of the common identifier of an AF session request sent after the time threshold is the same as the value of the common identifier of 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 determination for an AF session request sent by AF before the time threshold involves generating a PCC rule for each SDF and a QoS for each SDF, based on the contract information and / or operator policy corresponding to each SDF in the SDF group. Similarly, the policy determination for an AF session sent by AF after the time threshold may involve generating a PCC rule for each SDF and a QoS for each SDF, based on the contract information and / or operator policy corresponding to each SDF in the SDF group.

[0128] In embodiments of this disclosure, the policy decision for AF session requests sent by AF after a time threshold can be determined based on AF session requests made before the time threshold, and efficiency is improved because the PCF does not need to make a new policy decision for AF session requests received after the time threshold.

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

[0130] In one embodiment, if the AF is an unreliable AF, the AF is transmitted to the PCF via the NEF and / or TSCTSF.

[0131] In the XRM service data transmission method provided in the embodiments of this disclosure, the core network function network element can send and receive AF session requests in the following procedure. (a) Setting up an AF session with required QoS procedure, (b) AF session procedures that require a QoS update process. (c) Procedure for setting service-specific parameters, (d) Procedure for setting a policy for a future AF session.

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

[0133] In step S71, the AF entity sends an AF session request, which includes a common identifier for identifying the XRM SDF group. Multiple SDFs for a single XRM service / application belong to the same SDF group, and the common identifier of SDFs within that SDF group is the same.

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

[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, an AF session request may include an XRM service identifier to identify an XRM SDF group, and SDFs belonging to the same SDF group in a single XRM service / application will have the same XRM service identifier.

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

[0138] In the embodiments of this disclosure, an AF entity sends an AF session request, which includes a common identifier for identifying an XRM SDF group. Therefore, after receiving the AF session request, a PCF entity can determine the XRM group to which the SDF belongs based on the common identifier. Furthermore, the PCF entity can combine time thresholds to perform policy decisions on AF session requests within those time thresholds. This allows the PCF entity to make more appropriate policy decisions and resource authorizations for XRM services based on the time thresholds and common identifiers, providing better QoS assurance for SDF transmissions and improving authorization efficiency by eliminating the need to repeatedly modify policy decisions for multiple SDFs belonging to the same XRM SDF group.

[0139] In the XRM service data transmission method provided in the embodiments of this 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 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 the 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 embodiments of this disclosure, step S73, in which the PCF entity performs a policy decision for an AF session request based on a time threshold and a common identifier, can be implemented as steps S81 to S82. As shown in Figure 9, in step S81, the PCF entity determines a common identifier of the same value received before the time threshold is reached. A common identifier with the same value is used to identify that multiple XRM SDFs belong to the same group. In step S82, the PCF entity performs a policy decision for AF session requests identified by a common identifier of the same value.

[0141] In embodiments of this disclosure, the PCF entity can determine SDFs belonging to the same group and make policy decisions for SDFs belonging to the same group by determining a time threshold and making policy decisions for AF session requests identified by the same common identifier before the time threshold is reached. This allows the PCF entity to make more appropriate policy decisions and resource permissions for XRM services and to provide better QoS assurance for SDF transmissions.

[0142] In the XRM service data transmission method provided in the embodiments of this disclosure, policy determination includes allowing the same QoS for all SDFs in an 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 its own Policy Control and Charging (PCC) rules for each SDF and generating its own QoS for each SDF based on contract information and / or operator policies corresponding to each SDF in an SDF group.

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

[0144] In the embodiments of this disclosure, after determining the XRM SDF group to which an SDF belongs, policy decisions can be made for SDFs within the same group, such as granting the same QoS or granting each SDF its own QoS. This allows the core network device to make more appropriate policy decisions and resource allocations for XRM services and provide better QoS assurance for SDF transmissions.

[0145] In the XRM service data transmission method provided in the embodiments of this disclosure, in response to the receipt of an AF session request containing a common identifier after a 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 common identifier value of an AF session request received by a PCF entity after a time threshold is the same as the common identifier value of an AF session request received before the time threshold, the PCF entity can perform the same policy decision on the AF session request received after the time threshold as it did on the AF session request received before the time threshold.

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

[0148] In embodiments of this disclosure, the policy decision of a PCF entity for AF session requests received after a time threshold can be determined based on AF session requests received before the time threshold, and efficiency is improved because there is no need to determine the policy decision again for AF session requests received after the time threshold.

[0149] In the XRM service data transmission method provided in the embodiments of this disclosure, an AF session request can be transmitted in the following manner. (a) Setting up an AF session with required QoS procedure, (b) AF session procedures that require a QoS update process. (c) Procedure for setting service-specific parameters, (d) Procedure for setting a policy for a future AF session.

[0150] The following describes in detail the XRM service data transmission method provided in the embodiment of this disclosure, using procedure (a): Setting up an AF session with required QoS procedure as an example, as shown in Figure 10. 1. The AF sends an AF session request, for example, creating an AF session request with an AF session that has a QoS creation request. The AF session request includes a common identifier to identify the SDF group of the 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 the UE address or UE identifier, AF identifier, application identifier, DNN, 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 the relevant mappings, including mapping from identifiers for identifying XRM services (AF service identifiers) to the DNN and S-NSSAI, mapping from external applications to Core Network (CN) application identifiers, mapping from external UE identifiers to UE identifiers within the CN based on UDM contract information (e.g., Subscriber Permanent Identifier (SUPI)), and mapping external to internal XRM service group identifiers based on 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 access the PCF directly. These signaling steps are the same as the steps to establish an AF session with the necessary QoS programs as described in TS 23.502 Section 4.15.6.6. The PCF receives the AF session request sent by the AF from either the NEF or the TSCTSF. The PCF makes a policy decision for the AF session by triggering a Policy Authorization Create request (Npcf_PolicyAuthorization_Create request) and sending the AF session request to the PCF. 4. The PCF makes policy decisions. The PCF can determine what updated or new policy decision information needs to be sent to the SMF.

[0151] In one embodiment, the PCF determines common identifiers of the same value received before a time threshold is reached and performs a policy decision for AF session requests identified by the same common identifier.

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

[0153] The policy decisions made by the PCF for AF session requests identified by a common identifier of the same value may include allowing the same QoS for all SDFs in an SDF group, generating the same PCC rule and the same QoS for each SDF based on the contract information and / or operator policy corresponding to each SDF in the SDF group, or generating separate PCC rules and the same QoS for each SDF based on the contract information and / or operator policy corresponding to each SDF in the SDF group.

[0154] Furthermore, PCF receives AF session requests containing a common identifier after the time threshold, and performs policy decisions on AF session requests received after the time threshold based on the policy decisions made on AF session requests received before the time threshold.

[0155] 5. The PCF responds to the NEF's policy permission creation request. 6. The NEF sends an AF session response message with QoS creation to the AF, and is used to notify the AF whether the AF session response message contains a permission result and whether the AF session request has been permitted. 7. The PCF initiates a request to the SMF to change the SM policy association (PCC rule (QoS monitoring policy)).

[0156] As described in Step 4, SMF generates QoS monitoring settings for UPF (and RAN) based on QoS policy decisions from PCF. 8. The SMF returns the SM policy association change response to the PCF. 9. SMF initiates an N4 session change request (QoS monitoring setting) to UPF. 10. After receiving the QoS monitoring configuration, UPF enables measurement and reporting. UPF responds to SMF. 11. For changes requested by the SMF, the SMF transmits a communication N1N2 message ([N2 SM information](PDU session ID, QFI, QoS configuration profile, QoS monitoring settings), N1 SM container). 12. The AMF can send N2 (SM information received from the SMF), NAS messages (PDU session ID, N1 SM container (PDU session change command)) to (R)AN. After receiving the QoS monitoring settings, the RAN enables event measurement and reporting. 13. UE and RAN perform resource configuration. 14. (R)AN can confirm the N2 PDU session request by sending an N2 PDU session confirmation message to 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. Subsequently, the PCF receives the QoS monitoring report and sends a notification to the AF.

[0157] The following describes in detail the XRM service data transmission provided in the embodiments of this disclosure, using procedure (b): Service specific parameter provisioning procedure as an example, as shown in Figure 11. 0. Some or all of the UEs for the XRM service or multimode data service are registered on the network, and a PCF is selected to complete the AM session association. The PCF subscribes the UDM to notifications of changes to the contract information for the XRM service or multimode data service based on the XRM service policy and QoS requirements. 1. The AF triggers the XRM service parameter service and creates an AF session request, which includes information such as a common identifier, UE address or identifier, and XRM service identifier. In one embodiment, the AF session request includes time window information.

[0158] AF provides XRM service or data service specific parameters to one or more UEs associated with a service via the XRM service parameter service. AF session requests include information such as a common identifier, service parameters, a UE or UE group, and event subscriptions.

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

[0160] Service Parameters: Information regarding policies and QoS-defined AF guidelines associated with XRM services or multimode data services. This includes parameters such as rule lists relating XRM service or multiple data service application program traffic, UE policies, common identifiers or group identifiers, DNN and S-NSSAI groups, SSC modes, and corresponding rule selection priorities (e.g., candidate QoS parameter priority, time threshold priority, access type or route selection priority).

[0161] UE or UE Group: A single UE or multiple UEs (Group UE) associated with an XRM service or multimode data service associated with an AF request. Event Subscription: AF can subscribe to notifications of SM policy results or the execution and modification of AM or UE policies. Alternatively, it can be a subscription to events in the XRM service data flow.

[0162] If AF needs to update or delete a corresponding request or subscription, it may initiate the update and deletion procedure for the AF session request through that service.

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

[0164] In one embodiment, the NEF can combine operator policies and contract information to determine whether the requested service characteristics can be permitted for an XRM service or multimode data service for a single UE or 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 PCF, and each PCF makes the corresponding decisions or updates regarding permissions, policies, and rules. Based on the permission result of the request, the PCF stores the corresponding information in the UDR. (Supports single PCF and multiple PCF scenarios)

[0166] In multiple UE scenarios, contract data for UE group members can be associated by XRM service instructions or Group ID / Common ID.

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

[0168] 4. The NEF returns a creation request response message to the AF. In Step 0, if the PCF issues a contract information update notification after UE registration, the AF requests an update to the UDR contract information, and the subsequent steps are then performed. 5. The PCF receives a notification of changes to the UDR's contract information. 6. The PCF sends the UE policy to the UE. 7. If the AF subscribes to execution notifications that inform of XRM service-related policies, the PCF sends the relevant execution results to the AF via the NEF. At the same time, if there are any changes to the relevant contract parameters, the PCF updates the UDR to update the changes, triggering other UE serving PCFs related to the XRM service group to perform policy changes and adjustments. 8. After receiving the notification, the NEF first performs the mapping of internal and external relevant parameters, and then sends the relevant report to the AF.

[0169] In embodiments of this disclosure, the PCF provides better QoS assurance for SDF transmissions by determining a time threshold and performing a policy decision on SDFs having the same common identifier received within the time threshold, thereby improving authorization efficiency by eliminating the need to repeatedly change the policy decision multiple times for multiple SDFs belonging to the same XRM SDF group.

[0170] Those skilled in the art will understand that the various embodiments / examples described above in the embodiments of this disclosure can be used in combination with the previously described embodiments or used independently. The principle of implementation is the same whether used independently or in combination with the previously described embodiments. In the embodiments of this disclosure, some embodiments are described in embodiments used together. Naturally, those skilled in the art will understand that such examples do not limit the embodiments of this disclosure.

[0171] Based on the same concept, embodiments of this disclosure further provide an XRM service data transmission device.

[0172] It should be understood that the XRM service data transmission devices provided in the embodiments of this disclosure include hardware structures and / or software modules corresponding to the execution of each function in order to realize the above functions. By combining the units and algorithmic steps of each example disclosed in the embodiments of this disclosure, the embodiments of this disclosure can be realized in hardware form or in the form of a combination of hardware and computer software. Whether a function is performed in hardware form or in the form of computer software driving the hardware depends on the specific application and design constraints of the proposed technology. A person skilled in the art may realize the described functions using different methods depending on each specific application, but such realization should not be considered to exceed the scope of the proposed technology of the embodiments of this disclosure.

[0173] Figure 12 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to Figure 12, the XRM service data transmission device 100 includes a decision module 101 and an execution module 102. The decision module 101 is used to determine an application function (AF) session request, which includes a common identifier for identifying an augmented reality and multimedia (XRM) service data flow (SDF) group. The execution module 102 is used to perform policy decisions for AF session requests 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 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 the priority of a timer locally set by the core network device, a time value or time window included in an AF session request, a timer or time window in an operator policy, and the 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 a common identifier of the same value received before the time threshold is reached, where the common identifier of the same value is 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 an AF session request identified by the common identifier of the same value.

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

[0177] In one embodiment, the execution module 102 is used to execute a policy decision on an AF session request received after a time threshold, based on a policy decision made on an AF session request received before a time threshold, in response to the receipt of an AF session request containing a common identifier after a time threshold.

[0178] Figure 13 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to Figure 13, the XRM service data transmission device 200 includes a receiving module 201 and an execution module 202. The receiving module 201 is used to receive application function (AF) session requests, which include a common identifier for identifying augmented reality and multimedia (XRM) service data flow (SDF) groups. Executor module 202 is used to perform policy decisions on AF session requests based on time thresholds and common identifiers.

[0179] In one embodiment, the time threshold includes 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 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 the priority of a timer or time window locally set by a PCF entity, a time value or time window included in an 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 execution module 102 is used to determine a common identifier of the same value received before a time threshold is reached, and the common identifier of the same value is used to identify that multiple XRM service data flows (SDFs) belong to the same group, and to perform policy decisions for AF session requests identified by the common identifier of the same value.

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

[0182] In one embodiment, the execution module 102 is used to execute a policy decision on an AF session request received after a time threshold, based on a policy decision made on an AF session request received before a time threshold, in response to the receipt of an AF session request containing a common identifier after a time threshold.

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

[0184] Figure 14 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to Figure 14, the XRM service data transmission device 300 includes a transmit module 301. The transmit module 301 is used to transmit AF session requests, which include a common identifier and a time threshold for identifying Augmented Reality and Multimedia (XRM) Service Data Flow (SDF) groups, and the AF session requests are used by a Policy Control Function (PCF) entity to perform policy decisions on the AF session requests based on the common identifier and the time threshold.

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

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

[0187] In one embodiment, the policy decision for an AF session request having a common identifier, sent after a time threshold, is determined based on the policy decision for an AF session request sent before the time threshold.

[0188] In one embodiment, the transmission module 301 is used to send an AF session request to at least one of the following functional entities: a policy control function (PCF) entity, a network exposure function (NEF) entity, and a time-sensitive communications and time synchronization function (TSCTSF) entity.

[0189] Figure 15 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to Figure 15, the XRM service data transmission device 400 includes a receiving module 401 and a transmitting module 402. The receiving module 401 is used to receive application function (AF) session requests, which include a common identifier and a time threshold for identifying augmented reality and multimedia (XRM) service data flow (SDF) groups. The transmission module 402 is used to send AF session requests to Policy Control Function (PCF) entities, which the PCF entities use to make policy decisions regarding the AF session requests based on a common identifier and a time threshold.

[0190] In one embodiment, an AF session request is used to perform a policy decision on AF session requests identified by a common identifier of the same value that were received before the PCF entity reached the time threshold, and the common identifier of the same value is used to identify that multiple XRM service data flows (SDFs) belong to the same group.

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

[0192] In one embodiment, the policy decision for an AF session request having a common identifier, sent after a time threshold, is determined based on the policy decision for an AF session request sent before the time threshold.

[0193] In one embodiment, the core network device includes network exposure function (NEF) entities and / or time-sensitive communication and time synchronization function (TSCTSF) entities.

[0194] Figure 16 is a block diagram of an XRM service data transmission device according to an exemplary embodiment. Referring to Figure 16, the XRM service data transmission device 500 includes a transmitting module 501, a receiving module 502, and an execution module 503. The transmission module 501 is used by application function (AF) entities to send AF session requests, which include a common identifier for identifying augmented reality and multimedia (XRM) service dataflow (SDF) groups. The receiving module 502 is used by policy control function (PCF) entities to receive AF session requests, and the execution module 503 is used by PCF entities to perform policy decisions on AF session requests based on time thresholds and common identifiers.

[0195] In one embodiment, the time threshold includes a time threshold determined based on a timer locally set by the 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 the priority of a timer locally set by the PCF entity, a time value or time window included in an AF session request, a timer or time window in an operator policy, and the 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 a common identifier of the same value received before a time threshold is reached, the common identifier of the same value is used to identify that multiple XRM service data flows (SDFs) belong to the same group of service data flows, and the PCF entity performs a policy decision for AF session requests identified by the common identifier of the same value.

[0197] In one embodiment, policy determination includes a PCF entity allowing the same quality of service (QoS) for SDFs within an SDF group, or a PCF entity generating the same QoS for each SDF based on contract information and / or operator policies corresponding to each SDF within an SDF group, or a PCF entity generating its own policy control and billing (PCC) rules for each SDF and generating its own QoS for each SDF based on contract information and / or operator policies corresponding to each SDF within an SDF group.

[0198] In one embodiment, in response to the receipt of an AF session request containing a common identifier after a time threshold, the execution module 503 executes a policy decision for the AF session request received after the time threshold, based on the policy decisions made by the PCF entity for the AF session requests received before the time threshold.

[0199] In one embodiment, the transmitting module 501 is used by the AF to transmit an AF session request to at least one of the following entities: a Network Exposure Function (NEF) entity, a Time Sensitive Communications and Time Synchronization Function (TSCTSF) entity, and a PCF entity.

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

[0201] The specific modes in which each module operates in relation to the apparatus of the above embodiment are described in detail in the embodiment of the method, and therefore will not be described in detail here.

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

[0203] The device 600 may further include a power component 626 configured to perform power management for 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 memory 632, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0204] In exemplary embodiments, a non-temporary computer-readable storage medium containing instructions, such as a memory 632 containing instructions, is further provided. The method can be completed by executing the instructions by a processing component 622 of the device 600. Examples of the non-temporary computer-readable storage medium include ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

[0205] Furthermore, please understand that in this disclosure, “plural” refers to two or more, and the same applies to other quantifiers. “And / or” indicates a relationship between related objects, and there may be three possible relationships. For example, A and / or B can indicate three cases: A exists alone, A and B exist together, or B exists alone. The singular forms of “one kind,” “the said,” and “the said” also include the plural form unless the context clearly indicates a different meaning.

[0206] Furthermore, it should be understood that the meanings of words such as “in response to” and “for example” as used 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 “in the case” or “if” or “then.”

[0207] Furthermore, while terms such as “first,” “second,” etc., are used to describe various types of information, it should be understood that such information should not be limited to these terms. These terms are used solely to distinguish information of the same kind from one another and do not indicate any particular order or importance. In fact, expressions such as “first,” “second,” etc., may be used interchangeably. For example, without departing from the scope of this disclosure, first information may also be called second information, and similarly, second information may also be called first information.

[0208] Furthermore, while the operations are described in a specific order in the drawings in the embodiments of this disclosure, it should be understood that this does not require the operations to be performed in a specific or sequential order shown, nor does it require all shown operations to be performed to obtain the desired results. In certain environments, multitasking and parallel processing may be advantageous.

[0209] Those skilled in the art will readily come to other embodiments of the Disclosure by examining this Specified Specified and practicing the inventions disclosed herein. This application is intended to encompass any variations, uses, or appropriate modifications of the Disclosure, which, in accordance with the general principles of the Disclosure, include common or ordinary means of the art not disclosed herein.

[0210] This disclosure is not limited to the exact configuration shown above and in the drawings, and it should be understood that various modifications and changes are possible without departing from its scope. The scope of this disclosure is limited only by the attached claims.

Claims

1. A method for transmitting augmented reality and multimedia service data performed by a core network device, A step of determining an application function (AF) session request, wherein the session request includes a common identifier for identifying an augmented reality and multimedia (XRM) service dataflow (SDF) group; The steps include: performing a policy decision for an AF session request based on a time threshold and the common identifier; The step of performing a policy decision for an AF session request based on the time threshold and the common identifier is: A step of determining a common identifier of the same value received after the AF session request has been received and before the time threshold has been reached, wherein the common identifier of the same value is used to identify that multiple XRM service data flows (SDFs) belong to the same group of service data flows, The step of performing a policy decision for AF session requests identified by the same common identifier is included, A method for transmitting augmented reality and multimedia service data, characterized by the following features.

2. The aforementioned time threshold is A time threshold determined based on a timer locally set by the core network device, or A time threshold determined based on the time value or time window included in the aforementioned AF session request, or A time threshold determined based on a timer or time window in the operator policy, or A time threshold determined based on the default timer or time window in the contract information, or This includes a timer locally configured 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 time threshold determined based on the priority of the default timer or time window in the contract information. The augmented reality and multimedia service data transmission method according to claim 1.

3. The aforementioned policy decision is Allowing the same Quality of Service (QoS) to SDFs within the aforementioned SDF group, or Based on the contract information and / or operator policy corresponding to each SDF within the SDF group, generate the same QoS for each SDF, or This includes generating policy control and billing (PCC) rules for each SDF based on contract information and / or operator policies corresponding to each SDF within the SDF group, and generating QoS for each SDF. The augmented reality and multimedia service data transmission method according to claim 1.

4. The augmented reality and multimedia service data transmission method is The process further includes the step of, in response to the receipt of an AF session request containing the common identifier after a time threshold, performing 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. The augmented reality and multimedia service data transmission method according to claim 1.

5. A method for transmitting augmented reality and multimedia service data, which is performed by a policy control function (PCF) entity in a core network device, A step of 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, The steps include: performing a policy decision for the AF session request based on a time threshold and the common identifier; The step of performing a policy decision for an AF session request based on the time threshold and the common identifier is: A step of determining a common identifier of the same value received after the AF session request has been received and before the time threshold has been reached, wherein the common identifier of the same value is used to identify that multiple XRM service data flows (SDFs) belong to the same group of service data flows, The step of performing a policy decision for AF session requests identified by the same common identifier is included, A method for transmitting augmented reality and multimedia service data, characterized by the following features.

6. The aforementioned time threshold is A time threshold determined based on a timer locally set by the Policy Control Function (PCF) entity, or A time threshold determined based on the time value or time window included in the aforementioned AF session request, or A time threshold determined based on a timer or time window in the operator policy, or A time threshold determined based on the default timer or time window in the contract information, or This includes a timer locally set 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 time threshold determined based on the priority of the default timer or time window in the contract information. The augmented reality and multimedia service data transmission method according to feature 5.

7. The aforementioned policy decision is Allowing the same Quality of Service (QoS) to SDFs within the aforementioned SDF group, or Based on the contract information and / or operator policy corresponding to each SDF within the SDF group, generate the same QoS for each SDF, or The steps include generating policy control and billing (PCC) rules for each SDF based on contract information and / or operator policies corresponding to each SDF within the SDF group, and generating QoS for each SDF, The augmented reality and multimedia service data transmission method according to feature 5.

8. The augmented reality and multimedia service data transmission method is The process further includes the step of, in response to the receipt of an AF session request containing the common identifier after a time threshold, performing 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. The augmented reality and multimedia service data transmission method according to feature 5.

9. The step of receiving the aforementioned AF session request is: The process includes receiving an AF session request sent by an AF entity, or by at least one functional entity, which is an AF entity, or a Network Exposure Function (NEF) entity, or a Time Sensitive Communications and Time Synchronization Function (TSCTSF) entity. The augmented reality and multimedia service data transmission method according to feature 5.

10. A method for transmitting augmented reality and multimedia service data, performed by an application function (AF) entity in a core network device, The steps include sending an AF session request, the AF session request including a common identifier and a time threshold for identifying a group of Augmented Reality and Multimedia (XRM) Service Dataflows (SDFs), the AF session request being used by a Policy Control Function (PCF) entity to make a policy decision on the AF session request based on the common identifier and the time threshold, the AF session request being used by the PCF entity to make a policy decision on AF session requests that have been received after the AF session request has been received and before the time threshold has been reached, identified by the same common identifier, the same common identifier is used to identify that multiple XRM Service Dataflows (SDFs) belong to the same group. A method for transmitting augmented reality and multimedia service data, characterized by the following features.

11. The step of sending the aforementioned AF session request is: The step includes sending an AF session request to at least one of the following functional entities: a Policy Control Function (PCF) entity, a Network Exposure Function (NEF) entity, and a Time Sensitive Communications and Time Synchronization Function (TSCTSF) entity. The augmented reality and multimedia service data transmission method according to claim 10.

12. The earlier core network device includes core network functional network elements, and the earlier method is A step in which a pre-core network function network element receives 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 step of a pre-core network function network element 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 time threshold, further comprising: The augmented reality and multimedia service data transmission method according to claim 1.

13. The aforementioned core network function network element includes a network exposure function (NEF) entity and / or a time-sensitive communication and time synchronization function (TSCTSF) entity. The augmented reality and multimedia service data transmission method according to claim 12.

14. Augmented reality and multimedia service data transmission device, Processor and Includes memory for storing instructions that can be executed by the processor, The processor is configured to perform the augmented reality and multimedia service data transmission method described in claim 1. An augmented reality and multimedia service data transmission device characterized by the following:

15. It is a communication system, A policy control function (PCF) entity for performing the augmented reality and multimedia service data transmission method described in claim 5, An application function (AF) entity for sending an application function (AF) session request, Includes a core network function network element for receiving the AF session request and sending the AF session request to the PCF entity, The AF session request includes a common identifier and a time threshold for identifying an Augmented Reality and Multimedia (XRM) Services Dataflow (SDF) group, and the AF session request is used by the PCF entity to make policy decisions on the AF session request based on the common identifier and the time threshold. A communication system characterized by the following features.

16. Augmented reality and multimedia service data transmission device, Processor and Includes memory for storing instructions that can be executed by the processor, The processor is configured to perform the augmented reality and multimedia service data transmission method described in claim 5. An augmented reality and multimedia service data transmission device characterized by the following:

17. Augmented reality and multimedia service data transmission device, Processor and Includes memory for storing instructions that can be executed by the processor, The processor is configured to perform the augmented reality and multimedia service data transmission method described in claim 10. An augmented reality and multimedia service data transmission device characterized by the following:

Images