Communication method, terminal device and network device

Abstract

Provided are a communication method, a terminal device and a network device. The communication method comprises: a first network element binding a downlink data packet to a first connection on the basis of a first filter parameter, wherein the first filter parameter includes time information or the first filter parameter has an association relationship with the time information, and the time information comprises one or more values or value ranges.

Description

Communication methods, terminal equipment and network equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a terminal device and a network device. Background Technology

[0002] Currently, QoS mechanisms and QoS flow binding are designed for one-way binding and guarantees for either uplink or downlink. However, in some cases, this one-way binding and guarantee is not applicable. For example, in scenarios where computing nodes are introduced to perform computing tasks on terminal devices, guaranteeing one-way transmission latency is no longer suitable. Summary of the Invention

[0003] This application provides a communication method, a terminal device, and a network device. The various aspects covered by this application are described below.

[0004] In a first aspect, a communication method is provided, comprising: a first network element binding a downlink data packet to a first connection according to a first filter parameter, wherein the first filter parameter includes time information or the first filter parameter is associated with the time information, and the time information includes one or more values ​​or a range of values.

[0005] In a second aspect, a communication method is provided, comprising: a terminal device sending a first message to a second network element, the first message being used to request the establishment or modification of a first session, the first session being associated with a first connection, the first message including first indication information and / or a first time; wherein, the first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

[0006] Thirdly, a communication method is provided, comprising: a second network element sending a third message to a first network element, the third message containing a first filter parameter, the first filter parameter being used to bind downlink data packets to a first connection, the first filter parameter containing time information or the first filter parameter being associated with time information, the time information including one or more values ​​or a range of values.

[0007] Fourthly, a network device is provided, which is a first network element. The network device includes: a processing module, configured to bind downlink data packets to a first connection according to first filter parameters, wherein the first filter parameters include time information or the first filter parameters are associated with time information, and the time information includes one or more values ​​or a range of values.

[0008] Fifthly, a terminal device is provided, comprising: a sending module, configured to send a first message to a second network element, the first message being configured to request the establishment or modification of a first session, the first session being associated with a first connection, the first message including first indication information and / or a first time; wherein, the first indication information is configured to instruct the terminal device to request or support the guarantee of the first time, and the first time is configured to indicate the time requirement corresponding to the first connection.

[0009] In a sixth aspect, a network device is provided, which is a second network element. The network device includes: a first sending module, configured to send a third message to the first network element, the third message including a first filter parameter, the first filter parameter being used to bind downlink data packets to a first connection, the first filter parameter including time information or having a correlation between the first filter parameter and time information, the time information including one or more values ​​or a range of values.

[0010] In a seventh aspect, a network device is provided, including a processor and a memory, the memory being used to store one or more computer programs, and the processor being used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the first aspect.

[0011] Eighthly, a terminal device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the second aspect.

[0012] A ninth aspect provides a network device including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps of the method of the third aspect.

[0013] Tenthly, embodiments of this application provide a communication system including the aforementioned terminal device and / or network device. In another possible design, the system may further include other devices that interact with the terminal device or network device as described in the embodiments of this application.

[0014] Eleventhly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to perform some or all of the steps in the methods described above.

[0015] In a twelfth aspect, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0016] In a thirteenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0017] In this embodiment, the first network element can bind data packets to user plane connections (such as QoS flows) based on filter parameters containing time information or filter parameters that are related to time information. That is, the first network element can dynamically bind user plane connections based on time information, which helps to ensure round-trip transmission time and / or simultaneously ensure transmission time and computation time. Attached Figure Description

[0018] Figure 1 is a system architecture example diagram of a wireless communication system applicable to embodiments of this application.

[0019] Figure 2 is a schematic diagram of the QoS flow applicable to the embodiments of this application.

[0020] Figure 3 is an example diagram of the process of establishing a protocol data unit (PDU) session.

[0021] Figure 4 is a scenario example diagram of computing power unloading provided in the embodiments of this application.

[0022] Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application.

[0023] Figure 6 is an example diagram of filters and QoS flows provided in an embodiment of this application.

[0024] Figure 7 is an example diagram of time information in filter parameters provided in an embodiment of this application.

[0025] Figure 8 is an example diagram of time information in filter parameters provided in another embodiment of this application.

[0026] Figure 9 is a flowchart illustrating a communication method provided in another embodiment of this application.

[0027] Figure 10 is a schematic diagram of the structure of a network device provided in an embodiment of this application.

[0028] Figure 11 is a schematic diagram of the structure of the terminal device provided in the embodiment of this application.

[0029] Figure 12 is a schematic diagram of the structure of a network device provided in another embodiment of this application.

[0030] Figure 13 is a schematic structural diagram of the communication device provided in an embodiment of this application. Detailed Implementation

[0031] Communication system architecture

[0032] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, New Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, non-terrestrial networks (NTN) system, terrestrial networks (TN) system, and Universal Mobile Telecommunications (UMT) system. The technologies provided in this application include UMTS (Underground Universe Telecommunications System), wireless local area networks (WLAN), wireless fidelity (WIFI), and 5th-generation (5G) systems. The technical solutions provided in this application can also be applied to other communication systems, such as future communication systems like sixth-generation mobile communication systems and satellite communication systems.

[0033] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

[0034] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0035] The communication system in this application embodiment can be applied to unlicensed spectrum, which can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, which can also be considered as dedicated spectrum.

[0036] A key feature of communication system architecture (such as 5G system architecture) is that it can be a service-oriented architecture, meaning that network elements (service providers) in the core network can provide specific services and make them available to other network elements (consumers) through predefined API interfaces.

[0037] Figure 1 exemplarily illustrates a system architecture example of a wireless communication system to which embodiments of this application can be applied. Taking this communication system as a 5G system architecture as an example, one of the most important features of the 5G network architecture is its service-oriented architecture, meaning that network elements (service providers) in the core network can provide specific services and allow other network elements (consumers) to call them through predefined API interfaces. The wireless communication system shown in Figure 1 may include multiple network elements, nodes, or devices, such as terminal devices, access network (AN) devices, UPF network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, and application function (AF) network elements. The wireless communication system may also include DN, etc.

[0038] The functions of each part or network element involved in the wireless communication system in the 5G network are illustrated below.

[0039] Terminal equipment: Terminal equipment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device. In the embodiments of this application, the terminal equipment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as handheld devices with wireless connectivity, vehicle-mounted devices, etc. The terminal devices in the embodiments of this application may be mobile phones, tablets, laptops, handheld computers, mobile internet devices (MIDs), wearable devices, vehicle devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.

[0040] Access network equipment: Access network equipment provides network access functionality for authorized terminal devices in a specific area and can use transmission channels of different quality depending on the terminal device's level and service requirements. Access network equipment manages radio resources, provides access services to terminal devices, and thus completes the forwarding of control signals and data between the terminal devices and the core network.

[0041] Access network equipment can be a device in a wireless network. Access network equipment can also be called radio access network (RAN) equipment or network equipment; for example, access network equipment can be a base station. In the embodiments of this application, access network equipment can refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, transmitting and receiving point (TRP), transmitting point (TP), master MeNB, auxiliary SeNB, multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, network-side devices in 6G networks, and devices that perform base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network equipment.

[0042] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0043] In some deployments, the access network device in this application embodiment may refer to a CU or a DU, or the access network device may include both a CU and a DU. The gNB may also include an AAU.

[0044] Access network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on aircraft, balloons, and satellites. This application does not limit the scenario in which the access network equipment and terminal equipment are located.

[0045] UPF (User Plane Function) element: The UPF is a user plane function in the core network, responsible for forwarding and receiving user data (such as service data streams) from terminal devices. The UPF can connect to access network devices (such as base stations) and external data networks for data transmission. For example, the UPF can receive user data from the DN (Digital Network Node) and transmit it to the terminal device through the access network device; alternatively, the UPF can also receive user data from the terminal device through the access network device and then forward it to the DN. The transmission resources and scheduling functions providing services to the terminal device in the UPF are managed and controlled by the SMF (Service Provider Function). In some embodiments, the UPF can be divided into intermediate-UPF (I-UPF) and anchor-UPF (A-UPF). The I-UPF is connected to the access network, and the A-UPF is a session anchor UPF, also known as a PDU session anchor (PSA).

[0046] AMF (Active Mobile Element): The AMF is the mobility management function in the core network. It can be used to implement functions other than session management in the mobility management entity (MME), such as lawful interception or access authorization (or authentication). In some embodiments, in addition to performing mobility management on terminal devices, the AMF can also be responsible for forwarding session management-related messages between the terminal device and the SMF.

[0047] SMF Network Element: SMF is the session management function in the core network. It is mainly responsible for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of endpoints for manageable user plane functions, policy control, or charging function interfaces, downlink data notification, and configuration of routing information for user plane functions.

[0048] PCF Network Element: The PCF is a policy management function in the core network, responsible for formulating policies related to mobility management, session management, and charging of terminal devices. Specifically, the PCF can provide policy rule information to control plane functional network elements (such as AMF, SMF, etc.) to manage and control the mobility management and session management of terminal devices.

[0049] AF (Action Frame) network elements: AFs primarily support interaction with the 3rd Generation Partnership Project (3GPP) core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side. In other words, AFs can primarily be used to convey application-side requests to the network side. In some embodiments, an AF can be an internal operator application, such as IP Multimedia Subsystem (IMS) technology. In some embodiments, an AF can be understood as a third-party server, such as an application server on the Internet, providing relevant service information, including providing the PCF (Physical Processing Function) with service-related Quality of Service (QoS) requirement information and sending user plane data information of the service to the A-UPF (Application-Planner Filter). In some embodiments, an AF can also be a content provider (CP). In some embodiments, if the AF is an internal operator AF and is within a trusted domain with other network functions (NFs), it can directly interact and access other NFs; if the AF is not within a trusted domain, it needs to access other NFs through other network elements (e.g., NEF network elements hereinafter referred to as NEF network elements).

