Communication method and communication device

Abstract

Provided are a communication method and a communication device, the method comprising: a first network entity sending first information to a second network entity, the first information being used for requesting the second network entity to determine jitter information corresponding to a target service flow. According to the method in the embodiment of the invention, optimization of CDRX configuration is facilitated.

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, access network equipment can configure connected mode discontinuous reception (CDRX) based on jitter information corresponding to a service flow. However, it is currently unclear how to obtain the jitter information corresponding to the service flow.

[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 sends first information to a second network entity, where the first information is used to request the second network entity to determine jitter information corresponding to a target service flow.

[0006] According to a second aspect, a communication method is provided, including: a second network entity receives first information sent by a first network entity, wherein the first information is used to request the second network entity to determine jitter information corresponding to a target service flow; and the second network entity determines the jitter information corresponding to the target service flow based on the first information.

[0007] According to a third aspect, a communication method is provided, including: a third network entity sends second information to a first network entity, wherein the second information is used to trigger the first network entity to send first information to a second network entity, and the first information is used to request the second network entity to determine jitter information corresponding to a target service flow.

[0008] According to a fourth aspect, a communication method is provided, including: a fourth network entity receiving jitter information of a target service flow sent by the first network entity or the second network entity.

[0009] In a fifth aspect, a communication device is provided, including: a sending unit, configured to send first information to a second network entity, wherein the first information is used to request the second network entity to determine jitter information corresponding to a target service flow.

[0010] In the sixth aspect, a communication device is provided, including: a receiving unit for receiving first information sent by a first network entity, wherein the first information is used to request the device to determine the jitter information corresponding to the target business flow; and a determination unit for determining the jitter information corresponding to the target business flow based on the first information.

[0011] In the seventh aspect, a communication device is provided, including: a sending unit, used to send second information to a first network entity, the second information is used to trigger the first network entity to send first information to a second network entity, and the first information is used to request the second network entity to determine the jitter information corresponding to the target service flow.

[0012] In an eighth aspect, a communication device is provided, comprising: a receiving unit, configured to receive jitter information of a target service flow sent by a first network entity or a second network entity.

[0013] In the ninth 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 fourth aspects.

[0014] In a tenth 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 fourth aspects.

[0015] In an eleventh 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 fourth aspects.

[0016] In a twelfth 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 fourth aspects.

[0017] In a thirteenth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method described in any one of the first to fourth aspects.

[0018] In an embodiment of the present application, a first network entity sends first information to a second network entity, and the first information is used to request the second network entity to determine the jitter information corresponding to the target service flow, which helps the second network entity to determine the jitter information corresponding to the target service flow based on the first information, and further helps the access network device to optimize the CDRX configuration based on the jitter information corresponding to the target service flow. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0026] FIG8 is a schematic structural diagram of a communication device provided in one embodiment of the present application.

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

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

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

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

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

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] 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).

[0040] The following describes a system architecture in an embodiment of the present application in conjunction with FIG2 .

[0041] Figure 2 is the 5GS (5G system) architecture diagram, 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.

[0042] 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.

[0043] Enhanced Multimedia (XRM) service flows have a certain periodicity. For example, the server can send video frames of XRM services at a certain frame rate. Access network equipment (such as RAN or next generation radio access network (NG-RAN)) can optimize the connected mode discontinuous reception (CDRX) configuration in the connected state according to the period of the service flow to achieve device node management. However, due to multipath routing and coding complexity between the server and the core network elements (such as 5G core network (5GC) elements), the video frames of the XRM service may not be able to reach the access network device according to the predetermined period. Therefore, while providing the service flow period to the access network device, it is also necessary to provide the N6 jitter information corresponding to the service flow period (such as the jitter information between DN and UPF) to the access network device, thereby assisting the access network device in optimizing the CDXR configuration.

[0044] The existing standard simply proposes that the SMF request the UPF to obtain the N6 jitter range for a given period. The 5GC then derives the jitter information and forwards it, along with the period information, to the access network equipment. However, it is currently unclear how the jitter information corresponding to a service flow is obtained. For example, it is unclear when the SMF requests the N6 jitter range for a given period, what information the SMF sends to assist the UPF in identifying the target service flow to be monitored, and how the UPF forwards the measured N6 jitter range to the access network equipment.

[0045] In order to solve one or more of the above technical problems, the present application proposes a communication method and a communication device.

[0046] The embodiments of the present application are described in detail below with reference to FIG3 to FIG7 .

[0047] FIG3 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 300 shown in FIG3 may include step S320, which is as follows:

[0048] S320: The first network entity sends first information to the second network entity.

[0049] The first network entity may be an SMF, and the second network entity may be a UPF.

[0050] Optionally, the first information may be used to request the second network entity to determine jitter information corresponding to the target service flow. The jitter information may include at least one of the following information: jitter range, jitter average, and jitter variance.

[0051] Optionally, the jitter information corresponding to the target service flow may be N6 jitter information, for example, the jitter information of the target service flow between the UPF and the DN.

