CN118633319A

CN118633319A - Information processing method and device, communication equipment and storage medium

Info

Publication number: CN118633319A
Application number: CN202380008088.9A
Authority: CN
Inventors: 吴锦花; 沈洋
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2023-01-09
Filing date: 2023-01-09
Publication date: 2024-09-10
Also published as: WO2024148495A1

Abstract

The embodiment of the disclosure provides an information processing method and device, a communication device and a storage medium; an information processing method, performed by AF, comprising: and sending requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of a data stream of the multimedia augmented reality XRM service.

Description

Information processing method and device, communication equipment and storage medium

Technical Field

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

Background

In mobile media services, extended Reality (XR) services such as augmented Reality (Augmented Reality, AR) or Virtual Reality (VR), cloud game services, video-based robots or unmanned aerial vehicle remote control, etc., and will contribute higher and higher traffic to the fifth generation mobile communication technology (5G) network. Multimodal data, which is data describing the same service or application and input from the same device or different devices, may be output to one or more destination devices. The data streams in the multimodal data often have a certain or even a strong correlation, such as synchronization of audio streams and video streams, synchronization of haptic data and visual data, etc.

Multimedia augmented reality (Multimedia Virtual Reality, XRM) traffic characteristics require that the 5G wireless communication system (5G system,5 gs) comprehensively consider the relevant data stream quality of service (Quality of Service, qoS) characteristics of the traffic, for example, consider whether parameters such as delay critical guaranteed bit rate (Guaranteed Bit Rate, GBR), guaranteed bit rate (Guaranteed Flow Bit Rate, GFBR), packet delay Budget (PACKET DELAY Budget, PDB) and/or maximum data burst (Maximum Data Burst Volume, MDBV) can be met at the same time and cooperatively agree. To a plurality of XRM data flows of a User Equipment (UE) and XRM data flows of a plurality of UEs, and to guarantee of consistency of QoS authorization and enforcement of each other. However, in the actual service process, the QoS authorization of each data flow may be directly affected due to the network delay status and/or the delay requirement of the application function (Application Function, AF) service, so as to affect whether the XRM service function can succeed.

Disclosure of Invention

The embodiment of the disclosure provides an information processing method and device, a communication device and a storage medium.

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

And sending requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of the data flow of the XRM service.

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

at least one demand value for uplink delay;

At least one demand value for downstream delay;

the first indication information is used for indicating the proportion of at least one uplink time delay to the bidirectional time delay and/or the proportion of at least one downlink time delay to the bidirectional time delay;

The second indication information is used for indicating a proportion threshold value of at least one uplink time delay to the bidirectional time delay and/or a proportion threshold value of at least one downlink time delay to the bidirectional time delay;

The third indication information is used for indicating whether the uplink time delay and the downlink time delay of at least one set of bidirectional time delay are the same;

Fourth indication information, wherein the fourth indication information is used for indicating that the data flow of the XRM service needs to consider bidirectional time delay;

priority indication information, wherein the priority indication information is used for indicating the priority of uplink time delay and/or the priority of downlink time delay;

A configuration file, wherein the configuration file is used for indicating a requirement value of an uplink delay and/or a requirement value of a downlink delay in at least one set of bidirectional delays, or the configuration file is used for indicating: at least one set of the requirement value of the uplink delay and the priority indicating information of the uplink delay in the bidirectional delay, and/or the requirement value of the downlink delay and the priority indicating information of the downlink delay.

In some embodiments, the demand information is sent, including one of:

transmitting the demand information to a policy control function (Policy Control Function, PCF);

Transmitting the demand information to a network opening function (Network Exposure Function, NEF), wherein the demand information is for the NEF to transmit to a time sensitive communication and time synchronization function (THE TIME SENSITIVE Communication and Time Synchronization Function, TSCTSF) or PCF;

The demand information is sent to TSCTSF, where the demand information is used TSCTSF to send to the PCF.

In some embodiments, the demand information is sent, including one of:

in the AF conversation request flow, sending demand information;

in the AF conversation updating flow, sending demand information;

In a service specific parameter providing process, transmitting demand information;

and in the process of setting the strategy for the subsequent AF session, sending the requirement information.

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

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

Policy AND CHARGING Control (PCC) rules;

QoS policies;

And/or the number of the groups of groups,

The predetermined information includes at least one of:

At least one value of the uplink time delay;

at least one value of the downlink delay;

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

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

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

In some embodiments, at least one of the following is also included in the first request:

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

UE address information;

A UE identifier for indicating a UE associated with the XRM service;

An application identifier, wherein the application identification information is used for indicating the XRM service;

a flow description;

data network name (Data Network Name, DNN);

Network slice selection support information (Network Slice Selection Assistance Information, S-NSSAI);

QoS parameters.

In some embodiments, in the service specific parameter providing procedure, sending the demand information includes:

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

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

XRM service identification;

a service description, wherein the service description includes a common identifier;

Service parameters;

A UE identifier for indicating a UE associated with the XRM service;

a UE group identifier for indicating a group of UEs or a plurality of UEs associated with the XRM service;

subscription events.

In some embodiments, a method comprises:

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

In some embodiments, a subscription notification is received, including one of:

Receiving a subscription notification sent by a user plane function (User Plane Function, UPF);

Receiving a 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;

Receiving subscription notification sent by 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.

According to a second aspect of embodiments of the present disclosure, there is provided an information processing method performed by a PCF, including:

And receiving requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of the data flow of the XRM service.

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

at least one demand value for uplink delay;

At least one demand value for downstream delay;

In some embodiments, demand information is received, including one of:

Receiving AF sending requirement information;

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

the request information sent by TSCTSF is received, wherein the request information is TSCTSF received from the NEF or received from the AF.

In some embodiments, demand information is received, including one of:

in the AF conversation request flow, receiving demand information;

in the AF conversation updating process, receiving demand information;

receiving demand information in a service specific parameter providing process;

in the policy flow set for the subsequent AF session, the demand information is received.

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

Determining a predetermined rule of the data stream based on the demand information;

the predetermined information is determined based on the demand information.

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

In some embodiments, a method comprises:

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

Wherein the update request is for the SMF to update the SMF stored PCC rules and/or QoS policies.

In some embodiments, the predetermined information is determined based on the demand information, including at least one of:

Determining the value of at least one uplink time delay and/or the value of at least one downlink time delay based on the demand information;

Determining the value of at least one uplink time delay and/or the value of at least one downlink time delay based on the demand information and the local configuration information; the local configuration information comprises: operator policy, default configuration information, and/or subscription information;

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

In some embodiments, the method comprises one of:

determining a QoS control of a traffic data Flow (SERVICE DATA Flow, SDF) level or a QoS Flow level based on the demand information; wherein the QoS control includes: qoS authorization and/or OoS update;

determining a QoS control of the SDF level or the QoS level based on the demand information and the local configuration information; the local configuration information comprises: operator policy, default configuration information, and/or subscription information.

In some embodiments, in the AF session request flow, receiving the demand information includes:

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

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

UE address information;

A UE identifier for indicating a UE associated with the XRM service;

a flow description;

DNN；

S-NSSAI；

QoS parameters.

In some embodiments, in a service specific parameter providing procedure, receiving demand information includes:

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

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

XRM service identification;

Service parameters;

A UE identifier for indicating a UE associated with the XRM service;

subscription events.

According to a third aspect of embodiments of the present disclosure, there is provided an information processing method performed by a first network function, including:

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

In some embodiments, the method comprises one of:

Transmitting the demand information to the PCF;

In some embodiments, a method comprises:

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

and sending subscription notification to the AF.

In some embodiments, the first network function is TSCTSF; the receiving demand information includes one of:

Receiving requirement information sent by AF;

And receiving the requirement information sent by the NEF.

In some embodiments, a method comprises: and sending the requirement information to the PCF.

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

And the first sending module is configured to send requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of the data flow of the XRM service.

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

at least one demand value for uplink delay;

At least one demand value for downstream delay;

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

Transmitting the demand information to the PCF;

Transmitting demand information to the NEF, wherein the demand information is used for the NEF to transmit to TSCTSF or PCF;

in the AF conversation request flow, sending demand information;

in the AF conversation updating flow, sending demand information;

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

PCC rules;

QoS policies;

And/or the number of the groups of groups,

The predetermined information includes at least one of:

At least one value of the uplink time delay;

at least one value of the downlink delay;

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

UE address information;

A UE identifier for indicating a UE associated with the XRM service;

a flow description;

DNN；

S-NSSAI；

QoS parameters.

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

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

XRM service identification;

Service parameters;

A UE identifier for indicating a UE associated with the XRM service;

subscription events.

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

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

Receiving a subscription notification sent by UPF;

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

and the second receiving module is configured to receive the requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of the data flow of the XRM service.

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

at least one demand value for uplink delay;

At least one demand value for downstream delay;

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

Receiving AF sending requirement information;

in the AF conversation request flow, receiving demand information;

in the AF conversation updating process, receiving demand information;

receiving demand information in a service specific parameter providing process;

In some embodiments, an apparatus comprises: a first processing module; a first processing module configured to perform at least one of:

the predetermined information is determined based on the demand information.

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

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

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

Determining a service data flow SDF level or QoS control of a QoS flow level based on the demand information; 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 an AF session request procedure, wherein the first request includes the requirement information.

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

UE address information;

A UE identifier for indicating a UE associated with the XRM service;

a flow 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 procedure, wherein the second request includes the requirement information.

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

XRM service identification;

Service parameters;

A UE identifier for indicating a UE associated with the XRM service;

subscription events.

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

And a third receiving module configured to receive the requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of the data stream of the XRM service.

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

