Communication method and system, and related device

Abstract

The present disclosure relates to the technical field of communications. Provided are a communication method and system, and a related device. The method comprises: a core network entity acquiring quality-of-service (QoS) decision-making assistance information, wherein the QoS decision-making assistance information comprises QoS information related to a business and / or QoS information related to an air interface; and the core network entity making a QoS decision on the basis of the QoS decision-making assistance information. The embodiments of the present disclosure can make a QoS policy more rational, thereby improving the reliability and service efficiency of a business.

Description

Communication method, system and related equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims priority to Chinese patent application number 202311127065.8, filed on September 1, 2023, entitled “Communication Methods, Systems and Related Equipment,” and the entire contents of this Chinese patent application are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to the field of communication technology, and in particular to a communication method, system, and related equipment. Background Art

[0004] In related technologies, the QoS (Quality of Service) mechanism is a one-way QoS mechanism in which the CN (Core Network) makes QoS decisions, and the RAN (Radio Access Network) and UE (User Equipment) perform QoS execution. The initiative in QoS decision-making rests entirely with the CN. When the QoS policy issued by the CN is not suitable for the RAN or UE, the RAN and UE can only passively reject it and have no right to actively participate in the QoS decision-making process. This results in significant resource waste and trial-and-error overhead, and the QoS mechanism has a coarse granularity and low efficiency.

[0005] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute prior art known to ordinary technicians in the field.

[0006] Summary of the Invention

[0007] Through research, the inventors found that due to the openness of the wireless environment and the complex and changeable air interface status, the coarse-grained centralized QoS decision-making independently performed by the CN cannot perceive and integrate the air interface status on the RAN side and the service characteristics on the UE side, resulting in a mismatch between QoS decisions and the air interface and services, thereby reducing the performance and efficiency of data transmission, and the performance in terms of reliability and latency has also declined, which cannot meet the deterministic requirements of various key services in future B5G / 6G networks.

[0008] In response to the above problems, the present application discloses a communication method, system and related equipment, which can enable the CN side to make more reasonable and more matching QoS decisions.

[0009] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by practice of the present disclosure.

[0010] According to one aspect of the present disclosure, a communication method is provided, which is applied to a core network entity, and the method includes:

[0011] Acquiring QoS decision-making auxiliary information; the QoS decision-making auxiliary information includes QoS information related to the service and / or QoS information related to the air interface;

[0012] Make QoS decisions based on QoS decision-making auxiliary information.

[0013] In one embodiment of the present disclosure, the QoS decision-making auxiliary information includes first auxiliary information and / or second auxiliary information, and obtaining the quality of service QoS decision-making auxiliary information includes:

[0014] Obtain the first auxiliary information reported by the access network entity,

[0015] and / or,

[0016] Second auxiliary information reported by the user equipment is obtained, wherein the first auxiliary information is QoS information related to the air interface, and the second auxiliary information is QoS information related to the service.

[0017] In one embodiment of the present disclosure, the reporting type of QoS decision-making auxiliary information reported by the access network entity and the user equipment includes one or more of the following types:

[0018] Initial reporting: the user device actively initiates the report;

[0019] Periodic reporting: User equipment initiates reporting periodically.

[0020] Event-triggered reporting: the user equipment actively initiates reporting based on the service status, or the access network entity actively initiates reporting based on the air interface status, or the core network entity requires the user equipment and / or access network entity to initiate reporting based on dynamic policies.

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

[0022] A first reporting indication is sent to the access network entity, where the first reporting indication is used to instruct the access network entity to report first auxiliary information.

[0023] In one embodiment of the present disclosure, the first reporting indication is used to instruct the access network entity to enable or disable periodic reporting, and to instruct the access network entity to enable or disable event-triggered reporting.

[0024] In one embodiment of the present disclosure, the method further includes:

[0025] A second reporting instruction is sent to the user equipment, where the second reporting instruction is used to instruct the user equipment to report the second auxiliary information.

[0026] In one embodiment of the present disclosure, the second reporting indication is used to instruct the user equipment to enable or disable periodic reporting, and to instruct the user equipment to enable or disable event-triggered reporting.

[0027] In one embodiment of the present disclosure, the first auxiliary information includes one or more of the following information:

[0028] Air interface status, notification control, references to alternative QoS profiles, and

[0029] Air interface requirements or recommendations for guaranteed flow bit rate, packet delay estimate, packet error rate, maximum flow bit rate, session aggregation maximum bit rate, user equipment aggregation maximum bit rate and / or UE slice maximum bit rate.

[0030] In one embodiment of the present disclosure, the second auxiliary information includes one or more of the following information:

[0031] Describes the SDF's packet filter, requested packet filter action, and requested / proposed QoS.

[0032] In one embodiment of the present disclosure, the method further includes:

[0033] After making a QoS decision based on the QoS decision auxiliary information, the QoS policy is sent to the access network entity and / or user equipment for uplink and downlink transmission.

[0034] In one embodiment of the present disclosure, the QoS policy includes a QoS profile and a QoS rule.

[0035] In one embodiment of the present disclosure, delivering a QoS policy to an access network entity and / or a user equipment includes:

[0036] Sending QoS configuration files to access network entities, and

[0037] The QoS rules are forwarded to the user equipment through the access network entity.

[0038] In one embodiment of the present disclosure, the method further includes:

[0039] A first feedback message sent by an access network entity is received, where the first feedback message includes a QoS flow list accepted by the access network entity and / or a QoS flow list rejected by the access network entity.

[0040] In one embodiment of the present disclosure, the method further includes:

[0041] In a case where the first feedback message includes a list of QoS flows rejected by the access network entity, the QoS profile related to the rejected QoS flows is released.

[0042] In one embodiment of the present disclosure, the QoS policy further includes QoS parameters at the QoS flow level;

[0043] Delivering QoS policies to access network entities and / or user equipment also includes:

[0044] The QoS parameters of the QoS flow level are forwarded to the user equipment through the access network entity.

[0045] In one embodiment of the present disclosure, the QoS policy further includes a reporting indication;

[0046] Delivering QoS policies to access network entities and / or user equipment also includes:

[0047] The reporting instruction is sent to the access network entity and / or user equipment.

[0048] In one embodiment of the present disclosure, the reporting indication includes a first reporting indication and / or a second reporting indication;

[0049] Sending a reporting instruction to an access network entity and / or user equipment includes:

[0050] Sending the first reporting instruction to the access network entity, and / or

[0051] Forwarding the second reporting instruction to the user equipment through the access network entity;

[0052] Among them, the first reporting indication is used to instruct the access network entity to enable or disable periodic reporting, and to instruct the access network entity to enable or disable event-triggered reporting; the second reporting indication is used to instruct the user equipment to enable or disable periodic reporting, and to instruct the user equipment to enable or disable event-triggered reporting.

[0053] According to another aspect of the present disclosure, a communication method is provided, which is applied to an access network entity, and the method includes:

[0054] Reporting QoS decision-making auxiliary information to the core network entity so that the core network entity can make QoS decisions based on the QoS decision-making auxiliary information;

[0055] The QoS decision-making auxiliary information includes QoS information related to the air interface.

[0056] According to another aspect of the present disclosure, a communication method is provided, applied to a user equipment, the method comprising:

[0057] Reporting QoS decision-making auxiliary information to the core network entity so that the core network entity can make QoS decisions based on the QoS decision-making auxiliary information;

[0058] The QoS decision-making auxiliary information includes service-related QoS information.