[0050] DN: DN refers to a network that can be used to provide data transmission. DN can be a private network, such as a local area network (LAN), an external network not controlled by an operator, such as the Internet, or a proprietary network jointly deployed by operators, such as a network providing IMS services.

[0051] It should be understood that the various network elements mentioned above in the core network can also be referred to as functional entities, and this application does not limit this. For example, a UPF network element can also be referred to as a UPF entity, and an AMF network element can also be referred to as an AMF entity, etc. It should also be understood that in some embodiments, xx network element or xx functional entity can also be directly abbreviated as xx, for example, a UPF network element (or UPF entity) can be abbreviated as UPF, and an AMF network element (or AMF entity) can be abbreviated as AMF. For ease of description, xx (such as UPF, AMF, etc.) mentioned in the embodiments of this application can refer to xx network element or xx entity, which will not be repeated hereafter.

[0052] Optionally, the wireless communication system may also include other network elements such as unified data management (UDM), authentication server function (AUSF), network slice selection function (NSSF), network exposure function (NEF), and NWDAF. This application embodiment does not limit this.

[0053] UDM network elements are subscription databases in the core network, used for generating and storing user subscription data in the network (e.g., 5G network), managing authentication data, and other functions. UDM network elements can support interaction with external third-party servers.

[0054] The AUSF network element can be used to receive AMF requests for authentication of terminal devices, request a key from the UDM, and then forward the issued key to the AMF for authentication processing.

[0055] NSSF network elements can be used for network slicing selection.

[0056] The NEF (Network Element) can manage the network data exposed by the 5G network element. External untrusted applications need to access the core network's internal data through the NEF to ensure the security of the 3GPP network. In some embodiments, the NEF can also provide functions such as opening QoS capabilities for external applications, event subscription, and AF (Active Front-End) request distribution.

[0057] NWDAF network elements can collect data from various network elements and network management systems in the core network for big data statistics, analysis, or intelligent data analysis to obtain network-side analysis results or network-side prediction data. This enables various network elements to more effectively control terminal devices based on the data analysis results.

[0058] In the wireless communication system shown in Figure 1, various parts or network elements can communicate with each other through interfaces. For example, terminal devices connect to the AN (Access Layer) via the Uu interface to exchange access layer messages and wireless data transmission; terminal devices connect to the AMF (Non-Access Stratum, NAS) via the N1 interface to exchange NAS messages; the AN connects to the AMF via the N2 interface to transmit radio bearer control information from the core network side to the AN; the UPF transmits data with the AN via the N3 interface and with the DN (Network Node) via the N6 interface. Other interfaces connecting parts or network elements are shown in Figure 1 and will not be described further here.

[0059] It should be understood that the network elements such as terminal equipment, access network equipment, SMF, and PCF shown in Figure 1 are merely names, and the names do not limit the equipment itself. In 5G networks and other future networks, the network elements corresponding to terminal equipment, access network equipment, SMF, and PCF may also have other names, and this application embodiment does not specifically limit them.

[0060] It should be understood that the above communication system is illustrated using a 5G system as an example. Of course, this application can also be applied to other 3GPP communication systems, such as 4G communication systems or future 3GPP communication systems. The embodiments of this application are not limited in this respect.

[0061] It should be understood that all or part of the functions of the communication device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0062] It should be understood that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will know that with the evolution of network architecture, the embodiments of this application can also be applied to similar technical problems.

[0063] QoS flow

[0064] Referring to Figure 2, the concept of QoS streams is introduced in 5G networks. After a terminal device accesses the 5G network via the Uu port, it can establish QoS streams for data transmission under the control of the SMF (Service Provider Function). The SMF provides the Access Network Equipment (AN) with QoS stream configuration information for each QoS stream, specifically including bit rate requirements, time requirements, and bit error rate requirements. For each QoS stream, the AN can schedule radio resources to guarantee the QoS requirements based on the QoS stream configuration information received from the SMF. In a 5G network, a QoS stream can transmit both uplink data streams (i.e., data streams sent by the terminal device to the peer device via the 5G network) and downlink data streams (i.e., data streams sent by the peer device to the terminal device via the 5G network). Here, the peer device refers to the peer application server or the peer terminal. The time requirements for uplink and downlink data streams within a QoS stream are the same. If the time requirements for the uplink and downlink data streams of a certain service differ, they will be transmitted through different QoS streams. Here, time refers to the data transmission time between the terminal device and the UPF (User Provider Function).

[0065] For uplink and downlink transmission scenarios, QoS rules can be configured on the terminal device side for uplink data QoS flow binding (mapping data packets from different services to QoS flows), and downlink packet detection rules (PDR) can be configured for downlink data QoS flow binding. Similar to UMTS and EPS networks, the core network will still aggregate different service data flows with the same QoS requirements into the same QoS flow for transmission.

[0066] In mobile communication networks, one or more QoS flows need to be established to transmit user plane data, and different QoS flows correspond to different QoS parameters. As an important measure of communication quality, QoS parameters are usually used to indicate the characteristics of QoS flows. QoS parameters may include, but are not limited to: 5G QoS identifier (5QI), allocation and retention priority (ARP), guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), maximum packet loss rate (UL / DL), packet delay budget (PDB), AN-PDB, packet error rate (PER), priority level, averaging window, resource type, maximum data burst volume, UE-aggregate maximum bit rate (UE-AMBR), and session-AMBR.

[0067] The aforementioned QoS parameters can be included in the QoS profile and transmitted to the corresponding nodes (such as access network devices). Each QoS flow can be configured with a set of QoS parameters. For each QoS flow, the QoS profile may include the following parameters: 5QI and ARP. For each non-guaranteed bit rate (non-GBR) QoS flow, the QoS profile may also include the following parameter: reflective QoS attribute (RQA). For each GBR QoS flow, the QoS profile may also include the following parameters: uplink and downlink GFBR, and uplink and downlink MFBR. In the case of only guaranteed GBR QoS flows, the QoS profile may also include one or more of the following QoS parameters: notification control, and maximum uplink and downlink packet loss rate.

[0068] A filter, or service data flow (SDF) template, contains parameters describing the characteristics of data packets and is used to filter out specific packets to bind to a specific QoS flow. The most commonly used filter is the IP 5-tuple, which includes the source IP address, destination IP address, source port number, destination port number, and protocol type.

[0069] UPF and terminal devices form filters based on combinations of packet characteristic parameters (see the trapezoid in the terminal device and the parallelogram in the UPF in Figure 2) to filter uplink or downlink packets that conform to the packet characteristics transmitted in the user plane and bind them to a certain data stream.

[0070] Policy control and charging (PCC) policy

[0071] A PCC policy can contain multiple PCC rules, each of which describes the QoS parameters corresponding to a specific service data flow (described by a service data flow template). Some important parameters are shown in Table 1.

[0072] Table 1

[0073] PDU Session Establishment Process

[0074] The PDU session establishment process is initiated by the terminal device to establish a session connection between the terminal device and the UPF, which can be used to transmit communication data.

[0075] In some scenarios, the PDU session establishment process is shown in Figure 3. The PDU session establishment process shown in Figure 3 may include steps S311 to S330.

[0076] In step S311, the UE sends a PDU session establishment request to the AMF.

[0077] In step S312, the AMF performs SMF selection.

[0078] In step S313, the AMF sends a Create SM Context Request (Namf_PDUSession_CreateSMContext Request) to the SMF.

[0079] In steps S314a-S314b, SMF, PCF, and UDM together perform registration / subscription retrieval / subscription for updates.

[0080] In step S315, the SMF sends a Create SM Context response to the AMF.

[0081] In step S316, PDU session authorization / authentication is performed.

[0082] In step S317a, the SMF performs PCF selection.

[0083] In step S317b, the SMF and PCF establish / modify a session management policy.

[0084] In step S318, the SMF performs UPF selection.

[0085] In step S319, the session management policy is modified between the SMF and the PCF.

[0086] In step S320a, the SMF sends an N4 session establishment / modification request to the UPF.

[0087] In step S320b, the UPF sends an N4 session establishment / modification response to the SMF.

[0088] In step S321, N1N2 message transfer (Namf_Communication_N1N2MessageTransfer) is performed between AMF and SMF.

[0089] In step S322, the AMF sends an N2 PDU session request (NAS msg) to the access network device.

[0090] In step S323, the terminal device and the access network device perform PDU session establishment acceptance (AN - Dedicated Resource Establishment).

[0091] In step S324, the access network device sends an N2 PDU session request confirmation to the AMF, after which the terminal device can send the first uplink data to the UPF.

[0092] In step S325, the AMF sends an UpdateSMContext Request (Nsmf_PDUSession_UpdateSMContext Request) to the SMF.

[0093] In step S326a, the SMF sends an N4 session modification request to the UPF.

[0094] In step S326b, the UPF sends an N4 session modification response to the SMF.

[0095] In step S327, the SMF sends an UpdateSMContext Response (Nsmf_PDUSession_UpdateSMContext Response) to the AMF.

[0096] In step S328, the SMF sends an SM context status notification (Nsmf_PDUSession_SMContextStatusNotify) to the AMF.

[0097] In step S329, the SMF sends the IPv6 address configuration to the UE, and correspondingly, the UPF can send the first downlink data to the UE.

[0098] In step S330, a desubscription / deregistration process is performed between SMF and UDM.

