WO2024148495A1

WO2024148495A1 - Information processing method and apparatus, and communication device and storage medium

Info

Publication number: WO2024148495A1
Application number: PCT/CN2023/071461
Authority: WO
Inventors: 吴锦花; 沈洋
Original assignee: 北京小米移动软件有限公司
Priority date: 2023-01-09
Filing date: 2023-01-09
Publication date: 2024-07-18
Also published as: CN118633319A

Abstract

Provided in the embodiments of the present disclosure are an information processing method and apparatus, and a communication device and a storage medium. The information processing method is executed by an AF, and comprises: sending requirement information, wherein the requirement information is used for indicating a bidirectional delay requirement of a data stream of a multimedia virtual reality (XRM) service.

Description

Information processing method and device, communication equipment and storage medium

Technical Field

The present disclosure relates to, but is not limited to, the field of communication technology, and in particular to an information processing method and apparatus, a communication device, and a storage medium.

Background technique

In mobile media services, extended reality (XR) services such as augmented reality (AR) or virtual reality (VR), cloud gaming services, video-based robot or drone remote control services, and the fifth generation of mobile communication technology (5G) networks, multimodal data is data that describes the same service or application and is input from the same device or different devices. These data may be output to one or more destination devices. The data streams in multimodal data often have a certain or even strong correlation, such as the synchronization of audio streams and video streams, and the synchronization of tactile data and visual data.

The characteristics of Multimedia Virtual Reality (XRM) services require the 5G wireless communication system (5G System, 5GS) to comprehensively consider the Quality of Service (QoS) characteristics of the relevant data flows of the service, such as whether the parameters such as the delay critical guaranteed bit rate (GBR), guaranteed bit rate (GFBR), packet delay budget (PDB) and/or maximum data burst volume (MDBV) can be met and coordinated at the same time. It involves multiple XRM data flows of a user equipment (UE) and the consistency of QoS authorization and execution of XRM data flows of multiple UEs. However, in the actual service process, the QoS authorization of each data flow will be directly affected by the network delay status and/or the delay requirements of the application function (AF) service, so as to affect whether the XRM service function can be successful.

Summary of the invention

Embodiments of the present disclosure provide an information processing method and apparatus, a communication device, and a storage medium.

According to a first aspect of an embodiment of the present disclosure, there is provided an information processing method, which is performed by an AF, and includes:

Sending requirement information, where the requirement information is used to indicate the requirement for the two-way delay of the data stream of the XRM service.

In some embodiments, the requirement information includes at least one of the following:

At least one required uplink delay value;

At least one required downlink delay value;

First indication information, wherein the first indication information is used to indicate a ratio of at least one uplink delay to a two-way delay and/or a ratio of at least one downlink delay to a two-way delay;

Second indication information, wherein the second indication information is used to indicate at least one threshold value of the ratio of uplink delay to the two-way delay and/or at least one threshold value of the ratio of downlink delay to the two-way delay;

third indication information, wherein the third indication information is used to indicate whether the uplink delay and the downlink delay in at least one set of two-way delays are the same;

Fourth indication information, wherein the fourth indication information is used to indicate that a data flow of the XRM service needs to consider a two-way delay;

Priority indication information, wherein the priority indication information is used to indicate the priority of uplink delay and/or the priority of downlink delay;

A configuration file, wherein the configuration file is used to indicate a required value of an uplink delay and/or a required value of a downlink delay in at least one set of two-way delays, or the configuration file is used to indicate: a required value of an uplink delay and priority indication information of an uplink delay in at least one set of two-way delays, and/or a required value of a downlink delay and priority indication information of a downlink delay.

In some embodiments, sending the demand information includes one of the following:

Sending demand information to the Policy Control Function (PCF);

Sending demand information to the Network Exposure Function (NEF), where the demand information is used by the NEF to send to the Time Sensitive Communication and Time Synchronization Function (TSCTSF) or PCF;

Send demand information to TSCTSF, where the demand information is used by TSCTSF to send to PCF.

In the AF session request process, the demand information is sent;

In the AF session update process, the demand information is sent;

Sending demand information in the business-specific parameter provision process;

In the process of setting policies for subsequent AF sessions, the requirement information is sent.

In some embodiments, the demand information is used by the PCF to determine predetermined rules and/or determine predetermined information.

In some embodiments, the predetermined rule includes at least one of the following:

Policy and Charging Control (PCC) rules;

QoS policy;

and / or,

Booking information, including at least one of the following:

At least one uplink delay value;

at least one downlink delay value;

QoS identifier, wherein the QoS identifier is used to indicate at least one QoS parameter.

In some embodiments, in the AF session request process, sending the requirement information includes:

In the AF session request process, a first request is sent, wherein the first request includes requirement information.

In some embodiments, the first request further includes at least one of the following:

A common identifier, wherein the common identifier is used to indicate all data flows in the group of XRM services;

UE address information;

UE identifier, used to indicate the UE related to the XRM service;

Application identifier, where the application identification information is used to indicate the XRM service;

Stream description;

Data Network Name (DNN);

Network Slice Selection Assistance Information (S-NSSAI);

QoS parameters.

In some embodiments, in the service-specific parameter provision process, sending the requirement information includes:

In the service-specific parameter provision process, a second request is sent, wherein the second request includes requirement information.

In some embodiments, the second request further includes at least one of the following:

XRM business identifier;

Business description, wherein the business description includes a common identifier;

Business parameters;

UE identifier, used to indicate the UE related to the XRM service;

UE group identifier, used to indicate a group of UEs or multiple UEs related to the XRM service;

Subscribe to events.

In some embodiments, the method comprises:

A subscription notification is received, wherein the subscription notification includes a report determined based on the requirement information.

In some embodiments, receiving a subscription notification includes one of:

Receive subscription notifications sent by the User Plane Function (UPF);

Receive a subscription notification sent by NEF; wherein the subscription notification is received by NEF from UPF, or the subscription notification is received by NEF from PCF;

Receive the subscription notification sent by PCF; wherein, the subscription notification is received by PCF from the session management function SMF, and the subscription notification is received by SMF from UPF.

According to a second aspect of an embodiment of the present disclosure, there is provided an information processing method, which is executed by a PCF, and includes:

Receive requirement information, where the requirement information is used to indicate a requirement for a two-way delay of a data stream of an XRM service.

At least one required uplink delay value;

At least one required downlink delay value;

In some embodiments, receiving the requirement information includes one of the following:

Receive demand information sent by AF;

receiving demand information sent by NEF, wherein the demand information is received by NEF from AF;

Receive the demand information sent by TSCTSF, where the demand information is received by TSCTSF from NEF or from AF.

In the AF session request process, receiving demand information;

In the AF session update process, receiving demand information;

In the business-specific parameter provision process, receive demand information;

In the process of setting a policy for a subsequent AF session, the requirement information is received.

In some embodiments, the method comprises at least one of the following:

Based on the demand information, determine the predetermined rules of data flow;

Based on the demand information, reservation information is determined.

In some embodiments, the predetermined rules include: PCC rules and/or QoS policies.

In some embodiments, the method comprises:

Sending an update request to a Session Management Function (SMF), wherein the update request includes: PCC rules and/or QoS policies;

The update request is used by SMF to update the PCC rules and/or QoS policies stored in SMF.

In some embodiments, based on the demand information, determining the predetermined information includes at least one of the following:

Determine, based on the demand information, at least one uplink delay value and/or at least one downlink delay value;

Determine at least one uplink delay value and/or at least one downlink delay value based on the demand information and the local configuration information; wherein the local configuration information includes: operator policy, default configuration information and/or subscription information;

Based on the demand information, a QoS identifier of the data flow is determined, wherein the QoS identifier is used to indicate at least one QoS parameter.

In some embodiments, the method comprises one of the following:

Based on the demand information, determine the QoS control at the service data flow (SDF) level or the QoS flow level; wherein the QoS control includes: QoS authorization and/or OoS update;

Based on the demand information and local configuration information, determine the QoS control of the SDF level or the QoS level; wherein the local configuration information includes: operator policy, default configuration information and/or subscription information.

In some embodiments, in the AF session request process, receiving requirement information includes:

In the AF session request process, a first request is received, wherein the first request includes requirement information.

UE address information;

UE identifier, used to indicate the UE related to the XRM service;

Stream description;

DNN;

S-NSSAI;

QoS parameters.

In some embodiments, in the service-specific parameter provision process, receiving requirement information includes:

In the service-specific parameter provision process, a second request is received, wherein the second request includes requirement information.

XRM business logo;

Business parameters;

UE identifier, used to indicate the UE related to the XRM service;

Subscribe to events.

According to a third aspect of an embodiment of the present disclosure, there is provided an information processing method, which is performed by a first network function and includes:

In some embodiments, the first network function is NEF; receiving demand information includes: receiving demand information sent by AF.

In some embodiments, the method comprises one of the following:

Send demand information to PCF;

In some embodiments, the method comprises:

Receiving a subscription notification sent by the UPF or PCF, wherein the subscription notification includes a report determined based on the demand information;

Send subscription notification to AF.

In some embodiments, the first network function is a TSCTSF; receiving the requirement information comprises one of the following:

Receive demand information sent by AF;

Receive demand information sent by NEF.

In some embodiments, the method includes sending demand information to the PCF.

According to a fourth aspect provided by an embodiment of the present disclosure, there is provided an information processing device, including:

The first sending module is configured to send requirement information, wherein the requirement information is used to indicate the requirement for a two-way delay of a data stream of an XRM service.

At least one required uplink delay value;

At least one required downlink delay value;

In some embodiments, the first sending module is configured to perform one of the following:

Send demand information to PCF;

Sending demand information to NEF, where the demand information is used by NEF to send to TSCTSF or PCF;

In the AF session request process, the demand information is sent;

In the AF session update process, the demand information is sent;

PCC Rules;

QoS policy;

and / or,

Booking information, including at least one of the following:

At least one uplink delay value;

at least one downlink delay value;

In some embodiments, the first sending module is configured to send a first request in an AF session request process, wherein the first request includes requirement information.

UE address information;

UE identifier, used to indicate the UE related to the XRM service;

Stream description;

DNN;

S-NSSAI;

QoS parameters.

In some embodiments, the first sending module is configured to send a second request in the service-specific parameter provision process, wherein the second request includes requirement information.

XRM business logo;

Business parameters;

UE identifier, used to indicate the UE related to the XRM service;

Subscribe to events.

In some embodiments, the apparatus includes: a first receiving module configured to receive a subscription notification, wherein the subscription notification includes a report determined based on demand information.

In some embodiments, the first receiving module is configured to perform one of the following:

Receive subscription notifications sent by UPF;

According to a fifth aspect of an embodiment of the present disclosure, there is provided an information processing device, including:

The second receiving module is configured to receive requirement information, wherein the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service.

At least one required uplink delay value;

At least one required downlink delay value;

In some embodiments, the second receiving module is configured to perform one of the following:

Receive demand information sent by AF;

In the AF session request process, receiving demand information;

In the AF session update process, receiving demand information;

In some embodiments, the apparatus includes: a first processing module; the first processing module is configured to perform at least one of the following:

Based on the demand information, reservation information is determined.

