[go: up one dir, main page]

WO2025209383A1 - Procédé de communication, appareil de communication, et système de communication - Google Patents

Procédé de communication, appareil de communication, et système de communication

Info

Publication number
WO2025209383A1
WO2025209383A1 PCT/CN2025/086103 CN2025086103W WO2025209383A1 WO 2025209383 A1 WO2025209383 A1 WO 2025209383A1 CN 2025086103 W CN2025086103 W CN 2025086103W WO 2025209383 A1 WO2025209383 A1 WO 2025209383A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
moq
network element
type
message type
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/086103
Other languages
English (en)
Chinese (zh)
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 WO2025209383A1 publication Critical patent/WO2025209383A1/fr
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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements

Definitions

  • the present application relates to the field of wireless communication technology, and in particular to a communication method, a communication device, and a communication system.
  • each service flow can transmit at least one MoQ message, each containing one or more objects.
  • Service flow objects transmitted on the same QUIC connection reuse the same IP quintuple. Therefore, the 5G system cannot use the IP quintuple information to perform QoS flow mapping for service flow objects on the same connection.
  • QUIC Quick UDP Internet Connections
  • MoQ stands for Media over QUIC.
  • the method includes: determining a first mapping rule, the first mapping rule being used to indicate the first message type of each MoQ message in at least two MoQ messages, and indicating a mapping relationship between a QoS flow and the first message type and a first parameter of each of the MoQ messages, the first parameter including information about the object in the MoQ message, the first message type of the MoQ message indicating that the MoQ message contains multiple objects; the objects in each MoQ message are transmitted through the same connection; and sending the first mapping rule, the first mapping rule being used to map the objects in the at least two MoQ messages to corresponding QoS flows.
  • the multiple objects can be mapped to corresponding QoS flows for transmission based on the first mapping rule, thereby realizing the mapping of objects in the MoQ message to QoS flows, which can meet the QoS transmission requirements of different objects, thereby improving the user experience.
  • the first network element is a policy control network element; the method further includes: receiving the first message type and the first parameter from an application function network element.
  • the first network element is a session management network element; the method further includes: receiving the first message type and the first parameter from a policy control network element.
  • an embodiment of the present application provides a communication method, which can be performed by a user plane network element or a module (such as a chip) in the user plane network element.
  • the method includes: receiving a first MoQ message; if the first MoQ message is identified as a MoQ message of a first message type, mapping the object in the first MoQ message to a corresponding QoS flow according to a first mapping rule; wherein the first mapping rule is used to indicate the first message type of each MoQ message in at least two MoQ messages, and to indicate a mapping relationship between the QoS flow and the first message type and first parameter of each MoQ message, the first parameter including information about the object in the MoQ message, the first message type of the MoQ message indicating that the MoQ message contains multiple objects; and the objects in each MoQ message are transmitted through the same connection.
  • the information of the object in the MoQ message includes at least one of a priority of the object, a candidate value of a track field in the MoQ message, or a candidate value of a group field in the MoQ message.
  • the method further includes: if it is identified that the first MoQ message is a MoQ message of the second message type, performing PDU aggregate QoS processing on the first MoQ message according to a second mapping rule;
  • the second mapping rule is used to indicate that PDU set QoS processing is performed on the object in the MoQ message of the second message type, and the second message type is used to indicate a MoQ message containing one object.
  • the method further includes: receiving indication information, where the indication information is used to instruct identification of a type of the MoQ message; and identifying the type of the first MoQ message according to the indication information.
  • embodiments of the present application provide a communication method, which can be performed by an application function network element or a module (e.g., a chip) within the application function network element.
  • the method includes: sending a first message type and a first parameter to a first network element; wherein the first message type is used to indicate an MoQ message containing multiple objects, and the first parameter includes the priority of the objects in the MoQ message of the first message type.
  • the method further includes: sending a second message type to the first network element, where the second message type is used to indicate a MoQ message containing an object.
  • the method further includes: sending indication information to the first network element, where the indication information is used to instruct identification of the type of the MoQ message.
  • the first network element is a policy control network element or a session management network element.
  • an embodiment of the present application provides a communication method, which can be executed by a first network element or a module (such as a chip) in the first network element.
  • the first network element is a policy control network element or a session management network element.
  • the MoQ message if the MoQ message includes multiple objects, the multiple objects can be mapped to corresponding QoS flows for transmission based on the mapping rules. If the MoQ message includes one object, the one object can also be mapped to the corresponding QoS flow for transmission based on the mapping rules. This implements the mapping of objects in the MoQ message to QoS flows, can meet the QoS transmission requirements of different objects, and thus can improve user experience.
  • the first network element is a policy control network element; the method further includes: receiving the first message type, the first parameter, the second message type, and the second parameter from an application function network element.
  • the first network element is a policy control network element; the method further includes: receiving indication information from an application function network element, the indication information being used to indicate identification of the type of the MoQ message; and sending the indication information to a session management network element.
  • the first network element is a session management network element; the method further includes: receiving the first message type, the first parameter, the second message type, and the second parameter from a policy control network element.
  • the first network element is a session management network element; the method further includes: receiving indication information from a policy control network element, the indication information being used to indicate identification of the type of the MoQ message; and sending the indication information to a user plane network element.
  • the information of the object in the MoQ message of the first message type includes at least one of the priority of the object in the MoQ message of the first message type, the candidate value of the track field in the MoQ message of the first message type, or the candidate value of the group field in the MoQ message of the first message type;
  • the information of the object in the MoQ message of the second message type includes at least one of the priority of the object in the MoQ message of the second message type, the candidate value of the track field in the MoQ message of the second message type, or the candidate value of the group field in the MoQ message of the second message type.
  • the multiple objects can be mapped to corresponding QoS flows for transmission based on the mapping rules. If the first MoQ message includes one object, the one object can also be mapped to the corresponding QoS flow for transmission based on the mapping rules. This implements the mapping of objects in the MoQ message to QoS flows, can meet the QoS transmission requirements of different objects, and thus can improve user experience.
  • the information of the object in the MoQ message of the first message type includes at least one of the priority of the object in the MoQ message of the first message type, the candidate value of the track field in the MoQ message of the first message type, or the candidate value of the group field in the MoQ message of the first message type;
  • the information of the object in the MoQ message of the second message type includes at least one of the priority of the object in the MoQ message of the second message type, the candidate value of the track field in the MoQ message of the second message type, or the candidate value of the group field in the MoQ message of the second message type.
  • the method further includes: receiving indication information, where the indication information is used to instruct identification of a type of the MoQ message; and identifying the type of the first MoQ message according to the indication information.
  • the method further includes: receiving the mapping rule from a policy control network element or a session management network element.
  • an embodiment of the present application provides a communication method, which can be performed by an application function network element or a module (such as a chip) in the application function network element.
  • the method includes: sending the first message type, the first parameter, the second message type, and the second parameter to a first network element; wherein the first message type is used to indicate a flow-by-flow MoQ message, and the first parameter includes the priority of the object in the MoQ message of the first message type; the second message type is used to indicate a packet-by-packet MoQ message, and the second parameter includes the priority of the object in the MoQ message of the second message type.
  • the method further includes: sending indication information to the first network element, where the indication information is used to instruct identification of the type of the MoQ message.
  • the first network element is a policy control network element or a session management network element.
  • an embodiment of the present application provides a communication device, which may be a first network element or a module (such as a chip) in the first network element.
  • the device has the function of implementing any implementation method of the first or fourth aspects described above.
  • the function 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.
  • an embodiment of the present application provides a communication device, which may be a user plane network element or a module (such as a chip) in a user plane network element.
  • the device has the function of implementing any implementation method of the second or fifth aspect above.
  • the function can be implemented by hardware or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication device, which may be an application function network element or a module (such as a chip) in an application function network element.
  • the device has the function of implementing any implementation method of the third aspect or the sixth aspect above.
  • the function can be implemented by hardware or by executing corresponding software implementation by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication device, comprising a unit or means for executing each step of any implementation method in the above-mentioned first to sixth aspects.
  • an embodiment of the present application provides a communication device, comprising a processor and an interface circuit, wherein the processor is configured to communicate with other devices via the interface circuit and execute any of the implementation methods described in aspects 1 to 6 above.
  • the processor comprises one or more.
  • the communication device may further include a memory for storing computer instructions, the memory being coupled to a processor, and the processor executing the computer instructions stored in the memory so that the device executes any implementation method in the above-mentioned first to sixth aspects.
  • an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when run on a communication device, enables any implementation method in the above-mentioned first to sixth aspects to be executed.
  • the present application provides a chip (or chip system), which includes a processor, the processor is coupled to a memory, and the memory stores a computer program; the processor is used to call part or all of the computer program in the memory, so that any implementation method of the above-mentioned first to sixth aspects is executed.
  • the present application provides a communication system comprising a first network element for executing any implementation method of the first aspect, and a user-side network element for executing any implementation method of the second aspect.
  • the present application provides a communication system, comprising a first network element for executing any implementation method of the fourth aspect, and a user-side network element for executing any implementation method of the fifth aspect.
  • the communication system also includes an application function network element for executing any implementation method of the sixth aspect.
  • 3 to 6 are flow charts of a communication method according to an embodiment of the present application.
  • FIG 7 and 8 are schematic structural diagrams of the communication device provided in the embodiments of the present application.
  • Figure 1 shows a schematic diagram of a 5G network architecture based on a service-oriented architecture.
  • the 5G network architecture shown in Figure 1 includes the data network (DN) and the carrier network. The following briefly describes the functions of some of these network elements.
  • the operator network includes one or more of the following network elements: authentication server function (AUSF) network element, unified data repository (UDR) network element, policy control function (PCF) network element, unified data management (UDM) network element, access and mobility management function (AMF) network element, application function (AF) network element, session management function (SMF) network element, network repository function (NRF) network element, network exposure function (NEF) network element, user plane function (UPF) network element, access network (AN) equipment (the AN equipment in the figure is a radio access network (RAN) equipment as an example), etc.
  • AUSF authentication server function
  • UDR unified data repository
  • PCF policy control function
  • UDM access and mobility management function
  • AMF access and mobility management function
  • AF application function
  • SMF session management function
  • NEF network repository function
  • NEF network exposure function
  • UPF user plane function
  • AN access network
  • AN access network equipment
  • RAN radio access network
  • Access network equipment includes wired access network equipment and wireless access network equipment.
  • wireless access network equipment can be a base station (base station), an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system; it can also be a module or unit that performs part of the functions of a base station, for example, a centralized unit (CU) or a distributed unit (DU).
  • CU centralized unit
  • DU distributed unit
  • Terminal devices that communicate with access network devices include terminals, user equipment (UE), mobile stations, mobile terminals, etc.
  • the figure uses the UE as an example of a terminal device.
  • Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc.
  • the terminal can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc.
  • the embodiments of this application do not limit the specific technology and specific device form used by the terminal device.
  • the mobility management element is primarily responsible for the attachment, mobility management, and tracking area update (TAU) processes of terminal devices in mobile networks.
  • the MNE terminates non-access stratum (NAS) messages, completes registration management, connection management, reachability management, and mobility management, allocates tracking area lists (TA lists), and transparently routes session management (SM) messages to the session management element.
  • NAS non-access stratum
  • TA lists tracking area lists
  • SM session management
  • the MNE may be an AMF element.
  • future communications such as the 6th generation (6G)
  • 6G 6th generation
  • the MNE may still be an AMF element or have other names, which are not limited in this application.
  • the session management network element is a control plane network element provided by the operator network, which is responsible for managing the protocol data unit (PDU) session of the terminal device.
  • the PDU session is a channel for transmitting PDUs.
  • the terminal device transmits PDUs to each other with the DN through the PDU session.
  • the SMF network element is responsible for establishing, maintaining and deleting PDU sessions.
  • the session management network element includes session management (such as session establishment, modification and release, including tunnel maintenance between user plane network elements and access network equipment), selection and control of user plane network elements, service and session continuity (SSC) mode selection, roaming and other session-related functions.
  • the session management network element can be an SMF network element.
  • future communications such as 6G communications, the session management network element can still be an SMF network element, or have other names, which are not limited in this application.
  • the user plane network element is a gateway provided by the operator and serves as the gateway for communication between the operator network and the DN.
  • the user plane network element includes user plane-related functions such as packet routing and transmission, packet detection, service usage reporting, QoS processing, lawful interception, uplink packet detection, and downlink packet storage.
  • the user plane network element can be a UPF network element.
  • future communications such as 6G communications, the user plane network element can still be a UPF network element or have other names, which are not limited in this application.
  • the network open network element is a control plane network element provided by the operator.
  • the network open network element opens the external interface of the operator network to a third party in a secure manner.
  • the network open network element can serve as a relay for the communication between the session management network element and the network element of the third party.
  • the network open network element acts as a relay, it can translate the identification information of the subscriber, as well as the identification information of the third-party network element. For example, when the network open network element sends the SUPI of the subscriber from the operator network to the third party, the SUPI can be translated into its corresponding external identity.
  • the application function network element is used to communicate application-side requirements to the network, such as quality of service (QoS) requirements or user status event subscriptions.
  • the AFNE can be a third-party functional entity or an application server deployed by the operator.
  • the AFNE can be an AFNE.
  • future communications such as 6G communications, the AFNE can still be an AFNE or have other names, which are not limited in this application.
  • the MoQ protocol is an optimized version of the QUIC protocol. Its goal is to define a unified, low-latency, and highly scalable media distribution protocol and architecture based on QUIC.
  • the MoQ protocol can be applied to real-time media services such as cloud gaming, audio and video conferencing, and live streaming.
  • the MoQ model consists of objects, groups, and/or tracks.
  • Objects are the basic elements and include metadata and payloads. Metadata is visible to relays, and payloads can be encrypted and are visible only to the sender and receiver.
  • Objects can be used to carry data content. For example, an object can contain a video segment, an audio segment, a video frame, or an audio frame.
  • a group contains multiple objects, and a track contains multiple groups or multiple objects. Tracks generally contain more objects than groups.
  • the OBJECT_PREFER_DATAGRAM message can also include a track field (also known as a Track Alias field) or a group field (also known as a group ID field).
  • the track field contains the ID of the track to which the object belongs
  • the group field contains the ID of the group to which the object belongs.
  • Stream-by-stream refers to the QUIC connection including reliable stream transmission, meaning that the data of the service stream transmitted in the QUIC connection must be reliable, similar to transmission control protocol (TCP).
  • Packet-by-packet refers to the QUIC connection including unreliable data transmission, meaning that the data of the service stream transmitted in the QUIC connection does not need to be reliable, similar to UDP transmission. Reliable streams and unreliable data can be transmitted in the same connection or in different QUIC connections.
  • one MoQ message corresponds to one service flow, that is, one MoQ message is sent on one service flow, and the MoQ message contains one or more objects.
  • the present application is not limited to sending only one MoQ message on one service flow, and multiple MoQ messages can also be sent.
  • service flows are filtered based on IP quintuple information and mapped to QoS flows for transmission. For example, if the service flow corresponding to a service includes a video stream and an audio stream, and the video and audio streams have different IP quintuple information, the 5G system processes the data packets based on the IP quintuple information included in the received data. For example, the video stream data packets may be mapped to QoS flow #1, and the audio stream data packets may be mapped to QoS flow #2. This allows QoS assurance for different media streams through different QoS flows.
  • MoQ message #1 is sent on service flow #1, and includes object #1.
  • MoQ message #2 is sent on service flow #2, and includes objects #2 through #4, that is, objects #2, #3, and #4.
  • MoQ message #3 is sent on service flow #3, and includes objects #5 through #9, that is, objects #5, #6, #7, #8, and #9.
  • service flows #1, #2, and #3 are transmitted on the same connection (based on QUIC)
  • the different objects in service flows #1, #2, and #3 all correspond to the same IP five-tuple information, that is, objects #1 through #9 all correspond to the same IP five-tuple information.
  • different objects may have different QoS transmission requirements, different objects need to be mapped to different QoS flows. However, because these objects all correspond to the same IP five-tuple information, QoS flow mapping of service flows cannot be performed using the IP five-tuple information.
  • one or more service streams can be transmitted on a QUIC connection.
  • Each service stream corresponds to one or more MoQ messages (hereinafter, one service stream corresponds to one MoQ message as an example).
  • Each MoQ message contains one or more objects.
  • a service stream can also be referred to as a media stream.
  • the service stream or media stream can be a video stream, an audio stream, a tactile stream, or other types of streams.
  • a service stream transmitted on a QUIC connection can also be referred to as a QUIC stream.
  • this application provides corresponding solutions.
  • the first network element is a mobility management entity (MME), an SMF network element, a PCF network element, or another type of network element. This application will be described later using the example where the first network element is an SMF network element or a PCF network element.
  • MME mobility management entity
  • SMF Session Management Function
  • PCF Packet Control Function
  • the first message type is used to indicate a MoQ message containing multiple objects.
  • the MoQ message of the first message type may be the aforementioned STREAM_HEADER_TRACK message or STREAM_HEADER_GROUP message, etc.
  • Mapping rule 5 above means: If the message type of a MoQ message is a STREAM_HEADER_GROUP message, and the priority of an object in the MoQ message is priority #2, the object is mapped to QoS flow #2.
  • the STREAM_HEADER_GROUP message can contain one or more objects with priority #2, as well as objects of other priorities.
  • Mapping rule 8 above means that if the message type of a MoQ message is a STREAM_HEADER_TRACK message, the priority of one or more objects in the MoQ message is Priority #1, and the value of the track ID field in the MoQ message is track ID #2, the object is mapped to QoS flow #2.
  • a STREAM_HEADER_TRACK message can contain one or more objects with Priority #1 priority, as well as objects of other priorities.
  • Mapping rule 9 above means: If the message type of a MoQ message is a STREAM_HEADER_GROUP message, the priority of one or more objects in the MoQ message is Priority #1, and the value of the group ID field in the MoQ message is group ID #1, the object is mapped to QoS flow #1.
  • a STREAM_HEADER_GROUP message can contain one or more objects with Priority #1 priority, as well as objects of other priorities.
  • Mapping rule 14 means that if the message type of a MoQ message is STREAM_HEADER_GROUP and the track ID field in the MoQ message is group ID #2, then all objects in the MoQ message are mapped to QoS flow #2.
  • a STREAM_HEADER_GROUP message can contain one or more objects, and these objects can have the same or different priorities.
  • the first mapping rule is used to map an object in a MoQ message of a first message type to a corresponding QoS flow.
  • the SMF network element can send the first mapping rule to the UPF network element through the interface between the SMF network element and the UPF network element.
  • the second mapping rule is used to indicate that PDU set QoS handle is to be performed on the object in the MoQ message of the second message type.
  • the PDU set QoS handle here means that when the object represents a frame, the 5G system can perform PDU set QoS handle based on frame characteristics such as frame end marker, frame importance parameters, etc. For example, according to the frame importance parameters (such as the I ⁇ P ⁇ B frame identifier), important frames (I ⁇ P ⁇ B frames) are mapped to QoS flows of different high and low priorities according to their importance levels; for another example, according to the frame end marker bit, the received frame is considered to be a complete frame, and the 5G system performs frame integrity scheduling based on the end marker bit.
  • the frame end marker bit can be obtained by identifying the payload length field (Payload Length) in the object, and the frame importance can be obtained by identifying the priority field (Send Order) in the object.
  • the second message type is used to indicate a MoQ message containing an object, for example, it may be the aforementioned OBJECT_STREAM message or OBJECT_PREFER_DATAGRAM message.
  • the first network element determining the second mapping rule refers to: the first network element generating the second mapping rule.
  • the first network element is a PCF network element, the PCF network element receives the second message type from the AF network element, and then generates the second mapping rule based on the second message type.
  • the first network element is an SMF network element, the SMF network element receives the second message type from the AF network element or the PCF network element, and then generates the second mapping rule based on the second message type.
  • the PCF network element can send the second mapping rule to the SMF network element through the interface between the PCF network element and the SMF network element, and then the SMF network element sends the second mapping rule to the UPF network element through the interface between the SMF network element and the UPF network element.
  • the above steps 201a and 203a may be completed in one step, and the above steps 202a and 204a may be completed in one step.
  • the UPF network element After receiving the first MoQ message, the UPF network element identifies the type of the first MoQ message. If the first MoQ message is identified as a MoQ message of the first message type, the UPF network element maps the object in the first MoQ message to the corresponding QoS flow according to the first mapping rule.
  • the first mapping rule includes mapping rules 1 to 6.
  • the first MoQ message is a STREAM_HEADER_TRACK message
  • the STREAM_HEADER_TRACK message includes object #1, object #2, and object #3, as well as priority #1 of object #1, priority #3 of object #2, and priority #3 of object #3.
  • the UPF network element can map object #1 to QoS flow #1 according to mapping rule 1, and map object #2 and object #3 to QoS flow #3 according to mapping rule 3.
  • the first mapping rule includes mapping rules 11 and 12.
  • the first MoQ message is a STREAM_HEADER_TRACK message
  • the STREAM_HEADER_TRACK message includes object #1 and object #2, as well as priority #1 for object #1 and priority #2 for object #2, and track ID #1.
  • the UPF network element can map both object #1 and object #2 to QoS flow #1 based on mapping rule 11. At this point, although object #1 and object #2 have different priorities, they are still mapped to the same QoS flow.
  • the first mapping rule includes mapping rules 13 through 14.
  • the first MoQ message is a STREAM_HEADER_GROUP message
  • the STREAM_HEADER_GROUP message includes object #1 and object #2, as well as priority #1 for object #1 and priority #1 for object #2, and group ID #1.
  • the UPF network element can map both object #1 and object #2 to QoS flow #1 based on mapping rule 13. In this case, object #1 and object #2 have the same priority and are mapped to the same QoS flow.
  • Step 207a is an optional step. When the above steps 203a and 204a are executed, step 207a may also be executed.
  • the UPF network element may also receive indication information indicating the identification of the type of the MoQ message.
  • the UPF network element identifies the type of the first MoQ message based on the indication information.
  • Step 206a or step 207a is then performed based on the type of the first MoQ message.
  • the PCF network element may receive the indication information from the AF network element, then send the indication information to the SMF network element, which then sends the indication information to the UPF network element.
  • the SMF network element may receive the indication information from the AF network element or the PCF network element, then send the indication information to the UPF network element.
  • the method comprises the following steps:
  • the mapping rule is used to indicate the first message type or the second message type of each MoQ message in at least two MoQ messages, and to indicate the mapping relationship between the QoS flow and the first message type and the first parameter of each MoQ message, and/or to indicate the mapping relationship between the QoS flow and the second message type and the second parameter of each MoQ message.
  • the objects in the at least two MoQ messages are transmitted through the same connection (based on QUIC), so the objects in the at least two MoQ messages correspond to the same IP five-tuple information.
  • the first message type is used to indicate a stream-by-stream MoQ message.
  • the stream-by-stream MoQ message refers to the reliable transmission of the object in the MoQ message, or it can be understood that the object is transmitted in a reliable stream.
  • Reliable transmission is similar to TCP transmission. Since reliable transmission has high requirements on transmission reliability, the objects in the stream-by-stream MoQ message need to be mapped to a QoS stream with a higher guarantee level for transmission to ensure the success rate, delay and/or quality of the object transmission.
  • the MoQ message of the first message type can be the aforementioned OBJECT_STREAM message, STREAM_HEADER_TRACK message or STREAM_HEADER_GROUP message, etc.
  • the second parameter includes information about the object in the MoQ message of the second message type.
  • the object information may include at least one of the object's priority, candidate values for the track field in the MoQ message, or candidate values for the group field in the MoQ message.
  • the second parameter may include the object's priority, and candidate values for the track field in the MoQ message or candidate values for the group field in the MoQ message, wherein the track field is used to indicate the track to which the object in the OBJECT_PREFER_DATAGRAM message belongs, and the group field is used to indicate the group to which the object in the OBJECT_PREFER_DATAGRAM message belongs.
  • mapping rule is explained below with reference to an example.
  • the MoQ message of the first message type includes an OBJECT_STREAM message, a STREAM_HEADER_TRACK message, and a STREAM_HEADER_GROUP message
  • the priority value of the object in the first parameter can be priority #1, priority #2, or priority #3
  • the MoQ message of the second message type includes an OBJECT_PREFER_DATAGRAM message, and the priority value of the object in the second parameter can be priority #3 or priority #4
  • the QoS streams include QoS stream #1, QoS stream #2, and QoS stream #3.
  • the mapping rules include, but are not limited to, one or more of the following mapping rules 1 to mapping rule 18.
  • Mapping rule 15 (OBJECT_PREFER_DATAGRAM message, track ID #1) -> QoS flow #2.
  • Mapping rule 4 above means: If the message type of a MoQ message is a STREAM_HEADER_GROUP message, and the priority of one or more objects in the MoQ message is Priority #1, the object is mapped to QoS flow #1.
  • the STREAM_HEADER_GROUP message can contain one or more objects with Priority #1, as well as objects of other priorities.
  • Mapping rule 5 above means: If the message type of a MoQ message is a STREAM_HEADER_GROUP message, and the priority of one or more objects in the MoQ message is priority #2, the object is mapped to QoS flow #2.
  • the STREAM_HEADER_GROUP message can contain one or more objects with priority #2, as well as objects of other priorities.
  • mapping rule 8 is: if the message type of a MoQ message is an OBJECT_STREAM message, and the priority of an object in the MoQ message is priority #2, the object is mapped to QoS flow #2.
  • Mapping rule 11 above means: If the message type of a MoQ message is a STREAM_HEADER_TRACK message, and the track ID field in the MoQ message is set to track ID #1, then all objects in the MoQ message are mapped to QoS flow #1.
  • a STREAM_HEADER_TRACK message can contain one or more objects, and these objects can have the same or different priorities.
  • Mapping rule 13 above means that if the message type of a MoQ message is a STREAM_HEADER_GROUP message, and the track ID field in the MoQ message is group ID #1, then all objects in the MoQ message are mapped to QoS flow #1.
  • a STREAM_HEADER_GROUP message can contain one or more objects, and these objects can have the same or different priorities.
  • Mapping rule 14 means that if the message type of a MoQ message is STREAM_HEADER_GROUP and the track ID field in the MoQ message is group ID #2, then all objects in the MoQ message are mapped to QoS flow #2.
  • a STREAM_HEADER_GROUP message can contain one or more objects, and these objects can have the same or different priorities.
  • mapping rule 15 is: if the message type of a MoQ message is OBJECT_PREFER_DATAGRAM message, and the value of the track ID field in the MoQ message is track ID#1, then the object in the MoQ message is mapped to QoS flow #2.
  • mapping rule 16 is: if the message type of a MoQ message is OBJECT_PREFER_DATAGRAM message, and the value of the track ID field in the MoQ message is track ID#2, then the object in the MoQ message is mapped to QoS flow #3.
  • mapping rule 17 is: if the message type of a MoQ message is OBJECT_PREFER_DATAGRAM message, and the value of the track ID field in the MoQ message is group ID#1, then the object in the MoQ message is mapped to QoS flow#2.
  • mapping rule 18 is: if the message type of a MoQ message is OBJECT_PREFER_DATAGRAM message, and the value of the track ID field in the MoQ message is group ID#2, then the object in the MoQ message is mapped to QoS flow #3.
  • the first network element determines the mapping rule, which means that the first network element configures the mapping rule, or it can be understood that the mapping rule is pre-configured on the first network element.
  • the first network element can be an SMF network element or a PCF network element.
  • the above mapping rule can also be split into two mapping rules, for example, the two mapping rules include a first mapping rule and a second mapping rule.
  • the first mapping rule is used to indicate the mapping relationship between the QoS flow and the first message type and the first parameter
  • the second mapping rule is used to indicate the mapping relationship between the QoS flow and the second message type and the second parameter.
  • Step 202b The first network element sends the mapping rule to the UPF network element.
  • the UPF network element receives the mapping rule.
  • the mapping rule is used to map an object in a MoQ message of a first message type to a corresponding QoS flow, and to map an object in a MoQ message of a second message type to a corresponding QoS flow.
  • the PCF network element can send the mapping rules to the SMF network element through the interface between the PCF network element and the SMF network element, and then the SMF network element sends the mapping rules to the UPF network element through the interface between the SMF network element and the UPF network element.
  • the SMF network element can send the mapping rules to the UPF network element through the interface between the SMF network element and the UPF network element.
  • Step 203b The UPF network element receives the first MoQ message.
  • Step 204b If it is identified that the first MoQ message is a MoQ message of the first message type, the UPF network element maps the object in the first MoQ message to the corresponding QoS flow according to the mapping rule.
  • Step 205b If it is identified that the first MoQ message is a MoQ message of the second message type, the UPF network element maps the object in the first MoQ message to the corresponding QoS flow according to the mapping rule.
  • the UPF network element After receiving the first MoQ message, the UPF network element identifies the type of the first MoQ message. If the first MoQ message is identified as a MoQ message of the first message type, the UPF network element maps the objects in the first MoQ message to the corresponding QoS flow according to the mapping rules. If the first MoQ message is identified as a MoQ message of the second message type, the UPF network element maps the objects in the first MoQ message to the corresponding QoS flow according to the mapping rules.
  • the first MoQ message is specifically a STREAM_HEADER_TRACK message, and the STREAM_HEADER_TRACK message includes object #1, object #2, and object #3, as well as priority #1 of object #1, priority #3 of object #2, and priority #3 of object #3.
  • the UPF network element can map object #1 to QoS flow #1 according to mapping rule 1, and map object #2 and object #3 to QoS flow #3 according to mapping rule 3.
  • the first MoQ message is specifically an OBJECT_PREFER_DATAGRAM message, and the OBJECT_PREFER_DATAGRAM message includes object #1 and priority #3 of object #1.
  • the UPF network element can map object #1 to QoS flow #2 according to mapping rule 9.
  • mapping rules include mapping rules 15 to 18, the first MoQ message is specifically an OBJECT_PREFER_DATAGRAM message, and the OBJECT_PREFER_DATAGRAM message includes object #1 and track ID #1.
  • the UPF network element can map object #1 to QoS flow #2 according to mapping rule 15.
  • the first MoQ message is specifically an OBJECT_PREFER_DATAGRAM message, and the OBJECT_PREFER_DATAGRAM message includes object #1 and group ID #2, the UPF network element can map object #1 to QoS flow #3 according to mapping rule 18.
  • the priorities of the multiple objects may also be the same.
  • the first MoQ message may only include one priority, which represents the priority of all objects in the first MoQ message.
  • the UPF network element may also receive indication information indicating the identification of the type of the MoQ message.
  • the UPF network element identifies the type of the first MoQ message based on the indication information.
  • Step 204b or step 205b is then performed based on the type of the first MoQ message.
  • the first network element is a PCF network element
  • the PCF network element may receive the indication information from the AF network element, then send the indication information to the SMF network element, which then sends the indication information to the UPF network element.
  • the SMF network element may receive the indication information from the AF network element or the PCF network element, then send the indication information to the UPF network element.
  • the multiple objects can be mapped to corresponding QoS flows for transmission based on the mapping rules. If the first MoQ message includes one object, the one object can also be mapped to the corresponding QoS flow for transmission based on the mapping rules. This implements the mapping of objects in the MoQ message to QoS flows, can meet the QoS transmission requirements of different objects, and thus can improve user experience.
  • step 300a the UE has established a session and sends a subscription request to the UPF network element.
  • the UPF network element receives the subscription request.
  • This subscription request is used to subscribe to the media content of a track, group, or object.
  • step 300b the UPF network element sends a subscription request to the AF network element.
  • the AF network element receives the subscription request.
  • Step 301 The AF network element sends a first request to the PCF network element.
  • the PCF network element receives the first request.
  • the first request may be a session establishment request with specific QoS requirements (sessionwith QoS create request).
  • the first request includes indication information, a first message type, and a first parameter corresponding to the first message type.
  • the first parameter includes information about an object in a MoQ message of the first message type, where the object information includes at least one of candidate values for a priority field (send order), candidate values for a track field in the MoQ message, or candidate values for a group field in the MoQ message.
  • the priority field is used to indicate the priority of the object in the MoQ message of the first message type.
  • the first parameter includes priority #1, priority #2, and priority #3.
  • the track field is used to indicate the identifier (track ID) of the track.
  • the group field is used to indicate the identifier (group ID) of the group.
  • the priority of the object in the first parameter includes priority #1, priority #2, and priority #3, as well as track ID #1, track ID #2, group ID #1, and group ID #2.
  • the first request also includes a second message type.
  • the second message type is used to indicate a MoQ message containing an object, for example, it may be an OBJECT_STREAM message or an OBJECT_PREFER_DATAGRAM message.
  • Step 302 The PCF network element determines a PCC rule.
  • the PCC rule includes a first mapping rule corresponding to the first message type, wherein the first mapping rule is used to indicate the first message type of each of the at least two MoQ messages and to indicate a mapping relationship between the QoS flow and the first message type and first parameter of each MoQ message.
  • the PCC rule further includes a second mapping rule corresponding to the second message type.
  • the second mapping rule is used to instruct to perform PDU aggregate QoS processing on the MoQ message of the second message type.
  • step 303 the PCF network element sends a session management policy establishment request (SM Policy Establish Request) message to the SMF network element.
  • SM Policy Establish Request session management policy establishment request
  • the indication information is used to indicate the identification of the type of the MoQ message.
  • Step 304 The SMF network element sends an N4 message to the UPF network element.
  • the UPF network element receives the N4 message.
  • the indication information is used to indicate the identification of the type of the MoQ message.
  • Step 305 The AF network element sends a subscription success message to the UPF network element.
  • the UPF network element receives the subscription success message.
  • Step 306 The AF network element sends a first MoQ message to the UPF network element.
  • the UPF network element receives the first MoQ message.
  • the first MoQ message may be a MoQ message of a first message type (eg, a STREAM_HEADER_GROUP message or a STREAM_HEADER_TRACK message), or may be a MoQ message of a second message type (eg, an OBJECT_STREAM message or an OBJECT_PREFER_DATAGRAM message).
  • a first message type e.g, a STREAM_HEADER_GROUP message or a STREAM_HEADER_TRACK message
  • a MoQ message of a second message type eg, an OBJECT_STREAM message or an OBJECT_PREFER_DATAGRAM message.
  • Step 307 The UPF network element identifies the type of the first MoQ message according to the indication information.
  • Step 308 If the type of the first MoQ message is the first message type, the UPF network element maps the object in the first MoQ message to the corresponding QoS flow according to the first mapping rule.
  • Step 309 If the type of the first MoQ message is the second message type, the UPF network element performs PDU aggregate QoS processing on the first MoQ message according to the second mapping rule.
  • the multiple objects can be mapped to corresponding QoS flows for transmission based on the first mapping rule, thereby realizing the mapping of objects in the MoQ message to QoS flows, which can meet the QoS transmission requirements of different objects, thereby improving the user experience.
  • step 400a the UE has established a session and sends a subscription request to the UPF network element.
  • the UPF network element receives the subscription request.
  • This subscription request is used to subscribe to the media content of a track, group, or object.
  • step 400b the UPF network element sends a subscription request to the AF network element.
  • the AF network element receives the subscription request.
  • a subscription request is sent to the AF network element.
  • This subscription request is used to subscribe to the media content of a track, group, or object.
  • Step 401 The AF network element sends a first request to the PCF network element.
  • the PCF network element receives the first request.
  • the first request is a session establishment request with specific QoS requirements.
  • the first request includes indication information, a first message type, a first parameter corresponding to the first message type, a second message type, and a second parameter corresponding to the second message type.
  • the first message type is used to indicate a stream-by-stream MoQ message, for example, it may be a STREAM_HEADER_TRACK message, a STREAM_HEADER_GROUP message, or an OBJECT_STREAM message.
  • the first parameter includes information about an object in a MoQ message of the first message type.
  • the object information includes at least one of candidate values for a priority field (send order), candidate values for a track field in the MoQ message, or candidate values for a group field in the MoQ message.
  • the priority field indicates the priority of the object in the MoQ message of the first message type.
  • the object priorities in the first parameter include priority #1, priority #2, and priority #3.
  • the second message type is used to indicate a packet-by-packet MoQ message, for example, it may be an OBJECT_PREFER_DATAGRAM message.
  • the second parameter includes information about an object in a MoQ message of the second message type.
  • the object information includes at least one of candidate values for a priority field, candidate values for a track field in the MoQ message, or candidate values for a group field in the MoQ message.
  • the priority field indicates the priority of the object in the MoQ message of the second message type.
  • the object priorities in the second parameter include priority #3 and priority #4.
  • Step 402 The PCF network element determines the PCC rule.
  • Step 403 The PCF network element sends a session management policy establishment request message to the SMF network element.
  • the SMF network element receives the session management policy establishment request message.
  • the session management policy establishment request message includes PCC rules and indication information.
  • the PCC rule includes a mapping rule.
  • Step 404 The SMF network element sends an N4 message to the UPF network element.
  • the UPF network element receives the N4 message.
  • the indication information is used to indicate the identification of the type of the MoQ message.
  • Step 405 The AF network element sends a subscription success message to the UPF network element.
  • the UPF network element receives the subscription success message.
  • Step 406 The AF network element sends a first MoQ message to the UPF network element.
  • the UPF network element receives the first MoQ message.
  • the first MoQ message may be a MoQ message of a first message type (eg, a STREAM_HEADER_GROUP message, a STREAM_HEADER_TRACK message, or an OBJECT_STREAM message), or may be a MoQ message of a second message type (eg, an OBJECT_PREFER_DATAGRAM message).
  • a first message type e.g, a STREAM_HEADER_GROUP message, a STREAM_HEADER_TRACK message, or an OBJECT_STREAM message
  • a MoQ message of a second message type eg, an OBJECT_PREFER_DATAGRAM message
  • Step 407 The UPF network element identifies the type of the first MoQ message according to the indication information.
  • Step 408 The UPF network element maps the object in the first MoQ message to the corresponding QoS flow according to the type and mapping rule of the first MoQ message.
  • the multiple objects can be mapped to corresponding QoS flows for transmission based on the mapping rules. If the first MoQ message includes one object, the one object can also be mapped to the corresponding QoS flow for transmission based on the mapping rules. This implements the mapping of objects in the MoQ message to QoS flows, can meet the QoS transmission requirements of different objects, and thus can improve user experience.
  • FIG5 is a flow chart of a communication method provided in an embodiment of the present application. The method includes the following steps:
  • Steps 500a to 500b are the same as steps 301 to 302 in the embodiment of FIG. 3 .
  • step 501 the UE sends a DNS request to the PSA UPF network element.
  • the PSA UPF network element receives the DNS request.
  • the DNS request includes the uniform resource locator (URL) corresponding to the MoQ domain name.
  • URL uniform resource locator
  • the URL is MoQ.xx.com/video, where MoQ.xx.com is the MoQ domain name.
  • the request message includes the MoQ domain name, and the request message requests to select a relay UPF network element based on the MoQ domain name.
  • the SMF network element selects the relay UPF network element based on the MoQ domain name.
  • the first MoQ message may be a MoQ message of a first message type (eg, a STREAM_HEADER_GROUP message, a STREAM_HEADER_TRACK message, or an OBJECT_STREAM message), or may be a MoQ message of a second message type (eg, an OBJECT_PREFER_DATAGRAM message).
  • a first message type e.g, a STREAM_HEADER_GROUP message, a STREAM_HEADER_TRACK message, or an OBJECT_STREAM message
  • a MoQ message of a second message type eg, an OBJECT_PREFER_DATAGRAM message
  • Step 607 The relay UPF network element maps the object in the first MoQ message to the corresponding QoS flow according to the type and mapping rule of the first MoQ message.
  • the communication device 700 shown in Figure 7 includes a processing unit 710 and a transceiver unit 720.
  • the communication device 700 is used to implement the functions of the first network element, the user plane network element or the application function network element in the above method embodiment.
  • the processing unit 710 is configured to determine a first mapping rule, where the first mapping rule is used to indicate a first message type of each MoQ message in at least two MoQ messages, and to indicate a mapping relationship between a QoS flow and the first message type and a first parameter of each of the MoQ messages, where the first parameter includes information about an object in the MoQ message, and the first message type of the MoQ message indicates that the MoQ message contains multiple objects; and the objects in each of the MoQ messages are transmitted via the same connection; and the transceiver unit 720 is configured to send the first mapping rule, where the first mapping rule is used to map the objects in the at least two MoQ messages to corresponding QoS flows.
  • the first network element is a policy control network element; the transceiver unit 720 is further configured to receive the first message type and the first parameter from an application function network element.
  • the first network element is a policy control network element; the transceiver unit 720 is further configured to receive indication information from an application function network element, the indication information being used to indicate identification of the type of the MoQ message, and to send the indication information to a session management network element.
  • the first network element is a session management network element; the transceiver unit 720 is further configured to receive indication information from the policy control network element, the indication information being used to indicate identification of the type of the MoQ message, and send the indication information to the user plane network element.
  • the information of the object in the MoQ message includes at least one of a priority of the object, a candidate value of a track field in the MoQ message, or a candidate value of a group field in the MoQ message.
  • the transceiver unit 720 is further configured to send a second message type to the first network element, where the second message type is used to indicate a MoQ message containing an object.
  • the transceiver unit 720 is configured to receive a first MoQ message; if the first MoQ message is identified as a MoQ message of a first message type, the processing unit 710 is configured to map the object in the first MoQ message to a corresponding QoS flow according to a mapping rule; or if the first MoQ message is a MoQ message of a second message type, the processing unit 710 is configured to map the object in the first MoQ message to a corresponding QoS flow according to the mapping rule; wherein the mapping rule is configured to indicate the first message type or the second message type of each MoQ message in at least two MoQ messages, and to indicate a mapping relationship between a QoS flow and the first message type and first parameter of each MoQ message, and/or a mapping relationship between a QoS flow and the second message type and second parameter of each MoQ message; the first message type is configured to indicate a flow-by-flow MoQ message
  • the information of the object in the MoQ message of the first message type includes at least one of the priority of the object in the MoQ message of the first message type, the candidate value of the track field in the MoQ message of the first message type, or the candidate value of the group field in the MoQ message of the first message type;
  • the information of the object in the MoQ message of the second message type includes at least one of the priority of the object in the MoQ message of the second message type, the candidate value of the track field in the MoQ message of the second message type, or the candidate value of the group field in the MoQ message of the second message type.
  • the transceiver unit 720 is further configured to receive indication information, where the indication information is used to indicate identification of the type of the MoQ message; and the processing unit 710 is further configured to identify the type of the first MoQ message according to the indication information.
  • the first network element is a policy control network element or a session management network element.
  • processing unit 710 and the transceiver unit 720 For a more detailed description of the processing unit 710 and the transceiver unit 720, reference can be made to the relevant description in the above method embodiment, which will not be repeated here.
  • the communication device 800 shown in FIG8 includes a processor 810 and an interface circuit 820.
  • the processor 810 and the interface circuit 820 are coupled to each other.
  • the interface circuit 820 may be a transceiver or an input/output interface.
  • the communication device 800 may further include a memory 830 for storing instructions executed by the processor 810, input data required by the processor 810 to execute instructions, or data generated after the processor 810 executes instructions.
  • processors in the embodiments of the present application may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions.
  • the software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, mobile hard disks, compact disc read-only memory (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium can also be a component of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in a first network element, a user plane network element or an application function network element.
  • the processor and the storage medium can also exist as discrete components in an access network device or a terminal device.
  • the above embodiments they can be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software When implemented using software, they can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs or instructions.
  • a computer program refers to a set of instructions that instructs an electronic computer or other device with message processing capabilities to perform each step of the action, usually written in a certain programming language and running on a certain target architecture.
  • the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device.

Landscapes

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

Abstract

La présente demande concerne un procédé de communication, un appareil de communication, et un système de communication. Dans le procédé, par rapport à un message MoQ, si le message MoQ comprend une pluralité d'objets, la pluralité d'objets peut être mise en correspondance, sur la base de règles de mise en correspondance, avec des flux de QoS correspondants pour la transmission, de sorte que la mise en correspondance à partir des objets dans le message MoQ avec les flux de QoS soit réalisée, et les exigences de transmission de QoS de différents objets peuvent être satisfaites, et ainsi l'expérience de l'utilisateur peut également être améliorée.
PCT/CN2025/086103 2024-04-03 2025-03-31 Procédé de communication, appareil de communication, et système de communication Pending WO2025209383A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410404623.9A CN120786463A (zh) 2024-04-03 2024-04-03 通信方法、通信装置及通信系统
CN202410404623.9 2024-04-03

Publications (1)

Publication Number Publication Date
WO2025209383A1 true WO2025209383A1 (fr) 2025-10-09

Family

ID=97266373

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/086103 Pending WO2025209383A1 (fr) 2024-04-03 2025-03-31 Procédé de communication, appareil de communication, et système de communication

Country Status (2)

Country Link
CN (1) CN120786463A (fr)
WO (1) WO2025209383A1 (fr)

Also Published As

Publication number Publication date
CN120786463A (zh) 2025-10-14

Similar Documents

Publication Publication Date Title
CN112954768B (zh) 通信方法、装置及系统
WO2023213177A1 (fr) Procédé et appareil de communication
WO2023020046A1 (fr) Procédé de communication et appareil de communication
WO2021213000A1 (fr) Procédé, appareil et système de transmission de paquet multimédia
WO2023231450A1 (fr) Procédé de synchronisation temporelle et appareil de communication
WO2023016298A1 (fr) Procédé de sensibilisation au service, appareil de communication et système de communication
WO2023030077A1 (fr) Procédé de communication, appareil de communication et système de communication
CN115915196A (zh) 一种链路状态检测方法、通信装置及通信系统
WO2023213156A1 (fr) Procédé de communication, appareil de communication et système de communication
WO2023179238A1 (fr) Procédé de synchronisation, appareil de communication et système de communication
WO2024012376A1 (fr) Procédé de communication, appareil de communication et système de communication
EP4325929A1 (fr) Procédé de communication sans fil, appareil de communication et système de communication
CN120224483A (zh) 通信方法、通信装置及通信系统
WO2025209383A1 (fr) Procédé de communication, appareil de communication, et système de communication
WO2023056784A1 (fr) Procédé de collecte de données, appareil de communication et système de communication
WO2022067736A1 (fr) Procédé et appareil de communication
WO2025161525A1 (fr) Procédé de communication et appareil de communication
CN118869615A (zh) 一种通信方法、通信装置及通信系统
WO2025113218A1 (fr) Procédé de communication, appareil de communication et système de communication
WO2025050676A1 (fr) Procédé de communication, appareil de communication et système de communication
WO2025102808A1 (fr) Procédé de communication, appareil de communication et système de communication
WO2023231465A1 (fr) Procédé de synchronisation temporelle, appareil de communication et système de communication
WO2023246649A1 (fr) Procédé de communication, appareil de communication et système de communication
WO2024239660A1 (fr) Procédé de communication, appareil de communication et système de communication
WO2023179331A1 (fr) Procédé d'envoi de paquets de données, dispositif de communication et système de communication

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: 25781678

Country of ref document: EP

Kind code of ref document: A1