Communication method and communication device

By using policy control and billing PCC rules between PCF and SMF in the communication system, the round-trip transmission delay of the service data flow is directly controlled, which solves the problem of untimely control delay in the prior art and improves the service data flow Transmission efficiency and user experience.

CN119095103APending Publication Date: 2024-12-06GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202411138590.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-01-07
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The existing technology is difficult to control the round-trip transmission delay of service data flow in a timely manner, resulting in the inability to meet the high-demand user experience, especially in cloud gaming and artificial intelligence interactive services.

Method used

Through the policy control function PCF sends policy control and billing PCC rules to the session management function SMF, including the first round trip transmission delay RTT control information corresponding to the service data flow of the target service, and the SMF performs the transmitted service quality QoS flow based on this information. Control, adjust the uplink and downlink transmission delay requirements to achieve RTT control.

Benefits of technology

It improves the timeliness of the delay control of round-trip transmission of service data flows and meets high-demand service user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095103A_ABST
    Figure CN119095103A_ABST
Patent Text Reader

Abstract

The invention provides a communication method and a communication device. The communication method comprises: a PCF determining first RTT control information corresponding to a service data stream of a target service; the PCF sends a PCC rule to an SMF, the service data stream comprises an uplink service data stream and a downlink service data stream, the PCC rule comprises a first PCC rule and a second PCC rule, the first PCC rule comprises an uplink transmission delay requirement corresponding to the uplink service data stream, and the second PCC rule comprises a downlink transmission delay requirement corresponding to the downlink service data stream. The second PCC rule comprises a downlink transmission time delay requirement corresponding to the downlink service data flow, the first PCC rule and / or the second PCC rule further comprises a time delay monitoring indication, and the time delay monitoring indication is used for monitoring the actual transmission time delay of the uplink service data flow and / or the downlink service data flow; and the PCF adjusts the uplink transmission time delay requirement or the downlink transmission time delay requirement according to the received monitoring result and the first RTT control information.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on January 7, 2022, with application number 202280068525.1 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference in this application. Technical Field

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

[0003] Some services (such as cloud games, artificial intelligence-related interactive services, etc.) have high requirements for the round-trip transmission delay (total round-trip transmission delay) corresponding to the service data flow. In related technologies, the round-trip transmission delay can be controlled through the application layer. For example, when the application server knows that the received uplink data transmission delay is large through the time tag of the application layer, it can send a lower downlink data transmission delay requirement to the network side.

[0004] However, it takes a long time for the control at the application layer to reach the network side for transmission control, resulting in the inability to control the round-trip transmission delay in a timely manner, which may not meet the user experience of certain services. Summary of the invention

[0005] The present application provides a communication method and a communication device to improve the timeliness of round-trip transmission delay control corresponding to a business data flow.

[0006] In a first aspect, a communication method is provided, comprising a policy control function PCF sending a policy control and charging PCC rule to a session management function SMF, wherein the PCC rule includes first round-trip transmission delay RTT control information corresponding to a service data flow of a target service, wherein the PCC rule is used by the SMF to control the quality of service QoS flow transmitting the service data flow according to the first RTT control information.

[0007] In a second aspect, a communication method is provided, including: a policy control function PCF determines a first round-trip transmission delay RTT control information corresponding to a service data flow of a target service; the PCF sends a policy control and charging PCC rule to a session management function SMF, wherein the service data flow includes an uplink service data flow and a downlink service data flow, the PCC rule includes a first PCC rule and a second PCC rule, the first PCC rule includes an uplink transmission delay requirement corresponding to the uplink service data flow, the second PCC rule includes a downlink transmission delay requirement corresponding to the downlink service data flow, the first PCC rule and / or the second PCC rule also include a delay monitoring indication, and the delay monitoring indication is used to monitor the actual transmission delay of the uplink service data flow and / or the downlink service data flow; the PCF adjusts the uplink transmission delay requirement or the downlink transmission delay requirement according to the received monitoring result and the first RTT control information.

[0008] According to a third aspect, a communication method is provided, including: a session management function SMF receives a policy control and charging PCC rule sent by a policy control function PCF, wherein the PCC rule includes a first round-trip transmission delay RTT control information corresponding to a service data flow of a target service; and the SMF controls the quality of service QoS flow of the service data flow according to the first RTT control information.

[0009] In a fourth aspect, a communication method is provided, comprising: an access network device receives control information of a quality of service QoS flow sent by a session management function SMF, wherein the control information of the QoS flow includes control information of a second round-trip transmission delay RTT corresponding to the QoS flow; the access network device schedules wireless resources to perform RTT control on the QoS flow according to the control information of the QoS flow.

[0010] In a fifth aspect, a communication method is provided, comprising: an application function AF sends a request to a policy control function PCF, the request including a round-trip transmission delay RTT requirement corresponding to a service data flow of a target service, wherein the request is used by the PCF to determine a policy control and charging PCC rule corresponding to the service data flow based on the RTT requirement, wherein the PCC rule includes the first RTT control information corresponding to the service data flow.

[0011] In the sixth aspect, a communication device is provided, which is a policy control function PCF entity, and the PCF entity includes: a sending module, used to send policy control and billing PCC rules to the session management function SMF, and the PCC rules include the first round-trip transmission delay RTT control information corresponding to the service data flow of the target service, wherein the PCC rules are used by the SMF to control the service quality QoS flow transmitting the service data flow according to the first RTT control information.

[0012] In the seventh aspect, a communication device is provided, which is a policy control function PCF entity, and the PCF entity includes: a determination module, used to determine the first round-trip transmission delay RTT control information corresponding to the service data flow of the target service; a sending module, used to send policy control and billing PCC rules to the session management function SMF, wherein the service data flow includes an uplink service data flow and a downlink service data flow, and the PCC rules include a first PCC rule and a second PCC rule, the first PCC rule includes an uplink transmission delay requirement corresponding to the uplink service data flow, and the second PCC rule includes a downlink transmission delay requirement corresponding to the downlink service data flow, the first PCC rule and / or the second PCC rule also include a delay monitoring indication, and the delay monitoring indication is used to monitor the actual transmission delay of the uplink service data flow and / or the downlink service data flow; an adjustment module, used to adjust the uplink transmission delay requirement or the downlink transmission delay requirement according to the received monitoring result and the first RTT control information.

[0013] In an eighth aspect, a communication device is provided, which is a session management function SMF entity, and the SMF entity includes: a receiving module for receiving a policy control and charging PCC rule sent by a policy control function PCF, wherein the PCC rule includes a first round-trip transmission delay RTT control information corresponding to a service data flow of a target service; and a control module for controlling the quality of service QoS flow transmitting the service data flow according to the first RTT control information.

[0014] In the ninth aspect, a communication device is provided, which is an access network device, and the access network device includes: a receiving module, used to receive control information of the quality of service QoS flow sent by the session management function SMF, wherein the control information of the QoS flow includes the second round-trip transmission delay RTT control information corresponding to the QoS flow; a scheduling module, used to schedule wireless resources according to the control information of the QoS flow to perform RTT control on the QoS flow.

[0015] In the tenth aspect, a communication device is provided, which is an application function AF entity, and the AF entity includes: a sending module, used to send a request to a policy control function PCF, the request including a round-trip transmission delay RTT requirement corresponding to a service data flow of a target service, wherein the request is used by the PCF to determine a policy control and billing PCC rule corresponding to the service data flow according to the RTT requirement, wherein the PCC rule includes the first RTT control information corresponding to the service data flow.

[0016] In the eleventh aspect, a communication device is provided, comprising 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 call the computer program in the memory so that the terminal device executes part or all of the steps in the method of any one of the first aspect to the fifth aspect.

[0017] In a twelfth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned communication device (PCF entity, SMF entity, access network equipment, AF entity, etc.). In another possible design, the system may also include other devices that interact with the communication device in the solution provided in the embodiment of the present application.

[0018] In the thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a terminal to execute part or all of the steps in the method of any one of the first to fifth aspects above.

[0019] In a fourteenth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a terminal to perform some or all of the steps in the method of any one of the first to fifth aspects above. In some implementations, the computer program product may be a software installation package.

[0020] In the fifteenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement part or all of the steps described in the method of any one of the first to fifth aspects above.

[0021] In an embodiment of the present application, the policy control and charging rules sent by the policy control function to the session management function directly include the first round-trip transmission delay control information corresponding to the service data flow of the target service, so that the network side can directly control the round-trip transmission delay corresponding to the service data flow according to the first round-trip transmission delay control information, thereby improving the timeliness of the control. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 4 is a system architecture diagram of a wireless communication system to which the embodiments of the present application can be applied.

[0023] Figure 2 A schematic diagram of a QoS model provided in an embodiment of the present application.

[0024] Figure 3 A flow chart of a communication method provided in one embodiment of the present application.

[0025] Figure 4 A flowchart of a communication method provided in another embodiment of the present application.

[0026] Figure 5 A flowchart of a communication method provided in yet another embodiment of the present application.

[0027] Figure 6 A flowchart of a communication method provided in yet another embodiment of the present application.

[0028] Figure 7 A flowchart of a communication method provided in yet another embodiment of the present application.

[0029] Figure 8 A flowchart of a communication method provided in yet another embodiment of the present application.

[0030] Fig. 9 A flowchart of a communication method provided in yet another embodiment of the present application.

[0031] Fig.10 A schematic structural block diagram of a communication device provided in one embodiment of the present application.

[0032] Fig.11 A schematic structural block diagram of a communication device provided in another embodiment of the present application.

[0033] Fig.12 A schematic structural block diagram of a communication device provided in yet another embodiment of the present application.

[0034] Fig.13 A schematic structural block diagram of a communication device provided in yet another embodiment of the present application.

[0035] Fig.14 A schematic structural block diagram of a communication device provided in yet another embodiment of the present application.

[0036] Fig.15 A schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0037] Communication system architecture

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