In some embodiments, the apparatus includes: a second sending module configured to send an update request to the SMF, wherein the update request includes: a PCC rule and/or a QoS policy;

In some embodiments, the first processing module is configured to perform at least one of the following:

In some embodiments, the first processing module is configured to perform one of the following:

Based on the demand information, determine the QoS control of the service data flow SDF level or QoS flow level; wherein the QoS control includes: QoS authorization and/or OoS update;

In some embodiments, the second receiving module is configured to receive a first request in the AF session request process, wherein the first request includes requirement information.

UE address information;

UE identifier, used to indicate the UE related to the XRM service;

Stream description;

DNN;

S-NSSAI;

QoS parameters.

In some embodiments, the second receiving module is configured to receive a second request in the service-specific parameter providing process, wherein the second request includes requirement information.

XRM business logo;

Business parameters;

UE identifier, used to indicate the UE related to the XRM service;

Subscribe to events.

According to a sixth aspect of an embodiment of the present disclosure, there is provided an information processing device, including:

The third receiving module is configured to receive requirement information, wherein the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service.

In some embodiments, the first network function is NEF; the third receiving module is configured to receive demand information sent by AF.

In some embodiments, the apparatus includes: a third sending module; the third sending module is configured to perform one of the following:

Send demand information to PCF;

In some embodiments, the third receiving module is configured to receive a subscription notification sent by the UPF or the PCF, wherein the subscription notification includes a report determined based on the demand information;

The third sending module is configured to send a subscription notification to the AF.

In some embodiments, the first network function is TSCTSF; and the third receiving module is configured to perform one of the following:

Receive demand information sent by AF;

Receive demand information sent by NEF.

In some embodiments, the third sending module is configured to send demand information to the PCF.

According to a seventh aspect of an embodiment of the present disclosure, there is provided an information processing system, including an AF, a first network function, and a PCF;

The AF is configured to: send requirement information to the PCF or to the first network function, wherein the requirement information is used to indicate a requirement for a two-way delay of a data stream of a multimedia extended reality XRM service;

The first network function is configured to send demand information to the PCF.

According to an eighth aspect of an embodiment of the present disclosure, a communication device is provided, the communication device including:

processor;

a memory for storing processor-executable instructions;

The processor is configured to implement the information processing method of any embodiment of the present disclosure when running executable instructions.

According to a ninth aspect of an embodiment of the present disclosure, a computer storage medium is provided, wherein the computer storage medium stores a computer executable program, and when the executable program is executed by a processor, the information processing method of any embodiment of the present disclosure is implemented.

The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

In the embodiment of the present disclosure, AF sends requirement information, which is used to indicate the requirement for two-way delay of the data flow of the XRM service; in this way, taking into account the real-time or quasi-real-time two-way delay status of the data flow of the XRM service, it can be helpful to determine the QoS authorization of each data flow in the SRM service, thereby accurately determining whether the XRM service function support can be successful.

It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Fig. 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment.

Fig. 2 is a schematic diagram showing an information processing method according to an exemplary embodiment.

Fig. 3 is a schematic diagram showing an information processing method according to an exemplary embodiment.

Fig. 4 is a schematic diagram showing an information processing method according to an exemplary embodiment.

Fig. 5 is a schematic diagram showing an information processing method according to an exemplary embodiment.

Fig. 6 is a schematic diagram showing an information processing method according to an exemplary embodiment.

Fig. 7 is a schematic diagram showing an information processing method according to an exemplary embodiment.

Fig. 8 is a schematic diagram showing an information processing method according to an exemplary embodiment.

Fig. 9 is a schematic diagram showing an information processing method according to an exemplary embodiment.

Fig. 10 is a schematic diagram showing an information processing method according to an exemplary embodiment.

Fig. 11 is a block diagram showing an information processing device according to an exemplary embodiment.

Fig. 12 is a block diagram showing an information processing device according to an exemplary embodiment.

Fig. 13 is a block diagram showing an information processing device according to an exemplary embodiment.

Fig. 14 is a block diagram of a base station according to an exemplary embodiment.

FIG15 is a schematic diagram of a network architecture of a 5G system according to an exemplary embodiment.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the embodiments of the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the embodiments of the present disclosure as detailed in the appended claims.

The terms used in the disclosed embodiments are only for the purpose of describing specific embodiments and are not intended to limit the disclosed embodiments. The singular forms of "a" and "the" used in the disclosed embodiments and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and/or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

It should be understood that although the terms first, second, third, etc. may be used to describe various information in the disclosed embodiments, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the disclosed embodiments, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

Please refer to FIG1 , which shows a schematic diagram of the structure of a wireless communication system provided by an embodiment of the present disclosure.

As shown in FIG1 , the wireless communication system may include: a plurality of user equipments 110 and a plurality of access network equipments 120. The wireless communication system may be a 4th generation mobile communication technology (4G) system, also known as a long term evolution (LTE) system; or, the wireless communication system may be a 5G system, also known as a new air interface system or a 5G NR system. Alternatively, the wireless communication system may be a next generation system of the 5G system, etc.

The user equipment 110 may be a device that provides voice and/or data connectivity to a user. The user equipment 110 may communicate with one or more core networks via a radio access network (RAN). The user equipment 110 may be an IoT user equipment, such as a sensor device, a mobile phone (or a "cellular" phone), and a computer with an IoT user equipment, for example, a fixed, portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted device. For example, a station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote user equipment (remote terminal), an access terminal, a user device (user terminal), a user agent, a user device, or a user equipment (user equipment). Alternatively, the user equipment 110 may also be a device of an unmanned aerial vehicle. Alternatively, the user device 110 may be a vehicle-mounted device, such as a driving computer with wireless communication function, or a wireless user device connected to a driving computer. Alternatively, the user device 110 may be a roadside device, such as a street lamp, a signal lamp, or other roadside device with wireless communication function.

The access network device 120 may be a network side device in a wireless communication system. The access network device 120 may be an evolved base station (eNB) used in a 4G system. Alternatively, the access network device 120 may also be a base station (gNB) using a centralized distributed architecture in a 5G system. Alternatively, the access network device 120 may also be an access network in a 5G system, which may be called a new generation radio access network (NG-RAN). When the access network device 120 adopts a centralized distributed architecture, it generally includes a centralized unit (CU) and at least two distributed units (DU). The centralized unit is provided with a protocol stack of a packet data convergence protocol (PDCP) layer, a radio link layer control protocol (RLC) layer, and a media access control (MAC) layer; the distributed unit is provided with a physical (PHY) layer protocol stack. The embodiment of the present disclosure does not limit the specific implementation method of the access network device 120.

A wireless connection may be established between the access network device 120 and the user equipment 110 via a wireless air interface. In different implementations, 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, for example, the wireless air interface is a new air interface; or, the wireless air interface may also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.

In some embodiments, an E2E (End to End) connection may also be established between the user devices 110. For example, vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and vehicle-to-pedestrian (V2P) communication in vehicle-to-everything (V2X) communication.

Here, the above user equipment can be considered as the terminal equipment in the following embodiments.

In some embodiments, the wireless communication system may further include a core network device 130 .

Several access network devices 120 are respectively connected to core network devices 130. The core network device 130 may be a core network device in a wireless communication system, for example, the core network device 130 may be a mobility management entity (MME) in an evolved packet core (EPC). Alternatively, the core network device may also be other core network devices, such as a Serving GateWay (SGW), a Public Data Network GateWay (PGW), a Policy and Charging Rules Function (PCRF), or a Home Subscriber Server (HSS), etc.; or the core network device 130 may also be a core network device in 5G; for example, it may be a Policy Control Function (PCF), or a Session Management Function (SMF), an Access and Mobility Management Function (AMF), a Unified Data Management (UDM), or a User Plane Function (UPF), etc. The embodiments of the present disclosure do not limit the implementation form of the core network device 130.

In order to facilitate the understanding of those skilled in the art, the embodiments of the present disclosure list multiple implementation methods to clearly illustrate the technical solutions of the embodiments of the present disclosure. Of course, those skilled in the art can understand that the multiple embodiments provided by the embodiments of the present disclosure can be executed separately, or can be executed together with the methods of other embodiments of the embodiments of the present disclosure, or can be executed together with some methods in other related technologies separately or in combination; the embodiments of the present disclosure do not limit this.

In order to better understand the technical solution described in any embodiment of the present disclosure, first, the application scenarios to which the present disclosure is applicable are partially described:

The XRM service characteristics require 5GS to comprehensively consider the QoS characteristics of the relevant data flows of the service, such as whether parameters such as GBR, GFBR, PDB and/or MDBV can be met and coordinated at the same time. It involves multiple XRM data flows of a UE, and XRM data flows of multiple UEs, and the consistency of QoS authorization and execution between each other. Among them, uplink-downlink transmission coordination to meet Round-Trip latency requirements is a key issue in 5GS XRM service research.

In related technologies, AF may provide PDB as latency requirements when requesting QoS, or provide a round-trip requirement indication (RT requirement indication) as an indication of whether the two-way delay needs to be considered, for network authorization reference.

However, the delay status in the actual business process is affected by various factors in the network and changes dynamically and continuously. In particular, XRM services often require multiple data streams within the UE, or different data streams of multiple UEs, to successfully authorize the corresponding QoS to support business implementation. Therefore, the real-time or quasi-real-time delay status of the network and the real-time delay requirements of the AF service will directly affect the QoS authorization of each data stream, and even affect whether the 5GS XRM service function support can be successful. However, the 5GS system currently does not have a perfect mechanism to support this requirement, and there is no corresponding technical solution to support the QoS authorization and optimization of the two-way delay requirements of the PCF XRM service data flow.

As shown in FIG. 2 , the present disclosure embodiment provides an information processing method, which is executed by an application function (Application Function) AF, including:

Step S21: Sending requirement information, wherein the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service.

In some embodiments, the AF may send the requirement information to a network node, for example, the network node may be selected from a PCF and a first network function, wherein the first network function may be an SMF and a TSCTSF.

In the embodiments of the present disclosure, AF, PCF, SMF, TSCTSF, etc. may all be logical nodes or functions that can be flexibly deployed in a communication network.

In the embodiment of the present disclosure, the requirement information may also be: a requirement for a two-way delay of a data stream for indicating a service. The service may be, but is not limited to, an XRM service; the service may be any service, for example, an XR service.

An information processing method provided in an embodiment of the present disclosure may include: sending requirement information, wherein the requirement information may be two-way delay requirement information, or the requirement information is used to indicate the requirement for two-way delay.

In one embodiment, the demand information is used to indicate the demand for enhanced two-way delay. Exemplarily, the demand information is used to indicate the demand for enhanced two-way delay of the data stream of the XRM service. Here, the enhanced two-way delay is relative to the demand involving only delay but not considering uplink and downlink delays, or the enhanced two-way delay is relative to the demand involving only two-way delay but not specifically indicating the demand value, ratio, ratio threshold and/or priority of the two-way delay, etc.

In one embodiment, the requirement information may be two-way delay requirement information, or the requirement information may be RT delay requirement information.

In one embodiment, the XRM service in step S21 may be at least one XRM service; the XRM service may be a service of one UE, or may be a service of multiple UEs. The at least one mentioned in the embodiment of the present disclosure may be one or more; and the multiple may be two or more.

