A data transmission method and apparatus

Abstract

A data transmission method and device, the method comprising: a first function entity sending request information to an access network device, the request information containing description information of first downlink data, the first downlink data being downlink data requested to be transmitted by the first function entity; the access network device determining second downlink data according to the description information of the first downlink data and air interface transmission conditions of the access network device, the second downlink data being a full set or a subset of the first downlink data; and the access network device sending response information to the first function entity, the response information containing authorization information of the second downlink data. The method and device of the present application can make the transmission of downlink data match the air interface transmission of the access network device, and solve problems such as air interface congestion of downlink data.

Description

Technical Field

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

[0002] In wireless communication systems, functional network elements or entities in the core network can send downlink data to access network equipment, which then forwards the downlink data to the corresponding terminals. How to match the transmission of downlink data with the air interface transmission of access network equipment, and avoid air interface congestion for downlink data, is a research direction. Summary of the Invention

[0003] In a first aspect, a data transmission method is provided, which is applied to an access network device, comprising: receiving request information from a first functional entity, the request information including description information of first downlink data, the first downlink data being downlink data requested to be transmitted by the first functional entity; determining second downlink data based on the description information of the first downlink data and the air interface transmission status of the access network device, the second downlink data being the entire set or a subset of the first downlink data;

[0004] Send a response message to the first functional entity, the response message containing authorization information for the second downlink data.

[0005] With the above design, before transmitting the first downlink data to the access network device, the first functional entity needs to send a request message to the access network device. The access network device can flexibly and dynamically control the transmission of the first downlink data based on the air interface transmission situation. For example, when air interface transmission is relatively idle, the access network device can authorize the transmission of the entire first downlink data, meaning it allows the first functional entity to transmit all of the requested first downlink data; or, as described, the access network device authorizes or allows the first functional entity to transmit the entire first downlink data requested in the request message. In this case, the second downlink data authorized by the access network device is the complete set of the first downlink data. Alternatively, when air interface transmission is relatively congested, the access network device can authorize a portion of the first downlink data, meaning it allows the first functional entity to transmit a portion of the requested first downlink data; or, as described, the access network device authorizes or allows the first functional entity to transmit a portion of the requested first downlink data in the request message. In this case, the second downlink data authorized by the access network device is a subset of the first downlink data. In this embodiment, the first functional entity transmits downlink data to the access network device according to the authorization or permission of the access network device. The transmission of downlink data by the access network device is matched with the air interface status of the access network device, so as to avoid congestion or packet loss caused by sudden downlink data, and improve the efficiency and robustness of system data transmission.

[0006] In one implementation, the description information of the first downlink data includes at least one of the following: the identifier of the first downlink data, or the size of the first downlink data. Further, the description information of the first downlink data also includes at least one of the following: the transmission period of the first downlink data, or the transmission time of the first downlink data.

[0007] In one implementation, the authorization information of the second downlink data includes at least one of the following: the identifier of the second downlink data, or the size of the second downlink data. Further, the authorization information of the second downlink data also includes at least one of the following: the transmission time of the second downlink data, or the transmission period of the second downlink data.

[0008] In one implementation, receiving request information from a first functional entity includes: receiving request information from the first functional entity through a second functional entity; sending response information to the first functional entity includes: sending the response information to the first functional entity through the second functional entity.

[0009] The above design allows for the transmission of request and response information via the control plane. For example, taking request information as an example, the specific control plane transmission path could include: first functional entity → second functional entity → access control function → access network device. Alternatively, request and response information can be transmitted via the user plane. For example, taking request information as an example, the specific user plane transmission path could include: first functional entity → access network device. Since the transmission reliability of the control plane is generally higher than that of the user plane, transmitting request and response information via the control plane can improve the transmission reliability of both information.

[0010] In one implementation, the identifiers of the first downlink data and the second downlink data include an identifier for a Quality of Service (QoS) flow or an identifier for an Internet Protocol (IP) flow.

[0011] In one implementation, the request information further includes at least one of the following: a session identifier between the terminal and the network, or a connection identifier between the first functional entity and the access network.

[0012] In a second aspect, a data transmission method is provided, the beneficial effects of which can be found in the description of the first aspect. Applied to a first functional entity, the method includes: sending request information to an access network device, the request information including description information of first downlink data, the first downlink data being downlink data requested for transmission by the first functional entity; and receiving response information from the access network device, the response information including authorization information of second downlink data, the second downlink data being the entire set or a subset of the first downlink data.

[0013] In one implementation, the description information of the first downlink data includes at least one of the following: the identifier of the first downlink data, or the size of the first downlink data. Further, the description information of the first downlink data also includes at least one of the following: the transmission period of the first downlink data, or the transmission time of the first downlink data.

[0014] In one implementation, the authorization information of the second downlink data includes at least one of the following: the identifier of the second downlink data, or the size of the second downlink data. Further, the authorization information of the second downlink data also includes at least one of the following: the transmission time of the second downlink data, or the transmission period of the second downlink data.

[0015] In one implementation, sending the request information to the access network device includes: sending the request information to the access network device through a second functional entity; receiving the response information from the access network device includes: receiving the response information from the access network device through the second functional entity.

[0016] In one implementation, the identifiers of the first downlink data and the second downlink data include an identifier for a Quality of Service (QoS) flow or an identifier for an Internet Protocol (IP) flow.

[0017] In one implementation, the request information further includes at least one of the following: a session identifier between the terminal and the network, or a connection identifier between the first functional entity and the access network.

[0018] Thirdly, a data transmission method is provided, the beneficial effects of which are described in the first aspect. This method is applied to a first functional entity and an access network device, comprising: the first functional entity sending request information to the access network device, the request information including description information of first downlink data, the first downlink data being downlink data requested for transmission by the first functional entity; the access network device determining second downlink data based on the description information of the first downlink data and the air interface transmission status of the access network device, the second downlink data being the entire set or a subset of the first downlink data; and the access network device sending response information to the first functional entity, the response information including authorization information for the second downlink data.

[0019] In one implementation, the description information of the first downlink data includes at least one of the following: the identifier of the first downlink data, or the size of the first downlink data. Further, the description information of the first downlink data also includes at least one of the following: the transmission period of the first downlink data, or the transmission time of the first downlink data.

[0020] In one implementation, the authorization information of the second downlink data includes at least one of the following: the identifier of the second downlink data, or the size of the second downlink data. Further, the authorization information of the second downlink data also includes at least one of the following: the transmission time of the second downlink data, or the transmission period of the second downlink data.

[0021] In one implementation, the first functional entity sends request information to the access network device, including: the first functional entity sending the request information to the access network device through a second functional entity; the access network device sends response information to the first functional entity, including: the access network device sending the response information to the first functional entity through the second functional entity.

[0022] In one implementation, the identifiers of the first downlink data and the second downlink data include an identifier for a Quality of Service (QoS) flow or an identifier for an Internet Protocol (IP) flow.

[0023] In one implementation, the request information further includes at least one of the following: a session identifier between the terminal and the network, or a connection identifier between the first functional entity and the access network.

[0024] In one implementation, the method further includes: a first functional entity sending second downlink data to an access network device; and the access network device sending the second downlink data to a corresponding terminal.

[0025] Fourthly, a data transmission method is provided, applied to an access network device, comprising: sending a request message to a first functional entity, the request message including description information of third downlink data, the third downlink data being downlink data requested for transmission by the access network device; and receiving fourth downlink data from the first functional entity, the fourth downlink data being a subset or the entirety of the third downlink data, the fourth downlink data being downlink data permitted to be transmitted by the first functional entity.

[0026] Through the above design, the access network device can reverse schedule the downlink data transmission of the first NCCF according to the transmission status of the air interface, thereby avoiding downlink data congestion on the access network device side, improving downlink data transmission efficiency and system robustness, and enhancing the user experience.

[0027] In one implementation, before receiving the fourth downlink data from the first functional entity, the method further includes: receiving response information from the first functional entity, the response information containing authorization information for the fourth downlink data.

[0028] In one implementation, the description information of the third downlink data includes at least one of the following: the identifier of the third downlink data, or the size of the third downlink data. Further, the description information of the third downlink data also includes at least one of the following: the transmission period of the third downlink data, or the transmission time of the third downlink data.

[0029] In one implementation, the authorization information of the fourth downlink data includes at least one of the following: the identifier of the fourth downlink data, or the size of the fourth downlink data. Further, the authorization information of the fourth downlink data also includes at least one of the following: the transmission time of the fourth downlink data, or the transmission period of the fourth downlink data.

[0030] In one implementation, sending the request information to the first functional entity includes: sending the request information to the first functional entity through a second functional entity. Receiving the response information from the first functional entity includes: receiving the response information from the first functional entity through the second functional entity.

[0031] In one implementation, the identifiers of the third downlink data and the fourth downlink data include an identifier for a Quality of Service (QoS) flow or an identifier for an Internet Protocol (IP) flow.

[0032] In one implementation, the method further includes sending the fourth downlink data to the corresponding terminal.