[0052] Optionally, the first information may include at least one of the following information: a jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

[0053] Optionally, the period information of the target service flow may be a period of a data burst of the target service flow.

[0054] Optionally, the flow description information may include at least one of the following information: packet filtering information of an Internet Protocol (IP) 5-tuple, an application identifier corresponding to the target service flow, an identifier (ID) of a target UE corresponding to the target service flow, an address of the target UE, and packet header information of a data packet corresponding to the target service flow. The IP 5-tuple packet filtering information may include a source address, a source port number, a destination address, a destination port number, and a supported protocol identifier (ID).

[0055] In an embodiment of the present application, a first network entity sends first information to a second network entity, and the first information is used to request the second network entity to determine the jitter information corresponding to the target service flow, which helps the second network entity to determine the jitter information corresponding to the target service flow based on the first information, and further helps the access network device to optimize the CDRX configuration based on the jitter information corresponding to the target service flow.

[0056] In some embodiments, before step S320, method 300 may further include step S310, which is as follows:

[0057] S310: The third network entity sends second information to the first network entity.

[0058] Optionally, the second information may be used to trigger the first network entity to send the first information. Optionally, the second information may include at least one of the following information: a jitter information acquisition instruction, periodic information of the target service flow, and flow description information of the target service flow. The jitter information acquisition instruction may instruct the first network entity to send the first information.

[0059] The second information may trigger the first network entity to send the first information in an explicit or implicit manner. For example, if the first information includes a jitter information acquisition instruction, then the second information is equivalent to explicitly triggering the first network entity to send the first information; if the first information includes periodic information and / or flow description information of the target service flow, then the second information is equivalent to implicitly triggering the first network entity to send the first information.

[0060] Optionally, the third network entity may be an AF. Optionally, the third network entity may send the second information to the first network entity through the PCF. It should be noted that the AF can be divided into a trusted AF and an untrusted AF. If the third network entity is a trusted AF, the second message may be sent directly to the PCF, and then the PCF forwards the second information to the first network entity; if the third network entity is an untrusted AF, the second message needs to be sent to the PCF through the network exposure function (NEF), and then the PCF forwards the second information to the first network entity.

[0061] Optionally, the third network entity may be an access network device, such as a RAN or NG-RAN. Optionally, the third network entity may send the second information to the first network entity through the AMF.

[0062] In some embodiments, after step S320, method 300 may further include step S330, which is as follows:

[0063] S330: The second network entity determines jitter information corresponding to the target service flow according to the first information.

[0064] For example, the second network entity may determine the target service flow according to the period information of the target service flow or the flow description information of the target service flow, and obtain the N6 jitter information corresponding to the target service flow based on its own implementation.

[0065] In some embodiments, after step S320, method 300 may further include step S340, which is as follows:

[0066] S340: The second network entity sends third information to the first network entity.

[0067] Optionally, the third information may include jitter information corresponding to the target service flow. Optionally, the third information may also include period information and / or flow description information of the target service flow.

[0068] In some embodiments, after step S320, method 300 may further include step S350, which is as follows:

[0069] S350: The first network entity sends fourth information to the fourth network entity.

[0070] Optionally, the fourth information may include jitter information corresponding to the target service flow. Optionally, the fourth information may also include period information and / or flow description information of the target service flow.

[0071] Optionally, the fourth network entity may be an access network device. Optionally, after receiving the third information sent by the second network entity, the first network entity may send the fourth information to the fourth network entity through the AMF.

[0072] In some embodiments, after step S320, method 300 may further include step S350, which is as follows:

[0073] S350: The second network entity sends fifth information to the fourth network entity.

[0074] Optionally, the fifth information may include jitter information corresponding to the target service flow. Optionally, the fifth information may also include period information and / or flow description information of the target service flow.

[0075] Optionally, the fourth network entity may be an access network device, such as a RAN or NG-RAN. Optionally, the second network entity may send the fifth information to the fourth network entity via a user interface. For example, the fourth network entity may add the fifth information to a General Packet Radio Service (GPRS) tunnel transport protocol user plane portion (GTP-U) header of a data packet (corresponding to the target service flow) and send the data packet to the fourth network entity. Accordingly, the fourth network entity may read the GTP-U header of the data packet to obtain the fifth information.

[0076] Furthermore, the fourth network entity may optimize the CDRX configuration according to the jitter information corresponding to the target service flow.

[0077] The above embodiment will be further described in detail below with reference to FIG. 4 to FIG. 7 .

[0078] Figure 4 is a schematic flow chart of a communication method according to an embodiment of the present application. In method 400 shown in Figure 4, the SMF may request the UPF to obtain the N6 jitter range associated with a given service flow period based on the indication information of the AF, and forward the jitter information to the RAN via the control plane. Method 400 may include steps S410 to S460, as follows:

[0079] S410 , the AF sends the second information to the PCF via a network exposure function (NEF).

