Information transmission method and device, communication equipment and storage medium

Abstract

The embodiment of the invention relates to an information transmission method and device, communication equipment and a storage medium, a policy control function (PCF) determines and sends an association identifier of a predetermined service, and the association identifier is used for associating a transmission delay parameter of uplink transmission and a transmission delay parameter of downlink transmission of a predetermined service data stream.

Description

[0001] This disclosure is a divisional application of Chinese application filed on January 9, 2023, with application number 202380007916.7 and title "Information Transmission Method, Apparatus, Communication Equipment and Storage Medium". Technical Field

[0002] This application relates to, but is not limited to, the field of wireless communication technology, and particularly to information transmission methods, apparatus, communication devices, and storage media. Background Technology

[0003] Mobile media services, extended reality (XR) services such as cloud-based augmented reality (AR) / virtual reality (VR), cloud gaming, and video-based remote control of machines or drones are expected to contribute increasingly higher traffic to 5G networks. XR services involve multimodal data streams. Multimodal data describes data input from the same device or different devices (including sensors) for the same service / application, which may be output to one or more destination device terminals. The data streams in multimodal data often have some or even strong correlation, such as the synchronization of audio and video streams, or the synchronization of haptic and visual senses. Summary of the Invention

[0004] In view of the above, embodiments of this disclosure provide an information transmission method, apparatus, communication device, and storage medium.

[0005] According to a first aspect of the present disclosure, an information transmission method is provided, wherein the method is applied to a policy control function (PCF), comprising:

[0006] The association identifier of the pre-defined service is determined and sent, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the pre-defined service data stream.

[0007] In one embodiment, the association identifier is sent by the PCF to the Session Management Function (SMF), and by the SMF to at least one of the following:

[0008] Access network equipment;

[0009] User Plane Function (UPF).

[0010] In one embodiment, the association identifier is indicated by the policy control and billing PCC rules associated with the pre-defined service.

[0011] In one embodiment, the method further includes:

[0012] Receive the uplink QoS latency monitoring report and the downlink QoS latency monitoring report, wherein the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using the association identifier;

[0013] Based on the QoS latency monitoring reports of the uplink and downlink transmissions, update the Policy Control and Charging (PCC) rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service.

[0014] In one embodiment, updating the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service based on the QoS latency monitoring reports of the uplink and downlink transmissions includes:

[0015] Send the uplink QoS latency monitoring report and the downlink QoS latency monitoring report to the application function (AF) associated with the predetermined service;

[0016] Receive the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission from the AF, and send AF session update information;

[0017] Based on the AF session update information, update the PCC rules for the uplink transmission of the scheduled service and / or the PCC rules for the downlink transmission of the scheduled service.

[0018] In one embodiment, receiving the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission includes at least one of the following:

[0019] Receive the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the UPF;

[0020] The system receives the QoS latency monitoring reports for the uplink and downlink transmissions sent by the access network device through the UPF.

[0021] In one embodiment, the method further includes:

[0022] The application function (AF) associated with the predetermined service receives AF session update information sent in response to the uplink QoS latency monitoring report and the downlink QoS latency monitoring report; wherein the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent to the AF by the UPF;

[0023] Based on the AF session update information, update the PCC rules for the uplink transmission of the scheduled service and / or the PCC rules for the downlink transmission of the scheduled service.

[0024] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the uplink subscription event triggering conditions, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0025] and / or

[0026] The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network equipment after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the downlink subscription event triggering conditions, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

[0027] In one embodiment, updating the PCC rules for the predetermined service uplink transmission includes: updating the packet unit delay budget (PDB) parameter and / or packet unit set delay budget (PSDB) parameter in the PCC rules for the predetermined service uplink transmission.

[0028] The step of updating the PCC rules for the scheduled downlink transmission of the service includes updating the PDB parameters and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of the service.

[0029] In one embodiment, determining the associated identifier of the pre-booked service includes:

[0030] The association identifier is determined based on at least one of the following:

[0031] The transmission delay parameters for the bidirectional transmission of the predetermined service data stream;

[0032] The contract information associated with the pre-booked service;

[0033] The operator strategy associated with the pre-booked service.

[0034] In one embodiment, the method further includes: determining the transmission delay parameters of the uplink transmission of the data stream and / or the transmission delay parameters of the downlink transmission of the data stream based on the transmission delay parameters of the bidirectional transmission of the predetermined service data stream.

[0035] In one embodiment, the scheduled service includes at least one of the following:

[0036] Augmented Reality Multimedia XRM services;

[0037] Multimodal services.

[0038] According to a second aspect of the present disclosure, an information transmission method is provided, wherein the method is applied to an application function AF, comprising:

[0039] The transmission delay parameters for bidirectional transmission of a predetermined service are sent to the Policy Control Function (PCF). These bidirectional transmission delay parameters are used by the PCF to determine the association identifier of the predetermined service, and are used to associate the transmission delay parameters for uplink transmission and downlink transmission of the predetermined service data stream.

[0040] In one embodiment, the association identifier is sent by the PCF to at least one of the following via the Session Management Function (SMF): the access network device; and the User Plane Function (UPF).

[0041] In one embodiment, the association identifier is carried in the policy control and billing PCC rules of the predetermined service association sent by the PCF to the SMF.

[0042] In one embodiment, the method further includes:

[0043] Receive the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the User Plane Function (UPF) or PCF.

[0044] In one embodiment, the method further includes:

[0045] Based at least on the QoS latency monitoring reports of the uplink transmission and the downlink transmission, it is determined whether to send AF session update information to the PCF.

[0046] In one embodiment, the AF session update information is used by the PCF to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service.

[0047] In one embodiment, the AF session update information is used by the PCF to update the Packet Unit Delay Budget (PDB) parameter and / or Packet Unit Set Delay Budget (PSDB) parameter in the PCC rules for the uplink transmission of the predetermined service, and / or to update the PDB parameter and / or PSDB parameter in the PCC rules for the downlink transmission of the predetermined service.

[0048] In one embodiment, receiving the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the UPF includes: receiving the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the UPF through the NEF.

[0049] The step of receiving the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the PCF includes: receiving the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the PCF through the NEF.

[0050] In one embodiment, the transmission delay parameters of the bidirectional transmission of the predetermined service data stream are used by the PCF to determine the transmission delay parameters of the uplink transmission of the data stream and / or the transmission delay parameters of the downlink transmission of the data stream.

[0051] In one embodiment, the transmission delay parameters for sending the predetermined bidirectional service transmission to the PCF include at least one of the following:

[0052] The transmission delay parameters for the bidirectional transmission of the predetermined service are sent to the PCF via the Network Exposure Function (NEF).

[0053] The transmission delay parameters of the predetermined service bidirectional transmission are sent to the PCF through the Time Sensitive Communication Time Synchronization Function (TSCTS).

[0054] The transmission delay parameters for the bidirectional transmission of the predetermined service are sent from the NEF to the PCF via the TSCTSF.

[0055] According to a third aspect of the present disclosure, an information transmission method is provided, wherein the method is applied to a User Plane Function (UPF) and includes:

[0056] Receive the association identifier of the pre-ordered service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the pre-ordered service data stream.

[0057] In one embodiment, the association identifier is a policy control and billing PCC rule indication of the predetermined service association sent by the policy control function (PCF) to the session management function (SMF).

[0058] In one embodiment, the method further includes at least one of the following:

[0059] Send the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission to the PCF;

[0060] Send the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission to the AF associated with the predetermined service;

[0061] The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using the association identifier.

[0062] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the first uplink subscription event triggering condition, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0063] and / or

[0064] The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the triggering condition of the first downlink subscription event, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

[0065] According to a fourth aspect of the present disclosure, an information transmission method is provided, wherein the method is applied to an access network device and includes:

[0066] Receive the association identifier of the pre-ordered service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the pre-ordered service data stream.

[0067] In one embodiment, the association identifier is indicated by the policy control and billing PCC rules carried by the policy control function (PCF) and sent to the session management function (SMF) of the predetermined service association.

[0068] In one embodiment, the method further includes:

[0069] The UPF sends the uplink QoS latency monitoring report and the downlink QoS latency monitoring report to the PCF, wherein the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using the association identifier.

[0070] In one embodiment, the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are used by the PCF to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service.

[0071] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the triggering condition of the second uplink subscription event, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0072] And / or,

[0073] The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the access network device after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the triggering conditions of the second downlink subscription event, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

[0074] In one embodiment, updating the PCC rules for the predetermined service uplink transmission includes: updating the packet unit delay budget (PDB) parameter and / or packet unit set delay budget (PSDB) parameter in the PCC rules for the predetermined service uplink transmission.

[0075] The step of updating the PCC rules for the scheduled downlink transmission of the service includes updating the PDB parameters and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of the service.

[0076] According to a fifth aspect of the present disclosure, an information transmission apparatus is provided, wherein an apparatus disposed in a policy control function (PCF) includes:

[0077] The processing module is configured to determine and send the association identifier of the pre-defined service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the pre-defined service data stream.

[0078] In one embodiment, the association identifier is sent by the PCF to the Session Management Function (SMF), and by the SMF to at least one of the following:

[0079] Access network equipment;

[0080] User-facing features (UPF).

[0081] In one embodiment, the association identifier is indicated by the policy control and billing PCC rules associated with the pre-defined service.

[0082] In one embodiment, the apparatus further includes:

[0083] The transceiver module is configured to receive the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission, wherein the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission are associated using the association identifier;

[0084] The processing module is further configured to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service based on the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission.

[0085] In one embodiment, the transceiver module is further configured to send the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report to the AF associated with the predetermined service.

[0086] The transceiver module is further configured to receive AF session update information sent by the AF in response to the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission;

[0087] The processing module is further configured to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service based on the AF session update information.

[0088] In one embodiment, the transceiver module is specifically configured to include at least one of the following:

[0089] Receive the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the UPF;

[0090] The system receives the QoS latency monitoring reports for the uplink and downlink transmissions sent by the access network device through the UPF.

[0091] In one embodiment, the apparatus further includes:

[0092] The transceiver module is configured to receive AF session update information sent by the application function AF associated with the predetermined service in response to the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report; wherein the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent to the AF by the UPF;

[0093] The processing module is further configured to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service based on the AF session update information.

[0094] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the uplink subscription event triggering conditions, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0095] and / or

[0096] The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network equipment after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the downlink subscription event triggering conditions, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

[0097] In one embodiment, updating the PCC rules for the predetermined service uplink transmission includes: updating the packet unit delay budget (PDB) parameter and / or packet unit set delay budget (PSDB) parameter in the PCC rules for the predetermined service uplink transmission.

[0098] The step of updating the PCC rules for the scheduled downlink transmission of the service includes updating the PDB parameters and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of the service.

[0099] In one embodiment, determining the associated identifier of the pre-booked service includes:

[0100] The association identifier is determined based on at least one of the following:

[0101] The transmission delay parameters for the bidirectional transmission of the predetermined service data stream;

[0102] The contract information associated with the pre-booked service;

[0103] The operator strategy associated with the pre-booked service.

[0104] In one embodiment, the processing module is further configured to:

[0105] Based on the transmission delay parameters of the bidirectional transmission of the predetermined service data stream, determine the transmission delay parameters of the uplink transmission of the data stream and / or the transmission delay parameters of the downlink transmission of the data stream.

[0106] In one embodiment, the scheduled service includes at least one of the following:

[0107] Augmented Reality Multimedia XRM services;

[0108] Multimodal services. According to a sixth aspect of the present disclosure, an information transmission apparatus is provided, wherein an application function (AF) is configured, comprising:

[0109] The transceiver module is configured to send transmission delay parameters for bidirectional transmission of a predetermined service to the policy control function (PCF). The bidirectional transmission delay parameters are used by the PCF to determine the association identifier of the predetermined service, and are used to associate the transmission delay parameters of the uplink transmission and the downlink transmission of the predetermined service data stream.

[0110] In one embodiment, the association identifier is sent by the PCF to at least one of the following via the Session Management Function (SMF): the access network device; and the User Plane Function (UPF).

[0111] In one embodiment, the association identifier is carried in the policy control and billing PCC rules of the predetermined service association sent by the PCF to the SMF.

[0112] In one embodiment, the transceiver module is further configured to receive the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the User Plane Function (UPF) or PCF.

[0113] In one embodiment, the apparatus further includes a processing module configured to:

[0114] Based at least on the QoS latency monitoring reports of the uplink transmission and the downlink transmission, it is determined whether to send AF session update information to the PCF.

[0115] In one embodiment, the AF session update information is used by the PCF to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service.

[0116] In one embodiment, the AF session update information is used by the PCF to update the Packet Unit Delay Budget (PDB) parameter and / or Packet Unit Set Delay Budget (PSDB) parameter in the PCC rules for the uplink transmission of the predetermined service, and / or to update the PDB parameter and / or PSDB parameter in the PCC rules for the downlink transmission of the predetermined service.

[0117] In one embodiment, the transceiver module is specifically configured to receive the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission sent by the UPF through the NEF.

[0118] and / or

[0119] The transceiver module is specifically configured to receive the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the PCF through the NEF.

[0120] In one embodiment, the transmission delay parameters of the bidirectional transmission of the predetermined service data stream are used by the PCF to determine the transmission delay parameters of the uplink transmission of the data stream and / or the transmission delay parameters of the downlink transmission of the data stream.

[0121] In one embodiment, the transceiver module is specifically configured to include at least one of the following:

[0122] The transmission delay parameters for the predetermined bidirectional transmission of the service are sent to the PCF via the NEF.

[0123] The transmission delay parameters for the predetermined bidirectional transmission of the service are sent to the PCF via the TSCTSF.

[0124] The transmission delay parameters for the bidirectional transmission of the predetermined service are sent from the NEF to the PCF via the TSCTSF.

[0125] According to a seventh aspect of the present disclosure, an information transmission apparatus is provided, wherein the apparatus is disposed in a User Plane Function (UPF) and includes:

[0126] The transceiver module is configured to receive the associated identifier of a pre-defined service, wherein the associated identifier is used to associate the transmission delay parameters of the uplink transmission and the downlink transmission of the pre-defined service data stream.

[0127] In one embodiment, the association identifier is a policy control and billing PCC rule indication of the predetermined service association sent by the policy control function (PCF) to the session management function (SMF).

[0128] In one embodiment, the transceiver module is further configured to include at least one of the following:

[0129] Send the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission to the PCF;

[0130] Send the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission to the AF associated with the predetermined service;

[0131] The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using the association identifier.

[0132] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the first uplink subscription event triggering condition, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0133] and / or

[0134] The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the triggering condition of the first downlink subscription event, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

[0135] According to an eighth aspect of the present disclosure, an information transmission apparatus is provided, wherein the apparatus is disposed in an access network device, comprising:

[0136] The transceiver module is configured to receive the associated identifier of a pre-defined service, wherein the associated identifier is used to associate the transmission delay parameters of the uplink transmission and the downlink transmission of the pre-defined service data stream.

[0137] In one embodiment, the association identifier is indicated by the policy control and billing PCC rules carried by the policy control function (PCF) and sent to the session management function (SMF) of the predetermined service association.

[0138] In one embodiment, the transceiver module is further configured to:

[0139] The UPF sends the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission to the PCF, wherein the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission are associated using the association identifier.

[0140] In one embodiment, the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are used by the PCF to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service.

[0141] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the triggering condition of the second uplink subscription event, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0142] And / or,

[0143] The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the access network device after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the triggering conditions of the second downlink subscription event, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

[0144] In one embodiment, updating the PCC rules for the predetermined service uplink transmission includes: updating the packet unit delay budget (PDB) parameter and / or packet unit set delay budget (PSDB) parameter in the PCC rules for the predetermined service uplink transmission.

[0145] The step of updating the PCC rules for the scheduled downlink transmission of the service includes updating the PDB parameters and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of the service.

[0146] According to a ninth aspect of the present disclosure, a communication device is provided, wherein the communication device includes:

[0147] processor;

[0148] Memory used to store the processor's executable instructions;

[0149] The processor is configured to implement the information transmission method described in the first, second, third, or fourth aspect when running the executable instructions.

[0150] According to a tenth aspect of the present disclosure, a computer storage medium is provided, wherein the computer storage medium stores a computer executable program, and the executable program, when executed by a processor, implements the information transmission method described in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0151] According to an eleventh aspect of the present disclosure, a core network device is provided, wherein the core network device includes: a policy control function (PCF) and a user plane function (UPF), wherein the PCF is used to execute the information transmission method described in the first aspect; and the UPF is used to execute the information transmission method described in the third aspect.

[0152] This disclosure provides an information transmission method, apparatus, communication device, and storage medium. The PCF determines and sends an association identifier for a predetermined service, wherein the association identifier is used to associate the uplink transmission delay parameters and downlink transmission delay parameters of the predetermined service data stream. The association identifier is used to associate the uplink and downlink transmission delay parameters. Core network elements and / or access network devices can determine the uplink and downlink transmission delay parameters based on the association identifier, performing coordinated processing of the uplink and downlink transmission delay parameters. This improves the coordination efficiency of the uplink and downlink transmission delay parameters, thereby meeting the bidirectional transmission delay requirements of the predetermined service and increasing the transmission success rate of the predetermined service.

[0153] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the embodiments of this disclosure. Attached Figure Description

[0154] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0155] Figure 1 This is a schematic diagram illustrating the structure of a wireless communication system according to an exemplary embodiment;

[0156] Figure 2 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0157] Figure 3 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0158] Figure 4 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0159] Figure 5 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0160] Figure 6 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0161] Figure 7 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0162] Figure 8 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0163] Figure 9 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0164] Figure 10 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0165] Figure 11 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0166] Figure 12 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0167] Figure 13 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0168] Figure 14 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0169] Figure 15 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0170] Figure 16 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0171] Figure 17 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0172] Figure 18 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0173] Figure 19 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0174] Figure 20 This is a flowchart illustrating an information transmission method according to an exemplary embodiment;

[0175] Figure 21 This is a schematic diagram of an information transmission structure according to an exemplary embodiment;

[0176] Figure 22 This is a schematic diagram of an information transmission structure according to an exemplary embodiment;

[0177] Figure 23 This is a schematic diagram of an information transmission structure according to an exemplary embodiment;

[0178] Figure 24 This is a schematic diagram of an information transmission structure according to an exemplary embodiment;

[0179] Figure 25 This is a block diagram illustrating a UE according to an exemplary embodiment;

[0180] Figure 26 This is a block diagram illustrating a base station according to an exemplary embodiment. Detailed Implementation

[0181] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of the present invention.

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

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