[0033] Fifthly, a data transmission method is provided, the beneficial effects of which can be found in the description of the fourth aspect. Applied to a first functional entity, the method includes: receiving request information from an access network device, the request information containing description information of third downlink data, the third downlink data being downlink data requested for transmission by the access network device; and sending fourth downlink data to the access network device, the fourth downlink data being a subset or the entirety of the third downlink data, the fourth downlink data being downlink data permitted to be sent by the first functional entity.

[0034] In one implementation, before sending the fourth downlink data to the access network device, the method further includes: sending response information to the access network device, the response information containing authorization information for the fourth downlink data.

[0035] In one implementation, the description information of the third downlink data includes at least one of the following: the identifier of the third downlink data, or the size of the third downlink data. Further, the description information of the third downlink data also includes at least one of the following: the transmission period of the third downlink data, or the transmission time of the third downlink data.

[0036] In one implementation, the authorization information of the fourth downlink data includes at least one of the following: the identifier of the fourth downlink data, or the size of the fourth downlink data. Further, the authorization information of the fourth downlink data also includes at least one of the following: the transmission time of the fourth downlink data, or the transmission period of the fourth downlink data.

[0037] In one implementation, receiving request information from the access network device includes: receiving request information from the access network device through a second functional entity; sending response information to the access network device includes: sending the response information to the access network device through the second functional entity.

[0038] In one implementation, the identifiers of the third downlink data and the fourth downlink data include an identifier for a Quality of Service (QoS) flow or an identifier for an Internet Protocol (IP) flow.

[0039] In a sixth aspect, a data transmission method is provided, the beneficial effects of which can be found in the description of the fourth aspect. Applied to an access network device and a first functional entity, the method includes: the access network device sending a request message to the first functional entity, the request message containing description information of third downlink data, the third downlink data being downlink data requested for transmission by the access network device; and the first functional entity sending fourth downlink data to the access network device, the fourth downlink data being a subset or the entirety of the third downlink data, the fourth downlink data being downlink data permitted to be transmitted by the first functional entity.

[0040] In one implementation, the method further includes: a first functional entity sending response information to an access network device, the response information including authorization information for the fourth downlink data.

[0041] In one implementation, the description information of the third downlink data includes at least one of the following: the identifier of the third downlink data, or the size of the third downlink data. Further, the description information of the third downlink data also includes at least one of the following: the transmission period of the third downlink data, or the transmission time of the third downlink data.

[0042] In one implementation, the authorization information of the fourth downlink data includes at least one of the following: the identifier of the fourth downlink data, or the size of the fourth downlink data. Further, the authorization information of the fourth downlink data also includes at least one of the following: the transmission time of the fourth downlink data, or the transmission period of the fourth downlink data.

[0043] In one implementation, sending the request information to the first functional entity includes: sending the request information to the first functional entity through a second functional entity; the first functional entity sending the response information to the access network device includes: the first functional entity sending the response information to the access network device through the second functional entity.

[0044] In one implementation, the identifiers of the third downlink data and the fourth downlink data include an identifier for a Quality of Service (QoS) flow or an identifier for an Internet Protocol (IP) flow.

[0045] A seventh aspect provides a communication apparatus, including units or means for performing each step of any one of the first to sixth aspects described above.

[0046] Eighthly, a communication device is provided, including a processor and a memory; the memory is used to store computer instructions, and when the device is in operation, the processor executes the computer instructions stored in the memory to cause the device to perform the methods of any one of the first to sixth aspects described above.

[0047] A ninth aspect provides a communication apparatus comprising a processor coupled to a memory for invoking a program stored in the memory to execute the methods of any one of the first to sixth aspects described above. The memory may be located within or outside the apparatus. Furthermore, there may be one or more processors.

[0048] In a tenth aspect, a communication device is provided, comprising a processor and an interface circuit, the processor being configured to communicate with other devices via the interface circuit and to execute the methods of any one of the first to sixth aspects described above, wherein the processor may be one or more.

[0049] Eleventhly, a chip system is provided, comprising: a processor for performing the methods of any one of the first to sixth aspects described above.

[0050] In a twelfth aspect, a computer-readable storage medium is provided, wherein instructions are stored therein, which, when executed on a communication device, cause the methods of any one of the first to sixth aspects described above to be performed.

[0051] In a thirteenth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed by a communication device, cause the methods of any one of the first to sixth aspects described above to be performed.

[0052] In a fourteenth aspect, a communication system is provided, comprising an access network device performing the method of the first aspect and a first functional entity performing the method of the second aspect; or, comprising an access network device performing the method of the fourth aspect and a first functional entity performing the method of the fifth aspect. Attached Figure Description

[0053] Figure 1 This is a schematic diagram of the network architecture of the communication system to which the embodiments of this application apply;

[0054] Figure 2 A schematic diagram illustrating a congestion control strategy provided in an embodiment of this application;

[0055] Figure 3 A process of the data transmission method provided in the embodiments of this application;

[0056] Figure 4 Another process of the data transmission method provided in the embodiments of this application;

[0057] Figure 5 A schematic diagram illustrating an application scenario provided in an embodiment of this application;

[0058] Figure 6 A schematic diagram of the device provided in the embodiments of this application;

[0059] Figure 7 Another schematic diagram of the device provided in the embodiments of this application. Detailed Implementation

[0060] refer to Figure 1 This is a network architecture diagram of a communication system applicable to embodiments of this application. The communication system includes a wireless access network 100 and a core network 200. Optionally, the communication system 1000 may also include the Internet.

[0061] The wireless access network 100 may include at least one wireless access network device and at least one terminal. The terminal connects wirelessly to the wireless access network device, and the wireless access network device connects to the core network 200 via wired or wireless means. The core network device and the wireless access network device may be independent physical devices, or the functions of the core network device and the logical functions of the wireless access network device may be integrated into the same physical device, or a single physical device may integrate some of the functions of the core network device and some of the functions of the wireless access network device. Terminals and wireless access network devices can be interconnected via wired or wireless means. Figure 1 This is just a schematic diagram. The communication system 1000 may also include other network devices, such as wireless repeaters and wireless backhaul devices. Figure 1 It is not shown in the middle.

[0062] Wireless access network (WAN) equipment is a device used in a communication system to connect terminals to a wireless network. WAN equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in 5G mobile communication systems, a next-generation base station in 6G mobile communication systems, a base station in future mobile communication systems, or an access node in a wireless fidelity (WiFi) system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). The CU here performs the functions of the radio resource control (RRC) protocol and packet data convergence protocol (PDCP) of the base station, and can also perform the functions of the service data adaptation protocol (SDAP). The DU performs the functions of the radio link control (RLC) layer and medium access control (MAC) layer of the base station, and can also perform some or all of the physical (PHY) layer functions. For specific descriptions of the above-mentioned protocol layers, please refer to the relevant technical specifications of the 3rd generation partnership project (3GPP). The wireless access network equipment can be a macro base station, a micro base station, an indoor station, a relay node, or a donor node, etc. The embodiments of this application do not limit the specific technology and specific equipment form used in the wireless access network equipment. In the embodiments of this application, the wireless access network equipment can be simply referred to as access network equipment. Unless otherwise specified, the access network equipment mentioned below refers to the wireless access network equipment.

[0063] A terminal is a device with wireless transceiver capabilities. It can also be called a user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0064] As an example and not a limitation, in the embodiments of this application, when the terminal is a wearable device, the wearable device can also be called a wearable smart device or a smart wearable device, etc., which is a general term for devices that are intelligently designed and developed using wearable technology to make everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on only one type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets, smart helmets, and smart jewelry for vital sign monitoring. The various terminals described above, if located in a vehicle (e.g., placed in or installed in a vehicle), can be considered as vehicle terminals, which are also called on-board units (OBUs).

[0065] Access network devices and terminals can be fixed in location or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network devices and terminals.

[0066] Communication between access network devices and terminals, between access network devices, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0067] Core network equipment refers to the equipment in the core network 200 that provides service support to terminals. For example... Figure 1 As shown, the core network equipment includes access control function, network computing converged function (NCCF) node, and computing management function (CMF) node.

[0068] The Access Control Function (ACC) manages terminal access and mobility, including user location updates, network registration, and cell handover. Its function is similar to the Access and Mobility Management Function (AMF) in 5G systems. The Core Network Controller (NCCF) is responsible for receiving and sending core network service data, as well as data caching. For example, in the downlink direction, the NCCF can send downlink data to the access network equipment, which then forwards the downlink data to the corresponding terminal. In the uplink direction, the NCCF can receive uplink data from the terminal through the access network equipment. Furthermore, the NCCF provides computing services (or computing power services) to the terminal. Computing services utilize the NCCF's hardware and software resources to perform logical calculations, such as video / image rendering calculations and artificial intelligence (AI) inference calculations. The Network Session Management (CSM) is primarily responsible for one or more of the following: selecting the appropriate Network Controller Center (NCCF) based on the terminal's service request; and establishing a corresponding network layer bearer (or session, or session + user plane channel) between the terminal and the NCCF based on the terminal's or the NCCF's request. The CMF's network session management function is similar to the session management function (SMF) + policy control function (PCF) in 5G systems. In 5G systems, the SMF is mainly used for session management, such as establishing, modifying, and releasing user sessions. The PCF primarily supports providing a unified policy framework to control network behavior, providing policy rules to the control layer network functions, and is also responsible for obtaining user subscription information related to policy decisions. Furthermore, the CMF is also used to select the NCCF based on input parameters related to the computing services provided by the terminal or the NCCF, similar to the function of selecting a Domain Name System (DNS) service.