In one embodiment, the XRM service in step S21 may also be replaced by a multimodal data service. That is, the AF may send demand information to the network device, wherein the demand information is used to indicate the demand for the two-way delay of the data flow of the multimodal data service. Of course, it should be understood that the XRM service and the multimodal data service are only examples, and other service types are also possible.

In one embodiment, the two-way delay may include, but is not limited to, an uplink delay and a downlink delay, or a round-trip two-way delay.

Here, the requirement information may be used to indicate the requirement of at least one set of two-way delay of the data stream of the XRM service. In the embodiment of the present disclosure, the at least one set may be one set or multiple sets; the multiple sets may be two sets or more than two sets.

In one embodiment, the two-way delay can be: round-trip latency, or two-way delay budget, or uplink and downlink packet delay budget (PDB).

at least one required uplink delay value and/or at least one required downlink delay value;

at least one uplink delay requirement value and priority indication information indicating the uplink delay priority;

at least one downlink delay requirement value and priority indication information indicating a downlink delay priority;

In another embodiment, the demand information may further include: a demand value of a two-way delay. Here, the demand information may include the demand information of the two-way delay, and at least one of the following information: a demand value of an uplink delay and/or a demand value of a downlink delay in a set of two-way delays, first indication information, second indication information, third indication information, fourth indication information, and priority indication information.

Exemplarily, the demand information includes a demand value of an uplink delay and/or a demand value of a downlink delay in a set of two-way delays, and the demand value is a specific value. Alternatively, the demand information includes multiple sets of two-way delays, and one uplink delay in a two-way delay corresponds to one demand value and/or one downlink delay corresponds to one demand value. Here, the demand value of the uplink delay and the demand value of the downlink delay in the set of two-way delays can be the same or different; the demand values of the uplink delay in the multiple sets of two-way delays are different and/or the demand values of the downlink delay are different.

Exemplarily, the first indication information is used to indicate the proportion of the uplink delay in the two-way delay and/or the proportion of the downlink delay in the two-way delay in at least one set of two-way delays. Here, the proportion of the uplink delay in the two-way delay and the proportion of the downlink delay in the two-way delay in the set of two-way delays may be the same or different; for example, the proportion of the uplink delay in the two-way delay is 40%, and the proportion of the downlink delay in the two-way delay is 60%; for another example, the proportion of the uplink delay in the two-way delay and the proportion of the downlink delay in the two-way delay are both 50%. Here, the proportion of the uplink delay to the two-way delay and/or the proportion of the downlink delay to the two-way delay in the multiple sets of two-way delays may also be: the proportion of the uplink delay to the two-way delay in the first set of two-way delay is 40%, the proportion of the uplink delay to the two-way delay in the second set of two-way delay is 50%, and the proportion of the downlink delay to the two-way delay in the third set of two-way delay is 70%; here, when the proportion of the uplink delay to the two-way delay in the two-way delay is known, the proportion of the downlink delay to the two-way delay in the set of delays can be determined, or, when the proportion of the downlink delay to the two-way delay in the two-way delay is known, the proportion of the uplink delay to the two-way delay in the set of delays can be determined; for example, if the proportion of the uplink delay to the two-way delay in the first set of two-way delay is 40%, then the proportion of the downlink delay to the two-way delay in the first set of two-way delay may be 60%.

Exemplarily, the second indication information is used to indicate the ratio threshold of the uplink delay to the two-way delay and/or the ratio threshold of the downlink delay to the two-way delay in at least one set of two-way delays. The ratio threshold can also be used for ratio interval replacement; for example, the ratio threshold of the uplink delay to the two-way delay can be 40%, and the ratio interval of the uplink delay to the two-way delay can be less than or equal to 40%. Here, the ratio threshold can be the lowest value of the ratio, or the highest value, or the ratio interval value. Here, the ratio threshold of the uplink delay to the two-way delay in the set of two-way delays and the ratio threshold of the downlink delay to the two-way delay can be the same or different; for example, the ratio threshold of the uplink delay to the two-way delay is not less than 40%, and the ratio threshold of the downlink delay to the two-way delay is not more than 60%; for another example, the ratio threshold of the uplink delay to the two-way delay and the ratio threshold of the downlink delay to the two-way delay are both not less than 40%. Here, the threshold value of the proportion of uplink delay to two-way delay and/or the threshold value of the proportion of downlink delay to two-way delay in the multiple sets of two-way delays may also be: the threshold value of the proportion of uplink delay to two-way delay in the first set of two-way delay is not less than 40%, the threshold value of the proportion of uplink delay to two-way delay in the second set of two-way delay is not higher than 40%, the threshold value of the proportion of downlink delay to two-way delay in the third set of two-way delay is 50%, and the threshold value of the proportion of downlink delay to two-way delay in the fourth set of two-way delay is: greater than or equal to 30% and less than or equal to 50%.

Exemplarily, the third indication information can be used to indicate whether the uplink delay is the same as or different from the downlink delay in the two-way delay. Here, the third indication information includes 3 bits; the first bit is the first value, which can be used to indicate that the required value of the uplink delay in the first set of two-way delays is the same as the required value of the downlink delay; the second bit is the second value, which is used to indicate that the required value of the uplink delay in the second set of two-way delays is different from the required value of the downlink delay; and the third bit is the second value, which is used to indicate that the required value of the uplink delay in the third set of two-way delays is different from the required value of the downlink delay.

Exemplarily, the fourth indication information may be the RT requirement indication in the above embodiment, which is used to indicate the requirement of considering the two-way delay.

Exemplarily, the priority indication information is used to indicate the priority of the uplink delay and/or downlink delay in at least one set of two-way delays. Here, the higher the priority of the uplink delay and/or downlink delay in the two-way delay, the more likely the two-way delay will be considered for execution; or, the lower the priority of the uplink delay and/or downlink delay in the two-way delay, the less likely the two-way delay will be considered for execution.

In the embodiment of the present disclosure, AF sends requirement information, which is used to indicate the requirement for two-way delay of the data flow of the XRM service; in this way, taking into account the real-time or quasi-real-time two-way delay status of the data flow of the XRM service, it can be helpful to determine the QoS authorization of each data flow in the SRM service, so as to accurately determine whether the XRM service function support can be successful.

It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.

In some embodiments, sending the demand information in step S21 may include sending the demand information to the second network function. Here, the second network function is a logical node or function that can be flexibly deployed in the core network. Exemplarily, the second network function may be, but is not limited to, PCF, NEF and/or TSCTSFH, etc.

In some embodiments, the sending requirement information in step S21 includes one of the following:

Send demand information to PCF;

That is, the AF can send the demand information to different network devices as needed, and can send the demand information to the PCF directly or indirectly. For example, the demand information can be sent to the PCF via one or both of the NEF and the TSC TSF.

The present disclosure provides an information processing method, which is performed by an AF and includes one of the following:

Send demand information to PCF;

Exemplarily, the AF sends the requirement information to the PCF. In this way, the AF can directly send the requirement information to the PCF, so that the PCF can directly determine the value of the uplink and downlink delay of each data flow based on the requirement information.

Exemplarily, the AF sends demand information to the NEF, and the NEF sends the demand information to the PCF; or the AF sends demand information to the NEF, the NEF sends the demand information to the TSCTSF, and the TSCTSF sends the demand information to the PCF. Here, after receiving the demand information, the NEF may directly forward the demand information to the PCF or TSCTSF, or the NEF may first perform authorization authentication, and then forward the demand information to the PCF or TSCTSF after the authorization authentication is passed. In this way, the demand information sent by the AF can be forwarded to the PCF by the NEF, thereby achieving successful transmission of the demand information; and, authorization authentication can also be performed based on the NEF to verify whether the AF is trustworthy. If so, the NEF will forward the demand information, thereby improving the security of the transmission of the demand information.

Exemplarily, the AF sends the demand information to the TSCTSF, and the TSCTSF sends the demand information to the PCF. In this way, the AF can also forward the demand information to the PCF through the TSCTSF, thereby successfully achieving the successful transmission of the demand information.

In some embodiments, sending the demand information in step S21 includes one of the following:

In the AF session request process, the demand information is sent;

In the AF session update process, the demand information is sent;

It should be understood that the AF may send the demand information in different processes, and the content of the sent demand information may be the same or different. The specific content of the demand information has been described in detail in the above embodiment, and will not be repeated here.

As shown in FIG3 , the present disclosure embodiment provides an information processing method, which is executed by AF, including:

Step S31: sending requirement information in the AF session request process; or sending requirement information in the AF session update process; or sending requirement information in the service specific parameter provision process; or sending requirement information in the policy setting process for subsequent AF sessions.

Exemplarily, the AF session request process can be described in the communication protocol as: AF session with required QoS procedure. The AF session update process can be described in the communication protocol as: AF session with required QoS update procedure. The service specific parameter provisioning process can be described in the communication protocol as: Service specific parameter provisioning. The policy setting process for subsequent AF sessions can be described in the communication protocol as: Set a policy for a future AF session.

Exemplarily, setting a policy flow for a subsequent AF session may refer to a flow of policies, data, or service characteristics related to the service functions of the AF before the AF session request is started. Here, setting a policy flow for a subsequent AF session refers to a flow related to setting a future AF session when the AF session itself is not started.

In some embodiments, in the AF session request process, sending the requirement information includes: in the AF session request process, sending a first request, wherein the first request includes the requirement information.

An embodiment of the present disclosure provides an information processing method, which is executed by an AF, and includes: in an AF session request process, sending a first request, wherein the first request includes demand information.

In one embodiment, the first request may be an AF request; the AF request may be an AF session resource request.

In some embodiments, the first request includes demand information and XRM service information. Here, the XRM service information includes but is not limited to at least one of the following: common identification, UE address information, UE identifier, application identifier, flow identification, DNN, S-NSSAI and QoS parameters.

In some embodiments, the first request also includes at least one of the following: a common ID, wherein the common ID is used to indicate all data flows in the group of the XRM service; UE address information; a UE identifier, used to indicate a UE related to the XRM service; an application identifier, wherein the application identification information is used to indicate the XRM service; a flow description; a DNN; S-NSSAI; and QoS parameters.

Exemplarily, multiple data streams are processed as a group, and the common identifier is used to identify all data streams in the group; the multiple data streams can be multiple data streams in one UE or multiple data streams in multiple UEs. Exemplarily, the application identifier can be an AF identifier application ID (AF Identifier Application ID). The flow description is used to indicate the characteristic information of the data stream.

Exemplarily, the UE address information may be address information of a UE related to an XRM service. The address information may be, but is not limited to, an IP address. The UE identifier may be a string used to identify any UE, and the string may include at least one character; the UE identifier may be, but is not limited to, a Subscription Concealed Identifier (SUCI), a Subscriber Permanent Identifier (SUPI), or an index or number, etc.

Exemplarily, QoS parameters may be, but are not limited to, PDU Set Error Rate (PSER), PDU Set Delay Budget (PSDB) and/or PDU Set Integrated Indication (PSII), etc.