In some embodiments, an apparatus comprises: a third transmission module; a third transmission module configured to perform one of:

Transmitting the demand information to the PCF;

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

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

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

Receiving requirement information sent by AF;

And receiving the requirement information sent by the NEF.

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

According to a seventh aspect of embodiments 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: transmitting demand information to the PCF or to the first network function, wherein the demand information is used for indicating the demand of bidirectional delay of a data stream of the multimedia augmented reality XRM service;

The first network function is configured to: and sending the requirement information to the PCF.

According to an eighth aspect of the embodiments of the present disclosure, there is provided a communication device, comprising:

A processor;

A memory for storing processor-executable instructions;

Wherein the processor is configured to: the information processing method of any embodiment of the present disclosure is implemented when the executable instructions are executed.

According to a ninth aspect of the embodiments of the present disclosure, there is provided a computer storage medium storing a computer executable program which when executed by a processor implements the information processing method of any of the embodiments of the present disclosure.

The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects:

In the embodiment of the disclosure, the AF sends requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of a data stream of the XRM service; in this way, considering the real-time or quasi-real-time bidirectional delay state of the data flow of the XRM service, the QoS authorization of each data flow in the SRM service can be determined, so that whether the XRM service function support can be successful or not can be determined accurately.

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

Drawings

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

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

Fig. 3 is a schematic diagram illustrating 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 illustrating 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 of an information processing apparatus according to an exemplary embodiment.

Fig. 12 is a block diagram of an information processing apparatus according to an exemplary embodiment.

Fig. 13 is a block diagram of an information processing apparatus according to an exemplary embodiment.

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

Fig. 15 is a network architecture diagram of a 5G system according to an exemplary embodiment.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to 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. Rather, they are merely examples of apparatus and methods consistent with aspects of embodiments of the present disclosure as detailed in the accompanying claims.

The terminology used in the embodiments of the disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the disclosure. As used in this disclosure of embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in embodiments of the present disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of embodiments of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" depending on the context.

Referring to fig. 1, a schematic structural diagram of a wireless communication system according to an embodiment of the disclosure is shown.

As shown in fig. 1, the wireless communication system may include: a number of user devices 110 and a number of access network devices 120. Wherein the wireless communication system may be a fourth generation mobile communication technology (the 4th generation mobile communication,4G) system, also known as a long term evolution (Long Term Evolution, LTE) system; or the wireless communication system can also be a 5G system, also called a new air interface system or a 5G NR system. Or the wireless communication system may be a next generation system of a 5G system or the like.

User device 110 may be, among other things, 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 (Radio Access Network, RAN), and the user equipment 110 may be internet of things user equipment such as sensor devices, mobile phones (or "cellular" phones) and computers with internet of things user equipment, for example, stationary, portable, pocket, hand-held, computer-built-in or vehicle-mounted devices. Such as a Station (STA), subscriber unit (subscriber unit), subscriber Station (subscriber Station), mobile Station (mobile Station), remote Station (remote Station), access point, remote user equipment (remote terminal), access user equipment (ACCESS TERMINAL), user device (user terminal), user agent (user agent), user device (user device), or user equipment (user request). Or the user device 110 may be a device of an unmanned aerial vehicle. Alternatively, the user device 110 may be a vehicle-mounted device, for example, a laptop with a wireless communication function, or a wireless user device with an external laptop. Alternatively, the user device 110 may be a roadside device, for example, a street lamp, a signal lamp, or other roadside devices with wireless communication function.

Access network device 120 may be a network-side device in a wireless communication system. Wherein access network device 120 may be an evolved base station (eNB) employed in a 4G system. Or access network device 120 may be a base station (gNB) in a 5G system employing a centralized and distributed architecture. Or access network device 120 may be an access network in a 5G system may be referred to as a New Generation radio access network (NG-RAN). When access network device 120 employs a centralized and distributed architecture, it typically includes a Centralized Unit (CU) and at least two Distributed Units (DUs). A protocol stack of a packet data convergence protocol (PACKET DATA Convergence Protocol, PDCP) layer, a radio link layer control protocol (Radio Link Control, RLC) layer and a media access control (Medium Access Control, MAC) layer is arranged in the centralized unit; a Physical (PHY) layer protocol stack is provided in the distribution unit, and the specific implementation of the access network device 120 is not limited in the embodiments of the present disclosure.

A wireless connection may be established between access network device 120 and user device 110 over a wireless air interface. In various embodiments, the wireless air interface is a fourth generation mobile communication network technology (4G) standard-based wireless air interface; or the wireless air interface is a wireless air interface based on a fifth generation mobile communication network technology (5G) standard, for example, the wireless air interface is a new air interface; or the wireless air interface can also be a wireless air interface based on the technical standard of the next generation mobile communication network of 5G.

In some embodiments, an E2E (End to End) connection may also be established between the user devices 110. Such as vehicle-to-vehicle (vehicle to vehicle, V2V) communications, vehicle-to-road side equipment (vehicle to Infrastructure, V2I) communications, and vehicle-to-person (vehicle to pedestrian, V2P) communications in a vehicle networking communication (vehicle to everything, V2X).

Here, the above-described user equipment can be regarded as the terminal equipment of the following embodiment.

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

Several access network devices 120 are respectively connected to a core network device 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 (Mobility MANAGEMENT ENTITY, MME) in an evolved packet core (Evolved Packet Core, EPC). Or the core network device may be other core network devices, such as a service GateWay (SERVING GATEWAY, SGW), a public data network GateWay (Public Data Network GateWay, PGW), a Policy AND CHARGING Rules Function (PCRF), or a home subscriber server (Home Subscriber Server, HSS), etc.; or the core network device 130 may be a core network device in 5G; such as a policy control function (Policy Control Function, PCF), or session management function (Session Management Function, SMF), access and mobility management function (ACCESS AND Mobility Management Function, AMF), unified data management (Unified DATA MANAGEMENT, UDM), or user plane function (User Plane Function, UPF), etc. The embodiments of the present disclosure are not limited with respect to the implementation form of the core network device 130.

For ease of understanding by those skilled in the art, the embodiments of the present disclosure enumerate a plurality of implementations to clearly illustrate the technical solutions of the embodiments of the present disclosure. Of course, those skilled in the art will appreciate that the various embodiments provided in the embodiments of the disclosure may be implemented separately, may be implemented in combination with the methods of other embodiments of the disclosure, and may be implemented separately or in combination with some methods of other related technologies; the embodiments of the present disclosure are not so limited.

In order to better understand the technical solution described in any embodiment of the present disclosure, first, a part of the application scenario to which the present disclosure is applicable is described:

XRM traffic characteristics require 5GS to comprehensively consider QoS characteristics of related data flows of the traffic, for example, considering whether parameters such as delay GBR, GFBR, PDB and/or MDBV can be satisfied simultaneously and cooperatively consistent. To multiple XRM data flows for one UE, and to compliance guarantee of QoS authorization and enforcement for multiple XRM data flows for a UE with respect to each other. Among them, uplink-downlink transmission coordination (Uplink-downlink transmission coordination to meet Round-TRIP LATENCY requirements) meeting the round trip delay requirement is a key issue for 5GS XRM traffic research.

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

The delay status in the actual business process is dynamically and continuously changed under the influence of various factors in the network. In particular, XRM services often require that multiple data flows within a UE, or different data flows of multiple UEs, can successfully grant corresponding QoS to support service implementation. Therefore, the real-time or quasi-real-time delay state of the network and the real-time delay requirement of the AF service can directly influence the QoS authorization of each data flow, so that whether the 5GS XRM service function support can be successful or not is influenced. However, there is no perfect mechanism for supporting this requirement in the current 5GS system, and there is no corresponding technical solution for supporting QoS authorization and optimization of the bidirectional delay requirement of PCF XRM service data flows.

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

Step S21: and sending requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of the data flow of the XRM service.

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

In embodiments of the present disclosure, AF, PCF, SMF, TSCTSF, and the like may each be a logical node or function that can be flexibly deployed in a communication network.

In an embodiment of the present disclosure, the demand information may also be: for indicating the need for a bi-directional delay of the data flow of the service. The service may be, but is not limited to, an XRM service; the service may be any kind of service, for example, XR service.

The information processing method provided in the embodiment of the present disclosure may be: and sending the demand information. Here, the requirement information may be bidirectional delay requirement information, or the requirement information is used to indicate the requirement of bidirectional delay.

In one embodiment, demand information is used to indicate the demand for enhanced bi-directional latency. Illustratively, the requirement information is for indicating a requirement for enhanced bi-directional latency of a data stream of the XRM service. Here, the enhanced bidirectional delay is relative to only the time delay but not considering the uplink and downlink delays, or the enhanced bidirectional delay is relative to only the requirement of the bidirectional delay but not the requirement value, proportion threshold and/or priority of the specific indication of the bidirectional delay.

In one embodiment, the demand information may be bi-directional latency demand information, or the demand information may be RT latency demand 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 a plurality of UEs. At least one mentioned in the embodiments of the present disclosure may be one or more; the plurality may be two or more.

In one embodiment, the XRM service in step S21 may also be replaced with a multi-modal data service (multimodal DATA SERVICE). That is, the AF may send the requirement information to the network device, where the requirement information is used to indicate a requirement of a bidirectional delay of a data flow of the multi-mode data service. Of course, it should be understood that XRM traffic and multimodal data traffic are examples only, and that other traffic types are possible.

In one embodiment, the bi-directional delay may include, but is not limited to: uplink delay and downlink delay, or round trip bi-directional delay.