[0059] According to another aspect of the present disclosure, a core network entity is provided, including:

[0060] An information acquisition module is used to obtain quality of service (QoS) decision-making auxiliary information; the QoS decision-making auxiliary information includes QoS information related to the service and / or QoS information related to the air interface;

[0061] The decision module is used to make QoS decisions based on the QoS decision auxiliary information.

[0062] According to another aspect of the present disclosure, an access network entity is provided, including:

[0063] The first information sending module is used to report the quality of service (QoS) decision-making auxiliary information to the core network entity, so that the core network entity makes a QoS decision based on the QoS decision-making auxiliary information;

[0064] The QoS decision-making auxiliary information includes QoS information related to the air interface.

[0065] According to another aspect of the present disclosure, a user equipment is provided, including:

[0066] The second information sending module is used to report the quality of service QoS decision-making auxiliary information to the core network entity, so that the core network entity makes a QoS decision based on the QoS decision-making auxiliary information;

[0067] The QoS decision-making auxiliary information includes service-related QoS information.

[0068] According to another aspect of the present disclosure, there is provided a communication system, comprising:

[0069] User equipment;

[0070] Access network entity;

[0071] The core network entity is used to obtain the service quality QoS decision-making auxiliary information reported by the access network entity and / or the user equipment, and make QoS decisions based on the QoS decision-making auxiliary information; wherein the QoS decision-making auxiliary information includes QoS information related to the service and / or QoS information related to the air interface.

[0072] According to another aspect of the present disclosure, an electronic device is provided, including: a memory for storing instructions; and a processor for calling the instructions stored in the memory to implement the above-mentioned communication method.

[0073] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which computer instructions are stored. When the computer instructions are executed by a processor, the above-mentioned communication method is implemented.

[0074] According to yet another aspect of the present disclosure, a computer program product is provided. The computer program product stores instructions, which, when executed by a computer, enable the computer to implement the above communication method.

[0075] According to yet another aspect of the present disclosure, there is provided a chip comprising at least one processor and an interface;

[0076] An interface for providing program instructions or data to at least one processor;

[0077] At least one processor is configured to execute program instructions to implement the above communication method.

[0078] The communication method, system and related equipment provided by the embodiments of the present disclosure enable the core network entity to obtain service quality QoS decision-making auxiliary information, and then make QoS decisions based on the QoS information related to the service in the QoS decision-making auxiliary information, and / or make QoS decisions based on the QoS information related to the air interface, so as to make the QoS strategy more reasonable and improve the reliability and service efficiency of the service.

[0079] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0081] Obviously, the drawings described below are only some embodiments of the present disclosure. A person skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0082] FIG1 shows a schematic diagram of a QoS mechanism according to an embodiment of the present disclosure;

[0083] FIG2 shows a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0084] FIG3 shows a flow chart of a communication method according to an embodiment of the present disclosure;

[0085] FIG4 shows a flow chart of another communication method according to an embodiment of the present disclosure;

[0086] FIG5 shows a flow chart of another communication method according to an embodiment of the present disclosure;

[0087] FIG6 shows a flow chart of a communication method using initial reporting in an embodiment of the present disclosure;

[0088] FIG7 shows a flow chart of a communication method using periodic reporting in an embodiment of the present disclosure;

[0089] FIG8 shows a flow chart of a communication method for UE triggering reporting in an embodiment of the present disclosure;

[0090] FIG9 shows a flow chart of a communication method for RAN triggered reporting according to an embodiment of the present disclosure;

[0091] FIG10 shows a flow chart of a communication method for CN triggering reporting in an embodiment of the present disclosure;

[0092] FIG11 shows a flow chart of a communication method performed by an access network entity in an embodiment of the present disclosure;

[0093] FIG12 shows a flow chart of a communication method performed by a user equipment according to an embodiment of the present disclosure;

[0094] FIG13 shows a schematic diagram of a core network entity structure according to an embodiment of the present disclosure;

[0095] FIG14 shows a schematic diagram of an access network entity structure according to an embodiment of the present disclosure;

[0096] FIG15 shows a schematic diagram of the structure of a user equipment according to an embodiment of the present disclosure;

[0097] FIG16 shows a structural block diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0098] Example embodiments will be described more fully hereinafter with reference to the accompanying drawings.

[0099] It should be noted that example embodiments may be implemented in many forms and should not be construed as limited to the examples set forth herein.

[0100] In the future, B5G / 6G networks will provide strong support for emerging vertical industries with higher requirements in terms of reliability and latency. The Quality of Service (QoS) mechanism will meet the deterministic requirements of various services by performing differentiated forwarding processing on data packets.

[0101] In the QoS mechanism defined in 3GPP TS 23.501, as shown in Figure 1, when a UE requires QoS control, the CN (Consumer Network) issues QoS rules to the UE, which then decides whether and how to mark and transmit uplink (UL) data packets. Furthermore, the CN issues QoS profiles to the RAN (Region Ranking System), which controls uplink and downlink transmissions between the UE and the CN. In this solution, the CN's independent, coarse-grained QoS decisions are unable to perceive and integrate the RAN's air interface and UE-side services. This results in QoS decisions that may not match the air interface status and service characteristics, thereby reducing data transmission performance and efficiency.

[0102] As can be seen from the background technology section, in related technologies, the initiative for QoS decision-making lies entirely with the CN. When the QoS policy issued by the CN is not suitable for the RAN or UE, the RAN and UE can only passively reject it and have no right to actively participate in the QoS decision-making process, resulting in significant resource waste and trial-and-error overhead. The QoS mechanism is coarse-grained and inefficient. Specifically, when the QoS policy issued by the CN does not match the air interface status on the RAN side or the service characteristics on the UE side, the RAN and UE can only passively reject it and have no right to actively participate in the QoS decision-making process, resulting in significant resource waste and trial-and-error overhead. The QoS mechanism is coarse-grained and inefficient.

[0103] In addition, due to the openness of the wireless environment and the complex and changeable air interface status, the coarse-grained centralized QoS decision-making independently performed by the CN cannot perceive and integrate the air interface status on the RAN side and the service characteristics on the UE side, resulting in a mismatch between QoS decisions and the air interface and services, which in turn reduces the performance and efficiency of data transmission, and also reduces the performance in terms of reliability and latency, which cannot meet the deterministic requirements of various key services in future B5G / 6G networks.

[0104] To address the above issues, the present disclosure provides a communication method, system, and related equipment. The UE / RAN actively or passively (according to CN requirements) reports QoS decision-making assistance information to the CN, enabling the CN to make more reasonable and appropriate QoS decisions based on the QoS decision-making assistance information. This is conducive to achieving more accurate and fine-grained end-to-end QoS guarantees, and better meeting the deterministic requirements of low latency, high reliability, and other requirements for various services.

[0105] FIG2 shows a communication system according to an embodiment of the present disclosure. As shown in FIG2 , the communication system provided by the embodiment of the present disclosure includes an access network entity 201 and a core network entity 202 .

[0106] The access network entity 201 may be an entity in the RAN (4G system) or NG-RAN (5G system), or an entity related to the access network in the future B5G / 6G network. As an embodiment, the access network entity 201 may be a base station.

[0107] The core network entity 202 can be a network entity, specifically a CN entity in 5G CN (5GC), etc., or it can be an entity related to the core network in the future B5G / 6G network.

[0108] The core network entity 202 can be used to obtain the quality of service (QoS) decision-making auxiliary information reported by the access network entity and make QoS decisions based on the QoS decision-making auxiliary information; wherein the QoS decision-making auxiliary information includes QoS information related to the air interface.

