WO2023184191A1 - 一种扩展现实多媒体xrm业务的处理方法及其装置 - Google Patents

一种扩展现实多媒体xrm业务的处理方法及其装置 Download PDF

Info

Publication number
WO2023184191A1
WO2023184191A1 PCT/CN2022/083866 CN2022083866W WO2023184191A1 WO 2023184191 A1 WO2023184191 A1 WO 2023184191A1 CN 2022083866 W CN2022083866 W CN 2022083866W WO 2023184191 A1 WO2023184191 A1 WO 2023184191A1
Authority
WO
WIPO (PCT)
Prior art keywords
xrm
service
terminal device
information
business
Prior art date
Application number
PCT/CN2022/083866
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 CN202280000867.XA priority Critical patent/CN117158107A/zh
Priority to PCT/CN2022/083866 priority patent/WO2023184191A1/zh
Publication of WO2023184191A1 publication Critical patent/WO2023184191A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to a processing method and device for extended reality multimedia XRM services.
  • Extended reality multimedia (XRM) services such as virtual reality (VR), augmented reality (Augmented reality) and other XR services, video-based machine or drone remote control and other services will involve multi-modality data flow.
  • Each data stream in multimodal data often has a certain or even strong correlation, such as the synchronization of audio and video streams, the synchronization of touch and vision, etc.
  • XRM business requires the fifth generation mobile communication technology system (5th Generation Mobile Communication Technology system, 5GS) to comprehensively consider the relevant data flow quality of service (Quality of Service, QoS) characteristics of the business, such as delay critical, guaranteed bit rate (Guaranteed BitRate, GBR) , whether the guaranteed flow bit rate (Guaranteed flow Bit Rate, GFBR), packet delay budget (PacketDelayBudget, PDB), default maximum data burst volume (DefaultMaximumDataBurstVolume, MDBV)) and other parameters can be met and coordinated at the same time, especially when multiple The XRM business of terminal equipment ensures the consistency of QoS authorization and execution between multiple terminal equipment.
  • QoS Quality of Service
  • Embodiments of the present disclosure provide an extended reality multimedia XRM service processing method and device, which can be applied in the field of communication technology.
  • embodiments of the present disclosure provide a method for processing extended reality multimedia XRM services.
  • the method is executed by the network opening function NEF.
  • the method includes: receiving a request message sent by the application function AF, wherein the request message carries XRM business information; update the XRM information in the unified data register UDR according to the contract information corresponding to the XRM business information and the XRM business information.
  • NEF after NEF receives the XRM service information sent by AF, it can update the XRM information in the UDR based on the service information and the contract information corresponding to the XRM service information for PCF or RAN execution, thus realizing the XRM business group
  • NEF after NEF receives the XRM service information sent by AF, it can update the XRM information in the UDR based on the service information and the contract information corresponding to the XRM service information for PCF or RAN execution, thus realizing the XRM business group
  • the corresponding coordination of access and mobility-related requirements among multiple terminal devices ensures XRM business data flow QoS and transmission strategy coordination.
  • embodiments of the present disclosure provide another extended reality multimedia XRM service processing method.
  • the method is executed by the application function AF.
  • the method includes: sending a request message to the network opening function NEF, wherein the request message carries the XRM service information.
  • AF sends XRM service information to NEF, so that NEF can update UDR information as needed or send XRM service information to PCF, thereby realizing access and mobility between multiple terminal devices associated with the XRM service group.
  • the coordination of related requirements ensures the coordination of XRM business data flow QoS and transmission strategy.
  • embodiments of the present disclosure provide another extended reality multimedia XRM service processing method.
  • the method is executed by the policy control function PCF device.
  • the method includes: receiving XRM service information associated with the terminal device; and generating, according to the XRM service information, Quality of Service Qos rules and/or terminal device access and routing policies; sending the Qos rules and/or terminal device access and routing policies to the terminal device.
  • PCF after PCF obtains the XRM business information, it can perform corresponding authorization, measurement and rule decisions and updates based on this information, and send the generated Qos rules and/or terminal device access and routing policies to Terminal equipment, so that terminal equipment associated with XRM services can achieve coordination of QoS rules and/or terminal equipment access and routing strategies, providing a guarantee for realizing XRM business data flow QoS and transmission strategy coordination.
  • embodiments of the present disclosure provide another extended reality multimedia XRM service processing method.
  • the method is executed by a terminal device.
  • the method includes: receiving quality of service Qos rules sent by the policy control function PCF device and/or terminal device access and Routing policy, wherein the Qos rules and/or terminal device access and routing policies are generated based on XRM service information; execute the Qos rules and/or terminal device access and routing policies.
  • the terminal device after the terminal device receives the Qos rules and/or the terminal device access and routing policies generated based on the XRM service information, it can perform access and routing based on the Qos rules and/or the terminal device access and routing policies. Communication transmission, thereby realizing the coordination of QoS rules and/or terminal device access and routing strategies between terminal devices associated with the XRM service, and providing guarantee for the realization of XRM service data flow QoS and transmission strategy coordination.
  • embodiments of the present disclosure provide a communication device configured on the network opening function NEF side, including:
  • a transceiver module configured to receive a request message sent by the application function AF, where the request message carries XRM business information;
  • a processing module configured to update the XRM information in the unified data register UDR according to the contract information corresponding to the XRM service information and the XRM service information.
  • embodiments of the present disclosure provide a communication device configured on the application function AF side, including:
  • the transceiver module is configured to send a request message to the network opening function NEF, where the request message carries XRM service information.
  • embodiments of the present disclosure provide a communication device configured on the policy control function PCF device side, including:
  • Transceiver module used to receive XRM business information associated with terminal equipment
  • a processing module configured to generate quality of service Qos rules and/or terminal device access and routing policies based on the XRM service information
  • the transceiver module is also used to send Qos rules and/or terminal device access and routing policies to the terminal device.
  • an embodiment of the present disclosure provides a communication device, which is configured on the terminal device side and includes:
  • the transceiver module is used to receive the quality of service Qos rules and/or terminal device access and routing policies sent by the policy control function PCF device;
  • Processing module for executing Qos rules and/or terminal device access and routing policies.
  • an embodiment of the present disclosure provides a communication device.
  • the communication device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the communication device executes The method described in the above first aspect, or the method described in the above second aspect, or the method described in the above third aspect, or the method described in the above fourth aspect.
  • embodiments of the present disclosure provide an extended reality multimedia XRM service processing system.
  • the system includes the communication device described in the fourth aspect, the communication device described in the fifth aspect, the communication device described in the sixth aspect, Or the communication device according to the seventh aspect.
  • embodiments of the present invention provide a computer-readable storage medium for storing instructions used by the above-mentioned terminal device.
  • the network opening function NEF is caused to execute the above-mentioned first aspect.
  • Figure 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure
  • Figure 2 is a schematic flow chart of an extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure
  • Figure 3 is a schematic flow chart of another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure
  • Figure 4 is a schematic flowchart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure
  • Figure 5 is a schematic flowchart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure
  • Figure 6 is a schematic flow chart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure
  • Figure 7 is a schematic flow chart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure.
  • Figure 8 is a schematic flowchart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure
  • Figure 9 is a schematic flowchart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure.
  • Figure 10 is a schematic flowchart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure
  • Figure 11 is a schematic flow chart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure.
  • Figure 11a is a schematic flow chart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure
  • Figure 12 is an interactive schematic diagram of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure
  • Figure 13 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure.
  • Figure 14 is a schematic structural diagram of another communication device provided by an embodiment of the present disclosure.
  • Figure 15 is a schematic structural diagram of a chip provided by an embodiment of the present disclosure.
  • AMF Access and mobility management function
  • AMF is a logical node function network element on the core network side. It is the core network control plane access point for terminals and wireless. It receives all connection and session-related information from user equipment, and performs registration, connection, reachability, and mobility management. In addition, AMF provides session management message transmission channels for terminal devices and session management function (SMF) devices, and provides authentication and authentication functions for users when accessing.
  • SMF session management function
  • Radio access network (RAN)
  • RAN is the implementation of wireless access technology. It exists between a device (for example, a mobile phone, a computer, or any remotely controlled machine) and the core network (Core Network, CN), providing a communication connection between the two.
  • a device for example, a mobile phone, a computer, or any remotely controlled machine
  • the core network Core Network, CN
  • PCF Policy control function
  • PCF is another functional network element on the core network side. It can support a unified policy framework to manage network behavior, provide policy rules for network entities to implement, and access subscription information of the unified data repository (UDR).
  • UDR unified data repository
  • NEF is another functional network element on the core network side. 3gpp network elements open their capabilities to other network elements through NEF. NEF stores relevant information in the unified data repository (UDR) and can also obtain relevant information from the UDR. NEF can only access the UDR of the same public land mobile network (Public land mobile network, PLMN) as it.
  • PLMN public land mobile network
  • NEF provides corresponding security guarantees to ensure the security of external applications to the 3gpp network, and the conversion of 3gpp internal and external related information, such as the application function (AF) service identifier ServiceIdentifier and the data network name (data network name) within the 5G core network , DNN,), network slice selection assistance information (S-NSSAI), etc., especially network and user sensitive information must be hidden from external network elements; NEF can obtain other networks by accessing NDR For element-related information, NEF can only access the UDR of the same PLMN.
  • AF application function
  • S-NSSAI network slice selection assistance information
  • UDR is another functional network element on the core network side. It can be used for unified data management (UDM) to store or read subscription data; PCF stores or reads policy data; stores open data or Read open data from it; UDR and the network function (NF) accessing it have the same PLMN, that is, under the same network. That is, the service interface (Nudr) provided by UDR is a PLMN internal interface.
  • UDM unified data management
  • PCF stores or reads policy data
  • NF network function
  • AF is another functional network element on the core network side. It can interact with the 3GPP core network to provide services and support the following functions: the impact of the application side on business flow routing; access to network opening functions; exchange with the policy framework for policy control; Depending on the operator's deployment, application functions trusted by the operator can directly interact with related network functions. For application functions that the operator does not allow direct access to network functions, the External Capability Opening Framework (NEF) should be used to interact with the relevant network functions through NEF.
  • NEF External Capability Opening Framework
  • FIG. 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present disclosure.
  • the communication system may include but is not limited to one network device and one terminal device.
  • the number and form of devices shown in Figure 1 are only for examples and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more devices may be included.
  • the communication system shown in Figure 1 includes an access network device 11, a terminal device 12, and a core network device 13.
  • LTE long term evolution
  • 5th generation fifth generation
  • 5G new radio (NR) system 5th generation new radio
  • the access network device 11 in the embodiment of the present disclosure is an entity on the network side that is used to transmit or receive signals.
  • the access network device 11 can be an evolved base station (evolved NodeB, eNB), a transmission point (transmission reception point, TRP), a next generation base station (next generation NodeB, gNB) in an NR system, or other future mobile communication systems.
  • eNB evolved base station
  • TRP transmission reception point
  • gNB next generation base station
  • WiFi wireless fidelity
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the access network equipment.
  • the access network device 11 may be composed of a centralized unit (central unit, CU) and a distributed unit (DU), where the CU may also be called a control unit (control unit), using
  • the CU-DU structure can separate the protocol layers of network equipment, such as base stations, with some protocol layer functions placed under centralized control on the CU, while the remaining part or all protocol layer functions are distributed in the DU, and the CU centrally controls the DU.
  • the terminal device 12 in the embodiment of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone.
  • Terminal equipment can also be called terminal equipment (terminal), user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal equipment (mobile terminal, MT), etc.
  • the terminal device can be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid, wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific equipment form used by the terminal equipment.
  • the XRM service requires the 5GS system to comprehensively consider the relevant data flow QoS characteristics of the service, such as whether data flow, GFBR, PDB, MDBV and other parameters can be satisfied and coordinated at the same time, especially the XRM service involving multiple terminal devices. The consistency of QoS authorization and execution between terminal devices is guaranteed.
  • the management and coordination of access and mobility-related requirements among multiple terminal devices of XRM services are the prerequisite for ensuring the coordination of XRM service data flow QoS and transmission strategies.
  • RFSP Frequency Selection Priority
  • service area restrictions service area restrictions
  • PCF can modify service area restrictions at any time based on changes in operator policies or authorized tracking area ID (TAI) to ensure real-time collaboration without conflicts.
  • the present invention enhances the functions of NEF and supports providing XRMservice related application requests (Applicationrequirements) from AF, such as service specific parameters (service specific parameters) of one terminal device or multiple terminal devices for XRM services. ;QoS policy decision (policydecision) and or policy coordination (policy coordination) of XRM data flow; support AF's subscription and reporting of the QoS policy delivery result (deliveryresult) or QoS change (change) of the XRM data flow of XRMservice-related terminal equipment ;For PCF to execute the policyandQoScoordination between multiple PCFs corresponding to the XRMservice group terminal equipment.
  • This can support the XRMservice requirements of multiple terminal devices in the network using packet data unit session (withpacket dataunitsession), especially the policy and QoScoordination between multiple PCFs corresponding to the XRMservice Group terminal device.
  • the XRM service in this disclosure can also be called a multi-modal data flow service, or a multi-modal data flow service, etc. This disclosure does not cover this limited.
  • Figure 2 is a schematic flowchart of an extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. The method is executed by NEF. As shown in Figure 2, the method may include but is not limited to the following steps:
  • Step 201 Receive a request message sent by the application function AF, where the request message carries XRM service information.
  • NEF can receive the request message sent by AF through the service interface Nnef_XRM ServiceParameter service provided by NEF.
  • the XRM service information includes at least one of the following: an XRM service identifier, an XRM service group identifier, and specific parameters for AF to provide XRM services or multi-modal data services for XRM service-related terminal devices.
  • the XRM service identifier can be any identification information that can uniquely determine the XRM service.
  • the XRM service group identifier can be used to identify each terminal device related to the XRM service.
  • AF is a specific parameter provided by a terminal device related to the XRM service, and may also be a specific parameter of a multi-modal data service corresponding to the XRM service, which is not limited in this disclosure.
  • AF is the specific parameters of the XRM service or multi-modal data service provided by the one terminal device or multiple terminal devices, which may include the following: At least one item: Service Description, Service Parameters, terminal device identification, terminal device group identification, Subscription to events.
  • Service Description can be used to identify XRMservice or XRM data Service.
  • DNN and S-NSSAI can be identified by a combination of DNN and S-NSSAI (combination of DNN and S-NSSAI), or it can be identified by an XRM identification (ID); or it can be identified by an AFServiceIdentifier or an external application identifier (Application Identifier) )To represent.
  • Service Parameters information about AF guidelines determined by policies and QoS related to XRM business or multi-modal data services. For example, a list of rules that associate XRMservice or multiple data Service application traffic (a list of rules that associate XRMservice or multiple data Service application traffic); terminal device policy (policy) and other parameters; group identifier (GroupID); DNN and S-NSSAI Combination; the selection priority of the corresponding rule, for example: the priority of alternative (Alternative) QoS parameters, the priority of corresponding location (location) or time window (TimeWindow), or the priority of routing selection, etc.
  • policy terminal device policy
  • GroupID group identifier
  • DNN DNN
  • S-NSSAI Combination the selection priority of the corresponding rule, for example: the priority of alternative (Alternative) QoS parameters, the priority of corresponding location (location) or time window (TimeWindow), or the priority of routing selection, etc.
  • Subscription to events is the notifications about the SM policy results that AF needs to subscribe to (The AF may subscribe to notifications about the outcome of the SMpolicy), or the execution and changes of AMpolicy or UE Policy.
  • the subscription data of multiple terminal devices related to the XRM service can be associated through the XRM service identifier.
  • the data of multiple terminal devices in the XRM business group remains consistent.
  • the service QoS of multiple terminal devices is consistent, and the characteristic parameters of access and data routing are consistent.
  • Step 202 Update the XRM information in the unified data register UDR according to the contract information corresponding to the XRM service information and the XRM service information.
  • NEF after NEF receives the request message sent by AF, it can confirm whether to authorize the request based on the XRM business information. If the authorization is confirmed, the information corresponding to the XRM in the UDR can be updated based on the contract information and XRM service information corresponding to the XRM service information. For example, the characteristic parameters of the XRM can be updated for execution by the RAN or PCF to realize the XRM service group. Policies and QoS coordination among multiple PCFs corresponding to multiple terminal devices respectively, thereby realizing coordination of access and mobility-related requirements among multiple terminal devices associated with the XRM business group, thus ensuring XRM business data flow QoS and transmission policy coordination.
  • NEF after NEF receives the XRM service information sent by AF, it can update the XRM information in the UDR based on the service information and the contract information corresponding to the XRM service information for PCF or RAN execution, thus realizing the XRM business group
  • NEF after NEF receives the XRM service information sent by AF, it can update the XRM information in the UDR based on the service information and the contract information corresponding to the XRM service information for PCF or RAN execution, thus realizing the XRM business group
  • the corresponding coordination of access and mobility-related requirements among multiple terminal devices ensures XRM business data flow QoS and transmission strategy coordination.
  • Figure 3 is a schematic flowchart of an extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. The method is executed by NEF. As shown in Figure 3, the method may include but is not limited to the following steps:
  • Step 301 Receive a request message sent by the application function AF, where the request message carries XRM service information.
  • step 301 For the specific implementation of the above step 301, reference can be made to the detailed description of any embodiment of the present disclosure, which will not be described again here.
  • Step 302 Determine the core network side mapping information corresponding to the XRM service information.
  • NEF can determine the XRM business identifier or multi-modal data service identifier, the corresponding data network name DNN and network slice selection support information S-NSSAI; determine the data network name DNN and network slice corresponding to the multi-modal data service identifier Select the support information S-NSSAI; determine the external application identifier, that is, the core network (CN) application identifier corresponding to the XRM service identifier, where the external application identifier is used to identify the XRM service; according to the The contract information determines the terminal device identifier in the CN corresponding to the terminal device identifier; according to the contract information corresponding to the XRM service, determines the XRM business group identifier in the CN corresponding to the XRM business group identifier. Among them, NEF can obtain the contract corresponding to the XRM service from the UDM information.
  • Step 303 Determine the characteristic parameters corresponding to the XRM service.
  • NEF can determine the corresponding characteristic parameters based on the contract information corresponding to the XRM service.
  • NEF can also improve corresponding service feature parameters according to its local configuration.
  • Step 304 Store the characteristic parameters corresponding to the XRM service in the UDR.
  • NEF can store feature parameters as business feature parameters of application data.
  • NEF determines the characteristic parameters corresponding to the XRM service
  • it can store the characteristic parameters in the UDR. Therefore, the network element device, that is, the consumer (consumer), such as AF, PCF, SMF or AMF
  • the network element device such as AF, PCF, SMF or AMF
  • you can obtain the characteristic parameters corresponding to the XRM service reported by the UDR by subscribing to the event trigger, and then determine the corresponding policy and QoS, thereby realizing the access and mobility-related requirements among multiple terminal devices associated with the XRM service group.
  • Collaboration ensures XRM business data flow QoS and transmission strategy collaboration.
  • NEF after NEF receives the XRM service information sent by AF, it can determine the characteristic parameters corresponding to the XRM service based on the service information and the contract information corresponding to the XRM service information, and then store the characteristic parameters in the UDR for use. It is used on the consumer side to achieve coordination of access and mobility-related needs among multiple terminal devices associated with the XRM business group, thereby ensuring XRM business data flow QoS and transmission strategy coordination.
  • Figure 4 is a schematic flowchart of another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. This method is executed by NEF. As shown in Figure 4, the method may include but is not limited to the following steps:
  • Step 401 Receive a request message sent by the application function AF, where the request message carries XRM service information.
  • Step 402 Determine the core network side mapping information corresponding to the XRM service information.
  • Step 403 Determine the characteristic parameters corresponding to the XRM service.
  • Step 404 Send the characteristic parameters corresponding to the XRM service to the policy control function PCF device.
  • PCF can perform response authorization, as well as decision-making or updating of measurements and rules.
  • PCF can also store corresponding information in UDF based on the authorization result.
  • the XRM service is associated with multiple terminal devices, and multiple terminal devices may select multiple different PCFs, then the XRM business group associated with NEF may be associated with multiple different PCFs, so NEF Then the characteristic parameters can be sent to the multiple PCF devices.
  • each PCF can perform corresponding authorization, policy and rule decisions or updates, thereby enabling policy and QoS coordination among various PCFs, thereby realizing access and mobility-related requirements among multiple terminal devices associated with the XRM business group.
  • the collaboration provides guarantee for XRM business data flow QoS and transmission strategy collaboration.
  • NEF after NEF receives the XRM service information sent by AF, it can perform information mapping, and determine the characteristic parameters corresponding to the XRM service based on the service information and the contract information corresponding to the XRM service information, and then send the characteristic parameters to PCF, thereby achieving coordination of access and mobility-related requirements among multiple terminal devices associated with the XRM business group, thereby ensuring XRM service data flow QoS and transmission policy coordination.
  • Figure 5 is a schematic flowchart of another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. This method is executed by NEF. As shown in Figure 5, the method may include but is not limited to the following steps:
  • Step 501 Receive a request message sent by the application function AF, where the request message carries XRM service information.
  • Step 502 Determine the core network side mapping information corresponding to the XRM service information.
  • Step 503 Receive a first request sent by the network element device, where the first request includes an XRM service event trigger.
  • the network element device can be at least one of the following: AF, PCF, SMF, AMF.
  • the first request may be a subscription request sent by the network element device to NEF for subscribing to the XRM service event trigger.
  • XRM business event trigger can be XRM service or multimodal data related event trigger, such as Service QoSupdate, UE relocation, PCF change and other triggers.
  • step 503 may be executed after step 502, or may be executed simultaneously with step 502 or step 501, or may be executed before step 501, which is not limited in this disclosure.
  • Step 504 In response to the XRM service event trigger being triggered, report the information corresponding to the XRM service event trigger to the network element device.
  • NEF can trigger the XRM business event trigger based on the XRM business information and corresponding contract information.
  • the XRM business event trigger can also be triggered when the quality of service Qos characteristic parameters or routing changes corresponding to any terminal device associated with the XRM business group identifier are determined.
  • NEF can receive XRM service-related event triggers subscribed by network element devices (consumers), and when the subscribed event triggers are triggered, report relevant information to the consumer, so that the consumer can base on the obtained XRM services information to implement collaborative strategies.
  • NEF can perform information mapping after receiving the XRM service information sent by AF, and after receiving the first request sent by the network element device, when it is determined that the event trigger is triggered, the relevant information can be It is sent to the network element equipment to achieve coordination of access and mobility-related requirements among multiple terminal devices associated with the XRM business group, thereby ensuring XRM business data flow QoS and transmission policy coordination.
  • Figure 6 is a schematic flowchart of an extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. The method is executed by the application function AF. As shown in Figure 6, the method may include but is not limited to the following steps:
  • Step 601 Send a request message to the network opening function NEF, where the request message carries XRM service information.
  • AF can send a request message to NEF by triggering the Nnef_XRM ServiceParameter service.
  • the XRM service information includes at least one of the following: an XRM service identifier, an XRM service group identifier, and specific parameters for AF to provide XRM services or multi-modal data services for XRM service-related terminal devices.
  • the XRM service identifier can be any identification information that can uniquely determine the XRM service.
  • the XRM service group identifier can be used to identify each terminal device related to the XRM service.
  • AF is a specific parameter provided by a terminal device related to the XRM service, and may also be a specific parameter of a multi-modal data service corresponding to the XRM service, which is not limited in this disclosure.
  • AF is the specific parameters of the XRM service or multi-modal data service provided by the one terminal device or multiple terminal devices, which may include the following: At least one item: Service Description, Service Parameters, terminal device identification, terminal device group identification, Subscription to events.
  • Service Description can be used to identify XRMservice or XRM data Service.
  • DNN and S-NSSAI can be identified by a combination of DNN and S-NSSAI (combination of DNN and S-NSSAI), or it can be identified by an XRM identification (ID); or it can be identified by an AFServiceIdentifier or an external application identifier (Application Identifier) )To represent.
  • Service Parameters information about AF guidelines determined by policies and QoS related to XRM business or multi-modal data services. For example, a list of rules that associate XRMservice or multiple data Service application traffic (a list of rules that associate XRMservice or multiple data Service application traffic); terminal device policy (policy) and other parameters; group identifier (GroupID); DNN and S-NSSAI Combination; the selection priority of the corresponding rule, for example: the priority of alternative (Alternative) QoS parameters, the priority of corresponding location (location) or time window (TimeWindow), or the priority of routing selection, etc.
  • policy terminal device policy
  • GroupID group identifier
  • DNN DNN
  • S-NSSAI Combination the selection priority of the corresponding rule, for example: the priority of alternative (Alternative) QoS parameters, the priority of corresponding location (location) or time window (TimeWindow), or the priority of routing selection, etc.
  • Subscription to events is the notifications about the SM policy results that AF needs to subscribe to (The AF may subscribe to notifications about the outcome of the SMpolicy), or the execution and changes of AMpolicy or UEPolicy.
  • the subscription data of multiple terminal devices related to the XRM service can be associated through the XRM service identifier.
  • the data of multiple terminal devices in the XRM business group remains consistent.
  • the service QoS of multiple terminal devices is consistent, and the characteristic parameters of access and data routing are consistent.
  • AF can trigger generation and send a request message after receiving a request from an XRM service-related terminal device; or, it can also automatically trigger and send a request message according to the agreement, and this disclosure does not limit this.
  • AF sends XRM service information to NEF, so that NEF can update UDR information as needed or send XRM service information to PCF, thereby realizing access and mobility between multiple terminal devices associated with the XRM service group.
  • the coordination of related requirements ensures the coordination of XRM business data flow QoS and transmission strategy.
  • Figure 7 is a schematic flowchart of an extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. The method is executed by AF. As shown in Figure 7, the method may include but is not limited to the following steps:
  • Step 701 Send a request message to NEF, where the request message carries XRM service information.
  • AF when AF needs to update and delete corresponding requests, it can also initiate the update and delete process of AF requests by triggering the Nnef_XRM ServiceParameter service.
  • Step 702 Send a first request to NEF, where the first request includes an XRM business event trigger.
  • AF can also send a first request to NEF by triggering the Nnef_XRM ServiceParameter service to subscribe to the required XRM business event trigger.
  • the XRM business event trigger can be XRM service or multimodal data related event trigger, such as Service QoSupdate, UE relocation, PCF change and other triggers.
  • step 702 may be executed after step 701, or may be executed simultaneously with step 701, or may be executed before step 701, which is not limited in this disclosure.
  • Step 703 Receive information corresponding to the XRM business event trigger reported by NEF.
  • AF can obtain corresponding status information statusinformation by receiving NEFreport. Then, the coordination of subsequent QoS rules or terminal device access and routing policies is executed. For example, in the XRMserviceormultimodal data Group, changes in the QoS characteristic parameters or routing traffic of the first terminal device will trigger Eventreport to NEF, and then report to other corresponding terminal devices in the XRMserviceormultimodal data Group, or other Application traffic associated with the same terminal device. PCF or SMF, so that PCF or SMF performs corresponding session update (SessionUpdate), or network function reselection (NFreselection).
  • SessionUpdate session update
  • NFreselection network function reselection
  • UDR is a network-wide data center
  • NEF determines the characteristic parameters of the XRM service
  • it can store the parameters in UDR, so that AF can also subscribe to the request, wherein the second request includes an XRM business event trigger, and then receives information corresponding to the XRM business event trigger reported by the UDR.
  • AF sends XRM business information to NEF and subscribes to XRM business-related event triggers from NEF to obtain the information corresponding to the XRM business event trigger sent by NEF when the XRM business-related event trigger is triggered. , thereby achieving coordination of access and mobility-related requirements among multiple terminal devices associated with the XRM business group, thereby ensuring XRM service data flow QoS and transmission strategy coordination.
  • Figure 8 is a schematic flowchart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. The method is executed by PCF. As shown in Figure 8, the method may include but is not limited to the following steps:
  • Step 801 Receive XRM service information associated with the terminal device.
  • the PCF can receive the XRM service information sent by the NEF, or can also obtain the XRM service information reported by the UDR, which is not limited by this disclosure.
  • the PCF is a PCF related to the AM associated with the terminal device, that is, a PCF used to provide decision-making services for access management of the terminal device.
  • the XRM service information includes at least one of the following: an XRM service identifier, an XRM service group identifier, and specific parameters for AF to provide XRM services or multi-modal data services for XRM service-related terminal devices.
  • the XRM service identifier can be any identification information that can uniquely determine the XRM service.
  • the XRM service group identifier can be used to identify each terminal device related to the XRM service.
  • AF is a specific parameter provided by a terminal device related to the XRM service, and may also be a specific parameter of a multi-modal data service corresponding to the XRM service, which is not limited in this disclosure.
  • AF is the specific parameters of the XRM service or multi-modal data service provided by the one terminal device or multiple terminal devices, which may include the following: At least one item: Service Description, Service Parameters, terminal device identification, terminal device group identification, Subscription to events.
  • Service Description can be used to identify XRMservice or XRM data Service.
  • DNN and S-NSSAI can be identified by a combination of DNN and S-NSSAI (combination of DNN and S-NSSAI), or it can be identified by an XRM identification (ID); or it can be identified by an AFServiceIdentifier or an external application identifier (Application Identifier) )To represent.
  • Service Parameters information about AF guidelines determined by policies and QoS related to XRM business or multi-modal data services. For example, a list of rules that associate XRMservice or multiple data Service application traffic (a list of rules that associate XRMservice or multiple data Service application traffic); terminal device policy (policy) and other parameters; group identifier (GroupID); DNN and S-NSSAI Combination; the selection priority of the corresponding rule, for example: the priority of alternative (Alternative) QoS parameters, the priority of corresponding location (location) or time window (TimeWindow), or the priority of routing selection, etc.
  • policy terminal device policy
  • GroupID group identifier
  • DNN DNN
  • S-NSSAI Combination the selection priority of the corresponding rule, for example: the priority of alternative (Alternative) QoS parameters, the priority of corresponding location (location) or time window (TimeWindow), or the priority of routing selection, etc.
  • Subscription to events is the notifications about the SM policy results that AF needs to subscribe to (The AF may subscribe to notifications about the outcome of the SMpolicy), or the execution and changes of AMpolicy or UE Policy.
  • the subscription data of multiple terminal devices related to the XRM service can be associated through the XRM service identifier.
  • the data of multiple terminal devices in the XRM business group remains consistent.
  • the service QoS of multiple terminal devices is consistent, and the characteristic parameters of access and data routing are consistent.
  • Step 802 Generate quality of service Qos rules and/or terminal device access and routing policies based on the XRM service information.
  • Step 803 Send the Qos rules and/or terminal device access and routing policies to the terminal device.
  • PCF after PCF obtains the XRM business information, it can perform corresponding authorization, measurement and rule decisions and updates based on this information, and send the newly generated Qos rules, and terminal device access and routing policies to Afterwards, the terminal device can perform access and communication transmission based on the newly received Qos rules and terminal device access and routing policies. Since the Qos rules received by each terminal device supporting the XRM service, as well as the access and routing policies of the terminal device, are generated by the corresponding PCF based on the XRM service information, thus realizing the coordination of access and mobility between the terminal devices.
  • the PCF may also send the execution result to the AF through NEF when it is determined that the AF has subscribed to the XRM business-related policy execution result notification.
  • PCF after PCF obtains the XRM business information, it can perform corresponding authorization, measurement and rule decisions and updates based on this information, and send the newly generated Qos rules and/or terminal device access and routing policies.
  • the terminal equipment associated with the XRM business can realize the coordination of QoS rules and/or terminal equipment access and routing strategies, which provides a guarantee for the realization of XRM business data flow QoS and transmission strategy coordination.
  • Figure 9 is a schematic flowchart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. The method is executed by PCF. As shown in Figure 9, the method may include but is not limited to the following steps:
  • Step 901 Send a first request to NEF, where the first request includes an XRM business event trigger.
  • the XRM business event trigger can be XRM service or multimodal data related event trigger, such as Service QoSupdate, UE relocation, PCF change and other triggers.
  • NEF can determine the characteristic parameters of the XRM business based on the XRM business information and corresponding contract information, so PCF can subscribe to the XRF service event trigger from NEF. To obtain XRM business information.
  • Step 902 Receive information corresponding to the XRM business event trigger reported by NEF.
  • Step 903 Generate service quality Qos rules and/or terminal device access and routing policies based on the information corresponding to the XRM business event trigger.
  • Step 904 Send Qos rules and/or terminal device access and routing policies to the terminal device.
  • PCF can obtain XRM business information by subscribing to the And/or the terminal device access and routing policies are sent to the terminal devices, so that the terminal devices associated with the Strategic coordination provides guarantee.
  • Figure 10 is a schematic flowchart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. The method is executed by PCF. As shown in Figure 10, the method may include but is not limited to the following steps:
  • Step 1001 Send a second request to the UDR, where the second request includes an XRM business event trigger.
  • UDR is a network-wide data center
  • NEF determines the characteristic parameters of the XRM service
  • it can store the parameters in UDR, so that PCF can subscribe to XRM service event triggers from UDR to obtain XRM service information.
  • Step 1002 Receive information corresponding to the XRM business event trigger reported by the UDR.
  • Step 1003 Generate service quality Qos rules and/or terminal device access and routing policies based on the information corresponding to the XRM business event trigger.
  • Step 1004 Send Qos rules and/or terminal device access and routing policies to the terminal device.
  • steps 1001-1004 please refer to the detailed description of any embodiment of the present disclosure, and will not be described again here.
  • PCF can obtain XRM business information by subscribing to the And/or the terminal device access and routing policies are sent to the terminal devices, so that the terminal devices associated with the Strategic coordination provides guarantee.
  • Figure 11 is a schematic flowchart of yet another extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. The method is executed by PCF. As shown in Figure 11, the method may include but is not limited to the following steps:
  • Step 1101 Receive a terminal device subscription information change notification sent by the unified data register UDR, where the change notification carries the XRM service information.
  • UDR can determine the change of the subscription information of the terminal device, so that PCF You can receive the notification of change of terminal equipment contract information sent by UDR.
  • Step 1102 Generate service quality Qos rules and/or terminal device access and routing policies based on the XRM service information.
  • Step 1103 Send Qos rules and/or terminal device access and routing policies to the terminal device. .
  • the PCF can send the relevant policies to the terminal device, so that the terminal device can obtain the Qos rules and/or the terminal device based on the acquired Qos rules and/or terminal device. Access and routing policies are communicated.
  • the changed parameters are stored in the UDR.
  • the PCF can also send the execution result to the AF through NEF when it is determined that the AF has subscribed to the XRM business-related policy execution result notification.
  • PCF when PCF receives the notification of change of terminal equipment subscription information sent by UDR, it can perform corresponding authorization, measurement and rule decision-making and updating based on XRM business information, and transfer the newly generated Qos rules and/or terminal equipment to The access and routing policies are sent to the terminal devices, so that the terminal devices associated with the .
  • Figure 11a is a schematic flowchart of an extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. As shown in Figure 11a, the method may include but is not limited to the following steps:
  • Step 1104 Receive quality of service Qos rules and/or terminal device access and routing policies sent by the policy control function PCF device.
  • the quality of service Qos rules and/or terminal device access and routing policies are generated by PCF based on XRM business information.
  • Step 1105 Execute Qos rules and/or terminal device access and routing policies.
  • the PCF associated with the AM session selected by the terminal device when registering to the network determines the Qos rules and/or terminal device access and routing policies based on the XRM service information, and then the Qos rules and/or Or terminal device access and routing policies are sent to the terminal device. Afterwards, the terminal device can perform access and communication transmission based on the newly received Qos rules and terminal device access and routing policies. Since the Qos rules and terminal device access and routing policies received by each terminal device supporting the XRM service are all generated by the corresponding PCF based on the XRM service information, thus realizing the coordination of access and mobility between terminal devices.
  • the terminal device after the terminal device receives the Qos rules and/or the terminal device access and routing policies generated based on the XRM service information, it can perform access and routing based on the Qos rules and/or the terminal device access and routing policies. Communication transmission, thereby realizing the coordination of QoS rules and/or terminal device access and routing strategies between terminal devices associated with the XRM service, and providing guarantee for the realization of XRM service data flow QoS and transmission strategy coordination.
  • Figure 12 is an interactive schematic diagram of an extended reality multimedia XRM service processing method provided by an embodiment of the present disclosure. As shown in Figure 12, the method may include but is not limited to the following steps:
  • Step 1201 The terminal device registers with the network, selects the corresponding PCF, and completes AMsession association.
  • the terminal device may be one terminal device related to XRM business or multi-modal data service, or multiple terminal devices. It is understandable that multiple terminal devices can be selected separately
  • Step 1202 PCF subscribes to UDM for change notifications on XRM business or multi-modal data service-related contract information based on the XRM business policy and QoS requirements.
  • steps 1201 and 1202 do not have to be in strict sequence with the following steps. That is, the above-mentioned steps 1201 and 1202 can be executed before the following steps, or can be executed in parallel with the following steps. Alternatively, it can also be performed after each of the following steps, and this disclosure does not limit this.
  • Step 1203 AF creates a request, where the request contains the XRM business identifier and/or the XRM business group identifier.
  • Step 1204 AF sends Nnef XRM ServiceParameter request message to NEF.
  • AF can also send Nnef XRM ServiceParameter update message to NEF, or AF can also send Nnef XRM ServiceParameter deletion message to NEF.
  • Step 1205 NEF stores the XRM business information in UDR.
  • NEF can also update the XRM business information in the UDR, or remove the XRM business information in the UDR.
  • Step 1206 NEF returns a create request response message to AF.
  • Step 1207 PCF receives the contract information change notification from UDR.
  • Step 1208 The PCF transmits the terminal device policy to the terminal device.
  • Step 1209 PCF sends an event opening notification to NEF.
  • PCF can send notifications to NEF through the service interface Npcf provided by PCF, such as sending Npcf event exposure notify.
  • Step 1210 After receiving the notification, NEF first performs mapping of internal and external related parameters.
  • Step 1211 Report the mapped relevant parameters to AF.
  • FIG. 13 is a schematic structural diagram of a communication device 1300 provided by an embodiment of the present disclosure.
  • the communication device 1300 shown in FIG. 13 may include a transceiver module 1301 and a processing module 1302.
  • the transceiving module 1301 may include a sending module and/or a receiving module.
  • the sending module is used to implement the sending function
  • the receiving module is used to implement the receiving function.
  • the transceiving module 1301 may implement the sending function and/or the receiving function.
  • the communication device 1300 may be a network open function NEF, a device in the network open function NEF, or a device that can be used in conjunction with the network open function NEF.
  • the communication device 1300 is on the Network Open Function NEF side, where:
  • the transceiver module 1301 is configured to receive a request message sent by the application function AF, where the request message carries XRM service information.
  • the processing module 1302 is configured to update the XRM information in the unified data register UDR according to the contract information corresponding to the XRM service information and the XRM service information.
  • the XRM business information includes at least one of the following:
  • the AF provides specific parameters of the XRM service or multi-modal data service for the terminal device related to the XRM service.
  • the XRM service group identifier is used to identify each terminal device related to the XRM service.
  • the specific parameters include at least one of the following:
  • Service description Service parameters, terminal device identification, terminal device group identification, subscription events.
  • processing module 1302 is also used to:
  • processing module 1302 is specifically used for:
  • the XRM service group identifier in the CN corresponding to the XRM service group identifier is determined.
  • NEF can obtain the contract information corresponding to the XRM business from UDM.
  • processing module 1302 is also used to:
  • processing module 1302 is also configured to store the characteristic parameters corresponding to the XRM service into the unified data register UDR; and/or,
  • the transceiver module 1301 is also used to send the characteristic parameters corresponding to the XRM service to the policy control function PCF device.
  • the XRM service is associated with multiple terminal devices, and the transceiver module 1301 is also used to:
  • the characteristic parameter is sent to the PCF device corresponding to each terminal device in the plurality of terminal devices.
  • the subscription data of the plurality of terminal devices are associated through the XRM service identifier and/or the XRM service group identifier.
  • the transceiver module 1301 is also used to:
  • the network element device In response to the XRM service event trigger being triggered, report information corresponding to the XRM service event trigger to the network element device, where the network element device is at least one of the following: AF, PCF, SMF, AMF .
  • NEF after NEF receives the XRM service information sent by AF, it can update the XRM information in the UDR based on the service information and the contract information corresponding to the XRM service information for PCF or RAN execution, thus realizing the XRM business group
  • NEF after NEF receives the XRM service information sent by AF, it can update the XRM information in the UDR based on the service information and the contract information corresponding to the XRM service information for PCF or RAN execution, thus realizing the XRM business group
  • the corresponding coordination of access and mobility-related requirements among multiple terminal devices ensures XRM business data flow QoS and transmission strategy coordination.
  • the communication device 1300 may also be an application function AF, a device in the application function AF, or a device that can be used in conjunction with the application function AF.
  • the communication device 1300 is on the application function AF side, where:
  • the transceiver module 1301 is configured to send a request message to the network opening function NEF, where the request message carries XRM service information.
  • the XRM business information includes at least one of the following:
  • the AF provides specific parameters of the XRM service for the terminal equipment related to the XRM service.
  • the XRM service group identifier is used to identify each terminal device related to the XRM service.
  • the specific parameters include at least one of the following:
  • Service description Service parameters, terminal device identification, terminal device group identification, subscription events.
  • the transceiver module 1301 is also used to:
  • the transceiver module 1301 is also used to:
  • AF sends XRM service information to NEF, so that NEF can update UDR information as needed or send XRM service information to PCF, thereby realizing access and mobility between multiple terminal devices associated with the XRM service group.
  • the coordination of related requirements ensures the coordination of XRM business data flow QoS and transmission strategy.
  • the communication device 1300 may be a policy control function PCF device, or may be a device in the policy control function PCF device, or may be a device that can be used in conjunction with the policy control function PCF device.
  • the transceiver module 1301 is used to receive XRM service information associated with the terminal device.
  • the processing module 1302 is configured to execute quality of service Qos rules and/or coordination of terminal device access and routing policies according to the XRM service information.
  • the transceiver module 1301 is also used to:
  • the transceiver module 1301 is also used to:
  • the transceiver module 1301 is specifically used for:
  • the transceiver module 1301 is also used to:
  • processing module 1302 is also used to:
  • the changed parameters are stored in the UDR.
  • the transceiver module 1301 is also used to:
  • the execution result is sent to the AF through NEF.
  • PCF after PCF obtains the XRM business information, it can perform corresponding authorization, measurement and rule decisions and updates based on this information, and send the newly generated Qos rules and/or terminal device access and routing policies.
  • the terminal equipment associated with the XRM business can realize the coordination of QoS rules and/or terminal equipment access and routing strategies, which provides a guarantee for the realization of XRM business data flow QoS and transmission strategy coordination.
  • the communication device 1300 may also be a terminal device, a device in the terminal device, or a device that can be used in conjunction with the terminal device.
  • the communication device 1300 is in the terminal device, where:
  • the transceiver module is used to receive the quality of service Qos rules and/or terminal device access and routing policies sent by the policy control function PCF device.
  • Processing module for executing Qos rules and/or terminal device access and routing policies.
  • the terminal device after the terminal device receives the Qos rules and/or the terminal device access and routing policies generated based on the XRM service information, it can perform access and routing based on the Qos rules and/or the terminal device access and routing policies. Communication transmission, thereby realizing the coordination of QoS rules and/or terminal device access and routing strategies between terminal devices associated with the XRM service, and providing guarantee for the realization of XRM service data flow QoS and transmission strategy coordination.
  • FIG 14 is a schematic structural diagram of another communication device 1400 provided by an embodiment of the present disclosure.
  • the communication device 1400 may be a network open function NEF, an application function AF, a policy control function PCF device, a terminal device, or a chip, a chip system, or a chip that supports the network open function NEF to implement the above method.
  • the processor, etc. may also be a chip, chip system, or processor, etc., that supports the application function AF to implement the above method, or may be a chip, chip system, or processor, etc., that supports the policy control function PCF device to implement the above method.
  • the device can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • Communication device 1400 may include one or more processors 1401.
  • the processor 1401 may be a general-purpose processor or a special-purpose processor, or the like.
  • it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data.
  • the central processor can be used to control communication devices (such as base stations, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.) and execute computer programs. , processing data for computer programs.
  • the communication device 1400 may also include one or more memories 1402, on which a computer program 1404 may be stored.
  • the processor 1401 executes the computer program 1404, so that the communication device 1400 performs the steps described in the above method embodiments. method.
  • the memory 1402 may also store data.
  • the communication device 1400 and the memory 1402 can be provided separately or integrated together.
  • the communication device 1400 may also include a transceiver 1405 and an antenna 1406.
  • the transceiver 1405 may be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions.
  • the transceiver 1405 may include a receiver and a transmitter.
  • the receiver may be called a receiver or a receiving circuit, etc., used to implement the receiving function;
  • the transmitter may be called a transmitter, a transmitting circuit, etc., used to implement the transmitting function.
  • the communication device 1400 may also include one or more interface circuits 1407.
  • the interface circuit 1407 is used to receive code instructions and transmit them to the processor 1401 .
  • the processor 1401 executes the code instructions to cause the communication device 1400 to perform the method described in the above method embodiment.
  • the communication device 1400 is a network open function NEF: the transceiver 1405 is used to perform step 201 in Figure 2; step 301 in Figure 3; step 401, step 404 in Figure 4; step 501, step 503, step 5 in Figure 5 504 etc.
  • the processor 1401 is used to execute step 202 in Figure 2; step 302, step 303, step 304 in Figure 3; step 402, step 403 in Figure 4; step 502 in Figure 5, etc.
  • the communication device 1400 is the application function AF: the transceiver 1405 is used to perform step 601 in Figure 6; step 701, step 702, step 703, etc. in Figure 7.
  • the communication device 1400 is a policy control function PCF device: the transceiver 1405 is used to perform steps 801, 803 in Figure 8; steps 901, 902, and 904 in Figure 9; steps 1001, 1002, and steps in Figure 10 1004; Step 1101, Step 1103, etc. in Figure 11.
  • the processor 1401 is used to execute step 802 in Figure 8; step 903 in Figure 9; step 1003 in Figure 10; step 1102 in Figure 11, etc.
  • the communication device 1400 is a terminal device: the transceiver 1405 is used to perform steps 1104 and so on in Figure 11a.
  • the processor 1401 is used to perform steps 1105 and so on in Figure 11a.
  • the processor 1401 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuits, interfaces or interface circuits used to implement the receiving and transmitting functions can be separate or integrated together.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.
  • the processor 1401 may store a computer program 1403, and the computer program 1403 runs on the processor 1401, causing the communication device 1400 to perform the method described in the above method embodiment.
  • the computer program 1403 may be solidified in the processor 1401, in which case the processor 1401 may be implemented by hardware.
  • the communication device 1400 may include a circuit, which may implement the functions of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this disclosure may be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), n-type metal oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS n-type metal oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiments may be a network device or an access network device (such as the terminal device in the foregoing method embodiment), but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may Not limited by Figure 14.
  • the communication device may be a stand-alone device or may be part of a larger device.
  • the communication device may be:
  • the IC collection may also include storage components for storing data and computer programs;
  • the communication device may be a chip or a chip system
  • the schematic structural diagram of the chip shown in FIG. 15 refer to the schematic structural diagram of the chip shown in FIG. 15 .
  • the chip shown in Figure 15 includes a processor 1501 and an interface 1502.
  • the number of processors 1501 may be one or more, and the number of interfaces 1502 may be multiple.
  • the interface 1502 is used to execute step 201 in Figure 2; step 301 in Figure 3; step 401, step 404 in Figure 4; step 501, step 503, step 504 in Figure 5, etc.
  • Interface 1502 is used to execute step 601 in Figure 6; step 701, step 702, step 703, etc. in Figure 7.
  • Interface 1502 used to execute step 801 and step 803 in Figure 8; step 901, step 902 and step 904 in Figure 9; step 1001, step 1002 and step 1004 in Figure 10; step 1101 and step 11 in Figure 11 1103 etc.
  • Interface 1502 used to perform steps 1104 and so on in Figure 11a.
  • the chip also includes a memory 1503, which is used to store necessary computer programs and data.
  • Embodiments of the present disclosure also provide a processing system for extended reality multimedia XRM services.
  • the system includes a communication device as a network opening function NEF in the embodiment of FIG. 13, and a communication device as an application function AF, or as a policy control function PCF.
  • the communication device of the device, or the system includes the communication device as the network opening function NEF in the aforementioned embodiment of Figure 14, the communication device as the application function AF, and the communication device as the policy control function PCF device.
  • the present disclosure also provides a readable storage medium on which instructions are stored, and when the instructions are executed by a computer, the functions of any of the above method embodiments are implemented.
  • the present disclosure also provides a computer program product, which, when executed by a computer, implements the functions of any of the above method embodiments.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs.
  • the computer program When the computer program is loaded and executed on a computer, the processes or functions described in accordance with the embodiments of the present disclosure are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program may be stored in or transferred from one computer-readable storage medium to another, for example, the computer program may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the usable media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • At least one in the present disclosure can also be described as one or more, and the plurality can be two, three, four or more, and the present disclosure is not limited.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D” etc.
  • the technical features described in “first”, “second”, “third”, “A”, “B”, “C” and “D” are in no particular order or order.
  • each table in this disclosure can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which is not limited by this disclosure.
  • it is not necessarily required to configure all the correspondences shown in each table.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables may also be other names understandable by the communication device, and the values or expressions of the parameters may also be other values or expressions understandable by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables. wait.
  • Predefinition in this disclosure may be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-burning.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例公开了一种扩展现实多媒体XRM业务的处理方法及其装置，可应用于通信技术领域，其中，由网络开放功能NEF执行的方法包括：接收应用功能AF发送的请求消息，其中，所述请求消息中携带XRM业务信息；根据所述XRM业务信息对应的签约信息及所述XRM业务信息，更新统一数据寄存器UDR中所述XRM的信息由此，NEF收到AF发送的XRM业务信息后，即可根据该服务信息及XRM业务信息对应的签约信息，更新UDR中XRM的信息，以供PCF或RAN执行，从而实现了XRM业务组对应的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。