[0039] Figure 1 The wireless communication system 100 to which the embodiment of the present application can be applied is provided. Taking the communication system as a 5G system architecture as an example, the wireless communication system 100 may include a terminal device 110, an access network (AN) device 120, a user plane function (UPF) entity 130, an access and mobility management function (AMF) entity 140, a session management function (SMF) entity 150, a policy control function (PCF) entity 160, an application function (AF) entity 170, and a data network (DN) 180.

[0040] The following is an exemplary description of the functions of each part or functional entity involved in the wireless communication system 100 in the 5G network.

[0041] Terminal device 110: The terminal device may 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 device, user agent or user device. The terminal device in the embodiment of the present application may refer to a device that provides voice and / or data connectivity to a user, and may be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile Internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0042] Access network equipment 120: Access network equipment can be used to provide network access functions for authorized terminal devices in a specific area, and can use transmission channels of different qualities according to the level of the terminal device, business requirements, etc. The access network equipment can manage wireless resources, provide access services for terminal devices, and then complete the forwarding of control signals and data between terminal devices and the core network.

[0043] The access network device may be a device in a wireless network. The access network device may also be referred to as a radio access network (RAN) device or a network device, such as a base station. The access network device in the embodiment of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. Base station can broadly cover various names as follows, or replace with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, auxiliary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station can also refer to a communication module, a modem or a chip used to be arranged in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication device that performs the base station function, a network side device in a 6G network, and a device that performs the base station function in a future communication system. The base station can support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form used by the access network device.

[0044] 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 based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0045] In some deployments, the access network device in the embodiments of the present application may refer to a CU or a DU, or the access network device includes a CU and a DU. The gNB may also include an AAU.

[0046] The access network equipment and the terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on airplanes, balloons, and satellites in the air. The embodiments of the present application do not limit the scenarios in which the access network equipment and the terminal equipment are located.

[0047] UPF entity 130: UPF is a user plane function in the core network, which can be responsible for forwarding and receiving user data (such as service data flow) in the terminal device. Exemplarily, UPF can receive user data from DN and transmit it to the terminal device through the access network device; or, UPF can also receive user data from the terminal device through the access network device and then forward it to DN. The transmission resources and scheduling functions that provide services to terminal devices in UPF are managed and controlled by SMF. In some embodiments, UPF can be divided into intermediate-UPF (I-UPF) and anchor UPF (A-UPF). Among them, I-UPF is connected to the access network, A-UPF is the UPF of the session anchor, and A-UPF can also be called PDU session anchor (PSA).

[0048] AMF entity 140: AMF is a mobility management function in the core network, which can be used to implement other functions of the mobility management entity (MME) except session management, such as lawful interception, or access authorization (or authentication). In some embodiments, in addition to performing mobility management on terminal devices, AMF can also be responsible for forwarding session management related messages between terminal devices and SMF.

[0049] SMF entity 150: SMF is the session management function in the core network, which is mainly responsible for session management, allocation and management of Internet protocol (IP) addresses of 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.

[0050] PCF entity 160: PCF is a policy management function in the core network, which can be responsible for formulating policies related to mobility management, session management, billing, etc. of terminal devices. Specifically, PCF can provide policy rule information, etc. to functional entities of the control plane (such as AMF, SMF entities, etc.) to manage and control the mobility management, session management, etc. of terminal devices.

[0051] AF entity 170: AF mainly supports interaction with the 3rd generation partnership project (3GPP) core network to provide services, for example, influencing data routing decisions, policy control functions, or providing some third-party services to the network side. In other words, AF can be mainly used to convey the requirements of the application side to the network side. In some embodiments, AF can be understood as a third-party server, such as an application server in the Internet, which provides relevant business information, including providing service quality requirement information corresponding to the business to PCF, and sending user plane data information of the business to A-UPF. In some embodiments, AF can also be a service provider (content provider, CP).

[0052] DN 180: 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, or an external network that is not controlled by the operator, such as the Internet, or a proprietary network jointly deployed by operators, such as a network that provides IP multimedia core network subsystem (IMS) services.

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

[0054] Optionally, the wireless communication system 100 may also include other network entities such as a network slice selection function (NSSF) entity, an authentication and authorization service function (AUSF) entity, and a unified data management (UDM) entity, but this is not limited to the embodiments of the present application.

[0055] Figure 1In the wireless communication system 100 shown, various parts or functional entities can communicate with each other through interfaces. For example, the terminal device can connect to the AN through the Uu interface to establish an access layer connection, exchange access layer messages and wireless data transmission; the terminal device can connect to the AMF through the N1 interface to establish a non-access layer (NAS) connection, and exchange NAS messages; the AN can connect to the AMF through the N2 interface to transmit wireless bearer control information from the core network side to the AN; the UPF can transmit data to the AN through the N3 interface, and transmit data to the DN through the N6 interface, etc. The interfaces between other parts or functional entities can be seen in Figure 1 , I will not go into details here.

[0056] It should be understood that Figure 1 The access network equipment, AMF, SMF, UPF and PCF shown are just names, and the names do not limit the equipment itself. In 5G networks and other future networks, the entities corresponding to the access network equipment, AMF, SMF, UPF and PCF may also be other names, and the embodiments of the present application do not specifically limit this.

[0057] It should be understood that all or part of the functions of the communication device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).

[0058] It should be understood that the system architecture described in the embodiments of the present application is to more clearly illustrate the technical solutions of the embodiments of the present application, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that with the evolution of network architecture, the embodiments of the present application can also be applicable to similar technical problems.

[0059] Quality of Service Flow (QoS Flow)

[0060] In order to achieve a higher rate experience and greater bandwidth access capability, as well as lower latency and highly reliable information interaction, some communication systems (such as NR systems) introduce the concept of quality of service flow (QoS flow), which can also be referred to as QoS flow in some embodiments. QoS flow is the finest QoS differentiation granularity in the protocol data unit (PDU) session, that is, the difference between two PDU sessions is that their QoS flows are different.

[0061] A QoS flow identifier (QFI) can be used to identify a QoS flow. For example, a QFI can be used to identify a QoS flow. User plane data with the same QFI in a PDU session will receive the same forwarding treatment (such as the same scheduling, the same admission threshold, etc.).

[0062] In the same PDU session, there can be multiple QoS flows to support different QoS requirements for different types of data transmission. For example, video, voice, and web browsing services may need to use different QoS flows. In other words, a PDU session can have multiple (up to 64) QoS flows, but the QFI of each QoS flow is different (range 0 to 63). In some embodiments, the QFI of two PDU sessions of a terminal device may be repeated.

[0063] In some embodiments, a QoS model can be established based on QoS flows, such as the QoS model of a 5G network. The QoS model of a 5G network can support QoS flows with guaranteed bit rate (GBR) and QoS flows with non-guaranteed bit rate (Non-GBR). In some embodiments, the QoS model of a 5G network can also support reflective QoS.

[0064] In some embodiments, after the terminal device accesses the network (such as a 5G network) through the Uu interface, a QoS flow can be established under the control of the SMF for data transmission. For example, when establishing a PDU session, the SMF can configure corresponding QoS parameters for the UPF, AN, and the terminal device.

[0065] Figure 2 A QoS model is provided for an embodiment of the present application. Figure 2 The classification and marking of user plane data and the rule flow of QoS flow mapping to AN resources are shown. For uplink data transmission, the terminal device can match the data packet according to the QoS rules, and the data packet is transmitted upward from the matched QoS flow and its corresponding AN channel; for downlink data transmission, the UPF can match the data packet according to the packet detection rules (PDR), and the data packet is transmitted downward from the matched QoS flow and its corresponding AN channel. If a data packet does not match any QoS rule (uplink) or PDR (downlink), the data packet may be discarded by the terminal device or UPF.

[0066] After the corresponding QoS flow is established under the control of SMF, SMF can provide the access network device with control information for each QoS flow. Exemplarily, the control information of the QoS flow (also referred to as the configuration information of the QoS flow) may specifically include information such as bit rate requirements, delay requirements, and bit error rate requirements. For each QoS flow, the access network device schedules wireless resources to ensure the QoS requirements of the QoS flow based on the control information of the QoS flow received from the SMF. In some embodiments, a QoS flow can transmit both uplink service data flows (data flows sent by the terminal device to the peer device through a cellular network (such as a 5G network)) and downlink service data flows (data flows sent by the peer device to the terminal device through a cellular network), where the peer device may refer to a peer application server or a peer terminal device.

[0067] It should be noted that the latency requirements for the uplink service data flow and the downlink service data flow in a QoS flow are the same. If the latency requirements for the uplink service data flow and the downlink service data flow of a certain service are different, they can be transmitted through different QoS flows, where the latency here can refer to the data transmission latency between the terminal device and the UPF.

[0068] Specifically, as an example, the process of determining the control information of the QoS flow can be described as follows: the PCF sends the policy control and charging (PCC) rules at the service data flow (SDF) level to the SMF, wherein the PCC rules include QoS requirements, and the SMF can bind different PCC rules according to the QoS requirements, wherein PCC rules with the same QoS requirements can be bound to the same QoS flow, and a QFI is assigned to the bound QoS flow. Then, the SMF sends the bound QoS flow and QFI to the AN, and when the AN receives the downlink service data flow sent by the UPF, it can send it to the terminal device by scheduling resources using a radio bearer with a corresponding service quality according to the received QoS flow and QFI, or when the AN receives the uplink service data flow sent by the terminal device, it can send it to the UPF by scheduling resources using a radio bearer with a corresponding service quality according to the received QoS flow and QFI, thereby ensuring that the service data obtains the corresponding service quality to meet the delay requirement of the service data.

