Data transmission method and data transmission apparatus

Abstract

The present application relates to the technical field of communications, and provides a data transmission method and a data transmission apparatus. The method comprises: receiving a first message from a first core network element, the first message indicating a first quality of service (QoS) flow used for transmitting quality of experience (QoE) data; and transmitting first QoE data by means of the first QoS flow on the basis of the first message. In the method in embodiments of the present application, QoE data can be carried by means of a dedicated QoS flow, thereby ensuring timeliness of QoE data transmission.

Description

Methods and apparatus for transmitting data

[0001] This application claims priority to Chinese Patent Application No. 202510039182.1, filed on January 9, 2025, entitled “Method and Apparatus for Transmitting Data”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically to a method and apparatus for transmitting data. Background Technology

[0003] With the development of internet technology, audio and video communication has become an important part of people's daily lives and work. Due to the complexity and variability of the network environment, the quality of audio and video communication is often severely affected. Quality of experience (QoE) is an important indicator for measuring the quality of audio and video communication, and it can truly assess the user experience.

[0004] To improve user experience, QoE data can be reported to the network side. However, existing QoE reporting methods have some issues. Summary of the Invention

[0005] This application provides a method and apparatus for transmitting data, which can carry QoE data through a dedicated QoS stream, thereby ensuring the timeliness of QoE data transmission.

[0006] In a first aspect, a method for transmitting data is provided, the method being applied to a terminal device or a component in the terminal device (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), the method comprising:

[0007] Receive a first message from a first core network element, the first message indicating that a first Quality of Service (QoS) stream is used to transmit Quality of Experience (QoE) data; transmit the first QoE data through the first QoS stream according to the first message.

[0008] In this embodiment of the application, the first message indicates that the first QoS stream is used to transmit QoE data. The first QoE data is transmitted through the first QoS stream according to the first message, so that QoE data can be carried through a dedicated QoS stream, thereby ensuring the timeliness of QoE data transmission.

[0009] In some possible implementations, the first message is a session message.

[0010] In some possible implementations, the session message includes a Packet Data Unit (PDU) session establishment accept message or a PDU modification message.

[0011] In some possible implementations, the first message includes a mapping relationship between first information and the first QoS stream, wherein the first information is used to indicate the transmission of QoE data or to transmit QoE data corresponding to the first service.

[0012] In some possible implementations, the first information includes the destination address and / or destination port for transmitting QoE data.

[0013] In some possible implementations, the first message includes QoS flow description information, which is carried within the QoS flow description information.

[0014] In some possible implementations, the first message indicates that the first QoS stream is used to transmit QoE data of a first service type, wherein the first message further includes QoS rules for indicating the first service type.

[0015] In this embodiment of the application, the first message indicates that the first QoS stream is used to transmit QoE data of the first service type, so that the first QoE data of the first service type can be transmitted through the first QoS stream according to the first message. QoE data can be transmitted according to the characteristics of different services, providing differentiated transmission services for QoE data of different service types, thereby further ensuring the timeliness of QoE data transmission.

[0016] In some possible implementations, the first message contains QoS rules, and the first information is carried within the QoS rules.

[0017] In some possible implementations, the first service includes one of streaming services, voice services, or virtual reality (VR) services.

[0018] In some possible implementations, the method further includes: sending a second message to the first core network element, the second message being used to indicate whether the terminal device supports QoE data reporting.

[0019] In some possible implementations, the second message is a session request message.

[0020] In some possible implementations, the method further includes: receiving a third message from a second core network element, the third message indicating a method for collecting and / or reporting QoE data; wherein, transmitting data through the first QoS stream according to the first message includes: transmitting the first QoE data through the first QoS stream according to the first message and the third message.

[0021] In some possible implementations, the method of collecting and / or reporting QoE data includes one or more of the following: one-time data transmission, periodic data transmission, or a data transmission trigger event.

[0022] Secondly, a method for transmitting data is provided, the method being applied to a first core network element or a component within the first core network element (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), the method comprising:

[0023] A first message is determined, which indicates that a first Quality of Service (QoS) stream is used to transmit Quality of Experience (QoE) data; the first message is sent to the terminal device.

[0024] In this embodiment of the application, the first message is used to instruct the first QoS stream to be used for transmitting QoE data. Sending the first message to the terminal device helps the terminal device to carry QoE data through a dedicated QoS stream, thereby helping to ensure the timeliness of QoE data transmission.

[0025] In some possible implementations, the first message is a session message.

[0026] In some possible implementations, the session message includes a Packet Data Unit (PDU) session establishment accept message or a PDU modification message.

[0027] In some possible implementations, the first message includes a mapping relationship between first information and the first QoS stream, wherein the first information is used to indicate the transmission of QoE data or to transmit QoE data corresponding to the first service.

[0028] In some possible implementations, the first information includes the destination address and / or destination port for transmitting QoE data.

[0029] In some possible implementations, the first message includes QoS flow description information, which is carried within the QoS flow description information.

[0030] In some possible implementations, the first message indicates that the first QoS stream is used to transmit QoE data of a first service type, wherein the first message further includes QoS rules for indicating the first service type.

[0031] In the embodiments of this application, the first message indicates that the first QoS stream is used to transmit QoE data of the first service type, which helps the terminal device to transmit QoE data according to the characteristics of different services, and provides differentiated transmission services for QoE data of different service types, thereby helping to further ensure the timeliness of QoE data transmission.

[0032] In some possible implementations, the first message contains QoS rules, and the first information is carried within the QoS rules.

[0033] In some possible implementations, the first service includes one of streaming services, voice services, or virtual reality (VR) services.

[0034] In some possible implementations, the method further includes:

[0035] A second message is received from the terminal device, the second message being used to indicate whether the terminal device supports QoE data reporting.

[0036] In some possible implementations, the second message is a session request message.

[0037] In some possible implementations, the method further includes sending a fourth message to a second core network element, the fourth message being used to indicate whether the terminal device supports QoE data reporting.

[0038] Thirdly, a method for transmitting data is provided, the method being applied to a second core network element or a component within the second core network element (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), the method comprising:

[0039] A third message is identified, which indicates the method for collecting and / or reporting QoE data;

[0040] Send the third message to the terminal device.

[0041] In this embodiment, the third message is used to indicate the method of collecting and / or reporting QoE data. Sending the third message to the terminal device helps the terminal device transmit the first QoE data through the first QoS stream, so that the QoE data can be carried through a dedicated QoS stream, thereby helping to ensure the timeliness of QoE data transmission.

[0042] In some possible implementations, the method of collecting and / or reporting QoE data includes one or more of the following: one-time data transmission, periodic data transmission, or a data transmission trigger event.

[0043] In some possible implementations, the method further includes: receiving a fourth message from the first core network element, the fourth message being used to indicate whether the terminal device supports QoE data reporting.

[0044] Fourthly, a method for transmitting data is provided, the method being applied to a terminal device or a component in the terminal device (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), the method comprising:

[0045] Collect the first data to trigger reporting; perform a unified access control check and determine whether to report based on the access classification of the first data.

[0046] In this embodiment, determining whether to report based on the access classification of the first data can ensure that QoE data or AI data can be transmitted to the network as soon as possible in a congested environment, so that the network can adjust QoS as soon as possible, thereby ensuring the access classification of QoS data in a congested environment; or, the reporting of low-priority service data such as QoE data or AI data can be controlled in a congested environment to prevent congestion from escalating, thereby achieving the effect of flexible control.

[0047] In some possible implementations, the first data includes Quality of Experience (QoE) data or Artificial Intelligence (AI) data collected according to a certain configuration.

[0048] In some possible implementations, the method further includes: receiving second information from a first network device, the second information indicating whether access to the first network device is permitted or not; wherein, determining whether to report based on the access classification of the first data includes: determining whether to report based on the access classification of the first data and the second information.