[0109] In some embodiments, the communication system may further include user equipment 203 .

[0110] The user equipment 203 may be a wireless communication device such as a mobile phone, tablet computer, notebook, wearable device, vehicle-mounted communication device or drone.

[0111] The core network entity 202 can be used to obtain service quality QoS decision-making auxiliary information reported by the access network entity and / or user equipment, and make QoS decisions based on the QoS decision-making auxiliary information; wherein, the QoS decision-making auxiliary information includes QoS information related to the service and / or QoS information related to the air interface.

[0112] In some embodiments, the QoS decision-making auxiliary information may include first auxiliary information and / or second auxiliary information. The core network entity 202 obtains the QoS decision-making auxiliary information by obtaining first auxiliary information reported by the access network entity and / or obtaining second auxiliary information reported by the user equipment, where the first auxiliary information is QoS information related to the air interface and the second auxiliary information is QoS information related to the service.

[0113] In some embodiments, the reporting type of the QoS decision assistance information reported by the access network entity 201 and the user equipment 203 includes one or more of the following types: initial reporting, periodic reporting, and event-triggered reporting.

[0114] The initial report is initiated by the user equipment 203. As an embodiment, it can be performed during the PDU session establishment process after the user equipment 203 registers.

[0115] Periodic reporting is initiated by the user equipment 203 according to a periodicity. As an embodiment, it can be performed in the PDU session modification process.

[0116] Event-triggered reporting includes reporting processes triggered by user equipment 203, access network entity 201, and core network entity 202. The reporting process triggered by user equipment 203 is when the user equipment proactively initiates a report based on the service status; the reporting process triggered by access network entity 201 is when the access network entity proactively initiates a report based on the air interface status; and the reporting process triggered by core network entity 202 is when the core network entity requires the user equipment and / or access network entity to initiate a report based on a dynamic policy. As an example, event-triggered reporting can occur during a PDU session modification process.

[0117] In some embodiments, the core network entity 202 may require the user equipment 203 and / or the access network entity 201 to report QoS decision-making assistance information. When the core network entity 202 decides to enable QoS decision-making assistance information reporting for a service, for example, based on the importance of the service or the failure rate of the service, the core network entity 202 initiates a "core network entity 202-triggered reporting process" and instructs the user equipment 203 and / or the access network entity 201 to report different types of QoS decision-making assistance information through a "reporting indication." These types may include enabling periodic reporting for the user equipment 203 and the access network entity 201, enabling user equipment 203-triggered reporting for the user equipment 203, and enabling access network entity 201-triggered reporting for the access network entity 201. The QoS decision-making assistance information includes: QoS decision-making assistance information (RAN-QDAI) of the access network entity 201 and QoS decision-making assistance information (UE-QDAI) of the user equipment 203, namely the first assistance information and the second assistance information mentioned above. The information contained in different types of UE-QDAI / RAN-QDAI reporting processes is not exactly the same.

[0118] In some embodiments, the user equipment 203 actively or passively (as required by the core network entity 202) reports the QoS decision-making auxiliary information of the user equipment 203 to the core network entity 202, including: actively reporting UE-QDAI to the core network entity 202 when the user equipment 203 establishes a PDU session, reporting UE-QDAI to the core network entity 202 when the core network entity 202 enables periodic reporting for the user equipment 203 and the access network entity 201 and the periodic timer arrives, and reporting UE-QDAI to the core network entity 202 when the core network entity 202 enables event-triggered reporting for the user equipment 203 and meets the reporting conditions triggered by the user equipment 203 (such as the user equipment 203 needs to perform specific QoS processing on the selected SDF, etc.).

[0119] In some embodiments, the access network entity 201 actively or passively (as required by the core network entity 202) reports the QoS decision-making auxiliary information of the access network entity 201 to the core network entity 202, including: when the user equipment 203 establishes a PDU session, the access network entity 201 actively reports RAN-QDAI to the core network entity 202, when the core network entity 202 enables periodic reporting for the user equipment 203 and the access network entity 201 and the periodic timer arrives, reports RAN-QDAI to the core network entity 202, when the core network entity 202 enables event-triggered reporting for the access network entity 201 and meets the reporting conditions triggered by the access network entity 201, reports RAN-QDAI to the core network entity 202 (such as the target QoS of the QoS flow cannot be met by the current air interface status, etc.).

[0120] When the reporting type is initial reporting and periodic reporting, the core network entity 202 will receive the first auxiliary information and the second auxiliary information.

[0121] When the reporting type is event-triggered reporting, the core network entity 202 may only receive one type of auxiliary information, namely, the first auxiliary information and the second auxiliary information.

[0122] In one embodiment, the event-triggered reporting is initiated by the user equipment 203 according to the service status, and the core network entity 202 only receives the second auxiliary information. The auxiliary information is included in the NAS (Non-Access Stratum) message, and the NAS message is transparently transmitted by the access network entity 201 to the core network entity 202.

[0123] In one embodiment, the event-triggered reporting is initiated by the access network entity 201 according to the air interface status, and the core network entity 202 only receives the first auxiliary information, which is included in the N2 message.

[0124] In one embodiment, the event-triggered reporting is initiated simultaneously by the user equipment 203 and the access network entity 201, and the core network entity 202 receives the first auxiliary information and the second auxiliary information simultaneously.

[0125] In the disclosed embodiment, the core network entity 202 may require the user equipment 203 and / or the access network entity 201 to report QoS decision assistance information. The access network entity 201 actively or passively (at the request of the core network entity 202) reports RAN-QDAI to the core network entity 202, that is, reports the first assistance information. The user equipment 203 actively or passively (at the request of the core network entity 202) reports UE-QDAI to the core network entity 202, that is, reports the second assistance information.

[0126] In some embodiments, the core network entity 202 may require the access network entity 201 to report QoS decision assistance information (RAN-QDAI), that is, first assistance information, of the access network entity 201. As an embodiment, the core network entity 202 may also send a first reporting indication to the access network entity 201, where the first reporting indication is used to instruct the access network entity to report the first assistance information.

[0127] In some embodiments, the core network entity 202 may cancel the RAN-QDAI reporting requirement, that is, cancel the reporting requirement of the first auxiliary information, for the access network entity 201. As an embodiment, the first reporting indication is used to instruct the access network entity to enable or disable periodic reporting, and to instruct the access network entity to enable or disable event-triggered reporting.

[0128] In some embodiments, the core network entity 202 may require the user equipment 203 to report QoS decision assistance information (UE-QDAI), that is, the second assistance information, of the user equipment 203. In some embodiments, the core network entity 202 may also send a second reporting indication to the user equipment 203, where the second reporting indication is used to instruct the user equipment to report the second assistance information.

[0129] In some embodiments, the core network entity 202 may cancel the UE-QDAI reporting requirement for the user equipment 203, that is, cancel the reporting requirement of the second auxiliary information. As an embodiment, the second reporting indication is used to instruct the user equipment to enable or disable periodic reporting, and to instruct the user equipment to enable or disable event-triggered reporting.

[0130] In some embodiments, the access network entity 201 may also actively report RAN-QDAI to the core network entity 202, that is, report the first auxiliary information. The reporting types may include initial reporting, periodic reporting, and RAN-triggered reporting.

[0131] In some embodiments, the user equipment 203 may also actively report UE-QDAI to the core network entity 202, that is, report the second auxiliary information. The reporting types may include initial reporting, periodic reporting, and UE-triggered reporting.