[0099] As can be seen from the above description, current QoS mechanisms and QoS flow binding mechanisms are all unidirectional binding and guarantees for uplink or downlink. However, in some cases, this unidirectional binding and guarantee is not applicable. For example, in scenarios such as introducing computing nodes to perform computing tasks on terminal devices, extended reality (XR) rendering, and end-to-end collaborative artificial intelligence (AI) inference tasks, the demand for guaranteeing round-trip transmission time, and simultaneously guaranteeing transmission time and computing time, is increasing.

[0100] To address the aforementioned issues, this application proposes that the first network element can bind data packets to user plane connections (such as QoS flows) based on filter parameters containing time information or filter parameters that are related to time information. In other words, the first network element can dynamically bind user plane connections based on time information, which helps to ensure round-trip transmission time and / or simultaneously ensure transmission time and computation time.

[0101] To facilitate understanding, the scenarios applicable to the embodiments of this application will be introduced below.

[0102] In some embodiments, the present application can be applied to scenarios where the total round-trip time needs to be considered, such as computing power offloading scenarios, XR scenarios, and AI inference scenarios. In some embodiments, the total round-trip time mentioned in the present application includes not only the round-trip transmission time but also the computation time. That is, the total round-trip time mentioned in the present application includes the time consumed for data transmission and the time consumed for data computation. As an example, the total round-trip time includes the sum of uplink transmission time, downlink transmission time, and computation time, and the uplink transmission time and / or downlink transmission time further include the air interface transmission time and the core network transmission time.

[0103] In some embodiments, the present application can be applied to scenarios where computation time needs to be considered, i.e., scenarios where the data processing (such as computation) of one or more nodes during the data transmission process needs to be considered. For example, the present application can be applied to scenarios where both one-way transmission time and computation time need to be considered (i.e., the total one-way time from end to end).

[0104] The following section, in conjunction with Figure 4, describes the scenario of unloading computing power.

[0105] Computational offloading is a typical scenario where the total round-trip time needs to be considered. Furthermore, in computational offloading scenarios, the total round-trip time includes the time consumed for data transmission and the time consumed for data computation. As shown in Figure 4, after the terminal device sends data packets to the compute node via the uplink user plane connection, the compute node processes the data packets and then sends the processed data packets back to the terminal device via the downlink user plane connection.

[0106] In this application embodiment, a computing node can provide computing power services. For example, a computing node can provide computing power services to a terminal device. In some embodiments, a computing node can be an application server. For example, a computing node can include an edge application server. As another example, a computing node can include a cloud application server. This application embodiment does not limit the deployment form of the computing node. In some embodiments, the computing node can be deployed in a distributed manner. In some embodiments, the computing node can be deployed in a centralized manner.

[0107] This application does not limit the deployment location of the computing nodes. In some embodiments, the computing nodes may be deployed closer to the terminal devices. In some embodiments, the computing nodes may be deployed closer to the access network devices.

[0108] In some embodiments, a computing node can be a node in the core network. In some embodiments, a computing node can be a node on the access network device side. Of course, a computing node can also be a node on other sides, such as a node on a third-party server side, and this application embodiment is not limited in this regard.

[0109] It should be noted that in computing offloading scenarios, the processing time for each computing task (or request), and even for each data packet, varies dynamically due to the influence of many factors such as computing power, memory, storage, and software compatibility. Therefore, computing time needs to be considered in computing offloading scenarios.

[0110] In some embodiments, during a computing offloading scenario, the first network element can bind data packets to different user plane connections (such as QoS flows) according to computing time. Different user plane connections can correspond to different QoS parameter values.

[0111] It should be noted that in computing power offloading scenarios, data transmission and processing typically occur over a period of time to complete a single computing task. Therefore, in some scenarios, it can be assumed that the data is transmitted and processed in bursts at a specific point in time or over a period of time, rather than continuously over a long period. However, the embodiments of this application are not limited to this; the data in the embodiments of this application can be bursty data or continuously transmitted data.

[0112] It should also be noted that for a single computing power offloading, the total number of uplink data packets (e.g., m) and the total number of downlink data packets (e.g., n) can be the same or different.

[0113] The method embodiments of this application will be described below.

[0114] Figure 5 is a schematic flowchart of a communication method provided in an embodiment of this application. The communication method shown in Figure 5 can be executed by a first network element. This first network element can be, for example, a user plane network element, or a UPF shown in Figure 1, or a network element in a future communication system with the same or similar function as a UPF. The method shown in Figure 5 includes step S510, which will be described below.

[0115] In step S510, the first network element binds the downlink data packet to the first connection according to the first filter parameters (i.e. the filter configuration parameters).

[0116] In some embodiments, the first connection may include a user plane connection, i.e., the first connection may be referred to as or replaced by a first user plane connection. Exemplarily, the first connection may include a QoS stream or a connection in a future communication system that functions identically or similarly to a QoS stream. Therefore, in some embodiments, the first connection may be interchangeable with the first QoS stream. For ease of understanding, the following description uses the first connection as an example of a first QoS stream.

[0117] In some embodiments, the first filter parameter includes time information (or latency information). Alternatively, the first filter parameter is associated with the time information. That is, the embodiments of this application associate the first filter parameter with time information, thereby enabling data packets to be bound to QoS flows based on the time information, which helps to ensure round-trip transmission time and / or simultaneously ensure transmission time and computation time.

[0118] In some embodiments, this time information is related to the computation time (i.e., the computation time of the data packet) of the data packet corresponding to the first QoS flow. For example, this time information is directly related to the computation time of the data packet corresponding to the first QoS flow. Alternatively, it may be indirectly related to the computation time of the data packet corresponding to the first QoS flow. Matching appropriate QoS flows to data packets on demand based on the computation time of the data packet corresponding to the first QoS flow helps to ensure the total time (transmission time + computation time), such as ensuring the total round-trip time or the total one-way time.

[0119] In some embodiments, the correlation between time information and the computation time of data packets corresponding to the first QoS flow can be understood as the correlation between time information and one or more data packets corresponding to the first QoS flow, or in other words, the correlation between time information and one or more data packets in the first QoS flow. For example, time information is related to the computation time of one or more data packets generated in a computation task (such as a computation task in a computing offloading scenario). As an example, time information includes the total computation time of one or more data packets (such as all data packets) generated in a computation task. As another example, time information includes the computation time of a single data packet in a computation task.

[0120] This application does not limit the time information in its embodiments. For example, the time information includes one of the following: the calculation time of the data packet corresponding to the first QoS stream, and the sum of the uplink transmission time and the calculation time of the data packet corresponding to the first QoS stream. However, this application is not limited to this; for example, the time information included in the first filter parameter may also include one of the following: the sum of the downlink transmission time and the calculation time of the data packet corresponding to the first QoS stream, and the sum of the uplink transmission time, the calculation time of the data packet, and the downlink transmission time.

[0121] For example, in a downlink transmission scenario, the time information contained in the first filter parameter (i.e., the downlink filter parameter) may include the calculation time of the data packet corresponding to the first QoS stream, or the sum of the uplink transmission time and the calculation time of the data packet corresponding to the first QoS stream, or the sum of the uplink transmission time, the calculation time of the data packet, and the downlink transmission time.

[0122] For example, in an uplink transmission scenario, the time information contained in the first filter parameter (i.e., the uplink filter parameter) may include the calculation time of the data packet corresponding to the first QoS stream, or the sum of the downlink transmission time and the calculation time of the data packet corresponding to the first QoS stream, or the sum of the uplink transmission time, the calculation time of the data packet, and the downlink transmission time corresponding to the first QoS stream.

[0123] In some embodiments, the time information including the calculation time of the data packet corresponding to the first QoS stream may mean that the time information only includes the calculation time of the data packet corresponding to the first QoS stream. In this case, the time information can be considered directly related to the calculation time. In some embodiments, the time information including the calculation time of the data packet corresponding to the first QoS stream may mean that the time information includes the calculation time of the data packet corresponding to the first QoS stream and other times (such as uplink transmission time). In this case, the time information can be considered indirectly related to the calculation time.

[0124] In some embodiments, time information may include one or more values ​​or a range of values. For example, time information may include one or more values. As another example, time information may include one or more ranges of values.

[0125] Taking time information, including computation time, as an example, the time information can include one or more ranges of computation time values. For instance, the time information contained in the first filter parameter can include: filter parameter 1 {computation time ≤ 10ms}, filter parameter 2 {10ms < computation time < 20ms}, and filter parameter 3 {computation time ≥ 20ms}. Of course, filter parameter 1, filter parameter 2, and filter parameter 3 can be referred to as or understood as different parameter values ​​of the first filter parameter.

[0126] In some embodiments, different filter parameters correspond to different filters. In other words, the parameter values ​​of the first filter parameter are different for different filters. For example, filter parameter 1 corresponds to filter 1, filter parameter 2 corresponds to filter 2, and filter parameter 3 corresponds to filter 3. For instance, the time information in the first filter parameter corresponding to filter 1 is: calculation time ≤ 10ms. Another example is that the time information in the first filter parameter corresponding to filter 2 is: 10ms < calculation time < 20ms. Yet another example is that the time information in the first filter parameter corresponding to filter 3 is: calculation time ≥ 20ms.

[0127] This application does not limit the first filter parameter, as long as it is a filter configuration parameter that can be used to bind data packets to a QoS flow. For example, in addition to time information, the first filter parameter may also include IP address configuration, such as an IP 5-tuple.

[0128] In some embodiments, to ensure the total round-trip time and / or the total one-way time, it is necessary to bind data packets with longer computation times to QoS flows with higher QoS parameter requirements. For example, data packets with longer computation times can be bound to QoS flows with shorter transmission times (such as PDB). Alternatively, data packets with longer computation times can be bound to QoS flows with higher transmission rates. As one implementation, when the time information in the first filter parameter corresponding to filter 1 is ≤ 10ms and the time information in the first filter parameter corresponding to filter 2 is 10ms < computation time < 20ms, the QoS parameter requirement for filter 1 can be higher than that for filter 2.