[0069] The terminal includes an application (APP) layer and a 3GPP communication layer. The 3GPP communication layer includes a converged transport layer, a Transmission Control Protocol (TCP) / User Datagram Protocol (UDP) / Internet Protocol (IP) layer, and a Uu layer. The Uu layer can refer to the Uu air interface-related protocol layers, such as RRC, SDAP, PDCP, RLC, MAC, and PHY layers, without limitation. Access network equipment includes the Uu layer and the General Packet Radio Service Tunneling Protocol-Control Plane (GTP-C) / General Packet Radio Service Tunneling Protocol-User Plane (GTP-U). The GTP protocol is a set of high-level IP-based protocols, located on top of TCP / IP or UDP / IP protocols, primarily used to support General Packet Radio Service (GPRS) communication protocols in access network equipment. GTP-U is used to transmit user plane data, and GTP-C is used to transmit control plane signaling. The NCCF (Non-Access Strategies for Communication and Control) includes a coupled transport layer, a TCP / UDP / IP layer, and a GTP-U layer in the data plane. In the control plane, it includes scheduling decisions and the GTP-C layer. Taking downlink data transmission as an example, the NCCF encapsulates the application layer data (which can be considered downlink data) generated by the application layer through a converged transport layer, TCP / UDP / IP, and GTP-U layer, and then sends it to the access network. The access network equipment decapsulates the downlink data using the GTP-U layer, then encapsulates it again using the Uu layer, and sends it to the terminal. The terminal decapsulates the downlink data through the Uu, TCP / UDP / IP, and converged transport layers to obtain application layer data. Furthermore, the terminal can also communicate with the access control function using non-access stratum (NAS) protocols. The user plane interface between the terminal and the NCCF is Nsd, used to transmit data plane data, and the control plane interface is Nss, used to transmit control plane signaling. Optionally, when the control plane is tightly coupled, a control plane interface (Nss) may not exist between the terminal and the NCCF. The interface between the access network device and the NCCF is N3*, which enables joint scheduling of N3 and the application layer.

[0070] It is understood that the functions in the embodiments of this application may also be referred to as entities or network elements, etc. For example, NCCF may also be referred to as NCCF entity or network element, etc. The above-mentioned functions, entities, or network elements may be network components in hardware devices, software running on dedicated hardware devices, or virtualization functions instantiated on a platform (e.g., cloud platform), etc. Optionally, the above-mentioned functions, network elements, or entities may be implemented by one device, or by multiple devices, or may be a functional module within a device. The embodiments of this application do not specifically limit this.

[0071] like Figure 2 As shown, in one network architecture, the downlink transmission process includes: data network (DN) (AF or application server (AS)) → user plane function (UPF) → access network equipment → terminal. A mismatch between the downlink service transmission and the air interface transmission capacity of the access network equipment may lead to downlink data congestion. For example, if the access network equipment has limited air interface transmission resources, and a large amount of downlink data is being queued for transmission, sending a large amount of downlink data to the access network equipment may cause downlink data congestion at the access network equipment. In one implementation, the access network equipment collects air interface congestion information, such as congestion level, and reports the air interface congestion information to the UPF. The AF / AS, through the control plane application programming interface (API), calls (e.g., ...) Figure 2 As shown in a), for example, the UPF reports air interface congestion information to the local network exposure function (NEF) via API scheduling. The AF / AS obtains the air interface congestion information through the local NEF, or the AF / AS obtains it through user plane mechanisms (such as...). Figure 2 As shown in b), air interface congestion information of the access network device is obtained. Alternatively, the terminal reports air interface congestion information to the AF / AS through the application layer. The AF / AS adjusts the speed or data format of downlink data transmission based on the air interface congestion information. For example, when the air interface congestion level is high, the AF / AS can reduce the downlink data transmission speed and / or adjust the downlink data frame size, as different data frames require different amounts of data; for example, the downlink data frame can be adjusted to a smaller data frame size. In this implementation, the access network device reports air interface congestion information to the AF / AS through the UPF, and the AF / AS adjusts the downlink data transmission automatically. Since the access network device and / or UPF are uncontrollable by the AF / AS, the design of the AF / AS adjusting the downlink data transmission automatically based on the air interface congestion information may also cause a mismatch between downlink data transmission and air interface transmission.

[0072] This application provides a data transmission method, including: a first functional entity sending a request message to an access network device, the request message containing description information of first downlink data requested for transmission by the first functional entity. The access network device determines authorized / permitted second downlink data for transmission based on the description information of the first downlink data and air interface transmission conditions, the second downlink data being the entire set or a subset of the first downlink data. The access network device sends a response message to the NCCF, the response message including authorization information for the second downlink data. Through this design, the first functional entity needs to send a request message to the access network device before transmitting the first downlink data. The access network device can flexibly and dynamically control the transmission of the first downlink data based on air interface transmission conditions. For example, when air interface transmission is relatively idle, the access network device can authorize the transmission of all of the first downlink data, that is, the access network device allows the first functional entity to transmit all of the first downlink data it requested, or, as described, the access network device authorizes or allows the first functional entity to transmit all of the first downlink data requested in the request message. In this case, the second downlink data authorized by the access network device is the entire set of the first downlink data. Alternatively, when air interface transmission is congested, a portion of the first downlink data can be authorized, that is, the portion of the first downlink data that the access network device allows the first functional entity to transmit, or described as the portion of the first downlink data that the access network device authorizes or allows the first functional entity to transmit in the request information. In this case, the second downlink data authorized by the access network device is a subset of the first downlink data. In the embodiments of this application, the first functional entity transmits downlink data to the access network device according to the authorization or permission of the access network device. The transmission of downlink data by the access network device is matched with the air interface situation of the access network device, avoiding congestion or packet loss caused by bursts of downlink data, and improving the efficiency and robustness of system data transmission.

[0073] In this embodiment, the first functional entity is the function of transmitting downlink data to the access network device, and the second functional entity is the function of managing the network bearer established between the terminal and the first functional entity. The names of the first and second functional entities are not limited. For example, if the first functional entity is NCCF and the second functional entity is CMF, then... Figure 3 As shown, a process is provided, including:

[0074] Optionally, step 300: The terminal establishes a connection with the first NCCF.

[0075] For example, when a terminal accesses a network, it establishes a terminal-network session. This terminal-network session refers to an association between the terminal and the data network providing Protocol Data Unit (PDU) connection services. Multiple network elements in the mobile communication network collaborate to maintain this association. To maintain this association, the mobile communication network also introduces sessions between the CMF and NCCF on the core network side. A terminal-network session may include multiple CMF-NCCF sessions between the CMF and different NCCFs. These multiple CMF-NCCF sessions are for enabling PDU exchange between the terminal and the data network. The terminal-network session can be called a new PDU session or a PDU* session. In the following description, it will be uniformly referred to as a PDU* session. The PDU* session in this application is used to provide data exchange services for computing services or computing power services between the terminal and the data network. This session can be a dedicated session, used only for transmitting data for computing services or computing power services. Alternatively, the session can be used for transmitting data for computing services or computing power services, as well as data for other services, without limitation. The PDU* session contains at least one Quality of Service (QoS) stream. In this embodiment, the QoS stream is the smallest granularity for distinguishing QoS, and QoS control is achieved through the processing of user plane data by the terminal, access network equipment, and the first NCCF. In this embodiment, the QoS stream at least includes functions for controlling computing power services or computing services, and may further include some or all of the functions of the QoS stream in current mobile communication systems. In this embodiment, the QoS stream can be called a new QoS stream, or simply a QoS stream. In the following description, a QoS stream is used as an example. In one understanding, the QoS stream includes N3* and a data radio bearer (DRB), where N3* is used for data transmission between the first NCCF and the access network equipment, and the DRB is used for data transmission between the access network equipment and the terminal. During the session establishment process between the terminal and the network, the CMF selects one or more NCCFs for the terminal, including the first NCCF. In this embodiment, the process of an NCCF transmitting downlink data to the terminal is highlighted. For example, the first NCCF can provide computing services to the terminal, which may include rendering services such as rendering images, videos, and / or modeling objects output by modeling software. Alternatively, the first NCCF can provide AI services to the terminal, such as AI inference calculations, video and / or image recognition, etc. The terminal can establish a data plane transport layer connection with the first NCCF, which can be an Nsd connection. Optionally, a control plane connection, an Nss connection, can also be established.For example, when the first NCCF transmits downlink data to the terminal, it can determine the corresponding QoS flow. The first NCCF uses the N3* corresponding to this QoS flow to transmit downlink data to the access network device. The access network device uses the DRB corresponding to this QoS flow to send downlink data to the terminal. N3* is the transmission interface between the access network device and the first NCCF, N3* is the transmission channel between the access network device and the NCCF, and N3* is used to transmit data related to computing services or computing power services between the access network device and the NCCF. Furthermore, N3* can also implement all or part of the functions of the current N3.