[0184] Please refer to Figure 1 This illustration shows a schematic diagram of the structure of a wireless communication system provided in an embodiment of this disclosure. Figure 1 As shown, the wireless communication system is a communication system based on cellular mobile communication technology. The wireless communication system may include: a number of terminals 11 and a number of base stations 12.

[0185] Terminal 11 can be a device that provides voice and / or data connectivity to a user. Terminal 11 can communicate with one or more core network functional nodes via a Radio Access Network (RAN). Terminal 11 can be an Internet of Things (IoT) terminal, such as a sensor device, a mobile phone (or "cellular" phone), or a computer with an IoT terminal. For example, it can be a fixed, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted device. Examples include a station (STA), subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user equipment (UE). Alternatively, Terminal 11 can also be a device on an unmanned aerial vehicle (UAV). Alternatively, Terminal 11 can also be a vehicle-mounted device, such as a vehicle computer with wireless communication capabilities, or a wireless communication device connected to an external vehicle computer. Alternatively, terminal 11 can also be a roadside device, such as a street light, traffic light, or other roadside device with wireless communication capabilities.

[0186] Base station 12 can be an access network device in a wireless communication system. This wireless communication system can be a fourth-generation mobile communication (4G) system, also known as a Long Term Evolution (LTE) system; or it can be a 5G system, also known as a New Radio (NR) system or a 5G NR system. Alternatively, it can be a next-generation system after 5G. In this case, the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network), or an MTC system.

[0187] In this embodiment, base station 12 can be an evolved NB (eNB) used in a 4G system. Alternatively, base station 12 can also be a gNB (gNB) using a centralized-distributed architecture in a 5G system. When base station 12 adopts a centralized-distributed architecture, it typically includes a central unit (CU) and at least two distributed units (DU). The central unit is equipped with a protocol stack of Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Media Access Control (MAC) layers; the distributed units are equipped with a physical (PHY) layer protocol stack. This disclosure does not limit the specific implementation of base station 12.

[0188] Base station 12 and terminal 11 can establish a wireless connection via a wireless air interface. In different implementations, the wireless air interface is a wireless air interface based on the fourth-generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard, such as a new air interface; or, the wireless air interface can also be a wireless air interface based on a next-generation mobile communication network technology standard based on 5G.

[0189] In some embodiments, terminals 11 can also establish E2E (End to End) connections. Examples include V2V (vehicle to vehicle), V2I (vehicle to Infrastructure), and V2P (vehicle to pedestrian) communication scenarios in vehicle-to-everything (V2X) communication.

[0190] In some embodiments, the wireless communication system described above may further include a network management device 13.

[0191] Several base stations 12 are connected to network management device 13. Network management device 13 can be a core network functional node in a wireless communication system. For example, it can be the Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, it can be other core network functional nodes, such as a Serving Gateway (SGW), Public Data Network Gateway (PGW), Policy and Charging Rules Function (PCRF), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Policy Control Function (PCF), Unified Data Management (UDM), User Plane Function (UPF), Network Exposure Function (NEF), Session Management Function (SMF), etc. The implementation of the network management device 13 is not limited in this embodiment.

[0192] To facilitate understanding by those skilled in the art, this disclosure provides multiple embodiments to clearly illustrate the technical solutions of the embodiments of this disclosure. Of course, those skilled in the art will understand that the multiple embodiments provided in this disclosure can be executed individually, or in combination with the methods of other embodiments in this disclosure, or individually or in combination with some methods in other related technologies; this disclosure does not limit these aspects.

[0193] The data flow of XRM services, the data flows between each other, and the network transmission requirements of these service data flows all share some common characteristics. Effective identification and utilization of these common characteristics will be more helpful for network and service transmission and control, as well as for service assurance and user experience.

[0194] Extended Reality Multi-Media (XRM) services require mobile communication systems (such as 5G mobile communication systems) to comprehensively consider the Quality of Service (QoS) characteristics of the relevant data streams. This includes considering factors such as the guaranteed flow bit rate (GBR) data stream, guaranteed flow bit rate (GFBR), PDU delay budget (PDB), default maximum data burst volume (MDBV), and PDU set delay budget (PSDB), ensuring that these parameters are simultaneously met and coordinated consistently. This involves ensuring consistent QoS authorization and execution across multiple XRM data streams from a single UE and multiple XRM data streams from multiple UEs. Therefore, coordinating uplink and downlink transmissions to meet bidirectional latency requirements is a crucial issue requiring further research.

[0195] When requesting QoS for XRM services, AF can provide PDB as a latency requirement, or provide a bidirectional request indication as an indication of whether bidirectional latency needs to be considered, for network authorization reference.

[0196] In actual business operations, latency is dynamically and continuously changing due to various factors in the network. Therefore, the real-time or near-real-time latency status of the network, as well as the real-time latency requirements of AF services, directly affect the QoS authorization of each data stream, and thus the success of 5GS XRM service functionality support. Currently, there is no perfect mechanism to combine network latency status and latency requirements to implement QoS authorization; that is, there is no corresponding technical solution to support PCF in reasonably authorizing the bidirectional latency requirements of XRM service data streams.

[0197] Therefore, how to adjust the latency parameters of XRM service data streams according to the network latency status to meet the transmission requirements of XRM services is an urgent problem to be solved.

[0198] like Figure 2 As shown, this exemplary embodiment provides an information transmission method that can be executed by a PCF, including:

[0199] Step 201: Determine and send the association identifier of the pre-ordered service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the downlink transmission of the pre-ordered service data stream.

[0200] In one embodiment, the reservation service includes at least one of the following:

[0201] Augmented Reality Multimedia XRM services;

[0202] Multimodal services.

[0203] XRM services can include multiple data streams with synchronization requirements for transmitting information in various media formats such as text, audio, and images.

[0204] Multimodal services can include multiple data streams of different modes that have synchronization requirements.

[0205] In one possible implementation, the associated identifier for sending the pre-ordered service includes at least one of the following:

[0206] Send the associated identifier of the pre-ordered service directly;

[0207] Send the associated identifier of the pre-booked service indirectly.

[0208] In one possible implementation, the associated identifier of the pre-booked service is sent directly, including: the PCF directly sends the associated identifier of the pre-booked service to the SMF.

[0209] In one possible implementation, the associated identifier of the pre-booked service is sent indirectly, including: the PCF sends the associated identifier of the pre-booked service to the UPF and / or access network equipment through the SMF.

[0210] In one possible implementation, the scheduled service can have a bidirectional data stream.

[0211] In one possible implementation, the association identifier may include any of the following: Correlation ID; Peer ID; Round Trip Group ID; Peer Indication; Common ID. The name of the association identifier is not limited here.

[0212] In one possible implementation, the associated identifier can be generated based on the common identifier, or the associated identifier can be obtained by mapping based on the common identifier.

[0213] In one possible implementation, the association identifier is associated with the transmission delay parameters of the uplink transmission of the predetermined service data stream; and the association identifier is associated with the transmission delay parameters of the downlink transmission of the predetermined service data stream. That is, the core network functional node or access network device can determine the transmission delay parameters of the uplink transmission and the downlink transmission of the predetermined service data stream through the association identifier.

[0214] Transmission delay parameters may include, but are not limited to, delay configuration parameters associated with data stream transmission.

[0215] The transmission delay parameter may include at least one of the following: transmission delay; PDB; PSDB. PDB and / or PSDB may belong to 5QI. PSDB defines the upper limit of the transmission delay of the PDU set between the N6 endpoint at the UE and UPF.

[0216] In one possible implementation, the PCF can determine the uplink transmission delay of the data stream and / or the uplink transmission delay of the data stream based on the transmission delay parameters of the bidirectional transmission of the predetermined service data stream. The bidirectional transmission delay parameters of the predetermined service data stream can be indicated to the PCF by the AF associated with the predetermined service.

[0217] In one possible implementation, the AF can send the transmission delay parameters for bidirectional transmission of the predetermined service data stream to the PCF via the NEF.

[0218] In one possible implementation, the bidirectional transmission delay parameter can characterize the maximum allowable transmission delay of a predetermined service data stream during uplink and downlink transmission.

[0219] In one possible implementation, the transmission delay of the uplink data stream and the sum of the uplink transmission delays of the data stream are less than or equal to the transmission delay of the bidirectional transmission of the predetermined service data stream.

[0220] In one possible implementation, the association identifier is associated with at least one of the following:

[0221] Transmission delay parameters of the uplink service data stream for the pre-booked service;

[0222] Transmission delay parameters for the downlink service data stream of the pre-booked service;

[0223] Transmission delay parameters for the QoS stream of the pre-booked service;

[0224] PCC associated with pre-booked business;

[0225] 5QI related to pre-booking business.

[0226] In one possible implementation, PCF can generate associated identifiers based on a predetermined strategy.

[0227] In one possible implementation, an association identifier can be associated with a pre-booked service, or an association identifier can be associated with a class of pre-booked services.

[0228] In one embodiment, determining the associated identifier of the pre-booked service includes:

[0229] The association identifier must be determined based on at least one of the following:

[0230] Transmission delay parameters for bidirectional transmission of the scheduled business data stream;

[0231] Contract information associated with the pre-booked service;

[0232] Carrier strategies associated with pre-booked services.

[0233] In one possible implementation, the requirements of the scheduled service for transmission delay parameters may include at least one of the following: transmission delay parameter requirements of the scheduled service for bidirectional transmission of the data stream; transmission delay parameter requirements of the scheduled service for uplink transmission of the data stream; and transmission delay parameter requirements of the scheduled service for downlink transmission of the data stream.

[0234] In one possible implementation, the PCF can determine the bidirectional transmission delay rules or 5QI updates that the network supports for the pre-defined services based on the transmission delay parameters (i.e., transmission delay parameter requirements), subscription information, or operator policies, and then generate an associated identifier.

[0235] In one possible implementation, the association identifier can be determined based on one or more of the transmission delay parameters of bidirectional transmission, the subscription information of the pre-ordered service association, and the operator policy of the pre-ordered service association.

[0236] For example, associated identifiers can be assigned based on carrier policies. Carrier policies contain the rules for assigning associated identifiers.

[0237] In related technologies, the uplink and downlink transmissions of the scheduled business data stream are independent of each other, and the transmission delay parameters of the uplink transmission are not correlated, making it impossible to achieve coordinated adjustment of the uplink transmission delay parameters.

[0238] The association identifier is used to associate the transmission delay parameters of uplink transmission and downlink transmission. Core network elements and / or access network devices can determine the transmission delay parameters of uplink transmission and downlink transmission based on the association identifier, and perform coordinated processing of the transmission delay parameters of uplink transmission and downlink transmission, thereby improving the coordination efficiency of the transmission delay parameters of uplink transmission and downlink transmission, thus meeting the bidirectional transmission delay requirements of the scheduled services and improving the success rate of scheduled service transmission.

[0239] In one possible implementation, the PCF receives the transmission delay parameters of the bidirectional transmission sent by the AF associated with the pre-defined service.

[0240] The transmission delay parameter for bidirectional transmission can be the delay requirement for bidirectional transmission of a pre-defined service.

[0241] The AF associated with the reservation service may include, but is not limited to, the AF that requests the reservation service.

[0242] For example, an AF associated with a pre-booked service could be an AF that requests pre-booked service session resources from a core network functional node.

[0243] In one possible implementation, the AF can send the latency requirement for bidirectional transmission of the pre-defined service data stream to the PCF during the process of requesting session resources.

[0244] The AF can provide the PCF with bidirectional transmission delay parameters so that the PCF can determine the uplink transmission delay parameters and / or the uplink transmission delay parameters.

[0245] The AF can send bidirectional transmission delay parameters to the PCF in at least one of the following procedures:

[0246] 1) During the AF session, the AF provides the PCF with bidirectional transmission latency requirements and the required QoS parameters.

[0247] 2) AF session flow with required QoS update procedures.

[0248] 3) Service specific parameter configuration process.

[0249] 4) The process of configuring policies for subsequent AF sessions.

[0250] The AF provides bidirectional latency requirement information to the PCF, either directly or indirectly; indirect transmission includes:

[0251] 1) Send to PCF via NEF.

[0252] 2) Sent to PCF via TSCTSF,

[0253] 3) Send to PCF via TSCTSF and NEF.

[0254] like Figure 3 As shown, this exemplary embodiment provides an information transmission method that can be executed by a PCF, including:

[0255] Step 301: Based on the transmission delay parameters of the bidirectional transmission of the predetermined service data stream, determine the transmission delay parameters of the uplink transmission of the data stream and / or the transmission delay parameters of the downlink transmission of the data stream.

[0256] Transmission delay parameters for bidirectional transmission, uplink transmission, and / or downlink transmission of data streams, such as... Figure 2The implementation examples are illustrated below and will not be repeated here. The transmission delay parameter for bidirectional transmission can characterize the transmission delay of bidirectional transmission. That is, it represents the maximum allowable transmission delay for bidirectional data stream transmission.

[0257] In one possible implementation, the PCF can divide the transmission delay parameters of bidirectional transmission into uplink transmission delay parameters and downlink transmission delay parameters. Based on the uplink and downlink transmission delay parameters, the PCC rules for the uplink transmission of the predetermined service data stream and the PCC rules for the downlink transmission of the predetermined service data stream are determined respectively.

[0258] In one possible implementation, the PCC rules for uplink transmission and the PCC rules for downlink transmission of the pre-defined service data stream can be associated with the QoS monitoring policy for uplink transmission and the QoS monitoring policy for downlink transmission, respectively, so that UPF and access network equipment can monitor the uplink transmission latency and the downlink transmission latency.

[0259] For example, the PCF can determine the uplink PDB and downlink PDB based on the bidirectional transmission delay, and then generate corresponding PCC rules for the uplink SDF and downlink SDF. The corresponding PDB is used to allocate 5 QIs to the two PCC rules. These two PCC rules are respectively associated with the uplink transmission QoS monitoring policy and the downlink transmission QoS monitoring policy, monitoring the uplink delay and downlink delay respectively.

[0260] In one embodiment, the association identifier is sent by the PCF to the Session Management Function (SMF), and by the SMF to at least one of the following:

[0261] Access network equipment;

[0262] User-facing features (UPF).

[0263] Access network devices and / or UPFs can report transmission delay parameters for uplink and / or downlink data streams to core network elements. SMFs can send association identifiers to access network devices and / or UPFs.

[0264] When access network equipment and / or UPF monitor transmission delay parameters, they can use associated identifiers to associate the transmission delay parameters of uplink transmission and the transmission delay parameters of downlink transmission.

[0265] In one embodiment, the association identifier is indicated by the policy control and billing PCC rules associated with the pre-defined service.

[0266] In one possible implementation, the association identifier can be carried in the PCC rule.

[0267] In one possible implementation, the PCC rule can carry index information of the associated identifier, which is used to retrieve the corresponding associated identifier in the index table of associated identifiers.

[0268] In one possible implementation, the PCC rules include at least one of the following: PCC rules for uplink transmission; PCC rules for downlink transmission.

[0269] For example, when the PCF sends a PCC rule to the SMF, it can simultaneously send an association identifier for associating uplink transmission delay parameters and / or downlink transmission delay parameters; the SMF can then send the association identifier to the RAN and UPF.

[0270] In one possible implementation, the PCF can send the association identifier to the SMF within the PCC rule, and the SMF can then extract the association identifier and send it to the access network device and / or UPF.

[0271] In one possible implementation, PCF can add a field within the PCC rule to carry the association identifier.

[0272] In one possible implementation, the PCF can be within existing fields of the PCC rule, such as the service data flow template or the 5G QoS identifier.

[0273] In one possible implementation, the PCF can send the association identifier separately to the SMF, which then forwards it to the access network device and / or the UPF.

[0274] like Figure 4 As shown, this exemplary embodiment provides an information transmission method that can be executed by a PCF, including:

[0275] Step 401: Receive the uplink QoS latency monitoring report and the downlink QoS latency monitoring report, wherein the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using an association identifier;

[0276] Step 402: Based on the QoS latency monitoring reports of uplink and downlink transmissions, update the PCC rules for uplink transmission and / or the PCC rules for downlink transmission of the scheduled service.

[0277] In one possible implementation, the PCF can receive QoS latency monitoring reports for uplink transmissions and QoS latency monitoring reports for downlink transmissions sent by the UPF and / or access network devices.

[0278] In one possible implementation, the association identifier is determined by the PCF.

[0279] After the PCF updates the PCC rules, the PCF can indicate the association identifier through the updated PCC rules. The method by which the updated PCC rules indicate the association identifier can be similar to... Figure 3 The PCC rules indicate the associated identifiers in the embodiments shown, and will not be described again here.

[0280] In one possible implementation, the UPF and / or access network equipment can send uplink QoS latency monitoring reports and downlink QoS latency monitoring reports to the PCG via direct or indirect transmission.

[0281] UPF and / or access network devices can monitor the transmission delay parameters of uplink and / or downlink transmissions, and send uplink and downlink QoS delay monitoring reports to PCF. PCF then adjusts the PCC rules of uplink and / or downlink transmissions based on the received QoS delay monitoring reports, so that the transmission of data streams can adapt to the current network conditions.

[0282] In one possible implementation, the QoS latency monitoring report for uplink transmission can be used to indicate the transmission latency parameters of the current uplink transmission; the QoS latency monitoring report for downlink transmission can be used to indicate the transmission latency parameters of the current downlink transmission.

[0283] In one possible implementation, updating the PCC rules for the scheduled uplink transmission and / or the PCC rules for the scheduled downlink transmission includes at least one of the following:

[0284] Adjust the PCC rules for uplink transmission and / or downlink transmission;

[0285] Create new PCC rules for uplink transmissions and / or PCC rules for downlink transmissions.

[0286] For example, the PCF can update the PCC rules for the uplink transmission of the scheduled service and / or the PCC rules for the downlink transmission of the scheduled service, so that the uplink transmission delay of the data stream and the sum of the uplink transmission delays of the data stream are less than or equal to the delay requirements for the bidirectional transmission of the data stream.

[0287] In one embodiment, updating the PCC rules for the scheduled uplink transmission of the service includes: updating the packet unit delay budget (PDB) parameter and / or packet unit set delay budget (PSDB) parameter in the PCC rules for the scheduled uplink transmission of the service.

[0288] Update the PCC rules for the scheduled downlink transmission of services, including updating the PDB and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of services.

[0289] In one possible implementation, the PCF can adjust the uplink PDB parameters and / or PSDB parameters, and / or adjust the downlink PDB parameters and / or PSDB parameters based on the uplink QoS latency monitoring report and the downlink QoS latency monitoring report.

[0290] In one possible implementation, updating the PCC rules for the scheduled uplink transmission of the service includes updating 5QI in the PCC rules for the scheduled uplink transmission of the service.

