Communication method and communication device

Abstract

The invention provides a communication method and a communication device. The method comprises the following steps: a first network entity acquires first jitter information and / or first time delay information; and the first network entity determines target jitter information of a target service flow between a second network entity and a third network entity according to the first jitter information and / or the first time delay information. The method provided by the embodiment of the invention is helpful for the second network entity to perform CDRX configuration based on the target jitter information.

Description

Communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0002] In some communication systems, to support extended reality and multimedia services while conserving energy, traffic characteristics such as periodicity and jitter can be provided by application servers (ASs) to the radio access network (RAN) for enhanced node management and optimized connected mode discontinuous reception (CDRX) configurations. However, existing CDRX configurations are not ideal.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a communication method and a communication device. The following describes various aspects of the embodiments of the present application.

[0005] In a first aspect, a communication method is provided, including: a first network entity obtains first jitter information and / or first delay information; the first network entity determines target jitter information of a target service flow between a second network entity and a third network entity based on the first jitter information and / or the first delay information.

[0006] In a second aspect, a communication method is provided, including: a sixth network entity sends first information to a fourth network entity, where the first information is used to trigger the fourth network entity to determine target jitter information of a target service flow between the second network entity and the third network entity.

[0007] In a third aspect, a communication method is provided, including: a second network entity receives target jitter information of a target service flow between the second network entity and a third network entity sent by a fourth network entity; and the second network entity performs discontinuous reception CDRX configuration in a connected state based on the target jitter information.

[0008] In a fourth aspect, a communication method is provided, including: a fifth network entity receives second information sent by a fourth network entity, the second information being used to trigger the fifth network entity to determine jitter information of a target service flow between the fifth network entity and a third network entity; the fifth network entity sends first jitter information to the fourth network entity, the first jitter information including the jitter information of the target service flow between the fifth network entity and the third network entity.

[0009] In a fifth aspect, a communication method is provided, including: a fourth network entity sends fifth information to a first network entity, wherein the fifth information is used to trigger the first network entity to determine jitter information of a target service flow between the second network entity and the third network entity.

[0010] In a sixth aspect, a communication method is provided, including: a terminal device sends seventh information to a first network entity, wherein the seventh information is used to trigger the first network entity to determine target jitter information of a target service flow between a second network entity and a third network entity.

[0011] In the seventh aspect, a communication device is provided, including: an acquisition unit for acquiring first jitter information and / or first delay information; a determination unit for determining target jitter information of a target service flow between a second network entity and a third network entity based on the first jitter information and / or the first delay information.

[0012] In an eighth aspect, a communication device is provided, comprising: a sending unit, configured to send first information to a fourth network entity, wherein the first information is used to trigger the fourth network entity to determine target jitter information of a target service flow between the second network entity and the third network entity.

[0013] In the ninth aspect, a communication device is provided, including: a receiving unit for receiving target jitter information of a target service flow between the device and a third network entity sent by a fourth network entity; and a configuration unit for performing discontinuous reception CDRX configuration in a connected state based on the target jitter information.

[0014] In the tenth aspect, a communication device is provided, including: a receiving unit for receiving second information sent by a fourth network entity, the second information being used to trigger the device to determine jitter information of a target service flow between the device and a third network entity; and a sending unit for sending first jitter information to the fourth network entity, the first jitter information including the jitter information of the target service flow between the device and the third network entity.

[0015] In the eleventh aspect, a communication device is provided, including: a sending unit, configured to send fifth information to a first network entity, wherein the fifth information is used to trigger the first network entity to determine jitter information of a target service flow between a second network entity and a third network entity.

[0016] In a twelfth aspect, a communication device is provided, including: a sending unit, used to send seventh information to a first network entity, wherein the seventh information is used to trigger the first network entity to determine target jitter information of a target service flow between a second network entity and a third network entity.

[0017] In the thirteenth aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method described in any one of the first to sixth aspects.

[0018] In a fourteenth aspect, a communication device is provided, comprising a processor for calling a program from a memory so that the communication device executes the method described in any one of the first to sixth aspects.

[0019] In a fifteenth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in any one of the first to sixth aspects.

[0020] In the sixteenth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in any one of the first to sixth aspects.

[0021] In the seventeenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in any one of the first to sixth aspects.

[0022] In the eighteenth aspect, a computer program is provided, which enables a computer to execute the method described in any one of the first to sixth aspects.

[0023] In an embodiment of the present application, the first network entity obtains first jitter information and / or first delay information, and determines the target jitter information of the target service flow between the second network entity and the third network entity based on the first jitter information and / or the first delay information, thereby helping the second network entity to perform CDRX configuration based on the target jitter information, so that the CDRX configuration is more in line with the service flow characteristics, thereby optimizing the power saving effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] FIG1 is an example diagram of a wireless communication system used in an embodiment of the present application.

[0025] FIG2 is an example diagram of a 5GS architecture in an embodiment of the present application.

[0026] FIG3 is an example diagram of data transmission delay in one embodiment of the present application.

[0027] FIG4 is a schematic flowchart of a communication method provided in one embodiment of the present application.

[0028] FIG5 is a schematic flowchart of a communication method provided in another embodiment of the present application.

[0029] FIG6 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0030] FIG7 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0031] FIG8 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

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

[0033] FIG10 is a schematic structural diagram of a communication device provided in another embodiment of the present application.

[0034] FIG11 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0035] FIG12 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0036] FIG13 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0037] FIG14 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0038] FIG15 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The technical solution in this application will be described below with reference to the accompanying drawings.

[0040] FIG1 illustrates a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a user equipment (UE) 120. The network device 110 may communicate with the UE 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the UE 120 within the coverage area. The UE 120 may access a network (e.g., a wireless network) through the network device 110.

[0041] Figure 1 exemplarily shows a network device and two UEs. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include a different number of terminal devices within its coverage area, which is not limited in this embodiment of the present application. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment of the present application.

[0042] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0043] The UE in the embodiments of the present application may also be referred to as a terminal device, an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The UE in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device or an in-vehicle device with wireless connection capabilities. The UE in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0044] The network device in the embodiments of the present application may be a device for communicating with a UE, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a UE to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof.

[0045] In some embodiments, the network device can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile network device, and one or more cells can move according to the location of the mobile network device. In other examples, the helicopter or drone can be configured to act as a device for communicating with another network device. In some embodiments, the network device can refer to a CU or a DU, or the network device can include a CU and a DU, or the network device can also include an AAU.

[0046] It should be understood that network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; and can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the network devices and the scenarios in which they are used.

[0047] It should also be understood that all or part of the functions of the network device and UE in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0048] The solution in the embodiment of the present application is described below using FIG. 2 as an example.

[0049] Figure 2 is a diagram of the 5GS (5G system) architecture, which includes: network slice specific authentication and authorization function (NSSAAF), network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), network slice admission control function (NSACF), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), application function (AF), UE, radio access network (RAN), user plane function (UPF), data network (DN) and other network elements.

[0050] The embodiments of the present application involve terminal equipment (UE), access network elements (RAN), control plane elements (e.g., PCF, SMF, etc.), user plane elements (e.g., UPF), and application servers (AS). The DN can implement the user plane functions of the application server, and the AF can implement the control plane functions of the application server. Optionally, the access network element can be the network device 110 in Figure 1, and the terminal device can be the terminal device 120 in Figure 1.

[0051] Currently, 5GS supports a quality of service (QoS) monitoring mechanism. The following describes the QoS monitoring mechanism.

[0052] QoS monitoring is primarily used to measure packet delay. The packet delay between the UE and the anchor UPF consists of two components: the uplink and downlink packet delay in the access network, as defined in the 3rd Generation Partnership Project (3GPP) specification TS38.314, and the uplink and downlink packet delay between the base station and the anchor UPF. The base station is required to provide QoS monitoring for uplink and downlink packet delay measurements in the access network. QoS monitoring of uplink and downlink packet delay between the base station and the anchor UPF can be performed at different levels of granularity: per QoS flow per UE, or per user plane part of the GPRS tunnel protocol (GTP-U) path. This depends on operator configuration, third-party application requests, and PCF policy control for ultra-reliable and low latency communications (URLLC) services.

[0053] If a QoS monitoring request is received from the AF, the PCF generates an authorized QoS monitoring policy based on the service data flow. The PCF includes the authorized QoS monitoring policy in the PCC rule and provides it to the SMF.

[0054] The SMF can activate end-to-end uplink and downlink packet delay measurement between the UE and the anchor UPF for a QoS flow during the establishment or modification of a packet data unit (PDU) session. The SMF initiates QoS monitoring between the anchor UPF and the base station by sending a QoS monitoring request message to the anchor UPF via the N4 interface and to the base station via N2 signaling. The monitoring parameters in the QoS monitoring request message can be derived by the SMF based on the QoS monitoring policy of the PCF or local configuration. After receiving the QoS monitoring request message from the SMF, the base station initiates measurement of the uplink and downlink packet delay of the access network part and reports the measurement results to the anchor UPF via an uplink data packet. If the base station and the anchor UPF are time synchronized, one-way packet delay monitoring between the base station and the anchor UPF can be supported. If the base station and the anchor UPF are time asynchronous, it is necessary to assume that the uplink packet delay and downlink packet delay between the base station and the anchor UPF are the same. For both of the above cases, the anchor UPF will create a monitoring packet and send it to the base station at a certain measurement frequency. The measurement frequency is determined by the anchor UPF based on the QoS monitoring report frequency received from the SMF.