[0129] In some embodiments, different filters can correspond to different QoS flows. In other words, different filters have different QoS flow parameter requirements. As shown in Figure 6, filter 1 (e.g., uplink filter 1 or downlink filter 1) corresponds to QoS flow 1, filter 2 corresponds to QoS flow 2, and filter 3 corresponds to QoS flow 3. The parameter values ​​of the first filter parameters corresponding to filter 1, filter 2, and filter 3 are different. Correspondingly, the QoS parameter requirements for QoS flow 1, QoS flow 2, and QoS flow 3 are different.

[0130] In some embodiments, different QoS stream parameter requirements mean that different QoS streams correspond to different QoS parameters, thus resulting in different data transmission capabilities for different QoS streams. This application does not limit the QoS parameters corresponding to QoS streams. For example, QoS parameters may include one or more of the following: ARP, GFBR, MFBR, maximum packet loss rate, end-to-end PDB, AN-PDB, packet error rate, priority level, average window, resource type, maximum data burst size, UE-AMBR, and session-AMBR.

[0131] In some embodiments, QoS parameters may include one of the parameters described above. For example, a QoS parameter may include ARP. Another example is a QoS parameter that includes GFBR. Yet another example is a QoS parameter that includes MFBR. And yet another example is a QoS parameter that includes maximum packet loss rate.

[0132] In some embodiments, QoS parameters may include multiple parameters listed above. For example, QoS parameters may include ARP and GFBR. Alternatively, QoS parameters may include GFBR and MFBR. Another example is that QoS parameters may include ARP, GFBR, maximum packet loss rate, and end-to-end PDB. Yet another example is that QoS parameters may include ARP, maximum packet loss rate, AN-PDB, packet error rate, priority level, and UE-AMBR. Yet another example is that QoS parameters may include ARP, GFBR, MFBR, maximum packet loss rate, end-to-end PDB, AN-PDB, packet error rate, priority level, average window, resource type, maximum data burst size, UE-AMBR, and session-AMBR.

[0133] It should be noted that the above examples are merely illustrations, and QoS parameters can include any one or more of the above parameters. For the sake of brevity, they will not be listed one by one here.

[0134] In some embodiments, when the first filter parameter includes time information, the first network element can bind downlink data packets to the first connection based on the first filter parameter containing time information.

[0135] In some embodiments, the first network element binding downlink data packets to the first QoS flow according to the first filter parameters containing time information means that the first network element can bind downlink data packets to the first QoS flow based on the calculation time on the first network element side (i.e., the calculation consumption time on the first network element side).

[0136] In some embodiments, the first network element binding downlink data packets to the first QoS flow according to the first filter parameters containing time information means that the first network element binds downlink data packets to the first QoS flow according to the downlink filter parameters containing time information.

[0137] In some embodiments, where the first filter parameter is associated with time information, the first network element can select different filters (or filter parameters) based on different calculation times (see below for an introduction to calculation time) so as to bind downlink data packets to the first QoS flow according to the selected filter (or filter parameter).

[0138] As one implementation, the first network element can select the first filter parameter corresponding to the calculation time based on the calculation time and the correlation between the first filter parameter and time information, and bind the downlink data packet to the first QoS flow according to the first filter parameter. For example, the first network element can bind the downlink data packet to the first QoS flow based on the calculation time measured by the first network element and the correlation between the first filter parameter and time information. As another example, the first network element can bind the downlink data packet to the first QoS flow based on the calculation time sent by other devices (such as the second network element, application server, terminal device, etc.) and the correlation between the first filter parameter and time information.

[0139] In some embodiments, where there is a correlation between the first filter parameters and time information, the second network element can update the filter for the first network element based on this correlation. Alternatively, the second network element can directly send the calculated time value to the first network element, so that the first network element can bind downlink data packets to the first QoS flow based on the calculated time and the correlation between the first filter parameters and time information. A description of the second network element will be provided later and will not be detailed here.

[0140] In some embodiments, the first network element binds downlink data packets to the first QoS flow according to the first filter parameters, including: the first network element binds downlink data packets to the first QoS flow according to the calculation time of the downlink data packets and the first filter parameters.

[0141] As one implementation, if the first network element determines that the calculation time of the downlink data packet matches a first value or a first value range in the time information contained in the first filter parameters, then the first network element binds the downlink data packet to the first QoS flow corresponding to the first value or the first value range. Conversely, if the first network element determines that the calculation time of the downlink data packet matches a second value or a second value range in the time information contained in the first filter parameters, then the first network element binds the downlink data packet to the second QoS flow corresponding to the second value or the second value range.

[0142] Taking the calculation time of the data packet corresponding to the first QoS flow as an example, the time information contained in the first filter parameter is: calculation time ≤ 10ms, the time information corresponding to filter 1 is: 10ms < calculation time < 20ms, and the time information corresponding to filter 3 is: calculation time ≥ 20ms. In a scenario where the data packet is transmitted uplink first and then downlink (such as a scenario of computing power offloading), if the total round-trip time (uplink transmission time + calculation time + downlink transmission time) is 25ms, the uplink transmission time is a fixed value of 5ms according to the uplink QoS corresponding to the QoS flow, and the calculation time of the downlink data packet on the first network element side is 14ms, then according to the calculation time of the downlink data packet and the first filter parameter, the first network element can determine that the downlink data packet needs to be bound to filter 2 in order to transmit the downlink data packet through the QoS flow corresponding to filter 2.

[0143] As another implementation, if the first network element determines that the sum of the calculation time of the downlink data packet and the uplink transmission time corresponding to the first QoS flow matches a first value or a first value range in the time information contained in the first filter parameters, then the first network element binds the downlink data packet to the first QoS flow corresponding to the first value or the first value range. Conversely, if the first network element determines that the sum of the calculation time of the downlink data packet and the uplink transmission time corresponding to the first QoS flow matches a second value or a second value range in the time information contained in the first filter parameters, then the first network element binds the downlink data packet to the second QoS flow corresponding to the second value or the second value range.

[0144] Taking the first filter parameter containing the sum of the calculation time and uplink transmission time of the data packet corresponding to the first QoS flow as an example, assuming the time information for filter 1 is: calculation time + uplink transmission time ≤ 10ms, the time information for filter 2 is: 10ms < calculation time + uplink transmission time < 20ms, and the time information for filter 3 is: calculation time + uplink transmission time ≥ 20ms. In a scenario where the data packet is transmitted uplink first and then downlink, if the total round-trip time (uplink transmission time + calculation time + downlink transmission time) is 25ms, and the uplink transmission time is a fixed value of 10ms according to the uplink QoS corresponding to the QoS flow, and the calculation time of the uplink data packet on the first network element side is 14ms, then the calculation time + uplink transmission time of the uplink data packet = 14 + 10 = 24ms. The first network element can determine that the downlink data packet needs to be bound to filter 3 to transmit the downlink data packet through the QoS flow corresponding to filter 3.

[0145] Taking the example where the time information contained in the first filter parameters is the sum of the calculation time and the uplink transmission time of the data packet corresponding to the first QoS flow, and assuming that the time information corresponding to filter 1 is: calculation time + uplink transmission time ≤ 10ms, the time information corresponding to filter 2 is: 10ms < calculation time + uplink transmission time < 20ms, and the time information corresponding to filter 3 is: calculation time + uplink transmission time ≥ 20ms. In a scenario where the data packet is transmitted uplink first and then downlink, if the total round-trip time (uplink transmission time + calculation time + downlink transmission time) is 25ms, and the uplink transmission time is calculated as 3ms based on the time difference between the terminal device sending the first uplink data packet and the first network element receiving the last uplink data packet, and the calculation time of the downlink data packet on the first network element side is 14ms, then the calculation time of the downlink data packet + uplink transmission time = 14 + 3 = 17ms. The first network element can determine that it needs to bind the downlink data packet to filter 2 to transmit the downlink data packet through the QoS flow corresponding to filter 2.

[0146] As another implementation, if the first network element determines that the remaining time of the downlink data packet matches a first value or a first value range in the time information contained in the first filter parameters, then the first network element binds the downlink data packet to the first QoS flow corresponding to the first value or the first value range. Conversely, if the first network element determines that the remaining time of the downlink data packet matches a second value or a second value range in the time information contained in the first filter parameters, then the first network element binds the downlink data packet to the second QoS flow corresponding to the second value or the second value range.

[0147] The remaining time for the downlink data packet is determined based on the computation time of the downlink data packet and / or the uplink transmission time corresponding to the first QoS flow. For example, the remaining time for the downlink data packet is equal to the total round-trip time of the downlink data packet minus the uplink transmission time corresponding to the first QoS flow minus the computation time of the downlink data packet.

[0148] Taking the remaining time of the data packet corresponding to the first QoS flow as an example, the time information contained in the first filter parameter is: remaining time ≤ 10ms, the time information corresponding to filter 1 is: 10ms < remaining time < 20ms, and the time information corresponding to filter 3 is: remaining time ≥ 20ms. In a scenario where the data packet is transmitted uplink first and then downlink, if the total round-trip time (uplink transmission time + calculation time + downlink transmission time) is 25ms, the uplink transmission time is a fixed value of 5ms according to the uplink QoS corresponding to the QoS flow, and the calculation time of the downlink data packet on the first network element side is 14ms, then the remaining time of the downlink data packet is 25 - 5 - 14 = 6ms. Based on the remaining time of the downlink data packet and the first filter parameter, the first network element can determine that the downlink data packet needs to be bound to filter 1 to transmit the downlink data packet through the QoS flow corresponding to filter 1.