[0291] In one possible implementation, updating the PCC rules for the scheduled downlink transmission of the service includes updating 5QI in the PCC rules for the scheduled downlink transmission of the service.

[0292] For example, PCF can authorize new uplink PDB parameters and / or downlink PDB parameters based on uplink QoS latency monitoring reports and downlink QoS latency monitoring reports (e.g., a new 5QI corresponding to PDBPDB can be selected).

[0293] In one embodiment, receiving QoS latency monitoring reports for uplink and downlink transmissions includes at least one of the following:

[0294] Receive uplink QoS latency monitoring reports and downlink QoS latency monitoring reports sent by UPF;

[0295] Receive uplink QoS latency monitoring reports and downlink QoS latency monitoring reports sent by access network devices via UPF.

[0296] In one possible implementation, the QoS latency monitoring reports for uplink and downlink transmissions can be sent from the UPF to the PCF via a control plane flow from UPF to SMF to PCF.

[0297] In one possible implementation, the QoS latency monitoring reports for uplink and downlink transmissions can be reported to the PCF by the access network device through the UPF for QoS monitoring.

[0298] In one possible implementation, the uplink QoS latency monitoring report and the downlink QoS latency monitoring report received from the UPF can be obtained by the UPF and sent to the PCF, or they can be obtained by the access network equipment and sent to the PCF through the UPF.

[0299] In one embodiment, the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent by the UPF and / or access network equipment to monitor the uplink transmission latency parameters, determine that the monitored uplink transmission latency parameters meet the uplink subscription event triggering conditions, and determine the associated downlink QoS latency monitoring report through the association identifier.

[0300] and / or

[0301] The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent by the UPF and / or access network equipment to monitor the downlink transmission latency parameters, determine that the monitored downlink transmission latency parameters meet the downlink subscription event triggering conditions, and identify the associated uplink QoS latency monitoring report through the association identifier.

[0302] For example, if the UPF monitors that the uplink transmission latency parameters meet the triggering conditions of an uplink subscription event, it can send a latency monitoring report to the PCF and / or AF. The UPF can include the monitored uplink transmission latency parameters in the uplink QoS latency monitoring report. The UPF can also determine the corresponding downlink QoS latency monitoring report based on the association identifier of the uplink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the subscribed service's downlink transmission. For example, triggering the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0303] For example, if the UPF monitors that the downlink transmission latency parameters meet the triggering conditions of a downlink subscription event, it can send a latency monitoring report to the PCF and / or AF. The UPF can include the monitored downlink transmission latency parameters in the downlink transmission QoS latency monitoring report. The UPF can also determine the corresponding uplink transmission QoS latency monitoring report based on the association identifier of the downlink transmission QoS latency monitoring report. The UPF can send both the uplink and downlink transmission QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink transmission PCC rules and / or the subscribed service downlink transmission PCC rules. For example, triggering the PCF to authorize new uplink transmission PDB parameters and / or downlink transmission PDB parameters.

[0304] For example, if an access network device detects that the uplink transmission latency parameters meet the triggering conditions of an uplink subscription event, it can send a latency monitoring report to the PCF. The UPF can include the monitored uplink transmission latency parameters in the uplink QoS latency monitoring report. The UPF can also determine the corresponding downlink QoS latency monitoring report based on the association identifier of the uplink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the subscribed service's downlink transmission. For example, triggering the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0305] For example, if an access network device monitors downlink transmission latency parameters and finds that these parameters meet the triggering conditions for a downlink subscription event, it can send a latency monitoring report to the PCF. The UPF can include the monitored downlink transmission latency parameters in its downlink QoS latency monitoring report. The UPF can also determine the corresponding uplink QoS latency monitoring report based on the association identifier of the downlink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the scheduled downlink service. For example, this could trigger the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0306] In one possible implementation, the uplink subscription events used by the UPF and the uplink subscription events used by the access network device can be the same or different, and no limitation is made here.

[0307] In one possible implementation, the downlink subscription events used by the UPF and the downlink subscription events used by the access network device can be the same or different, and this is not limited here.

[0308] In one embodiment, based on the QoS latency monitoring reports of uplink and downlink transmissions, the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service are updated, including:

[0309] Send uplink QoS latency monitoring reports and downlink QoS latency monitoring reports to the AF associated with the pre-defined service;

[0310] Receive AF session update information sent in response to uplink and downlink QoS latency monitoring reports;

[0311] Based on AF session update information, update the PCC rules for scheduled uplink transmissions and / or scheduled downlink transmissions of services.

[0312] Here, PCF does not directly determine whether to update the PCC rules for uplink transmissions and / or the PCC rules for downlink transmissions.

[0313] The PCF can send the received uplink QoS latency monitoring reports and downlink QoS latency monitoring reports to the AF.

[0314] Here, the QoS latency monitoring reports for uplink and downlink transmissions sent by the PCF can be sent directly to the AF, or they can be sent by the PCF to the AF through the NEF.

[0315] After receiving the QoS latency monitoring reports for uplink and downlink transmissions, the AF can determine whether to send AF session update information to the PCF to update the PCC rules for uplink and / or downlink transmissions.

[0316] In one possible implementation, the AF session update information includes: transmission delay parameters for bidirectional transmission of the scheduled service data stream.

[0317] In one possible implementation, uplink QoS latency monitoring reports and downlink QoS latency monitoring reports are used to trigger modifications to AF sessions associated with a predetermined service, thereby triggering PCC rule updates.

[0318] For example, the AF can determine whether it is necessary to provide bidirectional transmission delay parameters to the PCF based on the QoS delay monitoring reports of uplink and downlink transmissions, so that the PCF can update the PCC rules for uplink and / or downlink transmissions.

[0319] PCF can update the PCC rules for uplink and / or downlink transmissions based on AF session update information.

[0320] The AF can provide the PCF with AF session update information so that the PCF can determine the PCC rules for uplink transmission and / or the PCC rules for downlink transmission, that is, update the transmission delay parameters for uplink transmission and / or the transmission delay parameters for downlink transmission.

[0321] The AF may send AF session update information to the PCF in at least one of the following procedures:

[0322] 1) During the AF session, the AF provides the PCF with bidirectional transmission latency requirements and the required QoS parameters.

[0323] 2) AF session flow with required QoS update procedures.

[0324] 3) Service specific parameter configuration process.

[0325] 4) The process of configuring policies for subsequent AF sessions.

[0326] The AF provides bidirectional latency requirement information to the PCF, either directly or indirectly; indirect transmission includes:

[0327] 1) Send to PCF via NEF.

[0328] 2) Sent to PCF via TSCTSF,

[0329] 3) Send to PCF via TSCTSF and NEF.

[0330] Combination Figure 2 He Ru Figure 4 Examples, such as Figure 5 As shown, this exemplary embodiment provides an information transmission method that can be executed by a PCF, including:

[0331] Step 501: Determine and send the association identifier of the pre-ordered service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the pre-ordered service data stream.

[0332] Step 502: Receive the uplink QoS latency monitoring report and the downlink QoS latency monitoring report, wherein the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using an association identifier;

[0333] Step 503: Based on the QoS latency monitoring reports of uplink and downlink transmissions, update the PCC rules for uplink transmission and / or the PCC rules for downlink transmission of the scheduled service.

[0334] Figure 5 Implementation examples, including Figure 2 Examples and Figure 4 The content of the embodiments. Therefore, the same explanations or features will not be repeated one by one, and can be referred to the embodiments on the corresponding side.

[0335] like Figure 6 As shown, this exemplary embodiment provides an information transmission method that can be executed by a PCF, including:

[0336] Step 601: Receive AF session update information sent by the AF associated with the predefined service in response to the uplink QoS latency monitoring report and the downlink QoS latency monitoring report; wherein, the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent to the AF by the UPF;

[0337] Step 602: Based on the AF session update information, update the PCC rules for the scheduled uplink transmission of the service and / or the PCC rules for the scheduled downlink transmission of the service.

[0338] Uplink QoS latency monitoring report and downlink QoS latency monitoring report, as follows: Figure 4 The embodiments shown are illustrated and will not be repeated here. In one possible implementation, the uplink QoS latency monitoring report and downlink QoS latency monitoring report sent from the UPF to the AF can be obtained by the UPF and sent to the AF, or it can be obtained by the access network device and sent to the AF through the UPF.

[0339] Here, QoS latency monitoring reports for uplink and downlink transmissions can be sent from the UPF to the AF via a user-facing notification process from the UPF to the AF.

[0340] Here, the UPF can provide the QoS latency monitoring reports for both uplink and downlink transmissions to the AF.

[0341] The methods by which UPF and / or access network devices determine the reporting of uplink QoS latency monitoring reports and downlink QoS latency monitoring reports are as described above and will not be repeated here.

[0342] In one possible implementation, uplink QoS latency monitoring reports and downlink QoS latency monitoring reports are used to trigger modifications to AF sessions associated with a predetermined service, thereby triggering PCC rule updates.

[0343] After receiving the QoS latency monitoring reports for uplink and downlink transmissions, the AF can determine whether to send AF session update information to trigger the PCF to update the PCC rules for uplink and / or downlink transmissions.

[0344] In one possible implementation, the AF session update information includes one of the following:

[0345] Transmission delay parameters for bidirectional transmission of the scheduled business data stream;

[0346] Uplink QoS latency monitoring report and downlink QoS latency monitoring report.

[0347] For example, the AF can determine whether it is necessary to provide bidirectional transmission delay parameters to the PCF based on the QoS delay monitoring reports of uplink and downlink transmissions, so that the PCF can update the PCC rules for uplink and / or downlink transmissions.

[0348] PCF can update the PCC rules for uplink and / or downlink transmissions based on AF session update information.

[0349] The method by which AF sends AF session update information to PCF is similar to that described above, and will not be repeated here.

[0350] The order of steps listed in the above PCF-side information transmission method embodiments is not intended to limit the execution order of each step. Each step can be executed in the order listed, or it can be executed in a different order if there is no contradiction. Each step can be implemented as a separate embodiment if there is no contradiction, or multiple steps can be combined as an embodiment.

[0351] Combination Figure 2 He Ru Figure 6 Examples, such as Figure 7 As shown, this exemplary embodiment provides an information transmission method that can be executed by a PCF, including:

[0352] Step 701: Determine and send the association identifier of the pre-ordered service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the downlink transmission of the pre-ordered service data stream.

[0353] Step 702: Receive AF session update information sent by the AF associated with the predefined service in response to the uplink QoS latency monitoring report and the downlink QoS latency monitoring report; wherein, the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent to the AF by the UPF;

[0354] Step 703: Based on the AF session update information, update the PCC rules for the scheduled uplink transmission of the service and / or the PCC rules for the scheduled downlink transmission of the service.

[0355] Figure 7 Implementation examples, including Figure 2 Examples and Figure 6 The content of the embodiments. Therefore, the same explanations or features will not be repeated one by one, and can be referred to the embodiments on the corresponding side.

[0356] In each embodiment, the information transmission methods performed on the PCF side, UPF side, AF side and access network side can be one-to-one corresponding. Therefore, the same explanations or features will not be repeated one by one, and the embodiments of the corresponding side can be referred to.

[0357] like Figure 8 As shown, this exemplary embodiment provides an information transmission method, which can be executed by an AF, including:

[0358] Step 801: Send the transmission delay parameters of the bidirectional transmission of the pre-defined service to the PCF. The bidirectional transmission delay parameters are used by the PCF to determine the association identifier of the pre-defined service. The transmission delay parameters are used to associate the uplink transmission delay parameters and the downlink transmission delay parameters of the pre-defined service data stream.

[0359] Reservation services include, but are not limited to, XRM services.

[0360] In one possible implementation, the scheduled service can have a bidirectional data stream.

[0361] In one possible implementation, the association identifier may include any of the following: Correlation ID; Peer ID; Round Trip Group ID; Peer Indication; Common ID. The name of the association identifier is not limited here.

[0362] In one possible implementation, the associated identifier can be generated based on the common identifier, or the associated identifier can be obtained by mapping based on the common identifier.

[0363] In one possible implementation, the association identifier is associated with the transmission delay parameters of the uplink transmission of the predetermined service data stream; and the association identifier is associated with the transmission delay parameters of the downlink transmission of the predetermined service data stream. That is, the core network functional node or access network device can determine the transmission delay parameters of the uplink transmission and the downlink transmission of the predetermined service data stream through the association identifier.

[0364] Transmission delay parameters may include, but are not limited to, delay configuration parameters associated with data stream transmission.

[0365] The transmission delay parameter may include at least one of the following: transmission delay; PDB; PSDB. PDB and / or PSDB may belong to 5QI. PSDB defines the upper limit of the transmission delay of the PDU set between the N6 endpoint at the UE and UPF.

[0366] In one possible implementation, the PCF can determine the uplink transmission delay of the data stream and / or the uplink transmission delay of the data stream based on the transmission delay parameters of the bidirectional transmission of the predetermined service data stream. The bidirectional transmission delay parameters of the predetermined service data stream can be indicated to the PCF by the AF associated with the predetermined service.

[0367] In one possible implementation, the PCF receives the transmission delay parameters of the bidirectional transmission sent by the AF associated with the pre-defined service.

[0368] The transmission delay parameter for bidirectional transmission can be the delay requirement for bidirectional transmission of a pre-defined service.

[0369] AF can include, but is not limited to, AFs that request to conduct pre-booked services.

[0370] For example, an AF can be an AF that requests reserved service session resources from a core network functional node.

[0371] In one possible implementation, the AF can send the latency requirement for bidirectional transmission of the pre-defined service data stream to the PCF during the process of requesting session resources.

[0372] The AF can provide the PCF with bidirectional transmission delay parameters so that the PCF can determine the uplink transmission delay parameters and / or the uplink transmission delay parameters.

[0373] The AF can send bidirectional transmission delay parameters to the PCF in at least one of the following procedures:

[0374] 1) During the AF session, the AF provides the PCF with bidirectional transmission latency requirements and the required QoS parameters.

[0375] 2) AF session flow with required QoS update procedures.

[0376] 3) Service specific parameter configuration process.

[0377] 4) The process of configuring policies for subsequent AF sessions.

[0378] The AF provides bidirectional latency requirement information to the PCF, either directly or indirectly; indirect transmission includes:

[0379] 1) Send to PCF via NEF.

[0380] 2) Sent to PCF via TSCTSF,

[0381] 3) Send to PCF via TSCTSF and NEF.

[0382] In one possible implementation, the AF can send the transmission delay parameters for bidirectional transmission of the predetermined service data stream to the PCF via the NEF.

[0383] In one possible implementation, the bidirectional transmission delay parameter can characterize the maximum allowable transmission delay of a predetermined service data stream during uplink and downlink transmission.

[0384] In one possible implementation, the transmission delay of the uplink data stream and the sum of the uplink transmission delays of the data stream are less than or equal to the transmission delay of the bidirectional transmission of the predetermined service data stream.

[0385] In one possible implementation, the association identifier is associated with at least one of the following:

[0386] Transmission delay parameters of the uplink service data stream for the pre-booked service;

[0387] Transmission delay parameters for the downlink service data stream of the pre-booked service;

[0388] Transmission delay parameters for the QoS stream of the pre-booked service;

[0389] PCC associated with pre-booked business;

[0390] 5QI related to pre-booking business.

[0391] In one possible implementation, PCF can generate associated identifiers based on a predetermined strategy.

[0392] In one possible implementation, an association identifier can be associated with a pre-booked service, or an association identifier can be associated with a class of pre-booked services.

[0393] In one embodiment, determining the associated identifier of the pre-booked service includes:

[0394] The association identifier must be determined based on at least one of the following:

[0395] Transmission delay parameters for bidirectional transmission of the scheduled business data stream;

[0396] Contract information associated with the pre-booked service;

[0397] Carrier strategies associated with pre-booked services.

[0398] In one possible implementation, the requirements of the scheduled service for transmission delay parameters may include at least one of the following: transmission delay parameter requirements of the scheduled service for bidirectional transmission of the data stream; transmission delay parameter requirements of the scheduled service for uplink transmission of the data stream; and transmission delay parameter requirements of the scheduled service for downlink transmission of the data stream.

[0399] In one possible implementation, the PCF can determine the bidirectional transmission delay rules or 5QI updates that the network supports for the pre-defined services based on the transmission delay parameters (i.e., transmission delay parameter requirements), subscription information, or operator policies, and then generate an associated identifier.

[0400] In one possible implementation, the association identifier can be determined based on one or more of the transmission delay parameters of bidirectional transmission, the subscription information of the pre-ordered service association, and the operator policy of the pre-ordered service association.

[0401] For example, associated identifiers can be assigned based on carrier policies. Carrier policies contain the rules for assigning associated identifiers.

[0402] In related technologies, the uplink and downlink transmissions of the scheduled business data stream are independent of each other, and the transmission delay parameters of the uplink transmission are not correlated, making it impossible to achieve coordinated adjustment of the uplink transmission delay parameters.

[0403] The association identifier is used to associate the transmission delay parameters of uplink transmission and downlink transmission. Core network elements and / or access network devices can determine the transmission delay parameters of uplink transmission and downlink transmission based on the association identifier, and perform coordinated processing of the transmission delay parameters of uplink transmission and downlink transmission, thereby improving the coordination efficiency of the transmission delay parameters of uplink transmission and downlink transmission, thus meeting the bidirectional transmission delay requirements of the scheduled services and improving the success rate of scheduled service transmission.

[0404] In one embodiment, the transmission delay parameters of the bidirectional transmission of the predetermined service data stream are used by the PCF to determine the transmission delay parameters of the uplink transmission of the data stream and / or the transmission delay parameters of the downlink transmission of the data stream.

[0405] The transmission delay parameter for bidirectional transmission can characterize the transmission delay of bidirectional transmission. That is, it is the maximum allowable transmission delay for bidirectional data stream transmission.

[0406] In one possible implementation, the PCF can divide the transmission delay parameters of bidirectional transmission into uplink transmission delay parameters and downlink transmission delay parameters. Based on the uplink and downlink transmission delay parameters, the PCC rules for the uplink transmission of the predetermined service data stream and the PCC rules for the downlink transmission of the predetermined service data stream are determined respectively.

[0407] In one possible implementation, the PCC rules for uplink transmission and the PCC rules for downlink transmission of the pre-defined service data stream can be associated with the QoS monitoring policy for uplink transmission and the QoS monitoring policy for downlink transmission, respectively, so that UPF and access network equipment can monitor the uplink transmission latency and the downlink transmission latency.