[0076] Step 301: The first NCCF sends a request message to the access network device. The request message includes a description of the first downlink data, which is the downlink data that the first NCCF requests to be transmitted.

[0077] For example, the request information can also be called flow scheduling request information, QoS flow scheduling request information, (downlink) N3* scheduling request information, etc. The description information of the first downlink data includes at least one of the following: the identifier of the first downlink data, or the size of the first downlink data. Furthermore, the description information of the first downlink data also includes at least one of the following: the transmission period of the first downlink data, or the transmission time of the first downlink data, etc., without limitation.

[0078] In one implementation, the request information may be a message sent by the first NCCF to the access network device (e.g., a flow scheduling request message, a QoS flow scheduling request message, or a (downlink) N3* scheduling request message, etc.), and the description information of the first downlink data may be a container, one or more information elements (IEs), or one or more parameters carried in the message. In another implementation, the request information may be a container carried in a message sent by the first NCCF to the access network device, and the description information of the first downlink data may be one or more IEs, or one or more parameters, etc., within that container. In yet another implementation, the request information may be an information element, and the description information of the first downlink data may be all or some of the bits in that information element; or, the request information may be multiple information elements, and the description information of the first downlink data may be all or some of the bits in those multiple information elements. Alternatively, the request information may be a parameter, and the description information of the first downlink data may be all or some of the bits in that parameter; or, the request information may be multiple parameters, and the description information of the first downlink data may be all or some of the bits in those multiple parameters.

[0079] Optionally, the request information may further include at least one of the following: a session identifier between the terminal and the network, or a connection identifier between the first NCCF and the access network. Optionally, the connection identifier between the first NCCF and the access network may include at least one of the following: a CMF-NCCF session identifier, an N3* identifier, an identifier corresponding to a QoS flow, or an IP flow identifier of the at least one terminal, etc.

[0080] In one design, request information can be transmitted via the control plane. For example, the first NCCF sends request information to the access network device via the CMF. Specifically, the transmission path of the request information includes: first NCCF → CMF → Access Control Function → Access Network Device. The request information is per terminal granularity, or per CMF-NCCF session granularity, or per terminal-network session, etc., in which case the request information may be for the data transmission of a single terminal. Alternatively, the request information may be for each NCCF-access network device node, in which case the request information is for the data transmission of at least one terminal. Optionally, the request information may also include at least one of the following: terminal-network session identifier, CMF-NCCF session identifier, N3* identifier, identifier corresponding to the QoS flow, or IP flow identifier of the at least one terminal. When the N3* identifier is identified by the NCCF-side identifier and the access network device-side identifier, the N3* identifier of all QoS flows in a PDU* session is the same, where the identifier may consist of an IP address and a port number. The CMF can determine the corresponding AMF based on the information contained in the request information, and the AMF can then determine the access network device. As explained earlier, the request information can be for data transmission from at least one terminal, which can access the same access network device or different access network devices. That is, the access network device determined by the AMF can be one access network device or multiple access network devices, etc., without limitation. Alternatively,

[0081] Request information can be transmitted via the user plane. The transmission path of the request information includes: first NCCF → access network device. The request information can be at the per-terminal granularity, requesting data transmission for a single terminal. Alternatively, the request information can be at the per-NCCF-access network device node granularity, requesting data transmission for at least one terminal, and the request information includes the N3* identifier of the at least one terminal, etc. No limitations are imposed.

[0082] Optionally, the identifier of the first downlink data may include an identifier of a Quality of Service (QoS) flow or an identifier of an IP flow, etc. In one design, the request information includes: a QoS flow list and data size, and may also include transmission time. The QoS flow list includes at least one QoS flow identifier, which can be considered as the identifier of the first downlink data requested by the first NCCF. For example, if the QoS flow list includes: QoS flow 1, QoS flow 2, and QoS flow 3, it indicates that the first NCCF requests to send downlink data using QoS flow 1, QoS flow 2, and QoS flow 3. In another design, a QoS flow includes at least one IP flow. The request information includes: an IP flow list and data size, and may also include transmission time. The IP flow list includes at least one IP flow identifier, which can be considered as the identifier of the first downlink data requested by the first NCCF. For example, if the IP flow list includes IP flow 1, IP flow 2, and IP flow 3, it indicates that the first NCCF requests to send the first downlink data using IP flow 1, IP flow 2, and IP flow 3. The identifier for an IP flow can be a 5-tuple, such as the source IP address, source port number, destination IP address, destination port number, and protocol.

[0083] Step 302: The access network device determines the second downlink data based on the description information of the first downlink data and the air interface transmission status of the access network device. The second downlink data is the entire set or a subset of the first downlink data. Here, a subset means that one or more of the following parameters in the second downlink data—the number of QoS* flows or IP flows, data size, transmission time, and transmission period—are a subset of the corresponding parameters in the first downlink data: number of QoS* flows or IP flows, data size, transmission time, and transmission period.

[0084] The description of step 302 can also be replaced by: The access network device determines the second downlink data based on the request information and the air interface transmission status of the access network device. Optionally, in addition to the description information of the first downlink data, the request information may also include other information, and there are no restrictions on the other information. For example, when determining the second downlink data, the access network device may need to consider the influence of other information contained in the request information, in addition to considering the influence of the description information of the first downlink data.

[0085] The description of step 302 can also be replaced by: The access network device determines the authorization information of the second downlink data based on the description information of the first downlink data and the air interface transmission status of the access network device. Alternatively, the access network device determines the authorization information of the second downlink data based on the request information and the air interface transmission status of the access network device. The authorization information of the second downlink data is used to indicate the second downlink data.

[0086] In the following description, we will take the example of an access network device determining the authorization information of the second downlink data based on the description information of the first downlink data and the air interface transmission status of the access network device.

[0087] For example, the authorization information for the second downlink data includes at least one of the following: the identifier of the second downlink data, or the size of the second downlink data. Optionally, the identifier of the second downlink data can be a QoS flow identifier or an IP flow identifier. For example, the identifier of the first downlink data requested by the first NCCF includes QoS flow 1, QoS flow 2, and QoS flow 3. If the access network device authorizes the first NCCF to use QoS flow 2 and QoS flow 3 for downlink data transmission, then the identifier of the second downlink data includes QoS flow 2 and QoS flow 3. The size of the second downlink data can be less than or equal to the size of the first downlink data. For example, the size of the first downlink data requested by the first NCCF is 2048 bits, and the size of the second downlink data authorized by the access network device is 1024 bits. Further, the authorization information for the second downlink data also includes at least one of the following: the transmission time of the second downlink data, or the transmission period of the second downlink data. The transmission time of the second downlink data is the entire set or a subset of the transmission time of the first downlink data, and the transmission period of the second downlink data is usually greater than or equal to the transmission period of the first downlink data. For example, the transmission time of the first downlink data requested by the first NCCF is from 15:05 to 15:30, and the transmission time of the second downlink data authorized by the access network device can be from 15:10 to 15:25. The transmission period of the first downlink data requested by the first NCCF is 15ms, and the transmission time of the second downlink data authorized by the access network device can be 20ms, etc.

[0088] In one implementation, when the authorization information for the second downlink data does not contain any information, the access network device may be instructed to refuse the first NCCF from sending any downlink data. And / or, the response information in step 304 below may include a rejection indication, which instructs the access network device to refuse the first NCCF from sending any downlink data.

[0089] In one implementation, the request information sent by the first NCCF to the access network device includes: an identifier of the first downlink data. Optionally, the request information further includes: the transmission time and / or period of the first downlink data. The response information sent by the access network device to the first NCCF includes: an identifier of the second downlink data. Optionally, the response information further includes: the size of the second downlink data, the transmission time and / or period of the second downlink data.

[0090] In another implementation, the request information sent by the first NCCF to the access network device includes: the size of the first downlink data. Optionally, the request information also includes: the transmission time and / or period of the first downlink data. The response information sent by the access network device to the first NCCF includes: the size of the second downlink data. Optionally, the response information also includes: the transmission time and / or period of the second downlink data. Further, optionally, the response information also includes: the identifier of the second downlink data.

[0091] In one implementation, the request information sent by the first NCCF to the access network device includes: the identifier and size of the first downlink data. Optionally, the request information also includes: the transmission time and / or period of the first downlink data. The response information sent by the access network device to the first NCCF includes: the identifier and size of the second downlink data. Optionally, the response information also includes: the transmission time and / or period of the second downlink data.

