Communication method and apparatus

Abstract

The application provides a communication method and device, the method comprises the following steps: sending time delay information, the time delay information is related to the air interface time delay corresponding to at least one terminal device acquired by the access network side, the air interface time delay is the transmission time delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device, the time delay information is used for determining the routing strategy corresponding to the at least one terminal device, and the routing strategy is used for the transmission of the bearer network between the core network device and the access network device, so that the user experience can be improved within the time delay requirement.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] In recent years, with the continuous development of 5G communication systems, data transmission latency has been continuously reduced and transmission capacity has been increasing. 5G communication systems are gradually penetrating some multimedia services with strong real-time requirements and large data capacity requirements, such as video transmission, cloud gaming (CG), and extended reality (XR). Among them, XR includes virtual reality (VR) and augmented reality (AR). Compared with traditional video services, XR has advantages such as multiple perspectives and strong interactivity, providing users with a brand-new visual experience.

[0003] However, XR services have relatively strict end-to-end latency requirements. Taking downlink transmission as an example, XR service data packets need to be transmitted from the server to the terminal device within a certain time. For example, cloud extended reality (Cloud XR) services have strict network latency requirements; the motion-to-photons (MTP) latency must be less than 20ms to provide a partially immersive experience. If asynchronous rendering technology is used, the end-to-end interaction latency is 70 milliseconds (ms). After deducting the encoding and rendering latency on the server side and the decoding processing latency on the terminal, the network transmission latency is 20ms, with 10ms each for uplink and downlink transmission. In recent years, with the evolution of XR services, the latency requirements for the network have become even more stringent, posing a significant challenge to communication systems. Therefore, how to ensure user experience within latency requirements is a technical problem that urgently needs to be solved by those in the field. Summary of the Invention

[0004] This application proposes a communication method and apparatus that can improve user experience within latency requirements.

[0005] In a first aspect, embodiments of this application provide a communication method that can be applied to the network side, such as an access network device, a module (e.g., processor, circuit, chip, or chip system) within the access network device, or a logical node, logical module, or software capable of implementing all or part of the functions of the access network device. Taking the application of this method to an access network device as an example, the method includes: sending delay information, which is related to the air interface delay corresponding to at least one terminal device obtained by the access network side. The air interface delay is the transmission delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The delay information is used to determine a routing strategy corresponding to the at least one terminal device, and the routing strategy is used for bearer network transmission between the core network device and the access network device.

[0006] In the above method, by sending latency information related to the air interface latency of at least one terminal device, the core network device can take this latency information into account when determining the routing strategy for at least one terminal device. For example, if the latency information is the air interface latency, in a multi-user scenario, for terminal devices with a relatively large air interface latency, a better routing strategy can be selected when determining the routing strategy. A better routing strategy can reduce the N3 segment routing latency (i.e., the transmission latency between the core network device and the access network device). For terminal devices with a relatively small air interface latency, a worse routing strategy can be selected when determining the routing strategy. This achieves a "mutual borrowing" between air interface latency and N3 segment routing latency, avoiding exceeding the end-to-end latency constraint, thereby improving the user experience within the latency requirements.

[0007] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0008] In another possible implementation, the method further includes receiving a delay response message, which is a response to the delay message.

[0009] In the above method, it is possible to know in a timely manner whether the core network equipment has received the delay information, thereby ensuring the reliability of the delay information transmission.

[0010] Secondly, embodiments of this application provide a communication method that can be applied to the network side, such as core network equipment, modules (e.g., processors, circuits, chips, or chip systems) within the core network equipment, or logical nodes, logical modules, or software capable of implementing all or part of the core network equipment's functions. Taking the application of this method to a core network equipment, where the core network equipment is a User Plane Function (UPF) network element, as an example, the method includes: receiving a routing policy corresponding to at least one terminal device. This routing policy is determined based on latency information, which is related to the air interface latency corresponding to at least one terminal device obtained by the access network side. The air interface latency is the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network equipment. This routing policy is used for bearer network transmission between the core network equipment and the access network equipment.

[0011] In the above method, by receiving and executing the routing policy corresponding to at least one terminal device, the user experience of multiple users can be guaranteed in multi-user scenarios.

[0012] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0013] In another possible implementation, the method further includes sending a first request message, the first request message including the delay information, the first request message being used to request the routing policy.

[0014] In another possible implementation, the method further includes receiving the delay information.

[0015] In another possible implementation, the method further includes sending a delay response message, which is a response to the delay message.

[0016] In the above method, the delay information can be promptly notified whether it has been received, thereby ensuring the reliability of the delay information transmission.

[0017] In another possible implementation, the method further includes sending routing policy response information, which is a response to the routing policy.

[0018] In the above method, the receipt of routing policies can be notified in a timely manner, thereby ensuring the reliability of routing policy transmission.

[0019] Thirdly, embodiments of this application provide a communication method that can be applied to the network side, such as core network equipment, modules (e.g., processors, circuits, chips, or chip systems) within the core network equipment, or logical nodes, logical modules, or software capable of implementing all or part of the core network equipment's functions. Taking the application of this method to a core network equipment, where the core network equipment is a User Plane Function (UPF) network element, as an example, the method includes: receiving latency information, which is related to the air interface latency corresponding to at least one terminal device obtained by the access network side. The air interface latency is the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network equipment. The latency information is used to determine a routing strategy corresponding to the at least one terminal device, and the routing strategy is used for bearer network transmission between the core network equipment and the access network equipment.

[0020] In the above method, by receiving latency information related to the air interface latency of at least one terminal device, the core network device can take this latency information into account when determining the routing strategy for at least one terminal device. For example, if the latency information is the air interface latency, in a multi-user scenario, for terminal devices with a relatively large air interface latency, a better routing strategy can be selected when determining the routing strategy. A better routing strategy can reduce the N3 segment routing latency (i.e., the transmission latency between the core network device and the access network device). For terminal devices with a relatively small air interface latency, a worse routing strategy can be selected when determining the routing strategy. This achieves a "mutual borrowing" between air interface latency and N3 segment routing latency, avoiding exceeding the end-to-end latency constraint, thereby improving the user experience within the latency requirements.

[0021] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0022] In another possible implementation, the method also includes receiving the routing policy.

[0023] In another possible implementation, the method further includes sending a first request message, the first request message including the delay information, the first request message being used to request the routing policy.

[0024] In another possible implementation, the method further includes sending a delay response message, which is a response to the delay message.

[0025] In the above method, the delay information can be promptly notified whether it has been received, thereby ensuring the reliability of the delay information transmission.

[0026] In another possible implementation, the method further includes sending routing policy response information, which is a response to the routing policy.

[0027] In the above method, the receipt of routing policies can be notified in a timely manner, thereby ensuring the reliability of routing policy transmission.

[0028] Fourthly, embodiments of this application provide a communication method that can be applied to the network side, such as core network equipment, modules (e.g., processors, circuits, chips, or chip systems) within the core network equipment, or logical nodes, logical modules, or software capable of implementing all or part of the core network equipment's functions. Taking the application of this method to a core network equipment, where the core network equipment is a Session Management Function (SMF) network element, as an example, the method includes: acquiring latency information, which is related to the air interface latency corresponding to at least one terminal device acquired by the access network side, and the air interface latency being the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network equipment; determining a routing strategy corresponding to the at least one terminal device based on the latency information, the routing strategy being used for bearer network transmission between the core network equipment and the access network equipment; and sending the routing strategy.

[0029] In the above method, by receiving latency information related to the air interface latency of at least one terminal device, this latency information is considered when determining the routing strategy for at least one terminal device. For example, if the latency information is the air interface latency, in a multi-user scenario, for terminal devices with a relatively large air interface latency, a better routing strategy is selected when determining the routing strategy. A better routing strategy can reduce the N3 segment routing latency (i.e., the transmission latency between the core network device and the access network device). For terminal devices with a relatively small air interface latency, a worse routing strategy is selected when determining the routing strategy. This achieves "mutual borrowing" between air interface latency and N3 segment routing latency, avoiding exceeding the end-to-end latency constraint, thereby improving the user experience within the latency requirements.

[0030] In one possible implementation, the method further includes: receiving a first request message, the first request message including the delay information, the first request message being used to request the routing policy.

[0031] In another possible implementation, acquiring the delay information includes receiving the delay information.

[0032] In another possible implementation, the method further includes receiving routing policy response information, which is a response to the routing policy.

[0033] In the above method, it is possible to know in a timely manner whether the core network device has received the routing policy, thereby ensuring the reliability of the routing policy transmission.

[0034] Fifthly, embodiments of this application provide a communication method that can be applied to the network side, such as core network equipment on the network side, modules (e.g., processors, circuits, chips, or chip systems) within the core network equipment, or logical nodes, logical modules, or software capable of implementing all or part of the core network equipment's functions. Taking the application of this method to a core network equipment, where the core network equipment is an Access and Mobility Management Function (AMF) network element, as an example, the method includes: receiving delay information, which is related to the air interface delay corresponding to at least one terminal device obtained by the access network side, and the air interface delay being the transmission delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network equipment; and sending the delay information, which is used to determine a routing strategy corresponding to the at least one terminal device, and the routing strategy is used for bearer network transmission between the core network equipment and the access network equipment.

[0035] In the above method, by sending latency information related to the air interface latency of at least one terminal device, it is beneficial to consider this latency information when determining the routing strategy for at least one terminal device. For example, if the latency information is the air interface latency, in a multi-user scenario, for terminal devices with a relatively large air interface latency, a better routing strategy can be selected when determining the routing strategy. A better routing strategy can reduce the N3 segment routing latency (i.e., the transmission latency between the core network device and the access network device). For terminal devices with a relatively small air interface latency, a worse routing strategy can be selected when determining the routing strategy. This achieves "mutual borrowing" between air interface latency and N3 segment routing latency, avoiding exceeding the end-to-end latency constraint, thereby improving the user experience within the latency requirements.