[0055] The QoS monitoring process is as follows:

[0056] 1. The anchor UPF encapsulates the QoS flow ID (QFI), QoS monitoring packet indication, and local time T1 into the GTP-U packet header. The QoS monitoring packet indication is used to indicate that this data packet is used for uplink and downlink packet delay measurement, and the local time is the time when the anchor UPF sends the downlink monitoring packet.

[0057] 2. The base station records the local time T1 in the received GTP-U packet header and the time T2 when the downlink monitoring packet is received.

[0058] 3. When the base station receives an uplink data packet corresponding to the QFI from the UE or sends a dummy uplink data packet as a monitoring response, it encapsulates the QoS monitoring packet indication, access network packet latency measurement results, local times T1 and T2, and the monitoring response packet transmission time T3 in the GTP-U header of the monitoring response packet. This response packet is sent to the UPF via the N3 interface. When the base station sends the dummy uplink data packet as a monitoring response to the anchor UPF is implementation-dependent.

[0059] 4. When the anchor UPF receives the monitoring response packet, it records the local time T4 and calculates the round-trip delay (if the time is not synchronized) or the uplink and downlink packet delay (if the time is synchronized) between the base station and the anchor UPF based on the time information contained in the GTP-U header of the monitoring response packet. If the base station and the anchor UPF are not synchronized in time, the anchor UPF obtains the packet delay between it and the base station by calculating (T2-T1+T4-T3) / 2. If the base station and the anchor UPF are synchronized in time, the anchor UPF can obtain the uplink packet delay by (T4-T3) and the downlink packet delay by (T2-T1). The anchor UPF can calculate the uplink and downlink packet delay between the anchor UPF and the UE based on the received downlink and uplink packet delay results of the access network and the uplink and downlink packet delay between the base station and the anchor UPF calculated above. When certain specific conditions are met (for example, the reporting threshold is reached), the anchor UPF reports the above calculation results to the SMF. Obviously, if the base station and anchor UPF time are not synchronized, the calculation results of the uplink and downlink packet delay may be inaccurate.

[0060] The "packet" mentioned in the above QoS monitoring process may refer to a data packet transmitted based on the real-time transport protocol (RTP). The receiver of the RTP transmission can use the sender report (SR) or receiver report (RR) data packet of the RTP control protocol (RTCP) to provide reception quality feedback. Among them, the interarrival jitter field in the SR / RR can feedback the statistical variance estimate of the interarrival time of the RTP data packet. The interarrival jitter field can be defined as the difference in the end-to-end transmission delay of two adjacent data packets.

[0061] In the CDRX configuration, the jitter information of the data packets between the AS and the RAN (as shown in Figure 3 ④) needs to be provided to the RAN before sending the service. This allows the RAN to configure the CDRX based on the jitter information, making the CDRX configuration more consistent with the service flow characteristics and thus optimizing the power saving effect.

[0062] However, the aforementioned QoS monitoring mechanism can only measure latency in the access network (as shown in Figure 3, ①) and the core network (as shown in Figure 3, ②). Application servers can only measure server-side jitter caused by factors such as encoder load and content complexity, or derive an end-to-end jitter estimate (as shown in Figure 3, ⑤) using interarrival jitter information in SR / RR packets. Furthermore, the end-to-end jitter estimate can only be estimated after the UE or AS has received a certain number of uplink / downlink packets and sent to the peer via SR / RR packets. Therefore, existing QoS monitoring mechanisms cannot calculate packet jitter information between the AS and the RAN (as shown in Figure 3, ④), and the AS cannot directly provide this jitter information to the core network.

[0063] To address one or more of the above technical issues, the present application provides a communication method and a communication device capable of determining jitter information between a second network entity (e.g., a RAN) and a third network entity (e.g., an AS). The embodiments of the present application are described in detail below with reference to Figures 4 to 8.

[0064] FIG4 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 400 shown in FIG4 may include steps S410 and S420, which are as follows:

[0065] S410: A first network entity obtains first jitter information and / or first delay information.

[0066] The first network entity may be a PCF or a RAN.

[0067] Optionally, the first jitter information may refer to jitter information corresponding to the target service flow, or may refer to jitter information of a data packet (such as an application layer data packet) corresponding to the target service flow. The jitter information may include a jitter value, and may also include: a jitter range (for example, a maximum value and a minimum value), a jitter mean, a jitter variance, etc. The target service flow may refer to a service flow transmitted based on the real-time transport protocol (RTP).

[0068] Optionally, the first delay information may refer to the transmission delay of the data packet corresponding to the target service flow. Optionally, the first delay information may be determined by the QoS monitoring mechanism in the aforementioned embodiment.

[0069] S420: The first network entity determines target jitter information of a target service flow between the second network entity and the third network entity according to the first jitter information and / or the first delay information.

[0070] Optionally, the target jitter information may be a jitter value of a target service flow. Optionally, multiple target jitter information may be obtained using the above method, and at least one of the following items may be calculated based on the multiple target jitter information: a jitter range of the target service flow (e.g., a maximum value and a minimum value of the target service flow), a jitter mean of the target service flow, a jitter variance of the target service flow, etc.

[0071] Furthermore, the RAN may perform CDRX configuration based on the target jitter information.

[0072] In an embodiment of the present application, the first network entity obtains first jitter information and / or first delay information, and determines the target jitter information of the target service flow between the second network entity and the third network entity based on the first jitter information and / or the first delay information, thereby helping the second network entity to perform CDRX configuration based on the target jitter information, so that the CDRX configuration is more in line with the service flow characteristics, thereby optimizing the power saving effect.

[0073] The present application utilizes the interarrival jitter field and timestamp field in the existing RTCP or RTP data packets, and combines the QoS monitoring mechanism to obtain the data packet jitter information between the second network entity and the third network entity (such as ④ in Figure 3).

[0074] Optionally, the jitter information can be calculated in the following ways:

[0075] Method 1: AF-assisted jitter information estimation:

[0076] Optionally, the first network entity may be a PCF.

[0077] The sixth network entity may send first information to the fourth network entity, where the first information may be used to trigger the first network entity to determine target jitter information of a target service flow between the second network entity and the third network entity. Optionally, the sixth network entity may send third information to the fourth network entity, where the third information is used to determine the target service flow.

[0078] The first jitter information may include jitter information of a target service flow between the terminal device and the third network entity.

[0079] The first delay information may include at least one of the following: delay information of the target service flow between the terminal device and the second network entity; delay information of the target service flow between the terminal device and the fifth network entity, and delay information of the target service flow between the second network entity and the fifth network entity.

[0080] Optionally, the first network entity may obtain the first jitter information and the first delay information. The first jitter information may be determined by the sixth network entity. For example, the sixth network entity may determine historical jitter information of the target service flow between the terminal device and the third network entity as the first jitter information. Alternatively, the sixth network entity may determine the first jitter information based on the interarrival jitter field in the header of the second data packet. The second data packet may be a data packet between the terminal device corresponding to the target service flow and the third network entity.

[0081] For example, in S410 above, the first network entity may receive first jitter information sent by the sixth network entity; the first network entity may obtain first latency information through QoS monitoring. Optionally, one or more of the first jitter information, the first information, and the third information may be sent simultaneously by the sixth network entity.

[0082] It should be noted that this application does not limit the order in which the first network entity obtains the first jitter information and the first delay information. For example, the first network entity may first obtain the first jitter information and then obtain the first delay information; or the first network entity may first obtain the first delay information and then obtain the first jitter information; or the first network entity may obtain the first jitter information and the first delay information simultaneously.

[0083] Optionally, the first network entity may further determine second jitter information based on the first delay information. The second jitter information may include jitter information of a target service flow between the terminal device and the second network entity. Optionally, the second jitter information may further include at least one of the following: jitter information of a target service flow between the terminal device and a fifth network entity, or jitter information of a target service flow between the second network entity and the fifth network entity.

[0084] Furthermore, in the above S420, the first network entity may subtract the jitter information of the target service flow between the terminal device and the second network entity from the first jitter information to obtain target jitter information.

[0085] The first network entity may send the target jitter information to the second network entity. Further, the second network entity may perform CDRX configuration based on the target jitter information.

[0086] For example, the second network entity can perform CDRX configuration based on the target jitter information and at least one of the following: jitter information of the target service flow between the third network entity and the fifth network entity, jitter information of the target service flow between the second network entity and the fifth network entity, jitter information of the target service flow between the terminal device and the second network entity, jitter information of the target service flow between the terminal device and the second network entity, and jitter information of the target service flow between the terminal device and the third network entity.

