Communication method and apparatus, and related network element

Abstract

The present application relates to the technical field of communications. Disclosed are a communication method and apparatus, and a related network element. The present application can take into consideration an SMF assisting a UPF in acquiring bitrate authorization information issued by an AF. In this way, on the basis of the bitrate authorization information issued by the AF, the UPF can dynamically adjust and effectively manage and control bitrate information corresponding to target application data, ensure that the bitrate information corresponding to the target application data is within the bitrate authorization information, and then send the target application data to a terminal device, such that the UPF has the capability of dynamically adjusting and effectively managing and controlling a bitrate of application data. In addition, compared with application-layer bitrate authorization authentication performed by an application server, since the bitrate authorization information is issued to the UPF by means of the assistance of the SMF, the UPF performs application-layer bitrate authorization authentication on the basis of the bitrate authorization information, thereby reducing the delay of application-layer bitrate authorization authentication.

Description

Communication method and device, and related network elements

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on February 6, 2024, with application number 202410171465.7, and priority to the Chinese patent application entitled “Communication Methods and Devices, Related Network Elements”, all contents of which are incorporated by reference into this application. Technical Field

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

[0003] When users request application data or application servers deliver application data, access network devices and core network devices play an important role in the communication system and jointly participate in the relevant processing of application data, such as scheduling, forwarding, caching or discarding application data.

[0004] However, as factors such as user demand, network congestion status, network configuration or contract information change, it may be necessary to dynamically adjust and effectively control the bit rate of application data with the joint participation of access network equipment and core network equipment. Summary of the Invention

[0005] In a first aspect, a communication method of the present application is applied to a first communication device, comprising:

[0006] Receive the bit rate authorization information from the SMF network element. The bit rate authorization information refers to the bit rate information allowed for the terminal device to access the application;

[0007] The target application data is sent to the terminal device according to the bit rate authorization information, and the bit rate information corresponding to the target application data is in the bit rate authorization information.

[0008] It can be seen that this embodiment considers that SMF assists the first communication device in obtaining the bit rate authorization information sent by AF. In this way, the first communication device can dynamically adjust and effectively control the bit rate information corresponding to the target application data according to the bit rate authorization information sent by AF, and ensure that the bit rate information corresponding to the target application data is within the bit rate authorization information, thereby realizing that the first communication device has the ability to dynamically adjust and effectively control the bit rate of the application data. At the same time, compared with the application server's authentication of the application layer bit rate authorization, since the bit rate authorization information is sent to the first communication device with the assistance of SMF, the first communication device performs authentication of the application layer bit rate authorization based on the bit rate authorization information, thereby reducing the delay of the application layer bit rate authorization authentication.

[0009] In some possible examples, the first communication device may be a UPF, a chip, or a chip component, etc. In this way, the SMF assists the UPF in obtaining the bit rate authorization information issued by the AF, so that the UPF can dynamically adjust and effectively control the bit rate information corresponding to the target application data according to the bit rate authorization information issued by the AF, and ensure that the bit rate information corresponding to the target application data is within the bit rate authorization information, thereby enabling the UPF to have the ability to dynamically adjust and effectively control the bit rate of the application data.

[0010] In some possible examples, the bitrate authorization information includes at least one of the following: the maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

[0011] It should be noted that the maximum bitrate allowed for a terminal device to access an application is typically set by the application server after the terminal device successfully registers with the application server. Thus, when the terminal device requests application data from the application server, the application server can select a bitrate from the maximum bitrate allowed for the terminal device to access the application, or a bitrate below it, and provide the application data at the selected bitrate to the terminal device.

[0012] Regarding the list of bitrates allowed for terminal devices to access applications, after the terminal device successfully registers with the application server, the application server typically sets the list of bitrates allowed for terminal devices to access applications. Thus, when the terminal device requests application data from the application server, the application server can select a bitrate from the list and provide the application data at the selected bitrate to the terminal device.

[0013] For the bit rate information allowed for terminal devices to access applications within a preset time period, the application server can set the bit rate information allowed for terminal devices to access applications (such as a maximum bit rate or a bit rate list) according to different time periods. For example, in a time period with a small number of users accessing the application (such as at night), since the number of terminal devices accessing the application server during this period is usually small, the occupancy rate of bandwidth resources is low or the congestion rate presented by the network status is low, etc., the application server can set the maximum bit rate allowed for terminal devices to access applications during this period to be larger or the bit rates available for selection in the bit rate list to be more. However, in a time period with a large number of users accessing the application (such as during the day), since the number of terminal devices accessing the application server during this period is usually large, the occupancy rate of bandwidth resources is high or the congestion rate presented by the network status is high, etc., the application server can set the maximum bit rate allowed for terminal devices to access applications during this period to be smaller or the bit rates available for selection in the bit rate list to be fewer. In this way, the bit rate information allowed for terminal devices to access applications can be flexibly set according to the time period.

[0014] Regarding the bitrate information allowed for terminal devices to access applications within a preset location area, the application server can set the bitrate information allowed for terminal devices to access applications (such as a maximum bitrate or a bitrate list) based on the location area. For example, in densely populated locations (such as business districts), since the number of terminal devices accessing application servers in these locations is generally large, resulting in a higher bandwidth resource utilization rate or a higher network congestion rate, the application server can set a smaller maximum bitrate allowed for terminal devices to access applications within these location areas or a smaller number of available bitrates in the bitrate list.

[0015] In some possible examples, the code rate authorization information is carried by an N4 session creation request message or an N4 session modification request message.

[0016] It should be noted that the N4 session creation process is used to create the initial N4 session context for the PDU session in the UPF. The SMF allocates a new N4 session ID and provides it to the UPF, and sends an N4 session creation request message to the UPF. Therefore, during the N4 session creation process, the SMF can send rate authorization information to the UPF via the N4 session creation request message so that the UPF can obtain the rate authorization information.

[0017] In addition, the N4 Session Modification procedure is used to update the N4 Session Context of an existing PDU Session at the UPF. It is performed between the SMF and the UPF when PDU Session-related parameters need to be modified. The SMF sends an N4 Session Modification Request message to the UPF. Therefore, during the N4 Session creation process, the SMF can send the rate authorization information to the UPF via the N4 Session Modification Request message so that the UPF can obtain the rate authorization information.

[0018] In some possible examples, before sending the target application data bit rate authorization information to the terminal device according to the bit rate authorization information, the method further includes: obtaining application data request information of the terminal device.

[0019] It should be noted that after the UPF obtains the bitrate authorization information, the terminal device can request the application data content it needs, such as videos, images, music, or other media resources. The terminal device's application data request can be generated based on user operations or internal application logic to meet user needs and obtain the required application data. In this way, the UPF can obtain the terminal device's application data request information.

[0020] In some possible examples, obtaining application data request information of a terminal device includes: receiving application data request information of the terminal device from an access network device.

[0021] It should be noted that the terminal device can request application data through application layer messages, and forward the application data request information of the terminal device to the UPF via RAN, so that the UPF obtains the application data request information of the terminal device. Finally, the UPF processes the application data request information of the terminal device according to the bit rate authorization information and sends the application data to the terminal device.

[0022] In some possible examples, obtaining application data request information of a terminal device includes: receiving application data request information from an SMF.

[0023] It should be noted that the terminal device can request application data through the control plane message, and send the application data request information of the terminal device to the UPF through the AMF and SMF, so that the UPF obtains the application data request information of the terminal device. Finally, the UPF processes the application data request information of the terminal device according to the bit rate authorization information and sends the application data to the terminal device.

[0024] In some possible examples, the application data request information includes target application data requested by the terminal device; and sending the target application data to the terminal device according to the bit rate authorization information includes:

[0025] In response to the application data request information, determining the bit rate information corresponding to the target application data in the bit rate authorization information;

[0026] If the target application data is cached locally or has been subscribed to, the target application data is sent to the terminal device;

[0027] If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to the subscription request message, which is used to request the application server to subscribe to the target application data.

[0028] It should be noted that if the application data request information includes the target application data requested by the terminal device, the UPF can determine the bit rate information corresponding to the target application data in the bit rate authorization information in response to the application data request information. That is to say, when the user does not specify the bit rate corresponding to the application data, the UPF can select a bit rate in the bit rate authorization information. In this way, the UPF can authenticate the application layer bit rate authorization of the target application data requested by the terminal device based on the bit rate authorization information, thereby reducing the delay of the application layer bit rate authorization authentication. At the same time, the UPF can determine whether it is necessary to subscribe to the application data from the application server based on the local cache situation or historical application data subscription information, and provide the target application data to the terminal device, so as to avoid the application server directly sending the target application data to the terminal device to reduce the delay required for the overall transmission of the target application data, and reduce the export bandwidth pressure of the application server when the terminal device requests the target application data (especially the target application data with a higher bit rate) from the application server.

[0029] In some possible examples, the application data request information includes target application data requested by the terminal device and bit rate information requested by the terminal device;

[0030] Send target application data to the terminal device based on the bitrate authorization information, including:

[0031] If the bitrate information requested by the terminal device is in the bitrate authorization information, the bitrate information requested by the terminal device is used as the bitrate information corresponding to the target application data;

[0032] If the bit rate information requested by the terminal device is not in the bit rate authorization information, the bit rate information corresponding to the target application data is determined in the bit rate authorization information;

[0033] If the target application data is cached locally or has been subscribed to, the target application data is sent to the terminal device;

[0034] If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to the subscription request message, which is used to request the application server to subscribe to the target application data.

[0035] It should be noted that if the application data request information includes the target application data requested by the terminal device and the bitrate information requested by the terminal device, the UPF needs to determine whether the bitrate information requested by the terminal device can be authorized based on the bitrate authorization information. When the bitrate information requested by the terminal device is within the bitrate authorization information, this indicates that the bitrate information requested by the terminal device can be authorized, and the bitrate information requested by the terminal device is used as the bitrate information actually corresponding to the target application data. When the bitrate information requested by the terminal device is not within the bitrate authorization information, this indicates that the bitrate information requested by the terminal device has not been authorized, and the UPF needs to determine the bitrate information actually corresponding to the target application data within the bitrate authorization information. At the same time, the UPF can determine whether it is necessary to subscribe to application data from the application server based on the local cache status or historical application data subscription information, and provide the target application data to the terminal device, avoiding the application server directly sending the target application data to the terminal device to reduce the delay required for the overall transmission of the target application data, thereby reducing the application server's egress bandwidth pressure when the terminal device requests the target application data from the application server (especially when requesting target application data with a higher bitrate).

[0036] In some possible examples, sending target application data to the terminal device according to the subscription request message includes:

[0037] Send a subscription request message to the application server;

[0038] receiving target application data from an application server;

[0039] Send target application data to the terminal device.

[0040] It should be noted that the UPF can request the target application data by sending a subscription request message to the application server. In this way, the application server obtains the application data that the UPF needs to subscribe to and the bit rate information corresponding to the application data through the subscription request message, and sends the target application data to the UPF.

[0041] In some possible examples, receiving target application data from an application server includes:

[0042] Receive a subscription response message from the application server, where the subscription response message includes a bitrate identifier ID;

[0043] Record and maintain the correspondence between target application data and bitrate ID;

[0044] receiving target application data from the application server according to the bitrate ID;

[0045] It should be noted that before the application server sends the target application data, the application server can send the bitrate ID to the UPF so that the UPF can record and maintain the correspondence between the target application data and the bitrate ID and use it as a local cache. The application server can then send the target application data based on the bitrate ID, and the UPF can receive the target application data based on the bitrate ID.

[0046] In some possible examples, before sending the target application data to the terminal device, the method further includes:

[0047] Send the bitrate information corresponding to the target application data to the terminal device.

[0048] It should be noted that when the terminal device does not request the bitrate information corresponding to the target application data, the UPF can determine the bitrate information corresponding to the target application data based on the bitrate authorization information and then inform the terminal device. When the terminal device requests the bitrate information corresponding to the target data, since the actual bitrate information determined by the UPF based on the bitrate authorization information may be different from the bitrate information requested by the terminal device, the UFP needs to inform the terminal device of the actual bitrate information in advance before the UPF sends the application data to the terminal device.

[0049] A second aspect is a communication method of the present application, applied to a second communication device, comprising:

[0050] In response to a PDU session creation request or a PDU session modification request, obtain the bitrate authorization information issued by the application function network element AF. The bitrate authorization information refers to the bitrate information allowed for the terminal device to access the application;

[0051] Send bitrate authorization information to UPF.

[0052] It should be noted that in response to the PDU session creation request or the PDU session modification request, it can be understood that after the second communication device receives the PDU session creation / modification request, the second communication device may check the local configuration information or contract information. Among them, the local configuration information or contract information may include indication information for indicating that the second communication device obtains the bit rate authorization information after receiving the PDU session creation request or the PDU session modification request. For example, these indication information may indicate that the second communication device needs to obtain bit rate authorization information for a specific slice or a specific data network name (DNN) user. In this way, the second communication device can trigger the process of obtaining the bit rate authorization information issued by the AF based on the local configuration information or contract information.

[0053] It can be seen that the second communication device can obtain the bit rate authorization information issued by the AF in the process of PDU session creation request or PDU session modification request, and then send the bit rate authorization information to the UPF, thereby assisting the UPF to obtain the bit rate authorization information in the process of PDU session creation request or PDU session modification request.

[0054] In some possible examples, the second communication device may be an SMF, a chip, or a chip component, etc. In this way, the SMF may obtain the bit rate authorization information issued by the AF during the process of the PDU session creation request or the PDU session modification request, and then send the bit rate authorization information to the UPF, thereby assisting the UPF in obtaining the bit rate authorization information during the process of the PDU session creation request or the PDU session modification request.

[0055] In some possible examples, the bit rate authorization information includes at least one of the following:

[0056] The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

[0057] It should be noted that the maximum bitrate allowed for a terminal device to access an application is typically set by the application server after the terminal device successfully registers with the application server. Thus, when the terminal device requests application data from the application server, the application server can select a bitrate from the maximum bitrate allowed for the terminal device to access the application, or a bitrate below it, and provide the application data at the selected bitrate to the terminal device.

[0058] Regarding the list of bitrates allowed for terminal devices to access applications, after the terminal device successfully registers with the application server, the application server typically sets the list of bitrates allowed for terminal devices to access applications. Thus, when the terminal device requests application data from the application server, the application server can select a bitrate from the list and provide the application data at the selected bitrate to the terminal device.

[0059] For the bit rate information allowed for terminal devices to access applications within a preset time period, the application server can set the bit rate information allowed for terminal devices to access applications (such as a maximum bit rate or a bit rate list) according to different time periods. For example, in a time period with a small number of users accessing the application (such as at night), since the number of terminal devices accessing the application server during this period is usually small, the occupancy rate of bandwidth resources is low or the congestion rate presented by the network status is low, etc., the application server can set the maximum bit rate allowed for terminal devices to access applications during this period to be larger or the bit rates available for selection in the bit rate list to be more. However, in a time period with a large number of users accessing the application (such as during the day), since the number of terminal devices accessing the application server during this period is usually large, the occupancy rate of bandwidth resources is high or the congestion rate presented by the network status is high, etc., the application server can set the maximum bit rate allowed for terminal devices to access applications during this period to be smaller or the bit rates available for selection in the bit rate list to be fewer. In this way, the bit rate information allowed for terminal devices to access applications can be flexibly set according to the time period.

[0060] Regarding the bitrate information allowed for terminal devices to access applications within a preset location area, the application server can set the bitrate information allowed for terminal devices to access applications (such as a maximum bitrate or a bitrate list) based on the location area. For example, in densely populated locations (such as business districts), since the number of terminal devices accessing application servers in these locations is generally large, resulting in a higher bandwidth resource utilization rate or a higher network congestion rate, the application server can set a smaller maximum bitrate allowed for terminal devices to access applications within these location areas or a smaller number of available bitrates in the bitrate list.

[0061] In some possible examples, obtaining the bitrate authorization information sent by the AF includes:

[0062] Send a first request message to the NEF, where the first request message is used to request the NEF to query the UDR for the bit rate authorization information issued by the AF;

[0063] A first response message is received from the NEF, where the first response message includes bit rate authorization information.

[0064] It should be noted that SMF can request the bit rate authorization information issued by AF from NEF, NEF queries the authorization information issued by AF from UDR, UDR returns the authorization information to NEF, and NEF returns the authorization information to SMF, thereby obtaining the bit rate authorization information issued by AF.

[0065] In some possible examples, obtaining the bitrate authorization information sent by the AF includes:

[0066] Send a second request message to the PCF, where the second request message is used to request the PCF to query the UDR for the bit rate authorization information issued by the AF;

[0067] A second response message is received from the PCF, where the second response message includes bit rate authorization information.

[0068] It should be noted that SMF can request PDU session policy from PCF, PCF can determine the need to obtain the rate authorization information issued by AF based on local configuration information or contract information, PCF queries UDR for the rate authorization information issued by AF, UDR returns the rate authorization information to PCF, and PCF sends the rate authorization information to SMF. Among them, local configuration information or contract information may include instruction information for instructing PCF to obtain rate authorization information after receiving the PDU session policy request from SMF. For example, these instruction information can indicate that PCF needs to obtain rate authorization information for a specific slice or a specific DNN user.