[0036] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0037] Sixthly, embodiments of this application provide a communication device, which can be an access network device on the network side, a module (e.g., processor, circuit, chip or chip system) in the access network device, or a logical node, logical module or software that can realize all or part of the functions of the access network device.

[0038] In one possible implementation, the communication device has the function of implementing the first aspect described above. For example, the communication device may include modules, units, or means that correspond one-to-one with the methods / operations / steps / actions described in the first aspect. The modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0039] In one possible implementation, the communication device includes a processing unit and a communication unit. The processing unit is configured to send delay information via the communication unit. The delay information is related to the air interface delay corresponding to at least one terminal device obtained by the access network side. The air interface delay is the transmission delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The delay information is used to determine a routing strategy corresponding to the at least one terminal device. The routing strategy is used for bearer network transmission between the core network device and the access network device.

[0040] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0041] In another possible implementation, the communication unit is also used to receive delay response information, which is a response to the delay information.

[0042] For the technical effects of the sixth aspect or possible implementation, please refer to the introduction of the technical effects of the first aspect or corresponding implementation.

[0043] In a seventh aspect, embodiments of this application provide a communication device, which can be a core network device on the network side, a module (e.g., a processor, circuit, chip, or chip system) within the core network device, or a logical node, logical module, or software capable of implementing all or part of the functions of the core network device. For example, the core network device can be a User Plane Function (UPF) network element.

[0044] In one possible implementation, the communication device has the function of implementing the second aspect described above. For example, the communication device may include modules, units, or means that correspond one-to-one with the methods / operations / steps / actions described in the second aspect. The modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0045] In one possible implementation, the communication device includes a processing unit and a communication unit. The processing unit is configured to receive, via the communication unit, a routing policy corresponding to at least one terminal device. The routing policy is determined based on latency information, which is related to the air interface latency of at least one terminal device obtained by the access network side. The air interface latency is the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The routing policy is used for bearer network transmission between the core network device and the access network device.

[0046] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0047] In another possible implementation, the communication unit is further configured to send a first request message, the first request message including the delay information, the first request message being used to request the routing policy.

[0048] In another possible implementation, the communication unit is also used to receive the delay information.

[0049] In another possible implementation, the communication unit is also used to send a delay response message, which is a response to the delay message.

[0050] In another possible implementation, the communication unit is also used to send routing policy response information, which is a response to the routing policy.

[0051] For the technical effects of the seventh aspect or possible implementation, please refer to the introduction of the technical effects of the second aspect or corresponding implementation.

[0052] Eighthly, embodiments of this application provide a communication device, which can be a core network device on the network side, a module (e.g., a processor, circuit, chip, or chip system) within the core network device, or a logical node, logical module, or software capable of implementing all or part of the functions of the core network device. For example, the core network device can be a User Plane Function (UPF) network element.

[0053] In one possible implementation, the communication device has the function of implementing the third aspect described above. For example, the communication device may include modules, units, or means that correspond one-to-one with the methods / operations / steps / actions described in the third aspect. The modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0054] In one possible implementation, the communication device includes a processing unit and a communication unit. The processing unit is configured to receive delay information via the communication unit. The delay information is related to the air interface delay corresponding to at least one terminal device obtained by the access network side. The air interface delay is the transmission delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The delay information is used to determine a routing strategy corresponding to the at least one terminal device. The routing strategy is used for bearer network transmission between the core network device and the access network device.

[0055] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0056] In another possible implementation, the communication unit is also used to receive the routing policy.

[0057] In another possible implementation, the communication unit is further configured to send a first request message, the first request message including the delay information, the first request message being used to request the routing policy.

[0058] In another possible implementation, the communication unit is also used to send a delay response message, which is a response to the delay message.

[0059] In another possible implementation, the communication unit is also used to send routing policy response information, which is a response to the routing policy.

[0060] For the technical effects of the eighth aspect or possible implementation, please refer to the introduction of the technical effects of the third aspect or corresponding implementation.

[0061] Ninthly, embodiments of this application provide a communication device, which can be a core network device on the network side, a module (e.g., a processor, circuit, chip, or chip system) in the core network device, or a logical node, logical module, or software capable of implementing all or part of the functions of the core network device. For example, the core network device can be a Session Management Function (SMF) network element.

[0062] In one possible implementation, the communication device has the function of implementing the fourth aspect above. For example, the communication device may include modules, units or means that correspond one-to-one with the methods / operations / steps / actions described in the fourth aspect. The modules, units or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0063] In one possible implementation, the communication device includes: a processing unit and a communication unit. The processing unit is configured to acquire latency information related to the air interface latency of at least one terminal device obtained by the access network side, wherein the air interface latency is the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The processing unit is further configured to determine a routing strategy corresponding to the at least one terminal device based on the latency information, wherein the routing strategy is used for bearer network transmission between the core network device and the access network device. The communication unit is configured to send the routing strategy.

[0064] In one possible implementation, the communication unit is further configured to receive a first request message, the first request message including the delay information, the first request message being used to request the routing policy.

[0065] In another possible implementation, the processing unit is used to receive the delay information through the communication unit.

[0066] In another possible implementation, the communication unit is also used to receive routing policy response information, which is a response to the routing policy.

[0067] For the technical effects of the ninth aspect or possible implementation, please refer to the introduction of the technical effects of the fourth aspect or corresponding implementation.

[0068] In a tenth aspect, embodiments of this application provide a communication device, which may be a core network device on the network side, a module (e.g., a processor, circuit, chip, or chip system) within the core network device, or a logical node, logical module, or software capable of implementing all or part of the functions of the core network device. For example, the core network device may be an Access and Mobility Management Function (AMF) network element.

[0069] In one possible implementation, the communication device has the function of implementing the fifth aspect above. For example, the communication device may include modules, units or means that correspond one-to-one with the methods / operations / steps / actions described in the fifth aspect. The modules, units or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0070] In one possible implementation, the communication device includes: a processing unit and a communication unit. The processing unit is configured to receive delay information via the communication unit, the delay information being related to the air interface delay corresponding to at least one terminal device obtained by the access network side, the air interface delay being the transmission delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device; and to send the delay information, the delay information being used to determine a routing strategy corresponding to the at least one terminal device, the routing strategy being used for bearer network transmission between the core network device and the access network device.

[0071] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0072] For the technical effects of the tenth aspect or possible implementation, please refer to the description of the technical effects of the fifth aspect or corresponding implementation.

[0073] Eleventhly, embodiments of this application provide a communication device including one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of the necessary computer programs or instructions for implementing the functions described in the first aspect above. The one or more processors can execute the computer programs or instructions, causing the communication device to implement the methods in any possible design or implementation of the first aspect above. Optionally, the communication device further includes an interface circuit for implementing communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0074] In one possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0075] In one possible design, the communication device may also include the memory.

[0076] In a twelfth aspect, embodiments of this application provide a communication device including one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of the necessary computer programs or instructions for implementing the functions involved in the second or third aspect described above. The one or more processors can execute the computer programs or instructions, causing the communication device to implement the methods in any possible design or implementation of the first aspect described above. Optionally, the communication device further includes an interface circuit for implementing communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0077] In one possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0078] In one possible design, the communication device may also include the memory.

[0079] In a thirteenth aspect, embodiments of this application provide a communication device including one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions described in the fourth aspect above. The one or more processors can execute the computer program or instructions, causing the communication device to implement the methods in any possible design or implementation of the first aspect above. Optionally, the communication device further includes an interface circuit for implementing communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0080] In one possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0081] In one possible design, the communication device may also include the memory.

[0082] In a fourteenth aspect, embodiments of this application provide a communication device including one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions described in the fifth aspect above. The one or more processors can execute the computer program or instructions, causing the communication device to implement the methods in any possible design or implementation of the first aspect above. Optionally, the communication device further includes an interface circuit for implementing communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0083] In one possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0084] In one possible design, the communication device may also include the memory.

[0085] In a fifteenth aspect, embodiments of this application provide a communication system comprising: the apparatus of the eleventh aspect, the apparatus of the twelfth aspect, and the apparatus of the thirteenth aspect; or, the communication system comprising: the apparatus of the eleventh aspect, the apparatus of the twelfth aspect, the apparatus of the thirteenth aspect, and the apparatus of the fourteenth aspect.

[0086] In a sixteenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when read and executed by a computer, implement the method in any of the possible implementations of the first to fifth aspects described above.

[0087] In a seventeenth aspect, embodiments of this application provide a computer program product that, when read and executed by a computer, implements the method in any of the possible implementations of the first to fifth aspects described above.

[0088] Eighteenthly, embodiments of this application provide a chip device including at least one processor for executing computer programs or instructions to implement any of the above aspects or possible implementations of any of the above aspects.

[0089] In one possible implementation, the input of the chip device corresponds to the receiving operation in any of the above-mentioned aspects or possible implementations, and the output of the chip device corresponds to the transmitting operation in any of the above-mentioned aspects or possible implementations.

[0090] Optionally, the processor is coupled to the memory via an interface.

[0091] Optionally, the chip device may also include a memory storing computer program instructions. Attached Figure Description

[0092] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0093] Figure 2 This is a schematic diagram of the architecture of another communication system provided in the embodiments of this application;

[0094] Figure 3 This is a schematic diagram of an open RAN architecture provided in an embodiment of this application;

[0095] Figure 4 This is a schematic diagram of the arrival of an XR video frame;

[0096] Figure 5 This is a schematic diagram of XR video transmission;

[0097] Figure 6 This is a schematic diagram of an interface between an SMF network element and a UPF network element.

[0098] Figure 7 This is a schematic diagram of a routing strategy between a UPF network element and an access network device (gNB);

[0099] Figure 8 This is a schematic diagram illustrating the relationship between channel conditions and packet delay budget of user data packets;

[0100] Figure 9 This is a diagram illustrating how data packet transmission delays exceeding the PDB can cause user lag.

[0101] Figure 10 This is a schematic diagram of a communication method based on an access network device, a UPF network element, and an SMF network element, provided in an embodiment of this application.