[0080] The second information may include a jitter information acquisition indication, period information of the target service flow, and / or flow description information of the target service flow. The flow description information may include packet filtering information including an IP five-tuple (source address, source port number, destination address, destination port number, supported protocol ID), an application identifier corresponding to the target service flow, an identifier of the target UE, an address of the target UE, application layer header information of the data packet corresponding to the target service flow, and the like.

[0081] S420, the PCF forwards the second information to the SMF.

[0082] S430, SMF sends first information to UPF.

[0083] The first information may be used to request the second network entity to determine N6 jitter information corresponding to the target service flow. Optionally, the first information may include a jitter information acquisition instruction, period information of the target service flow, and / or flow description information of the target service flow.

[0084] S440, UPF determines the N6 jitter information corresponding to the target service flow based on the first information

[0085] The UPF can determine the target service flow based on its periodicity information or flow description information, and obtain the corresponding N6 jitter information of the target service flow based on its own implementation. N6 jitter information can include jitter range, jitter average, jitter variance, etc.

[0086] S450, UPF sends the third information to SMF.

[0087] The third information may include N6 jitter information corresponding to the target service flow, period information of the target service flow, and flow description information of the target service flow.

[0088] S460: The SMF sends fourth information to the RAN.

[0089] The SMF may send fourth information to the fourth network entity through the AMF. The fourth information may include N6 jitter information corresponding to the target service flow, periodic information of the target service flow, and flow description information of the target service flow.

[0090] Furthermore, the RAN can optimize the CDRX configuration based on the N6 jitter information corresponding to the target service flow.

[0091] Figure 5 is a schematic flow chart of a communication method according to an embodiment of the present application. In the method 500 shown in Figure 5, the SMF may request the UPF to obtain the N6 jitter range associated with a given service flow period based on the indication information of the AF, and forward the jitter information to the RAN via the user plane. The method 500 may include steps S510 to S550, as follows:

[0092] S510: The AF sends the second information to the PCF via the NEF.

[0093] The second information may include a jitter information acquisition indication, period information of the target service flow, and / or flow description information of the target service flow. The flow description information may include packet filtering information including an IP five-tuple (source address, source port number, destination address, destination port number, supported protocol ID), an application identifier corresponding to the target service flow, an identifier of the target UE, an address of the target UE, application layer header information of the data packet corresponding to the target service flow, and the like.

[0094] S520: The PCF forwards the second information to the SMF.

[0095] S530, SMF sends first information to UPF.

[0096] The first information may be used to request the second network entity to determine N6 jitter information corresponding to the target service flow. Optionally, the first information may include a jitter information acquisition instruction, period information of the target service flow, and / or flow description information of the target service flow.

[0097] S540, UPF determines N6 jitter information corresponding to the target service flow based on the first information.

[0098] The UPF can determine the target service flow based on its periodicity information or flow description information, and obtain the corresponding N6 jitter information of the target service flow based on its own implementation. N6 jitter information can include jitter range, jitter average, jitter variance, etc.

[0099] The UPF adds the obtained N6 jitter information to the GTP-U header of the data packet and forwards the data packet to the RAN via the user plane (in downlink transmission (DL traffic)).

[0100] S550: RAN obtains N6 jitter information corresponding to the target service flow.

[0101] The RAN can read the GTP-U header of the data packet to obtain N6 jitter information and optimize the CDRX configuration based on the periodicity information of the target service flow. The periodicity information of the target service flow can be sent to the RAN by the control plane or added to the GTP-U header and sent to the RAN by the user plane.

[0102] Furthermore, the RAN can optimize the CDRX configuration based on the N6 jitter information corresponding to the target service flow.

[0103] Figure 6 is a schematic flow chart of a communication method according to an embodiment of the present application. In method 600 shown in Figure 6, the SMF may request the UPF to obtain the N6 jitter range associated with a given service flow period based on the indication information from the RAN, and forward the jitter information to the RAN via the control plane. Method 600 may include steps S610 to S660, as follows:

[0104] S610: RAN sends the second information to AMF.

[0105] The second information may include a jitter information acquisition indication, period information of the target service flow, and / or flow description information of the target service flow. The flow description information may include packet filtering information including an IP five-tuple (source address, source port number, destination address, destination port number, supported protocol ID), an application identifier corresponding to the target service flow, an identifier of the target UE, an address of the target UE, application layer header information of the data packet corresponding to the target service flow, and the like.

[0106] S620, AMF forwards the second information to SMF.

[0107] S630, SMF sends first information to UPF.

[0108] The first information may be used to request the second network entity to determine N6 jitter information corresponding to the target service flow. Optionally, the first information may include a jitter information acquisition instruction, period information of the target service flow, and / or flow description information of the target service flow.

[0109] S640: UPF determines N6 jitter information corresponding to the target service flow based on the first information.