In the disclosed embodiment, the purpose of sending the requirement information of the two-way delay requirement in the AF session request can be achieved by sending the requirement information in the AF session request process. And the requirement information can be sent through the first request, for example, through the AF request, so that two functions can be achieved through one first request. And the first request also includes XRM service information, so that the core network element can determine QoS authorization based on the requirement information and XRM service information.

In some embodiments, in the process of providing business-specific parameters, sending the requirement information includes: in the process of providing business-specific parameters, sending a second request, wherein the second request includes the requirement information.

An embodiment of the present disclosure provides an information processing method, which is executed by AF, including: sending a second request in a service-specific parameter provision process, wherein the second request includes demand information.

In one embodiment, the second request information includes: requirement information, and XRM service or multiple data service specific parameters.

In some embodiments, the second request also includes at least one of the following: an XRM service identifier; a service description, wherein the service description includes a common identifier; service parameters; a UE identifier for indicating a UE related to the XRM service; a UE group identifier for indicating a group of UEs or multiple UEs related to the XRM service; and a subscription event.

Exemplarily, the XRM service identifier is used to indicate the XRM service. The service description is used to identify the XRM service or the multimodal data service; specifically, the service description may include but is not limited to at least one of the following: a public identifier, an XRM service identifier, an AF service identifier (AF-Service-Identifier) or an external application identifier (Application Identifier). Here, the service description may identify the XRM service through a common identifier or may identify the XRM through an XRM service identifier. The service description may identify the XRM service through an AF service identifier (AF-Service-Identifier) or an external application identifier (Application Identifier).

Exemplarily, service parameters are used to indicate AF guidance information determined by policies and/or QoS parameters related to XRM services or multimodal data services. Service parameters may include, but are not limited to, at least one of the following: a list of rules that associate XRM service or multiple data Service application traffic, UE policy parameters, common identification, group identification, DNN and S-NSSAI, session and service continuity (Session and Service Continuity, SSC) mode, and priorities of related rules (for example, priority of alternative QoS parameters, location or time window priority and/or routing selection priority, etc.).

Exemplarily, subscription to events may be used to indicate execution and/or change events of subscription session management (SM) policies or access management (AM) policies or UE policies, etc., or may be used to indicate QoS monitoring events.

In the disclosed embodiment, the purpose of sending the demand information of the two-way delay demand in the service-specific parameter provision process can be achieved by sending the demand information in the service-specific parameter provision process. And the demand information can be sent through a second request, such as an AF request, so that two functions can be achieved through one second request. And the second request also includes information such as service description or service parameters, so that the core network element can determine QoS authorization based on the demand information and service description or service parameters.

Of course, in other embodiments, the AF may also provide the demand information to core network devices such as the PCF in an AF session update process or in a policy setting process for a subsequent AF session.

In some embodiments, the requirement information is used by the PCF to determine a predetermined rule and/or predetermined information. Exemplarily, the AF sends the requirement information to the PCF, the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service; the requirement information is used for the PCF to determine the predetermined rule and/or predetermined information.

In one embodiment, the predetermined rule includes at least one of the following:

Policy and Charging Control (PCC) rules;

QoS policy;

and / or,

Booking information, including at least one of the following:

At least one uplink delay value;

at least one downlink delay value;

Exemplarily, the PCC rule may be any rule related to charging, which is not limited here. The QoS policy may be any policy related to the quality of service of the data flow, which is not limited here.

Exemplarily, a QoS identifier can be used to identify at least one QoS characteristic of a data stream, and a QoS characteristic can be indicated by a QoS parameter. The QoS identifier can be a 5G QoS identifier (i.e., 5QI). Here, the QoS identifier can be used to identify at least one of the following: the address of the destination device of the data stream, the destination port of the data stream, the delay of the data stream, the bandwidth corresponding to the delay, the bit error rate of the data stream, and the scenario adapted by the data stream (such as conversation, voice or video, etc.).

In another embodiment, the demand information is used by the PCF to determine the PCC rules, and the PCC rules are used by the PCF to determine the QoS identifier.

In another embodiment, the demand information is used by the PCF to determine QoS control at the service data packet (SDF) level or the QoS flow level; wherein the QoS control includes but is not limited to: QoS authorization and/or OoS update.

In another embodiment, the demand information and the local configuration information are used by the PCF to determine the predetermined rules and/or predetermined information; and/or, the demand information and the local configuration information are used by the PCF to determine the QoS control of the SDF level or the QoS flow level. Here, the local configuration information can be but is not limited to at least one of the following: operator policy, default configuration information and/or subscription information.

In the disclosed embodiment, the demand information can be provided to the PCF through the AF, so that the PCF can determine the value of the two-way delay of the data flow of the XRM service, the PCC rule, the QoS policy and/or the QoS identification, etc. based on the demand information, so that the PCF can accurately determine the QoS authorization of the data flow of the XRM service, thereby accurately determining whether the XRM service function of at least one UE is successful.

As shown in FIG4 , the embodiment of the present disclosure provides an information processing method, which is executed by AF, including:

Step S41: receiving a subscription notification, wherein the subscription notification includes a report determined based on the demand information.

Exemplarily, the report determined by the demand information may be, but is not limited to: measured UL delay and/or DL delay, and/or measured two-way delay. Here, after receiving the demand information, the UPF and other network elements determine the measured UL delay and/or DL delay based on the demand information; the UPF may carry the UL delay and/or DL delay in the report.

In another embodiment, the subscription notification may include measurement information for determination based on the demand information.

In one embodiment, step S41 may be after step S21, that is, the AF first sends the demand information and then receives the subscription notification. However, it should be understood that in some embodiments, the AF may also receive the subscription notification, which includes information such as reports determined by the network device based on the demand information obtained in other ways.

In one embodiment, the AF sends the demand information to the UPF; the AF receives the subscription notification determined by the UPF based on the demand information. Here, the AF sending the demand information to the UPF may be: the AF directly sends the demand information to the UPF; or the AF sends the demand information to the NEF, and the NEF sends the demand information to the UPF.

In another embodiment, the demand information is used by the PCF to forward to the UPF, and the demand information is used by the UPF to determine the subscription notification. Exemplarily, the AF sends the demand information to the PCF, and the PCF sends the demand information to the UPF; the UPF determines a report based on the demand information, and the UPF carries the report in the subscription notification to send to the AF. Here, the PCF sending the demand information to the UPF can be: the PCF sends the demand information to the SMF, and the SMF sends the demand information to the UPF.

In some embodiments, receiving a subscription notification in step S41 includes one of the following:

Receive subscription notifications sent by UPF;

The present disclosure provides an information processing method, which is performed by an AF, including:

Receive subscription notifications sent by UPF;

Exemplarily, the UPF may send the subscription notification to the AF based on the user plane reporting method. For example, the UPF directly sends the subscription notification to the AF. For another example, the UFP sends the subscription notification to the NEF, and the NEF sends the subscription notification to the AF.

Exemplarily, UPF may send the subscription notification to AF based on the control plane reporting method. For example, UPF sends the subscription notification to SMF, SMF sends the subscription notification to PCF, and PCF sends the subscription notification to AF. For another example, UPF sends the subscription notification to SMF, SMF sends the subscription notification to PCF, PCF sends the subscription notification to NEF, and NEF sends the subscription notification to AF.

In the disclosed embodiment, the AF can receive the subscription notification reported by the UPF based on the user plane reporting method or the control plane reporting method, so as to adapt to the reception of subscription notifications in more application scenarios. And it is conducive to the AF to provide demand information to the PCF based on the subscription notification.

It should be understood that before receiving the subscription notification sent by the network device, the AF may first send demand information to the network device, so that the network device sends the subscription notification based on the demand information.

In response to receiving requirement information, such as a UPF, a measured UL delay and/or DL delay, and/or a measured two-way delay may be obtained.

The following is an information processing method, which is executed by PCF and is similar to the description of the information processing method executed by AF mentioned above; and, for technical details not disclosed in the embodiment of the information processing method executed by PCF, please refer to the description of the example of the information processing method executed by AF, which will not be described in detail here.

As shown in FIG5 , the embodiment of the present disclosure provides an information processing method, which is executed by a PCF and includes:

Step S51: receiving requirement information, wherein the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service.

In some embodiments of the present disclosure, AF, PCF, SMF and TSCTSF may be AF, PCF, SMF and TSCTSF in the above embodiments, respectively; demand information may be demand information in the above embodiments; and two-way delay may be two-way delay in the above embodiments. Detailed description has been given in the above embodiments and will not be repeated here.

Exemplarily, the two-way delay may include but is not limited to: uplink delay and downlink delay, or round-trip two-way delay. The two-way delay may be: round-trip latency, or two-way delay budget, or uplink and downlink packet delay budget (PDB).

Exemplarily, the requirement information includes at least one of the following:

Exemplarily, the demand information includes a demand value of an uplink delay and/or a demand value of a downlink delay in at least one set of two-way delays. The first indication information is used to indicate the proportion of the uplink delay in the two-way delay and/or the proportion of the downlink delay in the two-way delay in at least one set of two-way delays. The second indication information is used to indicate the threshold value of the proportion of the uplink delay in the two-way delay and/or the threshold value of the proportion of the downlink delay in the two-way delay in at least one set of two-way delays. The third indication information can be used to indicate whether the uplink delay is the same as or different from the downlink delay in the two-way delay. The priority indication information is used to indicate the priority of the uplink delay and/or downlink delay in at least one set of two-way delays.

In some embodiments, receiving the demand information in step S51 includes one of the following:

Receive demand information sent by AF;

The present disclosure provides an information processing method, which is executed by a PCF, including:

Receive demand information sent by AF;

In the AF session request process, receiving demand information;

In the AF session update process, receiving demand information;

In the AF session request process, receiving demand information;

In the AF session update process, receiving demand information;

In one embodiment, in the AF session request process, receiving requirement information includes: in the AF session request process, receiving a first request, wherein the first request includes the requirement information.

The embodiment of the present disclosure provides an information processing method, which is executed by a PCF, and includes: in an AF session request process, receiving a first request, wherein the first request includes demand information.

In some embodiments of the present disclosure, the first request may be the first request in the above embodiments.

Exemplarily, the first request may be an AF request; the AF request may be an AF session resource request.

Exemplarily, the first request may include at least one of the following: a common identification, wherein the common identification is used to indicate all data flows in the group of the XRM service; UE address information; a UE identifier, used to indicate a UE related to the XRM service; an application identifier, wherein the application identification information is used to indicate the XRM service; a flow description; a DNN; S-NSSAI; and QoS parameters.

In one embodiment, in a service-specific parameter providing process, receiving requirement information includes: in the service-specific parameter providing process, receiving a second request, wherein the second request includes the requirement information.

An embodiment of the present disclosure provides an information processing method, which is executed by a PCF, and includes: in a service-specific parameter provision process, receiving a second request, wherein the second request includes demand information.

In some embodiments of the present disclosure, the second request may be the second request in the above embodiment. Exemplarily, the second request may include at least one of the following: an XRM service identifier; a service description, wherein the service description includes a common identifier; a service parameter; a UE identifier for indicating a UE associated with the XRM service; a UE group identifier for indicating a group of UEs or multiple UEs associated with the XRM service; and a subscription event.

For the above implementation modes, please refer to the description on the AF side for details, which will not be described in detail here.