[0069] With the rapid development of mobile communication technology, many new services have emerged, such as AR, VR, cloud games, and artificial intelligence-related interactive services. These new services will pay more attention to the total round-trip delay of a round of interaction between the terminal device and the peer device. In other words, these new services have higher requirements for the round-trip transmission delay (RTT) corresponding to the service data flow, rather than the delay of a separate uplink service data flow or the delay of a downlink service data flow. In the related art, RTT can be controlled through the application layer, for example, RTT can be controlled through the application layer server. Specifically, when the received uplink data transmission delay is large, it can be known through the time tag of the application layer that a lower transmission delay requirement is sent to the network side for the downlink data, so that the downlink data can reach the terminal device faster, thereby achieving a total delay of one round of interaction between the uplink and downlink that does not exceed the RTT requirement. However, the control of the application layer takes a long time to reach the network side for transmission control, resulting in the inability to control RTT in a timely manner, which may not meet the user experience of this type of new service (service with high RTT requirements).

[0070] In order to solve the above problems, the embodiments of the present application provide a communication method and a communication device to improve the timeliness of RTT control corresponding to the service data flow. The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0071] The embodiment of the present application aims to improve the timeliness of control by directly controlling the RTT corresponding to the service data flow on the network side. Based on this, the embodiment of the present application provides two embodiments, wherein the first embodiment aims to control the RTT corresponding to the service data flow through the access network device; the second embodiment aims to control the RTT corresponding to the service data flow through the PCF. The two embodiments are described in detail below.

[0072] It should be noted that the embodiments of the present application are described from the perspective of the interaction between various parts or functional entities, but this does not mean that the implementation scheme of the present application must require the cooperation of various parts or functional entities or must be limited to the listed parts or functional entities to solve the technical problem. It is just that when they are used in combination, better technical effects can be achieved.

[0073] Embodiment 1:

[0074] Figure 3 It is a schematic flow chart of a communication method provided in an embodiment of the present application. Figure 3 The method shown is described from the perspective of the interaction between PCF and SMF, which can be Figure 1 The PCF and SMF shown in . Figure 3 The method shown includes step S310 and step S320.

[0075] In step S310, the PCF sends a PCC rule to the SMF. The PCC rule includes first RTT control information corresponding to the service data flow of the target service.

[0076] In an embodiment of the present application, the target service may refer to a service that has requirements for the RTT of the service data flow. In other words, the target service may refer to a service that places more emphasis on the total round-trip delay of a round of interaction between a terminal device and a peer device. In some embodiments, the target service may be, for example, an AR service, a VR service, a cloud gaming service, or an artificial intelligence-type interactive service. Under these service modes, the user-side terminal device needs to transmit certain service data flows (including both uplink service data flow transmission and downlink service data flow transmission) to the peer terminal device, and the RTT requirements will also be relatively high. It should be noted that the target service of the embodiment of the present application is not limited to the several service types listed above, as long as it is a service that has requirements for the RTT of the service data flow.

[0077] The embodiments of the present application do not specifically limit the data type carried by the service data stream of the target service. In some embodiments, the data carried by the service data stream may be multimedia data, such as video images, sound data, etc. In some embodiments, the data carried by the service data stream may be data collected by the terminal device, such as sensor data on the terminal device, action data detected by the terminal device, etc.

[0078] The present application does not specifically limit the process of generating PCC rules. For example, the PCF can generate PCC rules by itself according to the local configuration of the PCF, operator settings, etc.; or, the PCF can generate PCC rules according to information obtained from the AF.

[0079] In an embodiment of the present application, when a service data flow of a target service needs to be transmitted, the PCF can send the PCC rules corresponding to the service data flow to be transmitted to the SMF, wherein the PCC rules include the first RTT control information corresponding to the service data flow, so that the SMF can bind the received PCC rules to the QoS flow that can provide corresponding QoS guarantees.

[0080] In some embodiments, the first RTT control information includes an RTT requirement corresponding to the service data flow, and the RTT requirement is used to limit the actual RTT of the service data flow to not exceed the RTT requirement. In some embodiments, the RTT requirement can also be understood as a target RTT corresponding to the service data flow.

[0081] As an example, the RTT requirement may be data of a numerical type, for example, the RTT requirement may be a fixed value. For example, if the RTT requirement corresponding to a certain service data flow is 200ms, then the actual RTT of the service data flow cannot exceed 200ms. Alternatively, the RTT requirement may also be a variable value, for example, different RTT requirements may be configured for different service types.

[0082] As another example, the RTT requirement can be indicated by a QoS identifier, which is a scalar that can point to multiple QoS feature values, such as transmission delay requirements, bit error rate, etc. When the QoS identifier mapping table is pre-configured or standardized in the network, the corresponding QoS feature value can be represented by the QoS identifier. Taking the 5G system as an example, the 5G QoS identifier (5G QoS identifier, 5QI) can be used for indication. For example, the 5QI mapping table shown in Table 1 has been standardized in the 5G system, so 5QI = 66 can be understood as a packet delay budget (PDB) of 100ms, or it can be understood as a delay requirement of 100ms. Among them, PDB represents the one-way transmission delay between the terminal device and the UPF.

[0083] Table 1

[0084] 5Q Priority PDB Bit Error Rate 66 20 100ms <![CDATA[10 -2 ]]>

[0085] In some embodiments, the first RTT control information is also used to indicate control of the RTT of the service data flow, for example, it can be used to indicate the network side (such as access network equipment) to control the RTT of the service data flow.

[0086] Optionally, the PCC rule may include not only the first RTT control information corresponding to the service data flow, but also information such as a bit rate requirement and a bit error rate requirement.

[0087] In step S320, the SMF controls the QoS flow of the transmission service data flow according to the first RTT control information.

[0088] Exemplarily, after receiving the PCC rule sent by the PCF, the SMF can determine the QoS flow corresponding to the service data flow according to the first RTT control information in the PCC rule, and bind the service data flow corresponding to the PCC rule to the QoS flow.

[0089] In an embodiment of the present application, the PCC rules sent by the PCF to the SMF directly include the first RTT control information corresponding to the service data flow of the target service, so that the network side can directly control the RTT corresponding to the service data flow according to the first RTT control information, thereby improving the timeliness of the control.

[0090] In some embodiments, the SMF controls the QoS flow of the transmission service data flow according to the first RTT control information, which may refer to: the SMF determines the QoS flow for transmitting the service data flow according to the first RTT control information. In some embodiments, the SMF controls the QoS flow of the transmission service data flow according to the first RTT control information, which may refer to: the SMF sends the control information of the QoS flow to the access network device. In some embodiments, the SMF controls the QoS flow of the transmission service data flow according to the first RTT control information, which may refer to: the SMF determines the QoS flow for transmitting the service data flow according to the first RTT control information, and sends the control information of the QoS flow to the access network device.

[0091] As an implementation method, when the first RTT control information includes RTT requirements, the SMF can directly determine the QoS flow for transmitting the service data flow based on the RTT requirements. As another implementation method, when the first RTT control information is used to indicate the control of the RTT of the service data flow, the SMF can determine the QoS flow for transmitting the service data flow based on the first RTT control information and the one-way transmission delay requirement in the PCC rule, or based on the first RTT control information, the uplink transmission delay requirement in the PCC rule, and the downlink transmission delay requirement. For the specific content of the one-way transmission delay requirement, the uplink transmission delay requirement, and the downlink transmission delay requirement, please refer to the following text and will not be repeated here.

[0092] Figure 4 A schematic flow chart of a communication method provided in another embodiment of the present application. Figure 4 In some embodiments, step S320 may include step S322 and step S324.

[0093] In step S322, the SMF determines the QoS flow for transmitting the service data flow according to the first RTT control information.

[0094] In some embodiments, the QoS flow determined by the SMF can be used only to transmit the service data flow including the target service. In other words, the QoS flow determined by the SMF only transmits the service data flow corresponding to the target service, so as to accurately control the RTT of the service data flow transmitted in the QoS flow.

[0095] In other embodiments, the QoS flow determined by the SMF can be used to transmit a service data flow including a target service and a service data flow having the same first RTT control information as the service data flow including the target service. In other words, the QoS flow determined by the SMF can transmit multiple service data flows having the same RTT requirements, so as to save QoS flow resources.

[0096] As an implementation manner, all service data flows bound to the same QoS flow receive the same data transmission processing and radio resource scheduling manner.

[0097] In some embodiments, after the SMF determines the QoS flow, it can allocate a QFI for the QoS flow. Different QoS flows can be allocated different QFIs.

[0098] In step S324, the SMF sends the control information of the QoS flow to the access network device. The control information of the QoS flow includes the second RTT control information corresponding to the QoS flow, so that the access network device can perform wireless resource scheduling according to the control information of the QoS flow to achieve RTT control of the QoS flow.

[0099] It should be noted that the second RTT control information is determined by the SMF according to the first RTT control information. As an implementation method, the second RTT control information is generated according to the first RTT control information. For example, after receiving the first RTT control information in the PCC rule, the SMF can configure the first RTT control information in the control information of the QoS flow to generate the corresponding second RTT control information, wherein the RTT required in the second RTT control information can be the same as the RTT value required in the second RTT control information.

[0100] In some embodiments, when the first RTT control information includes an RTT requirement, the second RTT control information may include the same RTT requirement. In some embodiments, when the first RTT control information is used to indicate control of the RTT of the service data flow, correspondingly, the second RTT control information may be used to indicate control of the RTT of the QoS flow.

[0101] As mentioned above, the first RTT control information can be used to indicate the control of the RTT of the service data flow. Specifically, in some embodiments, when the first RTT control information is used to indicate the control of the RTT of the service data flow, the PCC rule sent by the PCF to the SMF may also include a first transmission delay requirement. The first transmission delay requirement can be used to indicate the one-way transmission delay requirement corresponding to the service data flow.