[0102] Figure 11 This is a schematic diagram of a communication method based on an access network device, a UPF network element, an SMF network element, and an AMF network element, provided in an embodiment of this application.

[0103] Figure 12 This is a schematic diagram of another communication method based on an access network device, a UPF network element, and an SMF network element provided in the embodiments of this application;

[0104] Figure 13 This is a schematic diagram of another communication method based on access network equipment, UPF network element, SMF network element and AMF network element provided in the embodiments of this application;

[0105] Figure 14This is a schematic diagram of a communication device provided in an embodiment of this application;

[0106] Figure 15 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application;

[0107] Figure 16 This is a schematic diagram of a chip device provided in an embodiment of this application;

[0108] Figure 17 This is a schematic diagram of a chip device provided in an embodiment of this application. Detailed Implementation

[0109] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0110] References to "one embodiment" or "some embodiments" as described in this application mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0111] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, "at least one" refers to one or more, and "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Here, a, b, and c can be single or multiple. And, unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects.

[0112] It is understood that in this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0113] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index; indirectly instructing the information to be instructed by instructing other information, where there is a relationship between the other information and the information to be instructed; or instructing only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent.

[0114] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0115] It is understood that "sending information" in this application can be interpreted as one device sending information to another device, or as one logical module within a device sending information to another logical module. For example, "access network device sending information" can be interpreted as the access network device sending information to another device (such as a user plane function network element), or as logical module 1 in the access network device sending information to logical module 2 in the access network device.

[0116] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "access network device receiving information" can be understood as the access network device receiving information from another device (such as a user plane function network element), or it can be understood as logical module 1 in the access network device receiving information from logical module 2 in the access network device.

[0117] In this application, phrases such as "sending information to... (e.g., a terminal)" or related illustrations in the accompanying drawings can be understood as indicating that the destination of the information is a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a terminal)," "receiving information from... (e.g., a terminal)," or "receiving information sent by (e.g., a terminal)," or related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0118] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. Figure 1 As shown, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (e.g., ...). Figure 1 110a and 110b (collectively referred to as 110) and at least one terminal device (such as Figure 1 RAN 100, denoted as RAN 120a-120j, is collectively referred to as RAN 120. RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment. Figure 1 (Not shown in the image). Terminal device 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions. The aforementioned RAN node can be any type of RAN node described below, the aforementioned core network equipment can be any type of core network equipment described below, and the aforementioned terminal device can be any type of terminal device described below. It is understood that... Figure 1 This application only illustrates one possible communication system architecture to which this embodiment can be applied. In other possible scenarios, the communication system architecture may also include other devices. It should be noted that the methods described in this application embodiment can be applied to... Figure 1 The communication system shown.

[0119] Please see Figure 2 , Figure 2 This is a schematic diagram of the architecture of another communication system provided in the embodiments of this application, to Figure 2The application scenario used in this application is illustrated using the communication system architecture shown. The communication system includes core network equipment and RAN nodes. The RAN node can also be called an access network device. Optionally, the communication system also includes terminal equipment. Optionally, the communication system also includes a data network (DN). For example, the data network can be a fixed network. The data network is mainly used to provide services such as operator services, internet access, or third-party services, including servers, where video source encoding and rendering are implemented. The core network equipment can be any type of core network equipment described below, the RAN node can be any type of RAN node described below, and the terminal equipment can be any type of terminal equipment described below. It is understood that... Figure 2 This application only illustrates one possible communication system architecture to which this embodiment can be applied. In other possible scenarios, the communication system architecture may also include other devices. It should be noted that the methods described in this application embodiment can be applied to... Figure 2 The communication system shown.

[0120] (1) An RAN node is part of a communication system and is a device deployed in a radio access network to provide wireless communication functions for terminal equipment. An RAN node may also be called a radio access network (RAN) entity, access node, network node, access network equipment, or communication device, etc.

[0121] RAN nodes can be RAN nodes in cellular systems related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN nodes can also be RAN nodes in open RAN (O-RAN or ORAN), cloud radioaccess network (CRAN), or wireless fidelity (WiFi) systems. RAN nodes can also be RAN nodes in communication systems that integrate two or more of the above systems.

[0122] In one possible implementation, the multiple RAN nodes 110 in the communication system 10 can be nodes of the same type or nodes of different types. In some scenarios, the roles of the RAN nodes 110 and the terminal devices 120 are relative, for example, Figure 1Network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminal devices 120j that access RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal device. RAN node 110 and terminal device 120 are sometimes referred to as communication devices, for example... Figure 1 Network elements 110a and 110b can be understood as communication devices with base station functions, while network elements 120a-120j can be understood as communication devices with terminal equipment functions.

[0123] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system, etc. Figure 1 110a), micro base stations or indoor stations (such as Figure 1 The RAN node can be a relay node, pico base station, small cell, relay station, balloon station, or donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node can also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0124] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each performing some of the functions of the base station. Please refer to [link / reference]. Figure 3For example, a RAN node can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0125] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0126] It should be noted that the RAN node can be the device or apparatus shown above, or a component (e.g., a chip), module, or unit in the device or apparatus shown above, and this application does not limit the specific.

[0127] It should be noted that, unless otherwise specified, the RAN node will be referred to as an access network device in this application.

[0128] (2) The terminal equipment can be a device or module that is connected to the above-mentioned communication system and has corresponding communication functions. The terminal equipment can also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal equipment can communicate with the core network through the radio access network (RAN), exchange voice or data with the RAN, or interact with the RAN for voice and data. Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, computers with wireless transceiver capabilities, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), vehicles and in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), robotic arms, virtual reality (VR) devices, augmented reality (AR) devices, extended reality (XR) headsets, video players, holographic projectors, wireless terminals in industrial control, smart wearable devices, tactile terminal devices, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), smart robots, workshop equipment, wireless terminals in autonomous driving and driverless vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart offices, and smart cities. Wireless terminals in a city, or wireless terminals in a smart home, flying equipment (e.g., intelligent robots, hot air balloons, drones, helicopters, airplanes), transportation vehicles with wireless communication capabilities, communication modules, etc. Terminal devices can also be other devices with terminal functions; for example, a terminal device can also be a device that performs terminal functions in D2D communication.Terminal equipment can also include vehicle-to-everything (V2X) terminal equipment, machine-to-machine / machine-type communications (M2M / MTC) terminal equipment, internet of things (IoT) terminal equipment, light UE, reduced capability UE (REDCAP UE), subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user device, drone equipment, etc. For example, it can include mobile phones (or "cellular" phones), computers with mobile terminal devices, portable, pocket-sized, handheld, and computer-embedded mobile devices, etc. Examples include personal communication service (PCS) telephones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). It also includes limited devices, such as those with low power consumption, limited storage capacity, or limited computing power. Examples include information sensing devices such as barcode scanners, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners. In this application, terminal devices with wireless transceiver capabilities and chips that can be installed in the aforementioned terminal devices are collectively referred to as terminal devices. The terminal device may also be configured with program instructions for performing corresponding communication functions.

[0129] It should be noted that the embodiments of this application do not limit the device form of the terminal device. The terminal device is usually provided with a communication module, circuit or chip that performs the corresponding communication function. The terminal device can be a device or apparatus with a chip, or a device or apparatus with integrated circuit, or a chip, module or control unit in the device or apparatus shown above. This application does not limit the specific device.

[0130] (3) Core network equipment is mainly responsible for access control, registration management, connection, session management, service management, and mobility management of terminal equipment accessing the network. For example, core network equipment includes network exposure function (NEF) network elements, policy control function (PCF) network elements, application function (AF) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, and user plane function (UPF) network elements.

[0131] NEF network element: mainly used to expose the services and capabilities of 3GPP network functions to AF network element, and at the same time, it can also enable AF network element to provide information to 3GPP network functions.

[0132] PCF network element: mainly used for policy management of charging policies and quality of service (QoS) policies.

[0133] AF network element: mainly used to transmit the application side's requirements to the network side.

[0134] AMF network elements are primarily used for mobility management, access authentication / authorization, and other functions. They are also responsible for transmitting user policies between terminal devices and PCF network elements.

[0135] SMF network elements are mainly used to complete session management functions such as Internet Protocol (IP) address allocation, UPF network element selection, and billing and QoS policy control for terminal devices.

[0136] UPF network elements: As the interface with the data network, they are mainly used to perform functions such as user plane data forwarding, session- or flow-level billing statistics, and bandwidth limiting.

[0137] It should be noted that network element can also be replaced by entity, network entity, device, communication device, communication module, node, communication node, etc. In this application, network element is used as an example for description.

[0138] It should be noted that the core network equipment can be the equipment or apparatus shown above, or it can be a component (e.g., a chip), module, or unit in the equipment or apparatus shown above. This application does not limit the specific details.

[0139] To better understand the solutions provided in the embodiments of this application, some terms, concepts or processes involved in the embodiments of this application will be introduced below.

[0140] I. Extended Reality

[0141] In recent years, with the continuous development of fifth-generation (5G) communication systems, data transmission latency has been continuously reduced and transmission capacity has been increasing. 5G communication systems have gradually penetrated into some multimedia services with strong real-time requirements and large data capacity requirements, such as video transmission, cloud gaming (CG), and extended reality (XR). XR includes virtual reality (VR) and augmented reality (AR).

[0142] With the rapid increase in communication transmission speeds, real-time video transmission has gradually become one of the core services in current networks. The continuous advancement and improvement of extended reality technology has also led to the vigorous development of related industries. Today, VR technology, as a type of XR, has entered various fields closely related to people's production and lives, including education, entertainment, military, healthcare, environmental protection, transportation, and public health. Compared to traditional video services, VR offers advantages such as multiple perspectives and strong interactivity, providing users with a completely new visual experience.