[0049] In this embodiment, the second information is used to indicate whether access to the first network device is allowed or not. Receiving the second information and determining whether to report based on the access classification of the first data and the second information can ensure that QoE data or AI data can be transmitted to the network as quickly as possible in a congested environment, so that the network can adjust QoS as soon as possible, thereby ensuring the access classification of QoS data in a congested environment. Alternatively, the reporting of low-priority service data such as QoE data or AI data can be controlled in a congested environment to prevent congestion from escalating, thereby achieving a flexible control effect.

[0050] In some possible implementations, the services corresponding to the QoE data include streaming services, voice services, or virtual reality (VR) services.

[0051] In some possible implementations, the method further includes: receiving the fifth message from a first core network element, the fifth message being used to indicate the access classification of the QoE data.

[0052] In some possible implementations, the fifth message is a session message or a registration message.

[0053] In some possible implementations, the fifth message includes a Packet Data Unit (PDU) session establishment accept message or a PDU session modification accept message.

[0054] Fifthly, a method for transmitting data is provided, the method being applied to a first network device or a component in the first network device (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), the method comprising:

[0055] Send a second message to the terminal device, the second message being used to indicate whether access to the first network device is permitted or not, a first access category.

[0056] In this embodiment, the second information is used to indicate whether access to the first network device is allowed or not. Sending the second information to the terminal device facilitates the terminal device to determine whether to report based on the second information and the access classification of the first data. This helps ensure that QoE data or AI data can be transmitted to the network as quickly as possible in a congested environment, so that the network can adjust QoS as quickly as possible, thereby helping to protect the access classification of QoS data in a congested environment. Alternatively, it helps to control the reporting of low-priority service data such as QoE data or AI data in a congested environment, which helps to prevent congestion from escalating, thereby helping to achieve the effect of flexible control.

[0057] In a sixth aspect, a data transmission apparatus is provided, comprising: the data transmission apparatus can be used in a terminal device of the first aspect; the data transmission apparatus can be a terminal device, or a device in the terminal device (e.g., a chip, a chip system, a circuit, or a processor), or a device that can be used in conjunction with the terminal device, or a logic module or software that can implement all or part of the terminal device.

[0058] The data transmission apparatus includes modules that perform the methods / operations / steps / actions described in the first aspect or any possible implementation of the first aspect. These modules can be hardware circuits, software, or a combination of hardware circuits and software.

[0059] In a seventh aspect, a data transmission apparatus is provided, comprising: the data transmission apparatus can be used in a first core network element of the second aspect; the data transmission apparatus can be a first core network element, or a device in the first core network element (e.g., a chip, a chip system, a circuit, or a processor), or a device that can be used in conjunction with the first core network element, or a logic module or software that can implement all or part of the first core network element.

[0060] The data transmission device includes modules that perform the methods / operations / steps / actions described in the second aspect or any possible implementation of the second aspect. These modules can be hardware circuits, software, or a combination of hardware circuits and software.

[0061] Eighthly, a data transmission apparatus is provided, comprising: the data transmission apparatus can be used in a second core network element of the third aspect; the data transmission apparatus can be a second core network element, or a device in the second core network element (e.g., a chip, a chip system, a circuit, or a processor), or a device that can be used in conjunction with the second core network element, or a logic module or software that can implement all or part of the second core network element.

[0062] The data transmission device includes modules that perform the methods / operations / steps / actions described in the third aspect or any possible implementation of the third aspect. These modules can be hardware circuits, software, or a combination of hardware circuits and software.

[0063] In a ninth aspect, a data transmission apparatus is provided, comprising: the data transmission apparatus can be used in a terminal device of the fourth aspect; the data transmission apparatus can be a terminal device, or a device in the terminal device (e.g., a chip, or a chip system, or a circuit, or a processor), or a device that can be used in conjunction with the terminal device, or a logic module or software that can implement all or part of the terminal device.

[0064] The data transmission device includes modules that perform the methods / operations / steps / actions described in the fourth aspect or any possible implementation of the fourth aspect. These modules can be hardware circuits, software, or a combination of hardware circuits and software.

[0065] In a tenth aspect, a data transmission apparatus is provided, comprising: the data transmission apparatus can be used in a first network device of the fifth aspect; the data transmission apparatus can be the first network device, or a device in the first network device (e.g., a chip, a chip system, a circuit, or a processor), or a device that can be used in conjunction with the first network device, or a logic module or software that can implement all or part of the first network device.

[0066] The data transmission device includes modules that perform the methods / operations / steps / actions described in the fifth aspect or any possible implementation of the fifth aspect. These modules can be hardware circuits, software, or a combination of hardware circuits and software.

[0067] Eleventhly, an apparatus for transmitting data is provided, comprising: a processor and a memory, the processor being coupled to the memory, the memory being used to store a computer program (also referred to as code or instructions), the computer program being executed by the processor causing the apparatus to perform a method in any of the above aspects or any possible implementation thereof.

[0068] In some possible implementations, the device also includes a memory coupled to the processor.

[0069] In some possible implementations, there are one or more processors, and / or one or more memories.

[0070] In some possible implementations, the memory can be integrated with the processor, or the memory can be set up separately from the processor.

[0071] In a twelfth aspect, a computer-readable storage medium is provided, on which a computer program (also referred to as code or instructions) is stored, which, when run on a computer, causes the computer to perform the methods of any of the above aspects or any possible implementations of any of the above aspects.

[0072] In a thirteenth aspect, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the method in any of the foregoing aspects or any possible implementation thereof.

[0073] In a fourteenth aspect, a chip is provided, comprising: a processor and a memory, the memory for storing a computer program (also referred to as code or instructions), the processor for calling and running the computer program stored in the memory, such that an apparatus or device on which the chip is mounted performs the method of any of the above aspects or any possible implementation thereof. Attached Figure Description

[0074] Figure 1 is a schematic block diagram of a wireless communication system applicable to this application.

[0075] Figure 2 is a schematic diagram of the structure of a communication chip in an embodiment of this application.

[0076] Figure 3 is a schematic architecture diagram of a communication system applicable to an embodiment of this application.

[0077] Figure 4 is a schematic diagram of the network architecture of a communication system according to an embodiment of this application.

[0078] Figure 5 is a schematic diagram of a RAN-based QoE reporting in an embodiment of this application.

[0079] Figure 6 is a schematic diagram of an AF-based QoE reporting in an embodiment of this application.

[0080] Figure 7 is a schematic flowchart of a data transmission method provided in one embodiment of this application.

[0081] Figure 8 is a schematic flowchart of a data transmission method provided in another embodiment of this application.

[0082] Figure 9 is a schematic flowchart of a data transmission method provided in another embodiment of this application.

[0083] Figure 10 is a schematic flowchart of a method for transmitting data provided in another embodiment of this application.

[0084] Figure 11 is a schematic flowchart of a method for transmitting data provided in another embodiment of this application.

[0085] Figure 12 is a schematic flowchart of a data transmission method provided in another embodiment of this application.

[0086] Figure 13 is a schematic flowchart of a data transmission method provided in another embodiment of this application.

[0087] Figure 14 is a schematic structural diagram of a data transmission device provided in an embodiment of this application.

[0088] Figure 15 is a schematic structural diagram of a data transmission device provided in another embodiment of this application.

[0089] Figure 16 is a schematic structural diagram of a data transmission device provided in another embodiment of this application.

[0090] Figure 17 is a schematic structural diagram of a data transmission device provided in another embodiment of this application.

[0091] Figure 18 is a schematic structural diagram of a data transmission device provided in another embodiment of this application.

[0092] Figure 19 is a schematic structural diagram of an apparatus provided in one embodiment of this application. Detailed Implementation

[0093] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0094] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application merely 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, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or order of execution, and that "first," "second," etc., do not necessarily imply that they are different. It should be understood that in this application, descriptions such as "in the case of," "if," "when," "if," etc., can be used interchangeably.

[0095] The wireless communication system in this application can be various communication systems, such as 5th generation (5G) systems, new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, satellite and other non-terrestrial communication systems, and communication systems that integrate terrestrial and non-terrestrial communication. The technical solution provided in this application can also be applied to future communication systems.

[0096] The wireless communication system in this application can be various wireless communication systems, such as 5th generation (5G) systems, new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, satellite and other non-terrestrial communication systems, and communication systems that integrate terrestrial and non-terrestrial communication. The technical solution provided in this application can also be applied to future communication systems.