[0102] It should be noted that the first transmission delay requirement used to indicate the one-way transmission delay requirement corresponding to the service data flow may refer to: the first transmission delay requirement is used to indicate the uplink transmission delay requirement corresponding to the service data flow; or, the first transmission delay requirement is used to indicate the downlink transmission delay requirement corresponding to the service data flow; or, the first transmission delay requirement is used to indicate the uplink transmission delay requirement and the downlink transmission delay requirement corresponding to the service data flow. At this time, the first transmission delay requirement indicates that the uplink transmission delay requirement corresponding to the service data flow is equal to the downlink transmission delay requirement, and both are equal to the first transmission delay requirement. Exemplarily, when the first transmission delay requirement is 100ms, it can indicate that the uplink transmission delay requirement and the downlink transmission delay requirement of the service data flow are both 100ms. In some embodiments, the first transmission delay requirement and / or the one-way transmission delay requirement can be indicated by a QoS identifier, for example, it can be indicated by a 5QI. For the specific content of the QoS identifier, please refer to the previous text and will not be repeated here.

[0103] Based on this, in some embodiments, the first RTT control information and the first transmission delay requirement can be used to jointly indicate the RTT requirement corresponding to the service data flow, wherein the first RTT control information indicates that the service data flow needs to be RTT controlled, and the specific RTT requirement can be obtained according to the first transmission delay requirement. As described above, the first transmission delay requirement can be used to indicate that the uplink transmission delay requirement corresponding to the service data flow is equal to the downlink transmission delay requirement, and both are equal to the first transmission delay requirement, then the first RTT control information and the first transmission delay requirement can be used to indicate that the RTT requirement corresponding to the service data flow is equal to twice the first transmission delay requirement. As an example, when the first transmission delay requirement is 100ms, when the first RTT control information and the first transmission delay requirement are used to jointly indicate the RTT requirement corresponding to the service data flow, it can be known that the RTT requirement is equal to twice the first transmission delay requirement, that is, the RTT requirement is 200ms. The RTT requirement is used to indicate that the actual RTT corresponding to the service data flow cannot exceed the RTT requirement.

[0104] It should be noted that when the first RTT control information and the first transmission delay requirement are used to jointly indicate the RTT requirement corresponding to the service data flow, priority may be given to satisfying the corresponding RTT requirement, and then the corresponding one-way transmission delay requirement may be considered; or only satisfying the corresponding RTT requirement may be considered without considering the one-way transmission requirement. As an example, when the first transmission delay requirement is 100ms, when the actual uplink transmission delay is 30ms, it may be considered to appropriately slow down the downlink transmission delay, for example, it may be slowed down to 90ms, 100ms, etc., and it may even exceed the preset one-way limit of 100ms, and slow down the downlink transmission delay to 150ms, 170ms, etc.

[0105] Correspondingly, in some embodiments, when the PCC rule includes a first transmission delay requirement, the control information of the QoS flow may also include a second transmission delay requirement, and the second transmission delay requirement may be used to indicate a one-way transmission delay requirement corresponding to the QoS flow. For the specific content of the one-way transmission delay requirement, please refer to the above text and will not be repeated here.

[0106] In some embodiments, the second RTT control information and the second transmission delay requirement can be used to jointly indicate the RTT requirement corresponding to the QoS flow, wherein the second RTT control information indicates that the QoS flow needs to be RTT controlled, and the specific RTT requirement can be obtained based on the second transmission delay requirement. For example, the second transmission delay requirement can be used to indicate that the uplink transmission delay requirement corresponding to the Qos flow is equal to the downlink transmission delay requirement, and both are equal to the second transmission delay requirement, then the second RTT control information and the second transmission delay requirement can be used to indicate that the RTT requirement corresponding to the QoS flow is equal to twice the second transmission delay requirement.

[0107] In some embodiments, the PCC rule may also include description information of the service data flow, which is used to define the service data flow. In some embodiments, the description information of the service data flow may be service data flow filter information. The embodiment of the present application does not limit the specific content of the service data flow filter information. Exemplarily, the data filter information may be a feature of the user plane data packet header. As an example, when the user plane data is IP type data, the data filter information may include source IP address, target IP address, source port number, target port number, etc. As another example, when the user plane data is Ethernet type data, the data filter information may include source MAC address, target MAC address, etc.

[0108] In some embodiments, the service data flow may include an uplink service data flow and a downlink service data flow. Correspondingly, the description information of the service data flow may also include uplink data description information and downlink data description information.

[0109] As an example, the uplink business data flow and the downlink business data flow can be indicated in the same business data flow description information. For example, the description information of the business data flow can be expressed as {uplink business data flow: "source IP address a, source port a, target IP address b, target port b, transmission protocol c", downlink business data flow: "source IP address b, source port b, target IP address a, target port a, transmission protocol c"}.

[0110] As another example, the uplink service data flow and the downlink service data flow may be indicated in different service data flow description information, for example, the uplink service data flow may be indicated in the uplink data description information, and the downlink service data flow may be indicated in the downlink data description information. Exemplarily, the service data flow description information of the uplink service data flow may be expressed as {"source IP address a, source port a, target IP address b, target port b, transmission protocol c"}; the service data flow description information of the downlink service data flow may be expressed as {"source IP address b, source port b, target IP address a, target port a, transmission protocol c"}.

[0111] In some embodiments, when the uplink service data flow and the downlink service data flow are indicated in different service data flow description information, the PCC rule may include a first PCC rule, a second PCC rule and first RTT control information. The first PCC rule may include an uplink transmission delay requirement corresponding to the uplink service data flow, and the second PCC rule may include a downlink transmission delay requirement corresponding to the downlink service data flow.

[0112] In some embodiments, the uplink transmission delay requirement in the first PCC rule may be different from (not equal to) the downlink delay requirement in the second PCC rule. Exemplarily, the first PCC rule may include uplink data description information corresponding to the uplink service data flow and the uplink transmission delay requirement, for example, the uplink transmission delay requirement is 50ms; the second PCC rule includes downlink data description information corresponding to the downlink service data flow and the downlink transmission delay requirement, for example, the downlink transmission delay requirement is 150ms.

[0113] Based on this, in some embodiments, the first RTT control information, the uplink transmission delay requirement, and the downlink transmission delay requirement can be used to jointly indicate the RTT requirement corresponding to the service data flow, wherein the first RTT control information indicates that the service data flow needs to be RTT controlled, and the specific RTT requirement can be obtained according to the uplink transmission delay requirement and the downlink transmission delay requirement. In other words, the first RTT control information, the uplink transmission delay requirement, and the downlink transmission delay requirement can be used to indicate that the RTT requirement corresponding to the service data flow is equal to the sum of the uplink transmission delay requirement and the downlink transmission delay requirement. As an example, when the uplink transmission delay requirement is 50ms and the downlink transmission delay requirement is 150ms, when the first RTT control information, the uplink transmission delay requirement, and the downlink transmission delay requirement are used to jointly indicate the RTT requirement corresponding to the service data flow, it can be known that the RTT requirement is equal to the sum of the uplink transmission delay requirement and the downlink transmission delay requirement, that is, the RTT requirement is 200ms. The RTT requirement is used to indicate that the actual RTT of the service data flow cannot exceed the RTT requirement.

[0114] It should be noted that when the first RTT control information, the uplink transmission delay requirement and the downlink transmission delay requirement are used to jointly indicate the RTT requirement corresponding to the service data flow, priority may be given to satisfying the corresponding RTT requirement, and the uplink transmission delay requirement and / or the downlink transmission delay requirement may be considered again; or only satisfying the corresponding RTT requirement may be considered without considering the uplink transmission delay requirement and / or the downlink transmission delay requirement. As an example, when the uplink transmission delay requirement is 50ms and the downlink transmission delay requirement is 150ms, when the actual uplink transmission delay is 30ms, it may be considered to appropriately slow down the downlink transmission delay, for example, it may be slowed down to 90ms, 150ms, etc., and it may even exceed the preset downlink limit of 150ms and slow down the downlink transmission delay to 160ms, 170ms, etc.

[0115] In some embodiments, the uplink transmission delay requirement and / or the downlink transmission delay requirement may be indicated by a QoS identifier, for example, a 5QI. The specific content of the QoS identifier can be found in the above text and will not be repeated here.

[0116] In some embodiments, when the PCC rule includes a first PCC rule and a second PCC rule, two QoS flows can be determined to transmit an uplink service data flow and a downlink service data flow respectively according to the first PCC rule and the second PCC rule. Taking the two QoS flows as a first QoS flow and a second QoS flow as an example, the first QoS flow can be used to transmit a service data flow (such as an uplink service data flow) corresponding to the first QoS flow, and the second QoS flow can be used to transmit a service data flow (such as a downlink service data flow) corresponding to the second QoS flow.

[0117] Correspondingly, in some embodiments, the second RTT control information, the transmission delay requirement corresponding to the first QoS flow, and the transmission delay requirement corresponding to the second QoS flow can be used to jointly indicate the RTT requirement corresponding to the QoS flow, wherein the second RTT control information indicates that the QoS flow needs to be RTT controlled, and the specific RTT requirement can be obtained according to the transmission delay requirement corresponding to the first QoS flow and the transmission delay requirement corresponding to the second QoS flow. In other words, the second RTT control information, the transmission delay requirement corresponding to the first QoS flow, and the transmission delay requirement corresponding to the second QoS flow can be used to indicate that the RTT requirement corresponding to the QoS flow is equal to the sum of the transmission delay requirement corresponding to the first QoS flow and the transmission delay requirement corresponding to the second QoS flow. As an example, when the transmission delay requirement corresponding to the first QoS flow is 50ms and the transmission delay requirement corresponding to the second QoS flow is 150ms, when the second RTT control information, the transmission delay requirement corresponding to the first QoS flow, and the transmission delay requirement corresponding to the second QoS flow are used to jointly indicate the RTT requirement corresponding to the QoS flow, it can be known that the RTT requirement is equal to the sum of the transmission delay requirement corresponding to the first QoS flow and the transmission delay requirement corresponding to the second QoS flow, that is, the RTT requirement is 200ms. The RTT requirement is used to indicate that the actual RTT of the service data flow cannot exceed the RTT requirement.