[0143] Beyond smartphones, there's a growing demand for enhanced XR experiences through user devices such as head-mounted displays (HMDs) or smart glasses (like VR and AR glasses). Unlike smartphones, HMDs and smart glasses require more careful consideration of power consumption. Smart glasses, in particular, are extremely small, similar to prescription glasses, and are expected to be worn for extended periods, making power consumption control significantly more critical than with smartphones. In cloud gaming, the terminal device can be a smartphone or tablet. For prolonged cloud gaming experiences, device power consumption and battery life are also crucial considerations. Therefore, as XR devices become increasingly lightweight, power consumption, while maintaining a good user experience, has become a key research focus.

[0144] For XR and video transmission services, the service model typically involves periodic arrivals based on frame rate. Please refer to [link / reference]. Figure 4 , Figure 4 This is a diagram illustrating the arrival of XR video frames. For a video with a frame rate of 60 frames per second (FPS), ideally, one frame arrives every 16.67 milliseconds. Because XR devices have higher display resolutions, their service rates can reach 30–45 megabits per second (Mbps) (corresponding to 4K resolution) and 80–100 Mbps (corresponding to 8K resolution).

[0145] However, XR services have relatively strict end-to-end latency requirements; please refer to [link / reference needed]. Figure 5 , Figure 5 This is a schematic diagram of XR video transmission. Taking downlink transmission as an example, the data packets for XR services need to be transmitted from the server to the terminal device within a certain time. Considering that the end-to-end latency of XR services (from the server sending the data to the terminal device receiving it) is 70ms, the packet delay budget (PDB) from the access network device sending the data packet to the terminal device receiving the data packet is generally 10ms.

[0146] II. Video Encoding Methods

[0147] There are various video encoding methods, primarily variable bit rate (VBR) and constant bit rate (CBR), which determine how the bit rate is allocated during the encoding process of a video file. These two encoding methods are described below:

[0148] (1) VBR is an encoding method whose main feature is that the bitrate of the video file can dynamically change according to the complexity of the scene. In complex scenes (such as action scenes), VBR allocates more bitrate to maintain video quality; in simple scenes, it allocates less bitrate. It has the following advantages: 1) Higher efficiency: VBR can dynamically adjust the bitrate according to the complexity of the scene, thereby reducing the file size while maintaining video quality. 2) Better video quality: Since VBR can allocate bitrate as needed, it can maintain higher video quality in complex scenes. However, there are also some disadvantages: 1) Network transmission problems: Due to the fluctuation of bitrate, VBR may not be suitable for applications that require a stable data stream. 2) More complex encoding and decoding: VBR requires more complex algorithms to determine the bitrate allocation for different scenes.

[0149] (2) CBR is another encoding method in which the bitrate of the video file remains basically constant throughout the file. This means that the data stream rate is relatively fixed regardless of the complexity of the scene. CBR is suitable for network transmission, especially for applications that require a stable data stream, such as video conferencing or real-time streaming media. It has the following advantages: 1) Stability: Since the bitrate is relatively constant, CBR is a good choice for applications that require stable transmission. 2) Ease of control: Since the bitrate is known, the allocation and management of network bandwidth becomes easier. However, there are also some disadvantages: 1) Lower efficiency: When the complexity of the scene changes, CBR may not effectively utilize the bitrate, leading to fluctuations in video quality. That is, if the video bitrate remains fixed when facing scenes of different complexities, the high-complexity scenes will have lower image quality.

[0150] III. Determining the Routing Strategy

[0151] When a terminal device accesses the network, the access network device sends the terminal device's control plane messages to the AMF network element. The AMF network element selects a suitable SMF network element to handle session management based on the terminal device's location information and session requirements. The SMF network element then selects the most suitable UPF network element to handle user plane data based on session information and network configuration. This selection process considers factors such as the UPF network element's location, load, and connection status with the base station to ensure efficient and stable data transmission.

[0152] PCF network elements formulate forwarding rules and QoS policies (also known as routing policies) for terminal device data based on the terminal device's subscription information and network policies. Routing policies include data flow classification and priority settings. SMF network elements pass these routing policies to the most suitable UPF network element. (See also: [link to relevant documentation]). Figure 6 , Figure 6 This is a schematic diagram of the interface between an SMF network element and a UPF network element. The SMF and UPF network elements can exchange relevant information, such as routing policies, through the N4 interface. The UPF network element executes the data routing path according to the routing policy, ensuring that data transmission meets specific quality of service requirements.

[0153] In multi-use scenarios, different users have significantly different channel conditions, resulting in varying channel transmission capabilities and different packet delay budget (PDB) requirements for air interface data transmission. For example, please refer to... Figure 7 , Figure 7This is a schematic diagram of a routing strategy between a UPF network element and an access network device (gNB). If a data packet sent to UE#1 arrives late, it indicates that the channel state corresponding to UE#1 is poor, and the air interface transmission delay is relatively large. Conversely, if a data packet sent to UE#2 arrives early, it indicates that the channel state corresponding to UE#2 is good, and the air interface transmission delay is relatively low. Please refer to [link to relevant documentation]. Figure 8 , Figure 8 This is a schematic diagram illustrating the relationship between channel conditions and packet delay budget for user data packets. For example... Figure 8 In (a) of the example, UE#1, when channel conditions are poor and air interface transmission capability is low, the actual air interface transmission delay exceeds the PDB; for example... Figure 8 In (b) of the above, UE#2, when the channel conditions are good and the air interface transmission capability is high, the actual air interface transmission delay does not exceed PDB.

[0154] XR services have relatively strict end-to-end latency requirements. Taking downlink transmission as an example, XR service data packets need to be transmitted from the server to the terminal device within a certain time to ensure a good user experience. Please refer to [link to relevant documentation]. Figure 9 , Figure 9 This diagram illustrates how data packet transmission latency exceeding the PDB (Programmable Buffer Depth) can cause user buffering. When an access network device sends data packets to a terminal device, if the transmission latency from the access network device to the terminal device exceeds the PDB, it will impact the user experience at the receiving end, potentially causing buffering issues such as video playback. Therefore, improving user experience within latency requirements is a crucial technical problem that urgently needs to be solved by those in the field.

[0155] Please see Figure 10 , Figure 10 This is a schematic diagram of a communication method based on an access network device, a UPF network element, and an SMF network element, provided in an embodiment of this application. The following is in conjunction with... Figure 10 The communication methods and apparatus are further described below. It is understood that this application uses access network equipment and core network equipment, such as UPF network elements and SMF network elements, as the executors of the interaction illustration, but this application does not limit the executors of the interaction illustration. For example, the method executed by the access network equipment in this application can also be implemented by modules (e.g., processors, circuits, chips, or chip systems) within the access network equipment, or by logical nodes, logical modules, or software capable of implementing all or part of the functions of the access network equipment; similarly, the method executed by the core network equipment (e.g., UPF network elements or SMF network elements) in this application can also be implemented by modules (e.g., processors, circuits, chips, or chip systems) within the core network equipment, or by logical nodes, logical modules, or software capable of implementing all or part of the functions of the core network equipment.

[0156] In addition, such as Figure 10The communication method shown may include one or more steps S1001 to S1004. It should be understood that, for ease of description, steps S1001 to S1004 are described in this order, and it is not intended to limit the execution to this specific order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S1001 to S1004 are as follows:

[0157] Step S1001: The access network device sends delay information.

[0158] In this process, the access network device sends latency information to the UPF network element, and the corresponding UPF network element receives latency information from the access network device.

[0159] The latency information is related to the air interface latency corresponding to at least one terminal device obtained by the access network side. This latency information can also be referred to as the latency information corresponding to at least one terminal device. Access network side acquisition includes sensing by the access network side or measurement by the access network side. It should be noted that the air interface latency corresponding to at least one terminal device obtained by the access network side can be equal to the actual transmission latency of at least one data packet corresponding to at least one terminal device between the terminal device and the access network device; however, the air interface latency corresponding to at least one terminal device obtained by the access network side may not be equal to the actual transmission latency of at least one data packet corresponding to at least one terminal device between the terminal device and the access network device.

[0160] In the uplink scenario, the access network side obtains the air interface delay corresponding to at least one terminal device as follows: The access network device can determine the air interface delay of the data packet transmission based on the time of scheduling at least one data packet corresponding to the at least one terminal device according to downlink control information (DCI) and the time of receiving the data packet. For example, the air interface delay is the time of receiving the data packet minus the time of scheduling the data packet. In the downlink scenario, the access network side can determine the air interface delay through the scheduling frequency of downlink control signaling corresponding to at least one terminal device, where downlink control signaling is used to schedule downlink data. For example, for different terminal devices, the access network side can determine that the corresponding air interface delay is smaller by sensing which terminal devices have a faster downlink control signaling scheduling frequency. For example, there are three terminal devices, namely UE#1, UE#2 and UE#3. The downlink control signaling scheduling frequency corresponding to UE#1 is greater than that corresponding to UE#2, and the downlink control signaling scheduling frequency corresponding to UE#2 is greater than that corresponding to UE#3. Accordingly, the air interface latency obtained by the access network side for UE#1 is less than that for UE#2, and the air interface latency for UE#2 is less than that for UE#3.

[0161] Specifically, the air interface delay is the transmission delay of at least one data packet corresponding to at least one terminal device between the at least one terminal device and the access network device. In the uplink scenario, the air interface delay is the transmission delay from the at least one terminal device to the access network device, as obtained by the access network side. In the downlink scenario, the air interface delay is the transmission delay from the access network device to the at least one terminal device, as obtained by the access network side. It should be noted that the air interface delay can also be referred to as the air interface segment transmission delay.

[0162] In one possible implementation, the latency information includes at least one of the following: expected latency, air interface latency, or routing priority information of at least one terminal device.