[0149] Taking the example where the time information contained in the first filter parameter is the remaining time of the data packet corresponding to the first QoS flow, assuming the time information for filter 1 is: remaining time ≤ 10ms, the time information for filter 2 is: 10ms < remaining time < 20ms, and the time information for filter 3 is: remaining time ≥ 20ms. In a scenario where the data packet is transmitted uplink first and then downlink, if the total round-trip time (uplink transmission time + calculation time + downlink transmission time) is 30ms, and the uplink transmission time is calculated as 3ms from the time the terminal device sends the first uplink data packet to the time the first network element receives the last uplink data packet, and the calculation time for the downlink data packet on the first network element side is 16ms, then the remaining time for the downlink data packet is 30 - 3 - 16 = 11ms. Based on the remaining time of the downlink data packet and the first filter parameter, the first network element can determine that the downlink data packet needs to be bound to filter 2 to be transmitted through the QoS flow corresponding to filter 2.

[0150] It should be noted that, in addition to calculating the uplink transmission time as the difference between the time the terminal device sends the first uplink data packet and the time the first network element receives the last uplink data packet, the above-mentioned uplink transmission time can also be calculated according to the calculation method mentioned below. The difference is that the statistical object is the time for sending and receiving data between the terminal device and the first network element.

[0151] In some embodiments, in scenarios where uplink transmission precedes downlink transmission, the uplink transmission time can be assumed to be constant, for example, the uplink transmission time can be a fixed value (e.g., a fixed value of 5ms) according to the uplink QoS corresponding to the QoS stream. In this case, downlink data packets can be bound to downlink QoS streams with different QoS parameters as needed for transmission based on the calculation time, to meet the requirements of total round-trip time or total downlink time. Figure 7 shows the total round-trip time corresponding to different filter parameters. As shown in Figure 7, in different filter parameters, the uplink transmission time is constant, while the calculation time and downlink transmission time vary.

[0152] In other embodiments, in scenarios where uplink transmission precedes downlink transmission, the uplink transmission time can be dynamically determined (or statistically calculated). For example, the uplink transmission time is the time difference between the first data packet transmitted by the terminal device and the last data packet received by the first network element. In this case, downlink data packets can be bound to downlink QoS streams with corresponding different QoS parameters on demand based on the calculation time plus the uplink transmission time to meet the requirements of total round-trip time or total downlink time. Figure 8 shows the total round-trip time corresponding to different filter parameters. As shown in Figure 8, the uplink transmission time, calculation time, and downlink transmission time all vary with different filter parameters.

[0153] It should be noted that uplink and downlink transmissions of data for the same computing task can be bound to different QoS flows. For example, the first network element binds a downlink data packet to the first QoS flow according to the first filter parameters, but the downlink data packet is actually bound to the second QoS flow during uplink transmission.

[0154] As mentioned above, the time information contained in the first filter parameters is related to the calculation time of the data packets corresponding to the first QoS flow. The following section provides an example of how the calculation time is determined.

[0155] In some embodiments, the calculation time can be determined based on the difference between the time point of the uplink data packet transmitted on the user plane and the time point of the downlink data packet transmitted.

[0156] In other embodiments, the calculation time is sent by other network elements. For example, the calculation time may be sent by a second network element. Another example is that the calculation time may be sent by an application server. Yet another example is that the calculation time may be sent by a terminal device. It should be noted that the embodiments of this application do not limit the calculation time to be indicated by a second network element, an application server, or a terminal device; for example, the calculation time may be indicated by any network element in the core network.

[0157] This application does not limit the method for determining the calculation time in its embodiments. In some implementations, the calculation time can be determined based on the difference between the time point of the first data packet transmitted uplink by the first network element and the time point of the first data packet transmitted downlink. Taking the scenario in Figure 4 as an example, the calculation time can be the difference between the time point of the first network element transmitting uplink data packet -1 and the time point of transmitting downlink data packet -1.

[0158] In other implementations, the calculation time can be determined based on the difference between the time of the last data packet transmitted uplink by the first network element and the time of the first data packet transmitted downlink. Taking the scenario in Figure 4 as an example, the calculation time can be the difference between the time when the first network element transmits uplink data -m and the time when it transmits downlink data -1.

[0159] In some implementations, the calculation time can be determined based on the difference between the time of the first data packet transmitted uplink by the first network element and the time of the last data packet transmitted downlink. Taking the scenario in Figure 4 as an example, the calculation time can be the difference between the time when the first network element transmits uplink data -1 and the time when it transmits downlink data -n.

[0160] In some implementations, the calculation time can be determined based on the difference between the time of the first data packet transmitted uplink by the first network element and the time of the second data packet transmitted downlink, where the second data packet corresponds to the first data packet. For example, the Kth data packet transmitted uplink by the first network element corresponds to the Qth data packet transmitted downlink, and the calculation time can be determined based on the difference between the time of the Kth data packet transmitted uplink by the first network element and the time of the Qth data packet transmitted downlink. This application does not limit K and Q, as long as K is less than or equal to the total number of data packets transmitted uplink, and Q is less than or equal to the total number of data packets transmitted downlink. For example, both K and Q can be 1. Another example is K being m and Q being n, where the mth data packet transmitted uplink by the first QoS flow corresponds to the nth data packet transmitted downlink. Taking the scenario in Figure 4 as an example, the calculation time can be the difference between the time of the first data packet transmitted uplink by the first network element and the time of the second data packet transmitted downlink.

[0161] In some implementations, the computation time can be sent by one or more of the following: a second network element, an application server, or a terminal device. For example, the computation time can be sent by the second network element. Another example is that the computation time can be sent by the application server. Yet another example is that the computation time can be sent by the terminal device.

[0162] It should be noted that the data packet transmitted uplink by the first network element (such as the first uplink data packet) can be understood as the time point at which the first network element receives the data packet from the previous hop (such as the access network device), or as the time point at which the first network element sends the data packet to the next hop (such as the computing node). It also takes time for the first network element to receive the data packet from the previous hop and then send it to the next hop.

[0163] It should also be noted that the data packet transmitted downlink by the first network element (such as the first data packet in the downlink) can be understood as the node from which the first network element receives the data packet from the previous hop (such as a computing node), or it can be understood as the time point at which the first network element sends the data packet to the next hop (such as an access network device).

[0164] In some embodiments, the first data packet (such as the first data packet of an uplink or the first data packet of a downlink) and / or the last data packet (such as the last data packet of an uplink or the last data packet of a downlink) mentioned above refers to the first data packet and / or the last data packet in a data packet for a computing task, or to the first data packet and / or the last data packet in a data burst.

[0165] In some embodiments, the "computation time" mentioned in this application can be understood as the time consumed in processing one or more data packets corresponding to a task (such as a computing task in a computing offloading scenario). For example, computation time can be understood as the time consumed in processing multiple data packets (such as some data packets or all data packets) corresponding to a task. As another example, computation time can be understood as the time consumed in processing one data packet of a task.

[0166] In some embodiments, the first filter parameter is configured by the second network element. That is, the second network element can configure the first filter parameter containing time information to the terminal device and / or the first network element. As one implementation, the second network element can configure the first filter parameter containing time information to the first network element via PDR, so that the first network element can perform downlink data flow binding according to the first filter parameter; and / or, the second network element can configure the first filter parameter containing time information to the terminal device via QoS rules, so that the terminal device can perform uplink data flow binding according to the first filter parameter.

[0167] In some embodiments, the second network element is a network element in the core network.

[0168] In some embodiments, the second network element is used for session management and / or session control. For example, the second network element may be a control plane network element. Another example is that the second network element may be an SMF (Signaling Module Function). Yet another example is that the second network element may be a network element with the same or similar function to an SMF in a future communication system.

[0169] In some embodiments, the first filter parameter is configured by the second network element to the first network element and / or the terminal device during session establishment or session modification. The configuration process of the first filter parameter is described below as an example.

[0170] For the first network element, the second network element can send a third message to the first network element. This third message may include first filter parameters. In some embodiments, the process of the second network element sending the first filter parameters to the first network element can also be understood as the process of the second network element configuring a PDR for the first network element, where the PDR includes the first filter parameters.

[0171] For the terminal device, the second network element can send a second message to the terminal device. The second message may include the first filter parameters. In some embodiments, the process of the second network element sending the first filter parameters to the terminal device can also be understood as the process of the second network element configuring QoS rules for the terminal device, wherein the QoS rules include the first filter parameters. Therefore, in some embodiments, the second message may also be referred to as or understood as a QoS rule, or a message carrying a QoS rule.

[0172] In some embodiments, the second network element can send a second message (i.e., the first filter parameter) to the terminal device via control. As one implementation, the second network element can send the second message to the mobility management network element, which then sends the second message to the terminal device via a NAS message.

[0173] In some embodiments, the second network element can send a second message containing the first filter parameters to the mobility management network element via the Namf_Communication_N1N2MessageTransfer message. For example, the second network element can carry the first filter parameters in a NAS container (such as an N1 SM container) and send it to the mobility management network element via the Namf_Communication_N1N2MessageTransfer message.

[0174] In some embodiments, when a mobility management network element receives a Namf_Communication_N1N2MessageTransfer message, it can send the second message from the Namf_Communication_N1N2MessageTransfer message to an access network device via a NAS message (such as an N2 PDU session request message), and then the access network device can send it to the terminal device. For example, the access network device can send the second message to the terminal device via a NAS message; for instance, the access network device can send the second message to the terminal device via a PDU session establishment accept message.