[0118] In some embodiments, the PCF may receive a request sent by the AF, and then determine the first RTT control information corresponding to the service data flow according to the request. Figure 4 In some embodiments, before step S310, the communication method may further include step S302 and step S304.

[0119] In step S302, the PCF receives a request from the AF, where the request includes an RTT requirement corresponding to the service data flow.

[0120] In some embodiments, the RTT requirement may be data of a numerical type, for example, the RTT requirement may be a fixed value. For example, the RTT requirement corresponding to the service data flow may be 200 ms. Alternatively, the RTT requirement may also be a variable value.

[0121] In some embodiments, the RTT requirement may be indication information, and the indication information may be used to indicate control of the RTT of the service data flow.

[0122] In some embodiments, the request may also include a first transmission delay requirement, and the first transmission delay requirement may be used to indicate a one-way transmission delay requirement corresponding to the service data flow.

[0123] In some embodiments, the request may also include an uplink transmission delay requirement corresponding to the uplink service data flow, and a downlink transmission delay requirement corresponding to the downlink service data flow.

[0124] In some embodiments, the request may further include description information of the service data flow, for example, may include uplink data description information of the service data flow and downlink data description information of the service data flow.

[0125] In step S304, the PCF determines first RTT control information according to the RTT requirement.

[0126] In some embodiments, when the RTT requirement is a numerical data type, the PCF can directly generate the first RTT control information according to the RTT requirement, and the first RTT control information can include, for example, the RTT requirement, which can be a numerical data type. As an example, if the RTT requirement corresponding to a certain service data flow is 200ms, the PCF can generate the first RTT control information according to the RTT requirement, and the first RTT control information includes the RTT requirement of 200ms.

[0127] In some embodiments, when the RTT requirement in the request is indication information and the request also includes a first transmission delay requirement, the RTT requirement corresponding to the service data flow can be jointly indicated by the RTT requirement and the first transmission delay requirement to be equal to twice the first transmission delay requirement.

[0128] In some embodiments, when the RTT requirement in the request is indication information, and the request also includes an uplink transmission delay requirement corresponding to the uplink business data flow and a downlink transmission delay requirement corresponding to the downlink business data flow, the RTT requirement corresponding to the business data flow can be jointly indicated based on the RTT requirement and the uplink transmission delay requirement and the downlink transmission delay requirement to be equal to the sum of the uplink transmission delay requirement and the downlink transmission delay requirement.

[0129] In some embodiments, the RTT requirement, one-way transmission delay requirement, first transmission delay requirement, uplink transmission delay requirement and downlink transmission delay requirement mentioned in the embodiment can be indicated using QoS identification or service type. For example, different service types correspond to different RTT requirements.

[0130] AF directly provides the RTT requirement corresponding to the service data flow of the target service to the network side, so that the network side can directly control the RTT corresponding to the service data flow according to the RTT requirement, thereby improving the timeliness of the control.

[0131] Embodiment 2:

[0132] Figure 5It is a schematic flow chart of a communication method provided in yet another embodiment of the present application. Figure 5 The method shown is described from the perspective of the interaction between PCF, SMF and AF, which can be Figure 1 The PCF, SMF and AF shown in . Figure 5 The method shown includes steps S510 to S530.

[0133] In step S510, the PCF determines first RTT control information corresponding to the service data flow of the target service.

[0134] In some embodiments, the PCF may determine the first RTT control information according to local configuration, operator settings, etc. In some embodiments, the PCF may determine the first RTT control information according to a request received from the AF.

[0135] In some embodiments, the first RTT control information may include an RTT requirement, which may be data of a numerical type. In some embodiments, the first RTT control information may be used to indicate control of the RTT of the service data flow.

[0136] In step S520, the PCF sends a policy control and charging PCC rule to the SMF. The service data flow includes an uplink service data flow and a downlink service data flow, and the PCC rule includes a first PCC rule and a second PCC rule. The first PCC rule includes an uplink transmission delay requirement corresponding to the uplink service data flow, and the second PCC rule includes a downlink transmission delay requirement corresponding to the downlink service data flow. The first PCC rule and / or the second PCC rule also include a delay monitoring indication, which is used to monitor the actual transmission delay of the uplink service data flow and / or the downlink service data flow.

[0137] In some embodiments, the uplink transmission delay requirement in the first PCC rule is different from (not equal to) the downlink transmission delay requirement in the second PCC rule. Based on this, the first PCC rule and the second PCC rule can be bound to different QoS flows, and the delay monitoring indications in the first PCC rule and the second PCC rule can be used to monitor the actual transmission delay of the respective corresponding QoS flows.

[0138] As an implementation method, after receiving the PCC rules sent by the PCF, the SMF can start delay monitoring, and then after receiving the actual transmission delay of the QoS flow sent by the access network device and / or UPF, forward the monitoring result to the PCF.

[0139] In step S530, the PCF adjusts the uplink transmission delay requirement or the downlink transmission delay requirement according to the received monitoring result and the first RTT control information.

[0140] It should be noted that if the monitoring result received by the PCF is for the uplink business data flow, the PCF can adjust the downlink transmission delay requirement corresponding to the downlink business data flow according to the monitoring result and the first RTT control information; if the monitoring result received by the PCF is for the downlink business data flow, the PCF can adjust the uplink transmission delay requirement corresponding to the uplink business data flow according to the monitoring result and the first RTT control information. Specifically, as an example, for example, if the uplink transmission delay requirement is 50ms and the downlink transmission delay requirement is 150ms, it can be determined that the RTT requirement corresponding to the first RTT control information is 200ms. Based on this, if the monitoring result received by the PCF shows that the actual transmission delay of the uplink business data flow is 30ms, the PCF can dynamically adjust the downlink transmission delay requirement according to the result and the first RTT, for example, the downlink transmission delay requirement can be adjusted from 150ms to 160ms or 170ms, etc.

[0141] In some embodiments, before step S510, the communication method may further include step S505. In step S505, the AF sends a request to the PCF, the request including the RTT requirement corresponding to the service data flow of the target service. Based on this, the PCF may determine the first RTT control information according to the RTT requirement.

[0142] In some embodiments, the RTT requirement may be data of a numerical type. In some embodiments, the RTT requirement may be indication information for indicating that the network side controls the RTT of the service data flow.

[0143] In this embodiment, the PCF may set a delay monitoring indication in the PCC rule so as to directly control the RTT corresponding to the service data flow according to the monitoring result and the first RTT control information, without feeding back to the application layer for RTT control, thereby improving the timeliness of the control.

[0144] The following uses several examples to introduce in detail the technical solution provided in the embodiment of the present application from the perspective of AF, PCF, SMF, and cooperation with the AN side, so as to better understand the implementation process of the solution given in the embodiment of the present application.

[0145] Example 1:

[0146] Figure 6 A flowchart of a communication method provided for yet another embodiment of the present application. Figure 6 The method shown is described from the perspective of the interaction between AF, PCF, SMF and AN. Figure 6 The method shown may include steps S610 to S650.

[0147] In step S610, the AF may provide the PCF located in the core network with service data flow description information of a service data flow, a corresponding first transmission delay requirement, and a corresponding RTT requirement, wherein the RTT requirement is indication information (RTT indication) for indicating RTT control of the service data flow.

[0148] In some embodiments, the service data flow description information may be service data flow filter information. The data filter information may be, for example, characteristics of a user plane data packet header, such as for IP type data, may include IP source address, target IP address, source port number, target port number, etc.; for Ethernet type data, may include source MAC address, target MAC address, etc.

[0149] In this example, the service data flow description information includes the uplink data description information and the downlink data description information of the service data flow, and in this example, it can be considered that the transmission delay of the uplink and downlink data is the same. For example, the service data flow description information is {uplink "source IP address a, source port a, target IP address b, target port b, transmission protocol c", downlink "source IP address b, source port b, target IP address a, target port a, transmission protocol c"}, and the first transmission delay requirement is 100ms, which means that the transmission delay requirement of the uplink service data flow from the terminal device to the UPF is not more than 100ms, and the transmission delay requirement of the downlink service data flow from the UPF to the terminal device is also not more than 100ms. In this example, the request also includes an RTT requirement, which is used to instruct the network side to control the RTT of the service data flow. In other words, the RTT requirement and the first transmission delay requirement can be used to indicate that the total requirement of the transmission delay of the uplink data from the terminal device to the UPF + the transmission delay of the downlink data from the UPF to the terminal device is not more than 100ms+100ms=200ms.

[0150] In step S620, the PCF may determine the PCC rule for the service data flow according to the request of the AF and send the PCC rule to the SMF, wherein the PCC rule includes the service data flow description information of the service data flow, the first transmission delay requirement corresponding to the service data flow, and the first RTT control information. The first transmission delay requirement is used to indicate the single-line transmission delay requirement corresponding to the service data flow, and the first RTT control information is used to indicate the control of the RTT of the service data flow.

[0151] In step S630, the SMF determines the QoS flow for transmitting the service data flow according to the PCC rule. For example, the SMF considers the first RTT control information and transmits the service data flow corresponding to the PCC rule including the first RTT control information through a separate QoS flow, and the QoS flow is only used to transmit the service data flow. Or the SMF considers the first RTT control information and transmits the service data flow through a QoS flow with the same QoS requirements (for example, the same transmission delay) and the first RTT control information, and the QoS flow can also be used to transmit other service data flows with the same QoS requirements and the first RTT control information.

[0152] In step S640, the SMF sends the second transmission delay requirement and the second RTT control information corresponding to the QoS flow to the access network device, and the second RTT control information is used to indicate the control of the RTT of the QoS flow. The second transmission delay requirement is determined according to the first transmission delay requirement, and the second RTT control information is determined according to the first RTT control information.

