WO2023216277A1 - 扩展现实媒体业务处理方法及装置、通信设备及存储介质 - Google Patents

扩展现实媒体业务处理方法及装置、通信设备及存储介质 Download PDF

Info

Publication number
WO2023216277A1
WO2023216277A1 PCT/CN2022/092894 CN2022092894W WO2023216277A1 WO 2023216277 A1 WO2023216277 A1 WO 2023216277A1 CN 2022092894 W CN2022092894 W CN 2022092894W WO 2023216277 A1 WO2023216277 A1 WO 2023216277A1
Authority
WO
WIPO (PCT)
Prior art keywords
tsctsf
delay
request
subscription
event
Prior art date
Application number
PCT/CN2022/092894
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 CN202280001715.1A priority Critical patent/CN117413607A/zh
Priority to PCT/CN2022/092894 priority patent/WO2023216277A1/zh
Publication of WO2023216277A1 publication Critical patent/WO2023216277A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present disclosure relates to the field of wireless communication technology but is not limited to the field of wireless communication technology, and particularly relates to an extended reality (Extended Reality and Media, XRM) business method and device, communication equipment and storage medium.
  • extended reality Extended Reality and Media, XRM
  • Mobile media services augmented reality (Augment Reality, AR), virtual reality (VR) and other extended reality (XR) services, cloud games, video-based machine or drone remote control and other services.
  • AR Augment Reality
  • VR virtual reality
  • XR extended reality
  • Multimodal data refers to the input data or output data of the same device or different devices describing the same business or application.
  • Each data stream in multimodal data often has a certain or even strong correlation, such as the synchronization of audio streams and video streams, the synchronization of tactile data and visual data, etc.
  • Embodiments of the present disclosure provide an XRM information processing method and device, communication equipment and storage media.
  • the first aspect of the embodiment of the present disclosure provides an XRM business processing method, which is executed by a Time Sensitive Communication and Time Synchronization Function (TSCTSF).
  • the method includes:
  • AF Application Function
  • the session creation request includes: synchronization indication and XRM group identification delay information; the session creation request also includes the XRM group identification and/or user equipment UEs UP address;
  • the synchronization indication and the XRM group identifier are sent to the Policy Control Function (PCF).
  • PCF Policy Control Function
  • a second aspect of the embodiment of the present disclosure provides an information processing method, which is executed by PCF.
  • the method includes:
  • policy control and charging Policy Control and Charging, PCC
  • PCC Policy Control and Charging
  • the third aspect of the embodiment of the present disclosure provides an information processing method, wherein the method is executed by AF, and the method includes:
  • the fourth aspect of the embodiment of the present disclosure provides an information processing method, which is executed by a Network Exposure Function (NEF), and the method further includes:
  • the session creation request is sent to the TSCTSF.
  • the fifth aspect of the embodiment of the present disclosure provides an extended reality service media XRM service processing device, wherein the device includes:
  • the first receiving module is configured to receive a session creation request of the application function AF, where the session creation request includes: a synchronization indication and an XRM group identifier;
  • the first sending module is configured to send the synchronization indication and the XRM group identifier to the policy control function PCF.
  • a sixth aspect of the embodiment of the present disclosure provides an information processing device, wherein the device includes:
  • the second receiving module is configured to receive the synchronization indication XRM group identifier sent by TSCTSF;
  • the PCC rule module is configured to generate PCC rules or activate predefined PCC rules according to the synchronization indication and the XRM group identifier.
  • a seventh aspect of the embodiment of the present disclosure provides an information processing device, wherein the device includes:
  • the third sending module is configured to send a session creation request of AF, where the session creation request includes a synchronization indication and an XRM group identifier;
  • the third receiving module is configured to receive a session creation response of the session creation request.
  • An eighth aspect of the embodiments of the present disclosure provides an information processing device, wherein the device further includes:
  • the fourth receiving module is configured to receive a session creation request of the application function AF, wherein the session creation request includes a synchronization indication and an XRM group identifier;
  • An acquisition module configured to obtain the address of the TSCTSF that receives the session creation request
  • the fourth sending module is configured to send the session creation request to the TSCTSF according to the address of the TSCTSF.
  • a ninth aspect of the embodiment of the present disclosure provides a communication device, including a processor, a transceiver, a memory, and an executable program stored on the memory and capable of being run by the processor, wherein the processor runs the executable program.
  • the program executes the information processing method provided by any one of the foregoing first to fourth aspects.
  • a tenth aspect of the embodiments of the present disclosure provides a computer storage medium that stores an executable program; after the executable program is executed by a processor, it can realize any one of the foregoing first to fourth aspects. information processing methods.
  • TSCTSF will receive a session creation request for XRM services.
  • the session creation request contains a synchronization instruction XRM group identifier.
  • the synchronization instruction and XRM group identifier can be used by PCF to generate PCC rules or based on predefined PCC rules, in this way, TSCTSF will treat the one or data flow involved in the session request as a TSC data flow to strictly implement synchronization and control delay, and reduce the delay and/or large delay difference of one or the data flow involved in the XRM business Phenomenon, improve the business quality of XRM business.
  • Figure 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment
  • Figure 2 is a schematic flowchart of an information processing method according to an exemplary embodiment
  • Figure 3 is a schematic flowchart of an information processing method according to an exemplary embodiment
  • Figure 4 is a schematic flowchart of an information processing method according to an exemplary embodiment
  • Figure 5 is a schematic flowchart of an information processing method according to an exemplary embodiment
  • Figure 6 is a schematic flowchart of an information processing method according to an exemplary embodiment
  • Figure 7 is a schematic flowchart of an information processing method according to an exemplary embodiment
  • Figure 8 is a schematic flowchart of an information processing method according to an exemplary embodiment
  • Figure 9 is a schematic structural diagram of an information processing device according to an exemplary embodiment
  • Figure 10 is a schematic structural diagram of an information processing device according to an exemplary embodiment
  • Figure 11 is a schematic structural diagram of an information processing device according to an exemplary embodiment
  • Figure 12 is a schematic structural diagram of an information processing device according to an exemplary embodiment
  • Figure 13 is a schematic structural diagram of a UE according to an exemplary embodiment
  • Figure 14 is a schematic structural diagram of a communication device according to an exemplary embodiment.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • word “if” as used herein may be interpreted as "when” or "when” or "in response to determining.”
  • FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system is a communication system based on cellular mobile communication technology.
  • the wireless communication system may include: several UEs 11 and several access devices 12.
  • UE 11 may be a device that provides voice and/or data connectivity to users.
  • the UE 11 may communicate with a core network via a Radio Access Network (RAN).
  • RAN Radio Access Network
  • the UE 11 may be an IoT UE, such as a sensor device, a mobile phone (or "cellular" phone) and a UE with an IoT
  • the computer of the UE may, for example, be a fixed, portable, pocket-sized, handheld, computer-built-in or vehicle-mounted device.
  • station STA
  • subscriber unit subscriber unit
  • subscriber station mobile station
  • mobile station mobile station
  • remote station remote station
  • access point remote UE ( remote terminal)
  • access UE access terminal
  • user terminal user terminal
  • user agent user agent
  • user equipment user device
  • user UE user equipment
  • UE 11 can also be a device for an unmanned aerial vehicle.
  • the UE 11 may also be a vehicle-mounted device, for example, it may be a driving computer with a wireless communication function, or a wireless communication device connected to an external driving computer.
  • the UE 11 can also be a roadside device, for example, it can be a street light, a signal light or other roadside equipment with wireless communication functions.
  • the access device 12 may be a network-side device in the wireless communication system.
  • the wireless communication system can be the 4th generation mobile communication technology (the 4th generation mobile communication, 4G) system, also known as the Long Term Evolution (LTE) system; or the wireless communication system can also be a 5G system, Also called new radio (NR) system or 5G NR system.
  • the wireless communication system may also be a next-generation system of the 5G system.
  • the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network). Or, MTC system.
  • the access device 12 may be an evolved access device (eNB) used in the 4G system.
  • the access device 12 may also be an access device (gNB) using a centralized distributed architecture in the 5G system.
  • eNB evolved access device
  • gNB access device
  • the access device 12 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU).
  • the centralized unit is equipped with a protocol stack including the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control protocol (Radio Link Control, RLC) layer, and the Media Access Control (Media Access Control, MAC) layer; distributed
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • the unit is provided with a physical (Physical, PHY) layer protocol stack, and the embodiment of the present disclosure does not limit the specific implementation of the access device 12.
  • a wireless connection can be established between the access device 12 and the UE 11 through the wireless air interface.
  • the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, such as
  • the wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.
  • XRM business requires the fifth generation mobile communication system (5th Generation System, 5GS) to comprehensively consider the quality of service (Quality of Service, QoS) characteristics of the relevant data flow of the business, such as the Guaranteed Bit Rate (GBR) associated with delay ) data flow, guaranteed flow bit rate (Guaranteed Flow Bit Rate, GFBR), packet delay estimate (Packet Delay Budget, PDB), and/or default maximum burst data volume (Default Maximum Data Burst Volume, MDBV) and other parameters, whether Able to be both satisfying and synergistic at the same time.
  • the data flow of the XRM service may involve the data flows of multiple XRM services of one UE, and/or the data flows of multiple UEs.
  • the QoS authorization and execution of these multiple data flows need to be consistent to ensure the Quality of business.
  • an embodiment of the present disclosure provides an XRM business processing method, which is executed by TSCTSF.
  • the method includes:
  • S1110 Receive a session creation request from AF, where the session creation request includes a synchronization indication and an XRM group identifier;
  • S1120 Send the synchronization indication and the XRM group identifier to the policy control function PCF.
  • the synchronization indication and the XRM group identifier are parameters that the session creation request must carry.
  • delay information and UEs IP addresses are optional parameters that can be carried in the session creation request. That is, in other embodiments, the session creation request will also include the delay information and/or the IP addresses of the UEs. At this time, the method further includes: sending the delay information and/or the UEs IP address to the PCF.
  • the information carried in the session creation request can be used by the PCF to generate policy control and charging (Policy Control and Charging, PCC) rules or activate predefined PCC rules.
  • Policy Control and Charging Policy Control and Charging, PCC
  • the AF may be a device located in a mobile communication network provided by a communication operator. This AF can be provided by the application operator. Specifically, the AF may include one or more application servers.
  • TSCTSF can be a core network element (also called core network equipment), and any network element that performs the above operations can be called TSCTSF.
  • 5GS provides time synchronization services
  • TSCTSF can be an important network element that provides time synchronization services.
  • AF wants to create a session involving multiple data streams and has small latency difference requirements for the multiple data streams or is sensitive to the latency of the data streams, it will send a session creation request to TSCTSF.
  • TSCTSF After receiving the session creation request from AF, the delay information and XRM group identifier of a session or data stream involved in the session created by the AF request can be obtained from the session creation request.
  • the multiple data streams involved in the session requested to be created in this embodiment of the disclosure may be Time Sensitive Communication (TSC) data streams.
  • TSC Time Sensitive Communication
  • TSCTSF will operate the time synchronization service on the TSC data streams.
  • the synchronization indication is carried in the session creation request and can be used to indicate that the current request to create a session is a time-sensitive session.
  • One or more data streams involved in this session are all TSC data streams, that is, these data streams are very sensitive to delay. Sensitive and very sensitive to the delay difference of multiple data streams.
  • the TSCTSF After the TSCTSF receives the session creation request containing the synchronization indication, if the session creation request contains the synchronization indication, the TSCTSF will provide time synchronization services for multiple data streams involved in the session created by the AF request (that is, the AF session).
  • TSCTSF receives the synchronization indication, it will send the synchronization indication to PCF.
  • PCF After PCF receives the synchronization indication, it knows that the AF session currently requested to be created involves TSC data streams. If there are multiple data streams, When determining the strategy to control the routing path, you can consider allowing multiple data flows to use the same routing path as much as possible to reduce the transmission delay difference.
  • the same UPF can be used preferentially for transmission and/or monitoring.
  • TSCTSF provides time synchronization services for one or more data streams requested by the AF to create a session based on the delay information provided by the AF or the delay information identified according to the XRM group identifier to ensure that one or more data streams involved in the session are The latency of multiple data streams and/or the latency difference between multiple data streams.
  • the XRM group ID is the group ID of the XRM business involved in the request to create a session.
  • the XRM group identifier is used to identify multiple data flows within an XRM business group. Multiple data streams in an XRM group may belong to one UE or multiple UEs.
  • the XRM group identification may be related to a group of UEs participating in multiple data stream transmissions.
  • the one UE group may include one or more UEs. Therefore, the UEs IP address can also be used to identify the XRM service.
  • the TSCTSF After receiving the delay information and the XRM group identifier and/or the UEs IP address, the TSCTSF will send the delay information, and at least one of the XRM group identifier and the UEs IP address to the PCF.
  • PCF is a core network function (or core network device) that formulates and maintains various policies.
  • the PCF will formulate policy control and charging (Policy Control and Charging, PCC) rules.
  • PCF After PCF receives the information sent by TSCTSF, it can dynamically generate PCC rules or activate predefined PCC rules. After the predefined PCC rule is activated, it is equivalent to the PCC rule taking effect, and the corresponding data flow can be scheduled and monitored according to the PCC rule.
  • the session creation request also includes: delay information and/or user equipment UEs IP address. If the session creation request contains delay information, it means that AF itself has provided the delay information for the session created by this request. Since the XRM service data flow involved in the session created by this AF request may involve a UE group, the UE group consists of UEs IP addresses. A UE group includes one or UE.
  • the S1120 may include: sending the synchronization indication and the XRM group identifier, as well as the delay information and/or the UEs IP address to the PCF.
  • PCF can generate PCC rules or activate predefined PCC rules based on the delay information received from TSCTSF.
  • the method further includes:
  • the TSCTSF may determine the maximum tolerated delay of each data flow involved in the session requested to be created, and/or the maximum tolerated delay difference of the data flows involved in the session.
  • TSCTSF can calculate the PDB. For example, the TSCTSF determines the PDB of the uplink data flow (ie, uplink PDB) and/or the PDB of the downlink data flow (ie, downlink PDB) based on the delay information.
  • the TSCTSF determines the PDB of the uplink data flow (ie, uplink PDB) and/or the PDB of the downlink data flow (ie, downlink PDB) based on the delay information.
  • TSCTSF calculates the PDB, it will send the PDB to PCF.
  • TSCTSF may send all delay information obtained from the session creation request and/or at least the delay information used to calculate the PDB to the PCF.
  • the PDB and the XRM group identifier can be provided to the PCF.
  • the PDB can also be sent to the PCF along with the delay information and the XRM group identifier.
  • the TSCTSF does not calculate the PDB, so the TSCTSF sends the delay information and XRM group identification and/or UEs IP addresses to the PCF after receiving the delay information.
  • the delay information includes at least one of the following:
  • the two-way delay here is: the sum of uplink delay and downlink delay.
  • the uplink delay may be: the delay of the data flow from the UE to the network device (for example, User Plane Function (UPF)).
  • UPF User Plane Function
  • the downlink delay can be: the delay of the data flow from the network device to the UE.
  • the delay difference of the data flow here may specifically be: the delay difference of multiple data flows.
  • the delay differences of the multiple data streams may include: the delay differences of multiple upstream data streams involved in the same XRM group identifier and/or UEs IP address, and/or, the delay differences in the multiple upstream data streams identified by the same XRM group and/or Or the delay difference between multiple downlink data streams involved in the UEs IP address.
  • the session creation request further includes at least one of the following:
  • QoS Quality of Service
  • the flow description may include an Information Element (IE) describing the attribute information of the data flow.
  • IE Information Element
  • the QoS information and requirements can be used by core network elements to determine the maximum delay that each data flow can tolerate and/or the maximum delay difference that the data flow can tolerate.
  • the QoS information and requirements include at least one of the following:
  • the QoS parameters may include at least one of the following:
  • Flow direction for example, one or data flow involved in the AF can be an upstream data flow and/or a downstream data flow, if the flow direction of the upstream data flow is upward; if the flow direction of the downstream data flow is downward;
  • Upstream data stream arrival time (Burst Arrival Time at UE);
  • Downstream data flow arrival time (Burst Arrival Time at UPF);
  • the duration of the data stream (Survival Time).
  • the alternative service requirements may include at least one of the following parameters:
  • Optional QoS-related parameter set which includes one or optional QoS parameter or QoS reference.
  • the QoS reference may also be used to determine any reference information that determines the QoS of the data flow.
  • QoS may be part of alternative business requirements.
  • the PDB and the synchronization indication, the XRM group identification and/or UEs IP addresses and the delay information are included in the authorization creation or update request and sent to the PCF.
  • the PCF After receiving the authorization creation or update request, the PCF will authenticate the AF session requested by AF. When the AF session is authorized, the session creation will continue. After the session creation is completed, one or more of the AF sessions involved in the AF session will be authenticated. The data stream is transferred based on the created session.
  • creating an AF session includes: allocating a session identifier, allocating transmission resources used by the session, and/or determining a routing path of one or data flow involved in the session.
  • the embodiment of the present disclosure provides an XRM business processing method, which is executed by TSCTSF.
  • the method includes:
  • S1210 Receive a session creation request from AF, where the session creation request includes a synchronization indication and an XRM group identifier;
  • S1220 Send an authorization creation or update request to the PCF, where the authorization creation or update request includes the synchronization indication and the XRM group identification.
  • S1240 Send a session creation response of the session creation request according to the response of the authorization creation or update request.
  • the session creation request may also include: delay information and/or UEs IP addresses. If the session creation request contains latency information and/or UEs IP addresses, TSCTSF will authorize the create or update request, along with the synchronization indication and XRM group identification, the latency information and/or UEs IP addresses received from the AF, Send it to PCF together.
  • TSCTSF After receiving the session creation request from AF, TSCTSF sends the authorization creation or update request to PCF, and will receive a response returned by PCF. And after receiving the response to the authorization creation or update request, TSCTSF will further send a session creation response to AF.
  • the sending of a session creation response to the session creation request based on the response to the authorization creation or update request may include;
  • the response to the authorization creation or update request is an acceptance response, and a session creation response indicating creation is sent to AF; or, the response to the authorization creation or update request is a rejection response, and a session creation response indicating no creation is sent to AF. .
  • the method further includes:
  • the subscription request is used to request to subscribe to an event report containing resource allocation status and/or transmission delay.
  • the subscription request is used for event subscription of resource allocation status changes of one or more data flows involved in the AF session; and/or event subscription of the delay of the data flow.
  • the subscribed events will be returned to AF in the form of event reports when the corresponding events occur.
  • the method further includes:
  • the address of the TSCTSF is pre-stored on the network opening function NEF, PCF or trusted AF.
  • the AF can communicate directly with the TSCTSF. For example, if the AF is recognized as a trusted device by the communication operator's management device, the address of the TSCTSF can be directly provided to the AF.
  • Both NEF and the PCF belong to network elements within the communication network provided by communication operators.
  • the address of the TSCTSF can also be stored on the NEF in advance. At this time, the AF can forward the interaction information between itself and the TSCTSF through the NEF.
  • the address of TSCTSF can also be directly stored on PCF to facilitate PCF to communicate directly with TSCTSF.
  • the TSCTSF provides its own address to the PCF.
  • the address of the TSCTSF may at least include: the IP address of the TSCTSF.
  • the address of the TSCTSF may not be pre-stored (ie, pre-configured) on the NEF, PCF or AF.
  • NEF may determine the address of the TSCTSF associated with the data network and/or network slice used by the session.
  • PCF or NEF can query the user data register (User Data Repository, UDR) for the address of TSCTSF.
  • UDR User Data Repository
  • the subscription request includes: event reporting mode information
  • the reporting mode of the event report indicated by the event reporting mode information includes at least one of the following:
  • the event report includes: the delay and/or delay difference of the data flow and/or the resource allocation status of the data flow, etc.
  • the periodic reporting mode is: event reports of subscribed events will be sent to TSCTSF periodically, and TSCTSF will forward them to AF. If the periodic reporting mode is adopted, the PCF side can configure a timer for the periodic reporting mode. When the timer expires, the event report corresponding to the subscription event will be submitted from the PCF to the TSCTSF.
  • the triggered reporting mode is: after the subscription event is triggered, TSCTSF will receive the event report sent by PCF. For example, when the delay of the data flow reaches the threshold, or the delay difference reaches the threshold, the TSCTSF will receive the event report submitted by the PCF.
  • the event reporting mode information may include an immediate reporting flag. If the immediate reporting flag is a predetermined value, it indicates that the reporting mode of the event report corresponding to the currently subscribed event is the immediate reporting mode.
  • the subscription event includes periodic information in periodic reporting mode, which means that the AF subscribes to event reports that are reported periodically. At this time, the event reporting mode information may be implicitly indicated by the period information.
  • the subscription event includes a threshold that triggers a subscription event, etc.
  • the AF subscription triggers an event report in the reporting mode.
  • the event reporting mode information may be implicitly indicated by the threshold.
  • the subscription request may include: one or bit carrying the event reporting mode.
  • an embodiment of the present disclosure provides an information processing method, which is executed by PCF.
  • the method includes:
  • S2110 Receive the synchronization indication and XRM group identification sent by TSCTSF;
  • S2120 Generate policy control and charging PCC rules or activate predefined PCC rules according to the synchronization indication and the XRM group identifier.
  • PCF will receive synchronization instructions and XRM group identifiers from TSCTSF for data flows that need to be generated or based on PCC rules.
  • the S2110 may include: while receiving the synchronization indication and the XRM group identifier sent by the TSCTSF, also receiving at least one of the delay information and the IP addresses of the UEs.
  • S2120 may include: generating PCC rules or activating predefined PCC rules according to at least one of the synchronization indication and the XRM group identifier, and/or delay information and UEs IP addresses. For example, if the PCF does not receive the delay information from the TSCTSF, it can obtain the delay information on its own based on the XRM group service identified by the XRM group identifier, and generate PCC rules or activate the predefined PCC based on the self-obtained delay information. rule.
  • the XRM group ID is the group ID of the XRM business involved in the request to create a session.
  • the XRM group identifier is used to identify multiple data flows within an XRM business group. Multiple data streams in an XRM group may belong to one UE or multiple UEs.
  • a PCC rule will be generated or a predefined PCC rule will be activated for one or data flow related to the session.
  • the method further includes:
  • PCC rules are generated or predefined PPC rules are activated for the data flows involved in the XRM group identification and/or the IP addresses of the UEs.
  • PCF after PCF receives the delay information, it will generate PCC rules or activate predefined PCC rules for one or data flow involved in the XRM group identification based on the delay information, thereby controlling the communication resources of the data flow. distribution, routing paths and/or charging conditions, etc.
  • the step of receiving the synchronization indication and delay information sent by the TSCTSF as well as the XRM group identifier and/or UEs IP address includes:
  • the PCF If the PCF receives an authorization creation or update request and determines authorization or update or determines not to authorize or update, it will notify TSCTSF through a response (response message).
  • the step according to the synchronization indication and the XRM group identifier includes:
  • the authorization creation or update request also includes the PDB calculated by the TSCTSF based on the delay information, the PDB calculated based on the synchronization indication, the TSCTSF, the XRM group identifier and/or the UES IP address , generate the PCC rule or activate the predefined PCC rule;
  • the PDB is calculated based on the delay information included in the authorization creation or update request, and the PDB calculated based on the PCF,
  • the XRM group identifier and/or the UEs IP address generates the PCC rule or activates the predefined PCC rule.
  • TSCTSF will calculate PDB based on delay information. In some embodiments, TSCTSF will not calculate PBD based on delay information.
  • PCF may receive the PDB sent by TSCTSF, so PCF can generate PCC rules or activate predefined PCC rules based on the PDB provided by TSCTSF. For example, based on the PBD provided by TSCTSF, PCF further determines the PDB and burst data volume applicable to each data flow to generate PCC rules or activate predefined PCC rules.
  • PCF will not receive PDB from TSCTSF. In this way, after PCF receives the delay information, it can calculate the PDB by itself based on the delay information, and generate PCC rules or activate predefined PCC rules based on the self-calculated PDB. For another example, PCF generates PCC rules based on its own calculated PDB and burst data volume or based on predefined PCC rules.
  • the PCC rule information related to the SFM is sent to the session management function (Session Management Function, SMF).
  • SMF Session Management Function
  • SMF will create, modify and/or release sessions according to PCC rules. For example, SMF will schedule session resources according to the PCC rule.
  • the PCF after the PCF executes the PCC rule, the PCF will send the PCC rule information related to the UPF to the UPF to facilitate the UPF to perform user plane data stream transmission according to the PCC policy information.
  • determining policy control and charging PCC rules for the UE involved in the XRM group identity based on the delay information includes:
  • PCC rules are determined for the data flow involved in the XRM group identification according to the PDB of the data flow and the burst data amount.
  • the method further includes:
  • the PCF will query the UE's subscription data based on the UE corresponding to the XRM group identifier, and determine whether to authorize the creation of a session associated with the XRM group identifier.
  • an embodiment of the present disclosure provides an information processing method, which is executed by PCF.
  • the method includes: S2210: Receive a subscription request; wherein the subscription request is used to request a subscription to an event report.
  • a subscription request from the AF is received, and the subscription request can be used by the AF to request a subscription event report from the network device.
  • the event report may include but is not limited to: an event report on resource allocation status and/or an event report on delay.
  • the AF subscribes to an event report on resource allocation status
  • the event report may indicate: a resource allocation report, a resource reclamation report, and/or a resource release report.
  • the subscription request includes: event reporting mode information
  • the reporting mode of the event report indicated by the event reporting mode information includes at least one of the following:
  • the event report includes: the delay and/or delay difference of the data flow and/or the resource allocation status of the data flow, etc.
  • the periodic reporting mode is: event reports of subscribed events will be sent to TSCTSF periodically, and TSCTSF will forward them to AF. If the periodic reporting mode is adopted, the PCF side can configure a timer for the periodic reporting mode. When the timer expires, the event report corresponding to the subscription event will be submitted from the PCF to the TSCTSF.
  • the triggered reporting mode is: after the subscription event is triggered, TSCTSF will receive the event report sent by PCF. For example, when the delay of the data flow reaches the threshold, or the delay difference reaches the threshold, the TSCTSF will receive the event report submitted by the PCF.
  • the event reporting mode information may include an immediate reporting flag. If the immediate reporting flag is a predetermined value, it indicates that the reporting mode of the event report corresponding to the currently subscribed event is the immediate reporting mode.
  • the subscription event includes periodic information in periodic reporting mode, which means that the AF subscribes to event reports that are reported periodically. At this time, the event reporting mode information may be implicitly indicated by the period information.
  • the subscription event includes a threshold that triggers a subscription event, etc.
  • the AF subscription triggers an event report in the reporting mode.
  • the event reporting mode information may be implicitly indicated by the threshold.
  • the subscription request may include: one or bit carrying the event reporting mode.
  • the method further includes:
  • the method further includes:
  • an event report is sent to the TSCTSF.
  • Changes in the delay difference of data flows may trigger the reporting of event reports.
  • the PCF can send an event report to the TSCTSF according to the subscription request, and the event report can finally be forwarded to the AF by the TSCTSF.
  • PCF can send event reports to TSCTSF according to the subscription request; the event report will eventually be forwarded to AF by TSCTSF.
  • the delay of data flow can be monitored and calculated by UPF. If AF requests to subscribe to event reports related to delay, PCF can subscribe to UPF, etc.
  • sending an event report to the TSCTSF includes:
  • an event report is sent to the TSCTSF.
  • PCF after receiving the subscription request, PCF can subscribe to UPF and/or NR-RAN for the delays of multiple data streams. In this way, PCF will receive UPF and/or NR-RAN regularly or irregularly. Provides latency for multiple data streams.
  • PCF after PCF receives the delays of multiple data streams, it can calculate the delay differences of multiple data streams associated with the same identification information. And further determine whether the time difference calculated by PCF triggers a subscription event. If the subscription event is triggered, an event report is sent to TSCTSF.
  • the subscription event can be considered to be triggered.
  • the subscription event can be notified to TSCTSF through the event report. The fact of being triggered.
  • a single UPF and/or NR-RAN can only monitor the multiple flows identified by the XRM group.
  • the delay of some data flows in a data flow can be subscribe to the UPF that transmits the multiple data flows involved in the XRM group identifier.
  • PCF calculates multiple The delay difference of data flow. For example, PCF will calculate the maximum delay difference of multiple data streams. If the maximum delay difference triggers a subscription event, it will send an event report to TSCTSF.
  • the incident report may contain at least one of the following:
  • the event report may only include the trigger flag bit of the subscription event. In this case, the event report is only used to notify the TSCTSF that the subscription event is triggered.
  • sending an event report to the TSCTSF includes:
  • an event report is sent to the TSCTSF.
  • a UPF can monitor the delay of the data stream associated with the XRM group identifier. .
  • UPF and/or NR-RAN can calculate the delay difference of multiple data flows based on the delays of multiple data flows monitored by itself.
  • PCF can directly subscribe to the delay difference from UPF and/or NR-RAN. In this way, PCF will receive the delay difference regularly or irregularly. After receiving the delay difference, PCF will determine the delay difference. Whether the delay difference between two data streams triggers a subscription event. If the subscription event is triggered, PCF will send an event report to TSCTSF. Otherwise, it will not send an event report to TTSCTSF.
  • sending an event report to the TSCTSF includes:
  • an event report is sent to the TSCTSF.
  • the PCF can also directly subscribe to the UPF for the delay of the data flow.
  • the PCF will also send an event report to the TSCTSF. Otherwise, the PCF will not send the event report to the TSCTSF.
  • sending an event report to the TSCTSF includes:
  • a subscription request is sent to the UPF and/or NR-RAN; wherein the subscription request includes: a subscription request in which the delay difference of the data flow triggers a subscription event; and/or the time delay difference of the data flow Delay triggers subscription requests for subscription events;
  • an event report is sent to the TSCTSF.
  • the PCF directly subscribes to the event report to the UPF and/or NR-RAN, and the UPF and/or NR-RAN respond according to their own Monitor the delay of the data flow, and determine whether the subscription event is triggered based on the delay difference of the data flow. If the subscription event is triggered, report the event to PCF. If from, PCF will receive the event report and send the event report to TSCTSF. , and finally sent to AF by TSCTSF.
  • PCF can also subscribe to the event report from UPF.
  • UPF and/or NR-RAN transmits and monitors the delay of the data flow.
  • UPF and/or NR-RAN will send an event report to PCF. Therefore, PCF will receive the event report and forward it to TSCTSF.
  • the PCF can also subscribe to the data flow from the corresponding UPF and/or NR-RAN. Delay-related event reports. At this time, if the delay of a certain data flow triggers a subscription event, PCF will receive the event report sent by UPF. After receiving the event report, the PCF will send the event report to the TSCTSF, and finally the TSCTF will send it to the AF.
  • the subscription event is triggered, including at least one of the following:
  • the delay of the data stream is greater than or equal to the delay threshold corresponding to the subscription event
  • the delay difference of the data stream is greater than or equal to the delay difference threshold corresponding to the subscription event
  • the timer for the subscription event arrives
  • the delay of the flow triggers the subscription event.
  • the network delay will not exceed the maximum delay difference that the data flow can tolerate. However, during the transmission process, the data flow may be affected due to fluctuations in network conditions, etc.
  • the delay difference will increase to be greater than or equal to the delay difference threshold of the subscription event, which means that the delay difference of the data flow triggers the subscription data.
  • the timer for subscribing to events can be a periodic timer. If the timer expires, PCF will send an event report to TSCTSF. If the timer has not expired, PCF will not send an event report to TSCTSF.
  • PCF will periodically send event reports to TSCTSF.
  • the delay threshold provided by the foregoing embodiments can be an alarm delay threshold determined based on the maximum tolerated delay or a stop delay threshold for stopping transmission of the data flow.
  • a reminder delay threshold can also be configured, for example, if When the delay of the data flow exceeds the alarm delay threshold and approaches the stop delay threshold, due to network fluctuations, the delay of the data flow may shrink and return to below the alarm threshold.
  • the delay difference threshold provided in the above embodiment is an alarm delay difference threshold formulated based on the maximum tolerated delay difference or a stop delay difference threshold when the data stream stops transmitting.
  • the reminder time can also be configured. Delay threshold. For example, if the actual delay difference of the data flow exceeds the alarm delay difference threshold or approaches the stop delay difference threshold, due to network fluctuations, the delay difference of the data flow may shrink, and the delay difference may be reduced to less than the alert delay. difference threshold.
  • the subscription request contains the immediate reporting flag, it is equivalent to the subscription event being triggered, so an event report needs to be reported.
  • the subscription event when the subscription event is triggered, it may also include at least one of the following:
  • the delay of the data flow is less than or equal to the reminder delay threshold
  • the delay difference of the data flow is less than or equal to the alert delay difference threshold.
  • the method further includes:
  • the PCC rule is updated.
  • updating the PCC rule when the subscription event is triggered includes:
  • latency-related subscription events are triggered to increase or decrease the QoS authorized by PCC rules.
  • PCC rules will limit the fifth generation mobile communication QoS identifier (5G QoS Identifier, 5QI).
  • the QoS authorized by the PCC rule can be improved by increasing the 5QI, thereby improving the QoS of the data flow identified by the XRM group.
  • the subscription request includes: event reporting mode information
  • the reporting mode of the event report indicated by the event reporting mode information includes at least one of the following:
  • the event report includes: the delay and/or delay difference of the data flow and/or the resource allocation status of the data flow, etc.
  • the periodic reporting mode is: event reports of subscribed events will be sent to TSCTSF periodically, and TSCTSF will forward them to AF. If the periodic reporting mode is adopted, the PCF side can configure a timer for the periodic reporting mode. When the timer expires, the event report corresponding to the subscription event will be submitted from the PCF to the TSCTSF.
  • the triggered reporting mode is: after the subscription event is triggered, TSCTSF will receive the event report sent by PCF. For example, when the delay of the data flow reaches the threshold, or the delay difference reaches the threshold, the TSCTSF will receive the event report submitted by the PCF.
  • the event reporting mode information may include an immediate reporting flag. If the immediate reporting flag is a predetermined value, it indicates that the reporting mode of the event report corresponding to the currently subscribed event is the immediate reporting mode.
  • the subscription event includes periodic information in periodic reporting mode, which means that the AF subscribes to event reports that are reported periodically. At this time, the event reporting mode information may be implicitly indicated by the period information.
  • the subscription event includes a threshold that triggers a subscription event, etc.
  • the AF subscription triggers an event report in the reporting mode.
  • the event reporting mode information may be implicitly indicated by the threshold.
  • the subscription request may include: one or bit specifically indicating the event reporting mode.
  • an embodiment of the present disclosure provides an information processing method, which is executed by AF.
  • the method includes:
  • S3110 Send an AF session creation request, where the session creation request includes a synchronization instruction and an XRM group identifier;
  • S3120 Receive a session creation response of the session creation request.
  • the AF may be provided by an or server.
  • the AF may be a server that provides XRM services.
  • the AF When the AF needs to transmit data streams with the UE, it can apply to the network side to create a session. At this time, it can send a session creation request to TSCTSF directly or through NEF.
  • the session creation request also includes: delay information and/or IP addresses of the UEs.
  • the UE of the UEs IP address is the UE that transmits the data stream of the XRM service; the XRM group identifies the XRM group, and the XRM group includes: one or XRM service that requires data stream transmission.
  • the delay information includes at least one of the following:
  • the two-way delay here is: the sum of uplink delay and downlink delay.
  • the uplink delay may be: the delay of the data flow from the UE to the network device (for example, User Plane Function (UPF)).
  • UPF User Plane Function
  • the downlink delay can be: the delay of the data flow from the network device to the UE.
  • the delay difference of the data flow here can be: the delay difference of the data flow.
  • the delay difference of the data flow here may include: the delay difference of the upstream data flow identified by the same XRM group, and/or the delay difference of the downlink data flow identified by the same XRM group.
  • the session creation request further includes at least one of the following:
  • the synchronization indication is carried in the session creation request and can be used to indicate that the current request to create a session is a time-sensitive session.
  • One of the data streams involved in this session is a TSC data stream, that is, these data streams are very sensitive to delay. And it is very sensitive to the delay difference of data flow.
  • the TSCTSF After the TSCTSF receives the session creation request containing the synchronization indication, if the session creation request contains the synchronization indication, the TSCTSF will provide time synchronization services for the data stream involved in the session created by the AF request (that is, the AF session).
  • the TSCTSF receives the synchronization indication, it will send the synchronization indication to the PCF.
  • the PCF After receiving the synchronization indication, the PCF knows that the AF session currently requested to be created involves TSC data flows. If there is a data flow, it determines When controlling the routing path strategy, you can consider allowing data flows to use the same routing path as much as possible to reduce the transmission delay difference.
  • the same UPF can be used preferentially for transmission and/or monitoring.
  • the synchronization indication may not be transmitted to the PCF.
  • the PCF directly determines whether the currently involved data flow is a TSC data flow based on the delay information. If it is a TSC data flow, it also needs to provide time synchronization for this data flow. Implement appropriate strategies based on business considerations.
  • the flow description may include an Information Element (IE) describing the attribute information of the data flow.
  • IE Information Element
  • the QoS information and requirements can be used by core network elements to determine the maximum delay that each data flow can tolerate and/or the maximum delay difference that the data flow can tolerate.
  • the QoS information and requirements include at least one of the following:
  • the QoS parameters may include at least one of the following:
  • Flow direction for example, one or data flow involved in the AF can be an upstream data flow and/or a downstream data flow, if the flow direction of the upstream data flow is upward; if the flow direction of the downstream data flow is downward;
  • Upstream data stream arrival time (Burst Arrival Time at UE);
  • Downstream data flow arrival time (Burst Arrival Time at UPF);
  • the duration of the data stream (Survival Time).
  • the alternative service requirements may include at least one of the following parameters:
  • Optional QoS-related parameter set which includes one or optional QoS parameter or QoS reference.
  • the QoS reference may also be used to determine any reference information that determines the QoS of the data flow.
  • QoS may be part of alternative business requirements.
  • the method further includes:
  • the method further includes:
  • TSCTSF will receive the notification message that the subscription event is triggered.
  • the notification message may include: event reporting.
  • the event report may include: an event report of resource status allocation and/or an event report related to latency.
  • the event report of the resource allocation status may include: an event report related to the delay of the data flow, and/or an event report related to the delay of the data flow.
  • AF receives the event report and determines whether it needs to continue to send AF's session creation request, or delay the creation or update of the session request; on the other hand, AF can monitor the transmission status of AF session data flow in the network through the event report.
  • the sending of the AF session creation request includes:
  • the session creation request of the AF is sent to the TSCTSF according to the address of the TSCTSF.
  • the AF if the AF stores the address of the TSCTSF, it means that the AF is trusted by the TSCTSF. In this way, the AF can directly exchange information with the TSCTSF based on the address of the TSCTSF.
  • the sending of the AF session creation request includes:
  • a session creation request of the AF is sent to the network opening function NEF, where the session creation request is used to be forwarded by the NEF to the TSCTSF.
  • AF may not be able to communicate directly with TSCTSF. Then AF sends the session creation request to NEF and forwards the response and/or update message of TSCTSF through NEF.
  • an embodiment of the present disclosure provides an information processing method, which is executed by NEF, and the method further includes:
  • S4110 Receive a session creation request from the application function AF, where the session creation request includes a synchronization indication and an XRM group identifier;
  • S4120 Obtain the address of the TSCTSF that receives the session creation request
  • S4130 Send the session creation request to the TSCTSF according to the address of the TSCTSF.
  • One or more data streams involved in the session created by the AF request may be TSC data streams.
  • the XRM group identifier is the identifier of the XRM service involved in the request to create a session.
  • the XRM group identifier may include identifiers of one or more XRM services. In short, the XRM group identifier can know multiple data flows within an XRM business group.
  • the XRM service involved in the XRM group identification needs to be transmitted by a UE group.
  • the one UE group may include one or more UEs.
  • the UEs IP address may include: the UE's Internet Protocol (Internet Protocol, IP) address.
  • the session creation request also includes: delay information and/or UEs IP addresses.
  • the obtaining the address of the TSCTSF that receives the session creation request includes:
  • the NEF can receive the session creation request sent by AF. After NEF receives the session creation request, if NEF locally stores the address of TSCTSF, NEF directly sends the session creation request to TSCTSF according to the locally stored TSCTSF.
  • the AF identifier and/or the XRM group identifier can be mapped to the DNN and/or network slice identifier according to the AF identifier and/or the XRM group identifier and the mapping relationship information.
  • the DNN and/or network slice identification may further be mapped to the address of the TSCTSF.
  • the mapping relationship information may indicate at least one of the following:
  • mapping relationship between the AF identifier and the network slice identifier
  • mapping relationship between XRM group identifiers and DNN The mapping relationship between XRM group identifiers and DNN
  • mapping relationship between XRM group identifiers and network slice identifiers
  • mapping relationship between the network slice identifier and the address of the TSCTSF is the mapping relationship between the network slice identifier and the address of the TSCTSF.
  • the network slice identifier includes but is not limited to: Single Network Slice Selection Assistance Information (S-NSSAI).
  • S-NSSAI Single Network Slice Selection Assistance Information
  • NEF does not configure the address of TSCTSF locally, it can determine the address of TSCTSF through the above method, and exchange information between AF and TSCTSF.
  • the method further includes:
  • NEF Since AF sends a session creation request to TSCTSF through NEF, NEF will receive the session creation response sent by TSCTSF and send the session creation response to AF.
  • the method further includes:
  • the notification message may include an event report, and the event report is carried in the notification message and sent to the AF.
  • the AF can realize the transmission status of one or data stream involved in the XRM service in the network based on the notification message sent by the NEF.
  • this embodiment of the present disclosure provides an XRM business processing method, which may include:
  • AF sends an AF session creation request to TSCTSF.
  • the AF session creation request provides synchronization instructions, delay information, and XRM group identification.
  • the delay information includes but is not limited to: uplink delay, downlink delay, two-way delay or delay difference.
  • AF may directly send an AF session creation request to TSCTSF, or send an AF session creation request to TSCSF through NEF.
  • TheTSCTSF calculates the request packet delay budget (Packet Delay Budge, PDB) based on the received synchronization instructions, delay information, group ID, UE address, AF ID, flow description, and received QoS information and requirements.
  • the group ID is one of the aforementioned XRM group identifiers, and the UE address can constitute one of the UEs IP addresses.
  • TSCTSF can subscribe to synchronization-related delays from PCF, such as 5G end-to-end delay or delay difference, by triggering Npcf_PolicyAuthorization_Create or Npcf_PolicyAuthorization_Subscribe request.
  • the delay subscribed from PCF here can be: the delay of actual transmission of the data stream.
  • the address of TSCTSF may be configured locally in NEF, PCF and/or trusted AF, or discovered and selected through the Network Respository Function (NRF).
  • NEF uses the group ID and/or AF ID to determine the DNN/and/or S-NSSAI, and uses the DNN and/or S-NSSAI to discover the address of the TSCTSF from the Network Repository Function (NRF).
  • the AF uses Nnef_AFsessionWithQoS_Create to send AF's session creation request to TSCTSFF to request to reserve resources for the AF session.
  • the AF session creation request may include: synchronization indication, delay information, group ID, application ID, UE address, one or more Data flow description or external application identifier, QoS reference, QoS parameters, alternative business requirements, DNN, S-NSSAI) to NEF, and sent by NEF to TSCTSF.
  • AF can directly send an AF session creation request to TSCTSF.
  • the AF sends an AF session resource request, for example, through a Nnef_AFsessionWithQoS_Create request to create an AF request.
  • AF carries XRM service information in the request message.
  • XRM service information includes synchronization instructions, delay information, application ID, group ID, UE address, one or data flow description, S-NSSAI and/or QoS parameters and other corresponding information.
  • This group ID can be used to identify all data flows in the XRM service group.
  • the delay information may include: uplink delay, downlink delay, two-way delay, end-to-end delay and/or delay difference.
  • the AF can provide the following separate QoS parameters: requested 5GS delay (optional), requested priority, requested guaranteed bit rate, and requested maximum bit rate.
  • requested 5GS delay optional
  • requested priority can be an optional parameter.
  • AF can also provide the following optional QoS parameters:
  • an optional set of QoS-related parameters may be provided.
  • NEF decides to call TSCTSF to interact with PCF based on the request to trigger PCF to generate PCC rules or activate predefined PCC rules through TSCTSF.
  • NEF includes the received synchronization instructions, delay information, group ID, application ID, individual QoS parameters, QoS reference and other information into the QoS related parameter set in the Ntsctsf_QoSandTSCAssistance_Create request message, and forwards the Ntsctsf_QoSandTSCAssistance_Create request message to TSCTSF.
  • TSC assistance (Assistance) information can be used by TSCTSF to provide time synchronization services to data streams.
  • the information content of the TSC auxiliary information can be shown in Table 1:
  • DT-TT can be: Device-side TSN translator (DT-TT).
  • TSN is Time Sensitive Network (TSN).
  • NW-TT can be: network-side time-sensitive network adapter (Network-side TSN translator, NW-TT).
  • the AF can use the ntsctsf_qsandtscassistance_create request message to directly interact with the TSCTSF to request to reserve resources for the AF session.
  • the address of the TSCTSF can be pre-configured locally in NEF, PCF and Trusted AF, or discovered and selected through NRF.
  • each DNN and/or S-NSSAI is configured with one TSCTSF.
  • NEF uses the group ID and/or AF identifier to determine the DNN/S-NSSAI, and uses the DNN/S-NSSAI to discover the TSCTSF from the NRF.
  • TSCTSF calculates the requested PDB based on the received synchronization indication, delay information, group ID, UE address, AF identifier, one or flow description(s), and received QoS information and requirements.
  • the TSCTSF has the address of the PCF to which the given UE is connected associated with the data flow involved in the XRM service.
  • TSCTSF interacts with PCF by triggering Npcf_PolicyAuthorization_Create/Update request and provides synchronization indication, delay information, group ID, UE address, AF identification, flow description(s), QoS reference, QoS parameters and alternative Business needs.
  • TSCTSF does not have the address of the PCF to which a given UE is connected associated with the data flow involved in the Received request message for personal QoS and alternative QoS related parameters Npcf_PolicyAuthorization_Create PCF.
  • TSCTSF has a discovery function, and the discovery function may include: TSCTSF discovers PCF through information interaction with NRF.
  • TSCTSF can subscribe to synchronization-related delays from PCF by sending Npcf_PolicyAuthorization_Create or Npcf_PolicyAuthorization_Subscribe requests.
  • TSCTSF receives any of the following individual QoS parameters from NEF: flow direction, burst arrival time, period, time domain, and time to live.
  • TSCTSF determines the TSC assist container and sends the TSC assist container to PCF along with the requested PDB and other QoS parameters received in the Npcf_PolicyAuthorization_Create/Update request.
  • PCF determines whether the request is authorized and notifies TSCTSF if the request is not authorized.
  • PCF is responsible for formulating policies and subscribing to event reports requested by AF or TSCTSF. For example, PCF subscribes to UPF for synchronization-related delays. For example, if PCF triggers a subscription or receives a subscription from TSCTSF), PCF may trigger QoS monitoring of a specific data flow to obtain the end-to-end delay and calculate the delay difference of the data flow.
  • PCF initiates an SM policy association modification request to SMF to subscribe to the event. Based on QoS measurements based on the QoS monitoring policy provided by PCF, SMF generates QoS monitoring configurations for UPF and RAN (if required). Once PCF receives the notification, the delay related to the notification and synchronization will be synchronized by PCF to TSCTSF.
  • PCF obtains the required QoS parameters based on the information provided by TSCTSF, determines whether to allow this QoS flow based on PCF configuration, and notifies TSCTSF of the result.
  • the QoS flow may be one of the aforementioned data flows associated with the XRM group identifier.
  • the PCF derives an alternative QoS parameter set from one or QoS reference parameters, or determines an alternative QoS related parameter set based on the alternative service requirements and the requested PDB.
  • the optional QoS parameter set or alternative QoS related parameter set here can be used for PCF specified policies.
  • the PCF sets the PDB and MDBV based on the request PDB and burst size received from the TSCTSF. If the requested PDB is not provided, PCF will determine the PDB that matches the QoS reference. PCF also sets the GBR and MBR of PCC rules (or PCC rules) based on the PDB sent by TSCTSF. PCF MAY use the request priority from AF to determine the priority of a data stream associated with the requested AF session. The QoS parameter values specified by TSCTSF will replace the default values of 5QI.
  • PCF interacts with TSCTSF by triggering the Npcf_PolicyAuthorization_Create/Update response to inform TSCTSFAF whether the creation request is authorized. If the request is not authorized, or the required QoS is not allowed, PCF will respond to TSCTSF with a Result value indicating the reason for the failure.
  • ntsctsf_qsandtscassistance_create session creation response to NEF, which will include: transaction reference ID and/or session creation result.
  • the session creation result indicates whether the session creation request is authorized. If the session creation request is authorized, the session will be created by the network, otherwise the session will not be created by the network.
  • the TSCTSF can directly send the ntsctsf_qsandtscassistance_create session creation response to the AF.
  • the session creation response can include the transmission related identification (Transaction Reference ID) and the session creation result.
  • the session creation result indicates whether the request is authorized.
  • the session creation result indicates whether the session creation request is authorized. If the session creation request is authorized, the session will be created by the network, otherwise the session will not be created by the network.
  • 10.TSCTSF sends the Npcf_PolicyAuthorization_Subscribe message to PCF to subscribe to the resource allocation status, and/or subscribe to the synchronization-related delay.
  • Subscription event triggers event reports can be transmitted to PCF by UPF.
  • UPF triggers a Notify message and reports measured information (for example, end-to-end delay, delay difference) to PCF.
  • measured information for example, end-to-end delay, delay difference
  • UPF detects a delay reaching event
  • an event report will be triggered.
  • the delay or delay difference reaches a corresponding threshold, or the periodic timer times out (that is, it detects that a subscription event of a periodic subscription is triggered).
  • PCF can send these delay-related event reports to TSCTSF. For example, if PCF finds that the delay difference reaches the delay difference threshold provided by AF, PCF notifies TSCTSF that these subscription events are triggered.
  • the PCF can adjust the relevant PCC rules for a data flow, for example, downgrade or upgrade the relevant QoS authorization.
  • PCF sends an Npcf_PolicyAuthorization_Notify message to TSCTSF to notify that the subscription event is triggered.
  • the specific notification subscription event can be as follows: As shown in step 11.
  • TSCTSF directly sends the Ntsctsf_QoSandTSCAssistance_Notify message to the AF.
  • NEF sends the Nnef_AFsessionWithQoS_Notify message to AF, carrying the event report provided by PCF.
  • AF can send a Nnef_AFsessionWithQoS_Revoke request to NEF.
  • NEF authorizes the revocation request and triggers the Ntsctsf_QoSandTSCAssistance_Delete/Unsubscribe and/or Npcf_PolicyAuthorization_Delete and Npcf_PolicyAuthorization_Unsubscribe operations on the AF create request.
  • an embodiment of the present disclosure provides an XRM business processing device, wherein the device includes:
  • the first receiving module 110 is configured to receive a session creation request of the application function AF, wherein the session creation request includes: synchronization indication and XRM group identification UEs IP address;
  • the first sending module 120 is configured to send the synchronization indication and the XRM group identification and/or the UEs IP address to the policy control function PCF.
  • This device may be included in the TSCTSF.
  • the first receiving module 110 and the first sending module 120 may be program modules. After the program modules are executed by a processor, the above operations can be implemented.
  • the first receiving module 110 and the first sending module 120 may be software and hardware combined modules, and the software and hardware combined modules may include: an editable array; the editable array includes but is not limited to: Field programmable arrays and/or complex programmable arrays.
  • the first receiving module 110 and the first sending module 120 may be pure hardware modules; but the pure hardware modules are not limited to application specific integrated circuits.
  • the synchronization indication and the XRM group identifier are used for the PCF to generate policy control and charging PCC rules or activate predefined PCC rules.
  • the session creation request also includes: delay information and/or user equipment UEs IP address;
  • the first sending module 120 is also configured to send the delay information and/or the UEs IP address to the PCF.
  • the device further includes:
  • a calculation module configured to calculate a packet delay budget PDB based on the delay information
  • the first sending module 120 is configured to send the PDB to the PCF.
  • the delay information includes at least one of the following:
  • the session creation request further includes at least one of the following:
  • the QoS information and requirements include at least one of the following:
  • the PDB and the synchronization indication, the XRM group identifier and/or the UEs IP address and the delay information are included in the authorization creation or update request and sent to the PCF.
  • the first receiving module 110 is further configured to receive a response to the authorization creation or update request
  • the first sending module 120 is further configured to send a session creation response to the session creation request according to the response to the authorization creation or update request.
  • the first sending module 120 is further configured to send a subscription request to the PCF, where the subscription request is used to request a subscription to an event report.
  • the first receiving module 110 is further configured to receive the event report sent by the PCF;
  • the first sending module 120 is further configured to send an event report to the AF, where the notification message includes the event report.
  • the address of the TSCTSF is pre-stored on the network opening function NEF, PCF or trusted AF.
  • the subscription request includes: event reporting mode information;
  • the reporting mode of the event report indicated by the event reporting mode information includes at least one of the following:
  • an embodiment of the present disclosure provides an information processing device, wherein the device includes:
  • the second receiving module 210 is configured to receive the synchronization indication and the XRM group identifier sent by the TSCTSF;
  • the PCC rule module 220 is configured to generate policy control and charging PCC rules or activate predefined PCC rules according to the synchronization indication and the XRM group identifier.
  • This device may be included in the PCF.
  • the second receiving module 210 and the PCC rule module 220 may be program modules. After the program module is executed by the processor, the above operations can be implemented.
  • the second receiving module 210 and the PCC rule module 220 may be software and hardware combined modules, and the software and hardware combined modules may include: editable arrays; the editable arrays include but are not limited to: field programmable arrays and/or complex programmable arrays.
  • the second receiving module 210 and the PCC rule module 220 may be pure hardware modules; but the pure hardware modules are not limited to application specific integrated circuits.
  • the second receiving module 210 is configured to receive the synchronization indication and the XRM group identifier sent by the TSCTSF, as well as delay information and/or UEs IP addresses.
  • the device further includes:
  • the PCC rule module is configured to generate policy control and charging PCC rules or activate predefined PCC rules for the data flow involved in the XRM group identifier and/or the UEs IP address according to the synchronization indication and the delay information. .
  • the second receiving module 210 is configured to receive an authorization creation or update request including the synchronization indication, the delay information, the XRM group identifier and/or the UEs IP address. ;
  • the device also includes:
  • the second sending module is configured to send a response to the authorization creation or update request to the TSCTSF.
  • the PCC rule module is configured to: when the authorization creation or update request also includes the PDB calculated by the TSCTSF based on the delay information, based on the synchronization indication, the PDB, the Use the XRM group identifier and/or the UES IP address to generate the PCC rule or activate the predefined PCC rule;
  • the PDB is calculated based on the delay information included in the authorization creation or update request, and the PDB calculated based on the PCF,
  • the XRM group identifier and/or the UEs IP address generates the PCC rule or activates the predefined PCC rule.
  • the PCC rule module is configured to set the PDB and burst data volume of the data flow according to the PDB and maximum burst data volume MDVB included in the authorization creation or update request; according to the data flow
  • the PDB and the burst data volume, the XRM group identifier and/or the UEs IP address generate PCC rules or activate predefined PCC rules.
  • the device further includes:
  • Authorization module configured to determine whether the session is authorized to be created.
  • the second receiving module 210 is further configured to receive a subscription request; wherein the subscription request is used to request a subscription to an event report.
  • the second sending module is further configured to send an event report to the TSCTSF when the delay difference of the data flow triggers a subscription event according to the subscription request; and/or, according to the Subscription request: when the delay of the data flow triggers a subscription event, send an event report to the TSCTSF.
  • the second sending module is further configured to subscribe to the user plane function UPF for the delay of the data flow according to the subscription request;
  • a delay difference module configured to determine the delay difference according to the delay of the data flow provided by the UPF
  • the second sending module is further configured to send an event report to the TSCTSF when the delay difference triggers a subscription event.
  • the second sending module is further configured to subscribe to the UPF for the delay difference of the data flow according to the subscription request; when the delay of the data flow provided by the UPF When a subscription event is triggered, an event report is sent to the TSCTSF.
  • the second sending module is configured to subscribe to the user plane function UPF for the delay of the data stream according to the subscription request; when the delay of the data stream provided by the UPF triggers a subscription event When, an event report is sent to the TSCTSF.
  • the second sending module is further configured to send a subscription request to the UPF according to the subscription request; wherein the subscription request includes: a subscription to a subscription event triggered by the delay difference of the data stream request; and/or, the delay of the data flow triggers a subscription request for a subscription event;
  • the second receiving module 210 is also configured to receive a notification message sent by the UPF that triggers a subscription event;
  • the second sending module is further configured to send an event report to the TSCTSF according to the notification message.
  • the subscription event is triggered, including at least one of the following:
  • the delay of the data flow is greater than or equal to the delay threshold corresponding to the subscription event
  • the delay difference of the data stream is greater than or equal to the delay difference threshold corresponding to the subscription event
  • the timer for the subscription event arrives
  • the subscription request includes: event reporting mode information;
  • the reporting mode of the event report indicated by the event reporting mode information includes at least one of the following:
  • the device further includes:
  • An update module configured to update the PCC rule when the subscription event is triggered.
  • the update module is configured to increase the QoS authorized by the PCC rule when the subscription event is triggered; or, when the subscription event is triggered, reduce the QoS authorized by the PCC rule. QoS.
  • an embodiment of the present disclosure provides an information processing device, wherein the device includes:
  • the third sending module 310 is configured to send a session creation request of AF, where the session creation request includes a synchronization indication and an XRM group identifier;
  • the third receiving module 320 is configured to receive a session creation response of the session creation request.
  • This device may be included in the PCT.
  • the third sending module 310 may be a program module. After the program module is executed by the processor, the above operations can be implemented.
  • the third sending module 310 may be a combined software and hardware module.
  • the combined software and hardware module may include: an editable array; the editable array includes but is not limited to: a field programmable array and/or a complex Programmable array.
  • the third sending module 310 may be a pure hardware module; the pure hardware module is but not limited to an application specific integrated circuit.
  • the session creation request also includes: delay information and/or IP addresses of the UEs.
  • the delay information includes at least one of the following:
  • the session creation request further includes at least one of the following:
  • the QoS information and requirements include at least one of the following:
  • the third receiving module is further configured to receive a notification message sent by the TSCTSF when the subscription event is triggered.
  • the third sending module 310 is further configured to send the session creation request of the AF to the TSCTSF according to the address of the TSCTSF when the AF stores the address of the TSCTSF.
  • the third sending module 310 is further configured to send a session creation request of the AF to the network opening function NEF when the AF does not store the address of the TSCTSF, wherein the session creation request , for forwarding by the NEF to the TSCTSF.
  • an embodiment of the present disclosure provides an information processing device, wherein the device further includes:
  • the fourth receiving module 410 is configured to receive a session creation request sent by the AF, wherein the session creation request includes the synchronization indication and the XRM group identification UEs IP address;
  • the acquisition module 420 is configured to obtain the address of the TSCTSF that receives the session creation request;
  • the fourth sending module 430 is configured to send the session creation request to the TSCTSF according to the address of the TSCTSF.
  • the information processing device may be included in the NEF.
  • the fourth receiving module 410, the obtaining module 420 and the fourth sending module 430 may be program modules. After the program modules are executed by the processor, the above operations can be implemented.
  • the fourth receiving module 410, the obtaining module 420 and the fourth sending module 430 may be software and hardware combination modules, and the software and hardware combination modules may include: an editable array; the editable array includes but does not Limited to: field programmable arrays and/or complex programmable arrays.
  • the fourth receiving module 410, the obtaining module 420 and the fourth sending module 430 may be pure hardware modules; the pure hardware modules are but not limited to application specific integrated circuits.
  • the session creation request also includes: delay information and/or user equipment UEs IP address.
  • the acquisition module 420 is configured to query the address of the TSCTSF pre-stored by the NEF; or, add the identity of the AF and/or the XRM group identity and/or included in the session creation request.
  • UEs IP addresses are mapped to the network name DNN and/or network slice identifier, and the address of the TSCTSF is discovered based on the DNN and/or network slice identifier mapping.
  • the fourth receiving module 410 is configured to receive a session creation response of the session creation request
  • the fourth sending module 430 is also configured to send the session creation response to the AF.
  • the fourth receiving module 410 is configured to receive the notification message sent by the TSCTSF when the subscription event is triggered;
  • the fourth sending module 430 is configured to send the notification message to the AF.
  • An embodiment of the present disclosure provides a communication device, including:
  • Memory used to store instructions executable by the processor
  • the processor is configured to execute the information processing method provided by any of the foregoing technical solutions.
  • the processor may include various types of storage media, which are non-transitory computer storage media that can continue to store information stored thereon after the communication device is powered off.
  • the communication device includes: a UE or a network element, and the network element may be any one of the aforementioned first to fourth network elements.
  • the processor may be connected to the memory through a bus or the like, and be used to read the executable program stored on the memory, for example, at least one of the methods shown in FIGS. 2 to 8 .
  • FIG. 13 is a block diagram of a UE 800 according to an exemplary embodiment.
  • UE 800 may be a mobile phone, computer, digital broadcast user equipment, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.
  • UE 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communications component.
  • Component 816 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communications component.
  • a processing component 802 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communications component.
  • I/O input/output
  • Processing component 802 generally controls the overall operations of UE 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 802 may include a processor 820 to execute instructions to generate all or part of the steps of the method described above.
  • processing component 802 may include a module or module to facilitate interaction between processing component 802 and other components.
  • processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
  • Memory 804 is configured to store various types of data to support operations at UE 800. Examples of this data include instructions for any application or method operating on the UE 800, contact data, phonebook data, messages, pictures, videos, etc.
  • Memory 804 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EEPROM erasable programmable read-only memory
  • EPROM Programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory, magnetic or optical disk.
  • Power supply component 806 provides power to various components of UE 800.
  • Power component 806 may include a power management system, a power supply, and other components associated with generating, managing, and distributing power to UE 800.
  • Multimedia component 808 includes a screen that provides an output interface between the UE 800 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes a touch sensor to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide action.
  • multimedia component 808 includes a front-facing camera and/or a rear-facing camera. When the UE 800 is in an operating mode, such as shooting mode or video mode, the front camera and/or rear camera can receive external multimedia data.
  • Each front-facing camera and rear-facing camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • Audio component 810 is configured to output and/or input audio signals.
  • audio component 810 includes a microphone (MIC) configured to receive external audio signals when UE 800 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signal may be further stored in memory 804 or sent via communication component 816 .
  • audio component 810 also includes a speaker for outputting audio signals.
  • the I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
  • Sensor component 814 includes one or more sensors for providing various aspects of status assessment for UE 800.
  • the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the UE 800, and the sensor component 814 can also detect the position change of the UE 800 or a component of the UE 800. , the presence or absence of user contact with the UE 800, the orientation or acceleration/deceleration of the UE 800 and the temperature change of the UE 800.
  • Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communication between UE 800 and other devices.
  • UE 800 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communications component 816 also includes a near field communications (NFC) module to facilitate short-range communications.
  • NFC near field communications
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • UE 800 may be configured by one or application specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the above method.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • DSPD digital signal processing device
  • PLD programmable logic device
  • FPGA field programmable gate array
  • controller microcontroller, microprocessor or other electronic component implementation for performing the above method.
  • a non-transitory computer-readable storage medium including instructions such as a memory 804 including instructions, executable by the processor 820 of the UE 800 to generate the above method is also provided.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
  • an embodiment of the present disclosure shows the structure of an access device.
  • the communication device 900 may be provided as a network side device.
  • the communication device may be various network elements such as the aforementioned access network element and/or network function.
  • communications device 900 includes a processing component 922, which further includes a processor, and memory resources represented by memory 932 for storing instructions, such as application programs, executable by processing component 922.
  • the application program stored in memory 932 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 922 is configured to execute instructions to perform any of the foregoing methods applied to the access device, for example, the methods shown in any one of Figures 2 to 8.
  • Communication device 900 may also include a power supply component 926 configured to perform power management of communication device 900, a wired or wireless network interface 950 configured to connect communication device 900 to a network, and an input-output (I/O) interface 958 .
  • the communication device 900 may operate based on an operating system stored in the memory 932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