[0175] In some embodiments, after receiving the first filter parameters, the access network device can establish a QoS flow corresponding to the first filter parameters. For example, the access network device can send an N2 message to establish multiple QoS flows corresponding to different QoS parameters.

[0176] In some embodiments, before configuring the first filter parameters on the second network element, the terminal device may send a first message to the second network element. In some embodiments, the first message may be used to request the establishment or modification of a first session (such as a PDU session). In some embodiments, the first session is associated with a first QoS flow.

[0177] In some embodiments, the first message may include first indication information. The first indication information may be used to instruct the terminal device to request or support or allow protection in the first instance.

[0178] In some embodiments, the first message includes a first time. The first time can be used to indicate the time requirement corresponding to the first QoS flow. For example, the first time in the first message can indicate the time requirement corresponding to the first QoS flow expected by the terminal device.

[0179] In some embodiments, the first time is related to the calculation time of the data packet corresponding to the first QoS flow.

[0180] In some embodiments, the first time may include one of the following: the sum of the uplink transmission time and the computation time corresponding to the first QoS stream, the sum of the downlink transmission time and the computation time corresponding to the first QoS stream, and the sum of the uplink transmission time, the computation time, and the downlink transmission time corresponding to the first QoS stream.

[0181] In some embodiments, the sum of the uplink transmission time and the computation time corresponding to the first QoS stream, and / or the sum of the downlink transmission time and the computation time corresponding to the first QoS stream, can be referred to or understood as the total one-way time (or the total end-to-end time). For example, the sum of the uplink transmission time and the computation time corresponding to the first QoS stream can be referred to or understood as the total uplink time. As another example, the sum of the downlink transmission time and the computation time corresponding to the first QoS stream can be referred to or understood as the total downlink time.

[0182] In some embodiments, the sum of the uplink transmission time corresponding to the first QoS stream, the computation time corresponding to the first QoS stream, and the downlink transmission time corresponding to the first QoS stream can be referred to as or understood as the total round-trip time.

[0183] It should be noted that the total time mentioned in the embodiments of this application refers to the total time including transmission time and computation time. This can be the total time in one direction (such as uplink transmission time + computation time, or downlink transmission time + computation time), or it can be the total round-trip time (uplink transmission time + computation time + downlink transmission time).

[0184] In some embodiments, before the second network element configures the first filter parameters, the third network element may send policy information of the terminal device to the second network element. The third network element may be a network element in the core network. In some embodiments, the third network element may be a network element used for policy control and / or policy formulation. For example, the third network element may be a PCF or a network element in a future communication system that has the same or similar functions as a PCF.

[0185] In some embodiments, the third network element may also send an SDF template to the second network element. The SDF template can be used to describe different services.

[0186] In some embodiments, the first filter parameters are determined based on first indication information sent by the terminal device and / or at a first moment. For example, the first filter parameters generated by the second network element are determined based on the first indication information sent by the terminal device and / or at a first moment.

[0187] In some embodiments, the first filter parameters are determined based on policy information of the terminal device sent by the third network element, such as based on the first time in the policy information. For example, the first filter parameters generated by the second network element are determined based on the first time in the policy information sent by the third network element.

[0188] For ease of understanding, the configuration process of the first filter parameters will be described below with reference to Figure 9.

[0189] Figure 9 is a flowchart illustrating a communication method according to another embodiment of this application. The method shown in Figure 9 includes steps S910 to S970.

[0190] In step S910, the terminal device sends a first message to the second network element.

[0191] In some embodiments, the first message includes first indication information and / or first time. For a description of the first indication information and the first time, please refer to the above.

[0192] In step S920, the third network element sends the terminal device's policy information to the second network element.

[0193] In some embodiments, the policy information may include a first time.

[0194] In step S930, the second network element generates QoS rules and / or PDRs corresponding to the first filter parameters. That is, the QoS rules and / or PDRs are used to indicate the configuration parameters of the filter containing time information.

[0195] In some embodiments, the second network element can generate QoS parameters corresponding to the QoS flow.

[0196] In some embodiments, the QoS rules and / or PDRs corresponding to the first filter parameters are generated based on the first indication information sent by the terminal device and / or at the first moment.

[0197] In other embodiments, the QoS rules and / or PDRs corresponding to the first filter parameters are generated based on the policy information (including the first time) of the terminal device sent by the third network element.

[0198] In step S940, the second network element sends a third message to the first network element. This third message may be, for example, a PDR (Programmable Receiver).

[0199] In some embodiments, the third message includes a first filter parameter. This first filter parameter may include, for example, time information.

[0200] In step S950, the second network element sends a Namf_Communicaation_N1N2MessageTransfer message to the mobility management network element. The Namf_Communicaation_N1N2MessageTransfer message may include a NAS container (such as an N1 SM container) carrying QoS rules.

[0201] In step S960, the mobility management network element sends a first filter parameter (or a first QoS parameter) to the access network device. For example, the mobility management network element may send an N2 PDU session request message to the access network device, which carries the first filter parameter.

[0202] In step S970, the access network device sends the first filter parameters to the terminal device. For example, the access network device may send a PDU session establishment acceptance message to the terminal device, which carries the first filter parameters.

[0203] The method embodiments of this application have been described in detail above with reference to Figures 1 to 9. The apparatus embodiments of this application will be described in detail below with reference to Figures 10 to 13. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0204] Figure 10 is a schematic diagram of the structure of a network device provided in an embodiment of this application. The network device 1000 shown in Figure 10 is a first network element. The network device 1000 includes a processing module 1010. The processing module 1010 can be used to bind downlink data packets to a first connection according to first filter parameters. The first filter parameters include time information or the first filter parameters are associated with time information. The time information includes one or more values ​​or a range of values.

[0205] In some embodiments, the time information is related to the calculation time of the data packet corresponding to the first connection.

[0206] In some embodiments, the time information includes one of the following: the calculation time of the data packet corresponding to the first connection; or the sum of the uplink transmission time corresponding to the first connection and the calculation time.

[0207] In some embodiments, the calculation time is determined based on the difference between the time point of the uplink data packet transmitted by the first network element and the time point of the downlink data packet transmitted.

[0208] In some embodiments, the calculation time is sent by a second network element, an application server, or a terminal device.

[0209] In some embodiments, the calculation time is determined based on one of the following: the difference between the time point of the first data packet transmitted uplink by the first network element and the time point of the first data packet transmitted downlink by the first network element; the difference between the time point of the last data packet transmitted uplink by the first network element and the time point of the first data packet transmitted downlink by the first network element; the difference between the time point of the first data packet transmitted uplink by the first network element and the time point of the last data packet transmitted downlink by the first network element; the difference between the time point of the first data packet transmitted uplink by the first network element and the time point of the second data packet transmitted downlink by the first network element, wherein the second data packet corresponds to the first data packet; and the calculation time received by the first network element from the second network element or the application server.

[0210] In some embodiments, the timing of the uplink data packets transmitted by the first network element includes the timing of the first network element receiving the data packets from the previous hop, or the timing of the first network element sending the data packets to the next hop; and / or, the timing of the downlink data packets transmitted by the first network element includes the timing of the first network element receiving the data packets from the previous hop, or the timing of the first network element sending the data packets to the next hop.

[0211] In some embodiments, the processing module 1010 is further configured to: if the first network element determines that the calculation time of the downlink data packet or the sum of the calculation time of the downlink data packet and the uplink transmission time corresponding to the first connection matches a first value or a first value range in the time information contained in the first filter parameter, then bind the downlink data packet to the first connection corresponding to the first value or the first value range.

[0212] In some embodiments, the processing module 1010 is further configured to: if the first network element determines that the remaining time of the downlink data packet matches a first value or a first value range in the time information contained in the first filter parameter, then bind the downlink data packet to the first connection corresponding to the first value or the first value range; wherein the remaining time of the downlink data packet is determined based on the calculation time of the downlink data packet and / or the uplink transmission time corresponding to the first connection.

[0213] In some embodiments, the network device further includes a receiving module 1020, configured to receive a third message sent by a second network element, the third message containing the first filter parameters.

[0214] In some embodiments, the first filter parameter is determined based on first indication information and / or first time sent by the terminal device, wherein the first indication information is used to instruct the terminal device to request or support guarantee of the first time, and the first time is used to instruct the time requirement corresponding to the first connection.

[0215] In some embodiments, the first filter parameter is determined based on the policy information of the terminal device sent by the third network element. The policy information of the terminal device includes a first time, which is used to indicate the time requirement corresponding to the first connection.

[0216] In some embodiments, the first time includes one of the following: the sum of the uplink transmission time and the computation time corresponding to the first connection; or, the sum of the downlink transmission time and the computation time corresponding to the first connection; or, the sum of the uplink transmission time, the computation time, and the downlink transmission time corresponding to the first connection.

[0217] In some embodiments, the processing module 1010 may be a processor 1310. The network device 1000 may also include a transceiver 1330 and a memory 1320, as shown in FIG13.

[0218] Figure 11 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The terminal device 1100 shown in Figure 11 includes a sending module 1110. The sending module 1110 can be used to send a first message to a second network element. The first message is used to request the establishment or modification of a first session. The first session is associated with a first connection. The first message includes first indication information and / or a first time. The first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

[0219] In some embodiments, the first time includes one of the following: the sum of the uplink transmission time and the computation time corresponding to the first connection; or, the sum of the downlink transmission time and the computation time corresponding to the first connection; or, the sum of the uplink transmission time, the computation time, and the downlink transmission time corresponding to the first connection.

[0220] In some embodiments, the terminal device further includes a receiving module 1120, configured to receive a second message sent by the second network element, the second message including first filter parameters.

[0221] In some embodiments, the transmitting module 1110 may be a transceiver 1330. The terminal device 1100 may also include a processor 1310 and a memory 1320, as shown in FIG13.