As shown in FIG6 , the embodiment of the present disclosure provides an information processing method, which is executed by a PCF and includes:

Step S61: Determine a predetermined rule of a data flow based on the demand information; and/or determine predetermined information based on the demand information.

In some embodiments of the present disclosure, the predetermined rule and the predetermined information may be the predetermined rule and the predetermined information in the above embodiments, respectively.

Exemplarily, the predetermined rule includes: PCC rule and/or QoS policy.

Exemplarily, the predetermined information includes but is limited to at least one of the following: at least one uplink delay value and/or at least one downlink delay value; and a QoS identifier, wherein the QoS identifier is used to indicate at least one QoS parameter.

In some embodiments, determining a predetermined rule based on the demand information in step S61 includes: determining a PCC rule for uplink delay and/or a PCC rule for downlink delay based on the demand information.

In some embodiments, determining the predetermined information based on the demand information in step S61 includes at least one of the following:

Determine, based on the demand information and the local configuration information, at least one uplink delay value and/or at least one downlink delay value;

In one embodiment, the local configuration information includes but is not limited to at least one of the following: operator policy, default configuration information and/or subscription information.

Here, the operator policy information may be, but is not limited to, any two-way delay policy formulated by the operator, such as a mobile determination that the uplink delay and/or downlink delay in a set of two-way delays does not exceed a certain threshold, etc. No specific restrictions are imposed on the operator policy information herein.

Here, the default configuration information is used to indicate the default configuration; the default configuration information can also be used to indicate the priority of the enhanced two-way delay requirement due to the default configuration. In this way, when the PCF receives the requirement information, it determines the values of the uplink delay and the downlink delay in the two-way delay based on the requirement information without considering the default configuration.

Here, the contract information may be, but is not limited to, any information indicating whether at least one characteristic of the XRM service or the multimodal data service is authorized, and no specific limitation is imposed on the contract information.

Determine at least one uplink delay value and/or at least one downlink delay value based on the demand information and the local configuration information;

In some embodiments, determining, based on the demand information, a value of at least one uplink delay and/or a value of at least one delay includes at least one of the following:

Determine at least one uplink delay value and/or at least one downlink delay value based on at least one uplink delay demand value and/or at least one downlink delay demand value in the demand information;

Determine, based on the first indication information in the demand information, a value of at least one uplink delay and/or a value of at least one downlink delay;

Determine, based on the second indication information in the demand information, a value of at least one uplink delay and/or a value of at least one downlink delay;

Determine at least one uplink delay value and/or at least one downlink delay value based on the third indication information and the first indication information in the requirement information or based on the third indication information and the first indication information in the requirement information;

Determine, based on fourth indication information in the demand information, a value of at least one uplink delay and/or a value of at least one downlink delay;

Based on the priority indication information in the demand information, a value of at least one uplink delay and/or a value of at least one downlink delay is determined.

Here, determining the value of at least one uplink delay and/or the value of at least one downlink delay may include: determining the value of the uplink delay and/or the value of the downlink delay in at least one set of two-way delays.

Exemplarily, the PCF receives demand information sent by the AF, and the demand information indicates that the demand value of the uplink delay in a set of two-way delays is 50ms and the demand value of the downlink delay is 60ms; the PCF can determine, based on the demand information, that the uplink delay value is 50ms and the downlink delay value is 60ms in a set of two-way delays of the data flow.

Exemplarily, the PCF receives demand information sent by the AF, the demand information includes first indication information, the first indication information indicates that a ratio of an uplink delay to a two-way delay is 40% and a ratio of a downlink delay to a two-way delay is 60%; the PCF learns that the two-way delay is 100ms, then determines that the uplink delay value in a set of two-way delays is 40ms and the downlink delay value is 60ms.

Exemplarily, the PCF receives demand information sent by the AF, where the demand information includes second indication information, where the second indication information indicates that a threshold value of a ratio of an uplink delay to a two-way delay is not less than 40% and a threshold value of a ratio of a downlink delay to a two-way delay is not more than 60%; the PCF learns that the two-way delay is 100ms, and determines that the uplink delay value in a set of two-way delays is 45ms and the downlink delay value is 55ms.

Exemplarily, the PCF receives the demand information sent by the AF, the demand information includes the third indication information and a demand value of the uplink delay in a set of two-way delays, which is 50ms, and the third indication information indicates that the uplink delay and downlink delay in a set of two-way delays are the same; the PCF determines that the values of the uplink delay and downlink delay in a set of two-way delays are both 50ms.

Exemplarily, the PCF receives demand information sent by the AF, and the demand information includes fourth indication information, and the fourth indication information indicates that the data flow of the XRM service needs to consider the two-way delay; the PCF learns that the two-way delay is 100ms; the PCF determines that the two-way delay is divided into uplink delay and downlink delay based on the fourth indication information, and the sum of the uplink delay and the uplink delay does not exceed the two-way delay; for example, the PCF determines that the value of the uplink delay is 40ms and the value of the downlink delay is 60ms; for another example, the PCF determines that the value of the uplink delay is 40ms and the value of the downlink delay is 55ms; for another example, the PCF determines that the value of the uplink delay and the value of the downlink delay are both 50ms.

Exemplarily, the PCF receives demand information sent by the AF, the demand information includes three sets of demand values for two-way delays, namely: the demand value for uplink delay in the first set of two-way delays is 40ms and the demand value for downlink delay is 60ms, the demand value for uplink delay and the demand value for downlink delay in the second set of two-way delays are both 50ms, and the demand value for uplink delay in the third set of two-way delays is 55ms and the demand value for downlink delay is 45ms; the demand information also includes priority indication information corresponding to the three sets of demand values for two-way delays, the three priority indications are low priority indication information corresponding to the first set of two-way delays, medium priority indication information corresponding to the second set of two-way delays, and high priority indication information corresponding to the third set of two-way delays. Based on the demand information, the PCF determines that the value of one set of two-way delays is the demand value of the third set of two-way delays, that is, the value of uplink delay is 55ms and the value of downlink delay is 45ms.

In the disclosed embodiment, the PCF can accurately determine the value of the uplink delay and/or downlink delay in at least one set of two-way delays based on demand information; and can be determined based on multiple methods to adapt to more application scenarios.

Of course, in other embodiments, the PCF may determine the value of the two-way delay based on demand information and local configuration information, such as operator policy information, default configuration information and/or subscription information.

In some embodiments, determining a QoS indicator of a data flow based on the demand information includes:

Determine the PCC rules of quantity flow based on demand information;

Based on the PCC rule, the QoS indicator of the data flow is determined.

Exemplarily, based on the received demand information, the PCF determines an uplink delay and a downlink delay of the data flow of the XRM service; the PCF generates a PCC rule for the uplink delay and another PCC rule for the downlink delay; the PCF generates corresponding QoS identifiers (e.g., 5QI) for the two PCC rules.

An embodiment of the present disclosure provides an information processing method, which is executed by PCF, including: sending an update request to SMF, wherein the update request includes: PCC rules and/or QoS policies; wherein the update request is used by SMF to update the PCC rules and/or QoS policies stored in SMF.

Exemplarily, the PCF determines the PCC rules and/or QoS policies of the data flow in the XRM service based on the demand information; the PCF sends an update request to the SMF, and the update request includes the PCC rules and/or QoS policies; after receiving the update request, the SMF updates the PCC rules stored in the SMF based on the PCC rules in the update request and/or updates the QoS policies stored in the SMF based on the QoS policies in the update request.

In an embodiment of the present disclosure, the PCF sends an update request to the SMF so that the SMF can update the PCC rules and/or QoS policies stored in the SMF.

The present disclosure provides an information processing method, which is executed by a PCF and includes one of the following:

Based on the demand information, determine the QoS control at the SDF level or the QoS flow level; wherein the QoS control includes: QoS authorization and/or OoS update;

Based on the demand information and local configuration information, QoS control at the SDF level or QoS level is determined.

In one embodiment, the local configuration information includes: operator policy, default configuration information and/or subscription information.

In one embodiment, the SDF-level QoS control may be QoS authorization and/or QoS update for a specific SDF.

In one embodiment, the QoS control at the QoS flow level may be QoS authorization and/or QoS update for all SDFs within the QoS flow.

Exemplarily, there are M data streams, and N of the M data streams are specific data streams, such as video data streams; the SDF-level QoS control can be to classify the N data streams into one category for QoS control; wherein M and N are integers; and N is less than M.

In the above embodiment, N of the M data streams are video data streams and L are audio data streams. The N video data streams can be treated as one type of data streams and subjected to QoS flow-level QoS control, and the L audio data streams can be treated as another type of data streams and subjected to QoS flow-level QoS control.

In some embodiments, determining QoS control at the SDF level or the QoS flow level based on the demand information includes at least one of the following:

Determine QoS control at the SDF level or the QoS flow level based on at least one required value of an uplink delay and/or a required value of a downlink delay in the requirement information;

Determine QoS control at the SDF level or the QoS flow level based on the first indication information in the demand information;

Determine QoS control at the SDF level or the QoS flow level based on the second indication information in the demand information;

Determine QoS control at the SDF level or the QoS flow level based on the third indication information in the demand information;

Based on the fourth indication information in the requirement information, QoS control at the SDF level or the QoS flow level is determined.

Of course, in other embodiments, the PCF may also determine the QoS control at the SDF level or the QoS flow level based on at least one uplink delay demand value and/or at least one downlink delay demand value in the demand information, the first indication information, the second indication information, the third indication information, the fourth indication information, and at least one of the priority indication information and the local configuration information.

In the embodiments of the present disclosure, QoS control at the SDF level or QoS flow level can be performed on the data flow based on the demand information, that is, multiple data flows can be classified into one category for control.

The following is based on an information processing method, which is performed by the first network function and is similar to the description of the information processing method performed by the AF and/or PCF mentioned above; and, for technical details not disclosed in the information processing method embodiment performed by the first network function, please refer to the description of the example of the information processing method performed by the AF and/or PCF, which will not be described in detail here.

As shown in FIG. 7 , an embodiment of the present disclosure provides an information processing method, which is performed by a first network function and includes:

Step S71: Receive requirement information, where the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service.

In one embodiment, the first network function may be a logical node or function that can be flexibly deployed in the core network. Exemplarily, the first network function may be, but is not limited to, NEF or TSCTSF.

In some embodiments of the present disclosure, the demand information may be the demand information in the above embodiments; and the two-way delay may be the two-way delay in the above embodiments.

Exemplarily, the two-way delay may be, but is not limited to, an uplink delay and a downlink delay, or a round-trip two-way delay. The two-way delay may be, for example, a round-trip delay, or a two-way delay budget, or an uplink and downlink packet delay budget (PDB).

Second indication information, wherein the second indication information is used to indicate at least one threshold value of a ratio of uplink delay to two-way delay and/or at least one threshold value of a ratio of downlink delay to two-way delay;

In some embodiments, the first network function is NEF; the receiving of demand information in step S71 includes: receiving demand information sent by AF.

The embodiment of the present disclosure provides an information processing method, which is executed by a NEF and includes: receiving demand information sent by an AF.

The present disclosure provides an information processing method, which is executed by NEF and includes one of the following:

Send demand information to PCF;

