Communication method and apparatus

Abstract

The present application relates to the technical field of communications. Provided are a communication method and apparatus. The present application can simplify the process of updating a quality of service (QoS) configuration. The method comprises: an access network device determining a service feature update for a service during the process of performing service transmission by means of a quality of service (QoS) flow, wherein the updated service feature is used for determining a target QoS configuration of QoS; or the access network device receiving first information from a terminal device or a first core network device during the process of performing service transmission, wherein the first information is used for determining the target QoS configuration of the QoS flow; and the access network device updating a QoS configuration of the QoS flow on the basis of the target QoS configuration.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on July 31, 2023, with application number 202310960641.0 and application name “Communication Method and Device”, and the Chinese patent application filed with the State Intellectual Property Office of China on April 3, 2024, with application number 202410408362.8 and application name “Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a communication method and device. Background Art

[0003] In communication systems, a Quality of Service (QoS) flow is the finest QoS differentiation granularity within a Protocol Data Unit (PDU) session, carrying the service flows within that PDU session. Because the network requirements for services can change dynamically, such as the varying complexity of media content in different cloud gaming scenarios, which can lead to dynamic changes in media data volume, the QoS configuration for QoS flows also needs to be dynamically adjusted to meet these changing service requirements.

[0004] However, the existing QoS configuration adjustment process is cumbersome, requires multiple interactions with the core network, and has complex signaling interactions, making it difficult to meet dynamically changing business needs.

[0005] Summary of the Invention

[0006] In order to solve the above technical problems, this application provides a communication method and apparatus that can simplify the QoS configuration update process. To achieve the above objectives, this application adopts the following technical solutions:

[0007] In the first aspect, a communication method is provided. The execution subject of the method can be an access network device, or a component applied to the access network device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can realize all or part of the functions of the access network device. The following description is made by taking the execution subject as the access network device as an example. The method includes: the access network device determines the update of the service characteristics of the service during the service transmission through the quality of service QoS flow, and the updated service characteristics are used to determine the target QoS configuration of the QoS; or the access network device receives first information from a terminal device or a first core network device during the service transmission, and the first information is used to determine the target QoS configuration of the QoS flow. The access network device updates the QoS configuration of the QoS flow according to the target QoS configuration.

[0008] For example, the first information is used to indicate a target QoS configuration of the QoS flow.

[0009] For another example, the first information includes information about the target QoS configuration of the QoS flow. For example, in the target QoS configuration, the delay is 10 ms. The first information includes indication information that the delay is 10 ms.

[0010] For another example, the first information includes QoS requirement information corresponding to the target QoS configuration of the QoS flow. For example, in the target QoS configuration, the latency is 10ms. Accordingly, the QoS requirement information corresponding to the target QoS configuration is: the latency requirement for the service is within 10ms. The first information includes the QoS requirement information that the latency requirement is within 10ms.

[0011] The access network device updates the QoS configuration of the QoS flow, which can be understood as the access network device activating or establishing the QoS configuration of the QoS flow.

[0012] That is to say, during the service transmission process, when the access network device determines that the service characteristics of the service are updated or receives the first information, the access network device updates the QoS configuration of the QoS flow, thereby realizing dynamic adjustment of the QoS configuration of the QoS flow during the service transmission process. Compared with the multi-level QoS mechanism, the access network device is used to trigger the QoS configuration update, and the cumbersome process of adjusting the QoS configuration through the QoS notification control process and the protocol data unit PDU session modification process, the access network device described in this application can autonomously and quickly update the QoS configuration according to the changes in the service characteristics of the service or the first information from the terminal device or the first core network device, which simplifies the QoS configuration update process and effectively guarantees the dynamically changing service needs.

[0013] In one possible design, the method further includes: the access network device determining a target QoS configuration of the QoS flow based on the updated service characteristics or the first information.

[0014] In this way, when the target QoS configuration is determined based on the updated service characteristics, the updated QoS configuration of the QoS flow can also meet dynamically changing service requirements. Alternatively, when the target QoS configuration is determined based on the first information, since the first information is provided by the terminal device or the first core network device to the access network device, it can also represent the dynamic changes in the service characteristics of the service. The updated QoS configuration of the QoS flow can also meet dynamically changing service requirements.

[0015] In one possible design, the access network device determines the target QoS configuration of the QoS flow, including: the access network device determines the QoS parameters that need to be updated in the QoS configuration.

[0016] That is, the access network device determines the target QoS configuration by determining the QoS parameters that need to be updated, so as to meet the dynamically changing service requirements.

[0017] In one possible design, the access network device determines the QoS parameters that need to be updated in the QoS configuration based on the updated service characteristics, including: the access network device determines the target QoS parameters in the QoS configuration based on the updated service characteristics, and the target QoS parameters are the adjusted parameters of the QoS parameters that need to be updated; the access network device determines the target QoS configuration based on the target QoS parameters.

[0018] In one possible design, the access network device determines the QoS parameters that need to be updated in the QoS configuration based on the first information, including: the access network device determines the target QoS parameters in the QoS configuration based on the first information, and the target QoS parameters are the adjusted parameters of the QoS parameters that need to be updated; the access network device determines the target QoS configuration based on the target QoS parameters.

[0019] In one possible design, the method also includes: the access network device receives multiple QoS configurations for the QoS flow from the second core network device; the access network device determines the target QoS configuration of the QoS flow, including: the access network device determines the target QoS configuration from the multiple QoS configurations.

[0020] That is, the access network device determines the target QoS configuration from multiple QoS configurations for the QoS flow provided by the second core network device, thereby simplifying the processing process on the access network device side.

[0021] It can be understood that the access network device receives multiple QoS configurations pre-authorized for the QoS flow from the second core network device, and when the service characteristics of the service are updated or the first information from the terminal device is received or the first information from the first core network device is received, the access network device determines the target QoS configuration from the multiple QoS configurations. In addition, if none of the multiple QoS configurations can meet the QoS requirements corresponding to the updated service characteristics or the first information, the access network device refuses to execute the QoS configuration update.

[0022] In one possible design, the method also includes: the access network device receives one or more QoS parameter adjustment ranges for the QoS flow from the second core network device; the access network device determines the target QoS configuration of the QoS flow, including: the access network device determines the target QoS parameters within the one or more QoS parameter adjustment ranges; the access network device determines the target QoS configuration based on the target QoS parameters.

[0023] That is to say, the access network device obtains one or more pre-authorized QoS parameter adjustment ranges for the QoS flow from the second core network device. In addition, the access network device determines the QoS parameters that need to be updated based on the updated service characteristics or the first information from the terminal device or the first information from the first core network device, and determines the target QoS parameters within the QoS parameter adjustment range corresponding to the QoS parameters that need to be updated, and then determines the target QoS configuration based on the target QoS parameters. In addition, if none of the QoS parameters within the one or more QoS parameter adjustment ranges can meet the QoS requirements corresponding to the updated service characteristics or the first information, the access network device refuses to execute the QoS configuration update.

[0024] In one possible design, the method also includes: the access network device sends second information to the terminal device and / or the first core network device, the second information is used to indicate the target QoS configuration of the QoS flow, and the target QoS configuration indicated by the second information is determined by the access network device based on the updated service characteristics.

[0025] That is to say, when the access network device determines that the service characteristics of the service are updated, the access network device also indicates the target QoS configuration to the terminal device and / or the first core network device through the second information, so that the terminal device and / or the first core network device updates the QoS configuration of the QoS flow.

[0026] It can be understood that when the access network device determines that the service characteristics of the service are updated, the target QoS configuration is determined based on the updated service characteristics, and the second information is determined based on the target QoS configuration. The second information is used to indicate the target QoS configuration for the terminal device and / or the first core network device.

[0027] In one possible design, in the case where the first information comes from the first core network device, the method further includes: the access network device sends second information to the terminal device, the second information is used to indicate the target QoS configuration of the QoS flow, the target QoS configuration indicated by the second information is determined by the access network device based on the first information, or the first information is the same as the second information. Alternatively, in the case where the first information comes from the terminal device, the method further includes: the access network device sends second information to the first core network device, the second information is used to indicate the target QoS configuration of the QoS flow, the target QoS configuration indicated by the second information is determined by the access network device based on the first information, or the first information is the same as the second information.

[0028] That is to say, when the first information comes from the first core network device, it means that the first core network device triggers the access network device to perform a QoS configuration update. In this case, the access network device also instructs the terminal device to perform a QoS configuration update through the second information, thereby achieving a rapid QoS configuration update. Alternatively, when the first information comes from the terminal device, it means that the terminal device triggers the access network device to perform a QoS configuration update. In this case, the access network device also instructs the first core network device to perform a QoS configuration update through the second information, thereby achieving a rapid QoS configuration update.

[0029] In one possible design, the access network device determines whether to send the second information to the terminal device based on the target QoS configuration or the target QoS parameters; or the access network device determines whether to send the second information to the first core network device based on the target QoS configuration or the target QoS parameters. For example, in the target QoS configuration, the QoS parameter that needs to be updated is delay information. Since the delay information (such as packet delay budget (PDB)) does not need to be updated on the first core network device side, the access network device does not need to send the second information to the first core network device.

[0030] In one possible design, in the case where the access network device sends the second information to the terminal device, the method further includes: the access network device receives third information from the terminal device, the third information indicates that the terminal device has successfully updated the QoS configuration of the QoS flow, and the terminal device has updated the QoS configuration of the QoS flow based on the second information. Alternatively, in the case where the access network device sends the second information to the first core network device, the method further includes: the access network device receives fourth information from the first core network device, the fourth information indicates that the first core network device has successfully updated the QoS configuration of the QoS flow, and the first core network device has updated the QoS configuration of the QoS flow based on the second information.

[0031] That is, when the access network device instructs the terminal device to perform a QoS configuration update through the second information, the access network device also receives the third information fed back by the terminal device, and learns from the third information that the QoS configuration update on the terminal device side is successful. Alternatively, when the access network device instructs the first core network device to perform a QoS configuration update through the second information, the access network device also receives the fourth information fed back by the first core network device, and learns from the fourth information that the QoS configuration update on the first core network device side is successful.

[0032] In one possible design, when the access network device receives third information from the terminal device, the method further includes: the access network device sends fifth information to the first core network device, and the fifth information indicates that the terminal device and / or the access network device have successfully updated the QoS configuration of the QoS flow. Alternatively, when the access network device receives fourth information from the first core network device, the method further includes: the access network device sends sixth information to the terminal device, and the sixth information indicates that the first core network device and / or the access network device have successfully updated the QoS configuration of the QoS flow.

[0033] That is to say, in the case where the first core network device triggers the access network device to perform a QoS configuration update, the access network device also sends the fifth information to the first core network device, and feeds back the success of the QoS configuration update on the terminal device side and / or the access network device side through the fifth information, so that the first core network device obtains the QoS configuration update status. Alternatively, in the case where the terminal device triggers the access network device to perform a QoS configuration update, the access network device also sends the sixth information to the terminal device, and feeds back the success of the QoS configuration update on the first core network device side and / or the access network device side through the sixth information, so that the first core network device obtains the QoS configuration update status.

[0034] In one possible design, when the access network device sends second information to the terminal device, the second information is carried in the packet data convergence protocol PDCP layer of the first data packet, or the radio resource control RRC signaling, or the media access control control element MAC CE; the first data packet is the data packet sent by the access network device to the terminal device.

[0035] In one possible design, when the access network device sends second information to the first core network device, the second information is carried in the General Packet Radio Service Rate Protocol user plane GTP-U layer of the second data packet; the second data packet is the data packet sent by the access network device to the first core network device.

[0036] For example, the second data packet may be a service data packet of the service.

[0037] For another example, the second data packet may also be an empty packet generated by the access network device.

[0038] In one possible design, in the case where the first information comes from the first core network device, the method further includes: the access network device sends seventh information to the first core network device, and the seventh information is used to indicate that the access network device has failed to update the QoS configuration of the QoS flow. Alternatively, in the case where the first information comes from the terminal device, the method further includes: the access network device sends seventh information to the terminal device, and the seventh information is used to indicate that the access network device has failed to update the QoS configuration of the QoS flow.

[0039] For example, the access network device determines that the current network resources cannot support the target QoS configuration indicated by the first information, or the access network device determines that the target QoS configuration indicated by the first information is not within the pre-authorization range of the core network, such as the target QoS configuration is not within the multiple QoS configurations provided by the second core network device, or the QoS parameters of the target QoS configuration are not within the QoS parameter adjustment range provided by the second core network device.

[0040] That is to say, in the case where the first core network device triggers the access network device to perform a QoS configuration update, the access network device also sends the seventh information to the first core network device, and uses the seventh information to feedback the failure of the QoS configuration update on the access network device side, so that the first core network device obtains the QoS configuration update status. Alternatively, in the case where the terminal device triggers the access network device to perform a QoS configuration update, the access network device also sends the seventh information to the terminal device, and uses the seventh information to feedback the failure of the QoS configuration update on the access network device side, so that the terminal device obtains the QoS configuration update status.

[0041] In one possible design, when the access network device sends the seventh information to the first core network device, the method further includes: the access network device sends the eighth information to the first core network device, the eighth information is used to indicate the QoS configuration supported by the access network device, and the QoS configuration indicated by the eighth information is used by the first core network device to update the QoS configuration of the QoS flow. Alternatively, when the access network device sends the seventh information to the terminal device, the method further includes: the access network device sends the eighth information to the terminal device, the eighth information is used to indicate the QoS configuration supported by the access network device, and the QoS configuration indicated by the eighth information is used by the terminal device to update the QoS configuration of the QoS flow.

[0042] For example, the access network device determines the eighth information based on the current network resource status and / or multiple QoS configurations (or multiple QoS parameter adjustment ranges) for the QoS flow provided by the second core network device. For example, the first information indicates that the target QoS configuration has a latency requirement of 5ms, but the current network resources can only support a transmission latency of 10ms. In this case, the access network device generates the eighth information, and the QoS configuration indicated by the eighth information includes a latency requirement of 10ms.

[0043] That is to say, in the event that the QoS configuration update on the access network device side fails, the access network device also sends the eighth information to the terminal device or the first core network device, thereby indicating the QoS configuration supported by the access network device, so that the terminal device or the first core network device updates the QoS configuration according to the eighth information, thereby assisting the terminal device or the first core network device to update the QoS configuration.

[0044] In one possible design, the method further includes: the access network device obtaining time information, where the time information indicates a time period during which the target QoS configuration is valid. In other words, the target QoS configuration is time-sensitive and is only valid within a certain time period(s).

[0045] In one possible design, after the access network device obtains the time information, the method further includes: the access network device performing QoS configuration restoration outside the valid time period indicated by the time information. The QoS configuration restoration refers to restoring the QoS configuration of the QoS flow to the original QoS configuration.

[0046] For example, the time information is 10s. The access network device determines that the QoS configuration is updated, such as updating from QoS configuration 1 to the target QoS configuration, and 10s after the update process, the access network device performs the QoS configuration restoration to restore the target QoS configuration to QoS configuration 1.

[0047] For another example, the time information is the time period of 10:00-11:00. After 11:00, the access network device performs the QoS configuration restoration.

[0048] In one possible design, the method also includes: when the access network device determines that the service characteristics of the service are updated, the access network device sends the time information to the terminal device and / or the first core network device, so that the terminal device and / or the first core network device updates or restores the QoS configuration of the QoS flow according to the time information.

[0049] In one possible design, the method also includes: when the first information comes from the terminal device, the access network device sends the time information to the first core network device, so that the first core network device updates or restores the QoS configuration of the QoS flow according to the time information.

[0050] In one possible design, when the first information comes from the first core network device, the access network device sends the time information to the terminal device, so that the terminal device updates or restores the QoS configuration of the QoS flow based on the time information.

[0051] In one possible design, the access network device obtains time information, including: the access network device determines the time information, or the access network device receives the time information from the second core network device, or the access network device receives the time information from the terminal device, or the access network device receives the time information from the first core network device.

[0052] In one possible design, the access network device determines the service feature update of the service during the service transmission process, including: under a trigger condition, the access network device determines the service feature update of the service.

[0053] The triggering condition includes at least one of the following:

[0054] In the first item, a difference between a first data volume and a second data volume is greater than a threshold; the first data volume is the data volume of the service transmitted within a first time unit, and the second data volume is the data volume of the service transmitted within a second time unit. In other words, if the data volume of the service transmitted by the access network device changes and exceeds the threshold, the access network device determines that the service characteristics of the service have been updated.

[0055] The second item is that the QoS configuration of the QoS flow expires. That is, when the QoS configuration of the QoS flow expires, the access network device determines that the service feature of the service is updated.

[0056] In one possible design, the access network device updates the QoS configuration of the QoS flow, including: the access network device adjusts resources, and the adjusted resources are used to transmit the service with updated service characteristics.

[0057] That is, the access network device performs resource scheduling adjustment so that the adjusted resources adapt to the update of the service characteristics, thereby ensuring the transmission efficiency of the service and improving resource scheduling flexibility and resource utilization.

[0058] On the second aspect, a communication method is provided. The execution subject of the method can be a first communication device, or a component applied to the first communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can realize all or part of the functions of the first communication device. The following description is taken as an example that the execution subject is the first communication device. The method includes: the first communication device determines the service feature update of the service during the service transmission process through the quality of service QoS flow, and the first communication device is a terminal device or a first core network device. The first communication device sends first information to the access network device based on the updated service feature, and the first information is used to determine the target QoS configuration of the QoS flow.

[0059] That is to say, during the service transmission process, when the first communication device determines that the service characteristics of the service are updated, the first communication device sends the first information to the access network device, so that the access network device updates the QoS configuration of the QoS flow according to the first information, thereby realizing dynamic adjustment of the QoS configuration, simplifying the QoS configuration update process, and effectively guaranteeing dynamically changing service needs.

[0060] In one possible design, the first communication device sends first information to the access network device based on the updated service characteristics, including: the first communication device determines the target QoS configuration of the QoS flow based on the updated service characteristics, and the first communication device sends the first information based on the target QoS configuration of the QoS flow, where the first information is used to indicate the target QoS configuration of the QoS flow.

[0061] In other words, the first information is determined based on the updated service characteristics. Thus, the first communication device provides the first information to the access network device, triggering the access network device to directly perform a rapid update of the QoS configuration based on the first information, thereby meeting dynamically changing service requirements.

[0062] In one possible design, the method further includes: the first communication device determining the target QoS configuration based on the updated service characteristics. The first communication device determining the first information based on the target QoS configuration.

[0063] In other words, the target QoS configuration is determined based on the updated service characteristics. Thus, the first communications device indicates the target QoS configuration to the access network device via the first information, triggering the access network device to rapidly update the QoS configuration based on the first information, thereby enabling the updated QoS configuration to meet dynamically changing service requirements.

[0064] In one possible design, the method further includes: the first communication device determining the target QoS configuration based on the updated service characteristics.

[0065] In other words, the target QoS configuration is determined based on the updated service characteristics. In this way, when the first communication device indicates the target QoS configuration to the access network device, the access network device is triggered to quickly update the QoS configuration based on the target QoS configuration, thereby meeting dynamically changing service requirements.

[0066] In one possible design, the first communication device determines the target QoS configuration, including: the first communication device determines QoS parameters that need to be updated in the QoS configuration of the QoS flow.

[0067] That is, the first communication device determines the target QoS configuration by determining the QoS parameters that need to be updated to meet dynamically changing service requirements.

[0068] In one possible design, the method also includes: the first communication device receives multiple QoS configurations for the QoS flow from the second core network device; the first communication device determines the target QoS configuration, including: the first communication device determines the target QoS configuration from the multiple QoS configurations.

[0069] That is, the first communication device determines the target QoS configuration from multiple QoS configurations for the QoS flow provided by the second core network device, thereby simplifying the processing process on the first communication device side.

[0070] It can be understood that the first communication device receives multiple QoS configurations pre-authorized for the QoS flow from the second core network device, and when the service characteristics of the service are updated, the first communication device determines the target QoS configuration from the multiple QoS configurations. In addition, if none of the multiple QoS configurations can meet the updated service characteristics or the QoS requirements corresponding to the first information, the first communication device refuses to trigger the QoS configuration update.

[0071] In one possible design, the method also includes: the first communication device receives one or more QoS parameter adjustment ranges for the QoS flow from the second core network device; the first communication device determines the target QoS configuration of the QoS flow, including: the first communication device determines the target QoS parameters within the one or more QoS parameter adjustment ranges; the access network device determines the target QoS configuration based on the target QoS parameters.

[0072] That is, the first communication device obtains one or more pre-authorized QoS parameter adjustment ranges from the second core network device. Furthermore, the first communication device determines the QoS parameters that need to be updated based on the updated service characteristics, and determines the target QoS parameters within the QoS parameter adjustment range corresponding to the QoS parameters that need to be updated, and then determines the target QoS configuration based on the target QoS parameters. In addition, if none of the QoS parameters within the one or more QoS parameter adjustment ranges can meet the QoS requirements corresponding to the updated service characteristics, the first communication device refuses to trigger the QoS configuration update.

[0073] In one possible design, the method further includes: when the first communication device is the first core network device, the first communication device receives fifth information from the access network device, and the fifth information indicates that the terminal device and / or the access network device have successfully updated the QoS configuration of the QoS flow. Alternatively, when the first communication device is the terminal device, the first communication device receives sixth information from the access network device, and the sixth information indicates that the first core network device and / or the access network device have successfully updated the QoS configuration of the QoS flow.

[0074] That is to say, in the case where the first core network device triggers the access network device to perform a QoS configuration update, the access network device also sends the fifth information to the first core network device, and feeds back the success of the QoS configuration update on the terminal device side and / or the access network device side through the fifth information, so that the first core network device is informed of the QoS configuration update status. Alternatively, in the case where the terminal device triggers the access network device to perform a QoS configuration update, the access network device also sends the sixth information to the terminal device, and feeds back the success of the QoS configuration update on the first core network device side and the access network device side through the sixth information, so that the terminal device is informed of the QoS configuration update status.

[0075] In one possible design, the method further includes: the first communication device updates the QoS configuration of the QoS flow according to the target QoS configuration, thereby achieving an update of the QoS configuration.

[0076] In one possible design, when the first communication device is the first core network device, the method further includes: the first communication device receives fifth information from the access network device, the fifth information indicating that the terminal device and / or the access network device successfully updated the QoS configuration of the QoS flow, that is, the terminal device and / or the access network device successfully updated the QoS configuration of the QoS flow to the target QoS configuration. The first communication device updates the QoS configuration of the QoS flow according to the target QoS configuration indicated by the fifth information, thereby implementing the update of the QoS configuration.

[0077] In one possible design, when the first communication device is the terminal device, the method further includes: the first communication device receives sixth information from the access network device, and the sixth information indicates that the first core network device and / or the access network device successfully updated the QoS configuration of the QoS flow, that is, the first core network device and / or the access network device successfully updated the QoS configuration of the QoS flow to the target QoS configuration. The first communication device updates the QoS configuration of the QoS flow according to the target QoS configuration indicated by the sixth information, thereby realizing the update of the QoS configuration.