[0069] In some possible examples, before obtaining the bit rate authorization information sent by the AF, the method further includes:

[0070] Receive an SM context request message or an SM context update request message from the AMF, where the SM context request message or the SM context update request message contains application data request information of the terminal device.

[0071] It should be noted that the terminal device can request application data through the control plane message, and the application data request information of the terminal device is sent to the UPF via the AMF and SMF. Based on this, during the PDU session creation process, the terminal device sends a PDU session creation request message to the AMF. The PDU session creation request message contains the application data request information of the terminal device. Then the AMF sends an SM context request message to the SMF. The SM context request message contains the application data request information, so that the SMF obtains the application data request information of the terminal device.

[0072] During the PDU session modification process, the terminal device sends a PDU session modification request message to the AMF. The PDU session modification request message includes the application data request information of the terminal device. Then the AMF sends an SM context update request message to the SMF. The SM context update request message includes the application data request information, so that the SMF obtains the application data request information of the terminal device.

[0073] In some possible examples, sending the bitrate authorization information to the UPF includes:

[0074] If the SM context request message includes application data request information, an N4 session creation request message is sent to the UPF, where the N4 session creation request message includes application data request information; or

[0075] If the SM context update request message includes application data request information, an N4 session modification request message is sent to the UPF, and the N4 session modification request message includes application data request information.

[0076] It should be noted that during the PDU session creation process, the terminal device sends a PDU session creation request message to the AMF. The PDU session creation request message contains the application data request information of the terminal device. Then the AMF sends an SM context request message to the SMF. The SM context request message contains the application data request information. Finally, the SMF sends an N4 session creation request message to the UPF. The N4 session creation request message contains the application data request information, thereby enabling the SMF to send the application data request information to the UPF.

[0077] During the PDU session modification process, the terminal device sends a PDU session modification request message to AMF, which includes the application data request information of the terminal device. Then, AMF sends an SM context update request message to SMF, which includes the application data request information. Finally, SMF sends an N4 session modification request message to UPF, which includes the application data request information, thereby enabling SMF to send the application data request information to UPF.

[0078] In some possible examples, the data request information includes target application data requested by the terminal device and / or bit rate information requested by the terminal device.

[0079] It should be noted that the terminal device can request the content of the target application data it needs, such as requesting videos, images, music or other media resources. Among them, the target application data request of the terminal device can be generated based on the user's operation or the logic within the application to meet the user's needs and obtain the required target application data. In addition, when requesting the target application data, the terminal device may request the bit rate information it needs. For example, when a user chooses to play a video in an application, the user may select the bit rate of the video to be 1080kbps, or adjust the bit rate of the video from 720kbps to 1080kbps. At this time, the terminal device will request 1080kbps from the application server.

[0080] A third aspect is a communication method of the present application, applied to a first communication device, comprising:

[0081] Receive network congestion information or bandwidth usage information from access network devices, or receive network performance analysis information from NWDAF;

[0082] The target application data is sent to the terminal device based on network congestion information, bandwidth usage information or network performance analysis information. The bit rate information corresponding to the target application data is in the bit rate authorization information. The bit rate authorization information refers to the bit rate information allowed for the terminal device to access the application.

[0083] It should be noted that network congestion information can refer to data used to monitor and manage network congestion during communications between the RAN and terminal devices. Bandwidth usage information can refer to data used to record and manage network resource usage during communications between the RAN and terminal devices. Network performance analysis information refers to data and events generated during network communications that can be used to evaluate and analyze network performance and quality. Network performance analysis information may include bandwidth utilization, transmission latency, packet loss rate, data volume, etc.

[0084] It can be seen that the first communication device can adjust the bit rate information corresponding to the target application data based on network congestion information, bandwidth usage information or network performance analysis information, and the adjusted bit rate information is in the bit rate authorization information, and then the target application data is sent to the terminal device, thereby achieving bit rate adjustment.

[0085] In some possible examples, the first communication device may be a UPF, a chip, or a chip component. In this way, the UPF may adjust the bitrate information corresponding to the target application data based on network congestion information, bandwidth usage information, or network performance analysis information, and the adjusted bitrate information is included in the bitrate authorization information. The target application data is then sent to the terminal device, thereby adjusting the bitrate.

[0086] In some possible examples, the bit rate authorization information includes at least one of the following:

[0087] The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

[0088] It should be noted that the maximum bitrate allowed for a terminal device to access an application is typically set by the application server after the terminal device successfully registers with the application server. Thus, when the terminal device requests application data from the application server, the application server can select a bitrate from the maximum bitrate allowed for the terminal device to access the application, or a bitrate below it, and provide the application data at the selected bitrate to the terminal device.

[0089] Regarding the list of bitrates allowed for terminal devices to access applications, after the terminal device successfully registers with the application server, the application server typically sets the list of bitrates allowed for terminal devices to access applications. Thus, when the terminal device requests application data from the application server, the application server can select a bitrate from the list and provide the application data at the selected bitrate to the terminal device.

[0090] For the bit rate information allowed for terminal devices to access applications within a preset time period, the application server can set the bit rate information allowed for terminal devices to access applications (such as a maximum bit rate or a bit rate list) according to different time periods. For example, in a time period with a small number of users accessing the application (such as at night), since the number of terminal devices accessing the application server during this period is usually small, the occupancy rate of bandwidth resources is low or the congestion rate presented by the network status is low, etc., the application server can set the maximum bit rate allowed for terminal devices to access applications during this period to be larger or the bit rates available for selection in the bit rate list to be more. However, in a time period with a large number of users accessing the application (such as during the day), since the number of terminal devices accessing the application server during this period is usually large, the occupancy rate of bandwidth resources is high or the congestion rate presented by the network status is high, etc., the application server can set the maximum bit rate allowed for terminal devices to access applications during this period to be smaller or the bit rates available for selection in the bit rate list to be fewer. In this way, the bit rate information allowed for terminal devices to access applications can be flexibly set according to the time period.

[0091] Regarding the bitrate information allowed for terminal devices to access applications within a preset location area, the application server can set the bitrate information allowed for terminal devices to access applications (such as a maximum bitrate or a bitrate list) based on the location area. For example, in densely populated locations (such as business districts), since the number of terminal devices accessing application servers in these locations is generally large, resulting in a higher bandwidth resource utilization rate or a higher network congestion rate, the application server can set a smaller maximum bitrate allowed for terminal devices to access applications within these location areas or a smaller number of available bitrates in the bitrate list.

[0092] In some possible examples, sending target application data to a terminal device based on network congestion information, bandwidth usage information, or network performance analysis information includes:

[0093] Determining the bitrate information corresponding to the target application data in the bitrate authorization information based on network congestion information, bandwidth usage information, or network performance analysis information;

[0094] If the target application data is cached locally or has been subscribed to, the target application data is sent to the terminal device;

[0095] If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to the subscription request message, which is used to request the application server to subscribe to the target application data.

[0096] It should be noted that the UPF can adjust the bitrate information corresponding to the target application data based on network congestion information, bandwidth usage information, or network performance analysis information, and the adjusted bitrate information is within the bitrate authorization information. At the same time, the UPF can determine whether it is necessary to subscribe to the target application data from the application server based on the local cache status or historical application data subscription information, and provide the target application data to the terminal device, thereby avoiding the application server directly sending the target application data to the terminal device to reduce the delay required for the overall transmission of the target application data, and reducing the export bandwidth pressure of the application server when the terminal device requests the target application data from the application server (especially the target application data with a higher bitrate).

[0097] In some possible examples, sending target application data to the terminal device according to the subscription request message includes:

[0098] Send a subscription request message to the application server;

[0099] receiving target application data from an application server;

[0100] Send target application data to the terminal device.

[0101] It should be noted that the UPF can request the target application data by sending a subscription request message to the application server. In this way, the application server obtains the application data that the UPF needs to subscribe to and the bit rate information corresponding to the application data through the subscription request message, and sends the target application data to the UPF.

[0102] In some possible examples, receiving target application data from an application server includes:

[0103] Receive a bitrate identifier ID from an application server;

[0104] Record and maintain the correspondence between target application data and bitrate ID;

[0105] receiving target application data from the application server according to the bitrate ID;

[0106] It should be noted that before the application server sends the target application data, the application server can send the bitrate ID to the UPF so that the UPF can record and maintain the correspondence between the target application data and the bitrate ID and use it as a local cache. The application server can then send the target application data based on the bitrate ID, and the UPF can receive the target application data based on the bitrate ID.

[0107] In some possible examples, before sending the target application data to the terminal device, the method further includes:

[0108] Send the bitrate information corresponding to the target application data to the terminal device.

[0109] It should be noted that when the terminal device does not request the bitrate information corresponding to the target application data, the UPF can determine the bitrate information corresponding to the target application data based on the bitrate authorization information and then inform the terminal device. When the terminal device requests the bitrate information corresponding to the target data, since the actual bitrate information determined by the UPF based on the bitrate authorization information may be different from the bitrate information requested by the terminal device, the UFP needs to inform the terminal device of the actual bitrate information in advance before the UPF sends the application data to the terminal device.

[0110] In some possible examples, before sending the target application data to the terminal device based on the network congestion information, the bandwidth usage information, or the network performance analysis information, the method further includes:

[0111] Receive bit rate authorization information from the SMF network element.

[0112] In this way, SMF assists UPF in obtaining the bit rate authorization information sent by AF, so that UPF can dynamically adjust and effectively control the bit rate information corresponding to the target application data according to the bit rate authorization information sent by AF, and ensure that the bit rate information corresponding to the target application data is within the bit rate authorization information, thereby enabling UPF to have the ability to dynamically adjust and effectively control the bit rate of application data.

[0113] In some possible examples, the code rate authorization information is carried by an N4 session creation request message or an N4 session modification request message.

[0114] It should be noted that the N4 session creation process is used to create the initial N4 session context for the PDU session in the UPF. The SMF allocates a new N4 session ID and provides it to the UPF, and sends an N4 session creation request message to the UPF. Therefore, during the N4 session creation process, the SMF can send rate authorization information to the UPF via the N4 session creation request message so that the UPF can obtain the rate authorization information.

[0115] In addition, the N4 Session Modification procedure is used to update the N4 Session Context of an existing PDU Session at the UPF. It is performed between the SMF and the UPF when PDU Session-related parameters need to be modified. The SMF sends an N4 Session Modification Request message to the UPF. Therefore, during the N4 Session creation process, the SMF can send the rate authorization information to the UPF via the N4 Session Modification Request message so that the UPF can obtain the rate authorization information.

[0116] A fourth aspect is a communication device of the present application, comprising:

[0117] A receiving unit is configured to receive bitrate authorization information from the SMF, wherein the bitrate authorization information refers to the bitrate information allowed for the terminal device to access the application;

[0118] The sending unit is used to send target application data to the terminal device according to the bit rate authorization information, and the bit rate information corresponding to the target application data is in the bit rate authorization information.

[0119] It should be noted that the beneficial effects brought about by the technical solution of the fourth aspect can be referred to the technical effects brought about by the technical solution of the first aspect, and will not be repeated here.

[0120] A fifth aspect is a communication device of the present application, comprising:

[0121] An acquiring unit, configured to acquire the bitrate authorization information issued by the AF in response to a PDU session creation request or a PDU session modification request, where the bitrate authorization information refers to the bitrate information allowed for the terminal device to access the application;

[0122] The sending unit is used to send the bit rate authorization information to the UPF.

[0123] It should be noted that the beneficial effects brought about by the technical solution of the fifth aspect can be referred to the technical effects brought about by the technical solution of the second aspect, and will not be repeated here.

[0124] A sixth aspect is a communication device of the present application, comprising:

[0125] A receiving unit, configured to receive network congestion information or bandwidth usage information from an access network device, or network performance analysis information from an NWDAF;

[0126] The sending unit is used to send target application data to the terminal device based on network congestion information, bandwidth usage information or network performance analysis information. The bit rate information corresponding to the target application data is in the bit rate authorization information. The bit rate authorization information refers to the bit rate information allowed for the terminal device to access the application.

[0127] It should be noted that the beneficial effects brought about by the technical solution of the sixth aspect can be referred to the technical effects brought about by the technical solution of the third aspect, and will not be repeated here.

[0128] The seventh aspect is a UPF of the present application, comprising a processor, a memory, and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to implement the steps in the method designed in the first or third aspect above.

[0129] It should be noted that the beneficial effects brought about by the technical solution of the seventh aspect can be referred to the technical effects brought about by the technical solution of the first aspect or the third aspect, and will not be repeated here.

[0130] The eighth aspect is an SMF of the present application, comprising a processor, a memory, and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to implement the steps in the method designed in the second aspect above.

[0131] It should be noted that the beneficial effects brought about by the technical solution of the eighth aspect can be referred to the technical effects brought about by the technical solution of the second aspect, and will not be repeated here.

[0132] The ninth aspect is a chip of the present application, comprising a processor, wherein the processor executes the steps in the method designed in the first aspect, second aspect or third aspect above.

[0133] Optionally, the chip further includes a communication interface, and the processor executes the sending step and / or receiving step in the method designed in the above-mentioned first aspect, second aspect or third aspect through the communication interface.

[0134] The tenth aspect is a chip module of the present application, comprising a chip, wherein the chip comprises a processor, wherein the processor executes the steps in the method designed in the above-mentioned first aspect, second aspect or third aspect.

[0135] Optionally, the chip module further includes a transceiver component, and the processor executes the sending step and / or receiving step in the method designed in the above-mentioned first aspect, second aspect or third aspect through the transceiver component.

[0136] In an eleventh aspect, a computer-readable storage medium of the present application is provided, wherein the computer program or instructions are stored therein, and when the computer program or instructions are executed, the steps of the method according to the first, second, or third aspects are implemented. For example, the computer program or instructions are executed by a processor.

[0137] A twelfth aspect is a computer program product of the present application, comprising a computer program or instructions, wherein when the computer program or instructions are executed, the steps of the method according to the first, second, or third aspect are performed. For example, the computer program or instructions are executed by a processor.

[0138] It should be noted that the beneficial effects brought about by the technical solutions of aspects 9 to 12 can be referred to the technical effects brought about by the technical solution of aspect 1, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0139] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application;

[0140] FIG2 is a schematic diagram of the architecture of a communication system for XR services according to an embodiment of the present application;

[0141] FIG3 is a schematic diagram of a MoQ protocol architecture according to an embodiment of the present application;

[0142] FIG4 is a flow chart of a method for transmitting bit rate authorization information according to an embodiment of the present application;

[0143] FIG5 is a flow chart of a method for subscribing to application data according to an embodiment of the present application;

[0144] FIG6 is a flow chart of a method for transmitting application data according to an embodiment of the present application;

[0145] FIG7 is a flow chart of another method for transmitting application data according to an embodiment of the present application;

[0146] FIG8 is a flow chart of a method for transmitting application data request information according to an embodiment of the present application;

[0147] 9 is a flowchart of another method for transmitting application data request information according to an embodiment of the present application;

[0148] FIG10 is a flow chart of another method for transmitting application data according to an embodiment of the present application;

[0149] FIG11 is a flow chart of a communication method according to an embodiment of the present application;

[0150] FIG12 is a block diagram of functional units of a communication device according to an embodiment of the present application;

[0151] FIG13 is a block diagram of functional units of another communication device according to an embodiment of the present application;

[0152] FIG14 is a block diagram of functional units of another communication device according to an embodiment of the present application;

[0153] FIG15 is a schematic structural diagram of a UPF according to an embodiment of the present application;

[0154] FIG16 is a schematic structural diagram of an SMF according to an embodiment of the present application;

[0155] FIG17 is a schematic structural diagram of another UPF according to an embodiment of the present application. DETAILED DESCRIPTION

[0156] It should be understood that the terms "first," "second," and the like in the embodiments of the present application are used to distinguish between different objects, rather than to describe a specific order. In addition, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, software, product, or device comprising a series of steps or units is not limited to the listed steps or units, but may also include steps or units not listed, or may also include other steps or units inherent to these processes, methods, products, or devices.

[0157] The term "embodiment" as used in the embodiments of this application means that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various locations in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive with other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0158] In the embodiments of the present application, "at least one" or "at least one item" refers to one or more, and "a plurality" refers to two or more.

[0159] The term "and / or" in the embodiments of the present application describes the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural. The character " / " can indicate that the associated objects are in an "or" relationship. In addition, the character " / " can represent a division sign, such as A / B, which means A divided by B.

[0160] In the embodiments of the present application, "at least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or multiple items. For example, at least one of a, b, or c can represent the following seven situations: a, b, c, a and b, a and c, b and c, a, b, and c. Each of a, b, and c can be an element or a set containing one or more elements.

[0161] In the embodiments of the present application, the terms "of," "corresponding," "relevant," "corresponding," "associated," "related," and "mapped" may sometimes be used interchangeably. It should be noted that when no distinction is emphasized, the concepts or meanings to be expressed are consistent.

