WO2025246716A1 - 通信方法及相关装置 - Google Patents

通信方法及相关装置

Info

Publication number
WO2025246716A1
WO2025246716A1 PCT/CN2025/089489 CN2025089489W WO2025246716A1 WO 2025246716 A1 WO2025246716 A1 WO 2025246716A1 CN 2025089489 W CN2025089489 W CN 2025089489W WO 2025246716 A1 WO2025246716 A1 WO 2025246716A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
message
moment
identifier
qos flow
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/089489
Other languages
English (en)
French (fr)
Inventor
强鹂
刘南南
李秉肇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025246716A1 publication Critical patent/WO2025246716A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • This application relates to the field of communications, and more particularly to a communication method and related apparatus.
  • the terminal In some human-computer interaction scenarios, the terminal generates interactive data in response to user actions.
  • the terminal can transmit this interactive data to the server via the base station.
  • the server will then respond based on the interactive data, sending response data back to the terminal via the base station.
  • the base station After receiving the response data from the server, the base station will send the response data to the terminal within the time limit specified by the pre-configured access network (AN) packet delay budget (PDB).
  • AN pre-configured access network
  • PDB packet delay budget
  • the terminal needs to cache the response data for a period of time until it becomes effective.
  • the terminal can play video footage generated based on the response data or apply pressure to the sensor based on the response data.
  • This application provides a communication method and related apparatus that helps to avoid data loss.
  • a communication method is provided, which can be executed by a first communication device.
  • This first communication device can be a terminal, a component configured in the terminal (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal's functions; this application does not limit the specific implementation.
  • the communication method of this application is described below using the first communication device as an example of a terminal.
  • the method includes: sending a first message, the first message including first data and a first moment, the first data being business-related data, and the first moment being the moment when the terminal expects to receive second data; and receiving the second data at the first moment.
  • the service can be a loopback service, meaning that the service involves the transmission of uplink data and the reception of downlink data associated with the uplink data.
  • the uplink data corresponds to the first data in this application
  • the downlink data associated with the uplink data corresponds to the second data in this application.
  • the second data is the data associated with the first data
  • the terminal expects to receive the data associated with the first data at the first moment.
  • the data associated with the first data can also be described as the response data of the first data, or the feedback data of the first data.
  • the second data is unrelated to the first data; the second data is data associated with the first moment.
  • the second data is the data that the terminal expects to receive at the first moment.
  • the moment when the terminal expects to receive the second data can also be described as the moment when the terminal requests to receive the second data, or the moment when the terminal needs to receive the second data, or the moment when the terminal requests to receive the second data.
  • the terminal expects to receive the second data at the first moment because after receiving the second data at the first moment, the second data can be made effective immediately. This helps to avoid the problem that the second data arrives at the terminal in advance but there is not enough storage space to store it, and thus helps to avoid the problem of data loss.
  • the method further includes: establishing a first service flow and establishing a second service flow, wherein the first service flow is used to carry the first message, the first message including first data, that is, the first service flow is used to carry the first data, and the second service flow is used to carry the second data.
  • the service flow can define a set of parameters that meet the user's quality of service requirements.
  • a service flow can be, for example, a quality of service (QoS) flow, or other terms defined in existing or future protocols that can achieve the same or similar functions; this application does not limit this.
  • QoS quality of service
  • the following description uses the establishment of a first QoS flow and the establishment of a second QoS flow as examples.
  • the method further includes: receiving a first request message, the first request message being used to request the establishment of a second QoS flow, the first request message including a first identifier of the first QoS flow.
  • the method further includes: sending a second request message, the second request message being used to request the establishment of the first QoS flow, the second request message including a first identifier of the second QoS flow.
  • the method before establishing the first QoS flow and the second QoS flow, the method further includes: sending a third request message, the third request message being used to request the establishment of the first QoS flow and the second QoS flow, the third request message including a first identifier of the first QoS flow and a first identifier of the second QoS flow.
  • the third request message includes QoS parameters related to the first QoS flow and QoS parameters related to the second QoS flow.
  • the method before establishing the first QoS flow and the second QoS flow, the method further includes: sending a fourth request message, the fourth request message being used to request the establishment of the first QoS flow and the second QoS flow; and receiving a response message of the fourth request message, the response message including a first identifier of the first QoS flow and a first identifier of the second QoS flow.
  • the second identifier of the first QoS flow and the second identifier of the second QoS flow are the same.
  • the second identifier is used to indicate that the first QoS flow and the second QoS flow are related, or in other words, to indicate that the first QoS flow and the second QoS flow belong to the same group, or in other words, to indicate that the first QoS flow and the second QoS flow belong to the same service and are respectively used for uplink and downlink data transmission of that service.
  • the method before sending the first message, further includes: determining the first moment based on the moment when the first data is generated and the delay requirement.
  • the first message also includes the identifier of the first data.
  • the method before receiving the second data at the first moment, the method further includes: receiving configuration information, which includes transmission resources for the second data, the transmission resources including at least time-domain resources and frequency-domain resources.
  • the configuration information also includes the configuration of discontinuous reception (DRX) and/or the configuration of measurement gaps.
  • DRX discontinuous reception
  • a communication method is provided, which can be executed by a second communication device.
  • This second communication device can be an access network device, a component configured within the access network device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the access network device; this application does not limit the specific implementation.
  • the communication method of this application is described below using an access network device as an example.
  • the method includes: receiving a first message, the first message including first data and a first moment, the first data being service-related data, the first moment being the moment when the terminal expects to receive second data, the second data being data associated with the first data, or the second data being data associated with the first moment; and sending the second data based on the first moment.
  • the method before sending the second data based on the first moment, further includes: determining that the second QoS stream is associated with the first QoS stream based on the identifier of the second QoS stream used to carry the second data, the first QoS stream being used to carry the first message, the first message including the first data, that is, the first QoS stream being used to carry the first data; and determining the first moment from the first message carried by the first QoS stream.
  • the first message also includes an identifier for the first data.
  • the identifier for the first data here is assigned by the terminal, and the terminal can send the identifier for the first data to the access network device through the first message.
  • the terminal does not assign an identifier to the first data
  • the first message may not include the identifier of the first data.
  • the access network device assigns an identifier to the first data after receiving it.
  • the method before sending the second data based on the first moment, further includes: sending a second message, the second message including the first data, and also including an identifier of the first data and/or the first moment; and receiving a third message, the third message including the second data, and also including an identifier of the first data and/or the first moment.
  • the identifier of the first data in the second or third message can be assigned by the terminal or by the access network device.
  • the second message further includes an identifier of the first data
  • the second message also includes a second moment, which is the moment when the access network device expects to receive the second data.
  • the method further includes: sending configuration information, which includes transmission resources for the second data, including time-domain resources and frequency-domain resources, when the terminal receives the second data at the first moment.
  • the configuration information also includes the configuration of the DRX and/or the configuration of the measurement gap.
  • a communication method is provided, which can be executed by a third communication device.
  • This second communication device can be a user plane function (UPF) network element, a component configured within the UPF network element (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the UPF network element functions; this application does not limit the specific implementation.
  • the communication method of this application is described below using the example of a UPF network element as the third communication device.
  • the method includes: receiving a second message, the second message including first data, and further including an identifier of the first data and/or a first time, the first data being service-related data, the first time being the time when the terminal expects to receive the second data, the second data being data associated with the first data, or the second data being data associated with the first time; and sending a third message, the third message including the second data, and further including an identifier of the first data and/or the first time.
  • the second message also includes a second timeframe, which is the time when the access network device expects to receive the second data.
  • Sending the third message includes: sending the third message based on the second timeframe.
  • the method before sending the third message based on the second time, the method further includes: determining that the second QoS stream is associated with the first QoS stream based on the identifier of the second QoS stream used to carry the second data, the first QoS stream being used to carry the second message; and determining the second time from the second message carried by the first QoS stream.
  • the method before sending the third message, further includes: sending a fourth message, the fourth message including first data, and also including an identifier of the first data and/or a first moment; and receiving a fifth message, the fifth message including second data, and also including an identifier of the first data and/or a first moment.
  • the fourth message also includes a third moment, which is the moment when the user plane function element expects to receive the second data.
  • a communication method is provided, which can be executed by a fourth communication device.
  • This fourth communication device can be a server, a component configured within the server (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the server's functions; this application does not limit the scope of this method.
  • the communication method of this application is described below using the fourth communication device as an example of a server.
  • the method includes: receiving a fourth message, the fourth message including first data, and further including an identifier of the first data and/or a first time, the first data being service-related data, the first time being the time when the terminal expects to receive second data, the second data being data associated with the first data, or the second data being data associated with the first time; and sending a fifth message, the fifth message including the second data, and further including an identifier of the first data and/or the first time.
  • the fourth message also includes a third moment, which is the moment when the user plane function network element expects to receive the second data.
  • Sending the fifth message includes: sending the fifth message based on the third moment.
  • a communication apparatus comprising: a method for performing any possible implementation of any of the above aspects.
  • the apparatus includes a module for performing the method in any possible implementation of any of the above aspects.
  • the device may include modules that perform the methods/operations/steps/actions described in the first aspect above. These modules may be hardware circuits, software, or a combination of hardware circuits and software.
  • the device is a communication chip, which may include input circuitry or interface for transmitting information or data, and output circuitry or interface for receiving information or data.
  • the device is a terminal, access network equipment, UPF network element, or server.
  • the terminal, access network equipment, UPF network element, or server may include a transmitter for sending information or data and a receiver for receiving information or data.
  • the device is used to perform any possible implementation of the methods described above, and the device can be configured in a terminal, access network equipment, UPF network element, or server.
  • a communication device comprising at least one processor, the at least one processor being configured to call and run a computer program from a memory, such that the device performs the method in any possible implementation of any of the preceding aspects.
  • the device further includes a memory for storing instructions and data.
  • the memory is coupled to the processor, which, when executing the instructions stored in the memory, can implement the methods described in the foregoing aspects.
  • the device may also include a transmitter and a receiver, which may be separate or integrated together and referred to as a transceiver.
  • a computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.
  • a computer-readable storage medium stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods in any possible implementation of any of the preceding aspects.
  • a computer program also referred to as code or instructions
  • this application provides a chip system including at least one processing unit for supporting the implementation of the functions involved in any possible implementation of any of the above aspects, such as receiving or processing data involved in the above methods.
  • the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.
  • the chip system may consist of chips or may include chips and other discrete components.
  • Figure 1 is a schematic diagram of a communication system applicable to an embodiment of this application.
  • Figure 2 is a schematic diagram of a network architecture applicable to an embodiment of this application.
  • Figure 3 is a schematic diagram of a scenario applicable to an embodiment of this application.
  • Figure 4 is a schematic diagram of data transmission provided in an embodiment of this application.
  • Figure 5 is a schematic diagram of adjusting AN-PDB according to an embodiment of this application.
  • Figure 6 is a schematic flowchart of a communication method provided in an embodiment of this application.
  • FIGS 7 and 8 are schematic block diagrams of the communication device provided in the embodiments of this application.
  • first in the embodiments shown below, the terms “first,” “second,” and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application.
  • first moment and “second moment” are only used to distinguish different moments and do not limit the order of time.
  • At least one means one or more, while “more than one” means two or more.
  • “And/or” describes the relationship between related objects, indicating that three relationships can exist. For example, A and/or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character “/” generally indicates that the preceding and following related objects are in an “or” relationship. “At least one of the following” or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • At least one of a, b, and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, and c can be single or multiple.
  • “send” and “receive” indicate the direction of signal transmission.
  • “send a first message to the access network device” can be understood as the destination of the first message being the access network device, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules.
  • “Receive a first message from a terminal” can be understood as the source of the first message being the terminal, which may include direct reception from the terminal via the air interface or indirect reception from the terminal via the air interface by other units or modules.
  • “Send” can also be understood as the "output” of the chip interface, and “receive” can also be understood as the "input” of the chip interface.
  • sending and receiving can occur between devices, such as between a terminal and an access network device; or they can occur within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.
  • FIG 1 is a schematic diagram of a communication system applicable to an embodiment of this application.
  • the communication system 1000 shown in Figure 1 includes a radio access network (RAN) 100 and a core network (CN) 200.
  • the communication system 1000 also includes an Internet 300.
  • the radio access network 100 may include at least one RAN node (as shown in Figure 1, 110a and 110b) and at least one terminal (as shown in Figure 1, 120a-120j).
  • the terminal is wirelessly connected to the RAN node, and the RAN node is wirelessly or wiredly connected to the core network 200.
  • the core network equipment and the RAN node can be independent and different physical devices, or the functions of the core network equipment and the logical functions of the RAN node can be integrated on the same physical device, or a single physical device can integrate some of the functions of the core network equipment and some of the functions of the RAN node.
  • Terminals and RAN nodes can be interconnected via wired or wireless means.
  • Figure 1 is only a schematic diagram; the communication system may also include other RAN nodes, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 1.
  • the wireless access network 100 can be a cellular system related to the 3rd generation partnership project (3GPP), such as the 4th generation mobile communication technology (4G) system (also known as the long term evolution (LTE) system), the 5th generation mobile communication technology (5G) system (also known as the new radio (NR) system), or it can also be applied to next-generation mobile communication systems or other similar communication systems (such as the 6th generation mobile communication technology (6G) system), etc., and this application does not limit it in this regard.
  • 3GPP 3rd generation partnership project
  • 4G 4th generation mobile communication technology
  • LTE long term evolution
  • 5G also known as the new radio (NR) system
  • next-generation mobile communication systems or other similar communication systems such as the 6th generation mobile communication technology (6G) system
  • the wireless access network 100 can also be an open RAN (open-RAN, O-RAN, or ORAN), a cloud radio access network (CRAN), or a non-terrestrial network (NTN), a satellite communication network, a high-altitude platform station (HAPS) communication network, an integrated access and backhaul (IAB) communication network, a reconfigurable intelligent surface (RIS) communication network, etc.
  • the wireless access network 100 can also be a communication system that integrates two or more of the above systems.
  • RAN nodes also known as RAN devices or access network devices, are used to help terminals achieve wireless access.
  • Multiple RAN nodes in the communication system 1000 can be of the same type or different types.
  • the RAN node provided in this application embodiment can be a base station, a Node B, an evolved Node B (eNodeB or eNB), a transmission reception point (TRP), a next-generation Node B (gNB) in 5G or NR, a RAN node in an open radio access network (O-RAN or open RAN), or a next-generation base station in 6th generation mobile communication technology (6G).
  • the RAN node can also be a satellite base station in a non-terrestrial network (NTN) communication network, a base station in a future mobile communication system, or an access node in a wireless fidelity (Wi-Fi) system.
  • NTN non-terrestrial network
  • Wi-Fi wireless fidelity
  • the RAN node can also be a module or unit that performs some of the functions of a base station, for example, it can be a centralized unit (CU) or a distributed unit (DU).
  • the functions of the CU can be implemented by one entity or by different entities.
  • the functions of the CU can be further divided, such as separating the control plane (CP) and the user plane (UP), i.e., the CU's control plane (CU-CP) and the CU's user plane (CU-UP).
  • the RAN node can be a macro base station, a micro base station, an indoor station, a relay node, or a host node, etc. This application does not limit the specific technology or equipment form used in the RAN node.
  • a terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from RAN nodes.
  • Terminals can also be referred to as terminal devices, terminal equipment, user equipment (UE), mobile stations, mobile terminals, etc.
  • Terminals can be widely used in various scenarios, such as D2D, V2X communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, intelligent transportation, smart cities, etc.
  • a terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft, ship, robot, robotic arm, smart home device, etc.
  • the embodiments of this application do not limit the specific technology or device form used in the terminal.
  • the terminal can be widely used for communication in various scenarios. These scenarios include, but are not limited to, at least one of the following: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communications (mMTC), device-to-device (D2D), vehicle-to-everything (V2X), machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, or smart cities, etc.
  • the terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, helicopter, airplane, drone, ship, robot, robotic arm, or smart home device, etc. This application does not limit the specific technology or specific device form adopted by the terminal device.
  • RAN nodes and terminals can be fixed or mobile. RAN nodes and terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of RAN nodes and terminals.
  • RAN nodes and terminals can be relative.
  • the helicopter or drone 120i in Figure 1 can be configured as a mobile RAN node.
  • terminal 120i For terminals 120j that access the radio access network 100 through 120i, terminal 120i is a RAN node; however, for RAN node 110a, 120i is a terminal, meaning that 110a and 120i communicate via a radio interface protocol.
  • 110a and 120i can also communicate via a RAN node-to-RAN node interface protocol.
  • 120i is also a RAN node relative to 110a. Therefore, both RAN nodes and terminals can be collectively referred to as communication devices.
  • 110a and 110b in Figure 1 can be called communication devices with RAN node functions
  • 120a-120j in Figure 1 can be called communication devices with terminal functions.
  • Communication between RAN nodes and terminals, between RAN nodes, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can also be conducted using spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or both simultaneously.
  • GHz gigahertz
  • the embodiments of this application do not limit the spectrum resources used for wireless communication.
  • the functions of the RAN node can be executed by modules (such as chips) within the RAN node, or by a control subsystem that includes RAN node functions.
  • This control subsystem including RAN node functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities.
  • the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.
  • Core network equipment refers to the equipment in the core network that provides service support to terminals. Examples of some core network equipment include: access and mobility management function (AMF) network elements, session management function (SMF) network elements, UPF network elements, etc., which will not be listed here.
  • AMF access and mobility management function
  • SMF session management function
  • UPF UPF network elements
  • Figure 2 is a schematic diagram of a network architecture applicable to an embodiment of this application. Taking the 5G network architecture as an example, Figure 2 shows network functions and entities including: UE, RAN, UPF, AMF, SMF, and data network (DN).
  • UE User Plane Function
  • RAN User Plane Function
  • UPF User Plane Function
  • AMF Access Management Function
  • SMF Session Management Function
  • DN data network
  • the network architecture may also include unified data management (UDM), network exposure function (NEF), policy control function (PCF), network repository function (NRF), network slice selection function (NSSF), authentication server function (AUSF), and network data analytics function (NWDAF).
  • UDM unified data management
  • NEF network exposure function
  • PCF policy control function
  • NRF network repository function
  • NSSF network slice selection function
  • AUSF authentication server function
  • NWDAF network data analytics function
  • UE, RAN, UPF, and DN are typically referred to as user plane (or data plane) network functions and entities.
  • User data traffic can be transmitted through Protocol Data Unit (PDU) sessions established between the UE and DN. This transmission passes through the RAN node and the UPF, which can be considered a user plane network element in the core network.
  • the other network elements are called control plane network functions and entities (or control plane network elements), primarily responsible for authentication and authorization, registration management, session management, mobility management, and policy control, thereby ensuring reliable and stable transmission of user-layer traffic.
  • the user plane carries service data, while the control plane carries signaling messages.
  • Figure 2 illustrates the interaction relationships between network functions and entities, as well as their corresponding interfaces.
  • the UE and AMF can interact via the N1 interface, and the interaction messages are called N1 messages.
  • Some interfaces are implemented using a service-oriented approach.
  • AMF Access Management Function
  • AMF Access Management Function
  • a network element module, or component that provides access management functions. It is mainly responsible for signaling processing, such as access control, mobility management, attach and detach, and gateway selection.
  • AMF network element provides services to a session in a terminal, it provides control plane storage resources for that session to store the session identifier and the identifier of the SMF associated with the session identifier.
  • SMF is a network element, module, or component responsible for handling user services, such as user plane function selection, user plane function redirection, IP address allocation, bearer establishment, modification and release, and QoS control.
  • the UPF is responsible for forwarding and receiving user data in the terminal.
  • the UPF can receive user data from the DN and transmit it to the UE through the RAN node; the UPF can also receive user data from the UE through the RAN node and forward it to the DN.
  • the transmission resources and scheduling functions that provide services to the UE in the UPF are managed and controlled by the SMF network element.
  • the terminal In some human-computer interaction scenarios, the terminal generates interactive data in response to user operations.
  • the terminal can transmit this interactive data to a server (such as a server deployed in the DN shown in Figure 2) via a base station.
  • the server then sends data associated with the interactive data back to the terminal via the base station.
  • This data associated with the interactive data can be considered as the response data of the interactive data.
  • the base station After receiving the response data from the server, the base station can estimate the AN-PDB between the base station and the terminal based on historical scheduling information and the end-to-end latency of the application. Subsequently, the base station sends the response data to the terminal within the time specified by the AN-PDB. This scheduling method is called latency-based scheduling.
  • the terminal is XR glasses.
  • the XR glasses generate head-turning data in response to the user's head-turning action.
  • the server After receiving this head-turning data, the server generates screen data associated with it. Then, the server sends this screen data to the terminal via a base station.
  • the base station can adjust the size of the AN-PDB according to the deviation between the actual arrival time and the theoretical arrival time of the data.
  • AN-PDB only applies to data transmission for periodic services. Because periodic services have a theoretical arrival time, the base station can adjust the AN-PDB size based on the deviation between the actual and theoretical arrival times. For non-periodic services, such as random bursts, the base station may not even know the data's generation time after receiving it, let alone its theoretical arrival time, making it impossible to adjust the AN-PDB size. Furthermore, under the constraint of AN-PDB, data is highly likely to arrive at the terminal earlier than the stipulated effective time, requiring the data to be cached on the terminal for a period until the designated effective time. However, for lightweight terminals such as XR glasses and smart bracelets, storage space is limited. If the data arrives at the terminal earlier than the effective time, the terminal may not have enough storage space to store the data, potentially leading to data loss.
  • this application provides a communication method in which a terminal can inform a base station of the time it expects to receive data.
  • the base station can then send the data to the terminal with sufficient information so that the terminal can receive the data at that time.
  • the terminal receives the data at that time, it takes effect immediately without buffering, thus avoiding the problem of data loss due to limited storage space.
  • FIG. 6 is a schematic flowchart of a communication method 600 provided in an embodiment of this application.
  • Method 600 includes steps S601 and S602.
  • method 600 also includes steps S603 to S608. The specific steps are as follows:
  • the terminal sends a first message to the access network device.
  • the first message includes first data and a first time.
  • the first data is service-related data
  • the first time is the time when the terminal expects to receive second data.
  • the second data is data associated with the first data, or the second data is data associated with the first time. Accordingly, the access network device receives the first message.
  • the first data is, for example, a service data unit (SDU).
  • SDU service data unit
  • the second data is data associated with the first data, or in other words, the second data is response data or feedback data to the first data.
  • the terminal is XR glasses.
  • the XR glasses respond to the user's head-turning action by generating head-turning data.
  • the terminal can then receive screen data corresponding to the angle of this head-turning data.
  • the first data is the head-turning data
  • the data associated with the first data is the screen data corresponding to the angle of this head-turning data.
  • the head-turning data can also be described as control commands related to head-turning.
  • the terminal is a mobile phone.
  • the phone In response to a user's photo-taking action, the phone generates raw image data. Subsequently, the phone can receive rendered image data derived from this raw image data.
  • the first data is the raw image data
  • the data associated with the first data is the rendered image data derived from it.
  • the terminal is an XR haptic glove.
  • the XR haptic glove responds to the user's gestures, generating gesture data. Subsequently, the XR haptic glove can receive the tactile data corresponding to this gesture data.
  • the first data is the gesture data
  • the data associated with the first data is the tactile data.
  • the second data is data associated with the first moment but unrelated to the first data; in other words, the second data is the data the terminal expects to receive at the first moment.
  • the moment when the terminal expects to receive the second data can also be described as the moment when the terminal requests to receive the second data, or the moment when the terminal requests to receive the second data, or the moment when the terminal needs to receive the second data.
  • the access network device sends second data to the terminal based on the first moment.
  • the terminal receives the second data.
  • the terminal includes a communication interface and an application (or sensor), such as a camera application, a video application, a game application, etc., and a sensor such as a camera, a pressure sensor, a tactile sensor, a vision sensor, a biosensor, etc.
  • the application (or sensor) generates first data and transmits it to the communication interface, which then sends the first data to an access network device.
  • the terminal's communication interface receives second data from the access network device, then sends the second data to the application (or sensor) and applies the second data to the application (or sensor), for example, displaying an image generated based on the second data in a camera application, displaying a video generated based on the second data in a video application, or applying pressure generated based on the second data to a tactile sensor.
  • the application (or sensor) generates the first data, it can send the first data and the fourth time to the communication interface.
  • the fourth time is the time when the application (or sensor) expects to receive the second data, or in other words, the fourth time is the time when the second data takes effect on the application (or sensor).
  • “effective” can be replaced with “use,” “implement,” “execute,” “display,” “play,” etc.
  • “effective” means playing the image generated based on the image data; if the first data is original image data and the second data is image data rendered from the original image data, then “effective” means displaying the image generated based on the rendered image data; if the first data is finger operation and the second data is tactile data corresponding to the gesture data, then “effective” means applying pressure to the sensor based on the tactile data, or performing a vibration operation.
  • the application determines the fourth moment based on the time when the first data was generated and the latency requirement.
  • the latency requirement can be a round trip time (RTT) requirement or a motion-to-photon (MTP) latency requirement.
  • the fourth moment refers to application-level time information, such as the exact time (hours, minutes, and seconds).
  • the first moment described in this application embodiment is the moment when the terminal's communication interface expects to receive the second data.
  • the communication interface determines the first moment based on the fourth moment, taking into account one or more of the following latency factors: the latency of the second data being transmitted from the communication interface to the application (or sensor), the scheduling latency of the communication interface, or the internal processing latency of the communication interface.
  • the communication interface can directly send the second data to the application (or sensor) without storage after receiving it at the first moment.
  • the first moment is time information that the communication system can understand, such as the system frame number, time slot number, and orthogonal frequency division multiplexing (OFDM) symbols.
  • time information such as the system frame number, time slot number, and orthogonal frequency division multiplexing (OFDM) symbols.
  • OFDM orthogonal frequency division multiplexing
  • S602 includes: the access network device determining the transmission time of the second data based on the first time and latency factors, denoted as the fifth time, and transmitting the second data to the terminal at the fifth time.
  • the latency factors include one or more of the following: network load conditions, UE behavior, transmission latency between the access network device and the terminal, internal processing latency of the access network device, or scheduling latency of the access network device.
  • the access network device transmitting the second data at the fifth time satisfies the terminal's requirement of receiving the second data at the first time.
  • the first moment and the fifth moment may be the same moment.
  • each time slot is 0.5ms.
  • the time slot number of the fifth moment is the same as the time slot number of the first moment, that is, the first moment and the fifth moment are the same moment.
  • the terminal expects to receive the second data at the first moment because the second data can be made effective immediately after the terminal receives it. This helps to avoid the problem of the second data arriving at the terminal in advance but not having enough storage space for storage, and thus helps to avoid the problem of data loss.
  • method 600 may also include more steps, such as S603 to S608 described below, each of which is described below.
  • a terminal's service involves two data transmissions: uplink and downlink, with significantly different data characteristics. For example, uplink data transmission has high latency requirements but low bandwidth requirements, while downlink video data has high bandwidth requirements but no reliability requirements. Therefore, two different service flows need to be established to meet the uplink and downlink transmission needs.
  • a service flow can define a set of parameters that meet the user's Quality of Service (QoS) requirements.
  • QoS Quality of Service
  • a service flow can be, for example, a QoS flow, or other terms defined in existing or future protocols that can achieve the same or similar functions; this application does not limit this.
  • the following description uses the establishment of two QoS flows as an example, with the two QoS flows used for uplink and downlink transmission respectively.
  • method 600 further includes S603: the terminal interacts with the control plane network element of the core network to establish a first QoS stream and a second QoS stream, wherein the first QoS stream is used to carry a first message, and the second QoS stream is used to carry second data. After establishing the first QoS stream and the second QoS stream, the terminal can transmit service-related data with the UPF network element.
  • the scheduling of the first QoS stream and the second QoS stream mentioned above is related, or rather, corresponding. Therefore, it is necessary to associate the first QoS stream and the second QoS stream. Through the association between the first QoS stream and the second QoS stream, the data carried by the QoS stream can be associated with the data carried by the second QoS stream, so as to achieve accurate data scheduling.
  • the terminal first triggers the establishment of a first QoS flow.
  • a control plane network element e.g., an AMF network element
  • the control plane network element sends a first request message to the terminal.
  • the first request message requests the establishment of the second QoS flow and includes a first identifier of the first QoS flow.
  • the first request message also includes a first identifier of the second QoS flow.
  • the first QoS flow and the second QoS flow are associated by carrying the first identifier of the first QoS flow in the message requesting the establishment of the second QoS flow.
  • the first identifier is the flow identifier of the QoS flow, such as the QoS flow identifier (QFI), or the QoS identifier in 5G (5G QoS identifier (5QI), or an identifier with similar function. This application does not limit this.
  • the control plane network element first triggers the establishment of a second QoS flow.
  • the terminal triggers the establishment of a first QoS flow.
  • the terminal sends a second request message to the control plane network element.
  • the second request message requests the establishment of the first QoS flow and includes a first identifier of the second QoS flow.
  • the first QoS flow and the second QoS flow are associated by carrying the first identifier of the first QoS flow and the first identifier of the second QoS flow in the message requesting the establishment of the first QoS flow.
  • the terminal sends the first identifier of the first QoS flow to the control plane network element. This allows the control plane network element to obtain the first identifier of the first QoS flow and subsequently include it in the first request message.
  • the control plane network element sends the first identifier of the second QoS flow to the terminal. This allows the terminal to obtain the first identifier of the second QoS flow and subsequently include it in the second request message.
  • the terminal triggers the establishment of a first QoS flow and a second QoS flow.
  • the terminal sends a third request message to the control plane network element.
  • the third request message is used to request the establishment of the first QoS flow and the second QoS flow.
  • the third request message includes a first identifier of the first QoS flow and a first identifier of the second QoS flow.
  • the terminal requests the establishment of two QoS flows at once, and associates the first QoS flow and the second QoS flow by carrying the first identifier of the first QoS flow and the first identifier of the second QoS flow in the third request message.
  • the terminal triggers the establishment of a first QoS flow and a second QoS flow.
  • the terminal sends a fourth request message to the control plane network element, which requests the establishment of the first QoS flow and the second QoS flow.
  • the terminal receives a response message from the control plane network element to the fourth request message, which includes a first identifier of the first QoS flow and a first identifier of the second QoS flow.
  • the first QoS flow and the second QoS flow are associated by carrying the first identifiers of the first QoS flow and the second QoS flow in the response message to the fourth request message.
  • the control plane network element after establishing the first QoS flow and the second QoS flow, assigns a unified identifier to the first QoS flow and the second QoS flow to associate the first QoS flow and the second QoS flow.
  • This unified identifier can be viewed as the second identifier of the first QoS flow and the second identifier of the second QoS flow.
  • the second identifier is a group identifier (or a group identifier, a group identifier, or a class identifier). If the first QoS flow and the second QoS flow have the same group identifier, it means that the first QoS flow and the second QoS flow belong to the same group, that is, the first QoS flow and the second QoS flow are associated.
  • the terminal when the terminal establishes the first QoS flow, the terminal can send a fifth request message to the control plane network element.
  • This fifth request message requests the establishment of the first QoS flow and carries a first identifier and a second identifier of the first QoS flow.
  • the terminal receives a response message from the control plane network element to the fifth request message, which includes both the first and second identifiers of the first QoS flow.
  • the control plane network element After the first QoS flow is established, when establishing the second QoS flow, the control plane network element sends a sixth request message to the terminal.
  • This sixth request message includes both the first and second identifiers of the second QoS flow.
  • both the first and second QoS flows carry the second identifier, indicating that they belong to the same group or are QoS flows of the same service, used for uplink and downlink transmission respectively.
  • the access network device can determine, based on its capabilities, whether it can meet the terminal's requirement to receive the second data at the first moment, or in other words, whether it supports the terminal receiving the second data at the first moment. In one possible implementation, the access network device determines whether it supports the terminal receiving the second data at the first moment based on the RTT (Round-Trip Time) over a historical period between the access network device and the terminal.
  • RTT Red-Trip Time
  • the access network device can meet the terminal's requirement to receive the second data at the first moment.
  • the access network device can estimate whether it has sufficient transmission resources to schedule the second data at the fifth moment, which is the moment when the access network device sends the second data. For example, for some real-time services or guaranteed bit rate (GBR) services, the access network device has already reserved transmission resources in advance, meaning that at the fifth moment, the access network device does not have idle resources to schedule the second data, and therefore cannot meet the terminal's requirement to receive the second data at the first moment.
  • GRR guaranteed bit rate
  • method 600 further includes S604: the access network device sends configuration information to the terminal, and the terminal receives the configuration information accordingly.
  • the configuration information includes transmission resources for the second data, such as time-domain resources and frequency-domain resources, to inform the terminal at what time and on what frequency band to detect the second data sent by the access network device.
  • the terminal may be in DRX sleep mode at the first moment.
  • the terminal may stop some or all functional modules, thus failing to receive the second data. Therefore, the access network device can adjust the DRX configuration based on the first moment and include the adjusted DRX configuration in the configuration information to avoid the terminal being unable to receive the second data at the first moment due to being in DRX sleep mode.
  • the first moment may fall within the time period corresponding to the measurement gap.
  • the terminal might perform cell measurements or other operations during the first moment, and therefore cannot transmit data during the time period corresponding to the measurement gap. Therefore, the access network equipment can adjust the measurement gap configuration based on the first moment and include the adjusted configuration in the configuration information. This avoids the first moment falling within the time period corresponding to the measurement gap, thus helping to prevent the terminal from failing to receive the second data during the first moment.
  • the terminal's services will generate multiple data sets. These multiple data sets can be distinguished by their identifiers.
  • the first data set is a single data set.
  • the first data set is a PDU set, which can be considered as a single data set.
  • the first data set is a data burst, which can be considered as a single data set.
  • the first message also includes an identifier for the first data, which is a service-specific identifier, such as an identifier for a PDU set or a data burst identifier.
  • an identifier for the first data can be an image identifier.
  • the terminal includes a communication interface and an application (or sensor).
  • the application (or sensor) can assign an identifier to the first data, and then the application (or sensor) sends the identifier of the first data to the communication interface.
  • the communication interface assigns an identifier to the first data after receiving it from the application (or sensor).
  • the identifier of the first data can also be described as the index of the first data, or the sequence number (SN) of the first data, but this application embodiment does not limit this.
  • the access network device After receiving the first message, if the first message also includes the identifier of the first data, the access network device records the association between the identifier of the first data and the first moment. This association indicates that the terminal expects to receive the second data at the first moment.
  • the terminal in response to a user's head-turning operation, receives first head-turning data, which corresponds to identifier 1.
  • the terminal expects to receive screen data associated with the first head-turning data at time t1.
  • the access network device can record the association between identifier 1 and t1, indicating that the terminal expects to receive the screen data associated with the first head-turning data at time t1.
  • the terminal responds again to the user's head-turning operation, receiving second head-turning data, which corresponds to identifier 2.
  • the terminal expects to receive screen data associated with the second head-turning data at time t2.
  • the access network device can also record the association between identifier 2 and t2, indicating that the terminal expects to receive the screen data associated with the second head-turning data at time t2.
  • the access network device can determine the expected time for receiving the screen data associated with the first head-turning data as t1 based on identifier 1, and determine the expected time for receiving the screen data associated with the second head-turning data as t2 based on identifier 2.
  • method 600 further includes S605: the access network device sends a second message to the UPF network element, the second message including first data, and also including an identifier of the first data and/or a first time. Accordingly, the UPF network element receives the second message. Further, after S605, method 600 further includes S606: the UPF network element sends a fourth message to the server, the fourth message including the first data, and also including an identifier of the first data and/or a first time, accordingly, the server receives the fourth message.
  • the UPF network element can pass messages from the access network device to the server, that is, the second message and the fourth message can be the same message, and the content of the fourth message is the same as the content of the second message.
  • the fourth message includes the first data and an identifier for the first data.
  • This method of transmitting the identifier for the first data helps reduce signaling overhead.
  • the first data and its identifier will be referred to as content 1 below.
  • the second message includes content 1
  • the fourth message includes content 1.
  • the fourth message includes the first data and the first moment.
  • This method of transmitting time information is more direct and efficient.
  • the first data and the first moment will be referred to as content 2 below.
  • the second message includes content 2
  • the fourth message includes content 2.
  • the first moment in Content 1 above can be replaced with the fifth moment, meaning the second message includes both the first data and the fifth moment.
  • the first data and the fifth moment will be referred to as Content 3 below.
  • the second message includes Content 3
  • the fourth message includes Content 3.
  • the second message also includes a fifth moment, that is, the second message includes the first data, the identifier of the first data, and the fifth moment, and the fourth message includes the first data, the identifier of the first data, and the fifth moment.
  • the first data, the identifier of the first data, and the fifth moment will be referred to as content 4 below.
  • the second message includes content 4
  • the fourth message includes content 4.
  • the second message also includes a fifth moment
  • the fourth message also includes a fifth moment. That is, the second message includes the first data, the first moment, and the fifth moment, and the fourth message includes the first data, the first moment, and the fifth moment.
  • the first data, the first moment, and the fifth moment will be referred to as content 5 below.
  • the second message includes content 5
  • the fourth message includes content 5.
  • the access network device determines the moment when it expects to receive the second data, denoted as the second moment. Subsequently, the access network device can include the second moment in the aforementioned second message; that is, in addition to including any one of content 1 to content 5, the second message also includes the second moment. In this way, the UPF network element can subsequently send the second data to the access network device based on the second moment, as described below, which will not be elaborated here.
  • the access network device determines the second time based on the first time moment, taking into account one or more of the following latency factors: transmission latency between the access network device and the terminal, internal processing latency of the access network device, or scheduling latency of the access network device. If the access network device receives the second data at the second time moment, it can ensure that the terminal receives the second data at the first time moment.
  • the UPF network element To control the transmission latency between the UPF network element and the server, and thus ensure that the terminal receives the second data at the first possible moment, the UPF network element, after receiving the second message, determines the expected moment when it will receive the second data, denoted as the third moment. Subsequently, the UPF network element can include the third moment in the aforementioned fourth message. That is, the fourth message includes any one of content 1 to content 5, plus the third moment. This allows the server to subsequently send the second data to the UPF network element based on the third moment. See the description below for details, which will not be elaborated here.
  • the UPF network element determines the third time based on the second time moment, taking into account one or more of the following delay factors: transmission delay between the UPF network element and the access network equipment, internal processing delay of the UPF network element, or scheduling delay of the UPF network element. If the UPF network element receives the second data at the third time moment, it can ensure that the access network equipment receives the second data at the second time moment.
  • the terminal's first data is transmitted to the server via the base station and UPF network element. While sending the first data to the server via the UPF network element, the access network device can also send the identifier and/or first moment of the first data to the server via the UPF network element. The following describes the process by which the server sends the second data to the terminal via the UPF network element and the access network device.
  • the server retrieves the second data based on the first data. For example, it retrieves image data corresponding to the head-turning angle based on the head-turning data. Another example is retrieving rendered image data based on the original image data. Yet another example is retrieving sensor tactile data based on gesture data.
  • method 600 further includes S607: the server sends a fifth message to the UPF network element, the fifth message including second data, and also including the identifier of the first data and/or the first time, and correspondingly, the UPF network element receives the fifth message.
  • method 600 further includes S608: the UPF network element sends a third message to the access network device, the third message including second data, and also including the identifier of the first data and/or the first time, and correspondingly, the access network device receives the third message.
  • the UPF network element can transparently transmit messages from the server to the access network device; that is, the fifth message and the third message can be the same message.
  • the content of the fifth message is related to the content of the fourth message, and the content of the third message can be the same as the content of the fifth message.
  • the fourth message mentioned above includes content 1; correspondingly, the fifth message includes the second data and also includes the identifier of the first data; correspondingly, the third message includes the second data and also includes the identifier of the first data.
  • the second data and the identifier of the first data will be referred to as content 6 below.
  • the fifth message includes content 6, and the third message includes content 6.
  • the fourth message mentioned above includes content 2; correspondingly, the fifth message includes the second data and also the first moment; correspondingly, the third message includes the second data and also the first moment.
  • the second data and the first moment will be referred to as content 7 below.
  • the fifth message includes content 7
  • the third message includes content 7.
  • the fourth message mentioned above includes content 3; correspondingly, the fifth message includes the second data and the fifth time point; correspondingly, the third message includes the second data and the fifth time point.
  • the second data and the fifth time point will be referred to as content 8 below.
  • the fifth message includes content 8
  • the third message includes content 8.
  • the fourth message mentioned above includes content 4.
  • the fifth message in addition to including content 6, also includes a fifth moment, that is, the fifth message includes the second data, the identifier of the first data, and the fifth moment.
  • the third message includes the second data, the identifier of the first data, and the fifth moment.
  • the data associated with the first data, the identifier of the first data, and the fifth moment will be referred to as content 9 below.
  • the fourth message mentioned above includes content 5.
  • the fifth message in addition to including content 7, also includes the fifth moment, that is, the fifth message includes the second data, the first moment, and the fifth moment.
  • the third message includes the second data, the first moment, and the fifth moment.
  • the data associated with the first data, the first moment, and the fifth moment will be referred to as content 10 below.
  • the access network device can send the second data to the terminal based on the content included in the third message. More specifically, since the terminal may establish multiple QoS flows for transmitting uplink data, the access network device first determines the QoS flow associated with the second QoS flow carrying the second data, i.e., the first QoS flow. Then, the access network device determines the first moment from the first message carried by the first QoS flow. Subsequently, the access network device can execute the above-described S602, i.e., send the second data to the terminal based on the first moment.
  • the access network device can execute the above-described S602, i.e., send the second data to the terminal based on the first moment.
  • the third message includes, in addition to any one of the contents 6 to 10 mentioned above, a first identifier of the second QoS flow.
  • the access network device determines the association between the second QoS flow and the first QoS flow by looking up the association relationship of the stored QoS flows based on the first identifier of the second QoS flow.
  • the third message includes any one of the contents 6 to 10 above, as well as the second identifier of the second QoS flow.
  • the access network device determines the first QoS flow with the same second identifier as the second QoS flow by looking up the association relationship of the stored QoS flows based on the second identifier of the second QoS flow. In other words, if the second identifier of the first QoS flow is the same as the second identifier of the second QoS flow, it means that the first QoS flow and the second QoS flow are associated.
  • the third message includes, in addition to any one of the contents 6 to 10 mentioned above, a first identifier of the first QoS flow and a first identifier of the second QoS flow.
  • the access network device can determine the association between the first QoS flow and the second QoS flow based on the third message.
  • the access network device when the third message includes the aforementioned content 6, since content 6 does not include the reception time and/or transmission time of the data associated with the first data, the access network device first determines the association between the second QoS stream and the first QoS stream according to the above description. Then, since the first QoS stream may carry multiple messages, and the service-related data included in different messages may correspond to different reception times, the access network device can determine the reception time corresponding to the first data, i.e., the first time, from the first message carried by the first QoS stream based on the identifier of the first data.
  • the access network device can send the second data to the terminal based on this configuration information.
  • This configuration information includes the transmission resources for the second data, and optionally, also includes the configuration of DRX and the configuration of measurement intervals.
  • the access network device can determine the time to send the second data to the terminal (i.e., the fifth time) and/or the time when the terminal expects to receive the second data (i.e., the first time) from the third message. In this way, the access network device does not need to query the stored information to determine the first time or the fifth time, and this implementation method is simpler and more efficient.
  • S607 includes: the server sending a fifth message to the UPF network element based on the third time. More specifically, the server determines the time to send the second data to the UPF network element based on the third time and latency factors, denoted as the sixth time, and sends the fifth message to the UPF network element at the sixth time.
  • the latency factors include one or more of the following: transmission latency between the server and the UPF network element, internal processing latency of the server, or scheduling latency of the server.
  • the server sending the second data to the UPF network element at the sixth time satisfies the requirement of the UPF network element to receive the second data at or before the third time.
  • S608 includes: the UPF network element sending a third message to the access network device based on the second time. More specifically, the UPF network element determines a seventh time based on the second time and delay factors, and sends the third message to the access network device at the seventh time.
  • the delay factors include one or more of the following: transmission delay between the UPF network element and the access network device, internal processing delay of the UPF network element, or scheduling delay of the UPF network element.
  • the UPF network element sending the second data to the access network device at the seventh time can satisfy the requirement that the access network device receives the second data at or before the second time.
  • the UPF network element Before sending a third message to the access network device based on a second time, the UPF network element first needs to determine the time at which the access network device expects to receive the second data as the second time. In one possible implementation, the UPF network element determines the second time by: determining that the second QoS flow is associated with the first QoS flow based on the identifier of the second QoS flow used to carry the second data; and then, determining the second time from the second message carried by the first QoS flow.
  • the UPF network element determines the second time from the second message carried by the first QoS flow by: determining the second time from the second message carried by the first QoS flow based on the identifier of the first data.
  • UPF network elements determining the second time step is similar to the method used by access network devices to determine the first time step as described above. For example, based on the first identifier or the second identifier of the second QoS flow, the association between the second QoS flow and the first QoS flow is determined, and then the second time step is determined from the second message carried by the first QoS flow. For details, please refer to the description above; it will not be repeated here.
  • the communication method according to an embodiment of the present application has been described in detail above with reference to FIG6.
  • the communication device according to an embodiment of the present application will be described in detail below with reference to FIG7 and FIG8.
  • FIG. 7 is a schematic block diagram of a communication device 700 provided in an embodiment of this application.
  • the device 700 includes a transceiver module 710.
  • the device 700 further includes a processing module 720.
  • the processing module 720 is used for data processing.
  • the transceiver module 710 can implement corresponding communication functions.
  • the transceiver module 710 can also be called a communication interface or a communication module.
  • the device 700 may further include a storage module, which can be used to store data and/or to store computer programs or instructions.
  • the processing module 720 can read the computer programs/instructions and/or data in the storage module so that the device 700 can implement the above-described method embodiments.
  • the device 700 can be used to perform the actions performed by the terminal, access network device, or UPF network element in the above method embodiments.
  • the device 700 can be a component (e.g., a chip) configured in the terminal, access network device, or UPF network element.
  • the processing module 720 is used to perform processing-related operations of the terminal, access network device, or UPF network element in the above method embodiments.
  • the transceiver module 710 is used to perform receiving and transmitting-related operations of the terminal, access network device, or UPF network element in the above method embodiments.
  • the transceiver module 710 may include a sending module and a receiving module.
  • the sending module is used to perform the sending operation in the above method embodiments.
  • the receiving module is used to perform the receiving operation in the above method embodiments.
  • device 700 may include a transmitting module but not a receiving module.
  • device 700 may include a receiving module but not a transmitting module. Specifically, it depends on whether the above-described scheme executed by device 700 includes both transmitting and receiving actions.
  • the device 700 is used to perform the actions performed by the terminal, access network device, or UPF network element in the embodiment shown in FIG6 above.
  • the device 700 is used to perform the actions performed by the terminal, access network device, or UPF network element in the embodiment shown in FIG6 above.
  • the transceiver module 710 is configured to: send a first message, the first message including first data and a first moment, the first data being business-related data, the first moment being the moment when the terminal expects to receive second data, the second data being data associated with the first data, or the second data being data associated with the first moment; and receive the second data at the first moment.
  • the processing module 720 is used to: establish a first QoS stream and establish a second QoS stream, wherein the first QoS stream is used to carry a first message and the second QoS stream is used to carry second data.
  • the transceiver module 710 is configured to: receive a first request message, the first request message being used to request the establishment of a second QoS flow, the first request message including a first identifier of the first QoS flow.
  • the transceiver module 710 is configured to: send a second request message, the second request message being used to request the establishment of a first QoS flow, the second request message including a first identifier of the second QoS flow.
  • the transceiver module 710 is configured to: send a third request message, the third request message being used to request the establishment of a first QoS stream and a second QoS stream, the third request message including a first identifier of the first QoS stream and a first identifier of the second QoS stream.
  • the transceiver module 710 is configured to: send a fourth request message, the fourth request message being used to request the establishment of a first QoS stream and a second QoS stream; and receive a response message to the fourth request message, the response message including a first identifier of the first QoS stream and a first identifier of the second QoS stream.
  • the second identifier of the first QoS flow is the same as the second identifier of the second QoS flow.
  • the processing module 720 is used to: determine the first moment based on the moment when the first data is generated and the delay requirement.
  • the first message may also include an identifier for the first data.
  • the transceiver module 710 is used to: receive configuration information, which includes transmission resources for the second data.
  • the configuration information may also include the configuration of the DRX and/or the configuration of the measurement gap.
  • the device 700 may specifically be the terminal shown in the embodiment of FIG. 6 above, or the functions of the terminal shown in the embodiment of FIG. 6 above may be integrated into the device 700.
  • the above functions may be implemented by hardware or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the device 700 may be used to execute the various processes and/or steps corresponding to the terminal in the above method embodiments.
  • the transceiver module 710 is configured to: receive a first message, the first message including first data and a first moment, the first data being service-related data, the first moment being the moment when the terminal expects to receive second data, the second data being data associated with the first data, or the second data being data associated with the first moment; and, based on the first moment, send the second data.
  • the processing module 720 is configured to: determine that the second QoS stream is associated with the first QoS stream based on the identifier of the second QoS stream used to carry the second data, wherein the first QoS stream is used to carry the first message; and determine a first moment from the first message carried by the first QoS stream.
  • the first message may also include an identifier for the first data.
  • the transceiver module 710 is configured to: send a second message, the second message including first data, and further including an identifier of the first data and/or a first moment; and receive a third message, the third message including the second data, and further including an identifier of the first data and/or a first moment.
  • the second message also includes an identifier of the first data
  • the third message also includes an identifier of the first data
  • the processing module 720 is used to: determine a first moment from the first message carried by the first QoS stream according to the identifier of the first data.
  • the second message may also include a second time, which is the time when the access network device expects to receive the second data.
  • the transceiver module 710 is used to: send configuration information, including the transmission resources of the second data, when the terminal receives the second data at the first moment.
  • the configuration information may also include the configuration of the DRX and/or the configuration of the measurement gap.
  • the device 700 may specifically be the access network device in the embodiment shown in FIG. 6 above, or the functions of the access network device in the embodiment shown in FIG. 6 above may be integrated into the device 700.
  • the above functions may be implemented by hardware or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the device 700 may be used to execute the various processes and/or steps corresponding to the access network device in the above method embodiments.
  • the transceiver module 710 is configured to: receive a second message, the second message including first data, and further including an identifier of the first data and/or a first time, the first data being service-related data, the first time being the time when the terminal expects to receive the second data, the second data being data associated with the first data, or the second data being data associated with the first time; and send a third message, the third message including the second data, and further including an identifier of the first data and/or the first time.
  • the second message also includes a second time, which is the time when the access network device expects to receive the second data; the transceiver module 710 is used to: send a third message based on the second time.
  • the processing module 720 is configured to: determine that the second QoS stream is associated with the first QoS stream based on the identifier of the second QoS stream used to carry the second data, wherein the first QoS stream is used to carry the second message; and determine a second moment from the second message carried by the first QoS stream.
  • the transceiver module 710 is configured to: send a fourth message, the fourth message including first data, and further including an identifier of the first data and/or a first moment; and receive a fifth message, the fifth message including second data, and further including an identifier of the first data and/or a first moment.
  • the fourth message also includes a third moment, which is the moment when the user plane function element expects to receive the second data.
  • the device 700 may specifically be the UPF network element in the embodiment shown in FIG. 6 above, or the functions of the UPF network element in the embodiment shown in FIG. 6 above may be integrated into the device 700.
  • the above functions may be implemented by hardware or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the device 700 may be used to execute the various processes and/or steps corresponding to the UPF network element in the above method embodiments.
  • module here may refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and/or other suitable components that support the described functions.
  • ASIC application-specific integrated circuit
  • processor e.g., a shared processor, a proprietary processor, or a group processor, etc.
  • memory for executing one or more software or firmware programs, integrated logic circuitry, and/or other suitable components that support the described functions.
  • device 700 may also be a chip or a chip system, such as a system-on-chip (SoC).
  • SoC system-on-chip
  • the transceiver module may be the transceiver circuit of the chip, and is not limited thereto.
  • FIG 8 is a schematic block diagram of another communication device 800 provided in an embodiment of this application.
  • the device 800 includes a processor 810.
  • the sensing device 800 also includes a transceiver 820 and a memory 830.
  • the processor 810, transceiver 820, and memory 830 communicate with each other via internal interconnection paths.
  • the memory 830 stores instructions, and the processor 810 executes the instructions stored in the memory 830 to control the transceiver 820 to transmit and/or receive signals.
  • the number of these processors 810 can be one or more.
  • the processor 810 and the memory 830 can be configured separately or integrated together.
  • the device 800 also includes a power supply circuit that can be used to supply power to the device 800.
  • the device 800 may specifically be a terminal, access network device, or UPF network element in the above embodiments, or the functions of the terminal, access network device, or UPF network element in the above embodiments may be integrated into the device 800.
  • the device 800 may be used to execute the various steps and/or processes corresponding to the terminal, access network device, or UPF network element in the above method embodiments.
  • the memory 830 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory.
  • the memory may also store device type information.
  • the processor 810 may be used to execute instructions stored in the memory, and when the processor executes the instructions, the processor 810 may execute the various steps and/or processes corresponding to the terminal, access network device, or UPF network element in the above method embodiments.
  • This application also provides a computer-readable storage medium for storing a computer program that, when run on a computer, causes the computer to perform the methods described in the above embodiments.
  • This application also provides a computer program product, which includes a computer program or instructions that, when executed, cause a computer to perform the methods described in the above embodiments.
  • the processor may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), 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.
  • each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software.
  • the steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware processor, or as a combination of hardware and software modules within the processor.
  • the software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor executes the instructions in the memory, combining them with its hardware to complete the steps of the above method. To avoid repetition, detailed descriptions are omitted here.
  • modules 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.
  • the modules described as separate components may or may not be physically separate.
  • the components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.
  • the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.
  • the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.
  • the aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种通信方法及相关装置，有利于避免数据丢失的问题。该方法包括：终端向接入网设备发送第一消息，第一消息包括第一数据和第一时刻，第一数据为业务相关的数据，第一时刻为终端期望接收到第二数据的时刻，第二数据是与第一数据关联的数据，或者，第二数据是与第一时刻关联的数据；接入网设备基于第一时刻，向终端发送第二数据。

Description

通信方法及相关装置
本申请要求于2024年05月30日提交中国专利局、申请号为202410698266.1、申请名称为“通信方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法及相关装置。
背景技术
在一些人机交互场景中，终端响应于用户操作产生交互数据，终端可以将交互数据通过基站传输给服务器，服务器会基于交互数据做出反馈，即通过基站向终端发送该交互数据的响应数据。基站在接收到来自服务器的响应数据之后，在预先配置好的接入网(access network，AN)-报文时延预算(packet delay budget，PDB)规定的时长内向终端发送该响应数据。
实际上，基站按照AN-PDB将响应数据发送给终端后，响应数据到达终端的时刻大概率会早于响应数据的生效时刻，这样终端需要将响应数据缓存一段时间，直至生效时刻。在生效时刻，终端可以播放根据该响应数据生成的视频画面，或者根据该响应数据给传感器施加压力。
然而，对于一些轻量级的终端(例如，扩展现实(extended reality，XR)眼镜)而言，其存储空间有限，在响应数据到达终端的时刻早于响应数据的生效时刻的场景下，终端没有足够的存储空间来存储响应数据，可能会带来数据丢失的问题。
发明内容
本申请提供一种通信方法及相关装置，有利于避免数据丢失的问题。
第一方面，提供了一种通信方法，该方法可以由第一通信装置执行，该第一通信装置可以为终端，也可以为配置在终端中的部件(例如处理器、芯片、或芯片系统等)，还可以为能实现全部或部分终端功能的逻辑模块或软件，本申请对此不做限定。下面以第一通信装置为终端为例介绍本申请的通信方法。
该方法包括：发送第一消息，第一消息包括第一数据和第一时刻，第一数据为业务相关的数据，第一时刻为终端期望接收到第二数据的时刻；以及，在第一时刻接收第二数据。
在一种可能的情形中，该业务可以为环回的业务，也就是说，该业务有上行数据的发送，以及有与该上行数据关联的下行数据的接收。上行数据对应本申请中的第一数据，与该上行数据关联的下行数据对应本申请中的第二数据，也就是说，第二数据是与第一数据关联的数据，终端期望在第一时刻接收到与第一数据关联的数据。
与第一数据关联的数据，也可以描述为，第一数据的响应数据，或者，第一数据的反馈数据。
在另一种可能的情形中，第二数据与第一数据无关，第二数据是与第一时刻关联的数据，换言之，第二数据是终端期望在第一时刻接收到的数据。
终端期望接收到第二数据的时刻，也可以描述为，终端要求接收到第二数据的时刻，或者，终端需要接收到第二数据的时刻，或者，终端请求接收到第二数据的时刻。
在本申请中，终端期望在第一时刻接收到第二数据，是因为终端在第一时刻接收到第二数据之后，可以立即生效第二数据，这样有利于避免第二数据提前到达终端却没有足够的存储空间进行存储的问题，进而有利于避免数据丢失的问题。
结合第一方面，在第一方面的某些实现方式中，在发送第一消息之间，该方法还包括：建立第一服务流，以及，建立第二服务流，第一服务流用于承载第一消息，第一消息包括第一数据，也即，第一服务流用于承载第一数据，第二服务流用于承载第二数据。
其中，服务流可以定义一组满足用户的服务质量要求的参数，服务流例如为服务质量(quality of service，QoS)流，或者为已有或未来的协议中定义的其它能够实现相同或相似功能的术语，本申请对此不做限定。下文以建立第一QoS流和建立第二QoS流为例进行描述。
结合第一方面，在第一方面的某些实现方式中，在建立第一QoS流之后，该方法还包括：接收第一请求消息，第一请求消息用于请求建立第二QoS流，第一请求消息包括第一QoS流的第一标识。
结合第一方面，在第一方面的某些实现方式中，在建立第二QoS流之后，该方法还包括：发送第二请求消息，第二请求消息用于请求建立第一QoS流，第二请求消息包括第二QoS流的第一标识。
结合第一方面，在第一方面的某些实现方式中，在建立第一QoS流以及建立第二QoS流之前，该方法还包括：发送第三请求消息，第三请求消息用于请求建立第一QoS流和第二QoS流，第三请求消息包括第一QoS流的第一标识和第二QoS流的第一标识。或者，第三请求消息包括与第一QoS流相关的QoS参数和第二QoS流相关的QoS参数。
结合第一方面，在第一方面的某些实现方式中，在建立第一QoS流以及建立第二QoS流之前，该方法还包括：发送第四请求消息，第四请求消息用于请求建立第一QoS流和第二QoS流；以及，接收第四请求消息的响应消息，该响应消息包括第一QoS流的第一标识和第二QoS流的第一标识。
结合第一方面，在第一方面的某些实现方式中，第一QoS流的第二标识和第二QoS流的第二标识相同。其中，第二标识用于表示第一QoS流与第二QoS流相关，或者说，用于表示第一QoS流与第二QoS流属于同一个组，或者说，用于表示第一QoS流和第二QoS流属于同一个业务、且分别用于该业务的上行数据传输和下行数据传输。
结合第一方面，在第一方面的某些实现方式中，在发送第一消息之前，该方法还包括：根据生成第一数据的时刻以及时延要求，确定第一时刻。
结合第一方面，在第一方面的某些实现方式中，第一消息还包括第一数据的标识。
结合第一方面，在第一方面的某些实现方式中，在第一时刻接收第二数据之前，该方法还包括：接收配置信息，该配置信息包括第二数据的传输资源，传输资源至少包括时域资源和频域资源。
结合第一方面，在第一方面的某些实现方式中，该配置信息还包括非连续接收(discontinuous reception，DRX)的配置和/或测量间隙的配置。
第二方面，提供了一种通信方法，该方法可以由第二通信装置执行，该第二通信装置可以为接入网设备，也可以为配置在接入网设备中的部件(例如处理器、芯片、或芯片系统等)，还可以为能实现全部或部分接入网设备功能的逻辑模块或软件，本申请对此不做限定。下面以第二通信装置为接入网设备为例介绍本申请的通信方法。
该方法包括：接收第一消息，第一消息包括第一数据和第一时刻，第一数据为业务相关的数据，第一时刻为终端期望接收到第二数据的时刻，第二数据是与第一数据关联的数据，或者，第二数据是与第一时刻关联的数据；以及，基于第一时刻，发送第二数据。
结合第二方面，在第二方面的某些实现方式中，在基于所述第一时刻，发送第二数据之前，该方法还包括：根据用于承载第二数据的第二QoS流的标识，确定第二QoS流与第一QoS流关联，第一QoS流用于承载第一消息，第一消息包括第一数据，也即，第一QoS流用于承载第一数据；以及，从第一QoS流承载的第一消息中确定第一时刻。
结合第二方面，在第二方面的某些实现方式中，第一消息还包括所述第一数据的标识。需要说明的是，此处的第一数据的标识是由终端分配的，终端可以通过第一消息将第一数据的标识发送给接入网设备。
在另一种可能的实现方式中，终端未给第一数据分配标识，第一消息可以不包括第一数据的标识，那么接入网设备在接收到第一数据之后，为第一数据分配标识。
结合第二方面，在第二方面的某些实现方式中，在基于所述第一时刻，发送第二数据之前，该方法还包括：发送第二消息，第二消息包括第一数据，还包括第一数据的标识和/或第一时刻；以及，接收第三消息，第三消息包括第二数据，还包括第一数据的标识和/或第一时刻。
应理解的是，第二消息或第三消息中的第一数据的标识可以是由终端分配的，也可以是由接入网设备分配的。
结合第二方面，在第二方面的某些实现方式中，第二消息还包括第一数据的标识，第三消息还包括第一数据的标识。从第一QoS流承载的第一消息中确定第一时刻，包括：根据第一数据的标识，从第一QoS流承载的第一消息中确定第一时刻。
结合第二方面，在第二方面的某些实现方式中，第二消息还包括第二时刻，第二时刻为接入网设备期望接收到第二数据的时刻。
结合第二方面，在第二方面的某些实现方式中，在接收第一消息之后，该方法还包括：在支持终端在第一时刻接收到第二数据的情况下，发送配置信息，该配置信息包括第二数据的传输资源，传输资源包括时域资源和频域资源。
结合第二方面，在第二方面的某些实现方式中，该配置信息还包括DRX的配置和/或测量间隙的配置。
第三方面，提供了一种通信方法，该方法可以由第三通信装置执行，该第二通信装置可以为用户面功能(user plane function，UPF)网元，也可以为配置在UPF网元中的部件(例如处理器、芯片、或芯片系统等)，还可以为能实现全部或部分UPF网元功能的逻辑模块或软件，本申请对此不做限定。下面以第三通信装置为UPF网元为例介绍本申请的通信方法。
该方法包括：接收第二消息，第二消息包括第一数据，还包括第一数据的标识和/或第一时刻，第一数据为业务相关的数据，第一时刻为终端期望接收到第二数据的时刻，第二数据是与第一数据关联的数据，或者，第二数据是与第一时刻关联的数据；以及，发送第三消息，第三消息包括第二数据，还包括第一数据的标识和/或第一时刻。
结合第三方面，在第三方面的某些实现方式中，第二消息还包括第二时刻，第二时刻为接入网设备期望接收到第二数据的时刻。发送第三消息，包括：基于第二时刻，发送第三消息。
结合第三方面，在第三方面的某些实现方式中，在基于第二时刻，发送第三消息之前，该方法还包括：根据用于承载所述第二数据的第二QoS流的标识，确定第二QoS流与第一QoS流关联，第一QoS流用于承载第二消息；以及，从第一QoS流承载的第二消息中确定第二时刻。
结合第三方面，在第三方面的某些实现方式中，在发送第三消息之前，该方法还包括：发送第四消息，第四消息包括第一数据，还包括第一数据的标识和/或第一时刻；以及，接收第五消息，第五消息包括第二数据，还包括第一数据的标识和/或第一时刻。
结合第三方面，在第三方面的某些实现方式中，第四消息还包括第三时刻，第三时刻为用户面功能网元期望接收到第二数据的时刻。
第四方面，提供一种通信方法，该方法可以由第四通信装置执行，该第四通信装置可以为服务器，也可以为配置在服务器中的部件(例如处理器、芯片、或芯片系统等)，还可以为能实现全部或部分服务器功能的逻辑模块或软件，本申请对此不做限定。下面以第四通信装置为服务器为例介绍本申请的通信方法。
该方法包括：接收第四消息，第四消息包括第一数据，还包括所述第一数据的标识和/或第一时刻，第一数据为业务相关的数据，第一时刻为终端期望接收第二数据的时刻，第二数据是与第一数据关联的数据，或者，第二数据是与第一时刻关联的数据；以及，发送第五消息，第五消息包括第二数据，还包括第一数据的标识和/或第一时刻。
结合第四方面，在第四方面的某些实现方式中，第四消息还包括第三时刻，第三时刻为用户面功能网元期望接收到第二数据的时刻。发送第五消息，包括：基于第三时刻，发送第五消息。
应当理解的是，本申请的第二方面至第四方面与本申请的第一方面的技术方案相对应，各方面及对应的可行实施方式所取得的有益效果相似，不再赘述。
第五方面，提供了一种通信装置，包括：用于执行上述任一方面中任一种可能的实现方式中的方法。具体地，该装置包括用于执行上述任一方面中任一种可能的实现方式中的方法的模块。
在一种设计中，该装置可以包括执行上述第一方面中所描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
在另一种设计中，该装置为通信芯片，通信芯片可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
在另一种设计中，该装置为终端、接入网设备、UPF网元或服务器，终端、接入网设备、UPF网元或服务器可以包括用于发送信息或数据的发射机，用于接收信息或数据的接收机。
在另一种设计中，该装置用于执行上述任一方面任意可能的实现方式中的方法，该装置可以配置在终端、接入网设备、UPF网元或服务器中。
第六方面，提供了一种通信装置，包括，至少一个处理器，所述至少一个处理器用于从存储器中调用并运行计算机程序，使得该装置执行上述任一方面中任一种可能的实现方式中的方法。
可选地，该装置还包括存储器，该存储器可用于存储指令和数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的指令时，可以实现上述各方面中描述的方法。
可选地，该装置还包括：发射机(发射器)和接收机(接收器)，发射机和接收机可以分离设置，也可以集成在一起，称为收发机(收发器)。
第七方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述任一方面中任一种可能实现方式中的方法。
第八方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述任一方面中任一种可能实现方式中的方法。
第九方面，本申请提供了一种芯片系统，该芯片系统器包括至少一个处理，用于支持实现上述任一方面中任一种可能实现方式中所涉及的功能，例如，接收或处理上述方法中所涉及的数据等。
在一种可能的设计中，所述芯片系统还包括存储器，所述存储器用于保存程序指令和数据，存储器位于处理器之内或处理器之外。
可选地，该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
附图说明
图1是适用于本申请实施例的通信系统的示意图；
图2是适用于本申请实施例的一种网络架构示意图；
图3是适用于本申请实施例的一种场景示意图；
图4是本申请实施例提供的一种数据传输的示意图；
图5是本申请实施例提供的一种调整AN-PDB的示意图；
图6是本申请实施例提供的一种通信方法的示意性流程图；
图7和图8是本申请实施例提供的通信装置的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
在介绍本申请实施例提供的通信方法及相关装置之前，先做出以下几点说明。
第一，在下文示出的实施例中，各术语及英文缩略语，如UPF、QoS流、SDU等，均为方便描述而给出的示例性举例，不应对本申请构成任何限定。本申请并不排除在已有或未来的协议中定义其它能够实现相同或相似功能的术语的可能。
第二，在下文示出的实施例中第一、第二以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，第一时刻和第二时刻仅为区分不同的时刻，并不限制时间上的先后顺序。
第三，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b和c中的至少一项(个)，可以表示：a，或b，或c，或a和b，或a和c，或b和c，或a、b和c，其中a，b，c可以是单个，也可以是多个。
第四，本申请中的“发送”和“接收”，表示信号传递的走向。例如，“向接入网设备发送第一消息”，可以理解为该第一消息的目的端是接入网设备，可以包括通过空口直接发送，也包括其他单元或模块通过空口间接发送。“接收来自终端的第一消息”可以理解为第一消息的源端是终端，可以包括通过空口直接从终端接收，也可以包括通过空口从其他单元或模块间接地从终端接收。“发送”也可以理解为芯片接口的“输出”，“接收”也可以理解为芯片接口的“输入”。
换言之，发送和接收可以是在设备之间进行的，例如，终端和接入网设备之间进行的；也可以是在设备内进行的，例如，通过总线、走线或接口在设备内的部件之间、模组之间、芯片之间、软件模块或者硬件模块之间发送或接收。
图1是适用于本申请实施例的通信系统的示意图。图1所示的通信系统1000包括无线接入网(radioaccess network，RAN)100和核心网(core network，CN)200。可选地，通信系统1000还包括互联网300。其中，无线接入网100可以包括至少一个RAN节点(如图1中的110a和110b)，还可以包括至少一个终端(如图1中的120a-120j)。终端通过无线的方式与RAN节点相连，RAN节点通过无线或有线方式与核心网200连接。核心网设备与RAN节点可以是独立的不同的物理设备，也可以是将核心网设备的功能与RAN节点的逻辑功能集成在同一个物理设备上，还可以是一个物理设备上集成了部分核心网设备的功能和部分的RAN节点的功能。终端和终端之间以及RAN节点和RAN节点之间可以通过有线或无线的方式相互连接。图1只是示意图，该通信系统中还可以包括其它RAN节点，如还可以包括无线中继设备和无线回传设备，在图1中未示出。
无线接入网100可以为第三代合作伙伴计划(3rd generation partnership project，3GPP)相关的蜂窝系统，例如，第四代移动通信技术(4th generation mobile communication technology，4G)系统(又称为长期演进(long term evolution，LTE)系统)，第五代移动通信技术(5th generation mobile communication technology，5G)系统(又称为新空口(new radio，NR)系统)，或者还可以应用于下一代移动通信系统或其他类似的通信系统(例如第六代移动通信技术(6th generation mobile communication technology，6G)系统)等，本申请对此不做限定。
无线接入网100还可以是开放式RAN(open-RAN、O-RAN或ORAN)、云无线接入网络(cloud radio access network，CRAN)。无线接入网100还可以是非地面网络(non-terrestrial network，NTN)，卫星通信网络，高空平台站(high altitude platform station，HAPS)通信网络，接入回传一体化(integrated access and backhaul，IAB)通信网络，可重构智能表面(reconfigurable intelligent surface，RIS)通信网络等。无线接入网100还可以是以上两种或两种以上系统融合的通信系统。
RAN节点又可以称为RAN设备或接入网设备。RAN节点用于帮助终端实现无线接入。通信系统1000中的多个RAN节点可以为同一类型的节点，也可以为不同类型的节点。
本申请实施例提供的RAN节点可以是基站(base station)、节点B(Node B)、演进型节点B(evolved NodeB，eNodeB或eNB)、发送接收点(transmission reception point，TRP)、5G或NR中的下一代节点B(next generation NodeB，gNB)、开放无线接入网(open radio access network，O-RAN或open RAN)中的RAN节点、第六代移动通信技术(6th generation mobile communication technology，6G)中的下一代基站。或者，RAN节点还可以是非地面网络(non-terrestrial network，NTN)通信网络中的卫星基站、或者是未来移动通信系统中的基站、或无线保真(wireless fidelity，Wi-Fi)系统中的接入节点等。或者，RAN节点还可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(centralized unit，CU)、分布式单元(centralized unit，DU)，CU的功能可以由一个实体来实现，也可以由不同的实体实现。例如，可以对CU的功能进行进一步切分，例如，将控制面(control plane，CP)和用户面(user plane，UP)分离，即CU的控制面(CU-CP)和CU的用户面(CU-UP)。RAN节点可以是宏基站，RAN节点还可以是微基站或室内站，还可以是中继节点或宿主节点等。本申请中对RAN节点所采用的具体技术和具体设备形态不做限定。
终端是具有无线收发功能的设备，可以向RAN节点发送信号，或接收来自RAN节点的信号。终端还可以称为终端装置、终端设备、用户设备(user equipment，UE)、移动台、移动终端等。终端可以广泛应用于各种场景，例如，D2D、V2X通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端具体可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、飞机、轮船、机器人、机械臂、智能家居设备等。本申请的实施例对终端所采用的具体技术和具体设备形态不做限定。
终端可以广泛应用于各种场景进行通信。该场景例如包括但不限于以下至少一个场景：增强移动宽带(enhanced mobile broadband，eMBB)、超高可靠性超低时延通信(ultra-reliable low-latency communication，URLLC)、大规模机器类型通信(massive machine-type communications，mMTC)、设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)、机器类型通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、或智慧城市等。终端可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、直升机、飞机、无人机、轮船、机器人、机械臂、或智能家居设备等。本申请对终端设备所采用的具体技术和具体设备形态不做限定。
RAN节点和终端可以是固定位置的，也可以是可移动的。RAN节点和终端可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在飞机、气球和人造卫星上。本申请的实施例对RAN节点和终端的应用场景不做限定。
RAN节点和终端的角色可以是相对的。例如，图1中的直升机或无人机120i可以被配置成移动RAN节点，对于那些通过120i接入到无线接入网100的终端120j来说，终端120i是RAN节点；但对于RAN节点110a来说，120i是终端，即110a与120i之间是通过无线空口协议进行通信的。当然，110a与120i之间也可以是通过RAN节点与RAN节点之间的接口协议进行通信的，此时，相对于110a来说，120i也是RAN节点。因此，RAN节点和终端都可以统一称为通信装置，图1中的110a和110b可以称为具有RAN节点功能的通信装置，图1中的120a-120j可以称为具有终端功能的通信装置。
RAN节点和终端之间、RAN节点和RAN节点之间、终端和终端之间可以通过授权频谱进行通信，也可以通过免授权频谱进行通信，也可以同时通过授权频谱和免授权频谱进行通信；可以通过6千兆赫兹(gigahertz，GHz)以下的频谱进行通信，也可以通过6GHz以上的频谱进行通信，还可以同时使用6GHz以下的频谱和6GHz以上的频谱进行通信。本申请的实施例对无线通信所使用的频谱资源不做限定。
在本申请的实施例中，RAN节点的功能也可以由RAN节点中的模块(如芯片)来执行，也可以由包含有RAN节点功能的控制子系统来执行。这里的包含有RAN节点功能的控制子系统可以是智能电网、工业控制、智能交通、智慧城市等上述应用场景中的控制中心。终端的功能也可以由终端中的模块(如芯片或调制解调器)来执行，也可以由包含有终端功能的装置来执行。
核心网设备是指为终端提供业务支持的核心网中的设备。目前，一些核心网设备的举例为：接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、UPF网元等等，此处不一一列举。
图2是适用于本申请实施例的一种网络架构示意图。图2以第五代移动通信技术(5th generation mobile communication technology，5G)网络架构为例，示出的网络功能和实体包括：UE、RAN、UPF、AMF、SMF、数据网络(data network，DN)。
需要说明的是，在一些实施例中还可以包括比图2所示的更多或更少的网络功能和实体，在此不做限定。例如，可选地，该网络架构还包括统一数据管理(unified data management，UDM)、网络暴露功能(network exposure function，NEF)、策略控制功能(policy control function，PCF)、网络存储功能(network repository function，NRF)、网络切片选择功能(network slice selection function，NSSF)、认证服务器功能(authentication server function，AUSF)、网络数据分析功能(network data analytics function，NWDAF)。
本申请中所示出的各网络功能和实体的名称均为方便描述而给出的示例性举例，不应对本申请构成任何限定。本申请并不排除在已有或未来的协议中定义其它能够实现相同或相似功能的术语的可能。
图2中的UE、RAN、UPF以及DN通常被称为用户面(或数据面)网络功能和实体，用户的数据流量可以通过UE和DN之间建立的协议数据单元(protocol data unit，PDU)会话进行传输，传输会经过RAN节点和UPF这两个网络功能和实体，UPF可以认为是核心网的用户面网元。其他的网元则被称为控制面网络功能和实体(或称为控制面网元)，主要负责认证和鉴权、注册管理、会话管理、移动性管理以及策略控制等功能，从而实现用户层流量可靠稳定的传输。其中，用户面用于承载业务数据，控制面用于承载信令消息。
图2中示出了网络功能和实体之间的交互关系以及对应的接口。例如，UE和AMF之间可以通过N1接口进行交互，交互消息称为N1消息(N1 message)。部分接口采用服务化接口的方式实现。
AMF是提供接入管理功能的网元、模块或组件，主要负责信令处理部分，例如：接入控制、移动性管理、附着与去附着以及网关选择等功能。AMF网元为终端中的会话提供服务的情况下，会为该会话提供控制面的存储资源，以存储会话的标识、与会话的标识关联的SMF的标识等。
SMF是负责处理用户业务的网元、模块或组件，例如用户面功能选择，用户面功能重定向，IP地址的分配，承载的建立、修改和释放以QoS控制。
UPF负责终端中用户数据的转发和接收。UPF可以从DN接收用户数据，通过RAN节点传输给UE；UPF还可以通过RAN节点从UE接收用户数据，转发到DN。UPF中为UE提供服务的传输资源和调度功能由SMF网元管理控制。
下面对本申请涉及的相关技术和概念进行介绍。
在一些人机交互场景中，终端响应于用户操作产生交互数据，终端可以将交互数据通过基站传输给服务器(该服务器例如为部署在上述图2所述的DN中的服务器)，服务器通过基站向终端发送与该交互数据关联的数据，所述与该交互数据关联的数据可以看作是该交互数据的响应数据。基站在接收到来自服务器的响应数据之后，可以根据历史调度信息以及应用的端到端时延估计基站和终端之间的AN-PDB，随后基站在AN-PSDB规定的时长内向终端发送该响应数据。这种调度方式称为基于时延的调度。
参见图3的一个示例场景，终端为XR眼镜，XR眼镜响应于用户的转头操作生成转头数据，服务器在接收到该转头数据之后，根据该转头数据生成与该转头数据关联的画面数据。之后，服务器通过基站向终端发送该画面数据。
然而，在实际的数据传输过程中，该画面数据实际到达基站的时刻(简称为实际到达时刻)与理论上到达基站的时刻(简称为理论到达时刻)可能存在误差，参见图4所示的数据传输的示意图，若该画面数据的实际到达时刻早于该画面数据的理论到达时刻，这样实际上留给基站调度的时间很充足，但是基站依然按照预先估计的AN-PDB向终端发送该画面数据，那么该画面数据会提前到达终端，所以终端需要将该画面数据进行缓存直至规定的画面推送时刻，在该画面推送时刻，终端在屏幕上显示画面。若该画面数据的实际到达时刻晚于该画面数据的理论到达时刻，该画面数据可能即将过期，但是基站依然按照预先估计的AN-PDB向终端发送该画面数据，这样，很可能终端接收到该画面数据的时刻已经过了规定的画面推送时刻，这样会影响用户体验。
在基于时延的调度基础上，考虑到数据可能早于或晚于理论到达时刻，参见图5所示的调整AN-PDB的示意图，基站可以根据数据的实际到达时刻与理论到达时刻之间的偏差，延长或者缩短AN-PDB的大小。
然而，这种动态调整AN-PDB的方式仅能针对周期性业务的数据传输，因为周期性业务存在理论到达时刻，因此，基站才可以根据数据的实际到达时刻与理论到达时刻之间的偏差调整AN-PDB的大小。对于非周期性业务而言，例如随机的突发业务，基站在收到数据之后，可能都无法获知数据的生成时刻，因此更加无法获知数据的理论到达时刻，也就无法调整AN-PDB的大小。此外，在AN-PDB的约束下，数据大概率会早于规定的生效时刻到达终端，那么数据就需要在终端上缓存一段时间直至规定的生效时刻。但是，对于一些轻量级的终端，例如，XR眼镜、智能手环等而言，其存储空间有限，在数据到达终端的时刻早于生效时刻的情况下，终端没有足够的存储空间来存储数据，可能会带来数据丢失的问题。
有鉴于此，本申请提供一种通信方法，在该方法中，终端可以将终端期望接收到数据的时刻告知基站，这样，基站便可以有依据地向终端发送该数据，以使终端可以在该时刻接收到该数据。终端在该时刻接收到该数据后，无需缓存立即生效，这样可以避免存储空间有限的终端丢失数据的问题。
图6是本申请实施例提供的一种通信方法600的示意性流程图，方法600包括S601和S602，可选地，方法600还包括S603至S608，具体步骤如下：
S601，终端向接入网设备发送第一消息，第一消息包括第一数据和第一时刻，第一数据为业务相关的数据，第一时刻为终端期望接收到第二数据的时刻，第二数据是与第一数据关联的数据，或者，第二数据是与第一时刻关联的数据。相应地，接入网设备接收第一消息。
第一数据例如为业务数据单元(service data unit，SDU)。
在一种情形中，第二数据是与第一数据关联的数据，或者说，第二数据是第一数据的响应数据或反馈数据。
在一个示例场景中，终端为XR眼镜，XR眼镜响应于用户的转头操作，生成转头数据，之后，终端可以接收到该转头数据对应的角度的画面数据。在本示例中，第一数据为转头数据，与第一数据关联的数据为该转头数据对应的角度的画面数据。其中，转头数据也可以描述为与转头相关的控制指令。
在另一个示例场景中，终端为手机，手机响应于用户的拍照操作，生成原始图像数据，之后，手机可以接收到对该原始图像数据渲染后的图像数据。在本示例中，第一数据为原始图像数据，与第一数据关联的数据为对该原始图像数据渲染后的图像数据。
在另一个示例场景中，终端为XR触觉手套，XR触觉手套响应于用户的手势操作，生成手势数据，之后，XR触觉手套可以接收该手势数据对应的触感数据。在本示例中，第一数据为手势数据，与第一数据关联的数据为该触感数据。
在另一种情形中，第二数据是与第一时刻关联的数据，而与第一数据无关，换言之，第二数据是终端期望在第一时刻接收到的数据。
终端期望接收到第二数据的时刻，也可以描述为，终端要求接收到第二数据的时刻，或者，终端请求接收到第二数据的时刻，或者，终端需要接收到第二数据的时刻。
S602，接入网设备基于第一时刻，向终端发送第二数据。相应地，终端接收第二数据。
在一种可能的实现方式中，终端包括通信接口和应用(或传感器)，该应用例如为相机应用、视频类应用、游戏类应用等，传感器例如为摄像头、压力传感器、触觉传感器、视觉传感器、生物传感器等。应用(或传感器)生成第一数据，并将第一数据传输至通信接口，然后通信接口向接入网设备发送第一数据。相应地，终端的通信接口接收来自接入网设备的第二数据，然后通信接口向应用(或传感器)发送第二数据，并在应用(或传感器)上生效所述第二数据，例如，在相机应用显示基于第二数据生成的图像，又例如，在视频类应用上显示基于第二数据生成的视频，又例如，在触觉触感器上施加基于第二数据生成的压力。
需要说明的是，应用(或传感器)生成第一数据之后，可以向通信接口发送第一数据和第四时刻，第四时刻为应用(或传感器)期望接收到第二数据的时刻，或者说，第四时刻为第二数据在应用(或传感器)上生效的时刻。
其中，生效可以替换为使用、实施、执行、显示、播放等，参照上面的示例，第一数据为转头数据，第二数据为该转头数据对应的角度的画面数据，则生效是指，播放基于该画面数据生成的画面；第一数据为原始图像数据，第二数据为对该原始图像数据渲染后的图像数据，则生效是指，显示基于该渲染后的图像数据生成的图像；第一数据为手指操作，第二数据为该手势数据对应的触感数据，则生效是指，基于该触感数据给传感器施加压力，或者，执行震动操作。
在一种可能的实现方式中，应用(或传感器)根据生成第一数据的时刻与时延要求，确定第四时刻。时延要求可以是往返时延(round trip time，RTT)的要求，或者是动显(motion-to-photon，MTP)时延的要求。
应理解的是，第四时刻为应用层面的时间信息，例如几点几分几秒。
本申请实施例所述的第一时刻为终端的通信接口期望接收到第二数据的时刻，通信接口在接收到第一数据和第四时刻之后，基于第四时刻，并考虑如下一项或多项时延因素确定第一时刻：第二数据从通信接口传输到应用(或传感器)的时延、通信接口的调度时延或通信接口的内部处理时延。基于上述对第一时刻的限定，通信接口在第一时刻接收到第二数据之后无需存储便可以直接将其发送至应用(或传感器)。
第一时刻为通信系统可以理解的时间信息，例如为系统帧号、时隙号、正交频分复用(orthogonal frequency division multiplexing，OFDM)符号。
更具体地，S602包括：接入网设备基于第一时刻以及时延因素确定第二数据的发送时刻，记为第五时刻，并在第五时刻向终端发送第二数据。其中，时延因素包括如下一项或多项：网络负载情况、UE行为、接入网设备与终端之间的传输时延、接入网设备的内部处理时延或接入网设备的调度时延。这样，接入网设备在第五时刻发送第二数据，可以满足终端在第一时刻接收到第二数据的需求。
需要说明的是，当接入网设备和终端之间的传输时延很短，甚至短于单位时间的时候，第一时刻与第五时刻可能为同一时刻。例如，在以时隙为时间单位时，每个时隙是0.5ms，当接入网设备和终端之间的传输时延短于0.5ms时，那么第五时刻的时隙号与第一时刻的时隙号相同，即第一时刻与第五时刻为同一时刻。
在本申请实施例中，终端之所以期望在第一时刻接收到第二数据，是因为终端在第一时刻接收到第二数据之后，可以立即生效第二数据，这样，对于存储空间有限的终端而言，有利于避免第二数据提前到达终端却没有足够的存储空间进行存储的问题，进而有利于避免数据丢失的问题。
在另一些实施例中，方法600还可以包括更多的步骤，例如下面所介绍的S603至S608，对各步骤的介绍如下。
终端的一个业务关联上行和下行两路数据传输，且两路数据传输的数据特征相差较大。例如，上行传输的转头数据对时延要求高但是对带宽要求低，而下行传输的画面数据对带宽要求高但是对可靠性没有要求。因此，需要建立两条不同的服务流以满足上行和下行的传输需求。其中，服务流可以定义一组满足用户的服务质量要求的参数，服务流例如为QoS流，或者为已有或未来的协议中定义的其它能够实现相同或相似功能的术语，本申请对此不做限定。下面以建立两路QoS流为例进行描述，两路QoS流分别用于上行传输和下行传输。
在一种可能的实现方式中，在S601之前，方法600还包括S603：终端与核心网的控制面网元交互建立第一QoS流和第二QoS流，其中，第一QoS流用于承载第一消息，第二QoS流用于承载第二数据。在建立第一QoS流和第二QoS流之后，终端可以与UPF网元传输业务相关的数据。
上述第一QoS流和第二QoS流的调度具有相关性，或者说是相对应的，因此，需要将第一QoS流和第二QoS流相关联，通过第一QoS流和第二QoS流的关联关系，可以将QoS流承载的数据与第二QoS流承载的数据相关联，实现数据的准确调度。
下面对如何将第一QoS流和第二QoS流相关联进行说明。
在一种可能的实现方式中，终端先触发建立第一QoS流，在第一QoS流建立之后，控制面网元(例如，AMF网元)触发建立第二QoS流，例如，控制面网元向终端发送第一请求消息，第一请求消息用于请求建立第二QoS流，第一请求消息包括第一QoS流的第一标识。可选地，第一请求消息还包括第二QoS流的第一标识。这样，通过在请求建立第二QoS流的消息中携带第一QoS流的第一标识将第一QoS流和第二QoS流相关联。
第一标识为QoS流的流标识，例如为QoS流标识符(QoS flow identifier，QFI)，或者为5G中的QoS标识符(5G QoS identifier，5QI)，或者是具有类似功能的标识，本申请对此不做限定。
在另一种可能的实现方式中，控制面网元先触发建立第二QoS流，在第二QoS流建立之后，终端触发建立第一QoS流，例如，终端向控制面网元发送第二请求消息，第二请求消息用于请求建立第一QoS流，第二请求消息包括第二QoS流的第一标识。这样，通过在请求建立第一QoS流的消息中携带第一QoS流的第一标识和第二QoS流的第一标识将第一QoS流和第二QoS流相关联。
需要说明的是，终端在建立第一QoS流的过程中会将第一QoS流的第一标识发送给控制面网元，这样，控制面网元可以获取到第一QoS流的第一标识，进而可以在第一请求消息中携带第一QoS流的第一标识。类似地，控制面网元在建立第二QoS流的过程中会将第二QoS流的第一标识发送给终端，这样，终端可以获取到第二QoS流的第一标识，进而可以在第二请求消息中携带第二QoS流的第一标识。
在另一种可能的实现方式中，终端触发建立第一QoS流以及建立第二QoS流，例如，终端向控制面网元发送第三请求消息，第三请求消息用于请求建立第一QoS流和建立第二QoS流，第三请求消息包括第一QoS流的第一标识和第二QoS流的第一标识，这样，终端一次请求建立两条QoS流，并且通过在第三请求消息中携带第一QoS流的第一标识和第二QoS流的第一标识将第一QoS流和第二QoS流相关联。
在另一种可能的实现方式中，终端触发建立第一QoS流以及建立第二QoS流，例如，终端向控制面网元发送第四请求消息，第四请求消息用于请求建立第一QoS流和建立第二QoS流。终端接收来自控制面网元的第四请求消息的响应消息，该响应消息包括第一QoS流的第一标识和第二QoS流的第一标识。这样，通过在第四请求消息的响应消息中携带第一QoS流的第一标识和第二QoS流的第一标识将第一QoS流和第二QoS流相关联。
在另一种可能的实现方式中，在建立第一QoS流和第二QoS流之后，控制面网元为第一QoS流和第二QoS流分配一个统一的标识以将第一QoS流和第二QoS流相关联。
该统一的标识可以看作是第一QoS流的第二标识以及第二QoS流的第二标识。例如，第二标识为组标识(或称为属组标识、分组标识、类标识)，第一QoS流和第二QoS流具有相同的组标识，说明第一QoS流和第二QoS流属于同一组，也即第一QoS流和第二QoS流相关联。
结合上面的描述，在一种可能的实现方式中，在终端建立第一QoS流时，终端可以向控制面网元发送第五请求消息，第五请求消息用于请求建立第一QoS流，第五请求消息中携带第一QoS流的第一标识以及第一QoS流的第二标识；或者，终端接收到来自控制面网元的第五请求消息的响应消息，该响应消息中包括第一QoS流的第一标识和第二标识。在第一QoS流建立之后，在建立第二QoS流时，控制面网元向终端发送第六请求消息，第六请求消息包括第二QoS流的第一标识以及第二标识，这样，第一QoS流和第二QoS流都具体第二标识，表示第一QoS流和第二QoS流属于同一组，或者是属于同一个业务的分别用于上行传输和下行传输的QoS流。
接入网设备在接收到第一消息之后，可以根据自己的能力判断是否可以满足终端在第一时刻接收到第二数据的需求，或者说，是否支持终端在第一时刻接收到第二数据。在一种可能的实现方式中，接入网设备根据接入网设备与终端之间的历史时间内的RTT判断是否支持终端在第一时刻接收到第二数据。
例如，历史往返时延为10ms，终端发出第一数据的时刻记为t1，第一时刻记为t2，若t2-t1小于10ms，则接入网设备无法满足终端在第一时刻接收到第二数据的需求，若t2-t1大于或等于10ms，则接入网设备可以满足终端在第一时刻接收到第二数据的需求。
在另一种可能的实现方式中，接入网设备可以预估接入网设备在第五时刻是否有足够的传输资源来调度第二数据，第五时刻为接入网设备发送第二数据的时刻。例如，对于一些实时业务，或者保证比特率类型(guaranteed bit rate，GBR)的业务，接入网设备已经为其提前预留传输资源，也就是在第五时刻接入网设备没有空闲资源来调度第二数据，因此无法满足终端在第一时刻接收到第二数据的需求。
可选地，接入网设备在可以满足终端在第一时刻接收到第二数据的需求的情况下，在S602之前，方法600还包括S604：接入网设备向终端发送配置信息，相应地，终端接收该配置信息。该配置信息包括第二数据的传输资源，例如，时域资源和频域资源，以告知终端在哪个时间在哪个频段上检测接入网设备发送的第二数据。
在一些可能的情况下，终端在第一时刻处于DRX睡眠阶段，在DRX睡眠阶段，终端可以停止部分或全部功能模块从而无法接收到第二数据。因此，接入网设备可以基于第一时刻调整DRX配置，并在该配置信息中携带调整后的DRX的配置，以避免终端由于处于DRX睡眠阶段而无法在第一时刻接收到所述第二数据的情况发生。
在一些可能的情况下，第一时刻处于测量间隙对应的时段内，也就是说，终端可能在第一时刻进行小区测量等操作，在测量间隙对应的时段内，终端无法进行数据传输。因此，接入网设备可以基于第一时刻调整测量间隙的配置，并在该配置信息中携带调整后的测量间隙的配置，这样可以避免第一时刻处于测量间隙对应的时段内，进而有利于避免终端无法在第一时刻接收到第二数据的情况发生。
终端的业务会产生多份数据，通过数据的标识可以区分多份数据，本申请实施例中的第一数据为一份数据，例如，第一数据为一个PDU集合(PDU set)，一个PDU集合可以看作是一份数据，又例如，第一数据为一个数据突发(data burst)，一个数据突发(data burst)可以看作是一份数据。
作为一个可选的实施例，第一消息还包括第一数据的标识，该标识是针对业务的标识，例如是PDU集合的标识或数据突发的标识。第一数据为图像数据时，第一数据的标识可以是图像的标识。
在上面的描述中，终端包括通信接口和应用(或传感器)，应用(或传感器)可以为第一数据分配一个标识，之后应用(或传感器)向通信接口发送第一数据的标识。或者，应用(或传感器)未为第一数据分配标识，则通信接口在从应用(或传感器)接收到第一数据之后，为第一数据分配一个标识。
第一数据的标识也可以描述为第一数据的索引，或者第一数据的序列号(sequence number，SN)，本申请实施例对此不做限定。
接入网设备在接收到第一消息之后，在第一消息还包括第一数据的标识的情况下，接入网设备记录第一数据的标识与第一时刻的关联关系，该关联关系指示终端期望在第一时刻接收到第二数据。
例如，终端响应于用户的转头操作，得到第一转头数据，第一转头数据对应标识1，终端期望在t1接收到与第一转头数据关联的画面数据，则接入网设备可以记录标识1与t1的关联关系，该关联关系指示终端期望接收到与第一转头数据关联的画面数据的时刻为t1。之后，终端再次响应于用户的转头操作，得到第二转头数据，第二转头数据对应标识2，终端期望在t2接收到与第二转头数据关联的画面数据，则接入网设备还可以记录标识2与t2的关联关系，该关联关系指示终端期望接收到与第二转头数据关联的画面数据的时刻为t2。这样，接入网设备在后续接收到与第一转头数据关联的画面数据和标识1之后，可以根据标识1确定终端期望接收到与第一转头数据关联的画面数据的时刻为t1，根据标识2确定终端期望接收到与第二转头数据关联的画面数据的时刻为t2。
可选地，在S602之前，方法600还包括S605：接入网设备向UPF网元发送第二消息，第二消息包括第一数据，还包括第一数据的标识和/或第一时刻。相应地，UPF网元接收第二消息。进一步地，在S605之后，方法600还包括S606：UPF网元向服务器发送第四消息，第四消息包括第一数据，还包括第一数据的标识和/或第一时刻，相应地，服务器接收第四消息。
其中，UPF网元可以将来自接入网设备的消息透传给服务器，即第二消息和第四消息可以为同一个消息，第四消息包括的内容与第二消息包括的内容相同。
例如，第二消息包括第一数据，还包括第一数据的标识，则相应地，第四消息包括第一数据，还包括第一数据的标识，这种传输第一数据的标识的方式有利于减少信令开销。为便于描述，下文中将第一数据以及第一数据的标识称为内容1，在本示例中，第二消息包括内容1，第四消息包括内容1。
又例如，第二消息包括第一数据，还包括第一时刻，则相应地，第四消息包括第一数据，还包括第一时刻，这种传输时间信息的方式更加直接高效。为便于描述，下文中将第一数据以及第一时刻称为内容2，在本示例中，第二消息包括内容2，第四消息包括内容2。
上述内容1中的第一时刻可以替换为第五时刻，即第二消息包括第一数据，还包括第五时刻。为便于描述，下文中将第一数据以及第五时刻称为内容3，在本示例中，第二消息包括内容3，第四消息包括内容3。
在上述第二消息包括内容1，第四消息包括内容1的基础上，第二消息还包括第五时刻，即第二消息包括第一数据、第一数据的标识以及第五时刻，第四消息包括第一数据、第一数据的标识以及第五时刻。为便于描述，下文中将第一数据、第一数据的标识以及第五时刻称为内容4，在本示例中，第二消息包括内容4，第四消息包括内容4。
在上述第二消息包括内容2，第四消息包括内容2的基础上，第二消息还包括第五时刻，第四消息还包括第五时刻，即第二消息包括第一数据、第一时刻以及第五时刻，第四消息包括第一数据、第一时刻以及第五时刻。为便于描述，下文中将第一数据、第一时刻以及第五时刻称为内容5，在本示例中，第二消息包括内容5，第四消息包括内容5。
为了对接入网设备和UPF网元之间的传输时延加以控制，进而确保终端在第一时刻接收到第二数据，接入网设备在接收到第一消息之后，根据第一时刻确定接入网设备期望接收到第二数据的时刻，记为第二时刻。之后，接入网设备可以在上述第二消息中携带第二时刻，即第二消息在包括内容1至内容5中的任意一内容的基础上，还包括第二时刻。这样，后续UPF网元可以基于第二时刻向接入网设备发送第二数据，具体参见下文的描述，此处暂不详述。
应理解的是，接入网设备基于第一时刻，并考虑如下一项或多项时延因素确定第二时刻：接入网设备与终端之间的传输时延、接入网设备的内部处理时延或接入网设备的调度时延。接入网设备在第二时刻接收到第二数据，可以确保终端在第一时刻接收到第二数据。
为了对UPF网元与服务器之间的传输时延加以控制，进而确保终端在第一时刻接收到第二数据，UPF网元在接收到第二消息之后，根据第二时刻确定UPF网元期望接收到第二数据的时刻，记为第三时刻。之后，UPF网元可以在上述第四消息中携带第三时刻，即第四消息在包括内容1至内容5中的任意一内容的基础上，还包括第三时刻，这样，后续服务器可以基于第三时刻向UPF网元发送第二数据，具体参见下文的描述，此处暂不详述。
应理解的是，UPF网元基于第二时刻，并考虑如下一项或多项时延因素确定第三时刻：UPF网元与接入网设备之间的传输时延、UPF网元的内部处理时延或UPF网元的调度时延。UPF网元在第三时刻接收到第二数据，可以确保接入网设备在第二时刻接收到第二数据。
在上面的描述中，终端的第一数据通过基站、UPF网元传输至服务器。接入网设备在通过UPF网元向服务器发送第一数据的同时，还可以通过UPF网元向服务器发送第一数据的标识和/或第一时刻。下面介绍服务器通过UPF网元和接入网设备向终端发送第二数据的过程。
服务器在接收到第四消息之后，基于第一数据获取第二数据。例如，基于转头数据获取与转头数据对应的角度的画面数据。又例如，基于原始图像数据获取渲染后的图像数据。又例如，基于手势数据获取传感器的触感数据。
可选地，在S606之后，方法600还包括S607：服务器向UPF网元发送第五消息，第五消息包括第二数据，还包括第一数据的标识和/或第一时刻，相应地，UPF网元接收第五消息。进一步地，在S607之后，方法600还包括S608：UPF网元向接入网设备发送第三消息，第三消息包括第二数据，还包括第一数据的标识和/或第一时刻，相应地，接入网设备接收第三消息。
其中，UPF网元可以将来自服务器的消息透传给接入网设备，即第五消息和第三消息可以为同一个消息。第五消息包括的内容与第四消息包括的内容相关，第三消息包括的内容可以与第五消息包括的内容相同。
例如，上述第四消息包括内容1，相应地，第五消息包括第二数据，还包括第一数据的标识，相应地，第三消息包括所述第二数据，还包括第一数据的标识。为便于描述，下文中将第二数据以及第一数据的标识称为内容6，在本示例中，第五消息包括内容6，第三消息包括内容6。
又例如，上述第四消息包括内容2，相应地，第五消息包括第二数据，还包括第一时刻，相应地，第三消息包括第二数据，还包括第一时刻。为便于描述，下文中将第二数据以及第一时刻称为内容7，在本示例中，第五消息包括内容7，第三消息包括内容7。
又例如，上述第四消息包括内容3，相应地，第五消息包括第二数据，还包括第五时刻，相应地，第三消息包括第二数据，还包括第五时刻。为便于描述，下文中将第二数据以及第五时刻称为内容8，在本示例中，第五消息包括内容8，第三消息包括内容8。
又例如，上述第四消息包括内容4，相应地，第五消息在包括内容6的基础上，还包括第五时刻，即第五消息包括第二数据、第一数据的标识以及第五时刻，相应地，第三消息包括第二数据、第一数据的标识以及第五时刻。为便于描述，下文中将第一数据关联的数据、第一数据的标识以及第五时刻称为内容9。
又例如，上述第四消息包括内容5，相应地，第五消息在包括内容7的基础上，还包括第五时刻，即第五消息包括第二数据、第一时刻以及第五时刻，相应地，第三消息包括第二数据、第一时刻以及第五时刻。为便于描述，下文中将第一数据关联的数据、第一时刻以及第五时刻称为内容10。
接入网设备在接收到第三消息之后，可以基于第三消息包括的内容向终端发送第二数据。更具体地，由于终端可能建立有多条用于传输上行数据的QoS流，因此，接入网设备首先要确定与承载第二数据的第二QoS流关联的QoS流，即第一QoS流，之后，接入网设备从第一QoS流承载的第一消息中确定第一时刻，进而，接入网设备可以执行上述S602，即基于第一时刻，向终端发送第二数据。
下面结合第二QoS流的标识，对如何确定第二QoS流与第一QoS流关联做出进一步说明。
在一种可能的实现方式中，第三消息在包括上述内容6至内容10中的任意一内容的基础上，还包括第二QoS流的第一标识，接入网设备在接收到第三消息之后，根据第二QoS流的第一标识，通过查找存储的QoS流的关联关系，确定第二QoS流与第一QoS流关联。
在另一种可能的实现方式中，第三消息在包括上述内容6至内容10中的任意一内容的基础上，还包括第二QoS流的第二标识，接入网设备在接收到第三消息之后，根据第二QoS流的第二标识，通过查找存储的QoS流的关联关系，确定与第二QoS流具有相同的第二标识的第一QoS流，换言之，第一QoS流的第二标识和第二QoS流的第二标识相同，意味着第一QoS流和第二QoS流关联。
此外，在另一种可能的实现方式中，第三消息在包括上述内容6至内容10中的任意一内容的基础上，还包括第一QoS流的第一标识和第二QoS流的第一标识，接入网设备在接收到第三消息之后，根据第三消息可以确定第一QoS流与第二QoS流关联。
对第一标识和第二标识的介绍可参见上文中的描述，此处不再赘述。
需要说明的是，在第三消息包括上述内容6的情况下，由于内容6不包括所述与第一数据的关联的数据的接收时刻和/或发送时刻，因此，接入网设备首先根据上文的描述确定第二QoS流与第一QoS流关联，之后，由于第一QoS流上可能承载多条消息，不同消息包括的业务相关的数据可能对应不同的接收时刻，因此，接入网设备可以根据第一数据的标识，从第一QoS承载的第一消息中确定第一数据对应的接收时刻，即第一时刻。此外，若接入网设备存储有用于传输第二数据的配置信息与第一数据的标识的关联关系，则接入网设备可以基于该配置信息向终端发送第二数据。该配置信息包括第二数据的传输资源，可选地，还包括DRX的配置和测量间隙的配置。
需要说明的是，在第三消息包括上述内容7至内容10中的任意一内容的情况下，接入网设备可以从第三消息中确定向终端发送第二数据的时刻(即第五时刻)和/或终端期望接收到第二数据的时刻(即第一时刻)，这样接入网设备无需查询存储的信息来确定第一时刻或第五时刻，这样的实现方式更加简单高效。
结合上文的描述，若第四消息在包括上述内容1至内容5中的任意一内容的基础上，还包括第三时刻，则S607包括：服务器基于第三时刻，向UPF网元发送第五消息。更具体地，服务器基于第三时刻以及时延因素确定向UPF网元发送第二数据的时刻，记为第六时刻，并在第六时刻向UPF网元发送第五消息。其中，时延因素包括如下一项或多项：服务器与UPF网元之间的传输时延、服务器的内部处理时延或服务器的调度时延。服务器在第六时刻向UPF网元发送第二数据，可以满足UPF网元在第三时刻或早于第三时刻接收到第二数据的需求。
结合上文的描述，若第二消息在包括上述内容1至内容5中的任意一内容的基础上，还包括第二时刻，则S608包括：UPF网元基于第二时刻，向接入网设备发送第三消息。更具体地，UPF网元基于第二时刻以及时延因素确定第七时刻，并在第七时刻向接入网设备发送第三消息。其中，时延因素包括如下一项或多项：UPF网元与接入网设备之间的传输时延、UPF网元的内部处理实验或UPF网元的调度时延。UPF网元在第七时刻向接入网设备发送第二数据，可以满足接入网设备在第二时刻或早于第二时刻接收到第二数据。
UPF网元在基于第二时刻，向接入网设备发送第三消息之前，首先需要确定接入网设备期望接收到第二数据的时刻为第二时刻。在一种可能的实现方式中，UPF网元确定第二时刻，包括：UPF网元根据用于承载第二数据的第二QoS流的标识，确定第二QoS流与第一QoS流关联，进而，UPF网元从第一QoS流承载的第二消息中确定第二时刻。在上述第二消息还包括第一数据的标识的情况下，UPF网元从第一QoS流承载的第二消息中确定第二时刻，包括：UPF网元根据第一数据的标识，从第一QoS流承载的第二消息中确定第二时刻。
UPF网元确定第二时刻的更具体的实现方式与上文中接入网设备确定第一时刻的方式类似，例如，根据第二QoS流的第一标识或者第二QoS流的第二标识，确定第二QoS流与第一QoS关联，进而从第一QoS流承载的第二消息中确定第二时刻。具体可参见上文中的描述，此处不再赘述。
应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中结合图6，详细描述了根据本申请实施例的通信方法，下面将结合图7和图8，详细描述根据本申请实施例的通信装置。
图7是本申请实施例提供的一种通信装置700的示意性框图，装置700包括：收发模块710。可选地，装置700还包括处理模块720。
处理模块720用于进行数据处理。收发模块710可以实现相应的通信功能。收发模块710还可以称为通信接口或者通信模块。
可选地，装置700还可以包括存储模块，该存储模块可以用于存储数据，和/或，用于存储计算机程序或指令，处理模块720可以读取存储模块中的计算机程序/指令和/或数据，以使得装置700实现上述方法实施例。
装置700可以用于执行上述方法实施例中终端、接入网设备或UPF网元所执行的动作。或者，装置700为配置于终端、接入网设备或UPF网元中的部件(例如芯片)。处理模块720用于执行上述方法实施例中终端、接入网设备或UPF网元的处理相关的操作。收发模块710用于执行上述方法实施例中终端、接入网设备或UPF网元的接收和发送相关的操作。
可选地，收发模块710可以包括发送模块和接收模块。发送模块用于执行上述方法实施例中的发送操作。接收模块用于执行上述方法实施例中的接收操作。
需要说明的是，装置700可以包括发送模块，而不包括接收模块。或者，装置700可以包括接收模块，而不包括发送模块。具体可以视装置700执行的上述方案中是否包括发送动作和接收动作。
可选地，装置700用于执行上述图6所示的实施例中终端、接入网设备或UPF网元所执行的动作。具体可以参阅上述图6所示的实施例中的相关介绍，此处不再赘述。
在一个实施例中，收发模块710用于：发送第一消息，第一消息包括第一数据和第一时刻，第一数据为业务相关的数据，第一时刻为终端期望接收到第二数据的时刻，第二数据是与第一数据关联的数据，或者，第二数据是与第一时刻关联的数据；以及，在第一时刻接收第二数据。
可选地，处理模块720用于：建立第一QoS流，以及，建立第二QoS流，第一QoS流用于承载第一消息，第二QoS流用于承载第二数据。
可选地，收发模块710用于：接收第一请求消息，第一请求消息用于请求建立第二QoS流，第一请求消息包括第一QoS流的第一标识。
可选地，收发模块710用于：发送第二请求消息，第二请求消息用于请求建立第一QoS流，第二请求消息包括第二QoS流的第一标识。
可选地，收发模块710用于：发送第三请求消息，第三请求消息用于请求建立第一QoS流和第二QoS流，第三请求消息包括第一QoS流的第一标识和第二QoS流的第一标识。
可选地，收发模块710用于：发送第四请求消息，第四请求消息用于请求建立第一QoS流和第二QoS流；以及，接收第四请求消息的响应消息，该响应消息包括第一QoS流的第一标识和第二QoS流的第一标识。
可选地，第一QoS流的第二标识和第二QoS流的第二标识相同。
可选地，处理模块720用于：根据生成第一数据的时刻以及时延要求，确定第一时刻。
可选地，第一消息还包括第一数据的标识。
可选地，收发模块710用于：接收配置信息，该配置信息包括第二数据的传输资源。
可选地，该配置信息还包括DRX的配置和/或测量间隙的配置。
在本实施例中，本领域技术人员可以理解，装置700可以具体为上述图6所示的实施例中的终端，或者，上述图6所示的实施例中终端的功能可以集成在装置700中。上述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。装置700可以用于执行上述方法实施例中与终端对应的各个流程和/或步骤。
在另一个实施例中，收发模块710用于：接收第一消息，第一消息包括第一数据和第一时刻，第一数据为业务相关的数据，第一时刻为终端期望接收到第二数据的时刻，第二数据是与第一数据关联的数据，或者，第二数据是与第一时刻关联的数据；以及，基于第一时刻，发送第二数据。
可选地，处理模块720用于：根据用于承载第二数据的第二QoS流的标识，确定第二QoS流与第一QoS流关联，第一QoS流用于承载第一消息；以及，从第一QoS流承载的第一消息中确定第一时刻。
可选地，第一消息还包括所述第一数据的标识。
可选地，收发模块710用于：发送第二消息，第二消息包括第一数据，还包括第一数据的标识和/或第一时刻；以及，接收第三消息，第三消息包括第二数据，还包括第一数据的标识和/或第一时刻。
可选地，第二消息还包括第一数据的标识，第三消息还包括第一数据的标识；处理模块720用于：根据第一数据的标识，从第一QoS流承载的第一消息中确定第一时刻。
可选地，第二消息还包括第二时刻，第二时刻为接入网设备期望接收到第二数据的时刻。
可选地，收发模块710用于：在支持终端在第一时刻接收到第二数据的情况下，发送配置信息，该配置信息包括第二数据的传输资源。
可选地，该配置信息还包括DRX的配置和/或测量间隙的配置。
在本实施例中，本领域技术人员可以理解，装置700可以具体为上述图6所示的实施例中的接入网设备，或者，上述图6所示的实施例中接入网设备的功能可以集成在装置700中。上述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。装置700可以用于执行上述方法实施例中与接入网设备对应的各个流程和/或步骤。
在另一个实施例中，收发模块710用于：接收第二消息，第二消息包括第一数据，还包括第一数据的标识和/或第一时刻，第一数据为业务相关的数据，第一时刻为终端期望接收到第二数据的时刻，第二数据是与第一数据关联的数据，或者，第二数据是与第一时刻关联的数据；以及，发送第三消息，第三消息包括第二数据，还包括第一数据的标识和/或第一时刻。
可选地，第二消息还包括第二时刻，第二时刻为接入网设备期望接收到第二数据的时刻；收发模块710用于：基于第二时刻，发送第三消息。
可选地，处理模块720用于：根据用于承载第二数据的第二QoS流的标识，确定第二QoS流与第一QoS流关联，第一QoS流用于承载第二消息；以及，从第一QoS流承载的第二消息中确定第二时刻。
可选地，收发模块710用于：发送第四消息，第四消息包括第一数据，还包括第一数据的标识和/或第一时刻；以及，接收第五消息，第五消息包括第二数据，还包括第一数据的标识和/或第一时刻。
可选地，第四消息还包括第三时刻，第三时刻为用户面功能网元期望接收到第二数据的时刻。
在本实施例中，本领域技术人员可以理解，装置700可以具体为上述图6所示的实施例中的UPF网元，或者，上述图6所示的实施例中UPF网元的功能可以集成在装置700中。上述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。装置700可以用于执行上述方法实施例中与UPF网元对应的各个流程和/或步骤。
应理解，这里的装置700以功能模块的形式体现。这里的术语“模块”可以指应用专用集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。
在本申请的实施例，装置700也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。对应的，收发模块可以是该芯片的收发电路，在此不做限定。
图8是本申请实施例提供的另一种通信装置800的示意性框图。该装置800包括处理器810。可选地，该感知装置800还包括收发器820和存储器830。其中，处理器810、收发器820和存储器830通过内部连接通路互相通信，该存储器830用于存储指令，该处理器810用于执行该存储器830存储的指令，以控制该收发器820发送信号和/或接收信号。
该处理器810的数量可以为一个或多个。
该处理器810和该存储器830可以分离设置，也可以集成在一起。
可选地，该装置800还包括供电电路，该供电电路可用于为该装置800供电。
应理解，装置800可以具体为上述实施例中的终端、接入网设备或UPF网元，或者，上述实施例中终端、接入网设备或UPF网元的功能可以集成在装置800中，装置800可以用于执行上述方法实施例中与终端、接入网设备或UPF网元对应的各个步骤和/或流程。可选地，该存储器830可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。该处理器810可以用于执行存储器中存储的指令，并且该处理器执行该指令时，该处理器810可以执行上述方法实施例中与终端、接入网设备或UPF网元对应的各个步骤和/或流程。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质用于存储计算机程序，当计算机程序在计算机上运行时，使得计算机执行上述实施例所描述的方法。
本申请实施例还提供一种计算机程序产品，计算机程序产品包括：计算机程序或指令，当计算机程序或指令被运行时，使得计算机执行上述实施例描述的方法。
应理解，在本申请实施例中，该处理器可以是中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、ASIC、现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器执行存储器中的指令，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的模块及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或模块的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能模块可以集成在一个处理模块中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个模块中。
所述功能如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (28)

  1. 一种通信方法，其特征在于，包括：
    发送第一消息，所述第一消息包括第一数据和第一时刻，所述第一数据为业务相关的数据，所述第一时刻为终端期望接收到第二数据的时刻，所述第二数据是与所述第一数据关联的数据，或者，所述第二数据是与所述第一时刻关联的数据；
    在所述第一时刻接收所述第二数据。
  2. 根据权利要求1所述的方法，其特征在于，在所述发送第一消息之前，所述方法还包括：
    建立第一服务质量QoS流，以及，建立第二QoS流，所述第一QoS流用于承载所述第一消息，所述第二QoS流用于承载所述第二数据。
  3. 根据权利要求2所述的方法，其特征在于，在建立所述第一QoS流之后，所述方法还包括：
    接收第一请求消息，所述第一请求消息用于请求建立所述第二QoS流，所述第一请求消息包括所述第一QoS流的第一标识。
  4. 根据权利要求2所述的方法，其特征在于，在建立所述第二QoS流之后，所述方法还包括：
    发送第二请求消息，所述第二请求消息用于请求建立所述第一QoS流，所述第二请求消息包括所述第二QoS流的第一标识。
  5. 根据权利要求2所述的方法，其特征在于，在所述建立第一QoS流以及建立第二QoS流之前，所述方法还包括：
    发送第三请求消息，所述第三请求消息用于请求建立所述第一QoS流和所述第二QoS流，所述第三请求消息包括所述第一QoS流的第一标识和所述第二QoS流的第一标识。
  6. 根据权利要求2所述的方法，其特征在于，在所述建立第一QoS流以及建立第二QoS流之前，所述方法还包括：
    发送第四请求消息，所述第四请求消息用于请求建立所述第一QoS流和所述第二QoS流；
    接收所述第四请求消息的响应消息，所述响应消息包括所述第一QoS流的第一标识和所述第二QoS流的第一标识。
  7. 根据权利要求2至6中任一项所述的方法，其特征在于，所述第一QoS流的第二标识和所述第二QoS流的第二标识相同。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，在所述发送第一消息之前，所述方法还包括：
    根据生成所述第一数据的时刻以及时延要求，确定所述第一时刻。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述第一消息还包括所述第一数据的标识。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，在所述第一时刻接收所述第二数据之前，所述方法还包括：
    接收配置信息，所述配置信息包括所述第二数据的传输资源。
  11. 根据权利要求10所述的方法，其特征在于，所述配置信息还包括非连续接收DRX的配置和/或测量间隙的配置。
  12. 一种通信方法，其特征在于，包括：
    接收第一消息，所述第一消息包括第一数据和第一时刻，所述第一数据为业务相关的数据，所述第一时刻为终端期望接收到第二数据的时刻，所述第二数据是与所述第一数据关联的数据，或者，所述第二数据是与所述第一时刻关联的数据；
    基于所述第一时刻，发送所述第二数据。
  13. 根据权利要求12所述的方法，其特征在于，在所述基于所述第一时刻，发送所述第二数据之前，所述方法还包括：
    根据用于承载所述第二数据的第二服务质量QoS流的标识，确定所述第二QoS流与第一QoS流关联，所述第一QoS流用于承载所述第一消息；
    从所述第一QoS流承载的所述第一消息中确定所述第一时刻。
  14. 根据权利要求13所述的方法，其特征在于，所述第一消息还包括所述第一数据的标识。
  15. 根据权利要求14所述的方法，其特征在于，在所述基于所述第一时刻，发送所述第二数据之前，所述方法还包括：
    发送第二消息，所述第二消息包括所述第一数据，还包括所述第一数据的标识和/或所述第一时刻；
    接收第三消息，所述第三消息包括所述第二数据，还包括所述第一数据的标识和/或所述第一时刻。
  16. 根据权利要求15所述的方法，其特征在于，所述第二消息还包括所述第一数据的标识，所述第三消息还包括所述第一数据的标识；
    所述从所述第一QoS流承载的所述第一消息中确定所述第一时刻，包括：
    根据所述第一数据的标识，从所述第一QoS流承载的所述第一消息中确定所述第一时刻。
  17. 根据权利要求15或16所述的方法，其特征在于，所述第二消息还包括第二时刻，所述第二时刻为接入网设备期望接收到所述第二数据的时刻。
  18. 根据权利要求12至17中任一项所述的方法，其特征在于，在所述接收第一消息之后，所述方法还包括：
    在支持所述终端在所述第一时刻接收到所述第二数据的情况下，发送配置信息，所述配置信息包括所述第二数据的传输资源。
  19. 根据权利要求18所述的方法，其特征在于，所述配置信息还包括非连续接收DRX的配置和/或测量间隙的配置。
  20. 一种通信方法，其特征在于，包括：
    接收第二消息，所述第二消息包括第一数据，还包括所述第一数据的标识和/或第一时刻，所述第一数据为业务相关的数据，所述第一时刻为终端期望接收到第二数据的时刻，所述第二数据是与所述第一数据关联的数据，或者，所述第二数据是与所述第一时刻关联的数据；
    发送第三消息，所述第三消息包括所述第二数据，还包括所述第一数据的标识和/或所述第一时刻。
  21. 根据权利要求20所述的方法，其特征在于，所述第二消息还包括第二时刻，所述第二时刻为接入网设备期望接收到所述第二数据的时刻；
    所述发送第三消息，包括：
    基于所述第二时刻，发送所述第三消息。
  22. 根据权利要求21所述的方法，其特征在于，在所述基于所述第二时刻，发送所述第三消息之前，所述方法还包括：
    根据用于承载所述第二数据的第二服务质量QoS流的标识，确定所述第二QoS流与第一QoS流关联，所述第一QoS流用于承载所述第二消息；
    从所述第一QoS流承载的所述第二消息中确定所述第二时刻。
  23. 根据权利要求20至22中任一项所述的方法，其特征在于，在所述发送第三消息之前，所述方法还包括：
    发送第四消息，所述第四消息包括所述第一数据，还包括所述第一数据的标识和/或所述第一时刻；
    接收第五消息，所述第五消息包括所述第二数据，还包括所述第一数据的标识和/或所述第一时刻。
  24. 根据权利要求23所述的方法，其特征在于，所述第四消息还包括第三时刻，所述第三时刻为用户面功能网元期望接收到所述第二数据的时刻。
  25. 一种通信装置，其特征在于，包括用于实现如权利要求1至11中任一项所述的方法的模块，或，包括用于实现如权利要求12至19中任一项所述的方法的模块，包括用于实现如权利要求20至24中任一项所述的方法的模块。
  26. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述至少一个处理器执行时，使得如权利要求1至11中任一项所述的方法被执行，或，使得如权利要求12至19中任一项所述的方法被执行，或，使得如权利要求20至24中任一项所述的方法被执行。
  27. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，当所述计算机程序在计算机上运行时，使得如权利要求1至11中任一项所述的方法被执行，或，使得如权利要求12至19中任一项所述的方法被执行，或，使得如权利要求20至24中任一项所述的方法被执行。
  28. 一种计算机程序产品，其特征在于，包括：计算机程序或指令，当所述计算机程序或指令被运行时，使得如权利要求1至11中任一项所述的方法被执行，或，使得如权利要求12至19中任一项所述的方法被执行，或，使得如权利要求20至24中任一项所述的方法被执行。
PCT/CN2025/089489 2024-05-30 2025-04-17 通信方法及相关装置 Pending WO2025246716A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410698266.1A CN121056936A (zh) 2024-05-30 2024-05-30 通信方法及相关装置
CN202410698266.1 2024-05-30

Publications (1)

Publication Number Publication Date
WO2025246716A1 true WO2025246716A1 (zh) 2025-12-04

Family

ID=97810240

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/089489 Pending WO2025246716A1 (zh) 2024-05-30 2025-04-17 通信方法及相关装置

Country Status (2)

Country Link
CN (1) CN121056936A (zh)
WO (1) WO2025246716A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004302686A (ja) * 2003-03-28 2004-10-28 Konami Computer Entertainment Yokyo Inc 仮想コミュニケーションシステム
WO2023147707A1 (zh) * 2022-02-07 2023-08-10 Oppo广东移动通信有限公司 通信方法、接入网设备、核心网网元以及终端设备
CN117204098A (zh) * 2022-03-31 2023-12-08 北京小米移动软件有限公司 一种消除时分干扰的方法及装置
CN117692720A (zh) * 2022-09-09 2024-03-12 鹏城实验室 一种通信方法及相关设备
CN118019052A (zh) * 2022-11-10 2024-05-10 中国移动通信有限公司研究院 一种数据传输方法、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004302686A (ja) * 2003-03-28 2004-10-28 Konami Computer Entertainment Yokyo Inc 仮想コミュニケーションシステム
WO2023147707A1 (zh) * 2022-02-07 2023-08-10 Oppo广东移动通信有限公司 通信方法、接入网设备、核心网网元以及终端设备
CN117204098A (zh) * 2022-03-31 2023-12-08 北京小米移动软件有限公司 一种消除时分干扰的方法及装置
CN117692720A (zh) * 2022-09-09 2024-03-12 鹏城实验室 一种通信方法及相关设备
CN118019052A (zh) * 2022-11-10 2024-05-10 中国移动通信有限公司研究院 一种数据传输方法、设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Correction of QoS sustainability analytics", 3GPP DRAFT; S2-2001865, vol. SA WG2, 18 February 2020 (2020-02-18), pages 1 - 4, XP052456579 *

Also Published As

Publication number Publication date
CN121056936A (zh) 2025-12-02

Similar Documents

Publication Publication Date Title
WO2017113130A1 (zh) 一种资源请求方法、设备、网络侧节点及系统
US12538309B2 (en) Downlink transmission method and communication apparatus
US20240080716A1 (en) Wireless communication method, communication apparatus, and communication system
US20240171522A1 (en) Electronic device, communication method, and computer-readable storage medium
US20240056889A1 (en) Communication processing method for data transmission and related device
CN117641422A (zh) 一种通信方法及通信装置
WO2023116435A1 (zh) 一种通信方法及装置
WO2023179238A1 (zh) 一种授时方法、通信装置及通信系统
CN113938985A (zh) 一种通信方法及装置
WO2024187316A1 (zh) 通信方法以及通信设备
WO2022252651A1 (zh) 一种无线通信方法及装置
CN117322087A (zh) 资源处理的方法、终端设备、网络设备及存储介质
US20240334241A1 (en) Detection method, communication apparatus, and communication system
WO2021134561A1 (zh) 通信方法和通信装置
WO2024140600A1 (zh) 通信方法、通信装置及通信系统
WO2025246716A1 (zh) 通信方法及相关装置
TW201536006A (zh) 控制封包優先順序的方法及其存取點
WO2024178696A1 (zh) 信息传输方法及装置、通信设备及存储介质
WO2024130664A1 (zh) 通信方法及通信装置
WO2025092284A1 (zh) 数据传输方法和装置
WO2017206031A1 (zh) 信息传输方法及装置
WO2025067076A1 (zh) 通信方法及装置
WO2026077156A1 (zh) 一种通信方法及装置
WO2025067073A1 (zh) 通信方法及装置
WO2025176038A1 (zh) 一种通信方法及通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25814437

Country of ref document: EP

Kind code of ref document: A1