[0097] To facilitate understanding of the embodiments of this application, a wireless communication system applicable to the embodiments of this application will first be described with reference to FIG1. ​​As shown in FIG1, the wireless communication system includes a wireless access network 100. The wireless access network 100 may include at least one network device (FIG. 110a, 110b and 110c in FIG1), and may also include at least one terminal (FIG. 120a to 120g in FIG1).

[0098] The terminal device in this application embodiment may refer to user equipment (UE), station, access terminal, user unit, user station, mobile station, mobile station (MS), remote station, remote terminal, mobile terminal (MT), user terminal, terminal (or terminal device), wireless communication equipment, user agent or user device, etc., or a device used to provide voice or data connectivity to users, or an Internet of Things device. For example, terminal devices include handheld devices with wireless connection functions, vehicle-mounted devices, etc., but this application embodiment does not limit this. The terminal device in this application embodiment may be a mobile phone, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, large screen, vehicle-mounted device (e.g., car, bicycle, electric vehicle, airplane, ship, train, high-speed rail, etc.), wearable device (e.g., smartwatch, smart bracelet, pedometer, smart glasses, etc.), machine type communication (MTC) terminal device, terminal device in 5G network, or terminal device in future evolved public land mobile network (PLMN), etc., and is not limited to this in this application embodiment.The terminal device in the embodiments of this application may also be a tablet computer, a laptop computer, a handheld computer, a mobile internet device (MID), a virtual reality (VR) device, an augmented reality (AR) device, a point of sale (POS) machine, customer-premises equipment (CPE), a light UE, a reduced capability UE (RedCap UE), a wireless terminal in industrial control, a smart home device (e.g., a refrigerator, a television, an air conditioner, an electricity meter, etc.), a smart robot, a robotic arm, workshop equipment, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or a flying device (e.g., a smart robot, a hot air balloon, a drone, an airplane), etc. Terminal devices can also be vehicle devices, such as vehicle devices, vehicle modules, vehicle chips, on-board units (OBU), or telematics boxes (T-BOX). Terminal devices can also be other devices with terminal functions. For example, a terminal device can also be a device that plays a terminal function in device-to-device (D2D) communication.

[0099] In some implementations, the terminal device can be used to act as a base station. Optionally, the terminal device can act as a scheduling entity to provide sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) scenarios. For example, cellular phones and cars can communicate using sidelink signals, or cellular phones and smart home devices can communicate using sidelink signals without relaying communication signals through a base station.

[0100] The network device in this application embodiment can refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network, and can also be called a base station (BS). For example, the network device can be a NodeB, an evolved NodeB (eNodeB), a next-generation NodeB (gNB) in a 5G mobile communication system, a transmission reception point (TRP), an access point (AP), a network device in a non-terrestrial network (NTN) system (such as a satellite), a base station in a future mobile communication system or an access point (AP) in a WiFi system, a radio controller, relay station, access point, vehicle-mounted device, wearable device, or network device in other future evolved communication systems, etc.

[0101] In some implementations, multiple RAN nodes can collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, a RAN node (i.e., the network device in this application) can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). In different systems, CUs (or CU-CPs and CU-UPs), DUs, or RUs may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN) system, a CU can also be called an open CU (O-CU), a DU can also be called an open DU (O-DU), a CU-CP can also be called an O-CU-CP, a CU-UP can also be called an O-CU-UP, and a RU can also be called an O-RU. Any of the units among the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. It should be understood that this application does not limit the specific technology or specific device form used in the network equipment.

[0102] In some implementations, the network device can be fixed or mobile, and this application does not limit this. For example, a helicopter or drone can be configured as a mobile network device, and one or more cells can move according to the location of the mobile network device. In other examples, a helicopter or drone can be configured as a device to communicate with another network device.

[0103] In some implementations, network devices can be deployed on land or in the air, and this application does not limit this. For example, network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites.

[0104] In this embodiment, the terminal device or network device may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the specific structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment.

[0105] Furthermore, various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0106] Figure 2 is a schematic diagram of the structure of a communication chip according to an embodiment of this application. This communication chip can be applied to terminal devices.

[0107] As shown in Figure 2, the communication chip may include a baseband subsystem, a radio frequency subsystem, a power management subsystem, and peripherals (which may include storage, external interfaces, etc.). The functions of each part can be as follows:

[0108] Baseband subsystem: responsible for application layer processing, external interface functions, and Layer 3 (L3) / Layer 2 (L2) / Layer 1 (L1) communication protocol processing.

[0109] Radio Frequency Subsystem: The radio frequency front-end and antenna realize the conversion of spatial electromagnetic waves into electrical signals, as well as the required amplification, filtering and other functions to achieve excellent coverage; it connects with the baseband to complete the frequency conversion and nonlinear distortion correction of analog signals.

[0110] Power Management Subsystem: Provides power management functions for the baseband chip.

[0111] In subsequent embodiments, a wireless communication system is used as an example to describe the technical solutions of the embodiments of this application in detail. The wireless communication system applicable to the embodiments of this application is described below with reference to FIG3.

[0112] Figure 3 is a schematic architecture diagram of a communication system applicable to an embodiment of this application. The wireless communication system 300 may include:

[0113] Network elements for network slice selection function (NSSF), authentication server function (AUSF), network exposure function (NEF), policy control function (PCF), unified data management (UDM), unified data repository (UDR), network repository function (NRF), application function (AF), access and mobility management function (AMF), session management function (SMF), network slice specific authentication and authorization function (NSSAAF), edge application server discovery function (EASDF), service communication proxy (SCP), network slice admission control function (NSACF), radio access network (RAN) (which can be RAN or AN), and user plane functions. Functions, UPF network elements, etc.

[0114] In the aforementioned operator networks, the portion excluding the radio access network can be referred to as the core network. The following section introduces the various network elements of the core network.

[0115] An AF (Application Controller) network element is similar to an application server, interacting with other core network control plane elements and providing service capabilities. AF elements can exist for different application services and can be owned by operators or trusted third parties.

[0116] PCF network elements support a unified policy framework to manage network behavior and provide policy rules for network entities to implement.

[0117] UDM network elements are responsible for the management of user identifiers, contract data, authentication data, and the registration and management of user service network elements.

[0118] UPF network elements are modules in the core network that process data. Their main functions include: routing and forwarding data from the base station to the network, quality of service (QoS) control, and billing information statistics.

[0119] The AMF network element is responsible for UE authentication, authorization, registration, mobility management and connection management. For example, the AMF can interact with the RAN and UE through the N2 and N1 interfaces to complete functions such as registration, session establishment and mobility management.

[0120] The SMF network element is mainly responsible for session management, including managing the creation and deletion of user packet data unit (PDU) sessions, maintaining PDU session context and user plane forwarding pipeline information, allocating addresses to terminals, and managing various channels between terminals and the core network. For example, the SMF can control the UPF through the N4 interface.

[0121] The user plane function (UPF) entity's main functions include packet routing and forwarding, serving as a session anchor, acting as an uplink classifier to support routing traffic to the local data network, and serving as a branch point to support multi-homed PDU sessions.

[0122] The NWDAF network element can be responsible for security-related analysis. It should be noted that the security analysis function can also be performed by other network elements, and this embodiment of the application is not limited to this.

[0123] Data network (DN), such as carrier services, internet access, or third-party services.

[0124] The devices, network elements, or entities mentioned in this application can be interchanged in some scenarios.

[0125] In the architecture shown in Figure 3, some communication interfaces between network elements are marked as follows:

[0126] N1 interface: The interface between the terminal equipment and the core network control plane, used to transmit NAS signaling.

[0127] N2 interface: Communication interface between the wireless access network and the core network control plane.

[0128] N3 Interface: The communication interface between the radio access network and the user plane network element (UPF) of the core network, used for transmitting user data.

[0129] N4 Interface: The communication interface between the Control Plane Session Management (SMF) and the User Plane (UPF) is used for policy configuration of the UPF.