[0110] The UPF can determine the target service flow based on its periodicity information or flow description information, and obtain the corresponding N6 jitter information of the target service flow based on its own implementation. N6 jitter information can include jitter range, jitter average, jitter variance, etc.

[0111] S650, UPF sends the third information to SMF.

[0112] The third information may include N6 jitter information corresponding to the target service flow, period information of the target service flow, and flow description information of the target service flow.

[0113] S660: The SMF sends fourth information to the RAN.

[0114] The SMF may send fourth information to the fourth network entity through the AMF. The fourth information may include N6 jitter information corresponding to the target service flow, periodic information of the target service flow, and flow description information of the target service flow.

[0115] Furthermore, the RAN can optimize the CDRX configuration based on the N6 jitter information corresponding to the target service flow.

[0116] Figure 7 is a schematic flow chart of a communication method according to an embodiment of the present application. In method 700 shown in Figure 7, the SMF may request the UPF to obtain the N6 jitter range associated with a given service flow period based on the indication information of the RAN, and forward the jitter information to the RAN via the user plane. Method 700 may include steps S710 to S750, as follows:

[0117] S710: RAN sends the second information to AMF.

[0118] The second information may include a jitter information acquisition indication, period information of the target service flow, and / or flow description information of the target service flow. The flow description information may include packet filtering information including an IP five-tuple (source address, source port number, destination address, destination port number, supported protocol ID), an application identifier corresponding to the target service flow, an identifier of the target UE, an address of the target UE, application layer header information of the data packet corresponding to the target service flow, and the like.

[0119] S720, AMF forwards the second information to SMF.

[0120] S730, SMF sends first information to UPF.

[0121] The first information may be used to request the second network entity to determine N6 jitter information corresponding to the target service flow. Optionally, the first information may include a jitter information acquisition instruction, period information of the target service flow, and / or flow description information of the target service flow.

[0122] S740, UPF determines N6 jitter information corresponding to the target service flow based on the first information.

[0123] The UPF can determine the target service flow based on its periodicity information or flow description information, and obtain the corresponding N6 jitter information of the target service flow based on its own implementation. N6 jitter information can include jitter range, jitter average, jitter variance, etc.

[0124] The UPF adds the obtained N6 jitter information to the GTP-U header of the data packet and forwards the data packet to the RAN via the user plane (in downlink transmission (DL traffic)).

[0125] S750: RAN obtains N6 jitter information corresponding to the target service flow.

[0126] The RAN can read the GTP-U header of the data packet to obtain N6 jitter information and optimize the CDRX configuration based on the periodicity information of the target service flow. The periodicity information of the target service flow can be sent to the RAN by the control plane or added to the GTP-U header and sent to the RAN by the user plane.

[0127] Furthermore, the RAN can optimize the CDRX configuration based on the N6 jitter information corresponding to the target service flow.

[0128] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 7 , and the device embodiment of the present application is described in detail below in conjunction with Figures 8 to 12 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, and therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0129] FIG8 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG8 , the device 800 includes a sending unit 810, which is specifically as follows:

[0130] The sending unit 810 is configured to send first information to a second network entity, where the first information is used to request the second network entity to determine jitter information corresponding to a target service flow.

[0131] Optionally, the first information includes at least one of the following information: a jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

[0132] Optionally, the apparatus 800 further includes a receiving unit 820, which is configured to receive second information sent by a third network entity before sending the first information to the second network entity, where the second information is used to trigger the apparatus to send the first information.

[0133] Optionally, the second information includes at least one of the following information: a jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

[0134] Optionally, the third network entity is an application function AF, and the receiving unit is specifically configured to receive the second information sent by the third network entity through a policy control function PCF.

[0135] Optionally, the third network entity is an access network device, and the receiving unit 820 is specifically used to: receive the second information sent by the third network entity through the access and mobility management function AMF.

[0136] Optionally, the apparatus 800 further includes a receiving unit 820, configured to receive third information sent by the second network entity, where the third information includes jitter information corresponding to the target service flow.

[0137] Optionally, the third information also includes period information and / or flow description information of the target service flow.

[0138] Optionally, the sending unit 810 is further configured to send fourth information to a fourth network entity, where the fourth information includes jitter information corresponding to the target service flow.

[0139] Optionally, the fourth network entity is an access network device, and the sending unit 810 is specifically used to: send the fourth information to the fourth network entity through the access and mobility management function AMF.

[0140] Optionally, the access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0141] Optionally, the fourth information also includes period information and / or flow description information of the target service flow.

[0142] Optionally, the period information of the target service flow is the period of the data burst of the target service flow.

[0143] Optionally, the flow description information includes at least one of the following information: packet filtering information of the Internet Protocol IP quintuple, the application identifier corresponding to the target service flow, the identifier of the target UE corresponding to the target service flow, the address of the target UE, and the header information of the data packet corresponding to the target service flow.

[0144] Optionally, the jitter information is N6 jitter information.

[0145] Optionally, the N6 jitter information is jitter information of the target service flow between the user plane function UPF and the data network DN.