Exemplarily, the NEF receives the demand information sent by the AF, and sends the demand information to the PCF. Alternatively, the NEF receives the demand information sent by the AF, and sends the demand information to the TSCTSF; the TSCTSF sends the demand information to the PCF.

Receive demand information sent by AF;

Receive demand information sent by NEF.

The embodiment of the present disclosure provides an information processing method, which is executed by TSCTSF, and includes: receiving demand information sent by AF or NEF.

The embodiment of the present disclosure provides an information processing method, which is executed by TSCTSF, and includes: sending demand information to PCF.

Exemplarily, the TSCTSF receives the demand information sent by the AF, and sends the demand information to the PCF. Alternatively, the AF sends the demand information to the NEF; the TSCTSF receives the demand information sent by the NEF, and sends the demand information to the PCF.

The present disclosure provides an information processing method, which is executed by a NEF and includes:

Send subscription notification to AF.

For the above implementation modes, details may be referred to the description of the AF side and/or the PCF side, which will not be described in detail here.

In order to further explain any embodiment of the present disclosure, several specific embodiments are provided below.

Example 1

As shown in FIG8 , an embodiment of the present disclosure provides an information processing method, which is performed by a communication device, and the communication device includes: a UE, a RAN device, an AMF, an SMF, a UPF, a PCF, a NEF, and an AF; the information processing method includes the following steps:

Step S801: AF sends an AF request, which carries demand information;

Exemplarily, the AF request may be an AF session resource request; the AF creates the AF request through Nnef_AFsessionWithQoS_Create request; the AF carries demand information in the AF request, and the demand information is used to indicate the demand for the two-way delay of the data flow of the XRM service. The AF request may be the first request in the above embodiment. Here, the two-way delay may be, but is not limited to: uplink delay and downlink delay, or round-trip two-way delay. The demand information may include, but is not limited to, at least one of the following:

An indication of whether the uplink and downlink delays (or PDBs) are the same;

Required values of uplink and/or downlink delay (or PDB);

The proportion of uplink and/or downlink delay (or PDB) to the RTT two-way delay (e.g. 40% for uplink, 50% for uplink, 70% for downlink);

A threshold value of the ratio of the uplink and/or downlink delay (or PDB) to the RTT two-way delay (for example, the threshold value may be not less than 40%, not more than 40%, equal to 30% or 50%, or between 30-50%);

An uplink and/or downlink delay (or PDB) configuration file (eg, multiple sets of uplink and/or downlink delay requirement values, and optionally, also including the priority of the uplink and/or downlink delay).

Here, the indication of whether the uplink and downlink delays (or PDBs) are the same may be the third indication information in the above-mentioned embodiment; the ratio of the uplink and/or downlink delays (or PDBs) to the RTT two-way delay may be the first indication information in the above-mentioned embodiment; the threshold of the ratio of the uplink and/or downlink delays (or PDBs) to the RTT two-way delay may be the second indication information in the above-mentioned embodiment; the priority of the uplink and/or linear delay included in the uplink and/or downlink delay (or PDB) profile may be the priority indication information in the above-mentioned embodiment.

Exemplarily, the AF request may also include: XRM service information; the XRM service information may be but is not limited to at least one of the following: common identification, UE address information, UE identifier, application identifier, flow identification, DNN, S-NSSAI and QoS parameters.

Step S802: NEF authorizes AF request;

Exemplarily, if the AF is an untrusted AF, the AF request sent by the AF can be provided to the PCF through the NEF. Optionally, the NEF performs relevant mappings, including: mapping of XRM service identifiers (e.g., AF-Service-Identifier) to DNN and S-NSSAI, mapping of external applications to core network (CN) application identifiers; and unified data management (UDM) contract information, mapping of external UE identifiers to UE identifiers within the CN (e.g., SUPI), and mapping of external to internal XRM service group identifiers based on the UDM contract information.

Step S803: NEF sends the AF request to PCF;

Step S804: The PCF determines a reservation rule and/or reservation information based on the demand information;

Exemplarily, the predetermined information and/or predetermined rule may be a policy decision.

Exemplarily, based on demand information, PCF divides the value of two-way delay (e.g., RT latency) into UL PDB (i.e., uplink delay) and DL PDB (i.e., downlink delay); UL PDB and DL PDB may be the same or different, and the sum of UL PDB and DL PDB is less than or equal to the value of two-way delay.

Exemplarily, the PCF may monitor the UL latency of the UL QoS flow and the DL latency of the DL QoS flow respectively to track the two-way latency (this may be accomplished by utilizing the QoS monitoring method in the existing communication protocol).

Exemplarily, PCF divides the two-way delay into UL PDB and DL PDB, and generates two PCC rules for the data flow; one PCC rule is used for the UL data flow, and the other PCC rule is used for the DL data flow; and the corresponding 5QI is allocated to the UL PDB and DL PDB respectively. Here, the two PCC rules should also have associated QoS monitoring policies to achieve the tracking of the two-way delay; so that the UL PDB or DL PDB can be tracked independently. Based on the monitoring results of the QoS monitoring policy, PCF can adjust the UL PDB and DL PDB to better adapt to the new situation.

Exemplarily, the PCF generates or updates PCC rules for the data flow of the corresponding XRM service based on the demand information; and/or, the PCF divides the two-way delay into UL PDB and DL PDB based on the demand information; and/or, the PCF allocates 5QI to the corresponding UL PDB and/or DL PDB based on the demand information; the PCF determines the UL PDB and DL PDB based on the demand information and local configuration information; and/or, the PCF stores and updates the configuration file of the XRM service, which includes: UL PDB and/or DL PDB, PCC rules, and/or 5QI allocated to UL PDB and/or DL PDB, etc.

Exemplarily, the PCF triggers Npcf_SMPolicyControl_UpdateNotify to update the policy information of the corresponding PDU session of the SMF, where the policy information includes the PCC rule and QoS policy determined by the PCF. The Npcf_SMPolicyControl_UpdateNotify may be the update request in the above embodiment.

Exemplarily, the requirement information provided by the AF request may affect QoS control at the SDF level (e.g., affecting QoS authorization or QoS update for a specific SDF), or QoS control at the QoS flow level (e.g., affecting QoS authorization or QoS update for all SDFs within a QoS flow).

Exemplarily, the PCF performs QoS authorization and QoS update at the corresponding SDF level based on the demand information provided by the AF request (for example, an indication of whether the uplink and downlink delays (or PDBs) are the same and/or the required values of the uplink and downlink delays (or PDBs)). Alternatively, the PCF performs QoS authorization and QoS update at the corresponding SDF level based on the demand information (for example, the proportion of the uplink or downlink delay to the RTT two-way delay) and local configuration information (for example, operator policy and/or default configuration information). Alternatively, the PCF performs QoS authorization and QoS update at the corresponding SDF level based on the demand information (for example, the threshold value of the proportion of the uplink or downlink delay to the RTT two-way delay). Alternatively, the PCF performs QoS authorization and QoS update at the corresponding SDF level based on the configuration file of the uplink or downlink delay (for example, multiple sets of required values of the uplink and/or downlink delays, optionally including the priority of the uplink and/or downlink delays). Alternatively, the PCF may perform QoS authorization and QoS update at the corresponding SDF level based on the result of the authorization or failure of the QoS request.

Exemplarily, the AF provides the demand information to the PCF, which may be sent directly to the AF or indirectly to the AF. The indirect sending includes one of the following: sending to the PCF via the NEF; or sending to the PCF via the TSCTSF; or sending to the PCF via the NEF and the TSCTSF (here the AF sends the demand information to the NEF, the NEF sends the demand information to the TSCTSF, and the TSCTSF sends the demand information to the PCF).

Step S805: PCF sends an authorization response to NEF;

Exemplarily, the authorization response may be Npcf_Policy Authorization_Create response; the authorization response may be used to indicate whether the policy generated by the PCF is authorized.

Step S806: NEF sends an authorization response to AF;

Exemplarily, the authorization response may be a Nnef_AFsessionWithQoS_Create response; the authorization response may be used to indicate whether the AF request is authorized.

Step S807: PCF sends an update request to SMF;

Exemplarily, the update request may be an SM Policy Association Modification Request; the update request includes PCC rules. Here, based on the measured QoS monitoring policy from the PCF, the SMF generates a QoS monitoring configuration (QoS Monitoring configuration) for the UPF (optionally, or RAN equipment).

Step S808: SMF sends an update response to PCF;

Exemplarily, the update response can be an SM Policy Association Modification Response.

Step S809: SMF sends an N4 session modification request to UPF;

Exemplarily, the N4 session modification request may be an N4Session Modification Request; the N4 session modification request includes (QoS monitoring configuration).

Step S810: SMF receives the response returned by UPF based on the N4 session modification request;

Exemplarily, after receiving the QoS monitoring configuration, UPF enables measurement and reporting; UPF responds to SMF.

Step S811: AMF and SMF exchange N1N2 messages;

Exemplarily, AMF receives a session modification request sent by SMF, and calls a Namf_Communication_N1N2 message based on the session modification request; the Namf_Communication_N1N2 message includes a PDU session ID, QFI(s), a QoS configuration file, a QoS monitoring configuration and/or an N1SM container.

Step S812: AMF sends an N2 message, a NAS message, and an N1SM container to the RAN device;

Exemplarily, the N2 message is received by the AMF from the SMF; the NAS message includes the ID of the PDU session, and the N1SM container includes the PDU session modification (PDU Session Modification Command). After receiving the QoS monitoring configuration, the RAN device enables measurement and reporting (for example, the RAN device measures the UL delay and the DL delay, and takes the sum of the UL delay and the DL delay as the two-way delay).

Step S813: Perform resource configuration between the RAN device and the UE; this step S813 is optional.

Step S814: The RAN device sends a session confirmation message to the AMF;

Exemplarily, a session confirmation message is used to confirm a session modification request; the session confirmation message may be an N2PDU Session Ack Message.

Step S815: AMF sends a session update request to SMF;

Exemplarily, AMF forwards the session confirmation message (including N2SM message) received from the RAN device to SMF through the Nsmf_PDUSession_UpdateSMContext service operation.

Step S816: SMF sends a session update response to AMF;

Exemplarily, SMF responds to the session update request using Nsmf_PDUSession_UpdateSMContext Response (i.e., session update response).

Step S817: SMF sends an N4 session modification request to UPF;

Exemplarily, the N4 session modification request can be N4Session Modification Request.

Step S818: UPF sends an N4 session modification response to SMF.

Exemplarily, the N4 session modification response can be N4Session Modification Response.

Here, when the PCF subsequently receives the measurement and/or report based on the QoS monitoring configuration, it will send the measurement and/or report to the AF and trigger the modification of related resources and/or trigger the AF session update process or the AF session release process.

For the above implementation modes, specific reference may be made to the descriptions on the AF side and/or the PCF side and/or the first network function side, which will not be repeated here.

Example 2

As shown in FIG9 , an embodiment of the present disclosure provides an information processing method, which is performed by a communication device, and the communication device includes: UE, UEx, RAN device, AMF, PCF, PCFx, UDM, UDR, NEF and AF; the information processing method includes the following steps:

Step S900: UE registration policy association;