[0163] The expected latency is the expected transmission latency of at least one data packet between the access network device and the core network device. In the uplink scenario, the expected latency is the expected transmission latency of at least one data packet from the access network device to the core network device; in the downlink scenario, the expected latency is the expected transmission latency of at least one data packet from the core network device to the access network device. The expected latency can be determined based on the air interface latency, specifically, it can be determined based on the air interface latency and the packet delay budget (PDB). The PDB is the expected latency budget for data packet transmission between the terminal device and the core network device. The PDB includes the core network packet delay budget (CN PDB) and the access network packet delay budget (ANPDB). Specifically, the CN PDB is the expected latency budget for data packet transmission from the core network device to the access network device, or vice versa; the AN PDB is the expected latency budget for data packet transmission from the access network device to the terminal device, or vice versa. It should be noted that the expected latency can also be called the expected N3 segment latency. In one example, the three terminal devices are UE#1, UE#2, and UE#3. The air interface latency obtained by the access network side is D1 = 3ms for UE#1, D2 = 5ms for UE#2, and D3 = 16ms for UE#3. The packet latency budget is PDB = 20ms. The expected latency R1 for UE#1 is PDB - D1 = 20 - 3 = 17ms, the expected latency R2 for UE#2 is PDB - D2 = 20 - 5 = 15ms, and the expected latency R3 for UE#3 is PDB - D3 = 20 - 16 = 4ms.

[0164] The routing priority information of at least one terminal device is used to indicate the routing priority of at least one terminal device. This routing priority information is used to determine the routing strategy between the core network device and the access network device. For example, a higher routing priority allows the core network device to choose a better routing strategy after receiving the routing priority. The routing priority information of at least one terminal device can also be referred to as the priority information for the transmission of at least one data packet corresponding to at least one terminal device in the bearer network, or the air interface transmission priority information of at least one terminal device. The routing priority information of at least one terminal device is determined based on air interface latency. The higher the air interface latency of the terminal device obtained by the access network side, the lower its corresponding air interface transmission priority and the higher its routing priority. In one example, the three terminal devices are UE#1, UE#2, and UE#3. The air interface latency obtained by the access network side is D1 = 3ms for UE#1, D2 = 5ms for UE#2, and D3 = 16ms for UE#3. Since D3 > D2 > D1, the air interface transmission priority of UE#3 is lower than that of UE#2, the air interface transmission priority of UE#2 is lower than that of UE#1, the routing priority of UE#3 is higher than that of UE#2, and the routing priority of UE#2 is higher than that of UE#1.

[0165] Optionally, the access network device sends delay information, which can be carried in a newly added request field, such as a delay information request; the delay information can also be carried in the GPRS-tunneling protocol user plane (GTP-U); the delay information can also be carried in a newly added field of the Protocol Data Unit session establishment request (PDU session establishment request).

[0166] In another possible implementation, the UPF network element sends a delayed response message.

[0167] In this process, the UPF network element sends delay response information to the access network device, and the access network device receives the delay response information from the UPF network element.

[0168] The delay response information is a response to the delay information. This delay response information includes an ACK or a NACK. An ACK indicates that the UPF network element has received the delay information sent by the access network device. A NACK indicates that the UPF network element has not received the delay information sent by the access network device. Optionally, if the delay response information sent by the UPF network element to the access network device is a NACK, the access network device may choose to retransmit the delay information.

[0169] Among them, when a UPF network element sends delay response information, if the delay information is carried in a newly added request field, such as a delay information request, the delay response information can also be carried in a newly added request field, such as a delay information response. If the delay information can be carried in a newly added field of a Protocol Data Unit (PDU) session establishment request, the delay response information can also be carried in a PDU session establishment response.

[0170] In the above method, the access network equipment and core network equipment (such as UPF network element) can be notified whether the delay information has been received, thereby ensuring the reliability of the delay information transmission.

[0171] Step S1002: The UPF network element sends delay information.

[0172] In this process, the UPF network element sends latency information to the SMF network element, and correspondingly, the SMF network element receives latency information from the UPF network element. This can be implemented in two ways:

[0173] In one possible implementation, the method further includes: the UPF network element sending a first request message.

[0174] Specifically, the UPF network element sends a first request message to the SMF network element. This first request message includes latency information and is used to request a routing policy corresponding to at least one terminal device. In other words, when the UPF network element sends a first request message to the SMF network element to request a routing policy, the first request message carries latency information.

[0175] Optionally, the first request message can also be used to request whether to update the routing policy. After receiving the first request message, if the SMF network element needs to update the routing policy, the SMF network element sends at least one routing policy corresponding to the terminal device to the UPF network element; if the routing policy does not need to be updated, the SMF network element can send a response message to the UPF network element, which indicates that the routing policy does not need to be updated.

[0176] Optionally, the first request message may be carried in a newly added request field, for example, a route update request.

[0177] In another possible implementation, the method further includes: the UPF network element sending delay information to the SMF network element. That is, the UPF network element can directly send delay information to the SMF network element, and this delay information is not carried in the first request message.

[0178] In summary, whether the UPF network element sends a first request message to the SMF network element requesting a routing policy and the first request message carries latency information, or the UPF network element can directly send latency information to the SMF network element, these are all possible ways for the SMF network element to obtain latency information.

[0179] Step S1003: The SMF network element determines the routing policy corresponding to at least one terminal device based on the latency information.

[0180] This routing policy is used for bearer network transmission between core network equipment and access network equipment. The routing policy corresponding to at least one terminal device can also be referred to as the N3 segment routing policy corresponding to at least one terminal device. The routing policy includes at least one of the following: protocol data unit (PDU) session identifier, data network name, or QoS rule.

[0181] In one possible implementation, the latency information includes expected latency. A higher expected latency corresponds to a lower routing priority for the corresponding terminal device, and a worse routing strategy is selected for that terminal device. Conversely, a lower expected latency corresponds to a higher routing priority for the corresponding terminal device, and a better routing strategy is selected for that terminal device. The quality of the routing strategy can be measured by the time it takes for data packets to travel through the bearer network. In one example, the three terminal devices are UE#1, UE#2, and UE#3. The access network side obtains the following air interface latency information: UE#1 = D1 = 3ms, UE#2 = D2 = 5ms, and UE#3 = D3 = 16ms. The packet latency budget is PDB = 20ms. The expected latency for UE#1 is R1 = PDB - D1 = 20 - 3 = 17ms, for UE#2 it is R2 = PDB - D2 = 20 - 5 = 15ms, and for UE#3 it is R3 = PDB - D3 = 20 - 16 = 4ms. Since R1 > R2 > R3, UE#3 has a higher routing priority than UE#2, and UE#2 has a higher routing priority than UE#1. Therefore, for users with higher routing priorities, a better routing strategy is chosen. Thus, UE#3's routing strategy is superior to UE#2's, and UE#2's routing strategy is superior to UE#1's. This approach avoids exceeding end-to-end latency constraints, thereby improving the user experience.

[0182] In another possible implementation, latency information includes air interface latency. A higher air interface latency corresponds to a higher routing priority for the corresponding terminal device, resulting in a better routing strategy for that terminal device. Conversely, a lower air interface latency corresponds to a lower routing priority for the corresponding terminal device, resulting in a worse routing strategy for that terminal device. In one example, the three terminal devices are UE#1, UE#2, and UE#3. The access network side obtains the following air interface latency information: UE#1 = D1 = 3ms, UE#2 = D2 = 5ms, and UE#3 = D3 = 16ms. Since D3 > D2 > D1, UE#3 has a higher routing priority than UE#2, and UE#2 has a higher routing priority than UE#1. Therefore, for users with higher routing priorities, a better routing strategy is selected. Thus, UE#3's routing strategy is superior to UE#2's, and UE#2's routing strategy is superior to UE#1's. By using the above methods, we can avoid exceeding end-to-end latency constraints, thereby improving the user experience.

[0183] In another possible implementation, the latency information includes routing priority information for at least one terminal device. A higher routing priority for a terminal device results in a better routing strategy; conversely, a lower routing priority results in a worse routing strategy. In one example, the three terminal devices are UE#1, UE#2, and UE#3. The access network side obtains the following air interface latency information: UE#1 = 3ms, UE#2 = 5ms, and UE#3 = 16ms. Since D3 > D2 > D1, UE#3 has a higher routing priority than UE#2, and UE#2 has a higher routing priority than UE#1. Therefore, for users with higher routing priorities, a better routing strategy is chosen. Thus, UE#3's routing strategy is superior to UE#2's, and UE#2's is superior to UE#1's. This approach avoids exceeding end-to-end latency constraints, thereby improving the user experience.

[0184] Step S1004: The SMF network element sends the routing policy corresponding to at least one terminal device.

[0185] In this process, the SMF network element sends routing policies corresponding to at least one terminal device to the UPF network element, and correspondingly, the UPF network element receives the routing policies corresponding to at least one terminal device from the SMF network element. Optionally, after receiving the routing policies corresponding to at least one terminal device from the SMF network element, the UPF network element executes the data routing path according to the routing policies corresponding to the at least one terminal device, ensuring that data transmission meets specific quality of service requirements. Through this method, a superior user experience can be guaranteed for multiple users in multi-user scenarios.

[0186] In one example, the three terminal devices are UE#1, UE#2, and UE#3. The air interface latency obtained by the access network side is D1 = 3ms for UE#1, D2 = 5ms for UE#2, and D3 = 16ms for UE#3. Since D3 > D2 > D1, the routing priority of UE#3 is higher than that of UE#2, and the routing priority of UE#2 is higher than that of UE#1. Therefore, for users with higher routing priorities, the routing strategy they choose is better. Thus, routing strategy 3 for UE#3 is better than routing strategy 2 for UE#2, and routing strategy 2 for UE#2 is better than routing strategy 1 for UE#1. The SMF network element sends routing strategy 3 for UE#3, routing strategy 2 for UE#2, and routing strategy 1 for UE#1 to the UPF network element. Accordingly, the UPF network element executes the routing path for data packet 3 according to routing strategy 3 for UE#3, the routing path for data packet 2 according to routing strategy 2 for UE#2, and the routing path for data packet 1 according to routing strategy 1 for UE#1.

[0187] Optionally, the SMF network element sends a routing policy corresponding to at least one terminal device. If the UPF network element sends a first request message to the SMF network element, the first request message includes latency information. The first request message is used to request the routing policy corresponding to at least one terminal device. The first request message is carried in a newly added request field, for example, a route update request. The routing policy corresponding to the at least one terminal device can be carried in the newly added request field, such as a route update response. The routing policy corresponding to the at least one terminal device can also be carried in the existing field forwarding action rule (FAR) in an existing N4 session modification request.