Description

一种扩展现实多媒体XRM业务的处理方法及其装置 技术领域
本公开涉及通信技术领域，尤其涉及一种扩展现实多媒体XRM业务的处理方法及其装置。
背景技术
扩展现实多媒体(extended realityMultimedia，XRM)业务，比如，虚拟现实(virtual reality，VR)、增强现实(Augmented reality)等XR业务，基于视频的机器或无人机远程控制等业务，都会涉及多模态数据流。多模态数据中的各数据流往往具有一定甚至很强的相关性，比如音频和视频流的同步，触觉和视觉的同步等。这类媒体业务的数据流本身，各数据流之间，以及这些业务数据流对网络传输的需求，都存在一些共性特征，这些特性的有效识别和利用将更有助于网络和业务的传输、控制，也更有助于业务保障和用户体验。
XRM业务需要第五代移动通信技术系统(5th Generation Mobile Communication Technology system，5GS)综合考虑业务的相关数据流服务质量(QualityofService，QoS)特性，例如延迟临界delaycritical、保障比特速率(Guaranteed BitRate，GBR)，保障流比特速率(Guaranteed flow Bit Rate，GFBR)，包延迟预算(PacketDelayBudget，PDB)，默认最大数据突发量(DefaultMaximumDataBurstVolume，MDBV))等参数是否能同时满足并协同一致，尤其是涉及多个终端设备的XRM业务，多个终端设备之间的QoS授权与执行的一致性保障。
对于XRM业务的多终端设备而言，接入和移动性相关需求的管理和协同，是保障XRM业务数据流QoS和传输策略协同的前提。
发明内容
本公开实施例提供一种扩展现实多媒体XRM业务的处理方法及其装置，可应用于通信技术领域中。
第一方面，本公开实施例提供一种扩展现实多媒体XRM业务的处理方法，该方法由网络开放功能NEF执行，该方法包括：接收应用功能AF发送的请求消息，其中，所述请求消息中携带XRM业务信息；根据所述XRM业务信息对应的签约信息及所述XRM业务信息，更新统一数据寄存器UDR中所述XRM的信息。
本公开中，NEF收到AF发送的XRM业务信息后，即可根据该服务信息及XRM业务信息对应的签约信息，更新UDR中XRM的信息，以供PCF或RAN执行，从而实现了XRM业务组对应的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
第二方面，本公开实施例提供另一种扩展现实多媒体XRM业务的处理方法，方法由应用功能AF执行，方法包括：向网络开放功能NEF发送请求消息，其中，所述请求消息中携带XRM业务信息。
本公开中，AF通过将XRM业务信息发送给NEF，使得NEF可以根据需要更新UDR信息或将XRM业务信息发送给PCF，从而实现该XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
第三方面，本公开实施例提供另一种扩展现实多媒体XRM业务的处理方法，方法由策略控制功能PCF设备执行，方法包括：接收终端设备关联的XRM业务信息；根据所述XRM业务信息，生成服务质量Qos规则和/或终端设备接入和路由策略；将所述Qos规则和/或终端设备接入和路由策略发送给所述终端设备。
本公开中，PCF在获取到XRM业务信息后，即可根据该信息，执行相应授权、以及测量和规则的决策和更新，并将生成的Qos规则和/或终端设备接入和路由策略发送给终端设备，从而使得XRM业务关联的终端设备间可以实现Qos规则和/或终端设备接入和路由策略的协同，为实现XRM业务数据流QoS和传输策略协同提供了保障。
第四方面，本公开实施例提供另一种扩展现实多媒体XRM业务的处理方法，方法由终端设备执行，方法包括：接收策略控制功能PCF设备发送的服务质量Qos规则和/或终端设备接入和路由策略，其中，所述Qos规则和/或终端设备接入和路由策略为基于XRM业务信息生成的；执行所述Qos规则和/或终端设备接入和路由策略。
本公开中，终端设备在接收到基于XRM业务信息生成的Qos规则和/或终端设备接入和路由策略后，即可基于该Qos规则和/或终端设备接入和路由策略，进行接入及通信传输，从而实现了与该XRM业务关联的各终端设备间的Qos规则和/或终端设备接入和路由策略的协同，为实现XRM业务数据流QoS和传输策略协同提供了保障。
第五方面，本公开实施例提供一种通信装置，配置在网络开放功能NEF侧，包括：
收发模块，用于接收应用功能AF发送的请求消息，其中，所述请求消息中携带XRM业务信息；
处理模块，用于根据所述XRM业务信息对应的签约信息及所述XRM业务信息，更新统一数据寄存器UDR中所述XRM的信息。
第六方面，本公开实施例提供一种通信装置，配置在应用功能AF侧，包括：
收发模块，用于向网络开放功能NEF发送请求消息，其中，所述请求消息中携带XRM业务信息。
第七方面，本公开实施例提供一种通信装置，配置在策略控制功能PCF设备侧，包括：
收发模块，用于接收终端设备关联的XRM业务信息；
处理模块，用于根据所述XRM业务信息，生成服务质量Qos规则和/或终端设备接入和路由策略；
收发模块，还用于将Qos规则和/或终端设备接入和路由策略发送给终端设备。
第八方面，本公开实施例提供一种通信装置，配置在终端设备侧，包括：
收发模块，用于接收策略控制功能PCF设备发送的服务质量Qos规则和/或终端设备接入和路由策略；
处理模块，用于执行Qos规则和/或终端设备接入和路由策略。
第九方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该通信装置执行上述第一方面所述的方法，或者执行上述第二方面所述的方法，或者执行上述第三方面所述的方法，或执行上述第四方面所述的方法。
第十方面，本公开实施例提供一种扩展现实多媒体XRM业务的处理系统，该系统包括第四方面所述的通信装置、第五方面所述的通信装置、第六方面所述的通信装置、或者第七方面所述的通信装置。
第十一方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述网络开放功能NEF执行上述第一方面所述的方法，或者使所述应用功能AF执行上述第二方面所述的方法，或者使所述策略控制功能PCF设备执行上述第三方面所述的方法，或者使所述终端设备执行上述第四方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1是本公开实施例提供的一种通信系统的架构示意图；
图2是本公开实施例提供的一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图3是本公开实施例提供的另一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图4是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图5是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图6是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图7是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图8是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图9是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图10是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图11是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图11a是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图；
图12是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的交互示意图；
图13是本公开实施例提供的一种通信装置的结构示意图；
图14是本公开实施例提供的另一种通信装置的结构示意图；
图15是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
为了便于理解，首先介绍本公开涉及的术语。
1、接入与移动性管理功能(access and mobility management function，AMF)
AMF为核心网侧的逻辑节点功能网元，其是终端和无线的核心网控制面接入点，从用户设备接收所 有连接和会话相关信息，并执行注册、连接、可达性、移动性管理。此外，AMF为终端设备和会话管理功能(session management function，SMF)设备提供会话管理消息传输通道，为用户接入时提供认证、鉴权功能。
2、无线接入网(radio access network，RAN)
RAN是无线接入技术的实现。它存在于一个设备(例如，一个移动电话，一个计算机，或任何被远程控制的机器)与核心网(Core Network，CN)之间，提供两者间的通信连接。
3、策略控制功能(policy control function，PCF)
PCF，为核心网侧的另一功能网元，其可以支持统一的策略框架去管理网络行为，提供策略规则给网络实体去实施执行，访问统一数据寄存器(unified data repository，UDR)的订阅信息。
4、网络开放功能(network exposure function，NEF)
NEF，为核心网侧的又一功能网元。3gpp的网元都是通过NEF将其能力开放给其它网元的。NEF将相关信息存储到统一数据寄存器(unified data repository，UDR)中、也可以从UDR获取相关的信息，NEF只能访问和其相同公共陆地移动网络(Public land mobile network，PLMN)的UDR。NEF提供相应的安全保障来保证外部应用到3gpp网络的安全，3gpp内部和外部相关信息的转换，例如应用功能(application function,AF)服务标识ServiceIdentifier和5G核心网内部的数据网络名(data network name，DNN,)、网络切片选择支持信息(network slice selection assistance information，S-NSSAI)等的转换，尤其是网络和用户敏感信息一定要对外部网元隐藏掉；NEF可以通过访问NDR获取到其它网元的相关信息，NEF只能访问和其相同PLMN的UDR。
5、统一数据寄存器(unified data repository，UDR)
UDR为核心网侧的又一功能网元，其可以用于统一数据管理(unified data management，UDM)存储订阅数据或读取订阅数据；PCF存储策略数据或者读取策略数据；存储开放的数据或者从中读取开放的数据；UDR和访问其的网络功能(network function，NF)具有相同的PLMN，也就是同一个网络下，也即，UDR提供的服务化接口(Nudr)是一个PLMN内部接口。
6、应用功能(application function，AF)
AF为核心网侧的又一功能网元，其可以与3GPP核心网络交互以提供服务，支持以下功能：应用侧对业务流路由的影响；访问网络开放功能；与策略框架交换用于策略控制；根据运营商的部署，运营商信任的应用功能可以直接与相关的网络功能交互。对于运营商不允许直接访问网络功能的应用功能，应通过NEF使用外部能力开放架构(NEF)与相关的网络功能进行交互。
请参见图1，图1为本公开实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个网络设备和一个终端设备，图1所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络设备，两个或两个以上的终端设备。图1所示的通信系统以包括一个接入网设备11、一个终端设备12、一个核心网设备13。
需要说明的是，本公开实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。
本公开实施例中的接入网设备11是网络侧的一种用于发射或接收信号的实体。例如，接入网设备11可以为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本公开的实施例对接入网设备所采用的具体技术和具体设备形态不做限定。本公开实施例提供的接入网设备11可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将网络设备，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本公开实施例中的终端设备12是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
本公开中，XRM业务需要5GS系统综合考虑业务的相关数据流QoS特性，例如数据流，GFBR，PDB，MDBV等参数是否能同时满足并协同一致，尤其是涉及多个终端设备的XRM业务，多个终端设备之间的QoS授权与执行的一致性保障。
XRM业务的多个终端设备之间，对于接入和移动性相关需求的管理和协同，是保障XRM业务数据流QoS和传输策略协同的前提。例如多终端设备间AMF提供给RAN的无线接入类型索引(index to radio access type),和/或，频率选择优先级(Frequency Selection Priority，RFSP)索引Index的一致性和变更协同，服务区域限制(service area restrictions)如何协同。PCF可基于运营商策略或授权跟踪区域标识(tracking area ID,TAI)的变化随时修改service area restrictions，保障实时协同,不产生冲突。
本发明，为了实现上述目的，增强了NEF的功能，支持从AF提供XRMservice相关应用请求(Applicationrequirements)，比如，用于XRM业务的一个终端设备或多个终端设备的服务特定参数(service specific parameters)；XRM数据流的QoS策略决定(policydecision)，和或策略协作(policy coordination)；支持AF对XRMservice相关终端设备的XRM数据流的QoS策略传输结果(deliveryresult)或QoS变更(change)的订阅和上报；供PCF执行XRMservice组终端设备相应多PCF间的policyandQoScoordination。这样可支持网络中使用分组数据单元会活(withpacket dataunitsession)的多个终端设备XRMservice需求，尤其可实现XRMservice Group终端设备相应的多PCF间的policyandQoScoordination。
由于XRM业务对应的数据流通常为多模态数据流，因此，本公开中的XRM业务，也可以称为多模态数据流业务，或多模态数据流服务等，本公开对此不做限定。
下面结合附图对本公开所提供的一种扩展现实多媒体XRM业务的处理方法及其装置进行详细地介绍。本公开以下各实施例中，均假设XRM业务或者多模态数据服务相关的部分或全部终端设备，已经注册的网络，并选择了PCF，完成了接入管理AM会话session关联。其中，该PCF可以根据XRM业务的策略和QoS需求，向UDM请求XRM业务或多模态数据服务相关的签约信息的变更通知。
请参见图2，图2是本公开实施例提供的一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由NEF执行。如图2所示，该方法可以包括但不限于如下步骤：
步骤201，接收应用功能AF发送的请求消息，其中，请求消息中携带XRM业务信息。
可选的，NEF可以通过NEF提供的服务化接口Nnef_XRM ServiceParameter service，接收AF发送的请求消息。
可选的，XRM业务信息包括以下至少一项：XRM业务标识，XRM业务组标识，及AF为XRM业务相关的终端设备提供XRM业务或多模态数据服务的特定参数。
其中，XRM业务标识，可以为任一可唯一确定该XRM业务的标识信息。XRM业务组标识可以用于标识与该XRM业务相关的各个终端设备。
可选的，AF为XRM业务相关的终端设备提供的特定参数，还可以为与XRM业务对应的多模态数据服务的特定参数，本公开对此不做限定。
可选的，该XRM业务相关的终端设备可能为一个，也可能为多个，AF为该一个终端设备或多个终端设备提供的XRM业务或多模态数据服务的特定参数，可以包括以下以下至少一项：服务描述(Service Description)，服务参数(Service Parameters)，终端设备标识，终端设备组标识，订阅事件(Subscription to events)。
其中，Service Description，可以用来标识XRMserviceorXRM data Service。
其可以用DNN和S-NSSAI的组合(combination of DNN和S-NSSAI)，或者，可以用XRM标识(identification，ID)来标识；或者，用AF服务标识(AFServiceIdentifier)或外部应用标识(Application Identifier)来表示。
Service Parameters，为有关XRM业务或多模态数据服务相关政策和QoS确定的AF指南的信息。例如，XRM业务或多个数据服务相关的应用路由的规则列表(a list of rules that associate XRMserviceormultiple data Service application traffic)；终端设备策略(policy)等参数；组标识(GroupID)；DNN和S-NSSAI组合；相应规则的选择优先级，例如：可供替代的(Alternative)QoS参数优先级，相应位置(location)或时间窗口(TimeWindow)优先级，或路由选择优先级等。
Subscription to events，为AF需要订阅的有关SM策略结果的通知(The AF may subscribe to notifications about the outcome of the SMpolicy)，或AMpolicy或UE Policy的执行和变更。
可选的，XRM业务相关的多个终端设备的签约数据可以通过XRM业务标识关联。其中，XRM业务组中的多个终端设备的数据保持一致，比如，多个终端设备的业务QoS一致，接入和数据路由的特性参数一致。
步骤202，根据XRM业务信息对应的签约信息及所述XRM业务信息，更新统一数据寄存器UDR中所述XRM的信息。
本公开中，NEF收到AF发送的请求消息后，可以根据XRM业务信息，确认是否授权该请求。若确认授权，则可以根据该XRM业务信息对应的签约信息及XRM业务信息，更新UDR中该XRM对应的信息，比如，更新该XRM的特性参数，从而供RAN或PCF执行，以实现XRM业务组对应的多个终端设备分别对应的多个PCF间的策略和QoS协同，从而实现该XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
本公开中，NEF收到AF发送的XRM业务信息后，即可根据该服务信息及XRM业务信息对应的签约信息，更新UDR中XRM的信息，以供PCF或RAN执行，从而实现了XRM业务组对应的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
请参见图3，图3是本公开实施例提供的一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由NEF执行。如图3所示，该方法可以包括但不限于如下步骤：
步骤301，接收应用功能AF发送的请求消息，其中，请求消息中携带XRM业务信息。
其中，上述步骤301的具体实现，可以参照本公开任一实施例的详细描述，此处不再赘述。
步骤302，确定与XRM业务信息对应的核心网侧映射信息。
可选的，NEF可以确定XRM业务标识或多模态数据服务标识，对应的数据网络名DNN和网络切片选择支持信息S-NSSAI；确定多模态数据服务标识对应的数据网络名DNN和网络切片选择支持信息S-NSSAI；确定外部应用标识，即该XRM业务标识对应的核心网(core network，CN)应用标识，其中，所述外部应用标识用于标识所述XRM业务；根据XRM业务对应的签约信息，确定终端设备标识对应的CN内终端设备标识；根据XRM业务对应的签约信息，确定XRM业务组标识对应的CN内XRM业务组标识,其中，NEF可以从UDM中获取XRM业务对应的签约信息。
步骤303，确定XRM业务对应的特性参数。
可选的，NEF可以根据该XRM业务对应的签约信息，确定其对应的特性参数。
可选的，NEF还可以根据其本地的配置完善相应的业务特性参数。
步骤304，将XRM业务对应的特性参数存储至UDR。
可选的，NEF可以将特性参数作为application data的业务特性参数存储。
本公开中，NEF在确定了XRM业务对应的特性参数后，即可将该特性参数存储至UDR中，由此，网元设备，即消费端(consumer)，比如，AF、PCF、SMF或AMF即可通过订阅事件触发器，来获取UDR报告的XRM业务对应的特性参数，进而确定对应的策略及QoS，从而实现该XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
本公开中，NEF在接收到AF发送的XRM业务信息后，即可根据该服务信息及XRM业务信息对应的签约信息，确定XRM业务对应的特性参数，进而将该特性参数存储至UDR，以供消费端使用，从而实现该XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
请参见图4，图4是本公开实施例提供的另一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由NEF执行。如图4所示，该方法可以包括但不限于如下步骤：
步骤401，接收应用功能AF发送的请求消息，其中，请求消息中携带XRM业务信息。
步骤402，确定与XRM业务信息对应的核心网侧映射信息。
步骤403，确定XRM业务对应的特性参数。
其中，上述步骤401-步骤403的具体实现，可以参照本公开任一实施例的详细描述，此处不再赘述。
步骤404，将XRM业务对应的特性参数发送给策略控制功能PCF设备。
本公开中，NEF将XRM业务对应的特性参数发送给PCF后，PCF即可执行响应授权，以及测量和规则的决策或更新。可选的，PCF还可以根据授权结果，存储相应信息至UDF中。
可选的，该XRM业务与多个终端设备关联，且多个终端设备可能选择到了多个不同的PCF，则NEF关联的该XRM业务组也就可能会关联到多个不同的PCF，从而NEF则可以将特性参数发送给该多个PCF设备。从而每个PCF即可执行相应的授权、策略和规则的决策或更新，从而使得各个PCF间策略和QoS协同，进而实现了XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，为XRM业务数据流QoS和传输策略协同提供了保障。
本公开中，NEF在接收到AF发送的XRM业务信息后，即可执行信息映射，并根据该服务信息及XRM业务信息对应的签约信息，确定XRM业务对应的特性参数，进而将该特性参数发送给PCF，从而实现该XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
请参见图5，图5是本公开实施例提供的另一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由NEF执行。如图5所示，该方法可以包括但不限于如下步骤：
步骤501，接收应用功能AF发送的请求消息，其中，请求消息中携带XRM业务信息。
步骤502，确定与XRM业务信息对应的核心网侧映射信息。
本公开中，步骤501-步骤502的具体实现过程，可参见本公开中任一实施例中的详细描述，在此不再赘述。
步骤503，接收网元设备发送的第一请求，其中，第一请求中包括XRM业务事件触发器。
其中，网元设备可以为以下至少一项：AF，PCF，SMF，AMF。
其中，第一请求，可以为网元设备向NEF发送的订阅请求，用于订阅XRM业务事件触发器。XRM业务事件触发器，可以为XRMserviceormultimodal data relatedeventtrigger，例如Service QoSupdate,UE relocation，PCF change等触发器。
需要说明的是，步骤503，可以位于步骤502之后执行，或者，也可以与步骤502或步骤501同步执行，或者在步骤501之前执行，本公开对此不做限定。
步骤504，响应于XRM业务事件触发器被触发，向网元设备报告XRM业务事件触发器对应的信息。
可选的，NEF在收到AF发送的请求消息后，可以根据XRM业务信息及对应的签约信息，触发XRM业务事件触发器。
或者，也可以在确定该XRM业务组标识关联的任一终端设备对应的服务质量Qos特性参数或路由变更时，触发XRM业务事件触发器。
本公开中，NEF可以接收网元设备(消费端)订阅XRM业务相关事件触发器，并在订阅的事件触发器被触发时，向消费端报告相关信息，从而使得消费端可以基于获得的XRM业务信息，执行协同策略。
本公开中，NEF在接收到AF发送的XRM业务信息后，即可执行信息映射，并在接收到网元设备发送的第一请求后，在确定事件触发器被触发时，即可将相关信息发送给网元设备，从而实现该XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
请参见图6，图6是本公开实施例提供的一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由应用功能AF执行。如图6所示，该方法可以包括但不限于如下步骤：
步骤601，向网络开放功能NEF发送请求消息，其中，请求消息中携带XRM业务信息。
可选的，AF可以通过触发Nnef_XRM ServiceParameter service，向NEF发送请求消息。
可选的，XRM业务信息包括以下至少一项：XRM业务标识，XRM业务组标识，及AF为XRM业务相关的终端设备提供XRM业务或多模态数据服务的特定参数。
其中，XRM业务标识，可以为任一可唯一确定该XRM业务的标识信息。XRM业务组标识可以用于标识与该XRM业务相关的各个终端设备。
可选的，AF为XRM业务相关的终端设备提供的特定参数，还可以为与XRM业务对应的多模态数据服务的特定参数，本公开对此不做限定。
可选的，该XRM业务相关的终端设备可能为一个，也可能为多个，AF为该一个终端设备或多个终端设备提供的XRM业务或多模态数据服务的特定参数，可以包括以下以下至少一项：服务描述(Service Description)，服务参数(Service Parameters)，终端设备标识，终端设备组标识，订阅事件(Subscription to events)。
其中，Service Description，可以用来标识XRMserviceorXRM data Service。
其可以用DNN和S-NSSAI的组合(combination of DNN和S-NSSAI)，或者，可以用XRM标识(identification，ID)来标识；或者，用AF服务标识(AFServiceIdentifier)或外部应用标识(Application Identifier)来表示。
Service Parameters，为有关XRM业务或多模态数据服务相关政策和QoS确定的AF指南的信息。例如，XRM业务或多个数据服务相关的应用路由的规则列表(a list of rules that associate XRMserviceormultiple data Service application traffic)；终端设备策略(policy)等参数；组标识(GroupID)；DNN和S-NSSAI组合；相应规则的选择优先级，例如：可供替代的(Alternative)QoS参数优先级，相应位置(location)或时间窗口(TimeWindow)优先级，或路由选择优先级等。
Subscription to events，为AF需要订阅的有关SM策略结果的通知(The AF may subscribe to  notifications about the outcome of the SMpolicy)，或AMpolicy或UEPolicy的执行和变更。
可选的，XRM业务相关的多个终端设备的签约数据可以通过XRM业务标识关联。其中，XRM业务组中的多个终端设备的数据保持一致，比如，多个终端设备的业务QoS一致，接入和数据路由的特性参数一致。
可选的，AF可以在收到XRM业务相关的终端设备的请求后，触发生成，并发送请求消息；或者，也可以根据协议约定，自动触发并发送请求消息，本公开对此不做限定。
本公开中，AF通过将XRM业务信息发送给NEF，使得NEF可以根据需要更新UDR信息或将XRM业务信息发送给PCF，从而实现该XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
请参见图7，图7是本公开实施例提供的一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由AF执行。如图7所示，该方法可以包括但不限于如下步骤：
步骤701，向NEF发送请求消息，其中，请求消息中携带XRM业务信息。
上述步骤701的具体实现过程可参照本公开任一实施例的详细描述，此处不再赘述。
可选的，当AF需要更新和删除相应请求时，也可通过触发Nnef_XRM ServiceParameter service服务，发起AF请求的更新和删除流程。
步骤702，向NEF发送第一请求，其中，第一请求中包括XRM业务事件触发器。
本公开中，AF还可以通过触发Nnef_XRM ServiceParameter service，向NEF发送第一请求，以订阅需要的XRM业务事件触发器。
其中，XRM业务事件触发器，可以为XRMserviceormultimodal data relatedeventtrigger，例如Service QoSupdate，UE relocation，PCF change等触发器。
需要说明的是，步骤702可以在步骤701之后执行，或者也可以与步骤701同步执行，或者也可以在步骤701之前执行，本公开对此不做限定。
步骤703，接收NEF报告的XRM业务事件触发器对应的信息。
可选的，AF可以通过接收NEFreport，获取相应状态信息statusinformation。进而再执行后续QoS规则或终端设备接入和路由等策略的协同。例如，XRMserviceormultimodal data Group中，第一个终端设备的QoS特性参数变更或路由traffic变更，则触发Eventreport到NEF，进而报告给XRMserviceormultimodal data Group中对应的其它终端设备，或同一终端设备的其它Applicationtraffic关联的PCF或SMF，从而PCF或SMF执行相应回话更新(SessionUpdate)，或网络功能重选(NFreselection)。
可选的，由于UDR是全网数据中心，NEF在确定了XRM业务的特性参数后，可以将参数存储在UDR中，从而AF也向UDR订阅XRM业务事件触发器，比如，向UDR发送第二请求，其中，第二请求中包括XRM业务事件触发器，进而再接收UDR报告的XRM业务事件触发器对应的信息。
本公开中，AF通过将XRM业务信息发送给NEF，并从NEF处订阅XRM业务相关事件触发器，以在XRM业务相关事件触发器被触发时，获取NEF发送的XRM业务事件触发器对应的信息，从而实现该XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
请参见图8，图8是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由PCF执行。如图8所示，该方法可以包括但不限于如下步骤：
步骤801，接收终端设备关联的XRM业务信息。
可选的，PCF可以接收NEF发送的XRM业务信息，或者，也可以获取UDR报告的XRM业务信息，本公开对此不做限定。
可选的，PCF为与终端设备关联的AM相关的PCF，即用于为终端设备的接入管理提供决策服务的PCF。
可选的，XRM业务信息包括以下至少一项：XRM业务标识，XRM业务组标识，及AF为XRM业务相关的终端设备提供XRM业务或多模态数据服务的特定参数。
其中，XRM业务标识，可以为任一可唯一确定该XRM业务的标识信息。XRM业务组标识可以用于标识与该XRM业务相关的各个终端设备。
可选的，AF为XRM业务相关的终端设备提供的特定参数，还可以为与XRM业务对应的多模态数据服务的特定参数，本公开对此不做限定。
可选的，该XRM业务相关的终端设备可能为一个，也可能为多个，AF为该一个终端设备或多个终端设备提供的XRM业务或多模态数据服务的特定参数，可以包括以下以下至少一项：服务描述(Service Description)，服务参数(Service Parameters)，终端设备标识，终端设备组标识，订阅事件 (Subscription to events)。
其中，Service Description，可以用来标识XRMserviceorXRM data Service。
其可以用DNN和S-NSSAI的组合(combination of DNN和S-NSSAI)，或者，可以用XRM标识(identification，ID)来标识；或者，用AF服务标识(AFServiceIdentifier)或外部应用标识(Application Identifier)来表示。
Service Parameters，为有关XRM业务或多模态数据服务相关政策和QoS确定的AF指南的信息。例如，XRM业务或多个数据服务相关的应用路由的规则列表(a list of rules that associate XRMserviceormultiple data Service application traffic)；终端设备策略(policy)等参数；组标识(GroupID)；DNN和S-NSSAI组合；相应规则的选择优先级，例如：可供替代的(Alternative)QoS参数优先级，相应位置(location)或时间窗口(TimeWindow)优先级，或路由选择优先级等。
Subscription to events，为AF需要订阅的有关SM策略结果的通知(The AF may subscribe to notifications about the outcome of the SMpolicy)，或AMpolicy或UE Policy的执行和变更。
可选的，XRM业务相关的多个终端设备的签约数据可以通过XRM业务标识关联。其中，XRM业务组中的多个终端设备的数据保持一致，比如，多个终端设备的业务QoS一致，接入和数据路由的特性参数一致。
步骤802，根据所述XRM业务信息，生成服务质量Qos规则和/或终端设备接入和路由策略。
步骤803，将所述Qos规则和/或终端设备接入和路由策略发送给终端设备。
本公开中，PCF在获取到XRM业务信息后，即可根据该信息，执行相应授权、以及测量和规则的决策和更新，并将新生成的Qos规则，及终端设备接入和路由策略发送给终端设备，之后，终端设备即可基于新接收的Qos规则，及终端设备接入和路由策略，进行接入和通信传输。由于支持该XRM业务的各个终端设备收到的Qos规则，及终端设备接入和路由策略，均为对应的PCF基于XRM业务信息生成了，从而实现了各终端设备间接入和移动的协同。
可选的，如果AF订阅了XRM业务相关策略的执行结果通知，则PCF还可以在确定AF订阅了XRM业务相关策略执行结果通知时，将执行结果通过NEF发送给所述AF。
本公开中，PCF在获取到XRM业务信息后，即可根据该信息，执行相应授权、以及测量和规则的决策和更新，并将新生成的Qos规则和/或终端设备接入和路由策略发送给终端设备，从而使得XRM业务关联的终端设备间可以实现Qos规则和/或终端设备接入和路由策略的协同，为实现XRM业务数据流QoS和传输策略协同提供了保障。
请参见图9，图9是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由PCF执行。如图9所示，该方法可以包括但不限于如下步骤：
步骤901，向NEF发送第一请求，其中，第一请求中包括XRM业务事件触发器。
其中，XRM业务事件触发器，可以为XRMserviceormultimodal data relatedeventtrigger，例如Service QoSupdate，UE relocation，PCF change等触发器。
本公开中，由于AF可以将XRM业务信息发送给NEF，从而NEF即可根据XRM业务信息及对应的签约信息，确定XRM业务的特性参数，从而PCF即可从NEF处订阅XRF服务事件触发器，以获取XRM业务信息。
步骤902，接收NEF报告的XRM业务事件触发器对应的信息。
步骤903，根据XRM业务事件触发器对应的信息，生成服务质量Qos规则和/或终端设备接入和路由策略。
步骤904，将Qos规则和/或终端设备接入和路由策略发送给终端设备。
步骤901-904的具体实现过程，可参照本公开任一实施例的详细描述，此处不再赘述。
本公开中，PCF可以通过向NEF订阅XRF服务事件触发器，以获取XRM业务信息，之后，即可根据该信息，执行相应授权、以及测量和规则的决策和更新，并将新生成的Qos规则和/或终端设备接入和路由策略发送给终端设备，从而使得XRM业务关联的终端设备间可以实现Qos规则和/或终端设备接入和路由策略的协同，为实现XRM业务数据流QoS和传输策略协同提供了保障。
请参见图10，图10是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由PCF执行。如图10所示，该方法可以包括但不限于如下步骤：
步骤1001，向UDR发送第二请求，其中，所述第二请求中包括XRM业务事件触发器。
本公开中，由于UDR是全网数据中心，NEF在确定了XRM业务的特性参数后，可以将参数存储在UDR中，从而PCF可以从UDR处订阅XRM业务事件触发器，以获取XRM业务信息。
步骤1002，接收UDR报告的XRM业务事件触发器对应的信息。
步骤1003，根据XRM业务事件触发器对应的信息，生成服务质量Qos规则和/或终端设备接入和路 由策略。
步骤1004，将Qos规则和/或终端设备接入和路由策略发送给终端设备。步骤1001-1004的具体实现过程，可参照本公开任一实施例的详细描述，此处不再赘述。
本公开中，PCF可以通过向UDR订阅XRF服务事件触发器，以获取XRM业务信息，之后，即可根据该信息，执行相应授权、以及测量和规则的决策和更新，并将新生成的Qos规则和/或终端设备接入和路由策略发送给终端设备，从而使得XRM业务关联的终端设备间可以实现Qos规则和/或终端设备接入和路由策略的协同，为实现XRM业务数据流QoS和传输策略协同提供了保障。
请参见图11，图11是本公开实施例提供的又一种扩展现实多媒体XRM业务的处理方法的流程示意图，该方法由PCF执行。如图11所示，该方法可以包括但不限于如下步骤：
步骤1101，接收统一数据寄存器UDR发送的终端设备签约信息变更通知，其中，所述变更通知中携带所述XRM业务信息。
可选的，本公开中，NEF在根据AF发送的请求消息，确定了XRM业务对应的特性参数，并将对应的特性参数存储至UDR后，UDR即可确定终端设备的签约信息变更，从而PCF即可接收到UDR发送的终端设备签约信息变更通知。
步骤1102，根据XRM业务信息，生成服务质量Qos规则和/或终端设备接入和路由策略。
步骤1103，将Qos规则和/或终端设备接入和路由策略发送给终端设备。。
可选的，PCF在确定了终端设备侧的Qos规则和/或终端设备接入和路由策略后，即可将相关策略发送给终端设备，从而使得终端设备基于获取的Qos规则和/或终端设备接入和路由策略进行通信。
可选的，响应于所述终端设备对应的签约信息变更，将变更后的参数存储至UDR。
同时，如果AF订阅了XRM业务相关策略的执行结果通知，则PCF还可以在确定AF订阅了XRM业务相关策略执行结果通知时，将执行结果通过NEF发送给所述AF。
上述步骤1101-1103的实现过程，可参照本公开任一实施例的详细描述，此处不再赘述。
本公开中，PCF可以在接收到UDR发送的终端设备签约信息变更通知时，根据XRM业务信息，执行相应授权、以及测量和规则的决策和更新，并将新生成的Qos规则和/或终端设备接入和路由策略发送给终端设备，从而使得XRM业务关联的终端设备间可以实现Qos规则和/或终端设备接入和路由策略的协同，为实现XRM业务数据流QoS和传输策略协同提供了保障。
请参见图11a，图11a是本公开实施例提供的一种扩展现实多媒体XRM业务的处理方法的流程示意图。如图11a所示，该方法可以包括但不限于如下步骤：
步骤1104，接收策略控制功能PCF设备发送的服务质量Qos规则和/或终端设备接入和路由策略。
其中，服务质量Qos规则和/或终端设备接入和路由策略，为PCF基于XRM业务信息生成的。
步骤1105，执行Qos规则和/或终端设备接入和路由策略。
本公开中，终端设备在注册到网络时选择的与AM session关联的PCF，在基于XRM业务的信息，确定了Qos规则和/或终端设备接入和路由策略，即会将该Qos规则和/或终端设备接入和路由策略发送给终端设备。之后，终端设备即可基于新接收的Qos规则及终端设备接入和路由策略，进行接入和通信传输。由于支持该XRM业务的各个终端设备收到的Qos规则及终端设备接入和路由策略，均为对应的PCF基于XRM业务信息生成了，从而实现了各终端设备间接入和移动的协同。
本公开中，终端设备在接收到基于XRM业务信息生成的Qos规则和/或终端设备接入和路由策略后，即可基于该Qos规则和/或终端设备接入和路由策略，进行接入及通信传输，从而实现了与该XRM业务关联的各终端设备间的Qos规则和/或终端设备接入和路由策略的协同，为实现XRM业务数据流QoS和传输策略协同提供了保障。
请参见图12，图12是本公开实施例提供的一种扩展现实多媒体XRM业务的处理方法的交互示意图。如图12所示，该方法可以包括但不限于如下步骤：
步骤1201，终端设备注册到网络，并选择了对应的PCF，完成了AMsess ion关联。
其中，该终端设备，可以为XRM业务或多模态数据服务相关的一个终端设备，或者多个终端设备。可以理解的是，多个终端设备，可以分别选择
步骤1202，PCF根据XRM业务的策略和QoS需求,向UDM订阅XRM业务或多模态数据服务相关签约信息的变更通知。
需要说明的是，上述步骤1201和步骤1202，可以不必与下述各步骤具有严格的先后顺序，即上述步骤1201和步骤1202，可以在以下各步骤前执行，也可以与以下各步骤并行执行，或者，还可以在以下各步骤之后执行，本公开对此不做限定。
步骤1203，AF创建请求，其中，请求中包含XRM业务标识和/或XRM业务组标识。
步骤1204，AF向NEF发送Nnef XRM ServiceParameter请求消息。
可选的，AF还可以向NEF发送Nnef XRM ServiceParameter更新消息，或者，AF还可以向NEF发送Nnef XRM ServiceParameter删除消息。
步骤1205，NEF将XRM业务信息存储至UDR。
可选的，NEF还可以更新UDR中的XRM业务信息，或者移除(removing)UDR中的XRM业务信息。
步骤1206，NEF给AF返回创建请求响应消息。
步骤1207，PCF收到UDR的签约信息变更通知。
步骤1208，PCF给终端设备传输终端设备策略。
步骤1209，PCF给NEF发送事件开放通知。
可选的，PCF可以通过PCF提供的服务接口Npcf，向NEF发送通知，比如发送Npcf event exposure notify。
步骤1210，NEF收到通知后，首先执行内外相关参数的映射。
步骤1211，将映射后的相关参数报告给AF。
上述步骤1201-1211的具体实现方式，可以参照本公开任一任一实施例的详细描述，在此不再赘述。
本公开中，通过上述XRM信息的交互，即可实现XRM业务组对应的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
请参见图13，为本公开实施例提供的一种通信装置1300的结构示意图。图13所示的通信装置1300可包括收发模块1301和处理模块1302。收发模块1301可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块1301可以实现发送功能和/或接收功能。
可以理解的是，通信装置1300可以是网络开放功能NEF，也可以是网络开放功能NEF中的装置，还可以是能够与网络开放功能NEF匹配使用的装置。
通信装置1300在网络开放功能NEF侧，其中：
收发模块1301，用于接收应用功能AF发送的请求消息，其中，所述请求消息中携带XRM业务信息。
处理模块1302，用于根据所述XRM业务信息对应的签约信息及所述XRM业务信息，更新统一数据寄存器UDR中所述XRM的信息。
可选的，所述XRM业务信息包括以下至少一项：
XRM业务标识；
XRM业务组标识；
所述AF为所述XRM业务相关的终端设备提供XRM业务或多模态数据服务的特定参数。
可选的，所述XRM业务组标识用于标识与所述XRM业务相关的各个终端设备。
可选的，所述特定参数包括以下至少一项：
服务描述，服务参数，终端设备标识，终端设备组标识，订阅事件。
可选的，所述处理模块1302，还用于：
确定与所述XRM业务信息对应的核心网侧映射信息。
可选的，所述处理模块1302，具体用于：
确定所述XRM业务标识或多模态数据服务标识，对应的数据网络名DNN和网络切片选择支持信息S-NSSAI；
确定外部应用标识对应的核心网CN应用标识，其中，所述外部应用标识用于标识所述XRM业务；
根据XRM业务对应的签约信息，确定所述终端设备标识对应的CN内终端设备标识；
根据XRM业务对应的签约信息，确定所述XRM业务组标识对应的CN内XRM业务组标识。
可选的，NEF可以从UDM中获取XRM业务对应的签约信息。
可选的，所述处理模块1302，还用于：
确定所述XRM业务对应的特性参数。
可选的，所述处理模块1302，还用于将所述XRM业务对应的特性参数存储至统一数据寄存器UDR；和/或，
所述收发模块1301，还用于将所述XRM业务对应的特性参数发送给策略控制功能PCF设备。
可选的，所述XRM业务与多个终端设备关联，所述收发模块1301，还用于：
将所述特性参数发送给与所述多个终端设备中的每个终端设备对应的PCF设备。
可选的，所述多个终端设备的签约数据，通过所述XRM业务标识和/或所述XRM业务组标识关联。
可选的，所述收发模块1301，还用于：
接收网元设备发送的第一请求，其中，所述第一请求中包括XRM业务事件触发器；
响应于所述XRM业务事件触发器被触发，向所述网元设备报告所述XRM业务事件触发器对应的信息，其中，所述网元设备为以下至少一项：AF，PCF，SMF，AMF。
本公开中，NEF收到AF发送的XRM业务信息后，即可根据该服务信息及XRM业务信息对应的签约信息，更新UDR中XRM的信息，以供PCF或RAN执行，从而实现了XRM业务组对应的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
可以理解的是，通信装置1300还可以是应用功能AF，也可以是应用功能AF中的装置，还可以是能够与应用功能AF匹配使用的装置。
通信装置1300在应用功能AF侧，其中：
收发模块1301，用于向网络开放功能NEF发送请求消息，其中，所述请求消息中携带XRM业务信息。
可选的，所述XRM业务信息包括以下至少一项：
XRM业务标识；
XRM业务组标识；
所述AF为所述XRM业务相关的终端设备提供XRM业务的特定参数。
可选的，所述XRM业务组标识用于标识与所述XRM业务相关的各个终端设备。
可选的，所述特定参数包括以下至少一项：
服务描述，服务参数，终端设备标识，终端设备组标识，订阅事件。
可选的，所述收发模块1301，还用于：
向所述NEF发送第一请求，其中，所述第一请求中包括XRM业务事件触发器；
接收所述NEF报告的所述XRM业务事件触发器对应的信息。
可选的，所述收发模块1301，还用于：
向UDR发送第二请求，其中，所述第二请求中包括XRM业务事件触发器；
接收所述UDR报告的所述XRM业务事件触发器对应的信息。
本公开中，AF通过将XRM业务信息发送给NEF，使得NEF可以根据需要更新UDR信息或将XRM业务信息发送给PCF，从而实现该XRM业务组关联的多个终端设备间的接入和移动性相关需求的协同，进而保障了XRM业务数据流QoS和传输策略协同。
可以理解的是，通信装置1300可以是策略控制功能PCF设备，也可以是策略控制功能PCF设备中的装置，还可以是能够与策略控制功能PCF设备匹配使用的装置。
收发模块1301，用于接收终端设备关联的XRM业务信息。
处理模块1302，用于根据所述XRM业务信息，执行服务质量Qos规则和/或终端设备接入和路由策略的协同。
可选的，所述收发模块1301，还用于：
向NEF发送第一请求，其中，所述第一请求中包括XRM业务事件触发器；
接收所述NEF报告的所述XRM业务事件触发器对应的信息。
可选的，所述收发模块1301，还用于：
向UDR发送第二请求，其中，所述第二请求中包括XRM业务事件触发器；
接收所述UDR报告的所述XRM业务事件触发器对应的信息。
可选的，所述收发模块1301，具体用于：
接收统一数据寄存器UDR发送的所述终端设备签约信息变更通知，其中，所述变更通知中携带所述XRM业务信息。
可选的，所述收发模块1301，还用于：
向所述终端设备发送终端设备策略。
可选的，所述处理模块1302，还用于：
响应于所述终端设备对应的签约信息变更，将变更后的参数存储至UDR。
可选的，所述收发模块1301，还用于：
响应于应用功能AF请求了XRM业务相关策略执行结果通知，将执行结果通过NEF发送给所述AF。
本公开中，PCF在获取到XRM业务信息后，即可根据该信息，执行相应授权、以及测量和规则的决策和更新，并将新生成的Qos规则和/或终端设备接入和路由策略发送给终端设备，从而使得XRM业务关联的终端设备间可以实现Qos规则和/或终端设备接入和路由策略的协同，为实现XRM业务数据流QoS和传输策略协同提供了保障。
可以理解的是，通信装置1300还可以是终端设备，也可以是终端设备中的装置，还可以是能够与终端设备匹配使用的装置。
通信装置1300在终端设备中，其中：
收发模块，用于接收策略控制功能PCF设备发送的服务质量Qos规则和/或终端设备接入和路由策 略。
处理模块，用于执行Qos规则和/或终端设备接入和路由策略。
本公开中，终端设备在接收到基于XRM业务信息生成的Qos规则和/或终端设备接入和路由策略后，即可基于该Qos规则和/或终端设备接入和路由策略，进行接入及通信传输，从而实现了与该XRM业务关联的各终端设备间的Qos规则和/或终端设备接入和路由策略的协同，为实现XRM业务数据流QoS和传输策略协同提供了保障。
请参见图14，图14是本公开实施例提供的另一种通信装置1400的结构示意图。通信装置1400可以是网络开放功能NEF，也可以是应用功能AF，还可以是策略控制功能PCF设备，还可以是终端设备，也可以是支持网络开放功能NEF实现上述方法的芯片、芯片系统、或处理器等，还可以是支持应用功能AF实现上述方法的芯片、芯片系统、或处理器等，还可以是支持策略控制功能PCF设备实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1400可以包括一个或多个处理器1401。处理器1401可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1400中还可以包括一个或多个存储器1402，其上可以存有计算机程序1404，处理器1401执行所述计算机程序1404，以使得通信装置1400执行上述方法实施例中描述的方法。可选的，所述存储器1402中还可以存储有数据。通信装置1400和存储器1402可以单独设置，也可以集成在一起。
可选的，通信装置1400还可以包括收发器1405、天线1406。收发器1405可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1405可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1400中还可以包括一个或多个接口电路1407。接口电路1407用于接收代码指令并传输至处理器1401。处理器1401运行所述代码指令以使通信装置1400执行上述方法实施例中描述的方法。
通信装置1400为网络开放功能NEF：收发器1405用于执行图2中的步骤201；图3中的步骤301；图4中的步骤401、步骤404；图5中的步骤501、步骤503、步骤504等。处理器1401用于执行图2中的步骤202；图3中的步骤302、步骤303、步骤304；图4中的步骤402、步骤403；图5中的步骤502等。
通信装置1400为应用功能AF：收发器1405用于执行图6中的步骤601；图7中的步骤701、步骤702、步骤703等。
通信装置1400为策略控制功能PCF设备：收发器1405用于执行图8中的步骤801、步骤803；图9中的步骤901、步骤902、步骤904；图10中的步骤1001、步骤1002、步骤1004；图11中的步骤1101、步骤1103等。处理器1401用于执行图8中的步骤802；图9中的步骤903；图10中的步骤1003；图11中的步骤1102等。
通信装置1400为终端设备：收发器1405用于执行图11a中的步骤1104等。处理器1401用于执行图11a中的步骤1105等。
在一种实现方式中，处理器1401中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1401可以存有计算机程序1403，计算机程序1403在处理器1401上运行，可使得通信装置1400执行上述方法实施例中描述的方法。计算机程序1403可能固化在处理器1401中，该种情况下，处理器1401可能由硬件实现。
在一种实现方式中，通信装置1400可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、 双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是网络设备或者接入网设备(如前述方法实施例中的终端设备)，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图14的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图15所示的芯片的结构示意图。图15所示的芯片包括处理器1501和接口1502。其中，处理器1501的数量可以是一个或多个，接口1502的数量可以是多个。
对于芯片用于实现本公开实施例中网络开放功能NEF的功能的情况：
接口1502，用于执行图2中的步骤201；图3中的步骤301；图4中的步骤401、步骤404；图5中的步骤501、步骤503、步骤504等。
对于芯片用于实现本公开实施例中应用功能AF的功能的情况：
接口1502，用于用于执行图6中的步骤601；图7中的步骤701、步骤702、步骤703等。
对于芯片用于实现本公开实施例中策略控制功能PCF设备的功能的情况：
接口1502，用于执行图8中的步骤801、步骤803；图9中的步骤901、步骤902、步骤904；图10中的步骤1001、步骤1002、步骤1004；图11中的步骤1101、步骤1103等。
对于芯片用于实现本公开实施例中终端设备设备的功能的情况：
接口1502，用于执行图11a中的步骤1104等。
可选的，芯片还包括存储器1503，存储器1503用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开实施例还提供一种扩展现实多媒体XRM业务的处理系统，该系统包括前述图13实施例中作为网络开放功能NEF的通信装置，和作为应用功能AF的通信装置，或作为策略控制功能PCF设备的通信装置，或者，该系统包括前述图14实施例中作为网络开放功能NEF的通信装置，和作为应用功能AF的通信装置，和作为策略控制功能PCF设备的通信装置。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
可以理解的是，本公开中“多个”是指两个或两个以上，其它量词与之类似。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。单数形式的“一种”、 “所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
进一步可以理解的是，本公开实施例中尽管在附图中以特定的顺序描述操作，但是不应将其理解为要求按照所示的特定顺序或是串行顺序来执行这些操作，或是要求执行全部所示的操作以得到期望的结果。在特定环境中，多任务和并行处理可能是有利的。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (50)

  1. 一种扩展现实多媒体XRM业务的处理方法，其特征在于，由网络开放功能NEF执行，所述方法包括：
    接收应用功能AF发送的请求消息，其中，所述请求消息中携带XRM业务信息；
    根据所述XRM业务信息对应的签约信息及所述XRM业务信息，更新统一数据寄存器UDR中所述XRM的信息。
  2. 如权利要求1所述的方法，其特征在于，所述XRM业务信息包括以下至少一项：
    XRM业务标识；
    XRM业务组标识；
    所述AF为所述XRM业务相关的终端设备提供XRM业务的特定参数。
  3. 如权利要求2所述的方法，其特征在于，所述XRM业务组标识用于标识与所述XRM业务相关的各个终端设备。
  4. 如权利要求2所述的方法，其特征在于，所述特定参数包括以下至少一项：
    服务描述，服务参数，终端设备标识，终端设备组标识，订阅事件。
  5. 如权利要求3所述的方法，其特征在于，还包括：
    确定与所述XRM业务信息对应的核心网侧映射信息。
  6. 如权利要求5所述的方法，其特征在于，所述确定与所述XRM业务信息对应的核心网侧映射信息，包括以下至少一项：
    确定所述XRM业务标识，对应的数据网络名DNN和网络切片选择支持信息S-NSSAI；
    确定外部应用标识对应的核心网CN应用标识，其中，所述外部应用标识用于标识所述XRM业务；
    根据所述XRM业务对应的签约信息，确定所述终端设备标识对应的CN内终端设备标识；
    根据所述XRM业务对应的签约信息，确定所述XRM业务组标识对应的CN内XRM业务组标识。
  7. 如权利要求1所述的方法，其特征在于，还包括：
    确定所述XRM业务对应的特性参数。
  8. 如权利要求7所述的方法，其特征在于，还包括：
    将所述XRM业务对应的特性参数存储至统一数据寄存器UDR；和/或，
    将所述XRM业务对应的特性参数发送给策略控制功能PCF设备。
  9. 如权利要求8所述的方法，其特征在于，所述XRM业务与多个终端设备关联，所述方法还包括：
    将所述特性参数发送给与所述多个终端设备中的每个终端设备对应的PCF设备。
  10. 如权利要求9所述的方法，其特征在于，
    所述多个终端设备的签约数据,通过所述XRM业务标识和/或XRM业务组标识关联。
  11. 如权利要求1-10任一所述的方法，其特征在于，还包括：
    接收网元设备发送的第一请求，其中，所述第一请求中包括XRM业务事件触发器；
    响应于所述XRM业务事件触发器被触发，向所述网元设备报告所述XRM业务事件触发器对应的信息，其中，所述网元设备为以下至少一项：AF，PCF，SMF，AMF。
  12. 一种扩展现实多媒体XRM业务的处理方法，其特征在于，由应用功能AF执行，所述方法包括：
    向网络开放功能NEF发送请求消息，其中，所述请求消息中携带XRM业务信息。
  13. 如权利要求12所述的方法，其特征在于，所述XRM业务信息包括以下至少一项：
    XRM业务标识；
    XRM业务组标识；
    所述AF为所述XRM业务相关的终端设备提供XRM业务的特定参数。
  14. 如权利要求13所述的方法，其特征在于，所述XRM业务组标识用于标识与所述XRM业务相关的各个终端设备。
  15. 如权利要求13所述的方法，其特征在于，所述特定参数包括以下至少一项：
    服务描述，服务参数，终端设备标识，终端设备组标识，订阅事件。
  16. 如权利要求12所述的方法，其特征在于，还包括：
    向所述NEF发送第一请求，其中，所述第一请求中包括XRM业务事件触发器；
    接收所述NEF报告的所述XRM业务事件触发器对应的信息。
  17. 如权利要求12所述的方法，其特征在于，还包括：
    向UDR发送第二请求，其中，所述第二请求中包括XRM业务事件触发器；
    接收所述UDR报告的所述XRM业务事件触发器对应的信息。
  18. 一种扩展现实多媒体XRM业务的处理方法，其特征在于，由策略控制功能PCF设备执行，所述方法包括：
    接收终端设备关联的XRM业务信息；
    根据所述XRM业务信息，生成服务质量Qos规则和/或终端设备接入和路由策略；
    将所述Qos规则和/或终端设备接入和路由策略发送给所述终端设备。
  19. 如权利要求18所述的方法，其特征在于，还包括：
    向NEF发送第一请求，其中，所述第一请求中包括XRM业务事件触发器；
    接收所述NEF报告的所述XRM业务事件触发器对应的信息。
  20. 如权利要求18所述的方法，其特征在于，还包括：
    向统一数据寄存器UDR发送第二请求，其中，所述第二请求中包括XRM业务事件触发器；
    接收所述UDR报告的所述XRM业务事件触发器对应的信息。
  21. 如权利要求20所述的方法，其特征在于，所述接收终端设备关联的XRM业务信息包括：
    接收UDR发送的所述终端设备签约信息变更通知，其中，所述变更通知中携带所述XRM业务信息。
  22. 如权利要求21所述的方法，其特征在于，还包括：
    响应于所述终端设备对应的签约信息变更，将变更后的参数存储至UDR。
  23. 如权利要求18所述的方法，其特征在于，还包括：
    响应于应用功能AF请求了XRM业务相关策略执行结果通知，将执行结果通过NEF发送给所述AF。
  24. 一种扩展现实多媒体XRM业务的处理方法，其特征在于，由终端设备执行，所述方法包括：
    接收策略控制功能PCF设备发送的服务质量Qos规则和/或终端设备接入和路由策略，其中，所述Qos规则和/或终端设备接入和路由策略为基于XRM业务信息生成的；
    执行所述Qos规则和/或终端设备接入和路由策略。
  25. 一种通信装置，其特征在于，配置在网络开放功能NEF侧，所述装置包括：
    收发模块，用于接收应用功能AF发送的请求消息，其中，所述请求消息中携带XRM业务信息；
    处理模块，用于根据所述XRM业务信息对应的签约信息及所述XRM业务信息，更新统一数据寄存器UDR中所述XRM的信息。
  26. 如权利要求25所述的装置，其特征在于，所述XRM业务信息包括以下至少一项：
    XRM业务标识；
    XRM业务组标识；
    所述AF为所述XRM业务相关的终端设备提供XRM业务的特定参数。
  27. 如权利要求26所述的装置，其特征在于，所述XRM业务组标识用于标识与所述XRM业务相关的各个终端设备。
  28. 如权利要求26所述的装置，其特征在于，所述特定参数包括以下至少一项：
    服务描述，服务参数，终端设备标识，终端设备组标识，订阅事件。
  29. 如权利要求27所述的装置，其特征在于，所述处理模块，还用于：
    确定与所述XRM业务信息对应的核心网侧映射信息。
  30. 如权利要求29所述的装置，其特征在于，所述处理模块，具体用于：
    确定所述XRM业务标识，对应的数据网络名DNN和网络切片选择支持信息S-NSSAI；
    确定外部应用标识对应的核心网CN应用标识，其中，所述外部应用标识用于标识所述XRM业务；
    根据所述XRM业务对应的签约信息，确定所述终端设备标识对应的CN内终端设备标识；
    根据所述XRM业务对应的签约信息，确定所述XRM业务组标识对应的CN内XRM业务组标识。
  31. 如权利要求25所述的装置，其特征在于，所述处理模块，还用于：
    确定所述XRM业务对应的特性参数。
  32. 如权利要求31所述的装置，其特征在于，
    所述处理模块，还用于将所述XRM业务对应的特性参数存储至统一数据寄存器UDR；和/或，
    所述收发模块，还用于将所述XRM业务对应的特性参数发送给策略控制功能PCF设备。
  33. 如权利要求32所述的装置，其特征在于，所述XRM业务与多个终端设备关联，所述收发模块，还用于：
    将所述特性参数发送给与所述多个终端设备中的每个终端设备对应的PCF设备。
  34. 如权利要求33所述的装置，其特征在于，
    所述多个终端设备的签约数据，通过所述XRM业务标识和/或所述XRM业务组标识关联。
  35. 如权利要求25-34任一所述的装置，其特征在于，所述收发模块，还用于：
    接收网元设备发送的第一请求，其中，所述第一请求中包括XRM业务事件触发器；
    响应于所述XRM业务事件触发器被触发，向所述网元设备报告所述XRM业务事件触发器对应的信息，其中，所述网元设备为以下至少一项：AF，PCF，SMF，AMF。
  36. 一种通信装置，其特征在于，配置在应用功能AF侧，所述装置包括：
    收发模块，用于向网络开放功能NEF发送请求消息，其中，所述请求消息中携带XRM业务信息。
  37. 如权利要求36所述的装置，其特征在于，所述XRM业务信息包括以下至少一项：
    XRM业务标识；
    XRM业务组标识；
    所述AF为所述XRM业务相关的终端设备提供XRM业务的特定参数。
  38. 如权利要求37所述的装置，其特征在于，所述XRM业务组标识用于标识与所述XRM业务相关的各个终端设备。
  39. 如权利要求37所述的装置，其特征在于，所述特定参数包括以下至少一项：
    服务描述，服务参数，终端设备标识，终端设备组标识，订阅事件。
  40. 如权利要求36所述的装置，其特征在于，所述收发模块，还用于：
    向所述NEF发送第一请求，其中，所述第一请求中包括XRM业务事件触发器；
    接收所述NEF报告的所述XRM业务事件触发器对应的信息。
  41. 如权利要求36所述的装置，其特征在于，所述收发模块，还用于：
    向UDR发送第二请求，其中，所述第二请求中包括XRM业务事件触发器；
    接收所述UDR报告的所述XRM业务事件触发器对应的信息。
  42. 一种通信装置，其特征在于，配置在策略控制功能PCF设备侧，所述装置包括：
    收发模块，用于接收终端设备关联的XRM业务信息；
    处理模块，用于根据所述XRM业务信息，生成服务质量Qos规则和/或终端设备接入和路由策略；
    所述收发模块，还用于将所述Qos规则和/或终端设备接入和路由策略发送给所述终端设备。
    。
  43. 如权利要求42所述的装置，其特征在于，所述收发模块，还用于：
    向NEF发送第一请求，其中，所述第一请求中包括XRM业务事件触发器；
    接收所述NEF报告的所述XRM业务事件触发器对应的信息。
  44. 如权利要求42所述的装置，其特征在于，所述收发模块，还用于：
    向统一数据寄存器UDR发送第二请求，其中，所述第二请求中包括XRM业务事件触发器；
    接收所述UDR报告的所述XRM业务事件触发器对应的信息。
  45. 如权利要求44所述的装置，其特征在于，所述收发模块，具体用于：
    接收UDR发送的所述终端设备签约信息变更通知，其中，所述变更通知中携带所述XRM业务信息。
  46. 如权利要求42所述的装置，其特征在于，所述处理模块，还用于：
    响应于所述终端设备对应的签约信息变更，将变更后的参数存储至UDR。
  47. 如权利要求42-46任一所述的装置，其特征在于，所述收发模块，还用于：
    响应于应用功能AF请求了XRM业务相关策略执行结果通知，将执行结果通过NEF发送给所述AF。
  48. 一种通信装置，其特征在于，配置在终端设备中，所述装置包括：
    收发模块，用于接收策略控制功能PCF设备发送的服务质量Qos规则和/或终端设备接入和路由策略，其中，所述Qos规则和/或终端设备接入和路由策略为基于XRM业务信息生成的；
    处理模块，用于执行所述Qos规则和/或终端设备接入和路由策略。
  49. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至12中任一项所述的方法，或者执行如权利要求13至17中任一项所述的方法，或者执行如权利要求18至23中任一项所述的方法，或者执行如权利要求24所述的方法。
  50. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至12中任一项所述的方法被实现，或者使如权利要求13至17中任一项所述的方法被实现，或者使如权利要求18至23中任一项所述的方法被实现，或者使如权利要求24所述的方法被实现。