[0153] In step S650, the access network device performs dynamic resource scheduling for uplink and downlink data according to the second RTT control information. For example, the access network device learns from the information obtained from the SMF that the one-way transmission delay requirement corresponding to the QoS flow is not more than 100ms, and the corresponding RTT requirement is not more than 200ms. In this case, the RTT requirement can be considered during resource scheduling, and resource scheduling can be performed to dynamically adjust the actual transmission delay of the uplink and downlink without exceeding the RTT requirement. For example, when the uplink transmission is faster, the downlink transmission delay can be appropriately slowed down, or when the uplink transmission is slower, the downlink transmission delay can be appropriately accelerated.

[0154] For example, when the actual uplink transmission delay is 30ms, the access network device can appropriately slow down the downlink transmission delay, for example, appropriately slow down the downlink transmission delay to 90ms or 100ms. In some embodiments, the downlink transmission delay can even exceed the preset one-way limit of 100ms and be slowed down to 150ms or 170ms.

[0155] Example 2:

[0156] Figure 7 A flowchart of a communication method provided for yet another embodiment of the present application. Figure 7 The method shown is described from the perspective of the interaction between AF, PCF, SMF and AN. Figure 7 The method shown may include steps S710 to S750.

[0157] Compared with Example 1, in Example 2, the AF can directly provide an RTT requirement corresponding to the service data flow to the PCF of the core network without limiting the unidirectional transmission delay requirement. In this example, the RTT requirement can be in numerical form, such as a fixed value.

[0158] Specifically, in step S710, the AF provides a service data flow description information and corresponding RTT requirement of a service data flow to the PCF located in the core network. For example, the RTT requirement for the service data flow is 200ms, which means that the total requirement of the transmission delay of the uplink service data flow from the terminal device to the UPF + the transmission delay of the downlink service data flow from the UPF to the terminal device is no more than 200ms.

[0159] In step S720, the PCF determines the PCC rule for the service data flow according to the request of the AF, and sends the PCC rule to the SMF, wherein the PCC rule includes the service data flow description information of the service data flow and the first RTT control information corresponding to the service data flow, wherein the first RTT control information includes the RTT requirement.

[0160] In step S730, the SMF determines the QoS flow for transmitting the service data flow according to the PCC rule. For example, the SMF considers the RTT requirement and transmits the service data flow corresponding to the PCC rule including the RTT requirement through a separate QoS flow, and the QoS flow is only used to transmit the service data flow. Alternatively, the SMF considers the RTT requirement and transmits the service data flow through a QoS flow with the same RTT requirement, and the QoS flow can also be used to transmit other service data flows with the same RTT requirement.

[0161] In step S740, the SMF sends the second RTT control information corresponding to the QoS flow to the access network device, where the second RTT control information includes the RTT requirement, wherein the second RTT control information is determined by the SMF according to the first RTT control information.

[0162] In step S750, the access network device dynamically schedules resources for uplink and downlink data according to the RTT requirement. For example, the access network device learns from the information obtained from the SMF that the RTT requirement of the QoS flow is no more than 200ms, then the RTT requirement can be considered during resource scheduling, and resource scheduling can be performed to dynamically adjust the actual transmission delays of the uplink and downlink without exceeding the RTT requirement. For example, when the uplink transmission is faster, the downlink transmission delay can be appropriately slowed down, or when the uplink transmission is slower, the downlink transmission delay can be appropriately accelerated. Exemplarily, when the actual transmission delay of the uplink service data flow is 30ms, the access network device can schedule resources within the range of no more than 170ms for the downlink service data flow transmission, or when the actual transmission delay of the downlink service data flow is 30ms, the resources can be scheduled within the range of no more than 170ms for the uplink service data flow transmission.

[0163] Example 3:

[0164] Figure 8 A flowchart of a communication method provided for yet another embodiment of the present application. Figure 8 The method shown is described from the perspective of the interaction between AF, PCF, SMF and AN. Figure 8 The method shown may include steps S810 to S850.

[0165] Compared with Example 1, in Example 3, the AF may provide the PCF with an uplink transmission delay requirement corresponding to the uplink service data flow and a downlink transmission delay requirement corresponding to the downlink service data flow, respectively.

[0166] Specifically, in step S810, the AF may provide the PCF located in the core network with a service data flow description information of an uplink service data flow and the corresponding uplink transmission delay requirement, and a service data flow description information of a downlink service data flow and the corresponding downlink transmission delay requirement, and the RTT requirement is used to control the RTT of the two service data flows. As an example, the service data flow description information of the uplink service data flow is "source IP address a, source port a, target IP address b, target port b, transmission protocol c", and the uplink transmission delay requirement is 50ms; the service data flow description information of the downlink service data flow is "source IP address b, source port b, target IP address a, target port a, transmission protocol c", and the downlink transmission delay requirement is 150ms; the RTT requirement may be used to indicate that the total transmission delay requirement of the uplink service data flow and the downlink service data flow is not more than 50ms+150ms=200ms.

[0167] In step S820, the PCF determines the PCC rule for the service data flow according to the request of the AF, and sends the PCC rule to the SMF. The PCC rule may include a first PCC rule, a second PCC rule and a first RTT control information. The first PCC rule may include the service data flow description information of the uplink service data flow and the transmission delay requirement of the uplink service data flow, the second PCC rule may include the service data flow description information of the downlink service data flow and the transmission delay requirement of the downlink service data flow, and the first RTT control information is used to indicate the control of the RTT of the service data flow, which is determined according to the RTT requirement, and is used to indicate the RTT control of the service data flows corresponding to the two PCC rules. In other words, the PCF can determine different PCC rules for the uplink service data flow and the downlink service data flow.

[0168] In step S830, the SMF determines the QoS flows for transmitting the uplink service data flow and the downlink service data flow respectively. For example, according to the difference in transmission delay in the first PCC rule and the second PCC rule, the two service data flows are bound to the two QoS flows. Optionally, the SMF can also determine, according to the first RTT control information, that each QoS flow is only used to transmit one service data flow, that is, the QoS flow is not shared with other service data flows.

[0169] In step S840, the SMF sends the transmission delay requirement and the second RTT control information of each QoS flow to the access network device, wherein the second RTT control information is determined by the SMF based on the first RTT control information, and the second RTT control information is used to indicate the control of the RTT of the QoS flow, and is used to indicate the access network device to control the round-trip transmission delay of the two QoS flows.

[0170] In step S850, the access network device dynamically schedules resources for the data of the two QoS flows according to the second RTT control information. For example, the access network device learns from the information obtained from the SMF that the transmission delay requirements of the two QoS flows are no more than 50ms and no more than 150ms, respectively, and the RTT requirements of the two QoS flows are no more than 200ms. In this case, the RTT requirements can be considered during resource scheduling, and resource scheduling can be performed without exceeding the RTT requirements, so as to dynamically adjust the actual transmission delay of the two QoS flows, for example, when the first QoS flow is transmitted faster, the transmission delay of the second QoS flow can be appropriately slowed down, or when the first QoS flow is transmitted slower, the transmission delay of the second QoS flow can be appropriately accelerated. As an example, when the actual transmission delay of the first QoS flow is 30ms, the second QoS flow can be appropriately slowed down to 140ms. In some embodiments, it even exceeds the preset one-way limit of 150ms, for example, the second QoS flow is slowed down to 160ms.

[0171] Example 4:

[0172] Fig. 9 A flowchart of a communication method provided for yet another embodiment of the present application. Fig. 9 The method shown is described from the perspective of the interaction between AF, PCF, and SMF. Fig. 9 The method shown may include steps S910 to S960.

[0173] In Example 4, the PCF can control the RTT of the service data flow, for example, by setting a delay monitoring indication in the PCC rule. After the SMF reports the monitoring result to the PCF, the PCF can dynamically adjust the transmission delay requirement of the service data flow according to the monitoring result.

[0174] Specifically, in step S910, the AF may provide the PCF located in the core network with service data flow description information of an uplink service data flow and the corresponding uplink transmission delay requirement, and service data flow description information of a downlink service data flow and the corresponding downlink transmission delay requirement. The RTT requirement is used to control the RTT of the two service data flows.

[0175] In step S920, the PCF may set a delay monitoring indication in the PCC rule and send it to the SMF based on the request of the AF. For example, the delay monitoring indication may be set in the first PCC rule and / or the second PCC rule. As an example, the PCF may send the first PCC rule (including the service data flow description information of the uplink service data flow, the uplink transmission delay requirement, and the delay monitoring indication) and the second PCC rule (including the service data flow description information of the downlink service data flow, the downlink transmission delay requirement, and the delay monitoring indication) to the SMF. It should be noted that the delay monitoring indication may also be set only in the first PCC rule or only in the second PCC rule, and the present application does not limit this.

[0176] In step S930, the SMF determines the QoS flow for transmitting the service data flow according to the PCC rule, and starts delay monitoring for the uplink service data flow and / or the downlink service data flow. For example, according to different transmission delays, two service data flows can be bound to two QoS flows, and each QoS flow is only used to transmit one service data flow, that is, the QoS flow is not shared with other service data flows.

[0177] In step S940, after the SMF starts monitoring the actual transmission delay of the QoS flow, the monitoring result may be reported to the PCF.

[0178] In step S950, the PCF adjusts the uplink transmission delay requirement or the downlink transmission delay requirement according to the report obtained from the SMF and the first RTT control information (for example, dynamically adjusts the uplink transmission delay requirement in the first PCC rule, or the downlink transmission delay requirement in the second PCC rule). For example, when the uplink service data stream is transmitted faster, the transmission delay requirement in the second PCC rule can be appropriately increased, or when the uplink service data stream is transmitted slower, the transmission delay requirement in the second PCC rule can be appropriately reduced. As an example, when the actual uplink transmission delay is 30ms, the PCF can modify the transmission delay requirement in the second PCC rule to 170ms.

[0179] In step S960, the PCF sends the adjusted uplink transmission delay requirement or downlink transmission delay requirement to the SMF.