[0078] In one possible design, the first communication device receives seventh information from the access network device, and the seventh information indicates that the access network device has failed to update the QoS configuration of the QoS flow. The access network device updates the QoS configuration of the QoS flow based on the first information, thereby enabling the first communication device to obtain the QoS configuration update status on the access network device side.

[0079] In one possible design, the method further includes: the first communication device receiving eighth information from the access network device, where the eighth information is used to indicate the QoS configuration supported by the access network device.

[0080] That is to say, in the event that the QoS configuration update on the access network device side fails, the access network device also sends the eighth information to the first communication device, thereby indicating the QoS configuration supported by the access network device, so that the first communication device updates the QoS configuration according to the eighth information, thereby assisting the first communication device in updating the QoS configuration.

[0081] In one possible design, the method further includes: the first communication device updates the QoS configuration of the QoS flow according to the QoS configuration indicated by the eighth information, thereby providing a probability of successful QoS configuration update to meet dynamically changing business needs as much as possible.

[0082] In one possible design, the first information is carried in the packet data convergence protocol PDCP layer or the general packet radio service rate protocol user plane GTP-U layer of the first data packet, or the radio resource control RRC signaling, or the media access control control element MAC CE, and the first data packet is a data packet sent by the first communication device to the access network device.

[0083] In one possible design, the first communication device obtains time information, where the time information indicates a time period during which the target QoS configuration is valid. In other words, the target QoS configuration is time-sensitive and is only valid within a certain time period(s).

[0084] In one possible design, after the first communication device obtains the time information, the method further includes: the first communication device performing QoS configuration restoration outside the valid time period indicated by the time information. The QoS configuration restoration refers to restoring the QoS configuration of the QoS flow to the original QoS configuration.

[0085] For example, the time information is 10s. The first communication device determines the QoS configuration update, such as updating from QoS configuration 1 to the target QoS configuration, and after 10s of the update process, the first communication device performs the QoS configuration recovery and updates the target QoS configuration to QoS configuration 1.

[0086] For another example, the time information is the time period from 10:00 to 11:00. After 11:00, the first communication device performs the QoS configuration restoration.

[0087] In one possible design, the method further includes: the first communication device sending the time information to the access network device, so that the access network device updates or restores the QoS configuration of the QoS flow based on the time information.

[0088] In one possible design, the first communication device obtains time information, including: the first communication device determines the time information, or the first communication device receives the time information from the second core network device.

[0089] In one possible design, the first communications device determines, during service transmission, that a service feature of the service is updated, including:

[0090] Under a trigger condition, the first communication device determines that a service feature of the service is updated.

[0091] The triggering condition includes at least one of the following:

[0092] In the first item, the difference between the first data volume and the second data volume is greater than a threshold. The first data volume is the data volume of the service transmitted within the first time unit, and the second data volume is the data volume of the service transmitted within the second time unit. In other words, if the data volume of the service transmitted by the first communications device changes and exceeds the threshold, the first communications device determines that the service characteristics of the service have been updated.

[0093] The second item is obtaining a notification message, where the notification message indicates the network requirements of the service.

[0094] For example, in a case where the first communication device is the terminal device, the terminal device receives notification information from the application layer, so that the first communication device is informed of the service feature update of the service.

[0095] For another example, when the first communication device is the first core network device, the first core network device receives a notification message from an application server. For example, the first core network device receives a downlink data packet from the application server, the downlink data packet carries the notification message, the notification message indicates that the service network requirement has changed, or the notification message indicates the target network requirement of the service, thereby enabling the first communication device to be informed of the service feature update of the service.

[0096] The third item is that the QoS configuration of the QoS flow expires. That is, when the QoS configuration of the QoS flow expires, the first communication device determines that the service feature of the service is updated.

[0097] In the third aspect, a communication method is provided. The execution subject of the method can be a second communication device, or a component applied to the second communication device (such as a processor, a chip, or a chip system, etc.), or a logic module or software that can realize all or part of the functions of the second communication device. The following description is taken as an example that the execution subject is the second communication device. The method includes: the second communication device receives second information from the access network device, the second information is used to indicate the target QoS configuration of the quality of service QoS flow, the QoS flow is used for service transmission between the terminal device and the first core network device, and the second communication device is the terminal device or the first core network device; the second communication device updates the QoS configuration of the QoS flow to the target QoS configuration.

[0098] That is to say, during the service transmission process, the access network device instructs the second communication device to update the QoS configuration through the second information, so that the second communication device performs QoS configuration update according to the second information, realizes dynamic adjustment of QoS configuration, simplifies the QoS configuration update process, and effectively guarantees dynamically changing service needs.

[0099] In one possible design, the method further includes: the second communication device sending third information to the access network device, wherein the third information indicates that the second communication device has successfully updated the QoS configuration of the QoS flow.

[0100] That is to say, when the access network device instructs the second communication device to perform QoS configuration update through the second information, the access network device also receives the third information fed back by the second communication device, and learns through the third information that the QoS configuration update on the second communication device side is successful.

[0101] In one possible design, the method further includes: the second communication device obtaining time information, where the time information indicates a time period during which the target QoS configuration is valid. In other words, the target QoS configuration is time-sensitive and is only valid within a certain time period(s).

[0102] In one possible design, the method further includes: the second communication device restoring the QoS configuration of the QoS flow based on the time information. In other words, the second communication device restores the QoS configuration of the QoS flow based on the time information.

[0103] For example, the time information is 10s. The second communication device determines the QoS configuration update, such as updating from QoS configuration 1 to the target QoS configuration, and after 10s of the update process, the second communication device performs QoS configuration recovery and updates the target QoS configuration to QoS configuration 1.

[0104] For another example, the time information is the time period from 10:00 to 11:00. After 11:00, the second communication device performs QoS configuration recovery.

[0105] In one possible design, the second information is carried in the packet data convergence protocol PDCP layer or the general packet radio service rate protocol user plane GTP-U layer of the first data packet, or the radio resource control RRC signaling, or the media access control control element MAC CE, and the first data packet is a data packet received by the second communication device from the access network device.

[0106] In a fourth aspect, a communication method is provided. The execution subject of the method may be a third core network device, or a component (such as a processor, a chip, or a chip system, etc.) applied to the third core network device, or a logic module or software that can realize all or part of the functions of the third core network device. The following description is made by taking the execution subject as the third core network device as an example. The method includes: the third core network device obtains quality of service QoS information, and the QoS information includes a first QoS requirement and a second QoS requirement of the service; the third core network device determines a policy and charging control PCC rule based on the QoS information. The PCC rule indicates a QoS configuration, and when the first QoS parameter of the QoS configuration is a first value, the QoS configuration meets the first QoS requirement; when the first QoS parameter of the QoS configuration is a second value, the QoS configuration meets the second QoS requirement; or, the PCC rule indicates multiple QoS configurations, and the first QoS configuration of the multiple QoS configurations meets the first QoS requirement, and the second QoS configuration of the multiple QoS configurations meets the second QoS requirement.

[0107] That is to say, the third core network device can determine the QoS configuration according to the different QoS requirements of the service during operation, so that the QoS configuration meets the different QoS requirements of the service, laying the foundation for the QoS configuration update during the service transmission process.

[0108] In one possible design, the QoS information further includes at least one of the following:

[0109] The first item is the effectiveness conditions, which include the conditions for the effectiveness of the first QoS requirement and the conditions for the effectiveness of the second QoS requirement, so that the third core network device can know the conditions for the effectiveness of different QoS requirements of the service, which helps the third core network device to determine the effective time period of the QoS configuration.

[0110] The second item is a trigger condition, which is used to determine whether the service characteristics of the service are updated, thereby determining whether to trigger the update of the QoS configuration.

[0111] The third item is device information, where the device information indicates the communication device that uses the trigger condition, thereby indicating which communication device triggers the update of the QoS configuration.

[0112] In one possible design, the third core network device obtains QoS information, including: the third core network device receives the QoS information from the application server AF.

[0113] That is, the third core network device obtains the QoS information from the application server.

[0114] In one possible design, the service is transmitted between the terminal device and the first core network device via a QoS flow. The PCC rule further includes at least one of the following:

[0115] The first item is the first indication information, which indicates that the QoS configuration of the QoS flow is updateable, so that the terminal device, access network device or first core network device dynamically adjusts the QoS configuration of the QoS flow.

[0116] The second item, second indication information, instructs a communication device to update the QoS configuration of the QoS flow, where the communication device is the terminal device, the first core network device, or the access network device. In other words, the communication device is instructed by the third core network device to trigger the update of the QoS configuration.

[0117] The third item is the effectiveness conditions, which include the conditions for the effectiveness of the first QoS requirement and the conditions for the effectiveness of the second QoS requirement.

[0118] The fourth item is a trigger condition, which is used to determine whether the service characteristics of the service are updated.

[0119] The fifth item is device information, where the device information indicates the communication device that uses the trigger condition.

[0120] In one possible design, the method also includes: the third core network device sends the PCC rules to the second core network device through a first process, and the first process includes a protocol data unit PDU session establishment process or a PDU session modification process.

[0121] That is, the third core network device provides the PCC rule to the second core network device, so that the second core network device configures parameters for the terminal device, the access network device or the first core network device according to the PCC rule.

[0122] In a fifth aspect, a communication device is provided for implementing the various methods described above. The communication device includes modules, units, or means corresponding to the implementation methods. The modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the functions.

[0123] In some possible designs, the communication device may include a processing module and a transceiver module. The processing module may be used to implement the processing functions in any of the above aspects and any possible implementations thereof. The transceiver module, also referred to as a transceiver unit, is used to implement the sending and / or receiving functions in any of the above aspects and any possible implementations thereof. The transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface.

[0124] In some possible designs, the transceiver module includes a sending module and / or a receiving module, which are used to implement the sending or receiving functions in any of the above aspects and any possible implementation methods.

[0125] In a sixth aspect, a communication device is provided, comprising: a processor and a memory, wherein the processor and the memory are coupled, and the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, the communication device executes a method as in any one of the above aspects or any possible design of any one of the aspects.

[0126] In a seventh aspect, a communication device is provided, comprising: a processor; the processor is configured to execute a computer program or instruction so that the communication device executes the method described in any one of the aspects.

[0127] Optionally, the communication device further includes a memory, which may be coupled to the processor, or may exist independently of the processor, for example, the memory and the processor are two independent modules. The memory may be located outside the communication device or inside the communication device.

[0128] In an eighth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any one of the aspects.

[0129] In a ninth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, enables the communication device to execute the method described in any one of the aspects.

[0130] The communication device provided in any one of the fifth to ninth aspects may be the access network device in the first aspect, or a component in the access network device, such as a chip or a chip system; or, the communication device may be the first communication device in the second aspect, or a component in the first communication device, such as a chip or a chip system; or, the communication device may be the second communication device in the third aspect, or a component in the second communication device, such as a chip or a chip system; or, the communication device may be the third core network device in the fourth aspect, or a component in the third core network device, such as a chip or a chip system. Where the device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices.

[0131] It can be understood that when the communication device provided in any one of the fifth to ninth aspects is a chip, the sending action / function of the communication device can be understood as output information, and the receiving action / function of the communication device can be understood as input information.

[0132] Among them, the technical effects brought about by any design method in the fifth to ninth aspects can refer to the technical effects brought about by different design methods in the first to fourth aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0133] FIG1 is a schematic diagram of the architecture of a communication system used in an embodiment of the present application.

[0134] FIG2 a is a schematic diagram of the architecture of another communication system used in an embodiment of the present application.

[0135] FIG2b is a user plane protocol provided in an embodiment of the present application.

[0136] FIG3 is a flow chart of a multi-level QoS mechanism provided in an embodiment of the present application.

[0137] FIG4 is a schematic diagram of a reflective QoS mechanism provided in an embodiment of the present application.

[0138] FIG5 is a flow chart of a communication method provided in an embodiment of the present application.

[0139] FIG6 is a flow chart of another communication method provided in an embodiment of the present application.

[0140] FIG7 is a flow chart of another communication method provided in an embodiment of the present application.

[0141] FIG8 is a flow chart of another communication method provided in an embodiment of the present application.

[0142] FIG9 is a flow chart of another communication method provided in an embodiment of the present application.

[0143] FIG10 is a flow chart of another communication method provided in an embodiment of the present application.

[0144] FIG11 is a flow chart of another communication method provided in an embodiment of the present application.

[0145] FIG12 is a flow chart of another communication method provided in an embodiment of the present application.

[0146] FIG13 is a flow chart of another communication method provided in an embodiment of the present application.

[0147] FIG14 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0148] FIG15 is a schematic structural diagram of another communication device provided in an embodiment of the present application.

[0149] FIG16 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0150] The embodiment of the present application can be applied to the communication system shown in Figure 1. The communication system can be a communication system that supports fourth generation (4G) access technology, such as long term evolution (LTE) access technology; or, the communication system can also be a communication system that supports fifth generation (5G) access technology, such as new radio (NR) access technology; or, the communication system can also be a communication system that supports multiple wireless technologies, such as a communication system that supports LTE access technology and NR access technology. In addition, the communication system can also be applicable to future-oriented communication technologies.

[0151] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. As shown in Figure 1, the communication system includes terminal devices and network devices. The network devices include access network (AN) devices and core network (CN) devices. The access network devices can also be replaced with radio access network (RAN) devices.

[0152] The terminal device accesses the core network via an access network device or a radio access network device. The terminal device includes a device that provides voice and / or data connectivity to the user. Specifically, it includes a device that provides voice to the user, a device that provides data connectivity to the user, or a device that provides both voice and data connectivity to the user. For example, it may include a handheld device with wireless connectivity or a processing device connected to a wireless modem. The terminal device can communicate with the core network via the radio access network, exchange voice or data with the RAN, or exchange voice and data with the RAN. The terminal device may include user equipment (UE), wireless terminal device, mobile terminal device, device-to-device (D2D) terminal device, vehicle-to-everything (V2X) terminal device, machine-to-machine / machine-type communications (M2M / MTC) terminal device, Internet of Things (IoT) terminal device, subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user device, etc. For example, it may include a mobile phone (or "cellular" phone), a computer with a mobile terminal device, a portable, pocket-sized, handheld, or computer-built-in mobile device, etc. Examples include personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). Also included are limited devices, such as those with low power consumption, limited storage capacity, or limited computing power. Examples include information sensing devices such as barcode scanners, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners.

[0153] The various terminal devices introduced above, if located on a vehicle (eg, placed in or installed in a vehicle), can be considered as vehicle-mounted terminal devices, which are also called on-board units (OBUs).

[0154] In the embodiment of the present application, the terminal device may further include a relay. Alternatively, it can be understood that anything that can communicate data with a base station can be considered a terminal device.

[0155] In the embodiments of the present application, the apparatus for implementing the functions of the terminal device may be the terminal device, or may be an apparatus capable of supporting the terminal device in implementing the functions, such as a chip system, which may be installed in the terminal device. In the embodiments of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices. In the technical solutions provided in the embodiments of the present application, the apparatus for implementing the functions of the terminal device is described as an example of a terminal device.

[0156] The access network device can be a device that connects a terminal device to a wireless network. The access network device in the embodiment of the present application may include various forms of base stations, for example, a macro base station, a micro base station (also known as a small station), a relay station, an access point, a transmitting point (TP), an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G communication system, a device that implements base station functions in a communication system evolved after 5G, a mobile switching center, and a device that assumes base station functions in D2D, V2X, and M2M communications; it can also be an access network device in a non-terrestrial network (NTN) communication system, that is, it can be deployed on a high-altitude platform or satellite; it can also be a module or unit that completes part of the functions of a base station, for example, it can be a centralized unit (CU) in a cloud radio access network (C-RAN) system, or it can be a distributed unit (DU). The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device. All or part of the functions of the access network device may also be implemented through software functions running on hardware, or through virtualized functions instantiated on a platform (e.g., a cloud platform). In the embodiments of this application, unless otherwise specified, the access network device refers to the RAN device.

[0157] The different core network devices of the core network are introduced as follows:

[0158] User plane network element: This element is used for packet routing and forwarding, as well as quality of service (QoS) processing for user plane data. As shown in Figure 2a, in a 5G communication system, the user plane network element may be a user plane function (UPF) network element. In future communication systems, the user plane network element may still be a UPF network element, or may have other names, which are not limited in this embodiment of the present application.

[0159] Data network (DN) element: A network used to provide data transmission. As shown in Figure 2a, in a 5G communication system, the data network can be a DN. In future communication systems, the data network can still be a DN, or it can have other names, which are not limited in this embodiment of the application.

[0160] Authentication service network element: used for authentication services, generating keys to achieve two-way authentication of terminal devices, and supporting a unified authentication framework. As shown in Figure 2a, in a 5G communication system, the authentication service network element can be an authentication server function (AUSF) network element. In future communication systems, the authentication server function network element can still be an AUSF network element, or it can have other names, which is not limited in the embodiments of the present application.

[0161] Access and mobility management network element: used for mobility management and access management, etc., and can be used to implement other functions of the mobility management entity (MME) in addition to session management, such as lawful interception and access authorization / authentication. As shown in Figure 2a, in a 5G communication system, the access and mobility management network element can be an access and mobility management function (AMF) network element. In future communication systems, the access and mobility management network element can still be an AMF network element, or it can have other names, which is not limited in the embodiments of the present application.

[0162] Session management network element: This element is primarily used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of endpoints for manageable user plane functions, policy control, and charging function interfaces, and downlink data notification. As shown in Figure 2a, in a 5G communication system, the session management network element may be a session management function (SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or may have other names, which are not limited in this embodiment of the present application.

[0163] Service communication function network element: used to provide communication selection between network function (NF) network elements. As shown in Figure 2a, in a 5G communication system, the service communication function network element can be a service communication function (SCP) network element. In future communication systems, the service communication function network element can still be an SCP network element, or it can have other names, which are not limited in this embodiment of the present application.

[0164] The network data analysis function network element is used for network data analysis functions and provides network data collection and analysis services based on technologies such as big data and artificial intelligence. As shown in Figure 2a, in a 5G communication system, the network data analysis function network element can be a network data analysis function (NWDAF) network element. In future communication systems, the network data analysis function network element can still be an NWDAF network element, or it can have other names, such as network analysis network element or network analysis function network element, which is not limited in the embodiments of the present application.

[0165] Network capability exposure function network element: used to provide network customization functions. As shown in Figure 2a, in a 5G communication system, the network capability exposure function network element can be a network capability exposure function (NEF) network element. In future communication systems, the network capability exposure function network element can still be an NEF network element, or it can have other names, which are not limited in the embodiments of the present application.

[0166] Network storage network element: used to maintain real-time information of all network function services in the network. As shown in Figure 2a, in a 5G communication system, the network storage network element can be a network repository function (NRF) network element. In future communication systems, the network storage network element can still be an NRF network element, or it can have other names, which are not limited in this embodiment of the application.

[0167] Policy control network element: a unified policy framework for guiding network behavior, providing policy rule information for control plane network elements (such as AMF network elements, SMF network elements, etc.). In a 4G communication system, the policy control network element may be a policy and charging rules function (PCRF) network element. As shown in Figure 2a, in a 5G communication system, the policy control network element may be a policy control function (PCF) network element. In future communication systems, the policy control network element may still be a PCF network element, or it may have other names, which is not limited in the embodiments of the present application.

[0168] Data management network element: This element is used to process terminal device identification, access authentication, registration, and mobility management. As shown in Figure 2a, in a 5G communication system, the data management network element can be a unified data management (UDM) network element. In future communication systems, the data management network element can still be a UDM network element, or it can have other names, which are not limited in this embodiment of the application.

[0169] Application network element: used for data routing affected by applications, accessing network open function network elements, interacting with the policy framework for policy control, etc. As shown in Figure 2a, in a 5G communication system, the application network element can be an application function (AF) network element. In future communication systems, the application network element can still be an AF network element, or it can have other names, such as application server (AS), service server, third-party server, etc., which are not limited in this embodiment of the present application. In this embodiment of the present application, the application server is used as an example for introduction.

[0170] Referring to Figure 2a, a terminal device accesses the 5G network through an (R)AN device. The terminal device communicates with the AMF network element through the N1 interface (N1 for short); the (R)AN device communicates with the AMF network element through the N2 interface (N2 for short); the (R)AN device communicates with the UPF network element through the N3 interface (N3 for short); the SMF network element communicates with the UPF network element through the N4 interface (N4 for short); the UPF network element accesses the DN through the N6 interface (N6 for short); and different UPF network elements communicate with each other through the N9 interface (N9 for short). In the architecture shown in Figure 2a, N1, N2, N3, N4, N6, and N9 represent reference points between related network elements / network functions. (R)AN devices refer to AN devices or RAN devices.

[0171] In addition, the control plane functions such as the AUSF network element, AMF network element, SMF network element, NWDAF network element, NEF network element, NRF network element, PCF network element, UDM network element or AF network element shown in Figure 2a use service-based interfaces for interaction. For example, the service-based interface provided by the AUSF network element to the outside is Nausf; the service-based interface provided by the AMF network element to the outside is Namf; the service-based interface provided by the SMF network element to the outside is Nsmf; the service-based interface provided by the NWDAF network element to the outside is Nnwdaf; the service-based interface provided by the NEF network element to the outside is Nnef; the service-based interface provided by the NRF network element to the outside is Nnrf; the service-based interface provided by the PCF network element to the outside is Npcf; the service-based interface provided by the UDM network element to the outside is Nudm; and the service-based interface provided by the AF network element to the outside is Naf. For relevant function descriptions and interface descriptions, please refer to the 5G system architecture diagram in the 23501 standard, which will not be repeated here.

[0172] Optionally, each of the above-mentioned core network devices can be implemented by a single device, or by multiple devices, or as a functional module within a single device, and this is not specifically limited in the embodiments of the present application. It is understood that the above-mentioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0173] Optionally, in the embodiments of the present application, the term "network element" can be replaced with "entity", "device", etc. For example, "AMF network element" can also be written as "AMF entity" or "AMF device", and "SMF network element" can also be written as "SMF entity" or "SMF device", etc. In addition, in some embodiments, for the convenience of description, "XXX network element" is abbreviated as "XXX", for example, "AUSF network element" can also be abbreviated as "AUSF", and "SMF network element" can also be abbreviated as "SMF". In the embodiments of the present application, XXX network element is used as an example for introduction, and a unified explanation is given here, which will not be repeated below.

[0174] FIG2 b shows a user plane protocol model from a terminal device to an application server.

[0175] In this protocol model, from top to bottom, it includes the application layer, transport layer, network layer, link layer, and physical layer.

[0176] In Figure 2b, the connection for sending and receiving data is located in the transport layer, which is the end-to-end protocol layer from the terminal device to the application server. The relevant protocols of the transport layer include the Quick User Datagram Protocol Internet Connection (QUIC) protocol and the User Datagram Protocol (UDP), or the relevant protocols of the transport layer include the UDP protocol, or the relevant protocols of the transport layer include the Transmission Control Protocol (TCP), etc.

[0177] It is easy to understand that in some protocol division models, the QUIC protocol is divided into an application layer protocol rather than a transport layer protocol.