Here, the requirement information may be a requirement for at least one set of bidirectional delays for indicating a data flow of the XRM service. At least one set of the disclosed embodiments can be one set or multiple sets; the multiple sets may be two sets or more than two sets.

In one embodiment, the bi-directional delay may be: round-trip delay (Round-TRIP LATENCY), or bidirectional delay budget (Two way delay budget), or uplink and downlink Packet Delay Budget (PDB).

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

At least one demand value for uplink delay and/or at least one demand value for downlink delay;

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

at least one requirement value of downlink delay and priority indication information for indicating the priority of the downlink delay;

In another embodiment, the demand information may further include: a demand value for the bi-directional delay. Here, the demand information may include demand information of a bidirectional delay, and at least one of the following information: the method comprises the steps of a set of bidirectional delay, a requirement value of uplink delay and/or a requirement value of downlink delay, first indication information, second indication information, third indication information, fourth indication information and priority indication information.

The demand information includes, for example, a demand value for an upstream delay and/or a demand value for a downstream delay in a set of bidirectional delays, the demand value being a specific value. Or the demand information includes sets of bidirectional delays, one uplink delay in each bidirectional delay corresponding to a demand value and/or one downlink delay corresponding to a demand value. Here, the requirement value of the uplink delay and the requirement value of the downlink delay in the set of bidirectional delays may be the same or different; the multiple sets of bidirectional delays have different uplink delay requirement values and/or different downlink delay requirement values.

The first indication information is used for indicating the proportion of the uplink time delay to the bidirectional time delay and/or the proportion of the downlink time delay to the bidirectional time delay in at least one set of bidirectional time delay. Here, the proportion of the upstream delay to the bidirectional delay and the proportion of the downstream delay to the bidirectional delay in the set of bidirectional delays may be the same or different; for example, the proportion of the uplink delay to the bidirectional delay is 40%, and the proportion of the downlink delay to the bidirectional delay is 60%; for another example, the proportion of the uplink delay to the bidirectional delay and the proportion of the downlink delay to the bidirectional delay are both 50%. Here, the proportion of the uplink delay to the bidirectional delay and/or the proportion of the downlink delay to the bidirectional delay in the multiple sets of bidirectional delays may also be: the first set of bidirectional delay and the second set of bidirectional delay are respectively provided with an uplink delay and a downlink delay, wherein the proportion of the uplink delay in the first set of bidirectional delay is 40%, the proportion of the uplink delay in the second set of bidirectional delay is 50%, and the proportion of the downlink delay in the third set of bidirectional delay is 70%; here, when the proportion of the uplink delay to the bidirectional delay is known, the proportion of the downlink delay to the bidirectional delay in the set of delays can be determined, or when the proportion of the downlink delay to the bidirectional delay in the set of delays is known, the proportion of the uplink delay to the bidirectional delay in the set of delays can be determined; for example, the proportion of the upstream delay in the first set of bidirectional delay to the bidirectional delay is 40%, and the proportion of the downstream delay in the first set of bidirectional delay to the bidirectional delay may be 60%.

The second indication information is used for indicating a proportion threshold value of uplink time delay to the bidirectional time delay and/or a proportion threshold value of downlink time delay to the bidirectional time delay in at least one set of bidirectional time delay. The scale threshold may also be used for scale interval replacement; for example, the proportion threshold of the uplink delay to the bidirectional delay may be 40%, and the proportion interval of the good line delay to the bidirectional delay may be less than or equal to 40%. Here, the proportion threshold may be a proportion minimum value, or a maximum value, or a proportion interval value. Here, the ratio threshold of the uplink delay to the bidirectional delay and the ratio threshold of the downlink delay to the bidirectional delay may be the same or different; for example, the proportion threshold value of the uplink delay accounting for the bidirectional delay is not lower than 40%, and the proportion threshold value of the downlink delay accounting for the bidirectional delay is not higher than 60%; for another example, the ratio threshold of the uplink delay to the bidirectional delay and the ratio threshold of the downlink delay to the bidirectional delay are not lower than 40%. Here, the ratio threshold of the uplink delay to the bidirectional delay and/or the ratio threshold of the downlink delay to the bidirectional delay of the multiple sets of bidirectional delays may also be: the ratio threshold of the uplink delay to the bidirectional delay in the first set of bidirectional delay is not lower than 40%, the ratio threshold of the uplink delay to the bidirectional delay in the second set of bidirectional delay is not higher than 40%, the ratio threshold of the downlink delay to the bidirectional delay in the third set of bidirectional delay is 50%, and the ratio threshold of the downlink delay to the bidirectional delay in the fourth set of bidirectional delay is: greater than or equal to 30% and less than or equal to 50%.

The third indication information may be used to indicate that the uplink delay and the downlink delay are the same or different in the bidirectional delay. Here, the third indication information includes 3 bits; the first bit is a first value, and can be used for indicating that the requirement value of the uplink time delay and the requirement value of the downlink time delay of the first set of bidirectional time delay are the same; the second bit is a second value, and is used for indicating that the requirement value of the uplink delay and the requirement value of the downlink delay of the second set of bidirectional delay are different; and the third bit is a second value, and is used for indicating that the requirement value of the uplink delay and the requirement value of the downlink delay are different in the third set of bidirectional delay.

The fourth indication information may be, for example, an RT requirement indication in the above embodiment, for indicating a requirement that bidirectional delay needs to be considered.

Illustratively, the priority indication information is used to indicate the priority of the uplink and/or downlink delay in at least one set of bidirectional delays. Here, the higher the priority of the upstream and/or downstream delays in the bi-directional delay is, the more the bi-directional delay is relatively considered to be performed; or the lower the priority in the upstream and/or downstream delays in the bi-directional delay, the less the bi-directional delay is relatively considered to be implemented.

It should be noted that, as those skilled in the art may understand, the methods provided in the embodiments of the present disclosure may be performed alone or together with some methods in the embodiments of the present disclosure or some methods in the related art.

In some embodiments, the sending of the requirement information in step S21 may be: and sending the requirement information to the second network function. Here, the second network function is a logical node or function in the core network that can be flexibly deployed. Illustratively, the second network function may be, but is not limited to being, PCF, NEF, TSCTSFH, and/or the like.

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

Transmitting the demand information to the PCF;

That is, the AF may send the demand information to different network devices as needed, may send the demand information directly or indirectly to the PCF, for example, may send the demand information to the PCF via one or both of NEF or TSCTSF.

The embodiment of the present disclosure provides an information processing method, performed by AF, including one of:

Transmitting the demand information to the PCF;

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

Illustratively, the AF sends the demand information to the NEF, which sends the demand information to the PCF; or the AF sends the requirement information to the NEF, the NEF sends the requirement information to the TSCTSF, and the TSCTSF sends the requirement information to the PCF. Here, the NEF may directly forward the requirement information to the PCF or TSCTSF after receiving the requirement information, or the NEF may first perform authorization authentication, and forward the requirement information to the PCF or TSCTSF after the authorization authentication is passed. Therefore, the NEF can forward the requirement information sent by the AF to the PCF, so that the successful transmission of the requirement information is realized; and authorization authentication can be performed based on the NEF, whether the AF is trusted or not is verified, if yes, the NEF forwards the demand information, and therefore the security of demand information transmission can be improved.

Illustratively, the AF sends the demand information to TSCTSF, TSCTSF sends the demand information to the PCF. In this way, the AF may also forward the requirement information to the PCF through TSCTSF, so that successful delivery of the requirement information can be successfully achieved.

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

in the AF conversation request flow, sending demand information;

in the AF conversation updating flow, sending demand information;

It should be appreciated that the AF may send the demand information in a different flow. And the content of the transmitted demand information may be the same or different. The specific content of the requirement information has been described in detail in the foregoing embodiments, and will not be described in detail herein.

As shown in fig. 3, an embodiment of the present disclosure provides an information processing method, performed by AF, including:

Step S31: in the AF conversation request flow, sending demand information; or in the AF conversation updating flow, sending the demand information; or in the service specific parameter providing flow, sending the demand information; or in the process of setting the strategy for the subsequent AF session, the requirement information is sent.

Illustratively, the AF session request flow may be described in the communication protocol as: AF session with required QoS procedure. The AF session update procedure can be described in the communication protocol as: AF session with required QoS update procedure. The service specific parameter providing procedure can be described in the communication protocol as: SERVICE SPECIFIC PARAMETER Provisioning. Setting policy flows for subsequent AF sessions can be described in the communication protocol as: set a policy for a future AF session.

By way of example, when setting policy flows for subsequent AF sessions, it may be referred to that: before the AF session request is started, the flow of policies or data or service characteristics related to the service function of the AF is performed. Here, the policy flow is set in the subsequent AF session, that is, the related flow set for the AF session that needs to be started in the future, without the AF session itself being started.

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

The embodiment of the disclosure provides an information processing method, which is executed by AF and comprises the following steps: in the AF session request process, a first request is sent, wherein the first request includes the requirement 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 the demand information and XRM traffic information. Here, the XRM service information includes, but is not limited to, at least one of: common identification, UE address information, UE identifier, application identifier, flow identification, DNN, S-NSSAI, and QoS parameters.

In some embodiments, at least one of the following is also included in the first request: a common identity (common ID), wherein the common identity is used to indicate all data flows in a group of XRM traffic; UE address information; a UE identifier for indicating a UE associated with the XRM service; an application identifier, wherein the application identification information is used for indicating the XRM service; a flow description; DNN; S-NSSAI; qoS parameters.

Illustratively, there are multiple data streams treated as a group, with a common identifier identifying all of the data streams in the group; the plurality of data streams may be a plurality of data streams in one UE or a plurality of data streams in a plurality of UEs. The Application identifier may be, for example, an AF identifier Application ID (AF IDENTIFIER Application ID). And the flow description is used for indicating the characteristic information of the data flow.