PCT/CN2022/083866 2022-03-29 2022-03-29 一种扩展现实多媒体xrm业务的处理方法及其装置 WO2023184191A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280000867.XA CN117158107A (zh) 2022-03-29 2022-03-29 一种扩展现实多媒体xrm业务的处理方法及其装置
PCT/CN2022/083866 WO2023184191A1 (zh) 2022-03-29 2022-03-29 一种扩展现实多媒体xrm业务的处理方法及其装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/083866 WO2023184191A1 (zh) 2022-03-29 2022-03-29 一种扩展现实多媒体xrm业务的处理方法及其装置

Publications (1)

Publication Number Publication Date
WO2023184191A1 true WO2023184191A1 (zh) 2023-10-05

Family

ID=88198376

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/083866 WO2023184191A1 (zh) 2022-03-29 2022-03-29 一种扩展现实多媒体xrm业务的处理方法及其装置

Country Status (2)

Country Link
CN (1) CN117158107A (zh)
WO (1) WO2023184191A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112584545A (zh) * 2019-09-30 2021-03-30 华为技术有限公司 数据传输方法及装置
EP3855705A1 (en) * 2020-01-24 2021-07-28 T-Mobile USA, Inc. Network repository function (nrf) discovery control

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112584545A (zh) * 2019-09-30 2021-03-30 华为技术有限公司 数据传输方法及装置
EP3855705A1 (en) * 2020-01-24 2021-07-28 T-Mobile USA, Inc. Network repository function (nrf) discovery control