[0178] Below the network layer, several different 3GPP network protocol stacks connect from the terminal device to the access network device, and from the access network device to the user plane network element. Specifically, the 3GPP network protocol stack between the terminal device and the access device includes the service data adaptation protocol (SDAP) layer, the packet data convergence protocol (PDCP) layer, and lower protocol layers, including the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The 3GPP network protocol stack between the access network device and the user plane network element includes the general packet radio service (GPRS) tunneling protocol for the user plane (GTP-U) layer and lower protocol layers, including the user datagram protocol (UDP) layer / internet protocol (IP) layer, layer 2 (L2), and layer 1 (L1). Among them, access network equipment and user plane network elements belong to the 3GPP network.

[0179] The GTP-U layer includes the GTP-U tunnel. The GTP-U tunnel is a connection tunnel between the access network device and the user plane network element (such as the 5G-AN device and UPF network element in Figure 2b). Data from / to the terminal device is added to the GTP-U tunnel for transmission. The GTP-U tunnel is PDU-session granular, meaning that for each PDU session, a GTP-U tunnel is established between the access network device and the user plane network element.

[0180] The network protocol stack between the terminal device and the user plane network element includes the network layer. The network protocol stack between the user plane network element and the application server includes the network layer, link layer and physical layer.

[0181] To facilitate understanding of the embodiments of the present application, the following briefly describes the relevant technologies or terms involved in the embodiments of the present application. It should be understood that these descriptions are only for the purpose of facilitating understanding of the embodiments of the present application and should not constitute any limitation on the present application.

[0182] 1. QoS Flow

[0183] In a communication system, when a terminal device has a business communication requirement, a protocol data unit (PDU) session is established. A PDU session may include one or more QoS flows, and each QoS flow is used to carry a business flow. Among them, the QoS flow can be pre-configured, the QoS flow can also be established through the PDU session establishment process, and the QoS flow can also be established through the PDU session modification process. A QoS flow identity (QFI) is used to identify a QoS flow. User-plane data with the same QFI in a PDU session will receive the same forwarding processing (such as the same scheduling, the same access threshold, etc.).

[0184] In a communication system, QoS flows can be controlled by SMF network elements.

[0185] For example, the SMF network element can send QoS rules (e.g., QoS rules) for QoS flows to the terminal device. The QoS rules include QFI, packet filter set, QoS rule ID, etc. The terminal device can classify and mark the uplink service flow according to the QoS rules. That is, the terminal device can associate the uplink data with the corresponding QoS flow according to the QoS rules.

[0186] For example, the SMF network element can send a QoS description (e.g., QoS profile) of a QoS flow to the access network device. The QoS description can include a 5G QoS identifier (5QI), allocation and retention priority (ARP), guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), QFI, etc. One QoS description corresponds to one QFI. The access network device can control the service flow based on the QoS description.

[0187] It should be noted that in the embodiments of the present application, QoS description may also have other names, such as QoS profile, QoS document, QoS archive, QoS file, QoS configuration, QoS configuration file, QoS configuration document, etc. In the embodiments of the present application, QoS description is used as an example for introduction, which should not be understood as limiting the embodiments of the present application. In the embodiments of the present application, QoS description may refer to QoS profile. QoS profile can refer to the relevant 3GPP technical specifications and will not be repeated here.

[0188] For example, the SMF network element can send the N4 rules (e.g., N4 rule) of the QoS flow to the user plane network element. The N4 rules include packet detection rules, usage reporting rules, and QoS enforcement rules. The QoS enforcement rules include the maximum bit rate, guaranteed bit rate (GBR), and average window.

[0189] Among them, the types of QoS flows can be divided into the following types: guaranteed bit rate (GBR) QoS flow, delay-critical GBR QoS flow and non-guaranteed bit rate (Non-GBR) QoS flow.

[0190] It should be noted that in the embodiments of the present application, the following descriptions have the same meaning and can be replaced with each other: configuration of QoS flow, QoS configuration. They are described here as a unified description and will not be repeated in the following text.

[0191] 2. Video surveillance scenarios

[0192] In video surveillance scenarios, the video capture device typically has a certain level of local processing capabilities. When no target event is detected, the device simply continuously captures and stores video, periodically notifying the remote server that everything is normal. However, when a target event is triggered, such as an event of interest, the device transmits high-definition video back to the remote server. This generates a sudden surge in uplink traffic, meaning a large amount of uplink data needs to be transmitted.

[0193] 3. Cloud extended reality (XR), cloud gaming, and cloud photography scenarios

[0194] Real-time media services, such as the emerging augmented reality (AR), virtual reality (VR), mixed reality (MR), cloud gaming, and cloud photography, have extremely stringent requirements for end-to-end latency. Furthermore, due to factors such as adaptive frame rate adjustments and user behavior triggers, transmission traffic is sporadic, and the amount of data transmitted is unpredictable.

[0195] For example, for services like cloud gaming, media frames are sent from the cloud server to the terminal device. Due to the diversity of game content and user behavior, the sizes of different media frames are irregular, and the network side cannot predict the size of the downlink media frames.

[0196] For example, in cloud photography services, when a user clicks the photo button, the terminal device sends the uncompressed raw image data to the cloud server. The cloud server then performs noise reduction, sharpening, compression, and encoding on the raw image data, and promptly sends the processed image data back to the terminal device, which then displays the processed image data. In this case, the main traffic characteristic of this service is the sudden increase in uplink traffic caused by user behavior.

[0197] 4. Multi-level QoS mechanism

[0198] The 3GPP protocol defines a multi-level QoS mechanism, which can support V2X communications.

[0199] As shown in Figure 3, the multi-level QoS mechanism includes the following operations:

[0200] Step 1: The AS sends QoS information to the PCF network element. Correspondingly, the PCF network element receives the QoS information from the AS.

[0201] The AS may be an application server for V2X communication, such as V2X AS.

[0202] The QoS information includes: QoS requirement information of N levels for the same QoS flow, where N is a positive integer greater than or equal to 2. The QoS requirement information includes, but is not limited to, packet delay budget (PDB) and packet error rate (PER).

[0203] Step 2: The PCF network element generates policy and charging control (PCC) rules based on the QoS information.

[0204] The PCC rule includes N QoS parameter sets, each of which is used to indicate a QoS configuration. The N QoS parameter sets are mapped from QoS information, such as N QoS parameter sets corresponding to N levels of QoS requirement information.

[0205] Exemplarily, the PCF network element identifies a preferred QoS parameter set among the N QoS parameter sets. The preferred QoS parameter set can be understood as a parameter set that is preferentially applied to the QoS flow among the N QoS parameter sets.

[0206] Step 3: The PCF network element sends the PCC rules to the SMF network element. Correspondingly, the SMF network element receives the PCC rules from the PCF network element.

[0207] The PCC rules in step 3 are the same as those in step 2 and are not described in detail herein.

[0208] Step 4: The SMF network element establishes N QoS files and the association relationship between the N QoS files and the above QoS flows according to the PCC rules, and identifies the preferred QoS file in the N QoS files.

[0209] The N QoS profiles correspond one-to-one to the N QoS parameter sets. The preferred QoS profile can be understood as a QoS profile that is preferentially applied to the above QoS flow among the N QoS profiles.

[0210] Step 5: The SMF network element sends N QoS files to the RAN device. Correspondingly, the RAN device receives the N QoS files from the SMF network element.

[0211] The RAN device may include a next generation radio access network (NG-RAN) device, such as NG-RAN device.

[0212] The N QoS files in step 5 are the same as the N QoS files in step 4 and are not described in detail.

[0213] For the RAN device, after receiving N QoS profiles, if it detects that the QoS configuration of the above QoS flow cannot meet the preferred QoS profile, the RAN device determines the above N QoS profiles based on the association relationship between the above QoS flow and the N QoS profiles. For the above N QoS profiles, the RAN device determines a QoS profile supported by itself from other QoS profiles except the preferred QoS profile. In addition, the RAN device performs step 6:

[0214] Step 6: The RAN device notifies the PCF network element through the QoS notification control process.

[0215] Exemplarily, during the QoS notification control process, the RAN device sends a notification message to the PCF network element. In response, the PCF network element receives the notification message from the RAN device. The notification message indicates that the QoS configuration of the QoS flow cannot meet the preferred QoS profile. Optionally, the notification message also indicates the QoS profile currently supported by the RAN device.

[0216] It should be understood that the QoS file indicated by the notification message is a QoS file other than the preferred QoS file among the above-mentioned N QoS files.

[0217] Step 7: The PCF network element initiates a PDU session modification process and adjusts the QoS configuration through the PDU session modification process.

[0218] In other words, QoS configuration adjustments are triggered by the QoS notification control process and implemented through the PDU session modification process. In a multi-level QoS mechanism, RAN devices can trigger QoS configuration adjustments through the QoS notification control process and can also provide the PCF network element with feedback on supported QoS profiles, but they cannot adjust the QoS configuration. RAN devices must notify core network devices before triggering the PDU session modification process to implement QoS configuration adjustments. This results in high signaling overhead and cannot meet dynamically changing QoS requirements.

[0219] In addition, the above multi-level QoS mechanism is applicable to GBR QoS flows and has a limited scope of application.

[0220] 5. Reflective QoS mechanism

[0221] To reduce the signaling overhead of issuing QoS rules on the network side, the Reflective QoS mechanism was introduced. The Reflective QoS mechanism means that the QoS configuration used for uplink data is the same as that used for downlink data.

[0222] Specifically, the UPF network element sends a downlink data packet to the RAN device. Accordingly, the RAN device receives the downlink data packet from the UPF network element. The GTP-U extension header of the downlink data packet includes a reflective QoS indication (RQI). The RQI is used to indicate the reflective quality of service mechanism that activates the QoS flow granularity. The RAN device sends a downlink data packet to the terminal device. Accordingly, the terminal device receives a downlink data packet from the RAN device. The downlink data packet includes an RQI and a QFI. The QFI is used to identify the QoS flow. The terminal device updates the QoS Rule based on the RQI and QFI, and then generates a derived or derived QoS rule (derived QoS rule). The derived QoS rule includes an uplink packet filter (UL packet filter), a QFI, and a precedence value, etc.

[0223] Taking FIG4 as an example, the QoS flows between the terminal device and the user plane network element include: default QoS flow 1 (Default QoS Flow1) and QoS flow 2 (QoS Flow2).

[0224] As shown in FIG4 , at time T1, the terminal device initiates a service but does not match the UL packet filter, and sends an uplink packet (UL packet) to the user plane network element through Default QoS Flow1, as shown by the dotted curve marked with UL at time T1.

[0225] As shown in Figure 4, at time T2, the user plane network element initiates the QoS Flow signaling plane establishment process to implement downlink flow mapping. The QoS Flow signaling plane establishment process is executed through QoS Flow2, as shown by the dotted curve marked with DL at time T2.

[0226] As shown in Figure 4, at time T3, the terminal device establishes a process based on the QoS Flow signaling plane and maps the uplink flow to QoS Flow2, that is, sends the UL packet to the user plane network element through QoS Flow2, as shown by the dotted curve marked with UL at time T3.

[0227] Optionally, a feedback QoS timer (Reflective QoS timer) is also configured in the Reflective QoS mechanism. After the Reflective QoS timer times out, the terminal device deletes the derived QoS rule. The Reflective QoS timer can be pre-configured for the terminal device by the communication system. Alternatively, the Reflective QoS timer can be configured for the terminal device by the SMF network element. Alternatively, the Reflective QoS timer can be configured for the terminal device by the PCF network element.

[0228] That is, in the Reflective QoS mechanism, the terminal device can only modify the UL packet filter on the terminal device side and cannot adjust the QoS configuration.

[0229] It should be noted that in the embodiments of the present application, the following descriptions have the same meaning and can be used interchangeably: updating the QoS configuration, adjusting the QoS configuration, updating the QoS configuration, and adjusting the QoS configuration. These descriptions are unified here and will not be repeated in the following text.

[0230] As can be seen from the preceding description, QoS configurations must be continuously adjusted to meet dynamically changing service demands. While multi-level QoS mechanisms allow for QoS configuration adjustments through the QoS notification control process and the PDU session modification process, the high signaling overhead makes it difficult to meet dynamically changing service demands. In the reflective QoS mechanism, although terminal devices can update the UL packet filter, they still cannot adjust the QoS configuration.

[0231] In summary, how to simplify the QoS configuration update process to meet dynamically changing business needs is a technical problem that needs to be solved urgently.

[0232] In view of this, an embodiment of the present application provides a first communication method, which can be applied to the communication system shown in Figure 1 or Figure 2a. In the communication method provided in the embodiment of the present application, an access network device determines a service feature update of a service during service transmission, or the access network device receives first information from a terminal device or a first core network device during service transmission. The service transmission process is performed via a QoS flow, and the first information is used to determine a target QoS configuration of the QoS flow. The access network device updates the QoS configuration of the QoS flow.

[0233] That is, during service transmission, when the access network device determines that the service characteristics of the service have been updated or receives first information, the access network device updates the QoS configuration of the QoS flow, thereby achieving dynamic adjustment of the QoS configuration. Compared to the multi-level QoS mechanism, in which the access network device is used to trigger QoS configuration updates and the QoS configuration can only be adjusted through the QoS notification control process and the PDU session modification process, the access network device in this application can autonomously update the QoS configuration, simplifying the QoS configuration update process.

[0234] It should be understood that the names of messages between devices or the names of parameters in messages in the following embodiments of the present application are only examples, and other names may be used in specific implementations. The embodiments of the present application do not specifically limit this. A unified explanation is given here and no further details are given below.

[0235] The communication method proposed in the embodiment of the present application is described in detail below with reference to Figures 5 to 13. The communication method in the embodiment of the present application includes two phases, namely phase one and phase two.

[0236] Phase 1 can be understood as a QoS parameter set configuration process. For example, the QoS parameter set in phase 1 is used to indicate at least one QoS configuration for a QoS flow.

[0237] As shown in Figure 5, in phase 1, the AF network element provides QoS information, such as the QoS requirements of the service, to the PCF network element. The PCF network element generates PCC rules based on the QoS requirements of the service and sends the PCC rules to the SMF network element. The PCC rules are used to indicate at least one QoS configuration. The SMF network element performs at least one of the following based on the PCC rules: sending the QoS rules to the terminal device, or sending the QoS description to the RAN device, or sending the N4 rule to the UPF network element. The PCC rules, QoS rules, QoS description, and N4 rules may include a QoS parameter set, which indicates at least one QoS configuration for the QoS flow.

[0238] Phase 2 can be understood as the QoS configuration update process of the QoS flow. For example, in phase 2, the updated QoS configuration is included in the at least one QoS configuration.

[0239] As shown in Figure 5, in phase 2, taking the terminal device updating the QoS configuration as an example, the terminal device selects a QoS configuration based on the N4 rule obtained in phase 1 (e.g., selecting a QoS configuration from at least one QoS configuration indicated by the N4 rule as the QoS configuration selected by the terminal device), updates the configuration of the QoS flow to the selected QoS configuration, and sends information 1 to the RAN device. Accordingly, the RAN device receives information 1 from the terminal device. Information 1 is used to indicate the selected QoS configuration. The RAN device updates the configuration of the QoS flow based on information 1. Furthermore, the RAN device sends information 2 to the UPF network element. Accordingly, the UPF network element receives information 2 from the RAN device. Information 2 indicates the selected QoS configuration. The UPF network element updates the configuration of the QoS flow based on information 2.

[0240] Next, the communication method of the embodiment of the present application is described in detail:

[0241] As shown in FIG6 , the communication method proposed in the embodiment of the present application includes the following operations:

[0242] S601. The third core network device obtains QoS information.

[0243] Exemplarily, the third core network device is introduced as follows:

[0244] In the embodiment of the present application, the third core network device is used to provide policy rule information, etc. For example, the third core network device is a policy control network element. Taking the 5G communication system as an example, the third core network device is a PCF network element.

[0245] For example, the QoS information is introduced as follows:

[0246] In the embodiment of the present application, the QoS information (or indication) includes a first QoS requirement and a second QoS requirement of the service, thereby representing at least two QoS requirements of the above service during operation. Each QoS requirement includes, but is not limited to, at least one of the following: latency requirement, reliability requirement, bandwidth requirement, etc.

[0247] For example, in the first QoS requirement, the delay requirement is 5 ms, the PER is 99.99%, and the bandwidth requirement is 10 MHz. In the second QoS requirement, the delay requirement is 10 ms, the PER is 99.99%, and the bandwidth requirement is 5 MHz.

[0248] Optionally, the QoS information (or indication) may also include a QoS requirement range, thereby characterizing the dynamic range of QoS requirements that may change during the operation of the service. For example, each QoS requirement includes, but is not limited to, at least one of the following: a latency requirement range, a reliability requirement range, a bandwidth requirement range, etc.

[0249] Optionally, the QoS information further (or indicates) includes a currently used (or effective) QoS requirement. For example, the QoS information indicates that the currently used (or effective) QoS requirement is the first QoS requirement described above. The currently used (or effective) QoS requirement can be understood as the QoS requirement of the service during current operation.

[0250] Optionally, the QoS information further includes QoS validation conditions. The QoS validation conditions are used to indicate the conditions under which the QoS requirements take effect (such as the time, location, event, etc.).

[0251] For example, the QoS validation condition is used to indicate the time when the QoS requirement takes effect. The time indicated by the QoS validation condition can be an absolute time, such as 09:00-19:00, or a relative time, such as the first to third time slots of each frame, or a continuous validity period, such as 10 seconds after the QoS configuration is updated. This embodiment of the present application does not limit this.

[0252] For example, the QoS validation condition is used to indicate the location where the QoS requirement takes effect. The location indicated by the QoS validation condition can be the location of the terminal device, such as the cell or tracking area (TA) where the terminal device is located, etc., which is not limited in this embodiment of the application.

[0253] For example, the QoS validation condition is used to indicate the event when the QoS requirement takes effect. The event indicated by the QoS validation condition may include network congestion-free, such as the channel busy ratio (CBR), channel occupancy ratio (CR), or channel interference strength (such as received signal strength indicator (RSSI) or reference signal received power (RSRP)), or the network congestion level is lower than a preset value.

[0254] Optionally, the QoS information further indicates the duration of the QoS requirement. For example, the QoS information indicates that the duration of the first QoS requirement is 3 time slots (or radio frames) or 3 seconds, and the duration of the second QoS requirement is 4 time slots (or radio frames) or 4 seconds.

[0255] Optionally, the QoS information also includes trigger conditions. The trigger conditions are used to assist the communication device side (e.g., terminal device, access network device, first core network device, etc.) in monitoring and triggering QoS configuration updates. In other words, if the communication device side (e.g., terminal device, RAN device, UPF network element, etc.) detects that the trigger conditions are met, a QoS configuration update is triggered.

[0256] Exemplarily, the triggering conditions include an IP quintuple, Internet Protocol version 6 (IPv6) header extension information, and changes in traffic characteristics. The IP quintuple and IPv6 header extension information are related to a QoS flow. When the triggering conditions are met, the QoS configuration of the QoS flow is updated.

[0257] Optionally, the QoS information is further used to indicate an execution subject, wherein the execution subject indicated by the QoS information is used to determine whether to update the QoS configuration, such as the execution subject determining whether to update the QoS configuration and determining the target QoS configuration according to a trigger condition.

[0258] For example, if the execution subject indicated by the QoS information is a terminal device, it means that the terminal device determines (according to the triggering condition) whether to update the QoS configuration.

[0259] For another example, if the execution subject indicated by the QoS information is the access network device, it means that the access network device determines (according to the triggering condition) whether to update the QoS configuration.

[0260] For another example, if the execution subject indicated by the QoS information is the first core network device, it means that the first core network device determines (based on the triggering conditions) whether to update the QoS configuration.

[0261] In addition, QoS information may also have other names, such as dynamic QoS information, QoS request, dynamic QoS request (dynamic QoS reqts), etc., which is not limited in the embodiments of the present application.

[0262] Exemplarily, the implementation process of S601 includes:

[0263] As a possible implementation, the application server sends QoS information to the third core network device. Correspondingly, the third core network device receives the QoS information from the application server.

[0264] Exemplarily, the QoS information is included in an AF request.

[0265] As another possible implementation method, the third core network device pre-configures QoS information, or the communication system pre-defines QoS information, which is not limited in the embodiments of the present application.

[0266] For the third core network device, after obtaining the QoS information, the third core network device executes S602:

[0267] S602: The third core network device determines a PCC rule according to the QoS information.

[0268] Exemplarily, the third core network device determines the PCC rule according to QoS information, user subscription information and / or local policy.

[0269] The PCC rule indicates the QoS configuration.

[0270] The following describes the QoS configuration indicated by the PCC rule through two examples (Example 1 and Example 2).

[0271] Example 1: In the QoS configuration indicated by the PCC rule, if the first QoS parameter of the QoS configuration is a first value, the QoS configuration meets the first QoS requirement. If the first QoS parameter of the QoS configuration is a second value, the QoS configuration meets the second QoS requirement.

[0272] In Example 1, the PCC rule includes a QoS parameter set (QoS Parameter Set). This QoS parameter set can be described as a basic QoS parameter set (QoS Parameter Set). This QoS parameter set includes a first QoS parameter (QoS param) and a step size (step). Alternatively, this QoS parameter set includes the first QoS parameter and an adjustable range for the first QoS parameter.

[0273] In the basic QoS parameter set, the first QoS parameter is an adjustable QoS parameter. For example, a terminal device, access network device, or first core network device can adjust the first QoS parameter to update the QoS configuration and meet dynamically changing QoS requirements. For example, when the first QoS parameter is a first value, the QoS configuration indicated by the basic QoS parameter set meets the first QoS requirement. When the first QoS parameter is a second value, the QoS configuration indicated by the basic QoS parameter set meets the second QoS requirement. Optionally, the step size can be understood as the minimum granularity for adjusting the first QoS parameter.

[0274] Exemplarily, the basic QoS parameter set includes QoS parameters such as PDB, PER, and bandwidth. For example, if the basic QoS parameter set includes a step size, the first QoS parameter may be a bandwidth parameter, and the step size may be 1 megabit. For another example, if the basic QoS parameter set includes an adjustable range corresponding to the first QoS parameter, the first QoS parameter may be PDB, and its adjustable range may be 5 ms to 20 ms.

[0275] In the case of Example 1, a change in the value of the first QoS parameter means that a QoS configuration update needs to be triggered.

[0276] Example 2: The PCC rule indicates multiple QoS configurations, a first QoS configuration among the multiple QoS configurations meets a first QoS requirement, and a second QoS configuration among the multiple QoS configurations meets a second QoS requirement.

[0277] In Example 2, the PCC rule includes at least two QoS parameter sets. Each QoS parameter set indicates a QoS configuration, and the QoS configurations indicated by different QoS parameter sets meet different QoS requirements. For example, the PCC rule includes a first QoS parameter set and a second QoS parameter set. The first QoS parameter set indicates a first QoS configuration, which meets the first QoS requirement. The second QoS parameter set indicates a second QoS configuration, which meets the second QoS requirement.

[0278] In the case of Example 2, the configuration of the QoS flow is updated from one QoS configuration among the above-mentioned multiple QoS configurations to another QoS configuration, which means that a QoS configuration update needs to be triggered.