[0130] N6 interface: Communication interface between the core network user plane element UPF and DN.

[0131] It is understood that Figure 3 exemplarily illustrates the architecture of a communication system to which the methods provided in the embodiments of this application are applicable. The communication system to which the methods provided in the embodiments of this application are applicable may include other network elements or network entities, and this is not limited in the embodiments of this application.

[0132] Figure 4 is a schematic diagram of a network architecture applicable to an embodiment of this application. As shown in Figure 4, the wireless communication system 400 may include: a short message service function (SMSF) network element, a UE-policy control function (PCF) network element, an AMF network element, an SMF network element, a UPF network element, and a RAN network element (such as RAN, which can be CU), etc.

[0133] In Figure 4, the SMSF network element, UE-PCF network element, AMF network element, SMF network element, and UPF network element can all directly interact with the RAN network element.

[0134] With the development of internet technology, audio and video communication has become an important part of people's daily lives and work. Due to the complexity and variability of the network environment, the quality of audio and video communication is often severely affected. Quality of experience (QoE) is an important indicator for measuring the quality of audio and video communication, and it can truly assess the user experience.

[0135] To improve user experience, QoE data can be reported to the network side. However, existing QoE reporting methods have some issues.

[0136] For example, there are currently two ways to report QoE: RAN-based QoE reporting and AF-based QoE reporting.

[0137] As shown in Figure 5, RAN-based QoE reporting can be triggered by Operations, Administration and Maintenance (OAM) configuration. The QoE data collected by OAM is mainly used for operation and maintenance management. As shown in Figure 6, AF-based QoE reporting can be triggered by AF configuration and collected by the AF. This AF can be a Data Collection Application Function (DCAF) network element. Configuration distribution and QoE data collection are implemented through the M5 interface. The DCAF can establish a session with the UE data collection (DC) client. QoE data reported through these two methods can be provided to the Network Data Analytics Function (NWDAF) network element to assist NWDAF in analyzing service experience.

[0138] The user (consumer) of the NWDAF service experience analysis results can be the PCF. If the PCF finds that the service experience does not meet the service level agreement (SLA), it may determine new QoS parameters. When NWDAF analyzes the data for service experience, it may also need to refer to UE air interface performance measurement data obtained from OAM, such as reference signal received power (RSRP), reference signal received quality (RSRQ), and signal-to-interference-plus-noise ratio (SINR). In other words, in order to analyze the service experience results, NWDAF needs to obtain different data from different network nodes, such as obtaining QoE data from AF and UE air interface performance measurement data from OAM. Obtaining data from both requires AF or OAM to initiate QoE configuration reporting separately.

[0139] The above analysis shows that the existing QoE reporting methods involve a large number of network elements, resulting in a long and slow data collection chain. At the same time, the existing QoE reporting methods cannot provide differentiated transmission services for QoE data of different service types.

[0140] To address one or more of the aforementioned technical problems, this application proposes a method and apparatus for transmitting data. It should be noted that the solutions in the embodiments of this application are also applicable to the reporting of artificial intelligence (AI) data or other data (such as data that needs to be reported after the terminal device screen is off).

[0141] The following, with reference to Figures 7 to 11, takes QoE data reporting as an example to illustrate in detail the data transmission method in the embodiments of this application.

[0142] Figure 7 is a schematic flowchart of a data transmission method provided in an embodiment of this application. The method 700 shown in Figure 7 may include steps S710, S720, and S730, as detailed below:

[0143] S710, the first core network element determines the first message, which can be used to indicate the first QoS flow for transmitting QoE data.

[0144] The first core network element can be an SMF network element or another core network element.

[0145] In some embodiments, the first message may include first information, which may be used to indicate the transmission of QoE data or to transmit QoE data corresponding to a first service. The first service may include one of streaming services, voice services, or virtual reality (VR) services.

[0146] QoE data for different services can contain different content. For example, QoE data for dynamic adaptive streaming (DASH), QoE data for 5G multimedia subsystem (MS), and QoE data for VR can include one or more of the following: representation switch events, average throughput, initial playout delay, buffer level, playlist, MPD information, playout delay for media start-up, or device information.

[0147] In some embodiments, the first message may include a mapping relationship between first information and a first QoS stream.

[0148] For example, the first message may include a mapping relationship between the first information and the QoS flow identifier (QFI) of the first QoS flow.

[0149] In some embodiments, the first information may include the destination address and / or destination port for transmitting data (such as QoE data).

[0150] For example, the first piece of information can include the address of the NWDAF network element or its identifier. When multiple data types (QoE data or AI data used for training models) need to be reported to the NWDAF, the data types can be distinguished by the destination port. The destination address and destination port can be sent to the terminal device over the network. When the terminal device encapsulates a specific data type, it can encapsulate the destination address and destination port corresponding to that specific data type.

[0151] In some embodiments, the first message may include QoS flow description information, and the first information may be carried in the QoS flow description information.

[0152] In some embodiments, the first message may include a QoS rule, and the first information may be carried in the QoS rule.

[0153] In some embodiments, a new field can be defined in the first message, which may contain first information or a mapping relationship between the first information and the first QoS flow.

[0154] For example, a new information element (IE) can be defined in the session message, which can contain the mapping relationship between the first information and the first QoS stream.

[0155] In some embodiments, the first message may indicate that the first QoS stream is used to transmit QoE data of a first service type.

[0156] For example, the QoS flow description information in the first message can carry the first information, and the QoS rules in the first message can indicate the first service type; or, the QoS flow description information in the first message can carry the first information and indicate the first service type; or, the QoS rules in the first message can carry the first information and indicate the first service type; or, a new field can be defined in the first message, which can carry the first information and indicate the first service type.

[0157] S720: The first core network element sends the first message to the terminal device.

[0158] The first message can be a session message or any other message.

[0159] For example, the first message can be a PDU session establishment accept message or a PDU modification message.

[0160] S730, the terminal device transmits the first QoE data through the first QoS stream according to the first message.

[0161] For example, the terminal device can map the first QoE data to the first QoS stream according to the 5-tuple information corresponding to the QFI (indicated by the first message) so as to report the first QoE data to the network side; or, the terminal device can map the first QoE data to the first QoS stream according to the destination address and / or destination port (indicated by the first message) so as to report the first QoE data to the network side.

[0162] In some embodiments, before step S730, the terminal device may send a second message to the first core network element. The second message may be used to indicate whether the terminal device supports QoE data reporting, and may also indicate the data types supported by the terminal device (such as the data types of data collected and / or reported supported by the terminal device), and may also indicate the methods of data collection and / or reporting supported by the terminal device.

[0163] The second message can be a session request message. For example, the second message can be a PDU session establishment request message.

[0164] In some embodiments, upon receiving the second message, the first core network element may send a fourth message to the second core network element. The fourth message may be used to indicate whether the terminal device supports QoE data reporting, and may also indicate the data types supported by the terminal device (such as the data types collected and / or reported by the terminal device), and the methods of collecting and / or reporting data supported by the terminal device.

[0165] In some embodiments, prior to step S730, the second core network element may determine a third message. The third message may be used to indicate the type of data collected and / or reported by the terminal device, and / or the manner in which the terminal device collects and / or reports data. For example, the third message may be used to indicate the manner in which QoE data is collected and / or reported.

[0166] Optionally, upon receiving a fourth message, the second core network element can determine a third message based on the fourth message. For example, the second core network element can determine the third message based on the data types supported by the terminal device (such as the data types collected and / or reported by the terminal device) and / or the methods of collecting and / or reporting data supported by the terminal device.

[0167] The second core network element can be NWDAF.

[0168] In some embodiments, the second core network element can send a third message to the terminal device. Optionally, the second core network element can send a third message to the terminal device through the first core network element.

[0169] During transmission, the first core network element itself may be unaware of the third message (i.e., transmit the third message transparently) or it may be aware of the third message (i.e., parse the third message and reassemble and encapsulate it).

[0170] For example, NWDAF can send a third message to SMF, and then SMF can send the third message to the terminal device; or, NWDAF can send a third message to SMF, SMF can parse the content carried by the third message, re-encapsulate the content, and send the re-encapsulated third message to the terminal device.