[0408] For example, the PCF can determine the uplink PDB and downlink PDB based on the bidirectional transmission delay, and then generate corresponding PCC rules for the uplink SDF and downlink SDF. The corresponding PDB is used to allocate 5 QIs to the two PCC rules. These two PCC rules are respectively associated with the uplink transmission QoS monitoring policy and the downlink transmission QoS monitoring policy, monitoring the uplink delay and downlink delay respectively.

[0409] In one embodiment, the association identifier is sent by the PCF to at least one of the following via the Session Management Function (SMF): the access network device; and the User Plane Function (UPF).

[0410] In one possible implementation, the associated identifier for sending the pre-ordered service includes at least one of the following:

[0411] Send the associated identifier of the pre-ordered service directly;

[0412] Send the associated identifier of the pre-booked service indirectly.

[0413] In one possible implementation, the associated identifier of the pre-booked service is sent directly, including: the PCF directly sends the associated identifier of the pre-booked service to the SMF.

[0414] In one possible implementation, the associated identifier of the pre-booked service is sent indirectly, including: the PCF sends the associated identifier of the pre-booked service to the UPF and / or access network equipment through the SMF.

[0415] In one embodiment, the association identifier is carried in the policy control and billing PCC rules for the pre-defined service association sent by the PCF to the SMF.

[0416] In one possible implementation, the association identifier can be carried in the PCC rule.

[0417] In one possible implementation, the PCC rule can carry index information of the associated identifier, which is used to retrieve the corresponding associated identifier in the index table of associated identifiers.

[0418] In one possible implementation, the PCC rules include at least one of the following: PCC rules for uplink transmission; PCC rules for downlink transmission.

[0419] For example, when the PCF sends a PCC rule to the SMF, it can simultaneously send an association identifier for associating uplink transmission delay parameters and / or downlink transmission delay parameters; the SMF can then send the association identifier to the RAN and UPF.

[0420] In one possible implementation, the PCF can send the association identifier to the SMF within the PCC rule, and the SMF can then extract the association identifier and send it to the access network device and / or UPF.

[0421] In one possible implementation, PCF can add a field within the PCC rule to carry the association identifier.

[0422] In one possible implementation, the PCF can be within existing fields of the PCC rule, such as the service data flow template or the 5G QoS identifier.

[0423] In one possible implementation, the PCF can send the association identifier separately to the SMF, which then forwards it to the access network device and / or the UPF.

[0424] like Figure 9 As shown, this exemplary embodiment provides an information transmission method, which can be executed by an AF, including:

[0425] Step 901: Receive the QoS latency monitoring report for uplink transmission and the QoS latency monitoring report for downlink transmission sent by UPF or PCF.

[0426] In one possible implementation, the QoS latency monitoring reports for uplink and downlink transmissions are associated using an association identifier.

[0427] In one embodiment, receiving the QoS latency monitoring report for uplink transmission and the QoS latency monitoring report for downlink transmission sent by the UPF includes: receiving the QoS latency monitoring report for uplink transmission and the QoS latency monitoring report for downlink transmission sent by the UPF through the NEF.

[0428] Receive uplink QoS latency monitoring reports and downlink QoS latency monitoring reports sent by PCF, including: receiving uplink QoS latency monitoring reports and downlink QoS latency monitoring reports sent by PCF through NEF.

[0429] Here, the QoS latency monitoring reports for uplink and downlink transmissions received by the AF from the UPF can be sent directly to the AF by the UPF, or they can be sent by the UPF to the AF through the NEF.

[0430] Here, the QoS latency monitoring reports for uplink and downlink transmissions received by the AF from the PCF can be sent directly by the PCF to the AF, or they can be sent by the PCF to the AF through the NEF.

[0431] Combination Figure 8 and Figure 9 Examples, such as Figure 10 As shown, this exemplary embodiment provides an information transmission method, which can be executed by an AF, including:

[0432] Step 1001: Send the transmission delay parameters of the bidirectional transmission of the pre-defined service to the PCF. The bidirectional transmission delay parameters are used by the PCF to determine the association identifier of the pre-defined service. The transmission delay parameters are used to associate the uplink transmission delay parameters and the downlink transmission delay parameters of the pre-defined service data stream.

[0433] Step 1002: Receive the QoS latency monitoring report for uplink transmission and the QoS latency monitoring report for downlink transmission sent by UPF or PCF.

[0434] Figure 10 Implementation examples, including Figure 8 Examples and Figure 9 The content of the embodiments. Therefore, the same explanations or features will not be repeated one by one, and can be referred to the embodiments on the corresponding side.

[0435] like Figure 11 As shown, this exemplary embodiment provides an information transmission method, which can be executed by an AF, including:

[0436] Step 1101: Based at least on the QoS latency monitoring reports of uplink and downlink transmissions, determine whether to send AF session update information to the PCF.

[0437] In one embodiment, AF session update information is used by the PCF to update the PCC rules for the scheduled uplink transmission of the service and / or the PCC rules for the scheduled downlink transmission of the service.

[0438] In one possible implementation, the AF session request may include information such as a data flow description and the QoS characteristics of the data flow. The PCF can then generate or update PCC rules for the corresponding data flow based on this information.

[0439] UPF and / or access network devices can monitor the transmission delay parameters of uplink and / or downlink transmissions, and send uplink and downlink QoS delay monitoring reports to PCF or AF. PCF adjusts the PCC rules of uplink and / or downlink transmissions based on the received QoS delay monitoring reports. Alternatively, AF determines whether to send AF session update information to PCF so that PCF can adjust the PCC rules of uplink and / or downlink transmissions, enabling data flow transmission to adapt to the current network conditions.

[0440] In one possible implementation, the uplink QoS latency monitoring report and downlink QoS latency monitoring report sent from the UPF to the AF can be obtained by the UPF through monitoring and sent to the AF, or they can be obtained by the access network equipment through monitoring and sent to the AF via the UPF.

[0441] In one possible implementation, the PCF does not directly determine whether to update the PCC rules for uplink and / or downlink transmissions. The PCF can send the received QoS latency monitoring reports for uplink and downlink transmissions to the AF.

[0442] After receiving the QoS latency monitoring reports for uplink and downlink transmissions, the AF can determine whether to send AF session update information for the PCF to update the PCC rules for uplink and / or downlink transmissions.

[0443] In one possible implementation, the AF session update information includes: transmission delay parameters for bidirectional transmission of the scheduled service data stream.

[0444] In one possible implementation, uplink QoS latency monitoring reports and downlink QoS latency monitoring reports are used to trigger modifications to AF sessions associated with a predetermined service, thereby triggering PCC rule updates.

[0445] For example, the AF can determine whether it is necessary to provide bidirectional transmission delay parameters to the PCF based on the QoS delay monitoring reports of uplink and downlink transmissions, so that the PCF can update the PCC rules for uplink and / or downlink transmissions.

[0446] PCF can update the PCC rules for uplink and / or downlink transmissions based on AF session update information.

[0447] The AF can provide the PCF with AF session update information so that the PCF can determine the PCC rules for uplink transmission and / or the PCC rules for downlink transmission, that is, update the transmission delay parameters for uplink transmission and / or the transmission delay parameters for downlink transmission.

[0448] The AF may send AF session update information to the PCF in at least one of the following procedures:

[0449] 1) During the AF session, the AF provides the PCF with bidirectional transmission latency requirements and the required QoS parameters.

[0450] 2) AF session flow with required QoS update procedures.

[0451] 3) Service specific parameter configuration process.

[0452] 4) The process of configuring policies for subsequent AF sessions.

[0453] In one embodiment, sending transmission delay parameters for the predetermined bidirectional transmission of services to the PCF includes at least one of the following:

[0454] Transmission delay parameters for the pre-defined bidirectional transmission of services are sent from NEF to PCF.

[0455] Transmission delay parameters for bidirectional transmission of the pre-defined service are sent to the PCF via TSCTSF;

[0456] Transmission delay parameters for bidirectional transmission of the scheduled service are sent from NEF to PCF via TSCTSF.

[0457] The AF provides bidirectional latency requirement information (transmission latency parameters for pre-defined bidirectional service transmission) to the PCF, either directly or indirectly; indirect transmission includes:

[0458] 1) Send to PCF via NEF.

[0459] 2) Sent to PCF via TSCTSF,

[0460] 3) Send to PCF via TSCTSF and NEF.

[0461] In one possible implementation, the QoS latency monitoring reports for uplink and downlink transmissions can be sent from the UPF to the AF via a user-facing notification process from the UPF to the AF.

[0462] Here, the UPF can provide the QoS latency monitoring reports for both uplink and downlink transmissions to the AF.

[0463] The methods by which UPF and / or access network devices determine the reporting of uplink QoS latency monitoring reports and downlink QoS latency monitoring reports are as described above and will not be repeated here.

[0464] In one possible implementation, uplink QoS latency monitoring reports and downlink QoS latency monitoring reports are used to trigger modifications to AF sessions associated with a predetermined service, thereby triggering PCC rule updates.

[0465] After receiving the QoS latency monitoring reports for uplink and downlink transmissions, the AF can determine whether to send AF session update information to the PCF to update the PCC rules for uplink and / or downlink transmissions.

[0466] In one possible implementation, the AF session update information includes one of the following:

[0467] Transmission delay parameters for bidirectional transmission of the scheduled business data stream;

[0468] Uplink QoS latency monitoring report and downlink QoS latency monitoring report.

[0469] For example, the AF can determine whether it is necessary to provide bidirectional transmission delay parameters to the PCF based on the QoS delay monitoring reports of uplink and downlink transmissions, so that the PCF can update the PCC rules for uplink and / or downlink transmissions.

[0470] PCF can update the PCC rules for uplink and / or downlink transmissions based on AF session update information.

[0471] The method by which AF sends AF session update information to PCF is similar to that described above, and will not be repeated here.

[0472] In one possible implementation, the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent by the UPF and / or access network equipment to monitor the uplink transmission latency parameters, determine that the monitored uplink transmission latency parameters meet the uplink subscription event triggering conditions, and determine the associated downlink QoS latency monitoring report through the association identifier.

[0473] and / or

[0474] The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent by the UPF and / or access network equipment to monitor the downlink transmission latency parameters, determine that the monitored downlink transmission latency parameters meet the downlink subscription event triggering conditions, and identify the associated uplink QoS latency monitoring report through the association identifier.

[0475] For example, if the UPF monitors that the uplink transmission latency parameters meet the triggering conditions of an uplink subscription event, it can send a latency monitoring report to the PCF and / or AF. The UPF can include the monitored uplink transmission latency parameters in the uplink QoS latency monitoring report. The UPF can also determine the corresponding downlink QoS latency monitoring report based on the association identifier of the uplink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the subscribed service's downlink transmission. For example, triggering the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0476] For example, if the UPF monitors that the downlink transmission latency parameters meet the triggering conditions of a downlink subscription event, it can send a latency monitoring report to the PCF and / or AF. The UPF can include the monitored downlink transmission latency parameters in the downlink transmission QoS latency monitoring report. The UPF can also determine the corresponding uplink transmission QoS latency monitoring report based on the association identifier of the downlink transmission QoS latency monitoring report. The UPF can send both the uplink and downlink transmission QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink transmission PCC rules and / or the subscribed service downlink transmission PCC rules. For example, triggering the PCF to authorize new uplink transmission PDB parameters and / or downlink transmission PDB parameters.

[0477] For example, if an access network device detects that the uplink transmission latency parameters meet the triggering conditions of an uplink subscription event, it can send a latency monitoring report to the PCF. The UPF can include the monitored uplink transmission latency parameters in the uplink QoS latency monitoring report. The UPF can also determine the corresponding downlink QoS latency monitoring report based on the association identifier of the uplink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the subscribed service's downlink transmission. For example, triggering the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0478] For example, if an access network device monitors downlink transmission latency parameters and finds that these parameters meet the triggering conditions for a downlink subscription event, it can send a latency monitoring report to the PCF. The UPF can include the monitored downlink transmission latency parameters in its downlink QoS latency monitoring report. The UPF can also determine the corresponding uplink QoS latency monitoring report based on the association identifier of the downlink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the scheduled downlink service. For example, this could trigger the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0479] In one embodiment, AF session update information is used by the PCF to update the Packet Unit Delay Budget (PDB) parameter and / or Packet Unit Set Delay Budget (PSDB) parameter in the PCC rules for scheduled uplink transmission of services, and / or to update the PDB parameter and / or PSDB parameter in the PCC rules for scheduled downlink transmission of services.

[0480] In one possible implementation, the PCF can adjust the PDB and / or PSDB parameters of the uplink transmission, and / or adjust the PDB and / or PSDB parameters of the downlink transmission based on the AF session update information.

[0481] In one possible implementation, updating the PCC rules for the scheduled uplink transmission of the service includes updating 5QI in the PCC rules for the scheduled uplink transmission of the service.

[0482] In one possible implementation, updating the PCC rules for the scheduled downlink transmission of the service includes updating 5QI in the PCC rules for the scheduled downlink transmission of the service.

[0483] For example, the PCF can authorize new PDB parameters for uplink transmissions and / or downlink transmissions based on AF session update information (e.g., a new 5QI corresponding to PDBPDB can be selected).

[0484] The order of steps listed in the above embodiments of the AF-side information transmission method is not intended to limit the execution order of each step. Each step can be executed in the order listed, or it can be executed in a different order if there is no contradiction. Each step can be implemented as a separate embodiment if there is no contradiction, or multiple steps can be combined as an embodiment.

[0485] Combination Figure 8 , Figure 9 and Figure 11 Examples, such as Figure 12 As shown, this exemplary embodiment provides an information transmission method, which can be executed by an AF, including:

[0486] Step 1201: Send the transmission delay parameters of the bidirectional transmission of the pre-defined service to the PCF. The bidirectional transmission delay parameters are used by the PCF to determine the association identifier of the pre-defined service. The transmission delay parameters are used to associate the uplink transmission delay parameters and the downlink transmission delay parameters of the pre-defined service data stream.

[0487] Step 1202: Receive the uplink QoS latency monitoring report and downlink QoS latency monitoring report sent by UPF or PCF.

[0488] Step 1203: Based at least on the uplink QoS latency monitoring report and the downlink QoS latency monitoring report, determine whether to send AF session update information to the PCF.

[0489] Figure 11 Implementation examples, including Figure 8 Implementation examples Figure 9 Examples and Figure 10 The content of the embodiments. Therefore, the same explanations or features will not be repeated one by one, and can be referred to the embodiments on the corresponding side.

[0490] In each embodiment, the information transmission methods performed on the PCF side, UPF side, AF side and access network side can be one-to-one corresponding. Therefore, the same explanations or features will not be repeated one by one, and the embodiments of the corresponding side can be referred to.

[0491] like Figure 13 As shown, this exemplary embodiment provides an information transmission method that can be executed by a UPF, including:

[0492] Step 1301: Receive the association identifier of the pre-ordered service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the pre-ordered service data stream.

[0493] Reservation services include, but are not limited to, XRM services.

[0494] In one possible implementation, the associated identifier of the subscribed service is received, including at least one of the following:

[0495] The associated identifier for receiving pre-booked services directly;

[0496] The associated identifier for receiving pre-booked services is received indirectly.

[0497] In one possible implementation, receiving the associated identifier of a pre-booked service directly includes receiving the associated identifier of the pre-booked service directly from the PCG.

[0498] In one possible implementation, the associated identifier of the pre-booked service is sent indirectly, including receiving the associated identifier of the pre-booked service sent by the PCF through the SMF.

[0499] In one possible implementation, the scheduled service can have a bidirectional data stream.

[0500] In one possible implementation, the association identifier may include any of the following: Correlation ID; Peer ID; Round Trip Group ID; Peer Indication; Common ID. The name of the association identifier is not limited here.

[0501] In one possible implementation, the associated identifier can be generated based on the common identifier, or the associated identifier can be obtained by mapping based on the common identifier.

[0502] In one possible implementation, the association identifier is associated with the transmission delay parameters of the uplink transmission of the predetermined service data stream; and the association identifier is associated with the transmission delay parameters of the downlink transmission of the predetermined service data stream. That is, the core network functional node or access network device can determine the transmission delay parameters of the uplink transmission and the downlink transmission of the predetermined service data stream through the association identifier.

[0503] Transmission delay parameters may include, but are not limited to, delay configuration parameters associated with data stream transmission.

[0504] The transmission delay parameter may include at least one of the following: transmission delay; PDB; PSDB. PDB and / or PSDB may belong to 5QI. PSDB defines the upper limit of the transmission delay of the PDU set between the N6 endpoint at the UE and UPF.

[0505] In one possible implementation, the PCF can determine the uplink transmission delay of the data stream and / or the uplink transmission delay of the data stream based on the transmission delay parameters of the bidirectional transmission of the predetermined service data stream. The bidirectional transmission delay parameters of the predetermined service data stream can be indicated to the PCF by the AF associated with the predetermined service.

[0506] In one possible implementation, the AF can send the transmission delay parameters for bidirectional transmission of the predetermined service data stream to the PCF via the NEF.

[0507] In one possible implementation, the bidirectional transmission delay parameter can characterize the maximum allowable transmission delay of a predetermined service data stream during uplink and downlink transmission.

[0508] In one possible implementation, the transmission delay of the uplink data stream and the sum of the uplink transmission delays of the data stream are less than or equal to the transmission delay of the bidirectional transmission of the predetermined service data stream.

[0509] In one possible implementation, the association identifier is associated with at least one of the following:

[0510] Transmission delay parameters of the uplink service data stream for the pre-booked service;

[0511] Transmission delay parameters for the downlink service data stream of the pre-booked service;

[0512] Transmission delay parameters for the QoS stream of the pre-booked service;

[0513] PCC associated with pre-booked business;

[0514] 5QI related to pre-booking business.

[0515] In one possible implementation, PCF can generate associated identifiers based on a predetermined strategy.

[0516] In one possible implementation, an association identifier can be associated with a pre-booked service, or an association identifier can be associated with a class of pre-booked services.

[0517] In one embodiment, determining the associated identifier of the pre-booked service includes:

[0518] The association identifier must be determined based on at least one of the following:

[0519] Transmission delay parameters for bidirectional transmission of the scheduled business data stream;

[0520] Contract information associated with the pre-booked service;

[0521] Carrier strategies associated with pre-booked services.

[0522] In one possible implementation, the requirements of the scheduled service for transmission delay parameters may include at least one of the following: transmission delay parameter requirements of the scheduled service for bidirectional transmission of the data stream; transmission delay parameter requirements of the scheduled service for uplink transmission of the data stream; and transmission delay parameter requirements of the scheduled service for downlink transmission of the data stream.

[0523] In one possible implementation, the PCF can determine the bidirectional transmission delay rules or 5QI updates that the network supports for the pre-defined services based on the transmission delay parameters (i.e., transmission delay parameter requirements), subscription information, or operator policies, and then generate an associated identifier.