[0279] Optionally, in at least one set of QoS parameter sets in the PCC rule, each set of QoS parameter sets is identified by an index. The index used to identify the QoS parameter set may be pre-configured or configured by a third core network device, and this embodiment of the present application does not limit this.

[0280] Optionally, the PCC rule indicates one or more of the following: the currently used (or effective) QoS requirement, or the QoS effectiveness condition, or the duration of the QoS requirement, or the triggering condition, or the execution subject. For details, see the introduction of S601 and will not be repeated here.

[0281] For the third core network device, after determining the PCC rule, the third core network device executes S603:

[0282] S603: The third core network device sends the PCC rules to the second core network device. Correspondingly, the second core network device receives the PCC rules from the third core network device.

[0283] Exemplarily, the second core network device is introduced as follows:

[0284] In the embodiment of the present application, the second core network device is a session management network element. Taking the 5G communication system as an example, the second core network device is an SMF network element.

[0285] The PCC rules can be found in the introduction of S602 and will not be described in detail here.

[0286] Exemplarily, the implementation process of S603 includes:

[0287] The third core network device sends the PCC rule to the second core network device through the first process. Correspondingly, the second core network device receives the PCC rule from the third core network device through the first process.

[0288] The first process includes a PDU session establishment process or a PDU session modification process.

[0289] For example, the PDU session establishment process can be recorded as a session management policy association establishment process (SM Policy Association procedure). The second core network device (such as the SMF network element) initiates the SM Policy Association procedure and obtains the PCC rules from the third core network device (such as the PCF network element) through the SM Policy Association procedure.

[0290] For another example, the PDU session establishment process can be recorded as a session management policy association modification process. The second core network device (such as the SMF network element) initiates the session management policy association modification process and obtains the PCC rules from the third core network device (such as the PCF network element) through the session management policy association modification process.

[0291] For another example, the PDU session establishment process can be recorded as a session management policy association modification process. The third core network device (such as a PCF network element) initiates the session management policy association modification process and sends the PCC rules to the second core network device (such as an SMF network element) through the session management policy association modification process.

[0292] For the second core network device, after obtaining the PCC rule, the second core network device executes S604a, S604b, or S604c:

[0293] S604a: The second core network device determines the N4 rule based on the PCC rule. The second core network device sends the N4 rule to the first core network device. Correspondingly, the first core network device receives the N4 rule from the second core network device.

[0294] Exemplarily, the first core network device is introduced as follows:

[0295] In the embodiment of the present application, the first core network device is a user plane network element. Taking a 5G communication system as an example, the first core network device can be a UPF network element.

[0296] Optionally, the N4 rule indicates at least one QoS configuration, see the introduction of S603 and will not be repeated here.

[0297] For example, when the N4 rule includes a basic QoS parameter set, it can be understood that the N4 rule indicates a QoS configuration. The QoS configuration indicated by the N4 rule can be dynamically updated. For example, in the QoS configuration indicated by the N4 rule, the first QoS parameter can be dynamically adjusted. Adjustment of the first QoS parameter means that the QoS configuration is updated. Alternatively, the basic QoS parameter set includes a dynamic adjustment range for the first QoS parameter, meaning that the first QoS parameter can be dynamically adjusted within the range.

[0298] For another example, when the N4 rule includes at least two QoS parameter sets, it can be understood that the N4 rule indicates at least two QoS configurations, for example, the N4 rule indicates a first QoS configuration and a second QoS configuration.

[0299] Optionally, the N4 rule indicates the currently used (or effective) QoS requirement, the QoS effectiveness condition or the duration of the QoS requirement. Please refer to the introduction of S601 and will not be repeated here.

[0300] Optionally, rule N4 includes indication information a1, indicating that the QoS configuration is updateable. The QoS configuration indicated by indication information a1 is the configuration of the QoS flow for service transmission between the terminal device and the first core network device (such as a UPF network element). It can be understood that after the first core network device receives indication information a1, the first core network device can dynamically update the QoS configuration of the QoS flow based on indication information a1.

[0301] Optionally, rule N4 includes indication information a2, which indicates that the execution entity is the first core network device. See the introduction to S603 and will not be repeated here. It can be understood that indication information a2 indicates that the update of the QoS configuration is triggered by the first core network device. In other words, indication information a2 instructs the first core network device to monitor business needs and trigger the QoS configuration update.

[0302] It should be understood that the indication information a2 indicates that the QoS configuration is updateable. In other words, when the N4 rule includes the indication information a2, the N4 rule may not include the indication information a1.

[0303] Optionally, the N4 rule indicates a trigger condition, i.e., the trigger condition is used by the user plane network element to determine whether to trigger a QoS configuration update. The trigger condition is used to determine whether the service characteristics of the service have been updated. For example, if the service traffic characteristics have changed, or if the service protocol layer explicitly notifies the service requirements of the service through a notification message, then the service characteristics of the service have been updated.

[0304] S604b: The second core network device determines a QoS description according to the PCC rule. The second core network device sends the QoS description to the access network device. Correspondingly, the access network device receives the QoS description from the second core network device.

[0305] Exemplarily, the access network device may be a RAN device.

[0306] Optionally, the QoS description indicates at least one QoS configuration, see the introduction of S603 and will not be repeated here.

[0307] For example, when the QoS description includes a basic QoS parameter set, the basic QoS parameter set indicates a QoS configuration. The QoS configuration indicated by the basic QoS parameter set can be dynamically updated. For example, in the basic QoS parameter set, a first QoS parameter can be dynamically adjusted. Adjustment of the first QoS parameter means that the QoS configuration is updated. Alternatively, the basic QoS parameter set includes a dynamic adjustment range for the first QoS parameter, meaning that the first QoS parameter can be dynamically adjusted within the range.

[0308] For another example, when the QoS description includes at least two QoS parameter sets, the QoS description can also be replaced with multiple QoS descriptions (multiple QoS profiles). The at least two QoS parameter sets include a first QoS parameter set and a second QoS parameter set, the first QoS parameter set indicating a first QoS configuration, and the second QoS parameter set indicating a second QoS configuration. It can be understood that the QoS description indicates the first QoS configuration and the second QoS configuration.

[0309] Optionally, the QoS description indicates the currently used (or effective) QoS configuration, QoS effectiveness conditions or duration of the QoS requirement. Please refer to the introduction of S601 and will not be repeated here.

[0310] Optionally, the QoS description includes indication information b1, which indicates that the QoS configuration is updateable. The QoS configuration indicated by the indication information b1 is the configuration of the QoS flow for service transmission between the terminal device and the first core network device (such as the UPF network element). It can be understood that after the access network device receives the indication information b1, the access network device can dynamically update the QoS configuration of the QoS flow based on the indication information b1.

[0311] Among them, the access network device updates the QoS configuration of the QoS flow, which can also be understood as the access network device dynamically adjusting resources based on information from the terminal device and / or the first core network device (such as information X1 or information Y1 described below), such as efficiently scheduling resources based on information provided by the terminal device and / or the first core network device (such as information X1 or information Y1 described below). For example, if the access network device learns that the traffic characteristics of the service have changed (such as the data volume, duration, expected arrival time, burst traffic cycle, start or end of burst data volume, etc. of the burst traffic), the access network device can flexibly schedule network resources to ensure the transmission of the service. At the same time, it can also allocate resources to other services or other users, thereby further improving resource utilization. For another example, if the access network device determines that no data will arrive in the future based on the changes in service traffic characteristics, it will allocate resources to other services or other users to improve resource utilization.

[0312] It should be noted that, in this application, a burst data volume may include at least one data packet. For example, if arranged in the order of transmission (or reception), the first data packet in the at least one data packet may be understood as the first data packet transmitted (or received). The last data packet in the at least one data packet may be understood as the last data packet transmitted (or received).

[0313] The start of a burst of data can be understood as the first data packet in at least one data packet corresponding to the burst of data. In addition, the start of a burst of data can also be described as the start of a burst of data or the start of a burst of traffic.

[0314] The starting information of the burst data volume can be understood as information indicating the first data packet (ie, the first data packet in the at least one data packet corresponding to the burst data volume).

[0315] The end of a burst of data can be understood as the last data packet in at least one data packet corresponding to the burst of data. In addition, the end of a burst of data can also be described as the end of a burst of data or the end of a burst of traffic.

[0316] The end information of the burst data volume can be understood as information indicating the last data packet (ie, the last data packet in the at least one data packet corresponding to the burst data volume).

[0317] Optionally, the QoS description includes indication information b2, which indicates that the execution entity is the access network device. (See the description of S603 and will not be repeated here.) It can be understood that indication information b2 indicates that the access network device triggers the QoS configuration update. In other words, indication information b2 instructs the access network device to monitor service requirements and trigger the QoS configuration update.

[0318] It should be understood that the indication information b2 indicates that the QoS configuration is updateable. In other words, when the QoS description includes the indication information b2, the QoS description may not include the indication information b1.

[0319] Optionally, the QoS configuration indicates a trigger condition, which is used by the access network device to determine whether to trigger a QoS update. The trigger condition is used to determine whether the service characteristics of the service have been updated. For example, a change in service traffic characteristics or a change in service requirements explicitly notified by the service protocol layer via a notification message indicates that the service characteristics of the service have been updated.

[0320] S604c: The second core network device determines a QoS rule based on the PCC rule. The second core network device sends the QoS rule to the terminal device. Correspondingly, the terminal device receives the QoS rule from the second core network device.

[0321] The QoS rule indicates at least one QoS configuration, for which please refer to the introduction of S603 and will not be described in detail.

[0322] For example, when a QoS rule includes a basic QoS parameter set, the basic QoS parameter set indicates a QoS configuration. The QoS configuration indicated by the basic QoS parameter set can be dynamically updated. For example, in the basic QoS parameter set, a first QoS parameter can be dynamically adjusted. Adjustment of the first QoS parameter means that the QoS configuration is updated. Alternatively, the basic QoS parameter set includes a dynamic adjustment range for the first QoS parameter, meaning that the first QoS parameter can be dynamically adjusted within the range.

[0323] For another example, when the QoS rule includes at least two QoS parameter sets, it can be understood that the QoS rule indicates at least two QoS configurations, for example, the QoS rule indicates a first QoS configuration and a second QoS configuration.

[0324] Optionally, the QoS rule indicates the currently used (or effective) QoS configuration, QoS effectiveness condition or duration of the QoS requirement. Please refer to the introduction of S601 and will not be repeated here.

[0325] Optionally, the QoS rule includes indication information c1, where the indication information c1 indicates that the QoS configuration is updateable. The QoS configuration indicated by the indication information c1 is the configuration of the QoS flow for service transmission between the terminal device and the first core network device (such as a UPF network element). It can be understood that after the terminal device receives the indication information c1, the terminal device can dynamically update the QoS configuration of the QoS flow based on the indication information c1.

[0326] Optionally, the QoS rule includes indication information c2, which indicates that the execution subject is the terminal device. (See the introduction to S603 and will not be repeated here.) It can be understood that indication information c2 indicates that the terminal device triggers the update of the QoS configuration. In other words, indication information c2 instructs the terminal device to monitor service needs and trigger the QoS configuration update.

[0327] It should be understood that, from the indication information c2, it can be known that the QoS configuration is updateable. In other words, when the QoS rule includes the indication information c2, the QoS rule may not include the indication information c1.

[0328] Optionally, the QoS rule indicates a trigger condition, which is used by the terminal device to determine whether to trigger a QoS update. The trigger condition is used to determine whether the service characteristics of the service have been updated. For example, if the service traffic characteristics have changed, or if the service protocol layer explicitly notifies the service requirements of the service through a notification message, then the service characteristics of the service have been updated.

[0329] In this way, the second core network device implements the parameter delivery process of the QoS configuration by executing S604a, S604b and S604c.

[0330] The specific implementation of the communication method shown in FIG. 6 will be described in detail below with reference to the example shown in FIG. 7 .

[0331] FIG7 is a flow chart of a communication method provided in an embodiment of the present application. The first core network device in FIG6 may be the UPF network element shown in FIG7 , the second core network device in FIG6 may be the SMF network element shown in FIG7 , the third core network device in FIG6 may be the PCF network element shown in FIG7 , the access network device in FIG6 may be the RAN device shown in FIG7 , and the application server in FIG6 may be the AF network element shown in FIG7 .

[0332] Specifically, in FIG7 , the communication method according to an embodiment of the present application includes the following steps:

[0333] S701: Optionally, the AF network element sends a QoS request to the PCF network element. Correspondingly, the PCF network element receives the QoS request from the AF network element.

[0334] The QoS request includes QoS information, which can be found in the introduction of S701 and will not be described in detail here.

[0335] In addition, the QoS request may also have other names, such as dynamic QoS request information, dynamic QoS request (dynamic QoS reqts), etc., which is not limited in the embodiment of the present application.

[0336] Exemplarily, the implementation process of S701 includes:

[0337] For example, the AF network element sends an AF request to the PCF network element. Correspondingly, the PCF network element receives the AF request from the AF network element.

[0338] The AF request includes QoS information.

[0339] For another example, the AF network element sends a QoS request to the PCF network element through the capability exposure interface. Correspondingly, the PCF network element receives the QoS request from the AF network element through the capability exposure interface.

[0340] For another example, the AF network element is in the trusted domain and sends a QoS request to the PCF network element. That is, the AF network element sends the QoS request to the PCF network element by calling the service interface of the PCF network element, such as the Npcf_PolicyAuthorization service interface.

[0341] On the contrary, the AF network element is in the non-trusted domain, and the AF network element sends a QoS request to the PCF network element through the NEF network element. That is, the AF network element sends a QoS request to the NEF network element by calling the service interface of the NEF network element, such as the Nnef_AFSessionWithQoS service interface, and the NEF network element sends a QoS request to the PCF network element by calling the service interface of the PCF, such as the Npcf_PolicyAuthorization service interface.

[0342] S702a. Optionally, when the terminal device initiates the PDU session establishment process, the terminal device sends a PDU session establishment request to the AMF network element. Accordingly, the AMF network element receives the PDU session establishment request from the terminal device. The AMF network element sends the PDU session establishment request to the SMF network element. Accordingly, the SMF network element receives the PDU session establishment request from the AMF network element.

[0343] The PDU session establishment request is used to request the establishment of a PDU session.

[0344] For example, the implementation process of S702a can be referred to in related technologies and will not be described in detail.

[0345] S702b. Optionally, when the terminal device initiates the PDU session modification process, the terminal device sends a PDU session modification request to the AMF network element. Accordingly, the AMF network element receives the PDU session modification request (PDU Session Modification Request) from the terminal device. The AMF network element sends the PDU session modification request to the SMF network element. Accordingly, the SMF network element receives the PDU session modification request from the AMF network element.

[0346] The PDU session modification request is used to request modification of a PDU session.

[0347] For example, the implementation process of S702b can be referred to in related technologies and will not be described in detail.

[0348] S703: The PCF network element generates a PCC rule according to the QoS request.

[0349] Specifically, the PCF network element generates PCC rules according to the QoS request, the user's subscription information and the local policy.

[0350] The PCC rules can be found in the introduction of S602 and will not be described in detail here.

[0351] S704: The PCF network element sends the PCC rules to the SMF network element. Correspondingly, the SMF network element receives the PCC rules from the PCF network element.

[0352] For example, when the terminal device executes S702a, the SMF network element initiates a session management policy association establishment process (SM Policy Association procedure) and obtains PCC rules from the PCF network element through the SM Policy Association procedure.

[0353] For another example, when the terminal device executes S702b, the SMF network element initiates a session management policy association modification process, and obtains PCC rules from the PCF network element through the session management policy association modification process.

[0354] For another example, when the terminal device does not execute S702a and S702b, the PCF network element initiates a session management policy association modification process and sends the PCC rules to the SMF network element through the session management policy association modification process.

[0355] For the SMF network element, after obtaining the PCC rule, the SMF network element executes S705a, S705b or S705c:

[0356] S705a: The SMF network element determines the N4 rule based on the PCC rule. The SMF network element sends the N4 rule to the UPF network element. Correspondingly, the UPF network element receives the N4 rule from the SMF network element.

[0357] The implementation process of S705a can refer to the introduction of S604a and will not be repeated here.

[0358] Exemplarily, the implementation process of S705a includes:

[0359] For example, the SMF network element sends the N4 rules to the UPF network element through the N4 Session Establishment process. Correspondingly, the UPF network element receives the N4 rules from the SMF network element through the N4 Session Establishment process.

[0360] For another example, the SMF network element sends the N4 rules to the UPF network element through the N4 Session Modification process. Correspondingly, the UPF network element N4 Session Modification process receives the N4 rules from the SMF network element.

[0361] S705b: The SMF network element determines the QoS description based on the PCC rules and local policy. The SMF network element sends the QoS description to the RAN device. In response, the RAN device receives the QoS description from the SMF network element.

[0362] The implementation process of S705b can refer to the introduction of S604b and will not be repeated here.

[0363] S705c: The SMF network element determines QoS rules based on the PCC rules and / or local policies. The SMF network element sends the QoS rules to the terminal device. In response, the terminal device receives the QoS rules from the SMF network element.

[0364] The implementation process of S705c can refer to the introduction of S604c and will not be repeated here.

[0365] Exemplarily, the implementation process of S705c includes:

[0366] For example, the SMF network element sends QoS rules to the RAN device via the AMF network element. Accordingly, the RAN device receives the QoS rules from the SMF network element via the AMF network element. The RAN device sends QoS rules to the terminal device. Accordingly, the terminal device receives the QoS rules from the RAN device. In other words, the SMF network element sends QoS rules to the terminal device via the AMF network element and the RAN device, and accordingly, the terminal device receives the QoS rules from the SMF network element via the RAN device and the AMF network element. In the above process, the RAN device is used to forward the QoS rules, and the QoS rules are included in the PDU Session Establishment / Modification Receive message sent to the terminal device side.

[0367] For the SMF network element, the configuration of the QoS parameter set is achieved by executing S705a, S705b and S705c.

[0368] For terminal devices, AMF network elements, SMF network elements, and UPF network elements, S706a or S706b is also executed:

[0369] S706a. When executing the PDU session establishment process, the terminal device, AMF network element, SMF network element and UPF network element execute the remaining steps for PDU Session Establishment process.

[0370] Among them, the PDU Session Establishment process can be found in the relevant 3GPP technical specifications and will not be described in detail.

[0371] S706b. When executing the PDU session modification process, the terminal device, AMF network element, SMF network element and UPF network element execute the remaining steps for PDU Session Modification process.

[0372] Among them, the PDU Session Modification process can be found in the relevant 3GPP technical specifications and will not be described in detail.

[0373] In summary, the PCF network element generates at least one set of QoS parameter sets based on the QoS request and then provides this set of QoS parameter sets to the SMF network element. The SMF network element provides this set of QoS parameter sets to the UPF network element, RAN equipment, and terminal equipment, thereby implementing the configuration of the QoS parameter sets and laying the foundation for dynamic updates of QoS configuration.

[0374] The above describes the configuration process of the QoS parameter set.

[0375] The following describes the QoS configuration update process.

[0376] As shown in FIG8 , taking the terminal device triggering a QoS configuration update as an example, the communication method proposed in the embodiment of the present application includes the following operations:

[0377] S801. The terminal device determines that the service characteristics of the service are updated.

[0378] Exemplarily, when the trigger condition c1 is met, the terminal device determines that the service feature of the service is updated.

[0379] The trigger condition c1 includes at least one of the following:

[0380] Trigger condition c1-1: The difference between data volume x1 and data volume x2 is greater than threshold x. Data volume x1 is the data volume of the service transmitted within time unit x1, and data volume x2 is the data volume of the service transmitted within time unit x2. This means that the traffic characteristics of the service have changed, such as a downlink data burst. This means that the terminal device determines, based on the downlink data burst, that the traffic characteristics of the service (i.e., the service characteristics of the service) have changed, indicating that the network demand for the service has changed.

[0381] In the embodiment of the present application, the data volume x1 and the data volume x2 are the data volumes of the same service, and the service data of the service is transmitted through the same QoS flow.

[0382] In the embodiment of the present application, the time unit may be one or more symbols, one or more time slots, one or more subframes, one or more radio frames, etc. Symbols, time slots, subframes, and radio frames can be found in the relevant 3GPP technical specifications and will not be described in detail.

[0383] Trigger condition c1-2: Receive notification message x. Notification message x indicates the network requirements of the service. For example, notification message x indicates the size of a media frame, which includes the service data. Notification message x is a notification message sent by the application (app) layer of the terminal device. When an application needs to receive or send a large number of media frames, notification message x indicates the network requirements of the service, allowing the terminal device to be informed of the updated network requirements of the service.

[0384] Optionally, the notification information x includes changes in the network requirements or traffic characteristics of the service, such as a 20 MHz bandwidth requirement (or the size of burst traffic), the duration of the network requirement (or the duration of burst traffic), etc.

[0385] Among them, the notification message x can be a message sent by the application layer alone to the underlying communication module of the terminal device, or a message carried in the data packet when the application layer sends the data packet, such as carried in the protocol header or extended header of the TCP / UDP, RTP and other protocols of the data packet.

[0386] Trigger condition c1-3, the QoS configuration of the QoS flow expires. The QoS flow is used to transmit the above-mentioned services. The QoS configuration of the QoS flow has a valid time period. For example, the valid time period of QoS configuration 1 is recorded as time period 1, and the valid time period of QoS configuration 2 is recorded as time period 2. QoS configuration 1 can meet the requirements of service feature 1, and QoS configuration 2 can meet the requirements of service feature 2. When time period 1 expires, it means that the service features of the above-mentioned service are updated, that is, updated from service feature 1 to service feature 2. Or the corresponding QoS configuration's effectiveness conditions are no longer met. Accordingly, the terminal device needs to update the QoS configuration, such as updating from QoS configuration 1 to QoS configuration 2.

[0387] It should be understood that the trigger condition c1 may be configured by the second core network device, as described in the introduction to the QoS rule. Alternatively, the trigger condition c1 may be pre-configured, which is not limited in the present embodiment.

[0388] For the terminal device, when it is determined that the service feature of the service is updated, S802 and S803 are executed:

[0389] S802. Optionally, the terminal device determines a target QoS configuration for the QoS flow.

[0390] This step is optional, that is, after the terminal device determines that the service feature is updated, it does not execute S802 but executes S803.

[0391] Exemplarily, the target QoS configuration is a configuration indicated by a target QoS parameter set.

[0392] For example, if the QoS rule includes at least two QoS parameter sets, the terminal device selects one QoS parameter set from the at least two QoS parameter sets as the target QoS parameter set based on the updated service characteristics. Accordingly, the terminal device determines the target QoS configuration for the QoS flow based on the target QoS parameter set. As a possible alternative description, the QoS rule includes at least two QoS configurations. Based on the updated service characteristics, the terminal device determines the target QoS configuration from the at least two QoS configurations.

[0393] Optionally, when the QoS rule includes at least two QoS parameter sets, each QoS parameter set has an index. Accordingly, the terminal device can also determine the index of the target QoS parameter set, which is recorded as the target index. The target index is used to identify the target QoS parameter set, which can be understood as the target index being used to determine the target QoS configuration.