[0162] The “network” in the embodiments of the present application can be expressed as the same concept as the “system”, and the communication system is the communication network.

[0163] The "connection" in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices, and is not specifically limited to this.

[0164] The following is a detailed introduction to the relevant contents involved in the technical solutions of the embodiments of this application.

[0165] The communication system of this embodiment is described in detail below.

[0166] The technical solutions of the embodiments of the present application can be applied to various wireless communication systems, such as: long term evolution (LTE) system, advanced long term evolution (LTE-A) system, new radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, non-terrestrial communication network (NTN) system, universal mobile telecommunication system (UMTS), 6th generation (6G) communication system or other future communication systems.

[0167] It should be noted that the number of user connections supported by traditional communication systems is limited and easy to implement. With the development of communication technology, the communication system of the present application can not only support traditional communication systems, but also support device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine type communication (MTC), vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication, narrowband Internet of Things (NB-IoT) communication, etc. Therefore, the technical solutions of the embodiments of the present application can also be applied to the above-mentioned communication systems.

[0168] For example, the embodiments of the present application can be applied to beamforming (beamforming), carrier aggregation (CA), dual connectivity (DC) or standalone (SA) deployment scenarios, etc.

[0169] As another example, embodiments of the present application can be applied to communication scenarios using unlicensed spectrum. In embodiments of the present application, unlicensed spectrum can also be considered shared spectrum. Alternatively, embodiments of the present application can also be applied to licensed spectrum. Licensed spectrum can also be considered unshared spectrum.

[0170] The terminal device, access network device and core network device mentioned in this embodiment are described below.

[0171] A terminal device can be a device with transceiver functions and can also be referred to as a terminal, user equipment (UE), remote UE, relay UE, access terminal device, user unit, user station, mobile station, mobile station, remote station, mobile device, user terminal device, intelligent terminal device, wireless communication device, user agent, or user device. It should be noted that a relay device is a terminal device that can provide relay forwarding services for other terminal devices (including remote terminal devices).

[0172] For example, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in unmanned autonomous driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0173] For another example, the terminal device can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system (such as an NR communication system, a 6G communication system), or a terminal device in a future evolved public land mobile communication network (PLMN), etc., without specific limitation.

[0174] In addition, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; can be deployed on the water (such as ships, etc.); can be deployed in the air (such as airplanes, balloons and satellites, etc.). The terminal device may include a device with wireless communication functions, such as a chip system, a chip, or a chip module. For example, the chip system may include a chip and may also include other discrete devices. The terminal device may be a chip, a chip module, a device, a unit, etc., and there is no specific limitation on this.

[0175] To meet the challenges of wireless broadband technology and maintain the leading edge of 3GPP networks, the 3GPP standards group has developed a next-generation mobile communications network architecture, known as the 5G network architecture. This architecture not only supports 3GPP-defined wireless technologies (such as LTE) accessing the 5G core network (5GC), but also supports non-3GPP access technologies accessing the 5GC through the non-3GPP interworking function (N3IWF), the trusted non-3GPP gateway function (TNGF), the trusted WLAN interworking function (TWIF), or the next-generation packet data gateway (NG-PDG). The core network functions can be divided into user plane function (UPF) and control plane function (CPF). The UPF is primarily responsible for packet forwarding, quality of service (QoS) control, and billing information statistics. CPF is mainly responsible for user registration and authentication, mobility management, and sending data packet forwarding policies and QoS control policies to UPF. It can be further divided into access and mobility management function (AMF) and session management function (SMF).

[0176] The access network equipment can be called a radio access network (RAN). RAN can be a network composed of multiple 5G-RAN nodes, which implements wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management functions. 5G-RAN is connected to the UPF through the user plane interface N3 to transmit data from terminal devices; 5G-RAN establishes a control plane signaling connection with the AMF through the control plane interface N2 to implement functions such as radio access bearer control. RAN can be any device with wireless transceiver functions, including but not limited to 5G base stations (5G node base, gNB), evolved base stations (eNB), wireless access points (WiFi AP), world interoperability for microwave access base stations (WiMAX BS), transmission receiving points (TRP), wireless relay nodes, wireless backhaul nodes, etc.

[0177] In addition, the access network device may refer to a device used to communicate with a terminal device. For example, the access network device may be a base transceiver station (BTS) in a global system of mobile communication (GSM) system or a code division multiple access (CDMA) system, a node B (NB) in a wideband code division multiple access (WCDMA) system, an evolutionary node base (eNB) in an LTE system, a wireless controller in a cloud radio access network (CRAN) scenario, or a relay station, an access point, an in-vehicle device, a wearable device, an access network device in a future 5G network, or an access network device in a future evolved PLMN network, etc., and the embodiments of the present application are not limited thereto.

[0178] In NR, the functions of the access network equipment are divided into two parts, called centralized unit (CU)-distributed unit (DU) separation. From the perspective of the protocol stack, the CU includes the RRC layer and PDCP layer of the LTE base station, and the DU includes the radio link control (RLC) layer, media access control (MAC) layer and physical (PHY) layer of the LTE base station. In ordinary 5G base station deployments, the CU and DU can be physically connected through optical fiber, and logically there is a specially defined F1 interface for communication between the CU and the DU. From a functional perspective, the CU is mainly responsible for wireless resource control and configuration, cross-cell mobility management, bearer management, etc. The DU is mainly responsible for scheduling, physical signal generation and transmission.

[0179] Optionally, the access network device can be a macro base station, a micro base station, a pico base station, a small station, a relay station, a balloon station, etc.

[0180] Core network equipment may include network elements that provide various functions. "Network element" may also be referred to as an entity, device, apparatus, or module, without specific limitation. Furthermore, for ease of understanding and explanation, the term "network element" is omitted in some descriptions. For example, a network exposure function (NEF) network element is referred to as NEF. In this case, "NEF" should be understood as either an NEF network element or an NEF entity. The following descriptions of identical or similar situations are omitted.

[0181] For example, the core network equipment may include a mobility management entity (MME), a broadcast multicast service center (BMSC), etc., or may include corresponding functional entities in the 5G system, such as a core network control plane (CP) or a user plane (UP) network function, etc. The core network control plane can also be understood as a core network control plane function (CPF) entity.

[0182] The following describes the various network elements included in the core network equipment.

[0183] The SMF is responsible for the control plane functions of terminal device session management, including the selection and control of user plane functions (UPF), Internet protocol (IP) address allocation, session QoS management, acquisition policy and charging control (PCC) policy, etc.

[0184] UPF can serve as the anchor point for protocol data unit (PDU) session connections, responsible for data packet filtering, data transmission / forwarding, rate control, generation of billing information, etc. for terminal devices, and provides connection to the data network (DN).

[0185] The policy control function (PCF) can provide configuration policy information for terminal devices and provide policy information for network control plane elements (such as SMF) to manage and control terminal devices; it can also generate terminal device access policies and QoS flow control policies.

[0186] The AF can interact with network elements in the core network to provide some services. For example, the AF interacts with the PCF to control service policies, interacts with the NEF to obtain some network capability information or provide some application information to the network, and provides some data network access point information to the PCF to generate routing information for corresponding data services.

[0187] NEF can be responsible for providing some network-related status information to application services.

[0188] The Authentication Server Function (AUSF) can implement 3GPP and non-3GPP access authentication.

[0189] Unified Data Management (UDM), unified data management functions, 3GPP AKA authentication, user identification, access authorization, registration, mobility, subscription, SMS management, etc.

[0190] The network slice selection function (NSSF) can determine the network slice instance that the terminal device is allowed to access based on the slice selection auxiliary information, contract information, etc. of the terminal device.

[0191] The network repository function (NRF) may be a new function that provides registration and discovery capabilities, enabling network functions (NFs) to discover each other and communicate through API interfaces.

[0192] Unified data management (UDM) is responsible for the management of user identification, contract data, authentication data, and user service network element registration management.

[0193] The unified data repository (UDR) can be used by the UDM to store subscription data or read subscription data and by the PCF to store policy data or read policy data.

[0194] The network data analytics function (NWDAF) can provide network analysis services based on the request data of network services.

[0195] The network slice specific authentication and authorization function (NSSAAF) can be used to provide authentication and authorization for specific network slices.

[0196] It should be noted that the terminal device is connected to the access network device wirelessly, and the access network device is connected to the core network device wirelessly or wired. The access network device and the core network device can be independent and different physical devices, or the core network device functions and the access network device logical functions can be integrated into the same physical device, or a single physical device can integrate some core network device functions and some access network device functions.

[0197] For example, Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application. The naming of each network element included in Figure 1 is merely a name, and the name does not limit the function of the network element itself. In 5G networks and other future networks, the above-mentioned network elements may also have other names, and this is not specifically limited. For example, in a 6G network, some or all of the above-mentioned network elements may continue to use the terminology used in 5G, or may have other names, etc., which are uniformly explained here and will not be repeated below.

[0198] In addition, the network elements in Figure 1 do not necessarily need to exist simultaneously; the required network elements can be determined based on demand. The connection relationships between the network elements in Figure 1 are not uniquely determined and can be adjusted based on demand. It is understood that the above-mentioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0199] Of course, FIG1 is merely an example of a network architecture of a communication system and does not constitute a limitation on the network architecture of the communication system in the embodiment of the present application.

[0200] In application data transmission scenarios, users request application data from application servers, or application servers deliver application data to users. Application data can include data from various services, including latency-sensitive and data-intensive services such as extended reality (XR).

[0201] XR primarily encompasses virtual reality (VR), augmented reality (AR), and mixed reality (MR) technologies for interacting with reality. XR services are primarily video services, and video data is generated in a bursty manner. Data for a given service is generated periodically, typically with 60 frames of video data per second, or one frame every 16.6 milliseconds. Due to the large size of a single video frame, the data is fragmented into dozens of IP packets. For networks transmitting XR services, dozens of IP packets must be transmitted every 16.6 milliseconds. Furthermore, packet arrival times are uncertain, ranging from approximately [-4, 4] ms to [-5, 5] ms, and follow a truncated Gaussian distribution.

[0202] The following describes XR services using VR services as an example.

[0203] VR is a transformative technology that is revolutionizing content and communication consumption. By obstructing the user's line of sight, VR transports their senses into an independent, new virtual space, providing a more immersive and engaging experience. Terminal devices (such as wearable VR headsets) capture user motion information, such as head and hand movements, squatting and standing up, and transmit it via networks (such as access and core network equipment) to cloud-based application servers. The application servers then render and generate images based on the user's motion information and transmit them to the terminal devices via the communications network for viewing.

[0204] Furthermore, VR services are cyclical. Terminal devices periodically send uplink control packets containing interactive device signals such as head rotation and controllers, typically with a period of approximately 2.5ms to 5ms. The application server generates video frames at the frame rate and sends them to the terminal device via the downlink (for example, if the frame rate is 60fps, one frame is generated every 16.67ms).

[0205] When a user requests application data or an application server sends application data, the access network equipment and the core network equipment in the communication system need to jointly participate in the relevant processing of the application data.

[0206] For example, in the case of XR services, as shown in Figure 2, the UPF is responsible for identifying media information and transmitting it to the RAN via GTP-U. The RAN then schedules the media data for the XR service to the server based on this media information. In this way, the UPF and RAN jointly participate in media data scheduling. This media information may include the PDU set sequence number, the last PDU in the set, the PDU sequence number within the set, the byte size of the PDU set, and the importance of the PDU set.

[0207] Of course, FIG. 2 may also involve other network elements in the core network participating in the scheduling of media data, and there is no specific limitation on this.

[0208] As factors such as user demand, network congestion status, network configuration, or contract information change, it may be necessary to dynamically adjust and effectively control the bit rate of application data with the joint participation of access network equipment and core network equipment.

[0209] Based on this, this embodiment mainly considers scenarios where the UPF is assisted by access network equipment and relevant network elements in the core network to dynamically adjust and effectively control the bit rate of application data. In this way, this embodiment can delegate the function of adjusting or controlling the application layer bit rate to the UPF, thereby reducing the latency of application layer bit rate adjustment or control.

[0210] The following uses the transmission of XR services based on media over quick UDP internet connections (media over QUIC, MoQ) as an example to illustrate the scenario where UPF needs to dynamically adjust and effectively control the bit rate of application data.