[0132] In some embodiments, the first auxiliary information may include one or more of the following information:

[0133] Air interface status, notification control, references to alternative QoS profiles, and

[0134] Air interface requirements or recommendations for guaranteed flow bit rate, packet delay estimate, packet error rate, maximum flow bit rate, session aggregation maximum bit rate, user equipment aggregation maximum bit rate and / or UE slice maximum bit rate.

[0135] In some embodiments, the second auxiliary information may include one or more of the following information:

[0136] Describes the SDF's packet filter, requested packet filter action, and requested / proposed QoS.

[0137] In some embodiments, the core network entity 202 may also send the QoS policy to the access network entity 201 and / or the user equipment 203 for uplink and downlink transmission after making a QoS decision based on the QoS decision auxiliary information. That is, the core network entity 202 makes a QoS decision based on the QoS decision auxiliary information, and sends the QoS decision result to the user equipment 203 and the access network entity 201 for uplink and downlink transmission.

[0138] In some embodiments, the QoS policy includes a QoS profile and a QoS rule.

[0139] In some embodiments, the core network entity 202 sends the QoS policy to the access network entity 201 and / or the user equipment 203, including sending the QoS profile to the access network entity 201, and forwarding the QoS rules to the user equipment 203 through the access network entity 201.

[0140] In some embodiments, the core network entity 202 may also receive a first feedback message sent by the access network entity 201 , where the first feedback message includes a list of QoS flows accepted by the access network entity 201 and / or a list of QoS flows rejected by the access network entity 201 .

[0141] In some embodiments, the core network entity 202 may further release the QoS profile related to the rejected QoS flow when the first feedback message includes a list of QoS flows rejected by the access network entity 201 .

[0142] In some embodiments, the QoS policy may also include QoS parameters at the QoS flow level; the core network entity 202 sends the QoS policy to the access network entity 201 and / or the user equipment 203, and also includes: forwarding the QoS parameters at the QoS flow level to the user equipment 203 through the access network entity 201.

[0143] In some embodiments, the QoS policy may also include a reporting indication; the core network entity 202 sends the QoS policy to the access network entity 201 and / or the user equipment 203, and also includes: sending the reporting indication to the access network entity 201 and / or the user equipment 203.

[0144] In some embodiments, the reporting indication may include a first reporting indication and / or a second reporting indication; the core network entity 202 sends the reporting indication to the access network entity 201 and / or the user equipment 203, including: sending the first reporting indication to the access network entity 201, and / or forwarding the second reporting indication to the user equipment 203 through the access network entity 201; wherein, the first reporting indication is used to instruct the access network entity 201 to enable or disable periodic reporting, and to instruct the access network entity 201 to enable or disable event-triggered reporting; the second reporting indication is used to instruct the user equipment 203 to enable or disable periodic reporting, and to instruct the user equipment 203 to enable or disable event-triggered reporting.

[0145] In the embodiment of the present disclosure, the user equipment 203 / access network entity 201 actively or passively (according to the requirements of the core network entity 202) reports QoS decision-making auxiliary information to the core network entity 202, so that the core network entity 202 can make more reasonable and more matching QoS decisions based on the QoS decision-making auxiliary information, improve the reliability and service efficiency of the business, reduce the delay of signaling interaction and data transmission, thereby achieving more accurate and fine-grained end-to-end QoS guarantee, and better meeting the deterministic requirements of low latency, high reliability and other aspects of various services.

[0146] FIG3 shows a flow chart of a communication method in an embodiment of the present disclosure. As shown in FIG3 , the communication method provided in the embodiment of the present disclosure includes steps S302 - S304 .

[0147] In S302, the core network entity obtains quality of service (QoS) decision-making auxiliary information; the QoS decision-making auxiliary information includes service-related QoS information and / or air interface-related QoS information.

[0148] In S304, the core network entity makes a QoS decision based on the QoS decision auxiliary information.

[0149] In some embodiments, the QoS decision assistance information may include first assistance information and / or second assistance information.

[0150] FIG4 shows a flow chart of a communication method according to an embodiment of the present disclosure. The communication method shown in FIG4 is similar to the embodiment of FIG3 , wherein step 404 is the same as step 304 and is not described again here.

[0151] In the embodiment of Figure 4, the above-mentioned S302 obtains service quality QoS decision-making auxiliary information, which is to obtain QoS decision-making auxiliary information from the user equipment and / or access network entity in S402. Specifically, obtaining service quality QoS decision-making auxiliary information includes: obtaining first auxiliary information reported by the access network entity, and / or obtaining second auxiliary information reported by the user equipment, wherein the first auxiliary information is QoS information related to the air interface, and the second auxiliary information is QoS information related to the service.

[0152] In some embodiments, the reporting type of the QoS decision-making assistance information reported by the access network entity and the user equipment includes one or more of the following types:

[0153] Initial reporting: the user device actively initiates the report;

[0154] Periodic reporting: User equipment initiates reporting periodically.

[0155] Event-triggered reporting is initiated by the user equipment based on the service status, or by the access network entity based on the air interface status, or by the core network entity based on a dynamic policy. It is understood that the reporting initiated by the core network entity based on a dynamic policy may be the core network entity requiring the user equipment and / or access network entity to initiate reporting based on the dynamic policy, for example, the core network instructs the UE / RAN to enable / disable the reporting, and in the case of enabling the reporting, the UE / RAN performs the reporting.

[0156] In some embodiments, the above method may further include: the core network entity sending a first reporting indication to the access network entity, where the first reporting indication is used to instruct the access network entity to report the first auxiliary information.

[0157] In some embodiments, the first reporting indication is used to instruct the access network entity to enable or disable periodic reporting, and to instruct the access network entity to enable or disable event-triggered reporting.

[0158] In some embodiments, the above method may further include: the core network entity sending a second reporting indication to the user equipment, where the second reporting indication is used to instruct the user equipment to report the second auxiliary information.

[0159] In some embodiments, the second reporting indication is used to instruct the user equipment to enable or disable periodic reporting, and to instruct the user equipment to enable or disable event-triggered reporting.

[0160] In some embodiments, the first auxiliary information includes one or more of the following information:

[0161] Air interface status (such as time and frequency resource occupancy), notification control, references to alternative QoS profiles, and

[0162] Air interface requirements or recommendations for guaranteed flow bit rate (GFBR), packet delay estimate (PDB), packet error rate (PER), maximum flow bit rate (MFBR), session aggregate maximum bit rate (Session-AMBR), user equipment aggregate maximum bit rate (UE-AMBR) and / or UE slice maximum bit rate (UE-Slice-MBR).

[0163] In some embodiments, the second auxiliary information includes one or more of the following information:

[0164] Describes the packet filters of the SDF, the requested packet filter operations (such as add, modify, delete), and the requested / recommended QoS, such as the service requirements or recommended values ​​for MFBR, Session-AMBR, etc.

[0165] In some embodiments, the above method may further include: after the core network entity makes a QoS decision based on the QoS decision auxiliary information, sending the QoS policy to the access network entity and / or user equipment for uplink and downlink transmission.

[0166] In some embodiments, the QoS policy may include a QoS profile and a QoS rule.

[0167] In some embodiments, the core network entity sends the QoS policy to the access network entity and / or the user equipment, including sending the QoS configuration file to the access network entity and forwarding the QoS rules to the user equipment through the access network entity.

[0168] In some embodiments, the above method may further include: the core network entity receives a first feedback message sent by the access network entity, the first feedback message including a list of QoS flows accepted by the access network entity and / or a list of QoS flows rejected by the access network entity.