[0087] For example, in method one, the sixth network entity can provide the end-to-end jitter information recorded after the last interaction with the target UE to the first network entity, or after the application server and the UE complete a period of data interaction, provide the statistical end-to-end jitter information to the first network entity; the first network entity can initiate at least two QoS monitoring operations in succession, obtain two measurement results including the first part (between the UE and the second network entity) delay, or the second part (between the second network entity and the fifth network entity) delay and the delay between the UE and the fifth network entity, and calculate the jitter value of the RAN part based on the two measurement results; finally, the first network entity can calculate the jitter information between the second network entity and the third network entity through the end-to-end jitter value and the first part jitter value, and send the jitter information to the second network entity. The following takes the first network entity as PCF, the second network entity as RAN, the third network entity as AS, the fifth network entity as UPF, and the sixth network entity as AF as an example, and describes the embodiment of method one in detail in combination with Figure 5. As shown in Figure 5, method 500 includes steps S510 to S540, which are specifically as follows:

[0088] S510: The AF sends an estimation request message to the PCF.

[0089] The AF sends an estimation request message to the PCF via the network exposure function (NEF).

[0090] The estimation request message may include end-to-end jitter information between the AS and the UE. For example, the jitter information may include the end-to-end jitter value between the AS and the UE, and may also include the jitter range (maximum value, minimum value), jitter mean, jitter variance, etc. The jitter information may be jitter information corresponding to the target service flow.

[0091] The above-mentioned end-to-end jitter information can be determined by the AF. For example, it can be the end-to-end jitter information in the historical record after the AS interacted with the target UE in the past (the historical record can be stored on the UE side or the AS side), or it can be obtained from the interarrival jitter field carried in the SR / RR data packet header after the AS interacts with the UE for a period of time.

[0092] In addition, the estimation request message may further include indication information for triggering the PCF to estimate target jitter information corresponding to the target service flow; the estimation request message may further include flow description information for determining the target service flow.

[0093] S520: PCF initiates QoS monitoring.

[0094] The PCF can initiate multiple QoS monitoring operations to obtain multiple latency information. The latency information may include at least one of the following:

[0095] The latency between the UE and the UPF, the latency in the RAN (between the UE and the RAN), and the latency in the core network (CN) (between the RAN and the UPF).

[0096] S530: The PCF calculates jitter information using the delay information.

[0097] PCF can use the multiple delay information obtained from QoS monitoring to calculate at least one of the following:

[0098] Jitter of the service flow between UE and UPF, jitter of the RAN part, and jitter of the CN part.

[0099] For example, suppose the delay of the CN part obtained for the i-th time is D i , then the jitter of CN part can be expressed by (D i+1 -D i ), where i is a positive integer. The jitter of the RAN can also be calculated using a similar method.

[0100] At the same time, by triggering QoS monitoring multiple times to estimate jitter information, the jitter range (minimum value, maximum value), jitter mean, jitter variance and other information can be statistically analyzed.

[0101] The PCF then subtracts the RAN jitter information from the AS-to-UE jitter information to obtain the AS-to-RAN jitter information. Furthermore, the PCF can obtain jitter information between multiple ASes and RANs and, based on this information, calculate the jitter range, jitter mean, and jitter variance of the service flow transmitted between the ASes and RANs.

[0102] Similarly, the PCF can obtain the jitter information between the UPF and the AS by subtracting the jitter information of the service flow between the UE and the UPF from the jitter information between the AS and the UE.

[0103] S540: The PCF sends target jitter information to the RAN.

[0104] The PCF can provide the estimated service flow jitter information to the RAN to facilitate RAN CDRX configuration. The service flow jitter information may include at least one of the following:

[0105] Jitter range, jitter mean, and jitter variance of service flow transmission between AS and RAN;

[0106] Jitter range, jitter mean, and jitter variance of service flow transmission between AS and UPF;

[0107] Jitter range, jitter mean, and jitter variance of CN service flows;

[0108] Jitter range, jitter mean, and jitter variance of service flows in the RAN portion;

[0109] Jitter range, jitter mean, and jitter variance of the service flow between the UE and the UPF;

[0110] Jitter range, jitter mean, and jitter variance of the end-to-end service flow between the UE and the AS.

[0111] Method 2: UPF-assisted jitter information estimation:

[0112] Optionally, the first network entity is a PCF.

[0113] The sixth network entity may send first information to the first network entity, where the first information may be used to trigger the first network entity to determine target jitter information for a target service flow between the second network entity and the third network entity. Optionally, the sixth network entity may send third information to the first network entity, where the third information is used to determine the target service flow. Optionally, the first information and the third information may be sent simultaneously or separately by the sixth network entity.

[0114] The first jitter information may include jitter information of a target service flow between the fifth network entity and the third network entity.

[0115] The first delay information may include delay information of the target service flow between the second network entity and the fifth network entity. Optionally, the first delay information may also include at least one of the following: delay information of the target service flow between the terminal device and the fifth network entity, and delay information of the target service flow between the terminal device and the second network entity.

[0116] Optionally, the first network entity may obtain first jitter information and first delay information. The first jitter information may be determined by the fifth network entity. Optionally, the fifth network entity may calculate the first jitter information based on N third data packets, where N is an integer greater than or equal to 2. The third data packets may be data packets between the fifth network entity and the third network entity corresponding to the target service flow. For example, the fifth network entity may obtain the first jitter information based on the time at which each of the N third data packets arrives at the fifth network entity and the timestamp field in the header of each data packet.

[0117] For example, in the above S410, the first network entity may receive the first jitter information sent by the fifth network entity; the first network entity may obtain the first delay information through QoS monitoring.

[0118] It should be noted that this application does not limit the order in which the first network entity obtains the first jitter information and the first delay information. For example, the first network entity may first obtain the first jitter information and then obtain the first delay information; or the first network entity may first obtain the first delay information and then obtain the first jitter information; or the first network entity may obtain the first jitter information and the first delay information simultaneously.

[0119] The first network entity may also send second information to the fifth network entity. The second information may be used to trigger the fifth network entity to determine jitter information of a target service flow between the fifth network entity and the third network entity. The first network entity may also send fourth information to the fifth network entity. The fourth information may be used to determine the target service flow. Optionally, the second information and the fourth information may be sent simultaneously or separately by the first network entity.

[0120] The first network entity may further determine third jitter information based on the first delay information. The third jitter information may include jitter information of a target service flow between the second network entity and the fifth network entity. Optionally, the third jitter information may further include at least one of the following: jitter information of the target service flow between the terminal device and the fifth network entity, and jitter information of the target service flow between the terminal device and the second network entity.

[0121] Furthermore, in the above S420, the first network entity may add the first jitter information to the jitter information of the target service flow between the second network entity and the fifth network entity to obtain target jitter information.

[0122] The first network entity may send the target jitter information to the second network entity. Further, the second network entity may perform CDRX configuration based on the target jitter information.

[0123] For example, the second network entity can perform CDRX configuration based on the target jitter information and at least one of the following: jitter information of the target service flow between the third network entity and the fifth network entity, jitter information of the target service flow between the second network entity and the fifth network entity, jitter information of the target service flow between the terminal device and the second network entity, jitter information of the target service flow between the terminal device and the fifth network entity, and jitter information of the target service flow between the terminal device and the third network entity.

[0124] For example, in method 2, the fifth network entity can read the application layer data packet header to obtain a timestamp; the fifth network entity can calculate the jitter information between the third network entity and the fifth network entity based on the time when at least two data packets arrive at the fifth network entity and their timestamps, and send the calculation result to the first network entity; the first network entity continuously initiates at least two QoS monitoring times to obtain two measurement results including the first part of the delay (between the UE and the second network entity), or the second part of the delay (between the second network entity and the fifth network entity) and the delay between the UE and the fifth network entity, and calculate the jitter value of the first part based on the two measurement results; finally, the first network entity can calculate the jitter information between the second network entity and the third network entity based on the end-to-end jitter value and the first part of the jitter value, and send the jitter information to the second network entity.

[0125] The following describes the embodiment of the second approach in detail with reference to FIG6 , taking the first network entity as a PCF, the second network entity as a RAN, the third network entity as an AS, the fifth network entity as a UPF, and the sixth network entity as an AF as an example. As shown in FIG6 , the method 600 includes steps S610 to S670, which are specifically as follows:

[0126] S610: The AF sends an estimation request message to the PCF.

[0127] The AF sends an estimation request message to the PCF through the NEF.

[0128] The estimation request message may further include indication information for triggering the PCF to estimate target jitter information corresponding to the target service flow; the estimation request message may further include flow description information for determining the target service flow.

[0129] S620, PCF sends a calculation request message to UPF.

[0130] The calculation request message may include indication information and flow description information. For example, the PCF may send the indication information and flow description information to the UPF to trigger the UPF to calculate the jitter information of the target service flow between the UPF and the AS.