[0171] In some embodiments, upon receiving a third message, the terminal device may transmit first QoE data via a first QoS stream based on the first message and the third message.

[0172] The methods for collecting and / or reporting QoE data may include one or more of the following: one-time data transmission, periodic data transmission, data transmission triggering events, or corresponding data transmission types.

[0173] In some embodiments, prior to step S730, the first core network element may send a message to the third core network element instructing the first QoS flow to be used for transmitting QoE data. The third core network element may be a UPF element or other core network elements.

[0174] In some embodiments, before step S730, the second core network element sends a subscription message to the first core network element to subscribe to the PDU creation event.

[0175] In this embodiment of the application, the first message indicates that the first QoS stream is used to transmit QoE data. The first QoE data is transmitted through the first QoS stream according to the first message, so that QoE data can be carried through a dedicated QoS stream, thereby ensuring the timeliness of QoE data transmission.

[0176] The method for transmitting data in the embodiments of this application will be described in detail below with reference to Figures 8 to 11.

[0177] Figure 8 is a schematic flowchart of a data transmission method provided in an embodiment of this application. The method 800 shown in Figure 8 may include steps S801 to S808, as follows:

[0178] S801, NWDAF sends a subscription message to SMF.

[0179] The message subscription is used to subscribe to PDU creation events. It should be noted that step S801 is optional.

[0180] S802, the UE sends a PDU session establishment request message to the SMF.

[0181] PDU session establishment request messages can carry UE capability information, which can indicate whether the UE supports QoE data reporting.

[0182] For a detailed description of the PDU session establishment request message, please refer to the second message in the embodiment of method 700 above, which will not be repeated here.

[0183] Upon receiving a PDU session establishment request message, the SMF can generate a QoS profile based on the UE capability information.

[0184] For example, a QoS profile can have only one value, and this QoS stream is used to transmit all QoE data; or, a QoS profile can have multiple values, and different QoS profiles can correspond to QoE data from different services.

[0185] S803, SMF reports UE capability information to NWDAF.

[0186] S804, SMF sends a PDU session establishment accept message to UE.

[0187] PDU session establishment accept messages can be used to indicate that a specific QoS stream is used to transmit QoE data.

[0188] For example, the PDU session establishment acceptance message may carry a QoS flow identifier (QFI), which can be used to indicate a specific QoS flow; or, the PDU session establishment acceptance message may include first information, which can be used to indicate the transmission of QoE data or to transmit QoE data corresponding to a first service; or, the PDU session establishment acceptance message may include a mapping relationship between the first information and the QFI.

[0189] The PDU session establishment accept message may include QoS flow description information and / or QoS rules, and may also include newly defined fields.

[0190] For a detailed description of the PDU session establishment and message acceptance process, please refer to the first message in the embodiment of method 700 above, which will not be repeated here. The execution order of S803 and S804 above is only illustrative and not limiting; there is no necessary order between S803 and S804.

[0191] Optionally, the SMF can also instruct the UPF to use a specific QoS stream for transmitting QoE data.

[0192] S805, SMF sends a QoS profile to RAN.

[0193] SMF can send the QoS profile to RAN via N2 messages.

[0194] S806, NWDAF sends QoE configuration to UE.

[0195] QoE configuration can be used to indicate how QoE data is collected and / or reported. Methods for collecting and / or reporting QoE data can include one or more of the following: one-time data transfer, periodic data transfer, a data transfer trigger event, or the corresponding data transfer type.

[0196] For a detailed description of the QoE configuration, please refer to the third message in the embodiment of method 700 above, which will not be repeated here.

[0197] For example, the NWDAF can send the QoE configuration to the SMF, and then the SMF can send the QoE configuration to the UE via the PDU session modification message.

[0198] For a detailed description of NWDAF sending QoE configuration to UE via SMF, please refer to the embodiment of the second core network element sending a third message to the terminal device via the first core network element in method 700 above, which will not be repeated here.

[0199] S807, the UE collects QoE data according to the QoE configuration.

[0200] The content of the QoE data can be found in the description of the embodiments of method 700 above, and will not be repeated here.

[0201] S808, the UE reports QoE data to the NWDAF.

[0202] For example, the UE can send QoE data to the UPF through a specific QoS flow, and then the UPF can send QoE data to the NWDAF.

[0203] Figure 9 is a schematic flowchart of a data transmission method provided in an embodiment of this application. The method 900 shown in Figure 9 may include steps S901 to S908, as follows:

[0204] S901, NWDAF sends a subscription message to SMF.

[0205] The message subscription is used to subscribe to PDU creation events. It should be noted that step S901 is optional.

[0206] S902, the UE sends a PDU session establishment request message to the SMF.

[0207] PDU session establishment request messages can carry UE capability information, which can indicate whether the UE supports QoE data reporting.

[0208] For a detailed description of the PDU session establishment request message, please refer to the second message in the embodiment of method 700 above, which will not be repeated here.

[0209] Upon receiving a PDU session establishment request message, the SMF can generate a QoS profile based on the UE capability information.

[0210] For example, a QoS profile can have only one value, and this QoS stream is used to transmit all QoE data; or, a QoS profile can have multiple values, and different services can correspond to different QoS profiles.

[0211] S903, SMF reports UE capability information to NWDAF.

[0212] S904, SMF sends a PDU session establishment accept message to UE.

[0213] PDU session establishment accept messages can be used to indicate that a specific QoS stream is used to transmit QoE data.

[0214] For example, the PDU session establishment acceptance message may carry a QoS flow identifier (QFI), which can be used to indicate a specific QoS flow; or, the PDU session establishment acceptance message may include first information, which can be used to indicate the transmission of QoE data or to transmit QoE data corresponding to a first service; or, the PDU session establishment acceptance message may include a mapping relationship between the first information and the QFI.

[0215] The PDU session establishment accept message may include QoS flow description information and / or QoS rules, and may also include newly defined fields.

[0216] For a detailed description of the PDU session establishment and acceptance message, please refer to the first message in the embodiment of method 700 above, which will not be repeated here.

[0217] Optionally, the SMF can also instruct the UPF to use a specific QoS stream for transmitting QoE data.

[0218] S905, SMF sends a QoS profile to RAN.

[0219] SMF can send the QoS profile to RAN via N2 messages.

[0220] S906, NWDAF sends QoE configuration to UE.

[0221] QoE configuration can be used to indicate how QoE data is collected and / or reported. Methods for collecting and / or reporting QoE data can include one or more of the following: one-time data transfer, periodic data transfer, a data transfer trigger event, or the corresponding data transfer type.

[0222] For a detailed description of the QoE configuration, please refer to the third message in the embodiment of method 700 above, which will not be repeated here.

[0223] For example, the NWDAF can send QoE configuration to the AMF via the N1 transmission message, and then the AMF can send QoE configuration to the UE via the downlink (DL) transmission message or the registration accept message.

[0224] S907, the UE collects QoE data according to the QoE configuration.

[0225] The content of the QoE data can be found in the description of the embodiments of method 700 above, and will not be repeated here.

[0226] S908, the UE reports QoE data to the NWDAF.

[0227] For example, the UE can send QoE data to the UPF through a specific QoS flow, and then the UPF can send QoE data to the NWDAF.

[0228] Figure 10 is a schematic flowchart of a data transmission method provided in an embodiment of this application. The method 1000 shown in Figure 10 may include steps S1001 to S1008, as follows:

[0229] S1001, NWDAF sends a subscription message to SMF.

[0230] Subscribing to messages is used to subscribe to PDU creation events. It should be noted that step S1001 is optional.

[0231] S1002, the UE sends a PDU session establishment request message to the SMF.

[0232] PDU session establishment request messages can carry UE capability information, which can indicate whether the UE supports QoE data reporting.

[0233] For a detailed description of the PDU session establishment request message, please refer to the second message in the embodiment of method 700 above, which will not be repeated here.

[0234] Upon receiving a PDU session establishment request message, the SMF can generate a QoS profile based on the UE capability information.