[0169] In some embodiments, the above method may further include: when the first feedback message includes a QoS flow list rejected by the access network entity, the core network entity releases the QoS profile related to the rejected QoS flow.

[0170] In some embodiments, the QoS policy further includes QoS parameters at the QoS flow level;

[0171] The core network entity sends the QoS policy to the access network entity and / or the user equipment, and further includes: forwarding the QoS parameters of the QoS flow level to the user equipment through the access network entity.

[0172] In some embodiments, the QoS policy further includes a reporting indication;

[0173] The core network entity sends the QoS policy to the access network entity and / or the user equipment, and further includes: sending a reporting instruction to the access network entity and / or the user equipment.

[0174] In some embodiments, the reporting indication includes a first reporting indication and / or a second reporting indication;

[0175] The core network entity sends a reporting indication to the access network entity and / or the user equipment, including: sending a first reporting indication to the access network entity, and / or forwarding a second reporting indication to the user equipment through the access network entity; wherein the first reporting indication is used to instruct the access network entity to enable or disable periodic reporting, and to instruct the access network entity to enable or disable event-triggered reporting; the second reporting indication is used to instruct the user equipment to enable or disable periodic reporting, and to instruct the user equipment to enable or disable event-triggered reporting.

[0176] FIG5 shows a flow chart of a communication method in an embodiment of the present disclosure. As shown in FIG5 , in this method, the CN may require the UE and / or the RAN to report QoS decision assistance information. The CN may require the UE to report the UE's QoS decision assistance information (UE-QDAI). The CN may require the RAN to report the RAN's QoS decision assistance information (RAN-QDAI). The CN may cancel the UE's requirement to report UE-QDAI. The CN may cancel the RAN's requirement to report RAN-QDAI. It should be noted that the steps represented by the dotted lines in FIG5 are optional steps.

[0177] The following takes the 5G network as an example to explain in detail the various reporting types of the above embodiment. It should be noted that the 5G network is only an example, and the solution of the embodiment of the present disclosure can also be applied to other evolved networks such as 6G.

[0178] FIG6 shows a flow chart of a communication method using initial reporting in an embodiment of the present disclosure. As shown in FIG6 , the method may include steps S601 - S609 .

[0179] In S601, the UE reports the UE-QDAI to the AMF via a NAS message. This NAS message is encapsulated by the RAN in the N2 message sent to the AMF containing the RAN-QDAI.

[0180] In S602, the AMF forwards the UE-QDAI reported by the UE and the RAN-QDAI reported by the RAN to the SMF.

[0181] In S603, the SMF and the PCF perform the SM policy association process, and then the PCF provides the SMF with policy decision information.

[0182] In S604, the SMF sends the SM policy provided by the PCF to the UPF, such as the packet detection rules, execution rules, and reporting rules to be placed on the UPF.

[0183] In S605, the SMF forwards the derived QoS policy to the AMF, including the QoS profile, QoS rules, and QoS flow-level QoS parameters (if necessary) related to the QFI(s). In addition, it also includes reporting indications, i.e., enabling / disabling periodic / UE-triggered reporting for the UE and enabling / disabling periodic / RAN-triggered reporting for the RAN.

[0184] In S606, the AMF sends the QoS profile and reporting indication provided by the SMF to the RAN, including the QoS rules, QoS flow-level QoS parameters (if necessary) and reporting indication to be forwarded by the RAN to the UE.

[0185] In S607, the RAN forwards the QoS rules, QoS flow-level QoS parameters (if necessary) and reporting indication provided in step 6 to the UE.

[0186] In S608, the RAN feeds back its accepted / rejected QFI list to the AMF. If the RAN rejects the QFI, the SMF is responsible for updating the QoS rules and QoS flow-level QoS parameters related to the rejected QoS flow in the UE accordingly.

[0187] In S609, the AMF forwards the QoS feedback received from the RAN to the SMF. If the QoS feedback contains a rejected QFI list, the SMF shall release the QoS profile associated with the rejected QFI.

[0188] FIG7 shows a flow chart of a communication method using periodic reporting in an embodiment of the present disclosure. As shown in FIG7 , the method may include steps S701 - S709 .

[0189] In S701, the UE periodically reports the UE-QDAI to the AMF via a NAS message, in which the reporting type is set to periodic reporting. The RAN forwards this NAS message together with the RAN-QDAI to the AMF.

[0190] In S702, the AMF forwards the UE-QDAI reported by the UE and the RAN-QDAI reported by the RAN to the SMF.

[0191] In S703, the SMF may perform the SM policy association modification process with the PCF, and then the PCF provides the policy decision information to the SMF. If dynamic PCC is not deployed, the SMF may apply local policies to make SM policy decisions.

[0192] In S704, if the PCF / SMF updates the SM policy, the SMF sends it to the UPF, such as the packet detection rules, execution rules, reporting rules, etc. to be placed on the UPF. If the PCF / SMF does not update the SM policy, this step is skipped.

[0193] In S705, if the PCF / SMF updates the SM policy, the SMF forwards the newly derived QoS policy to the AMF, including the QoS profile related to the QFI(s), QoS rules, and QoS flow-level QoS parameters (if necessary). Otherwise, the SMF responds to the AMF with a periodic report rejection message.

[0194] In S706, if the PCF / SMF updates the SM policy, the AMF sends the QoS profile provided by the SMF to the RAN, including the QoS rules and QoS flow-level QoS parameters (if necessary) to be forwarded by the RAN to the UE. Otherwise, the AMF forwards the periodic reporting rejection message provided by the SMF to the RAN.

[0195] In S707, if the PCF / SMF updates the SM policy, the RAN forwards the QoS rules and QoS flow-level QoS parameters (if necessary) provided in step 6 to the UE. Otherwise, the RAN forwards the periodic reporting rejection message forwarded by the AMF to the UE, and the periodic reporting process ends here.

[0196] In S708, if the PCF / SMF updates the SM policy, the RAN feeds back its accepted / rejected QFI list to the AMF. If the RAN rejects the QFI, the SMF is responsible for updating the QoS rules and QoS flow-level QoS parameters related to the rejected QoS flow in the UE accordingly.

[0197] In S709, if the PCF / SMF updates the SM policy, the AMF forwards the QoS feedback received from the RAN to the SMF. If the QoS feedback contains a rejected QFI list, the SMF shall release the QoS profile associated with the rejected QFI.

[0198] FIG8 shows a flow chart of a communication method for UE-triggered reporting in an embodiment of the present disclosure. As shown in FIG8 , the method may include steps S801 - S809 .

[0199] In S801, the UE initiates the UE-triggered reporting process by sending a NAS message containing the UE-QDAI and the reporting type set to UE-triggered reporting. The RAN forwards this NAS message to the AMF. If the UE is in the CM-IDLE state, the UE needs to perform the service request process described in Section 4.2.3 of 3GPP TS 23.502 before sending this NAS message.

[0200] In S802, AMF forwards the UE-QDAI reported by the UE to SMF.

[0201] In S803, the SMF may perform the SM policy association modification process with the PCF, and then the PCF provides the policy decision information to the SMF. If dynamic PCC is not deployed, the SMF may apply local policies to make SM policy decisions.

[0202] In S804, if the PCF / SMF updates the SM policy, the SMF sends it to the UPF, such as the packet detection rules, execution rules, reporting rules, etc. to be placed on the UPF. If the PCF / SMF does not update the SM policy, this step is skipped.