[0146] Optionally, the jitter information includes at least one of the following information: jitter range, jitter average value, and jitter variance.

[0147] Optionally, the device is a session management function SMF, and the second network entity is a user plane function UPF.

[0148] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 900 in FIG9 includes a receiving unit 910 and a determining unit 920, which are specifically as follows:

[0149] A receiving unit 910 is configured to receive first information sent by a first network entity, where the first information is used to request the apparatus to determine jitter information corresponding to a target service flow;

[0150] The determining unit 920 is configured to determine jitter information corresponding to the target service flow based on the first information.

[0151] Optionally, the first information includes at least one of the following information: a jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

[0152] Optionally, the apparatus 900 further includes a sending unit 930, configured to send third information to the first network entity, where the third information includes jitter information corresponding to the target service flow.

[0153] Optionally, the third information also includes period information and / or flow description information of the target service flow.

[0154] Optionally, the apparatus 900 further includes a sending unit 930, configured to send fifth information to a fourth network entity, where the fifth information includes jitter information corresponding to the target service flow.

[0155] Optionally, the fourth network entity is an access network device, and the sending unit 930 is specifically configured to send the fifth information to the fourth network entity via a user.

[0156] Optionally, the access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0157] Optionally, the fifth information also includes period information and / or flow description information of the target service flow.

[0158] Optionally, the period information of the target service flow is the period of the data burst of the target service flow.

[0159] Optionally, the flow description information includes at least one of the following information: packet filtering information of the Internet Protocol IP quintuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

[0160] Optionally, the jitter information is N6 jitter information.

[0161] Optionally, the N6 jitter information is jitter information of the target service flow between the user plane function UPF and the data network DN.

[0162] Optionally, the jitter information includes at least one of the following information: jitter range, jitter average value, and jitter variance.

[0163] Optionally, the first network entity is a session management function SMF, and the device is a user plane function UPF.

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

[0165] The sending unit 1010 is used to send second information to the first network entity, where the second information is used to trigger the first network entity to send first information to the second network entity, where the first information is used to request the second network entity to determine jitter information corresponding to the target service flow.

[0166] Optionally, the second information includes at least one of the following information: a jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

[0167] Optionally, the period information of the target service flow is the period of the data burst of the target service flow.

[0168] Optionally, the flow description information includes at least one of the following information: packet filtering information of the Internet Protocol IP quintuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

[0169] Optionally, the device is an application function AF, and the sending unit 1010 is specifically used to: send the second information to the first network entity through a policy control function PCF.

[0170] Optionally, the device is an access network device, and the sending unit 1010 is specifically used to: send the second information to the first network entity through the access and mobility management function AMF.

[0171] Optionally, the access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0172] Optionally, the first network entity is a session management function SMF, and the second network entity is a user plane function UPF.

[0173] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1100 in FIG11 includes a receiving unit 1110, which is specifically as follows:

[0174] The receiving unit 1110 is configured to receive jitter information of a target service flow sent by the first network entity or the second network entity.

[0175] Optionally, the receiving unit 1110 is specifically used to: receive fourth information sent by the first network entity through the access and mobility management function AMF, where the fourth information includes jitter information corresponding to the target service flow.

[0176] Optionally, the fourth information also includes period information and / or flow description information of the target service flow.

[0177] Optionally, the receiving unit 1110 is specifically configured to: receive fifth information sent by the second network entity through a user plane, where the fifth information includes jitter information corresponding to the target service flow.

[0178] Optionally, the fifth information also includes period information and / or flow description information of the target service flow.

[0179] Optionally, the period information of the target service flow is the period of the data burst of the target service flow.

[0180] Optionally, the flow description information includes at least one of the following information: packet filtering information of the Internet Protocol IP quintuple, the application identifier corresponding to the target service flow, the identifier of the target UE corresponding to the target service flow, the address of the target UE, and the header information of the data packet corresponding to the target service flow.

[0181] Optionally, the jitter information is N6 jitter information.

[0182] Optionally, the N6 jitter information is jitter information of the target service flow between the user plane function UPF and the data network DN.

[0183] Optionally, the jitter information includes at least one of the following information: jitter range, jitter average value, and jitter variance.

[0184] Optionally, the first network entity is a session management function SMF, the second network entity is a user plane function UPF, and the device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0185] FIG12 is a schematic block diagram of an apparatus according to an embodiment of the present application. The dashed lines in FIG12 indicate that the unit or module is optional. Apparatus 1200 may be used to implement the method described in the above method embodiment. Apparatus 1200 may be a chip or a communication device.

[0186] The device 1200 may include one or more processors 1210. The processor 1210 may support the device 1200 to implement the method described in the above method embodiment. The processor 1210 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.

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

[0188] The apparatus 1200 may further include a transceiver 1230. The processor 1210 may communicate with other devices or chips via the transceiver 1230. For example, the processor 1210 may transmit and receive data with other devices or chips via the transceiver 1230.