[0222] Figure 12 is a schematic diagram of a network device provided in another embodiment of this application. The network device 1200 shown in Figure 12 includes a first sending module 1210. The first sending module 1210 can be used to send a third message to a first network element. The third message includes a first filter parameter. The first filter parameter is used to bind downlink data packets to a first connection. The first filter parameter includes time information or the first filter parameter is associated with time information. The time information includes one or more values ​​or a range of values.

[0223] In some embodiments, the time information is related to the calculation time of the data packet corresponding to the first connection.

[0224] In some embodiments, the time information includes one of the following: the calculation time of the data packet corresponding to the first connection; or the sum of the uplink transmission time corresponding to the first connection and the calculation time.

[0225] In some embodiments, the calculation time is determined based on the difference between the time point of the uplink data packet transmitted by the first network element and the time point of the downlink data packet transmitted.

[0226] In some embodiments, the calculation time is sent by a second network element, an application server, or a terminal device.

[0227] In some embodiments, the calculation time is determined based on one of the following: the difference between the time point of the first data packet transmitted uplink by the first network element and the time point of the first data packet transmitted downlink by the first network element; the difference between the time point of the last data packet transmitted uplink by the first network element and the time point of the first data packet transmitted downlink by the first network element; the difference between the time point of the first data packet transmitted uplink by the first network element and the time point of the last data packet transmitted downlink by the first network element; the difference between the time point of the first data packet transmitted uplink by the first network element and the time point of the second data packet transmitted downlink by the first network element, wherein the second data packet corresponds to the first data packet; and the calculation time received by the first network element from the second network element or the application server.

[0228] In some embodiments, the timing of the uplink data packets transmitted by the first network element includes the timing of the first network element receiving the data packets from the previous hop, or the timing of the first network element sending the data packets to the next hop; and / or, the timing of the downlink data packets transmitted by the first network element includes the timing of the first network element receiving the data packets from the previous hop, or the timing of the first network element sending the data packets to the next hop.

[0229] In some embodiments, the network device further includes: a receiving module 1220, configured to receive a first message sent by a terminal device, the first message being used to request the establishment or modification of a first session, the first session being associated with the first connection, the first message including first indication information and / or a first time; wherein, the first indication information is used to instruct the terminal device to request or support guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

[0230] In some embodiments, the network device further includes: a second sending module, configured to send a second message to a terminal device, the second message containing the first filter parameters.

[0231] In some embodiments, the first filter parameter is determined based on first indication information and / or first time sent by the terminal device, wherein the first indication information is used to instruct the terminal device to request or support guarantee of the first time, and the first time is used to instruct the time requirement corresponding to the first connection.

[0232] In some embodiments, the first filter parameter is determined based on the policy information of the terminal device sent by the third network element. The policy information of the terminal device includes a first time, which is used to indicate the time requirement corresponding to the first connection.

[0233] In some embodiments, the first time includes one of the following: the sum of the uplink transmission time and the computation time corresponding to the first connection; or, the sum of the downlink transmission time and the computation time corresponding to the first connection; or, the sum of the uplink transmission time, the computation time, and the downlink transmission time corresponding to the first connection.

[0234] In some embodiments, the first transmitting module 1210 may be a transceiver 1330. The network device 1200 may also include a processor 1310 and a memory 1320, as shown in FIG13.

[0235] Figure 13 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 13 indicate that the unit or module is optional. This device 1300 can be used to implement the methods described in the above method embodiments. Device 1300 can be a chip, a terminal device, or a network device.

[0236] Apparatus 1300 may include one or more processors 1310. The processor 1310 may support apparatus 1300 in implementing the methods described in the preceding method embodiments. The processor 1310 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0237] The apparatus 1300 may further include one or more memories 1320. The memories 1320 store a program that can be executed by the processor 1310, causing the processor 1310 to perform the methods described in the preceding method embodiments. The memories 1320 may be independent of the processor 1310 or integrated within the processor 1310.

[0238] The device 1300 may also include a transceiver 1330. The processor 1310 can communicate with other devices or chips via the transceiver 1330. For example, the processor 1310 can send and receive data with other devices or chips via the transceiver 1330.

[0239] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0240] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal device or network device provided in the embodiments of this application, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0241] This application also provides a computer program. This computer program can be applied to the terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of this application.

[0242] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0243] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

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

[0245] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0246] In the embodiments of this application, the term "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" in the embodiments of this application can be replaced with "instructing" or "used to determine". For example, "A includes B" can be replaced with "A instructs B" or "A is used to determine B".

[0247] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0248] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0249] In the embodiments of this application, the term "and / or" 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 existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0250] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0251] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0253] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0254] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0255] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method characterized by comprising: include: The first network element binds downlink data packets to the first connection according to the first filter parameters. The first filter parameters include time information or there is a correlation between the first filter parameters and time information. The time information includes one or more values ​​or a range of values.

2. The method of claim 1, wherein, The time information is related to the calculation time of the data packet corresponding to the first connection.

3. The method according to claim 1 or 2, characterized in that, The time information includes one of the following: The computation time of the data packet corresponding to the first connection; or The sum of the uplink transmission time corresponding to the first connection and the calculation time.

4. The method according to claim 2 or 3, characterized in that, The calculation time is determined based on the difference between the time point of the uplink data packet transmitted by the first network element and the time point of the downlink data packet transmitted.

5. The method according to claim 2 or 3, characterized in that, The calculation time is sent by the second network element, application server, or terminal device.

6. The method according to any one of claims 2-5, characterized in that, The calculation time is determined based on one of the following: The time difference between the first data packet transmitted uplink and the first data packet transmitted downlink by the first network element; The time difference between the last data packet transmitted uplink by the first network element and the time of the first data packet transmitted downlink; The time difference between the first data packet transmitted uplink by the first network element and the last data packet transmitted downlink; The time difference between the first data packet transmitted uplink by the first network element and the time difference between the second data packet transmitted downlink by the first network element; the second data packet corresponds to the first data packet. The computation time received by the first network element from the second network element or the application server.

7. The method according to claim 4 or 6, characterized in that: The time point of the data packet transmitted uplink by the first network element includes the time point when the first network element receives the data packet from the previous hop, or the time point when the first network element sends the data packet to the next hop; and / or The timing of the data packets transmitted downlink by the first network element includes the timing when the first network element receives the data packets from the previous hop, or the timing when the first network element sends the data packets to the next hop.

8. The method according to any one of claims 1-7, characterized in that, The first network element binds downlink data packets to the first connection according to the first filter parameters, including: If the first network element determines that the calculation time of the downlink data packet or the sum of the calculation time of the downlink data packet and the uplink transmission time corresponding to the first connection matches the first value or the first value range in the time information contained in the first filter parameter, then the first network element binds the downlink data packet to the first connection corresponding to the first value or the first value range.

9. The method according to any one of claims 1-7, characterized in that, The first network element binds downlink data packets to the first connection according to the first filter parameters, including: If the first network element determines that the remaining time of the downlink data packet matches a first value or a first value range in the time information contained in the first filter parameter, then the first network element binds the downlink data packet to the first connection corresponding to the first value or the first value range. The remaining time of the downlink data packet is determined based on the calculation time of the downlink data packet and / or the uplink transmission time corresponding to the first connection.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: The first network element receives a third message sent by the second network element, the third message containing the first filter parameters.

11. The method according to any one of claims 1-10, characterized in that, The first filter parameter is determined based on the first indication information and / or the first time sent by the terminal device. The first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

12. The method according to any one of claims 1-10, characterized in that, The first filter parameter is determined based on the policy information of the terminal device sent by the third network element. The policy information of the terminal device includes a first time, which is used to indicate the time requirement corresponding to the first connection.

13. The method according to claim 11 or 12, characterized in that, The first time includes one of the following: The sum of the uplink transmission time and the computation time corresponding to the first connection; or, The sum of the downlink transmission time and the computation time corresponding to the first connection; or, The sum of the uplink transmission time corresponding to the first connection, the computation time corresponding to the first connection, and the downlink transmission time corresponding to the first connection.

14. A communication method, comprising: include: The terminal device sends a first message to the second network element. The first message is used to request the establishment or modification of a first session. The first session is associated with a first connection. The first message includes first indication information and / or a first time. The first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

15. The method of claim 14, wherein, The first time includes one of the following: The sum of the uplink transmission time and the computation time corresponding to the first connection; or, The sum of the downlink transmission time and the computation time corresponding to the first connection; or, The sum of the uplink transmission time corresponding to the first connection, the computation time corresponding to the first connection, and the downlink transmission time corresponding to the first connection.

16. The method according to claim 14 or 15, characterized in that The method further includes: The terminal device receives a second message sent by the second network element, the second message including a first filter parameter.

17. A method of communication, comprising: include: The second network element sends a third message to the first network element. The third message contains a first filter parameter. The first filter parameter is used to bind downlink data packets to the first connection. The first filter parameter contains time information or the first filter parameter is associated with time information. The time information includes one or more values ​​or a range of values.

18. The method of claim 17, wherein, The time information is related to the calculation time of the data packet corresponding to the first connection.

19. The method of claim 17 or 18, wherein, The time information includes one of the following: The computation time of the data packet corresponding to the first connection; or The sum of the uplink transmission time corresponding to the first connection and the calculation time.

20. The method of claim 18 or 19, wherein, The calculation time is determined based on the difference between the time point of the uplink data packet transmitted by the first network element and the time point of the downlink data packet transmitted.

21. The method of claim 18 or 19, wherein, The calculation time is sent by the second network element, application server, or terminal device.