[0131] S630: UPF calculates jitter information.

[0132] UPF can read the timestamp field in the application layer data packet header to calculate the jitter information of the target service flow between UPF and AS. For example, the time when the i-th data packet arrives at UPF is recorded as T i , the timestamp field in the packet header indicates the packet sending time is S i The jitter information of the target service flow between UPF and AS can be obtained by (T i+1 -S i+1 )-(T i -S i ) is calculated. Obviously, at least two data packets are required to calculate the jitter information of the service flow. As the number of data packets detected by the UPF increases (more than two packets), the jitter range, jitter mean, and variance of the service flow between the UPF and the AS can be calculated.

[0133] S640: The UPF sends jitter information to the PCF.

[0134] The UPF can feed back the jitter information of the target service flow between the UPF and the AS to the PCF.

[0135] S650: PCF initiates QoS monitoring.

[0136] The PCF can initiate multiple QoS monitoring operations to obtain multiple latency information. The latency information may include at least one of the following:

[0137] The latency between the UE and the UPF, the latency in the RAN (between the UE and the RAN), and the latency in the core network (CN) (between the RAN and the UPF).

[0138] Optionally, step S650 may be performed at any time between S610 and S660.

[0139] S660: The PCF calculates jitter information using the delay information.

[0140] PCF can use the multiple delay information obtained from QoS monitoring to calculate at least one of the following:

[0141] Jitter information of the service flow between UE and UPF, jitter information of the RAN part, and jitter information of the CN part.

[0142] By combining the jitter information of the target service flow between the UPF and the AS measured by the UPF with the results obtained through QoS monitoring, the end-to-end jitter information between the UE and the AS and the jitter information between the AS and the RAN can be calculated. Furthermore, the PCF can obtain the end-to-end jitter information between multiple UEs and ASs and the jitter information between multiple ASs and the RAN, and calculate at least one of the following based on this jitter information:

[0143] Jitter range, jitter mean, and jitter variance of the end-to-end service flow between the UE and the AS.

[0144] Jitter range, jitter mean, and jitter variance of service flows transmitted between the AS and the RAN.

[0145] S670: The PCF sends target jitter information to the RAN.

[0146] The PCF can provide the estimated service flow jitter information to the RAN to facilitate RAN CDRX configuration. The service flow jitter information may include at least one of the following:

[0147] Jitter range, jitter mean, and jitter variance of service flow transmission between AS and RAN;

[0148] Jitter range, jitter mean, and jitter variance of service flow transmission between AS and UPF;

[0149] Jitter range, jitter mean, and jitter variance of CN service flows;

[0150] Jitter range, jitter mean, and jitter variance of service flows in the RAN portion;

[0151] Jitter range, jitter mean, and jitter variance of the service flow between the UE and the UPF;

[0152] Jitter range, jitter mean, and jitter variance of the end-to-end service flow between the UE and the AS.

[0153] Method 3: Jitter information estimation based on RAN detection:

[0154] The first network entity may be a RAN.

[0155] The fourth network entity may send fifth information to the first network entity, where the fifth information may be used to trigger the first network entity to determine target jitter information for a target service flow between the second network entity and the third network entity. Optionally, the fourth network entity may send sixth information to the first network entity, where the sixth information may be used to determine the target service flow. Optionally, the fifth information and the sixth information may be sent simultaneously or separately by the fourth network entity.

[0156] The first jitter information may include jitter information of a target service flow between the second network entity and the third network entity.

[0157] Optionally, the first network entity may obtain first jitter information. Optionally, the first network entity may calculate the first jitter information based on N first data packets, where N is an integer greater than or equal to 2. The first data packets may be data packets between the second network entity and the third network entity corresponding to the target service flow. For example, in S410 above, the first network entity may obtain the first jitter information based on the time when each of the N first data packets arrives at the second network entity and the timestamp field in the header of each data packet.

[0158] Furthermore, the first network entity may perform CDRX configuration based on the target jitter information.

[0159] For example, in method three, the first network entity can read the application layer data packet header to obtain the timestamp; the first network entity can calculate the jitter information between the second network entity and the third network entity based on the arrival time of at least two data packets at the second network entity and their timestamps.

[0160] The following describes the embodiment of the third approach in detail with reference to FIG7 , taking the first network entity as a RAN, the second network entity as a RAN, the third network entity as an AS, the fourth network entity as a PCF, and the fifth network entity as a UPF as an example. As shown in FIG7 , the method 700 includes steps S710 to S730, which are specifically as follows:

[0161] S710: The AF sends an estimation request message to the PCF.

[0162] The AF sends an estimation request message to the PCF through the NEF.

[0163] The estimation request message may further include indication information for triggering the PCF to estimate target jitter information corresponding to the target service flow; the estimation request message may further include flow description information for determining the target service flow.

[0164] S720: The PCF sends a calculation request message to the RAN.

[0165] The calculation request message may include indication information and flow description information. For example, the PCF may send the calculation request message to the RAN via the AMF or SMF to trigger the RAN to calculate the jitter information of the target service flow between the RAN and the AS.

[0166] S730: RAN calculates jitter information.

[0167] RAN can read the timestamp field in the application layer data packet header to calculate the jitter information of the target service flow between RAN and AS. For example, the time when the i-th data packet arrives at RAN is recorded as T i , the timestamp field in the packet header indicates the packet sending time is S i The jitter information of the target service flow between RAN and AS can be obtained by (T i+1 -S i+1 )-(T i -S i ) is calculated. Obviously, at least two data packets are required to calculate the jitter information of the service flow. As the number of data packets detected by the UPF increases (more than two packets), the jitter range, jitter mean, and variance of the service flow between the RAN and the AS can be calculated.

[0168] Furthermore, the RAN can perform CDRX configuration based on the jitter information calculated by itself.

[0169] Method 4: UE-assisted jitter information estimation:

[0170] The first network entity may be a RAN.

[0171] The terminal device may send seventh information to the first network entity. The seventh information may be used to trigger the first network entity to determine jitter information of a target service flow between the second network entity and the third network entity. The terminal device may send eighth information to the first network entity. The eighth information may be used to determine the target service flow. Optionally, the seventh information and the eighth information may be sent simultaneously or at different times by the terminal device.

[0172] The first jitter information may include jitter information of a target service flow between the terminal device and the third network entity.

[0173] The first delay information may include delay information of the target service flow between the terminal device and the second network entity.

[0174] Optionally, the first network entity may obtain the first jitter information and the first delay information. The first jitter information may be determined by the terminal device. For example, the terminal device may determine historical jitter information of the target service flow between the terminal device and the third network entity as the first jitter information. Alternatively, the terminal device may determine the first jitter information based on the interarrival jitter field in the header of the second data packet. The second data packet may be a data packet between the terminal device and the third network entity corresponding to the target service flow.

[0175] For example, in S410 above, the first network entity may receive first jitter information sent by the terminal device; the first network entity may obtain first delay information. Optionally, the first network entity may obtain the first delay information through internal implementation, and this application does not limit the specific acquisition method. For example, the first network entity may calculate the first delay information by interacting with the UE and using the data transmission delay.

[0176] Optionally, one or more of the first jitter information, the seventh information and the eighth information may be sent simultaneously by the terminal device.

[0177] It should be noted that this application does not limit the order in which the first network entity obtains the first jitter information and the first delay information. For example, the first network entity may first obtain the first jitter information and then obtain the first delay information; or the first network entity may first obtain the first delay information and then obtain the first jitter information; or the first network entity may obtain the first jitter information and the first delay information simultaneously.

[0178] Optionally, the first network entity may further determine fourth jitter information based on the first delay information. The fourth jitter information may include jitter information of a target service flow between the terminal device and the second network entity. Optionally, the fourth jitter information may further include at least one of the following: jitter information of a target service flow between the terminal device and a fifth network entity, and jitter information of a target service flow between the second network entity and the fifth network entity.

[0179] Furthermore, in the above S420, the first network entity may subtract the jitter information of the target service flow between the terminal device and the second network entity from the first jitter information to obtain the target jitter information.

[0180] Furthermore, the first network entity may perform CDRX configuration based on the target jitter information.

[0181] For example, in method four, the UE can provide the end-to-end jitter information recorded after the last interaction between the application server and the target UE to the first network entity, or after the application server and the UE complete a period of data interaction, provide the statistical end-to-end jitter information to the first network entity; then the first network entity can measure the jitter information between the second network entity and the UE; finally, the first network entity can calculate the jitter information between the second network entity and the third network entity by subtracting the service flow jitter between the second network entity and the UE from the end-to-end jitter information provided by the UE.

[0182] The following describes the embodiment of the fourth approach in detail with reference to FIG8 , taking the first network entity as a RAN, the second network entity as a RAN, the third network entity as an AS, the fourth network entity as a PCF, and the fifth network entity as a UPF as an example. As shown in FIG8 , the method 800 includes steps S810 and S820, which are specifically as follows:

[0183] S810: The UE sends an estimation request message to the RAN.