[0189] 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.

[0190] 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.

[0191] 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.

[0192] 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.

[0193] 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.

[0194] 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.

[0195] 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.

[0196] 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 this embodiment according to actual needs.

[0197] 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.

[0198] 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)).

[0199] 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 this application. Therefore, the scope of protection of this 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 sends first information to the second network entity, where the first information is used to request the second network entity to determine jitter information corresponding to a target service flow.

2. The method according to claim 1, characterized in that The first information includes at least one of the following information: Jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

3. The method according to claim 1 or 2, characterized in that Before the first network entity sends the first information to the second network entity, the method further includes: The first network entity receives second information sent by a third network entity, where the second information is used to trigger the first network entity to send the first information.

4. The method according to claim 3, characterized in that The second information includes at least one of the following information: Jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

5. The method according to claim 3 or 4, characterized in that The third network entity is an application function AF, and the first network entity receives the second information sent by the third network entity, including: The first network entity receives the second information sent by the third network entity through a policy control function (PCF).

6. The method according to claim 3 or 4, characterized in that The third network entity is an access network device, and the first network entity receives the second information sent by the third network entity, including: The first network entity receives the second information sent by the third network entity through the access and mobility management function AMF.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The first network entity receives third information sent by the second network entity, where the third information includes jitter information corresponding to the target service flow.

8. The method according to claim 7, characterized in that The third information also includes period information and / or flow description information of the target service flow.

9. The method according to claim 7 or 8, characterized in that The method further comprises: The first network entity sends fourth information to a fourth network entity, where the fourth information includes jitter information corresponding to the target service flow.

10. The method according to claim 9, characterized in that The fourth network entity is an access network device, and the first network entity sends fourth information to the fourth network entity, including: The first network entity sends the fourth information to the fourth network entity through the access and mobility management function AMF.

11. The method according to claim 6 or 10, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

12. The method according to any one of claims 9 to 11, characterized in that The fourth information also includes period information and / or flow description information of the target service flow.

13. The method according to claim 2, 4, 8 or 12, characterized in that The period information of the target service flow is the period of the data burst of the target service flow.

14. The method according to claim 2, 4, 8 or 12, characterized in that The flow description information includes at least one of the following information: Packet filtering information of the Internet Protocol IP quintuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

15. The method according to any one of claims 1 to 14, characterized in that The jitter information is N6 jitter information.

16. The method according to claim 15, characterized in that The N6 jitter information is the jitter information of the target service flow between the user plane function UPF and the data network DN.

17. The method according to any one of claims 1 to 16, characterized in that The jitter information includes at least one of the following information: jitter range, jitter average value, and jitter variance.

18. The method according to any one of claims 1 to 17, characterized in that The first network entity is a session management function SMF, and the second network entity is a user plane function UPF.

19. A communication method, characterized in that: include: The second network entity receives first information sent by the first network entity, where the first information is used to request the second network entity to determine jitter information corresponding to the target service flow; The second network entity determines jitter information corresponding to the target service flow according to the first information.

20. The method according to claim 19, wherein The first information includes at least one of the following information: Jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

21. The method according to claim 19 or 20, characterized in that The method further comprises: The second network entity sends third information to the first network entity, where the third information includes jitter information corresponding to the target service flow.

22. The method according to claim 21, characterized in that The third information also includes period information and / or flow description information of the target service flow.

23. The method according to claim 19 or 20, characterized in that The method further comprises: The second network entity sends fifth information to the fourth network entity, where the fifth information includes jitter information corresponding to the target service flow.

24. The method according to claim 23, wherein The fourth network entity is an access network device, and the second network entity sends fifth information to the fourth network entity, including: The second network entity sends the fifth information to the fourth network entity through a user.

25. The method according to claim 24, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

26. The method according to any one of claims 23 to 25, characterized in that The fifth information also includes period information and / or flow description information of the target service flow.

27. The method according to claim 20, 22 or 26, characterized in that The period information of the target service flow is the period of the data burst of the target service flow.

28. The method according to claim 20, 22 or 26, characterized in that The flow description information includes at least one of the following information: Packet filtering information of the Internet Protocol IP quintuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

29. The method according to any one of claims 19 to 28, characterized in that The jitter information is N6 jitter information.

30. The method according to claim 29, wherein The N6 jitter information is the jitter information of the target service flow between the user plane function UPF and the data network DN.

31. The method according to any one of claims 19 to 30, characterized in that The jitter information includes at least one of the following information: jitter range, jitter average value, and jitter variance.

32. The method according to any one of claims 19 to 31, characterized in that The first network entity is a session management function SMF, and the second network entity is a user plane function UPF.

33. A communication method, characterized in that: include: The third network entity sends second information to the first network entity, where the second information is used to trigger the first network entity to send first information to the second network entity, where the first information is used to request the second network entity to determine jitter information corresponding to the target service flow.