Landscapes

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

Abstract

本公开实施例提供一种信息处理方法及装置、通信设备及存储介质。由TSCTSF执行的信息处理方法可包括：接收应用功能AF的会话创建请求，其中，所述会话创建请求包括同步指示和XRM组标识；将所述同步指示以及所述XRM组标识发送给策略控制功能PCF。

Description

扩展现实媒体业务处理方法及装置、通信设备及存储介质 技术领域
本公开涉及无线通信技术领域但不限于无线通信技术领域，尤其涉及一种扩展现实(Extended Reality and Media，XRM)业务方法及装置、通信设备及存储介质。
背景技术
移动媒体类服务、增强现实(Augment Reality，AR)、虚拟现实(Virtual Reality，VR)等扩展现实(Extended Reality，XR)业务、云游戏、基于视频的机器或无人机远程控制等业务。
XR业务涉及多模态数据流。多模态数据，是描述同一业务或应用的同一个设备或不同设备的输入数据或输出数据。
多模态数据中的各数据流往往具有一定甚至很强的相关性，比如，音频流和视频流的同步，触觉数据和视觉数据的同步等。这类媒体业务的数据流本身，各数据流之间，以及这些业务数据流对网络传输的需求，都存在一些共性特征，这些特性的有效识别和利用将更有助于网络和业务的传输、控制，也更有助于业务保障和用户体验。
发明内容
本公开实施例提供一种XRM信息处理方法及装置、通信设备及存储介质。
本公开实施例第一方面提供一种XRM业务处理方法，其中，由时间敏感通信和时间同步功能(Time Sensitive Communication and Time Synchronization Function，TSCTSF)执行，所述方法包括：
接收应用功能(Application Function，AF)的会话创建请求，其中，所述会话创建请求包括：同步指示和XRM组标识时延信息；所述会话创建请求还包括XRM组标识和/或用户设备UEs UP地址；
将所述同步指示以及所述XRM组标识发送给策略控制功能(Policy Control Function，PCF)。
本公开实施例第二方面提供一种信息处理方法，其中，由PCF执行，所述方法包括：
接收TSCTSF发送的同步指示以及XRM组标识；
根据所述同步指示和所述XRM组标识，生成策略控制和计费(Policy Control and Charging，PCC)规则或者激活预定义的PCC规则。
本公开实施例第三方面提供一种信息处理方法，其中，由AF执行，所述方法包括：
发送AF的会话创建请求，所述会话创建请求包括同步指示和XRM组标识；
接收所述会话创建请求的会话创建响应。
本公开实施例第四方面提供一种信息处理方法，其中，由网络开放功能(Network Exposure Function，NEF)执行，所述方法还包括：
接收应用功能AF的会话创建请求，其中，所述会话创建请求包括同步指示XRM组标识；
获取接收所述会话创建请求的TSCTSF的地址；
根据所述TSCTS F的地址，将所述会话创建请求发送给所述TSCTSF。
本公开实施例第五方面提供一种扩展现实业务媒体XRM业务处理装置，其中，所述装置包括：
第一接收模块，被配置为接收应用功能AF的会话创建请求，其中，所述会话创建请求包括：同步指示以及XRM组标识；
第一发送模块，被配置为将所述同步指示以及所述XRM组标识发送给策略控制功能PCF。
本公开实施例第六方面提供一种信息处理装置，其中，所述装置包括：
第二接收模块，被配置为接收TSCTSF发送的同步指示XRM组标识；
PCC规则模块，被配置为根据所述同步指示和所述XRM组标识，生成PCC规则或者激活预定义的PCC规则。
本公开实施例第七方面提供一种信息处理装置，其中，所述装置包括：
第三发送模块，被配置为发送AF的会话创建请求，所述会话创建请求包括同步指示和XRM组标识；
第三接收模块，被配置为接收所述会话创建请求的会话创建响应。
本公开实施例第八方面提供一种信息处理装置，其中，所述装置还包括：
第四接收模块，被配置为接收应用功能AF的会话创建请求，其中，所述会话创建请求包括同步指示和XRM组标识；
获取模块，被配置为获取接收所述会话创建请求的TSCTSF的地址；
第四发送模块，被配置为根据所述TSCTSF的地址，将所述会话创建请求发送给所述TSCTSF。
本公开实施例第九方面提供一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够由所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如前述第一方面至第四方面任意一个方面提供的信息处理方法。
本公开实施例第十方面提供一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现前述第一方面至第四方面任意一个方面提供的信息处理方法。
本公开实施例提供的技术方案，TSCTSF会接收针对XRM业务的会话创建请求，该会话创建请求中包含同步指示XRM组标识，该同步指示以及XRM组标识可用于PCF生成PCC规则或者基于预定义的PCC规则，如此，TSCTSF会对该会话请求涉及的一个或数据流视为TSC数据流严格实现同步和控制时延，减少XRM业务涉及的一个或数据流的时延和/或时延差大的现象，提升XRM业务的业务质量。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开 实施例。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明实施例，并与说明书一起用于解释本发明实施例的原理。
图1是根据一示例性实施例示出的一种无线通信系统的结构示意图；
图2是根据一示例性实施例示出的一种信息处理方法的流程示意图；
图3是根据一示例性实施例示出的一种信息处理方法的流程示意图；
图4是根据一示例性实施例示出的一种信息处理方法的流程示意图；
图5是根据一示例性实施例示出的一种信息处理方法的流程示意图；
图6是根据一示例性实施例示出的一种信息处理方法的流程示意图；
图7是根据一示例性实施例示出的一种信息处理方法的流程示意图；
图8是根据一示例性实施例示出的一种信息处理方法的流程示意图；
图9是根据一示例性实施例示出的一种信息处理装置的结构示意图；
图10是根据一示例性实施例示出的一种信息处理装置的结构示意图；
图11是根据一示例性实施例示出的一种信息处理装置的结构示意图；
图12是根据一示例性实施例示出的一种信息处理装置的结构示意图；
图13是根据一示例性实施例示出的一种UE的结构示意图；
图14是根据一示例性实施例示出的一种通信设备的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明实施例相一致的所有实施方式。相反，它们仅是本发明实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于 确定”。
请参考图1，其示出了本公开实施例提供的一种无线通信系统的结构示意图。如图1所示，无线通信系统是基于蜂窝移动通信技术的通信系统，该无线通信系统可以包括：若干个UE 11以及若干个接入设备12。
其中，UE 11可以是指向用户提供语音和/或数据连通性的设备。UE 11可以经无线接入网(Radio Access Network，RAN)与一个或核心网进行通信，UE 11可以是物联网UE，如传感器设备、移动电话(或称为“蜂窝”电话)和具有物联网UE的计算机，例如，可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)、移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程UE(remote terminal)、接入UE(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户UE(user equipment，UE)。或者，UE 11也可以是无人飞行器的设备。或者，UE 11也可以是车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线通信设备。或者，UE 11也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
接入设备12可以是无线通信系统中的网络侧设备。其中，该无线通信系统可以是第四代移动通信技术(the 4th generation mobile communication，4G)系统，又称长期演进(Long Term Evolution，LTE)系统；或者，该无线通信系统也可以是5G系统，又称新空口(new radio，NR)系统或5G NR系统。或者，该无线通信系统也可以是5G系统的再下一代系统。其中，5G系统中的接入网可以称为NG-RAN(New Generation-Radio Access Network，新一代无线接入网)。或者，MTC系统。
其中，接入设备12可以是4G系统中采用的演进型接入设备(eNB)。或者，接入设备12也可以是5G系统中采用集中分布式架构的接入设备(gNB)。当接入设备12采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体访问控制(Media Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对接入设备12的具体实现方式不加以限定。
接入设备12和UE 11之间可以通过无线空口建立无线连接。在不同的实施方式中，该无线空口是基于第四代移动通信网络技术(4G)标准的无线空口；或者，该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
XRM业务需要第五代移动通信系统(5th Generation System，5GS)综合考虑业务的相关数据流的服务质量(Quality of Service，QoS)特性，例如，与延时关联的保证比特(Guaranteed Bit Rate，GBR)数据流、保证流比特率(Guaranteed Flow Bit Rate，GFBR)、分组时延估计(Packet Delay Budget，PDB)、和/或默认最大突发数据量(Default Maximum Data Burst Volume，MDBV)等参数是否能同时满足并协同一致。XRM业务的数据流，可涉及一个UE的多个XRM业务的数据流，和/或多个 UE的数据流，这多个数据流的QoS授权与执行需要保持一致性，从能确保XRM业务的业务质量。
如图2所示，本公开实施例提供一种XRM业务处理方法，其中，由TSCTSF执行，所述方法包括：
S1110：接收AF的会话创建请求，其中，所述会话创建请求包括同步指示以及XRM组标识；
S1120：将所述同步指示以及所述XRM组标识发送给策略控制功能PCF。
在一些实施例中，所述同步指示和所述XRM组标识为所述会话创建请求必须携带的参数。
在一些场景下，时延信息和UEs IP地址是所述会话创建请求可以携带的可选参数。即在另一些实施例中，所述会话创建请求还会包括所述时延信息和/或所述UEs IP地址。此时，所述方法还包括：将所述时延信息和/或所述UEs IP地址发送给PCF。
总之，会话创建请求携带的信息，可将用于供所述PCF生成策略控制和计费(Policy Control and Charging，PCC)规则或者激活预定义的PCC规则。
AF可为位于通信运营商提供的移动通信网络的一个设备。该AF可由应用运营商提供。具体地，该AF可包括一个或多个应用服务器。
TSCTSF可为一种核心网网元(又称核心网设备)，任何执行上述操作的网元都可以称之为TSCTSF。
5GS提供时间同步业务，而TSCTSF可为提供时间同步业务的重要网元。
示例性地，若AF想要创建一个涉及多个数据流且对这多个数据流的时延差要求小或者对数据流的时延很敏感时，会向TSCTSF发送会话创建请求，如此，TSCTSF接收到AF的会话创建请求之后，可以从会话创建请求中获取该AF请求创建的会话涉及的一个或数据流的时延信息以及XRM组标识。
本公开实施例请求创建的会话涉及的多个数据流可为时间敏感通信(Time Sensitive Communication，TSC)数据流，如此，TSCTSF对TSC数据流会对时间同步业务的操作。
所述同步指示携带在所述会话创建请求中，可用于表明当前请求创建会话是时间敏感会话，针对该会话涉及的一个或多个数据流均是TSC数据流，即这些数据流对时延很敏感，且对多个数据流的时延差很敏感。
TSCTSF收到包含有所述同步指示的会话创建请求之后，若该会话创建请求中包含同步指示，TSCTSF会对该AF请求创建的会话(即AF会话)涉及的多个数据流提供时间同步业务。
示例性地，若TSCTSF收到了同步指示之后，会将同步指示发送给PCF，PCF收到同步指示之后，知道当前请求创建的AF会话涉及的都是TSC数据流，若存在多个数据流时，在确定控制路由路径的策略时，可以考虑让多个数据流尽可能采用相同的路由路径，从而减少传输时延差。
例性地，由于该XDM组标识涉及的多个数据流都是TSC数据流，可以优先使用相同的UPF进行传输和/或监控。
示例性地，TSCTSF根据AF提供的时延信息或根据XRM组标识所标识确定的时延信息为AF所请求创建会话的一个或多个数据流提供时间同步业务，以确保该会话涉及的一个或多个数据流的 时延和/或多个数据流之间的时延差。
该XRM组标识为请求创建会话涉及的XRM业务的组标识。该XRM组标识用来识别一个XRM业务组内的多个数据流。一个XRM组的多个数据流，可能归属于一个UE，或者多个UE。
示例性地，该XRM组标识可以由参与多个数据流传输可涉及一个UE组。该一个UE组可包括一个或多个UE。因此该UEs IP地址也可以用于来标识该XRM业务。
在收到时延信息和XRM组标识和/或UEs IP地址之后，TSCTSF会将该时延信息，以及所述XRM组标识和UEs IP地址中的至少一个发送给PCF。PCF是一个制定和维护各种策略的核心网功能(或称核心网设备)。
示例性地，例如，PCF收到所述时延信息以及所述XRM组标识和/或UEs IP地址之后，会制定策略控制和计费(Policy Control and Charging，PCC)规则。
PCF接收到TSCTSF发送的信息之后，可以动态生成PCC规则或者，激活预先定义的PCC规则。预先定义的PCC规则被激活后，相当于PCC规则生效，可以根据该PCC规则调度并监控对应的数据流。
在一些实施例中，所述会话创建请求，还包括：时延信息和/或用户设备UEs IP地址。若会话创建请求中包含时延信息，则说明AF自身提供了本次请求创建会话的时延信息。由于AF本次请求创建的会话涉及的XRM业务的数据流可能涉及UE组，该UE组由UEs IP地址。一个UE组包括一个或UE。
所述S1120可包括：将所述同步指示和所述XRM组标识，以及所述时延信息和/或所述UEs IP地址，发送给所述PCF。
若将时延信息发送给PCF，则PCF可以根据从TSCTSF接收的时延信息，生成PCC规则或者激活预定义的PCC规则。
在一些实施例中，所述方法还包括：
根据所述时延信息，计算PDB。
所述TSCTSF接收到所述时延信息之后，可以确定出请求创建的会话涉及的每个数据流的最大容忍时延，和/或该会话涉及的数据流的最大容忍时延差。
根据该时延信息，TSCTSF可以计算出PDB。示例性地，TSCTSF会根据时延信息，确定上行数据流的PDB(即上行PDB)和/或下行数据流的PDB(即下行PDB)。
若TSCTSF计算了PDB，则会将该PDB发送给PCF。
示例性地，TSCTSF不自行计算PDB，则会直接将时延信息和XRM组标识一同发送给PCF，由PCF自行计算PDB。在一些实施例中，TSCTSF可以将从会话创建请求中获取的所有时延信息和/或至少用于计算PDB的时延信息，发送给PCF。
在一些实施中，若TSCTSF自行计算了PDB，则可以将PDB和XRM组标识提供给PCF，当然也可以将PDB和时延信息以及XRM组标识一起发送给PCF。
在另一些实施例中，TSCTSF不会计算PDB，因此TSCTSF在接收到时延信息和XRM组标识 和/或UEs IP地址发送给PCF。
在一些实施例中，所述时延信息包括以下至少之一：
双向时延；
上行时延；
下行时延；
数据流的时延差。
此处的双向时延为：上行时延和下行时延之和。
上行时延可为：UE到网络设备(例如，用户面功能(User Plane Function，UPF))的数据流的时延。
下行时延可为：网络设备到UE的数据流的时延。
此处的数据流的时延差具体可为：多个数据流的时延差。例如，该多个数据流的时延差可包括：由同一个XRM组标识和/或UEs IP地址涉及的多个上行数据流的时延差，和/或，由同一个XRM组标识和/或UEs IP地址涉及的多个下行数据流的时延差。
在一些实施例中，所述会话创建请求还包括以下至少之一：
流描述；
服务质量(Quality of Service，QoS)信息和需求；
所述AF的标识。
流描述可包括一个或信息单元(Information Element，IE)描述了数据流的属性信息。
所述QoS信息和需求可用于核心网网元确定各个数据流能够容忍的最大时延和/或数据流能够容忍的最大时延差。
示例性地，所述QoS信息和需求包括以下至少之一：
QoS参数；
QoS参考；
备选的业务需求。
示例性地，所述QoS参数可包括以下至少之一：
请求的5GS时延；
请求的周期；
请求的最大保障比特(Guaranteed Bitrate，GB)；
请求的最大比特(Maximum Bitrate)；
流方向，例如，该AF涉及的一个或数据流可为上行数据流和/或下行数据流，若上行数据流的流方向为上行；若下行数据流的流方向为下行；
突发大小(Burst Size)；
上行数据流达到时间(Burst Arrival Time at UE)；
下行数据流达到时间(Burst Arrival Time at UPF)；
时间域(Time Domain)；
数据流的持续时长(Survival Time)。
所述备选的业务需求(Alternative Service Requirments)可包括如下参数至少之一：
AF提供的有助于确定独立QoS参数的信息；
可选QoS相关参数集合，该集合内包括一个或可选QoS参数或者QoS参考。
示例性地，QoS参考同样可用于确定确定数据流的QoS的任意参考信息。在一些实施例中，QoS可为备选的业务需求的部分内容。
当然以上仅仅是对QoS信息和需求的举例说明，具体实现时不局限于上述举例说明。
在一些实施例中，所述PDB以及所述同步指示、所述XRM组标识和/或UEs IP地址以及所述时延信息，包含在授权创建或者更新请求中发送给所述PCF。
PCF接收到该授权创建或者更新请求之后，会对AF请求的AF会话进行鉴权，在该AF会话被授权时，则会继续进行会话创建，在完成会话创建之后，该AF会话涉及的一个或数据流会基于创建的会话传输。
例如，创建AF会话包括：分配会话标识、分配会话使用的传输资源，和/或确定会话涉及的一个或数据流的路由路径。
如图3所示，本公开实施例提供一种XRM业务处理方法，其中，由TSCTSF执行，所述方法包括：
S1210：接收AF的会话创建请求，其中，所述会话创建请求包括同步指示以及XRM组标识；
S1220：向PCF发送授权创建或者更新请求，其中，所述授权创建或者更新请求包括将所述同步指示以及所述XRM组标识。
S1230：接收所述授权创建或者更新请求的响应；
S1240：根据所述授权创建或者更新请求的响应，发送所述会话创建请求的会话创建响应。
在一些实施例中，所述会话创建请求还可包括：时延信息和/或UEs IP地址。若会话创建请求包含时延信息和/或UEs IP地址，则TSCTSF会将从AF接收的时延信息和/或UEs IP地址，通过授权创建或者更新请求，与所述同步指示以及XRM组标识，一同发送给PCF。
由于TSCTSF收到了AF的会话创建请求之后，向PCF发送所述授权创建或者更新请求，会收到PCF返回的响应。且TSCTSF在接收到所述授权创建或者更新请求的响应，会进一步向AF发送会话创建响应。
所述根据所述授权创建或者更新请求的响应，发送所述会话创建请求的会话创建响应，可包括；
所述授权创建或者更新请求的响应为接受响应，向AF发送指示创建话的会话创建响应；或者，所述授权创建或者更新请求的响应为拒绝响应，向AF发送指示不创建话的会话创建响应。
在一些实施例中，所述方法还包括：
向所述PCF发送订阅请求，所述订阅请求，用于请求订阅事件报告。
示例性地，所述订阅请求，用于请求订阅包含资源分配状态和/或传送时延的事件报告。
例如，该订阅请求，用于AF会话涉及的一个或多个数据流的资源分配状态变化的事件订阅；和/或，数据流的时延的事件订阅。
订阅的事件，将发生对应的事件时，会以事件报告的形式向AF返回。
在一些实施例中，所述方法还包括：
接收所述PCF发送的所述事件报告；
向所述AF发送事件报告。
在一些实施例中，所述TSCTSF的地址预先存储在网络开放功能NEF、PCF或者可信的AF上。
若TSCTSF的地址预先存储在发送所述会话创建请求的AF上，则AF可以与TSCTSF之间直接通信。例如，该AF为被通信运营商的管理设备认定为可信设备，则可以将TSCTSF的地址直接提供给AF上。
NEF和所述PCF都属于通信运营商提供的通信网络内的网元。所述TSCTSF的地址也可以预先存储在NEF上，此时，AF可以通过NEF转发自身与TSCTSF之间的交互的信息。
另外，PCF上也可以直接存储TSCTSF的地址，方便PCF直接与TSCTSF进行通信。示例性地，PCF被TSCTSF基于发现功能发现之后，TSCTSF将其自身的地址提供给PCF。
所述TSCTSF的地址可至少包括：TSCTSF的IP地址。
在一些实施例中，TSCTSF的地址也可以不预先存储(即预先配置)所述NEF、PCF或者AF上。例如，NEF可以根据会话使用的数据网络和/或网络切片，确定出与该数据网络和/或网络切片关联的TSCTSF的地址。
例如，PCF或者NEF等可以向用户数据寄存器(User Data Repository，UDR)查询TSCTSF的地址。
当然以上仅仅是举例说明，具体实现不局限于上述举例说明。
在一些实施例中，所述订阅请求包括：事件报告模式信息；
其中，所述事件报告模式信息指示的所述事件报告的报告模式包括以下至少之一：
立即报告模式；
周期报告模式；
触发报告模式。
若是立即报告模式，则PCF收到订阅请求之后，会立即上报订阅的事件报告，该事件报告内包括：数据流的时延和/或时延差和/或数据流的资源分配状况等。
周期报告模式为：订阅事件的事件报告会被周期性发送给TSCTSF，并由TSCTSF转发给AF。若采用周期性报告模式，则PCF侧可以配置周期性报告模式的定时器，定时器失效，则订阅事件对应的事件报告会从PCF提交到TSCTSF。
触发报告模式为：订阅事件被触发之后，TSCTSF会接收到PCF发送的事件报告。例如，数据流的时延达到阈值，或者时延差达到阈值时，则TSCTSF会收到PCF提交的事件报告。
示例性地，所述事件报告模式信息可包括立即报告标志，若该立即报告标志为预定值，则说明 当前订阅事件所对应的事件报告的报告模式为立即报告模式。又示例性地，所述订阅事件包括周期报告模式的周期信息，则说明AF订阅周期性上报的事件报告。此时，该事件报告模式信息可以由周期信息隐含指示。
再示例性地，所述订阅事件包括触发订阅事件的阈值等，则说明AF订阅触发报告模式的事件报告。此时事件报告模式信息可以由阈值隐含指示。
当然所述订阅请求中可包括：一个或比特携带所述事件报告模式。
如图4所示，本公开实施例提供一种信息处理方法，其中，由PCF执行，所述方法包括：
S2110：接收TSCTSF发送的同步指示以及XRM组标识；
S2120：根据所述同步指示和所述XRM组标识，生成策略控制和计费PCC规则或者激活预定义的PCC规则。
PCF会从TSCTSF接收到需要生成或者基于PCC规则的数据流的同步指示和XRM组标识。
在一些实施例中，所述S2110可包括：在接收TSCTSF发送的同步指示以及XRM组标识的同时，还接收时延信息和UEs IP地址的至少其中之一。
S2120可包括：根据根据所述同步指示和所述XRM组标识，和/或时延信息与UEs IP地址的至少其中之一，生成PCC规则或者激活预定义的PCC规则。示例性地，PCF若未从TSCTSF接收到时延信息，可以根据XRM组标识所标识的XRM组业务，自行获取时延信息，并根据自行获取的时延信息生成PCC规则或者激活预定义的PCC规则。
该XRM组标识为请求创建会话涉及的XRM业务的组标识。该XRM组标识用来识别一个XRM业务组内的多个数据流。一个XRM组的多个数据流，可能归属于一个UE，或者多个UE。
若接收到会话创建请求之后，确定授权创建会话，则会为该会话相关的一个或数据流生成PCC规则或激活预定义的PCC规则。
在一些实施例中，所述方法还包括：
根据所述同步指示以及时延信息为所述XRM组标识和/或所述UEs IP地址涉及的数据流，生成PCC规则或激活预定义的PPC规则。
在本公开实施例中，PCF收到时延信息之后，会根据该时延信息为XRM组标识涉及的一个或数据流生成PCC规则或激活预定义的PCC规则，从而控制该数据流的通信资源分配、路由路径和/或收费情况等。
示例性地，所述接收TSCTSF发送的同步指示、和时延信息以及XRM组标识和/或UEs IP地址，包括：
接收包含所述同步指示、和所述时延信息以及所述XRM组标识和/或所述UEs IP地址的授权创建或者更新请求；
向所述TSCTSF发送所述授权创建或者更新请求的响应。
若PCF收到授权创建或者更新请求之后，会确定授权或者更新或者确定不授权或不更新，都会 向通过响应(响应消息)告知TSCTSF。
在一些实施例中，所述根据所述同步指示以及所述XRM组标识，包括：
当所述授权创建或者更新请求还包括所述TSCTSF根据所述时延信息计算的PDB时，根据所述同步指示、所述TSCTSF计算的PDB、所述XRM组标识和/或所述UES IP地址，生成所述PCC规则或者激活预定义的所述PCC规则；
或者，
当所述授权创建或者更新请求不包括所述TSCTSF根据所述时延信息计算的PDB时，根据所述授权创建或者更新请求包含的所述时延信息计算PDB，根据所述PCF计算的PDB、所述XRM组标识和/或所述UEs IP地址，生成所述PCC规则或激活预定义的所述PCC规则。
在一些实施例中，TSCTSF会根据时延信息计算PDB，在一些实施例中，TSCTSF不会根据时延信息计算PBD。
若TSCTSF计算了PDB，则PCF可能收到TSCTSF发送的PDB，如此PCF可以根据TSCTSF提供的PDB生成PCC规则或激活预定义的PCC规则。例如，PCF根据TSCTSF提供的PBD，进一步确定适用于各个数据流的PDB和突发数据量生成PCC规则或激活预定义的PCC规则。
若TSCTSF未计算PDB，则PCF将不会从TSCTSF收到PDB。如此，PCF收到时延信息之后，可以根据时延信息自行计算PDB，并根据自行计算的PDB生成PCC规则或激活预定义的PCC规则。又例如，PCF根据自身计算的PDB和突发数据量生成PCC规则或基于预定义的PCC规则。
在本公开实施例中，PCF生成PCC规则或预先定义的PCC规则被激活之后，会将与SFM相关的PCC规则的信息发送给会话管理功能(Session Management Function，SMF)。SMF会根据PCC规则进行会话创建、修改和/或释放。示例性地，SMF会根据该PCC规则调度会话资源等。
在一些实施例中，PCF执行PCC规则之后，PCF会将与UPF相关的PCC规则的信息发送给UPF，方便UPF根据PCC的策略信息进行用户面的数据流传输。
在一些实施例中，所述根据所述授权创建或者更新请求包含的PDB，根据所述时延信息为所述XRM组标识涉及的UE确定策略控制和计费PCC规则，包括：
根据所述授权创建或者更新请求包含的PDB和MDVB，确定数据流的PDB和突发数据量；
根据所述数据流的PDB和所述突发数据量，为所述XRM组标识涉及的数据流确定PCC规则。
在一些实施例中，所述方法还包括：
确定是否授权创建会话。
示例性地，PCF会根据XRM组标识对应的UE，查询UE的签约数据，确定是否授权创建与XRM组标识关联的会话。
如图5所示，本公开实施例提供一种信息处理方法，其中，由PCF执行，所述方法包括：S2210：接收订阅请求；其中，所述订阅请求，用于请求订阅事件报告。
示例性地，接收AF的订阅请求，该订阅请求，可用于AF向网络设备请求订阅事件报告。
该事件报告可包括但不限于：资源分配状况的事件报告和/或时延的事件报告。
例如，若AF订阅了资源分配状况的事件报告，则该AF会话的一个或多个数据流的资源分配发生变化时，可以通过事件报告通知AF。例如，该事件报告可指示：资源分配报告、资源回收报告和/或资源释放报告。
在一些实施例中，所述订阅请求包括：事件报告模式信息；
其中，所述事件报告模式信息指示的所述事件报告的报告模式包括以下至少之一：
立即报告模式；
周期报告模式；
触发报告模式。
若是立即报告模式，则PCF收到订阅请求之后，会立即上报订阅的事件报告，该事件报告内包括：数据流的时延和/或时延差和/或数据流的资源分配状况等。
周期报告模式为：订阅事件的事件报告会被周期性发送给TSCTSF，并由TSCTSF转发给AF。若采用周期性报告模式，则PCF侧可以配置周期性报告模式的定时器，定时器失效，则订阅事件对应的事件报告会从PCF提交到TSCTSF。
触发报告模式为：订阅事件被触发之后，TSCTSF会接收到PCF发送的事件报告。例如，数据流的时延达到阈值，或者时延差达到阈值时，则TSCTSF会收到PCF提交的事件报告。
示例性地，所述事件报告模式信息可包括立即报告标志，若该立即报告标志为预定值，则说明当前订阅事件所对应的事件报告的报告模式为立即报告模式。又示例性地，所述订阅事件包括周期报告模式的周期信息，则说明AF订阅周期性上报的事件报告。此时，该事件报告模式信息可以由周期信息隐含指示。
再示例性地，所述订阅事件包括触发订阅事件的阈值等，则说明AF订阅触发报告模式的事件报告。此时事件报告模式信息可以由阈值隐含指示。
当然所述订阅请求中可包括：一个或比特携带所述事件报告模式。
在一些实施例中，所述方法还包括：
S2220：在前述订阅事件被触发时，向TSCTSF发送事件报告。
在一些实施例中，所述方法还包括：
根据所述订阅请求，当数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告；
和/或，
根据所述订阅请求，当所述数据流的时延触发订阅事件时，向所述TSCTSF发送事件报告。
数据流的时延差出现变化可能触发事件报告的上报。如此，PCF可以根据订阅请求，向TSCTSF发送事件报告，该事件报告可最终被由TSCTSF转发给AF。
数据流的时延出现波动时，也可能触发事件报告的上报，如此，PCF可以根据订阅请求向TSCTSF发送事件报告；该事件报告最终会由TSCTSF转发给AF。
数据流的时延可以由UPF监测并计算得到。若AF请求订阅的是与时延相关的事件报告，则PCF可以向UPF进行订阅等。
示例性地，所述根据所述订阅请求，当数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告，包括：
根据所述订阅请求，向UPF和/或NR-RAN订阅所述所述数据流的时延；
根据所述UPF和/或NR-RAN提供的所述数据流的时延，确定所述时延差；
当所述时延差触发订阅事件时，向所述TSCTSF发送事件报告。
在本公开实施例中，PCF收到订阅请求之后，可以向UPF和/或NR-RAN订阅多个数据流的时延，如此，PCF会定期或者不定期的收到UPF和/或NR-RAN提供的多个数据流的时延。
如此，PCF收到多个数据流的时延之后，可以计算与同一个标识信息关联的多个数据流的时延差。并进一步判断PCF计算的时参差是否触发了订阅事件，若触发了订阅事件，则向TSCTSF发送事件报告。
例如，同一个XRM组标识涉及的多个数据流中的任意两个数据流的时延差大于时延差阈值时，可认为订阅事件被触发，此时，可以通过事件报告向TSCTSF告知订阅事件被触发的事实。
示例性地，为同一个XRM组标识涉及的数据流，可由多个UPF和/或NR-RAN进行数据流传输时，则单个UPF和/或NR-RAN仅能监控到该XRM组标识的多个数据流中的部分数据流的时延，此时，PCF可以向传输该XRM组标识涉及的多个数据流的UPF订阅时延，拿到各个数据流的时延之后，由PCF计算多个数据流的时延差。例如，PCF会计算多个数据流的最大时延差，若最大时延差触发订阅事件，则向TSCTSF发送事件报告。事件报告包含的内容可包括以下至少之一：
订阅事件的触发标志位；
导致订阅事件被触发的数据流的流标识；
导致订阅事件被触发的数据流的时延等。
当然以上事件报告的举例，具体实现时不局限于上述举例。
在一些实施例中，所述事件报告可仅包括订阅事件的触发标志位，此时，该事件报告仅用于通知TSCTSF的订阅事件被触发。
在另一个实施例中，所述根据所述订阅请求，当数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告，包括：
根据所述订阅请求，向所述UPF和/或NR-RAN订阅所述数据流的时延差；
当所述UPF和/或NR-RAN提供的所述数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告。
若XDM组标识关联(或涉及)的多个数据流，由于同步要求被调度经过相同的UPF和/或NR-RAN，此时，一个UPF可以监控到该XRM组标识关联的数据流的时延。此时，UPF和/或NR-RAN可以根据自身监控的多个数据流的时延，计算出多个数据流的时延差。
在这种情况下，PCF可以向UPF和/或NR-RAN直接订阅时延差，如此，PCF会定期或者不定期的接收到时延差，PCF在接收到时延差之后，会确定该多个数据流的时延差是否触发了订阅事件，若触发了订阅事件，则PCF会向TSCTSF发送事件报告，否则不向TTSCTSF发送事件报告。
在一些实施例中，所述根据所述订阅请求，当所述数据流的时延触发订阅事件时，向所述TSCTSF发送事件报告，包括：
根据所述订阅请求，向UPF订阅所述数据流的时延；
当所述UPF和/或NR-RAN提供的数据流的时延触发订阅事件时，向所述TSCTSF发送事件报告。
在一些实施例中，PCF也可以直接向UPF订阅数据流的时延，在数据流的时延触发了订阅事件时，也会向TSCTSF发送事件报告，否则不向TSCTSF发送事件报告。
在一个实施例中，所述根据所述订阅请求，当数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告，包括：
根据所述订阅请求，向所述UPF和/或NR-RAN发送订阅请求；其中，所述订阅请求包括：数据流的时延差触发订阅事件的订阅请求；和/或，所述数据流的时延触发订阅事件的订阅请求；
接收所述UPF发送触发订阅事件的通知消息；
根据所述通知消息，向所述TSCTSF发送事件报告。
在一个实施场景下，若该XRM组标识涉及数据流，且数据流由相同的UPF传输时，则PCF直接向UPF和/或NR-RAN订阅事件报告，UPF和/或NR-RAN根据自身对数据流的时延监控，并基于数据流的时延差确定是否触发了订阅事件，若触发了订阅事件，向PCF事件报告，如从，PCF会收到事件报告，并将事件报告发送给TSCTSF，并最终由TSCTSF发送给AF。
在另一个实施场景下，若该XRM组标识仅涉及一个数据流，PCF同样可以向UPF订阅事件报告，此时，UPF和/或NR-RAN传输并监控该数据流的时延，在该时延触发了订阅事件时，则UPF和/或NR-RAN会向PCF发送事件报告，因此，PCF会接收到事件报告并转发给TSCTSF。
在还有一个实施场景下，若该XRM组标识涉及数据流，且AF这数据流的数据流的时延相关的订阅事件，同样PCF可以向对应的UPF和/或NR-RAN订阅与数据流的时延相关的事件报告，此时，若某个数据流的时延触发了订阅事件，则PCF会收到UPF发送的事件报告。PCF在收到事件报告之后，会将该事件报告发送给TSCTSF，并最终由TSCTF发送给AF。
示例性地，所述订阅事件被触发，包括以下至少之一：
所述数据流的时延大于或等于所述订阅事件对应的时延阈值；
所述数据流的时延差大于或等于所述订阅事件对应的时延差阈值；
所述订阅事件的定时器到达；
接收到立即报告标志。
在网络的时延不会超过XRM组标识涉及的数据流能够容忍的最大时延时，则AF请求创建的AF会话被创建，但是网络的状况有波动，可能会出现在数据流传输过程中数据流的时延大于或等于订阅事件对应的时延阈值，则说明此时数据流的时延触发了订阅事件。
若该XRM组标识涉及数据流，在AF会话被创建时，网络的时延是不会过数据流能够容忍的最大时延差，但是在传输的过程中，由于网络状况的波动等导致数据流的时延差会增大到大于或等于 订阅事件的时延差阈值，则说明数据流的时延差触发了订阅数据。
例如，订阅事件的定时器可为周期性定时器，若定时器失效，则PCF会向TSCTSF发送事件报告。若定时器未失效，则PCF不会向TSCTSF发送事件报告。
若订阅的周期性事件报告，则PCF会周期性向TSCTSF发送事件报告。
假设前述实施例提供的时延阈值可为根据最大容忍延时确定的报警时延阈值或者数据流停止传输的停止时延阈值，在另一些实施例中还可以配置提醒时延阈值，例如，若数据流的时延超过报警时延阈值将逼近停止时延阈值时，由于网络波动，数据流的时延还可能会缩小，恢复到报警阈值以下。
同样地，上述实施例提供的时延差阈值为根据最大容忍时延差制定的报警时延差阈值或者数据流停止传输的停止时延差阈值，则在另一个实施例中还可以配置提醒时延差阈值。例如，数据流的实际时延差超过报警时延差阈值或者逼近停止时延差阈值，由于网络波动，数据流的时延差还可能缩小，则可能时延差还可以下降到小于提醒时延差阈值。
例如，订阅请求包含立即报标志，也相当于订阅事件被触发，因此需要上报事件报告。
因此，所述订阅事件被触发，还可包括以下至少之一：
数据流的时延小于或等于提醒时延阈值；
数据流的时延差小于或等于提醒时延差阈值。
在一些实施例中，所述方法还包括：
当所述订阅事件被触发时，更新所述PCC规则。
在一些实施例中，所述当所述订阅事件被触发时，更新所述PCC规则，包括：
当所述订阅事件被触发时，提升所述PCC规则授权的QoS；
或者，
当所述订阅事件被触发时，降低所述PCC规则授权的QoS。
例如，与时延相关的订阅事件被触发，提升或者降低PCC规则授权的QoS。
例如，PCC规则会限定第五代移动通信QoS标识符(5G QoS Identifier，5QI)。
当与时延相关的订阅事件被触发，且是数据流的时延降低，则可以通过提升5QI，实现PCC规则授权的QoS的提升，从而提升XRM组标识的数据流的QoS。
当与时延相关的订阅事件被触发，且是数据流时延增加，则可以通过降低一点QoS(例如，降低5QI)等，实现PCC规则想定的QoS的降低，从而优先保证数据流的传输。
在一些实施例中，所述订阅请求包括：事件报告模式信息；
其中，所述事件报告模式信息指示的所述事件报告的报告模式包括以下至少之一：
立即报告模式；
周期报告模式；
触发报告模式。
若是立即报告模式，则PCF收到订阅请求之后，会立即上报订阅的事件报告，该事件报告内包 括：数据流的时延和/或时延差和/或数据流的资源分配状况等。
周期报告模式为：订阅事件的事件报告会被周期性发送给TSCTSF，并由TSCTSF转发给AF。若采用周期性报告模式，则PCF侧可以配置周期性报告模式的定时器，定时器失效，则订阅事件对应的事件报告会从PCF提交到TSCTSF。
触发报告模式为：订阅事件被触发之后，TSCTSF会接收到PCF发送的事件报告。例如，数据流的时延达到阈值，或者时延差达到阈值时，则TSCTSF会收到PCF提交的事件报告。
示例性地，所述事件报告模式信息可包括立即报告标志，若该立即报告标志为预定值，则说明当前订阅事件所对应的事件报告的报告模式为立即报告模式。又示例性地，所述订阅事件包括周期报告模式的周期信息，则说明AF订阅周期性上报的事件报告。此时，该事件报告模式信息可以由周期信息隐含指示。
再示例性地，所述订阅事件包括触发订阅事件的阈值等，则说明AF订阅触发报告模式的事件报告。此时事件报告模式信息可以由阈值隐含指示。
当然所述订阅请求中可包括：一个或比特专门指示所述事件报告模式。
如图6所示，本公开实施例提供一种信息处理方法，其中，由AF执行，所述方法包括：
S3110：发送AF的会话创建请求，所述会话创建请求包括同步指示以及XRM组标识；
S3120：接收所述会话创建请求的会话创建响应。
本公开实施例中，该AF可由一个或服务器。该AF可为提供XRM业务的服务器。
该AF需要与UE之间进行数据流传输时，可以向网络侧申请创建会话，则此时，可以向TSCTSF直接或者通过NEF向TSCTSF发送会话创建请求。
在另一个实施例中，所述会话创建请求还包括：时延信息和/或所述UEs IP地址。
该UEs IP地址的UE为传输XRM业务的数据流的UE；XRM组标识XRM组，该XRM组包括：一个或需要进行数据流传输的XRM业务。
在一些实施例中，所述时延信息包括以下至少之一：
双向时延；
上行时延；
下行时延；
数据流的时延差。
此处的双向时延为：上行时延和下行时延之和。
上行时延可为：UE到网络设备(例如，用户面功能(User Plane Function，UPF))的数据流的时延。
下行时延可为：网络设备到UE的数据流的时延。
此处的数据流的时延差可为：数据流的时延差。此处的数据流的时延差可包括：由同一个XRM组标识的上行数据流的时延差，和/或，由同一个XRM组标识的下行数据流的时延差。
在一个实施例中，所述会话创建请求还包括以下至少之一：
同步指示；
流描述；
服务质量QoS信息和需求；
所述AF的标识。
所述同步指示携带在所述会话创建请求中，可用于表明当前请求创建会话是时间敏感会话，针对该会话涉及的一个或数据流均是TSC数据流，即这些数据流对时延很敏感，且对数据流的时延差很敏感。
TSCTSF收到包含有所述同步指示的会话创建请求之后，若该会话创建请求中包含同步指示，TSCTSF会对该AF请求创建的会话(即AF会话)涉及的数据流提供时间同步业务。
示例性地，若TSCTSF收到了同步指示之后，会将同步指示发送给PCF，PCF收到同步指示之后，知道当前请求创建的AF会话涉及的都是TSC数据流，若存在数据流时，在确定控制路由路径的策略时，可以考虑让数据流尽可能采用相同的路由路径，从而减少传输时延差。
示例性地，由于该XDM组标识涉及的数据流都是TSC数据流，可以优先使用相同过的UPF进行传输和/或监控。
又示例性地，当然所述同步指示也可以不传输给PCF，PCF直接根据时延信息确定当前涉及的数据流是否为TSC数据流，若是TSC数据流同样需要基于为这种数据流提供时间同步业务的考虑执行相应的策略。
流描述可包括一个或信息单元(Information Element，IE)描述了数据流的属性信息。
所述QoS信息和需求可用于核心网网元确定各个数据流能够容忍的最大时延和/或数据流能够容忍的最大时延差。
示例性地，所述QoS信息和需求包括以下至少之一：
QoS参数；
QoS参考；
备选的业务需求。
示例性地，所述QoS参数可包括以下至少之一：
请求的5GS时延；
请求的周期；
请求的最大保障比特(Guaranteed Bitrate，GB)；
请求的最大比特(Maximum Bitrate)；
流方向，例如，该AF涉及的一个或数据流可为上行数据流和/或下行数据流，若上行数据流的流方向为上行；若下行数据流的流方向为下行；
突发大小(Burst Size)；
上行数据流达到时间(Burst Arrival Time at UE)；
下行数据流达到时间(Burst Arrival Time at UPF)；
时间域(Time Domain)；
数据流的持续时长(Survival Time)。
所述备选的业务需求(Alternative Service Requirments)可包括如下参数至少之一：
AF提供的有助于确定独立QoS参数的信息；
可选QoS相关参数集合，该集合内包括一个或可选QoS参数或者QoS参考。
示例性地，QoS参考同样可用于确定确定数据流的QoS的任意参考信息。在一些实施例中，QoS可为备选的业务需求的部分内容。
当然以上仅仅是对QoS信息和需求的举例说明，具体实现时不局限于上述举例说明。
在一个实施例中，所述方法还包括：
接收所述会话创建请求的会话创建响应。
在一些实施例中，所述方法还包括：
接收所述TSCTSF在订阅事件被触发时发送的通知消息。
若订阅事件被触发了，则TSCTSF会接收到订阅事件被触发的通知消息。该通知消息可包括：事件报告。
该事件报告可包括：资源状态分配的事件报告和/或与时延相关的事件报告。
该资源分配状态的事件报告可包括：与数据流的时延相关的事件报告，和/或数据流的时延相关的事件报告。
如此，一方面AF接收到事件报告，确定是否需要继续发送AF的会话创建请求，或者时延创建或者更新会话请求；另一方面AF可以通过事件报告监控AF会话数据流在网络中的传输状况。
在一些实施例中，所述发送AF的会话创建请求，包括：
当所述AF存储有TSCTSF的地址时，根据所述TSCTSF的地址向所述TSCTSF发送所述AF的会话创建请求。
在本公开实施例中，若AF存储有TSCTSF的地址，即表明AF是被TSCTSF信任的AF，如此，AF可以根据TSCTSF的地址，直接与TSCTSF之间交互信息。
在另一些实施例中，所述发送AF的会话创建请求，包括：
当所述AF未存储TSCTSF的地址时，向网络开放功能NEF发送所述AF的会话创建请求，其中，所述会话创建请求，用于由所述NEF转发给所述TSCTSF。
若AF未存储有TSCTSF的地址，则AF可能不能直接和TSCTSF通信，则AF将会话创建请求发送给NEF，并通过NEF转发的TSCTSF的响应和/或更新消息等。
如图7所示，本公开实施例提供一种信息处理方法，其中，由NEF执行，所述方法还包括：
S4110：接收应用功能AF的会话创建请求，其中，所述会话创建请求包括同步指示以及XRM组标识；
S4120：获取接收所述会话创建请求的TSCTSF的地址；
S4130：根据所述TSCTS F的地址，将所述会话创建请求发送给所述TSCTSF。
该AF请求创建的会话涉及的一个或多个数据流可为TSC数据流。该XRM组标识为请求创建会话涉及的XRM业务的标识。该XRM组标识可包括一个或多个XRM业务的标识。总之，该XRM组标识可以知道一个XRM业务组内多个数据流。
示例性地，该XRM组标识涉及的XRM业务需要由一个UE组来传输。该一个UE组可包括一个或多个UE。该UEs IP地址可包括：UE的网络协议(Internet Protocol，IP)地址。
在一个实施例中，所述会话创建请求还包括：时延信息和/或UEs IP地址。
在一个实施例中，所述获取接收所述会话创建请求的TSCTSF的地址，包括：
查询所述NEF预先存储的TSCTSF的地址；
或者，
将所述AF的标识和/或所述会话创建请求包含的XRM组标识和/或UEs IP地址，映射到网络名称DNN和/或网络切片标识，并根据所述DNN和/或网络切片标识映射发现所述TSCTSF的地址。
该NEF可接收AF发送的会话创建请求，NEF接收到该会话创建请求之后，若NEF本地存储有TSCTSF的地址，则NEF根据本地存储的TSCTSF直接将该会话创建请求发送刚给TSCTSF。
若NEF未存储有TSCTSF的地址，则可以根据AF的标识和/或XRM组标识以及映射关系信息，将AF标识和/或XRM组标识映射到DNN和/或网络切片标识。该DNN和/或网络切片标识进一步可映射到TSCTSF的地址。
该映射关系信息可指示以下至少之一：
AF的标识与DNN之间的映射关系；
AF的标识与网络切片标识之间的映射关系；
XRM组标识与DNN之间的映射关系；
XRM组标识与网络切片标识之间的映射关系；
UEs IP地址与DNN之间的映射俄关系；
UEs IP地址与网络切片标识之间的映射关系；
DNN与TSCTSF的地址之间的映射关系；
网络切片标识与TSCTSF的地址之间的映射关系。
该网络切片标识包括但不限于：单一网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)。
总之，NEF若本地没有配置TSCTSF的地址，则可以通过上述方式确定TSCTSF的地址，且在AF和TSCTSF之间进行信息交互。
在一些实施例中，所述方法还包括：
接收所述会话创建请求的会话创建响应；
将所述会话创建响应发送给所述AF。
由于AF通过NEF向TSCTSF发送会话创建请求，如此NEF会接收到TSCTSF发送的会话创建响应，并将该会话创建响应发送给AF。
在一些实施例中，所述方法还包括：
接收订阅事件被触发时所述TSCTSF发送的通知消息；
将所述通知消息发送给所述AF。
该通知消息可包括事件报告，该事件报告被携带在通知消息中发送给AF，如此，AF可以根据NEF发送的通知消息，实现对XRM业务涉及的一个或数据流在网络中的传输状况。
如图8所示，本公开实施例提供一种XRM业务处理方法，可包括：
1.AF发送AF会话创建请求给TSCTSF，AF会话创建请求提供同步指示、时延信息以及XRM组标识。该时延信息包括但不限于：上行时延，下行时延，双向时延或时延差。例如，AF可直接向TSCTSF发送AF会话创建请求，或者，通过NEF向TSCSF发送AF会话创建请求。
2.TSCTSF根据收到的同步指示、时延信息、组ID、UE地址、AF ID、流描述以及收到的QoS信息和需求，计算请求包时延预算(Packet Delay Budge，PDB)。该组ID为前述XRM组标识的一种，该UE地址可构成UEs IP地址的一种。
TSCTSF可以通过触发Npcf_PolicyAuthorization_Create或Npcf_PolicyAuthorization_Subscribe请求，从PCF订阅与同步相关的时延，例如，如5G端到端时延或时延差。此处从PCF订阅的时延可为：数据流实际传输的时延。
TSCTSF的地址可能是配置在NEF、PCF和/或可信AF本地，或者通过网络仓储功能(Network Respository Function，NRF)发现和选择。NEF使用组ID和/或AF ID来确定DNN/和/或S-NSSAI，且使用DNN和/或S-NSSAI从网络仓储功能(Network Repository Function，NRF)发现的TSCTSF的地址。
AF使用Nnef_AFsessionWithQoS_Create向TSCTSFF发送AF的会话创建请求，以请求为AF会话预留资源，该AF会话创建请求可包括：同步指示、时延信息、组ID、应用程序ID、UE地址、一个或多个数据流描述或外部应用标识符、QoS参考、QoS参数、备选的业务需求，DNN，S-NSSAI)到NEF，并由NEF发送给TSCTSF。
或者，
AF直接可向TSCTSF发送AF会话创建请求。示例性地，AF发送AF会话资源请求，例如通过Nnef_AFsessionWithQoS_Create请求，创建AF请求。AF在请求消息中携带XRM服务信息，XRM服务信息包括同步指示、时延信息、应用程序ID、组ID、UE地址、一个或数据流描述、S-NSSAI和/或QoS参数等相应信息。这里组ID，可用于识别XRM服务组中的所有数据流。该时延信息可包括：上行时延、下行时延、双向时延、端到端时延和/或时延差。
可选地，在AF的会话创建请求中，AF可以提供以下单独的QoS参数：请求的5GS时延(可选)、请求的优先级、请求的保证比特率、请求的最大比特率。该优先级可为可选参数。
AF还可以提供以下可选的QoS参数：
流方向、突发大小、UE上行或UPF下行的突发到达时间、周期性、时域、生存时间。
当备选的业务需求由独立QoS参数制定的AF请求提供时，可以提供一组可选QoS相关参数。
2.NEF授权该AF会话创建请求。
3.NEF根据请求决定调用TSCTSF与PCF交互，以通过TSCTSF触发PCF生成PCC规则或激活预定义的PCC规则。NEF将收到的同步指示、时延信息、组ID、应用ID、单个QoS参数、QoS参考等信息包含Ntsctsf_QoSandTSCAssistance_Create请求消息中的QoS相关参数集合中，并将Ntsctsf_QoSandTSCAssistance_Create请求消息转发给TSCTSF。TSC辅助(Assistance)信息可用于TSCTSF向数据流提供时间同步业务。该TSC辅助信息的信息内容可如表1所示：
Figure PCTCN2022092894-appb-000001
表1
DT-TT可为：设备侧的TSN适配器(Device-side TSN translator，DT-TT)。TSN为时间敏感网络(Time Sensitive Network，TSN)。
NW-TT可为：网络侧时间敏感网络适配器(Network-side TSN translator，NW-TT)。
如果AF被通信运营商信任，则AF可使用ntsctsf_qsandtscassistance_create请求消息，直接与TSCTSF交互，以请求为AF会话预留资源。
TSCTSF的地址可以被预先配置在NEF、PCF和受信任的AF本地，或者通过NRF发现和选择。
示例性地，每个DNN和/或S-NSSAI都配置一个TSCTSF。或者，NEF使用组ID和/或AF标识符来确定DNN/S-NSSAI，并使用DNN/S-NSSAI从NRF发现TSCTSF。
4.可选地，TSCTSF根据收到的同步指示、时延信息、组ID、UE地址、AF标识符、一个或流描述(s)、和收到的QoS信息和要求，计算请求的PDB。
5.TSCTSF具有XRM业务涉及的数据流关联的给定UE所连接的PCF的地址。在这种情况下，TSCTSF通过触发Npcf_PolicyAuthorization_Create/Update请求与PCF交互，并提供同步指示、时延信息、组ID、UE地址、AF标识、流描述(s)、QoS参考、QoS参数和备选的业务需求。
TSCTSF不具有XRM业务涉及的数据流关联的给定UE所连接的PCF的地址，则TSCTSF发现PCF，并向发现的PCF发送同步指示、时延信息，组ID，要求PDB，TSC援助容器和其他收到个人QoS和替代QoS相关参数Npcf_PolicyAuthorization_Create PCF的请求消息。示例性地，TSCTSF具有发现功能，该发现功能可包括：TSCTSF通过与NRF之间的信息交互，发现PCF。
TSCTSF可以通过发送Npcf_PolicyAuthorization_Create或Npcf_PolicyAuthorization_Subscribe请求，从PCF订阅与同步相关的时延。
如果TSCTSF从NEF接收到以下任何一个单独的QoS参数:流方向、突发到达时间、周期、时间域以及生存时间。
TSCTSF确定TSC协助容器，并将TSC协助容器与请求的PDB，以及其他在Npcf_PolicyAuthorization_Create/Update请求中收到的QoS参数，一起发送给PCF。
6.对于第5步中从TSCTSF接收到的请求，PCF确定请求是否得到授权，如果请求没有得到授权，则通知TSCTSF。
PCF负责制定策略并订阅被AF或TSCTSF请求的事件报告。例如，PCF向UPF订阅同步相关的时延。例如，PCF触发订阅或接收来自TSCTSF订阅)，PCF可能触发特定数据流的QoS监测，从而得到端到端时延，并计算数据流的时延差。
例如，PCF向SMF发起SM策略关联修改请求以订阅该事件。根据基于PCF提供的QoS监控策略的QoS测量，SMF为UPF和RAN生成QoS监控配置(如果需要的话)。一旦PCF收到通知，该通知与同步相关的时延会被PCF同步给TSCTSF。
如果请求被授权，PCF根据TSCTSF提供的信息获取所需的QoS参数，并根据PCF配置确定是否允许此QoS流，并将结果通知TSCTSF。该QoS流可为前述与XRM组标识关联的一个或数据流。
此外，如果提供了备选的业务需求，PCF从一个或QoS参考参数派生可选QoS参数集，或根据备选的业务需求和被请求的PDB中确定备用QoS相关参数集。此处的可选QoS参数集或者备用QoS相关参数集都可以用于PCF指定策略。
如果PCF接收到的是单独的QoS参数，而不是QoS参考，则PCF根据从TSCTSF接收到的请求PDB和突发大小设置PDB和MDBV。如果没有提供被请求的PDB，PCF将确定与QoS参考匹配的PDB。PCF还根据TSCTSF发送的PDB等设置PCC规则(或称PCC规则)的GBR和MBR。PCF可以使用来自AF的请求优先级，确定请求的AF会话关联的一个或数据流的优先级。TSCTSF指定的QoS参数值，将取代5QI的默认值。
7.PCF通过触发Npcf_PolicyAuthorization_Create/Update响应与TSCTSF交互，告知TSCTSFAF创建请求是否被授权。如果请求未被授权，或者所需的QoS不被允许，PCF将用一个结果(Result)值响应TSCTSF，该值指示失败原因。
8.TSCTSF向NEF发送一个ntsctsf_qsandtscassistance_create会话创建响应，该会话创建响应将包括：事务引用ID和/或会话创建结果。会话创建结果表明该会话创建请求是否被授权。若会话创建请求被授权，则该会话会被网络创建，否则该会话不会被网络创建。
如果AF得到了运营商的信任，则TSCTSF可直接向AF发送ntsctsf_qsandtscassistance_create会话创建响应。
9.NEF向AF发送一个Nnef_AFsessionWithQoS_Create会话创建响应，该会话创建响应可包括传输相关标识(Transaction Reference ID)以及会话创建结果。会话创建结果表示请求是否被授权。会话创建结果表明该会话创建请求是否被授权。若会话创建请求被授权，则该会话会被网络创建，否则该会话不会被网络创建。
10.TSCTSF向PCF发送Npcf_PolicyAuthorization_Subscribe消息以订阅资源分配状态，和/或订阅与同步相关的时延。
11.订阅事件触发，事件报告可由UPF传输给PCF。例如，UPF触发通知(Notify)消息，向PCF报告测量的信息(例如，端到端时延、时延差)。示例性地，当UPF检测到时延达到事件时，将触发事件报告，例如，时延或时延差达到对应阈值，或周期计时器超时(即检测到周期订阅的订阅事件被触发)。
如果PCF收到时延差或端到端时延的订阅，PCF可以将这些时延相关的事件报告发送给TSCTSF。例如，如果PCF发现时延差达到了AF提供的时延差阈值，PCF将这些订阅事件被触发通知给TSCTSF。
根据UPF的通知，PCF可以为一个或数据流调整相关的PCC规则，例如，降级或升级相关的QoS授权。
12.当订阅事件被触发时，例如达到端到端时延或时延差的阈值，或周期计时器超时，PCF向TSCTSF发送Npcf_PolicyAuthorization_Notify消息，以通知订阅事件被触发，具体通知的订阅事件可如步骤11所示。
13.TSCTSF向NEF发送带有PCF的事件报告的Ntsctsf_QoSandTSCAssistance_Notify消息。
如果AF被运营商信任，TSCTSF直接向AF发送Ntsctsf_QoSandTSCAssistance_Notify消息。
14.NEF向AF发送Nnef_AFsessionWithQoS_Notify消息，携带PCF提供的事件报告。
为了撤销AF创建请求，AF可以向NEF发送Nnef_AFsessionWithQoS_Revoke请求。NEF对撤销请求授权，并对AF创建请求触发Ntsctsf_QoSandTSCAssistance_Delete/Unsubscribe和/或Npcf_PolicyAuthorization_Delete和Npcf_PolicyAuthorization_Unsubscribe操作。
如图9所示，本公开实施例提供一种XRM业务处理装置，其中，所述装置包括：
第一接收模块110，被配置为接收应用功能AF的会话创建请求，其中，所述会话创建请求包括：同步指示以及XRM组标识UEs IP地址；
第一发送模块120，被配置为将所述同步指示以及所述XRM组标识和/或所述UEs IP地址发送给策略控制功能PCF。
该装置可包含在TSCTSF中。
在一些实施例中，所述第一接收模块110以及所述第一发送模块120可为程序模块，该程序模块被处理器执行之后，能够实现上述操作。
在一些实施例中，所述第一接收模块110以及所述第一发送模块120可为软硬件结合模块，该软硬件结合模块可包括：可编辑阵列；所述可编辑阵列包括但不限于：现场可编程阵列和/或复杂可编程阵列。
在还有一些实施例中，所述第一接收模块110以及所述第一发送模块120可为纯硬件模块；所述纯硬件模块但不限于专用集成电路。
在一些实施例中，所述同步指示以及所述XRM组标识，用于供所述PCF生成策略控制和计费PCC规则或者激活预定义的PCC规则。
在一些实施例中，所述会话创建请求，还包括：时延信息和/或用户设备UEs IP地址；
所述第一发送模块120，还被配置为将所述时延信息和/或所述UEs IP地址，发送给所述PCF。
在一些实施例中，所述装置还包括：
计算模块，被配置为根据所述时延信息，计算分组时延预算PDB；
所述第一发送模块120，被配置为将所述PDB发送给所述PCF。
在一些实施例中，所述时延信息包括以下至少之一：
双向时延上行时延；
下行时延；
数据流的时延差。
在一些实施例中，所述会话创建请求还包括以下至少之一：
流描述；
服务质量QoS信息和需求；
所述AF的标识。
在一些实施例中，所述QoS信息和需求包括以下至少之一：
QoS参数；
QoS参考；
备选的业务需求。
在一些实施例中，所述PDB以及所述同步指示、和所述XRM组标识和/或所述UEs IP地址以及所述时延信息，包含在授权创建或者更新请求中发送给所述PCF。
在一些实施例中，所述第一接收模块110，还被配置为接收所述授权创建或者更新请求的响应；
所述第一发送模块120，还被配置为根据所述授权创建或者更新请求的响应，发送所述会话创建请求的会话创建响应。
在一些实施例中，所述第一发送模块120，还被配置为向所述PCF发送订阅请求，其中，所述订阅请求，用于请求订阅事件报告。
在一些实施例中，所述第一接收模块110，还被配置为接收所述PCF发送的所述事件报告；
所述第一发送模块120，还被配置为向所述AF发送事件报告，其中，所述通知消息包括所述事件报告。
在一些实施例中，所述TSCTSF的地址预先存储在网络开放功能NEF、PCF或者可信的AF上。
在一个实施例中，所述订阅请求包括：事件报告模式信息；
其中，所述事件报告模式信息指示的所述事件报告的报告模式包括以下至少之一：
立即报告模式；
周期报告模式；
触发报告模式。
如图10所示，本公开实施例提供一种信息处理装置，其中，所述装置包括：
第二接收模块210，被配置为接收TSCTSF发送的同步指示以及XRM组标识；
PCC规则模块220，被配置为根据所述同步指示和所述XRM组标识，生成策略控制和计费PCC规则或者激活预定义的PCC规则。
该装置可包括在PCF中。
在一些实施例中，所述第二接收模块210以及PCC规则模块220可为程序模块，该程序模块被处理器执行之后，能够实现上述操作。
在一些实施例中，所述第二接收模块210以及PCC规则模块220可为软硬件结合模块，该软硬件结合模块可包括：可编辑阵列；所述可编辑阵列包括但不限于：现场可编程阵列和/或复杂可编程阵列。
在还有一些实施例中，所述第二接收模块210以及PCC规则模块220可为纯硬件模块；所述纯硬件模块但不限于专用集成电路。
在一些实施例中，所述第二接收模块210，被配置为接收所述TSCTSF发送的所述同步指示和所述XRM组标识，以及时延信息和/或UEs IP地址。
在一些实施例中，所述装置还包括：
PCC规则模块，被配置为根据所述同步指示以及时延信息为所述XRM组标识和/或所述UEs IP地址涉及的数据流，生成策略控制和计费PCC规则或者激活预定义的PCC规则。
在一些实施例中，所述第二接收模块210，被配置为接收包含所述同步指示、和所述时延信息以及所述XRM组标识和/或所述UEs IP地址的授权创建或者更新请求；
所述装置还包括：
第二发送模块，被配置为向所述TSCTSF发送所述授权创建或者更新请求的响应。
在一些实施例中，所述PCC规则模块，被配置为当所述授权创建或者更新请求还包括所述TSCTSF根据所述时延信息计算的PDB时，根据所述同步指示、所述PDB、所述XRM组标识和/或所述UES IP地址，生成所述PCC规则或者激活预定义的所述PCC规则；
或者，
当所述授权创建或者更新请求不包括所述TSCTSF根据所述时延信息计算的PDB时，根据所述授权创建或者更新请求包含的所述时延信息计算PDB，根据所述PCF计算的PDB、所述XRM组标识和/或所述UEs IP地址，生成所述PCC规则或激活预定义的所述PCC规则。
在一些实施例中，所述PCC规则模块，被配置为根据所述授权创建或者更新请求包含的PDB和最大突发数据量MDVB，设置数据流的PDB和突发数据量；根据所述数据流的PDB和所述突发数据量、所述XRM组标识和/或所述UEs IP地址，生成PCC规则或激活预定义的PCC规则。
在一些实施例中，所述装置还包括：
授权模块，被配置为确定是否授权创建会话。
在一些实施例中，所述第二接收模块210，还被配置为接收订阅请求；其中，所述订阅请求，用于请求订阅事件报告。
在一些实施例中，所述第二发送模块，还被配置为根据所述订阅请求，当数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告；和/或，根据所述订阅请求，当所述数据流的时延触发订阅事件时，向所述TSCTSF发送事件报告。
在一些实施例中，所述第二发送模块，还被配置为根据所述订阅请求，向用户面功能UPF订阅所述所述数据流的时延；
时延差模块，被配置为根据所述UPF提供的所述数据流的时延，确定所述时延差；
所述第二发送模块，还被配置为当所述时延差触发订阅事件时，向所述TSCTSF发送事件报告。
在一些实施例中，所述第二发送模块，还被配置为根据所述订阅请求，向所述UPF订阅所述数据流的时延差；当所述UPF提供的所述数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告。
在一些实施例中，所述第二发送模块，被配置为根据所述订阅请求，向用户面功能UPF订阅所述数据流的时延；当所述UPF提供的数据流的时延触发订阅事件时，向所述TSCTSF发送事件报告。
在一些实施例中，所述第二发送模块，还被配置为根据所述订阅请求，向所述UPF发送订阅请求；其中，所述订阅请求包括：数据流的时延差触发订阅事件的订阅请求；和/或，所述数据流的时延触发订阅事件的订阅请求；
所述第二接收模块210，还被配置为接收所述UPF发送触发订阅事件的通知消息；
所述第二发送模块，还被配置为根据所述通知消息，向所述TSCTSF发送事件报告。
在一些实施例中，所述订阅事件被触发，包括以下至少之一：
所述数据流的时延大于或等于所述订阅事件对应的时延阈值；
所述数据流的时延差大于或等于所述订阅事件对应的时延差阈值；
所述订阅事件的定时器到达；
接收到立即报告标志。
在一个实施例中，所述订阅请求包括：事件报告模式信息；
其中，所述事件报告模式信息指示的所述事件报告的报告模式包括以下至少之一：
立即报告模式；
周期报告模式；
触发报告模式。
在一些实施例中，所述装置还包括：
更新模块，被配置为当所述订阅事件被触发时，更新所述PCC规则。
在一些实施例中，所述更新模块，被配置为当所述订阅事件被触发时，提升所述PCC规则授权的QoS；或者，当所述订阅事件被触发时，降低所述PCC规则授权的QoS。
如图11所示，本公开实施例提供一种信息处理装置，其中，所述装置包括：
第三发送模块310，被配置为发送AF的会话创建请求，所述会话创建请求包括同步指示以及XRM组标识；
第三接收模块320，第三接收模块，被配置为接收所述会话创建请求的会话创建响应。
该装置可包括在PCT中。
在一些实施例中，所述第三发送模块310可为程序模块，该程序模块被处理器执行之后，能够实现上述操作。
在一些实施例中，所述第三发送模块310可为软硬件结合模块，该软硬件结合模块可包括：可编辑阵列；所述可编辑阵列包括但不限于：现场可编程阵列和/或复杂可编程阵列。
在还有一些实施例中，所述第三发送模块310可为纯硬件模块；所述纯硬件模块但不限于专用集成电路。
在一个实施例中，所述会话创建请求还包括：时延信息和/或所述UEs IP地址。
在一些实施例中，所述时延信息包括以下至少之一：
双向时延；
上行时延；
下行时延；
数据流的时延差。
在一些实施例中，所述会话创建请求还包括以下至少之一：
同步指示；
流描述；
服务质量QoS信息和需求；
所述AF的标识。
在一些实施例中，所述QoS信息和需求包括以下至少之一：
QoS参数；
QoS参考；
备选的业务需求。
在一些实施例中，所述第三接收模块，还被配置为接收所述TSCTSF在订阅事件被触发时发送的通知消息。
在一些实施例中，所述第三发送模块310，还被配置为当所述AF存储有TSCTSF的地址时，根据所述TSCTSF的地址向所述TSCTSF发送所述AF的会话创建请求。
在一些实施例中，所述第三发送模块310，还被配置为当所述AF未存储TSCTSF的地址时，向网络开放功能NEF发送所述AF的会话创建请求，其中，所述会话创建请求，用于由所述NEF转发给所述TSCTSF。
如图12所示，本公开实施例提供一种信息处理装置，其中，所述装置还包括：
第四接收模块410，被配置为接收AF发送的会话创建请求，其中，所述会话创建请求包括同步指示和XRM组标识UEs IP地址；
获取模块420，被配置为获取接收所述会话创建请求的TSCTSF的地址；
第四发送模块430，被配置为根据所述TSCTS F的地址，将所述会话创建请求发送给所述TSCTSF。
该信息处理装置可包含在NEF中。
在一些实施例中，所述第四接收模块410、获取模块420以及第四发送模块430可为程序模块，该程序模块被处理器执行之后，能够实现上述操作。
在一些实施例中，所述第四接收模块410、获取模块420以及第四发送模块430可为软硬件结合模块，该软硬件结合模块可包括：可编辑阵列；所述可编辑阵列包括但不限于：现场可编程阵列和/或复杂可编程阵列。
在还有一些实施例中，所述第四接收模块410、获取模块420以及第四发送模块430可为纯硬件模块；所述纯硬件模块但不限于专用集成电路。
在一个实施例中，所述会话创建请求还包括：时延信息和/或用户设备UEs IP地址。
在一些实施例中，所述获取模块420，被配置为查询所述NEF预先存储的TSCTSF的地址；或者，将所述AF的标识和/或所述会话创建请求包含的XRM组标识和/或UEs IP地址，映射到网络名称DNN和/或网络切片标识，并根据所述DNN和/或网络切片标识映射发现所述TSCTSF的地址。
在一些实施例中，所述第四接收模块410，被配置为接收所述会话创建请求的会话创建响应；
所述第四发送模块430，还被配置为将所述会话创建响应发送给所述AF。
在一些实施例中，所述第四接收模块410，被配置为接收订阅事件被触发时所述TSCTSF发送的通知消息；
所述第四发送模块430，被配置为将所述通知消息发送给所述AF。
本公开实施例提供一种通信设备，包括：
用于存储处理器可执行指令的存储器；
处理器，分别存储器连接；
其中，处理器被配置为执行前述任意技术方案提供的信息处理方法。
处理器可包括各种类型的存储介质，该存储介质为非临时性计算机存储介质，在通信设备掉电之后能够继续记忆存储其上的信息。
这里，所述通信设备包括：UE或者网元，该网元可为前述第一网元至第四网元中的任意一个。
所述处理器可以通过总线等与存储器连接，用于读取存储器上存储的可执行程序，例如，如图2至图8所示的方法的至少其中之一。
图13是根据一示例性实施例示出的一种UE 800的框图。例如，UE 800可以是移动电话，计算机，数字广播用户设备，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图13，UE 800可以包括以下一个或组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制UE 800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或处理器820来执行指令，以生成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在UE 800的操作。这些数据的示例包括用于在UE 800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为UE 800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或电源，及其他与为UE 800生成、管理和分配电力相关联的组件。
多媒体组件808包括在所述UE 800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当UE 800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦 能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当UE 800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或传感器，用于为UE 800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如所述组件为UE 800的显示器和小键盘，传感器组件814还可以检测UE 800或UE 800一个组件的位置改变，用户与UE 800接触的存在或不存在，UE 800方位或加速/减速和UE 800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于UE 800和其他设备之间有线或无线方式的通信。UE 800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，UE 800可以被一个或应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由UE 800的处理器820执行以生成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
如图14所示，本公开一实施例示出一种接入设备的结构。例如，通信设备900可以被提供为一网络侧设备。该通信设备可为前述的接入网元和/或网络功能等各种网元。
参照图14，通信设备900包括处理组件922，其进一步包括一个或处理器，以及由存储器932所代表的存储器资源，用于存储可由处理组件922的执行的指令，例如应用程序。存储器932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件922被配置为执行指令，以执行上述方法前述应用在所述接入设备的任意方法，例如，如图2至图8任意一个所示方法。
通信设备900还可以包括一个电源组件926被配置为执行通信设备900的电源管理，一个有线 或无线网络接口950被配置为将通信设备900连接到网络，和一个输入输出(I/O)接口958。通信设备900可以操作基于存储在存储器932的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (46)

  1. 一种扩展现实业务媒体XRM业务处理方法，其中，由时间敏感通信和时间同步功能TSCTSF执行，所述方法包括：
    接收应用功能AF的会话创建请求，其中，所述会话创建请求包括同步指示和XRM组标识；
    将所述同步指示以及所述XRM组标识发送给策略控制功能PCF。
  2. 根据权利要求1所述的方法，其中，所述会话创建请求，还包括：时延信息和/或用户设备UEs网络协议IP地址；
    所述方法还包括：
    所述时延信息和/或所述UEs IP地址，发送给所述PCF。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    根据所述时延信息，计算分组时延预算PDB；
    所述方法还包括：
    将所述PDB发送给所述PCF。
  4. 根据权利要求2或3所述的方法，其中，所述时延信息包括以下至少之一：
    双向时延；
    上行时延；
    下行时延；
    数据流的时延差。
  5. 根据权利要求1至4任一项所述的方法，其中，所述会话创建请求还包括以下至少之一：
    流描述；
    服务质量QoS信息和需求；
    所述AF的标识。
  6. 根据权利要求5所述的方法，其中，所述QoS信息和需求包括以下至少之一：
    QoS参数；
    QoS参考；
    备选的业务需求。
  7. 根据权利要求3所述的方法，其中，所述PDB以及所述同步指示、和所述XRM组标识和/或所述UEs IP地址以及所述时延信息，包含在授权创建或者更新请求中发送给所述PCF。
  8. 根据权利要求7所述的方法，其中，所述方法还包括：
    接收所述授权创建或者更新请求的响应；
    根据所述授权创建或者更新请求的响应，发送所述会话创建请求的会话创建响应。
  9. 根据权利要求1所述的方法，其中，所述方法还包括：
    向所述PCF发送订阅请求，其中，所述订阅请求，用于请求订阅事件报告。
  10. 根据权利要求9所述的方法，其中，所述方法还包括：
    接收所述PCF发送的所述事件报告；
    向所述AF发送事件报告。
  11. 根据权利要求1至10任一项所述的方法，其中，所述TSCTSF的地址预先存储在网络开放功能NEF、PCF或者可信的AF上。
  12. 一种信息处理方法，其中，由PCF执行，所述方法包括：
    接收TSCTSF发送的同步指示和XRM组标识；
    根据所述同步指示和所述XRM组标识，生成策略控制和计费PCC规则或者激活预定义的PCC规则。
  13. 根据权利要求12所述的方法，其中，所述接收TSCTSF发送的同步指示和XRM组标识，包括：
    接收所述TSCTSF发送的所述同步指示和所述XRM组标识，以及时延信息和/或UEs IP地址。
  14. 根据权利要求13所述的方法，其中，所述接收所述TSCTSF发送的所述同步指示和所述XRM组标识，以及时延信息和/或UEs IP地址，包括：
    接收包含所述同步指示、和所述时延信息以及所述XRM组标识和/或所述UEs IP地址的授权创建或者更新请求；
    向所述TSCTSF发送所述授权创建或者更新请求的响应。
  15. 根据权利要求14所述的方法，其中，所述根据所述同步指示和所述XRM组标识，生成策略控制和计费PCC规则或者激活预定义的PCC规则，包括：
    当所述授权创建或者更新请求还包括所述TSCTSF根据所述时延信息计算的PDB时，根据所述同步指示、所述PDB、所述XRM组标识和/或所述UES IP地址，生成所述PCC规则或者激活预定义的所述PCC规则；
    或者，
    当所述授权创建或者更新请求不包括所述TSCTSF根据所述时延信息计算的PDB时，根据所述授权创建或者更新请求包含的所述时延信息计算PDB，根据所述PCF计算的PDB、所述XRM组标识和/或所述UEs IP地址，生成所述PCC规则或激活预定义的所述PCC规则。
  16. 根据权利要求15所述的方法，其中，所述根据所述同步指示、所述PDB、所述XRM组标识和/或所述UES IP地址，生成所述PCC规则或者激活预定义的所述PCC规则，包括：
    根据所述授权创建或者更新请求包含的PDB和最大突发数据量MDVB，设置数据流的PDB和突发数据量；
    根据所述数据流的PDB和所述突发数据量、所述XRM组标识和/或所述UEs IP地址，生成PCC规则或激活预定义的PCC规则。
  17. 根据权利要求14所述的方法，其中，所述方法还包括：
    确定是否授权创建会话。
  18. 根据权利要求12至17任一项所述的方法，其中，所述方法还包括：
    接收订阅请求；其中，所述订阅请求，用于请求订阅事件报告。
  19. 根据权利要求18所述的方法，其中，所述方法还包括：
    根据所述订阅请求，当数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告；
    和/或，
    根据所述订阅请求，当所述数据流的时延触发订阅事件时，向所述TSCTSF发送事件报告。
  20. 根据权利要求19所述的方法，其中，所述根据所述订阅请求，当数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告，包括：
    根据所述订阅请求，向用户面功能UPF和/或无线接入网络NG-RAN订阅所述数据流的时延；
    根据所述UPF和/或所述NG-RAN提供的所述数据流的时延，确定所述时延差；
    当所述时延差触发订阅事件时，向所述TSCTSF发送事件报告。
  21. 根据权利要求19所述的方法，其中，所述根据所述订阅请求，当数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告，包括：
    根据所述订阅请求，向所述UPF和/或无线接入网络NG-RAN订阅所述数据流的时延差；
    当所述UPF和/或无线接入网络NG-RAN提供的所述数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告。
  22. 根据权利要求19所述的方法，其中，所述根据所述订阅请求，当所述数据流的时延触发订阅事件时，向所述TSCTSF发送事件报告，包括：
    根据所述订阅请求，向用户面功能UPF和/或无线接入网络NG-RAN订阅所述数据流的时延；
    当所述用户面功能UPF和/或所述NG-RAN提供的数据流的时延触发订阅事件时，向所述TSCTSF发送事件报告。
  23. 根据权利要求19所述的方法，其中，所述根据所述订阅请求，当数据流的时延差触发订阅事件时，向所述TSCTSF发送事件报告，包括：
    根据所述订阅请求，向所述UPF和/或无线接入网络NG-RAN发送订阅请求；其中，所述订阅请求包括：数据流的时延差触发订阅事件的订阅请求；和/或，所述数据流的时延触发订阅事件的订阅请求；
    接收所述UPF和/或所述NG-RAN发送触发订阅事件的通知消息；
    根据所述通知消息，向所述TSCTSF发送事件报告。
  24. 根据权利要求19所述的方法，其中，所述订阅事件被触发，包括以下至少之一：
    所述数据流的时延大于或等于所述订阅事件对应的时延阈值；
    所述数据流的时延差大于或等于所述订阅事件对应的时延差阈值；
    所述订阅事件的定时器到达；
    接收到立即报告标志。
  25. 根据权利要求18所述的方法，其中，所述订阅请求包括：事件报告模式信息；
    其中，所述事件报告模式信息指示的所述事件报告的报告模式包括以下至少之一：
    立即报告模式；
    周期报告模式；
    触发报告模式。
  26. 根据权利要求20所述的方法，其中，所述方法还包括：
    当所述订阅事件被触发时，更新所述PCC规则。
  27. 根据权利要求25所述的方法，其中，所述当所述订阅事件被触发时，更新所述PCC规则，包括：
    当所述订阅事件被触发时，提升所述PCC规则授权的QoS；
    或者，
    当所述订阅事件被触发时，降低所述PCC规则授权的QoS。
  28. 一种信息处理方法，其中，由AF执行，所述方法包括：
    发送AF的会话创建请求，所述会话创建请求包括同步指示和XRM组标识；
    接收所述会话创建请求的会话创建响应。
  29. 根据权利要求28所述的方法，其中，所述会话创建请求还包括：时延信息和/或所述UEs IP地址。
  30. 根据权利要求29所述的方法，所述时延信息包括以下至少之一：
    双向时延；
    上行时延；
    下行时延；
    数据流的时延差。
  31. 根据权利要求27至30任一项所述的方法，其中，所述会话创建请求还包括以下至少之一：
    流描述；
    服务质量QoS信息和需求；
    所述AF的标识。
  32. 根据权利要求31所述的方法，其中，所述QoS信息和需求包括以下至少之一：
    QoS参数；
    QoS参考；
    备选的业务需求。
  33. 根据权利要求27所述的方法，其中，所述方法还包括：
    接收所述TSCTSF在订阅事件被触发时发送的通知消息。
  34. 根据权利要求27所述的方法，其中，所述发送AF的会话创建请求，包括：
    当所述AF存储有TSCTSF的地址时，根据所述TSCTSF的地址向所述TSCTSF发送所述AF的会话创建请求。
  35. 根据权利要求27所述的方法，其中，所述发送AF的会话创建请求，包括：
    当所述AF未存储TSCTSF的地址时，向网络开放功能NEF发送所述AF的会话创建请求。
  36. 一种信息处理方法，其中，由网络开放功能NEF执行，所述方法还包括：
    接收应用功能AF的会话创建请求，其中，所述会话创建请求包括同步指示和XRM组标识；
    获取接收所述会话创建请求的TSCTSF的地址；
    根据所述TSCTS F的地址，将所述会话创建请求发送给所述TSCTSF。
  37. 根据权利要求36所述的方法，其中，所述会话创建请求还包括：时延信息和/或用户设备UEs IP地址。
  38. 根据权利要求37所述的方法，其中，所述获取接收所述会话创建请求的TSCTSF的地址，包括：
    查询所述NEF预先存储的TSCTSF的地址；
    或者，
    将所述AF的标识和/或所述会话创建请求包含的XRM组标识和/或UEs IP地址，映射到网络名称DNN和/或网络切片标识，并根据所述DNN和/或网络切片标识映射发现所述TSCTSF的地址。
  39. 根据权利要求37或38所述的方法，其中，所述方法还包括：
    接收所述会话创建请求的会话创建响应；
    将所述会话创建响应发送给所述AF。
  40. 根据权利要求36或37所述的方法，其中，所述方法还包括：
    接收订阅事件被触发时所述TSCTSF发送的通知消息；
    将所述通知消息发送给所述AF。
  41. 一种扩展现实业务媒体XRM业务处理装置，其中，所述装置包括：
    第一接收模块，被配置为接收应用功能AF的会话创建请求，其中，所述会话创建请求包括同步指示和XRM组标识；
    第一发送模块，被配置为将所述同步指示以及所述XRM组标识发送给策略控制功能PCF。
  42. 一种信息处理装置，其中，所述装置包括：
    第二接收模块，被配置为接收TSCTSF发送的同步指示和XRM组标识；
    PCC规则模块，被配置为根据所述同步指示和所述XRM组标识，生成策略控制和计费PCC规则或者激活预定义的PCC规则。
  43. 一种信息处理装置，其中，所述装置包括：
    第三发送模块，被配置为发送AF的会话创建请求，所述会话创建请求包括同步指示和XRM组标识；
    第三接收模块，被配置为接收所述会话创建请求的会话创建响应。
  44. 一种信息处理装置，其中，所述装置还包括：
    第四接收模块，被配置为接收应用功能AF的会话创建请求，其中，所述会话创建请求包括同 步指示和XRM组标识；
    获取模块，被配置为获取接收所述会话创建请求的TSCTSF的地址；
    第四发送模块，被配置为根据所述TSCTSF的地址，将所述会话创建请求发送给所述TSCTSF。
  45. 一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够由所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如权利要求1至11、12至26、27至35或36至40任一项提供的方法。
  46. 一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现如权利要求1至11、12至26、27至35或36至40任一项提供的方法。