[0188] In one possible implementation, the method further includes: the UPF network element sending routing policy response information.

[0189] Optionally, if the routing policy corresponding to at least one terminal device can also be carried in the existing field forwarding action rule (FAR) in the existing N4 session modification request, the UPF network element sends routing policy response information, which can be carried in the N4 session modification response.

[0190] In this process, the UPF network element sends a routing policy response message to the SMF network element. This response message is a confirmation of the routing policy. It includes either an ACK (positive acknowledgment) or a NACK (negative acknowledgment). An ACK indicates that the UPF network element has received the routing policy from the SMF network element, while a NACK indicates that the UPF network element has not received it. Optionally, if the UPF network element sends a NACK response, the SMF network element can choose to retransmit the routing policy. This method ensures timely notification to the SMF network element whether the UPF network element has received the routing policy, thereby guaranteeing the reliability of the routing policy transmission.

[0191] exist Figure 10 In the described method, latency information is sent by the access network device. This latency information is related to the air interface latency of at least one terminal device. This allows the core network device to consider the latency information when determining the routing strategy for at least one terminal device. For example, if the latency information is the air interface latency, in a multi-user scenario, for terminal devices with a relatively large air interface latency, a better routing strategy can be selected when determining the routing strategy. The better routing strategy can reduce the N3 segment routing latency (i.e., the transmission latency between the core network device and the access network device). For terminal devices with a relatively small air interface latency, a worse routing strategy can be selected when determining the routing strategy. This achieves a "mutual borrowing" between air interface latency and N3 segment routing latency, avoiding exceeding the end-to-end latency constraint, thereby improving the user experience within the latency requirements.

[0192] Please see Figure 11 , Figure 11 This is a schematic diagram of a communication method based on an access network device, a UPF network element, an SMF network element, and an AMF network element, provided in an embodiment of this application. The following is in conjunction with... Figure 11 The communication methods and apparatus are further described below. It is understood that this application uses access network equipment and core network equipment, such as UPF, SMF, and AMF network elements, as the executors of the interaction illustration, but this application does not limit the executors of the interaction illustration. For example, the method executed by the access network equipment in this application can also be implemented by modules (e.g., processors, circuits, chips, or chip systems) within the access network equipment, or by logical nodes, logical modules, or software capable of implementing all or part of the access network equipment's functions; similarly, the method executed by the core network equipment (e.g., UPF, SMF, and AMF network elements) in this application can also be implemented by modules (e.g., processors, circuits, chips, or chip systems) within the core network equipment, or by logical nodes, logical modules, or software capable of implementing all or part of the core network equipment's functions.

[0193] In addition, such as Figure 11 The communication method shown may include one or more steps S1101 to S1104. It should be understood that, for ease of description, steps S1101 to S1104 are described in this order, and it is not intended to limit the execution to this specific order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S1101 to S1104 are as follows:

[0194] Step S1101: The access network device sends delay information.

[0195] In this process, the access network device sends latency information to the AMF network element, and the AMF network element receives latency information from the access network device. The latency information is related to the air interface latency of at least one terminal device obtained by the access network side. For an explanation of the latency information, please refer to the relevant description in step S1001.

[0196] Optionally, the access network device sends delay information, which can be carried in a newly added request field, such as a delay information request; the delay information can also be carried in a delay update request added in an existing configuration update.

[0197] Step S1102: The AMF network element sends delay information.

[0198] In this process, the AMF network element sends delay information to the SMF network element, and correspondingly, the SMF network element receives delay information from the AMF network element. The SMF network element receiving delay information from the AMF network element is one possible implementation method for obtaining delay information.

[0199] Optionally, the AMF network element sends delay information, which can be carried in session update information, such as the Protocol Data Unit Session Update SM Context (Nsmf_PDUSession_UpdateSMContext); or the delay information can be carried in a newly added message carrying delay-related information, such as a delay update message.

[0200] Step S1103: The SMF network element determines the routing policy corresponding to at least one terminal device based on the latency information.

[0201] This routing strategy is used for bearer network transmission between core network devices and access network devices. For details, please refer to the relevant description in step S1002.

[0202] Step S1104: The SMF network element sends the routing policy corresponding to at least one terminal device.

[0203] In this process, the SMF network element sends a routing policy corresponding to at least one terminal device to the UPF network element, and correspondingly, the UPF network element receives a routing policy corresponding to at least one terminal device from the SMF network element. For details, please refer to the relevant description in step S1003.

[0204] Optionally, the SMF network element sends a routing policy corresponding to at least one terminal device. The routing policy corresponding to the at least one terminal device can be carried in a newly added request field, such as a route update response. Alternatively, the routing policy corresponding to the at least one terminal device can be carried in an existing field forwarding action rule (FAR) in an existing N4 session modification request.

[0205] In one possible implementation, the method further includes: the UPF network element sending routing policy response information.

[0206] Optionally, if the routing policy corresponding to at least one terminal device can also be carried in the existing field forwarding action rule (FAR) in the existing N4 session modification request, the UPF network element sends routing policy response information, which can be carried in the N4 session modification response.

[0207] In this process, the UPF network element sends a routing policy response message to the SMF network element. This response message is a confirmation of the routing policy. It includes either an ACK (positive acknowledgment) or a NACK (negative acknowledgment). An ACK indicates that the UPF network element has received the routing policy from the SMF network element, while a NACK indicates that the UPF network element has not received it. Optionally, if the UPF network element sends a NACK response, the SMF network element can choose to retransmit the routing policy. This method ensures timely notification to the SMF network element whether the UPF network element has received the routing policy, thereby guaranteeing the reliability of the routing policy transmission.

[0208] exist Figure 11In the described method, latency information is sent by the access network device. This latency information is related to the air interface latency of at least one terminal device. This allows the core network device to consider the latency information when determining the routing strategy for at least one terminal device. For example, if the latency information is the air interface latency, in a multi-user scenario, for terminal devices with a relatively large air interface latency, a better routing strategy can be selected when determining the routing strategy. The better routing strategy can reduce the N3 segment routing latency (i.e., the transmission latency between the core network device and the access network device). For terminal devices with a relatively small air interface latency, a worse routing strategy can be selected when determining the routing strategy. This achieves a "mutual borrowing" between air interface latency and N3 segment routing latency, avoiding exceeding the end-to-end latency constraint, thereby improving the user experience within the latency requirements.

[0209] Please see Figure 12 , Figure 12 This is a schematic diagram of another communication method based on access network equipment, UPF network element, and SMF network element provided in the embodiments of this application. The following is in conjunction with... Figure 12 The communication methods and apparatus are further described below. It is understood that this application uses access network equipment and core network equipment, such as UPF network elements and SMF network elements, as the executors of the interaction illustration, but this application does not limit the executors of the interaction illustration. For example, the method executed by the access network equipment in this application can also be implemented by modules (e.g., processors, circuits, chips, or chip systems) within the access network equipment, or by logical nodes, logical modules, or software capable of implementing all or part of the functions of the access network equipment; similarly, the method executed by the core network equipment (e.g., UPF network elements or SMF network elements) in this application can also be implemented by modules (e.g., processors, circuits, chips, or chip systems) within the core network equipment, or by logical nodes, logical modules, or software capable of implementing all or part of the functions of the core network equipment.

[0210] In addition, such as Figure 12 The communication method shown may include one or more steps from S1201 (e.g., S1201a, S1201b, or S1201c) to S1205 (e.g., S1205b). It should be understood that, for ease of description, the method is described here in the order of steps S1201 (e.g., S1201a, S1201b, or S1201c) to S1205 (e.g., S1205b), and is not intended to limit the execution to this specific order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S1201 (e.g., S1201a, S1201b, or S1201c) to S1205 (e.g., S1205b) are as follows:

[0211] Step S1201a: The access network device sends uplink and downlink delay-related information to the UPF network element and adds a new request, such as a delay information request.

[0212] Among them, uplink and downlink latency-related information can be carried in the new request. For example, the new request can be a delay information request.

[0213] It should be noted that the uplink and downlink latency-related information in this embodiment can also be referred to as latency information. The latency information is related to the air interface latency corresponding to at least one terminal device obtained by the access network side. Please refer to the relevant description in step S1001 for details.

[0214] Step S1201b: The access network device sends uplink and downlink delay-related information to the UPF network element, such as the GTP-U extension header.

[0215] The uplink and downlink latency information can be carried in the GTP-U extension header. Refer to the relevant description in step S1001 for details.

[0216] Step S1201c: The access network device sends uplink and downlink delay-related information to the UPF network element, such as a Protocol Data Unit (PDU) session establishment request.

[0217] The uplink and downlink latency information can be carried in a new field of the Protocol Data Unit (PDU) sessionestablishment request. See the relevant description in step S1001 for details.

[0218] It should be noted that only one of the above steps S1201a, S1201b and S1201c needs to be performed.

[0219] Step S1202a: The UPF network element sends a delay information response to the access network device, for example, a delay information response.

[0220] It should be noted that the delay information response is a response to uplink and downlink delay-related information, and can also be called delay response information. Please refer to the relevant description in step S1001 for details.

[0221] If step S1201a is executed, i.e., the uplink and downlink delay-related information is carried in the newly added request field, such as a delay information request, the delay information response can be carried in the newly added request field, such as a delay information response.

[0222] Step S1202c: The UPF network element sends a Protocol Data Unit Session Establishment Response (PDUsession Establishment Response) to the access network device.

[0223] If step S1201c above has been performed, meaning that the uplink and downlink latency information is carried in a newly added field of the Protocol Data Unit (PDU) session establishment request, the latency information response can also be carried in the PDU session establishment response. Refer to the relevant description in step S1001 for details.

[0224] It should be noted that only one of the above steps S1202a and S1202c needs to be performed.

[0225] Step S1203: The UPF network element sends a routing policy update request, such as a route update request, to the SMF network element.