22. The method of any one of claims 18-21, wherein, The calculation time is determined based on one of the following: The time difference between the first data packet transmitted uplink and the first data packet transmitted downlink by the first network element; The time difference between the last data packet transmitted uplink by the first network element and the time of the first data packet transmitted downlink; The time difference between the first data packet transmitted uplink by the first network element and the last data packet transmitted downlink; The time difference between the first data packet transmitted uplink by the first network element and the time difference between the second data packet transmitted downlink by the first network element; the second data packet corresponds to the first data packet. The computation time received by the first network element from the second network element or the application server.

23. The method according to claim 20 or 22, characterized in that: The time point of the data packet transmitted uplink by the first network element includes the time point when the first network element receives the data packet from the previous hop, or the time point when the first network element sends the data packet to the next hop; and / or The timing of the data packets transmitted downlink by the first network element includes the timing when the first network element receives the data packets from the previous hop, or the timing when the first network element sends the data packets to the next hop.

24. The method of any one of claims 17-23, wherein, The method further includes: The second network element receives a first message sent by the terminal device. The first message is used to request the establishment or modification of a first session. The first session is associated with the first connection. The first message includes first indication information and / or a first time. The first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

25. The method of any one of claims 17-24, wherein, The method further includes: The second network element sends a second message to the terminal device, the second message containing the first filter parameters.

26. The method of any one of claims 17-25, wherein, The first filter parameter is determined based on the first indication information and / or the first time sent by the terminal device. The first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

27. The method of any one of claims 17-26, wherein, The first filter parameter is determined based on the policy information of the terminal device sent by the third network element. The policy information of the terminal device includes a first time, which is used to indicate the time requirement corresponding to the first connection.

28. The method of claim 24 or 26 or 27, wherein, The first time includes one of the following: The sum of the uplink transmission time and the computation time corresponding to the first connection; or, The sum of the downlink transmission time and the computation time corresponding to the first connection; or, The sum of the uplink transmission time corresponding to the first connection, the computation time corresponding to the first connection, and the downlink transmission time corresponding to the first connection.

29. A network device, comprising: The network device is a first network element, and the network device includes: The processing module is used to bind downlink data packets to a first connection according to a first filter parameter, wherein the first filter parameter contains time information or the first filter parameter is associated with time information, and the time information includes one or more values ​​or a range of values.

30. The network device of claim 29, wherein, The time information is related to the calculation time of the data packet corresponding to the first connection.

31. The network device of claim 29 or 30, wherein, The time information includes one of the following: The computation time of the data packet corresponding to the first connection; or The sum of the uplink transmission time corresponding to the first connection and the calculation time.

32. The network device of claim 30 or 31, wherein, The calculation time is determined based on the difference between the time point of the uplink data packet transmitted by the first network element and the time point of the downlink data packet transmitted.

33. The network device of claim 30 or 31, wherein, The calculation time is sent by the second network element, application server, or terminal device.

34. The network device according to any one of claims 30-33, characterized in that, The calculation time is determined based on one of the following: The time difference between the first data packet transmitted uplink and the first data packet transmitted downlink by the first network element; The time difference between the last data packet transmitted uplink by the first network element and the time of the first data packet transmitted downlink; The time difference between the first data packet transmitted uplink by the first network element and the last data packet transmitted downlink; The time difference between the first data packet transmitted uplink by the first network element and the time difference between the second data packet transmitted downlink by the first network element; the second data packet corresponds to the first data packet. The computation time received by the first network element from the second network element or the application server.

35. The network device according to claim 32 or 34, characterized in that: The time point of the data packet transmitted uplink by the first network element includes the time point when the first network element receives the data packet from the previous hop, or the time point when the first network element sends the data packet to the next hop; and / or The timing of the data packets transmitted downlink by the first network element includes the timing when the first network element receives the data packets from the previous hop, or the timing when the first network element sends the data packets to the next hop.

36. The network device according to any one of claims 29-35, characterized in that, The processing module is further used for: If the first network element determines that the calculation time of the downlink data packet or the sum of the calculation time of the downlink data packet and the uplink transmission time corresponding to the first connection matches the first value or the first value range in the time information contained in the first filter parameter, then the downlink data packet is bound to the first connection corresponding to the first value or the first value range.

37. The network device according to any one of claims 29-35, characterized in that, The processing module is further used for: If the first network element determines that the remaining time of the downlink data packet matches a first value or a first value range in the time information contained in the first filter parameter, then the downlink data packet is bound to the first connection corresponding to the first value or the first value range. The remaining time of the downlink data packet is determined based on the calculation time of the downlink data packet and / or the uplink transmission time corresponding to the first connection.

38. The network device according to any one of claims 29-37, characterized in that, The network device also includes: The receiving module is used to receive a third message sent by the second network element, wherein the third message contains the first filter parameters.

39. The network device according to any one of claims 29-38, characterized in that, The first filter parameter is determined based on the first indication information and / or the first time sent by the terminal device. The first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

40. The network device according to any one of claims 29-39, characterized in that, The first filter parameter is determined based on the policy information of the terminal device sent by the third network element. The policy information of the terminal device includes a first time, which is used to indicate the time requirement corresponding to the first connection.

41. The network device according to claim 39 or 40, characterized in that, The first time includes one of the following: The sum of the uplink transmission time and the computation time corresponding to the first connection; or, The sum of the downlink transmission time and the computation time corresponding to the first connection; or, The sum of the uplink transmission time corresponding to the first connection, the computation time corresponding to the first connection, and the downlink transmission time corresponding to the first connection.

42. A terminal device, characterized in that, include: The sending module is used to send a first message to the second network element. The first message is used to request the establishment or modification of a first session. The first session is associated with a first connection. The first message includes first indication information and / or a first time. The first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

43. The terminal device according to claim 42, characterized in that, The first time includes one of the following: The sum of the uplink transmission time and the computation time corresponding to the first connection; or, The sum of the downlink transmission time and the computation time corresponding to the first connection; or, The sum of the uplink transmission time corresponding to the first connection, the computation time corresponding to the first connection, and the downlink transmission time corresponding to the first connection.

44. The terminal device according to claim 42 or 43, characterized in that, The terminal device also includes: The receiving module is used to receive a second message sent by the second network element, the second message including the first filter parameters.

45. A network device, characterized in that, The network device is a second network element, and the network device includes: The first sending module is used to send a third message to the first network element. The third message includes a first filter parameter. The first filter parameter is used to bind downlink data packets to the first connection. The first filter parameter includes time information or the first filter parameter is associated with time information. The time information includes one or more values ​​or a range of values.

46. ​​The network device according to claim 45, characterized in that, The time information is related to the calculation time of the data packet corresponding to the first connection.

47. The network device according to claim 45 or 46, characterized in that, The time information includes one of the following: The computation time of the data packet corresponding to the first connection; or The sum of the uplink transmission time corresponding to the first connection and the calculation time.

48. The network device according to claim 46 or 47, characterized in that, The calculation time is determined based on the difference between the time point of the uplink data packet transmitted by the first network element and the time point of the downlink data packet transmitted.

49. The network device according to claim 46 or 47, characterized in that, The calculation time is sent by the second network element, application server, or terminal device.

50. The network device according to any one of claims 46-49, characterized in that, The calculation time is determined based on one of the following: The time difference between the first data packet transmitted uplink and the first data packet transmitted downlink by the first network element; The time difference between the last data packet transmitted uplink by the first network element and the time of the first data packet transmitted downlink; The time difference between the first data packet transmitted uplink by the first network element and the last data packet transmitted downlink; The time difference between the first data packet transmitted uplink by the first network element and the time difference between the second data packet transmitted downlink by the first network element; the second data packet corresponds to the first data packet. The computation time received by the first network element from the second network element or the application server.

51. The network device according to claim 48 or 50, characterized in that: The time point of the data packet transmitted uplink by the first network element includes the time point when the first network element receives the data packet from the previous hop, or the time point when the first network element sends the data packet to the next hop; and / or The timing of the data packets transmitted downlink by the first network element includes the timing when the first network element receives the data packets from the previous hop, or the timing when the first network element sends the data packets to the next hop.

52. The network device according to any one of claims 45-51, characterized in that, The network device also includes: A receiving module is configured to receive a first message sent by a terminal device. The first message is used to request the establishment or modification of a first session. The first session is associated with the first connection. The first message includes first indication information and / or a first time. The first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

53. The network device according to any one of claims 45-52, characterized in that, The network device also includes: The second sending module is used to send a second message to the terminal device, the second message containing the first filter parameters.

54. The network device according to any one of claims 45-53, characterized in that, The first filter parameter is determined based on the first indication information and / or the first time sent by the terminal device. The first indication information is used to instruct the terminal device to request or support the guarantee of the first time, and the first time is used to indicate the time requirement corresponding to the first connection.

55. The network device according to any one of claims 45-54, characterized in that, The first filter parameter is determined based on the policy information of the terminal device sent by the third network element. The policy information of the terminal device includes a first time, which is used to indicate the time requirement corresponding to the first connection.

56. The network device according to claim 52, 54, or 55, characterized in that, The first time includes one of the following: The sum of the uplink transmission time and the computation time corresponding to the first connection; or, The sum of the downlink transmission time and the computation time corresponding to the first connection; or, The sum of the uplink transmission time corresponding to the first connection, the computation time corresponding to the first connection, and the downlink transmission time corresponding to the first connection.

57. A network device, characterized in that, It includes a memory and a processor, the memory being used to store a program, and the processor being used to invoke the program in the memory to cause the network device to perform the method as described in any one of claims 1-13.

58. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method as described in any one of claims 14-16.

59. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 17-28.

60. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-28.

61. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-28.

62. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-28.

63. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-28.

64. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-28.

Images