[0524] In one possible implementation, the association identifier can be determined based on one or more of the transmission delay parameters of bidirectional transmission, the subscription information of the pre-ordered service association, and the operator policy of the pre-ordered service association.

[0525] For example, associated identifiers can be assigned based on carrier policies. Carrier policies contain the rules for assigning associated identifiers.

[0526] In related technologies, the uplink and downlink transmissions of the scheduled business data stream are independent of each other, and the transmission delay parameters of the uplink transmission are not correlated, making it impossible to achieve coordinated adjustment of the uplink transmission delay parameters.

[0527] The association identifier is used to associate the transmission delay parameters of uplink transmission and downlink transmission. Core network elements and / or access network devices can determine the transmission delay parameters of uplink transmission and downlink transmission based on the association identifier, and perform coordinated processing of the transmission delay parameters of uplink transmission and downlink transmission, thereby improving the coordination efficiency of the transmission delay parameters of uplink transmission and downlink transmission, thus meeting the bidirectional transmission delay requirements of the scheduled services and improving the success rate of scheduled service transmission.

[0528] In one embodiment, the association identifier is a policy control and billing PCC rule indication of a pre-defined service association sent by the policy control function (PCF) to the session management function (SMF).

[0529] In one possible implementation, the association identifier can be carried in the PCC rule.

[0530] In one possible implementation, the PCC rule can carry index information of the associated identifier, which is used to retrieve the corresponding associated identifier in the index table of associated identifiers.

[0531] In one possible implementation, the PCC rules include at least one of the following: PCC rules for uplink transmission; PCC rules for downlink transmission.

[0532] For example, when the PCF sends a PCC rule to the SMF, it can simultaneously send an association identifier for associating uplink transmission delay parameters and / or downlink transmission delay parameters; the SMF can then send the association identifier to the RAN and UPF.

[0533] In one possible implementation, the PCF can send the association identifier to the SMF within the PCC rule, and the SMF can then extract the association identifier and send it to the access network device and / or UPF.

[0534] In one possible implementation, PCF can add a field within the PCC rule to carry the association identifier.

[0535] In one possible implementation, the PCF can be within existing fields of the PCC rule, such as the service data flow template or the 5G QoS identifier.

[0536] In one possible implementation, the PCF can send the association identifier separately to the SMF, which then forwards it to the access network device and / or the UPF.

[0537] like Figure 14 As shown, this exemplary embodiment provides an information transmission method that can be executed by a UPF, including at least one of the following:

[0538] Step 1401a: Send the uplink QoS latency monitoring report and the downlink QoS latency monitoring report to the PCF;

[0539] Step 1401b: Send the uplink QoS latency monitoring report and the downlink QoS latency monitoring report to the AF associated with the predetermined service;

[0540] The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using an association identifier.

[0541] In one possible implementation, the uplink QoS latency monitoring report and the downlink QoS latency monitoring report sent to the PCF are used by the PCF to update the PCC rules for the scheduled service uplink transmission and / or the PCC rules for the scheduled service downlink transmission.

[0542] In one possible implementation, the uplink and downlink QoS latency monitoring reports sent to the AF are used by the AF to determine whether to send AF session update information to the PCF, so that the PCF can update the PCC rules for the scheduled service uplink transmission and / or the scheduled service downlink transmission.

[0543] UPF can monitor the transmission delay parameters of uplink and / or downlink transmissions, and send the QoS delay monitoring reports of uplink and downlink transmissions to PCF. PCF then adjusts the PCC rules of uplink and / or downlink transmissions based on the received QoS delay monitoring reports, so that the transmission of data streams can adapt to the current network conditions.

[0544] In one possible implementation, the QoS latency monitoring report for uplink transmission can be used to indicate the transmission latency parameters of the current uplink transmission; the QoS latency monitoring report for downlink transmission can be used to indicate the transmission latency parameters of the current downlink transmission.

[0545] In one possible implementation, updating the PCC rules for the scheduled uplink transmission and / or the PCC rules for the scheduled downlink transmission includes at least one of the following:

[0546] Adjust the PCC rules for uplink transmission and / or downlink transmission;

[0547] Create new PCC rules for uplink transmissions and / or PCC rules for downlink transmissions.

[0548] For example, the PCF can update the PCC rules for the uplink transmission of the scheduled service and / or the PCC rules for the downlink transmission of the scheduled service, so that the uplink transmission delay of the data stream and the sum of the uplink transmission delays of the data stream are less than or equal to the delay requirements for the bidirectional transmission of the data stream.

[0549] Here, QoS latency monitoring reports for uplink and downlink transmissions can be sent from the UPF to the AF via a user-facing notification process from the UPF to the AF.

[0550] Here, the UPF can provide the QoS latency monitoring reports for both uplink and downlink transmissions to the AF.

[0551] The methods by which UPF and / or access network devices determine the reporting of uplink QoS latency monitoring reports and downlink QoS latency monitoring reports are as described above and will not be repeated here.

[0552] In one possible implementation, uplink QoS latency monitoring reports and downlink QoS latency monitoring reports are used to trigger modifications to AF sessions associated with a predetermined service, thereby triggering PCC rule updates.

[0553] After receiving the QoS latency monitoring reports for uplink and downlink transmissions, the AF can determine whether to send AF session update information to the PCF to update the PCC rules for uplink and / or downlink transmissions.

[0554] Here, the QoS latency monitoring reports for uplink and downlink transmissions sent by the UPF can be sent directly to the AF, or they can be sent by the UPF through the NEF.

[0555] In one possible implementation, the AF session update information includes one of the following:

[0556] Transmission delay parameters for bidirectional transmission of the scheduled business data stream;

[0557] Uplink QoS latency monitoring report and downlink QoS latency monitoring report.

[0558] For example, the AF can determine whether it is necessary to provide bidirectional transmission delay parameters to the PCF based on the QoS delay monitoring reports of uplink and downlink transmissions, so that the PCF can update the PCC rules for uplink and / or downlink transmissions.

[0559] PCF can update the PCC rules for uplink and / or downlink transmissions based on AF session update information.

[0560] The AF can provide the PCF with AF session update information so that the PCF can determine the PCC rules for uplink transmission and / or the PCC rules for downlink transmission, that is, update the transmission delay parameters for uplink transmission and / or the transmission delay parameters for downlink transmission.

[0561] The AF may send AF session update information to the PCF in at least one of the following procedures:

[0562] 1) During the AF session, the AF provides the PCF with bidirectional transmission latency requirements and the required QoS parameters.

[0563] 2) AF session flow with required QoS update procedures.

[0564] 3) Service specific parameter configuration process.

[0565] 4) The process of configuring policies for subsequent AF sessions.

[0566] The AF provides bidirectional latency requirement information to the PCF, either directly or indirectly; indirect transmission includes:

[0567] 1) Send to PCF via NEF.

[0568] 2) Sent to PCF via TSCTSF,

[0569] 3) Send to PCF via TSCTSF and NEF.

[0570] In one possible implementation, the uplink QoS latency monitoring report and downlink QoS latency monitoring report sent from the UPF to the PCF can be obtained by the UPF through monitoring and sent to the PCF, or they can be obtained by the access network equipment through monitoring and sent to the PCF via the UPF.

[0571] In one possible implementation, the uplink QoS latency monitoring report and downlink QoS latency monitoring report sent from the UPF to the AF can be obtained by the UPF through monitoring and sent to the AF, or they can be obtained by the access network equipment through monitoring and sent to the AF via the UPF.

[0572] Combination Figure 13 and Figure 14 Examples, such as Figure 15 As shown, this exemplary embodiment provides an information transmission method that can be executed by a UPF, including:

[0573] Step 1501: Receive the association identifier of the pre-ordered service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the downlink transmission of the pre-ordered service data stream.

[0574] The method also includes at least one of the following:

[0575] Step 1501a: Send the uplink QoS latency monitoring report and the downlink QoS latency monitoring report to the PCF;

[0576] Step 1501b: Send the uplink QoS latency monitoring report and the downlink QoS latency monitoring report to the AF associated with the pre-defined service;

[0577] Figure 15 Implementation examples, including Figure 13 Examples and Figure 14 The content of the embodiments. Therefore, the same explanations or features will not be repeated one by one, and can be referred to the embodiments on the corresponding side.

[0578] In one embodiment, the uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the uplink transmission latency parameters, determining that the monitored uplink transmission latency parameters meet the first uplink subscription event triggering condition, and identifying the associated downlink QoS latency monitoring report through the association identifier.

[0579] and / or

[0580] The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent by the UPF and / or access network equipment to monitor the downlink transmission latency parameters, determine that the monitored downlink transmission latency parameters meet the triggering conditions of the first downlink subscription event, and identify the associated uplink QoS latency monitoring report through the association identifier.

[0581] For example, if the UPF monitors that the uplink transmission latency parameters meet the triggering conditions of an uplink subscription event, it can send a latency monitoring report to the PCF and / or AF. The UPF can include the monitored uplink transmission latency parameters in the uplink QoS latency monitoring report. The UPF can also determine the corresponding downlink QoS latency monitoring report based on the association identifier of the uplink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the subscribed service's downlink transmission. For example, triggering the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0582] For example, if the UPF monitors that the downlink transmission latency parameters meet the triggering conditions of a downlink subscription event, it can send a latency monitoring report to the PCF and / or AF. The UPF can include the monitored downlink transmission latency parameters in the downlink transmission QoS latency monitoring report. The UPF can also determine the corresponding uplink transmission QoS latency monitoring report based on the association identifier of the downlink transmission QoS latency monitoring report. The UPF can send both the uplink and downlink transmission QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink transmission PCC rules and / or the subscribed service downlink transmission PCC rules. For example, triggering the PCF to authorize new uplink transmission PDB parameters and / or downlink transmission PDB parameters.

[0583] For example, if an access network device detects that the uplink transmission latency parameters meet the triggering conditions of an uplink subscription event, it can send a latency monitoring report to the PCF. The UPF can include the monitored uplink transmission latency parameters in the uplink QoS latency monitoring report. The UPF can also determine the corresponding downlink QoS latency monitoring report based on the association identifier of the uplink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the subscribed service's downlink transmission. For example, triggering the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0584] For example, if an access network device monitors downlink transmission latency parameters and finds that these parameters meet the triggering conditions for a downlink subscription event, it can send a latency monitoring report to the PCF. The UPF can include the monitored downlink transmission latency parameters in its downlink QoS latency monitoring report. The UPF can also determine the corresponding uplink QoS latency monitoring report based on the association identifier of the downlink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the scheduled downlink service. For example, this could trigger the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0585] In one possible implementation, the uplink subscription events used by the UPF and the uplink subscription events used by the access network device can be the same or different, and no limitation is made here.

[0586] In one possible implementation, the downlink subscription events used by the UPF and the downlink subscription events used by the access network device can be the same or different, and this is not limited here.

[0587] In one embodiment, updating the PCC rules for the scheduled uplink transmission of the service includes: updating the packet unit delay budget (PDB) parameter and / or packet unit set delay budget (PSDB) parameter in the PCC rules for the scheduled uplink transmission of the service.

[0588] Update the PCC rules for the scheduled downlink transmission of services, including updating the PDB and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of services.

[0589] In one possible implementation, the PCF can adjust the PDB and / or PSDB parameters of the uplink transmission, and / or adjust the PDB and / or PSDB parameters of the downlink transmission based on the AF session update information.

[0590] In one possible implementation, updating the PCC rules for the scheduled uplink transmission of the service includes updating 5QI in the PCC rules for the scheduled uplink transmission of the service.

[0591] In one possible implementation, updating the PCC rules for the scheduled downlink transmission of the service includes updating 5QI in the PCC rules for the scheduled downlink transmission of the service.

[0592] For example, the PCF can authorize new PDB parameters for uplink transmissions and / or downlink transmissions based on AF session update information (e.g., a new 5QI corresponding to the PDB can be selected).

[0593] The order of the steps listed in the above embodiments of the UPF-side information transmission method is not intended to limit the execution order of each step. Each step can be executed in the order listed, or it can be executed in a different order if there is no contradiction. Each step can be implemented as a separate embodiment if there is no contradiction, or multiple steps can be combined as an embodiment.

[0594] In each embodiment, the information transmission methods performed on the PCF side, UPF side, AF side and access network side can be one-to-one corresponding. Therefore, the same explanations or features will not be repeated one by one, and the embodiments of the corresponding side can be referred to.

[0595] like Figure 16 As shown, this exemplary embodiment provides an information transmission method, which can be executed by an access network device, including:

[0596] Step 1601: Receive the association identifier of the pre-ordered service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the pre-ordered service data stream.

[0597] Reservation services include, but are not limited to, XRM services.

[0598] In one possible implementation, the associated identifier of the subscribed service is received, including at least one of the following:

[0599] The associated identifier for receiving pre-booked services directly;

[0600] The associated identifier for receiving pre-booked services is received indirectly.

[0601] In one possible implementation, receiving the associated identifier of a pre-booked service directly includes receiving the associated identifier of the pre-booked service directly from the PCG.

[0602] In one possible implementation, the associated identifier of the pre-booked service is sent indirectly, including receiving the associated identifier of the pre-booked service sent by the PCF through the SMF.

[0603] In one possible implementation, the scheduled service can have a bidirectional data stream.

[0604] In one possible implementation, the association identifier may include any of the following: Correlation ID; Peer ID; Round Trip Group ID; Peer Indication; Common ID. The name of the association identifier is not limited here.

[0605] In one possible implementation, the associated identifier can be generated based on the common identifier, or the associated identifier can be obtained by mapping based on the common identifier.

[0606] In one possible implementation, the association identifier is associated with the transmission delay parameters of the uplink transmission of the predetermined service data stream; and the association identifier is associated with the transmission delay parameters of the downlink transmission of the predetermined service data stream. That is, the core network functional node or access network device can determine the transmission delay parameters of the uplink transmission and the downlink transmission of the predetermined service data stream through the association identifier.

[0607] Transmission delay parameters may include, but are not limited to, delay configuration parameters associated with data stream transmission.

[0608] The transmission delay parameter may include at least one of the following: transmission delay; PDB; PSDB. PDB and / or PSDB may belong to 5QI. PSDB defines the upper limit of the transmission delay of the PDU set between the N6 endpoint at the UE and UPF.

[0609] In one possible implementation, the PCF can determine the uplink transmission delay of the data stream and / or the uplink transmission delay of the data stream based on the transmission delay parameters of the bidirectional transmission of the predetermined service data stream. The bidirectional transmission delay parameters of the predetermined service data stream can be indicated to the PCF by the AF associated with the predetermined service.

[0610] In one possible implementation, the AF can send the transmission delay parameters for bidirectional transmission of the predetermined service data stream to the PCF via the NEF.

[0611] In one possible implementation, the bidirectional transmission delay parameter can characterize the maximum allowable transmission delay of a predetermined service data stream during uplink and downlink transmission.

[0612] In one possible implementation, the transmission delay of the uplink data stream and the sum of the uplink transmission delays of the data stream are less than or equal to the transmission delay of the bidirectional transmission of the predetermined service data stream.

[0613] In one possible implementation, the association identifier is associated with at least one of the following:

[0614] Transmission delay parameters of the uplink service data stream for the pre-booked service;

[0615] Transmission delay parameters for the downlink service data stream of the pre-booked service;

[0616] Transmission delay parameters for the QoS stream of the pre-booked service;

[0617] PCC associated with pre-booked business;

[0618] 5QI related to pre-booking business.

[0619] In one possible implementation, PCF can generate associated identifiers based on a predetermined strategy.

[0620] In one possible implementation, an association identifier can be associated with a pre-booked service, or an association identifier can be associated with a class of pre-booked services.

[0621] In one embodiment, determining the associated identifier of the pre-booked service includes:

[0622] The association identifier must be determined based on at least one of the following:

[0623] Transmission delay parameters for bidirectional transmission of the scheduled business data stream;

[0624] Contract information associated with the pre-booked service;

[0625] Carrier strategies associated with pre-booked services.

[0626] In one possible implementation, the requirements of the scheduled service for transmission delay parameters may include at least one of the following: transmission delay parameter requirements of the scheduled service for bidirectional transmission of the data stream; transmission delay parameter requirements of the scheduled service for uplink transmission of the data stream; and transmission delay parameter requirements of the scheduled service for downlink transmission of the data stream.

[0627] In one possible implementation, the PCF can determine the bidirectional transmission delay rules or 5QI updates that the network supports for the pre-defined services based on the transmission delay parameters (i.e., transmission delay parameter requirements), subscription information, or operator policies, and then generate an associated identifier.

[0628] In one possible implementation, the association identifier can be determined based on one or more of the transmission delay parameters of bidirectional transmission, the subscription information of the pre-ordered service association, and the operator policy of the pre-ordered service association.

[0629] For example, associated identifiers can be assigned based on carrier policies. Carrier policies contain the rules for assigning associated identifiers.

[0630] In related technologies, the uplink and downlink transmissions of the scheduled business data stream are independent of each other, and the transmission delay parameters of the uplink transmission are not correlated, making it impossible to achieve coordinated adjustment of the uplink transmission delay parameters.

[0631] The association identifier is used to associate the transmission delay parameters of uplink transmission and downlink transmission. Core network elements and / or access network devices can determine the transmission delay parameters of uplink transmission and downlink transmission based on the association identifier, and perform coordinated processing of the transmission delay parameters of uplink transmission and downlink transmission, thereby improving the coordination efficiency of the transmission delay parameters of uplink transmission and downlink transmission, thus meeting the bidirectional transmission delay requirements of the scheduled services and improving the success rate of scheduled service transmission.

[0632] In one embodiment, the association identifier is indicated by the policy control and billing PCC rules carried by the policy control function (PCF) and sent to the session management function (SMF) for the predetermined service association.

[0633] In one possible implementation, the association identifier can be carried in the PCC rule.

[0634] In one possible implementation, the PCC rule can carry index information of the associated identifier, which is used to retrieve the corresponding associated identifier in the index table of associated identifiers.

[0635] In one possible implementation, the PCC rules include at least one of the following: PCC rules for uplink transmission; PCC rules for downlink transmission.

[0636] For example, when the PCF sends a PCC rule to the SMF, it can simultaneously send an association identifier for associating uplink transmission delay parameters and / or downlink transmission delay parameters; the SMF can then send the association identifier to the RAN and UPF.

[0637] In one possible implementation, the PCF can send the association identifier to the SMF within the PCC rule, and the SMF can then extract the association identifier and send it to the access network device and / or UPF.

[0638] In one possible implementation, PCF can add a field within the PCC rule to carry the association identifier.