[0394] For another example, when the QoS rule includes a set of QoS parameter sets (such as the basic QoS parameter set mentioned above), the terminal device determines the first QoS parameter in the above QoS parameter set (for example, determines the size of the first QoS parameter) based on the updated service characteristics. Wherein, when the size of the first QoS parameter is determined, the QoS configuration indicated by the QoS parameter set is the target QoS configuration. As a possible alternative description, the terminal device determines the first QoS parameter in the QoS configuration of the above QoS flow based on the updated service characteristics, thereby determining the target QoS configuration.

[0395] Optionally, when the QoS rule includes a set of QoS parameter sets (such as the basic QoS parameter set described above), the terminal device determines the target parameter value based on the value of the first QoS parameter before adjustment, the value of the first QoS parameter after adjustment, and the step size. For example, if the first QoS parameter is bandwidth, the value of the first QoS parameter after adjustment is 10 MHz, the value of the first QoS parameter before adjustment is 0 MHz, and the step size is 1 MHz, then the value of the target parameter is 10.

[0396] In the embodiment of the present application, the target parameter is used to determine the target QoS configuration.

[0397] Optionally, if there are multiple first QoS parameters, that is, there are multiple adjustable QoS parameters, the above target parameters include the first QoS parameter and the number of adjustment steps, that is, the bandwidth and 10.

[0398] For another example, when the QoS rule includes a set of QoS parameter sets (such as the basic QoS parameter set mentioned above, which includes an adjustable range of the first QoS parameter), the terminal device determines the above-mentioned first QoS parameter within the adjustable range of the first QoS parameter (for example, determines the size of the first QoS parameter) based on the updated service characteristics. Wherein, when the size of the first QoS parameter is determined, the above-mentioned QoS configuration indicated based on the QoS parameter set is the target QoS configuration. As a possible alternative description, the terminal device determines the first QoS parameter in the QoS configuration of the above-mentioned QoS flow based on the updated service characteristics, thereby determining the target QoS configuration. For example, the first QoS parameter is bandwidth, and the adjustable range of the first QoS parameter is 10-50MHz. The value of the first QoS parameter after adjustment is 30MHz, and the size of the target parameter is 30.

[0399] Optionally, if there are multiple first QoS parameters, that is, multiple adjustable QoS parameters, there are also multiple adjustable ranges. For example, there are two first QoS parameters, denoted as QoS parameter 1 and QoS parameter 2. The adjustable range of QoS parameter 1 is denoted as adjustable range 1, and the adjustable range of QoS parameter 2 is denoted as adjustable range 2. The target parameters mentioned above then include the first QoS parameters and the adjusted target values, such as bandwidth and 30.

[0400] In the embodiment of the present application, the target parameter is used to determine the target QoS configuration.

[0401] For S802, it can also be replaced with the following description:

[0402] When the service characteristics of the service are updated, the terminal device determines the target QoS rule of the QoS flow according to the updated service characteristics, wherein the target QoS rule indicates the target QoS configuration.

[0403] Optionally, the terminal device updates the QoS configuration of the QoS flow according to the target QoS rule, such as updating the QoS configuration of the QoS flow to the target QoS configuration. For details, see the introduction after S812 and will not be repeated here.

[0404] S803: The terminal device sends information X1 to the access network device. Correspondingly, the access network device receives the information X1 from the terminal device.

[0405] The information X1 is used to indicate the target QoS configuration of the QoS flow.

[0406] For example, the information X1 may include the following information:

[0407] For example, the information X1 includes a target index, for which reference can be made to the introduction of S802 and will not be described in detail.

[0408] For another example, the information X1 includes target parameters, which can be found in the introduction of S802 and will not be described in detail.

[0409] For another example, the information X1 includes information of a target QoS configuration, such as the information X1 including one or more of the following: a PDB size, a PER size, a maximum data burst volume (MDBV) size, or a bandwidth size.

[0410] For example, if S802 is optional, information X1 includes the target network requirements of the service, such as the service characteristics after the service update (as described in S801), which can specifically be the end of the frame, the data volume of the burst data, the period of the burst data, the start or end of the burst data, the duration of the burst data and / or the arrival time of the burst data.

[0411] It should be noted that, in this application, a frame can correspond to at least one data packet. For example, if arranged in the order of transmission (or reception), the first data packet in the at least one data packet can be understood as the first data packet transmitted (or received). The last data packet in the at least one data packet can be understood as the last data packet transmitted (or received).

[0412] The end of a frame may be understood as the last data packet in at least one data packet corresponding to the frame.

[0413] The start and end of the burst data volume can be found in the introduction of S604b and will not be described in detail.

[0414] For example, the information X1 may be carried in the following information:

[0415] For example, information X1 is carried in the PDCP layer of the uplink data packet. That is, S803 can be alternatively described as: the terminal device sends a data packet to the access network device. Correspondingly, the access network device receives the data packet from the terminal device. The PDCP layer of the data packet includes information X1.

[0416] For another example, information X1 is carried in a media access control element (MAC CE). That is, S803 can be alternatively described as: the terminal device sends a MAC CE to the access network device. Accordingly, the access network device receives the MAC CE from the terminal device. The MAC CE includes information X1.

[0417] For another example, information X1 is carried in RRC signaling. That is, S803 can be replaced by the following description: the terminal device sends RRC signaling to the access network device. Correspondingly, the access network device receives the RRC signaling from the terminal device. The RRC signaling includes information X1.

[0418] It should be understood that information X1 can also be carried in other messages, and this embodiment of the present application does not limit this.

[0419] It is understandable that, when information X1 is carried in the PDCP layer of the uplink data packet, the terminal device can continue to send information X1 to the access network device until feedback information from the access network device is received. For details, see the introduction of S811 and S812, which will not be repeated here. In the embodiment of the present application, the terminal device continues to send information X1 to the access network device, which helps the access network device successfully receive information X1, thereby improving the reliability of information transmission.

[0420] Optionally, the terminal device sends information X2 to the access network device. Correspondingly, the access network device receives the information X2 from the terminal device.

[0421] The information X2 indicates the time period X, which is the time period during which the target QoS configuration takes effect. The target QoS configuration can be referred to the introduction of S802 and will not be described in detail here.

[0422] The manner in which the information X2 indicates the time period X may include the following:

[0423] For example, the information X2 indicates the start time and the end time of the time period X.

[0424] For another example, information X2 indicates the start time and duration of time period X.

[0425] For another example, information X2 indicates the end time of time period X.

[0426] For another example, information X2 indicates the duration of time period X.

[0427] For example, when information X2 indicates the end time or duration of time period X, the start time of time period X may be the time when the access network device receives information X2. Alternatively, the start time of time period X may be the time when the access network device updates the QoS configuration of the QoS flow to the target QoS configuration.

[0428] It should be understood that information X2 can be carried in an uplink data packet, MAC CE, or RRC signaling. An uplink data packet is a data packet sent by a terminal device to an access network device. In this embodiment of the present application, information X2 and information X1 can be carried in the same message transmission or in different message transmissions, which is not limited in this embodiment of the present application.

[0429] It should be understood that the time period X may be determined autonomously by the terminal device.

[0430] Alternatively, time period X may also be determined by the third core network device. For example, after the third core network device determines time period X, it indicates the start time or time period X of the service feature update to the second core network device through the PCC rule, and then indicates time period X to the terminal device through the second core network device.

[0431] Alternatively, the time period X may also be determined by the second core network device. For example, after the second core network device determines the time period X, it indicates the time period X to the terminal device.

[0432] In the embodiment of the present application, the manner in which the terminal device obtains the time period X is not limited.

[0433] For the access network device, when the access network device receives the information X1, the access network device executes S804:

[0434] S804: The access network device updates the QoS configuration of the QoS flow.

[0435] For the access network device, the information X1 is used to determine the QoS description corresponding to the target QoS configuration. The information X1 can be found in the introduction of S803 and will not be described in detail.

[0436] For example, upon receiving information X1, the access network device determines the target QoS configuration for the QoS flow based on information X1 and updates the QoS configuration of the QoS flow based on the target QoS configuration. For another example, upon receiving information X1, the access network device updates the QoS description of the QoS flow. The QoS description indicates the QoS configuration. When the access network device updates the QoS description of the QoS flow, it means that the access network device updates the QoS configuration of the QoS flow.

[0437] For another example, upon receiving information X1, the access network device determines a target QoS description for the QoS flow based on information X1, and updates the QoS configuration of the QoS flow based on the target QoS description. The target QoS description indicates the target QoS configuration. For example, if information X1 includes target network requirements for the service, such as updated service characteristics, specifically the end of a frame, the size of a burst data flow, the duration of the burst data flow, and / or the arrival time of the burst data flow, the access network device determines the maximum data burst volume (MDBV) based on at least one of the aforementioned burst service traffic characteristics.

[0438] For another example, when receiving information X1, the access network device updates the QoS description of the QoS flow. It can also be understood that the access network device dynamically adjusts resources or efficiently schedules resources based on the information X1 sent by the terminal device. For example, if the access network device learns that the traffic characteristics of the service have changed (such as the data volume, duration, expected arrival time, period, start or end of the burst data volume, etc.), the access network device can flexibly schedule network resources to ensure the transmission of the service. At the same time, it can also allocate network resources to other services or other users, thereby further improving resource utilization. For another example, based on the changes in service traffic characteristics, the access network device determines that no data will arrive in the future for a period of time, and thus allocates wireless resources to other services or other users, thereby improving resource utilization.

[0439] Optionally, the access network device determines whether RRC reconfiguration is required based on the target QoS configuration. If RRC reconfiguration is required, the access network device initiates an RRC reconfiguration process to the terminal device to update the QoS configuration of the QoS flow to the target QoS configuration, or to update the QoS configuration of the data radio bearer (DRB) to the target QoS configuration.

[0440] For the access network device, the QoS configuration update may succeed or fail. In the case of a failure in the QoS configuration update, the access network device may optionally execute S805-S806. In the case of a success in the QoS configuration update, the access network device may optionally execute S807, which is described in detail as follows:

[0441] S805: The access network device sends information X3 to the terminal device. Correspondingly, the terminal device receives information X3 from the access network device.

[0442] The information X3 is used to indicate that the access network device has failed to update the QoS configuration of the QoS flow. The access network device updates the QoS configuration of the QoS flow based on the information X1.

[0443] Exemplarily, when the current network resources do not meet the target QoS configuration (i.e., the target QoS configuration indicated by information X1), or when the target QoS configuration is not within the pre-authorized range of the core network (such as multiple QoS configurations or one or more QoS parameter adjustment ranges provided by the second core network device), the access network device fails to update the QoS configuration of the QoS flow. The current network resources refer to the air interface resources between the access network device and the terminal device.

[0444] Optionally, the access network device sends information X4 to the terminal device. Correspondingly, the terminal device receives information X4 from the access network device. The information X4 is used to indicate the QoS configuration supported by the access network device.

[0445] Exemplarily, the QoS configuration supported by the access network device is recorded as QoS configuration 1. QoS configuration 1 is the configuration indicated by QoS parameter set 1.

[0446] For example, if the QoS description includes at least two QoS parameter sets, the access network device selects a QoS parameter set supported by the device from the at least two QoS parameter sets based on information X1 as QoS parameter set 1. If the access network device cannot accept the target QoS configuration indicated by information X1, the access network device determines QoS parameter set 1 from the at least two QoS parameter sets. QoS parameter set 1 is the QoS parameter set supported by the current network resources and closest to the target QoS configuration indicated by information X1. Alternatively, QoS parameter set 1 is the highest QoS configuration supported by the current network resources.

[0447] Furthermore, when the QoS description includes at least two QoS parameter sets, each QoS parameter set has an index. Accordingly, the access network device can determine the index of QoS parameter set 1, which is recorded as index 1. Accordingly, information X4 includes index 1.

[0448] For another example, when the QoS description includes a set of QoS parameter sets (such as the basic QoS parameter set mentioned above), the access network device determines the first QoS parameter (for example, determines the size of the first QoS parameter) from the above QoS parameter set based on information X1. After the first QoS parameter is adjusted, the configuration indicated by the above QoS parameter set is closest to or equal to the target QoS configuration indicated by information X1. If the access network device cannot accept the first QoS parameter indicated by information X1, the access network device determines the first QoS parameter. The first QoS parameter determined by the access network device is the highest QoS parameter that the current network resources can support, and / or the first QoS parameter determined by the access network device is closest to the first QoS parameter indicated by information X1. In this way, when the access network device determines the first QoS parameter, it can also determine the target QoS configuration indicated by the basic QoS parameter set.

[0449] Furthermore, when the QoS description includes a set of QoS parameter sets (such as the basic QoS parameter set described above), the access network device determines target parameter 1 based on the value of the first QoS parameter before adjustment, the value of the first QoS parameter after adjustment, and the step size. Accordingly, information X4 includes target parameter 1. Target parameter 1 is used to represent the number of adjustment steps for the first QoS parameter. For details, see the introduction to S802 and are not further described.

[0450] Alternatively, if the QoS description includes a set of QoS parameter sets (such as the basic QoS parameter set described above, and the basic QoS parameter set includes an adjustable range for the first QoS parameter), the access network device determines target parameter 1 based on the adjustable range for the first QoS parameter and the current network resource situation. Accordingly, information X4 includes target parameter 1. Target parameter 1 is used to represent the magnitude of the first QoS parameter. For details, see the description of S802 and will not be repeated here.

[0451] Exemplarily, information X4 is carried in a downlink data packet. That is, the access network device sends a downlink data packet to the terminal device. Correspondingly, the terminal device receives the downlink data packet from the access network device. The PDCP layer of the downlink data packet includes information X4.

[0452] Exemplarily, information X4 is carried in RRC signaling. That is, the access network device sends RRC signaling to the terminal device. Correspondingly, the terminal device receives RRC signaling from the access network device. The RRC signaling includes information X4.

[0453] Exemplarily, information X4 is carried in a MAC CE. That is, the access network device sends a MAC CE to the terminal device. Correspondingly, the terminal device receives the MAC CE from the access network device. The MAC CE includes information X4.

[0454] It should be understood that information X4 can also be carried in other messages, and this embodiment of the present application does not limit this.

[0455] For the terminal device, when the terminal device receives information X3, it executes:

[0456] S806. The terminal device performs adaptive adjustment.

[0457] For example, on the terminal device side, the application layer is notified so that the application layer can make adjustments, such as adjusting the amount of data to be sent or the amount of data to be received, to match the network conditions.

[0458] Optionally, when the terminal device receives information X4, the terminal device updates the QoS configuration of the QoS flow based on information X4. For example, the terminal device updates the QoS configuration to the QoS configuration indicated by information X4, thereby updating the QoS configuration. Because the QoS configuration indicated by information X4 is closest to the target QoS configuration, the terminal device can also meet dynamically changing service needs as much as possible when updating the QoS configuration based on information X4.

[0459] If the RAN side successfully updates the QoS configuration of the QoS flow to the target QoS configuration indicated by information X1, the following steps are performed:

[0460] S807: Optionally, the access network device sends information X1 to the first core network device. Correspondingly, the first core network device receives the information X1 from the access network device.

[0461] Exemplarily, the first core network device is introduced as follows:

[0462] In the embodiment of the present application, the first core network device is a user plane network element. Taking a 5G communication system as an example, the first core network device can be a UPF network element.

[0463] The information X1 is used to indicate the target QoS configuration of the QoS flow.

[0464] Exemplarily, the information X1 includes information of a target index, a target parameter, or a target QoS configuration. For details, please refer to the introduction of S803 and will not be repeated here.

[0465] For example, the information X1 may be carried in the following information:

[0466] For example, information X1 is carried in the GTP-U layer of the uplink data packet. That is, S807 can be replaced by the following description: the access network device sends an uplink data packet to the first core network device. Accordingly, the first core network device receives the uplink data packet from the access network device. The GTP-U layer of the uplink data packet includes information X1.

[0467] It should be understood that information X1 can also be carried in other messages, and this embodiment of the present application does not limit this.

[0468] It is understandable that, when information X1 is carried in the GTP-U layer of the uplink data packet, the access network device can continue to send information X1 to the first core network device until feedback information from the first core network device is received. For details, see the introduction of S809 and S810, which will not be repeated here. In the embodiment of the present application, the access network device continues to send information X1 to the first core network device, which helps the first core network device successfully receive information X1, thereby improving the reliability of information transmission.

[0469] Optionally, the access network device determines whether to send information X1 to the first core network device based on the target QoS configuration.

[0470] For example, if the target QoS configuration only modifies the PDB, PER and other parameters corresponding to the QoS flow and has no effect on the QoS parameters on the first core network device side, the access network device does not need to send information X1 to the first core network device; if the target QoS configuration is activated and established based on information X1, the access network device needs to send information X1 to the first core network device to activate and establish the corresponding N4 rules.

[0471] Optionally, when the access network device receives information X2, the access network device sends information X2 to the first core network device. Accordingly, the first core network device receives information X2 from the access network device. Information X2 and information X1 may be carried in the same message or in different messages, as is not limited in this embodiment of the present application.

[0472] For the first core network device, when the first core network device receives the information X1, it executes S808:

[0473] S808. The first core network device updates the N4 rule of the QoS flow.

[0474] For the first core network device, the information X1 is used to determine the N4 rule corresponding to the target QoS configuration. The information X1 can be found in the introduction of S803 and will not be described in detail.

[0475] For example, upon receiving information X1, the first core network device determines the target QoS configuration of the QoS flow according to information X1, and updates the QoS configuration of the QoS flow according to the target QoS configuration, that is, updates the N4 rule corresponding to the QoS flow.

[0476] For another example, upon receiving information X1, the first core network device updates the N4 rule of the QoS flow. The N4 rule indicates the QoS configuration. The first core network device updates the N4 rule of the QoS flow, which means that the first core network device updates the QoS configuration of the QoS flow.

[0477] For another example, upon receiving information X1, the first core network device determines a target N4 rule for the QoS flow based on information X1, and updates the QoS configuration of the QoS flow based on the target N4 rule, wherein the target N4 rule indicates a target QoS configuration.

[0478] Optionally, for the first core network device, after the QoS configuration is updated, the first core network device performs the following operations:

[0479] S809: Optionally, the first core network device sends information X5 to the access network device. Correspondingly, the access network device receives the information X5 from the first core network device.

[0480] The information X5 is used to indicate that the first core network device has successfully updated the QoS configuration (or N4 rule) of the QoS flow. The first core network device updates the QoS configuration (or N4 rule) of the QoS flow based on the information X1.

[0481] For example, the information X5 includes the following information:

[0482] For example, information X5 includes a target index and an acknowledgment (ACK). The target index can be found in the introduction to S802 and will not be described in detail here. ACK is used to indicate that the QoS configuration corresponding to the target index has been successfully updated. The QoS configuration corresponding to the target index can be understood as the target QoS configuration determined by the first core network device based on the target index.

[0483] For another example, information X5 includes a target parameter and an ACK. The target parameter can be found in the description of S802 and will not be further described. The ACK is used to indicate that the QoS configuration corresponding to the target parameter has been successfully updated. The QoS configuration corresponding to the target parameter can be understood as the target QoS configuration determined by the first core network device based on the target parameter.

[0484] For the access network device, when the access network device receives the information X5, it executes S810 and / or S811:

[0485] S810. Optionally, the access network device stops sending information X1 to the first core network device, thereby saving communication resources.

[0486] S811. Optionally, the access network device sends information X6 to the terminal device. Correspondingly, the terminal device receives the information X6 from the access network device.

[0487] Information X6 indicates that the first core network device and / or access network device has successfully updated the QoS configuration of the QoS flow. The first core network device updates the QoS configuration of the QoS flow based on information X1, and the access network device updates the QoS configuration of the QoS flow based on information X1.

[0488] For example, the information X6 includes the following information:

[0489] For example, information X6 includes a target index and ACK, and you can refer to the introduction of information X5, which will not be repeated here.

[0490] For another example, information X6 includes target parameters and ACK, which can be found in the introduction of information X5 and will not be described in detail.

[0491] It is easy to understand that the following introduction about S811 is given:

[0492] Example 1: In this embodiment of the present application, if the QoS configuration on the access network device side is successfully updated and the QoS configuration on the first core network device side does not need to be updated, the access network device may execute S811 after executing S804. Information X6 is used to indicate that the access network device has successfully updated the QoS configuration for the QoS flow.

[0493] Example 2: In an embodiment of the present application, if the QoS configuration on the access network device side is successfully updated and the QoS configuration on the first core network device side is also successfully updated, the access network device may execute S811 after executing S809. Information X6 is used to indicate that the first core network device and the access network device have successfully updated the QoS configuration for the QoS flow.

[0494] Case 3: In the embodiment of the present application, S811 includes S811a. Optionally, S811 also includes S811b. Specifically:

[0495] If the QoS configuration on the access network device side is updated successfully (regardless of whether the QoS configuration on the first core network device side needs to be updated), the access network device may execute S811a after executing S804:

[0496] S811a: The access network device sends information X6 to the terminal device. Correspondingly, the terminal device receives information X6 from the access network device.

[0497] The information X6 is used to indicate that the access network device has successfully updated the QoS configuration of the QoS flow. It can be understood that in S811a, the information X6 is used to indicate the QoS configuration update on the access network device side, and is not used to indicate the QoS configuration update on the first core network device side.

[0498] In case 3, further, if the QoS configuration on the first core network device side does not need to be updated, S811 includes S811a but does not include S811b. Conversely, if the QoS configuration on the first core network device side needs to be updated and the update is successful, S811 also includes S811b:

[0499] S811b: The access network device sends information X6 to the terminal device. Correspondingly, the terminal device receives information X6 from the access network device.

[0500] Among them, information X6 is used to indicate that the first core network device has successfully updated the QoS configuration of the QoS flow. It can be understood that in S811b, information X6 is used to indicate the QoS configuration update status on the first core network device side, and is not used to indicate the QoS configuration update status on the access network device side.

[0501] For the terminal device, when the terminal device receives the information X6, it executes S812:

[0502] S812. Optionally, the terminal device stops sending information X1 to the access network device, thereby saving communication resources.

[0503] For the terminal device, as a possible implementation method, when the terminal device receives information X6, the terminal device updates the configuration of the QoS flow to the target QoS configuration, or the terminal device updates the configuration of the QoS flow according to the target QoS configuration.

[0504] In this way, the QoS configuration update triggered by the terminal device is successful.

[0505] That is to say, when the terminal device determines that the service characteristics need to be updated, the terminal device determines the target QoS configuration and notifies the access network device to update the QoS configuration in the form of an accompanying data packet, thereby realizing dynamic QoS configuration update and ensuring the dynamic network requirements of the service.

[0506] The specific implementation of the communication method shown in FIG. 8 will be described in detail below with reference to the example shown in FIG. 9 .

[0507] FIG9 is a flow chart of a communication method according to an embodiment of the present application. The first core network device in FIG8 may be the UPF network element shown in FIG9 , the second core network device in FIG8 may be the SMF network element shown in FIG9 , the third core network device in FIG8 may be the PCF network element shown in FIG9 , and the access network device in FIG8 may be the RAN device shown in FIG9 .