[0211] MoQ is a QUIC-based media transmission protocol that provides end-to-end encryption support. As shown in Figure 3, the MoQ protocol architecture includes a client, a MoQ relay node, and a server. The MoQ protocol transmits media at the object level, and carries metadata with each object. An object can be a video frame, and metadata is auxiliary information specific to the object (for example, the object's sequence number, priority, and other information). The MoQ Relay can forward, cache, or discard objects based on the metadata it receives.

[0212] To enable MoQ-based transmission of XR service data, the UPF needs to identify the media information of XR services, and MoQ uses end-to-end encryption. Therefore, if the UPF identifies the media information of XR services transmitted over MoQ, the UPF needs to act as a MoQ Relay. Therefore, when the UPF acts as a MoQ Relay, it may be necessary to enhance the UPF's capabilities to dynamically adjust and effectively control the bitrate of application data in response to changes in factors such as user demand, network congestion, network configuration, or contract information. This allows the UPF to adapt to these changes through bitrate adjustment and control. At the same time, the capabilities of other relevant network elements in the access network equipment and core network of the communication system also need to be enhanced to assist the UPF in dynamically adjusting and effectively controlling the bitrate of application data through enhanced capabilities.

[0213] The following embodiments illustrate how access network devices and core network elements can assist the UPF in dynamically adjusting and effectively controlling the bitrate of application data. These solutions can be independent or interrelated. The same content between different solutions can be referenced without specific limitation.

[0214] [Scheme 1]

[0215] In "Scheme 1," this embodiment considers that relevant gateways in the core network can assist the UPF in obtaining the rate authorization information issued by the AF. In this way, the UPF can dynamically adjust and effectively control the rate information corresponding to the application data based on the rate authorization information issued by the AF, and ensure that the rate information corresponding to the application data is within the rate authorization information. Because this embodiment uses the relevant gateway to assist in sending the rate authorization information to the UPF, the UPF can authenticate the rate authorization based on the rate authorization information and use this to dynamically adjust and effectively control the rate information corresponding to the application data, thereby reducing the delay in application-layer rate authorization authentication and the delay in application-layer rate adjustment or control.

[0216] It should be noted that the bit rate authorization information refers to the bit rate information allowed for a terminal device to access an application. The bit rate authorization information is described in detail below.

[0217] Bitrate refers to the bit rate at which application data (such as media data, audio, video, or images) is transmitted, typically measured in bits per second (bps). A higher bitrate increases the amount of data transmitted and improves the quality of the application data, but also requires more bandwidth and storage space. For example, bitrates for application data can be 64kbps (kilobits per second), 128kbps, 480kbps, 720kbps, 1080kbps, 4K kbps, or 1Mbps (megabits per second).

[0218] Typically, a terminal device registers with an application server through a registration request process. After successful registration, the terminal device can successfully access the application server and request the application server to deliver application data. The application server also records the terminal device's device ID, account number, password, and access permissions.

[0219] In some examples, the bitrate authorization information may include the maximum bitrate allowed for the terminal device to access the application.

[0220] This is because, after successful registration, the application server typically sets the maximum bitrate allowed for terminal devices to access the application. Therefore, when the terminal device requests application data from the application server, the application server selects a bitrate from the maximum bitrate allowed for the terminal device to access the application, or a bitrate below it, and provides the application data at the selected bitrate to the terminal device.

[0221] For example, when the application server sets the maximum bit rate allowed for the terminal device to access the application to 1080kbps, the terminal device can only use bit rates below 1080kbps, or the application server can only provide the terminal device with application data corresponding to the maximum bit rate of 1080kbps.

[0222] In addition, the application server can set the maximum bit rate according to the service subscribed by the terminal device. Since different terminal devices subscribe to different services, the application server sets different maximum bit rates according to the different subscribed services. For example, when some terminal devices have subscribed to membership services from the application server, the application server can set the maximum bit rate allowed for these terminal devices to access the application to be larger (such as 4K kbps). When some terminal devices only subscribe to non-member services from the application server, the application server can set the maximum bit rate allowed for these terminal devices to access the application to be smaller (such as 720kbps).

[0223] In some examples, the code rate authorization information may include a code rate list that the terminal device is allowed to use when accessing the application, wherein the code rate list may refer to a combination of a series of different code rates.

[0224] This is because, after successful registration, the application server typically sets a list of bitrates that the terminal device is allowed to use when accessing the application. Thus, when the terminal device requests application data from the application server, the application server selects a bitrate from the list and provides the application data at the selected bitrate to the terminal device.

[0225] In addition, the application server can set a rate list based on the services subscribed by the terminal device. Since different terminal devices subscribe to different services, the application server sets different rate lists based on the different subscription services. For example, when some terminal devices have subscribed to membership services with the application server, the application server can set a rate list with more available rates for these terminal devices to access the application. When some terminal devices only subscribe to non-member services with the application server, the application server can set a rate list with fewer available rates for these terminal devices to access the application.

[0226] In some examples, the bitrate authorization information may include bitrate information that the terminal device is allowed to use when accessing the application within a preset time period. The bitrate information here may include a maximum bitrate or a bitrate list.

[0227] This is because the application server can set the bit rate information (such as the maximum bit rate or bit rate list) allowed for terminal devices to access the application according to different time periods. For example, in a time period with a small number of users accessing the application (such as at night), since the number of terminal devices accessing the application server during this period is usually small, the occupancy rate of bandwidth resources is low or the congestion rate presented by the network status is low, etc., so the application server can set the maximum bit rate allowed for terminal devices to access the application during this period to be larger or the bit rates available for selection in the bit rate list are more. However, in a time period with a large number of users accessing the application (such as during the day), since the number of terminal devices accessing the application server during this period is usually large, the occupancy rate of bandwidth resources is high or the congestion rate presented by the network status is high, etc., so the application server can set the maximum bit rate allowed for terminal devices to access the application during this period to be smaller or the bit rates available for selection in the bit rate list are fewer. In this way, the bit rate information allowed for terminal devices to access the application can be flexibly set according to the time period.

[0228] In some examples, the code rate authorization information may include code rate information allowed for a terminal device to access an application within a preset location area. The code rate information may include a maximum code rate or a code rate list.

[0229] This is because the application server can set the bitrate information (such as the maximum bitrate or bitrate list) allowed for terminal devices to access applications based on different location areas. For example, in densely populated locations (such as business districts), since the number of terminal devices accessing the application server in these locations is generally large, resulting in higher bandwidth resource utilization or higher network congestion, the application server can set a lower maximum bitrate allowed for terminal devices to access applications in these locations or a smaller number of available bitrates in the bitrate list.

[0230] The following example illustrates how the relevant gateways in the core network assist the UPF in obtaining the bit rate authorization information issued by the AF.

[0231] FIG4 is a flow chart of a method for transmitting bit rate authorization information according to an embodiment of the present application. In FIG4 , the method specifically includes the following steps:

[0232] S401. AF sends bit rate authorization information to NEF.

[0233] Correspondingly, NEF obtains the bit rate authorization information sent by AF.

[0234] In this way, NEF can be responsible for providing rate authorization information to other network elements.

[0235] S402. NEF saves the bit rate authorization information to UDR.

[0236] In this way, UDR is specifically responsible for the management and storage of bit rate authorization information.

[0237] S403.SMF obtains bit rate authorization information.

[0238] It should be noted that the SMF can obtain the bit rate authorization information in response to a PDU session creation request or a PDU session modification request.

[0239] In response to the PDU session creation request or the PDU session modification request, it can be understood that after the SMF receives the PDU session creation / modification request, the SMF will check the local configuration information or contract information. Among them, the local configuration information or contract information may include indication information for instructing the SMF to obtain the bit rate authorization information after receiving the PDU session creation request or the PDU session modification request. For example, these indication information may indicate that the SMF needs to obtain the bit rate authorization information for a specific slice or a specific data network name (DNN) user. In this way, the SMF can trigger the process of obtaining the bit rate authorization information issued by the AF based on the local configuration information or contract information.

[0240] In addition, SMF can obtain the bit rate authorization information issued by AF in different ways. The following methods are provided here:

[0241] Method 1: SMF requests the bitrate authorization information issued by AF from NEF, NEF queries the authorization information issued by AF from UDR, UDR returns the authorization information to NEF, and NEF returns the authorization information to SMF. The specific steps are as follows:

[0242] S403A. SMF sends a request message to NEF for bit rate authorization information.

[0243] Correspondingly, the NEF receives the request message.

[0244] The request message may be used to request the NEF to query the UDR for the bit rate authorization information issued by the AF. For ease of distinction, the request message may also be referred to as a "first request message."

[0245] S403B. NEF sends a query message to UDR for querying the bit rate authorization information.

[0246] Correspondingly, the UDR receives the query message.

[0247] S403C.UDR sends bit rate authorization information to NEF.

[0248] Correspondingly, NEF receives the bit rate authorization information.

[0249] S403D.NEF sends bit rate authorization information to SMF.

[0250] Correspondingly, SMF receives the bit rate authorization information.

[0251] The bit rate authorization information may be carried by the first response message, that is, the first response message includes the bit rate authorization information.

[0252] Method 2: SMF requests PDU session policy from PCF. PCF can determine the need to obtain the rate authorization information issued by AF based on local configuration information or contract information. PCF queries UDR for the rate authorization information issued by AF. UDR returns the rate authorization information to PCF, and PCF sends the rate authorization information to SMF. Among them, local configuration information or contract information may include instruction information for instructing PCF to obtain rate authorization information after receiving the PDU session policy request from SMF. For example, these instructions can indicate that PCF needs to obtain rate authorization information for a specific slice or a specific DNN user. The specific steps are as follows:

[0253] S403a. The SMF sends a request message to the PCF for requesting a PDU session policy.

[0254] Correspondingly, the PCF receives the request message.

[0255] The request message may be used to request the PCF to query the UDR for the bit rate authorization information issued by the AF. For ease of distinction, the request message may also be referred to as a "second request message."

[0256] S403b. The PCF sends a query message to the UDR for querying the bit rate authorization information based on the local configuration information or contract information.

[0257] Correspondingly, the UDR receives the query message.

[0258] S403c. UDR sends bit rate authorization information to PCF.

[0259] Correspondingly, the PCF receives the bit rate authorization information.

[0260] S403d. PCF sends bit rate authorization information to SMF.

[0261] Correspondingly, SMF receives the bit rate authorization information.

[0262] The bit rate authorization information may be carried by the second response message, that is, the second response message includes the bit rate authorization information.

[0263] S404.SMF sends bit rate authorization information to UPF.

[0264] Correspondingly, UPF receives bit rate authorization information.

[0265] The bit rate authorization information is carried by the N4 session creation request message or the N4 session modification request message.

[0266] It should be noted that the N4 session creation process is used to create the initial N4 session context for the PDU session in the UPF. The SMF allocates a new N4 session ID and provides it to the UPF, and sends an N4 session creation request message to the UPF. Therefore, during the N4 session creation process, the SMF can send rate authorization information to the UPF via the N4 session creation request message so that the UPF can obtain the rate authorization information.

[0267] In addition, the N4 Session Modification procedure is used to update the N4 Session Context of an existing PDU Session at the UPF. It is performed between the SMF and the UPF when PDU Session-related parameters need to be modified. The SMF sends an N4 Session Modification Request message to the UPF. Therefore, during the N4 Session creation process, the SMF can send the rate authorization information to the UPF via the N4 Session Modification Request message so that the UPF can obtain the rate authorization information.

[0268] As shown in Figure 4, the relevant gateways in the core network can assist the UPF to obtain the bitrate authorization information. The auxiliary operations are as follows:

[0269] AF sends the bit rate authorization information to NEF, and NEF saves the bit rate authorization information sent by AF to UDR. After SMF obtains the PDU session creation request or PDU session modification request, SMF obtains the bit rate authorization information from UDR through NEF, or SMF obtains the bit rate authorization information from UDR through PCF. Finally, SMF sends the bit rate authorization information sent by AF to UPF.

[0270] In this way, the UPF can dynamically adjust and effectively control the bitrate corresponding to the application data based on the bitrate authorization information sent by the AF, and ensure that the bitrate information corresponding to the application data is within the bitrate authorization information. Since this embodiment sends the bitrate authorization information to the UPF, the UPF can authenticate the application-layer bitrate authorization based on the bitrate authorization information and use it to dynamically adjust and effectively control the bitrate corresponding to the application data, thereby reducing the delay of application-layer bitrate authorization authentication and the delay of application-layer bitrate adjustment or control.

[0271] [Scheme 2]

[0272] After the UPF obtains the bit rate authorization information, in "Solution 2", this embodiment needs to consider the situation where the UPF locally caches application data and subscribes to application data.

[0273] Specifically, for a PDU session creation request or a PDU session modification request, the UPF may request the application server to subscribe to specific application data based on the bitrate authorization information. The bitrate information corresponding to the specific application data is included in the bitrate authorization information so that the specific application data can be cached locally first. The specific application data may be application data related to the PDU session creation request or the PDU session modification request.

[0274] This is because, when a terminal device requests PDU session creation or PDU session modification, the UPF and SMF will record and maintain information such as the session context corresponding to the terminal device during the process of the PDU session creation request or PDU session modification request. At this time, the UPF can determine the bit rate information allowed for the terminal device to access the application based on the bit rate authorization information, so as to request the application server to subscribe to the application data related to the terminal device in advance based on the bit rate information allowed for the terminal device to access the application. The bit rate information corresponding to the application data related to the terminal device is in the bit rate authorization information, and the application data related to the terminal device is cached locally in the UPF.

[0275] In this way, UPF can directly provide the terminal device with application data in the local cache or subscribed application data, avoiding the application server from directly sending application data to the terminal device to reduce the delay required for the overall transmission of application data, and reduce the export bandwidth pressure of the application server when the terminal device requests application data from the application server (especially requesting application data with a higher bit rate).

[0276] The following example illustrates how the UPF can request the application server to subscribe to application data based on the bit rate authorization information.

[0277] FIG5 is a flow chart of a method for subscribing to application data according to an embodiment of the present application. In FIG5 , the method specifically includes the following steps:

[0278] S501. UPF determines the application data that needs to be subscribed locally based on the bit rate authorization information. The bit rate information corresponding to the application data is in the bit rate authorization information.

[0279] It should be noted that UPF needs to record and maintain the correspondence between application data and bitrate information, and use this to locally cache application data and provide application data, etc.

[0280] S502. UPF sends a subscription request message to the application server. The subscription request message is used to request subscription to application data.

[0281] Correspondingly, the application server receives the subscription request message.

[0282] The subscription request message may include application data and / or bit rate information corresponding to the application data.

[0283] In this way, the application server obtains the application data that the UPF needs to subscribe to and the bit rate information corresponding to the application data through the subscription request message.

[0284] S503. The application server sends a subscription response message to the UPF, wherein the subscription response message may include a code rate identifier (ID).

[0285] Correspondingly, UPF receives the subscription response message.

[0286] In this way, the UPF can obtain the code rate ID through the subscription response message, so as to obtain application data according to the code rate ID later.

[0287] S504. UPF records and maintains the correspondence between application data and bitrate ID.

[0288] S505. The application server sends application data to the UPF according to the bitrate ID.

[0289] Correspondingly, UPF receives application data according to the bitrate ID.

[0290] As shown in Figure 5, the UPF requests the application server to subscribe to application data based on the bitrate authorization information, and the application server sends the application data to the UPF. During the subscription process, the UPF needs to record and maintain the correspondence between the application data and the bitrate ID, and use this to cache the application data locally and provide application data.

[0291] [Scheme 3]

[0292] After the UPF obtains the bit rate authorization information, in "Scheme 3", this embodiment needs to consider the situation where the terminal device requests application data through application layer messages, and how the UPF processes the application data request of the terminal device according to the bit rate authorization information and sends the application data to the terminal device.

[0293] It should be noted that a terminal device can request the content of the application data it needs, such as videos, images, music, or other media resources. The application data request of the terminal device can be generated based on the user's operation or the logic within the application to meet the user's needs and obtain the required application data. For example, when a user chooses to play a video or view an image in an application, the terminal device will request the application data from the application server. After receiving the application data, the terminal device can perform corresponding processing and display, allowing the user to watch the video or view the image.

[0294] Additionally, when requesting application data, the terminal device may request the required bitrate information. For example, when a user selects to play a video in an application, they may select a bitrate of 1080kbps, or adjust the bitrate from 720kbps to 1080kbps. In this case, the terminal device will request 1080kbps from the application server.

[0295] After the RAN receives the application data request from the terminal device, the RAN can forward the application data request to the UPF. After the UPF obtains the application data request from the terminal device, the UPF can determine the bit rate information (i.e., the actual bit rate information) corresponding to the application data requested by the terminal device based on the bit rate authorization information, ensure that the actual bit rate information is within the bit rate authorization information, and then determine whether it is necessary to subscribe to the application data from the application server based on the local cache information or historical application data subscription information, and finally send the application data to the terminal device. Among them, when the application data is cached locally or has been subscribed to, the UPF sends the application data to the terminal device; when the application data is not cached locally or has not been subscribed to, the UPF needs to subscribe to the application data from the application server.

[0296] Of course, when the terminal device requests the bit rate information corresponding to the application data, since the actual bit rate information may be different from the bit rate information requested by the terminal device, the UFP needs to inform the terminal device of the actual bit rate information in advance before the UPF sends the application data to the terminal device.

[0297] For example, after a user selects a video to play in an application and chooses a bitrate of 1080kbps, the terminal device sends an application data request message to the RAN. This message includes the name of the requested video content and the requested bitrate of 1080kbps. The RAN then forwards this request message to the UPF. Assume that the bitrate authorization information includes a maximum bitrate of 720kbps allowed for the terminal device to access the application. After receiving the application data request message, the UPF needs to adjust the requested bitrate to 720kbps or below, as the bitrate of 1080kbps requested by the terminal device exceeds its maximum bitrate of 720kbps. After the UPF determines that the actual bitrate of the video is 720kbps, it notifies the terminal device of the actual bitrate and checks whether the video content is cached locally. When the video content is cached locally, UPF can send the video content directly to the terminal device; when the video content is not cached locally, UPF needs to subscribe to the video content from the application server first and then send it to the terminal device.

[0298] It can be seen that UPF can authenticate the application layer rate authorization of the application data requested by the terminal device based on the rate authorization information, thereby reducing the delay of application layer rate authorization authentication. At the same time, UPF can determine whether it is necessary to subscribe to application data from the application server based on the local cache status or historical application data subscription information, and provide application data to the terminal device, avoiding the application server directly sending application data to the terminal device to reduce the delay required for the overall transmission of application data, and reduce the export bandwidth pressure of the application server when the terminal device requests application data from the application server (especially requesting application data with a higher rate).

[0299] The following is an example of the process of UPF sending application data to the terminal device according to the bit rate authorization information.

[0300] FIG6 is a flow chart of a method for transmitting application data according to an embodiment of the present application. In FIG6 , the method specifically includes the following steps:

[0301] S601. The terminal device sends application data request information to the RAN.

[0302] Correspondingly, the RAN receives the application data request information.

[0303] The application data request information may include target application data requested by the terminal device and / or bit rate information requested by the terminal device.

[0304] S602. RAN sends application data request information to UPF.

[0305] Correspondingly, UPF receives the application data request information.

[0306] S603. UPF processes the application data request information according to the bit rate authorization information.

[0307] It should be noted that the UPF can process the application data request information in different ways according to the bit rate authorization information. The following methods are provided here:

[0308] Method a: If the application data request information includes the target application data requested by the terminal device, the UPF can determine the bitrate information corresponding to the target application data in the bitrate authorization information in response to the application data request information. In other words, if the user does not specify the bitrate corresponding to the application data, the UPF can select a bitrate in the bitrate authorization information.

[0309] For example, after a user selects to play a video in an application, the terminal device sends an application data request message to the RAN. This message includes the name of the requested video content. The RAN then forwards this message to the UPF. Assume that the bitrate authorization information includes the maximum bitrate allowed for the terminal device to access the application, which is 720 kbps. Thus, after receiving the application data request message, the UPF determines that the bitrate of the video is 720 kbps.

[0310] Method b: If the application data request information includes the target application data requested by the terminal device and the bit rate information requested by the terminal device, the UPF needs to determine whether the bit rate information requested by the terminal device can be authorized based on the bit rate authorization information. When the bit rate information requested by the terminal device is within the bit rate authorization information, this means that the bit rate information requested by the terminal device can be authorized, and the bit rate information requested by the terminal device is used as the bit rate information actually corresponding to the target application data. When the bit rate information requested by the terminal device is not within the bit rate authorization information, this means that the bit rate information requested by the terminal device has not been authorized, and the UPF needs to determine the bit rate information actually corresponding to the target application data within the bit rate authorization information.

[0311] For example, when a user selects a video to play in an application and chooses a bitrate of 1080 kbps, the terminal device sends an application data request message to the RAN. This message includes the name of the requested video content and the requested bitrate of 1080 kbps. The RAN then forwards this application data request message to the UPF. Assume that the bitrate authorization information includes a maximum bitrate of 720 kbps for the terminal device to access the application. Thus, after receiving the application data request message, the UPF determines that the actual bitrate of the video is 720 kbps.

[0312] S604. UPF sends the bit rate information corresponding to the target application data to the terminal device.

[0313] It should be noted that the UPF needs to first send the bit rate information corresponding to the target application data to the RAN, and then the RAN forwards it to the terminal device.

[0314] S605. The UPF determines whether it is necessary to subscribe to the target application data from the application server based on the local cache information or the historical application data subscription information.

[0315] It should be noted that if the target application data is cached locally or has been subscribed to, S606 is executed; if the target application data is not cached locally or has not been subscribed to, S607 to S611 are executed.

[0316] S606. UPF sends target application data to the terminal device.

[0317] Correspondingly, the terminal device receives the target application data.

[0318] It should be noted that the UPF needs to first send the target application data to the RAN, and then the RAN forwards it to the terminal device.

[0319] S607. UPF sends a subscription request message to the application server. The subscription request message is used to request subscription to target application data.

[0320] The subscription request message may include target application data and / or bit rate information actually corresponding to the target application data.

[0321] In this way, the application server obtains the target application data that the UPF needs to subscribe to and the actual bit rate information corresponding to the target application data through the subscription request message.

[0322] S608: The application server sends a subscription response message to the UPF, wherein the subscription response message may include a code rate ID.

[0323] Correspondingly, UPF receives the subscription response message.

[0324] In this way, the UPF can obtain the code rate ID through the subscription response message, so as to obtain the target application data according to the code rate ID later.

[0325] S609. UPF records and maintains the correspondence between the target application data and the bitrate ID.

[0326] S610. The application server sends target application data to the UPF according to the bitrate ID.

[0327] Correspondingly, the UPF receives the target application data according to the bitrate ID.

[0328] S611. UPF sends target application data to the terminal device.

[0329] Correspondingly, the terminal device receives the target application data.

[0330] It should be noted that the UPF needs to first send the target application data to the RAN, and then the RAN forwards it to the terminal device.

[0331] As can be seen from Figure 6, the terminal device can request application data through application layer messages, and the UPF can process the application data request of the terminal device according to the bit rate authorization information and send the application data to the terminal device.

[0332] [Scheme 4]

[0333] In "Solution 4," this embodiment combines "Solution 1" and "Solution 3" above to enable the relevant gateway in the core network to assist the UPF in obtaining the bitrate authorization information issued by the AF. The UPF then processes the application data request of the terminal device based on the bitrate authorization information and sends the application data to the terminal device. The following example illustrates this.

[0334] FIG7 is a flow chart of another method for transmitting application data according to an embodiment of the present application. In FIG7 , the method specifically includes the following steps:

[0335] S701. AF sends bit rate authorization information to NEF.

[0336] Correspondingly, NEF obtains the bit rate authorization information sent by AF.

[0337] In this way, NEF can be responsible for providing rate authorization information to other network elements.

[0338] S702.NEF saves the bit rate authorization information to UDR.

[0339] In this way, UDR is specifically responsible for the management and storage of bit rate authorization information.

[0340] S703.SMF obtains bit rate authorization information.

[0341] It should be noted that the SMF can obtain the bit rate authorization information in response to a PDU session creation request or a PDU session modification request.

[0342] In response to the PDU session creation request or the PDU session modification request, it can be understood that after the SMF receives the PDU session creation / modification request, the SMF will check the local configuration information or contract information. Among them, the local configuration information or contract information may include indication information for instructing the SMF to obtain the bit rate authorization information after receiving the PDU session creation request or the PDU session modification request. For example, these indication information may indicate that the SMF needs to obtain the bit rate authorization information for a specific slice or a specific data network name (DNN) user. In this way, the SMF can trigger the process of obtaining the bit rate authorization information issued by the AF based on the local configuration information or contract information.

[0343] In addition, SMF can obtain the bit rate authorization information issued by AF in different ways. The following methods are provided here:

[0344] Method 1: SMF requests the bitrate authorization information issued by AF from NEF, NEF queries the authorization information issued by AF from UDR, UDR returns the authorization information to NEF, and NEF returns the authorization information to SMF. The specific steps are as follows:

[0345] S703A. SMF sends a request message to NEF for bit rate authorization information.

[0346] Correspondingly, the NEF receives the request message.

[0347] The request message may be used to request the NEF to query the UDR for the bit rate authorization information issued by the AF. For ease of distinction, the request message may also be referred to as a "first request message."

[0348] S703B.NEF sends a query message to UDR for querying the bit rate authorization information.

[0349] Correspondingly, the UDR receives the query message.

[0350] S703C.UDR sends bit rate authorization information to NEF.

[0351] Correspondingly, NEF receives the bit rate authorization information.

[0352] S703D.NEF sends bit rate authorization information to SMF.

[0353] Correspondingly, SMF receives the bit rate authorization information.

[0354] The bit rate authorization information may be carried by the first response message, that is, the first response message includes the bit rate authorization information.

[0355] Method 2: SMF requests PDU session policy from PCF. PCF can determine the need to obtain the rate authorization information issued by AF based on local configuration information or contract information. PCF queries UDR for the rate authorization information issued by AF. UDR returns the rate authorization information to PCF, and PCF sends the rate authorization information to SMF. Among them, local configuration information or contract information may include instruction information for instructing PCF to obtain rate authorization information after receiving the PDU session policy request from SMF. For example, these instructions can indicate that PCF needs to obtain rate authorization information for a specific slice or a specific DNN user. The specific steps are as follows:

[0356] S703a. The SMF sends a request message to the PCF for requesting a PDU session policy.

[0357] Correspondingly, the PCF receives the request message.

[0358] The request message may be used to request the PCF to query the UDR for the bit rate authorization information issued by the AF. For ease of distinction, the request message may also be referred to as a "second request message."

[0359] S703b. The PCF sends a query message to the UDR for querying the bit rate authorization information based on the local configuration information or contract information.

[0360] Correspondingly, the UDR receives the query message.

[0361] S703c. UDR sends bit rate authorization information to PCF.

[0362] Correspondingly, the PCF receives the bit rate authorization information.

[0363] S703d. PCF sends bit rate authorization information to SMF.

[0364] Correspondingly, SMF receives the bit rate authorization information.

[0365] The bit rate authorization information may be carried by the second response message, that is, the second response message includes the bit rate authorization information.

[0366] S704.SMF sends bit rate authorization information to UPF.

[0367] Correspondingly, UPF receives bit rate authorization information.

[0368] The bit rate authorization information is carried by the N4 session creation request message or the N4 session modification request message.

[0369] S705. The terminal device sends application data request information to the RAN.

[0370] Correspondingly, the RAN receives the application data request information.

[0371] The application data request information may include target application data requested by the terminal device and / or bit rate information requested by the terminal device.

[0372] S706. RAN sends application data request information to UPF.

[0373] Correspondingly, UPF receives the application data request information.

[0374] S707. UPF processes the application data request information according to the bit rate authorization information.

[0375] It should be noted that the UPF can process the application data request information in different ways according to the bit rate authorization information. The following methods are provided here:

[0376] Method a: If the application data request information includes the target application data requested by the terminal device, the UPF can determine the bitrate information corresponding to the target application data in the bitrate authorization information in response to the application data request information. In other words, if the user does not specify the bitrate corresponding to the application data, the UPF can select a bitrate in the bitrate authorization information.

[0377] For example, after a user selects to play a video in an application, the terminal device sends an application data request message to the RAN. This message includes the name of the requested video content. The RAN then forwards this message to the UPF. Assume that the bitrate authorization information includes the maximum bitrate allowed for the terminal device to access the application, which is 720 kbps. Thus, after receiving the application data request message, the UPF determines that the bitrate of the video is 720 kbps.

[0378] Method b: If the application data request information includes the target application data requested by the terminal device and the bit rate information requested by the terminal device, the UPF needs to determine whether the bit rate information requested by the terminal device can be authorized based on the bit rate authorization information. When the bit rate information requested by the terminal device is within the bit rate authorization information, this means that the bit rate information requested by the terminal device can be authorized, and the bit rate information requested by the terminal device is used as the bit rate information actually corresponding to the target application data. When the bit rate information requested by the terminal device is not within the bit rate authorization information, this means that the bit rate information requested by the terminal device has not been authorized, and the UPF needs to determine the bit rate information actually corresponding to the target application data within the bit rate authorization information.

[0379] For example, when a user selects a video to play in an application and chooses a bitrate of 1080 kbps, the terminal device sends an application data request message to the RAN. This message includes the name of the requested video content and the requested bitrate of 1080 kbps. The RAN then forwards this application data request message to the UPF. Assume that the bitrate authorization information includes a maximum bitrate of 720 kbps for the terminal device to access the application. Thus, after receiving the application data request message, the UPF determines that the actual bitrate of the video is 720 kbps.

[0380] S708. UPF sends the bit rate information corresponding to the target application data to the terminal device.

[0381] It should be noted that the UPF needs to first send the bit rate information corresponding to the target application data to the RAN, and then the RAN forwards it to the terminal device.

[0382] S709. The UPF determines whether it is necessary to subscribe to the target application data from the application server based on the local cache information or the historical application data subscription information.

[0383] It should be noted that if the target application data is cached locally or has been subscribed to, S710 is executed; if the target application data is not cached locally or has not been subscribed to, S711 to S715 are executed.

[0384] S710. UPF sends target application data to the terminal device.

[0385] Correspondingly, the terminal device receives the target application data.

[0386] It should be noted that the UPF needs to first send the target application data to the RAN, and then the RAN forwards it to the terminal device.

[0387] S711. UPF sends a subscription request message to the application server. The subscription request message is used to request subscription to target application data.

[0388] The subscription request message may include target application data and / or bit rate information actually corresponding to the target application data.

[0389] In this way, the application server obtains the target application data that the UPF needs to subscribe to and the actual bit rate information corresponding to the target application data through the subscription request message.

[0390] S712: The application server sends a subscription response message to the UPF, wherein the subscription response message may include a code rate ID.

[0391] Correspondingly, UPF receives the subscription response message.

[0392] In this way, the UPF can obtain the code rate ID through the subscription response message, so as to obtain the target application data according to the code rate ID later.

[0393] S713. UPF records and maintains the correspondence between target application data and bitrate ID.

[0394] S714. The application server sends the target application data to the UPF according to the bitrate ID.

[0395] Correspondingly, the UPF receives the target application data according to the bitrate ID.

[0396] S715. UPF sends target application data to the terminal device.

[0397] Correspondingly, the terminal device receives the target application data.

[0398] It should be noted that the UPF needs to first send the target application data to the RAN, and then the RAN forwards it to the terminal device.

[0399] [Scheme 5]

[0400] In the aforementioned "Solution 3," the terminal device requests application data through application layer messages, and the RAN forwards the terminal device's application data request to the UPF. However, in "Solution 5," this embodiment needs to consider the case where the terminal device requests application data through control plane messages, and the terminal device's application data request is sent to the UPF via the AMF and SMF. Ultimately, the UPF processes the terminal device's application data request based on the bit rate authorization information and then sends the application data to the terminal device.

[0401] The following embodiment only illustrates the process in which the terminal device requests application data through a control plane message and sends the application data request of the terminal device to the UPF via the AMF and SMF. The process in which the UPF processes the application data request of the terminal device according to the bit rate authorization information and sends the application data to the terminal device can refer to the content of the above-mentioned "Solution 3", which will not be repeated here.

[0402] FIG8 is a flow chart of a method for transmitting application data request information according to an embodiment of the present application. In FIG8 , the method specifically includes the following steps:

[0403] S801. The terminal device sends a PDU session creation request message to the AMF. The PDU session creation request message includes the application data request information of the terminal device.

[0404] Correspondingly, AMF receives the PDU session creation request message.

[0405] It should be noted that the terminal device needs to first send the PDU session creation request message to the RAN, which then forwards it to the AMF through the N2 interface.

[0406] S802. AMF sends a session management (SM) context request message to SMF. The SM context request message includes application data request information.

[0407] Correspondingly, the SMF receives the SM context request message.

[0408] S803. SMF sends an N4 session creation request message to UPF. The N4 session creation request message includes application data request information.

[0409] Correspondingly, UPF receives the N4 session creation request message.

[0410] As can be seen from FIG8 , in this embodiment, the application data request information of the terminal device can be transmitted through the PDU session creation process.

[0411] FIG9 is a flow chart of another method for transmitting application data request information according to an embodiment of the present application. In FIG9 , the method specifically includes the following steps:

[0412] S901. The terminal device sends a PDU session modification request message to the AMF. The PDU session modification request message includes the application data request information of the terminal device.

[0413] Correspondingly, AMF receives the PDU session modification request message.

[0414] It should be noted that the terminal device needs to first send the PDU session modification request message to the RAN, and then the RAN forwards it to the AMF through the N2 interface.

[0415] S902. AMF sends an SM context update request message to SMF, where the SM context update request message includes application data request information.

[0416] Correspondingly, the SMF receives the SM context update request message.

[0417] S903. SMF sends an N4 session modification request message to UPF. The N4 session modification request message includes application data request information.

[0418] Correspondingly, UPF receives the N4 session modification request message.

[0419] As can be seen from FIG9 , in this embodiment, the application data request information of the terminal device can be transmitted through the PDU session modification process.

[0420] [Scheme 6]

[0421] After the UPF obtains the bitrate authorization information, in "Solution 6," this embodiment considers that the UPF determines the applicable bitrate from the bitrate authorization information based on network congestion information or bandwidth usage information reported by the RAN, or network performance analysis information reported by the NWDAF. In other words, the UPF adjusts the bitrate information corresponding to the current application data based on the network congestion information, bandwidth usage information, or network performance analysis information, and the adjusted bitrate information is included in the bitrate authorization information.

[0422] It should be noted that network congestion information refers to data used to monitor and manage network congestion during communications between the RAN and terminal devices. Network congestion occurs when network traffic exceeds the processing capacity of network resources. This can be caused by a large number of users accessing the network simultaneously, excessive data transmission demands, or insufficient network resources. Network congestion can increase application data transmission latency, increase packet loss, and degrade user experience.

[0423] The RAN can obtain network congestion information in various ways, including the following:

[0424] Method 1: The RAN can measure the latency of application data transmitted from the terminal device to the application server / RAN or vice versa. If the latency is high, it may indicate that the network is heavily loaded and congested.

[0425] Method 2: The RAN can monitor packet loss during application data transmission. A high packet loss rate may indicate network congestion.

[0426] Method 3: The RAN maintains a queue for application data transmission. When the network is congested, the number of packets waiting to be transmitted in the queue increases. By monitoring the queue length, it is possible to infer whether the network is congested.

[0427] Method 4: RAN can monitor and analyze data flows through the network to understand traffic distribution and changes. If there is an abnormal increase in traffic in certain areas or time periods, it may be a sign of congestion.

[0428] Method 5: The RAN can monitor quality of service (QoS) parameters such as latency, packet loss, and bandwidth usage. When the network is congested, these parameters may exceed preset thresholds. If QoS parameters exceed the set limits, the RAN will determine that the network may be congested.

[0429] In this way, after the RAN reports network congestion information to the UPF, the UPF can determine the appropriate bitrate from the bitrate authorization information based on the network congestion information. When the network congestion information indicates network congestion, which can result in high packet loss rates, high bandwidth utilization, or high latency, the UPF can reduce the bitrate corresponding to the application data. This reduced bitrate is also included in the bitrate authorization information, thereby achieving bitrate adjustment.

[0430] Bandwidth usage information refers to data related to the recording and management of network resource usage during communications between the RAN and terminal devices. Bandwidth refers to the capacity of the data channel within a network resource that can be used for application data transmission and is typically used to measure the network's transmission capacity. Bandwidth usage information can include bandwidth utilization rate. Bandwidth utilization rate refers to the proportion of currently used bandwidth to total bandwidth. It can be used to measure network resource utilization and load, and can determine whether the network is experiencing congestion or whether bandwidth capacity needs to be increased. A higher bandwidth utilization rate indicates a greater load on the current network resources, potentially leading to network slowdown or congestion, impacting the user's network experience.

[0431] In this way, after the RAN reports bandwidth usage information to the UPF, the UPF can determine the applicable bitrate from the bitrate authorization information based on the bandwidth usage information. When the bandwidth usage information indicates high bandwidth utilization, since high bandwidth utilization indicates low available bandwidth, the UPF can reduce the bitrate corresponding to the application data, and the reduced bitrate is also included in the bitrate authorization information, thereby adjusting the bitrate. When the bandwidth usage information indicates low bandwidth utilization, since low bandwidth utilization indicates high available bandwidth, the UPF can increase the bitrate corresponding to the application data, and the increased bitrate is also included in the bitrate authorization information, thereby adjusting the bitrate.

[0432] Network performance analysis information refers to the data and events generated during network communications. This data and events can be used to evaluate and analyze network performance and quality. This information can include bandwidth utilization, transmission latency, packet loss rate, and data traffic. NWDAF collects and analyzes this information to optimize network resource allocation, improve service quality, or reduce network costs. Furthermore, by collecting and analyzing information such as latency and packet loss rate, NWDAF can provide the UPF with more accurate network performance data, helping it determine network congestion in real time and optimize resource allocation to provide better service quality.

[0433] In this way, after the NWDAF reports the network performance analysis information to the UPF, the UPF can determine the appropriate bitrate from the bitrate authorization information based on the network performance analysis information. When the network performance analysis information indicates network congestion or high bandwidth utilization, the UPF can reduce the bitrate corresponding to the application data.

[0434] In addition, since the UPF adjusts the bitrate information corresponding to the current application data based on network congestion information, bandwidth usage information, or network performance analysis information, the UPF can determine whether it is necessary to subscribe to the application data corresponding to the adjusted bitrate information from the application server based on local cache information or historical application data subscription information in "Solution 3", and finally send the application data to the terminal device. Among them, if the application data is cached locally or has been subscribed to, the UPF sends the application data to the terminal device; if the application data is not cached locally or has not been subscribed to, the UPF needs to subscribe to the application data from the application server.

[0435] Of course, when UPF adjusts the bit rate information corresponding to the application data, since the adjusted bit rate information is different from the original bit rate information, before UPF sends the adjusted application data to the terminal device, UFP needs to inform the terminal device of the adjusted bit rate information in advance.

[0436] The following is an example of the process of UPF sending application data to the terminal device based on network congestion information, bandwidth usage information or network performance analysis information.

[0437] FIG10 is a flow chart of another method for transmitting application data according to an embodiment of the present application. In FIG10 , the method specifically includes the following steps:

[0438] S1001. RAN sends network congestion information or bandwidth usage information to UPF.

[0439] Correspondingly, the UPF receives network congestion information or bandwidth usage information.

[0440] S1002. NWDAF sends network performance analysis information to UPF.

[0441] Correspondingly, UPF receives network performance analysis information.

[0442] S1003. The UPF determines the bit rate information corresponding to the target application data in the bit rate authorization information based on the network congestion information, bandwidth usage information or network performance analysis information.

[0443] S1004. UPF sends the bit rate information corresponding to the target application data to the terminal device.

[0444] It should be noted that the UPF needs to first send the bit rate information corresponding to the target application data to the RAN, and then the RAN forwards it to the terminal device.

[0445] S1005. The UPF determines whether it is necessary to subscribe to the target application data from the application server based on the local cache information or the historical application data subscription information.

[0446] It should be noted that if the target application data is cached locally or has been subscribed to, S1006 is executed; if the target application data is not cached locally or has not been subscribed to, S1007 to S1011 are executed.

[0447] S1006. UPF sends target application data to the terminal device.

[0448] Correspondingly, the terminal device receives the target application data.

[0449] It should be noted that the UPF needs to first send the target application data to the RAN, and then the RAN forwards it to the terminal device.

[0450] S1007. UPF sends a subscription request message to the application server. The subscription request message is used to request subscription to target application data.

[0451] The subscription request message may include target application data and / or bit rate information actually corresponding to the target application data.

[0452] In this way, the application server obtains the target application data that the UPF needs to subscribe to and the bit rate information corresponding to the target application data through the subscription request message.

[0453] S1008. The application server sends a subscription response message to the UPF, wherein the subscription response message may include a code rate ID.

[0454] Correspondingly, UPF receives the subscription response message.

[0455] In this way, the UPF can obtain the code rate ID through the subscription response message, so as to obtain the target application data according to the code rate ID later.

[0456] S1009. UPF records and maintains the correspondence between target application data and bitrate ID.

[0457] S1010. The application server sends target application data to the UPF according to the bitrate ID.

[0458] Correspondingly, the UPF receives the target application data according to the bitrate ID.

[0459] S1011. UPF sends target application data to the terminal device.

[0460] Correspondingly, the terminal device receives the target application data.

[0461] It should be noted that the UPF needs to first send the target application data to the RAN, and then the RAN forwards it to the terminal device.

[0462] As can be seen from Figure 10, UPF adjusts the bitrate information corresponding to the target application data based on network congestion information, bandwidth usage information or network performance analysis information, and determines whether it is necessary to subscribe to the target application data corresponding to the adjusted bitrate information from the application server based on local cache information or historical application data subscription information, and finally sends the target application data to the terminal device.

[0463] A communication method

[0464] In combination with the above content, a communication method according to an embodiment of the present application is described below by way of example. It should be noted that the UPF may be a chip, a chip module, or a communication module, and the SMF may be a chip, a chip module, or a communication module, etc.

[0465] As shown in FIG11 , FIG11 is a flow chart of a communication method according to an embodiment of the present application, which specifically includes the following steps:

[0466] S1101. In response to a PDU session creation request or a PDU session modification request, the SMF obtains the bit rate authorization information sent by the AF.

[0467] S1102. SMF sends bit rate authorization information to UPF.

[0468] Correspondingly, UPF receives bit rate authorization information.

[0469] S1103. The UPF sends the target application data to the terminal device according to the bit rate authorization information. The bit rate information corresponding to the target application data is in the bit rate authorization information.

[0470] Correspondingly, the terminal device receives the target application data.

[0471] It can be seen that SMF can obtain the bit rate authorization information issued by AF in the process of PDU session creation request or PDU session modification request, and then send the bit rate authorization information to UPF, thereby assisting UPF to obtain the bit rate authorization information in the process of PDU session creation request or PDU session modification request.

[0472] In this way, the UPF can dynamically adjust and effectively control the bitrate information corresponding to the target application data based on the bitrate authorization information sent by the AF, and ensure that the bitrate information corresponding to the target application data is within the bitrate authorization information, thereby enabling the UPF to dynamically adjust and effectively control the bitrate of the application data. At the same time, compared to the application server's authentication of application-layer bitrate authorization, since the bitrate authorization information is sent to the UPF with the assistance of the SMF, the UPF performs application-layer bitrate authorization authentication based on the bitrate authorization information, thereby reducing the delay of application-layer bitrate authorization authentication.

[0473] In some possible examples, the bitrate authorization information includes at least one of the following: the maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

[0474] It should be noted that the maximum bitrate allowed for a terminal device to access an application is typically set by the application server after the terminal device successfully registers with the application server. Thus, when the terminal device requests application data from the application server, the application server can select a bitrate from the maximum bitrate allowed for the terminal device to access the application, or a bitrate below it, and provide the application data at the selected bitrate to the terminal device.

[0475] Regarding the list of bitrates allowed for terminal devices to access applications, after the terminal device successfully registers with the application server, the application server typically sets the list of bitrates allowed for terminal devices to access applications. Thus, when the terminal device requests application data from the application server, the application server can select a bitrate from the list and provide the application data at the selected bitrate to the terminal device.

[0476] For the bit rate information allowed for terminal devices to access applications within a preset time period, the application server can set the bit rate information allowed for terminal devices to access applications (such as a maximum bit rate or a bit rate list) according to different time periods. For example, in a time period with a small number of users accessing the application (such as at night), since the number of terminal devices accessing the application server during this period is usually small, the occupancy rate of bandwidth resources is low or the congestion rate presented by the network status is low, etc., the application server can set the maximum bit rate allowed for terminal devices to access applications during this period to be larger or the bit rates available for selection in the bit rate list to be more. However, in a time period with a large number of users accessing the application (such as during the day), since the number of terminal devices accessing the application server during this period is usually large, the occupancy rate of bandwidth resources is high or the congestion rate presented by the network status is high, etc., the application server can set the maximum bit rate allowed for terminal devices to access applications during this period to be smaller or the bit rates available for selection in the bit rate list to be fewer. In this way, the bit rate information allowed for terminal devices to access applications can be flexibly set according to the time period.

[0477] Regarding the bitrate information allowed for terminal devices to access applications within a preset location area, the application server can set the bitrate information allowed for terminal devices to access applications (such as a maximum bitrate or a bitrate list) based on the location area. For example, in densely populated locations (such as business districts), since the number of terminal devices accessing application servers in these locations is generally large, resulting in a higher bandwidth resource utilization rate or a higher network congestion rate, the application server can set a smaller maximum bitrate allowed for terminal devices to access applications within these location areas or a smaller number of available bitrates in the bitrate list.

[0478] In some possible examples, the code rate authorization information is carried by an N4 session creation request message or an N4 session modification request message.

[0479] It should be noted that the N4 session creation process is used to create the initial N4 session context for the PDU session in the UPF. The SMF allocates a new N4 session ID and provides it to the UPF, and sends an N4 session creation request message to the UPF. Therefore, during the N4 session creation process, the SMF can send rate authorization information to the UPF via the N4 session creation request message so that the UPF can obtain the rate authorization information.

[0480] In addition, the N4 Session Modification procedure is used to update the N4 Session Context of an existing PDU Session at the UPF. It is performed between the SMF and the UPF when PDU Session-related parameters need to be modified. The SMF sends an N4 Session Modification Request message to the UPF. Therefore, during the N4 Session creation process, the SMF can send the rate authorization information to the UPF via the N4 Session Modification Request message so that the UPF can obtain the rate authorization information.

[0481] In some possible examples, before sending the target application data bit rate authorization information to the terminal device according to the bit rate authorization information, the method further includes: obtaining application data request information of the terminal device.

[0482] It should be noted that after the UPF obtains the bitrate authorization information, the terminal device can request the application data content it needs, such as videos, images, music, or other media resources. The terminal device's application data request can be generated based on user operations or internal application logic to meet user needs and obtain the required application data. In this way, the UPF can obtain the terminal device's application data request information.

[0483] In some possible examples, obtaining application data request information of a terminal device includes: receiving application data request information of the terminal device from an access network device.

[0484] It should be noted that the terminal device can request application data through application layer messages, and forward the application data request information of the terminal device to the UPF via RAN, so that the UPF obtains the application data request information of the terminal device. Finally, the UPF processes the application data request information of the terminal device according to the bit rate authorization information and sends the application data to the terminal device.

[0485] In some possible examples, obtaining application data request information of a terminal device includes: receiving application data request information from an SMF.

[0486] It should be noted that the terminal device can request application data through the control plane message, and send the application data request information of the terminal device to the UPF through the AMF and SMF, so that the UPF obtains the application data request information of the terminal device. Finally, the UPF processes the application data request information of the terminal device according to the bit rate authorization information and sends the application data to the terminal device.

[0487] In some possible examples, the application data request information includes target application data requested by the terminal device; and sending the target application data to the terminal device according to the bit rate authorization information includes:

[0488] In response to the application data request information, determining the bit rate information corresponding to the target application data in the bit rate authorization information;

[0489] If the target application data is cached locally or has been subscribed to, the target application data is sent to the terminal device;

[0490] If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to the subscription request message, which is used to request the application server to subscribe to the target application data.

[0491] It should be noted that if the application data request information includes the target application data requested by the terminal device, the UPF can determine the bit rate information corresponding to the target application data in the bit rate authorization information in response to the application data request information. That is to say, when the user does not specify the bit rate corresponding to the application data, the UPF can select a bit rate in the bit rate authorization information. In this way, the UPF can authenticate the application layer bit rate authorization of the target application data requested by the terminal device based on the bit rate authorization information, thereby reducing the delay of the application layer bit rate authorization authentication. At the same time, the UPF can determine whether it is necessary to subscribe to the application data from the application server based on the local cache situation or historical application data subscription information, and provide the target application data to the terminal device, so as to avoid the application server directly sending the target application data to the terminal device to reduce the delay required for the overall transmission of the target application data, and reduce the export bandwidth pressure of the application server when the terminal device requests the target application data (especially the target application data with a higher bit rate) from the application server.

[0492] In some possible examples, the application data request information includes target application data requested by the terminal device and bit rate information requested by the terminal device;

[0493] Send target application data to the terminal device based on the bitrate authorization information, including:

[0494] If the bitrate information requested by the terminal device is in the bitrate authorization information, the bitrate information requested by the terminal device is used as the bitrate information corresponding to the target application data;

[0495] If the bit rate information requested by the terminal device is not in the bit rate authorization information, the bit rate information corresponding to the target application data is determined in the bit rate authorization information;

[0496] If the target application data is cached locally or has been subscribed to, the target application data is sent to the terminal device;

[0497] If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to the subscription request message, which is used to request the application server to subscribe to the target application data.

[0498] It should be noted that if the application data request information includes the target application data requested by the terminal device and the bitrate information requested by the terminal device, the UPF needs to determine whether the bitrate information requested by the terminal device can be authorized based on the bitrate authorization information. When the bitrate information requested by the terminal device is within the bitrate authorization information, this indicates that the bitrate information requested by the terminal device can be authorized, and the bitrate information requested by the terminal device is used as the bitrate information actually corresponding to the target application data. When the bitrate information requested by the terminal device is not within the bitrate authorization information, this indicates that the bitrate information requested by the terminal device has not been authorized, and the UPF needs to determine the bitrate information actually corresponding to the target application data within the bitrate authorization information. At the same time, the UPF can determine whether it is necessary to subscribe to application data from the application server based on the local cache status or historical application data subscription information, and provide the target application data to the terminal device, avoiding the application server directly sending the target application data to the terminal device to reduce the delay required for the overall transmission of the target application data, thereby reducing the application server's egress bandwidth pressure when the terminal device requests the target application data from the application server (especially when requesting target application data with a higher bitrate).

[0499] In some possible examples, sending target application data to the terminal device according to the subscription request message includes:

[0500] Send a subscription request message to the application server;

[0501] receiving target application data from an application server;

[0502] Send target application data to the terminal device.

[0503] It should be noted that the UPF can request the target application data by sending a subscription request message to the application server. In this way, the application server obtains the application data that the UPF needs to subscribe to and the bit rate information corresponding to the application data through the subscription request message, and sends the target application data to the UPF.

[0504] In some possible examples, receiving target application data from an application server includes:

[0505] Receive a subscription response message from the application server, where the subscription response message includes a bitrate identifier ID;

[0506] Record and maintain the correspondence between target application data and bitrate ID;

[0507] receiving target application data from the application server according to the bitrate ID;

[0508] It should be noted that before the application server sends the target application data, the application server can send the bitrate ID to the UPF so that the UPF can record and maintain the correspondence between the target application data and the bitrate ID and use it as a local cache. The application server can then send the target application data based on the bitrate ID, and the UPF can receive the target application data based on the bitrate ID.

[0509] In some possible examples, before sending the target application data to the terminal device, the method further includes:

[0510] Send the bitrate information corresponding to the target application data to the terminal device.

[0511] It should be noted that when the terminal device does not request the bitrate information corresponding to the target application data, the UPF can determine the bitrate information corresponding to the target application data based on the bitrate authorization information and then inform the terminal device. When the terminal device requests the bitrate information corresponding to the target data, since the actual bitrate information determined by the UPF based on the bitrate authorization information may be different from the bitrate information requested by the terminal device, the UFP needs to inform the terminal device of the actual bitrate information in advance before the UPF sends the application data to the terminal device.

[0512] The above mainly introduces the solution of the embodiment of the present application from the perspective of the method side. The following is an example of the functional unit of a communication device of this embodiment. It can be understood that in order to implement the above functions, the UPF includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiment disclosed herein, this embodiment 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. Those skilled in the art 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 embodiment.

[0513] In the embodiments of the present application, the UPF can be divided into functional units according to the above-described method examples. For example, each functional unit can be divided according to its function, or two or more functions can be integrated into a single processing unit. The above-mentioned integrated units can be implemented in the form of hardware or software program modules. It should be noted that the division of units in the embodiments of the present application is illustrative and is only a logical functional division. In actual implementation, other division methods may be used.

[0514] In the case of using integrated units, FIG12 is a block diagram of the functional units of a communication device according to an embodiment of the present application, wherein the communication device 1200 includes a receiving unit 1201 and a sending unit 1202 .

[0515] Optionally, the receiving unit 1201 may be a module unit for receiving and processing signals, information, etc., and there is no specific limitation on this.

[0516] Optionally, the sending unit 1202 may be a module unit for sending and processing signals, information, etc., and there is no specific limitation on this.

[0517] Optionally, the communication device 1200 may further include a storage unit for storing computer program codes or instructions executed by the communication device 1200. The storage unit may be a memory.

[0518] Optionally, the communication device 1200 may be a chip or a chip module.

[0519] Optionally, the receiving unit 1201 and the sending unit 1202 may be integrated into the same unit or into different units.

[0520] For example, the receiving unit 1201 and the sending unit 1202 may be integrated into a communication unit, wherein the communication unit may be a communication interface, a transceiver, a transceiver circuit, etc.

[0521] Optionally, the communication device 1200 may further include a processing unit.

[0522] It should be noted that the processing unit can be a processor or controller, for example, a baseband processor, a baseband chip, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It can implement or execute the various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this embodiment. The processing unit can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0523] Optionally, the communication device 1200 is used to execute any step performed by the UPF / chip / chip module, etc. in the above method embodiment.