[0235] For example, a QoS profile can have only one value, and this QoS stream is used to transmit all QoE data; or, a QoS profile can have multiple values, and different services can correspond to different QoS profiles.

[0236] S1003, SMF reports UE capability information to NWDAF.

[0237] S1004, NWDAF sends QoE configuration to SMF.

[0238] QoE configuration can be used to indicate how QoE data is collected and / or reported. Methods for collecting and / or reporting QoE data can include one or more of the following: one-time data transfer, periodic data transfer, a data transfer trigger event, or the corresponding data transfer type.

[0239] For a detailed description of the QoE configuration, please refer to the third message in the embodiment of method 700 above, which will not be repeated here.

[0240] S1005, SMF sends a PDU session establishment accept message to UE.

[0241] PDU session establishment accept messages can be used to indicate that a specific QoS stream is used to transmit QoE data.

[0242] For example, the PDU session establishment acceptance message may carry a QoS flow identifier (QFI), which can be used to indicate a specific QoS flow; or, the PDU session establishment acceptance message may include first information, which can be used to indicate the transmission of QoE data or to transmit QoE data corresponding to a first service; or, the PDU session establishment acceptance message may include a mapping relationship between the first information and the QFI.

[0243] The PDU session establishment accept message may include QoS flow description information and / or QoS rules, and may also include newly defined fields.

[0244] For a detailed description of the PDU session establishment and acceptance message, please refer to the first message in the embodiment of method 700 above, which will not be repeated here.

[0245] PDU session establishment and acceptance messages can also carry QoE configuration.

[0246] Optionally, the SMF can also instruct the UPF to use a specific QoS stream for transmitting QoE data.

[0247] S1006, SMF sends a QoS profile to RAN.

[0248] SMF can send the QoS profile to RAN via N2 messages.

[0249] S1007, the UE collects QoE data according to the QoE configuration.

[0250] The content of the QoE data can be found in the description of the embodiments of method 700 above, and will not be repeated here.

[0251] S1008, the UE reports QoE data to the NWDAF.

[0252] For example, the UE can send QoE data to the UPF through a specific QoS flow, and then the UPF can send QoE data to the NWDAF.

[0253] Figure 11 is a schematic flowchart of a data transmission method provided in an embodiment of this application. The method 1100 shown in Figure 11 may include steps S1101 to S1107, as follows:

[0254] S1101, NWDAF sends a subscription message to SMF.

[0255] Subscribing to messages is used to subscribe to PDU creation events. It should be noted that step S1001 is optional.

[0256] S1102, the UE sends a PDU session establishment request message to the SMF.

[0257] PDU session establishment request messages can carry UE capability information, which can indicate whether the UE supports QoE data reporting.

[0258] For a detailed description of the PDU session establishment request message, please refer to the second message in the embodiment of method 700 above, which will not be repeated here.

[0259] Upon receiving a PDU session establishment request message, the SMF can generate a QoS profile based on the UE capability information.

[0260] For example, a QoS profile can have only one value, and this QoS stream is used to transmit all QoE data; or, a QoS profile can have multiple values, and different services can correspond to different QoS profiles.

[0261] S1103, SMF sends an instruction message to UPF.

[0262] This indication message can be used to indicate that a specific QoS flow is used to transmit QoE data. The content indicated by this indication message can be referred to in the PDU session establishment accept message in step S1104 below.

[0263] S1104, SMF sends a PDU session establishment accept message to UE.

[0264] PDU session establishment accept messages can be used to indicate that a specific QoS stream is used to transmit QoE data.

[0265] For example, the PDU session establishment acceptance message may carry a QoS flow identifier (QFI), which can be used to indicate a specific QoS flow; or, the PDU session establishment acceptance message may include first information, which can be used to indicate the transmission of QoE data or to transmit QoE data corresponding to a first service; or, the PDU session establishment acceptance message may include a mapping relationship between the first information and the QFI.

[0266] The PDU session establishment accept message may include QoS flow description information and / or QoS rules, and may also include newly defined fields.

[0267] For a detailed description of the PDU session establishment and acceptance message, please refer to the first message in the embodiment of method 700 above, which will not be repeated here.

[0268] S1105, SMF sends a new PDU event notification message to NWDAF.

[0269] The new PDU event notification message can carry initial information and / or UE capability information.

[0270] NWDAF can send QoE configuration to the UE in two ways, as follows:

[0271] Method 1: Send via service-based interface.

[0272] S1106-1, NWDAF sends a message to UE to subscribe to the measurement report of QoE.

[0273] Measurement reports from QoE subscriptions can carry QoE configurations.

[0274] Upon receiving a measurement report from a QoE subscription, the UE can collect QoE data according to the QoE configuration.

[0275] The content of the QoE data can be found in the description of the embodiments of method 700 above, and will not be repeated here.

[0276] S1107-1, the UE sends a QoE measurement report to the NWDAF.

[0277] QoE measurement reports can carry QoE data.

[0278] Method 2: Send a message.

[0279] S1106-2, NWDAF sends a specific message to UE.

[0280] Specific messages can carry QoE configuration. These specific messages can be newly defined messages or existing messages; this application embodiment does not limit this.

[0281] Upon receiving the QoE configuration, the UE can collect QoE data according to the QoE configuration.

[0282] The content of the QoE data can be found in the description of the embodiments of method 700 above, and will not be repeated here.

[0283] S1107-2, the UE reports QoE data to the NWDAF.

[0284] For example, the UE can send QoE data to the NWDAF through a newly defined message; or, the UE can send QoE data to the NWDAF through an existing message.

[0285] Figure 12 is a schematic flowchart of a data transmission method provided in an embodiment of this application. The method 1200 shown in Figure 12 may include steps S1210 and S1220, as follows:

[0286] S1210, the terminal device collects the first data and triggers the report.

[0287] In some embodiments, the first data may include QoE data collected according to a certain configuration, artificial intelligence (AI) data (such as AI data used to train models), or some data that needs to be reported after the (terminal device) screen is turned off.

[0288] The services corresponding to QoE data can include streaming services, voice services, or virtual reality (VR) services.

[0289] It should be noted that in step S1210 above, triggering the reporting can be understood as triggering the reporting process. In step S1220 below, the terminal device also needs to determine whether to report. Therefore, triggering the reporting process does not necessarily mean that data will be reported.

[0290] S1220, the terminal device performs a unified access control (UAC) check and determines whether to report based on the access category (AC) of the first data.

[0291] In some embodiments, a correspondence between services and access categories can be pre-defined, and the access category of the first data can be determined based on this correspondence and the service corresponding to the first data. For example, a table (as shown in Table 1 below) can be pre-defined, which can contain multiple services and their corresponding access categories. The terminal device can determine the access category of the first data based on the table and the service corresponding to the first data.

[0292] Table 1. Correspondence between services and access categories

[0293] Alternatively, the first core network element can indicate the access classification of the first data to the terminal device. For example, the first core network element can send a fifth message, which can be used to indicate the access classification of QoE data.

[0294] The fifth message can be a session message, a registration message, or other types of messages. For example, the fifth message can be a PDU session establishment acceptance message or a PDU modification message.

[0295] In some embodiments, prior to step S1220, the terminal device may receive second information from the first network device, which may be used to indicate a first access classification that allows or disallows access to the first network device.

[0296] For example, the first network device can be an access network device, and the first network device can broadcast second information. Correspondingly, the terminal device can receive the second information broadcast by the first network device.

[0297] In some embodiments, in step S1220 above, upon receiving the second information, the terminal device can determine whether to report based on the access classification of the first data and the second information.

[0298] In this embodiment, determining whether to report based on the access classification of the first data can ensure that QoE data or AI data can be transmitted to the network as soon as possible in a congested environment, so that the network can adjust QoS as soon as possible, thereby ensuring the access classification of QoS data in a congested environment; or, the reporting of low-priority service data such as QoE data or AI data can be controlled in a congested environment to prevent congestion from worsening, thereby achieving the purpose of flexible adjustment.

[0299] The method for transmitting data in the embodiments of this application will be described in detail below with reference to Figure 14.