[0508] Specifically, in FIG9 , the communication method according to an embodiment of the present application includes the following steps:

[0509] S901. The terminal device determines that the service characteristics of the service are updated.

[0510] S902: The terminal device determines the target QoS configuration for the QoS flow. This step is optional. The terminal device may send information X1 to the RAN device. The information X1 is used to represent service characteristics of the service update, such as the end of a frame, the size of a burst, the duration of a burst, and / or the arrival time of a burst.

[0511] S903: The terminal device sends information X1 to the RAN device. Correspondingly, the RAN device receives the information X1 from the terminal device.

[0512] S904. The RAN device updates the QoS configuration of the QoS flow. For example, the RAN device decides to update the QoS configuration of the QoS flow, such as the size of the maximum burst data volume MDBV, based on the service characteristics indicated by the information X1. It can also be understood that the access network device dynamically adjusts resources or efficiently schedules resources based on the information X1 on the terminal device side. For example, if the access network device learns that the traffic characteristics of the service have changed (such as the data volume, duration, expected arrival time, period, start or end information of the burst traffic), the access network device can flexibly schedule network resources to ensure the transmission of the service. At the same time, it can also allocate resources to other services or other users, thereby further improving resource utilization. For another example, based on the changes in service traffic characteristics, the access network device determines that no data will arrive in the future for a period of time, and thus allocates wireless resources to other services or other users, thereby improving resource utilization.

[0513] S905: The RAN device sends information X3 to the terminal device. Correspondingly, the terminal device receives information X3 from the RAN device.

[0514] S906. The terminal device performs adaptive adjustment.

[0515] S907: Optionally, the RAN device sends information X1 to the UPF network element. Correspondingly, the UPF network element receives the information X1 from the RAN device.

[0516] S908. The UPF network element updates the N4 rule of the QoS flow.

[0517] S909: Optionally, the UPF network element sends information X5 to the RAN device. Correspondingly, the RAN device receives information X5 from the UPF network element.

[0518] S910. Optionally, the RAN device stops sending information X1 to the UPF network element, thereby saving communication resources.

[0519] S911. Optionally, the RAN device sends information X6 to the terminal device. Correspondingly, the terminal device receives information X6 from the RAN device.

[0520] S912. Optionally, the terminal device stops sending information X1 to the RAN device.

[0521] Among them, S901-S912 can refer to the introduction of S801-S812 and will not be repeated here.

[0522] In this way, the QoS configuration update triggered by the terminal device is successful.

[0523] In some embodiments, for the RAN device, when the RAN device determines that the QoS configuration update is successful, the RAN device further executes S913:

[0524] S913. Optionally, the RAN device sends a QoS change notification (QoS Notification Control) message.

[0525] The QoS Notification Control message is used to indicate that the QoS configuration has been updated and to indicate the updated target QoS configuration.

[0526] Exemplarily, the RAN device sends a QoS Notification Control message to the SMF network element through the AMF network element. Correspondingly, the SMF network element receives the QoS Notification Control message from the RAN device through the AMF network element.

[0527] Optionally, the QoS Notification Control message includes at least one of a target index and a target parameter, wherein the target index and the target parameter can be found in the introduction of information X5 and will not be described in detail.

[0528] Optionally, the QoS Notification Control message includes information X2, thereby indicating to the SMF network element (and / or PCF network element) the time period during which the target QoS configuration is valid.

[0529] For the SMF network element, when the SMF network element receives the QoS Notification Control message, the SMF network element sends the QoS Notification Control message to the PCF network element. Correspondingly, the PCF network element receives the QoS Notification Control message from the SMF network element.

[0530] For the SMF network element and the PCF network element, when the QoS Notification Control message is received, S914 is executed:

[0531] S914. The SMF network element and the PCF network element adjust the QoS policy according to the QoS Notification Control message.

[0532] In this way, the SMF and PCF network elements can clearly understand the currently effective target QoS configuration and make corresponding adjustments. For example, they can adjust the charging policy based on the target QoS configuration.

[0533] As shown in FIG10 , taking the first core network device triggering a QoS configuration update as an example, the communication method proposed in the embodiment of the present application includes the following operations:

[0534] S1001. A first core network device determines a service feature update for a service.

[0535] Exemplarily, the first core network device is introduced as follows:

[0536] In the embodiment of the present application, the first core network device is a user plane network element. Taking a 5G communication system as an example, the first core network device can be a UPF network element.

[0537] Exemplarily, when the trigger condition a1 is met, the first core network device determines that the service feature of the service is updated (ie, the service demand has changed).

[0538] The trigger condition a1 includes at least one of the following:

[0539] Trigger condition a1-1: The difference between data volume y1 and data volume y2 is greater than threshold y. Data volume y1 is the amount of data transmitted during time unit y1, and data volume y2 is the amount of data transmitted during time unit y2. This means that the traffic characteristics of the service have changed.

[0540] In the embodiment of the present application, the data volume y1 and the data volume y2 are the data volumes of the same service, and the service data of the service are transmitted through the same QoS flow.

[0541] Trigger condition a1-2, and obtain notification message y. The notification message y indicates the network requirements of the service or the service characteristics of the service. For example, the notification message y indicates the size of the media frame, and the media frame includes the data of the service. The notification message y is the notification message carried in the data packet received by the first core network device. In the case that an application server needs to receive or send a large number of media frames, the notification message y indicates the network requirements of the service, so that the first core network device is informed of the network requirement update of the service. Specifically, the notification message y may be in the protocol header or extended header field of the IP / TCP / UDP / QUIC / RTP of the data packet. For example, the notification message y is in the RTP protocol extension header of the downlink data packet. The notification message y is used to characterize the current media frame, the size of the burst data, the period of the burst data, the start or end of the burst data, the duration corresponding to the service characteristics, or the arrival time of the corresponding burst data, etc.

[0542] Trigger condition a1-3: the QoS configuration of the QoS flow expires. The QoS flow is used to transmit the above-mentioned service. The QoS configuration of the QoS flow has a valid time period. For example, the valid time period of QoS configuration 1 is recorded as time period 1, and the valid time period of QoS configuration 2 is recorded as time period 2. When time period 1 expires, it means that the service characteristics of the above-mentioned service are updated, that is, from service characteristics 1 to service characteristics 2. Accordingly, the first core network device needs to update the QoS configuration, such as updating from QoS configuration 1 to QoS configuration 2.

[0543] It should be understood that the trigger condition a1 may be configured by the second core network device, as described in the introduction to rule N4, which will not be repeated here. Alternatively, the trigger condition a1 may also be pre-configured, which is not limited in the present embodiment.

[0544] That is to say, compared with S701, the difference of S1001 is that the execution entity is the first core network device.

[0545] For the first core network device, when it is determined that the service feature of the service is updated, S1002 and S1003 are executed:

[0546] S1002. Optionally, the first core network device determines a target QoS configuration for the QoS flow.

[0547] This step is optional, that is, after the first core network device determines that the service characteristics have changed, it does not execute S1002 but executes S1003.

[0548] Exemplarily, the first core network device determines a target QoS configuration for the QoS flow based on updated service characteristics or updated service requirements, wherein the target QoS configuration is a configuration indicated by a target QoS parameter set.

[0549] For example, when the N4 rule includes at least two QoS parameter sets, the first core network device selects one QoS parameter set from the at least two QoS parameter sets based on the updated service characteristics as the target QoS parameter set. Accordingly, the first core network device updates the QoS configuration of the QoS flow based on the target QoS parameter set. As a possible alternative description, the first core network device determines the target QoS configuration from the at least two QoS configurations based on the updated service characteristics.

[0550] Optionally, when the N4 rule includes at least two QoS parameter sets, each QoS parameter set has an index. Accordingly, the first core network device can also determine the index of the target QoS parameter set, which is recorded as the target index. The target index is used to identify the target QoS configuration, which can be understood as the target index being used to determine the target QoS configuration.

[0551] For another example, when the N4 rule includes a set of QoS parameter sets (such as the basic QoS parameter set described above), the first core network device determines the first QoS parameter in the QoS parameter set (e.g., determines the size of the first QoS parameter) based on the updated service characteristics. When the size of the first QoS parameter is determined, the QoS configuration indicated by the QoS parameter set is the target QoS configuration. As a possible alternative description, the first core network device determines the first QoS parameter in the QoS configuration of the QoS flow based on the updated service characteristics, thereby determining the target QoS configuration.

[0552] Optionally, when the N4 rule includes a set of QoS parameter sets (such as the basic QoS parameter set described above), the first core network device determines a target parameter (value) based on the value before the first QoS parameter is adjusted, the value after the first QoS parameter is adjusted, and the step size. In an embodiment of the present application, the target parameter is used to determine a target QoS configuration.

[0553] Optionally, if there are multiple first QoS parameters, that is, there are multiple adjustable QoS parameters, the above target parameters include the first QoS parameter and the number of adjustment steps, that is, the bandwidth and 10.

[0554] For another example, when the N4 rule includes a set of QoS parameter sets (such as the above-mentioned basic QoS parameter set, which includes an adjustable range of the first QoS parameter), the first core network device determines the above-mentioned first QoS parameter within the adjustable range of the first QoS parameter (for example, determines the size of the first QoS parameter) based on the updated service characteristics. Wherein, when the size of the first QoS parameter is determined, the above-mentioned QoS configuration indicated based on the QoS parameter set is the target QoS configuration. As a possible alternative description, the first core network device determines the first QoS parameter in the QoS configuration of the above-mentioned QoS flow based on the updated service characteristics, thereby determining the target QoS configuration. For example, the first QoS parameter is bandwidth, and the adjustable range of the first QoS parameter is 10-50MHz. The value of the first QoS parameter after adjustment is 30MHz, and the size of the target parameter is 30.

[0555] Optionally, if there are multiple first QoS parameters, that is, multiple adjustable QoS parameters, there are also multiple adjustable ranges. For example, there are two first QoS parameters, denoted as QoS parameter 1 and QoS parameter 2. The adjustable range of QoS parameter 1 is denoted as adjustable range 1, and the adjustable range of QoS parameter 2 is denoted as adjustable range 2. The target parameters mentioned above then include the first QoS parameters and the adjusted target values, such as bandwidth and 30.

[0556] In the embodiment of the present application, the target parameter is used to determine the target QoS configuration.

[0557] For S1002, it can also be replaced with the following description:

[0558] Replace description 1. When the service characteristics of the service are updated, the first core network device determines the target QoS configuration of the QoS flow according to the updated service characteristics or service requirements, that is, determines the N4 rule corresponding to the QoS flow.

[0559] That is to say, compared with S802, the difference of S1002 is that the execution entity is the first core network device.

[0560] S1003: The first core network device sends information Y1 to the access network device. Correspondingly, the access network device receives the information Y1 from the first core network device.

[0561] The information Y1 is used to indicate the target QoS configuration of the QoS flow.

[0562] For example, the information Y1 may include the following information:

[0563] For example, the information Y1 includes a target index, for which reference can be made to the introduction of S1002 and will not be described in detail.

[0564] For another example, information Y1 includes target parameters, which can be found in the introduction of S1002 and will not be described in detail.

[0565] For another example, the information Y1 includes information of target QoS configuration, such as information Y1 including one or more of the following: the size of PDB, the size of PER, or the size of bandwidth.

[0566] For another example, information Y1 includes target network requirements of the service or updated service characteristics, such as media frame data size, burst data size, burst data arrival time and / or burst data continuous transmission time, etc.

[0567] For example, the information Y1 may be carried in the following information:

[0568] For example, information Y1 is carried in the GTP-U layer of the downlink data packet. That is, S1003 can be replaced by the following description: the first core network device sends a downlink data packet to the access network device. Accordingly, the access network device receives the downlink data packet from the first core network device. The GTP-U layer of the downlink data packet includes information Y1.

[0569] It should be understood that information Y1 can also be carried in other messages, and this embodiment of the present application does not limit this.

[0570] It is understandable that, optionally, the first core network device can continue to send information Y1 to the access network device until feedback information is received from the access network device. Alternatively, the first core network device sends information Y1 to the access network device on one or multiple consecutive data packets until feedback information is received from the access network device. For details, see the introduction of S1011 and S1012, which will not be repeated here. In an embodiment of the present application, the first core network device sends information Y1 to the access network device on one or more data packets to ensure that the access network device can successfully receive information Y1, thereby improving the reliability of information transmission and realizing dynamic adjustment of QoS configuration.

[0571] Optionally, the first core network device sends information Y2 to the access network device. Accordingly, the access network device receives information Y2 from the first core network device. Information Y2 indicates the start time or time period Y for the service feature update, where time period Y is the time period during which the target QoS configuration is valid. For details about the target QoS configuration, refer to the description of S1002 and are not further described here.

[0572] For example, the information Y2 indicates the start time and the end time of the time period Y.

[0573] For another example, information Y2 indicates the starting time and duration of time period Y.

[0574] For another example, information Y2 indicates the end time of time period Y.

[0575] For another example, information Y2 indicates the duration of time period Y.

[0576] For example, when information Y2 indicates the end time or duration of time period Y, the start time of time period Y may be the time when the access network device receives information Y2. Alternatively, the start time of time period Y may be the time when the access network device updates the QoS configuration of the QoS flow to the target QoS configuration.

[0577] It should be understood that information Y2 can be carried in a downlink data packet. The downlink data packet is a data packet sent by the first core network device to the access network device. In this embodiment of the present application, information Y2 and information Y1 can be carried in the same downlink data packet for transmission, or they can be carried in different downlink data packets for transmission, which is not limited in this embodiment of the present application.

[0578] It should be understood that the time period Y can be determined autonomously by the first core network device.

[0579] Alternatively, time period Y may also be determined by the third core network device. For example, after the third core network device determines time period Y, it indicates time period Y to the second core network device through the PCC rule, and then indicates time period Y to the first core network device through the second core network device.

[0580] Alternatively, the time period Y may also be determined by the second core network device. For example, after the second core network device determines the time period Y, it indicates the time period Y to the first core network device.

[0581] In the embodiment of the present application, the manner in which the first core network device obtains the time period Y is not limited.

[0582] That is to say, compared with S803, the difference of S1003 is that the execution entity is the first core network device, and the information sent is information Y1.

[0583] For the access network device, when the access network device receives the information Y1, the access network device executes S1004:

[0584] S1004: The access network device updates the QoS configuration of the QoS flow.

[0585] For the access network device, information Y1 is used to determine the QoS profile corresponding to the target QoS configuration. Information Y1 can be found in the description of S1003 and will not be further described. For example, upon receiving information Y1, the access network device determines the target QoS configuration for the QoS flow based on information Y1 and updates the QoS configuration of the QoS flow based on the target QoS configuration.

[0586] For another example, upon receiving information Y1, the access network device updates the QoS description of the QoS flow. The QoS description indicates the QoS configuration. Updating the QoS description of the QoS flow by the access network device means that the access network device updates the QoS configuration of the QoS flow. For example, information Y1 includes target network requirements for the service, such as service characteristics after the service update, which may specifically include the end of a frame, the size of a burst data flow, the duration of the burst data flow, and / or the arrival time of the burst data flow. The access network device then determines the maximum data burst volume (MDBV) based on at least one of the above-mentioned burst service traffic characteristics.

[0587] For another example, upon receiving information Y1, the access network device updates the QoS description of the QoS flow. It can also be understood that the access network device dynamically adjusts resources or efficiently schedules resources based on the information Y1 on the first core network device side. For example, if the access network device learns of changes in the traffic characteristics of the service (such as the data volume, duration, expected arrival time, period, start or end information of the burst flow), the access network device can flexibly schedule network resources to ensure the transmission of the service. At the same time, it can also allocate network resources to other services or other users, thereby further improving resource utilization.

[0588] For another example, upon receiving information Y1, the access network device determines the target QoS description of the QoS flow based on information Y1, and updates the QoS configuration of the QoS flow based on the target QoS description, wherein the target QoS description indicates the target QoS configuration.

[0589] Optionally, the access network device determines whether RRC reconfiguration is required based on the target QoS configuration. If RRC reconfiguration is required, the access network device initiates an RRC reconfiguration process to the terminal device to update the QoS configuration of the QoS flow to the target QoS configuration, or to update the QoS configuration of the data radio bearer (DRB) to the target QoS configuration.

[0590] That is, compared with S704, the difference of S1004 is that the execution subject is the access network device and the reference information is information Y1.

[0591] For the access network device, the QoS configuration update may succeed or fail. In the case of a failure in the QoS configuration update, the access network device may optionally execute S1005-S1006. In the case of a success in the QoS configuration update, the access network device may optionally execute S1007, which is described in detail as follows:

[0592] S1005: Optionally, the access network device sends information Y3 to the first core network device. Correspondingly, the first core network device receives the information Y3 from the access network device.

[0593] The information Y3 is used to indicate that the access network device has failed to update the QoS configuration of the QoS flow. The access network device updates the QoS configuration of the QoS flow based on the information Y1.

[0594] For example, if the current network resources do not meet the target QoS configuration (i.e., the target QoS configuration indicated by information Y1), the access network device fails to update the QoS configuration of the QoS flow. The current network resources refer to the air interface resources between the access network device and the terminal device, that is, the access network device determines that the target QoS configuration cannot be met at this time.

[0595] Optionally, the access network device sends information Y4 to the first core network device. Accordingly, the first core network device receives information Y4 from the access network device. Information Y4 indicates the QoS configuration supported by the access network device. For information Y4, see the introduction to information X4 and will not be repeated here.

[0596] Exemplarily, information Y4 is carried in an uplink data packet. That is, the access network device sends an uplink data packet to the first core network device. Correspondingly, the first core network device receives the uplink data packet from the access network device. The GTP-U layer of the uplink data packet includes information Y4.

[0597] It should be understood that information Y4 can also be carried in other messages, and this embodiment of the present application does not limit this.

[0598] That is to say, compared with S805, the difference of S1005 is that the information receiving end is the first core network device, and the transmitted information is information Y3.

[0599] For the first core network device, when the first core network device receives information Y3, S1006 is executed:

[0600] S1006. The first core network device stops adjusting the QoS configuration.

[0601] Optionally, when the first core network device receives information Y4, the first core network device updates the QoS configuration of the QoS flow based on information Y4. For example, the first core network device updates the QoS configuration to the QoS configuration indicated by information Y4, thereby updating the QoS configuration. Because the QoS configuration indicated by information Y4 is closest to the target QoS configuration, the first core network device can also meet dynamically changing service needs as much as possible when updating the QoS configuration based on information Y4.

[0602] S1007: Optionally, the access network device sends information Y1 to the terminal device. Correspondingly, the terminal device receives the information Y1 from the access network device.

[0603] The information Y1 is used to indicate the target QoS configuration of the QoS flow.

[0604] Exemplarily, the information Y1 may include target index, target parameters or target QoS configuration information. For details, please refer to the introduction of S1003 and will not be repeated here.

[0605] Optionally, the access network device determines whether it is necessary to send information Y1 to the terminal device based on the target QoS configuration, see S807 for details. The difference is that the receiving end here is replaced by the first core network device to the terminal device.

[0606] For example, the information Y1 may be carried in the following information:

[0607] For example, information Y1 is carried in the PDCP layer of the downlink data packet. That is, S1007 can be replaced by the following description: the access network device sends a downlink data packet to the terminal device. Correspondingly, the terminal device receives the downlink data packet from the access network device. The PDCP layer of the downlink data packet includes information Y1.

[0608] For another example, information Y1 is carried in RRC signaling. That is, S1007 can be replaced by the following description: the access network device sends RRC signaling to the terminal device. Correspondingly, the terminal device receives the RRC signaling from the access network device. The RRC signaling includes information Y1.

[0609] For another example, information Y1 is carried in a MAC CE. That is, S1007 can be alternatively described as: the access network device sends a MAC CE to the terminal device. Correspondingly, the terminal device receives the MAC CE from the access network device. The MAC CE includes information Y1.

[0610] It should be understood that information Y1 can also be carried in other messages, and this embodiment of the present application does not limit this.

[0611] It is understood that the access network device may continue to send information Y1 to the terminal device until feedback information is received from the terminal device. Alternatively, the access network device may send information Y1 to the terminal device in one or more data packets until feedback information is received from the terminal device. For details, see S1009 and S1010, which will not be repeated here. In the embodiment of the present application, the access network device continuously sends information Y1 to the terminal device, which helps the terminal device successfully receive information Y1, thereby improving the reliability of information transmission.

[0612] Optionally, the access network device determines whether it is necessary to send information Y1 to the terminal device based on the target QoS configuration. Please refer to S807 for details and will not be repeated here.

[0613] That is to say, compared with S807, the difference of S1007 is that the information receiving end is the terminal device, and the transmitted information is information Y1.

[0614] Optionally, when the access network device receives information Y2, the access network device sends information Y2 to the terminal device. Accordingly, the terminal device receives information Y2 from the access network device. Information Y2 and information Y1 may be carried in the same message or in different messages, which is not limited in this embodiment of the present application.

[0615] For the terminal device, when the terminal device receives the information Y1, it executes S1008:

[0616] S1008. Optionally, the terminal device updates the QoS configuration of the QoS flow.

[0617] For the terminal device, the information Y1 is used to determine the QoS rule corresponding to the target QoS configuration. The information Y1 can be found in the introduction of S1003 and will not be described in detail.

[0618] For example, upon receiving information Y1, the terminal device updates the QoS rule of the QoS flow, wherein the QoS rule indicates the QoS configuration. The terminal device updating the QoS rule of the QoS flow means that the terminal device updates the QoS configuration of the QoS flow.

[0619] That is to say, compared with S808, the difference of S1008 is that the execution subject is the terminal device.

[0620] Optionally, for a terminal device, after the QoS configuration is updated, the terminal device performs the following operations:

[0621] S1009: Optionally, the terminal device sends information Y5 to the access network device. Correspondingly, the access network device receives the information Y5 from the terminal device.

[0622] The information Y5 is used to indicate that the terminal device has successfully updated the QoS configuration of the QoS flow. The terminal device updates the QoS configuration of the QoS flow based on the information Y1.

[0623] Exemplarily, the information Y5 includes the following information:

[0624] For example, information Y5 includes a target index and an ACK. The target index can be found in the description of S1002 and will not be repeated here. The ACK is used to indicate that the QoS configuration corresponding to the target index has been successfully updated. The QoS configuration corresponding to the target index can be understood as the target QoS configuration determined by the terminal device based on the target index.

[0625] For another example, information Y5 includes a target parameter and an ACK. The target parameter can be found in the description of S1002 and will not be further described. The ACK indicates that the QoS configuration corresponding to the target parameter has been successfully updated. The QoS configuration corresponding to the target parameter can be understood as the target QoS configuration determined by the terminal device based on the target parameter.

[0626] That is to say, compared with S809, the difference of S1009 is that the execution subject is the terminal device and the transmitted information is information Y5.

[0627] For the access network device, when the access network device receives the information Y5, it executes S1010 and / or S1011:

[0628] S1010. Optionally, the access network device stops sending information Y1 to the terminal device, thereby saving communication resources.