The UE address information may be, for example, address information for XRM traffic-related UEs. The address information may be, but is not limited to, an IP address. The identifier of the UE may be any character string for identifying the UE, and the character string may include at least one character; the identifier of the UE may be, but is not limited to, a Subscriber implicit identity (Subscription Concealed Identifier, SUCI), a Subscriber permanent identity (subscnber PERMANENT IDENTIFIER, SUPI), an index or number, or the like.

Illustratively, the QoS parameters may be, but are not limited to: PDU set error rate (PDU Set Error Rate, PSER), PDU set delay budget (PDU Set Delay Budget, PSDB), and/or PDU set Indication (PSII), among others.

In the embodiment of the disclosure, the purpose of sending the requirement information of the requirement of the bidirectional delay in the AF session request can be achieved by sending the requirement information in the AF session request flow. And the requirement information may be transmitted through a first request, for example, through an AF request, so that two functions may be implemented through one first request. And the first request also comprises XRM service information, so that the network element of the core network can determine QoS authorization and the like based on the requirement information and the XRM service information.

In some embodiments, in the service specific parameter providing procedure, sending the demand information includes: in the service specific parameter providing process, a second request is sent, wherein the second request includes the requirement information.

The embodiment of the disclosure provides an information processing method, which is executed by AF and comprises the following steps: in the service specific parameter providing process, a second request is sent, wherein the second request includes the requirement information.

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

In some embodiments, the second request further includes at least one of: XRM service identification; a service description, wherein the service description includes a common identifier; service parameters; a UE identifier for indicating a UE associated with the XRM service; a UE group identifier for indicating a group of UEs or a plurality of UEs associated with the XRM service; and subscribing to events.

Illustratively, the XRM service identity is used to indicate XRM service. And the service description is used for identifying the XRM service or the multi-mode data service; in particular, the service description may include, but is not limited to, at least one of: public identity, XRM Service identity, AF Service identity (AF-Service-Identifier) or external application identity (Application Identifier). Here, the service description may identify the XRM service by a common identification or may identify the XRM by an XRM service identification. The Service description may identify the XRM Service by an AF Service Identifier (AF-Service-Identifier) or an external application Identifier (Application Identifier).