[0300] Figure 13 is a schematic flowchart of a data transmission method provided in an embodiment of this application. The method 1300 shown in Figure 13 may include steps S1301 to S1306, as follows:

[0301] S1301, RAN broadcasts second information.

[0302] The second piece of information can indicate the access classification that the RAN allows or disallows.

[0303] For a detailed description of the second information, please refer to the second information in the embodiment of the above method 1200, which will not be repeated here.

[0304] S1302, the UE performs QoE data or AI data collection and triggers the data reporting process.

[0305] S1303, UE determines the access category of QoE data or AI data.

[0306] The UE determines the access classification of QoE data by mapping the data type of the QoE data to the access classification.

[0307] For the method of determining the access classification of QoE data, please refer to step S1220 in the embodiment of the above method 1200, which will not be repeated here.

[0308] S1304, the UE determines whether to report data based on the access category corresponding to the second information and the QoE data or AI data.

[0309] If the data to be reported is determined, the UE can report QoE data or AI data in three ways, as follows:

[0310] Method 1:

[0311] S1305-1, the UE sends an activation message to the AMF to activate the PDU session.

[0312] S1306-1, the UE reports QoE data or AI data to the UPF through the PDU session.

[0313] Method 2:

[0314] S1305-2, the UE sends an activation message to the SMF to establish a PDU session.

[0315] S1306-2, the UE reports QoE data or AI data to the UPF through the PDU session.

[0316] Method 3:

[0317] S1305-3, UE reports QoE data or AI data to RAN.

[0318] It should be noted that the steps or the order of execution of the steps included in the above embodiments are merely examples and not limitations. The embodiments of this application may include more or fewer steps, or may include other steps. At the same time, the above steps may be executed in other orders, and this application does not limit this.

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

[0320] Figure 14 is a schematic structural diagram of a data transmission device provided in an embodiment of this application. The data transmission device 1400 shown in Figure 14 can be used in the terminal device in the foregoing embodiments. The data transmission device 1400 can be a terminal device, or a device in the terminal device (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), or a device that can be used in conjunction with the terminal device, or a logic module or software that can implement all or part of the terminal device.

[0321] As shown in Figure 14, the data transmission device 1400 includes a receiving unit 1410 and a transmission unit 1420, as detailed below:

[0322] The receiving unit 1410 is configured to receive a first message from a first core network element, wherein the first message indicates that a first Quality of Service (QoS) stream is used to transmit Quality of Experience (QoE) data.

[0323] The transmission unit 1420 is used to transmit first QoE data through the first QoS stream according to the first message.

[0324] Optionally, the first message is a session message.

[0325] Optionally, the session message includes a Packet Data Unit (PDU) session establishment accept message or a PDU modification message.

[0326] Optionally, the first message includes a mapping relationship between first information and the first QoS stream, wherein the first information is used to indicate the transmission of QoE data or to transmit QoE data corresponding to the first service.

[0327] Optionally, the first information includes the destination address and / or destination port for transmitting data.

[0328] Optionally, the first message includes QoS flow description information, and the first information is carried in the QoS flow description information.

[0329] Optionally, the first message indicates that the first QoS stream is used to transmit QoE data of a first service type, wherein the first message further includes QoS rules, the QoS rules being used to indicate the first service type.

[0330] Optionally, the first message contains QoS rules, and the first information is carried in the QoS rules.

[0331] Optionally, the first service includes one of streaming services, voice services, or virtual reality (VR) services.

[0332] Optionally, the device 1400 further includes a sending unit 1430, configured to: send a second message to the first core network element, the second message being used to indicate whether the terminal device supports QoE data reporting.

[0333] Optionally, the second message is a session request message.

[0334] Optionally, the receiving unit 1410 is further configured to: receive a third message from a second core network element, the third message being used to indicate the method of collecting and / or reporting QoE data; wherein, the transmitting unit 1420 is specifically configured to: transmit the first QoE data through the first QoS stream according to the first message and the third message.

[0335] Optionally, the method of collecting and / or reporting QoE data includes one or more of the following: one-time data transmission, periodic data transmission, or a data transmission trigger event.

[0336] Figure 15 is a schematic structural diagram of a data transmission device provided in an embodiment of this application. The data transmission device 1500 shown in Figure 15 can be used in the first core network element in the foregoing embodiments. The data transmission device 1500 can be the first core network element, or a device in the first core network element (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), or a device that can be matched with the first core network element, or a logic module or software that can implement all or part of the first core network element.

[0337] As shown in Figure 15, the data transmission device 1500 includes a determining unit 1510 and a sending unit 1520, as detailed below:

[0338] Determining unit 1510 is used to determine a first message, the first message being used to indicate that a first Quality of Service (QoS) stream is used to transmit Quality of Experience (QoE) data;

[0339] The sending unit 1520 is used to send the first message to the terminal device.

[0340] Optionally, the first message is a session message.

[0341] Optionally, the session message includes a Packet Data Unit (PDU) session establishment accept message or a PDU modification message.

[0342] Optionally, the first message includes a mapping relationship between first information and the first QoS stream, wherein the first information is used to indicate the transmission of QoE data or to transmit QoE data corresponding to the first service.

[0343] Optionally, the first information includes the destination address and / or destination port for transmitting data.

[0344] Optionally, the first message includes QoS flow description information, and the first information is carried in the QoS flow description information.

[0345] Optionally, the first message indicates that the first QoS stream is used to transmit QoE data of a first service type, wherein the first message further includes QoS rules, the QoS rules being used to indicate the first service type.

[0346] Optionally, the first message contains QoS rules, and the first information is carried in the QoS rules.

[0347] Optionally, the first service includes one of streaming services, voice services, or virtual reality (VR) services.

[0348] Optionally, the device 1500 further includes a receiving unit 1530, configured to: receive a second message from the terminal device, the second message being used to indicate whether the terminal device supports QoE data reporting.

[0349] Optionally, the second message is a session request message.

[0350] Optionally, the sending unit 1520 is further configured to: send a fourth message to the second core network element, the fourth message being used to indicate whether the terminal device supports QoE data reporting.

[0351] Figure 16 is a schematic structural diagram of a data transmission device provided in an embodiment of this application. The data transmission device 1600 shown in Figure 16 can be used in the second core network element in the foregoing embodiments. The data transmission device 1600 can be the second core network element, or a device in the second core network element (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), or a device that can be used in conjunction with the second core network element, or a logic module or software that can implement all or part of the second core network element.

[0352] As shown in Figure 16, the data transmission device 1600 includes a determining unit 1610 and a sending unit 1620, as detailed below:

[0353] The determining unit 1610 is used to determine a third message, the third message being used to indicate the method of collecting and / or reporting QoE data;

[0354] The sending unit 1620 is used to send the third message to the terminal device.

[0355] Optionally, the method of collecting and / or reporting QoE data includes one or more of the following: one-time data transmission, periodic data transmission, or a data transmission trigger event.

[0356] Optionally, the device 1600 further includes a receiving unit 1630, which is also configured to: receive a fourth message from the first core network element, the fourth message being used to indicate whether the terminal device supports QoE data reporting.

[0357] Figure 17 is a schematic structural diagram of a data transmission device provided in an embodiment of this application. The data transmission device 1700 shown in Figure 17 can be used in the terminal device in the foregoing embodiments. The data transmission device 1700 can be a terminal device, or a device in the terminal device (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), or a device that can be used in conjunction with the terminal device, or a logic module or software that can implement all or part of the terminal device.

[0358] As shown in Figure 17, the data transmission device 1700 includes a collection unit 1710 and a determination unit 1720, as detailed below:

[0359] Collection unit 1710 is used to collect the first data to trigger reporting;

[0360] The determination unit 1720 is used to perform unified access control checks and determine whether to report based on the access classification of the first data.

[0361] Optionally, the first data includes Quality of Experience (QoE) data or Artificial Intelligence (AI) data collected according to a certain configuration.

[0362] Optionally, the device 1700 further includes a receiving unit 1730, configured to: receive second information from the first network device, the second information being used to indicate a first access category that allows or disallows access to the first network device;