[0180] It should be noted that the examples provided in the embodiments of the present application are only for facilitating the understanding of the solutions of the present application and should not be used to limit the present application. The present application can also reasonably re-combine the solutions described above, and the re-combined solutions should also be included in the protection scope of the present application.

[0181] Combination of the above Figures 1 to 9 , describes the method embodiment of the present application in detail, and the following is combined with Figures 10 to 15 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0182] Fig.10 It is a schematic structural block diagram of a communication device provided in one embodiment of the present application. Fig.10 The communication device 1000 shown may refer to a PCF entity, and the communication device 1000 may include a sending module 1010 .

[0183] The sending module 1010 can be used to send policy control and billing PCC rules to the session management function SMF, where the PCC rules include the first round-trip transmission delay RTT control information corresponding to the service data flow of the target service, wherein the PCC rules are used by the SMF to control the service quality QoS flow of the transmission service data flow according to the first RTT control information.

[0184] Optionally, the first RTT control information is also used to indicate control of the RTT of the service data flow.

[0185] Optionally, the PCC rule further includes a first transmission delay requirement, where the first transmission delay requirement is used to indicate a one-way transmission delay requirement corresponding to the service data flow.

[0186] Optionally, the first RTT control information and the first transmission delay requirement are used to indicate that the RTT requirement corresponding to the service data flow is equal to twice the first transmission delay requirement.

[0187] Optionally, the service data flow includes an uplink service data flow and a downlink service data flow, the PCC rule includes a first PCC rule, a second PCC rule and first RTT control information, the first PCC rule includes an uplink transmission delay requirement corresponding to the uplink service data flow, and the second PCC rule includes a downlink transmission delay requirement corresponding to the downlink service data flow.

[0188] Optionally, the uplink transmission delay requirement is different from the downlink transmission delay requirement.

[0189] Optionally, the QoS flow includes a first QoS flow and a second QoS flow, the first QoS flow is used to transmit an uplink service data flow, and the second QoS flow is used to transmit a downlink service data flow.

[0190] Optionally, the QoS flow includes a first QoS flow and a second QoS flow, the first QoS flow is used to transmit an uplink service data flow, and the second QoS flow is used to transmit a downlink service data flow.

[0191] Optionally, the first RTT control information includes an RTT requirement corresponding to the service data flow.

[0192] Optionally, the actual RTT of the service data flow does not exceed the RTT requirement.

[0193] Optionally, the PCF entity further includes a receiving module 1020 and a determining module 1030. The receiving module 1020 may be configured to receive a request from an application function AF, the request including an RTT requirement corresponding to a service data flow. The determining module 1030 may be configured to determine first RTT control information according to the RTT requirement.

[0194] Optionally, the QoS flow is used only to transmit service data flows including target services.

[0195] Optionally, the QoS flow is used to transmit the service data flow and a service data flow having the same first RTT control information as the service data flow including the target service.

[0196] Optionally, the PCC rule also includes description information of the service data flow.

[0197] Optionally, the description information includes uplink data description information of the service data flow and downlink data description information of the service data flow.

[0198] Optionally, the RTT requirement and / or one-way transmission delay requirement corresponding to the service data flow is indicated by a QoS identifier.

[0199] Fig.11 It is a schematic structural block diagram of a communication device provided in another embodiment of the present application. Fig.11 The communication device 1100 shown may refer to a PCF entity, and the communication device 1100 may include a determination module 1110 , a sending module 1120 , and an adjustment module 1130 .

[0200] The determination module 1110 may be configured to determine first round-trip transmission delay RTT control information corresponding to a service data flow of a target service.

[0201] The sending module 1120 can be used to send policy control and charging PCC rules to the session management function SMF, wherein the service data flow includes an uplink service data flow and a downlink service data flow, the PCC rules include a first PCC rule and a second PCC rule, the first PCC rule includes an uplink transmission delay requirement corresponding to the uplink service data flow, the second PCC rule includes a downlink transmission delay requirement corresponding to the downlink service data flow, the first PCC rule and / or the second PCC rule also includes a delay monitoring indication, and the delay monitoring indication is used to monitor the actual transmission delay of the uplink service data flow and / or the downlink service data flow.

[0202] The adjustment module 1130 may be configured to adjust an uplink transmission delay requirement or a downlink transmission delay requirement according to the received monitoring result and the first RTT control information.

[0203] Optionally, the adjustment module 1130 is further used to: if the monitoring result is for the uplink business data flow, adjust the downlink transmission delay requirement according to the monitoring result and the first RTT control information; if the monitoring result is for the downlink business data flow, adjust the uplink transmission delay requirement according to the monitoring result and the first RTT control information.

[0204] Optionally, the uplink transmission delay requirement is different from the downlink transmission delay requirement.

[0205] Optionally, the communication device 1100 also includes a receiving module, which can be used to receive a request for an application function AF, where the request includes an RTT requirement corresponding to a service data flow; the determination module 1110 can be further used to: determine first RTT control information according to the RTT requirement.

[0206] Optionally, the first RTT control information is also used to indicate control of the RTT of the service data flow.

[0207] Optionally, the PCC rule also includes description information of the service data flow.

[0208] Optionally, the description information includes uplink data description information of the service data flow and downlink data description information of the service data flow.

[0209] Fig.12 It is a schematic structural block diagram of a communication device provided in yet another embodiment of the present application. Fig.12 The communication device 1200 shown may refer to an SMF entity, and the communication device 1200 may include a receiving module 1210 and a control module 1220 .

[0210] The receiving module 1210 may be configured to receive a policy control and charging PCC rule sent by a policy control function PCF, where the PCC rule includes first round-trip transmission delay RTT control information corresponding to a service data flow of a target service.

[0211] The control module 1220 may be configured to control the quality of service QoS flow of the transmission service data flow according to the first RTT control information.

[0212] Optionally, the first RTT control information is also used to indicate control of the RTT of the service data flow.

[0213] Optionally, the PCC rule further includes a first transmission delay requirement, where the first transmission delay requirement is used to indicate a one-way transmission delay requirement corresponding to the service data flow.

[0214] Optionally, the first RTT control information and the first transmission delay requirement are used to indicate that the RTT requirement corresponding to the service data flow is equal to twice the first transmission delay requirement.

[0215] Optionally, the service data flow includes an uplink service data flow and a downlink service data flow, the PCC rule includes a first PCC rule, a second PCC rule and first RTT control information, the first PCC rule includes an uplink transmission delay requirement corresponding to the uplink service data flow, and the second PCC rule includes a downlink transmission delay requirement corresponding to the downlink service data flow.

[0216] Optionally, the uplink transmission delay requirement is different from the downlink transmission delay requirement.

[0217] Optionally, the QoS flow includes a first QoS flow and a second QoS flow, the first QoS flow is used to transmit an uplink service data flow, and the second QoS flow is used to transmit a downlink service data flow.

[0218] Optionally, the first RTT control information, the uplink transmission delay requirement and the downlink transmission delay requirement are used to indicate that the RTT requirement corresponding to the service data flow is equal to the sum of the uplink transmission delay requirement and the downlink transmission delay requirement.

[0219] Optionally, the first RTT control information includes an RTT requirement corresponding to the service data flow.

[0220] Optionally, the actual RTT of the service data flow does not exceed the RTT requirement.

[0221] Optionally, the control module 1220 is further used to: determine a QoS flow according to the first RTT control information, and the QoS flow is only used to transmit the service data flow.

[0222] Optionally, the control module 1220 is further used to: determine a QoS flow according to the first RTT control information, the QoS flow being used to transmit a service data flow including a target service and a service data flow having the same first RTT control information as the service data flow including the target service.

[0223] Optionally, the control module 1220 is further used to: send control information of the QoS flow to the access network device, where the control information of the QoS flow includes second RTT control information corresponding to the QoS flow.

[0224] Optionally, the second RTT control information is determined by the SMF according to the first RTT control information.

[0225] Optionally, the PCC rule also includes description information of the service data flow.

[0226] Optionally, the description information includes uplink data description information of the service data flow and downlink data description information of the service data flow.

[0227] Optionally, the RTT requirement and / or one-way transmission delay requirement corresponding to the service data flow is indicated by a QoS identifier.

[0228] Fig.13 It is a schematic structural block diagram of a communication device provided in yet another embodiment of the present application. Fig.13 The communication device 1300 shown may refer to an access network device, and the communication device 1300 may include a receiving module 1310 and a scheduling module 1320 .

[0229] The receiving module 1310 may be configured to receive control information of a quality of service QoS flow sent by a session management function SMF, wherein the control information of the QoS flow includes second round-trip transmission delay RTT control information corresponding to the QoS flow.

[0230] The scheduling module 1320 may be configured to schedule wireless resources according to the control information of the QoS flow to perform RTT control on the QoS flow.

[0231] Optionally, the second RTT control information is also used to indicate control of the RTT of the QoS flow.

[0232] Optionally, the control information of the QoS flow also includes a second transmission delay requirement, where the second transmission delay requirement is used to indicate a one-way transmission delay requirement corresponding to the QoS flow.

[0233] Optionally, the second RTT control information and the second transmission delay requirement are used to indicate that the RTT requirement corresponding to the QoS flow is equal to twice the second transmission delay requirement.

[0234] Optionally, the QoS flow includes a first QoS flow and a second QoS flow, the control information of the QoS flow includes control information of the first QoS flow, control information of the second QoS flow and second RTT control information, the control information of the first QoS flow includes the transmission delay requirement corresponding to the first QoS flow, and the control information of the second QoS flow includes the transmission delay requirement corresponding to the second QoS flow.

[0235] Optionally, a transmission delay requirement corresponding to the first QoS flow is different from a transmission delay requirement corresponding to the second QoS flow.

[0236] Optionally, the second RTT control information, the transmission delay requirement corresponding to the first QoS flow, and the transmission delay requirement corresponding to the second QoS flow are used to indicate that the RTT requirement corresponding to the QoS flow is equal to the sum of the transmission delay requirement corresponding to the first QoS flow and the transmission delay requirement corresponding to the second QoS flow.

