WO2024152183A1 - 扩展现实和多媒体业务数据传输方法、装置及存储介质 - Google Patents

扩展现实和多媒体业务数据传输方法、装置及存储介质 Download PDF

Info

Publication number
WO2024152183A1
WO2024152183A1 PCT/CN2023/072476 CN2023072476W WO2024152183A1 WO 2024152183 A1 WO2024152183 A1 WO 2024152183A1 CN 2023072476 W CN2023072476 W CN 2023072476W WO 2024152183 A1 WO2024152183 A1 WO 2024152183A1
Authority
WO
WIPO (PCT)
Prior art keywords
session request
sdf
time threshold
policy
entity
Prior art date
Application number
PCT/CN2023/072476
Other languages
English (en)
French (fr)
Inventor
吴锦花
沈洋
毛玉欣
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2023/072476 priority Critical patent/WO2024152183A1/zh
Priority to CN202380007953.8A priority patent/CN118679720A/zh
Publication of WO2024152183A1 publication Critical patent/WO2024152183A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a method, device and storage medium for data transmission of extended reality and multimedia (Extended Reality and Media, XRM) business.
  • extended reality and multimedia Extended Reality and Media, XRM
  • Extended Reality and Media (XRM) services also called multimodal services
  • XRM Extended Reality and Media
  • the data streams of each service in multimodal data often have a strong correlation, such as the need to synchronize audio and video streams, touch and vision.
  • XRM services need to comprehensively consider the Quality of Service (QoS) characteristics of related service data flows of the services, and the QoS authorization between multiple service data flows of a single terminal or data flows of multiple terminals needs to be consistent.
  • QoS Quality of Service
  • PCF Policy Control Function
  • the present disclosure provides an extended reality and multimedia service data transmission method, device and storage medium.
  • a method, apparatus, and storage medium method for transmitting extended reality and multimedia service data are provided, which are performed by a core network device.
  • the method includes:
  • the session request includes a common identifier for identifying an extended reality and multimedia XRM service data flow SDF group;
  • a policy decision is performed on the AF session request.
  • a method, device and storage medium method for data transmission of extended reality and multimedia services are provided, which are performed by a policy control function PCF entity in a core network device, and the method includes:
  • the AF session request includes a common identifier for identifying an extended reality and multimedia XRM service data flow SDF group;
  • a policy decision is performed on the AF session request.
  • a method, device, and storage medium method for transmitting extended reality and multimedia service data are provided, which are performed by an application function AF entity in a core network device, and the method includes:
  • An AF session request is sent, wherein the AF session request includes a common identifier and a time threshold for identifying an extended reality and multimedia XRM service data flow SDF group, and the AF session request is used by a policy control function PCF entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.
  • a method, device and storage medium method for data transmission of extended reality and multimedia services are provided, which are performed by a core network element function in a core network device, and the method includes:
  • the AF session request includes a common identifier and a time threshold for identifying an extended reality and multimedia XRM service data flow SDF group;
  • the AF session request is sent to a policy control function PCF entity, where the AF session request is used by the PCF entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.
  • an apparatus for transmitting extended reality and multimedia service data including:
  • a determination module used to determine an application function AF session request, wherein the session request includes a common identifier for identifying an extended reality and multimedia XRM service data flow SDF group;
  • the execution module is used to make an execution policy decision on the AF session request based on the time threshold and the common identifier.
  • a device for transmitting extended reality and multimedia service data comprising:
  • a sending module configured for the application function entity AF to send an AF session request, wherein the AF session request includes a common identifier for identifying an extended reality and multimedia XRM service data flow SDF group;
  • a receiving module configured for a policy control function PCF entity to receive the AF session request
  • An execution module is used for the PCF entity to make an execution policy decision on the AF session request based on the time threshold and the common identifier.
  • a device for transmitting extended reality and multimedia service data comprising:
  • a receiving module configured to receive an application function AF session request, wherein the AF session request includes a common identifier for identifying an extended reality and multimedia XRM service data flow SDF group;
  • An execution module is used to make an execution policy decision on the AF session request based on a time threshold and the common identifier.
  • a device for transmitting data of an extended reality and multimedia service includes:
  • a sending module is used to send an AF session request, wherein the AF session request includes a common identifier and a time threshold for identifying an extended reality and multimedia XRM service data flow SDF group, and the AF session request is used for 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.
  • a device for transmitting extended reality and multimedia service data comprising:
  • a receiving module configured to receive an application function AF session request, wherein the AF session request includes a common identifier and a time threshold for identifying an extended reality and multimedia XRM service data flow SDF group;
  • the sending module is used to send the AF session request to a policy control function PCF entity, where the AF session request is used by the PCF entity to perform a policy decision on the AF session request based on the common identifier and a time threshold.
  • an extended reality and multimedia service data transmission device comprising: a sending module, configured for an application function entity AF to send an AF session request, wherein the AF session request comprises a common identifier for identifying an extended reality and multimedia XRM service data flow SDF group;
  • a receiving module configured for a policy control function PCF entity to receive the AF session request
  • An execution module is used for the PCF entity to make an execution policy decision on the AF session request based on the time threshold and the common identifier.
  • an extended reality and multimedia service data transmission device a processor; a memory for storing processor executable instructions; wherein the processor is configured to: execute the method described in the above-mentioned first aspect or second aspect or third aspect or fourth aspect and any one of the embodiments thereof.
  • a storage medium in which instructions are stored.
  • the core network device is enabled to execute the method described in the first aspect, or when the instructions in the storage medium are executed by a processor of a policy control function PCF entity, the PCF entity is enabled to execute the method described in the second aspect, or when the instructions in the storage medium are executed by a processor of an application function AF entity, the AF entity is enabled to execute the method described in the third aspect, or when the instructions in the storage medium are executed by a processor of a core network function network element, the core network function network element is enabled to execute the method described in the fourth aspect, or when the instructions in the storage medium are executed by the processors of the PCF entity and the AF entity in the core network device, the PCF entity and the AF entity are enabled to execute the method described in the fifth aspect.
  • a communication system is provided, wherein the system is used to execute the method described in the first aspect.
  • a communication system including the following entities:
  • a policy control function PCF entity used to execute the method described in the second aspect
  • An application function AF entity used to execute the method described in the third aspect
  • a core network functional network element used to execute the method described in any one of the fourth aspects.
  • PCF receives an AF session request, and since the AF session request includes a common identifier for identifying the XRM SDF group, PCF can determine the group to which the SDF belongs based on the common identifier. Furthermore, PCF can combine the time threshold to execute policy decisions for the AF session requests within the time threshold, so that PCF can make more reasonable policy decisions and authorize resources for the XRM service based on the time threshold and the common identifier, and provide better QoS guarantee for SDF transmission, without the need to repeatedly modify policy decisions for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.
  • Fig. 1 is a schematic diagram of a communication system according to an exemplary embodiment.
  • Fig. 2 is a flow chart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 3 is a flow chart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 4 is a flow chart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 5 is a flow chart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 6 is a flow chart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 7 is a flow chart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 8 is a flowchart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 9 is a flow chart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 10 is a flowchart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 11 is a flowchart showing a method for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 12 is a block diagram showing an apparatus for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 13 is a block diagram showing an apparatus for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 14 is a block diagram showing an apparatus for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 15 is a block diagram showing an apparatus for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 16 is a block diagram showing an apparatus for transmitting extended reality and multimedia service data according to an exemplary embodiment.
  • Fig. 17 is a block diagram showing a device for transmitting augmented reality and multimedia service data according to an exemplary embodiment.
  • the extended reality and multimedia service data transmission method provided by the embodiment of the present disclosure can be applied to the wireless communication system shown in Figure 1.
  • the mobile station accesses the wireless access network through a wireless access network device such as a base station, and the wireless access network device and the core network device complete the backhaul and forward transmission of data to perform various communication services.
  • a wireless communication system is a network that provides wireless communication functions.
  • the wireless communication system can use different communication technologies, such as code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), carrier sense multiple access/collision avoidance (Carrier Sense Multiple Access with Collision Avoidance).
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • Carrier Sense Multiple Access with Collision Avoidance Carrier Sense Multiple Access with Collision Avoidance
  • the network can be divided into 2G (generation) network, 3G network, 4G network or future evolution network, such as 5G network, 5G network can also be called new radio network (New Radio, NR
  • the present disclosure sometimes refers to the wireless communication network as a network or system.
  • the network may include a radio access network (Radio Access Network, RAN) and a core network (Core Network, CN).
  • the network includes network equipment, which may be a wireless access network node, a core network function, etc. Among them, a wireless access network node may also be referred to as a base station.
  • the network may provide network services to the terminal through the network equipment. Different operators may provide different network services to the terminal. It may also be understood that different operators correspond to different operator networks.
  • MS Mobile Station
  • UE User Equipment
  • MT Mobile Terminal
  • the terminal can be a handheld device with wireless connection function, a vehicle-mounted device, etc.
  • some examples of terminals are: smart phones (Mobile Phone), pocket computers (Pocket Personal Computer, PPC), PDAs, personal digital assistants (Personal Digital Assistant, PDA), laptops, tablet computers, wearable devices, or vehicle-mounted devices, etc.
  • the 5G system includes devices that manage and coordinate the access and mobility-related requirements of the wireless access network and terminals.
  • the 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).
  • SMF session management function
  • AMF access and mobility management function
  • RAN radio access network
  • UDM unified data management
  • PCF policy control function
  • UPF user plane function
  • UE user equipment
  • the core network functions also include other types of equipment, which will not be listed one by one in the embodiments of the present disclosure.
  • the AF entity is responsible for interacting with the 3GPP core network to provide business or services, including interaction with NEF and policy architecture.
  • the main functions include: secure open 3GPP network function to provide services and capabilities, open internally, or open to third parties, etc. Transform or translate the information interacting with AF and the internal network function interaction information, such as AF service identification and internal 5G core network information such as Data Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI), etc.
  • DNN Data Network Name
  • S-NSSAI Single Network Slice Selection Assistance Information
  • the AMF entity is responsible for access and mobility management. Its main functions include: connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management, user authentication, switching, location update and other access and mobility related functions.
  • the main functions of the PCF entity include unified policy formulation, provision of policy control, and obtaining contract information related to policy decisions from the unified database (unified data management, UDR) and other policy-related functions.
  • unified policy formulation provision of policy control
  • UDR unified data management
  • the UPF entity is responsible for user plane functions, including data packet routing and transmission, packet detection, service usage reporting, QoS processing, legal monitoring, uplink packet detection, downlink packet storage and other user plane related functions.
  • the SMF entity is responsible for session management functions. Its main functions include: session management (such as session establishment, modification and release, including tunnel maintenance between UPF and AN), UPF selection and control, service and session continuity (SSC) mode selection, roaming and other session-related functions.
  • session management such as session establishment, modification and release, including tunnel maintenance between UPF and AN
  • UPF selection and control including tunnel maintenance between UPF and AN
  • SSC service and session continuity
  • XRM extended reality and multimedia
  • the data streams of each service in multimodal data often have a strong correlation, such as the need to synchronize audio and video streams, touch and vision.
  • XRM services need to comprehensively consider the Quality of Service (QoS) characteristics of related service data flows of the services, and the QoS authorization between multiple service data flows of a single terminal or data flows of multiple terminals needs to be consistent.
  • QoS Quality of Service
  • PCF Policy Control Function
  • the disclosed embodiment provides a method for transmitting XRM service data, where the PCF receives an AF session request. Since the AF session request includes a common identifier for identifying the XRM SDF group, the PCF can determine the XRM SDF group to which the SDF belongs based on the common identifier. Furthermore, the PCF can combine the time threshold to execute policy decisions for the AF session requests within the time threshold, so that the PCF can make more reasonable policy decisions and authorize resources for the XRM service based on the time threshold and the common identifier, and provide better QoS guarantee for SDF transmission, without repeatedly modifying policy decisions for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.
  • FIG2 is a flow chart of an XRM service data transmission method according to an exemplary embodiment. As shown in FIG2 , the method is applied to a core network device and includes the following steps.
  • step S11 an AF session request is determined, and the session request includes a common identifier for identifying the XRM SDF group.
  • multiple SDFs of an XRM service/application belong to the same SDF group, and the common identifiers of the SDFs in an SDF group are the same.
  • the SDF corresponding to the common identifier corresponds to the same terminal or to multiple terminals (a terminal group).
  • the AF session request may also carry information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.
  • the AF session request may include an XRM service identifier for identifying the XRM SDF group.
  • the SDFs belonging to the same SDF group in a XRM service/application have the same XRM service identifier.
  • step S12 a policy decision is performed on the AF session request based on the time threshold and the common identifier.
  • the core network device determines the AF session request. Since the AF session request includes a common identifier for identifying the XRM SDF group, the core network device can determine the XRM group to which the SDF belongs based on the common identifier. Furthermore, the core network device can combine the time threshold to execute policy decisions for the AF session requests within the time threshold, so that the core network device can make more reasonable policy decisions and authorize resources for the XRM service based on the time threshold and the common identifier, and provide better QoS guarantee for SDF transmission, without repeatedly modifying policy decisions for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.
  • the time threshold includes:
  • a time threshold determined based on a timer locally set on a core network device or
  • the time threshold is determined based on the timer set locally on the core network device, the time value or time window in the AF session request, the operator's policy or subscription information/default timer or time window, and the priority of each type of value.
  • the core network device may determine the time threshold based on a timer locally set in the core network device.
  • the core network device may determine the time threshold to be 10 ms or 8 ms or other time values less than 10 ms.
  • the AF session request carries a time value or a time window
  • the core network device determines the time threshold based on the time window carried in the AF session request.
  • the AF session request carries a time window of 10ms-30ms, and the core network device can determine that a time threshold can be confirmed between 10ms-30ms, which is greater than 10ms and less than 30ms.
  • the core network device may determine the time threshold based on a timer or a time window in an operator policy.
  • the core network device when the core network device receives an AF session request for a certain XRM service, it can determine that the time threshold of the SDF group for the XRM service is 15ms, or a value less than 15ms considering the network status, such as 12ms.
  • the time threshold is determined based on a default timer or time window in the contract information.
  • the contract information is stored in the Unified Data Management (UDM).
  • UDM Unified Data Management
  • the core network device receives an AF session request for a certain XRM service and determines that the default timer in the subscription request for the XRM service is 10ms. Then the core network device can determine the time of the SDF group for the XRM service.
  • the time threshold is 10ms or 8ms (some suitable value less than 10ms).
  • the core network device determines the time threshold based on a timer locally set in the core network device, a time window, a timer in an operator policy, and a priority of a default timer.
  • a timer when a timer is set locally on the core network device, a timer is set in the operator policy, a default timer is recorded in the contract information, and the PCF receives an AF session request that also carries a time window, the core network device can determine the time threshold based on the priority of these timers or time windows.
  • the priority of each timer or time window can be determined based on preset rules. For example, the priority of the default timer in the contract information is lower than the timer in the operator policy, which is lower than the timer set locally by the core network device, which is lower than the priority of the time window carried in the AF session request.
  • the core network device can select the timer or time window with the highest priority as the time threshold.
  • the execution policy decision on the AF session request based on the time threshold and the common identifier in the above step S12 can be implemented as steps S21-S22, as shown in FIG3:
  • step S21 the core network device determines the common identifier with the same value received before the time threshold is reached.
  • the common identifier with the same value is used to identify that multiple XRM SDFs belong to the same group.
  • step S22 the core network device executes a policy decision on the AF session request identified by the common identifier with the same value.
  • the core network device determines a time threshold and executes a policy decision on the AF session request identified by the common identifier with the same value before the time threshold is reached, so that the core network device can determine the SDFs belonging to the same group and make policy decisions for the same group of SDFs, so that the core network device can make more reasonable policy decisions and authorize resources for the XRM service, and provide more optimized QoS guarantee for SDF transmission.
  • the policy decision includes:
  • a Policy Control and Charging (PCC) rule is generated for each SDF, and a QoS is generated for each SDF.
  • PCC Policy Control and Charging
  • the PCC rules represent the service quality requirements and service billing requirements of the service.
  • the network will provide different QoS services to users based on the service type and the user's contract level, and report the billing information such as traffic and duration to the billing center for billing by detecting different service data flows.
  • policy decisions can be made for the SDFs in the same group, such as authorizing the same QoS or authorizing each SDF for its own QoS, so that the core network device It can make more reasonable policy decisions and authorize resources for XRM services, and provide better QoS guarantee for SDF transmission.
  • a policy decision is executed on the AF session request received after the time threshold based on the policy decision executed on the AF session request received before the time threshold.
  • the same policy decision as that of the AF session request received before the time threshold can be executed on the AF session request received after the time threshold.
  • the policy decision executed by the core network device for the AF session request received before the time threshold is based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision executed by the core network device for the AF session request received after the time threshold can also be based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision of the AF session request received by the core network device after the time threshold can be determined based on the AF session request before the time threshold, without the need to redetermine the policy decision for the AF session request received after the time threshold, thus saving efficiency.
  • the following describes the XRM service data transmission method provided by the embodiment of the present disclosure by taking the PCF entity in the core network device as the execution subject.
  • FIG4 is a flow chart of an XRM service data transmission method according to an exemplary embodiment. As shown in FIG4 , the method is executed by a PCF entity in a core network device and includes the following steps.
  • step S31 an AF session request is received, which includes a common identifier for identifying the XRM SDF group.
  • multiple SDFs of an XRM service/application belong to the same SDF group, and the common identifiers of the SDFs in an SDF group are the same.
  • the SDFs corresponding to the common identifiers are from the same terminal or from multiple terminals (a terminal group).
  • the AF session request may also carry information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.
  • the AF session request may include an XRM service identifier for identifying the XRM SDF group, and the SDFs belonging to the same SDF group in an XRM service/application have the same XRM service identifier.
  • step S32 a policy decision is performed on the AF session request based on the time threshold and the common identifier.
  • the PCF receives the AF session request. Since the AF session request includes a message for identifying the XRM The common identifier of the SDF group, so the PCF can determine the XRM group to which the SDF belongs based on the common identifier. Furthermore, the PCF can combine the time threshold to execute policy decisions for AF session requests within the time threshold, so that the PCF can make more reasonable policy decisions and authorize resources for XRM services based on the time threshold and common identifier, and provide better QoS guarantee for SDF transmission, without repeatedly modifying policy decisions for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.
  • the time threshold includes:
  • the time threshold is determined based on the timer set locally by the PCF entity, the time value or time window in the AF session request, the operator policy or subscription information/default timer or time window, and the priority of each type of value.
  • the PCF may determine the time threshold based on a timer locally set by the PCF entity.
  • the PCF may determine the time threshold to be 10 ms or 8 ms or other time values less than 10 ms.
  • the AF session request carries a time value or a time window
  • the PCF determines the time threshold based on the time window carried in the AF session request.
  • the AF session request carries a time window of 10ms-30ms, and the PCF may determine that a time threshold may be confirmed between 10ms-30ms, which is greater than 10ms and less than 30ms.
  • the PCF may determine the time threshold based on a timer or time window in the operator's policy.
  • the PCF when the PCF receives an AF session request for a certain XRM service, it can determine that the time threshold of the SDF group for the XRM service is 15ms, or a value less than 15ms considering the network status, such as 12ms.
  • the time threshold is determined based on a default timer or time window in the contract information.
  • the contract information is stored in the Unified Data Management (UDM).
  • UDM Unified Data Management
  • PDF receives an AF session request for an XRM service and determines that the default timer in the contract request for the XRM service is 10ms. Then PCF can determine that the time threshold of the SDF group for the XRM service is 10ms or 8ms (a suitable value less than 10ms).
  • the PCF determines the time threshold based on a timer set locally by the PCF entity, a time window, a timer in an operator policy, and a priority of a default timer.
  • the PCF may determine the time threshold according to the priority of these timers or time windows.
  • the priority of each timer or time window can be determined based on preset rules. For example, the priority of the default timer in the subscription information is lower than the timer in the operator policy, lower than the timer set locally by the PCF, and lower than the priority of the time window carried in the AF session request.
  • the PCF can select the timer or time window with the highest priority as the time threshold.
  • the execution policy decision on the AF session request based on the time threshold and the common identifier in the above step S32 can be implemented as steps S41-S42, as shown in FIG5:
  • step S41 the PCF entity determines the common identifiers of the same value received before the time threshold is reached.
  • the common identifier with the same value is used to identify that multiple XRM SDFs belong to the same group.
  • step S42 the PCF entity executes a policy decision on the AF session request identified by the common identifier with the same value.
  • the PCF determines a time threshold and executes a policy decision on the AF session request identified by the common identifier with the same value before the time threshold is reached, so that the PCF can determine the SDFs belonging to the same group and make policy decisions for the same group of SDFs, so that the PCF can make more reasonable policy decisions and authorize resources for the XRM service, and provide more optimized QoS guarantee for SDF transmission.
  • the policy decision includes:
  • a Policy Control and Charging (PCC) rule is generated for each SDF, and a QoS is generated for each SDF.
  • PCC Policy Control and Charging
  • the PCC rules represent the service quality requirements and service billing requirements of the service.
  • the network will provide different QoS services to users based on the service type and the user's contract level, and report the billing information such as traffic and duration to the billing center for billing by detecting different service data flows.
  • policy decisions can be made for the SDFs in the same group, such as authorizing the same QoS or authorizing each SDF to have its own QoS, etc., so that the PCF can make more reasonable policy decisions and authorize resources for the XRM service, providing better QoS guarantees for the transmission of the SDF.
  • a policy decision is executed on the AF session request received after the time threshold based on the policy decision executed on the AF session request received before the time threshold.
  • the AF session request received after the time threshold may be processed.
  • the AF session request that is received before the time threshold performs the same policy decision as the AF session request that was received before the time threshold.
  • the policy decision executed by the PCF for the AF session request received before the time threshold is based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision executed by the PCF for the AF session request received after the time threshold can also be based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision of the AF session request received by the PCF after the time threshold can be determined based on the AF session request before the time threshold, without redetermining the policy decision for the AF session request received after the time threshold, thus saving efficiency.
  • the AF session request received by the PCF may be directly sent by the AF entity; or sent by the AF entity to the NEF entity, which in turn sends it to the PCF; or sent by the AF entity to a time sensitive communication and time synchronization function (TSCTSF) entity, which in turn sends it to the PCF; or sent by the AF entity to the NEF, which in turn sends it to the TSCTSF entity, which in turn sends it to the PCF; or sent by the AF entity to the NEF, which in turn sends it to the TSCTSF entity, which in turn sends it to the PCF.
  • TSCTSF time sensitive communication and time synchronization function
  • the AF can directly send the AF session request to the PCF.
  • the AF sends the AF session request to the PCF via the NEF and/or the TSCTSF.
  • the PCF may receive an AF session request in the following process:
  • an embodiment of the present disclosure also provides an XRM service data transmission method performed by an AF entity in a core network device.
  • FIG6 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in FIG6 , the XRM service data transmission method is executed by an AF entity in a core network device and includes the following steps.
  • step S51 an AF session request is sent, which includes a common identifier and a time threshold for identifying the XRM SDF group.
  • the AF session request is used by the PCF entity to execute a policy on the AF session request based on the common identifier and time threshold. decision making.
  • multiple SDFs of an XRM service/application belong to the same SDF group, and the common identifiers of the SDFs in an SDF group are the same.
  • the SDFs corresponding to the common identifiers are from the same terminal or from multiple terminals (a terminal group).
  • the AF session request may also carry information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.
  • the AF session request may include an XRM service identifier for identifying the XRM SDF group, and the SDFs belonging to the same SDF group in an XRM service/application have the same XRM service identifier.
  • the time threshold included in the AF session request may be a time window or a time value.
  • the PCF may also determine the time threshold through a timer or time window set locally by the PCF entity, or determine the time threshold through a timer or time window recorded in the operator policy, or determine the time threshold through a default timer or time window in the contract information.
  • a timer or time window is locally set for a PCF entity, a timer or time window is also set in an operator policy, a default timer or time window is also recorded in the contract information, and a time window or time value is also carried in an AF session request, the PCF may determine the time threshold based on the priority of these timers or time windows.
  • the priority of each timer or time window can be determined based on preset rules. For example, the priority of the default timer in the subscription information is lower than the timer in the operator policy, lower than the timer set locally by the PCF, and lower than the priority of the time window carried in the AF session request.
  • the PCF can select the timer or time window with the highest priority as the time threshold.
  • AF sends an AF session request including a common identifier and a time threshold, so that PCF can execute policy decisions on the AF session request based on the time threshold and the common identifier, thereby making more reasonable policy decisions and authorizing resources for the XRM service, providing better QoS guarantee for SDF transmission, and eliminating the need to repeatedly modify policy decisions for multiple SDFs belonging to the same XRMSDF group, thereby improving authorization efficiency.
  • an AF session request is used by a PCF entity to execute a policy decision for an AF session request identified by 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 SDF belong to the same group.
  • the policy decision includes:
  • each SDF Based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, each SDF generates its own PCC rules are applied and QoS is generated for each SDF.
  • the PCC rules represent the service quality requirements and service billing requirements of the service.
  • the network will provide different QoS services to users based on the service type and the user's contract level, and report the billing information such as traffic and duration to the billing center for billing by detecting different service data flows.
  • the PCF after the PCF determines the XRM SDF group to which the SDF belongs, it can make policy decisions for the SDFs in the same group, such as authorizing the same QoS or authorizing each SDF to have its own QoS, etc., so that the PCF can make more reasonable policy decisions and authorize resources for the XRM service, and provide better QoS guarantees for the transmission of the SDF.
  • a policy decision of an AF session request with a common identifier sent after a time threshold is determined based on a policy decision of an AF session request sent before the time threshold.
  • the policy decision of the AF session request sent after the time threshold can be the same as the policy decision of the AF session request sent before the time threshold.
  • the policy decision of the AF session request sent by the AF before the time threshold is based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision of the AF session sent by the AF after the time threshold can also be based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision of the AF session request sent by the AF after the time threshold can be determined based on the AF session request before the time threshold, and the PCF does not need to redetermine the policy decision for the AF session request received after the time threshold, thereby saving efficiency.
  • the AF sends an AF session request to at least one functional entity among a PCF entity, a NEF entity, and a TSCTSF entity.
  • the AF when the AF is a trusted AF, the AF may directly send the AF session request to the PCF.
  • the AF when the AF is an untrusted AF, the AF sends the AF session request to the PCF via the NEF and/or the TSCTSF.
  • the PCF may receive an AF session request in the following process:
  • an embodiment of the present disclosure also provides an XRM service data transmission method executed by a core network function network element in a core network device.
  • FIG7 is a flowchart of an XRM service data transmission method according to an exemplary embodiment. As shown in FIG7 , the XRM service data transmission method is executed by a core network function network element in a core network device, and includes the following steps.
  • 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 of an XRM service/application belong to the same SDF group, and the common identifiers of the SDFs in an SDF group are the same.
  • the SDFs corresponding to the common identifiers are from the same terminal or from multiple terminals (a terminal group).
  • the AF session request may also carry information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.
  • the AF session request may include an XRM service identifier for identifying the XRM SDF group, and the SDFs belonging to the same SDF group in an XRM service/application have the same XRM service identifier.
  • step S62 an AF session request is sent to the PCF entity, where the AF session request is used by the PCF entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.
  • the time threshold included in the AF session request may be a time window or a time value.
  • the PCF may also determine the time threshold through a timer or time window set locally by the PCF entity, or determine the time threshold through a timer or time window recorded in the operator policy, or determine the time threshold through a default timer or time window in the contract information.
  • a timer or time window is locally set for a PCF entity, a timer or time window is also set in an operator policy, a default timer or time window is also recorded in the contract information, and a time window or time value is also carried in an AF session request, the PCF may determine the time threshold based on the priority of these timers or time windows.
  • the priority of each timer or time window can be determined based on preset rules. For example, the priority of the default timer in the subscription information is lower than the timer in the operator policy, lower than the timer set locally by the PCF, and lower than the priority of the time window carried in the AF session request.
  • the PCF can select the timer or time window with the highest priority as the time threshold.
  • the core network function network element receives the AF session request including the common identifier and the time threshold, and sends the AF session request to the PCF, so that the PCF can perform policy decisions on the AF session request based on the time threshold and the common identifier, thereby making more reasonable policy decisions and authorizing resources for the XRM service, and providing more reasonable policy decisions and authorization resources for SDF transmission.
  • Excellent QoS guarantee no need to repeatedly modify policy decisions for multiple SDFs belonging to the same XRM SDF group, improving authorization efficiency.
  • an AF session request is used by a PCF entity to execute a policy decision for an AF session request identified by 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 SDF belong to the same group.
  • the policy decision includes:
  • a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the PCC rules represent the service quality requirements and service billing requirements of the service.
  • the network will provide different QoS services to users based on the service type and the user's contract level, and report the billing information such as traffic and duration to the billing center for billing by detecting different service data flows.
  • the PCF after the PCF determines the XRM SDF group to which the SDF belongs, it can make policy decisions for the SDFs in the same group, such as authorizing the same QoS or authorizing each SDF to have its own QoS, etc., so that the PCF can make more reasonable policy decisions and authorize resources for the XRM service, and provide better QoS guarantees for the transmission of the SDF.
  • a policy decision of an AF session request with a common identifier sent after a time threshold is determined based on a policy decision of an AF session request sent before the time threshold.
  • the policy decision of the AF session request sent after the time threshold can be the same as the policy decision of the AF session request sent before the time threshold.
  • the policy decision of the AF session request sent by the AF before the time threshold is based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision of the AF session sent by the AF after the time threshold can also be based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision of the AF session request sent by the AF after the time threshold can be determined based on the AF session request before the time threshold, and the PCF does not need to redetermine the policy decision for the AF session request received after the time threshold, thereby saving efficiency.
  • the core network function network element includes a NEF entity and/or a TSCTSF entity.
  • the AF when the AF is an untrusted AF, the AF sends the information to the PCF via the NEF and/or the TSCTSF.
  • the core network function 10,000 may receive and send an AF session request in the following process:
  • the following describes an XRM service data transmission method proposed in an embodiment of the present disclosure based on the interaction process between various entities in a core network device.
  • FIG8 is a flow chart of an XRM service data transmission method according to an exemplary embodiment. As shown in FIG8 , the method includes the following steps.
  • step S71 the AF entity sends an AF session request, which includes a common identifier for identifying the XRM SDF group.
  • multiple SDFs of an XRM service/application belong to the same SDF group, and the common identifiers of the SDFs in an SDF group are the same.
  • the SDF corresponding to the common identifier corresponds to the same terminal or to multiple terminals (a terminal group).
  • the AF session request may also carry information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.
  • the AF session request may include an XRM service identifier for identifying the XRM SDF group, and the SDFs belonging to the same SDF group in an XRM service/application have the same XRM service identifier.
  • step S72 the PCF entity receives the AF session request.
  • step S73 the PCF entity performs a policy decision on the AF session request based on the time threshold and the common identifier.
  • the AF entity sends an AF session request. Since the AF session request includes a common identifier for identifying an XRM SDF group, the PCF entity can determine the XRM group to which the SDF belongs based on the common identifier after receiving the AF session request. Furthermore, the PCF entity can combine the time threshold to perform policy decisions for the AF session requests within the time threshold, so that the PCF entity can make more reasonable policies for the XRM service based on the time threshold and the common identifier. It can make strategic decisions and authorize resources to provide better QoS guarantee for SDF transmission, without the need to repeatedly modify the policy decisions of multiple SDFs belonging to the same XRM SDF group, thus improving the authorization efficiency.
  • the time threshold includes:
  • a time threshold determined based on a timer locally set on a core network device or
  • the time threshold is determined based on the timer set locally on the core network device, the time value or time window in the AF session request, the operator's policy or subscription information/default timer or time window, and the priority of each type of value.
  • the PCF entity in the above step S73 performs a policy decision on the AF session request based on the time threshold and the common identifier, which can be implemented as steps S81-S82, as shown in FIG9 :
  • step S81 the PCF entity determines the common identifier of the same value received before the time threshold is reached.
  • the common identifier with the same value is used to identify that multiple XRM SDFs belong to the same group.
  • step S82 the PCF entity executes a policy decision on the AF session request identified by the common identifier with the same value.
  • the PCF entity determines a time threshold and executes a policy decision on the AF session request identified by the common identifier with the same value before the time threshold is reached, so that the PCF entity can determine the SDFs belonging to the same group and make policy decisions for the same group of SDFs, so that the PCF entity can make more reasonable policy decisions and authorize resources for the XRM service, and provide more optimized QoS guarantee for SDF transmission.
  • the policy decision includes:
  • the PCF entity authorizes the same QoS to all SDFs in the SDF group; or
  • the PCF entity generates the same QoS for each SDF in the SDF group based on the subscription information and/or operator policy corresponding to each SDF; or
  • the PCF entity generates Policy Control and Charging (PCC) rules for each SDF based on the contract information and/or operator policy corresponding to each SDF in the SDF group, and generates QoS for each SDF.
  • PCC Policy Control and Charging
  • the PCC rules represent the service quality requirements and service billing requirements of the service.
  • the network will provide different QoS services to users based on the service type and the user's contract level, and report the billing information such as traffic and duration to the billing center for billing by detecting different service data flows.
  • policy decisions can be made for the SDFs in the same group, such as authorizing the same QoS or authorizing each SDF for its own QoS, so that the core network device It can make more reasonable policy decisions and authorize resources for XRM services, and provide better QoS guarantee for SDF transmission.
  • the PCF entity in response to receiving an AF session request including a common identifier after a time threshold, executes a policy decision on the AF session request received after the time threshold based on the policy decision executed on the AF session request received before the time threshold.
  • the PCF entity may execute the same policy decision for the AF session request received after the time threshold as for the AF session request received before the time threshold.
  • the policy decision executed by the PCF entity for the AF session request received before the time threshold is based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision executed by the PCF entity for the AF session request received after the time threshold can also be based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and a respective PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision of the AF session request received by the PCF entity after the time threshold can be determined based on the AF session request before the time threshold, without redetermining the policy decision for the AF session request received after the time threshold, thus saving efficiency.
  • an AF session request may be transmitted in the following process:
  • AF sends an AF session request, for example, creates an AF session request through an AF session with a QoS creation request.
  • the AF session request includes a common identifier for an SDF group that identifies an XRM service, and SDFs with the same common identifier belong to the same XRM service.
  • the AF session request also includes a time window.
  • the AF session request also includes information such as a UE address or UE identifier, an AF identifier, an application identifier, a DNN, an S-NSSAI, and QoS parameters.
  • NEF authorizes AF session request. If AF is an untrusted AF, AF sends AF session request to PCF through NEF.
  • NEF performs relevant mapping, including mapping of XRM service identifier (AF service identifier) to DNN and S-NSSAI, mapping of external application to core network (Core Network, CN) application identifier; and mapping of external UE identifier to UE identifier within CN based on UDM contract information (such as Subscriber Permanent Identifier, SUPI), as well as mapping of external to internal XRM service group identifier according to UDM contract information.
  • AF service identifier mapping of XRM service identifier
  • CN Core Network
  • UDM contract information such as Subscriber Permanent Identifier, SUPI
  • NEF authorizes the AF session request and determines whether to call TSCTSF or contact PCF directly based on the parameters provided by AF. These signaling steps are the same as the steps for setting up an AF session with the required QoS program in TS 23.502 Section 4.15.6.6.
  • PCF receives the AF session request sent by AF from NEF or TSCTSF.
  • NEF triggers a policy authorization create request (Npcf_PolicyAuthorization_Create request) and sends the AF session request to PCF for PCF to execute policy decisions on the AF session.
  • PCF makes policy decisions. PCF may determine updated or new policy decision information that needs to be sent to SMF.
  • the PCF determines the common identifiers with the same value received before the time threshold is reached, and executes a policy decision on the AF session request identified by the common identifiers with the same value.
  • the time threshold can be determined based on a timer set locally by the PCF entity; or based on a time window carried in an AF session request; or based on a timer in an operator policy; or based on a default timer in the contract information; or based on a timer set locally by the PCF entity, a time window, a timer in an operator policy, and a priority of a default timer.
  • the policy decision executed by the PCF for the AF session request identified by the common identifier with the same value can be to authorize the same QoS for the SDFs in the SDF group; or based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, generate the same PCC rules for each SDF and generate the same QoS for each SDF; or based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, generate respective PCC rules for each SDF and generate respective QoS for each SDF.
  • the PCF receives an AF session request including the common identifier after the time threshold, and executes a policy decision on the AF session request received after the time threshold based on the policy decision executed for the AF session request received before the time threshold.
  • PCF responds to NEF with a policy authorization creation request.
  • NEF sends an AF session response message with QoS creation to AF.
  • the AF session response message carries the authorization result, which is used to inform AF whether the AF session request is authorized.
  • PCF initiates an SM policy association modification request (PCC rule (QoS monitoring policy)) to SMF.
  • PCC rule QoS monitoring policy
  • the SMF Based on the QoS policy decisions from the PCF, the SMF generates QoS monitoring information for the UPF (and for the RAN) Configure as described in step 4.
  • SMF initiates an N4 session modification request (QoS monitoring configuration) to UPF.
  • UPF After receiving the QoS monitoring configuration, UPF enables measurement and reporting. UPF responds to SMF.
  • N1N2 message transmission [N2 SM information] (PDU session ID, QFI, QoS profile, QoS monitoring configuration), N1 SM container).
  • AMF may send N2 (SM information received by N2 from SMF), NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command)) message to (R)AN.
  • N2 SM information received by N2 from SMF
  • NAS message PDU Session ID, N1 SM container (PDU Session Modification Command)
  • R RAN enables event measurement and reporting.
  • UE and RAN perform resource configuration.
  • (R)AN may confirm the N2 PDU session request by sending an N2 PDU session confirm message to the AMF.
  • AMF forwards the N2 SM information received from AN to SMF via the PDU session update SM context service operation.
  • SMF can update the N4 session of UPF involved in the PDU session modification by sending an N4 session modification request message to UPF.
  • PCF receives the QoS monitoring report, it sends a notification to AF.
  • Some or all UEs related to XRM service or multi-mode data service have registered with the network and selected PCF to complete AM session association.
  • PCF subscribes to UDM for change notifications of contract information related to XRM service or multi-mode data service according to the policy and QoS requirements of XRM service.
  • AF triggers XRM service parameter service and creates an AF session request, which includes information such as common identifier, UE address or identifier, XRM service identifier, etc.
  • the AF session request carries time window information.
  • the AF provides XRM services or multiple data service specific parameters to one or more UEs related to the service through the XRM service parameter service.
  • the AF session request includes: common identification, service parameters (Service Parameters), UE or UE group, subscription to events (Subscription to events) and other information.
  • the service description identifies the XRM service or XRM data service, which can be identified by a combination of DNN and S-NSSAI, or XRM ID; or represented by AF service identifier (Service-Identifier) or external application identifier (Application Identifier).
  • Service Parameters Policy and QoS related to XRM services or multi-mode data services.
  • UE or UE group A single UE or multiple UEs (Group UE) related to the XRM service or multi-mode data service associated with the AF request.
  • AF can subscribe to notifications about SM policy results or the execution and changes of AM policies or UE policies. Or, event subscription of XRM business data stream.
  • the update or deletion process of the AF session request can also be initiated through this service.
  • AF sends the request to NEF.
  • NEF authorizes AF's request.
  • NEF performs relevant mappings, including mapping of XRM service or XRM data service (AF service identifier) to DNN and S-NSSAI, mapping of external application to CN application identifier; and mapping of external UE identifier to UE identifier within CN (such as SUPI) based on UDM contract information, as well as mapping of external to internal XRM service group identifier according to UDM contract information.
  • NEF stores the requested information in UDR (eg, as service characteristic parameter information storage of application data). In one implementation, NEF may improve the corresponding service parameters according to the local configuration.
  • the NEF may combine the operator's policy and subscription information to confirm whether the requested service feature is authorizable for an XRM service or a multi-mode data service for a single UE or a UE group and store the corresponding parameters in the UDR.
  • the NEF transmits the relevant service parameters to the PCF, and performs the corresponding authorization in each PCF, as well as the decision or update of policies and rules.
  • the PCF stores the corresponding information in the UDR based on the authorization result of the request.
  • the contract data of UE group members can be associated through XRM service indication or Group ID/Common ID.
  • AF or PCF can subscribe to relevant XRM services or multi-mode data related event triggers through NEF, such as QoS monitoring report, service QoS update, UE relocation, PCF change, etc.
  • NEF such as QoS monitoring report, service QoS update, UE relocation, PCF change, etc.
  • AF or PCF receives NEF report, obtains corresponding notification, and executes subsequent application requirements or QoS rule updates.
  • NEF returns a create request response message to AF.
  • step 0 the PCF executes the subscription information update notification after the UE is registered, the subsequent process is executed because the AF requests to update the UDR subscription information
  • PCF receives notification of contract information change from UDR.
  • PCF transmits UE policy to UE.
  • PCF If AF subscribes to the execution notification of the relevant policies of the XRM service, PCF sends the relevant The execution result is given to AF. At the same time, if there are changes to the relevant subscription parameters, PCF updates the changes to UDR, triggering the serving PCF of other UEs related to the XRM service group to execute policy changes and coordination.
  • NEF After receiving the notification, NEF first performs the mapping of relevant internal and external parameters, and then sends the relevant report to AF.
  • PCF determines a time threshold and executes policy decisions on SDFs with a common identifier having the same value received within the time threshold, thereby providing better QoS guarantee for SDF transmission. There is no need to repeatedly modify policy decisions for multiple SDFs belonging to the same XRM SDF group, thereby improving authorization efficiency.
  • an embodiment of the present disclosure also provides an XRM service data transmission device.
  • the XRM business data transmission device provided by the embodiment of the present disclosure includes hardware structures and/or software modules corresponding to the execution of each function.
  • the embodiment of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiment of the present disclosure.
  • Fig. 12 is a block diagram of an XRM service data transmission device according to an exemplary embodiment.
  • the device 100 includes a determination module 101 and an execution module 102 .
  • a determination module 101 is used to determine an application function AF session request, where the session request includes a common identifier for identifying an extended reality and multimedia XRM service data flow SDF group;
  • the execution module 102 is configured to execute a policy decision on the AF session request based on the time threshold and the common identifier.
  • the time threshold includes:
  • a time threshold determined based on a timer locally set on a core network device or
  • the time threshold is determined based on the timer locally set on the core network device, the time value or time window carried in the AF session request, the timer or time window in the operator policy, and the priority of the default timer or time window in the subscription information.
  • executing a policy decision on the AF session request includes:
  • a policy decision is executed on the AF session requests identified by the common identifier with the same value.
  • the policy decision includes:
  • a respective policy control and charging PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the execution module 102 is configured to, in response to receiving an AF session request including a common identifier after a time threshold, execute a policy decision on the AF session request received after the time threshold based on a policy decision executed on the AF session request received before the time threshold.
  • Fig. 13 is a block diagram of an XRM service data transmission device according to an exemplary embodiment.
  • the device 200 includes a receiving module 201 and an execution module 202.
  • the receiving module 201 is used to receive an application function AF session request, and the AF session request includes a common identifier for identifying an extended reality and multimedia XRM service data flow SDF group.
  • the execution module 202 is used to make an execution policy decision on the AF session request based on the time threshold and the common identifier.
  • the time threshold includes:
  • the time threshold is determined based on the timer or time window set locally by the PCF entity, the time value or time window carried in the AF session request, the timer or time window in the operator policy, and the priority of the default timer or time window in the subscription information.
  • the execution module 102 is used to determine a common identifier with the same value received before the time threshold is reached, and the common identifier with the same value is used to identify that multiple XRM service data flows SDF belong to the same group;
  • a policy decision is executed on the AF session requests identified by the common identifier with the same value.
  • the policy decision includes:
  • a respective policy control and charging PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the execution module 102 is configured to, in response to receiving an AF session request including a common identifier after a time threshold, execute a policy decision on the AF session request received after the time threshold based on a policy decision executed on the AF session request received before the time threshold.
  • the receiving module 101 is used to receive an AF session request sent by an AF entity, or at least one of a network open function NEF entity and a time sensitive communication and time synchronization function TSCTSF entity.
  • FIG14 is a block diagram of an XRM service data transmission device according to an exemplary embodiment.
  • the device 300 includes a sending module 301.
  • the sending module 301 is used to send an AF session request, which includes a common identifier and a time threshold for identifying an extended reality and multimedia XRM service data flow SDF group.
  • the AF session request is used by a policy control function PCF entity to perform a policy decision on the AF session request based on the common identifier and the time threshold.
  • the AF session request is used by the PCF entity to execute a policy decision for an AF session request identified by a common identifier with the same value received before a time threshold is reached, and the common identifier with the same value is used to identify that multiple XRM service data flows SDF belong to the same group.
  • the policy decision includes:
  • a respective policy control and charging PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision for the AF session request with the common identifier sent after the time threshold is determined based on the policy decision for the AF session request sent before the time threshold.
  • the sending module 301 is used to send an AF session request to at least one functional entity among a policy control function PCF entity, a network development function NEF entity, and a time sensitive communication and time synchronization function TSCTSF entity.
  • FIG15 is a block diagram of an XRM service data transmission device according to an exemplary embodiment.
  • the device 400 includes a receiving module 401 and a sending module 402.
  • the receiving module 401 is used to receive an application function AF session Request, the AF session request includes a common identifier and a time threshold for identifying an extended reality and multimedia XRM service data flow SDF group;
  • the sending module 402 is used to send an AF session request to a policy control function PCF entity, where the AF session request is used for the PCF entity to perform a policy decision on the AF session request based on a common identifier and a time threshold.
  • the AF session request is used by the PCF entity to execute a policy decision for an AF session request identified by a common identifier with the same value received before the time threshold is reached, and the common identifier with the same value is used to identify that multiple XRM service data flows SDF belong to the same group.
  • the policy decision includes:
  • a respective policy control and charging PCC rule is generated for each SDF, and a respective QoS is generated for each SDF.
  • the policy decision for the AF session request with the common identifier sent after the time threshold is determined based on the policy decision for the AF session request sent before the time threshold.
  • the core network device includes a network open function NEF entity and/or a time sensitive communication and time synchronization function TSCTSF entity.
  • Fig. 16 is a block diagram of an XRM service data transmission device according to an exemplary embodiment.
  • the device 500 includes a sending module 501 , a receiving module 502 and an executing module 503 .
  • the sending module 501 is used for the application function AF entity to send an AF session request, where the AF session request includes a common identifier for identifying an extended reality and multimedia XRM service data flow SDF group;
  • the receiving module 502 is used for the policy control function PCF entity to receive the AF session request;
  • the execution module 503 is used by the PCF entity to execute a policy decision on the AF session request based on the time threshold and the common identifier.
  • the time threshold includes:
  • the time threshold is determined based on the timer locally set by the PCF entity, the time value or time window carried in the AF session request, the timer or time window in the operator policy, and the priority of the default timer or time window in the subscription information.
  • the execution module 503 is used by the PCF entity to determine a common identifier with the same value received before a time threshold is reached, and the common identifier with the same value is used to identify that multiple XRM business data flows SDF belong to the same group of business data flows; the PCF entity executes a policy decision on the AF session request identified by the common identifier with the same value.
  • the policy decision includes:
  • the PCF entity authorizes the same quality of service QoS to the SDFs in the SDF group; or
  • the PCF entity generates the same QoS for each SDF in the SDF group based on the subscription information and/or operator policy corresponding to each SDF; or
  • the PCF entity generates a respective policy control and charging PCC rule for each SDF based on the subscription information and/or operator policy corresponding to each SDF in the SDF group, and generates a respective QoS for each SDF.
  • the execution module 503 in response to receiving an AF session request including a common identifier after a time threshold, executes a policy decision on the AF session request received after the time threshold based on the policy decision executed on the AF session request received before the time threshold.
  • the sending module 501 is used for the AF to send an AF session request to at least one of a network open function NEF entity, a time sensitive communication and time synchronization function TSCTSF entity, and a PCF entity.
  • the receiving module 502 is used by the PCF to receive an AF session request sent by an AF entity, or at least one of a network open function NEF entity and a time sensitive communication and time synchronization function TSC TSF entity.
  • FIG. 17 is a block diagram of a device 600 for extending reality and multimedia service data transmission according to an exemplary embodiment.
  • the device 600 may be provided as a server.
  • the device 600 includes a processing component 622, which further includes one or more processors, and a memory resource represented by a memory 632 for storing instructions executable by the processing component 622, such as an application.
  • the application stored in the memory 632 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 622 is configured to execute instructions to perform the above method.
  • the device 600 may also include a power supply component 626 configured to perform power management of the device 600, a wired or wireless network interface 650 configured to connect the device 600 to a network, and an input/output (I/O) interface 658.
  • the device 600 may operate based on an operating system stored in the memory 632, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
  • a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 632 including instructions, which can be executed by the processing component 622 of the device 600 to perform the above method.
  • the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic disk, or a memory card. Tapes, floppy disks and optical data storage devices, etc.
  • plural refers to two or more than two, and other quantifiers are similar thereto.
  • “And/or” describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B may represent: A exists alone, A and B exist at the same time, and B exists alone.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the singular forms “a”, “the”, and “the” are also intended to include plural forms, unless the context clearly indicates other meanings.
  • first, second, etc. are used to describe various information, but such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other, and do not indicate a specific order or degree of importance. In fact, the expressions “first”, “second”, etc. can be used interchangeably.
  • the first information can also be referred to as the second information, and similarly, the second information can also be referred to as the first information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开是关于一种扩展现实多媒体业务数据传输方法、装置及存储介质，涉及通信技术领域，用于为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更优的QoS保障。该方法包括：确定应用功能AF会话请求，所述AF会话请求中包括用于标识扩展现实多媒体XRM业务数据流SDF组的共同标识；基于时间阈值以及所述共同标识，对所述AF会话请求执行策略决策。