[0226] The routing policy update request can be the first request message, as detailed in step S1002.

[0227] The route policy update request is carried out in the newly added request field, for example, the newly added request field is route update request.

[0228] It should be noted that step S1202a can be placed before or after step S1203, and the order of steps S1202a and S1203 is not limited. Step S1202c can be placed before or after step S1203, and the order of steps S1202c and S1203 is not limited.

[0229] Step S1204a: The SMF network element sends a routing policy update response, such as a route update response, to the UPF network element.

[0230] Specifically, the newly added routing policy update response carries routing policy information, meaning the routing policy update response includes the routing policy corresponding to at least one terminal device. Specifically, the routing policy corresponding to at least one terminal device can be carried in a newly added request field, such as a route update response, as described in step S1004.

[0231] Step S1204b: The SMF network element sends the existing field forwarding action rule (FAR) from the existing N4 session modification request to the UPF network element.

[0232] Specifically, the SMF network element sends a routing policy corresponding to at least one terminal device to the UPF network element. This routing policy can also be carried within an existing field forwarding action rule (FAR) in an existing N4 session modification request. See the relevant description in step S1004 for details.

[0233] It should be noted that either step S1204a or step S1204b can be performed.

[0234] Step S1205b: The UPF network element sends an N4 session modification response to the SMF network element.

[0235] If step S1204b is executed, meaning that the routing policy corresponding to at least one terminal device can also be carried in the existing field forwarding action rule (FAR) in the existing N4 session modification request, the UPF network element sends routing policy response information, which can be carried in the N4 session modification response.

[0236] exist Figure 12In the method described, latency information is sent by the access network device. This latency information is related to the air interface latency of at least one terminal device. This allows the core network device to consider the latency information when determining the routing strategy for at least one terminal device. For example, if the latency information is the air interface latency, in a multi-user scenario, for terminal devices with a relatively large air interface latency, a better routing strategy can be selected when determining the routing strategy. A better routing strategy can reduce the N3 segment routing latency (i.e., the transmission latency between the core network device and the access network device). For terminal devices with a relatively small air interface latency, a worse routing strategy can be selected when determining the routing strategy. This achieves a "mutual borrowing" between air interface latency and N3 segment routing latency, avoiding exceeding the end-to-end latency constraints, thereby improving the user experience within the latency requirements.

[0237] Please see Figure 13 , Figure 13 This is a schematic diagram of another communication method based on access network equipment, UPF network element, SMF network element and AMF network element provided in the embodiments of this application. The following is in conjunction with Figure 13 The communication methods and apparatus are further described below. It is understood that this application uses access network equipment and core network equipment, such as UPF, SMF, and AMF network elements, as the executors of the interaction illustration, but this application does not limit the executors of the interaction illustration. For example, the method executed by the access network equipment in this application can also be implemented by modules (e.g., processors, circuits, chips, or chip systems) within the access network equipment, or by logical nodes, logical modules, or software capable of implementing all or part of the access network equipment's functions; similarly, the method executed by the core network equipment (e.g., UPF, SMF, and AMF network elements) in this application can also be implemented by modules (e.g., processors, circuits, chips, or chip systems) within the core network equipment, or by logical nodes, logical modules, or software capable of implementing all or part of the core network equipment's functions.

[0238] In addition, such as Figure 13 The communication method shown may include one or more steps from S1301 (e.g., S1301a or S1301b) to S1304 (e.g., S1304b). It should be understood that, for ease of description, the method is described here in the order of steps S1301 (e.g., S1301a or S1301b) to S1304 (e.g., S1304b), but this is not intended to limit the execution to this specific order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S1301 (e.g., S1301a or S1301b) to S1304 (e.g., S1304b) are as follows:

[0239] Step S1301a: The access network device sends uplink and downlink delay-related information to the AMF network element and adds a new request, such as a delay information request.

[0240] Among them, uplink and downlink latency-related information can be carried in the new request. For example, the new request can be a delay information request.

[0241] It should be noted that the uplink and downlink latency-related information in this embodiment can also be referred to as latency information. The latency information is related to the air interface latency corresponding to at least one terminal device obtained by the access network side. Please refer to the relevant description in step S1001 for details.

[0242] Step S1301b: The access network device sends a configuration update to the AMF network element.

[0243] The uplink and downlink latency information is carried in the latency update request added to the existing configuration update.

[0244] It should be noted that either step S1301a or step S1301b can be performed.

[0245] Step S1302a: The AMF network element sends session update information to the SMF network element. The session update information includes uplink and downlink latency related information.

[0246] In this process, the AMF network element sends uplink and downlink delay-related information to the SMF network element. This uplink and downlink delay-related information can be carried in session update information, such as the Protocol Data Unit Session Update SM Context (Nsmf_PDUSession_UpdateSMContext). For details, please refer to the relevant description in step S1102.

[0247] Step S1302b: The AMF network element sends a new message carrying delay-related information, such as a delay update message, to the SMF network element.

[0248] Specifically, the AMF network element sends uplink and downlink delay-related information to the SMF network element. This uplink and downlink delay-related information can be carried in a newly added message carrying delay-related information, such as a delay update information message.

[0249] It should be noted that either step S1302a or step S1302b can be performed.

[0250] Step S1303a: The SMF network element sends a routing policy update response, such as a route update response, to the UPF network element.

[0251] Specifically, the newly added routing policy update response carries routing policy information, meaning the routing policy update response includes the routing policy corresponding to at least one terminal device. Specifically, the routing policy corresponding to at least one terminal device can be carried in a newly added request field, such as a route update response, as described in step S1104.

[0252] Step S1303b: The SMF network element sends the existing field forwarding action rule (FAR) from the existing N4 session modification request to the UPF network element.

[0253] Specifically, the SMF network element sends a routing policy corresponding to at least one terminal device to the UPF network element. This routing policy can also be carried within an existing field forwarding action rule (FAR) in an existing N4 session modification request. See the relevant description in step S1104 for details.

[0254] It should be noted that either step S1303a or step S1303b can be performed.

[0255] Step S1304b: The UPF network element sends an N4 session modification response to the SMF network element.

[0256] If step S1303b is executed, meaning that the routing policy corresponding to at least one terminal device can also be carried in the existing field forwarding action rule (FAR) of the existing N4 session modification request, the UPF network element sends routing policy response information, which can be carried in the N4 session modification response. Refer to the relevant description in step S1104 for details.

[0257] exist Figure 13In the method described, latency information is sent by the access network device. This latency information is related to the air interface latency of at least one terminal device. This allows the core network device to consider the latency information when determining the routing strategy for at least one terminal device. For example, if the latency information is the air interface latency, in a multi-user scenario, for terminal devices with a relatively large air interface latency, a better routing strategy can be selected when determining the routing strategy. A better routing strategy can reduce the N3 segment routing latency (i.e., the transmission latency between the core network device and the access network device). For terminal devices with a relatively small air interface latency, a worse routing strategy can be selected when determining the routing strategy. This achieves a "mutual borrowing" between air interface latency and N3 segment routing latency, avoiding exceeding the end-to-end latency constraints, thereby improving the user experience within the latency requirements.

[0258] The methods of the embodiments of this application have been described in detail above, and the apparatus of the embodiments of this application is provided below.

[0259] Please see Figure 14 , Figure 14 This is a schematic diagram of a communication device provided in an embodiment of this application. Figure 14 As shown, the communication device 1400 may include modules or units for implementing the methods described in the embodiments above. In one possible design, the communication device 1400 includes a processing unit 1402 and a communication unit 1403. Optionally, the communication device 1400 may further include a storage unit 1401 for storing device program code and / or data.

[0260] Optionally, the communication device 1400 may be an access network device on the network side in the above embodiments, a module (such as a processor, circuit, chip or chip system) in the access network device, or a logical node, logical module or software that can realize all or part of the functions of the access network device.

[0261] For example, in one embodiment, the processing unit 1402 is used to send delay information through the communication unit 1403. The delay information is related to the air interface delay of at least one terminal device obtained by the access network side. The air interface delay is the transmission delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The delay information is used to determine the routing strategy corresponding to the at least one terminal device. The routing strategy is used for bearer network transmission between the core network device and the access network device.

[0262] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0263] In another possible implementation, the communication unit 1403 is also used to receive delay response information, which is a response to the delay information.

[0264] Optionally, the communication device 1400 can be a core network device on the network side, a module (e.g., processor, circuit, chip, or chip system) in the core network device, or a logical node, logical module, or software that can implement all or part of the functions of the core network device, as described in the above embodiments. For example, the core network device can be a User Plane Function (UPF) network element.

[0265] For example, in one embodiment, the processing unit 1402 is used to receive a routing policy corresponding to at least one terminal device through the communication unit 1403. The routing policy is determined based on latency information, which is related to the air interface latency of at least one terminal device obtained by the access network side. The air interface latency is the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The routing policy is used for bearer network transmission between the core network device and the access network device.

[0266] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0267] In another possible implementation, the communication unit 1403 is further configured to send a first request message, the first request message including the delay information, the first request message being used to request the routing policy.

[0268] In another possible implementation, the communication unit 1403 is also used to receive the delay information.

[0269] In another possible implementation, the communication unit 1403 is also used to send a delay response message, which is a response to the delay message.

[0270] In another possible implementation, the communication unit 1403 is also used to send routing policy response information, which is a response to the routing policy.

[0271] Optionally, the communication device 1400 can be a core network device on the network side, a module (e.g., processor, circuit, chip, or chip system) in the core network device, or a logical node, logical module, or software that can implement all or part of the functions of the core network device, as described in the above embodiments. For example, the core network device can be a User Plane Function (UPF) network element.

[0272] For example, in one embodiment, the processing unit 1402 is used to receive delay information through the communication unit 1403. The delay information is related to the air interface delay of at least one terminal device obtained by the access network side. The air interface delay is the transmission delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The delay information is used to determine the routing strategy corresponding to the at least one terminal device. The routing strategy is used for bearer network transmission between the core network device and the access network device.

[0273] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0274] In another possible implementation, the communication unit 1403 is also used to receive the routing policy.