[0237] Optionally, the second RTT control information includes an RTT requirement corresponding to the QoS flow.

[0238] Optionally, the actual RTT of the QoS flow does not exceed the RTT requirement.

[0239] Optionally, the RTT requirement and / or one-way transmission delay requirement corresponding to the QoS flow is indicated by a QoS identifier.

[0240] Fig.14 It is a schematic structural block diagram of a communication device provided in yet another embodiment of the present application. Fig.14 The communication device 1400 shown may refer to an AF entity, and the communication device 1400 may include a sending module 1410 .

[0241] The sending module 1410 can be used to send a request to the policy control function PCF, which includes the round-trip transmission delay RTT requirement corresponding to the service data flow of the target service, wherein the request is used by the PCF to determine the policy control and billing PCC rules corresponding to the service data flow based on the RTT requirement, wherein the PCC rules include the first RTT control information corresponding to the service data flow.

[0242] Optionally, the first RTT control information is also used to indicate control of the RTT of the service data flow.

[0243] Optionally, the request also includes a first transmission delay requirement, where the first transmission delay requirement is used to indicate a one-way transmission delay requirement corresponding to the service data flow.

[0244] Optionally, the first RTT control information and the first transmission delay requirement are used to indicate that the RTT requirement corresponding to the service data flow is equal to twice the first transmission delay requirement.

[0245] Optionally, the service data flow includes an uplink service data flow and a downlink service data flow, and the request includes an uplink transmission delay requirement corresponding to the uplink service data flow and a downlink transmission delay requirement corresponding to the downlink service data flow, respectively.

[0246] Optionally, the PCC rule includes a first PCC rule, a second PCC rule and first RTT control information, the first PCC rule includes an uplink transmission delay requirement corresponding to an uplink service data flow, and the second PCC rule includes a downlink transmission delay requirement corresponding to a downlink service data flow.

[0247] Optionally, the uplink transmission delay requirement is different from the downlink transmission delay requirement.

[0248] Optionally, the first RTT control information, the uplink transmission delay requirement and the downlink transmission delay requirement are used to indicate that the RTT requirement corresponding to the service data flow is equal to the sum of the uplink transmission delay requirement and the downlink transmission delay requirement.

[0249] Optionally, the first RTT control information includes an RTT requirement corresponding to the service data flow.

[0250] Optionally, the actual RTT of the service data flow does not exceed the RTT requirement.

[0251] Optionally, the request further includes description information of the service data flow, and the PCC rule includes description information of the service data flow.

[0252] Optionally, the description information includes uplink data description information of the service data flow and downlink data description information of the service data flow.

[0253] Optionally, the RTT requirement and / or one-way transmission delay requirement corresponding to the service data flow is indicated by a QoS identifier or a service type.

[0254] Fig.15 It is a schematic structural diagram of a communication device according to an embodiment of the present application. Fig.15 The dotted line in the figure indicates that the unit or module is optional. The device 1500 can be used to implement the method described in the above method embodiment. The device 1500 can be a chip or a communication device (such as a PCF entity, an SMF entity, an access network device, an AF entity, etc.).

[0255] The device 1500 may include one or more processors 1510. The processor 1510 may support the device 1500 to implement the method described in the method embodiment above. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0256] The apparatus 1500 may further include one or more memories 1520. The memory 1520 stores a program, which can be executed by the processor 1510, so that the processor 1510 executes the method described in the above method embodiment. The memory 1520 may be independent of the processor 1510 or integrated in the processor 1510.

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

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

[0259] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or network device provided in the embodiment of the present application, and the program enables the computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0260] The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the terminal or network device in each embodiment of the present application.

[0261] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions.

[0262] In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0263] In the embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0264] In the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship of indication and being indicated, configuration and being configured, etc.

[0265] In the embodiments of the present application, "pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0266] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0267] In the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

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

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

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

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

[0272] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0273] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: The policy control function PCF determines the first round-trip transmission delay RTT control information corresponding to the service data flow of the target service; The PCF sends a policy control and charging PCC rule to a session management function SMF, wherein the service data flow includes an uplink service data flow and a downlink service data flow, the PCC rule includes a first PCC rule and a second PCC rule, the first PCC rule includes an uplink transmission delay requirement corresponding to the uplink service data flow, the second PCC rule includes a downlink transmission delay requirement corresponding to the downlink service data flow, the first PCC rule and / or the second PCC rule further includes a delay monitoring indication, and the delay monitoring indication is used to monitor an actual transmission delay of the uplink service data flow and / or the downlink service data flow; The PCF adjusts the uplink transmission delay requirement or the downlink transmission delay requirement according to the received monitoring result and the first RTT control information.

2. The method according to claim 1, characterized in that: The uplink transmission delay requirement and / or the downlink transmission delay requirement is indicated by a 5G service quality identifier 5QI.

3. The method according to claim 1 or 2, characterized in that: The PCC rule is generated by the PCF.

4. The method according to claim 1 or 2, characterized in that: The uplink transmission delay requirement is different from the downlink transmission delay requirement.

5. The method according to claim 4, characterized in that The uplink transmission delay requirement is different from the downlink transmission delay requirement including: The packet delay budget PDB indicated by the 5QI indicating the uplink transmission delay requirement is different from the PDB indicated by the 5QI indicating the downlink transmission delay requirement.

6. The method according to claim 1 or 2, characterized in that: The method further comprises: The PCF receives a request from an application function AF, where the request includes an RTT requirement corresponding to the service data flow; The PCF determines first RTT control information corresponding to the service data flow of the target service, including: The PCF determines the first RTT control information according to the RTT requirement.

7. The method according to claim 6, characterized in that The RTT requirement is indication information, the request also includes a first transmission delay requirement, and the RTT requirement corresponding to the service data flow determined according to the RTT requirement and the first transmission delay requirement is equal to twice the first transmission delay requirement.

8. The method according to claim 7, characterized in that The first transmission delay requirement is used to indicate a one-way transmission delay requirement corresponding to the service data flow.

9. The method according to claim 6, characterized in that The RTT requirement is indication information, and the request also includes an uplink transmission delay requirement corresponding to the uplink business data flow and a downlink transmission delay requirement corresponding to the downlink business data flow, and the RTT requirement corresponding to the business data flow determined according to the RTT requirement, the uplink transmission delay requirement and the downlink transmission delay requirement is equal to the sum of the uplink transmission delay requirement and the downlink transmission delay requirement.

10. The method according to claim 6, characterized in that The first RTT control information includes the RTT requirement corresponding to the service data flow.

11. The method according to claim 1 or 2, characterized in that: The PCF adjusts the uplink transmission delay requirement or the downlink transmission delay requirement according to the received monitoring result and the first RTT control information, including: If the monitoring result is for the uplink service data flow, adjusting the downlink transmission delay requirement according to the monitoring result and the first RTT control information; If the monitoring result is for the downlink service data flow, the uplink transmission delay requirement is adjusted according to the monitoring result and the first RTT control information.

12. A communication method, characterized in that: include: The session management function SMF receives the policy control and charging PCC rules sent by the policy control function PCF, wherein the PCC rules include a first PCC rule and a second PCC rule, the first PCC rule includes an uplink transmission delay requirement corresponding to an uplink service data flow, the second PCC rule includes a downlink transmission delay requirement corresponding to a downlink service data flow, the first PCC rule and / or the second PCC rule also includes a delay monitoring indication, and the delay monitoring indication is used to monitor the actual transmission delay of the uplink service data flow and / or the downlink service data flow.

13. The method according to claim 12, characterized in that The uplink transmission delay requirement is different from the downlink transmission delay requirement.

14. A communication device, characterized in that: The communication device is a policy control function PCF entity, and the PCF entity includes: A determination module, used to determine first round-trip transmission delay RTT control information corresponding to a service data flow of a target service; A sending module, used to send a policy control and charging PCC rule to a session management function SMF, wherein the service data flow includes an uplink service data flow and a downlink service data flow, the PCC rule includes a first PCC rule and a second PCC rule, the first PCC rule includes an uplink transmission delay requirement corresponding to the uplink service data flow, the second PCC rule includes a downlink transmission delay requirement corresponding to the downlink service data flow, the first PCC rule and / or the second PCC rule also includes a delay monitoring indication, and the delay monitoring indication is used to monitor the actual transmission delay of the uplink service data flow and / or the downlink service data flow; An adjustment module is used to adjust the uplink transmission delay requirement or the downlink transmission delay requirement according to the received monitoring result and the first RTT control information.

15. A communication device, characterized in that: The communication device is a session management function SMF entity, and the SMF entity includes: A receiving module is used to receive a policy control and charging PCC rule sent by a policy control function PCF, wherein the PCC rule includes a first PCC rule and a second PCC rule, the first PCC rule includes an uplink transmission delay requirement corresponding to an uplink service data flow, the second PCC rule includes a downlink transmission delay requirement corresponding to a downlink service data flow, the first PCC rule and / or the second PCC rule also includes a delay monitoring indication, and the delay monitoring indication is used to monitor the actual transmission delay of the uplink service data flow and / or the downlink service data flow.

16. A communication device, characterized in that: The communication device is a policy control function PCF entity, and comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method according to any one of claims 1-11.

17. A communication device, characterized in that: The communication device is a session management function SMF entity, and comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method according to claim 12 or 13.

18. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 11.

19. A chip, characterized in that: The device comprises a processor, which is used to call a program from a memory so that a device equipped with the chip executes the method according to claim 12 or 13.

Citation Information

Patent Citations

  • Communication method and device, computer readable medium and electronic equipment

    CN110062426A

  • Communication method and communication device

    CN110830268A

  • Communication method, device and system

    CN112787827A

  • Apparatus and method for psa-upf relocation in wireless communication system

    WO2021054747A1

  • Data packet delay jitter monitoring method and device

    WO2021204161A1