Exemplarily, some or all UEs related to the XRM service or multimodal data service have registered with the network, and select PCF to complete the AM session association. Here, PCF subscribes to the UDM for change notifications of contract information related to the XRM service or multimodal data service according to the policy and QoS requirements of the XRM service.

Step S901: AF creates an AF request, which includes demand information;

Exemplarily, the AF request may be the second request in the above embodiment; the AF triggers the Nnef_XRMServiceParameter service to create the AF request; the AF carries the requirement information in the AF request, and the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service. Here, the two-way delay may be, but is not limited to: uplink delay and downlink delay, or round-trip two-way delay. The requirement information may include, but is not limited to, at least one of the following:

Indication of whether the uplink and downlink delays (or PDB) are the same;

Required values of uplink and/or downlink delay (or PDB);

Exemplarily, the AF may also include at least one of the following: an XRM service identifier; a service description, wherein the service description includes a common identifier; a service parameter; a UE identifier; a UE group identifier; and a subscription event.

Here, when the AF needs to update and delete a corresponding request (eg, an AF request) or a subscription, the update and/or deletion process of the AF request may also be initiated through the service.

Step S902: AF sends AF request to NEF;

Exemplarily, the NEF may also authorize the AF request. Here, the NEF performs the related mapping similarly to the NEF performing the related mapping in the above step S802.

Step S903: NEF stores the AF request in the UDR;

Exemplarily, the NEF stores information related to the service characteristics of the application data flow in the AF request; optionally, the NEF may improve the corresponding service characteristic related information (such as service parameters and/or service description, etc.) according to the local configuration. Optionally, the NEF may determine whether the requested service characteristics are authorizable and store the corresponding information in the UDR for the XRM service or multimodal data service of a single UE or multiple UEs based on the operator's policy and/or contract information.

If multiple UEs are involved, the NEF transmits information related to service characteristics to the PCF, and performs corresponding authorization, as well as decision or update of policies and rules in each PCF. The PCF stores the corresponding information in the UDR according to the authorization result requested by the AF.

If multiple UEs are involved, in the scenario of multiple UEs (i.e., group UE), the subscription information of the UE group members is associated through the XRM service identifier or UE group identifier or common identifier; the group data of the group UE remains consistent (for example, the QoS, access and data routing characteristic parameters of the service remain consistent).

Exemplarily, AF or PCF can subscribe to relevant XRM services or multimodal data service-related event triggers through NEF, such as QoS monitoring reports (reports obtained based on QoS monitoring configuration), service QoS updates, UE relocation and/or PCF changes, etc.

Exemplarily, the AF or PCF may obtain corresponding notifications by receiving reports from the NEF, and may execute subsequent updates of application requirements or QoS policies.

Step S904: NFE sends a response message of AF request to AF;

Exemplarily, in step S900, the PCF executes a subscription information update notification after the UE is registered; and because the AF requests to update the UDR subscription information, the subsequent process is executed.

Step S905: PCF receives the contract information update notification from UDR;

Step S906: The PCF sends the UE policy to the UE;

Exemplarily, the measurement strategy of the UE includes the predetermined information and/or predetermined rules in the above embodiments, for example, may be a PCC rule.

Step S907: PCF sends the execution result to NEF;

Exemplarily, if the AF subscribes to the execution notification of the XRM service-related policy, the PCF sends the policy-related execution result to the NEF so that the NEF sends it to the AF. At the same time, if there is a change in the relevant subscription parameters, the PCF updates the change to the UDR, triggering the PCF execution policy change and collaborative operation of other UEs related to the XRM service group. The execution result can be measured and/or reported in the above embodiment.

Step S908: NEF sends the execution result to AF.

Example 3

As shown in FIG. 10 , an embodiment of the present disclosure provides an information processing method, which is performed by a communication device, and the communication device includes: a UPF, a PCF, a NEF, and an AF; the information processing method includes the following steps:

Step S101: UPF detects an event trigger;

Exemplarily, when UPF detects a measurement and/or reaches an event, it triggers a report (for example, when a threshold is reached or a periodic timer times out, a report is triggered); UPF triggers a Nupf_EventExposure_Notify message.

Step S102: UPF sends a subscription notification to NEF;

Exemplarily, the subscription notification includes relevant information of the measured two-way delay; the subscription notification may be a Nupf_EventExposure_Notify message.

Step S103: NEF sends a subscription notification to AF.

Example 4

The embodiment of the present disclosure provides an information processing system, including: an AF, a first network function and a PCF;

The first network function is configured to send demand information to the PCF.

In some embodiments, the first network function includes NEF and/or TSCTSF;

NEF is configured to: receive the demand information sent by AF and send the demand information to PCF or TSCTSF;

or,

TSCTSCF is configured to receive demand information sent by AF or NEF and send the demand information to PCF.

In some embodiments, the PCF is configured to determine predetermined rules for the data flow based on the demand information and/or determine predetermined information.

As shown in FIG11 , an embodiment of the present disclosure provides an information processing device, including:

The first sending module 51 is configured to send requirement information, wherein the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service.

The information processing device provided by the embodiment of the present disclosure may be an AF.

The present disclosure provides an information processing device, including: a first sending module 51, configured to perform one of the following:

Send demand information to PCF;

In the AF session request process, the demand information is sent;

In the AF session update process, the demand information is sent;

PCC Rules;

QoS policy;

and / or,

Booking information, including at least one of the following:

At least one uplink delay value;

at least one downlink delay value;

The embodiment of the present disclosure provides an information processing device, including: a first sending module 51, configured to send a first request in an AF session request process, wherein the first request includes demand information.

UE address information;

UE identifier, used to indicate the UE related to the XRM service;

Stream description;

DNN;

S-NSSAI;

QoS parameters.

The embodiment of the present disclosure provides an information processing device, including: a first sending module 51, configured to send a second request in a service-specific parameter providing process, wherein the second request includes demand information.

XRM business logo;

Business parameters;

UE identifier, used to indicate the UE related to the XRM service;

Subscribe to events.

An embodiment of the present disclosure provides an information processing device, including: a first receiving module, configured to receive a subscription notification, wherein the subscription notification includes a report determined based on demand information.

The present disclosure provides an information processing device, including: a first receiving module, configured to perform one of the following:

Receive subscription notifications sent by UPF;

As shown in FIG12 , an information processing device is provided, including:

The second receiving module 61 is configured to receive requirement information, wherein the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service.

The information processing device provided by the embodiment of the present disclosure may be a PCF.

The embodiment of the present disclosure provides an information processing device, including: a second receiving module 61, configured to perform one of the following:

Receive demand information sent by AF;

In the AF session request process, receiving demand information;

In the AF session update process, receiving demand information;

The present disclosure provides an information processing device, including: a first processing module; the first processing module is configured to perform at least one of the following:

Based on the demand information, reservation information is determined.

An embodiment of the present disclosure provides an information processing device, including: a second sending module, configured to send an update request to SMF, wherein the update request includes: PCC rules and/or QoS policies; wherein the update request is used by SMF to update the PCC rules and/or QoS policies stored in SMF.

The present disclosure provides an information processing device, including: a first processing module, configured to perform at least one of the following:

The present disclosure provides an information processing device, including: a first processing module, configured to perform one of the following:

An embodiment of the present disclosure provides an information processing device, including: a second receiving module 61, configured to receive a first request in an AF session request process, wherein the first request includes demand information.

UE address information;

UE identifier, used to indicate the UE related to the XRM service;

Stream description;

DNN;

S-NSSAI;

QoS parameters.

An embodiment of the present disclosure provides an information processing device, including: a second receiving module 61, configured to receive a second request in a service-specific parameter providing process, wherein the second request includes demand information.

XRM business logo;

Business parameters;

UE identifier, used to indicate the UE related to the XRM service;

Subscribe to events.

As shown in FIG13 , an embodiment of the present disclosure provides an information processing device, including:

The third receiving module 71 is configured to receive requirement information, wherein the requirement information is used to indicate the requirement for the two-way delay of the data flow of the XRM service.

The information processing device provided in the embodiment of the present disclosure may be a first network function. The first network function may be, but is not limited to, NEF or TSCTSF.

In some embodiments, the first network function is NEF. The third receiving module 71 is configured to receive the demand information sent by AF.

An embodiment of the present disclosure provides an information processing device, including: a third receiving module 71, configured to receive demand information sent by an AF.

The present disclosure provides an information processing device, including: a third sending module; the third sending module is configured to perform one of the following:

Send demand information to PCF;

The present disclosure provides an information processing device, including:

The third receiving module 71 is configured to receive a subscription notification sent by the UPF or the PCF, wherein the subscription notification includes a report determined based on the demand information;

In some embodiments, the first network function is TSCTSF; the third receiving module 71 is configured to perform one of the following:

Receive demand information sent by AF;

Receive demand information sent by NEF.

The embodiment of the present disclosure provides an information processing device, including: a third receiving module 71, configured to perform one of the following:

Receive demand information sent by AF;

Receive demand information sent by NEF.

An embodiment of the present disclosure provides an information processing device, including: a third sending module, configured to send demand information to a PCF.

It should be noted that those skilled in the art can understand that the device provided in the embodiments of the present disclosure can be executed alone or together with some devices in the embodiments of the present disclosure or some devices in related technologies.

Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

The present disclosure provides a communication device, including:

processor;

a memory for storing processor-executable instructions;

In one embodiment, the communication device may include but is not limited to at least one of: AF, PCF, SMF, and TSCTSF.

The processor may include various types of storage media, which are non-temporary computer storage media that can continue to memorize information stored thereon after the user device loses power.

The processor may be connected to the memory via a bus or the like, and may be used to read an executable program stored in the memory, for example, at least one of the methods shown in FIG. 2 to FIG. 10 .

The present disclosure also provides a computer storage medium storing a computer executable program, which implements the information processing method of any embodiment of the present disclosure when the executable program is executed by a processor, for example, at least one of the methods shown in FIG. 2 to FIG. 10 .

Regarding the device or storage medium in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.

Fig. 14 is a block diagram of a user device 800 according to an exemplary embodiment. For example, the user device 800 may be a mobile phone, a computer, a digital broadcast user device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

14 , the user device 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 communication component 816 .

The processing component 802 generally controls the overall operation of the user device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