Description

扩展现实和多媒体业务数据传输方法、装置及存储介质 技术领域
本公开涉及通信技术领域，尤其涉及一种扩展现实和多媒体(Extend Reality and Media，XRM)业务数据传输方法、装置及存储介质。
背景技术
移动媒体类服务、云增强现实(Augmented Reality，AR)/虚拟现实(Virtual Reality，VR)等扩展现实(Extended Reality，XR)、云游戏、基于视频的机器或无人机远程控制等业务，将为5G网络贡献越来越高的流量。其中，扩展现实和多媒体(Extend Reality and Media，XRM)业务(又叫做多模态业务)涉及多模态数据。多模态数据中的各业务数据流往往具有很强的关联性，比如音频流和视频流需要同步，触觉和视觉需要同步等。这类媒体业务的数据流本身、各数据流之间以及这些业务数据流对网络传输的需求存在一些共性特征，这些特征的有效识别和利用将有助于网络和业务的传输、控制，也有助于业务保障和用户体验。
相关技术中，XRM业务需要综合考虑业务的相关业务数据流的服务质量(Quality of Service，QoS)特性，单一终端的多个业务数据流或多个终端的数据数据流之间的QoS授权需要保持一致性。
但目前策略控制功能实体(Policy Control Function，PCF)无法判断XMR业务组的范围和规模，不能准确确定XRM业务组的QoS授权需求，更不能准确的为XRM组内的多个业务数据流(Service Data Function，SDF)执行QoS授权。
发明内容
为克服相关技术中存在的问题，本公开提供一种扩展现实和多媒体业务数据传输方法、装置及存储介质。
根据本公开实施例的第一方面，提供一种扩展现实和多媒体业务数据传输方法、装置及存储介质方法，由核心网设备执行，所述方法包括：
确定应用功能AF会话请求，所述会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
基于时间阈值和所述共同标识，对AF会话请求执行策略决策。
根据本公开实施例的第二方面，提供一种扩展现实和多媒体业务数据传输方法、装置及存储介质方法，由核心网设备中的策略控制功能PCF实体执行，所述方法包括：
接收应用功能AF会话请求，所述AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
基于时间阈值以及所述共同标识，对所述AF会话请求执行策略决策。
根据本公开实施例的第三方面，提供一种扩展现实和多媒体业务数据传输方法、装置及存储介质方法，由核心网设备中的应用功能AF实体执行，所述方法包括：
发送AF会话请求，所述AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值，所述AF会话请求用于策略控制功能PCF实体基于所述共同标识和时间阈值对所述AF会话请求执行策略决策。
根据本公开实施例的第四方面，提供一种扩展现实和多媒体业务数据传输方法、装置及存储介质方法，由核心网设备中的核心网网元功能执行，所述方法包括：
接收应用功能AF会话请求，所述AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值；
向策略控制功能PCF实体发送所述AF会话请求，所述AF会话请求用于所述PCF实体基于所述共同标识和时间阈值对所述AF会话请求执行策略决策。
根据本公开实施例的第五方面，提供一种扩展现实和多媒体业务数据传输装置，包括：
确定模块，用于确定应用功能AF会话请求，所述会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
执行模块，用于基于时间阈值和所述共同标识，对AF会话请求执行策略决策。
根据本公开实施例的第六方面，提供一种扩展现实和多媒体业务数据传输装置，所述装置包括：
发送模块，用于应用功能实体AF发送AF会话请求，所述AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
接收模块，用于策略控制功能PCF实体接收所述AF会话请求；
执行模块，用于PCF实体基于时间阈值和所述共同标识，对所述AF会话请求执行策略决策。
根据本公开实施例的第七方面，提供一种扩展现实和多媒体业务数据传输装置，所述装置包括：
接收模块，用于接收应用功能AF会话请求，所述AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
执行模块，用于基于时间阈值以及所述共同标识，对所述AF会话请求执行策略决策。
根据本公开实施例的第八方面，提供一种扩展现实和多媒体业务数据传输装置，所述 装置包括：
发送模块，用于发送AF会话请求，所述AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值，所述AF会话请求用于策略控制功能PCF实体基于所述共同标识和时间阈值对所述AF会话请求执行策略决策。
根据本公开实施例的第九方面，提供一种扩展现实和多媒体业务数据传输装置，所述装置包括：
接收模块，用于接收应用功能AF会话请求，所述AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值；
发送模块，用于向策略控制功能PCF实体发送所述AF会话请求，所述AF会话请求用于所述PCF实体基于所述共同标识和时间阈值对所述AF会话请求执行策略决策。
根据本公开实施例的第十方面，提供一种扩展现实和多媒体业务数据传输装置，所述装置包括：发送模块，用于应用功能实体AF发送AF会话请求，所述AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
接收模块，用于策略控制功能PCF实体接收所述AF会话请求；
执行模块，用于PCF实体基于时间阈值和所述共同标识，对所述AF会话请求执行策略决策。
根据本公开实施例的第十一方面，提供一种扩展现实和多媒体业务数据传输装置，处理器；用于存储处理器可执行指令的存储器；其中，所述处理器被配置为：执行上述第一方面或第二方面或第三方面或第四方面及其任意一种实施方式中所述的方法。
根据本公开实施例的第十二方面，提供一种存储介质，所述存储介质中存储有指令，当所述存储介质中的指令由核心网设备的处理器执行时，使得核心网设备能够执行第一方面所述的方法，或当所述存储介质中的指令由策略控制功能PCF实体的处理器执行时，使得PCF实体能够执行执行第二方面所述的方法，或当所述存储介质中的指令由应用功能AF实体的处理器执行时，使得AF实体能够执行执行第三方面所述的方法，或当所述存储介质中的指令由核心网功能网元的处理器执行时，使得核心网功能网元能够执行执行第四方面所述的方法，或当所述存储介质中的指令由核心网设备中的PCF实体、AF实体的处理器执行时，使得PCF实体、AF实体能够执行执行第五方面所述的方法。
根据本公开实施例的第十三方面，提供一种通信系统，所述系统用于执行第一方面所述的方法。
根据本公开实施例的第十四方面，提供一种通信系统，包括以下的实体：
用于执行第二方面所述的方法的策略控制功能PCF实体；
用于执行第三方面所述的方法的应用功能AF实体；
用于执行第四方面任一项所述的方法的核心网功能网元。
本公开的实施例提供的技术方案可以包括以下有益效果：PCF接收AF会话请求，由于AF会话请求中包括用于标识XRM SDF组的共同标识，因此PCF可基于共同标识确定SDF属于的组。进一步的，PCF可结合时间阈值，为时间阈值内的AF会话请求执行策略决策，从而PCF可根据时间阈值和共同标识，为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更优的QoS保障，无需重复对属于同一XRM SDF组中的多个SDF进行多次策略决策的修改，提高授权效率。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1是根据一示例性实施例示出的一种通信系统示意图。
图2是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图3是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图4是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图5是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图6是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图7是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图8是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图9是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图10是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图11是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输方法的流程图。
图12是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输装置的框图。
图13是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输装置的框图。
图14是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输装置的框图。
图15是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输装置的框图。
图16是根据一示例性实施例示出的一种扩展现实和多媒体业务数据传输装置的框图。
图17是根据一示例性实施例示出的一种用于扩展现实和多媒体业务数据传输装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。
本公开实施例提供的扩展现实和多媒体业务数据传输方法，可以应用于图1所示的无线通信系统中，如图1所示，移动台通过诸如基站等无线接入网网络设备接入到无线接入网中，无线接入网网络设备与核心网网络设备完成数据的回传和前向传递，以进行各种通信服务。
可以理解的是，无线通信系统，是一种提供无线通信功能的网络。无线通信系统可以采用不同的通信技术，例如码分多址(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 FDMA，SC-FDMA)、载波侦听多路访问/冲突避免(Carrier Sense Multiple Access with Collision Avoidance)。根据不同网络的容量、速率、时延等因素可以将网络分为2G(generation)网络、3G网络、4G网络或者未来演进网络，如5G网络，5G网络也可称为是新无线网络(New Radio，NR)。为了方便描述，本公开有时会将无线通信网络简称为网络或系统。本公开中网络可包括无线接入网(Radio Access Network，RAN)以及核心网(Core Network，CN)。网络中包括有网络设备，该网络设备可以是无线接入网节点、核心网功能等。其中，无线接入网节点也可以称为基站。网络可以通过网络设备为终端提供网络服务，不同的运营商可以为终端提供不同的网络服务，也可以理解为不同的运营商对应有不同的运营商网络。
移动台(Mobile Station，MS)，也可以称为用户设备(User Equipment，UE)、终端(Terminal)、移动终端(Mobile Terminal，MT)等，是一种向用户提供语音和/或数据连通性的设备，例如，终端可以是具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：智能手机(Mobile Phone)、口袋计算机(Pocket Personal Computer，PPC)、掌上电脑、个人数字助理(Personal Digital Assistant，PDA)、笔记本电脑、平板电脑、可穿戴设备、或者车载设备等。
5G系统中包括有对无线接入网以及终端进行接入和移动性相关需求进行管理和协同的设备。例如核心网功能中包括会话管理功能设备(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)、用户设备(user equipment，UE)。当然，核心网功能中还包括有其他类型的设备，本公开实施例在此不再一一列举。
下面对本公开实施例涉及相关的实体功能进行详细介绍。
AF实体，负责与3GPP核心网交互提供业务或者服务，包括与NEF交互，策略架构交互等。
NEF实体，主要功能包括：安全的开放3GPP网络功能提供的业务和能力，有内部开放，或者开放给第三方等。转化或翻译与AF交互的信息和内部网络功能交互德行信息，如AF服务标识和内部5G核心网信息如数据网络名(Data Network Name，DNN)，单一网络切片选择辅助信息(Single Network SliceSelection Assistance Information，S-NSSAI)等。
AMF实体，负责接入和移动性管理，主要功能包括：连接管理、移动性管理、注册管理、接入认证和授权、可达性管理、安全上下文管理、用户进行认证、切换、位置更新等接入和移动性相关的功能。
PCF实体，主要功能包含：统一策略制定、策略控制的提供和从统一数据库(unified data management，UDR)中获取策略决策相关的签约信息等策略相关的功能。
UPF实体，负责用户面功能，主要功能包含：数据包路由和传输、包检测、业务用量上报、QoS处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。
SMF实体，负责会话管理功能，主要功能包含：会话管理(如会话建立、修改和释放，包含UPF和AN之间的隧道维护)、UPF的选择和控制、业务和会话连续性(service and session continuity，SSC)模式选择、漫游等会话相关的功能。
移动媒体类服务、云增强现实(Augmented Reality，AR)/虚拟现实(Virtual Reality，VR)等扩展现实(Extended Range，XR)、云游戏、基于视频的机器或无人机远程控制等业务，将为5G网络贡献越来越高的流量。其中，扩展现实和多媒体(Extend Reality and Media，XRM)业务(又叫做多模态业务)涉及多模态数据。多模态数据中的各业务数据流往往具有很强的关联性，比如音频流和视频流需要同步，触觉和视觉需要同步等。这类媒体业务的数据流本身、各数据流之间以及这些业务数据流对网络传输的需求存在一些共性特征，这些特征的有效识别和利用将有助于网络和业务的传输、控制，也有助于业务保障和用户体验。
相关技术中，XRM业务需要综合考虑业务的相关业务数据流的服务质量(Quality of Service，QoS)特性，单一终端的多个业务数据流或多个终端的数据数据流之间的QoS授权需要保持一致性。
但目前策略控制功能实体(Policy Control Function，PCF)无法判断XMR业务组的范围和规模，不能准确确定XRM业务组的QoS授权需求，更不能准确的为XRM组内的多个业务数据流(Service Data Function，SDF)执行QoS授权。
基于此，本公开实施例提供了一种XRM业务数据传输方法，PCF接收AF会话请求，由于AF会话请求中包括用于标识XRM SDF组的共同标识，因此PCF可基于共同标识确定SDF属于的XRM SDF组。进一步的，PCF可结合时间阈值，为时间阈值内的AF会话请求执行策略决策，从而PCF可根据时间阈值和共同标识，为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更优的QoS保障，无需重复对属于同一XRM SDF组中的多个SDF进行多次策略决策的修改，提高授权效率。
图2是根据一示例性实施例示出的一种XRM业务数据传输方法的流程图，如图2所示，应用于核心网设备，包括以下步骤。
在步骤S11中，确定AF会话请求，会话请求中包括用于标识XRM SDF组的共同标识。
其中，一个XRM业务/应用的多个SDF属于同一个SDF组，一个SDF组内的SDF的共同标识相同。
一种实施方式中，共同标识对应的SDF对应同一个终端或对应多个终端(一个终端组)。
一种实施方式中，AF会话请求还可以携带UE地址或UE标识，AF标识、应用标识,DNN、S-NSSAI、QoS参数等信息。
在一些实施例中，AF会话请求中可包括用于标识XRM SDF组的XRM业务标识，一 个XRM业务/应用中属于同一个SDF组的SDF具有相同的XRM业务标识。
在步骤S12中，基于时间阈值和共同标识，对AF会话请求执行策略决策。
在本公开实施例中，核心网设备确定AF会话请求，由于AF会话请求中包括用于标识XRM SDF组的共同标识，因此核心网设备可基于共同标识确定SDF属于的XRM组。进一步的，核心网设备可结合时间阈值，为时间阈值内的AF会话请求执行策略决策，从而核心网设备可根据时间阈值和共同标识，为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更优的QoS保障，无需重复对属于同一XRM SDF组中的多个SDF进行多次策略决策的修改，提高授权效率。
在本公开实施例提供的一种XRM业务数据传输方法中，时间阈值包括：
基于核心网设备本地设置的定时器，确定的时间阈值；或
基于AF会话请求中携带的时间取值或时间窗口，确定的时间阈值；或
基于运营商策略中的定时器或时间窗口，确定的时间阈值；或
基于签约信息中缺省定时器或时间窗口，确定的时间阈值；或
基于核心网设备本地设置的定时器、AF会话请求中的时间取值或时间窗口、运营商策略或签约信息的/缺省定时器或时间窗口，以及各类取值的优先级，确定的时间阈值。
一种实施方式中，核心网设备可基于核心网设备本地设置的定时器确定时间阈值。
例如，核心网设备本地设置的定时器为10ms，则核心网设备可确定时间阈值为10ms或8ms或其他小于10ms的时间值。
一种实施方式中，AF会话请求中携带有时间取值或时间窗口，核心网设备基于AF会话请求中携带的时间窗口确定时间阈值。
例如，AF会话请求中携带有10ms-30ms的时间窗口，则核心网设备可确定可在10ms-30ms之间确认一个时间阈值，大于10ms不超过30ms即可。
一种实施方式中，核心网设备可基于运营商策略中的定时器或时间窗口，确定时间阈值。
例如，运营商策略中针对某一XRM业务的设置的定时器为15ms，则核心网设备在接收到某一XRM业务的AF会话请求时，能够确定针对该XRM业务的SDF组的时间阈值为15ms，或考虑网络状态的某个小于15ms值，比如12ms。
一种实施方式中，基于签约信息中缺省定时器或时间窗口确定时间阈值。
其中，签约信息存储在统一数据管理(Unified Data Management，UDM)中。
例如，核心网设备接收到某一XRM业务的AF会话请求，确定针对该XRM业务的签约请求中的缺省定时器为10ms，则核心网设备能够确定针对该XRM业务的SDF组的时 间阈值为10ms或8ms(小于10ms的某个合适的值)。
一种实施方式中，核心网设备基于核心网设备本地设置的定时器、时间窗口、运营商策略中的定时器以及缺省定时器的优先级确定时间阈值。
例如，当核心网设备本地设置有定时器，运营商策略中也设置有定时器，签约信息中也记载有缺省定时器，同时PCF接收到AF会话请求中也携带有时间窗口时，核心网设备可根据这些定时器或时间窗口的优先级确定时间阈值。
其中，各个定时器或时间窗口的优先级可基于预设规则确定。例如，签约信息中缺省定时器的优先级低于运营商策略中的定时器低于核心网设备本地设置的定时器低于AF会话请求中携带的时间窗口的优先级。核心网设备可以选择优先级最高的定时器或时间窗口作为时间阈值。
在本公开实施例提供的一种XRM业务数据传输方法中，上述步骤S12中基于时间阈值以及共同标识，对AF会话请求执行策略决策可实现为步骤S21-S22，如图3所示：
在步骤S21中，核心网设备确定在时间阈值到达之前接收到的相同取值的共同标识。
其中，相同取值的共同标识用于标识多个XRM SDF归属同一组。
在步骤S22中，核心网设备对相同取值的共同标识所标识的AF会话请求执行策略决策。
在本公开实施例中，核心网设备通过确定时间阈值，在时间阈值到达之前对相同取值的共同标识所标识的AF会话请求执行策略决策，从而核心网设备能够确定属于同一组的SDF，并为同一组SDF进行策略决策，使得核心网设备为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更优化的QoS保障。
在本公开实施例提供的一种XRM业务数据传输方法中，策略决策包括：
对SDF组中的SDF均授权相同QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成相同的QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的策略控制与计费(Policy Control and Charging，PCC)规则，并对每个SDF生成各自的QoS。
其中，PCC规则表示业务对服务质量的要求，对业务的计费要求。网络会根据业务类型以及用户的签约等级为用户提供不同的QoS服务，并通过检测不同的业务数据流，将统计的流量、时长等计费信息上报计费中心，进行计费。
在本公开实施例中，在确定出SDF属于的XRM SDF组之后，可对同一个组内的SDF进行策略决策，例如授权相同的QoS或针对每个SDF授权各自的QoS等，使得核心网设 备为XRM业务进行更加合理的策略决策和授权资源，为SDF的传输提供更优的QoS保障。
在本公开实施例提供的一种XRM业务数据传输方法中，响应于在时间阈值之后接收到包括共同标识的AF会话请求，基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
一种实施方式中，若在时间阈值之后接收到的AF会话请求的共同标识的取值与在时间阈值之前接收到的AF会话请求的共同标识的取值相同，则可以对时间阈值之后接收到的AF会话请求执行与时间阈值之前接收到的AF会话请求相同的策略决策。
例如，核心网设备在时间阈值之前接收到的AF会话请求执行的策略决策是基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。则核心网设备对在时间阈值之后接收到的AF会话请求执行的策略决策同样可以基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。
在本公开实施例中，核心网设备在时间阈值之后接收到的AF会话请求的策略决策可以基于时间阈值之前的AF会话请求确定，无需重新对时间阈值之后接收到的AF会话请求重新确定策略决策，节省效率。
下面以核心网设备中的PCF实体为执行主体，对本公开实施例提供的XRM业务数据传输方法进行说明。
图4是根据一示例性实施例示出的一种XRM业务数据传输方法的流程图，如图4所示，由核心网设备中的PCF实体执行，包括以下步骤。
在步骤S31中，接收AF会话请求，AF会话请求中包括用于标识XRM SDF组的共同标识。
其中，一个XRM业务/应用的多个SDF属于同一个SDF组，一个SDF组内的SDF的共同标识相同。
一种实施方式中，共同标识对应的SDF来自同一个终端或来自多个终端(一个终端组)。
一种实施方式中，AF会话请求还可以携带UE地址或UE标识，AF标识、应用标识,DNN、S-NSSAI、QoS参数等信息。
在一些实施例中，AF会话请求中可包括用于标识XRM SDF组的XRM业务标识，一个XRM业务/应用中属于同一个SDF组的SDF具有相同的XRM业务标识。
在步骤S32中，基于时间阈值以及共同标识，对AF会话请求执行策略决策。
在本公开实施例中，PCF接收AF会话请求，由于AF会话请求中包括用于标识XRM SDF组的共同标识，因此PCF可基于共同标识确定SDF属于的XRM组。进一步的，PCF可结合时间阈值，为时间阈值内的AF会话请求执行策略决策，从而PCF可根据时间阈值和共同标识，为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更优的QoS保障，无需重复对属于同一XRM SDF组中的多个SDF进行多次策略决策的修改，提高授权效率。
在本公开实施例提供的一种XRM业务数据传输方法中，时间阈值包括：
基于PCF实体本地设置的定时器，确定的时间阈值；或
基于AF会话请求中携带的时间取值或时间窗口，确定的时间阈值；或
基于运营商策略中的定时器或时间窗口，确定的时间阈值；或
基于签约信息中缺省定时器或时间窗口，确定的时间阈值；或
基于PCF实体本地设置的定时器、AF会话请求中的时间取值或时间窗口、运营商策略或签约信息的/缺省定时器或时间窗口，以及各类取值的优先级，确定的时间阈值。
一种实施方式中，PCF可基于PCF实体本地设置的定时器确定时间阈值。
例如，PCF实体本地设置的定时器为10ms，则PCF可确定时间阈值为10ms或8ms或其他小于10ms的时间值。
一种实施方式中，AF会话请求中携带有时间取值或时间窗口，PCF基于AF会话请求中携带的时间窗口确定时间阈值。
例如，AF会话请求中携带有10ms-30ms的时间窗口，则PCF可确定可在10ms-30ms之间确认一个时间阈值，大于10ms不超过30ms即可。
一种实施方式中，PCF可基于运营商策略中的定时器或时间窗口，确定时间阈值。
例如，运营商策略中针对某一XRM业务的设置的定时器为15ms，则PCF在接收到某一XRM业务的AF会话请求时，能够确定针对该XRM业务的SDF组的时间阈值为15ms，或考虑网络状态的某个小于15ms值，比如12ms。
一种实施方式中，基于签约信息中缺省定时器或时间窗口确定时间阈值。
其中，签约信息存储在统一数据管理(Unified Data Management，UDM)中。
例如，PDF接收到某一XRM业务的AF会话请求，确定针对该XRM业务的签约请求中的缺省定时器为10ms，则PCF能够确定针对该XRM业务的SDF组的时间阈值为10ms或8ms(小于10ms的某个合适的值)。
一种实施方式中，PCF基于PCF实体本地设置的定时器、时间窗口、运营商策略中的定时器以及缺省定时器的优先级确定时间阈值。
例如，当PCF实体本地设置有定时器，运营商策略中也设置有定时器，签约信息中也 记载有缺省定时器，同时PCF接收到AF会话请求中也携带有时间窗口时，PCF可根据这些定时器或时间窗口的优先级确定时间阈值。
其中，各个定时器或时间窗口的优先级可基于预设规则确定。例如，签约信息中缺省定时器的优先级低于运营商策略中的定时器低于PCF本地设置的定时器低于AF会话请求中携带的时间窗口的优先级。PCF可以选择优先级最高的定时器或时间窗口作为时间阈值。
在本公开实施例提供的一种XRM业务数据传输方法中，上述步骤S32中基于时间阈值以及共同标识，对AF会话请求执行策略决策可实现为步骤S41-S42，如图5所示：
在步骤S41中，PCF实体确定在时间阈值到达之前接收到的相同取值的共同标识。
其中，相同取值的共同标识用于标识多个XRM SDF归属同一组。
在步骤S42中，PCF实体对相同取值的共同标识所标识的AF会话请求执行策略决策。
在本公开实施例中，PCF通过确定时间阈值，在时间阈值到达之前对相同取值的共同标识所标识的AF会话请求执行策略决策，从而PCF能够确定属于同一组的SDF，并为同一组SDF进行策略决策，使得PCF为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更优化的QoS保障。
在本公开实施例提供的一种XRM业务数据传输方法中，策略决策包括：
对SDF组中的SDF均授权相同QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成相同的QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的策略控制与计费(Policy Control and Charging，PCC)规则，并对每个SDF生成各自的QoS。
其中，PCC规则表示业务对服务质量的要求，对业务的计费要求。网络会根据业务类型以及用户的签约等级为用户提供不同的QoS服务，并通过检测不同的业务数据流，将统计的流量、时长等计费信息上报计费中心，进行计费。
在本公开实施例中，在确定出SDF属于的XRM SDF组之后，可对同一个组内的SDF进行策略决策，例如授权相同的QoS或针对每个SDF授权各自的QoS等，使得PCF为XRM业务进行更加合理的策略决策和授权资源，为SDF的传输提供更优的QoS保障。
在本公开实施例提供的一种XRM业务数据传输方法中，响应于在时间阈值之后接收到包括共同标识的AF会话请求，基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
一种实施方式中，若在时间阈值之后接收到的AF会话请求的共同标识的取值与在时间阈值之前接收到的AF会话请求的共同标识的取值相同，则可以对时间阈值之后接收到 的AF会话请求执行与时间阈值之前接收到的AF会话请求相同的策略决策。
例如，PCF在时间阈值之前接收到的AF会话请求执行的策略决策是基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。则PCF对在时间阈值之后接收到的AF会话请求执行的策略决策同样可以基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。
在本公开实施例中，PCF在时间阈值之后接收到的AF会话请求的策略决策可以基于时间阈值之前的AF会话请求确定，无需重新对时间阈值之后接收到的AF会话请求重新确定策略决策，节省效率。
在本公开实施例提供的一种XRM业务数据传输方法中，PCF接收到的AF会话请求可以是AF实体直接发送的；或者AF实体发送给NEF实体，由NEF实体发送给PCF；或者AF实体发送给时间敏感通信与时间同步功能(Time Sensitive Communication and TimeSynchronization function，TSCTSF)实体，由TSCTSF实体发送给PCF；或者，AF实体发送给NEF，NEF发送给TSCTSF实体，再由TSCTSF实体发送给PCF。
其中，当AF为可信AF时，AF可直接将AF会话请求发送给PCF。当AF为非可信AF时，AF通过NEF和/或TSCTSF发送给PCF。
在本公开实施例提供的一种XRM业务数据传输方法中，PCF可以在以下流程中接收AF会话请求：
(a)需要QoS设置的AF会话流程(Setting up an AF session with required QoS procedure)；
(b)需要进行QoS更新过程的AF会话流程(AF session with required QoS update procedure)
(c)服务特定参数设置流程(Service specific parameter provisioning)；
(d)为将来的AF会话设置策略流程(Set a policy for a future AF session)。
基于相同的构思，本公开实施例还提供了一种由核心网设备中的AF实体执行的XRM业务数据传输方法。
图6是根据一示例性实施例示出的一种XRM业务数据传输方法的流程图，如图6所示，XRM业务数据传输方法由核心网设备中的AF实体执行，包括以下步骤。
在步骤S51中，发送AF会话请求，AF会话请求中包括用于标识XRM SDF组的共同标识和时间阈值。
其中，AF会话请求用于PCF实体基于共同标识和时间阈值对AF会话请求执行策略 决策。
其中，一个XRM业务/应用的多个SDF属于同一个SDF组，一个SDF组内的SDF的共同标识相同。
一种实施方式中，共同标识对应的SDF来自同一个终端或来自多个终端(一个终端组)。
一种实施方式中，AF会话请求还可以携带UE地址或UE标识，AF标识、应用标识,DNN、S-NSSAI、QoS参数等信息。
在一些实施例中，AF会话请求中可包括用于标识XRM SDF组的XRM业务标识，一个XRM业务/应用中属于同一个SDF组的SDF具有相同的XRM业务标识。
在一些实施例中，AF会话请求包括的时间阈值可以是时间窗口或时间取值。
在一些实施例中，除AF会话请求中包括时间阈值之外，PCF还可以通过PCF实体本地设置的定时器或时间窗口确定时间阈值，或者通过运营商策略中记载的定时器或时间窗口确定时间阈值，或者通过签约信息中的缺省定时器或时间窗口确定时间阈值。
一种实施方式中，当PCF实体本地设置有定时器或时间窗口，运营商策略中也设置有定时器或时间窗口，签约信息中也记载有缺省定时器或时间窗口，同时AF会话请求中也携带有时间窗口或时间取值时，PCF可根据这些定时器或时间窗口的优先级确定时间阈值。
其中，各个定时器或时间窗口的优先级可基于预设规则确定。例如，签约信息中缺省定时器的优先级低于运营商策略中的定时器低于PCF本地设置的定时器低于AF会话请求中携带的时间窗口的优先级。PCF可以选择优先级最高的定时器或时间窗口作为时间阈值。
在本公开实施例中，AF通过发送包括共同标识和时间阈值的AF会话请求，使得PCF可基于时间阈值和共同标识对AF会话请求执行策略决策，从而为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更优的QoS保障，无需重复对属于同一XRMSDF组中的多个SDF进行多次策略决策的修改，提高授权效率。
在本公开实施例提供的一种XRM业务数据传输方法中，AF会话请求用于PCF实体为时间阈值到达之前接收到的相同取值的共同标识所标识的AF会话请求执行策略决策。其中，相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组。
在本公开实施例提供的一种XRM业务数据传输方法中，策略决策包括：
对SDF组中的SDF均授权相同QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成相同的QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成各自 的PCC规则，并对每个SDF生成各自的QoS。
其中，PCC规则表示业务对服务质量的要求，对业务的计费要求。网络会根据业务类型以及用户的签约等级为用户提供不同的QoS服务，并通过检测不同的业务数据流，将统计的流量、时长等计费信息上报计费中心，进行计费。
在本公开实施例中，在PCF确定出SDF属于的XRM SDF组之后，可对同一个组内的SDF进行策略决策，例如授权相同的QoS或针对每个SDF授权各自的QoS等，使得PCF为XRM业务进行更加合理的策略决策和授权资源，为SDF的传输提供更优的QoS保障。
在本公开实施例提供的一种XRM业务数据传输方法中，在时间阈值之后发送的具有共同标识的AF会话请求的策略决策，基于时间阈值之前发送的AF会话请求的策略决策确定。
一种实施方式中，若在时间阈值之后发送的AF会话请求的共同标识的取值与在时间阈值之前发送的AF会话请求的共同标识的取值相同，则在时间阈值之后发送的AF会话请求与时间阈值之前发送的AF会话请求策略决策可以相同。
例如，AF在时间阈值之前发送的AF会话请求的策略决策是基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。则AF在时间阈值之后发送的AF会话的策略决策同样可以是基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。
在本公开实施例中，AF在时间阈值之后发送的AF会话请求的策略决策可以基于时间阈值之前的AF会话请求确定，无需PCF重新对时间阈值之后接收到的AF会话请求重新确定策略决策，节省效率。
在本公开实施例提供的一种XRM业务数据传输方法中，AF向PCF实体、NEF实体、TSCTSF实体中的至少一个功能实体发送AF会话请求。
一种实施方式中，当AF为可信AF时，AF可直接将AF会话请求发送给PCF。当AF为非可信AF时，AF通过NEF和/或TSCTSF发送给PCF。
在本公开实施例提供的一种XRM业务数据传输方法中，PCF可以在以下流程中接收AF会话请求：
(a)需要QoS设置的AF会话流程(Setting up an AF session with required QoS procedure)；
(b)需要进行QoS更新过程的AF会话流程(AF session with required QoS update procedure)
(c)服务特定参数设置流程(Service specific parameter provisioning)；
(d)为将来的AF会话设置策略流程(Set a policy for a future AF session)。
基于相同的构思，本公开实施例还提供了一种由核心网设备中的核心网功能网元执行的XRM业务数据传输方法。
图7是根据一示例性实施例示出的一种XRM业务数据传输方法的流程图，如图7所示，XRM业务数据传输方法由核心网设备中的核心网功能网元执行，包括以下步骤。
在步骤S61中，接收AF会话请求，AF会话请求包括用于标识XRM SDF组的共同标识和时间阈值。
其中，一个XRM业务/应用的多个SDF属于同一个SDF组，一个SDF组内的SDF的共同标识相同。
一种实施方式中，共同标识对应的SDF来自同一个终端或来自多个终端(一个终端组)。
一种实施方式中，AF会话请求还可以携带UE地址或UE标识，AF标识、应用标识,DNN、S-NSSAI、QoS参数等信息。
在一些实施例中，AF会话请求中可包括用于标识XRM SDF组的XRM业务标识，一个XRM业务/应用中属于同一个SDF组的SDF具有相同的XRM业务标识。
在步骤S62中，向PCF实体发送AF会话请求，AF会话请求用于PCF实体基于共同标识和时间阈值对AF会话请求执行策略决策。
在一些实施例中，AF会话请求包括的时间阈值可以是时间窗口或时间取值。
在一些实施例中，除AF会话请求中包括时间阈值之外，PCF还可以通过PCF实体本地设置的定时器或时间窗口确定时间阈值，或者通过运营商策略中记载的定时器或时间窗口确定时间阈值，或者通过签约信息中的缺省定时器或时间窗口确定时间阈值。
一种实施方式中，当PCF实体本地设置有定时器或时间窗口，运营商策略中也设置有定时器或时间窗口，签约信息中也记载有缺省定时器或时间窗口，同时AF会话请求中也携带有时间窗口或时间取值时，PCF可根据这些定时器或时间窗口的优先级确定时间阈值。
其中，各个定时器或时间窗口的优先级可基于预设规则确定。例如，签约信息中缺省定时器的优先级低于运营商策略中的定时器低于PCF本地设置的定时器低于AF会话请求中携带的时间窗口的优先级。PCF可以选择优先级最高的定时器或时间窗口作为时间阈值。
在本公开实施例中，核心网功能网元通过接收包括共同标识和时间阈值的AF会话请求，并向PCF发送AF会话请求，使得PCF可基于时间阈值和共同标识对AF会话请求执行策略决策，从而为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更 优的QoS保障，无需重复对属于同一XRM SDF组中的多个SDF进行多次策略决策的修改，提高授权效率。
在本公开实施例提供的一种XRM业务数据传输方法中，AF会话请求用于PCF实体为时间阈值到达之前接收到的相同取值的共同标识所标识的AF会话请求执行策略决策。其中，相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组。
在本公开实施例提供的一种XRM业务数据传输方法中，策略决策包括：
对SDF组中的SDF均授权相同QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成相同的QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。
其中，PCC规则表示业务对服务质量的要求，对业务的计费要求。网络会根据业务类型以及用户的签约等级为用户提供不同的QoS服务，并通过检测不同的业务数据流，将统计的流量、时长等计费信息上报计费中心，进行计费。
在本公开实施例中，在PCF确定出SDF属于的XRM SDF组之后，可对同一个组内的SDF进行策略决策，例如授权相同的QoS或针对每个SDF授权各自的QoS等，使得PCF为XRM业务进行更加合理的策略决策和授权资源，为SDF的传输提供更优的QoS保障。
在本公开实施例提供的一种XRM业务数据传输方法中，在时间阈值之后发送的具有共同标识的AF会话请求的策略决策，基于时间阈值之前发送的AF会话请求的策略决策确定。
一种实施方式中，若在时间阈值之后发送的AF会话请求的共同标识的取值与在时间阈值之前发送的AF会话请求的共同标识的取值相同，则在时间阈值之后发送的AF会话请求与时间阈值之前发送的AF会话请求策略决策可以相同。
例如，AF在时间阈值之前发送的AF会话请求的策略决策是基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。则AF在时间阈值之后发送的AF会话的策略决策同样可以是基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。
在本公开实施例中，AF在时间阈值之后发送的AF会话请求的策略决策可以基于时间阈值之前的AF会话请求确定，无需PCF重新对时间阈值之后接收到的AF会话请求重新确定策略决策，节省效率。
在本公开实施例提供的一种XRM业务数据传输方法中，核心网功能网元包括NEF实体和/或TSCTSF实体。
一种实施方式中，当AF为非可信AF时，AF通过NEF和/或TSCTSF发送给PCF。
在本公开实施例提供的一种XRM业务数据传输方法中，核心网功能万元可以在以下流程中接收和发送AF会话请求：
(a)需要QoS设置的AF会话流程(Setting up an AF session with required QoS procedure)；
(b)需要进行QoS更新过程的AF会话流程(AF session with required QoS update procedure)
(c)服务特定参数设置流程(Service specific parameter provisioning)；
(d)为将来的AF会话设置策略流程(Set a policy for a future AF session)。
下面以核心网设备中各个实体交互的过程，对本公开实施例提出的一种XRM业务数据传输方法进行说明。
图8是根据一示例性实施例示出的一种XRM业务数据传输方法的流程图，如图8所示，包括以下步骤。
在步骤S71中，AF实体发送AF会话请求，AF会话请求包括用于标识XRM SDF组的共同标识。
其中，一个XRM业务/应用的多个SDF属于同一个SDF组，一个SDF组内的SDF的共同标识相同。
一种实施方式中，共同标识对应的SDF对应同一个终端或对应多个终端(一个终端组)。
一种实施方式中，AF会话请求还可以携带UE地址或UE标识，AF标识、应用标识,DNN、S-NSSAI、QoS参数等信息。
在一些实施例中，AF会话请求中可包括用于标识XRM SDF组的XRM业务标识，一个XRM业务/应用中属于同一个SDF组的SDF具有相同的XRM业务标识。
在步骤S72中，PCF实体接收AF会话请求。
在步骤S73中，PCF实体基于时间阈值和共同标识，对AF会话请求执行策略决策。
在本公开实施例中，AF实体发送AF会话请求，由于AF会话请求中包括用于标识XRM SDF组的共同标识，因此PCF实体接收到AF会话请求后可基于共同标识确定SDF属于的XRM组。进一步的，PCF实体可结合时间阈值，为时间阈值内的AF会话请求执行策略决策，从而PCF实体可根据时间阈值和共同标识，为XRM业务进行更加合理地策 略决策和授权资源，为SDF传输提供更优的QoS保障，无需重复对属于同一XRM SDF组中的多个SDF进行多次策略决策的修改，提高授权效率。
在本公开实施例提供的一种XRM业务数据传输方法中，时间阈值包括：
基于核心网设备本地设置的定时器，确定的时间阈值；或
基于AF会话请求中携带的时间取值或时间窗口，确定的时间阈值；或
基于运营商策略中的定时器或时间窗口，确定的时间阈值；或
基于签约信息中缺省定时器或时间窗口，确定的时间阈值；或
基于核心网设备本地设置的定时器、AF会话请求中的时间取值或时间窗口、运营商策略或签约信息的/缺省定时器或时间窗口，以及各类取值的优先级，确定的时间阈值。
在本公开实施例提供的一种XRM业务数据传输方法中，上述步骤S73中PCF实体基于时间阈值以及共同标识，对AF会话请求执行策略决策可实现为步骤S81-S82，如图9所示：
在步骤S81中，PCF实体确定在时间阈值到达之前接收到的相同取值的共同标识。
其中，相同取值的共同标识用于标识多个XRM SDF归属同一组。
在步骤S82中，PCF实体对相同取值的共同标识所标识的AF会话请求执行策略决策。
在本公开实施例中，PCF实体通过确定时间阈值，在时间阈值到达之前对相同取值的共同标识所标识的AF会话请求执行策略决策，从而PCF实体能够确定属于同一组的SDF，并为同一组SDF进行策略决策，使得PCF实体为XRM业务进行更加合理地策略决策和授权资源，为SDF传输提供更优化的QoS保障。
在本公开实施例提供的一种XRM业务数据传输方法中，策略决策包括：
PCF实体对SDF组中的SDF均授权相同QoS；或
PCF实体基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成相同的QoS；或
PCF实体基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的策略控制与计费(Policy Control and Charging，PCC)规则，并对每个SDF生成各自的QoS。
其中，PCC规则表示业务对服务质量的要求，对业务的计费要求。网络会根据业务类型以及用户的签约等级为用户提供不同的QoS服务，并通过检测不同的业务数据流，将统计的流量、时长等计费信息上报计费中心，进行计费。
在本公开实施例中，在确定出SDF属于的XRM SDF组之后，可对同一个组内的SDF进行策略决策，例如授权相同的QoS或针对每个SDF授权各自的QoS等，使得核心网设 备为XRM业务进行更加合理的策略决策和授权资源，为SDF的传输提供更优的QoS保障。
在本公开实施例提供的一种XRM业务数据传输方法中，响应于在时间阈值之后接收到包括共同标识的AF会话请求，PCF实体基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
一种实施方式中，若PCF实体在时间阈值之后接收到的AF会话请求的共同标识的取值与在时间阈值之前接收到的AF会话请求的共同标识的取值相同，则PCF实体可以对时间阈值之后接收到的AF会话请求执行与时间阈值之前接收到的AF会话请求相同的策略决策。
例如，PCF实体在时间阈值之前接收到的AF会话请求执行的策略决策是基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。则PCF实体对在时间阈值之后接收到的AF会话请求执行的策略决策同样可以基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。
在本公开实施例中，PCF实体在时间阈值之后接收到的AF会话请求的策略决策可以基于时间阈值之前的AF会话请求确定，无需重新对时间阈值之后接收到的AF会话请求重新确定策略决策，节省效率。
在本公开实施例提供的一种XRM业务数据传输方法中，AF会话请求可以在以下流程中进行传输：
(a)需要QoS设置的AF会话流程(Setting up an AF session with required QoS procedure)；
(b)需要进行QoS更新过程的AF会话流程(AF session with required QoS update procedure)
(c)服务特定参数设置流程(Service specific parameter provisioning)；
(d)为将来的AF会话设置策略流程(Set a policy for a future AF session)。
下面以流程(a)：Setting up an AF session with required QoS procedure流程为例，对本公开实施例提供的XRM业务数据传输方法进行详细完整的说明，如图10所示。
1、AF发送AF会话请求，例如通过具有QoS创建请求的AF会话创建AF会话请求。AF会话请求中包括用于标识XRM业务的SDF组的共同标识，具有相同取值的共同标识的SDF属于同一个XRM业务。一种实施方式中，AF会话请求中还包括时间窗口。一种实施方式中，AF会话请求还包括UE地址或UE标识、AF标识、应用标识、DNN、S-NSSAI、QoS参数等信息。
2、NEF授权AF会话请求。如果AF为非可信AF，AF通过NEF发送AF会话请求发送给PCF。一种实施方式中，NEF执行相关映射，包括标识XRM业务(AF业务标识)到DNN和S-NSSAI的映射，外部应用到核心网(Core Network，CN)应用标识的映射；以及基于UDM的签约信息，外部UE标识到CN内UE标识的映射(如用户永久标识符(Subscriber Permanent Identifier，SUPI))，以及根据UDM签约信息执行外部到内部的XRM业务组标识的映射。
3、NEF授权AF会话请求，并根据AF提供的参数确定是调用TSCTSF还是直接联系PCF。这些信令步骤与TS 23.502第4.15.6.6条中设置具有所需QoS程序的AF会话的步骤相同。PCF从NEF或TSCTSF接收AF发送的AF会话请求。NEF触发策略授权创建请求(Npcf_PolicyAuthorization_Create request)，将AF会话请求发送给PCF，供PCF对AF会话执行策略决策。
4、PCF做出策略决策。PCF可以确定需要向SMF发送的更新的或新的策略决策信息。
一种实施方式中，PCF确定在时间阈值到达之前接收到的相同取值的共同标识，对相同取值的共同标识所标识的AF会话请求执行策略决策。
其中，时间阈值可以基于PCF实体本地设置的定时器确定；或基于AF会话请求中携带的时间窗口确定；或基于运营商策略中的定时器确定；或基于签约信息中缺省定时器确定；或基于PCF实体本地设置的定时器、时间窗口、运营商策略中的定时器以及缺省定时器的优先级确定。
其中，PCF对相同取值的共同标识所标识的AF会话请求执行的策略决策可以是对SDF组中的SDF授权相同QoS；或基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成相同的PCC规则，并对每个SDF生成相同的QoS；或基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的PCC规则，并对每个SDF生成各自的QoS。
进一步的，PCF在时间阈值之后接收到包括共同标识的AF会话请求，基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
5、PCF向NEF响应策略授权创建请求。
6、NEF向AF发送具有QoS创建的AF会话响应消息，AF会话响应消息中携带授权结果，用于告知AF AF会话请求是否被授权。
7、PCF向SMF发起SM策略关联修改请求(PCC规则(QoS监控策略))。
基于来自PCF的QoS策略决策，SMF生成用于UPF(以及用于RAN)的QoS监控 配置，如步骤4所述。
8、SMF向PCF回复SM策略关联修改响应。
9、SMF向UPF发起N4会话修改请求(QoS监控配置)。
10、在接收到QoS监控配置后，UPF启用测量和报告。UPF响应SMF。
11、对于SMF请求的修改，SMF调用通信N1N2消息传输([N2 SM信息](PDU会话ID、QFI、QoS配置文件、QoS监控配置)、N1 SM容器)。
12、AMF可以向(R)AN发送N2((N2从SMF接收的SM信息)、NAS消息(PDU会话ID、N1 SM容器(PDU会话修改命令))消息。在接收到QoS监控配置后，RAN启用事件测量和报告。
13、UE和RAN进行资源设置。
14、(R)AN可以通过向AMF发送N2 PDU会话确认消息来确认N2 PDU会话请求。
15、AMF经由PDU会话更新SM上下文服务操作将从AN接收的N2 SM信息转发给SMF。
16、SMF回复PDU会话更新SM上下文响应。
17-18、SMF可以通过向UPF发送N4会话修改请求消息来更新PDU会话修改所涉及的UPF的N4会话。当后续PCF收到QoS监控报告，将通知发送给AF。
下面以流程(b)：Service specific parameter provisioning流程为例，对本公开实施例提供的XRM业务数据传输进行详细完整的说明，如图11所示。
0、XRM服务或多模式数据服务相关的部分UE或全部UE，已注册到网络，选择了PCF完成AM session关联。其中，PCF根据XRM业务的策略和QoS需求，向UDM订阅XRM服务或多模式数据服务相关签约信息的变更通知。
1、AF触发XRM服务参数服务，创建AF会话请求，AF会话请求中包括共同标识、UE地址或标识、XRM业务标识等信息。一种实施方式中，AF会话请求中携带时间窗口信息。
AF通过XRM服务参数服务给业务相关的单个或多个UE提供XRM服务或多个数据服务特定参数。AF会话请求中包括：共同标识、业务参数(Service Parameters)、UE或UE组、订阅事件(Subscription to events)等信息。
其中，业务描述(Service Description)标识XRM业务或者XRM数据业务，可用DNN和组合S-NSSAI组合，或者XRM ID来标识；或者AF业务标识(Service-Identifier)或外部应用标识符(Application Identifier)来表示。
业务参数(Service Parameters)：关于XRM服务或多模式数据服务相关政策和QoS确 定的AF指南的信息。关联XRM服务或多个数据服务应用程序流量的规则列表、UE策略等参数、共同标识或组标识、DNN和S-NSSAI组、SSC模式、相应规则的选择优先级(例如备选QoS参数优先级，时间阈值优先级，接入类型或路由选择优先级等)
UE或UE组：AF请求所关联的XRM服务或多模式数据服务相关的单个UE，或多个UE(Group UE)。
订阅事件(Subscription to events)：AF可以订阅关于SM策略结果的通知或AM政策或UE策略的执行和变更。或者，XRM业务数据流的事件订阅。
当AF需要更新和删除相应请求或订阅时，也可通过该服务发起AF会话请求的更新和删除流程。
2、AF将请求发送给NEF。NEF授权AF请求。NEF执行相关映射，包括，标识XRM业务或者XRM数据业务(AF业务标识)到DNN和S-NSSAI的映射，外部应用到CN应用标识的映射；以及基于UDM的签约信息，外部UE标识到CN内UE标识的映射(如SUPI)，以及根据UDM签约信息执行外部到内部的XRM service组标识的映射。
3、NEF存储应请求信息到UDR(例如，作为应用程序数据的业务特性参数信息存储)。一种实施方式中，NEF可能会根据本地配置完善相应业务参数。
一种实施方式中，NEF可结合运营商策略和签约信息为单个UE或UE组的XRM服务或多模式数据服务，确认是否请求业务特性可授权并将相应参数存储到UDR中。
如果涉及多个UE，则NEF传送相关业务参数到PCF，在每个PCF中执行相应授权，以及策略和规则的决策或更新。PCF根据请求授权结果，存储相应信息到UDR中。(支持单PCF和多PCF场景)
多UE场景，UE组成员的签约数据可通过XRM业务指示或者Group ID/Common ID关联。
AF或PCF可通过NEF，订阅相关XRM服务或多模式数据相关事件触发器，例如QoS监控报告、服务QoS更新、UE重新定位、PCF更改等。AF或PCF通过接收NEF报告，获取相应通知，执行后续应用需求或QoS规则的更新。
4、NEF给AF返回创建请求响应消息。
如果步骤0中，PCF在UE注册后执行了签约信息更新通知，则因为AF请求更新了UDR签约信息，而执行后续的流程
5、PCF收到UDR的签约信息变更通知。
6、PCF给UE传送UE策略。
7、如果AF订阅了通知XRM服务相关策略的执行通知，则PCF通过NEF发送相关 执行结果给AF。同时，若有相关签约参数变更，PCF更新变更到UDR，触发XRM业务组相关的其它UE的serving PCF执行策略变更和协同。
8、NEF收到通知后，首先执行内外相关参数的映射，然后将相关报告发送给AF。
在本公开实施例中，PCF通过确定时间阈值，对在时间阈值之内接收到的具有相同取值的共同标识的SDF执行策略决策，为SDF传输提供更优的QoS保障，无需重复对属于同一XRM SDF组中的多个SDF进行多次策略决策的修改，提高授权效率。
需要说明的是，本领域内技术人员可以理解，本公开实施例上述涉及的各种实施方式/实施例中可以配合前述的实施例使用，也可以是独立使用。无论是单独使用还是配合前述的实施例一起使用，其实现原理类似。本公开实施中，部分实施例中是以一起使用的实施方式进行说明的。当然，本领域内技术人员可以理解，这样的举例说明并非对本公开实施例的限定。
基于相同的构思，本公开实施例还提供一种XRM业务数据传输装置。
可以理解的是，本公开实施例提供的XRM业务数据传输装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本公开实施例中所公开的各示例的单元及算法步骤，本公开实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本公开实施例的技术方案的范围。
图12是根据一示例性实施例示出的一种XRM业务数据传输装置框图。参照图12，该装置100包括确定模块101和执行模块102。
确定模块101，用于确定应用功能AF会话请求，会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
执行模块102，用于基于时间阈值和所述共同标识，对AF会话请求执行策略决策。
一种实施方式中，时间阈值包括：
基于核心网设备本地设置的定时器，确定的时间阈值；或
基于AF会话请求中携带的时间取值或时间窗口，确定的时间阈值；或
基于运营商策略中的定时器或时间窗口，确定的时间阈值；或
基于签约信息中缺省定时器或时间窗口，确定的时间阈值；或
基于核心网设备本地设置的定时器、AF会话请求中携带的时间取值或时间窗口、运营商策略中的定时器或时间窗口以及所述签约信息中缺省定时器或时间窗口的优先级，确定的时间阈值。
一种实施方式中，基于时间阈值以及所述共同标识，对AF会话请求执行策略决策，包括：
确定在时间阈值到达之前接收到的相同取值的共同标识，相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组业务数据流；
对相同取值的共同标识所标识的AF会话请求执行策略决策。
一种实施方式中，策略决策包括：
对SDF组中的SDF授权相同服务质量QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成相同的QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的策略控制与计费PCC规则，并对每个SDF生成各自的QoS。
一种实施方式中，执行模块102用于响应于在时间阈值之后接收到包括共同标识的AF会话请求，基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
图13是根据一示例性实施例示出的一种XRM业务数据传输装置框图。参照图13，该装置200包括接收模块201和执行模块202。接收模块201，用于接收应用功能AF会话请求，AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识。
执行模块202，用于基于时间阈值以及共同标识，对AF会话请求执行策略决策。
一种实施方式中，时间阈值包括：
基于策略控制功能PCF实体本地设置的定时器，确定的时间阈值；或
基于AF会话请求中携带的时间取值或时间窗口，确定的时间阈值；或
基于运营商策略中的定时器或时间窗口，确定的时间阈值；或
基于签约信息中缺省定时器或时间窗口，确定的时间阈值；或
基于PCF实体本地设置的定时器或时间窗口、AF会话请求中携带的时间取值或时间窗口、运营商策略中的定时器或时间窗口以及签约信息中缺省定时器或时间窗口的优先级，确定的时间阈值。
一种实施方式中，执行模块102用于确定在时间阈值到达之前接收到的相同取值的共同标识，相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组；
对相同取值的共同标识所标识的AF会话请求执行策略决策。
一种实施方式中，策略决策包括：
对SDF组中的SDF授权相同服务质量QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成相同的QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对所每个SDF生成各自的策略控制与计费PCC规则，并对每个SDF生成各自的QoS。
一种实施方式中，执行模块102用于响应于在时间阈值之后接收到包括共同标识的AF会话请求，基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
一种实施方式中，接收模块101用于接收AF实体、或网络开放功能NEF实体、时间敏感通信与时间同步功能TSCTSF实体中的至少一个功能实体发送的AF会话请求。
图14是根据一示例性实施例示出的一种XRM业务数据传输装置框图。参照图14，该装置300包括发送模块301。发送模块301用于发送AF会话请求，AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值，AF会话请求用于策略控制功能PCF实体基于共同标识和时间阈值对所述AF会话请求执行策略决策。
一种实施方式中，AF会话请求用于PCF实体为时间阈值到达之前接收到的相同取值的共同标识所标识的AF会话请求执行策略决策，相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组。
一种实施方式中，策略决策包括：
对SDF组中的SDF授权相同服务质量QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成相同的QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的策略控制与计费PCC规则，并对每个SDF生成各自的QoS。
一种实施方式中，在时间阈值之后发送的具有共同标识的AF会话请求的策略决策，基于时间阈值之前发送的AF会话请求的策略决策确定。
一种实施方式中，发送模块301用于向策略控制功能PCF实体、网络开发功能NEF实体、时间敏感通信与时间同步功能TSCTSF实体中的至少一个功能实体发送的AF会话请求。
图15是根据一示例性实施例示出的一种XRM业务数据传输装置框图。参照图15，该装置400包括接收模块401和发送模块402。接收模块401用于接收应用功能AF会话 请求，AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值；
发送模块402用于向策略控制功能PCF实体发送AF会话请求，AF会话请求用于所述PCF实体基于共同标识和时间阈值对AF会话请求执行策略决策。
一种实施方式中，AF会话请求用于PCF实体为所述时间阈值到达之前接收到的相同取值的共同标识所标识的AF会话请求执行策略决策，相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组。
一种实施方式中，策略决策包括：
对SDF组中的SDF授权相同服务质量QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成相同的QoS；或
基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的策略控制与计费PCC规则，并对每个SDF生成各自的QoS。
一种实施方式中，在时间阈值之后发送的具有共同标识的AF会话请求的策略决策，基于时间阈值之前发送的AF会话请求的策略决策确定。
一种实施方式中，核心网设备包括网络开放功能NEF实体和/或时间敏感通信与时间同步功能TSCTSF实体。
图16是根据一示例性实施例示出的一种XRM业务数据传输装置框图。参照图16，该装置500包括发送模块501、接收模块502和执行模块503。
发送模块501用于应用功能AF实体发送AF会话请求，AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
接收模块502用于策略控制功能PCF实体接收AF会话请求；
执行模块503用于PCF实体基于时间阈值和共同标识，对AF会话请求执行策略决策。
一种实施方式中，时间阈值包括：
基于PCF实体本地设置的定时器，确定的时间阈值；或
基于AF会话请求中携带的时间取值或时间窗口，确定的时间阈值；或
基于运营商策略中的定时器或时间窗口，确定的时间阈值；或
基于签约信息中缺省定时器或时间窗口，确定的时间阈值；或
基于PCF实体本地设置的定时器、AF会话请求中携带的时间取值或时间窗口、运营商策略中的定时器或时间窗口以及所述签约信息中缺省定时器或时间窗口的优先级，确定的时间阈值。
一种实施方式中，执行模块503用于PCF实体确定在时间阈值到达之前接收到的相同取值的共同标识，相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组业务数据流；PCF实体对相同取值的共同标识所标识的AF会话请求执行策略决策。
一种实施方式中，策略决策包括：
PCF实体对SDF组中的SDF授权相同服务质量QoS；或
PCF实体基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成相同的QoS；或
PCF实体基于SDF组中每个SDF对应的签约信息和/或运营商策略，对每个SDF生成各自的策略控制与计费PCC规则，并对每个SDF生成各自的QoS。
一种实施方式中，执行模块503响应于在时间阈值之后接收到包括共同标识的AF会话请求，PCF实体基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
一种实施方式中，发送模块501用于AF向网络开放功能NEF实体、时间敏感通信与时间同步功能TSCTSF实体以及PCF实体中的至少一个发送AF会话请求。
一种实施方式中，接收模块502用于PCF接收AF实体、或网络开放功能NEF实体、时间敏感通信与时间同步功能TSCTSF实体中的至少一个功能实体发送的AF会话请求。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
图17是根据一示例性实施例示出的一种用于扩展现实和多媒体业务数据传输的装置600的框图。例如，装置600可以被提供为一服务器。参照图17，装置600包括处理组件622，其进一步包括一个或多个处理器，以及由存储器632所代表的存储器资源，用于存储可由处理组件622的执行的指令，例如应用程序。存储器632中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件622被配置为执行指令，以执行上述方法。
装置600还可以包括一个电源组件626被配置为执行装置600的电源管理，一个有线或无线网络接口650被配置为将装置600连接到网络，和一个输入输出(I/O)接口658。装置600可以操作基于存储在存储器632的操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM或类似。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器632，上述指令可由装置600的处理组件622执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁 带、软盘和光数据存储设备等。
进一步可以理解的是，本公开中“多个”是指两个或两个以上，其它量词与之类似。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
进一步可以理解的是，本公开中涉及到的“响应于”“如果”等词语的含义取决于语境以及实际使用的场景，如在此所使用的词语“响应于”可以被解释成为“在……时”或“当……时”或“如果”或“若”。
进一步可以理解的是，术语“第一”、“第二”等用于描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开，并不表示特定的顺序或者重要程度。实际上，“第一”、“第二”等表述完全可以互换使用。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。
进一步可以理解的是，本公开实施例中尽管在附图中以特定的顺序描述操作，但是不应将其理解为要求按照所示的特定顺序或是串行顺序来执行这些操作，或是要求执行全部所示的操作以得到期望的结果。在特定环境中，多任务和并行处理可能是有利的。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利范围来限制。

Claims (37)

  1. 一种扩展现实和多媒体业务数据传输方法，其特征在于，由核心网设备执行，所述方法包括：
    确定应用功能AF会话请求，所述会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
    基于时间阈值和所述共同标识，对AF会话请求执行策略决策。
  2. 根据权利要求1所述的方法，其特征在于，所述时间阈值包括：
    基于所述核心网设备本地设置的定时器，确定的时间阈值；或
    基于所述AF会话请求中携带的时间取值或时间窗口，确定的时间阈值；或
    基于运营商策略中的定时器或时间窗口，确定的时间阈值；或
    基于签约信息中缺省定时器或时间窗口，确定的时间阈值；或
    基于所述核心网设备本地设置的定时器、所述AF会话请求中携带的时间取值或时间窗口、所述运营商策略中的定时器或时间窗口以及所述签约信息中缺省定时器或时间窗口的优先级，确定的时间阈值。
  3. 根据权利要求1或2所述的方法，其特征在于，所述基于时间阈值以及所述共同标识，对所述AF会话请求执行策略决策，包括：
    确定在所述时间阈值到达之前接收到的相同取值的共同标识，所述相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组业务数据流；
    对所述相同取值的共同标识所标识的AF会话请求执行策略决策。
  4. 根据权利要求3所述的方法，其特征在于，所述策略决策包括：
    对所述SDF组中的SDF授权相同服务质量QoS；或
    基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成相同的QoS；或
    基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成各自的策略控制与计费PCC规则，并对所述每个SDF生成各自的QoS。
  5. 根据权利要求3或4所述的方法，其特征在于，所述方法还包括：
    响应于在时间阈值之后接收到包括所述共同标识的AF会话请求，基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
  6. 一种扩展现实和多媒体业务数据传输方法，其特征在于，由核心网设备中的策略 控制功能PCF实体执行，所述方法包括：
    接收应用功能AF会话请求，所述AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
    基于时间阈值以及所述共同标识，对所述AF会话请求执行策略决策。
  7. 根据权利要求6所述的方法，其特征在于，所述时间阈值包括：
    基于所述策略控制功能PCF实体本地设置的定时器，确定的时间阈值；或
    基于所述AF会话请求中携带的时间取值或时间窗口，确定的时间阈值；或
    基于运营商策略中的定时器或时间窗口，确定的时间阈值；或
    基于签约信息中缺省定时器或时间窗口，确定的时间阈值；或
    基于所述PCF实体本地设置的定时器、所述AF会话请求中携带的时间取值或时间窗口、所述运营商策略中的定时器或时间窗口以及所述签约信息中缺省定时器或时间窗口的优先级，确定的时间阈值。
  8. 根据权利要求6或7所述的方法，其特征在于，所述基于时间阈值以及所述共同标识，对所述AF会话请求执行策略决策，包括：
    确定在所述时间阈值到达之前接收到的相同取值的共同标识，所述相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组业务数据流；
    对所述相同取值的共同标识所标识的AF会话请求执行策略决策。
  9. 根据权利要求8所述的方法，其特征在于，所述策略决策包括：
    对所述SDF组中的SDF授权相同服务质量QoS；或
    基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成相同的QoS；或
    基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成各自的策略控制与计费PCC规则，并对所述每个SDF生成各自的QoS。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    响应于在时间阈值之后接收到包括所述共同标识的AF会话请求，基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
  11. 根据权利要求6所述的方法，其特征在于，所述接收AF会话请求，包括：
    接收AF实体、或网络开放功能NEF实体、时间敏感通信与时间同步功能TSCTSF实体中的至少一个功能实体发送的AF会话请求。
  12. 一种扩展现实和多媒体业务数据传输方法，其特征在于，由核心网设备中的应用功能AF实体执行，所述方法包括：
    发送AF会话请求，所述AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值，所述AF会话请求用于策略控制功能PCF实体基于所述共同标识和时间阈值对所述AF会话请求执行策略决策。
  13. 根据权利要求12所述的方法，其特征在于，所述AF会话请求用于PCF实体为所述时间阈值到达之前接收到的相同取值的共同标识所标识的AF会话请求执行策略决策，所述相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组。
  14. 根据权利要求12或13所述的方法，其特征在于，所述策略决策包括：
    对所述SDF组中的SDF授权相同服务质量QoS；或
    基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成相同的QoS；或
    基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成各自的策略控制与计费PCC规则，并对所述每个SDF生成各自的QoS。
  15. 根据权利要求12所述的方法，其特征在于，在所述时间阈值之后发送的具有共同标识的AF会话请求的策略决策，基于时间阈值之前发送的AF会话请求的策略决策确定。
  16. 根据权利要求15所述的方法，其特征在于，所述发送AF会话请求，包括：
    向策略控制功能PCF实体、网络开发功能NEF实体、时间敏感通信与时间同步功能TSCTSF实体中的至少一个功能实体发送的AF会话请求。
  17. 一种扩展现实和多媒体业务数据传输方法，其特征在于，由核心网设备中的核心网功能网元执行，所述方法包括：
    接收应用功能AF会话请求，所述AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值；
    向策略控制功能PCF实体发送所述AF会话请求，所述AF会话请求用于所述PCF实体基于所述共同标识和时间阈值对所述AF会话请求执行策略决策。
  18. 根据权利要求17所述的方法，其特征在于，所述AF会话请求用于所述PCF实体为所述时间阈值到达之前接收到的相同取值的共同标识所标识的AF会话请求执行策略决策，所述相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组。
  19. 根据权利要求17或18所述的方法，其特征在于，所述策略决策包括：
    对所述SDF组中的SDF授权相同服务质量QoS；或
    基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成相同的QoS；或
    基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成各自的策略控制与计费PCC规则，并对所述每个SDF生成各自的QoS。
  20. 根据权利要求19所述的方法，其特征在于，在所述时间阈值之后发送的具有共同标识的AF会话请求的策略决策，基于时间阈值之前发送的AF会话请求的策略决策确定。
  21. 根据权利要求17所述的方法，其特征在于，所述核心网功能网元包括网络开放功能NEF实体和/或时间敏感通信与时间同步功能TSCTSF实体。
  22. 一种扩展现实和多媒体业务数据传输方法，其特征在于，包括：
    应用功能AF实体发送AF会话请求，所述AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
    策略控制功能PCF实体接收所述AF会话请求；
    PCF实体基于时间阈值和所述共同标识，对所述AF会话请求执行策略决策。
  23. 根据权利要求22所述的方法，其特征在于，所述时间阈值包括：
    基于所述PCF实体本地设置的定时器，确定的时间阈值；或
    基于所述AF会话请求中携带的时间取值或时间窗口，确定的时间阈值；或
    基于运营商策略中的定时器或时间窗口，确定的时间阈值；或
    基于签约信息中缺省定时器或时间窗口，确定的时间阈值；或
    基于所述PCF实体本地设置的定时器、所述AF会话请求中携带的时间取值或时间窗口、所述运营商策略中的定时器或时间窗口以及所述签约信息中缺省定时器或时间窗口的优先级，确定的时间阈值。
  24. 根据权利要求22或23所述的方法，其特征在于，所述PCF实体基于时间阈值和所述共同标识，对所述AF会话请求执行策略决策，包括：
    PCF实体确定在所述时间阈值到达之前接收到的相同取值的共同标识，所述相同取值的共同标识用于标识多个XRM业务数据流SDF归属同一组业务数据流；
    PCF实体对所述相同取值的共同标识所标识的AF会话请求执行策略决策。
  25. 根据权利要求24所述的方法，其特征在于，所述策略决策包括：
    PCF实体对所述SDF组中的SDF授权相同服务质量QoS；或
    PCF实体基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个 SDF生成相同的QoS；或
    PCF实体基于所述SDF组中每个SDF对应的签约信息和/或运营商策略，对所述每个SDF生成各自的策略控制与计费PCC规则，并对所述每个SDF生成各自的QoS。
  26. 根据权利要求24或25所述的方法，其特征在于，所述方法还包括：
    响应于在时间阈值之后接收到包括所述共同标识的AF会话请求，PCF实体基于时间阈值之前接收到AF会话请求执行的策略决策，对时间阈值之后接收到的AF会话请求执行策略决策。
  27. 根据权利要求22所述的方法，其特征在于，所述应用功能实体AF发送AF会话请求包括：
    AF向网络开放功能NEF实体、时间敏感通信与时间同步功能TSCTSF实体以及PCF实体中的至少一个发送AF会话请求。
  28. 根据权利要求22所述的方法，其特征在于，所述策略控制功能PCF实体接收所述AF会话请求，包括：
    PCF接收AF实体、或网络开放功能NEF实体、时间敏感通信与时间同步功能TSCTSF实体中的至少一个功能实体发送的AF会话请求。
  29. 一种扩展现实和多媒体业务数据传输装置，其特征在于，所述装置包括：
    确定模块，用于确定应用功能AF会话请求，所述会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
    执行模块，用于基于时间阈值和所述共同标识，对AF会话请求执行策略决策。
  30. 一种扩展现实和多媒体业务数据传输装置，其特征在于，所述装置包括：
    接收模块，用于接收应用功能AF会话请求，所述AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
    执行模块，用于基于时间阈值以及所述共同标识，对所述AF会话请求执行策略决策。
  31. 一种扩展现实和多媒体业务数据传输装置，其特征在于，所述装置包括：
    发送模块，用于发送AF会话请求，所述AF会话请求中包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值，所述AF会话请求用于策略控制功能PCF实体基于所述共同标识和时间阈值对所述AF会话请求执行策略决策。
  32. 一种扩展现实和多媒体业务数据传输装置，其特征在于，所述装置包括：
    接收模块，用于接收应用功能AF会话请求，所述AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识和时间阈值；
    发送模块，用于向策略控制功能PCF实体发送所述AF会话请求，所述AF会话请求 用于所述PCF实体基于所述共同标识和时间阈值对所述AF会话请求执行策略决策。
  33. 一种扩展现实和多媒体业务数据传输装置，其特征在于，包括：
    发送模块，用于应用功能实体AF发送AF会话请求，所述AF会话请求包括用于标识扩展现实和多媒体XRM业务数据流SDF组的共同标识；
    接收模块，用于策略控制功能PCF实体接收所述AF会话请求；
    执行模块，用于PCF实体基于时间阈值和所述共同标识，对所述AF会话请求执行策略决策。
  34. 一种扩展现实和多媒体业务数据传输装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：执行权利要求1至5中任意一项所述的方法或权利要求6至11中任意一项所述的方法或权利要求12至16中任意一项所述的方法或权利要求17至21中任意一项所述的方法或权利要求22至28中任意一项所述的方法。
  35. 一种存储介质，其特征在于，所述存储介质中存储有指令，当所述存储介质中的指令由核心网设备的处理器执行时，使得核心网设备能够执行权利要求1至5中任意一项所述的方法，或当所述存储介质中的指令由策略控制功能PCF实体的处理器执行时，使得PCF实体能够执行权利要求6至11中任意一项所述的方法，或当所述存储介质中的指令由应用功能AF实体的处理器执行时，使得AF实体能够执行权利要求12至16中任意一项所述的方法，或当所述存储介质中的指令由核心网功能网元的处理器执行时，使得核心网功能网元能够执行权利要求17至21中任意一项所述的方法，或当所述存储介质中的指令由核心网设备中的PCF实体、AF实体的处理器执行时，使得PCF实体、AF实体能够执行权利要求22至28中任意一项所述的方法。
  36. 一种通信系统，其特征在于，所述系统用于执行如权利要求1-5任一项所述的方法。
  37. 一种通信系统，其特征在于，包括以下的实体：
    用于执行如权利要求6-11任一项所述的方法的策略控制功能PCF实体；
    用于执行如权利要求12-16任一项所述的方法的应用功能AF实体；
    用于执行如权利要求17-21任一项所述的方法的核心网功能网元。
PCT/CN2023/072476 2023-01-16 2023-01-16 扩展现实和多媒体业务数据传输方法、装置及存储介质 WO2024152183A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/072476 WO2024152183A1 (zh) 2023-01-16 2023-01-16 扩展现实和多媒体业务数据传输方法、装置及存储介质
CN202380007953.8A CN118679720A (zh) 2023-01-16 2023-01-16 扩展现实和多媒体业务数据传输方法、装置及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/072476 WO2024152183A1 (zh) 2023-01-16 2023-01-16 扩展现实和多媒体业务数据传输方法、装置及存储介质

Publications (1)

Publication Number Publication Date
WO2024152183A1 true WO2024152183A1 (zh) 2024-07-25

Family

ID=91955123

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/072476 WO2024152183A1 (zh) 2023-01-16 2023-01-16 扩展现实和多媒体业务数据传输方法、装置及存储介质

Country Status (2)

Country Link
CN (1) CN118679720A (zh)
WO (1) WO2024152183A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101370263A (zh) * 2007-08-15 2009-02-18 华为技术有限公司 一种策略控制方法及系统
CN114079944A (zh) * 2020-08-18 2022-02-22 华为技术有限公司 通信方法、装置及系统
WO2022093238A1 (en) * 2020-10-29 2022-05-05 Telefonaktiebolaget Lm Ericsson (Publ) Managing network slice bandwidth for remote game sessions

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101370263A (zh) * 2007-08-15 2009-02-18 华为技术有限公司 一种策略控制方法及系统
CN114079944A (zh) * 2020-08-18 2022-02-22 华为技术有限公司 通信方法、装置及系统
WO2022093238A1 (en) * 2020-10-29 2022-05-05 Telefonaktiebolaget Lm Ericsson (Publ) Managing network slice bandwidth for remote game sessions

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHINA MOBILE ET AL.: "New WID: Architecture Enhancements for XR and media services (XRM)", TSG SA MEETING #SP-98E SP-221134_REV1, 19 December 2021 (2021-12-19) *

Also Published As

Publication number Publication date
CN118679720A (zh) 2024-09-20

Similar Documents

Publication Publication Date Title
EP3780682B1 (en) Method and device for subscribing to service
CN110035424B (zh) 策略相关的通信方法、装置和系统
WO2020224622A1 (zh) 一种信息配置方法及装置
US12058139B2 (en) Method for implementing user plane security policy, apparatus, and system
JP2020505816A (ja) 通信方法、アクセスネットワークデバイス、コアネットワークデバイス及びユーザ装置
US11483801B2 (en) Resource configuration method and apparatus
US10530699B2 (en) Processing method, apparatus, and system for a service flow processing policy
US20220256396A1 (en) Congestion control method and apparatus
US20220225094A1 (en) Communication method, device, and system, and storage medium
CN113630819B (zh) 应用迁移方法及装置
CN110856175A (zh) 一种用户面安全的授权方法及装置
WO2018233451A1 (zh) 通信方法、装置和系统
US10959097B1 (en) Method and system for accessing private network services
WO2023280093A1 (zh) 执行在线签约的方法和装置
WO2024152183A1 (zh) 扩展现实和多媒体业务数据传输方法、装置及存储介质
KR102318746B1 (ko) 가상 id를 이용하여 복수의 pdu 세션들을 처리하는 방법 및 상기 방법을 수행하는 smf
WO2024152182A1 (zh) 扩展现实和多媒体业务数据传输方法、装置及存储介质
KR102273390B1 (ko) 네트워크 기능 통합방법 및 장치
WO2020088626A1 (zh) 一种pdu会话的动态调整方法、装置
WO2024148497A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2024061205A1 (zh) 参数获取方法、装置、第一网络功能及第二网络功能
WO2024067331A1 (zh) 个人物联网中的设备切换方法、通信方法及设备
EP4167681B1 (en) Communication method and apparatus
WO2023077948A1 (zh) 一种通信的方法和装置
WO2024092677A1 (zh) 漫游场景下传输数据的方法、装置及可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23916674

Country of ref document: EP

Kind code of ref document: A1