[0092] Optionally, the air interface scheduling status of the access network device includes at least one of the following: the current scheduling status of the access network device, the historical scheduling status of the access network device, or the predicted scheduling status of the access network device. The scheduling status of the access network device includes the downlink scheduling cycle of the access network device, and / or the use of semi-scheduling, etc. Semi-scheduling refers to the access network device sending a start scheduling command to the terminal when scheduling downlink data transmission, after which the access network device can periodically send downlink data to the terminal. At the end of downlink data transmission, the access network device sends an end command to the terminal, indicating the end of downlink data scheduling, etc. Optionally, the scheduling status of the access network device can be predicted using AI or other methods. For example, an AI model can be pre-trained to predict the scheduling status of the access network device. The current scheduling status, historical scheduling status, and / or predicted time information of the access network device can be input into the AI ​​model, and the output of the AI ​​model is the predicted scheduling status of the access network device, etc.

[0093] As previously explained, the access network device can determine the authorization information of the second downlink data based on the description information of the first downlink data and the air interface transmission status of the access network device. The description information of the first downlink data includes the identifier of the first downlink data or the size of the first downlink data. Furthermore, the description information of the first downlink data may also include at least one of the following: the transmission period of the first downlink data or the transmission time of the first downlink data, etc., without limitation. The authorization information of the second downlink data includes the identifier of the second downlink data or the size of the second downlink data. Furthermore, the authorization information of the second downlink data may also include at least one of the following: the transmission time of the second downlink data or the transmission period of the second downlink data.

[0094] For example, the first downlink data requested by the first NCCF includes QoS flow 1, QoS flow 2, and QoS flow 3. That is, the description information of the first downlink data includes the identifiers of QoS flow 1, QoS flow 2, and QoS flow 3. If the access network device determines that the downlink data to be transmitted in the DRB corresponding to QoS flow 1 is greater than a threshold, then the access network device can authorize downlink data transmission for QoS flow 2 and QoS flow 3, but not authorize downlink data transmission for QoS flow 1. In this case, the identifiers of the second downlink data in the authorized data include the identifiers of QoS flow 2 and QoS flow 3. Furthermore, the access network device can also consider requests from other NCCFs besides the first NCCF, such as requests from the second NCCF. For example, the first NCCF and the second NCCF send request information to the access network device respectively. The downlink data requested by the first NCCF includes QoS flow 1, QoS flow 2, and QoS flow 3; the downlink data requested by the second NCCF includes QoS flow 3, QoS flow 4, and QoS flow 5. In one implementation, if the downlink data to be transmitted in the DRB corresponding to QoS flow 3 is less than a threshold, QoS flow 3 can be authorized to both the first and second NCCFs. Alternatively, if the access network device grants QoS flow 3 to both the first NCCF and the second NCCF, it may cause the data to be transmitted in the DRB corresponding to QoS flow 3 to exceed the threshold. In this case, the access network device may grant QoS flow 3 to the first NCCF or the second NCCF, etc.

[0095] Optionally, the first NCCF can serve at least one terminal, which can access the network through the same or different access network devices. For example, the first NCCF serves a first terminal and a second terminal, where the first terminal accesses the network through a first access network and the second terminal accesses the network through a second access network device. When sending downlink data to the first terminal, the first NCCF can send a request message to the first access network device. Similarly, when sending downlink data to the second terminal, the first NCCF can send a request message to the second access network device. These two request messages are independent; that is, the scheduling of downlink data for the second terminal by the first NCCF and the second access network device is independent of the scheduling of downlink data for the first terminal by the first NCCF and the first access network device.

[0096] When determining the authorization information for the second downlink data, the access network device may need to consider the following factors in addition to the influence of the identifier of the first downlink data. For example, the size of the first downlink data. Continuing the example above, the first downlink data requested by the first NCCF includes QoS flow 1, QoS flow 2, and QoS flow 3. The size of the first downlink data can refer to the size of the downlink data corresponding to each of the three QoS flows in the first downlink data. For example, the size of the downlink data corresponding to QoS flow 1, the size of the downlink data corresponding to QoS flow 2, and the size of the downlink data corresponding to QoS flow 3 in the first downlink data. In one implementation, the threshold for the downlink data transmitted in each QoS flow may be the same or different. The access network device can determine whether the downlink data requested to be transmitted in each QoS flow requested by the first NCCF is less than or equal to the threshold. If it is less than or equal to the threshold, the access network device authorizes or allows the downlink data transmission of that QoS; otherwise, the access network device rejects the downlink data transmission of that QoS flow. Continuing with the above example, if the downlink data sizes of QoS flows 1 and 2 requested by the first NCCF are both less than or equal to the corresponding thresholds, and the downlink data requested by QoS flow 3 is greater than the corresponding threshold, then the access network device authorizes downlink data transmission for QoS flows 1 and QoS flows 2, and rejects downlink data transmission for QoS flow 3. In this case, the identifier of the second downlink data includes the identifiers of QoS flows 1 and QoS flows 2. Alternatively, if the downlink data sizes of QoS flows 1 and QoS flows 2 requested by the first NCCF are both less than or equal to the corresponding thresholds, and the downlink data requested by QoS flow 3 is greater than the corresponding threshold, then the access network device authorizes downlink data transmission for QoS flows 1 and QoS flows 2, allows downlink data transmission of QoS flow 3 within the threshold range, and rejects downlink data transmission of QoS flow 3 exceeding the threshold range. In this case, the identifier of the second downlink data includes QoS flows 1 and QoS flows 2, QoS flow 3, and the allowed data size for QoS flow 3.

[0097] The size of the first downlink data can refer to the sum of the downlink data corresponding to the three QoS flows mentioned above. In this case, the access network device can, for example, select the higher-priority QoS flow for priority authorization based on the priority of the QoS flows. For instance, if the priorities of the QoS flows are QoS flow 1, QoS flow 2, and QoS flow 3 from high to low, the access network device can prioritize allocating downlink data transmission to QoS flow 1 and QoS flow 2. If QoS flow 1 and QoS flow 2 cannot satisfy the transmission of all downlink data, the remaining downlink data can be reallocated to QoS flow 3 for transmission. Alternatively, if the access network device finds that the sum of the downlink data corresponding to the three QoS flows (i.e., the total size of the first downlink data) is greater than or equal to a threshold, it can authorize a portion of the first downlink data for downlink data transmission. For example, if the size of the first downlink data requested by the first NCCF is 2048 bits, the first NCCF can authorize the downlink transmission of 1024 bits. In one design, these 1024 bits can be transmitted in all three QoS flows requested by the first NCCF, or in any one or any two of the three QoS flows. For example, these 1024 bits can be preferentially allocated to the data transmission of high-priority QoS flows. Alternatively, they can be allocated based on the amount of data to be transmitted in each QoS flow. For instance, priority can be given to QoS flows with smaller amounts of data to be transmitted; this mechanism can be called the shortest job first (SJF) mechanism. Or, priority can be given to QoS flows with larger amounts of data to be transmitted; this mechanism can be called the long job first (LJF) mechanism. Alternatively, the access network device can also allocate corresponding QoS flows to downlink data based on factors such as downlink data transmission time requirements. For example, for downlink data that urgently needs to be transmitted to the terminal, the access network device can allocate it to QoS flows that are deterministically transmitting urgent data. It is understood that the above examples illustrate how the access network device allocates a portion of the first downlink data to different QoS flows, using the example of the access network device authorizing a portion of the first downlink data for downlink data transmission. If the access network device authorizes the entire first downlink data for downlink data transmission, the access network device can allocate the entire first downlink data to the corresponding QoS flow according to the above allocation mechanism.

[0098] For example, the air interface transmission status of the access network device may differ at different times. The time can refer to one or more scheduling cycles or one or more time periods of the air interface. When the first NCCF requests the first downlink data transmission, it sends the transmission cycle and / or transmission time of the first downlink data to the access network device, allowing the access network device to achieve more accurate authorization. For example, the first downlink data requested by the first NCCF includes QoS stream 1, QoS stream 2, and QoS stream 3. At the first time, the air interface scheduling of the access network device is idle; for example, the data transmission of the DRBs corresponding to QoS streams 1, QoS stream 2, and QoS stream 3 is all less than or equal to the threshold. If the first NCCF requests the first downlink data transmission at the first time, the access network device can authorize the above three QoS streams to perform downlink data transmission at the first time. At the second time, the air interface scheduling of the access network device is congested; for example, the data transmission of the DRBs corresponding to QoS streams 1, QoS stream 2, and QoS stream 3 is all greater than the threshold. If the first NCCF requests the first downlink data transmission at the second time, the access network device can reject the downlink data transmission of these three QoS streams at the second time. Alternatively, in the third time period, the air interface scheduling of the access network device is congested. For example, the data transmission of the DRB corresponding to QoS flow 1 and QoS flow 2 is less than or equal to the threshold, and the data transmission of the DRB corresponding to QoS flow 3 is greater than the threshold. If the first NCCF requests downlink data transmission in the third time period, the access network device may authorize the downlink data transmission of QoS flow 1 and QoS flow 2 in the third time period, and deny the downlink data transmission of QoS flow 3 in the third time period, etc.

[0099] Step 303: The access network device sends a response message to the first NCCF, the response message containing the authorization information for the second downlink data.