[0184] The estimation request message may include end-to-end jitter information between the AS and the UE, such as jitter range (maximum value, minimum value), jitter mean, jitter variance, etc. The jitter information may be jitter information corresponding to the target service flow.

[0185] The above-mentioned end-to-end jitter information can be determined by the UE. For example, it can be the end-to-end jitter information in the historical record after the AS interacted with the UE in the past (the historical record can be stored on the UE side or the AS side), or it can be obtained from the interarrival jitter field carried in the SR / RR data packet header after the AS interacts with the UE for a period of time.

[0186] In addition, the estimation request message may further include indication information for triggering the RAN to estimate target jitter information corresponding to the target service flow; the estimation request message may further include flow description information for determining the target service flow.

[0187] S820: RAN determines jitter information.

[0188] The RAN can measure the delay information of the target service flow between the UE and the RAN, and use the delay information to calculate the jitter information of the target service flow between the UE and the RAN.

[0189] Next, the RAN calculates the jitter information for the target service flow between the RAN and the AS by subtracting the jitter information for the target service flow between the RAN and the UE from the end-to-end jitter information provided by the UE. Furthermore, the RAN can obtain jitter information for multiple target service flows between the RAN and the AS and, based on this information, calculate the jitter range, jitter mean, and jitter variance for the target service flow between the RAN and the AS.

[0190] Furthermore, the RAN can perform CDRX configuration based on the jitter information calculated by itself.

[0191] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 8 . The device embodiment of the present application is described in detail below in conjunction with Figures 9 to 15 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0192] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG9 , the device 900 includes an acquisition unit 910 and a determination unit 920, specifically as follows:

[0193] An acquiring unit 910 is configured to acquire first jitter information and / or first delay information;

[0194] The determining unit 920 is configured to determine target jitter information of a target service flow between the second network entity and the third network entity according to the first jitter information and / or the first delay information.

[0195] Optionally, the first jitter information includes jitter information of the target service flow between the terminal device and the third network entity, and the first delay information includes at least one of the following: delay information of the target service flow between the terminal device and the second network entity; delay information of the target service flow between the terminal device and the fifth network entity, and delay information of the target service flow between the second network entity and the fifth network entity; wherein the acquisition unit 910 is specifically used to: receive the first jitter information sent by the sixth network entity; and obtain the first delay information through quality of service QoS monitoring.

[0196] Optionally, the determination unit 920 is also used to: determine second jitter information based on the first delay information, the second jitter information including the jitter information of the target service flow between the terminal device and the second network entity; wherein, the determination unit 920 is specifically used to: subtract the jitter information of the target service flow between the terminal device and the second network entity from the first jitter information to obtain the target jitter information.

[0197] Optionally, the second jitter information also includes at least one of the following: jitter information of the target service flow between the terminal device and the fifth network entity, and jitter information of the target service flow between the second network entity and the fifth network entity.

[0198] Optionally, the first jitter information includes jitter information of the target service flow between the fifth network entity and the third network entity, and the first delay information includes delay information of the target service flow between the second network entity and the fifth network entity; wherein the acquisition unit 910 is specifically used to: receive the first jitter information sent by the fifth network entity; and obtain the first delay information through quality of service QoS monitoring.

[0199] Optionally, the determination unit 920 is also used to: determine third jitter information based on the first delay information, the third jitter information including the jitter information of the target service flow between the second network entity and the fifth network entity; wherein, the determination unit 920 is specifically used to: add the first jitter information and the jitter information of the target service flow between the second network entity and the fifth network entity to obtain the target jitter information.

[0200] Optionally, the first delay information also includes at least one of the following: delay information of the target service flow between the terminal device and the fifth network entity, and delay information of the target service flow between the terminal device and the second network entity; the third jitter information also includes at least one of the following: jitter information of the target service flow between the terminal device and the fifth network entity, and jitter information of the target service flow between the terminal device and the second network entity.

[0201] Optionally, the apparatus 900 further includes a sending unit 930, configured to: send the target jitter information to the second network entity.

[0202] Optionally, the device 900 also includes a receiving unit 940, which is used to: receive first information sent by the sixth network entity, where the first information is used to trigger the first network entity to determine target jitter information of the target service flow between the second network entity and the third network entity.

[0203] Optionally, the apparatus 900 further includes a receiving unit 940, configured to: receive third information sent by the sixth network entity, where the third information is used to determine the target service flow.

[0204] Optionally, the device 900 further includes a sending unit 930, configured to send second information to the fifth network entity, wherein the second information is used to trigger the fifth network entity to determine jitter information of the target service flow between the fifth network entity and the third network entity.

[0205] Optionally, the apparatus 900 further includes a sending unit 930, configured to: send fourth information to the fifth network entity, where the fourth information is used to determine the target service flow.

[0206] Optionally, the device 900 is a policy control function PCF, the second network entity is an access network RAN, the third network entity is an application server AS, the fifth network entity is a user plane function UPF, and the sixth network entity is an application function AF.

[0207] Optionally, the first jitter information includes jitter information of the target service flow between the second network entity and the third network entity; wherein the acquisition unit 910 is specifically used to: calculate the first jitter information through N first data packets, the first data packet is the data packet between the second network entity and the third network entity corresponding to the target service flow, and N is an integer greater than or equal to 2.

[0208] Optionally, the acquiring unit 910 is specifically configured to obtain the first jitter information according to a time when each of the N first data packets arrives at the second network entity and a timestamp field in a header of each data packet.

[0209] Optionally, the device 900 also includes a receiving unit 940, which is used to: receive fifth information sent by the fourth network entity, and the fifth information is used to trigger the second network entity to determine the target jitter information of the target service flow between the second network entity and the third network entity.

[0210] Optionally, the apparatus 900 further includes a receiving unit 940, configured to receive sixth information sent by the fourth network entity, where the sixth information is used to determine the target service flow.

[0211] Optionally, the first jitter information includes jitter information of the target service flow between the terminal device and the third network entity, and the first delay information includes delay information of the target service flow between the terminal device and the second network entity; wherein, the acquisition unit 910 is specifically used to: receive the first jitter information sent by the terminal device; and obtain the first delay information.

[0212] Optionally, the determination unit 920 is also used to: determine fourth jitter information based on the first delay information, and the fourth jitter information includes the jitter information of the target service flow between the terminal device and the second network entity; wherein, the determination unit 920 is specifically used to: subtract the jitter information of the target service flow between the terminal device and the second network entity from the first jitter information to obtain the target jitter information.

[0213] Optionally, the apparatus 900 further includes a receiving unit 940, configured to receive seventh information sent by the terminal device, wherein the seventh information is used to trigger the first network entity to determine jitter information of the target service flow between the second network entity and the third network entity.

[0214] Optionally, the apparatus 900 further includes a receiving unit 940, configured to receive eighth information sent by the terminal device, where the eighth information is used to determine the target service flow.

[0215] Optionally, the apparatus 900 further includes a configuration unit 950, configured to perform discontinuous reception (CDRX) configuration in a connected state based on the target jitter information.

[0216] Optionally, the device 900 is an access network RAN, the second network entity is the RAN, the third network entity is an application server AS, and the fourth network entity is a policy control function PCF.

[0217] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG10 , the device 1000 includes a sending unit 1010, which is specifically as follows:

[0218] The sending unit 1010 is configured to send first information to a fourth network entity, where the first information is used to trigger the fourth network entity to determine target jitter information of a target service flow between the second network entity and the third network entity.

[0219] Optionally, the sending unit 1010 is further configured to: send third information to the fourth network entity, where the third information is used to determine the target service flow.

[0220] Optionally, the sending unit 1010 is further configured to send first jitter information to the fourth network entity, where the first jitter information includes jitter information of the target service flow between the terminal device and the third network entity.

[0221] Optionally, the first jitter information is historical jitter information of the target service flow between the terminal device and the third network entity, or the first jitter information is determined by the arrival interval jitter field in the header of the second data packet, and the second data packet is the data packet between the terminal device and the third network entity corresponding to the target service flow.

[0222] Optionally, the apparatus 1000 is an application function AF, the second network entity is an access network RAN, the third network entity is an application server AS, and the fourth network entity is a policy control function PCF.

[0223] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG11 , the device 1100 includes a receiving unit 1110 and a configuration unit 1120, specifically as follows:

[0224] The receiving unit 1110 is configured to receive target jitter information of a target service flow between the apparatus and the third network entity sent by a fourth network entity;

[0225] The configuration unit 1120 is configured to perform discontinuous reception (CDRX) configuration in a connected state based on the target jitter information.

[0226] Optionally, the configuration unit 1120 is specifically used to: perform CDRX configuration based on the target jitter information and at least one of the following items: the jitter information of the target service flow between the AS and the fifth network entity, the jitter information of the target service flow between the device and the fifth network entity, the jitter information of the target service flow between the terminal device and the device, the jitter information of the target service flow between the terminal device and the fifth network entity, and the jitter information of the target service flow between the terminal device and the third network entity.