[0629] S1011. Optionally, the access network device sends information Y6 to the first core network device. Correspondingly, the first core network device receives the information Y6 from the access network device.

[0630] Information Y6 indicates that the terminal device and / or access network device have successfully updated the QoS configuration of the QoS flow. The terminal device updates the QoS configuration of the QoS flow based on information Y1, and the access network device updates the QoS configuration of the QoS flow based on information Y1.

[0631] Exemplarily, the information Y6 includes the following information:

[0632] For example, information Y6 includes a target index and ACK, which can be found in the introduction of information Y5 and will not be repeated here.

[0633] For another example, information Y6 includes target parameters and ACK, which can be found in the introduction of information Y5 and will not be repeated here.

[0634] It is easy to understand that the following introduction is made about S1011:

[0635] Example 1: In this embodiment of the present application, if the QoS configuration on the access network device side is successfully updated and the QoS configuration on the terminal device side does not need to be updated, the access network device can execute S1011 after executing S1004. Information Y6 is used to indicate that the access network device has successfully updated the QoS configuration of the QoS flow.

[0636] Example 2: In an embodiment of the present application, if the QoS configuration on the access network device side is successfully updated and the QoS configuration on the terminal device side is also successfully updated, the access network device may execute S1011 after executing S1009. Information Y6 is used to indicate that the terminal device and the access network device have successfully updated the QoS configuration for the QoS flow.

[0637] Case 3: In the embodiment of the present application, S1011 includes S1011a. Optionally, S1011 also includes S1011b. Specifically:

[0638] If the QoS configuration on the access network device side is updated successfully (regardless of whether the QoS configuration on the terminal device side needs to be updated), the access network device may execute S1011a after executing S1004:

[0639] S1011a: The access network device sends information Y6 to the first core network device. Correspondingly, the first core network device receives information Y6 from the access network device.

[0640] The information Y6 is used to indicate that the access network device has successfully updated the QoS configuration of the QoS flow. It can be understood that in S1011a, the information Y6 is used to indicate the QoS configuration update on the access network device side, not on the terminal device side.

[0641] In case 3, further, if the QoS configuration on the terminal device side does not need to be updated, S1011 includes S1011a but does not include S1011b. On the contrary, if the QoS configuration on the terminal device side needs to be updated and the update is successful, S1011 also includes S1011b:

[0642] S1011b: The access network device sends information Y6 to the first core network device. Correspondingly, the first core network device receives information Y6 from the access network device.

[0643] Information Y6 is used to indicate that the terminal device has successfully updated the QoS configuration of the QoS flow. It can be understood that in S1011b, information Y6 is used to indicate the QoS configuration update status on the terminal device side, not on the access network device side.

[0644] For the first core network device, when the first core network device receives information Y6, it executes S1012:

[0645] S1012. Optionally, the first core network device stops sending information Y1 to the access network device, thereby saving communication resources.

[0646] For the first core network device, as a possible implementation method, when the first core network device receives information Y6, the first core network device updates the configuration of the QoS flow to the target QoS configuration, or the first core network device updates the configuration of the QoS flow according to the target QoS configuration.

[0647] In this way, the QoS configuration update triggered by the first core network device is successful.

[0648] That is to say, when the first core network device determines the service feature update, the first core network device determines the target QoS configuration and notifies the access network device to update the QoS configuration in the form of an accompanying data packet, thereby realizing dynamic QoS configuration update and ensuring the dynamic network requirements of the service.

[0649] The specific implementation of the communication method shown in FIG. 10 will be described in detail below in conjunction with the example shown in FIG. 11 .

[0650] Figure 11 is a flow chart of a communication method provided in an embodiment of the present application. The first core network device in Figure 10 may be the UPF network element shown in Figure 11 , the second core network device in Figure 10 may be the SMF network element shown in Figure 11 , the third core network device in Figure 10 may be the PCF network element shown in Figure 11 , and the access network device in Figure 10 may be the RAN device shown in Figure 11 .

[0651] Specifically, in FIG11 , the communication method according to an embodiment of the present application includes the following steps:

[0652] S1101. The UPF network element determines that the service characteristics of the service are updated.

[0653] S1102: The UPF network element determines the target QoS configuration for the QoS flow. This step is optional. The UPF network element may send information Y1 to the RAN device. The information Y1 is used to characterize service characteristics of the service update, such as the media frame data size, burst data size, burst data arrival time, and / or burst data transmission duration.

[0654] S1103: The UPF network element sends information Y1 to the RAN device. Correspondingly, the RAN device receives information Y1 from the UPF network element.

[0655] S1104. The RAN device updates the QoS configuration of the QoS flow. For example, the RAN device decides to update the QoS configuration of the QoS flow, such as the size of the maximum burst data volume (MDBV), based on the service characteristics indicated by the information Y1. It can also be understood that the access network device dynamically adjusts resources or efficiently schedules resources based on the information Y1 on the first core network device side. For example, if the access network device learns of changes in the traffic characteristics of the service (such as the data volume, duration, expected arrival time, period, start or end information of the burst traffic), the access network device can flexibly schedule network resources to ensure the transmission of the service. At the same time, it can also allocate network resources to other services or other users, thereby further improving resource utilization. For another example, based on changes in service traffic characteristics, the access network device determines that no data will arrive in the future, and thus allocates wireless resources to other services or other users, thereby improving resource utilization.

[0656] S1105: Optionally, the RAN device sends information Y3 to the first core network device. Correspondingly, the first core network device receives the information Y3 from the RAN device.

[0657] S1106. The first core network device stops adjusting the QoS configuration.

[0658] S1107: Optionally, the RAN device sends information Y1 to the terminal device. Correspondingly, the terminal device receives information Y1 from the RAN device.

[0659] S1108. Optionally, the terminal device updates the QoS configuration of the QoS flow.

[0660] S1109: Optionally, the terminal device sends information Y5 to the RAN device. Correspondingly, the RAN device receives the information Y5 from the terminal device.

[0661] S1110. Optionally, the RAN device stops sending information Y1 to the terminal device, thereby saving communication resources.

[0662] S1111. Optionally, the RAN device sends information Y6 to the UPF network element. Correspondingly, the UPF network element receives information Y6 from the RAN device.

[0663] S1112. Optionally, the UPF network element stops sending information Y1 to the RAN device, thereby saving communication resources.

[0664] Among them, S1101-S1112 can refer to the introduction of S1001-S1012 and will not be repeated here.

[0665] In some embodiments, for the RAN device, when the RAN device determines that the QoS configuration update is successful, S1113 is further executed:

[0666] S1113. The RAN device sends a QoS Notification Control message.

[0667] The QoS Notification Control message is used to indicate that the QoS configuration has been updated and to indicate the updated target QoS configuration.

[0668] For example, the implementation process of S1113 can refer to the introduction of S913 and will not be repeated here.

[0669] For the SMF network element, when the SMF network element receives the QoS Notification Control message, the SMF network element sends the QoS Notification Control message to the PCF network element. Correspondingly, the PCF network element receives the QoS Notification Control message from the SMF network element.

[0670] For the SMF network element and the PCF network element, when the QoS Notification Control message is received, S1114 is executed:

[0671] S1114, the SMF network element and the PCF network element adjust the QoS policy according to the QoS Notification Control message.

[0672] For example, the implementation process of S1114 can refer to the introduction of S914 and will not be repeated here.

[0673] In this way, the SMF and PCF network elements can clearly understand the currently effective target QoS configuration and make corresponding adjustments. For example, they can adjust the charging policy based on the target QoS configuration.

[0674] As shown in FIG12 , taking the access network device triggering a QoS configuration update as an example, the communication method proposed in the embodiment of the present application includes the following operations:

[0675] S1201: The access network device determines that the service characteristics of the service are updated.

[0676] Exemplarily, when the trigger condition b1 is met, the access network device determines that the service feature of the service is updated.

[0677] The trigger condition b1 includes at least one of the following:

[0678] Trigger condition b1-1: The difference between data volume z1 and data volume z2 is greater than threshold z. Data volume z1 is the amount of data transmitted during time unit z1, and data volume z2 is the amount of data transmitted during time unit z2. This means that the traffic characteristics of the service have changed.

[0679] In the embodiment of the present application, the data volume z1 and the data volume z2 are the data volumes of the same service, and the service data of the service are transmitted through the same QoS flow.

[0680] Trigger condition b1-2: The QoS configuration of the QoS flow expires. The QoS flow is used to transmit the aforementioned service. The QoS configuration of the QoS flow has a valid time period. For example, the valid time period of QoS configuration 1 is recorded as time period 1, and the valid time period of QoS configuration 2 is recorded as time period 2. When time period 1 expires, the service characteristics of the aforementioned service are updated, that is, from service characteristics 1 to service characteristics 2. Accordingly, the access network device needs to update the QoS configuration, for example, from QoS configuration 1 to QoS configuration 2.

[0681] Trigger condition b1-3, and obtain notification message z. Among them, notification message z indicates the network demand of the service. For example, notification message z indicates the size of the media frame, and the media frame includes the data of the service. Notification message z is a notification message carried in the data packet received by the access network device. In the case that an application server needs to receive or send a large number of media frames, notification message z indicates the network demand of the service, so that the access network device is informed of the network demand update of the service. Specifically, the notification message z may be in the protocol header or extension header field of the IP / TCP / UDP / QUIC / RTP of the data packet. For example, the notification message z is in the RTP protocol extension header or the downlink GTP-U layer header of the downlink data packet. The notification message z is used to characterize the size, start time, duration, network demand, period, start or end, etc. of the current media frame or burst data volume.

[0682] It should be understood that the trigger condition b1 may be configured by the SMF, as described in the QoS description, which will not be described in detail. Alternatively, the trigger condition b1 may also be pre-configured, which is not limited in this embodiment of the present application.

[0683] That is to say, compared with S801 and S1001, the difference of S1201 is that the execution entity is the access network device.

[0684] For the access network device, when it is determined that the service characteristics of the service are updated, the access network device executes S1202, S1203 or S1207, which are described in detail as follows:

[0685] On the one hand, the access network device performs an update of the QoS configuration, as described in S1202:

[0686] S1202: The access network device updates the QoS configuration of the QoS flow.

[0687] Exemplarily, the access network device updates the QoS configuration of the QoS flow to a target QoS configuration, wherein the target QoS configuration is a configuration indicated by a target QoS parameter set.

[0688] Among them, the access network device updates the QoS configuration of the QoS flow, which can also be understood as the access network device dynamically adjusting resources or efficiently scheduling resources according to the dynamic changes in service characteristics. For example, if the access network device learns that the traffic characteristics of the service have changed (such as the data volume, duration, expected arrival time, cycle, start or end information of the burst traffic), the access network device can flexibly schedule network resources to ensure the transmission of the service. At the same time, it can also provide network resources for other services or other users, thereby further improving resource utilization. For example, the access network device determines that there will be no data arriving in the future based on the changes in service traffic characteristics, and thus provides wireless resources to other services or other users, thereby improving resource utilization.

[0689] For example, if the QoS description includes at least two QoS parameter sets, the access network device selects one QoS parameter set from the at least two QoS parameter sets as the target QoS parameter set based on the updated service characteristics. Accordingly, the access network device updates the QoS configuration of the QoS flow based on the target QoS parameter set. As a possible alternative description, the QoS description indicates at least two QoS configurations. Based on the updated service characteristics, the access network device determines the target QoS configuration from the at least two QoS configurations.

[0690] Optionally, when the QoS description includes at least two QoS parameter sets, each QoS parameter set has an index, and accordingly, the access network device can also determine the index of the target QoS parameter set, which is recorded as the target index. The target index is used to identify the target QoS configuration.

[0691] For another example, when the QoS description includes a set of QoS parameter sets (such as the basic QoS parameter set described above), the access network device determines the first QoS parameter in the QoS parameter set (e.g., determines the size of the first QoS parameter) based on the updated service characteristics. When the size of the first QoS parameter is determined, the QoS configuration indicated by the QoS parameter set is the target QoS configuration. As a possible alternative description, the access network device determines the first QoS parameter in the QoS configuration of the QoS flow based on the updated service characteristics, thereby determining the target QoS configuration.

[0692] Optionally, when the QoS description includes a set of QoS parameter sets (such as the basic QoS parameter set described above), the access network device determines a target parameter value based on the value of the first QoS parameter before adjustment, the value of the first QoS parameter after adjustment, and the step size. In this embodiment of the present application, the target parameter is used to determine the target QoS configuration.

[0693] Optionally, if there are multiple first QoS parameters, that is, there are multiple adjustable QoS parameters, the above target parameters include the first QoS parameter and the number of adjustment steps, that is, the bandwidth and 10.

[0694] For another example, when the QoS description includes a set of QoS parameter sets (such as the above-mentioned basic QoS parameter set, which includes an adjustable range of the first QoS parameter), the access network device determines the above-mentioned first QoS parameter within the adjustable range of the first QoS parameter (for example, determines the size of the first QoS parameter) based on the updated service characteristics. Wherein, when the size of the first QoS parameter is determined, the above-mentioned QoS configuration indicated based on the QoS parameter set is the target QoS configuration. As a possible alternative description, the access network device determines the first QoS parameter in the QoS configuration of the above-mentioned QoS flow based on the updated service characteristics, thereby determining the target QoS configuration. For example, the first QoS parameter is bandwidth, and the adjustable range of the first QoS parameter is 10-50MHz. The value of the first QoS parameter after adjustment is 30MHz, and the size of the target parameter is 30.

[0695] Optionally, if there are multiple first QoS parameters, that is, multiple adjustable QoS parameters, there are also multiple adjustable ranges. For example, there are two first QoS parameters, denoted as QoS parameter 1 and QoS parameter 2. The adjustable range of QoS parameter 1 is denoted as adjustable range 1, and the adjustable range of QoS parameter 2 is denoted as adjustable range 2. The target parameters mentioned above then include the first QoS parameters and the adjusted target values, such as bandwidth and 30.

[0696] In the embodiment of the present application, the target parameter is used to determine the target QoS configuration.

[0697] Optionally, the access network device determines whether RRC reconfiguration is required based on the target QoS configuration. If RRC reconfiguration is required, the access network device initiates an RRC reconfiguration process to the terminal device to update the QoS configuration of the QoS flow to the target QoS configuration, or to update the QoS configuration of the data radio bearer (DRB) to the target QoS configuration.

[0698] For S1202, it can also be replaced with the following description:

[0699] When the service characteristics of the service are updated, the access network device determines the target QoS configuration of the QoS flow according to the updated service characteristics, and updates the QoS configuration of the QoS flow according to the target QoS configuration.

[0700] That is to say, compared with S802 and S1002, the difference of S1202 is that the execution subject is the access network device.

[0701] On the other hand, the access network device instructs the first core network device to execute the update of the QoS configuration, as described in S1203 for details:

[0702] S1203: Optionally, the access network device sends information Z1 to the first core network device. Correspondingly, the first core network device receives the information Z1 from the access network device.

[0703] The information Z1 is used to indicate the target QoS configuration of the QoS flow.

[0704] For example, the information Z1 may include the following information:

[0705] For example, the information Z1 includes a target index, for which reference can be made to the introduction of S1202 and will not be described in detail.

[0706] For another example, the information Z1 includes target parameters, which can be found in the introduction of S1202 and will not be described in detail.

[0707] For another example, the information Z1 includes information of the target QoS configuration, such as the information Z1 includes one or more of the following: the size of the PDB, the size of the PER, or the size of the bandwidth.

[0708] For another example, information Z1 includes target network requirements of the service.

[0709] For example, the information Z1 may be carried in the following information:

[0710] For example, information Z1 is carried in the GTP-U layer of the uplink data packet. That is, S1203 can be replaced with the description: the access network device sends an uplink data packet to the first core network device. Accordingly, the first core network device receives the uplink data packet from the access network device. The GTP-U layer of the uplink data packet includes information Z1. Specifically, the access network device can transmit the corresponding information Z1 in one or more uplink data packets.

[0711] It should be understood that information Z1 can also be carried in other messages, and this embodiment of the present application does not limit this.

[0712] It is understandable that the access network device can continue to send information Z1 to the first core network device until feedback information is received from the first core network device. Alternatively, the access network device sends information Z1 to the first core network device on one or more data packets. For details, see the introduction of S1205 and S1206, which will not be repeated here. In an embodiment of the present application, the access network device continues to send information Z1 to the first core network device to ensure that the first core network device successfully receives information Z1, thereby improving the reliability of information transmission and realizing dynamic adjustment of service QoS.

[0713] Optionally, the access network device determines whether it is necessary to send information Y1 to the first core network device based on the target QoS configuration. Please refer to S807 for details and will not be repeated here.

[0714] Optionally, the access network device sends information Z2 to the first core network device. Accordingly, the first core network device receives information Z2 from the access network device. Information Z2 indicates time period Z, which is the time period during which the target QoS configuration is valid. For details about the target QoS configuration, refer to the description of S1202 and are not further described.

[0715] For example, the information Z2 indicates the start time and the end time of the time period Z.

[0716] For another example, information Z2 indicates the start time and duration of time period Z.

[0717] For another example, information Z2 indicates the end time of time period Z.

[0718] For another example, information Z2 indicates the duration of time period Z.

[0719] For example, when information Z2 indicates the end time or duration of time period Z, the start time of time period Z may be the time when the first core network device receives information Z2. Alternatively, the start time of time period Z may be the time when the first core network device updates the QoS configuration of the QoS flow to the target QoS configuration.

[0720] It should be understood that information Z2 can be carried in one or more uplink data packets. The one or more uplink data packets are data packets sent by the access network device to the first core network device. In the embodiment of the present application, information Z2 and information Z1 can be carried in the same data packet for transmission, or they can be carried in different message transmissions, which is not limited in the embodiment of the present application.

[0721] It should be understood that the time period Z may be determined autonomously by the access network device.

[0722] Alternatively, time period Z may also be determined by the third core network device. For example, after the third core network device determines time period Z, it indicates time period Z to the second core network device through the PCC rule, and then indicates time period Z to the access network device through the second core network device.

[0723] Alternatively, the time period Z may also be determined by the second core network device. For example, after the second core network device determines the time period Z, it indicates the time period Z to the access network device.

[0724] In the embodiment of the present application, the manner in which the access network device obtains the time period Z is not limited.

[0725] That is to say, compared with S803 and S1003, the difference of S1203 is that the information sending end is the access network device, the information receiving end is the first core network device, and the transmitted information is information Z1.

[0726] For the first core network device, when the first core network device receives the information Z1, the first core network device executes S1204:

[0727] S1204. The first core network device updates the QoS configuration of the QoS flow.

[0728] For the first core network device, the information Z1 is used to determine the N4 rule corresponding to the target QoS configuration. The information Z1 can be found in the introduction of S1203 and will not be described in detail.

[0729] For example, when receiving information Z1, the first core network device determines the target QoS configuration of the QoS flow based on information Z1, and updates the QoS configuration of the QoS flow based on the target QoS configuration, that is, the first core network device updates the N4 rule of QoS to the N4 rule corresponding to the target QoS configuration.

[0730] For another example, upon receiving information Z1, the first core network device determines a target N4 rule for the QoS flow based on information Z1, and updates the QoS configuration of the QoS flow based on the target N4 rule, wherein the target N4 rule indicates a target QoS configuration.

[0731] That is to say, compared with S804 and S1004, the difference of S1204 is that the execution subject is the first core network device, and the reference information is information Z1.

[0732] Optionally, for the first core network device, after the QoS configuration is updated, the first core network device performs the following operations:

[0733] S1205: Optionally, the first core network device sends information Z3 to the access network device. Correspondingly, the access network device receives the information Z3 from the first core network device.

[0734] The information Z3 is used to indicate that the first core network device has successfully updated the QoS configuration of the QoS flow. The first core network device updates the QoS configuration of the QoS flow based on the information Z1.

[0735] Exemplarily, the information Z3 includes the following information:

[0736] For example, information Z3 includes a target index and an ACK. The target index can be found in the description of S1202 and will not be repeated here. The ACK is used to indicate that the QoS configuration corresponding to the target index has been successfully updated. The QoS configuration corresponding to the target index can be understood as the target QoS configuration determined by the first core network device based on the target index.

[0737] For another example, information Z3 includes a target parameter and an ACK. The target parameter can be found in the description of S1202 and will not be further described. The ACK is used to indicate that the QoS configuration corresponding to the target parameter has been successfully updated. The QoS configuration corresponding to the target parameter can be understood as the target QoS configuration determined by the first core network device based on the target parameter.

[0738] For the access network device, when the access network device receives the information Z3, it executes S1206:

[0739] S1206. Optionally, the access network device stops sending information Z1 to the first core network device, thereby saving communication resources.

[0740] On the other hand, the access network device instructs the terminal device to execute the update of the QoS configuration, as described in S1207:

[0741] S1207: Optionally, the access network device sends information Z1 to the terminal device. Correspondingly, the terminal device receives information Z1 from the access network device.

[0742] The information Z1 is used to indicate the target QoS configuration of the QoS flow.

[0743] Exemplarily, the information Z1 may include a target index, or target parameters, or target QoS configuration information. For details, please refer to the introduction of S1203 and will not be repeated here.

[0744] For example, the information Z1 may be carried in the following information:

[0745] For example, information Z1 is carried in the PDCP layer of one or more downlink data packets. That is, S1207 can be alternatively described as: the access network device sends one or more data packets to the terminal device. Accordingly, the terminal device receives one or more data packets from the access network device. The PDCP layer of the one or more data packets includes information Z1.

[0746] For another example, information Z1 is carried in RRC signaling. That is, S1207 can be replaced by the following description: the access network device sends RRC signaling to the terminal device. Correspondingly, the terminal device receives the RRC signaling from the access network device. The RRC signaling includes information Z1.

[0747] For another example, information Z1 is carried in a MAC CE. That is, S1207 can be replaced by: the access network device sends a MAC CE to the terminal device. Correspondingly, the terminal device receives the MAC CE from the access network device. The MAC CE includes information Z1.

[0748] It should be understood that information Z1 can also be carried in other messages, and this embodiment of the present application does not limit this.

[0749] It is understood that the access network device may continue to send information Z1 to the terminal device until feedback information is received from the terminal device. Alternatively, the access network device may send information Z1 to the terminal device in one or more data packets until feedback information is received from the terminal device. For details, see S1209 and S1210, which will not be repeated here. In the embodiment of the present application, the access network device continuously sends information Z1 to the terminal device, which helps the terminal device successfully receive information Z1, thereby improving the reliability of information transmission.

[0750] Optionally, the access network device determines whether it is necessary to send information Z1 to the terminal device based on the target QoS configuration. Please refer to S807 for details and will not be repeated here.

[0751] Optionally, the access network device sends information Z2 to the terminal device. Accordingly, the terminal device receives information Z2 from the access network device. Information Z2 indicates time period Z, which is the time period during which the target QoS configuration is valid. Information Z2 can be found in the introduction to S1203 and will not be repeated here.

[0752] It should be understood that information Z2 can be carried in a downlink data packet. A downlink data packet is a data packet sent from an access network device to a terminal device. In the embodiments of the present application, information Z2 and information Z1 can be carried in the same data packet for transmission, or they can be carried in different data packets for transmission, which is not limited in the embodiments of the present application.