[0100] For example, the response information can also be called flow scheduling response information, QoS flow scheduling response information, (downlink) N3* scheduling response information, etc., without any restrictions.

[0101] In one implementation, the response information can be a message sent by the access network device to the first NCCF (e.g., a flow scheduling response message, a QoS flow scheduling response message, a (downlink) N3* scheduling response message, etc.), and the authorization information for the second downlink data can be a container, one or more IEs, or one or more parameters carried in that message. In another implementation, the response information can be a container carried in a message sent by the access network device to the first NCCF, and the authorization information for the second downlink data can be one or more IEs, or one or more parameters, within that container. In yet another implementation, the response information can be a single cell, and the authorization information for the second downlink data can be all or some of the bits in that single cell; or, the response information can be multiple cells, and the authorization information for the second downlink data can be all or some of the bits in those multiple cells. Alternatively, the response information can be a parameter, and the authorization information for the second downlink data can be all or some of the bits in that parameter; or, the response information can be multiple parameters, and the authorization information for the second downlink data can be all or some of the bits in those multiple parameters.

[0102] In one implementation, response information can be transmitted via the control plane. For example, the access network device sends response information to the first NCCF via the CMF. The transmission path of the response information includes: access network device → access control function → CMF → first NCCF, etc. The response information is per-terminal granularity, or per-CMF-NCCF session granularity, or per-terminal-network session, etc., in which case the response information may be a response to the data transmission of a single terminal. Alternatively, the response information may be per NCCF-access network device node, in which case the response information is a response to the data transmission of at least one terminal. Optionally, the response information may also include at least one of the following: a terminal-network session identifier, a CMF-NCCF session identifier, an N3* identifier, an identifier corresponding to a QoS flow, or an IP flow identifier of the at least one terminal. The CMF can determine the corresponding first NCCF based on the above information contained in the response information; or,

[0103] Response information can be transmitted via the user plane. The transmission path of the response information includes: access network device → first NCCF. The response information can be at the granularity of each terminal, and the response information is a response to the data transmission of one terminal. Alternatively, the response information can be at the granularity of each NCCF-access network device node, and the response information is a response to the data transmission of at least one terminal. The response information includes the N3* identifier of the at least one terminal, etc., without limitation.

[0104] For a detailed description of the authorization information for the second downlink data, please refer to step 302.

[0105] Optionally, in step 304: the first NCCF sends the second downlink data to the access network device based on the response information.

[0106] For example, the first NCCF obtains the authorization information for the second downlink data in the response information. Based on this authorization information, the first NCCF sends the second downlink data to the access network device. For instance, if the authorization information includes identifiers for the second downlink data such as QoS flow 1 and QoS flow 2, the first NCCF can use QoS flow 1 and QoS flow 2 to send the second downlink data to the access network device. Alternatively, the authorization information may include the size of the second downlink data; after sending the authorized size of downlink data to the access network device, the first NCCF stops sending downlink data. Furthermore, before sending the authorized size of downlink data to the access network device, the first NCCF can send a request message again to request continued downlink data transmission. If the access network device authorizes the first NCCF to continue sending the requested downlink data, the first NCCF continues to send the corresponding downlink data based on the new authorization information; otherwise, the first NCCF stops sending downlink data. Alternatively, if the authorization information for the second downlink data includes the transmission time of the second downlink data, then within the authorized time of the access network device, the first NCCF sends the corresponding downlink data to the access network device; upon reaching the authorized time, the first NCCF stops sending downlink data to the access network device. Furthermore, before reaching the authorized time, the first NCCF may again request the transmission of downlink data from the access network device. If the access network device authorizes it to continue transmitting, the first NCCF continues to send the corresponding downlink data to the access network device according to the new authorization information; otherwise, the first NCCF stops sending downlink data.

[0107] Optionally, step 305: The access network device sends the second downlink data to the terminal.

[0108] For example, the access network device can map the second downlink data to the corresponding DRB and send the second downlink data to the terminal through the DRB. In one design, the first NCCF can send the second downlink data to the access network device at the granularity of QoS flow. When the access network device receives the second downlink data, it can use the DRB corresponding to the QoS flow to send the second downlink data to the terminal. Alternatively, in another design, the first NCCF can send the second downlink data to the access network device at the granularity of IP flow. When the access network device receives the second downlink data, it determines the DRB corresponding to the IP flow and uses the corresponding DRB to send the second downlink data to the terminal, etc. The correspondence between the IP flow and the DRB can be preset, protocol-defined, or configured by other devices for the access network device, etc., without limitation. The other devices can be CMF, access control function, NCCF, etc. Optionally, as explained above, the access network device and the terminal can transmit the second downlink data through the user plane. When the second downlink data transmission ends, the second downlink data includes an end identifier. Alternatively, the access network device can send a signaling to the terminal through the control plane to instruct the terminal to end the second downlink data transmission, etc.

[0109] As previously explained, the request and response information exchanged between the access network device and the first NCCF can be transmitted via the control plane or the user plane. When transmitted via the user plane, for example, request and / or response information can be carried using the GTP protocol between the NCCF and the access network, specifically GTP-C or GTP-U messages. During user plane transmission: the first NCCF sends request information to the access network device through the access control function, and the access network device sends response information to the first NCCF through the access control function, which serves the terminal. During control plane transmission: the first NCCF and the access network device exchange request and response information through the CMF and the access control function. For example, the first NCCF sends request information to the CMF, the CMF sends request information to the access control function, and the access control function sends request information to the access network device. The access network device sends response information to the access control function, the access control function sends response information to the CMF, and the CMF sends response information to the first NCCF. This CMF manages the first NCCF and provides services to the terminal.

[0110] It should be noted that the second downlink data sent by the first NCCF to the access network device may originate from other data sources, such as AF or AS. Before step 304, the process may further include: the first NCCF receiving the second downlink data from the data source. And / or, the first NCCF may be deployed with an application instance, and the first NCCF sends the second downlink data from the application instance to the access network device.

[0111] In this embodiment of the application, the access network device can authorize the downlink data of the first NCCF according to the transmission status of the air interface, thereby avoiding downlink data congestion of the access network device and improving the efficiency and robustness of downlink data transmission.

[0112] This application embodiment also provides a data transmission method, which differs from the aforementioned methods in that the access network device dynamically schedules downlink data transmission of the first NCCF, and the first NCCF authorizes the downlink data. The method includes: the access network device sending request information to a first functional entity, the request information containing description information of third downlink data, the third downlink data being the downlink data requested for transmission by the access network device; the access network device receiving fourth downlink data from the first functional entity, the fourth downlink data being a subset or the entirety of the third downlink data, the fourth downlink data being the downlink data authorized for transmission by the first functional entity.

[0113] Taking the first functional entity as the first NCCF and the second functional entity as the CMF as an example, such as Figure 4 As shown, a process is provided, including:

[0114] Optionally, step 400: The terminal establishes a connection with the first NCCF.

[0115] Step 401: The access network device sends a request message to the first NCCF, which includes a description of the third downlink data that the access network device requests to be transmitted.

[0116] For example, the request information may also be referred to as flow scheduling request information, QoS flow scheduling request information, (downlink) N3* scheduling request information, etc. The description information of the third downlink data includes at least one of the following: the identifier of the third downlink data, or the size of the third downlink data. For example, the identifier of the third downlink data includes the identifier of a QoS flow or the identifier of an IP flow. Optionally, the description information of the third downlink data may also include at least one of the following: the transmission period of the third downlink data, or the transmission time of the third downlink data.

[0117] In one implementation, the access network device can send a request to the first NCCF based on air interface scheduling. For example, if the access network device determines that the first DRB is relatively idle based on air interface scheduling, it can request the first NCCF to use QoS stream 1 associated with the first DRB for downlink data transmission. Furthermore, in addition to air interface scheduling, the access network device may also need to consider the transmission needs of other NCCFs. For example, even if the first DRB is relatively idle, but has already been pre-allocated to downlink data transmission for other terminals, the QoS stream 1 associated with the first DRB may not be suitable for allocation to the current terminal for downlink data transmission.

[0118] and Figure 3Similarly, request information can be transmitted via the control plane. This request information is per-terminal granularity, or per CMF-NCCF session granularity, or per terminal-network session, etc. In this case, the request information may be for the data transmission of a single terminal. Alternatively, the request information may be for each NCCF-access network device node, in which case the request information is for the data transmission of at least one terminal. Optionally, the request information may further include at least one of the following: a terminal-network session identifier, a CMF-NCCF session identifier, an N3* identifier, an identifier corresponding to a QoS flow, or the IP flow identifier of the at least one terminal.

[0119] The request information can be transmitted via the user plane. This request information can be at the terminal-level granularity, requesting data transmission for a single terminal. Alternatively, the request information can be at the NCCF-access network device node-level granularity, requesting data transmission for at least one terminal, and includes the N3* identifier of the at least one terminal, etc. No limitations are imposed.

[0120] Optionally, step 402: The first NCCF sends a response message to the access network device, the response message containing the authorization information of the fourth downlink data.