[0203] In S805, if the PCF / SMF updates the SM policy, the SMF forwards the newly derived QoS policy to the AMF, including the QoS profile related to the QFI(s), QoS rules, and QoS flow-level QoS parameters (if necessary). Otherwise, the SMF responds to the AMF with a UE-triggered report rejection message.

[0204] In S806, if the PCF / SMF updates the SM policy, the AMF sends the QoS profile provided by the SMF to the RAN, including the QoS rules and QoS flow-level QoS parameters (if necessary) to be forwarded by the RAN to the UE. Otherwise, the AMF forwards the UE-triggered reporting rejection message provided by the SMF to the RAN.

[0205] In S807, if the PCF / SMF updates the SM policy, the RAN forwards the QoS rules and QoS flow-level QoS parameters (if necessary) provided in step 6 to the UE. Otherwise, the RAN forwards the UE-triggered reporting rejection message forwarded by the AMF to the UE, and the UE-triggered reporting process ends here.

[0206] In S808, if the PCF / SMF updates the SM policy, the RAN feeds back its accepted / rejected QFI list to the AMF. If the RAN rejects the QFI, the SMF is responsible for updating the QoS rules and QoS flow-level QoS parameters related to the rejected QoS flow in the UE accordingly.

[0207] In S809, if the PCF / SMF updates the SM policy, the AMF forwards the QoS feedback received from the RAN to the SMF. If the QoS feedback contains a rejected QFI list, the SMF shall release the QoS profile associated with the rejected QFI.

[0208] FIG9 shows a flow chart of a communication method for RAN triggered reporting in an embodiment of the present disclosure. As shown in FIG9 , the method may include steps S901 - S909 .

[0209] In S901, the RAN initiates the RAN-triggered reporting process by sending an N2 message to the AMF, which includes RAN-QDAI and the reporting type is set to RAN-triggered reporting.

[0210] In S902, the AMF forwards the RAN-QDAI reported by the RAN to the SMF.

[0211] In S903, the SMF may perform the SM policy association modification process with the PCF, and then the PCF provides the policy decision information to the SMF. If dynamic PCC is not deployed, the SMF may apply local policies to make SM policy decisions.

[0212] In S904, if the PCF / SMF updates the SM policy, the SMF sends it to the UPF, such as the packet detection rules, execution rules, reporting rules, etc. to be placed on the UPF. If the PCF / SMF does not update the SM policy, this step is skipped.

[0213] In S905, if the PCF / SMF updates the SM policy, the SMF forwards the newly derived QoS policy to the AMF, including the QoS profile related to the QFI(s), QoS rules, and QoS flow-level QoS parameters (if necessary). Otherwise, the SMF responds to the AMF with a RAN triggered report rejection message.

[0214] In S906, if the PCF / SMF updates the SM policy, the AMF sends the QoS profile provided by the SMF to the RAN, including the QoS rules and QoS flow-level QoS parameters (if necessary) to be forwarded by the RAN to the UE. Otherwise, the AMF forwards the RAN-triggered reporting rejection message provided by the SMF to the RAN, and the RAN-triggered reporting process ends here.

[0215] In S907, if the PCF / SMF updates the SM policy, the RAN forwards the QoS rules and QoS flow-level QoS parameters (if necessary) provided in step 6 to the UE.

[0216] In S908, if the PCF / SMF updates the SM policy, the RAN feeds back its accepted / rejected QFI list to the AMF. If the RAN rejects the QFI, the SMF is responsible for updating the QoS rules and QoS flow-level QoS parameters related to the rejected QoS flow in the UE accordingly.

[0217] In S909, if the PCF / SMF updates the SM policy, the AMF forwards the QoS feedback received from the RAN to the SMF. If the QoS feedback contains a rejected QFI list, the SMF shall release the QoS profile associated with the rejected QFI.

[0218] FIG10 shows a flow chart of a communication method for CN-triggered reporting in an embodiment of the present disclosure. As shown in FIG10 , the method may include steps S1001 - S1004 .

[0219] In S1001, the SMF or PCF may execute the SM Policy Association Modification Procedure to modify the reporting indication. If the SM Policy Association Modification Procedure is initiated by the SMF and no dynamic PCC is deployed, the SMF may apply local policies to determine whether to modify the reporting indication. If the SMF does not modify any reporting indication, the CN-triggered reporting procedure terminates here.

[0220] In S1002, the SMF forwards the modified reporting indication to the AMF.

[0221] In S1003, the AMF forwards the modified RAN reporting indication to the RAN, which also includes the UE reporting indication that will be forwarded by the RAN to the UE in S1004. If the RAN does not receive the UE reporting indication, S1004 is skipped.

[0222] The RAN forwards the modified UE reporting indication to the UE. When the periodic timer expires or the event-triggered reporting condition is met, the UE / RAN initiates the periodic / UE-triggered / RAN-triggered reporting process.

[0223] FIG11 shows a flow chart of a communication method in an embodiment of the present disclosure. As shown in FIG11 , the method may include step S1101 .

[0224] In S1101, the access network entity reports quality of service (QoS) decision-making auxiliary information to the core network entity, so that the core network entity makes a QoS decision based on the QoS decision-making auxiliary information.

[0225] The QoS decision-making auxiliary information includes QoS information related to the air interface.

[0226] FIG12 shows a flow chart of a communication method in an embodiment of the present disclosure. As shown in FIG12 , the method may include step S1201 .

[0227] In S1201, the user equipment reports the quality of service (QoS) decision-making auxiliary information to the core network entity, so that the core network entity makes a QoS decision based on the QoS decision-making auxiliary information.

[0228] The QoS decision-making auxiliary information includes service-related QoS information.

[0229] In the embodiments of the present disclosure, the terms “first,” “second,” and “third” are used for descriptive purposes only and should not be understood as indicating or implying relative importance.

[0230] In this disclosure, the term "and / or" simply describes an association relationship between related objects, indicating that three possible relationships exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0231] Furthermore, although the steps of the methods of the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in this particular order, or that all illustrated steps must be performed to achieve desired results.

[0232] In some embodiments, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0233] Based on the same inventive concept, a core network entity is further provided in an embodiment of the present disclosure. FIG13 shows a core network entity in an embodiment of the present disclosure. As shown in FIG13 , the core network entity includes:

[0234] The information acquisition module 1302 is configured to acquire quality of service (QoS) decision-making auxiliary information; the QoS decision-making auxiliary information includes service-related QoS information and / or air interface-related QoS information;

[0235] The decision module 304 is configured to make a QoS decision based on the QoS decision auxiliary information.

[0236] In some embodiments, the QoS decision-making auxiliary information includes first auxiliary information and / or second auxiliary information. Information acquisition module 1302 is configured to acquire the first auxiliary information reported by the access network entity and / or acquire the second auxiliary information reported by the user equipment, wherein the first auxiliary information is QoS information related to the air interface and the second auxiliary information is QoS information related to the service.

[0237] In some embodiments, the reporting type of the QoS decision-making assistance information reported by the access network entity and the user equipment includes one or more of the following types:

[0238] Initial reporting: the user device actively initiates the report;

[0239] Periodic reporting: User equipment initiates reporting periodically.

[0240] Event-triggered reporting: the user equipment actively initiates reporting based on the service status, or the access network entity actively initiates reporting based on the air interface status, or the core network entity requires the user equipment and / or access network entity to initiate reporting based on dynamic policies.

[0241] In some embodiments, the core network entity may further include:

[0242] The third message sending module is used to send a first reporting instruction to the access network entity, where the first reporting instruction is used to instruct the access network entity to report first auxiliary information.

[0243] In some embodiments, the first reporting indication is used to instruct the access network entity to enable or disable periodic reporting, and to instruct the access network entity to enable or disable event-triggered reporting.

[0244] In some embodiments, the core network entity may further include:

[0245] The fourth message sending module is configured to send a second reporting instruction to the user equipment, where the second reporting instruction is used to instruct the user equipment to report second auxiliary information.

[0246] In some embodiments, the second reporting indication is used to instruct the user equipment to enable or disable periodic reporting, and to instruct the user equipment to enable or disable event-triggered reporting.

[0247] In some embodiments, the first auxiliary information includes one or more of the following information:

[0248] Air interface status, notification control, references to alternative QoS profiles, and

[0249] Air interface requirements or recommendations for guaranteed flow bit rate, packet delay estimate, packet error rate, maximum flow bit rate, session aggregation maximum bit rate, user equipment aggregation maximum bit rate and / or UE slice maximum bit rate.

[0250] In some embodiments, the second auxiliary information includes one or more of the following information:

[0251] Describes the SDF's packet filter, requested packet filter action, and requested / proposed QoS.

[0252] In some embodiments, the core network entity may further include:

[0253] The policy issuing module is used to issue the QoS policy to the access network entity and / or user equipment for uplink and downlink transmission after making a QoS decision based on the QoS decision auxiliary information.

[0254] In some embodiments, the QoS policy includes a QoS profile and a QoS rule.

[0255] In some embodiments, the policy issuing module is configured to issue the QoS configuration file to the access network entity, and forward the QoS rules to the user equipment via the access network entity.

[0256] In some embodiments, the core network entity may further include:

[0257] The message receiving module is configured to receive a first feedback message sent by an access network entity, wherein the first feedback message includes a QoS flow list accepted by the access network entity and / or a QoS flow list rejected by the access network entity.

[0258] In some embodiments, the core network entity may further include:

[0259] The data processing module is configured to release a QoS configuration file related to the rejected QoS flow when the first feedback message includes a QoS flow list rejected by the access network entity.

[0260] In some embodiments, the QoS policy further includes QoS parameters at the QoS flow level;

[0261] The policy delivery module is used to forward QoS parameters of the QoS flow level to the user equipment through the access network entity.

[0262] In some embodiments, the QoS policy further includes a reporting indication;

[0263] The policy issuing module is used to issue the reporting instruction to the access network entity and / or user equipment.

[0264] In some embodiments, the reporting indication includes a first reporting indication and / or a second reporting indication;

[0265] A policy issuing module, configured to issue the first reporting instruction to the access network entity, and / or forward the second reporting instruction to the user equipment through the access network entity;

[0266] Among them, the first reporting indication is used to instruct the access network entity to enable or disable periodic reporting, and to instruct the access network entity to enable or disable event-triggered reporting; the second reporting indication is used to instruct the user equipment to enable or disable periodic reporting, and to instruct the user equipment to enable or disable event-triggered reporting.

[0267] Based on the same inventive concept, an access network entity is further provided in an embodiment of the present disclosure. FIG14 shows an access network entity in an embodiment of the present disclosure. As shown in FIG14 , the access network entity includes:

[0268] The first information sending module 1402 is configured to report the quality of service (QoS) decision-making auxiliary information to the core network entity, so that the core network entity makes a QoS decision based on the QoS decision-making auxiliary information;

[0269] The QoS decision-making auxiliary information includes QoS information related to the air interface.

[0270] Based on the same inventive concept, a user equipment is further provided in an embodiment of the present disclosure. FIG15 shows a user equipment in an embodiment of the present disclosure. As shown in FIG15 , the user equipment includes:

[0271] The second information sending module 1502 is configured to report the quality of service (QoS) decision-making auxiliary information to the core network entity, so that the core network entity makes a QoS decision based on the QoS decision-making auxiliary information;

[0272] The QoS decision-making auxiliary information includes service-related QoS information.

[0273] The concepts of "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0274] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, such division is not mandatory.

[0275] In fact, according to the embodiment of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0276] Some of the blocks shown in the accompanying drawings are functional entities that do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0277] The electronic device provided by an embodiment of the present disclosure is described below with reference to Figure 16. The electronic device 1600 shown in Figure 16 is merely an example and should not limit the functions and scope of use of the embodiment of the present disclosure.

[0278] FIG16 shows a schematic diagram of the architecture of an electronic device 1600 provided by an embodiment of the present disclosure. As shown in FIG16 , the electronic device 1600 includes but is not limited to: at least one processor 1610 and at least one memory 1620 .

[0279] The memory 1620 is used to store instructions.

[0280] In some embodiments, the memory 1620 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 16201 and / or a cache memory unit 16202 , and may further include a read-only memory unit (ROM) 16203 .

[0281] In some embodiments, memory 1620 may also include a program / utility 16204 having a set (at least one) of program modules 16205, such program modules 16205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0282] In some embodiments, the memory 1620 may store an operating system, which may be a real-time operating system (RTX), LINUX, UNIX, WINDOWS, or OS X.

[0283] In some embodiments, data may also be stored in the memory 1620 .

[0284] As an example, the processor 1610 may read data stored in the memory 1620 , where the data may be stored at the same storage address as the instruction, or the data may be stored at a different storage address from the instruction.

[0285] The processor 1610 is configured to call instructions stored in the memory 1620 to implement the steps of various exemplary embodiments of the present disclosure described in the "Exemplary Method" section above. For example, the processor 1610 may execute the steps of the aforementioned method embodiments.

[0286] It should be noted that the processor 1610 may be a general-purpose processor or a dedicated processor. The processor 1610 may include one or more processing cores, and the processor 1610 executes various functional applications and data processing by running instructions.

[0287] In some embodiments, the processor 1610 may include a central processing unit (CPU) and / or a baseband processor.

[0288] In some embodiments, the processor 1610 may determine an instruction based on the priority identifier and / or function category information carried in each control instruction.

[0289] In the present disclosure, the processor 1610 and the memory 1620 may be provided separately or integrated together.

[0290] As an example, the processor 1610 and the memory 1620 may be integrated on a single board or a system on chip (SOC).

[0291] 16 , the electronic device 1600 is implemented as a general-purpose computing device and may further include a bus 1630 .

[0292] The bus 1630 may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures.

[0293] The electronic device 1600 may also communicate with one or more external devices 1640 (e.g., a keyboard, a pointing device, a Bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 1600, and / or any device that enables the electronic device 1600 to communicate with one or more other computing devices (e.g., a router, a modem, etc.). Such communication may occur through an input / output (I / O) interface 1650.

[0294] Furthermore, the electronic device 1600 can also communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN) and / or a public network, such as the Internet) through the network adapter 1660 .

[0295] As shown in FIG. 16 , the network adapter 1660 communicates with other modules of the electronic device 1600 through the bus 1630 .

[0296] It should be understood that although not shown in the figures, other hardware and / or software modules may be used in conjunction with the electronic device 1600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0297] It should be understood that the structure illustrated in the embodiments of the present disclosure does not constitute a specific limitation on the electronic device 1600. In other embodiments of the present disclosure, the electronic device 1600 may include more or fewer components than those shown in FIG16, or may combine or separate certain components, or may have different component arrangements. The components shown in FIG16 may be implemented in hardware, software, or a combination of software and hardware.

[0298] The present disclosure also provides a computer-readable storage medium having computer instructions stored thereon. When the computer instructions are executed by a processor, the communication method described in the above method embodiment is implemented.