[0753] For the terminal device, when the terminal device receives the information Z1, the terminal device executes S1208:

[0754] S1208. Optionally, the terminal device updates the QoS configuration of the QoS flow.

[0755] For the terminal device, the information Z1 is used to determine the QoS rule corresponding to the target QoS configuration. The information Z1 can be found in the introduction of S1207 and will not be described in detail.

[0756] For example, upon receiving information Z1, the terminal device updates the QoS rule of the QoS flow, wherein the QoS rule indicates the QoS configuration. The terminal device updating the QoS rule of the QoS flow means that the terminal device updates the QoS configuration of the QoS flow.

[0757] Optionally, for a terminal device, after the QoS configuration is updated, the terminal device performs the following operations:

[0758] S1209: Optionally, the terminal device sends information Z4 to the access network device. Correspondingly, the access network device receives the information Z4 from the terminal device.

[0759] The information Z4 is used to indicate that the terminal device has successfully updated the QoS configuration of the QoS flow. The terminal device updates the QoS configuration of the QoS flow based on the information Z1.

[0760] Exemplarily, the information Z4 includes the following information:

[0761] For example, information Z4 includes a target index and an ACK. The target index can be found in the description of S1202 and will not be repeated here. The ACK is used to indicate that the QoS configuration corresponding to the target index has been successfully updated. The QoS configuration corresponding to the target index can be understood as the target QoS configuration determined by the terminal device based on the target index.

[0762] For another example, information Z4 includes a target parameter and an ACK. The target parameter can be found in the description of S1202 and will not be further described. The ACK indicates that the QoS configuration corresponding to the target parameter has been successfully updated. The QoS configuration corresponding to the target parameter can be understood as the target QoS configuration determined by the terminal device based on the target parameter.

[0763] For the access network device, when the access network device receives the information Z4, it executes S1210:

[0764] S1210. Optionally, the access network device stops sending information Z1 to the terminal device, thereby saving communication resources.

[0765] In this way, the QoS configuration update triggered by the access network device is successful.

[0766] That is to say, when the access network device determines that the service characteristics are updated, the access network device determines the target QoS configuration and notifies the terminal device and / or the first core network device to update the QoS configuration in the form of an accompanying data packet, thereby realizing dynamic QoS configuration updates and ensuring the dynamic network requirements of the service.

[0767] The specific implementation of the communication method shown in FIG. 12 will be described in detail below in conjunction with the example shown in FIG. 13 .

[0768] FIG13 is a fourth flow chart of a communication method provided in an embodiment of the present application. The first core network device in FIG12 may be the UPF network element shown in FIG13 , the second core network device in FIG12 may be the SMF network element shown in FIG13 , the third core network device in FIG12 may be the PCF network element shown in FIG13 , and the access network device in FIG12 may be the RAN device shown in FIG13 .

[0769] Specifically, in FIG13 , the communication method according to an embodiment of the present application includes the following steps:

[0770] S1301. The RAN device determines that a service feature of a service is updated.

[0771] S1302: The RAN device updates the QoS configuration of the QoS flow.

[0772] S1303: Optionally, the RAN device sends information Z1 to the UPF network element. Correspondingly, the UPF network element receives information Z1 from the RAN device.

[0773] S1304. The UPF network element updates the QoS configuration of the QoS flow.

[0774] S1305: Optionally, the UPF network element sends information Z3 to the RAN device. Correspondingly, the RAN device receives information Z3 from the UPF network element.

[0775] S1306. Optionally, the RAN device stops sending information Z1 to the UPF network element, thereby saving communication resources.

[0776] S1307: The RAN device sends information Z1 to the terminal device. Correspondingly, the terminal device receives information Z1 from the RAN device.

[0777] S1308. The terminal device updates the QoS configuration of the QoS flow.

[0778] S1309: Optionally, the terminal device sends information Z4 to the RAN device. Correspondingly, the RAN device receives the information Z4 from the terminal device.

[0779] S1310. Optionally, the RAN device stops sending information Z1 to the terminal device, thereby saving communication resources.

[0780] Among them, S1301-S1310 can refer to the introduction of S1201-S1210 and will not be repeated here.

[0781] In some embodiments, for the RAN device, when the RAN device determines that the QoS configuration update is successful, the RAN device further executes S1311:

[0782] S1311. The RAN device sends a QoS Notification Control message.

[0783] The QoS Notification Control message is used to indicate that the QoS configuration has been updated and to indicate the updated target QoS configuration.

[0784] For example, the implementation process of S1311 can refer to the introduction of S913 and will not be repeated here.

[0785] For the SMF network element, when the SMF network element receives the QoS Notification Control message, the SMF network element sends the QoS Notification Control message to the PCF network element. Correspondingly, the PCF network element receives the QoS Notification Control message from the SMF network element.

[0786] For the SMF network element and the PCF network element, when the QoS Notification Control message is received, S1312 is executed:

[0787] S1312, the SMF network element and the PCF network element adjust the QoS policy according to the QoS Notification Control message.

[0788] For example, the implementation process of S1312 can refer to the introduction of S914 and will not be described in detail.

[0789] In this way, the SMF network element and the PCF network element can clearly understand the target QoS configuration currently in effect and make corresponding adjustments. For example, the charging policy can be adjusted according to the target QoS configuration.

[0790] It is understood that in the embodiment of the present application, the QoS flow can be a GBR QoS flow or a Non-GBR QoS flow. In the embodiment of the present application, it can be applied to video surveillance, XR, cloud gaming, and cloud photography scenarios, etc. For details, please refer to the glossary section and will not be repeated here.

[0791] It is understood that in the embodiments of this application, the collection, storage, use, processing, transmission, provision, and disclosure of user personal information (such as the location of a terminal device) involved are in compliance with relevant laws and regulations and do not violate public order and good morals. For example, the location of a terminal device is obtained with the user's authorization, which is explained here and will not be repeated.

[0792] It is understandable that in each of the above embodiments, the methods and / or steps implemented by the terminal device may also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the terminal device. The methods and / or steps implemented by the access network device may also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the access network device. The methods and / or steps implemented by the core network device (such as the first core network device, the second core network device, or the third core network device described above) may also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the core network device.

[0793] The chip system may be composed of chips, or the chip system may include chips and other discrete devices.

[0794] It is understandable that, in order to realize the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0795] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be pointed out that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0796] 14 shows a schematic structural diagram of a communication device 140. The communication device 140 includes a processing module 1401 and a transceiver module 1402. The communication device 140 can be used to implement the functions of the above-mentioned terminal device, access network device, first core network device, second core network device, or third core network device.

[0797] In some embodiments, the communication device 140 may further include a storage module (not shown in FIG. 14 ) for storing program instructions and data.

[0798] In some embodiments, the transceiver module 1402, which may also be referred to as a transceiver unit, is configured to implement a transmitting and / or receiving function. The transceiver module 1402 may be composed of a transceiver circuit, a transceiver, a transceiver, or a communication interface.

[0799] In some embodiments, the transceiver module 1402 may include a receiving module and a sending module, which are respectively used to execute the receiving and sending steps performed by the terminal device, access network device, first core network device, second core network device or third core network device in the above method embodiments, and / or used to support other processes of the technology described herein; the processing module 1401 may be used to execute the processing steps (such as determination, etc.) performed by the terminal device, access network device, first core network device, second core network device or third core network device in the above method embodiments, and / or used to support other processes of the technology described herein.

[0800] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0801] Optionally, in this application, "the transceiver module receives / sends information" can also be understood as the processing module receiving / sending information via the transceiver module. "The processing module receives / sends information via the transceiver module" can also be understood as the processing module controlling the transceiver module to receive / send information. Alternatively, "the processing module sends information via the transceiver module" can be understood as the processing module outputs information to the transceiver module, which then sends the information; "the processing module receives information via the transceiver module" can be understood as the transceiver module receiving the information and inputting the information to the processing module.

[0802] In the present application, the communication device 140 may be presented in the form of functional modules divided in an integrated manner. The "module" here may refer to a specific application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.

[0803] In some embodiments, when the communication device 140 in Figure 14 is a chip or a chip system, the function / implementation process of the transceiver module 1402 can be implemented through the input and output interface (or communication interface) of the chip or chip system, and the function / implementation process of the processing module 1401 can be implemented through the processor (or processing circuit) of the chip or chip system.

[0804] Since the communication device 140 provided in this embodiment can execute the above method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0805] As a possible product form, the terminal device, access network device, first core network device, second core network device or third core network device described in the embodiments of the present application can also be implemented using the following: one or more field programmable gate arrays (FPGA), programmable logic devices (PLD), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits that can perform the various functions described throughout this application.

[0806] As another possible product form, the terminal device, access network device, first core network device, second core network device or third core network device described in the embodiment of the present application can be implemented by a general bus architecture. For ease of explanation, refer to Figure 15, which is a structural diagram of a communication device 1500 provided in an embodiment of the present application, and the communication device 1500 includes a processor 1501 and a transceiver 1502. The communication device 1500 can be a terminal device, or a chip or chip system therein; or the communication device 1500 can be an access network device, or a chip or module therein; or the communication device 1500 can be a first core network device, or a chip or module therein; or the communication device 1500 can be a second core network device, or a chip or module therein; or the communication device 1500 can be a third core network device, or a chip or module therein.

[0807] Figure 15 only shows the main components of the communication device 1500. In addition to the processor 1501 and the transceiver 1502, the communication device 1500 may further include a memory 1503 and an input and output device (not shown).

[0808] Optionally, processor 1501 is primarily used to process communication protocols and communication data, as well as control the entire communication device, execute software programs, and process software program data. Memory 1503 is primarily used to store software programs and data. Transceiver 1502 may include a radio frequency circuit and an antenna. The radio frequency circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0809] Optionally, the processor 1501 , the transceiver 1502 , and the memory 1503 may be connected via a communication bus.

[0810] When the communication device is powered on, the processor 1501 can read the software program in the memory 1503, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 1501 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1501. The processor 1501 converts the baseband signal into data and processes the data.

[0811] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.

[0812] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the above-mentioned communication device 140 may take the form of a communication device 1500 as shown in FIG. 15 .

[0813] As an example, the functions / implementation process of the processing module 1401 in FIG14 can be implemented by the processor 1501 in the communication device 1500 shown in FIG15 calling the computer-executable instructions stored in the memory 1503. The functions / implementation process of the transceiver module 1402 in FIG14 can be implemented by the transceiver 1502 in the communication device 1500 shown in FIG15.

[0814] As another possible product form, the terminal device, access network device, first core network device, second core network device, or third core network device in this application may adopt the structure shown in Figure 16, or include the components shown in Figure 16. Figure 16 is a schematic diagram of the composition of a communication device 1600 provided in this application.

[0815] As shown in FIG16 , a communication device 1600 includes at least one processor 1601. Optionally, the communication device further includes a communication interface 1602.

[0816] When the program instructions are executed in the at least one processor 1601, the apparatus 1600 may implement the method provided in any of the aforementioned embodiments and any possible designs thereof. Alternatively, the processor 1601 may implement the method provided in any of the aforementioned embodiments and any possible designs thereof through logic circuits or by executing code instructions.

[0817] The communication interface 1602 may be used to receive program instructions and transmit them to the processor. Alternatively, the communication interface 1602 may be used for communication between the communication device 1600 and other communication devices, such as exchanging control signaling and / or service data. Exemplarily, the communication interface 1602 may be used to receive signals from devices other than the communication device 1600 and transmit them to the processor 1601, or to send signals from the processor 1601 to communication devices other than the communication device 1600.

[0818] Optionally, the communication interface 1602 may be a code and / or data read and write interface circuit, or the communication interface 1602 may be a signal transmission interface circuit between a communication processor and a transceiver, or a pin of a chip.

[0819] Optionally, the communication device 1600 may further include at least one memory 1603, which may be used to store required program instructions and / or data. It should be noted that the memory 1603 may exist independently of the processor 1601 or may be integrated with the processor 1601. The memory 1603 may be located within or outside the communication device 1600, without limitation.

[0820] Optionally, the communication device 1600 may further include a power supply circuit 1604, which may be used to supply power to the processor 1601. The power supply circuit 1604 may be located in the same chip as the processor 1601, or in another chip other than the chip where the processor 1601 is located.

[0821] Optionally, the communication device 1600 may further include a bus 1605 , and various parts of the communication device 1600 may be interconnected via the bus 1605 .

[0822] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the communication device 140 shown in FIG. 14 may take the form of the communication device 1600 shown in FIG. 16 .

[0823] As an example, the functions / implementation process of the processing module 1401 in FIG14 can be implemented by the processor 1601 in the communication device 1600 shown in FIG16 calling the computer-executable instructions stored in the memory 1603. The functions / implementation process of the transceiver module 1402 in FIG14 can be implemented by the communication interface 1602 in the communication device 1600 shown in FIG16.

[0824] It should be noted that the structure shown in Figure 16 does not constitute a specific limitation on the terminal device, access network device, first core network device, second core network device, or third core network device. For example, in other embodiments of the present application, the terminal device, access network device, first core network device, second core network device, or third core network device may include more or fewer components than shown, or combine or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0825] Optionally, the processor in the present application may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.

[0826] Optionally, the memory in the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), or direct rambus RAM (DR RAM).

[0827] Optionally, the power supply circuit described in the embodiment of the present application includes but is not limited to at least one of the following: a power supply line, a power supply subsystem, a power management chip, a power consumption management processor, or a power consumption management control circuit.

[0828] In some embodiments, an embodiment of the present application further provides a communication device, which includes a processor for implementing the method in any of the above method embodiments.

[0829] As a possible implementation, the communication device further includes a memory. The memory is used to store necessary computer programs and data. The computer program may include instructions, and the processor may invoke the instructions in the computer program stored in the memory to instruct the communication device to execute any of the above-described method embodiments. Of course, the memory may not be located in the communication device.

[0830] As another possible implementation, the communication device also includes an interface circuit, which is a code / data read / write interface circuit, and the interface circuit is used to receive computer execution instructions (computer execution instructions are stored in a memory, may be read directly from the memory, or may pass through other devices) and transmit them to the processor.

[0831] As another possible implementation, the communication device further includes a communication interface, where the communication interface is used to communicate with a module outside the communication device.

[0832] It can be understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or include chips and other discrete devices. The embodiments of the present application do not specifically limit this.

[0833] The present application also provides a computer-readable storage medium having a computer program or instruction stored thereon, which implements the functions of any of the above method embodiments when executed by a computer.

[0834] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0835] Those skilled in the art will appreciate that, for the sake of convenience and brevity of description, the specific working processes of the above-described systems, devices, and units may refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0836] It is understood that the systems, devices, and methods described in this application may also be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be through some interface, indirect coupling or communication connection of devices or units, and may be electrical, mechanical, or other forms.

[0837] The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Components shown as units may or may not be physical units. Some or all of these units may be selected to achieve the objectives of this embodiment as needed.

[0838] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0839] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state drive (SSD)). In the embodiment of the present application, the computer may include the aforementioned device.

[0840] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0841] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that: include: The access network device determines, during the service transmission process through the quality of service QoS flow, that the service characteristic of the service is updated, and the updated service characteristic is used to determine the target QoS configuration of the QoS; or the access network device receives first information from a terminal device or a first core network device during service transmission, wherein the first information is used to determine a target QoS configuration of the QoS flow; The access network device updates the QoS configuration of the QoS flow according to the target QoS configuration.

2. The method according to claim 1, characterized in that The method further comprises: The access network device determines a target QoS configuration of the QoS flow according to the updated service characteristics or the first information.

3. The method according to claim 2, characterized in that The access network device determines a target QoS configuration of the QoS flow, including: The access network device determines the QoS parameters that need to be updated in the QoS configuration.

4. The method according to claim 2, characterized in that: The method further comprises: The access network device receives a plurality of QoS configurations for the QoS flow from the second core network device; The access network device determines a target QoS configuration of the QoS flow, including: The access network device determines the target QoS configuration from the multiple QoS configurations.

5. The method according to any one of claims 2 to 4, characterized in that: The method further comprises: The access network device sends second information to the terminal device and / or the first core network device, where the second information is used to indicate the target QoS configuration of the QoS flow, and the target QoS configuration indicated by the second information is determined by the access network device based on the updated service characteristics.

6. The method according to any one of claims 2 to 4, characterized in that: In a case where the first information comes from the first core network device, the method further includes: The access network device sends second information to the terminal device, where the second information is used to indicate a target QoS configuration of the QoS flow; or, In the case where the first information comes from the terminal device, the method further includes: The access network device sends second information to the first core network device, where the second information is used to indicate a target QoS configuration of the QoS flow; The target QoS configuration indicated by the second information is determined by the access network device according to the first information.

7. The method according to claim 5 or 6, characterized in that: In the case where the access network device sends the second information to the terminal device, the second information is carried in the packet data convergence protocol PDCP layer, or the radio resource control RRC signaling, or the media access control control element MAC CE of the first data packet; the first data packet is a data packet sent by the access network device to the terminal device; When the access network device sends the second information to the first core network device, the second information is carried in a general packet radio service rate protocol user plane GTP-U layer of the second data packet; The second data packet is a data packet sent by the access network device to the first core network device.

8. The method according to any one of claims 2 to 4, characterized in that: In a case where the first information comes from the first core network device, the method further includes: The access network device sends seventh information to the first core network device, where the seventh information is used to indicate that the access network device fails to update the QoS configuration of the QoS flow; or, In the case where the first information comes from the terminal device, the method further includes: The access network device sends seventh information to the terminal device, where the seventh information is used to indicate that the access network device has failed to update the QoS configuration of the QoS flow.

9. The method according to claim 8, characterized in that In the case where the access network device sends the seventh information to the first core network device, the method further includes: The access network device sends eighth information to the first core network device, where the eighth information is used to indicate the QoS configuration supported by the access network device, and the QoS configuration indicated by the eighth information is used by the first core network device to update the QoS of the QoS flow Configuration; or, In the case where the access network device sends the seventh information to the terminal device, the method further includes: The access network device sends eighth information to the terminal device, where the eighth information is used to indicate the QoS configuration supported by the access network device, and the QoS configuration indicated by the eighth information is used by the terminal device to update the QoS configuration of the QoS flow.

10. The method according to any one of claims 2 to 4, characterized in that: The method further comprises: The access network device acquires time information, where the time information indicates a time period in which the target QoS configuration is valid.

11. The method according to claim 10, characterized in that The method further comprises: When the access network device determines that the service feature of the service is updated, the access network device sends the time information to the terminal device and / or the first core network device; or, In the case where the first information comes from the terminal device, the access network device sends the time information to the first core network device; or, In the case where the first information comes from the first core network device, the access network device sends the time information to the terminal device.

12. The method according to claim 10, characterized in that The access network device acquires time information, including: The access network device determines the time information, or the access network device receives the time information from the second core network device, or the access network device receives the time information from the terminal device, or the access network device receives the time information from the first core network device.

13. The method according to any one of claims 1 to 12, characterized in that The access network device updates the QoS configuration of the QoS flow, including: The access network device performs resource adjustment, and the adjusted resources are used to transmit the service with updated service characteristics.

14. A communication method, characterized in that: include: A first communication device determines a service feature update of the service during service transmission through a quality of service QoS flow, wherein the first communication device is a terminal device or a first core network device; The first communication device sends first information to the access network device according to the updated service characteristics, where the first information is used to determine the target QoS configuration of the QoS flow.

15. The method according to claim 14, characterized in that The first communication device sends first information to the access network device according to the updated service characteristics, including: The first communication device determines a target QoS configuration of the QoS flow according to the updated service characteristics; The first communication device sends the first information according to the target QoS configuration of the QoS flow, where the first information is used to indicate the target QoS configuration of the QoS flow.

16. The method according to claim 15, characterized in that The first communication device determines the target QoS configuration, including: The first communication device determines a QoS parameter that needs to be updated in the QoS configuration of the QoS flow.

17. The method according to claim 15, characterized in that The method further comprises: The first communication device receives a plurality of QoS configurations for the QoS flow from a second core network device; The first communication device determines the target QoS configuration, including: The first communication device determines the target QoS configuration from the plurality of QoS configurations.

18. The method according to any one of claims 14 to 17, characterized in that: The method further comprises: The first communication device updates the QoS configuration of the QoS flow according to the target QoS configuration.

19. The method according to any one of claims 14 to 17, characterized in that: The first communication device receives seventh information from the access network device, where the seventh information indicates that the access network device has failed to update the QoS configuration of the QoS flow, and the access network device has updated the QoS configuration of the QoS flow based on the first information.

20. The method according to claim 19, characterized in that The method further comprises: The first communication device receives eighth information from the access network device, and the eighth information is used to indicate the access network device Supported QoS configurations.

21. The method according to claim 20, characterized in that The method further comprises: The first communication device updates the QoS configuration of the QoS flow according to the QoS configuration indicated by the eighth information.

22. The method according to any one of claims 14 to 21, characterized in that The first information is carried in the packet data convergence protocol PDCP layer or the general packet radio service rate protocol user plane GTP-U layer of the first data packet, or the radio resource control RRC signaling, or the media access control control element MAC CE, and the first data packet is a data packet sent by the first communication device to the access network device.

23. The method according to any one of claims 14 to 22, characterized in that The first communication device acquires time information, where the time information indicates a time period during which the target QoS configuration is valid.

24. The method according to claim 23, characterized in that The method further comprises: The first communication device sends the time information to the access network device.

25. A communication method, characterized in that: include: The second communication device receives second information from the access network device, where the second information is used to indicate a target QoS configuration of a quality of service QoS flow, where the QoS flow is used for service transmission between the terminal device and the first core network device, and the second communication device is the terminal device or the first core network device; The second communication device updates the QoS configuration of the QoS flow to the target QoS configuration.

26. The method according to claim 25, characterized in that The method further comprises: The second communication device acquires time information, where the time information indicates a time period during which the target QoS configuration is valid.

27. The method according to claim 26, characterized in that The method further comprises: The second communication device restores the QoS configuration of the QoS flow according to the time information.

28. The method according to any one of claims 25 to 27, characterized in that The second information is carried in the packet data convergence protocol PDCP layer or the general packet radio service rate protocol user plane GTP-U layer of the first data packet, or the radio resource control RRC signaling, or the media access control control element MAC CE, and the first data packet is a data packet received by the second communication device from the access network device.

29. A communication device, characterized in that: The communication device includes a processor; the processor is used to run a computer program or instructions so that the communication device performs the method as described in any one of claims 1-13, or so that the communication device performs the method as described in any one of claims 14-24, or so that the communication device performs the method as described in any one of claims 25-28.

30. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions or programs, which, when executed on a computer, cause the method according to any one of claims 1 to 13 to be executed, or the method according to any one of claims 14 to 24 to be executed, or the method according to any one of claims 25 to 28 to be executed.

31. A computer program product, characterized in that The computer program product includes computer instructions; when part or all of the computer instructions are executed on a computer, the method as described in any one of claims 1 to 13 is executed, or the method as described in any one of claims 14 to 24 is executed, or the method as described in any one of claims 25 to 28 is executed.

Images