[0121] The authorization information for the fourth downlink data includes at least one of the following: the identifier of the fourth downlink data, or the size of the fourth downlink data. Optionally, the identifier of the fourth downlink data includes the identifier of a QoS flow or the identifier of an IP flow. Furthermore, the authorization information for the fourth downlink data also includes at least one of the following: the transmission time of the fourth downlink data, or the transmission period of the fourth downlink data, etc.

[0122] and Figure 3Similar to the scheme described above, response information can be transmitted via the control plane. This response information is granular to each terminal, or to each CMF-NCCF session, or to each terminal-network session, etc., in which case the response information may be in response to the data transmission of a single terminal. Alternatively, the response information may be granular to each NCCF-access network device node, in which case the response information is in response to the data transmission of at least one terminal. Optionally, the response information may also include at least one of the following: a terminal-network session identifier, a CMF-NCCF session identifier, an N3* identifier, an identifier corresponding to a QoS flow, or the IP flow identifier of the at least one terminal. Alternatively, response information can be transmitted via the user plane. This response information may be granular to each terminal, in which case the response information is in response to the data transmission of a single terminal. Alternatively, the response information may be granular to each NCCF-access network device node, in which case the response information is in response to the data transmission of at least one terminal, and the response information includes the N3* identifier of the at least one terminal, etc. No limitations are imposed.

[0123] Step 403: The first NCCF sends fourth downlink data to the access network device. The fourth downlink data is a subset or the entire set of the third downlink data. The fourth downlink data is the downlink data authorized to be sent by the first NCCF.

[0124] In this embodiment, step 402 is optional. In one implementation, when the first NCCF receives the request information, it determines the fourth downlink data based on the third downlink data description information contained in the request information. The first NCCF then executes step 403 to send the fourth downlink data to the access network device. Alternatively, in another implementation, step 402 is mandatory. When the first NCCF determines the fourth downlink data, it first executes step 402 to send a response information containing the fourth downlink data authorization information to the access network device, and then executes step 403 to send the fourth downlink data to the access network device.

[0125] Optionally, upon receiving the request information, the first NCCF may obtain the description information of the third downlink data. The first NCCF determines the fourth downlink data based on the description information of the third downlink data. For example, the description information of the third downlink data includes at least one of the following: a list of third downlink data, the size of the third downlink data, the transmission period and / or time of the third downlink data, etc. The authorization information of the fourth downlink data determined by the first NCCF includes at least one of the following: a list of fourth downlink data, the size of the fourth downlink data, the transmission period and / or time of the fourth downlink data, etc. The identifiers included in the fourth downlink data list are a subset or the entire set of the identifiers included in the third downlink data list. The size of the fourth downlink data is less than or equal to the size of the third downlink data. The transmission time of the fourth downlink data is a subset or the entire set of the transmission times of the third downlink data. The transmission period of the fourth downlink data is greater than or equal to the transmission period of the third downlink data, etc. Taking the identifier of the downlink data as a QoS flow identifier as an example, the list of third downlink data may include: QoS flow 1, QoS flow 2, and QoS flow 3. If the first NCCF determines that QoS flow 3 is authorized for downlink data transmission, then the list of fourth downlink data includes QoS flow 3, etc. For example, if the size of the third downlink data is 2048 bits, then the size of the fourth downlink data authorized by the first NCCF is less than or equal to the size of the third downlink data; for example, the size of the fourth downlink data authorized by the first NCCF could be 1024 bits. For example, if the transmission time of the third downlink data is from 17:59 to 18:10, then the transmission time of the fourth downlink data authorized by the first NCCF can be less than or equal to the requested transmission time; for example, the authorized transmission time could be from 18:00 to 18:05. For example, if the transmission period of the third downlink data is 15ms, then the transmission period authorized by the first NCCF can be greater than or equal to the transmission period of the third downlink data; for example, it could be 20ms.

[0126] In one design, the access network device requests third downlink data. If the first NCCF has sufficient downlink data, it may authorize the entire third downlink data for downlink data transmission. Alternatively, if the first NCCF senses that data from multiple QoS flows needs to be synchronized, it may also authorize a portion of the third downlink data for downlink data transmission. For example, the third downlink data requested by the access network device may include QoS flow 1, QoS flow 2, and QoS flow 3. If QoS flow 3 needs to be synchronized with QoS flow 4, the fourth downlink data authorized by the first NCCF may include QoS flow 1 and QoS flow 2.

[0127] Step 404: The access network device sends the fourth downlink data to the corresponding terminal.

[0128] For example, the access network device can map the QoS or IP flow identifier of the fourth downlink data to the DRB, and then send the fourth downlink data to the terminal through the DRB. Optionally, the access network device and the terminal can transmit the fourth downlink data through the user plane. When the fourth downlink data transmission ends, the fourth downlink data includes an end identifier. Alternatively, the access network device can send a signaling message to the terminal via the control plane to indicate the end of the fourth downlink data transmission, etc.

[0129] Through the above implementation, the access network device can reverse schedule the downlink data transmission of the first NCCF according to the transmission status of the air interface, thereby avoiding downlink data congestion on the access network device side, improving downlink data transmission efficiency and system robustness, and enhancing the user experience.

[0130] like Figure 5 As shown in the embodiments of this application, an application scenario is provided, including: the terminal is a virtual reality (VR) glasses, the terminal establishes a PDU* session with the NCCF, the PDU* session can be associated with multiple NCCFs, and the multiple NCCFs simultaneously provide rendering services to the terminal. When the NCCF sends downlink data corresponding to the rendering service to the terminal, such as... Figure 3 As shown, the NCCF can send request information to the access network device, which can then authorize the NCCF to send all or part of the downlink data based on the air interface scheduling. Alternatively, as... Figure 4 As shown, when the access network device detects that the terminal requires rendering services, it can send a request to the NCCF. The NCCF then authorizes all or part of the requested downlink data and sends the authorized downlink data to the access network device. Furthermore, as explained earlier, the access network device and the NCCF can exchange request and response information via the user plane or control plane. Figure 5 In the example, the access network device may require other relay networks, such as vehicular network devices D and G. Specifically, communication between the NCCF and the access network device needs to be forwarded through routers K, J, H, and vehicular network devices D and G.

[0131] It should be noted that, in the embodiments of this application:

[0132] 1. Highlight the differences between the various processes. The explanations of the different processes can be used for cross-referencing.

[0133] 2. This application primarily uses downlink data transmission as an example to illustrate its embodiments, and is not intended to limit the scope of this application. The methods in this application's embodiments can also be used in other data transmissions, such as uplink data transmission. For example, when an access network device sends uplink data to a first NCCF, it can send a request message to the first NCCF, and the first NCCF can send a response message containing authorization information to the access network device. The access network device then sends authorized uplink data to the first NCCF, etc.

[0134] 3. This application primarily describes embodiments of the application using the interaction between the access network device and the first NCCF as an example, and is not intended to limit the scope of this application. For instance, the methods described in this application can also be applied to a WIFI system, where the access node can replace the function of the access network device, etc.

[0135] It is understood that, in order to achieve the functions of the above embodiments, the first NCCF and access network devices include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0136] Figure 6 and Figure 7 This is a schematic diagram illustrating the structure of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the access network device or the first functional entity in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device may be... Figure 3 The access network device or the first functional entity in the process can also be Figure 4 The access network device or first functional entity in the process can also be a module (such as a chip) applied to the access network device or first functional entity.

[0137] like Figure 6 As shown, the communication device 600 includes a processing unit 610 and a transceiver unit 620.

[0138] In one implementation, the communication device 600 is used to implement the above. Figure 3 The method embodiment shown illustrates the function of the access network device or the first functional entity.

[0139] For example, when the communication device 600 is used to implement Figure 3In the method embodiment shown, the access network device functions as follows: the transceiver unit 620 receives request information from a first functional entity, the request information including description information of first downlink data, the first downlink data being the downlink data requested for transmission by the first functional entity; the processing unit 610 determines second downlink data based on the description information of the first downlink data and the air interface transmission status of the access network device, the second downlink data being the entire set or a subset of the first downlink data; the transceiver unit 620 also sends response information to the first functional entity, the response information including authorization information for the second downlink data.

[0140] For example, when the communication device 600 is used to implement Figure 3 In the method embodiment shown, the first functional entity functions as follows: The transceiver unit 620 sends request information to the access network device, the request information including description information of first downlink data, which is downlink data requested for transmission by the first functional entity; and receives response information from the access network device, the response information including authorization information of second downlink data, which is the complete set or subset of the first downlink data. The processing unit 610 generates request information, etc.

[0141] For a more detailed description of the processing unit 610 and the transceiver unit 620, please refer to [link / reference needed]. Figure 3 The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.

[0142] In another implementation, the communication device 600 is used to implement the above. Figure 4 The functions of the access network device or the first functional entity in the method embodiment shown.

[0143] For example, when the communication device 600 is used to implement Figure 4 In the method embodiment shown, the access network device functions as follows: The transceiver unit 620 sends a request message to a first functional entity, the request message containing description information of third downlink data, which is downlink data requested for transmission by the access network device; it also receives fourth downlink data from the first functional entity, the fourth downlink data being a subset or the entirety of the third downlink data, which is downlink data permitted to be transmitted by the first functional entity. The processing unit 610 generates request information, etc.