[0639] In one possible implementation, the PCF can be within existing fields of the PCC rule, such as the service data flow template or the 5G QoS identifier.

[0640] In one possible implementation, the PCF can send the association identifier separately to the SMF, which then forwards it to the access network device and / or the UPF.

[0641] like Figure 17 As shown, this exemplary embodiment provides an information transmission method, which can be executed by an access network device, including:

[0642] Step 1701: Send the uplink QoS latency monitoring report and the downlink QoS latency monitoring report to the PCF via the UPF. The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using an association identifier.

[0643] In one possible implementation, the QoS latency monitoring reports for uplink transmission and downlink transmission are used by the PCF to update the PCC rules for the uplink transmission and / or the PCC rules for the downlink transmission of the scheduled service.

[0644] Access network devices can monitor the transmission delay parameters of uplink and / or downlink transmissions, and send uplink and downlink QoS delay monitoring reports to the PCF. The PCF then adjusts the PCC rules for uplink and / or downlink transmissions based on the received QoS delay monitoring reports, so that the transmission of data streams can adapt to the current network conditions.

[0645] In one possible implementation, the QoS latency monitoring report for uplink transmission can be used to indicate the transmission latency parameters of the current uplink transmission; the QoS latency monitoring report for downlink transmission can be used to indicate the transmission latency parameters of the current downlink transmission.

[0646] In one possible implementation, updating the PCC rules for the scheduled uplink transmission and / or the PCC rules for the scheduled downlink transmission includes at least one of the following:

[0647] Adjust the PCC rules for uplink transmission and / or downlink transmission;

[0648] Create new PCC rules for uplink transmissions and / or PCC rules for downlink transmissions.

[0649] For example, the PCF can update the PCC rules for the uplink transmission of the scheduled service and / or the PCC rules for the downlink transmission of the scheduled service, so that the uplink transmission delay of the data stream and the sum of the uplink transmission delays of the data stream are less than or equal to the delay requirements for the bidirectional transmission of the data stream.

[0650] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the access network device after monitoring the uplink transmission latency parameters, determining that the monitored uplink transmission latency parameters meet the triggering condition of the second uplink subscription event, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0651] And / or,

[0652] The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are sent by the access network equipment to monitor the downlink transmission latency parameters, determine that the monitored downlink transmission latency parameters meet the triggering conditions of the second downlink subscription event, and identify the associated uplink QoS latency monitoring report through the association identifier.

[0653] For example, if an access network device detects that the uplink transmission latency parameters meet the triggering conditions of an uplink subscription event, it can send a latency monitoring report to the PCF. The UPF can include the monitored uplink transmission latency parameters in the uplink QoS latency monitoring report. The UPF can also determine the corresponding downlink QoS latency monitoring report based on the association identifier of the uplink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the subscribed service's downlink transmission. For example, triggering the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0654] For example, if an access network device monitors downlink transmission latency parameters and finds that these parameters meet the triggering conditions for a downlink subscription event, it can send a latency monitoring report to the PCF. The UPF can include the monitored downlink transmission latency parameters in its downlink QoS latency monitoring report. The UPF can also determine the corresponding uplink QoS latency monitoring report based on the association identifier of the downlink QoS latency monitoring report. The UPF can send both the uplink and downlink QoS latency monitoring reports to the PCF and / or AF, thereby triggering the PCF to update the uplink PCC rules and / or the PCC rules for the scheduled downlink service. For example, this could trigger the PCF to authorize new uplink PDB parameters and / or downlink PDB parameters.

[0655] In one embodiment, updating the PCC rules for the scheduled uplink transmission of the service includes: updating the packet unit delay budget (PDB) parameter and / or packet unit set delay budget (PSDB) parameter in the PCC rules for the scheduled uplink transmission of the service.

[0656] Update the PCC rules for the scheduled downlink transmission of services, including updating the PDB and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of services.

[0657] Update the PCC rules for the scheduled downlink transmission of services, including updating the PDB and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of services.

[0658] In one possible implementation, the PCF can adjust the PDB and / or PSDB parameters of the uplink transmission, and / or adjust the PDB and / or PSDB parameters of the downlink transmission based on the AF session update information.

[0659] In one possible implementation, updating the PCC rules for the scheduled uplink transmission of the service includes updating 5QI in the PCC rules for the scheduled uplink transmission of the service.

[0660] In one possible implementation, updating the PCC rules for the scheduled downlink transmission of the service includes updating 5QI in the PCC rules for the scheduled downlink transmission of the service.

[0661] For example, the PCF can authorize new PDB parameters for uplink transmissions and / or downlink transmissions based on AF session update information (e.g., a new 5QI corresponding to PDBPDB can be selected).

[0662] Combination Figure 16 and Figure 17 Examples, such as Figure 18 As shown, this exemplary embodiment provides an information transmission method, which can be executed by an access network device, including:

[0663] Step 1801: Receive the association identifier of the pre-ordered service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the pre-ordered service data stream.

[0664] Step 1802: Send the uplink QoS latency monitoring report and the downlink QoS latency monitoring report to the PCF via the UPF. The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using an association identifier.

[0665] Figure 18 Implementation examples, including Figure 16 Examples and Figure 17 The content of the embodiments. Therefore, the same explanations or features will not be repeated one by one, and can be referred to the embodiments on the corresponding side.

[0666] The order of steps listed in the above embodiments of the information transmission method on the access network device side is not intended to limit the execution order of each step. Each step can be executed in the order listed, or it can be executed in a different order if there is no contradiction. Each step can be implemented as a separate embodiment if there is no contradiction, or multiple steps can be combined as an embodiment.

[0667] In each embodiment, the information transmission methods performed on the PCF side, UPF side, AF side and access network side can be one-to-one corresponding. Therefore, the same explanations or features will not be repeated one by one, and the embodiments of the corresponding side can be referred to.

[0668] The following provides a specific example in conjunction with any of the above embodiments:

[0669] PCF adds a Correlation ID for bidirectional (Round Trip, RT) transmission to the uplink and downlink data flows of XRM services. The Correlation ID can include one of the following: Peer ID; Round Trip Group ID; Peer Indication; or Common ID. The Correlation ID is used to associate the uplink and downlink Service Data Flow (SDF), Quality of Service (QoS) flow, Policy Control and Charging (PCC) rules, and 5G Quality of Service Indicators (5QI) (e.g., PDB) parameters, i.e., transmission latency parameters, for this bidirectional transmission. When the PCF issues the PCC rule to the SMF, it also issues the association identifier for the bidirectional transmission. The SMF issues the association identifier to the RAN and UPF. When the RAN and UPF send the QoS monitoring notification for downlink (DL) / uplink (UL) latency, they also send the UL / DL latency identified by the association identifier to the PCF / AF.

[0670] Optionally, the PCF divides the bidirectional transmission latency into uplink PDB and downlink PDB, generating two PCC rules corresponding to the uplink SDF and downlink SDF, and allocating 5 QIs to each rule based on the corresponding PDB. The two PCC rules are associated with the Quality of Service (QoS) monitoring policy to monitor uplink latency and downlink latency respectively.

[0671] Optionally, when the PCF sends the PCC rule to the SMF, it also sends the association identifiers for the uplink and downlink SDF / QoS streams / PCC rules / 5QI (PDB) associated with the bidirectional transmission; the SMF sends the association identifiers to the RAN and UPF.

[0672] Optionally, the RAN and UPF associate uplink and downlink SDF / QoS streams / 5QI (PDB) based on the association identifier and send a correlation notification to the PCF / AF, so that the PCF / AF can initiate session modifications (e.g., for the AF to update bidirectional transmission latency requirements, or for the PCF to update uplink and / or downlink PCC rules / PDB).

[0673] Furthermore, when the RAN detects that the latency QoS monitoring of the UL SDF / QoS flow / 5QI meets the subscription event, it needs to send a notification to the UPF. Simultaneously, the RAN sends the latency QoS monitoring report of the DL SDF / QoS flow / 5QI identified by the associated identifier to the UPF. The RAN sends UL and DL QoS monitoring reports (i.e., uplink and downlink QoS latency monitoring reports) to the UPF / PCF; triggering uplink and / or downlink PCC rule updates; optionally, the PCF authorizes new uplink / downlink PDBs, updating the PCC rule to the corresponding PDB (which can be new 5QIs corresponding to the selected PDB). The method by which the RAN sends QoS monitoring reports for downlink latency is similar to that for uplink latency, and will not be described further here.

[0674] Furthermore, when the UPF detects that the latency QoS monitoring of the UL SDF / QoS stream / 5QI meets the subscription event, it needs to send a notification to the PCF / AF. Simultaneously, the UPF sends the latency QoS monitoring report of the DL SDF / QoS stream / 5QI identified by the associated identifier to the PCF / AF. The UPF sends UL and DL QoS monitoring reports (i.e., uplink and downlink QoS latency monitoring reports) to the PCF / AF, triggering uplink and / or downlink PCC rule updates. Optionally, the PCF authorizes new uplink / downlink PDBs and updates the PCC rule corresponding to the PDB (which can be new 5QIs corresponding to the selected PDB). The way the UPF sends QoS monitoring reports for downlink latency is similar to the way the RAN sends QoS monitoring reports for uplink latency, and will not be described further here.

[0675] Furthermore, the PCF can directly initiate rule updates (such as PCC rules) or send QoS monitoring reports to the AF to trigger AF session modifications, thereby indirectly initiating rule updates.

[0676] Optionally, the PCF can carry the association identifier within or outside the PCC rule; furthermore, new parameters such as Correlation ID / RT indication / Peer ID / Round TripGroup ID / Peer Indication can be added to the PCC rule, or the Correlation ID / RTindication / Peer ID / Round Trip Group ID / Peer Indication (e.g., service data flow template, or 5G QoS identifier) ​​can be carried implicitly through existing parameters.

[0677] Optionally, based on bidirectional transmission delay requirements, the PCF can divide bidirectional transmission into uplink packet delay budget (ULPDB) and downlink packet delay budget (DLPDB). The UL PDB and DL PDB can be different, but their sum cannot exceed the bidirectional transmission delay. The PCF decision generates an association identifier, associating the UL SDF / QoS flow / PCC rule / 5QI (PDB) and the DL SDF / QoS flow / PCC rule / 5QI (PDB).

[0678] Optionally, the PCF can adjust the UL PDB and DL PDB based on the QoS monitoring report. That is, the PCF can adjust the uplink and / or downlink PCC rules (e.g., UL PDB and / or DL ​​PDB, UL 5QI and / or DL5QI) based on the latency QoS monitoring reports of DL and UL.

[0679] Optionally, the PCF generates an association identifier based on the bidirectional transmission latency requirement indication (RT latency requirement indication), and / or XRM service subscription information, and / or operator policies. For example, if the requirement indication, service subscription, or operator policy supports rules or 5QI updates for bidirectional transmission latency, an association identifier is generated to identify uplink and downlink SDF / QoS flows / PCC rules / 5QI (PDB).

[0680] Optionally, the PCF can adjust uplink and / or downlink PCC rules (such as UL PDB and / or DLPDB, UL 5QI and / or DL ​​5QI) based on the QoS monitoring report. This can be done by the PCF directly triggering PCC rule updates, or by the PCF notifying the QoS monitoring report to the AF so that the AF can trigger PCC rule updates.

[0681] Optionally, the PCF can directly or indirectly trigger a PCC rule update. If the corresponding PDB can be updated, allocate the corresponding 5QI to the updated PDB.

[0682] Optionally, the AF provides bidirectional latency requirement information to the PCF. (The AF can provide this requirement information to the PCF through the following process:)

[0683] 1) During the AF session, the AF provides the PCF with bidirectional transmission latency requirements and the required QoS parameters.

[0684] 2) AF session flow with required QoS update procedures.

[0685] 3) Service specific parameter configuration process.

[0686] 4) The process of configuring policies for subsequent AF sessions.

[0687] The AF provides bidirectional latency requirement information to the PCF, either directly or indirectly; indirect transmission includes:

[0688] 1) Send to PCF via NEF.

[0689] 2) Sent to PCF via TSCTSF,

[0690] 3) Send to PCF via TSCTSF and NEF.

[0691] Please refer to the following example description for details:

[0692] Figure 19 The procedure for setting up an AF session with required QoS parameters includes the following steps:

[0693] Step 1901: The AF sends an AF session resource request, for example, by creating an AF request via a "Nnef_AFsessionWithQoS_Create request". The AF carries the bidirectional latency requirements (including round-trip latency or two-way delay budget) of the XRM service-related media data stream in the request message. Bidirectional latency can include uplink latency and / or downlink latency, or uplink latency PDB or downlink latency PDB;

[0694] Optionally, the AF session resource request carries XRM service information, including a common ID identifying the XRM service data flow group, UE address / UE identifier, AF Identifier ApplicationID, flow description(s), data network name (DNN), single network slice selection assistance information (S-NSSAI), QoS parameters, and other relevant information. Here, the common ID can be used to identify all flows within the XRM service group.

[0695] Step 1902: NEF Authorizes AF Request. If it is an untrusted AF, the NEF sends the AF request to the PCF. (Optionally, the NEF performs relevant mappings, including mapping of the XRM service identifier (AF-service-identifier) ​​to the DNN and S-NSSAI, mapping of external applications to core network application identifiers; and mapping of subscription information based on Unified Data Management (UDM), mapping of external UE identifiers to internal UE identifiers (such as Subscription Permanent Identifier (SUPI)), and mapping of external to internal XRM service group identifiers based on UDM subscription information.)

[0696] Step 1903: The NEF authorizes the AF request and decides whether to call the TSCTSF or directly contact the PCF based on the parameters provided by the AF. The PCF receives the attributes provided by the AF from the NEF or TSCTSF. The NEF triggers the Npcf_PolicyAuthorization_Create request, sending the AF request to the PCF, carrying bidirectional latency requirement information for the PCF's policy decision. The message carries XRM service-related information from the AF request;

[0697] Step 1904: The PCF makes a policy decision. The PCF may decide that updated or new policy information needs to be sent to the SMF.

[0698] A new RT Correlation ID has been added to the uplink and downlink data streams of the XRM service: PeerID / Round Trip Group ID / Peer Indication. This correlation ID is used to associate the uplink and downlink SDF / QoS streams / PCC rules / 5QI (PDB) of the Round Trip. When the PCF issues a PCC rule to the SMF, it also issues this RT Correlation ID. The SMF issues the Correlation ID to the RAN and UPF. When the RAN and UPF send the DL latency QoS monitoring notification (i.e., QoS latency monitoring report), they also send the UL latency QoS monitoring notification identified by the correlation ID to the PCF / AF. When the RAN and UPF send the UL latency QoS monitoring notification, they also send the DL latency QoS monitoring notification identified by the correlation ID to the PCF / AF.

[0699] The PCF adds a Round Trip (RT) Correlation ID to the uplink and downlink data flows of XRM services. The Correlation ID can include one of the following: Peer ID; Round Trip Group ID; or Peer Indication. The Correlation ID is used to associate the uplink and downlink Service Data Flow (SDF), Quality of Service (QoS) flow, Policy Control and Charging (PCC) rules, and 5G Quality of Service Indicators (5QIs) (e.g., PDB) of the bidirectional transmission. When the PCF issues PCC rules to the SMF, it also issues the Correlation ID for the bidirectional transmission. The SMF issues the Correlation ID to the RAN and UPF. When the RAN and UPF send downlink (DL) / uplink (UL) latency QoS monitoring notifications, they also send the UL / DL latency identified by the Correlation ID to the PCF / AF.

[0700] Optionally, the PCF divides the bidirectional transmission latency into uplink PDB and downlink PDB, generating two PCC rules corresponding to the uplink and downlink SDBs, and allocating 5 QIs to each rule based on the corresponding PDB. The two PCC rules are then associated with a Quality of Service (QoS) monitoring policy to monitor uplink and downlink latency.

[0701] Optionally, when the PCF issues the PCC rule to the SMF, it also issues a bidirectional transmission association identifier associated with the uplink and downlink SDF / QoS stream / PCC rule / 5QI (PDB) of the bidirectional transmission; the SMF issues the association identifier to the RAN and UPF.

[0702] Optionally, the RAN and UPF associate uplink and downlink SDF / QoS flows / 5QI (PDB) based on the association identifier and send a correlation notification to the PCF / AF, which allows the PCF / AF to initiate session modifications (e.g., for the AF to update bidirectional transmission latency requirements, or for the PCF to update uplink and / or downlink PCC rules / PDB).

[0703] Furthermore, when the RAN detects that the latency QoS monitoring of the UL SDF / QoS flow / 5QI meets the subscription event, it needs to send a notification to the UPF. Simultaneously, the RAN sends the latency QoS monitoring report of the DL SDF / QoS flow / 5QI identified by the associated identifier to the UPF. The RAN sends UL and DL QoS monitoring reports to the UPF / PCF, triggering uplink and / or downlink PCC rule updates. Optionally, the PCF authorizes new uplink / downlink PDBs and updates the PDB corresponding to the PCC rules (which can be new 5QIs corresponding to the selected PDB). The method by which the RAN sends QoS monitoring reports for downlink latency is similar to the method by which the RAN sends QoS monitoring reports for uplink latency, and will not be described further here.

[0704] Furthermore, when the UPF detects that the latency QoS monitoring of the UL SDF / QoS flow / 5QI meets the subscription event, it needs to send a notification to the PCF / AF. Simultaneously, the UPF sends the latency QoS monitoring report of the DL SDF / QoS flow / 5QI identified by the Correlation ID to the PCF / AF. The UPF sends UL and DL QoS monitoring reports to the PCF / AF, triggering uplink and / or downlink PCC rule updates. Optionally, the PCF authorizes new uplink / downlink PDBs and updates the PCC rule corresponding to the PDB (which can be new 5QIs corresponding to the selected PDB). The way the UPF sends QoS monitoring reports for downlink latency is similar to the way the RAN sends QoS monitoring reports for uplink latency, and will not be described further here.

[0705] Furthermore, the PCF can directly initiate rule updates (such as PCC rules) or send QoS monitoring reports to the AF to trigger AF session modifications, thereby indirectly initiating rule updates.

[0706] Optionally, the PCF can carry the correlation identifier within or outside the PCC rule; furthermore, it can add correlation ID / RT indication / Peer ID / Round TripGroup ID / Peer Indication parameters to the PCC rule, or implicitly carry the correlation ID / RT indication / Peer ID / Round Trip Group ID / Peer Indication (service data flow template, or 5G QoS identifier) ​​through existing parameters.