[0227] Optionally, the device 1100 is an access network RAN, the third network entity is an application server AS, the fourth network entity is a policy control function PCF, and the fifth network entity is a user plane function UPF.

[0228] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG12 , the device 1200 includes a receiving unit 1210 and a sending unit 1220, specifically as follows:

[0229] The receiving unit 1210 is configured to receive second information sent by a fourth network entity, where the second information is used to trigger the apparatus to determine jitter information of a target service flow between the apparatus and the third network entity;

[0230] The sending unit 1220 is configured to send first jitter information to the fourth network entity, where the first jitter information includes jitter information of the target service flow between the device and the third network entity.

[0231] Optionally, the receiving unit 1210 is further configured to: receive fourth information sent by the fourth network entity, where the fourth information is used to determine the target service flow.

[0232] Optionally, the device 1200 also includes a calculation unit 1230, which is used to: calculate the first jitter information through N third data packets, where the third data packets are data packets between the device and the third network entity corresponding to the target service flow, and N is an integer greater than or equal to 2.

[0233] Optionally, the calculation unit 1230 is specifically configured to obtain the first jitter information according to a time when each of the N third data packets arrives at the device and a timestamp field in a header of each data packet.

[0234] Optionally, the device 1200 is a user plane function UPF, the third network entity is an application server AS, and the fourth network entity is a policy control function PCF.

[0235] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG13 , the device 1300 includes a sending unit 1310, which is specifically as follows:

[0236] The sending unit 1310 is configured to send fifth information to the first network entity, where the fifth information is used to trigger the first network entity to determine jitter information of a target service flow between the second network entity and the third network entity.

[0237] Optionally, the sending unit 1310 is further configured to: send sixth information to the first network entity, where the sixth information is used to determine the target service flow.

[0238] Optionally, the device 1300 further includes a receiving unit 1320, configured to receive first information sent by a sixth network entity, wherein the first information is used to trigger the device to determine target jitter information of the target service flow between the second and third network entities.

[0239] Optionally, the apparatus 1300 further includes a receiving unit 1320, configured to receive third information sent by a sixth network entity, where the third information is used to determine the target service flow.

[0240] Optionally, the device 1300 is a policy control function PCF, the first network entity and the second network entity are an access network RAN, the third network entity is an application server AS, and the sixth network entity is an application function AF.

[0241] FIG14 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG14 , the device 1400 includes a sending unit 1410, which is specifically as follows:

[0242] The sending unit 1410 is configured to send seventh information to the first network entity, where the seventh information is used to trigger the first network entity to determine target jitter information of a target service flow between the second network entity and the third network entity.

[0243] Optionally, the sending unit 1410 is further configured to: send eighth information to the first network entity, where the eighth information is used to determine the target service flow.

[0244] Optionally, the sending unit 1410 is further configured to send first jitter information to the first network entity, where the first jitter information includes jitter information of a target service flow between the device and a third network entity.

[0245] Optionally, the first jitter information is historical jitter information of the target service flow between the device and the third network entity, or the first jitter information is determined by the arrival interval jitter field in the second data packet header, and the second data packet is a data packet between the device and the third network entity corresponding to the target service flow.

[0246] Optionally, the first network entity and the second network entity are an access network RAN, and the third network entity is an application server AS.

[0247] FIG15 is a schematic diagram of the structure of an apparatus provided in one embodiment of the present application. The dotted lines in FIG15 indicate that the unit or module is optional. Apparatus 1500 may be used to implement the method described in the above method embodiment. Apparatus 1500 may be a chip or a communication device.

[0248] The device 1500 may include one or more processors 1510. The processor 1510 may support the device 1500 to implement the method described in the method embodiment above. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another 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, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0249] The apparatus 1500 may further include one or more memories 1520. The memories 1520 store programs that can be executed by the processor 1510, causing the processor 1510 to perform the methods described in the above method embodiments. The memories 1520 may be independent of the processor 1510 or integrated into the processor 1510.

[0250] The apparatus 1500 may further include a transceiver 1530. The processor 1510 may communicate with other devices or chips via the transceiver 1530. For example, the processor 1510 may transmit and receive data with other devices or chips via the transceiver 1530.

[0251] The present invention also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present invention, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present invention.

[0252] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.

[0253] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the communication device in each embodiment of the present application.

[0254] It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0255] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0256] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0257] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0258] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of the solution of this embodiment according to actual needs.

[0259] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0260] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it 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 process or function described in the embodiment of the present application is 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 read 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 versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0261] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: include: The first network entity obtains first jitter information and / or first delay information; The first network entity determines target jitter information of a target service flow between the second network entity and the third network entity according to the first jitter information and / or the first delay information.

2. The method according to claim 1, characterized in that The first jitter information includes jitter information of the target service flow between the terminal device and the third network entity, and the first delay information includes at least one of the following: Delay information of the target service flow between the terminal device and the second network entity; Delay information of the target service flow between the terminal device and the fifth network entity, and delay information of the target service flow between the second network entity and the fifth network entity; The first network entity obtaining the first jitter information and / or the first delay information includes: The first network entity receives the first jitter information sent by the sixth network entity; The first network entity obtains the first delay information through quality of service (QoS) monitoring.

3. The method according to claim 2, characterized in that The method further comprises: The first network entity determines second jitter information according to the first delay information, where the second jitter information includes jitter information of the target service flow between the terminal device and the second network entity; The first network entity determining target jitter information of a target service flow between the second network entity and the third network entity according to the first jitter information and / or the first delay information includes: The first network entity subtracts the jitter information of the target service flow between the terminal device and the second network entity from the first jitter information to obtain the target jitter information.

4. The method according to claim 3, characterized in that The second jitter information further includes at least one of the following: jitter information of the target service flow between the terminal device and the fifth network entity, and jitter information of the target service flow between the second network entity and the fifth network entity.

5. The method according to claim 1, wherein The first jitter information includes jitter information of the target service flow between the fifth network entity and the third network entity, and the first delay information includes delay information of the target service flow between the second network entity and the fifth network entity; The first network entity obtaining the first jitter information and / or the first delay information includes: The first network entity receives the first jitter information sent by the fifth network entity; The first network entity obtains the first delay information through quality of service (QoS) monitoring.

6. The method according to claim 5, characterized in that The method further comprises: The first network entity determines third jitter information according to the first delay information, where the third jitter information includes jitter information of the target service flow between the second network entity and the fifth network entity; The first network entity determining target jitter information of a target service flow between the second network entity and the third network entity according to the first jitter information and / or the first delay information includes: The first network entity adds the first jitter information and the jitter information of the target service flow between the second network entity and the fifth network entity to obtain the target jitter information.

7. The method according to claim 6, characterized in that The first delay information also includes at least one of the following: the delay information of the target service flow between the terminal device and the fifth network entity, and the delay information of the target service flow between the terminal device and the second network entity; the third jitter information also includes at least one of the following: the jitter information of the target service flow between the terminal device and the fifth network entity, and the jitter information of the target service flow between the terminal device and the second network entity.

8. The method according to any one of claims 2 to 7, characterized in that The method further comprises: The first network entity sends the target jitter information to the second network entity.

9. The method according to any one of claims 2 to 8, characterized in that The method further comprises: The first network entity receives first information sent by the sixth network entity, where the first information is used to trigger the first network entity to determine target jitter information of the target service flow between the second network entity and the third network entity.

10. The method according to claim 9, characterized in that Before the first network entity receives the first information sent by the sixth network entity, the method further includes: The first network entity receives third information sent by the sixth network entity, where the third information is used to determine the target service flow.

11. The method according to any one of claims 5 to 8, characterized in that The method further comprises: The first network entity sends second information to the fifth network entity, where the second information is used to trigger the fifth network entity to determine jitter information of the target service flow between the fifth network entity and the third network entity.

12. The method according to claim 11, characterized in that The method further comprises: The first network entity sends fourth information to the fifth network entity, where the fourth information is used to determine the target service flow.

13. The method according to any one of claims 2 to 12, characterized in that The first network entity is a policy control function PCF, the second network entity is an access network RAN, the third network entity is an application server AS, the fifth network entity is a user plane function UPF, and the sixth network entity is an application function AF.

14. The method according to claim 1, wherein The first jitter information includes jitter information of the target service flow between the second network entity and the third network entity; The first network entity obtaining the first jitter information and / or the first delay information includes: The first network entity calculates the first jitter information through N first data packets, where the first data packets are data packets between the second network entity and the third network entity corresponding to the target service flow, and N is an integer greater than or equal to 2.

15. The method according to claim 14, characterized in that The first network entity calculates the first jitter information using N first data packets, including: The first network entity obtains the first jitter information according to a time when each of the N first data packets arrives at the second network entity and a timestamp field in a header of each data packet.

16. The method according to claim 14 or 15, characterized in that The method further comprises: The first network entity receives fifth information sent by the fourth network entity, where the fifth information is used to trigger the first network entity to determine target jitter information of the target service flow between the second network entity and the third network entity.