[0144] For example, when the communication device 600 is used to implement Figure 4In the method embodiment shown, the first functional entity functions as follows: Transceiver unit 620 receives request information from an access network device, the request information including description information of third downlink data, which is downlink data requested by the access network device; and sends fourth downlink data to the access network device, the fourth downlink data being a subset or the entirety of the third downlink data, which is downlink data permitted to be sent by the first functional entity. Processing unit 610 acquires the fourth downlink data.

[0145] For a more detailed description of the processing unit 610 and the transceiver unit 620, please refer to [link / reference needed]. Figure 4 The relevant descriptions in the method embodiments shown are directly obtained and will not be repeated here.

[0146] like Figure 7 As shown, the communication device 700 includes a processor 710 and an interface circuit 720. The processor 710 and the interface circuit 720 are coupled to each other. It is understood that the interface circuit 720 can be a transceiver or an input / output interface. Optionally, the communication device 700 may also include a memory 730 for storing instructions executed by the processor 710, or storing input data required by the processor 710 to execute instructions, or storing data generated after the processor 710 executes instructions.

[0147] When the communication device 700 is used to implement Figure 3 or Figure 4 In the method shown, the processor 710 is used to implement the functions of the processing unit 610, and the interface circuit 720 is used to implement the functions of the transceiver unit 620.

[0148] When the aforementioned communication device is a module applied to an access network device, the access network device module implements the functions of the access network device in the above method embodiments. The access network device module receives information from other modules (such as radio frequency modules or antennas) in the access network device, which is information sent by the terminal to the access network device; or, the access network device module sends information to other modules (such as radio frequency modules or antennas) in the access network device, which is information sent by the access network device to the terminal. Here, the access network device module can be the baseband chip of the access network device, or it can be a DU or other modules. The DU here can be a DU under an open radio access network (O-RAN) architecture.

[0149] When the aforementioned communication device is a module applied to the first functional entity, the first functional entity model implements the functions of the first functional entity in the above method embodiments. The first functional entity module receives information from other modules (such as a radio frequency module or antenna) within the first functional entity, the information being sent to the first functional entity by the access network device; or, the first functional entity module sends information to other modules (such as a radio frequency module or antenna) within the first functional entity, the information being sent to the access network device by the first functional entity. Here, the first functional entity module can be the baseband chip of the first functional entity, or other chips, etc., without limitation.

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

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

[0152] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0153] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0154] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0155] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A data transmission method, characterized in that, Applied to access network equipment, including: Receive request information from a first functional entity, the request information containing description information of first downlink data, the first downlink data being downlink data requested to be transmitted by the first functional entity, the first functional entity being a function to transmit downlink data to the access network device, the description information of the first downlink data containing at least one of the following: the identifier of the first downlink data, or the size of the first downlink data. Based on the description information of the first downlink data and the air interface transmission status of the access network device, the second downlink data is determined. The second downlink data is the entire set or a subset of the first downlink data. The air interface transmission status includes air interface transmission idle or air interface transmission congestion. Send response information to the first functional entity. The response information includes authorization information for the second downlink data. The authorization information for the second downlink data includes at least one of the following: the identifier of the second downlink data or the size of the second downlink data.

2. The method as described in claim 1, characterized in that, The description information of the first downlink data also includes at least one of the following: the transmission period of the first downlink data, or the transmission time of the first downlink data.

3. The method as described in claim 1, characterized in that, The authorization information of the second downlink data also includes at least one of the following: the transmission time of the second downlink data, or the transmission period of the second downlink data.

4. The method according to any one of claims 1 to 3, characterized in that, The receiving of request information from the first functional entity includes: receiving request information from the first functional entity through a second functional entity, wherein the second functional entity is a function that manages the network bearer established between the terminal and the first functional entity; Sending response information to the first functional entity includes: sending the response information to the first functional entity through the second functional entity.

5. The method according to any one of claims 1 to 3, characterized in that, The identifiers of the first downlink data and the second downlink data include the identifier of the Quality of Service (QoS) flow or the identifier of the Internet Protocol (IP) flow.

6. The method according to any one of claims 1 to 3, characterized in that, The request information also includes at least one of the following: a session identifier between the terminal and the network, or a connection identifier between the first functional entity and the access network.

7. A data transmission method, characterized in that, Applied to the first functional entity, including: Send a request message to the access network device. The request message includes a description of the first downlink data. The first downlink data is the downlink data requested to be transmitted by the first functional entity. The first functional entity is a function that transmits downlink data to the access network device. The description of the first downlink data includes at least one of the following: the identifier of the first downlink data or the size of the first downlink data. The system receives a response from the access network device. The response includes authorization information for second downlink data. The second downlink data is the complete set or a subset of the first downlink data. The second downlink data is determined by the access network device based on the description information of the first downlink data and the air interface transmission status of the access network device. The air interface transmission status includes air interface idle or air interface congestion. The authorization information for the second downlink data includes at least one of the following: the identifier of the second downlink data or the size of the second downlink data.

8. The method as described in claim 7, characterized in that, The description information of the first downlink data also includes at least one of the following: the transmission period of the first downlink data, or the transmission time of the first downlink data.

9. The method as described in claim 7, characterized in that, The authorization information of the second downlink data also includes at least one of the following: the transmission time of the second downlink data, or the transmission period of the second downlink data.

10. The method according to any one of claims 7 to 9, characterized in that, Sending request information to the access network device includes: sending the request information to the access network device through a second functional entity, wherein the second functional entity is a function that manages the network bearer established between the terminal and the first functional entity; Receiving response information from the access network device includes: receiving response information from the access network device through the second functional entity.

11. The method according to any one of claims 7 to 9, characterized in that, The identifiers of the first downlink data and the second downlink data include the identifier of the Quality of Service (QoS) flow or the identifier of the Internet Protocol (IP) flow.

12. The method according to any one of claims 7 to 9, characterized in that, The request information also includes at least one of the following: a session identifier between the terminal and the network, or a connection identifier between the first functional entity and the access network.

13. A data transmission method, characterized in that, This method is applied to a first functional entity and access network equipment, including: The first functional entity sends a request message to the access network device. The request message includes a description of the first downlink data. The first downlink data is the downlink data that the first functional entity requests to be transmitted. The first functional entity is a function that transmits downlink data to the access network device. The description of the first downlink data includes at least one of the following: the identifier of the first downlink data or the size of the first downlink data. The access network device determines the second downlink data based on the description information of the first downlink data and the air interface transmission status of the access network device. The second downlink data is the entire set or a subset of the first downlink data. The air interface transmission status includes air interface transmission idle or air interface transmission congestion. The access network device sends a response message to the first functional entity. The response message includes authorization information for the second downlink data. The authorization information for the second downlink data includes at least one of the following: the identifier of the second downlink data or the size of the second downlink data.

14. The method as described in claim 13, characterized in that, The description information of the first downlink data also includes at least one of the following: the transmission period of the first downlink data, or the transmission time of the first downlink data.

15. The method as described in claim 13, characterized in that, The authorization information of the second downlink data also includes at least one of the following: the transmission time of the second downlink data, or the transmission period of the second downlink data.

16. The method according to any one of claims 13 to 15, characterized in that, The first functional entity sends a request message to the access network device, including: the first functional entity sends the request message to the access network device through a second functional entity, wherein the second functional entity is a function that manages the network bearer established between the terminal and the first functional entity; The access network device sending response information to the first functional entity includes: the access network device sending the response information to the first functional entity through the second functional entity.

17. The method according to any one of claims 13 to 15, characterized in that, The identifiers of the first downlink data and the second downlink data include the identifier of the Quality of Service (QoS) flow or the identifier of the Internet Protocol (IP) flow.

18. The method according to any one of claims 13 to 15, characterized in that, The request information also includes at least one of the following: a session identifier between the terminal and the network, or a connection identifier between the first functional entity and the access network.

19. A data transmission device, characterized in that, Includes a unit for performing the method as described in any one of claims 1 to 6.

20. A data transmission device, characterized in that, The device includes a processor and an interface circuit, the interface circuit being used to receive signals from other devices outside the device and transmit them to the processor or to send signals from the processor to other devices outside the device, the processor being used to implement the method as described in any one of claims 1 to 6 via logic circuits or executing code instructions.

21. A data transmission device, characterized in that, Includes units for performing the method as described in any one of claims 7 to 12.

22. A data transmission device, characterized in that, The device includes a processor and an interface circuit, the interface circuit being used to receive signals from other devices outside the device and transmit them to the processor or to send signals from the processor to other devices outside the device, the processor being used to implement the method as described in any one of claims 7 to 12 via logic circuits or executing code instructions.

23. A data transmission system, characterized in that, Includes the apparatus as described in claim 19 or 20, and the apparatus as described in claim 21 or 22.

24. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 6, or the method as described in any one of claims 7 to 12.

Images