[0524] In specific implementation, the receiving unit 1201 and the sending unit 1202 are used to execute any step in the above method embodiment, and when executing an action such as sending, other units may be selectively called to complete the corresponding operation.

[0525] The receiving unit 1201 is configured to receive bit rate authorization information from the SMF, where the bit rate authorization information refers to bit rate information allowed for a terminal device to access an application;

[0526] The sending unit 1202 is configured to send target application data to the terminal device according to the bit rate authorization information, where the bit rate information corresponding to the target application data is in the bit rate authorization information.

[0527] As can be seen, this embodiment considers using the SMF to assist the UPF in obtaining the bitrate authorization information issued by the AF. In this way, the UPF can dynamically adjust and effectively control the bitrate information corresponding to the target application data based on the bitrate authorization information issued by the AF, and ensure that the bitrate information corresponding to the target application data is within the bitrate authorization information, thereby enabling the UPF to dynamically adjust and effectively control the bitrate of the application data. At the same time, compared to the application server's authentication of application-layer bitrate authorization, since the bitrate authorization information is issued to the UPF with the assistance of the SMF, the UPF performs application-layer bitrate authorization authentication based on the bitrate authorization information, thereby reducing the delay of application-layer bitrate authorization authentication.

[0528] It should be noted that the specific implementation of each operation in the embodiment shown in Figure 12 can be found in the description of the method embodiment shown above, and will not be detailed here.