17. The method according to any one of claims 14 to 16, characterized in that The method further comprises: The first network entity receives sixth information sent by the fourth network entity, where the sixth information is used to determine the target service flow.

18. The method according to claim 1, wherein The first jitter information includes jitter information of the target service flow between the terminal device and the third network entity, and the first delay information includes delay information of the target service flow between the terminal device and the second network entity; The first network entity obtaining the first jitter information and / or the first delay information includes: The first network entity receives the first jitter information sent by the terminal device; The first network entity obtains the first delay information.

19. The method according to claim 18, characterized in that The method further comprises: The first network entity determines fourth jitter information according to the first delay information, where the fourth jitter information includes jitter information of the target service flow between the terminal device and the second network entity; The first network entity determining target jitter information of a target service flow between the second network entity and the third network entity according to the first jitter information and / or the first delay information includes: The RAN subtracts the jitter information of the target service flow between the terminal device and the second network entity from the first jitter information to obtain the target jitter information.

20. The method according to claim 18 or 19, characterized in that The method further comprises: The first network entity receives seventh information sent by the terminal device, where the seventh information is used to trigger the first network entity to determine jitter information of the target service flow between the second network entity and the third network entity.

21. The method according to any one of claims 18 to 20, characterized in that The method further comprises: The first network entity receives eighth information sent by the terminal device, where the eighth information is used to determine the target service flow.

22. The method according to any one of claims 14 to 21, characterized in that The method further comprises: The first network entity performs discontinuous reception (CDRX) configuration in a connected state based on the target jitter information.

23. The method according to any one of claims 14 to 22, characterized in that The first network entity is an access network RAN, the second network entity is a RAN, the third network entity is an application server AS, and the fourth network entity is a policy control function PCF.

24. A communication method, characterized in that: include: The sixth network entity sends first information to the fourth network entity, where the first information is used to trigger the fourth network entity to determine target jitter information of a target service flow between the second network entity and the third network entity.

25. The method according to claim 24, characterized in that The method further comprises: The sixth network entity sends third information to the fourth network entity, where the third information is used to determine the target service flow.

26. The method according to claim 24 or 25, characterized in that The method further comprises: The sixth network entity sends first jitter information to the fourth network entity, where the first jitter information includes jitter information of the target service flow between the terminal device and the third network entity.

27. The method according to claim 26, characterized in that The first jitter information is the historical jitter information of the target service flow between the terminal device and the third network entity, or the first jitter information is determined by the arrival interval jitter field in the header of the second data packet, and the second data packet is the data packet between the terminal device and the third network entity corresponding to the target service flow.

28. The method according to any one of claims 24 to 27, characterized in that The second network entity is an access network RAN, the third network entity is an application server AS, the fourth network entity is a policy control function PCF, and the sixth network entity is an application function AF.

29. A communication method, characterized in that: include: The second network entity receives target jitter information of a target service flow between the second network entity and the third network entity sent by the fourth network entity; The second network entity performs discontinuous reception (CDRX) configuration in a connected state based on the target jitter information.

30. The method according to claim 29, wherein The second network entity performs discontinuous reception (CDRX) configuration in a connected state based on the target jitter information, including: The second network entity performs CDRX configuration based on the target jitter information and at least one of the following: The jitter information of the target business flow between the third network entity and the fifth network entity, the jitter information of the target business flow between the second network entity and the fifth network entity, the jitter information of the target business flow between the terminal device and the second network entity, the jitter information of the target business flow between the terminal device and the fifth network entity, and the jitter information of the target business flow between the terminal device and the third network entity.

31. The method according to claim 29 or 30, characterized in that The second network entity is an access network RAN, the third network entity is an application server AS, the fourth network entity is a policy control function PCF, and the fifth network entity is a user plane function UPF.

32. A communication method, characterized in that: include: The fifth network entity receives second information sent by the fourth network entity, where the second information is used to trigger the fifth network entity to determine jitter information of a target service flow between the fifth network entity and the third network entity; The fifth network entity sends first jitter information to the fourth network entity, where the first jitter information includes jitter information of the target service flow between the fifth network entity and the third network entity.

33. The method according to claim 32, characterized in that The method further comprises: The fifth network entity receives fourth information sent by the fourth network entity, where the fourth information is used to determine the target service flow.

34. The method according to claim 32 or 33, characterized in that The method further comprises: The fifth network entity calculates the first jitter information through N third data packets, where the third data packets are data packets between the fifth network entity and the third network entity corresponding to the target service flow, and N is an integer greater than or equal to 2.

35. The method according to claim 34, wherein The fifth network entity calculates the first jitter information using N third data packets, including: The fifth network entity obtains the first jitter information according to a time when each of the N third data packets arrives at the fifth network entity and a timestamp field in a header of each data packet.

36. The method according to any one of claims 32 to 35, characterized in that The third network entity is an application server AS, the fourth network entity is a policy control function PCF, and the fifth network entity is a user plane function UPF.

37. A communication method, characterized in that: include: The fourth network entity sends fifth information to the first network entity, where the fifth information is used to trigger the first network entity to determine jitter information of a target service flow between the second network entity and the third network entity.

38. The method according to claim 37, wherein Before the fourth network entity sends the fifth information to the first network entity, the method further includes: The fourth network entity sends sixth information to the second network entity, where the sixth information is used to determine the target service flow.

39. The method according to claim 37 or 38, characterized in that The method further comprises: The fourth network entity receives first information sent by the sixth network entity, where the first information is used to trigger the fourth network entity to determine target jitter information of the target service flow between the second network entity and the third network entity.

40. The method according to any one of claims 37 to 39, characterized in that The method further comprises: The fourth network entity receives third information sent by the sixth network entity, where the third information is used to determine the target service flow.

41. The method according to any one of claims 37 to 40, characterized in that The first network entity and the second network entity are an access network RAN, the third network entity is an application server AS, the fourth network entity is a policy control function PCF, and the sixth network entity is an application function AF.

42. A communication method, characterized in that: include: The terminal device sends seventh information to the first network entity, where the seventh information is used to trigger the first network entity to determine target jitter information of a target service flow between the second network entity and the third network entity.

43. The method according to claim 42, characterized in that The method further comprises: The terminal device sends eighth information to the first network entity, where the eighth information is used to determine the target service flow.

44. The method according to claim 42 or 43, characterized in that The method further comprises: The terminal device sends first jitter information to the first network entity, where the first jitter information includes jitter information of a target service flow between the terminal device and a third network entity.

45. The method according to claim 44, wherein The first jitter information is the historical jitter information of the target service flow between the terminal device and the third network entity, or the first jitter information is determined by the arrival interval jitter field in the header of the second data packet, and the second data packet is the data packet between the terminal device and the third network entity corresponding to the target service flow.

46. ​​The method according to any one of claims 42 to 45, characterized in that The first network entity and the second network entity are an access network RAN, and the third network entity is an application server AS.

47. A communication device, characterized in that include: an acquiring unit, configured to acquire first jitter information and / or first delay information; A determining unit is configured to determine target jitter information of a target service flow between the second network entity and the third network entity according to the first jitter information and / or the first delay information.

48. The device according to claim 47, characterized in that The first jitter information includes jitter information of the target service flow between the terminal device and the third network entity, and the first delay information includes at least one of the following: Delay information of the target service flow between the terminal device and the second network entity; Delay information of the target service flow between the terminal device and the fifth network entity, and delay information of the target service flow between the second network entity and the fifth network entity; The acquiring unit is specifically configured to: receive the first jitter information sent by the sixth network entity; and acquire the first delay information through quality of service (QoS) monitoring.

49. The device according to claim 48, characterized in that The determining unit is further configured to: determine second jitter information according to the first delay information, where the second jitter information includes jitter information of the target service flow between the terminal device and the second network entity; The determining unit is specifically configured to: subtract the jitter information of the target service flow between the terminal device and the second network entity from the first jitter information to obtain the target jitter information.

50. The device according to claim 49, characterized in that The second jitter information further includes at least one of the following: jitter information of the target service flow between the terminal device and the fifth network entity, and jitter information of the target service flow between the second network entity and the fifth network entity.

51. The device according to claim 47, characterized in that The first jitter information includes jitter information of the target service flow between the fifth network entity and the third network entity, and the first delay information includes delay information of the target service flow between the second network entity and the fifth network entity; The acquiring unit is specifically configured to: receive the first jitter information sent by the fifth network entity; and acquire the first delay information through quality of service (QoS) monitoring.

52. The device according to claim 51, characterized in that The determining unit is further configured to: determine third jitter information according to the first delay information, where the third jitter information includes jitter information of the target service flow between the second network entity and the fifth network entity; The determining unit is specifically configured to add the first jitter information and the jitter information of the target service flow between the second network entity and the fifth network entity to obtain the target jitter information.