Also Published As

Publication number Publication date
CN117158107A (zh) 2023-12-01

Similar Documents

Publication Publication Date Title
WO2023000149A1 (zh) 一种中继终端设备测量上报的方法及其装置
WO2024065842A1 (zh) 路径添加方法和装置
WO2024098208A1 (zh) 波束指示方法及装置
WO2024092523A1 (zh) 侧行链路定位消息的发送方法、接收方法及其装置
WO2024077455A1 (zh) 一种非陆地网络的接入方法及装置
WO2023184191A1 (zh) 一种扩展现实多媒体xrm业务的处理方法及其装置
WO2023201753A1 (zh) 一种终端能力上报方法、确定方法及其装置
WO2023201756A1 (zh) 一种用于基于条件的移动性的信息的处理方法及装置
JP2024519311A (ja) データ入手方法およびシステム、ならびにその装置
WO2024050778A1 (zh) 一种人工智能服务策略的更新方法及装置
WO2024020751A1 (zh) 一种第三方服务管理方法/装置/设备及存储介质
WO2024082233A1 (zh) 移动性限制实现方法和装置
WO2024092661A1 (zh) 模型的标识方法及装置
WO2024026890A1 (zh) 一种定位方法/装置/设备及存储介质
WO2023147708A1 (zh) 一种人工智能会话的更新方法及其装置
WO2024098323A1 (zh) 一种通过托管网络提供本地化服务的方法及其装置
WO2024092820A1 (zh) 一种托管网络确定方法、装置、设备及存储介质
WO2024065705A1 (zh) 应用功能授权方法及装置
WO2023115487A1 (zh) 一种人工智能会话的创建方法及其装置
WO2024065131A1 (zh) 一种多路径传输方法/装置/设备及存储介质
WO2023212960A1 (zh) 扩展现实业务策略实现方法及装置
WO2024026697A1 (zh) 一种卫星终端接入移动网络的方法及其装置
WO2023201755A1 (zh) 一种移动性管理的配置方法及装置
WO2024065844A1 (zh) 一种路径切换能力的交互方法及其装置
WO2023133689A1 (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: 22934046

Country of ref document: EP

Kind code of ref document: A1