PCT/CN2022/092894 2022-05-13 2022-05-13 扩展现实媒体业务处理方法及装置、通信设备及存储介质 WO2023216277A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280001715.1A CN117413607A (zh) 2022-05-13 2022-05-13 扩展现实媒体业务处理方法及装置、通信设备及存储介质
PCT/CN2022/092894 WO2023216277A1 (zh) 2022-05-13 2022-05-13 扩展现实媒体业务处理方法及装置、通信设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/092894 WO2023216277A1 (zh) 2022-05-13 2022-05-13 扩展现实媒体业务处理方法及装置、通信设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023216277A1 true WO2023216277A1 (zh) 2023-11-16

Family

ID=88729538

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/092894 WO2023216277A1 (zh) 2022-05-13 2022-05-13 扩展现实媒体业务处理方法及装置、通信设备及存储介质

Country Status (2)

Country Link
CN (1) CN117413607A (zh)
WO (1) WO2023216277A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112437122A (zh) * 2020-11-08 2021-03-02 腾讯科技（深圳）有限公司 通信方法、装置、计算机可读介质及电子设备
WO2021242940A1 (en) * 2020-05-28 2021-12-02 Lenovo (United States) Inc. A Corporation Of Delaware Apparatus and method of determing a grouped operation mode on a wireless network
CN114271018A (zh) * 2019-08-19 2022-04-01 Lg 电子株式会社 用于中继非结构化业务的方法和中继ue

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114271018A (zh) * 2019-08-19 2022-04-01 Lg 电子株式会社 用于中继非结构化业务的方法和中继ue
WO2021242940A1 (en) * 2020-05-28 2021-12-02 Lenovo (United States) Inc. A Corporation Of Delaware Apparatus and method of determing a grouped operation mode on a wireless network
CN112437122A (zh) * 2020-11-08 2021-03-02 腾讯科技（深圳）有限公司 通信方法、装置、计算机可读介质及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "KI#1, KI#2 Solution proposal: Policy Control enhancements for multi-modal traffic", 3GPP DRAFT; S2-2202305, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20220406 - 20220412, 29 March 2022 (2022-03-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052133150 *

Also Published As

Publication number Publication date
CN117413607A (zh) 2024-01-16

Similar Documents

Publication Publication Date Title
CN107743096B (zh) 网络优化方法、装置、终端以及存储介质
WO2018196102A1 (zh) 信息传递方法、装置及计算机可读存储介质
WO2023216277A1 (zh) 扩展现实媒体业务处理方法及装置、通信设备及存储介质
US20230046894A1 (en) Network dataset processing method and apparatus, computer device, and storage medium
WO2022032540A1 (zh) Uav飞行控制、管控策略处理方法及装置、设备及介质
WO2023245455A1 (zh) 信息传输方法、装置、通信设备及存储介质
WO2024055330A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2024020755A1 (zh) 无线通信方法、装置、通信设备及存储介质
WO2024055328A1 (zh) 数据流的处理方法、装置、通信设备及存储介质
WO2023178578A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2024065207A1 (zh) 一种数据发送方法、装置以及可读存储介质
WO2024031396A1 (zh) 逻辑信道的调度方法、装置、通信设备及存储介质
WO2024031458A1 (zh) 资源配置方法、装置、存储介质以及终端
WO2024000518A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2024055334A1 (zh) 丢包处理方法、装置、通信设备及存储介质
WO2023212959A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2024055331A1 (zh) 信息处理方法以及装置、通信设备及存储介质
WO2024020756A1 (zh) 无线通信方法、装置、通信设备及存储介质
WO2024031354A1 (zh) 计费校正方法、装置、通信设备及存储介质
WO2024065134A1 (zh) 终端设备状态辅助运营方法、装置
WO2022061773A1 (zh) 数据流处理方法及装置、通信设备及存储介质
WO2024055313A1 (zh) 一种目标终端确定方法、装置、通信设备及存储介质
WO2023005898A1 (zh) 多终端联合会话管理方法、网络侧设备及终端
WO2024020760A1 (zh) 一种QoS流的控制方法、装置及计算机存储介质
WO2024098348A1 (zh) 信息处理方法及装置、通信设备及存储介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280001715.1

Country of ref document: CN

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

Ref document number: 22941227

Country of ref document: EP

Kind code of ref document: A1