[0707] Optionally, based on bidirectional transmission delay requirements, the PCF can divide bidirectional transmission into uplink packet delay budget (ULPDB) and downlink packet delay budget (DLPDB). The UL PDB and DL PDB can be different, but their sum cannot exceed the bidirectional transmission delay. The PCF generates an association identifier, associating the UL SDF / QoS flow / PCC rule / 5QI (PDB) and the DL SDF / QoS flow / PCC rule / 5QI (PDB).

[0708] Optionally, the PCF can adjust the UL PDB and DL PDB based on QoS monitoring reports. That is, the PCF can adjust uplink and / or downlink PCC rules (e.g., UL PDB and / or DL ​​PDB, UL 5QI and / or DL5QI) based on latency QoS monitoring reports from DL and UL.

[0709] Optionally, the PCF generates an association identifier based on the bidirectional transmission latency requirement indication (RT latency requirement indication), and / or XRM service subscription information, and / or operator policies. For example, if the requirement indication, service subscription, or operator policy supports rules or 5QI updates for bidirectional transmission latency, an association identifier is generated to identify uplink and downlink SDF / QoS flows / PCC rules / 5QI (PDB).

[0710] Optionally, the PCF can adjust uplink and / or downlink PCC rules (e.g., UL PDB and / or DLPDB, UL 5QI and / or DL ​​5QI) based on the QoS monitoring report. This can be done by the PCF directly triggering PCC rule updates, or by the PCF notifying the QoS monitoring report to the AF so that the AF can trigger PCC rule updates.

[0711] Optionally, the PCF can directly or indirectly trigger a PCC rule update. If the corresponding PDB can be updated, allocate the corresponding 5QI to the updated PDB.

[0712] Optionally, the AF provides bidirectional latency requirement information to the PCF. (The AF can provide this requirement information to the PCF through the following process:)

[0713] 1) During the AF session, the AF provides the PCF with bidirectional transmission latency requirements and the required QoS parameters.

[0714] 2) AF session flow with required QoS update procedures.

[0715] 3) Service specific parameter configuration process.

[0716] 4) The process of configuring policies for subsequent AF sessions.

[0717] The AF provides bidirectional latency requirement information to the PCF, either directly or indirectly; indirect transmission includes:

[0718] 1) Send to PCF via NEF.

[0719] 2) Sent to PCF via TSCTSF,

[0720] 3) Send to PCF via TSCTSF and NEF.

[0721] Step 1905: PCF sends an "Npcf_Policy Authorization_Create response" to NEF.

[0722] Step 1906: NEF sends an "Nnef_AFsessionWithQoS_Create response" message to AF, carrying the feedback result and informing whether authorization has been requested.

[0723] Step 1907: PCF sends an “Npcf_SMPolicyControl_UpdateNotify request” to SMF to initiate an SM policy association modification request (PCC rule (QoS monitoring policy)).

[0724] Based on the QoS monitoring policy measured from the PCF, the SMF generates a QoS monitoring configuration for the UPF (or RAN if necessary), as described in step 1907.

[0725] When the PCF issues the PCC rule to the SMF, it also issues the bidirectional transmission association identifier; the SMF then issues the association identifier to the RAN and UPF.

[0726] Optionally, the PCF can carry the association identifier within or outside the PCC rule; furthermore, it can add Correlation ID / RT indication / Peer ID / Round Trip Group ID / PeerIndication parameters within the PCC rule, or implicitly carry Correlation ID / RT indication / PeerID / Round Trip Group ID / Peer Indication (service data flow template, or 5G QoS identifier) ​​through existing parameters.

[0727] Step 1908: The SMF responds to the PCF with a modified response associated with the SM policy (Npcf_SMPolicyControl_UpdateNotify response).

[0728] Step 1909: SMF initiates an N4 session modification request (QoS monitoring configuration) to UPF.

[0729] Based on the association identifier, UPF associates uplink and downlink SDF / QoS streams / 5QI (PDB) and sends a correlation notification to PCF / AF, which allows PCF / AF to initiate session modifications (e.g., for AF to update bidirectional transmission latency requirements, or for PCF to update uplink and / or downlink PCC rules / PDB).

[0730] When the UPF detects that the latency QoS monitoring of the UL SDF / QoS stream / 5QI meets the subscription event, it needs to send a notification to the PCF / AF. Simultaneously, the UPF sends a latency QoS monitoring report of the DL SDF / QoS stream / 5QI identified by the associated identifier to the PCF / AF. The UPF sends UL and DL QoS monitoring reports to the PCF / AF, triggering uplink and / or downlink PCC rule updates. Optionally, the PCF authorizes a new uplink / downlink PDB, and the updated PCC rules correspond to the PDB (which may be new 5QIs corresponding to the PDB).

[0731] Step 1910: Upon receiving the QoS monitoring configuration, the UPF enables measurement and reporting. The UPF responds to the SMF.

[0732] Step 1911: For the modifications required by SMF, SMF calls Namf_Communication_N1N2MessageTransfer([N2 SM information](PDU session ID, QFI(s), QoS Profile(s), QoS monitoring configuration), N1 SM container)

[0733] Step 1912: The AMF can send N2 ([N2 SM information received from SMF], NAS message (PDU session ID, N1 SM container (PDU session modification command)) to the (R)AN. Upon receiving the QoS monitoring configuration, the RAN enables event measurement and reporting (e.g., the RAN detects UL latency and DL latency, and the sum of UL PDB and DL PDB as bidirectional latency).

[0734] Based on the association identifier, the RAN associates the uplink and downlink SDF / QoS flows / 5QI(PDB) and sends a correlation notification to the PCF / AF, so that the PCF / AF can initiate session modifications (e.g., for the AF to update bidirectional transmission latency requirements, or for the PCF to update uplink and / or downlink PCC rules / PDB).

[0735] Furthermore, when the RAN detects that the latency QoS monitoring of the UL SDF / QoS flow / 5QI meets the subscription event, it needs to send a notification to the UPF. Simultaneously, the RAN sends the latency QoS monitoring report of the DL SDF / QoS flow / 5QI identified by the associated identifier to the UPF. The RAN sends UL and DL QoS monitoring reports to the UPF / PCF; triggering uplink and / or downlink PCC rule updates; optionally, the PCF authorizes new uplink / downlink PDBs, and the updated PCC rules correspond to the PDBs (which may be new 5QIs corresponding to the PDBs).

[0736] Step 1913: The RAN configures the transmission resources.

[0737] Step 1914: The RAN can acknowledge the N2 PDU session request by sending an N2 PDU session Ack message to the AMF.

[0738] Step 1915: The AMF forwards the N2 SM information received from the AN to the SMF through the "Nsmf_PDUSession_UpdateSMContext request" service operation.

[0739] Step 1916: SMF responds with an "Nsmf_PDUSession_UpdateSMContext response".

[0740] Steps 1917-1918: The SMF can update the N4 session of the UPF involved in the PDU session update by sending an "N4 Session Modification Request" message to the UPF. When the PCF subsequently receives the QoS monitoring report, the PCF will process it as follows:

[0741] Based on QoS monitoring reports, PCF adjusts uplink and / or downlink PCC rules (e.g., UL PDB and / or DL ​​PDB, UL5QI and / or DL ​​5QI). This can directly trigger PCC rule updates for PCF, or PCF can notify QoS monitoring reports to AF for AF to trigger PCC rule updates.

[0742] Optionally, the PCF can directly or indirectly trigger a PCC rule update. If the corresponding PDB can be updated, allocate the corresponding 5QI to the updated PDB.

[0743] Optionally, the AF provides bidirectional latency requirement information to the PCF. (The AF can provide this requirement information to the PCF through the following process:)

[0744] 1) During the AF session, the AF provides the PCF with bidirectional transmission latency requirements and the required QoS parameters.

[0745] 2) AF session flow with required QoS update procedures.

[0746] 3) Service specific parameter configuration process.

[0747] 4) The process of configuring policies for subsequent AF sessions.

[0748] The AF provides bidirectional latency requirement information to the PCF, either directly or indirectly; indirect transmission includes:

[0749] 1) Send to PCF via NEF.

[0750] 2) Sent to PCF via TSCTSF,

[0751] 3) Send to PCF via TSCTSF and NEF.

[0752] The process of reporting the QoS monitoring report to the AF can be as follows: Figure 20 As shown, this illustrates the user plane notification process from UPF to AF, or the control plane process from UPF to SMF to PCF.

[0753] The order of the steps listed in the above embodiments is not intended to limit the execution order of each step. Each step can be executed in the order listed, or it can be executed in a different order if there is no contradiction. Each step can be implemented as a separate embodiment if there is no contradiction, or multiple steps can be combined as an embodiment.

[0754] Figure 20 The notification process includes the following steps:

[0755] Step 2001: When an event is detected / reached, a report will be triggered (such as reaching a threshold or a periodic timer timeout). UPF triggers the "Nupf_EventExposure_Notify" message to report the measurement information.

[0756] Step 2002: The UPF sends a Nupf_EventExposure_Notify message (measuring bidirectional latency budget status information) to the NEF. The UPF reports the QoS latency monitoring report to the AF (via the NEF) to trigger the corresponding session update, or the UPF sends the QoS latency monitoring report to the PCF (via the SMF) for the PCF to trigger rule updates. The PCF reports to the AF to trigger an update or triggers an update locally; see details in [link to relevant documentation]. Figure X The corresponding rule update description.

[0757] Step 2003: NEF sends the "Nnef_Nnef_EventExposure_Notify" (measured bidirectional delay budget status information) message to AF.

[0758] The order of the steps listed in the above embodiments is not intended to limit the execution order of each step. Each step can be executed in the order listed, or it can be executed in a different order if there is no contradiction. Each step can be implemented as a separate embodiment if there is no contradiction, or multiple steps can be combined as an embodiment.

[0759] like Figure 21 As shown, this exemplary embodiment provides an information transmission device 100, wherein a policy control function (PCF) is configured to include:

[0760] Processing module 110 is configured to determine and send an association identifier for a pre-defined service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the downlink transmission of the pre-defined service data stream.

[0761] In one embodiment, the association identifier is sent by the PCF to the Session Management Function (SMF), and by the SMF to at least one of the following:

[0762] Access network equipment;

[0763] User-facing features (UPF).

[0764] In one embodiment, the association identifier is indicated by the policy control and billing PCC rules associated with the pre-defined service.

[0765] In one embodiment, the apparatus further includes:

[0766] After being configured as the association identifier for sending the predetermined service, the transceiver module 120 receives the QoS latency monitoring report for uplink transmission and the QoS latency monitoring report for downlink transmission, wherein the QoS latency monitoring report for uplink transmission and the QoS latency monitoring report for downlink transmission are associated using the association identifier.

[0767] The processing module 110 is further configured to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service based on the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission.

[0768] In one embodiment, the transceiver module 120 is further configured to send the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report to the AF associated with the predetermined service.

[0769] The transceiver module 120 is further configured to receive AF session update information sent by the AF in response to the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission;

[0770] The processing module 110 is further configured to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service based on the AF session update information.

[0771] In one embodiment, the transceiver module 120 is specifically configured to include at least one of the following:

[0772] Receive the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission sent by the UPF;

[0773] The system receives the QoS latency monitoring reports for the uplink and downlink transmissions sent by the access network device through the UPF.

[0774] In one embodiment, the apparatus further includes:

[0775] The transceiver module 120 is configured to receive AF session update information sent by the application function AF associated with the predetermined service in response to the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report; wherein the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent to the AF by the UPF;

[0776] The processing module 110 is further configured to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service based on the AF session update information.

[0777] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the uplink subscription event triggering conditions, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0778] and / or

[0779] The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network equipment after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the downlink subscription event triggering conditions, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

[0780] In one embodiment, updating the PCC rules for the predetermined service uplink transmission includes: updating the packet unit delay budget (PDB) parameter and / or packet unit set delay budget (PSDB) parameter in the PCC rules for the predetermined service uplink transmission.

[0781] The step of updating the PCC rules for the scheduled downlink transmission of the service includes updating the PDB parameters and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of the service.

[0782] In one embodiment, determining the associated identifier of the pre-booked service includes:

[0783] The association identifier is determined based on at least one of the following:

[0784] The transmission delay parameters for the bidirectional transmission of the predetermined service data stream;

[0785] The contract information associated with the pre-booked service;

[0786] The operator strategy associated with the pre-booked service.

[0787] In one embodiment, the processing module 110 is further configured to:

[0788] Based on the transmission delay parameters of the bidirectional transmission of the predetermined service data stream, determine the transmission delay parameters of the uplink transmission of the data stream and / or the transmission delay parameters of the downlink transmission of the data stream.

[0789] In one embodiment, the scheduled service includes at least one of the following:

[0790] Augmented Reality Multimedia XRM services;

[0791] Multimodal services.

[0792] like Figure 22 As shown, this exemplary embodiment provides an information transmission device 200, wherein, disposed in an application function AF, it includes:

[0793] The transceiver module 210 is configured to send transmission delay parameters for bidirectional transmission of a predetermined service to the policy control function (PCF). The bidirectional transmission delay parameters are used by the PCF to determine the association identifier of the predetermined service, and are used to associate the transmission delay parameters for uplink transmission and downlink transmission of the predetermined service data stream.

[0794] In one embodiment, the association identifier is sent by the PCF to at least one of the following via the Session Management Function (SMF): the access network device; and the User Plane Function (UPF).

[0795] In one embodiment, the association identifier is carried in the policy control and billing PCC rules of the predetermined service association sent by the PCF to the SMF.

[0796] In one embodiment, the transceiver module 210 is further configured to receive the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission sent by the User Plane Function (UPF) or PCF.

[0797] In one embodiment, the apparatus further includes a processing module 220 configured to:

[0798] Based at least on the QoS latency monitoring reports of the uplink transmission and the downlink transmission, it is determined whether to send AF session update information to the PCF.

[0799] In one embodiment, the AF session update information is used by the PCF to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service.

[0800] In one embodiment, the AF session update information is used to indicate the updating of the Packet Unit Delay Budget (PDB) parameter and / or Packet Unit Set Delay Budget (PSDB) parameter in the PCC rule for the scheduled service uplink transmission, and / or the updating of the PDB parameter and / or PSDB parameter in the PCC rule for the scheduled service downlink transmission.

[0801] In one embodiment, the transceiver module 210 is specifically configured to receive the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission sent by the UPF through the NEF.

[0802] and / or

[0803] The transceiver module 210 is specifically configured to receive the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission sent by the PCF through the NEF.

[0804] In one embodiment, the transmission delay parameters of the bidirectional transmission of the predetermined service data stream are used by the PCF to determine the transmission delay parameters of the uplink transmission of the data stream and / or the transmission delay parameters of the downlink transmission of the data stream.

[0805] In one embodiment, the transceiver module 210 is specifically configured to include at least one of the following:

[0806] The transmission delay parameters for the predetermined bidirectional transmission of the service are sent to the PCF via the NEF.

[0807] The transmission delay parameters for the predetermined bidirectional transmission of the service are sent to the PCF via the TSCTSF.

[0808] The transmission delay parameters for the bidirectional transmission of the predetermined service are sent from the NEF to the PCF via the TSCTSF.

[0809] like Figure 23 As shown, this exemplary embodiment provides an information transmission device 300, wherein the device, disposed in a User Plane Function (UPF), includes:

[0810] The transceiver module 310 is configured to receive the association identifier of the pre-defined service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the downlink transmission of the pre-defined service data stream.

[0811] In one embodiment, the association identifier is a policy control and billing PCC rule indication of the predetermined service association sent by the policy control function (PCF) to the session management function (SMF).

[0812] In one embodiment, the transceiver module 310 is further configured to include at least one of the following:

[0813] Send the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission to the PCF;

[0814] Send the QoS latency monitoring report of the uplink transmission and the QoS latency monitoring report of the downlink transmission to the AF associated with the predetermined service;

[0815] The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using the association identifier.

[0816] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the first uplink subscription event triggering condition, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0817] and / or

[0818] The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network device after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the triggering condition of the first downlink subscription event, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

[0819] like Figure 24 As shown, this exemplary embodiment provides an information transmission device 400, which is disposed in an access network device and includes:

[0820] The transceiver module 410 is configured to receive the association identifier of the pre-defined service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the downlink transmission of the pre-defined service data stream.

[0821] In one embodiment, the association identifier is indicated by the policy control and billing PCC rules carried by the policy control function (PCF) and sent to the session management function (SMF) of the predetermined service association.

[0822] In one embodiment, the transceiver module 410 is further configured to:

[0823] The UPF sends the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission to the PCF, wherein the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission are associated using the association identifier.

[0824] In one embodiment, the QoS latency monitoring report for uplink transmission and the QoS latency monitoring report for downlink transmission are used by the PCF to update the PCC rules for the uplink transmission of the predetermined service and / or the PCC rules for the downlink transmission of the predetermined service.

[0825] In one embodiment, the uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the triggering condition of the second uplink subscription event, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier.

[0826] And / or,

[0827] The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the access network device after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the triggering conditions of the second downlink subscription event, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

[0828] In one embodiment, updating the PCC rules for the predetermined service uplink transmission includes: updating the packet unit delay budget (PDB) parameter and / or packet unit set delay budget (PSDB) parameter in the PCC rules for the predetermined service uplink transmission.

[0829] The step of updating the PCC rules for the scheduled downlink transmission of the service includes updating the PDB parameters and / or PSDB parameters in the PCC rules for the scheduled downlink transmission of the service.

[0830] This disclosure provides a communication device, including:

[0831] processor;

[0832] Memory used to store processor-executable instructions;

[0833] The processor is configured to implement the information transmission method of any embodiment of this disclosure when running executable instructions.

[0834] In one embodiment, the communication equipment may include, but is not limited to, at least one of: a UE and a network device. The network device may include core network or access network equipment, etc. The access network equipment may include a base station; the core network may include an AMF (Active Network Filter) and an SMF (Small and Medium Network Filter).

[0835] The processor may include various types of storage media, which are non-transitory computer storage media that can continue to store information after the user equipment loses power.

[0836] The processor can connect to memory via a bus or similar means to read executable programs stored in memory, for example... Figures 2 to 20 At least one of the methods shown.

[0837] This disclosure also provides a computer storage medium storing a computer-executable program. When the executable program is executed by a processor, it implements the information transmission method of any embodiment of this disclosure. For example, such as... Figures 2 to 20 At least one of the methods shown.

[0838] Regarding the apparatus or storage medium in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0839] This disclosure also provides a core network device that executes the information transmission method of any embodiment of this disclosure, for example, such as... Figures 2 to 20 At least one of the methods shown.

[0840] For example:

[0841] The core network equipment receives the transmission delay parameters for the bidirectional transmission of the scheduled service sent by the AF.