[0529] In some possible examples, the bit rate authorization information includes at least one of the following:

[0530] The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

[0531] In some possible examples, the code rate authorization information is carried by an N4 session creation request message or an N4 session modification request message.

[0532] In some possible examples, before sending the target application data bit rate authorization information to the terminal device according to the bit rate authorization information, the receiving unit 1201 is further configured to obtain application data request information of the terminal device.

[0533] In some possible examples, in terms of obtaining application data request information of a terminal device, the receiving unit 1201 is configured to:

[0534] Receiving application data request information from a terminal device of an access network device; or,

[0535] Receive application data request information from SMF.

[0536] In some possible examples, the application data request information includes target application data requested by the terminal device; in terms of sending the target application data to the terminal device according to the bit rate authorization information, the sending unit 1202 is configured to:

[0537] In response to the application data request information, determining the bit rate information corresponding to the target application data in the bit rate authorization information;

[0538] If the target application data is cached locally or has been subscribed to, the target application data is sent to the terminal device;

[0539] If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to the subscription request message, which is used to request the application server to subscribe to the target application data.

[0540] In some possible examples, the application data request information includes target application data requested by the terminal device and bit rate information requested by the terminal device;

[0541] In terms of sending target application data to the terminal device according to the bit rate authorization information, the sending unit 1202 is used to:

[0542] If the bitrate information requested by the terminal device is in the bitrate authorization information, the bitrate information requested by the terminal device is used as the bitrate information corresponding to the target application data;

[0543] If the bit rate information requested by the terminal device is not in the bit rate authorization information, the bit rate information corresponding to the target application data is determined in the bit rate authorization information;

[0544] If the target application data is cached locally or has been subscribed to, the target application data is sent to the terminal device;

[0545] If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to the subscription request message, which is used to request the application server to subscribe to the target application data.

[0546] In some possible examples, in terms of sending target application data to the terminal device according to the subscription request message,

[0547] The sending unit 1202 is configured to send a subscription request message to the application server;

[0548] The receiving unit 1201 is configured to receive target application data from an application server;

[0549] The sending unit 1202 is configured to send target application data to the terminal device.

[0550] In some possible examples, in receiving target application data from an application server, the receiving unit 1201 is configured to:

[0551] Receive a subscription response message from the application server, where the subscription response message includes a bitrate identifier ID;

[0552] Record and maintain the correspondence between target application data and bitrate ID;

[0553] receiving target application data from the application server according to the bitrate ID;

[0554] In some possible examples, before sending the target application data to the terminal device, the sending unit 1202 is configured to:

[0555] Send the bitrate information corresponding to the target application data to the terminal device.

[0556] The above mainly introduces the solution of the embodiment of the present application from the perspective of the method side. The following is an example of the functional unit of another communication device of this embodiment. It can be understood that in order to realize the above functions, the SMF includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiment disclosed in this document, this embodiment 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. Those skilled in the art 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 embodiment.

[0557] The embodiments of the present application can divide the SMF into functional units according to the above-mentioned method examples. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into a processing unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software program modules. It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical functional division. In actual implementation, other division methods can be used.

[0558] In the case of using integrated units, FIG13 is a block diagram of functional units of another communication device according to an embodiment of the present application, wherein the communication device 1300 includes an acquiring unit 1301 and a sending unit 1302 .

[0559] Optionally, the acquisition unit 1301 may be a module unit for acquiring and processing signals, information, etc., and there is no specific limitation on this.

[0560] Optionally, the sending unit 1302 may be a module unit for sending and processing signals, information, etc., and there is no specific limitation on this.

[0561] Optionally, the communication device 1300 may further include a storage unit for storing computer program codes or instructions executed by the communication device 1300. The storage unit may be a memory.

[0562] Optionally, the communication device 1300 may be a chip or a chip module.

[0563] Optionally, the acquiring unit 1301 and the sending unit 1302 may be integrated into a communication unit, wherein the communication unit may be a communication interface, a transceiver, a transceiver circuit, etc.

[0564] Optionally, the communication device 1300 may further include a processing unit.

[0565] It should be noted that the processing unit can be a processor or controller, for example, a baseband processor, a baseband chip, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It can implement or execute the various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this embodiment. The processing unit can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0566] Optionally, the communication device 1300 is used to execute any step executed by the chip / chip module / SMF, etc. in the above method embodiment.

[0567] In specific implementation, the acquisition unit 1301 and the sending unit 1302 are used to execute any step in the above method embodiment, and when executing an action such as sending, other units may be selectively called to complete the corresponding operation.

[0568] The acquiring unit 1301 is configured to acquire the bitrate authorization information issued by the AF in response to a PDU session creation request or a PDU session modification request, where the bitrate authorization information refers to the bitrate information allowed for the terminal device to access the application;

[0569] The sending unit 1302 is used to send the bit rate authorization information to the UPF.

[0570] It can be seen that this embodiment can obtain the bit rate authorization information issued by the AF in the process of the PDU session creation request or the PDU session modification request, and then send the bit rate authorization information to the UPF, thereby assisting the UPF to obtain the bit rate authorization information in the process of the PDU session creation request or the PDU session modification request.

[0571] In some possible examples, the bit rate authorization information includes at least one of the following:

[0572] The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

[0573] In some possible examples, in obtaining the bit rate authorization information issued by the AF,

[0574] The sending unit 1302 is configured to send a first request message to the NEF, where the first request message is used to request the NEF to query the UDR for the bit rate authorization information issued by the AF;

[0575] The acquiring unit 1301 is configured to receive a first response message from the NEF, where the first response message includes bit rate authorization information.

[0576] In some possible examples, in obtaining the bit rate authorization information issued by the AF,

[0577] The sending unit 1302 is configured to send a second request message to the PCF, where the second request message is used to request the PCF to query the UDR for the bit rate authorization information issued by the AF;

[0578] The acquiring unit 1301 is configured to receive a second response message from the PCF, where the second response message includes bit rate authorization information.

[0579] In some possible examples, before obtaining the bit rate authorization information sent by the AF, the obtaining unit 1301 is configured to:

[0580] Receive a session management SM context request message or SM context update request message from the mobility management function gateway AMF, where the SM context request message or SM context update request message contains application data request information of the terminal device.

[0581] In some possible examples, in terms of sending the bit rate authorization information to the UPF, the sending unit 1302 is configured to:

[0582] If the SM context request message includes application data request information, an N4 session creation request message is sent to the UPF, where the N4 session creation request message includes application data request information; or

[0583] If the SM context update request message includes application data request information, an N4 session modification request message is sent to the UPF, and the N4 session modification request message includes application data request information.

[0584] In some possible examples, the data request information includes target application data requested by the terminal device and / or bit rate information requested by the terminal device.

[0585] The above mainly introduces the solution of the embodiment of the present application from the perspective of the method side. The following is an example of the functional unit of a communication device of this embodiment. It can be understood that in order to implement the above functions, the UPF includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiment disclosed herein, this embodiment 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. Those skilled in the art 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 embodiment.

[0586] In the embodiments of the present application, the UPF can be divided into functional units according to the above-described method examples. For example, each functional unit can be divided according to its function, or two or more functions can be integrated into a single processing unit. The above-mentioned integrated units can be implemented in the form of hardware or software program modules. It should be noted that the division of units in the embodiments of the present application is illustrative and is only a logical functional division. In actual implementation, other division methods may be used.

[0587] In the case of using integrated units, FIG14 is a block diagram of functional units of another communication device according to an embodiment of the present application, wherein the communication device 1400 includes a receiving unit 1401 and a sending unit 1402 .

[0588] Optionally, the receiving unit 1401 may be a module unit for receiving and processing signals, information, etc., and there is no specific limitation on this.

[0589] Optionally, the sending unit 1402 may be a module unit for sending and processing signals, information, etc., and there is no specific limitation on this.

[0590] Optionally, the communication device 1400 may further include a storage unit for storing computer program codes or instructions executed by the communication device 1400. The storage unit may be a memory.

[0591] Optionally, the communication device 1400 may be a chip or a chip module.

[0592] Optionally, the receiving unit 1401 and the sending unit 1402 may be integrated into the same unit or into different units.

[0593] For example, the receiving unit 1401 and the sending unit 1402 may be integrated into a communication unit, wherein the communication unit may be a communication interface, a transceiver, a transceiver circuit, etc.

[0594] Optionally, the communication device 1400 may further include a processing unit.

[0595] It should be noted that the processing unit can be a processor or controller, for example, a baseband processor, a baseband chip, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It can implement or execute the various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this embodiment. The processing unit can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0596] Optionally, the communication device 1400 is used to execute any step performed by the UPF / chip / chip module, etc. in the above method embodiment.

[0597] In specific implementation, the receiving unit 1401 and the sending unit 1402 are used to execute any step in the above method embodiment, and when executing an action such as sending, other units may be selectively called to complete the corresponding operation.

[0598] The receiving unit 1401 is configured to receive network congestion information or bandwidth usage information from an access network device, or receive network performance analysis information from an NWDAF;

[0599] The sending unit 1402 is used to send target application data to the terminal device based on network congestion information, bandwidth usage information or network performance analysis information. The bit rate information corresponding to the target application data is in the bit rate authorization information. The bit rate authorization information refers to the bit rate information allowed for the terminal device to access the application.

[0600] It can be seen that this embodiment can adjust the bit rate information corresponding to the target application data based on network congestion information, bandwidth usage information or network performance analysis information, and the adjusted bit rate information is included in the bit rate authorization information, and then the target application data is sent to the terminal device, thereby achieving bit rate adjustment.

[0601] It should be noted that the specific implementation of each operation in the embodiment described in FIG14 can be found in the description of the method embodiment shown above, and will not be described in detail here.

[0602] In some possible examples, the bit rate authorization information includes at least one of the following:

[0603] The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

[0604] In some possible examples, in terms of sending target application data to the terminal device based on network congestion information, bandwidth usage information, or network performance analysis information, the sending unit 1402 is configured to:

[0605] Determining the bitrate information corresponding to the target application data in the bitrate authorization information based on network congestion information, bandwidth usage information, or network performance analysis information;

[0606] If the target application data is cached locally or has been subscribed to, the target application data is sent to the terminal device;

[0607] If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to the subscription request message, which is used to request the application server to subscribe to the target application data.

[0608] In some possible examples, in terms of sending target application data to the terminal device according to the subscription request message,

[0609] The sending unit 1402 is configured to send a subscription request message to the application server;

[0610] Receiving unit 1401, configured to receive target application data from an application server;

[0611] The sending unit 1402 is configured to send target application data to the terminal device.

[0612] In some possible examples, in terms of receiving target application data from the application server, the receiving unit 1401 is configured to:

[0613] Receive a bitrate identifier ID from an application server;

[0614] Record and maintain the correspondence between target application data and bitrate ID;

[0615] receiving target application data from the application server according to the bitrate ID;

[0616] In some possible examples, before sending the target application data to the terminal device, the sending unit 1402 is configured to:

[0617] Send the bitrate information corresponding to the target application data to the terminal device.

[0618] In some possible examples, before sending target application data to the terminal device according to the network congestion information, bandwidth usage information, or network performance analysis information, the receiving unit 1401 is configured to:

[0619] Receive bit rate authorization information from the SMF network element.

[0620] In some possible examples, the code rate authorization information is carried by an N4 session creation request message or an N4 session modification request message.

[0621] The structure of a UPF in this embodiment is described below by way of example.

[0622] Please refer to Figure 15, which is a schematic diagram of the structure of a UPF according to an embodiment of the present application. The UPF 1500 may include a processor 1510, a memory 1520, and a communication bus for connecting the processor 1510 and the memory 1520.

[0623] Optionally, the memory 1520 includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or portable read-only memory (CD-ROM), and the memory 1520 is used to store the program code executed by UPF1500 and the transmitted data.

[0624] Optionally, UPF 1500 further includes a communication interface for receiving and sending data.

[0625] Optionally, UPF 1500 may be the first UPF described above.

[0626] Optionally, the processor 1510 may be one or more CPUs. In the case where the processor 1510 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0627] Optionally, the processor 1510 may be a baseband chip, a chip, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof.

[0628] In a specific implementation, the processor 1510 in the UPF 1500 is configured to execute a computer program or instruction 1521 stored in the memory 1520 to perform the following operations:

[0629] Receive the bitrate authorization information from the SMF. The bitrate authorization information refers to the bitrate information allowed for the terminal device to access the application.

[0630] The target application data is sent to the terminal device according to the bit rate authorization information, and the bit rate information corresponding to the target application data is in the bit rate authorization information.

[0631] As can be seen, this embodiment considers using the SMF to assist the UPF in obtaining the bitrate authorization information issued by the AF. In this way, the UPF can dynamically adjust and effectively control the bitrate information corresponding to the target application data based on the bitrate authorization information issued by the AF, and ensure that the bitrate information corresponding to the target application data is within the bitrate authorization information, thereby enabling the UPF to dynamically adjust and effectively control the bitrate of the application data. At the same time, compared to the application server's authentication of application-layer bitrate authorization, since the bitrate authorization information is issued to the UPF with the assistance of the SMF, the UPF performs application-layer bitrate authorization authentication based on the bitrate authorization information, thereby reducing the delay of application-layer bitrate authorization authentication.

[0632] It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above. UPF 1500 can be used to execute the above method embodiment of this embodiment, which will not be repeated here.

[0633] The following is an example of the structure of an SMF in this embodiment.

[0634] Please refer to FIG16 , which is a schematic diagram of the structure of an SMF according to an embodiment of the present application, wherein the SMF 1600 may include a processor 1610 , a memory 1620 , and a communication bus for connecting the processor 1610 and the memory 1620 .

[0635] Optionally, the memory 1620 includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or portable read-only memory (CD-ROM), and the memory 1620 is used to store the program code executed by SMF1600 and the data transmitted.

[0636] Optionally, SMF 1600 also includes a communication interface for receiving and sending data.

[0637] Optionally, SMF 1600 may be the first SMF mentioned above.

[0638] Optionally, the processor 1610 may be one or more CPUs. When the processor 1610 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0639] Optionally, the processor 1610 may be a baseband chip, a chip, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof.

[0640] In a specific implementation, the processor 1610 in the SMF 1600 is configured to execute a computer program or instruction 1621 stored in the memory 1620 to perform the following operations:

[0641] In response to a PDU session creation request or a PDU session modification request, obtain the bitrate authorization information issued by the AF. The bitrate authorization information refers to the bitrate information allowed for the terminal device to access the application.

[0642] Send bitrate authorization information to UPF.

[0643] It can be seen that this embodiment can obtain the bit rate authorization information issued by the AF in the process of the PDU session creation request or the PDU session modification request, and then send the bit rate authorization information to the UPF, thereby assisting the UPF to obtain the bit rate authorization information in the process of the PDU session creation request or the PDU session modification request.

[0644] It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above, and SMF 1600 can be used to execute the above method embodiment of this embodiment, which will not be repeated here.

[0645] The structure of another UPF of this embodiment is described below by way of example.

[0646] Please refer to Figure 17, which is a schematic diagram of the structure of a UPF according to an embodiment of the present application. The UPF 1700 may include a processor 1710, a memory 1720, and a communication bus for connecting the processor 1710 and the memory 1720.

[0647] Optionally, the memory 1720 includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or portable read-only memory (CD-ROM), and the memory 1720 is used to store the program code executed by UPF1700 and the transmitted data.

[0648] Optionally, UPF 1700 further includes a communication interface for receiving and sending data.

[0649] Optionally, UPF 1700 may be the first UPF described above.

[0650] Optionally, the processor 1710 may be one or more CPUs. In the case where the processor 1710 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0651] Optionally, the processor 1710 may be a baseband chip, a chip, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a transistor logic device, a hardware component or any combination thereof.

[0652] In a specific implementation, the processor 1710 in the UPF 1700 is configured to execute a computer program or instruction 1721 stored in the memory 1720 to perform the following operations:

[0653] Receive network congestion information or bandwidth usage information from access network devices, or receive network performance analysis information from NWDAF;

[0654] The target application data is sent to the terminal device based on network congestion information, bandwidth usage information or network performance analysis information. The bit rate information corresponding to the target application data is in the bit rate authorization information. The bit rate authorization information refers to the bit rate information allowed for the terminal device to access the application.

[0655] It can be seen that UPF can adjust the bitrate information corresponding to the target application data based on network congestion information, bandwidth usage information or network performance analysis information, and the adjusted bitrate information is included in the bitrate authorization information, and then the target application data is sent to the terminal device, thereby achieving bitrate adjustment.