[0363] Specifically, the determining unit 1720 is used to: determine whether to report based on the access classification of the first data and the second information.

[0364] Optionally, the services corresponding to the QoE data include streaming services, voice services, or virtual reality (VR) services.

[0365] Optionally, the device 1700 further includes a receiving unit 1730, configured to: receive the fifth message from a first core network element, the fifth message being used to indicate the access classification of the QoE data.

[0366] Optionally, the fifth message is a session message.

[0367] Optionally, the fifth message includes a Packet Data Unit (PDU) session establishment acceptance message or a PDU session modification acceptance message.

[0368] Figure 18 is a schematic structural diagram of a data transmission device provided in an embodiment of this application. The data transmission device 1800 shown in Figure 18 can be used in the first network device in the foregoing embodiments. The data transmission device 1800 can be the first network device, or a device in the first network device (e.g., a processor, chip, chip system, circuit, or a functional module, etc.), or a device that can be used in conjunction with the first network device, or a logic module or software that can implement all or part of the first network device.

[0369] As shown in Figure 18, the data transmission device 1800 includes a transmitting unit 1810, as detailed below:

[0370] The sending unit 1810 is used to send second information to the terminal device, the second information being used to indicate whether access to the first network device is allowed or not.

[0371] Figure 19 is a schematic structural diagram of an apparatus provided in an embodiment of this application. The dashed lines in Figure 19 indicate that the unit or module is optional. This apparatus 1900 can be used to implement the methods described in the above method embodiments. Apparatus 1900 can be a chip or a data transmission device.

[0372] Apparatus 1900 may include one or more processors 1910. The processor 1910 may support apparatus 1900 in implementing the methods described in the preceding method embodiments. The processor 1910 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, microprocessor units (MPUs), microcontroller units (MCUs), graphics processing units (GPUs), artificial intelligence processors (AI processors) or neural processing units (NPUs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0373] The device 1900 may also include one or more memories 1920. The memories 1920 store a program that can be executed by the processor 1910, causing the processor 1910 to perform the methods described in the preceding method embodiments. The memories 1920 may be independent of the processor 1910 or integrated within the processor 1910. In this embodiment, the memories 1920 may include, but are not limited to, cache, read-only memory (ROM), random access memory (RAM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc.

[0374] The device 1900 may also include a transceiver 1930. The processor 1910 can communicate with other devices or chips via the transceiver 1930. For example, the processor 1910 can send and receive data with other devices or chips via the transceiver 1930.

[0375] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0376] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0377] This application also provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the steps described in the various method embodiments above.

[0378] This application also provides a computer program product, which includes a computer program that, when run on a computer, causes the computer to perform the steps described in the various method embodiments above.

[0379] This application also provides a chip, which includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that a device or apparatus (such as a data transmission device) on which the chip is installed performs the steps in the various method embodiments described above.

[0380] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or some intermediate form. The computer-readable storage medium can include at least: any entity or device capable of carrying computer program code to a device / app, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some possible implementations, the computer-readable storage medium may not be an electrical carrier signal or a telecommunication signal.

[0381] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0382] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

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

[0385] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for transmitting data, characterized in that, The method is applied to a terminal device, and the method includes: Receive a first message from a first core network element, the first message indicating that a first Quality of Service (QoS) stream is used to transmit Quality of Experience (QoE) data; Based on the first message, the first QoE data is transmitted through the first QoS stream.

2. The method according to claim 1, characterized in that, The first message includes a mapping relationship between first information and the first QoS stream, wherein the first information is used to indicate the transmission of QoE data or to transmit QoE data corresponding to the first service.

3. The method according to claim 1, characterized in that, The first information includes the destination address and / or destination port for transmitting QoE data.

4. The method according to claim 2 or 3, characterized in that, The first message contains QoS flow description information, and the first information is carried in the QoS flow description information.

5. The method according to claim 4, characterized in that, The first message indicates that the first QoS stream is used to transmit QoE data of a first service type, wherein the first message further includes QoS rules, the QoS rules being used to indicate the first service type.

6. The method according to claim 2 or 5, characterized in that, The first service includes one of streaming services, voice services, or virtual reality (VR) services.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: A second message is sent to the first core network element, the second message being used to indicate whether the terminal device supports QoE data reporting.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Receive a third message from a second core network element, the third message being used to indicate the method of collecting and / or reporting QoE data; The step of transmitting data through the first QoS stream according to the first message includes: The first QoE data is transmitted through the first QoS stream according to the first message and the third message.

9. A method for transmitting data, characterized in that, The method is applied to a first core network element, and the method includes: A first message is determined, which indicates that a first Quality of Service (QoS) stream is used to transmit Quality of Experience (QoE) data; Send the first message to the terminal device.

10. The method according to claim 9, characterized in that, The first message includes a mapping relationship between first information and the first QoS stream, wherein the first information is used to indicate the transmission of QoE data or to transmit QoE data corresponding to the first service.

11. The method according to claim 10, characterized in that, The first information includes the destination address and / or destination port for transmitting QoE data.

12. The method according to claim 10 or 11, characterized in that, The first message contains QoS flow description information, and the first information is carried in the QoS flow description information.

13. The method according to claim 12, characterized in that, The first message indicates that the first QoS stream is used to transmit QoE data of a first service type, wherein the first message further includes QoS rules, the QoS rules being used to indicate the first service type.

14. The method according to claim 10 or 13, characterized in that, The first service includes one of streaming services, voice services, or virtual reality (VR) services.

15. The method according to any one of claims 9 to 14, characterized in that, The method further includes: A second message is received from the terminal device, the second message being used to indicate whether the terminal device supports QoE data reporting.

16. The method according to any one of claims 9 to 15, characterized in that, The method further includes: A fourth message is sent to the second core network element, the fourth message being used to indicate whether the terminal device supports QoE data reporting.

17. A method for transmitting data, characterized in that, The method is applied to a second core network element, and the method includes: A third message is identified, which indicates the method for collecting and / or reporting Quality of Experience (QoE) data; Send the third message to the terminal device.

18. The method according to claim 17, characterized in that, The methods for collecting and / or reporting QoE data include one or more of the following: one-time data transmission, periodic data transmission, or data transmission triggering events.

19. The method according to claim 17 or 18, characterized in that, The method further includes: The terminal device receives a fourth message from the first core network element, the fourth message being used to indicate whether the terminal device supports QoE data reporting.

20. A method for transmitting data, characterized in that, The method is applied to a terminal device, and the method includes: Collecting the first data triggers a reporting process; Perform a unified access control check and determine whether to report based on the access classification of the first data.

21. The method according to claim 20, characterized in that, The first data includes Quality of Experience (QoE) data or Artificial Intelligence (AI) data collected according to a certain configuration.

22. The method according to claim 20, characterized in that, The method further includes: Receive second information from the first network device, the second information being used to indicate a first access category that allows or disallows access to the first network device; The step of determining whether to report based on the access classification of the first data includes: Whether to report is determined based on the access classification of the first data and the second information.

23. The method according to claim 21, characterized in that, The services corresponding to the QoE data include one of the following: streaming services, voice services, or virtual reality (VR) services.

24. The method according to any one of claims 20 to 23, characterized in that, The method further includes: A fifth message is received from a first core network element, the fifth message being used to indicate the access classification of the first data.

25. A method for transmitting data, characterized in that, The method is applied to a first network device, and the method includes: Send a second message to the terminal device, the second message being used to indicate whether access to the first network device is permitted or not, a first access category.

26. A device for transmitting data, characterized in that, include: A module or unit for performing the method as described in any one of claims 1 to 25.

27. A device for transmitting data, characterized in that, include: A processor and a memory, the processor being coupled to the memory, the memory being used to store a computer program, which, when executed by the processor, causes the apparatus to perform the method as described in any one of claims 1 to 25.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 25.

29. A computer program product, characterized in that, include: A computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 25.

30. A chip, characterized in that, include: A processor and a memory, the memory for storing a computer program, the processor for calling and running the computer program stored in the memory, causing a device or apparatus on which the chip is mounted to perform the method as described in any one of claims 1 to 25.

Images