[0842] The core network equipment determines the association identifier of the predetermined service based on the transmission delay parameters of the bidirectional transmission of the predetermined service, wherein the association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the predetermined service data stream.

[0843] The core network equipment sends an association identifier to the access network equipment.

[0844] Regarding the core network equipment in the above embodiments, the specific methods by which each network element performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0845] Figure 25This is a block diagram illustrating a user equipment 3000 according to an exemplary embodiment. For example, the user equipment 3000 may be a mobile phone, computer, digital broadcast user equipment, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0846] Reference Figure 25 User equipment 3000 may include one or more of the following components: processing component 3002, memory 3004, power supply component 3006, multimedia component 3008, audio component 3010, input / output (I / O) interface 3012, sensor component 3014, and communication component 3016.

[0847] Processing component 3002 typically controls the overall operation of user equipment 3000, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 3002 may include one or more processors 3020 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 3002 may include one or more modules to facilitate interaction between processing component 3002 and other components. For example, processing component 3002 may include a multimedia module to facilitate interaction between multimedia component 3008 and processing component 3002.

[0848] Memory 3004 is configured to store various types of data to support the operation of user equipment 3000. Examples of this data include instructions for any application or method operating on user equipment 3000, contact data, phonebook data, messages, pictures, videos, etc. Memory 3004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0849] Power supply component 3006 provides power to various components of user equipment 3000. Power supply component 3006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to user equipment 3000.

[0850] Multimedia component 3008 includes a screen that provides an output interface between the user equipment 3000 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 3008 includes a front-facing camera and / or a rear-facing camera. When the user equipment 3000 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0851] Audio component 3010 is configured to output and / or input audio signals. For example, audio component 3010 includes a microphone (MIC) configured to receive external audio signals when user equipment 3000 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 3004 or transmitted via communication component 3016. In some embodiments, audio component 3010 also includes a speaker for outputting audio signals.

[0852] I / O interface 812 provides an interface between processing component 3002 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0853] Sensor assembly 3014 includes one or more sensors for providing status assessments of various aspects of user equipment 3000. For example, sensor assembly 3014 can detect the on / off state of user equipment 3000, the relative positioning of components, such as the display and keypad of user equipment 3000, changes in position of user equipment 3000 or a component of user equipment 3000, the presence or absence of contact between the user and user equipment 3000, the orientation or acceleration / deceleration of user equipment 3000, and temperature changes of user equipment 3000. Sensor assembly 3014 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 3014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 3014 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0854] Communication component 3016 is configured to facilitate wired or wireless communication between user equipment 3000 and other devices. User equipment 3000 can access wireless networks based on communication standards, such as WiFi, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 3016 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 3016 further includes a near-field communication (NFC) module to facilitate short-range communication. 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.

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

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

[0857] Figure 26As shown, one embodiment of this disclosure illustrates the structure of a base station. For example, base station 900 can be provided as a network-side device. (Refer to...) Figure 26 The base station 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by a memory 932 for storing instructions, such as application programs, that can be executed by the processing component 922. The application programs stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 922 is configured to execute instructions to perform any of the methods described above applied to the base station.

[0858] Base station 900 may also include a power supply component 926 configured to perform power management of 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. Base station 900 can operate on an operating system stored in memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0859] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

[0860] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. An information transmission method, wherein, Applied to policy control functions (PCF), including: Receive QoS latency monitoring reports for uplink transmissions and QoS latency monitoring reports for downlink transmissions; Based on the QoS latency monitoring report of the uplink transmission, the QoS latency monitoring report of the downlink transmission, and the transmission latency parameters of the bidirectional transmission, update at least one of the policy control and charging PCC rules of the uplink transmission and the PCC rules of the downlink transmission.

2. The method according to claim 1, wherein, The method further includes: The transmission delay parameters of the bidirectional transmission are determined, and the transmission delay parameters of the bidirectional transmission are used to determine at least one of the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission.

3. The method according to claim 1 or 2, wherein, The transmission delay parameter for bidirectional transmission is the transmission delay parameter for bidirectional transmission of the data stream of the Augmented Reality Multimedia XRM service.

4. The method according to any one of claims 1 to 3, wherein, The method further includes at least one of the following: The transmission delay parameters of the bidirectional transmission are sent to the User Plane Function (UPF) via the Session Management Function (SMF). Send at least one of the following to the application function AF: the QoS latency monitoring report of the uplink transmission, the QoS latency monitoring report of the downlink transmission, and the transmission latency parameter of the bidirectional transmission.

5. The method according to claim 4, wherein, The step of sending the transmission delay parameters of the bidirectional transmission to the UPF via the SMF includes: The association identifier is sent from the SMF to the UPF. The association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the data stream. The QoS delay monitoring report of the uplink transmission and the QoS delay monitoring report of the downlink transmission are associated using the association identifier.

6. The method according to claim 1, wherein, The method further includes: The transmission delay parameters of the bidirectional transmission are sent to the access network device via SMF.

7. The method according to claim 6, wherein, The step of sending the transmission delay parameters of the bidirectional transmission to the access network device via SMF includes: The association identifier is sent to the access network device via the SMF. The association identifier is used to associate the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission of the data stream. The QoS delay monitoring report of the uplink transmission and the QoS delay monitoring report of the downlink transmission are associated using the association identifier.

8. The method according to claim 5 or 7, wherein, The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by at least one of the UPF and the access network device to monitor the transmission latency parameters of the uplink transmission, determine that the monitored transmission latency parameters of the uplink transmission meet the uplink subscription event triggering conditions, and determine the associated downlink transmission QoS latency monitoring report through the association identifier. and / or The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network equipment after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the downlink subscription event triggering conditions, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

9. The method according to any one of claims 5, 7, and 8, wherein, The association identifier is indicated by at least one of the PCC rules for the uplink transmission and the PCC rules for the downlink transmission.

10. The method according to any one of claims 1 to 9, wherein, The method further includes: Based on the transmission delay parameters of the bidirectional transmission, at least one of the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission is determined.

11. An information transmission method, wherein, Applied to application functions (AF), including: The receiver receives at least one of the following: the QoS delay monitoring report for uplink transmission, the QoS delay monitoring report for downlink transmission, and the transmission delay parameters for bidirectional transmission sent by the policy control function (PCF).

12. The method according to claim 11, wherein, The QoS latency monitoring report for uplink transmission and the QoS latency monitoring report for downlink transmission are received by the PCF and sent to the AF. The QoS latency monitoring report for uplink transmission, the QoS latency monitoring report for downlink transmission, and the transmission latency parameters for bidirectional transmission are used by the PCF to update at least one of the policy control and charging (PCC) rules for uplink transmission and the PCC rules for downlink transmission.

13. The method according to claim 11 or 12, wherein, The transmission delay parameter of the bidirectional transmission is determined by the PCF, and the transmission delay parameter of the bidirectional transmission is used to determine at least one of the transmission delay parameter of the uplink transmission and the transmission delay parameter of the downlink transmission.

14. The method according to any one of claims 11 to 13, wherein, The transmission delay parameter for bidirectional transmission is the transmission delay parameter for bidirectional transmission of the data stream of the Augmented Reality Multimedia XRM service.

15. The method according to any one of claims 11 to 14, wherein, The transmission delay parameters for bidirectional transmission are sent by the PCF to the User Plane Function (UPF).

16. The method according to any one of claims 11 to 15, wherein, The method further includes: Based at least on the QoS latency monitoring reports of the uplink transmission and the downlink transmission, it is determined whether to send AF session update information to the PCF.

17. The method according to any one of claims 11 to 16, wherein, The received policy control function (PCF) sends at least one of the following: uplink QoS latency monitoring report, downlink QoS latency monitoring report, and bidirectional transmission latency parameters, including: Receive at least one of the following: the QoS latency monitoring report for the uplink transmission, the QoS latency monitoring report for the downlink transmission, and the transmission latency parameters for the bidirectional transmission sent by the PCF via the NEF.

18. An information transmission method, wherein, Applied to user-plane functions (UPF), including: Send uplink QoS latency monitoring reports and downlink QoS latency monitoring reports to the Policy Control Function (PCF). The PCF updates at least one of the policy control and charging PCC rules for uplink transmission and the PCC rules for downlink transmission based on the QoS delay monitoring report for uplink transmission, the QoS delay monitoring report for downlink transmission, and the transmission delay parameters for bidirectional transmission.

19. The method according to claim 18, wherein, The transmission delay parameter of the bidirectional transmission is determined by the PCF, and the transmission delay parameter of the bidirectional transmission is used to determine at least one of the transmission delay parameter of the uplink transmission and the transmission delay parameter of the downlink transmission.

20. The method according to claim 18 or 19, wherein, The transmission delay parameter for bidirectional transmission is the transmission delay parameter for bidirectional transmission of the data stream of the Augmented Reality Multimedia XRM service.

21. The method according to any one of claims 18 to 20, wherein, At least one of the uplink transmission QoS latency monitoring report, the downlink transmission QoS latency monitoring report, and the bidirectional transmission latency parameters is sent by the PCF to the application function AF.

22. The method according to any one of claims 18 to 21, wherein, The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using an association identifier.

23. The method according to claim 22, wherein, The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by at least one of the UPF and the access network device to monitor the transmission latency parameters of the uplink transmission, determine that the monitored transmission latency parameters of the uplink transmission meet the uplink subscription event triggering conditions, and determine the associated downlink transmission QoS latency monitoring report through the association identifier. and / or The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the UPF and / or access network equipment after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the downlink subscription event triggering conditions, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

24. The method according to claim 22 or 23, wherein, The association identifier is indicated by at least one of the PCC rules for the uplink transmission and the PCC rules for the downlink transmission.

25. An information transmission method, wherein, Applied to access network equipment, including: Send uplink QoS latency monitoring reports and downlink QoS latency monitoring reports to the Policy Control Function (PCF). The PCF updates at least one of the policy control and charging PCC rules for uplink transmission and the PCC rules for downlink transmission based on the QoS delay monitoring report for uplink transmission, the QoS delay monitoring report for downlink transmission, and the transmission delay parameters for bidirectional transmission.

26. The method of claim 25, wherein, The transmission delay parameter of the bidirectional transmission is determined by the PCF, and the transmission delay parameter of the bidirectional transmission is used to determine at least one of the transmission delay parameter of the uplink transmission and the transmission delay parameter of the downlink transmission.

27. The method according to claim 25 or 26, wherein, The transmission delay parameter for bidirectional transmission is the transmission delay parameter for bidirectional transmission of the data stream of the Augmented Reality Multimedia XRM service.

28. The method according to any one of claims 25 to 27, wherein, At least one of the uplink transmission QoS latency monitoring report, the downlink transmission QoS latency monitoring report, and the bidirectional transmission latency parameters is sent by the PCF to the application function AF.

29. The method according to any one of claims 25 to 28, wherein, The uplink QoS latency monitoring report and the downlink QoS latency monitoring report are associated using an association identifier.

30. The method according to claim 29, wherein, The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the access network device after monitoring the transmission latency parameters of the uplink transmission, determining that the monitored transmission latency parameters of the uplink transmission meet the uplink subscription event triggering conditions, and identifying the associated downlink transmission QoS latency monitoring report through the association identifier. and / or The uplink transmission QoS latency monitoring report and the downlink transmission QoS latency monitoring report are sent by the access network device after monitoring the transmission latency parameters of the downlink transmission, determining that the monitored transmission latency parameters of the downlink transmission meet the downlink subscription event triggering conditions, and identifying the associated uplink transmission QoS latency monitoring report through the association identifier.

31. The method according to claim 29 or 30, wherein, The association identifier is indicated by at least one of the PCC rules for the uplink transmission and the PCC rules for the downlink transmission.

32. An information transmission method, wherein, The invention is applied to a communication system, which includes at least one of a policy control function (PCF), an application function (AF), a user plane function (UPF), and an access network device. The method includes at least one of the following: The UPF sends an uplink QoS latency monitoring report and a downlink QoS latency monitoring report to the PCF. The access network device sends the QoS latency monitoring report for the uplink transmission and the QoS latency monitoring report for the downlink transmission to the PCF; The PCF updates at least one of the policy control and charging PCC rules for uplink transmission and the PCC rules for downlink transmission based on the QoS latency monitoring report for uplink transmission, the QoS latency monitoring report for downlink transmission, and the transmission latency parameters for bidirectional transmission. The PCF sends to the AF at least one of the following: the QoS latency monitoring report for the uplink transmission, the QoS latency monitoring report for the downlink transmission, and the transmission latency parameters for the bidirectional transmission.

33. The method according to claim 32, wherein, The method further includes: The PCF determines the transmission delay parameters of the bidirectional transmission, which are used to determine at least one of the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission.

34. The method according to claim 32 or 33, wherein, The transmission delay parameter for bidirectional transmission is the transmission delay parameter for bidirectional transmission of the data stream of the Augmented Reality Multimedia XRM service.

35. The method according to any one of claims 32 to 34, wherein, The method further includes: The PCF sends the transmission delay parameters of the bidirectional transmission to the UPF via the Session Management Function (SMF).

36. An information transmission device, wherein, Applied to policy control functions (PCF), including: The transceiver module is configured to receive QoS latency monitoring reports for uplink transmissions and QoS latency monitoring reports for downlink transmissions. The processing module is configured to update at least one of the policy control and charging (PCC) rules for uplink transmission and the PCC rules for downlink transmission based on the QoS latency monitoring report for uplink transmission, the QoS latency monitoring report for downlink transmission, and the transmission latency parameters for bidirectional transmission.

37. The method of claim 36, wherein, The processing module is also configured as follows: The transmission delay parameters of the bidirectional transmission are determined, and the transmission delay parameters of the bidirectional transmission are used to determine at least one of the transmission delay parameters of the uplink transmission and the transmission delay parameters of the downlink transmission.

38. The method according to claim 36 or 37, wherein, The transmission delay parameter for bidirectional transmission is the transmission delay parameter for bidirectional transmission of the data stream of the Augmented Reality Multimedia XRM service.

39. The method according to any one of claims 36 to 38, wherein, The transceiver module is also configured to perform at least one of the following: The transmission delay parameters of the bidirectional transmission are sent to the User Plane Function (UPF) via the Session Management Function (SMF). Send at least one of the following to the application function AF: the QoS latency monitoring report of the uplink transmission, the QoS latency monitoring report of the downlink transmission, and the transmission latency parameter of the bidirectional transmission.

40. An information transmission device, wherein, Applied to application functions (AF), including: The transceiver module is configured to receive at least one of the following sent by the policy control function PCF: uplink QoS latency monitoring report, downlink QoS latency monitoring report, and bidirectional transmission latency parameters.

41. The method according to claim 40, wherein, The QoS latency monitoring report for uplink transmission and the QoS latency monitoring report for downlink transmission are received by the PCF and sent to the AF. The QoS latency monitoring report for uplink transmission, the QoS latency monitoring report for downlink transmission, and the transmission latency parameters for bidirectional transmission are used by the PCF to update at least one of the policy control and charging (PCC) rules for uplink transmission and the PCC rules for downlink transmission.

42. The method according to claim 40 or 41, wherein, The transmission delay parameter of the bidirectional transmission is determined by the PCF, and the transmission delay parameter of the bidirectional transmission is used to determine at least one of the transmission delay parameter of the uplink transmission and the transmission delay parameter of the downlink transmission.

43. The method according to any one of claims 40 to 42, wherein, The transmission delay parameter for bidirectional transmission is the transmission delay parameter for bidirectional transmission of the data stream of the Augmented Reality Multimedia XRM service.

44. The method according to any one of claims 40 to 43, wherein, The transmission delay parameters for bidirectional transmission are sent by the PCF to the User Plane Function (UPF).

45. An information transmission device, wherein, Applied to user-plane functions (UPF), including: The transceiver module is configured to send uplink QoS latency monitoring reports and downlink QoS latency monitoring reports to the Policy Control Function (PCF). The PCF updates at least one of the policy control and charging PCC rules for uplink transmission and the PCC rules for downlink transmission based on the QoS delay monitoring report for uplink transmission, the QoS delay monitoring report for downlink transmission, and the transmission delay parameters for bidirectional transmission.

46. ​​The method according to claim 45, wherein, The transmission delay parameter of the bidirectional transmission is determined by the PCF, and the transmission delay parameter of the bidirectional transmission is used to determine at least one of the transmission delay parameter of the uplink transmission and the transmission delay parameter of the downlink transmission.

47. The method according to claim 45 or 46, wherein, The transmission delay parameter for bidirectional transmission is the transmission delay parameter for bidirectional transmission of the data stream of the Augmented Reality Multimedia XRM service.

48. The method according to any one of claims 45 to 47, wherein, At least one of the uplink transmission QoS latency monitoring report, the downlink transmission QoS latency monitoring report, and the bidirectional transmission latency parameters is sent by the PCF to the application function AF.

49. An information transmission device, wherein, Applied to access network equipment, including: The transceiver module is configured to send uplink QoS latency monitoring reports and downlink QoS latency monitoring reports to the Policy Control Function (PCF). The PCF updates at least one of the policy control and charging PCC rules for uplink transmission and the PCC rules for downlink transmission based on the QoS delay monitoring report for uplink transmission, the QoS delay monitoring report for downlink transmission, and the transmission delay parameters for bidirectional transmission.

50. The method according to claim 49, wherein, The transmission delay parameter of the bidirectional transmission is determined by the PCF, and the transmission delay parameter of the bidirectional transmission is used to determine at least one of the transmission delay parameter of the uplink transmission and the transmission delay parameter of the downlink transmission.

51. The method according to claim 49 or 50, wherein, The transmission delay parameter for bidirectional transmission is the transmission delay parameter for bidirectional transmission of the data stream of the Augmented Reality Multimedia XRM service.

52. The method according to any one of claims 49 to 51, wherein, At least one of the uplink transmission QoS latency monitoring report, the downlink transmission QoS latency monitoring report, and the bidirectional transmission latency parameters is sent by the PCF to the application function AF.

53. A communication system, comprising at least one of a policy control function (PCF), an application function (AF), a user plane function (UPF), and an access network device; The PCF is configured to perform the method as described in any one of claims 1 to 10; The AF is configured to perform the method as described in any one of claims 11 to 17; The UPF is configured to perform the method as described in any one of claims 18 to 24; The access network device is configured to perform the method as described in any one of claims 25 to 31.

54. A communication device, wherein, The communication device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to implement the information transmission method as described in any one of claims 1 to 32 when running the executable instructions.

55. A computer storage medium, wherein, The computer storage medium stores a computer executable program, which, when executed by a processor, implements the method as described in any one of claims 1 to 32.

56. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by a communication device, it implements the method as described in any one of claims 1 to 32.

Images