[0656] It should be noted that the specific implementation of each operation can adopt the corresponding description of the method embodiment shown above. UPF 1700 can be used to execute the above method embodiment of this embodiment, which will not be repeated here.

[0657] Other relevant contents of this embodiment are described below with examples.

[0658] An embodiment of the present application also provides a chip, including a processor, a memory, and a computer program or instructions stored in the memory, wherein the processor executes the computer program or instructions to implement the steps described in the above method embodiment.

[0659] An embodiment of the present application also provides a chip module, including a transceiver component and a chip, wherein the chip includes a processor, a memory, and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to implement the steps described in the above method embodiment.

[0660] An embodiment of the present application further provides a computer-readable storage medium storing a computer program or instructions, which implements the steps described in the above method embodiment when executed.

[0661] An embodiment of the present application further provides a computer program product, including a computer program or instructions, which implement the steps described in the above method embodiment when executed.

[0662] It should be noted that, for the above-mentioned various embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations. Those skilled in the art should know that this application is not limited by the order of the actions described, because some steps in the embodiments of the present application can be performed in other orders or simultaneously. In addition, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions, steps, modules or units involved are not necessarily required by the embodiments of the present application.

[0663] In the above embodiments, the embodiments of the present application have different focuses on the description of each embodiment. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0664] The steps of the method or algorithm described in the embodiments of the present application can be implemented in hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a terminal device or a management device. Of course, the processor and storage medium can also be present in a terminal device or a management device as discrete components.

[0665] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part 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, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can 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 can 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 can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available 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 digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0666] The modules / units included in the devices and products described in the above embodiments may be software modules / units, hardware modules / units, or partly software modules / units and partly hardware modules / units. For example, for the devices and products applied to or integrated in the chip, the modules / units included therein may all be implemented in the form of hardware such as circuits, or at least part of the modules / units may be implemented in the form of software programs, which run on the processor integrated inside the chip, and the remaining (if any) modules / units may be implemented in the form of hardware such as circuits; for the devices and products applied to or integrated in the chip module, the modules / units included therein may all be implemented in the form of hardware such as circuits, and different modules / units may be located in the same component (such as chip, circuit module, etc.) or different components of the chip module, or at least part of the modules / units may be It is implemented in the form of a software program, which runs on the processor integrated inside the chip module, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits; for various devices and products applied to or integrated in the terminal equipment, the various modules / units contained therein can be implemented in the form of hardware such as circuits, and different modules / units can be located in the same component (for example, chip, circuit module, etc.) or different components in the terminal equipment, or, at least some modules / units can be implemented in the form of a software program, which runs on the processor integrated inside the terminal equipment, and the remaining (if any) modules / units can be implemented in the form of hardware such as circuits.

[0667] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the embodiments of the present application. It should be understood that the above description is only a specific implementation method of the embodiments of the present application and is not intended to limit the scope of protection of the embodiments of the present application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application should be included in the scope of protection of the embodiments of the present application.

Claims

1. A communication method, characterized in that: Applied to a first communication device, the method includes: Receive bitrate authorization information from the session management function (SMF) network element, where the bitrate authorization information refers to the bitrate information allowed for the terminal device to access the application; The target application data is sent to the terminal device according to the bit rate authorization information, and the bit rate information corresponding to the target application data is in the bit rate authorization information.

2. The method according to claim 1, characterized in that The bit rate authorization information includes at least one of the following: The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

3. The method according to claim 1, characterized in that The code rate authorization information is carried by an N4 session creation request message or an N4 session modification request message.

4. The method according to claim 1, wherein Before sending the target application data bit rate authorization information to the terminal device according to the bit rate authorization information, the method further includes: Get application data request information of the terminal device.

5. The method according to claim 4, characterized in that The obtaining of application data request information of the terminal device includes: Receiving application data request information from a terminal device of an access network device; or, Receive the application data request information from SMF.

6. The method according to claim 4, characterized in that The application data request information includes the target application data requested by the terminal device; The sending target application data to the terminal device according to the bit rate authorization information includes: In response to the application data request information, determining bit rate information corresponding to the target application data in the bit rate authorization information; If the target application data is cached locally or has been subscribed to, sending the target application data to the terminal device; If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to a subscription request message, where the subscription request message is used to request the application server to subscribe to the target application data.

7. The method according to claim 4, characterized in that The application data request information includes the target application data requested by the terminal device and the bit rate information requested by the terminal device; The sending target application data to the terminal device according to the bit rate authorization information includes: If the bit rate information requested by the terminal device is in the bit rate authorization information, the bit rate information requested by the terminal device is used as the bit rate information corresponding to the target application data; If the bit rate information requested by the terminal device is not in the bit rate authorization information, determining the bit rate information corresponding to the target application data in the bit rate authorization information; If the target application data is cached locally or has been subscribed to, sending the target application data to the terminal device; If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to a subscription request message, where the subscription request message is used to request the application server to subscribe to the target application data.

8. The method according to claim 6 or 7, characterized in that The sending the target application data to the terminal device according to the subscription request message includes: Send a subscription request message to the application server; receiving the target application data from an application server; Send the target application data to the terminal device.

9. The method according to claim 8, characterized in that The receiving the target application data from the application server includes: Receiving a subscription response message from the application server, wherein the subscription response message includes a code rate identifier ID; Recording and maintaining the correspondence between the target application data and the bitrate ID; The target application data is received from an application server according to the bitrate ID.

10. The method according to claim 8, characterized in that Before sending the target application data to the terminal device, the method further includes: Send the bit rate information corresponding to the target application data to the terminal device.

11. A communication method, characterized in that: Applied to a second communication device, the method includes: In response to a protocol data unit (PDU) session creation request or a PDU session modification request, obtain bitrate authorization information issued by the application function network element (AF), where the bitrate authorization information refers to bitrate information allowed for the terminal device to access the application; The bit rate authorization information is sent to the user plane function network element UPF.

12. The method according to claim 11, characterized in that The bit rate authorization information includes at least one of the following: The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

13. The method according to claim 11, characterized in that The obtaining of the bit rate authorization information issued by the AF includes: Sending a first request message to the network open function network element NEF, wherein the first request message is used to request the NEF to query the unified database network element UDR for the bit rate authorization information issued by the AF; A first response message is received from the NEF, where the first response message includes the bit rate authorization information.

14. The method according to claim 12, characterized in that The obtaining of the bit rate authorization information issued by the AF includes: Sending a second request message to the policy control function network element PCF, where the second request message is used to request the PCF to query the UDR for the bit rate authorization information issued by the AF; A second response message is received from the PCF, where the second response message includes the bit rate authorization information.

15. The method according to any one of claims 12 to 14, characterized in that: Before obtaining the bit rate authorization information issued by the AF, the method further includes: Receive a session management SM context request message or an SM context update request message from the mobility management function gateway AMF, where the SM context request message or the SM context update request message includes application data request information of the terminal device.

16. The method according to claim 15, characterized in that The sending the bit rate authorization information to the UPF includes: If the SM context request message includes the application data request information, an N4 session creation request message is sent to the UPF, where the N4 session creation request message includes the application data request information; or If the SM context update request message includes the application data request information, an N4 session modification request message is sent to the UPF, where the N4 session modification request message includes the application data request information.

17. The method according to claim 16, characterized in that The data request information includes target application data requested by the terminal device and / or bit rate information requested by the terminal device.

18. A communication method, characterized in that: Applied to a first communication device, the method includes: Receive network congestion information or bandwidth usage information from access network equipment, or receive network performance analysis information from the network data analysis function network element NWDAF; The target application data is sent to the terminal device according to the network congestion information, the bandwidth usage information or the network performance analysis information. The bit rate information corresponding to the target application data is in the bit rate authorization information. The bit rate authorization information refers to the bit rate information allowed for the terminal device to access the application.

19. The method according to claim 18, characterized in that The bit rate authorization information includes at least one of the following: The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

20. The method according to claim 18, wherein The sending target application data to the terminal device according to the network congestion information, the bandwidth usage information, or the network performance analysis information includes: Determining bitrate information corresponding to target application data in the bitrate authorization information according to the network congestion information, the bandwidth usage information, or the network performance analysis information; If the target application data is cached locally or has been subscribed to, sending the target application data to the terminal device; If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to a subscription request message, where the subscription request message is used to request the application server to subscribe to the target application data.

21. The method according to claim 20, characterized in that The sending the target application data to the terminal device according to the subscription request message includes: Send a subscription request message to the application server; receiving the target application data from an application server; Send the target application data to the terminal device.

22. The method according to claim 21, characterized in that The receiving the target application data from the application server includes: Receive a bitrate identifier ID from an application server; Recording and maintaining the correspondence between the target application data and the bitrate ID; The target application data is received from an application server according to the bitrate ID.

23. The method according to claim 20 or 21, characterized in that Before sending the target application data to the terminal device, the method further includes: Send the bit rate information corresponding to the target application data to the terminal device.

24. The method according to any one of claims 18 to 23, characterized in that Before sending the target application data to the terminal device according to the network congestion information, the bandwidth usage information, or the network performance analysis information, the method further includes: Receive bit rate authorization information from the SMF network element.

25. The method according to claim 18, wherein The code rate authorization information is carried by an N4 session creation request message or an N4 session modification request message.

26. A communication device, characterized in that: include: A receiving unit, configured to receive bit rate authorization information from a session management function network element SMF, wherein the bit rate authorization information refers to bit rate information allowed for a terminal device to access an application; The sending unit is used to send target application data to the terminal device according to the bit rate authorization information, and the bit rate information corresponding to the target application data is in the bit rate authorization information.

27. The device according to claim 26, characterized in that The bit rate authorization information includes at least one of the following: The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

28. The device according to claim 26, characterized in that The bit rate authorization information is carried by an N4 session creation request message or an N4 session modification request message.

29. The device according to claim 26, characterized in that Before sending the target application data bit rate authorization information to the terminal device according to the bit rate authorization information, The receiving unit is further configured to obtain application data request information from the terminal device.

30. The device according to claim 29, characterized in that In terms of obtaining application data request information of a terminal device, the receiving unit is configured to: Receiving application data request information from a terminal device of an access network device; or, Receive the application data request information from SMF.

31. The device according to claim 29, characterized in that The application data request information includes the target application data requested by the terminal device; In the aspect of sending the target application data to the terminal device according to the bit rate authorization information, the sending unit is configured to: In response to the application data request information, determining bit rate information corresponding to the target application data in the bit rate authorization information; If the target application data is cached locally or has been subscribed to, sending the target application data to the terminal device; If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to a subscription request message, where the subscription request message is used to request the application server to subscribe to the target application data.

32. The device according to claim 29, characterized in that The application data request information includes the target application data requested by the terminal device and the bit rate information requested by the terminal device; In the aspect of sending the target application data to the terminal device according to the bit rate authorization information, the sending unit is configured to: If the bit rate information requested by the terminal device is in the bit rate authorization information, the bit rate information requested by the terminal device is used as the bit rate information corresponding to the target application data; If the bit rate information requested by the terminal device is not in the bit rate authorization information, determining the bit rate information corresponding to the target application data in the bit rate authorization information; If the target application data is cached locally or has been subscribed to, sending the target application data to the terminal device; If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to a subscription request message, where the subscription request message is used to request the application server to subscribe to the target application data.

33. The device according to claim 31 or 32, characterized in that In the aspect of sending the target application data to the terminal device according to the subscription request message, The sending unit is used to send a subscription request message to the application server; The receiving unit is configured to receive the target application data from an application server; The sending unit is further configured to send the target application data to the terminal device.

34. The device according to claim 33, characterized in that In the aspect of receiving the target application data from the application server, the receiving unit is configured to: Receiving a subscription response message from the application server, wherein the subscription response message includes a code rate identifier ID; Recording and maintaining the correspondence between the target application data and the bitrate ID; The target application data is received from an application server according to the bitrate ID.

35. The device according to claim 33, characterized in that Before sending the target application data to the terminal device, the sending unit is further configured to: Send the bit rate information corresponding to the target application data to the terminal device.

36. A communication device, characterized in that include: An acquiring unit, configured to acquire, in response to a protocol data unit (PDU) session creation request or a PDU session modification request, bit rate authorization information issued by an application function network element (AF), wherein the bit rate authorization information refers to bit rate information allowed for a terminal device to access an application; The sending unit is used to send the bit rate authorization information to the user plane function network element UPF.

37. The device according to claim 36, characterized in that The bit rate authorization information includes at least one of the following: The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

38. The device according to claim 36, characterized in that In terms of obtaining the bit rate authorization information issued by the AF, the obtaining unit is configured to: Sending a first request message to the network open function network element NEF, wherein the first request message is used to request the NEF to query the unified database network element UDR for the bit rate authorization information issued by the AF; A first response message is received from the NEF, where the first response message includes the bit rate authorization information.

39. The device according to claim 37, characterized in that In terms of obtaining the bit rate authorization information issued by the AF, the obtaining unit is configured to: Sending a second request message to the policy control function network element PCF, where the second request message is used to request the PCF to query the UDR for the bit rate authorization information issued by the AF; A second response message is received from the PCF, where the second response message includes the bit rate authorization information.

40. The device according to any one of claims 37 to 39, characterized in that Before obtaining the bit rate authorization information sent by the AF, the obtaining unit is further configured to: Receive a session management SM context request message or an SM context update request message from the mobility management function gateway AMF, where the SM context request message or the SM context update request message includes application data request information of the terminal device.

41. The device according to claim 40, characterized in that In terms of sending the bit rate authorization information to the UPF, the sending unit is configured to: If the SM context request message includes the application data request information, sending an N4 session creation request message to the UPF, where the N4 session creation request message includes the application data request information; or, If the SM context update request message includes the application data request information, an N4 session modification request message is sent to the UPF, where the N4 session modification request message includes the application data request information.

42. The device according to claim 41, characterized in that The data request information includes target application data requested by the terminal device and / or bit rate information requested by the terminal device.

43. A communication device, characterized in that include: A receiving unit, configured to receive network congestion information or bandwidth usage information from an access network device, or network performance analysis information from a network data analysis function (NWDAF); A sending unit is used to send target application data to the terminal device based on the network congestion information, the bandwidth usage information or the network performance analysis information, where the bit rate information corresponding to the target application data is in the bit rate authorization information, and the bit rate authorization information refers to the bit rate information allowed for the terminal device to access the application.

44. The device according to claim 43, characterized in that The bit rate authorization information includes at least one of the following: The maximum bitrate allowed for a terminal device to access an application, a list of bitrates allowed for a terminal device to access an application, bitrate information allowed for a terminal device to access an application within a preset time period, or bitrate information allowed for a terminal device to access an application within a preset location area.

45. The device according to claim 43, characterized in that In the aspect of sending the target application data to the terminal device according to the network congestion information, the bandwidth usage information or the network performance analysis information, the sending unit is configured to: Determining bitrate information corresponding to target application data in the bitrate authorization information according to the network congestion information, the bandwidth usage information, or the network performance analysis information; If the target application data is cached locally or has been subscribed to, sending the target application data to the terminal device; If the target application data is not cached locally or has not been subscribed to, the target application data is sent to the terminal device according to a subscription request message, where the subscription request message is used to request the application server to subscribe to the target application data.

46. The device according to claim 45, characterized in that In the aspect of sending the target application data to the terminal device according to the subscription request message, The sending unit is used to send a subscription request message to the application server; The receiving unit is configured to receive the target application data from an application server; The sending unit is further configured to send the target application data to the terminal device.

47. The device according to claim 46, characterized in that In the aspect of receiving the target application data from the application server, the receiving unit is configured to: Receive a bitrate identifier ID from an application server; Recording and maintaining the correspondence between the target application data and the bitrate ID; The target application data is received from an application server according to the bitrate ID.

48. The device according to claim 45 or 46, characterized in that Before sending the target application data to the terminal device, the sending unit is further configured to: Send the bit rate information corresponding to the target application data to the terminal device.

49. The device according to any one of claims 43 to 48, characterized in that Before sending the target application data to the terminal device according to the network congestion information, the bandwidth usage information, or the network performance analysis information, the receiving unit is further configured to: Receive bit rate authorization information from the SMF network element.

50. The device according to claim 43, characterized in that The code rate authorization information is carried by an N4 session creation request message or an N4 session modification request message.

51. A user plane function network element UPF, comprising a processor, a memory, and a computer program or instruction stored in the memory, characterized in that: The processor executes the computer program or instructions to implement the steps of the method according to any one of claims 1 to 11 or 18 to 25.

52. A session management function network element SMF, comprising a processor, a memory, and a computer program or instruction stored in the memory, characterized in that: The processor executes the computer program or instructions to implement the steps of the method according to any one of claims 12 to 17.

53. A chip comprising a processor, characterized in that: The processor executes the steps of the method according to any one of claims 1 to 25.

54. A computer-readable storage medium, characterized in that The computer stores a computer program or instruction, and when the computer program or instruction is executed, the steps of the method according to any one of claims 1 to 25 are performed.

55. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instructions are executed, the steps of the method according to any one of claims 1 to 25 are performed.

Images