53. The device according to claim 52, characterized in that The first delay information also includes at least one of the following: the delay information of the target service flow between the terminal device and the fifth network entity, and the delay information of the target service flow between the terminal device and the second network entity; the third jitter information also includes at least one of the following: the jitter information of the target service flow between the terminal device and the fifth network entity, and the jitter information of the target service flow between the terminal device and the second network entity.

54. The device according to any one of claims 48 to 53, characterized in that The device further includes a sending unit, configured to send the target jitter information to the second network entity.

55. The device according to any one of claims 48 to 54, characterized in that The device also includes a receiving unit, configured to receive first information sent by the sixth network entity, where the first information is used to trigger the first network entity to determine target jitter information of the target service flow between the second network entity and the third network entity.

56. The device according to claim 55, characterized in that The apparatus further includes a receiving unit configured to receive third information sent by the sixth network entity, where the third information is used to determine the target service flow.

57. The device according to any one of claims 51 to 54, characterized in that The apparatus further includes a sending unit, configured to send second information to the fifth network entity, where the second information is used to trigger the fifth network entity to determine jitter information of the target service flow between the fifth network entity and the third network entity.

58. The device according to claim 57, characterized in that The apparatus further includes a sending unit configured to send fourth information to the fifth network entity, where the fourth information is used to determine the target service flow.

59. The device according to any one of claims 48 to 58, characterized in that The device is a policy control function PCF, the second network entity is an access network RAN, the third network entity is an application server AS, the fifth network entity is a user plane function UPF, and the sixth network entity is an application function AF.

60. The device according to claim 47, wherein The first jitter information includes jitter information of the target service flow between the second network entity and the third network entity; The acquisition unit is specifically used to calculate the first jitter information through N first data packets, where the first data packets are data packets between the second network entity and the third network entity corresponding to the target service flow, and N is an integer greater than or equal to 2.

61. The device according to claim 60, characterized in that The acquiring unit is specifically configured to obtain the first jitter information according to a time when each of the N first data packets arrives at the second network entity and a timestamp field in a header of each data packet.

62. The device according to claim 60 or 61, characterized in that The device also includes a receiving unit, configured to receive fifth information sent by the fourth network entity, where the fifth information is used to trigger the second network entity to determine target jitter information of the target service flow between the second network entity and the third network entity.

63. The device according to any one of claims 60 to 62, characterized in that The apparatus further includes a receiving unit configured to receive sixth information sent by the fourth network entity, where the sixth information is used to determine the target service flow.

64. The device according to claim 47, characterized in that The first jitter information includes jitter information of the target service flow between the terminal device and the third network entity, and the first delay information includes delay information of the target service flow between the terminal device and the second network entity; The acquisition unit is specifically used to: receive the first jitter information sent by the terminal device; and acquire the first delay information.

65. The device according to claim 64, characterized in that The determining unit is further configured to: determine fourth jitter information according to the first delay information, where the fourth jitter information includes jitter information of the target service flow between the terminal device and the second network entity; The determining unit is specifically configured to: subtract the jitter information of the target service flow between the terminal device and the second network entity from the first jitter information to obtain the target jitter information.

66. The device according to claim 64 or 65, characterized in that The apparatus further includes a receiving unit configured to receive seventh information sent by the terminal device, wherein the seventh information is used to trigger the first network entity to determine jitter information of the target service flow between the second network entity and the third network entity.

67. The device according to any one of claims 64 to 66, characterized in that The apparatus further includes a receiving unit configured to receive eighth information sent by the terminal device, wherein the eighth information is used to determine the target service flow.

68. The device according to any one of claims 60 to 67, characterized in that The device further includes a configuration unit, configured to perform discontinuous reception (CDRX) configuration in a connected state based on the target jitter information.

69. The device according to any one of claims 60 to 68, characterized in that The device is an access network RAN, the second network entity is the RAN, the third network entity is an application server AS, and the fourth network entity is a policy control function PCF.

70. A communication device, characterized in that include: A sending unit is configured to send first information to a fourth network entity, where the first information is used to trigger the fourth network entity to determine target jitter information of a target service flow between the second network entity and the third network entity.

71. The device according to claim 70, characterized in that The sending unit is further configured to send third information to the fourth network entity, where the third information is used to determine the target service flow.

72. The device according to claim 70 or 71, characterized in that The sending unit is further configured to send first jitter information to the fourth network entity, where the first jitter information includes jitter information of the target service flow between the terminal device and the third network entity.

73. The device according to claim 72, characterized in that The first jitter information is the historical jitter information of the target service flow between the terminal device and the third network entity, or the first jitter information is determined by the arrival interval jitter field in the header of the second data packet, and the second data packet is the data packet between the terminal device and the third network entity corresponding to the target service flow.

74. The device according to any one of claims 70 to 73, characterized in that The device is an application function AF, the second network entity is an access network RAN, the third network entity is an application server AS, and the fourth network entity is a policy control function PCF.

75. A communication device, characterized in that include: a receiving unit, configured to receive target jitter information of a target service flow between the apparatus and the third network entity, sent by a fourth network entity; A configuration unit is used to perform discontinuous reception CDRX configuration in a connected state based on the target jitter information.

76. The device according to claim 75, characterized in that The configuration unit is specifically configured to perform CDRX configuration based on the target jitter information and at least one of the following: The jitter information of the target business flow between the AS and the fifth network entity, the jitter information of the target business flow between the device and the fifth network entity, the jitter information of the target business flow between the terminal device and the device, the jitter information of the target business flow between the terminal device and the fifth network entity, and the jitter information of the target business flow between the terminal device and the third network entity.

77. The device according to claim 75 or 76, characterized in that The device is an access network RAN, the third network entity is an application server AS, the fourth network entity is a policy control function PCF, and the fifth network entity is a user plane function UPF.

78. A communication device, characterized in that include: a receiving unit, configured to receive second information sent by a fourth network entity, wherein the second information is used to trigger the apparatus to determine jitter information of a target service flow between the apparatus and the third network entity; A sending unit is used to send first jitter information to the fourth network entity, where the first jitter information includes jitter information of the target service flow between the device and the third network entity.

79. The device according to claim 78, characterized in that The receiving unit is further configured to receive fourth information sent by the fourth network entity, where the fourth information is used to determine the target service flow.

80. The device according to claim 78 or 79, characterized in that The device also includes a calculation unit, which is used to: calculate the first jitter information through N third data packets, where the third data packets are data packets between the device and the third network entity corresponding to the target service flow, and N is an integer greater than or equal to 2.

81. The device according to claim 80, characterized in that The calculation unit is specifically configured to obtain the first jitter information according to a time when each of the N third data packets arrives at the device and a timestamp field in a header of each data packet.

82. The device according to any one of claims 78 to 81, characterized in that The device is a user plane function UPF, the third network entity is an application server AS, and the fourth network entity is a policy control function PCF.

83. A communication device, characterized in that include: The sending unit is configured to send fifth information to the first network entity, where the fifth information is used to trigger the first network entity to determine jitter information of a target service flow between the second network entity and the third network entity.

84. The device according to claim 83, characterized in that The sending unit is further configured to send sixth information to the first network entity, where the sixth information is used to determine the target service flow.

85. The device according to claim 83 or 84, characterized in that The apparatus further includes a receiving unit configured to receive first information sent by a sixth network entity, where the first information is used to trigger the apparatus to determine target jitter information of the target service flow between the second and third network entities.

86. The device according to any one of claims 83 to 85, characterized in that The apparatus further includes a receiving unit configured to receive third information sent by a sixth network entity, where the third information is used to determine the target service flow.

87. The device according to any one of claims 83 to 86, characterized in that The device is a policy control function PCF, the first network entity and the second network entity are an access network RAN, the third network entity is an application server AS, and the sixth network entity is an application function AF.

88. A communication device, characterized in that include: A sending unit is configured to send seventh information to the first network entity, where the seventh information is used to trigger the first network entity to determine target jitter information of a target service flow between the second network entity and the third network entity.

89. The device according to claim 88, characterized in that The sending unit is further configured to: Sending eighth information to the first network entity, where the eighth information is used to determine the target service flow.

90. The device according to claim 88 or 89, characterized in that The sending unit is further configured to send first jitter information to the first network entity, where the first jitter information includes jitter information of a target service flow between the device and a third network entity.

91. The device according to claim 90, characterized in that The first jitter information is the historical jitter information of the target service flow between the device and the third network entity, or the first jitter information is determined by the arrival interval jitter field in the second data packet header, and the second data packet is the data packet between the device and the third network entity corresponding to the target service flow.

92. The device according to any one of claims 88 to 91, characterized in that The first network entity and the second network entity are an access network RAN, and the third network entity is an application server AS.

93. A communication device, characterized in that It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 1 to 46.

94. A communication device, characterized in that The device comprises a processor configured to call a program from a memory so as to cause the communication device to execute the method according to any one of claims 1 to 46.

95. A chip, characterized in that The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 46.

96. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 46.

97. A computer program product, characterized in that A program is included, the program causing a computer to execute the method according to any one of claims 1 to 46.

98. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 46.

Images