[0275] In another possible implementation, the communication unit 1403 is further configured to send a first request message, the first request message including the delay information, the first request message being used to request the routing policy.

[0276] In another possible implementation, the communication unit 1403 is also used to send a delay response message, which is a response to the delay message.

[0277] In another possible implementation, the communication unit 1403 is also used to send routing policy response information, which is a response to the routing policy.

[0278] Optionally, the communication device 1400 can be a core network device on the network side in the above embodiments, a module (e.g., processor, circuit, chip, or chip system) in the core network device, or a logical node, logical module, or software that can implement all or part of the functions of the core network device. For example, the core network device can be a Session Management Function (SMF) network element.

[0279] For example, in one embodiment, the processing unit 1402 is used to acquire latency information, which is related to the air interface latency of at least one terminal device obtained by the access network side. The air interface latency is the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The processing unit 1402 is also used to determine a routing strategy corresponding to the at least one terminal device based on the latency information. The routing strategy is used for bearer network transmission between the core network device and the access network device. The communication unit 1403 is used to send the routing strategy.

[0280] In one possible implementation, the communication unit 1403 is further configured to receive a first request message, the first request message including the delay information, the first request message being used to request the routing policy.

[0281] In another possible implementation, the processing unit 1402 is used to receive the delay information through the communication unit 1403.

[0282] In another possible implementation, the communication unit 1403 is also used to receive routing policy response information, which is a response to the routing policy.

[0283] Optionally, the communication device 1400 can be a core network device on the network side in the above embodiments, a module (e.g., processor, circuit, chip, or chip system) in the core network device, or a logical node, logical module, or software that can implement all or part of the functions of the core network device. For example, the core network device can be an Access and Mobility Management Function (AMF) network element.

[0284] For example, in one embodiment, the processing unit 1402 is configured to receive delay information through the communication unit 1403. The delay information is related to the air interface delay of at least one terminal device obtained by the access network side. The air interface delay is the transmission delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The processing unit 1402 is configured to send the delay information. The delay information is used to determine the routing strategy corresponding to the at least one terminal device. The routing strategy is used for bearer network transmission between the core network device and the access network device.

[0285] In one possible implementation, the delay information includes at least one of the following: expected delay, air interface delay, or routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

[0286] It is understood that the division of units in the above-described device is merely a logical functional division. One function can correspond to one functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated onto a single physical entity, or distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for specific applications, but such implementations should not be considered beyond the scope of this application.

[0287] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0288] In one example, storage unit 1401 may include random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory and / or registers, etc.

[0289] Please see Figure 15 , Figure 15 This is a schematic diagram of the structure of another communication device 1500 provided in the embodiments of this application. The communication device 1500 may include modules, units or means corresponding to the methods / operations / steps / actions performed by the access network device or core network device in the above method embodiments. The modules, units or means may be hardware circuits, software, or hardware circuits combined with software.

[0290] The communication device 1500 includes at least one processor 1501. Optionally, it also includes a communication interface 1503 and a memory 1502. The processor 1501, memory 1502, and communication interface 1503 are interconnected via a bus 1504. Optionally, the processor 1501 and memory 1502 can be integrated together.

[0291] The memory 1502 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), and is used for related computer programs and data. The communication interface 1503 is used for receiving and sending data.

[0292] Processor 1501 can be one or more central processing units (CPUs). When processor 1501 is a CPU, the CPU can be a single-core CPU or a multi-core CPU.

[0293] The processor 1501 in the communication device 1500 is used to read computer programs or instructions stored in the memory 1502 to implement the functions of the aforementioned processing unit, and the communication interface 1503 in the communication device 1500 is used to implement the functions of the aforementioned communication unit.

[0294] Please see Figure 16 , Figure 16This is a schematic diagram of a chip device provided in an embodiment of this application. The communication device involved in this application can be a chip device. A chip device can be composed of chips or may include chips and other discrete components. The communication device includes one or more processors for implementing or supporting the communication device in implementing the functions in the methods of this application. A processor can also be called a processing unit or processing module and can implement certain control functions. The processor can be a general-purpose processor or a dedicated processor, etc. For example, it includes: a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor, etc. The central processing unit can be used to control the communication device, execute software programs, and / or process data. Different processors can be independent devices or integrated into one or more processors, for example, integrated on one or more application-specific integrated circuits (ASICs). It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0295] Optionally, the communication device includes one or more memories for storing computer program instructions that can be executed on the processor. The memory and processor are coupled; in this application, coupling refers to indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules.

[0296] Optionally, the memory may also store data. The processor and memory may be configured separately or integrated together. The memory may be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it may be volatile memory, such as random-access memory (RAM). In the embodiments of this application, the processor may also be flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art.

[0297] Optionally, the communication device may include instructions (sometimes referred to as code or program) that can be executed on the processor.

[0298] Optionally, the communication device may also include a transceiver and an antenna. The transceiver may be referred to as a transceiver unit, transceiver module, transceiver, transceiver circuit, transceiver, input / output interface, etc., and is used to realize the transmission and reception functions of the communication device through the antenna.

[0299] Please see Figure 17 , Figure 17 This is a schematic diagram of another chip device provided in an embodiment of this application. The communication device of this application can be a chip device. A chip device can be composed of chips or can include chips and other discrete components. The communication device includes a processor, a transceiver, and an antenna. Optionally, the communication device may also include a memory. The transceiver can be referred to as a transceiver unit, transceiver module, transceiver, transceiver circuit, transceiver, input / output interface, etc., and is used to realize the transmission and reception functions of the communication device through the antenna.

[0300] Server processing chip:

[0301] The processor needs to collect data related to source coding or model training.

[0302] Processor chip on the base station side:

[0303] The processor needs to train a model based on the received information and send the trained model to the server or terminal. At the same time, based on the token provided by the server or terminal, it uses the information source information obtained by reverse engineering the model, such as the data packet size, confidence level, and confidence interval.

[0304] Processor chip on the terminal side:

[0305] The processor needs to collect data related to source coding or model training.

[0306] This application also provides a computer-readable storage medium storing a computer program or instructions. When a computer reads and executes the computer program or instructions, it implements the method performed by the access network device or core network device in the above method embodiments.

[0307] This application also provides a computer program product, which, when read and executed by a computer, implements the method executed by the access network device or the core network device in the above method embodiments.

[0308] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0309] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. Of course, the processor and storage medium can also exist as discrete components in the base station or terminal.

[0310] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0311] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0312] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0313] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0314] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method, characterized in that, include: Sending delay information, the delay information being related to the air interface delay corresponding to at least one terminal device obtained by the access network side, the air interface delay being the transmission delay of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device, the delay information being used to determine the routing strategy corresponding to the at least one terminal device, the routing strategy being used for bearer network transmission between the core network device and the access network device.

2. The method according to claim 1, wherein the delay information includes at least one of the following: expected delay, the air interface delay, or the routing priority information of the at least one terminal device, wherein the expected delay is the expected transmission delay of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface delay.

3. The method according to claim 1, characterized in that, The method further includes: Receive delay response information, wherein the delay response information is a response to the delay information.

4. A communication method, characterized in that, include: The system receives a routing policy corresponding to at least one terminal device. The routing policy is determined based on latency information, which is related to the air interface latency of at least one terminal device obtained by the access network side. The air interface latency is the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device. The routing policy is used for bearer network transmission between the core network device and the access network device.

5. The method according to claim 4, characterized in that, The latency information includes at least one of the following: expected latency, air interface latency, or routing priority information of the at least one terminal device, wherein the expected latency is the expected transmission latency of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface latency.

6. The method according to claim 4 or 5, characterized in that, The method further includes: Send a first request message, the first request message including the latency information, the first request message being used to request the routing policy.

7. The method according to any one of claims 4-6, characterized in that, The method further includes: Receive the delay information.

8. The method according to claim 7, characterized in that, The method further includes: Send a delay response message, which is a response to the delay message.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: Send routing policy response information, which is a response to the routing policy.

10. A communication method, characterized in that, include: Acquire latency information, which is related to the air interface latency of at least one terminal device obtained by the access network side, and the air interface latency is the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device; Based on the latency information, a routing strategy corresponding to the at least one terminal device is determined, and the routing strategy is used for bearer network transmission between the core network device and the access network device. Send the routing policy.

11. The method according to claim 10, characterized in that, The method further includes: A first request message is received, the first request message including the latency information, and the first request message is used to request the routing policy.

12. The method according to claim 10, characterized in that, The acquisition of latency information includes: Receive the delay information.

13. The method according to any one of claims 10-12, characterized in that, The method further includes: Receive routing policy response information, wherein the routing policy response information is a response to the routing policy.

14. A communication method, characterized in that, include: Receive latency information, the latency information being related to the air interface latency of at least one terminal device obtained by the access network side, the air interface latency being the transmission latency of at least one data packet corresponding to the at least one terminal device between the at least one terminal device and the access network device; The delay information is sent to determine the routing strategy corresponding to the at least one terminal device. The routing strategy is used for bearer network transmission between the core network device and the access network device.

15. The method according to claim 14, characterized in that, The latency information includes at least one of the following: expected latency, air interface latency, or routing priority information of the at least one terminal device, wherein the expected latency is the expected transmission latency of the at least one data packet between the access network device and the core network device, and the routing priority information of the at least one terminal device is determined based on the air interface latency.

16. A communication device, characterized in that, The communication device includes a communication unit and a processing unit, wherein the processing unit is configured to perform the processing operation in the method as described in any one of claims 1-15, and the communication unit is configured to perform the sending and receiving operation in the method as described in any one of claims 1-15.

17. A communication device, characterized in that, The communication device includes one or more processors, which are configured to invoke computer programs or instructions stored in a memory to perform the method as described in any one of claims 1-15.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions, which, when read and executed by a computer, implement the method as described in any one of claims 1-15.

19. A computer program product, characterized in that, When the computer reads and executes the computer program product, it implements the method as described in any one of claims 1-15.

Images