Exemplary, service parameters are used to indicate AF guidance information for XRM service or multi-mode data service related policy and/or QoS parameter determination. The traffic parameters may include, but are not limited to, at least one of: the list of UI rules for XRM traffic or multimodal data application traffic (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 (SSC) patterns, and priorities of related rules (e.g., alternative QoS parameter priorities, location or time window priorities, and/or routing priorities, etc.).

Illustratively, the subscription event (Subscription to events) may be used to indicate an enforcement and/or change event of a subscription session management (Session Management, SM) policy or an access management (ACCESS MANAGEMENT, AM) policy or a UE policy, etc., or may be used to indicate a QoS monitoring event.

In the embodiment of the disclosure, the purpose of sending the demand information of the demand of the bidirectional delay in the service specific parameter providing process can be achieved by sending the demand information in the service specific parameter providing process. And the requirement information may be transmitted through a second request, such as an AF request, so that both functions may be implemented through one second request. And the second request also comprises information such as service description or service parameters, so that the network element of the core network can determine QoS authorization and the like based on the requirement information, the service description or the service parameters and the like.

Of course, in other embodiments, the AF may also provide the requirement information to the core network device such as PCF in the AF session update procedure or in setting policy procedure for the subsequent AF session, etc.

In some embodiments, the demand information is used by the PCF to determine predetermined rules and/or to determine predetermined information. Illustratively, the AF sends to the PCF demand information indicating a demand for a bidirectional delay of the data flow of the XRM service; the demand information is used by the PCF to determine predetermined rules and/or predetermined information.

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

Policy AND CHARGING Control (PCC) rules;

QoS policies;

And/or the number of the groups of groups,

The predetermined information includes at least one of:

At least one value of the uplink time delay;

at least one value of the downlink delay;

By way of example, the PCC rule may be any charging-related rule, and is not limited herein. The QoS policy may be any policy related to the quality of service of the data flow, and is not limited herein.

Illustratively, a QoS identifier may be used to identify at least one QoS characteristic of the data flow, one QoS characteristic may be indicated by one QoS parameter. The QoS identifier may be an identifier of 5G QoS (i.e., 5 QI). Here, qoS identification may be used to identify at least one of: 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 error rate of the data stream, and the scene (such as session, voice or video, etc.) to which the data stream is adapted.

In another embodiment, the requirement information is used by the PCF to determine PCC rules, which are used by the PCF to determine QoS identification.

In yet another embodiment, the requirement information is used for the PCF to determine a service data packet (SERVICE DATA Flow, SDF) level (level) or QoS control of the QoS Flow level; wherein the QoS control includes, but is not limited to: qoS authorization and/or OoS update.

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

In the embodiment of the disclosure, the requirement information may be provided to the PCF by the AF, so that the PCF may determine, based on the requirement information, a value of a bidirectional delay of a data flow of the XRM service, a PCC rule, a QoS policy, a QoS identifier, and/or the like, so that the PCF may accurately determine QoS authorization and the like of the data flow of the XRM service, thereby accurately determining whether the XRM service function of the at least one UE is successful.

As shown in fig. 4, an embodiment of the present disclosure provides an information processing method, performed by AF, including:

step S41: a subscription notification is received, wherein the subscription notification includes a report determined based on the demand information.

By way of example, the report of the need information determination may be, but is not limited to: measured UL delay and/or DL delay, and/or measured bi-directional delay. Here, after receiving the requirement information, the network elements such as UPF determine the measured UL delay and/or DL delay based on the requirement information; the UPF may carry UL latency and/or DL latency 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, i.e., the AF sends the requirement information first and then receives the subscription notification. However, it should be understood that in some embodiments, the AF may also receive subscription notifications that include information such as reports that the network device determines based on otherwise obtained demand information.

In one embodiment, the AF sends the demand information to the UPF; the AF receives subscription notifications that the UPF determines based on the requirement information. Here, the AF may send the requirement information to the UPF: AF directly sends the demand information to UPF; or the AF sends the demand information to the NEF, which sends the demand information to the UPF.

In another embodiment, the requirement information is for the PCF to forward to the UPF, and the requirement information is for the UPF to determine the subscription notification. Illustratively, the AF sends the demand information to the PCF, which sends the demand information to the UPF; the UPF determines a report based on the demand information, and the UPF carries the report in a subscription notification to send to the AF. Here, the PCF may send the requirement information to the UPF by: the PCF sends the demand information to the SMF, which sends the demand information to the UPF.

In some embodiments, the subscription notification is received in step S41, including one of:

Receiving a subscription notification sent by UPF;

The embodiment of the disclosure provides an information processing method, which is executed by AF and comprises the following steps:

Receiving a subscription notification sent by UPF;

Illustratively, the UPF may send the subscription notification to the AF based on the manner in which the user plane is reported. For example, the UPF directly sends subscription notifications to the AF. As another example, UFP sends subscription notification to NEF, which sends subscription notification to AF.

Illustratively, the UPF may send subscription notifications to the AF based on the manner in which the control plane reports. For example, the UPF sends the subscription notification to the SMF, the SMF sends the subscription notification to the PCF, and the PCF sends the subscription notification to the AF. For another example, the UPF sends the subscription notification to the SMF, the SMF sends the subscription notification to the PCF, the PCF sends the subscription notification to the NEF, and the NEF sends the subscription notification to the AF.

In the embodiment of the disclosure, the AF can receive the subscription notification reported by the UPF based on the mode reported by the user plane or the mode reported by the control plane, so that the AF can adapt to the receiving of the subscription notification in more application scenes. And is advantageous in enabling the AF to provide the PCF with the need information based on the subscription notification.

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

In response to receiving the demand information, such as UPF, the measured UL and/or DL delays, and/or the measured bi-directional delays may be obtained.

The following information processing method is performed by the PCF, similarly to the description of the information processing method performed by the AF described above; for technical details not disclosed in the embodiment of the information processing method performed by the PCF, reference is made to the description of an example of the information processing method performed by the AF, and a detailed description thereof will not be made here.

As shown in fig. 5, an embodiment of the present disclosure provides an information processing method, which is performed by a PCF, including:

Step S51: and receiving requirement information, wherein the requirement information is used for indicating the requirement of bidirectional 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, respectively, of the embodiments described above; the demand information may be demand information in the above-described embodiment; the bidirectional delay may be the bidirectional delay in the above-described embodiments. The foregoing embodiments have been described in detail, and are not described in detail herein.

Illustratively, the bi-directional delay may include, but is not limited to: uplink delay and downlink delay, or round trip bi-directional delay. The bi-directional delay may be: round-trip delay (Round-TRIP LATENCY), or bidirectional delay budget (Two way delay budget), or uplink and downlink Packet Delay Budget (PDB).

Exemplary, demand information includes at least one of:

Illustratively, the demand information includes a demand value for an upstream delay and/or a demand value for a downstream delay in at least one set of bidirectional delays. The first indication information is used for indicating the proportion of the uplink time delay to the bidirectional time delay and/or the proportion of the downlink time delay to the bidirectional time delay in at least one set of bidirectional time delay. And the second indication information is used for indicating the proportion threshold value of the uplink time delay to the bidirectional time delay and/or the proportion threshold value of the downlink time delay to the bidirectional time delay in at least one set of bidirectional time delay. And the third indication information can be used for indicating that the uplink time delay and the downlink time delay in the bidirectional time delay are the same or different. The priority indication information is used for indicating the priority of the uplink time delay and/or the downlink time delay of at least one set of bidirectional time delay.

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

Receiving AF sending requirement information;

The embodiment of the disclosure provides an information processing method, which is executed by PCF and comprises the following steps:

Receiving AF sending requirement information;

in the AF conversation request flow, receiving demand information;

in the AF conversation updating process, receiving demand information;

receiving demand information in a service specific parameter providing process;

in the AF conversation request flow, receiving demand information;

in the AF conversation updating process, receiving demand information;

receiving demand information in a service specific parameter providing process;

In one embodiment, in the AF session request flow, receiving the requirement information includes: in an AF session request procedure, a first request is received, wherein the first request includes requirement information.

The embodiment of the disclosure provides an information processing method, which is executed by PCF and comprises the following steps: in an AF session request procedure, a first request is received, wherein the first request includes requirement information.

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

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

For example, the first request may include at least one of: a common identifier, wherein the common identifier is used for indicating all data flows in the group of XRM services; UE address information; a UE identifier for indicating a UE associated with the XRM service; an application identifier, wherein the application identification information is used for indicating the XRM service; a flow description; DNN; S-NSSAI; qoS parameters.

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

The embodiment of the disclosure provides an information processing method, which is executed by PCF and comprises the following steps: in the service specific parameter providing process, a second request is received, wherein the second request includes the requirement information.

In some embodiments of the present disclosure, the second request may be the second request in the above embodiments. For example, the second request may include at least one of: XRM service identification; a service description, wherein the service description includes a common identifier; service parameters; a UE identifier for indicating a UE associated with the XRM service; a UE group identifier for indicating a group of UEs or a plurality of UEs associated with the XRM service; and subscribing to events.

The above embodiments may be specifically referred to the description on the AF side, and will not be described herein.

As shown in fig. 6, an embodiment of the present disclosure provides an information processing method, which is performed by a PCF, including:

step S61: determining a predetermined rule of the data stream based on the demand information; and/or determining the 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.

Illustratively, the predetermined rules include: PCC rules and/or QoS policies.

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

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

In some embodiments, the predetermined information is determined in step S61 based on the demand information, including at least one of:

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

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

Here, the operator policy information may be, but is not limited to, any policy about bidirectional delay, which is set by an operator, for example, the mobile determines that the uplink delay and/or the downlink delay of a set of bidirectional delays do not exceed a certain threshold, etc., and the operator policy information is not specifically limited herein.

Here, default configuration information for indicating a default configuration; the default configuration information may also be used to indicate that the priority of the need for enhanced bi-directional latency is due to the default configuration. Thus, when the PCF receives the demand information, the values of the upstream delay and the downstream delay in the bidirectional delay are determined based on the demand information, without considering the default configuration.

Here, the subscription information may be, but is not limited to, any information indicating whether at least one characteristic with the XRM service or the multi-mode data service is authorized, and the subscription information is not particularly limited herein.

In some embodiments, determining the value of the at least one upstream delay and/or the value of the at least one delay based on the demand information comprises at least one of:

Determining the value of at least one uplink delay and/or the value of at least one downlink delay based on the requirement value of at least one uplink delay and/or the requirement value of the downlink delay in the requirement information;

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

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

Determining the value of at least one uplink time delay and/or the value of at least one downlink time delay based on the third indication information in the demand information and the first indication information or based on the third indication information in the demand information and the first indication information;

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

And determining the value of at least one uplink time delay and/or the value of at least one downlink time delay based on the priority indication information in the demand information.

Here, determining the value of at least one uplink delay and/or the value of at least one downlink delay may be: and determining the value of at least one set of bidirectional delay and/or the value of the uplink delay and/or the value of the downlink delay.

Illustratively, the PCF receives the demand information sent by the AF, where the demand information indicates that a set of bidirectional delays has a demand value of 50ms for upstream delay and 60ms for downstream delay; the PCF may determine, based on the demand information, that the uplink delay has a value of 50ms and the downlink delay has a value of 60ms for a set of bi-directional delays of the data stream.

The PCF receives, by way of example, demand information sent by the AF, the demand information including first indication information indicating that an uplink delay accounts for 40% of the bidirectional delay and a downlink delay accounts for 60% of the bidirectional delay; the PCF knows that the bidirectional delay is 100ms, and determines that the value of the uplink delay is 40ms and the value of the downlink delay is 60ms in a set of bidirectional delay.

The PCF receives, by way of example, the demand information sent by the AF, where the demand information includes second indication information, and the second indication information indicates that a proportion threshold of uplink delay to bidirectional delay is not less than 40% and a proportion threshold of downlink delay to bidirectional delay is not more than 60%; the PCF knows that the bidirectional delay is 100ms, and determines that the value of the uplink delay is 45ms and the value of the downlink delay is 55ms in a set of bidirectional delay.

The PCF receives, by way of example, the requirement information sent by the AF, where the requirement information includes third indication information and a requirement value of an uplink delay in a set of bidirectional delays is 50ms, and the third indication information indicates that the uplink delay and the downlink delay in the set of bidirectional delays are the same; the PCF determines that the values of the uplink delay and the downlink delay in a set of bidirectional delay are 50ms.

The PCF receives, by way of example, the requirement information sent by the AF, where the requirement information includes fourth indication information, and the fourth indication information indicates that the data flow of the XRM service needs to consider bidirectional delay; PCF knows that the bidirectional time delay is 100ms; the PCF determines that the bidirectional time delay is divided into uplink time delay and uplink time delay based on the fourth indication information, and only the sum of the uplink time delay and the uplink time delay does not exceed the bidirectional time delay; for example, the PCF determines that the uplink delay has a value of 40ms and the downlink delay has a value of 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 uplink delay and the downlink delay are both 50ms.

Illustratively, the PCF receives the requirement information sent by the AF, where the requirement information includes three sets of requirement values of bidirectional delay, which are respectively: the first set of bidirectional delay has a requirement value of uplink delay of 40ms and a requirement value of downlink delay of 60ms, the second set of bidirectional delay has a requirement value of uplink delay and a requirement value of downlink delay of 50ms, and the third set of bidirectional delay has a requirement value of uplink delay of 55ms and a requirement value of downlink delay of 45ms; the demand information further includes priority indication information corresponding to the demand values of the three sets of bidirectional delays, the three priority indications being respectively low priority indication information corresponding to the first set of bidirectional delays, medium priority indication information corresponding to the medium priority of the second set of bidirectional delays, and high priority indication information corresponding to the third set of bidirectional delays. The PCF determines that the value of one set of bidirectional delay is the required value of the third set of bidirectional delay based on the required information, namely the value of the uplink delay is 55ms and the value of the downlink delay is 45ms.

In the embodiment of the disclosure, the PCF may accurately determine the value of the uplink delay and/or the downlink delay in at least one set of bidirectional delay based on the requirement information; and can be determined based on various ways, and can adapt to more application scenes.

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

In some embodiments, determining the QoS identification of the data flow based on the demand information comprises:

determining PCC rules of a number of flows based on the demand information;

based on the PCC rules, the QoS identification of the data flow is determined.

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

The embodiment of the disclosure provides an information processing method, which is executed by PCF and comprises the following steps: sending an update request to the SMF, wherein the update request includes: PCC rules and/or QoS policies; wherein the update request is for the SMF to update the SMF stored PCC rules and/or QoS policies.

Illustratively, the PCF determines PCC rules and/or QoS policies for the data flows in the XRM service based on the demand information; the PCF sends an update request to the SMF, wherein the update request comprises PCC rules and/or QoS policies; after the SMF receives the update request, the PCC rules stored in the SMF are updated based on the PCC rules in the update request and/or the QoS policies stored in the SMF are updated 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 to enable the SMF to update PCC rules and/or QoS policies stored in the SMF.

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

determining a QoS control of the SDF level or the QoS flow level based on the demand information; wherein the QoS control includes: qoS authorization and/or OoS update;

Based on the requirement information and the local configuration information, a QoS control of the SDF level or the 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 QoS control for the SDF level may be QoS authorization and/or QoS update for a particular SDF.

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

Illustratively, there are M data streams, of which N are particular data streams, such as video data streams; the QoS control of the SDF level may be QoS control for the N data flows classified into one type; wherein M, N is an integer; n is less than M.

In the above embodiment, if N data flows are video data flows and L data flows are audio data flows, qoS control at QoS flow level may be performed by using N video data flows as one type of data flows and QoS control at QoS flow level may be performed by using L audio data flows as another type of data flows.

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

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

determining QoS control of the SDF level or the QoS flow level based on first indication information in the demand information;

determining QoS control of the SDF level or the QoS flow level based on second indication information in the demand information;

determining QoS control of the SDF level or the QoS flow level based on third indication information in the demand information;

based on the fourth indication information in the demand information, determining the SDF level or QoS control of the QoS flow level.

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

In the embodiment of the disclosure, the QoS control of the SDF level or the QoS flow level may be performed on the data flow based on the requirement information, that is, the control of classifying the plurality of data flows into one type may be implemented.

The following information processing method, which is performed by the first network function, is similar to the description of the information processing method performed by the AF and/or PCF described above; for technical details not disclosed in the embodiment of the information processing method 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, and detailed description thereof will not be provided herein.

As shown in fig. 7, an embodiment of the present disclosure provides an information processing method, which is executed by a first network function, including:

Step S71: and receiving requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of the data flow of the XRM service.

In one embodiment, the first network function may be a logical node or function in the core network that is capable of flexible deployment. Illustratively, 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 demand information in the above embodiments; the bidirectional delay may be the bidirectional delay in the above-described embodiments.

Illustratively, the bi-directional delay may be, but is not limited to being: uplink delay and downlink delay, or round trip bi-directional delay. The bi-directional delay may be: round-trip delay (Round-TRIP LATENCY), or bidirectional delay budget (Two way delay budget), or uplink and downlink Packet Delay Budget (PDB).

Exemplary, demand information includes at least one of:

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

The embodiment of the disclosure provides an information processing method, which is executed by a NEF and comprises the following steps: and receiving the requirement information sent by the AF.

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

Transmitting the demand information to the PCF;

Illustratively, the NEF receives the requirement information sent by the AF and sends the requirement information to the PCF. Or the NEF receives the requirement information sent by the AF and sends the requirement information to TSCTSF; TSCTSF sends the demand information to the PCF.

Receiving requirement information sent by AF;

And receiving the requirement information sent by the NEF.

An embodiment of the present disclosure provides an information processing method, performed by TSCTSF, including: and receiving the requirement information sent by the AF or the NEF.

An embodiment of the present disclosure provides an information processing method, performed by TSCTSF, including: and sending the requirement information to the PCF.

Illustratively, TSCTSF receives the requirement information sent by the AF and sends the requirement information to the PCF. Or AF sends the demand information to NEF; TSCTSF receives the requirement information sent by the NEF, and sends the requirement information to the PCF.

The embodiment of the disclosure provides an information processing method, which is executed by a NEF and comprises the following steps:

and sending subscription notification to the AF.

The above embodiments may be specifically referred to the description of the AF side and/or the PCF side, and will not be described herein.

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

Example one

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

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

Illustratively, the AF request may be an AF session resource request; AF creates an AF request through Nnef _ AFsessionWithQoS _Create request; the AF carries requirement information in the AF request, where the requirement information is used to indicate the requirement of bidirectional delay of the data flow of the XRM service. The AF request may be the first request in the above-described embodiments. Here, the bidirectional delay may be, but is not limited to: uplink delay and downlink delay, or round trip bi-directional delay. The demand information may include, but is not limited to, at least one of:

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

a demand value for upstream and/or downstream delay (or PDB);

the uplink and/or downlink delay (or PDB) accounts for the proportion of RTT (e.g., 40% uplink, 50% uplink, 70% downlink);

The ratio threshold of the uplink and/or downlink delay (or PDB) to the RTT bidirectional delay (for example, the ratio threshold may be not lower than 40%, not higher than 40%, equal to 30% or 50%, between 30 and 50%);

An upstream and/or downstream delay (or PDB) profile (e.g., a plurality of sets of upstream and/or downstream delay demand values, optionally including priorities of the upstream and/or downstream delays).

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

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

Step S802: the NEF grants the AF request;

For example, if the AF is an untrusted AF, an AF request sent by the AF may be provided to the PCF by the NEF. Optionally, the NEF performs the correlation mapping, including: mapping of identification XRM traffic (e.g., AF-Service-Identifier) to DNN and S-NSSAI, mapping of external application identification to Core Network (CN); and Unified DATA MANAGEMENT, UDM, mapping the external UE identity to the in-CN UE identity (e.g., SUPI), and performing external to internal mapping of XRM service group identities according to the UDM subscription.

Step S803: the NEF sends an AF request to the PCF;

Step S804: the PCF determines a preset rule and/or preset information based on the requirement information;

for example, the predetermined information and/or the predetermined rule may be a Policy decision (Policy decision).

Illustratively, the PCF divides the value of the bi-directional delay (e.g., RT LATENCY) into UL PDB (i.e., uplink delay) and DL PDB (i.e., downlink delay) based on the demand information; the 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 the bi-directional delay.

Illustratively, the PCF may monitor the UL delay of the UL QoS flow and the DL delay of the DL QoS flow separately to track the bi-directional delay (by utilizing existing QoS monitoring methods in the communication protocol).

Illustratively, if the PCF divides the bi-directional delay into UL PDB and DL PDB, then the data flow generates two PCC rules; one PCC rule is used for the data flow of the UL, and the other PCC rule is used for the data flow of the DL; and allocates corresponding 5QI for UL PDB and DL PDB, respectively. Here, the two PCC rules should also have an associated QoS monitoring policy to enable tracking of bi-directional latency; this may enable UL PDBs or DL PDBs to be tracked independently. Based on the monitoring results of the QoS monitoring policy monitoring, the PCF may adjust the UL PDB and DL PDB to better accommodate the new situation.

Illustratively, the PCF generates or updates PCC rules for the data flows of the corresponding XRM services based on the demand information; and/or, the PCF divides the bi-directional delay into UL PDB and DL PDB based on the demand information; and/or, the PCF allocates 5QI for the corresponding UL PDB and/or DL PDB based on the demand information; the PCF determines UL PDB and DL PDB based on the demand information and the local configuration information; and/or, the PCF stores and updates a profile of the XRM service, the profile comprising: UL PDB and/or DL PDB, PCC rules, and/or 5QI allocated for UL PDB and/or DL PDB, etc.

Illustratively, the PCF triggers Npcf _ SMPolicyControl _ UpdateNotify to update policy information for the SMF corresponding PDU session, including PCC rules and QoS policies determined by the PCF. The Npcf _ SMPolicyControl _ UpdateNotify may be an update request in the above embodiment.

Illustratively, the AF requests provide demand information that may affect QoS control at the SDF level (e.g., affect QoS grants or QoS updates for a particular SDF), or QoS control at the QoS flow level (e.g., affect QoS grants or QoS updates for all SDFs within a QoS flow).

Illustratively, the PCF performs QoS authorization and QoS updating for the corresponding SDF level based on the requirement information provided by the AF request (e.g., an indication of whether the uplink and downlink delays (or PDBs) are the same and/or a requirement value of the uplink and downlink delays (or PDBs)). Or the PCF performs QoS authorization and QoS update at the corresponding SDF level based on the demand information (e.g., the proportion of upstream or downstream delays to RTT bi-directional delays) and the local configuration information (e.g., operator policy and/or default configuration information). Or the PCF performs QoS authorization and QoS update of the corresponding SDF level based on the demand information (e.g., a proportional threshold of the uplink or downlink delay to the RTT bi-directional delay). Or the PCF performs QoS authorization and QoS updating of the corresponding SDF level based on the configuration file of the uplink or downlink delay (e.g., multiple sets of demand values for the uplink and/or downlink delay, optionally including priorities of the uplink and/or downlink delay). Or the PCF may perform QoS authorization and QoS update of the corresponding SDF level based on the result of the authorization or failure of the requested QoS.

Illustratively, the AF provides the requirement information to the PCF, which may be directly sent to the AF or indirectly sent to the AF. Wherein the indirect transmission includes one of: sending to PCF through NEF; or sent to the PCF via TSCTSF; or to the PCF via NEF and TSCTSF (where AF sends the demand information to NEF, NEF sends the demand information to TSCTSF, which sends the demand information to PCF).

Step S805: the PCF sends an authorization response to the NEF;

Illustratively, 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: the NEF sends an authorization response to the AF;

Illustratively, the authorization response may be Nnef _ AFsessionWithQoS _create response; the authorization response may be used to indicate whether the AF request is authorized.

Step S807: the PCF sends an update request to the SMF;

Illustratively, the update request may be 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 (or alternatively, the RAN device).

Step S808: the SMF sends an update response to the PCF;

The update response may be SM Policy Association Modification Response, for example.

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

Illustratively, the N4session modification request may be N4Session Modification Request; the N4session modification request includes (QoS monitoring configuration).

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

illustratively, after the UPF receives the QoS monitoring configuration, measurement and reporting are enabled; the UPF responds to the SMF.

Step S811: interaction N1N2 information between AMF and SMF;

Illustratively, the AMF receives a session modification request sent by the SMF and invokes Namf _communication_N1N2 messages based on the session modification request; the Namf _communication_n1n2 message includes a PDU session ID, QFI(s), a QoS profile, a QoS monitoring configuration, and/or an N1SM container (container).

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

Illustratively, 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 the RAN device receives the QoS monitoring configuration, measurement and reporting is enabled (e.g., the RAN device measures UL and DL delays and takes the sum of the UL and DL delays as a bi-directional delay).

Step S813: setting resources between RAN equipment and UE; this step S813 is optional.

Step S814: the RAN equipment sends a session determination message to the AMF;

illustratively, the session confirmation message is used to confirm the session modification request; the Session acknowledgement message may be an N2PDU Session ACK MESSAGE.

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

Illustratively, the AMF forwards the session determination message (including the N2SM message) received from the RAN device to the SMF through Nsmf _ PDUSession _ UpdateSMContext service operations.

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

Illustratively, the SMF responds to the session update request using Nsmf _ PDUSession _ UpdateSMContext Response (i.e., session update response).

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

Illustratively, the N4session modification request may be N4Session Modification Request.

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

Illustratively, the N4session modification response may be N4Session Modification Response.

Here, when the subsequent PCF receives the measurement and/or report based on the QoS monitoring configuration, the measurement and/or report is sent to the AF, and the modification of the related resources is triggered and/or the AF session update procedure or the AF session release procedure is triggered.

The above embodiments may be specifically referred to the AF side and/or PCF side and/or the first network function side, and will not be described herein.

Example two

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

step S900: UE registration policy association;

Illustratively, some or all of the UEs associated with XRM traffic or multi-modal data traffic have registered with the network; and selects the PCF to complete the AM session association. Here, the PCF subscribes to the change notification of the XRM service or the subscription information related to the multi-mode data service to the UDM according to the policy and QoS requirements of the XRM service.

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

The AF request may be, for example, the second request in the above embodiment; AF triggers Nnef _ XRMServiceParameter service to create AF requests; the AF carries requirement information in the AF request, where the requirement information is used to indicate the requirement of bidirectional delay of the data flow of the XRM service. Here, the bidirectional delay may be, but is not limited to: uplink delay and downlink delay, or round trip bi-directional delay. The demand information may include, but is not limited to, at least one of:

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

a demand value for upstream and/or downstream delay (or PDB);

Illustratively, the AF may also include at least one of the following: XRM service identification; a service description, wherein the service description includes a common identifier; service parameters; a UE identifier; a UE group identifier; and subscribing to events.

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

Step S902: AF sends AF request to NEF;

Illustratively, the NEF may also authorize the AF request. Here, the NEF execution correlation map is similar to the NEF execution correlation map in step S802 described above.

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

illustratively, the NEF stores information related to the traffic characteristics of the application data stream in the AF request; optionally, the NEF may refine the corresponding service characteristic related information (e.g. service parameters and/or service descriptions, etc.) according to the local configuration. Alternatively, the NEF may determine, for XRM traffic or multi-modal data traffic of a single UE or multiple UEs, based on operator policy and/or subscription information, etc., whether the requested traffic characteristics may be authorized and store the corresponding information in the UDR.

If multiple UEs are involved, the NEF transmits traffic characteristics related information to the PCFs, where corresponding grants are performed, and policy and rules decisions or updates. And the PCF stores corresponding information into the UDR according to the authorization result of the AF request.

If a plurality of UEs are involved, in the scenario of the plurality of UEs (i.e. group UEs), wherein subscription information of the UE group members is associated through XRM service identification or UE group identifier or common identification; wherein the group data of the group UE remains consistent (e.g., qoS of the traffic, characteristic parameters of access and data routing, etc. remain consistent).

Illustratively, the AF or PCF may be triggered by a NEF, subscription-related XRM traffic or multi-modal data traffic-related event, such as QoS monitoring reports (reports obtained based on QoS monitoring configuration), traffic QoS updates, UE relocation and/or PCF changes, etc.

Illustratively, the AF or PCF may obtain the corresponding notification by receiving a report of the NEF; subsequent updates of application requirements or QoS policies may be performed.

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

Illustratively, in step S900, the PCF performs subscription information update notification after UE registration; and because the AF requests updating the UDR subscription information, the subsequent flow is performed.

Step S905: PCF receives the subscription information update notice of UDR;

step S906: PCF sends UE strategy to UE;

the policy of the UE includes the predetermined information and/or the predetermined rule in the foregoing embodiments, and may be, for example, a PCC rule.

Step S907: the PCF sends the execution result to the NEF;

Illustratively, if the AF subscribes to the notification of the execution of the XRM service related policy, the PCF sends the policy related execution result to the NEF, so that the NEF sends the AF. Meanwhile, if the related subscription parameters are changed, the PCF is updated and changed to the UDR, and PCF of other UE related to the XRM service group is triggered to execute policy change and cooperative operation. The execution result may be a measurement and/or report in the above-described embodiments.

Step S908: the NEF sends the execution result to the AF.

Example three

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

Step S101: the UPF detects event triggering;

illustratively, the UPF will trigger a report when a measurement is detected and/or an event is reached (e.g., trigger a report when a threshold is reached or a period timer expires); the UPF triggers Nupf _ EventExposure _notify message.

Step S102: the UPF sends subscription notification to the NEF;

Illustratively, the subscription notification includes information about the measured bi-directional delay; the subscription notification may be a Nupf _ EventExposure _notify message.

Step S103: the NEF sends a subscription notification to the AF.

Example four

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

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

The NEF is configured to: receiving the requirement information sent by the AF, and sending the requirement information to the PCF or TSCTSF;

Or alternatively

TSCTSCF are configured to: and receiving the requirement information sent by the AF or the NEF, and sending the requirement information to the PCF.

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

As shown in fig. 11, an embodiment of the present disclosure provides an information processing apparatus including:

the first sending module 51 is configured to send requirement information, where the requirement information is used to indicate a requirement of bidirectional delay of a data stream of the XRM service.

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

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

An embodiment of the present disclosure provides an information processing apparatus including: the first transmitting module 51 is configured to perform one of:

Transmitting the demand information to the PCF;

in the AF conversation request flow, sending demand information;

in the AF conversation updating flow, sending demand information;

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

PCC rules;

QoS policies;

And/or the number of the groups of groups,

The predetermined information includes at least one of:

At least one value of the uplink time delay;

at least one value of the downlink delay;

An embodiment of the present disclosure provides an information processing apparatus including: the first sending module 51 is configured to send a first request in the AF session request flow, where the first request includes the requirement information.

UE address information;

A UE identifier for indicating a UE associated with the XRM service;

a flow description;

DNN；

S-NSSAI；

QoS parameters.

An embodiment of the present disclosure provides an information processing apparatus including: the first sending module 51 is configured to send a second request in the service specific parameter providing procedure, where the second request includes the requirement information.

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

XRM service identification;

Service parameters;

A UE identifier for indicating a UE associated with the XRM service;

subscription events.

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

An embodiment of the present disclosure provides an information processing apparatus including: a first receiving module configured to perform one of:

Receiving a subscription notification sent by UPF;

As shown in fig. 12, there is provided an information processing apparatus including:

the second receiving module 61 is configured to receive the requirement information, where the requirement information is used to indicate a requirement of bidirectional delay of the data stream of the XRM service.

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

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

The configuration file is used for indicating the requirement value of the uplink delay and/or the requirement value of the downlink delay in at least one set of bidirectional delays, or the configuration file is used for indicating: at least one set of the requirement value of the uplink delay and the priority indicating information of the uplink delay in the bidirectional delay, and/or the requirement value of the downlink delay and the priority indicating information of the downlink delay.

An embodiment of the present disclosure provides an information processing apparatus including: the second receiving module 61 is configured to perform one of the following:

Receiving AF sending requirement information;

in the AF conversation request flow, receiving demand information;

in the AF conversation updating process, receiving demand information;

receiving demand information in a service specific parameter providing process;

An embodiment of the present disclosure provides an information processing apparatus including: a first processing module; a first processing module configured to perform at least one of:

the predetermined information is determined based on the demand information.

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

An embodiment of the present disclosure provides an information processing apparatus including: a first processing module configured to perform at least one of:

An embodiment of the present disclosure provides an information processing apparatus including: a first processing module configured to perform one of:

An embodiment of the present disclosure provides an information processing apparatus including: the second receiving module 61 is configured to receive a first request in an AF session request flow, where the first request includes requirement information.

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

UE address information;

A UE identifier for indicating a UE associated with the XRM service;

a flow description;

DNN；

S-NSSAI；

QoS parameters.

An embodiment of the present disclosure provides an information processing apparatus including: the second receiving module 61 is configured to receive a second request in the service specific parameter providing procedure, wherein the second request includes the requirement information.

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

XRM service identification;

Service parameters;

A UE identifier for indicating a UE associated with the XRM service;

subscription events.

As shown in fig. 13, an embodiment of the present disclosure provides an information processing apparatus including:

The third receiving module 71 is configured to receive the requirement information, where the requirement information is used to indicate a requirement of bidirectional delay of the data stream of the XRM service.

The information processing apparatus provided by 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 requirement information sent by the AF.

An embodiment of the present disclosure provides an information processing apparatus including: the third receiving module 71 is configured to receive the requirement information sent by the AF.

An embodiment of the present disclosure provides an information processing apparatus including: a third transmission module; a third transmission module configured to perform one of:

Transmitting the demand information to the PCF;

An embodiment of the present disclosure provides an information processing apparatus including:

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

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

Receiving requirement information sent by AF;

And receiving the requirement information sent by the NEF.

An embodiment of the present disclosure provides an information processing apparatus including: the third receiving module 71 is configured to perform one of:

Receiving requirement information sent by AF;

And receiving the requirement information sent by the NEF.

An embodiment of the present disclosure provides an information processing apparatus including: and the third sending module is configured to send the requirement information to the PCF.

It should be noted that, as will be understood by those skilled in the art, the apparatus provided in the embodiments of the present disclosure may be implemented separately or together with some apparatuses in the embodiments of the present disclosure or some apparatuses in the related art.

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

The embodiment of the disclosure provides a communication device, comprising:

A 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, TSCTSF.

The processor may include, among other things, various types of storage media, which are non-transitory computer storage media capable of continuing to memorize information stored thereon after a power failure of the user device.

The processor may be coupled to the memory via a bus or the like for reading an executable program stored on the memory, for example, at least one of the methods shown in fig. 2-10.

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

The specific manner in which the respective modules perform the operations in relation to the apparatus or storage medium of the above-described embodiments has been described in detail in relation to the embodiments of the method, and will not be described in detail herein.

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

Referring to fig. 14, 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 overall operation of the user device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate 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 at the user device 800. Examples of such data include instructions for any application or method operating on the user device 800, contact data, phonebook data, messages, pictures, video, and the like. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices 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 or optical disk.

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

The multimedia component 808 includes a screen between the user device 800 and the user that provides an output interface. 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 a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also 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. The front camera and/or the rear camera may receive external multimedia data when the user device 800 is in an operation mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

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

The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects of the user device 800. For example, the sensor assembly 814 may detect an on/off state of the device 800, a relative positioning of the components, such as a display and keypad of the user device 800, the sensor assembly 814 may also detect a change in position of the user device 800 or a component of the user device 800, the presence or absence of a user's contact with the user device 800, an orientation or acceleration/deceleration of the user device 800, and a change in temperature 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 gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 816 is configured to facilitate communication between the user device 800 and other devices, either in a wired or wireless manner. The user device 800 may access a wireless network based on a communication standard, such as WiFi,4G or 5G, or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may 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 elements for executing the methods described above.

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

As shown in fig. 15, an embodiment of the present disclosure shows a structure of a base station. For example, base station 900 may be provided as a network-side device. Referring to fig. 15, base station 900 includes a processing component 922 that further includes one or more processors and memory resources represented by memory 932 for storing instructions, such as applications, executable by processing component 922. The application programs stored in memory 932 may include one or more modules that each correspond to a set of instructions. Further, processing component 922 is configured to execute instructions to perform any of the methods described above as applied at the base station.

Base station 900 may also include a power component 926 configured to perform power management for base station 900, a wired or wireless network interface 950 configured to connect base station 900 to a network, and an input output (I/O) interface 958. The base station 900 may operate based on an operating system stored in memory 932, such as Windows Server TM, mac OS XTM, unixTM, linuxTM, freeBSDTM, or the like.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected 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 executed by an application function AF, comprising:

And sending requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of a data stream of the multimedia augmented reality XRM service.
The method of claim 1, wherein the demand information comprises at least one of:

at least one demand value for uplink delay;

At least one demand value for downstream delay;

the first indication information is used for indicating the proportion of at least one uplink time delay to the bidirectional time delay and/or the proportion of at least one downlink time delay to the bidirectional time delay;

The second indication information is used for indicating a proportion threshold value of at least one uplink time delay to the bidirectional time delay and/or a proportion threshold value of at least one downlink time delay to the bidirectional time delay;

The third indication information is used for indicating whether the uplink time delay and the downlink time delay in at least one set of bidirectional time delay are the same or not;

Fourth indication information, wherein the fourth indication information is used for indicating that the bidirectional delay needs to be considered for the data flow of the XRM service;

Priority indication information, wherein the priority indication information is used for indicating the priority of the uplink time delay and/or indicating the priority of the downlink time delay;

A configuration file, wherein the configuration file is used for indicating a requirement value of an uplink delay and/or a requirement value of a downlink delay in at least one set of bidirectional delays, or the configuration file is used for indicating: at least one set of requirement value of uplink delay and priority indication information of the uplink delay in the bidirectional delay, and/or requirement value of downlink delay and priority indication information of the downlink delay.
The method according to claim 1 or 2, wherein the transmission requirement information comprises one of:

Sending the requirement information to a policy control function PCF;

transmitting the requirement information to a network opening function (NEF), wherein the requirement information is used for the NEF to transmit to a time sensitive communication and time synchronization function TSCTSF or the PCF;

and sending the requirement information to the TSCTSF, wherein the requirement information is used for sending the TSCTSF to the PCF.
The method according to claim 1 or 2, wherein the transmission requirement information comprises one of:

in the AF session request flow, the requirement information is sent;

In the AF conversation updating flow, the requirement information is sent;

in a service specific parameter providing process, sending the requirement information;

And in the process of setting the strategy for the subsequent AF session, the requirement information is sent.
The method of any of claims 1 to 4, wherein the demand information is used by the PCF to determine predetermined rules and/or to determine predetermined information.
The method of claim 5, wherein,

The predetermined rule includes at least one of:

Policy and charging control, PCC, rules;

Quality of service QoS policies;

And/or the number of the groups of groups,

The predetermined information includes at least one of:

At least one value of the uplink time delay;

at least one value of the downlink delay;

And a QoS identifier, wherein the QoS identifier is used to indicate at least one QoS parameter.
The method of claim 4, wherein the sending the requirement information in the AF session request flow includes:

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

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

UE address information;

A UE identifier for indicating a UE associated with the XRM service;

An application identifier, wherein the application identification information is used for indicating the XRM service;

a flow description;

A data network name DNN;

network slice selection support information S-NSSAI;

QoS parameters.
The method of claim 4, wherein the transmitting the demand information in the service-specific parameter providing process includes:

and in the service specific parameter providing process, sending a second request, wherein the second request comprises the requirement information.
The method of claim 9, wherein the second request further comprises at least one of:

XRM service identification;

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

Service parameters;

A UE identifier for indicating a UE associated with the XRM service;

a UE group identifier for indicating a group of UEs or a plurality of UEs associated with the XRM service;

subscription 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 demand information.
The method of claim 11, wherein the receiving a subscription notification comprises one of:

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

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

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

and receiving requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of a data stream of the multimedia augmented reality XRM service.
The method of claim 13, wherein the demand information comprises at least one of:

at least one demand value for uplink delay;

At least one demand value for downstream delay;

the first indication information is used for indicating the proportion of at least one uplink time delay to the bidirectional time delay and/or the proportion of at least one downlink time delay to the bidirectional time delay;

The second indication information is used for indicating a proportion threshold value of at least one uplink time delay to the bidirectional time delay and/or a proportion threshold value of at least one downlink time delay to the bidirectional time delay;

The third indication information is used for indicating whether at least one set of bidirectional delay uplink delay and at least one set of bidirectional delay downlink delay are the same;

Fourth indication information, wherein the fourth indication information is used for indicating that the bidirectional delay needs to be considered for the data flow of the XRM service;

Priority indication information, wherein the priority indication information is used for indicating the priority of the uplink time delay and/or indicating the priority of the downlink time delay;

A configuration file, wherein the configuration file is used for indicating a requirement value of an uplink delay and/or a requirement value of a downlink delay in at least one set of bidirectional delays, or the configuration file is used for indicating: at least one set of requirement value of uplink delay and priority indication information of the uplink delay in the bidirectional delay, and/or requirement value of downlink delay and priority indication information of the downlink delay.
The method of claim 13 or 14, wherein the receiving demand information comprises one of:

Receiving an application function AF to send the requirement information;

Receiving the requirement information sent by a network opening function (NEF), wherein the requirement information is received by the NEF from the AF;

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

in the AF session request flow, receiving the demand information;

in the AF conversation updating process, receiving the requirement information;

receiving the demand information in a service specific parameter providing process;

And in the process of setting the strategy for the subsequent AF session, receiving the requirement information.
The method according to any one of claims 13 to 16, wherein the method comprises at least one of:

determining a predetermined rule of the data stream based on the demand information;

and determining predetermined information based on the demand information.
The method of claim 17, wherein the predetermined rule comprises: policy and charging control PCC rules and/or QoS policies.
The method of claim 18, wherein the method comprises:

sending an update request to a session management function SMF, wherein the update request comprises:

The PCC rules and/or the QoS policies;

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

determining the value of at least one uplink time delay and/or the value of at least one downlink time delay based on the demand information;

Determining the value of at least one uplink time delay and/or the value of at least one downlink time delay 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 requirement information, determining a QoS identification of the data flow, wherein the QoS identification is used for indicating at least one QoS parameter.
A method according to any one of claims 13 to 16, wherein the method comprises one of:

Determining a service data flow SDF level or QoS control of a QoS flow level based on the requirement information; wherein the QoS control includes: qoS authorization and/or OoS update;

Determining the QoS control of the SDF level or QoS level based on the demand information and local configuration information; wherein the local configuration information includes: operator policy, default configuration information, and/or subscription information.
The method of claim 16, wherein the receiving the requirement information in the AF session request flow includes:

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

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

UE address information;

A UE identifier for indicating a UE associated with the XRM service;

An application identifier, wherein the application identification information is used for indicating the XRM service;

a flow description;

A data network name DNN;

network slice selection support information S-NSSAI;

QoS parameters.
The method of claim 16, wherein the receiving the demand information in a service specific parameter providing process 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:

XRM service identification;

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

Service parameters;

A UE identifier for indicating a UE associated with the XRM service;

a UE group identifier for indicating a group of UEs or a plurality of UEs associated with the XRM service;

subscription events.
An information processing method, wherein the method is performed by a first network function and comprises:

and receiving requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of a data stream of the multimedia augmented reality XRM service.
The method of claim 26, wherein the first network function is a network open function, NEF; the receiving the demand information includes:

And receiving the requirement information sent by the application function AF.
The method of claim 27, wherein the method comprises one of:

Sending the requirement information to a policy control function PCF;

The demand information is sent to a time sensitive communication and time synchronization function TSCTSF, where the demand information is used for the TSCTSF to be sent 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 comprises a report determined based on the requirement information;

And sending the subscription notification to the AF.
The method of claim 26, wherein the first network function is a time sensitive communication and time synchronization function TSCTSF; the reception demand information includes one of:

receiving the requirement information sent by the AF;

And receiving the requirement information sent by the NEF.
The method of claim 30, wherein the method comprises:

And sending the requirement information to the PCF.
An information processing apparatus, comprising:

And the first sending module is configured to send requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of a data stream of the multimedia augmented reality XRM service.
An information processing apparatus, comprising:

And the second receiving module is configured to receive requirement information, wherein the requirement information is used for indicating the requirement of bidirectional delay of a data stream of the multimedia augmented reality XRM service.
An information processing system, comprising: AF. A first network function and a PCF;

The AF is configured to: transmitting demand information to the PCF or to the first network function, wherein the demand information is used for indicating a demand of bidirectional delay of a data stream of a multimedia augmented reality XRM service;

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

A processor;

A memory for storing the processor-executable instructions;

Wherein the processor is configured to: for implementing the information processing method of any one of claims 1 to 12, or of claims 13 to 25, or of claims 26 to 31 when said executable instructions are executed.
A computer storage medium storing a computer executable program which when executed by a processor implements the information processing method of any one of claims 1 to 12, or claims 13 to 25, or claims 26 to 31.