The memory 804 is configured to store various types of data to support operations on the user device 800. Examples of such data include instructions for any application or method operating on the user device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can 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 (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

The power supply component 806 provides power to the various components of the user device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the user device 800.

The multimedia component 808 includes a screen that provides an output interface between the user device 800 and the user. In some embodiments, 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 one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. When the user device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the user device 800 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

I/O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the user device 800. For example, the sensor assembly 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the user device 800, and the sensor assembly 814 can also detect the position change of the user device 800 or a component of the user device 800, the presence or absence of contact between the user and the user device 800, the orientation or acceleration/deceleration of the user device 800, and the temperature change of the user device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 816 is configured to facilitate wired or wireless communication between the user device 800 and other devices. The user device 800 can access a wireless network based on a communication standard, such as WiFi, 4G or 5G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, 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.

In an exemplary embodiment, the user device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.

In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the user device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

As shown in FIG. 15 , an embodiment of the present disclosure illustrates a structure of a base station. For example, the base station 900 may be provided as a network-side device. Referring to FIG. 15 , the base station 900 includes a processing component 922, which further includes one or more processors, and a memory resource represented by a memory 932 for storing instructions executable by the processing component 922, such as an application. The application stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 922 is configured to execute instructions to execute any method of the aforementioned method applied to the base station.

The base station 900 may also include a power supply component 926 configured to perform power management of the base station 900, a wired or wireless network interface 950 configured to connect the base station 900 to the network, and an input/output (I/O) interface 958. The base station 900 may operate based on an operating system stored in the memory 932, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, FreeBSD TM or the like.

Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

An information processing method, wherein the method is performed by an application function AF, comprising:

Sending requirement information, wherein the requirement information is used to indicate the requirement for two-way delay of a data stream of a multimedia extended reality XRM service.
The method according to claim 1, wherein the demand information includes at least one of the following:

At least one required uplink delay value;

At least one required downlink delay value;

First indication information, wherein the first indication information is used to indicate a ratio of at least one uplink delay to the two-way delay and/or a ratio of at least one downlink delay to the two-way delay;

Second indication information, wherein the second indication information is used to indicate a ratio threshold of at least one uplink delay to the two-way delay and/or a ratio threshold of at least one downlink delay to the two-way delay;

third indication information, wherein the third indication information is used to indicate whether the uplink delay and the downlink delay in at least one set of the two-way delay are the same;

Fourth indication information, wherein the fourth indication information is used to indicate that the data flow of the XRM service needs to consider the two-way delay;

Priority indication information, wherein the priority indication information is used to indicate the priority of the uplink delay and/or indicate the priority of the downlink delay;

A configuration file, wherein the configuration file is used to indicate at least one set of required values of uplink delay and/or required values of downlink delay in the two-way delay, or the configuration file is used to indicate: at least one set of required values of uplink delay in the two-way delay and priority indication information of the uplink delay, and/or required values of downlink delay and priority indication information of the downlink delay.
The method according to claim 1 or 2, wherein the sending requirement information comprises one of the following:

Sending the requirement information to the policy control function PCF;

Sending the requirement information to a network open function NEF, wherein the requirement information is used by the NEF to send to a time sensitive communication and time synchronization function TSCTSF or the PCF;

The requirement information is sent to the TSCTSF, wherein the requirement information is used by the TSCTSF to send to the PCF.
The method according to claim 1 or 2, wherein the sending requirement information comprises one of the following:

In the AF session request process, sending the requirement information;

In the AF session update process, sending the requirement information;

In the service specific parameter provision process, sending the requirement information;

In the process of setting a policy for a subsequent AF session, the requirement information is sent.
The method according to any one of claims 1 to 4, wherein the demand information is used by the PCF to determine a predetermined rule and/or determine predetermined information.
The method according to claim 5, wherein

The predetermined rules include at least one of the following:

Policy and charging control PCC rules;

Quality of Service (QoS) strategy;

and / or,

The predetermined information includes at least one of the following:

At least one uplink delay value;

at least one downlink delay value;

A QoS identifier, wherein the QoS identifier is used to indicate at least one QoS parameter.
The method according to claim 4, wherein, in the AF session request process, sending the demand information comprises:

In the AF session request process, a first request is sent, wherein the first request includes the requirement information.
The method according to claim 7, wherein the first request further includes at least one of the following:

A common identifier, wherein the common identifier is used to indicate all data flows in the group of the XRM service;

UE address information;

UE identifier, used to indicate the UE related to the XRM service;

An application identifier, wherein the application identification information is used to indicate the XRM service;

Stream description;

Data network name DNN;

Network Slice Selection Support Information S-NSSAI;

QoS parameters.
The method according to claim 4, wherein, in the service-specific parameter provision process, sending the requirement information comprises:

In the service-specific parameter providing process, a second request is sent, wherein the second request includes the requirement information.
The method according to claim 9, wherein the second request further comprises at least one of the following:

XRM business logo;

A business description, wherein the business description includes a common identifier;

Business parameters;

UE identifier, used to indicate the UE related to the XRM service;

UE group identifier, used to indicate a group of UEs or multiple UEs related to the XRM service;

Subscribe to events.
The method according to any one of claims 1 to 8, wherein the method comprises:

A subscription notification is received, wherein the subscription notification includes a report determined based on the requirement information.
The method according to claim 11, wherein the receiving a subscription notification comprises one of the following:

Receiving the subscription notification sent by the user plane function UPF;

receiving the subscription notification sent by the NEF; wherein the subscription notification is received by the NEF from the UPF, or the subscription notification is received by the NEF from the PCF;

Receive the subscription notification sent by the PCF; wherein, the subscription notification is received by the PCF from the session management function SMF, and the subscription notification is received by the SMF from the UPF.
An information processing method, wherein the method is performed by a policy control function PCF, comprising:

Receive demand information, where the demand information is used to indicate a two-way delay requirement for a data stream of a multimedia extended reality (XRM) service.
The method according to claim 13, wherein the demand information includes at least one of the following:

At least one required uplink delay value;

At least one required downlink delay value;

First indication information, wherein the first indication information is used to indicate a ratio of at least one uplink delay to the two-way delay and/or a ratio of at least one downlink delay to the two-way delay;

Second indication information, wherein the second indication information is used to indicate a ratio threshold of at least one uplink delay to the two-way delay and/or a ratio threshold of at least one downlink delay to the two-way delay;

third indication information, wherein the third indication information is used to indicate whether the uplink delay and the downlink delay in at least one set of the two-way delay are the same;

Fourth indication information, wherein the fourth indication information is used to indicate that the data flow of the XRM service needs to consider the two-way delay;

Priority indication information, wherein the priority indication information is used to indicate the priority of the uplink delay and/or to indicate the priority of the downlink delay;

A configuration file, wherein the configuration file is used to indicate at least one set of required values of uplink delay and/or required values of downlink delay in the two-way delay, or the configuration file is used to indicate: at least one set of required values of uplink delay in the two-way delay and priority indication information of the uplink delay, and/or required values of downlink delay and priority indication information of the downlink delay.
The method according to claim 13 or 14, wherein the receiving demand information comprises one of the following:

Receiving the requirement information sent by the application function AF;

receiving the requirement information sent by a network open function NEF, wherein the requirement information is received by the NEF from the AF;

The requirement information is received by a time-sensitive communication and time synchronization function TSCTSF, wherein the requirement information is received by the TSCTSF from the NEF or from the AF.
The method according to claim 13 or 14, wherein the receiving demand information comprises one of the following:

In the AF session request process, receiving the requirement information;

In the AF session update process, receiving the requirement information;

In the service specific parameter provision process, receiving the requirement information;

In the process of setting a policy for a subsequent AF session, the requirement information is received.
The method according to any one of claims 13 to 16, wherein the method comprises at least one of the following:

Based on the demand information, determining a predetermined rule for the data flow;

Based on the demand information, predetermined information is determined.
The method according to claim 17, wherein the predetermined rule comprises: a policy and charging control (PCC) rule and/or a QoS policy.
The method according to claim 18, wherein the method comprises:

Send an update request to the session management function SMF, wherein the update request includes:

The PCC rule and/or the QoS policy;

The update request is used by SMF to update the PCC rules and/or QoS policies stored in the SMF.
The method according to claim 17, wherein the determining the predetermined information based on the demand information comprises at least one of the following:

Based on the demand information, determine at least one uplink delay value and/or at least one downlink delay value;

Determine at least one uplink delay value and/or at least one downlink delay value based on the demand information and local configuration information; wherein the local configuration information includes: operator policy, default configuration information and/or subscription information;

Based on the demand information, a QoS identifier of the data flow is determined, wherein the QoS identifier is used to indicate at least one QoS parameter.
The method according to any one of claims 13 to 16, wherein the method comprises one of the following:

Based on the demand information, determine the QoS control of the service data flow SDF level or the QoS flow level; wherein the QoS control includes: QoS authorization and/or OoS update;

Based on the demand information and local configuration information, the QoS control of the SDF level or the QoS level is determined; wherein the local configuration information includes: operator policy, default configuration information and/or subscription information.
The method according to claim 16, wherein, in the AF session request process, receiving the requirement information comprises:

In the AF session request process, a first request is received, wherein the first request includes the requirement information.
The method according to claim 22, wherein the first request further comprises at least one of the following:

A common identifier, wherein the common identifier is used to indicate all data flows in the group of the XRM service;

UE address information;

UE identifier, used to indicate the UE related to the XRM service;

An application identifier, wherein the application identification information is used to indicate the XRM service;

Stream description;

Data network name DNN;

Network Slice Selection Support Information S-NSSAI;

QoS parameters.
The method according to claim 16, wherein, in the process of providing service-specific parameters, receiving the requirement information comprises:

In the service-specific parameter providing process, a second request is received, wherein the second request includes the requirement information.
The method of claim 24, wherein the second request further comprises at least one of the following:

XRM business logo;

A business description, wherein the business description includes a common identifier;

Business parameters;

UE identifier, used to indicate the UE related to the XRM service;

UE group identifier, used to indicate a group of UEs or multiple UEs related to the XRM service;

Subscribe to events.
An information processing method, wherein the method is performed by a first network function, comprising:

Receive demand information, where the demand information is used to indicate a two-way delay requirement for a data stream of a multimedia extended reality (XRM) service.
The method according to claim 26, wherein the first network function is a network open function NEF; and the receiving demand information comprises:

The requirement information sent by the application function AF is received.
The method according to claim 27, wherein the method comprises one of the following:

Sending the requirement information to the policy control function PCF;

The requirement information is sent to a time sensitive communication and time synchronization function TSCTSF, wherein the requirement information is used by the TSCTSF to send to the PCF.
The method according to claim 27 or 28, wherein the method comprises:

Receiving a subscription notification sent by a user plane function UPF or PCF, wherein the subscription notification includes a report determined based on the demand information;

The subscription notification is sent to AF.
The method according to claim 26, wherein the first network function is a time-sensitive communication and time synchronization function TSCTSF; and the receiving requirement information comprises one of the following:

Receiving the requirement information sent by AF;

The demand information sent by the NEF is received.
The method according to claim 30, wherein the method comprises:

The requirement information is sent to the PCF.
An information processing device, comprising:

The first sending module is configured to send requirement information, wherein the requirement information is used to indicate the requirement for two-way delay of the data stream of the multimedia extended reality XRM service.
An information processing device, comprising:

The second receiving module is configured to receive demand information, wherein the demand information is used to indicate the requirement for two-way delay of the data stream of the multimedia extended reality XRM service.
An information processing system, comprising: an AF, a first network function and a PCF;

The AF is configured to: send requirement information to the PCF or to the first network function, wherein the requirement information is used to indicate a requirement for a two-way delay of a data stream of a multimedia extended reality XRM service;

The first network function is configured to: send the requirement information to the PCF.
A communication device, wherein the communication device comprises:

processor;

a memory for storing instructions executable by the processor;

The processor is configured to implement the information processing method described in any one of claims 1 to 12, or claims 13 to 25, or claims 26 to 31 when running the executable instructions.
A computer storage medium, wherein the computer storage medium stores a computer executable program, and when the executable program is executed by a processor, it implements the information processing method described in any one of claims 1 to 12, or claims 13 to 25, or claims 26 to 31.