34. The method according to claim 33, wherein The second information includes at least one of the following information: Jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

35. The method according to claim 34, wherein The period information of the target service flow is the period of the data burst of the target service flow.

36. The method according to claim 34, wherein The flow description information includes at least one of the following information: Packet filtering information of the Internet Protocol IP quintuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

37. The method according to any one of claims 33 to 36, characterized in that The third network entity is an application function AF, and the third network entity sends the second information to the first network entity, including: The third network entity sends the second information to the first network entity through a policy control function PCF.

38. The method according to any one of claims 33 to 36, characterized in that The third network entity is an access network device, and the third network entity sends the second information to the first network entity, including: The third network entity sends the second information to the first network entity through the access and mobility management function AMF.

39. The method according to claim 38, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

40. The method according to any one of claims 33 to 39, characterized in that The first network entity is a session management function SMF, and the second network entity is a user plane function UPF.

41. A communication method, characterized in that: include: The fourth network entity receives the jitter information of the target service flow sent by the first network entity or the second network entity.

42. The method according to claim 41, wherein The fourth network entity receiving jitter information of a target service flow sent by the first network entity or the second network entity includes: The fourth network entity receives fourth information sent by the first network entity through the access and mobility management function AMF, where the fourth information includes jitter information corresponding to the target service flow.

43. The method according to claim 42, characterized in that The fourth information also includes period information and / or flow description information of the target service flow.

44. The method according to any one of claims 41 to 43, characterized in that The fourth network entity receiving jitter information of a target service flow sent by the first network entity or the second network entity includes: The fourth network entity receives fifth information sent by the second network entity through the user plane, where the fifth information includes jitter information corresponding to the target service flow.

45. The method according to claim 44, wherein The fifth information also includes period information and / or flow description information of the target service flow.

46. ​​The method according to claim 43 or 45, characterized in that The period information of the target service flow is the period of the data burst of the target service flow.

47. The method according to claim 43 or 45, characterized in that The flow description information includes at least one of the following information: Packet filtering information of the Internet Protocol IP quintuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

48. The method according to any one of claims 41 to 47, characterized in that The jitter information is N6 jitter information.

49. The method according to claim 48, characterized in that The N6 jitter information is the jitter information of the target service flow between the user plane function UPF and the data network DN.

50. The method according to any one of claims 41 to 49, characterized in that The jitter information includes at least one of the following information: jitter range, jitter average value, and jitter variance.

51. The method according to any one of claims 41 to 50, characterized in that The first network entity is a session management function SMF, the second network entity is a user plane function UPF, and the fourth network entity is a radio access network RAN ​​or a next generation radio access network NG-RAN.

52. A communication device, characterized in that include: A sending unit is used to send first information to a second network entity, where the first information is used to request the second network entity to determine jitter information corresponding to a target service flow.

53. The device according to claim 52, characterized in that The first information includes at least one of the following information: a jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

54. The device according to claim 52 or 53, characterized in that The apparatus further includes a receiving unit, which is configured to receive second information sent by a third network entity before sending the first information to the second network entity, where the second information is used to trigger the apparatus to send the first information.

55. The device according to claim 54, characterized in that The second information includes at least one of the following information: a jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

56. The device according to claim 54 or 55, characterized in that The third network entity is an application function AF, and the receiving unit is specifically configured to receive the second information sent by the third network entity through a policy control function PCF.

57. The device according to claim 54 or 55, characterized in that The third network entity is an access network device, and the receiving unit is specifically used to: receive the second information sent by the third network entity through the access and mobility management function AMF.

58. The device according to any one of claims 52 to 57, characterized in that The device further includes a receiving unit configured to receive third information sent by the second network entity, where the third information includes jitter information corresponding to the target service flow.

59. The device according to claim 58, characterized in that The third information also includes period information and / or flow description information of the target service flow.

60. The device according to claim 58 or 59, characterized in that The sending unit is further configured to send fourth information to a fourth network entity, where the fourth information includes jitter information corresponding to the target service flow.

61. The device according to claim 60, characterized in that The fourth network entity is an access network device, and the sending unit is specifically used to: send the fourth information to the fourth network entity through the access and mobility management function AMF.

62. The device according to claim 57 or 61, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

63. The device according to any one of claims 60 to 62, characterized in that The fourth information also includes period information and / or flow description information of the target service flow.

64. The device according to claim 53, 55, 59 or 61, characterized in that The period information of the target service flow is the period of the data burst of the target service flow.

65. The device according to claim 53, 55, 59 or 61, characterized in that The flow description information includes at least one of the following information: packet filtering information of the Internet Protocol IP five-tuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

66. The device according to any one of claims 52 to 65, characterized in that The jitter information is N6 jitter information.

67. The device according to claim 66, characterized in that The N6 jitter information is the jitter information of the target service flow between the user plane function UPF and the data network DN.

68. The device according to any one of claims 52 to 67, characterized in that The jitter information includes at least one of the following information: jitter range, jitter average value, and jitter variance.