[0299] The computer-readable storage medium in the embodiments of the present disclosure is a computer instruction that can be sent, propagated or transmitted for use by or in conjunction with an instruction execution system, apparatus or device.

[0300] As an example, computer readable storage media are non-volatile storage media.

[0301] In some embodiments, more specific examples of computer-readable storage media in the present disclosure may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, a USB flash drive, a mobile hard disk, or any suitable combination of the foregoing.

[0302] In the embodiments of the present disclosure, the computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer instructions (readable program codes).

[0303] Such a propagated data signal may take any of a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof.

[0304] In some examples, computing instructions contained on a computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0305] The embodiments of the present disclosure further provide a computer program product, which stores instructions. When the instructions are executed by a computer, the computer implements the communication method described in the above method embodiment.

[0306] The above instructions may be program codes. In specific implementation, the program codes may be written in any combination of one or more programming languages.

[0307] Programming languages ​​include object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages.

[0308] The program code may execute entirely on the user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server.

[0309] Where a remote computing device is involved, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0310] The embodiment of the present disclosure further provides a chip, comprising at least one processor and an interface;

[0311] An interface for providing program instructions or data to at least one processor;

[0312] At least one processor is used to execute program instructions to implement the communication method described in the above method embodiment.

[0313] In some embodiments, the chip may further include a memory for storing program instructions and data, and the memory may be located inside or outside the processor.

[0314] Those skilled in the art will appreciate that all or part of the steps for implementing the above embodiments may be implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software, which may be collectively referred to herein as a "circuit," "module," or "system."

[0315] Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein.

[0316] This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the appended claims.

Claims

1. A communication method, characterized in that: Applied to a core network entity, the method comprises: Acquire quality of service (QoS) decision-making auxiliary information; the QoS decision-making auxiliary information includes QoS information related to the service and / or QoS information related to the air interface; A QoS decision is made based on the QoS decision auxiliary information.

2. The method according to claim 1, characterized in that The QoS decision-making auxiliary information includes first auxiliary information and / or second auxiliary information, and the obtaining of the quality of service QoS decision-making auxiliary information includes: Obtain the first auxiliary information reported by the access network entity, and / or, The second auxiliary information reported by the user equipment is obtained, wherein the first auxiliary information is QoS information related to the air interface, and the second auxiliary information is QoS information related to the service.

3. The method according to claim 2, characterized in that The reporting types of QoS decision-making auxiliary information reported by the access network entity and the user equipment include one or more of the following types: Initial reporting, initiated by the user equipment; Periodic reporting: User equipment initiates reporting periodically. Event-triggered reporting is initiated by the user equipment according to the service status, or by the access network entity according to the air interface status, or by the core network entity according to the dynamic policy.

4. The method according to claim 2, characterized in that: The method further comprises: A first reporting indication is sent to an access network entity, where the first reporting indication is used to instruct the access network entity to report first auxiliary information.

5. The method according to claim 4, characterized in that The first reporting indication is used to instruct the access network entity to enable or disable periodic reporting.

6. The method according to any one of claims 2 to 5, characterized in that: The method further comprises: A second reporting indication is sent to the user equipment, where the second reporting indication is used to instruct the user equipment to report second auxiliary information.

7. The method according to claim 6, characterized in that The second reporting instruction is used to instruct the user equipment to enable or disable periodic reporting.

8. The method according to claim 2, characterized in that: The first auxiliary information includes one or more of the following information: Air interface status, notification control, references to alternative QoS profiles, and Air interface requirements or recommendations for guaranteed flow bit rate, packet delay estimate, packet error rate, maximum flow bit rate, session aggregation maximum bit rate, user equipment aggregation maximum bit rate and / or UE slice maximum bit rate.

9. The method according to claim 2, characterized in that: The second auxiliary information includes one or more of the following information: Describes the SDF's packet filters, requested packet filter actions, and requested / proposed QoS.

10. The method according to claim 1, characterized in that The method further comprises: After making a QoS decision based on the QoS decision auxiliary information, the QoS policy is sent to the access network entity and / or the user equipment for uplink and downlink transmission.

11. The method according to claim 10, characterized in that The QoS policy includes a QoS configuration file and a QoS rule.

12. The method according to claim 10, characterized in that Send QoS policies to access network entities and / or user equipment, including: Send the QoS configuration file to the access network entity, and The QoS rules are forwarded to the user equipment through the access network entity.

13. The method according to claim 12, characterized in that The method further comprises: A first feedback message sent by the access network entity is received, wherein the first feedback message includes a list of QoS flows accepted by the access network entity and / or a list of QoS flows rejected by the access network entity.

14. The method according to claim 13, characterized in that The method further comprises: In a case where the first feedback message includes a list of QoS flows rejected by the access network entity, a QoS profile related to the rejected QoS flows is released.

15. The method according to claim 12, characterized in that The QoS policy also includes QoS parameters at the QoS flow level; The sending of the QoS policy to the access network entity and / or the user equipment further includes: The QoS parameters of the QoS flow level are forwarded to the user equipment through the access network entity.

16. The method according to claim 12, characterized in that The QoS strategy also includes a reporting indication; The sending of the QoS policy to the access network entity and / or the user equipment further includes: The reporting instruction is sent to the access network entity and / or the user equipment.

17. The method according to claim 16, characterized in that The reporting instruction includes a first reporting instruction and / or a second reporting instruction; Sending a reporting instruction to an access network entity and / or a user equipment includes: Sending the first reporting instruction to the access network entity, and / or Forwarding the second reporting instruction to the user equipment through the access network entity; The first reporting indication is used to instruct the access network entity to enable or disable periodic reporting; the second reporting indication is used to instruct the user equipment to enable or disable periodic reporting.

18. A communication method, characterized in that: Applied to an access network entity, the method comprises: Reporting quality of service (QoS) decision-making auxiliary information to a core network entity, so that the core network entity makes a QoS decision based on the QoS decision-making auxiliary information; The QoS decision-making auxiliary information includes QoS information related to the air interface.

19. A communication method, characterized in that: Applied to user equipment, the method comprises: Reporting quality of service (QoS) decision-making auxiliary information to a core network entity, so that the core network entity makes a QoS decision based on the QoS decision-making auxiliary information; The QoS decision-making auxiliary information includes QoS information related to the service.

20. A core network entity, characterized in that: include: An information acquisition module is used to obtain QoS decision-making auxiliary information; The QoS decision auxiliary information includes QoS information related to the service and / or QoS information related to the air interface; A decision module is used to make a QoS decision based on the QoS decision auxiliary information.

21. An access network entity, characterized in that: include: A first information sending module, configured to report quality of service QoS decision-making auxiliary information to a core network entity, so that the core network entity makes a QoS decision based on the QoS decision-making auxiliary information; The QoS decision-making auxiliary information includes QoS information related to the air interface.

22. A user equipment, characterized in that: include: A second information sending module is used to report the quality of service QoS decision auxiliary information to the core network entity, so that the core network entity makes a QoS decision based on the QoS decision auxiliary information; The QoS decision-making auxiliary information includes QoS information related to the service.

23. A communication system, characterized in that: include: User equipment; Access network entity; A core network entity is used to obtain service quality QoS decision-making auxiliary information reported by an access network entity and / or a user device, and make QoS decisions based on the QoS decision-making auxiliary information; wherein the QoS decision-making auxiliary information includes QoS information related to the service and / or QoS information related to the air interface.

Images