69. The device according to any one of claims 52 to 68, characterized in that The device is a session management function SMF, and the second network entity is a user plane function UPF.

70. A communication device, characterized in that include: a receiving unit, configured to receive first information sent by a first network entity, wherein the first information is used to request the apparatus to determine jitter information corresponding to a target service flow; A determination unit is used to determine the jitter information corresponding to the target service flow based on the first information.

71. The device according to claim 70, characterized in that The first information includes at least one of the following information: a jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

72. The device according to claim 70 or 71, characterized in that The device further includes a sending unit configured to send third information to the first network entity, where the third information includes jitter information corresponding to the target service flow.

73. The device according to claim 72, characterized in that The third information also includes period information and / or flow description information of the target service flow.

74. The device according to claim 70 or 71, characterized in that The apparatus further includes a sending unit configured to send fifth information to a fourth network entity, where the fifth information includes jitter information corresponding to the target service flow.

75. The device according to claim 74, characterized in that The fourth network entity is an access network device, and the sending unit is specifically configured to send the fifth information to the fourth network entity through a user.

76. The device according to claim 75, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

77. The device according to any one of claims 74 to 76, characterized in that The fifth information also includes period information and / or flow description information of the target service flow.

78. The device according to claim 71, 73 or 77, characterized in that The period information of the target service flow is the period of the data burst of the target service flow.

79. The device according to claim 71, 73 or 77, characterized in that The flow description information includes at least one of the following information: packet filtering information of the Internet Protocol IP five-tuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

80. The device according to any one of claims 70 to 79, characterized in that The jitter information is N6 jitter information.

81. The device according to claim 80, characterized in that The N6 jitter information is the jitter information of the target service flow between the user plane function UPF and the data network DN.

82. The device according to any one of claims 70 to 81, characterized in that The jitter information includes at least one of the following information: jitter range, jitter average value, and jitter variance.

83. The device according to any one of claims 70 to 82, characterized in that The first network entity is a session management function SMF, and the device is a user plane function UPF.

84. A communication device, characterized in that include: A sending unit is used to send second information to a first network entity, where the second information is used to trigger the first network entity to send first information to a second network entity, where the first information is used to request the second network entity to determine jitter information corresponding to a target service flow.

85. The device according to claim 84, characterized in that The second information includes at least one of the following information: a jitter information acquisition indication, period information of the target service flow, and flow description information of the target service flow.

86. The device according to claim 85, characterized in that The period information of the target service flow is the period of the data burst of the target service flow.

87. The device according to claim 85, characterized in that The flow description information includes at least one of the following information: packet filtering information of the Internet Protocol IP five-tuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

88. The device according to any one of claims 84 to 87, characterized in that The device is an application function AF, and the sending unit is specifically configured to send the second information to the first network entity through a policy control function PCF.

89. The device according to any one of claims 84 to 87, characterized in that The device is an access network device, and the sending unit is specifically used to: send the second information to the first network entity through the access and mobility management function AMF.

90. The device according to claim 89, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

91. The device according to any one of claims 84 to 90, characterized in that The first network entity is a session management function SMF, and the second network entity is a user plane function UPF.

92. A communication device, characterized in that include: The receiving unit is configured to receive jitter information of a target service flow sent by the first network entity or the second network entity.

93. The device according to claim 92, characterized in that The receiving unit is specifically used to: receive fourth information sent by the first network entity through the access and mobility management function AMF, where the fourth information includes jitter information corresponding to the target service flow.

94. The device according to claim 93, characterized in that The fourth information also includes period information and / or flow description information of the target service flow.

95. The device according to any one of claims 92 to 94, characterized in that The receiving unit is specifically configured to receive fifth information sent by the second network entity through a user plane, where the fifth information includes jitter information corresponding to the target service flow.

96. The device according to claim 95, characterized in that The fifth information also includes period information and / or flow description information of the target service flow.

97. The device according to claim 94 or 96, characterized in that The period information of the target service flow is the period of the data burst of the target service flow.

98. The device according to claim 94 or 96, characterized in that The flow description information includes at least one of the following information: packet filtering information of the Internet Protocol IP five-tuple, the application identifier corresponding to the target business flow, the identifier of the target UE corresponding to the target business flow, the address of the target UE, and the header information of the data packet corresponding to the target business flow.

99. The device according to any one of claims 92 to 98, characterized in that The jitter information is N6 jitter information.

100. The device according to claim 99, characterized in that The N6 jitter information is the jitter information of the target service flow between the user plane function UPF and the data network DN.

101. The device according to any one of claims 92 to 100, characterized in that The jitter information includes at least one of the following information: jitter range, jitter average value, and jitter variance.

102. The device according to any one of claims 92 to 101, characterized in that The first network entity is a session management function SMF, the second network entity is a user plane function UPF, and the device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

103. 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 51.

104. 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 51.

105. 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 51.

106. 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 51.

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

Images