Communication method and related device

Abstract

A communication method and related apparatus, the method comprising: sending a first message to a network device, the first message being used to create a first QoS flow for an XR service request, the first QoS flow supporting PDU Set-based processing. And receiving a second message from the network equipment, wherein the second message comprises the first QoS parameter corresponding to the first QoS flow. By adopting the embodiment of the invention, the service quality requirement of the user on the XR service can be met, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication method and related devices. Background Art

[0002] In the next generation communication system, the terminal device can establish at least one packet data unit (PDU) session with the core network device through the access network device, wherein at least one quality of service (QoS) flow can be established for each PDU session. Extended reality (XR) service is one of the key media applications of 5G, with high throughput and high reliability transmission requirements.

[0003] In order to meet the service quality requirements of XR services and improve the user experience of XR, the 3rd generation partnership project (3GPP) has set up a working group to study the characteristics of XR services and the enhanced technology of XR service transmission. Usually, XR services will generate data frames periodically at a certain frame rate. For example, taking an augmented reality (AR) service with a frame rate of 60fps as an example, 60 frames of video images are generated per second, and a video frame appears approximately every 16.66ms. The data of a video frame may be carried and transmitted by multiple data packets. In general, it is meaningful only when all the data packets of a frame are received or received in excess of a certain proportion under a specific delay condition. Therefore, the traditional transmission requirements based on the delay and packet loss rate of the packet granularity have evolved into transmission requirements based on the packet data unit set (i.e., PDU Set), i.e., PDU Set delay budget (PSDB) and PDU Set error rate (PSER). A PDU Set may refer to a set of data packets constituting a frame. If the video is encoded in a slice manner, a PDU Set may refer to a set of data packets constituting a slice.

[0004] Currently, for XR services, the QoS flow created for XR services may not meet users' service quality requirements or user experience for XR services. Therefore, how to meet users' service quality requirements for XR services has become an urgent problem to be solved. Summary of the invention

[0005] The present application provides a communication method and related devices, which can meet the service quality requirements of terminal devices for XR services and help improve user experience.

[0006] In a first aspect, the present application provides a communication method, which is performed by a terminal device, which may be the terminal device itself, or a unit or module (such as a chip) with corresponding functions in the terminal device. In this method, the terminal device sends a first message to a network device, and the first message is used to create a first quality of service flow QoS flow for an extended reality XR service request, and the first QoS flow supports processing based on a packet data unit set PDU Set;

[0007] The terminal device receives a second message from the network device, where the second message includes a first QoS parameter corresponding to the first QoS flow.

[0008] In an embodiment of the present application, the terminal device can actively apply for / request to create a QoS flow for the XR service. After the network device completes the creation of the QoS flow for the XR service based on the request of the terminal device, the network device can send the QoS parameters configured when the network device actually creates the flow to the terminal device. This method of actively requesting creation by the terminal device can meet the user's service quality requirements for the XR service, which is conducive to improving the user experience.

[0009] In one possible design, before sending the first message to the network device, the method further includes:

[0010] The terminal device sends a PDU session establishment request to the network device;

[0011] The terminal device receives a PDU session establishment acceptance message from the network device;

[0012] The terminal device sends a first message to the network device, including:

[0013] Determining, according to the PDU session establishment acceptance message, whether the second QoS flow corresponding to the XR service supports PDU Set-based processing;

[0014] In a case where the second QoS flow does not support PDU Set-based processing, the first message is sent to the network device.

[0015] In this implementation mode, the terminal device can first determine whether the second QoS flow corresponding to the XR service created during the PDU session establishment process supports PDU Set-based processing. When it is determined that the second QoS flow does not support PDU Set-based processing, it sends a first message to the network device to request the creation of a first QoS flow that supports PDU Set-based processing. By creating a QoS flow based on PDU Set processing for the XR service, it can ensure that the network can transmit important PDU Sets in network congestion scenarios.

[0016] In one possible design, the PDU session establishment accept message includes first indication information and second indication information;

[0017] The first indication information indicates the second QoS flow;

[0018] The second indication information indicates whether the second QoS flow supports PDU Set-based processing.

[0019] In this implementation, the first indication information and the second indication information respectively indicate whether the second QoS flow and the second QoS flow support PDU Set-based processing. This has strong operability and allows the terminal device to prepare to determine whether the established second QoS flow supports PDU Set-based processing.

[0020] In a possible design, the terminal device sends a first message to the network device, including:

[0021] Acquire first information of the XR service, where the first information includes a second QoS parameter of the XR service, where the second QoS parameter includes one or more of the following information: a second PSDB, a second PSER, or a second PHISI;

[0022] The first message is sent to the network device according to the first information.

[0023] In this implementation, obtaining the first information of the XR service can be specifically understood as the application inside the terminal device for providing the XR service can open QoS information to the terminal device. Therefore, the application can actively report the first information corresponding to the XR service to the upper layer (such as the application layer) of the terminal device, or the terminal device can periodically read the first information of the XR service provided by the application from the application inside the terminal device. This implementation method of opening QoS information to the terminal device by the application can obtain the QoS requirements of the XR service in real time, so as to establish a QoS flow that meets the QoS requirements in a timely manner.

[0024] In one possible design, the first message includes one or more of the following third QoS parameters expected by the terminal device:

[0025] a third PSDB, a third PSER, a third PHISI, or a first tag value;

[0026] The first marking value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction, and the third QoS parameter is determined based on the second QoS parameter.

[0027] In this implementation, the terminal device sends an expected first tag value to the network device, so the network device can establish a QoS flow that supports the processing of the PDU Set in the uplink direction and / or the downlink direction according to the first tag value.

[0028] In one possible design, the first QoS parameter includes one or more of the following QoS parameters configured by the network device:

[0029] A first PSDB, a first PSER, a first PHISI, or a first tag value.

[0030] In this implementation, the network device sends the QoS parameters actually configured by the network device to the terminal device, which can be used to confirm the configuration of the network device. After the terminal device receives the first tag value sent by the network device, the terminal device can determine that the QoS flow established by the network device supports the processing of PDUSet in the uplink direction and / or downlink direction according to the first tag value.

[0031] In a possible design, the terminal device sends a first message to the network device, including:

[0032] When the XR service is determined according to the traffic characteristics, the first message is sent to the network device.

[0033] In this implementation mode, the method of determining XR services through traffic characteristics is relatively flexible and does not rely on the open capabilities of the network-side APP or the terminal's internal APP.

[0034] In one possible design, the first message includes one or more of the following third QoS parameters expected by the terminal device:

[0035] A first tag value, a second tag value, or a first 5QI; the first tag value is used to indicate support for PDU Set processing in the uplink direction and / or downlink direction, the second tag value is used to indicate that the first QoS flow supports PDU Set-based processing, the parameters indicated by the first 5QI include a packet delay budget PDB and a packet error rate PER, and the first 5QI is the 5QI associated with the second QoS flow.

[0036] In this implementation, the second tag value can be used by the network device to determine that the first Qos flow requested by the terminal device is processed based on the PDU Set. Therefore, the network device can process the PDB and PER indicated by the first 5QI as the PSDB and PSER expected by the terminal device. This implementation method of multiplexing the existing 5QI can save signaling overhead and is conducive to forward compatibility.

[0037] In one possible design, the first QoS parameter includes one or more of the following QoS parameters configured by the network device:

[0038] A first tag value, a second tag value, or a second 5QI.

[0039] In this implementation, the network device sends the QoS parameters actually configured by the network device to the terminal device, which can be used to confirm the configuration of the network device.

[0040] In one possible design, the first message is a PDU session modification request message, and / or the second message is a PDU session modification command message.

[0041] In this implementation, the first message is a PDU session modification request message, and the second message is a PDU session modification command message. This implementation method of enhancing existing messages can reduce the impact on the protocol and is conducive to forward compatibility of the protocol.

[0042] In one possible design, the first message includes flow information of the XR service.

[0043] In this implementation mode, the flow information of the XR service can be used by the network device to create the first QoS flow, which has strong operability.

[0044] In a second aspect, the present application provides a communication method, which is performed by a terminal device, which may be the terminal device itself, or a unit or module (such as a chip) in the terminal device with corresponding functions. In this method, the terminal device sends a third message to the network device, and the third message is used to request modification of a fourth QoS parameter corresponding to a third quality of service flow QoS flow created for an extended reality XR service; the third QoS flow supports processing based on a packet data unit set PDU Set;

[0045] The terminal device receives a fourth message from the network device, where the fourth message includes QoS parameter update information corresponding to the third QoS flow.

[0046] In an embodiment of the present application, the terminal device can actively apply for / request to modify the QoS parameters corresponding to the QoS flow established for the XR service during the PDU session establishment process. After the network device completes the modification of the QoS parameters corresponding to the QoS flow of the XR service based on the request of the terminal device, the network device can send the QoS parameters reconfigured by the network device to the terminal device. This method in which the terminal device actively requests to modify the QoS parameters can meet the user's service quality requirements for the XR service, which is conducive to improving the user experience.

[0047] In one possible design, before the terminal device sends the third message to the network device, the method further includes:

[0048] The terminal device sends a PDU session establishment request to the network device;

[0049] The terminal device receives a PDU session establishment accept message from the network device, where the PDU session establishment accept message includes third indication information, and the third indication information indicates the third QoS flow.

[0050] In this implementation, the third QoS flow is indicated by the third indication information, and the third indication information may be based on the existing packet filter information and the identification information of the QoS flow. Reusing the existing information may reduce the modification of the protocol.

[0051] In a possible design, the PDU session establishment accept message also includes a fourth QoS parameter, where the fourth QoS parameter includes one or more of the following information: a fourth PDU Set delay budget PSDB, a fourth PDU Set error rate PSER, a fourth PDU Set integrated processing information PHISI, or a first tag value; the first tag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction;

[0052] The terminal device sends a third message to the network device, including:

[0053] Acquire a fifth QoS parameter of the XR service, where the fifth QoS parameter includes one or more of the following information: a fifth PSDB, a fifth PSER, or a fifth PHISI;

[0054] In a case where the fourth QoS parameter does not match the fifth QoS parameter, the third message is sent to the network device based on the fifth QoS parameter.

[0055] In this implementation method, the mismatch between the fourth QoS parameter and the fifth QoS parameter can be understood as each item of the fourth QoS parameter and the fifth QoS parameter is different, or one or more items are different, and sending a third message to the network device based on the fifth QoS parameter can be understood as taking the fifth QoS parameter as the third QoS parameter expected by the terminal device, and carrying it in the third message and sending it to the network device.

[0056] In one possible design, the PDU session establishment acceptance message also includes a fourth QoS parameter, and the fourth QoS parameter includes one or more of the following information: a fourth PSDB, a fourth PSER, a fourth PHISI, or a first tag value; the first tag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction;

[0057] The terminal device sends a third message to the network device, including:

[0058] When the number of PDU Sets of the XR service received in a unit time is less than a first threshold, the third message is sent to the network device based on the fourth QoS parameter.

[0059] In this implementation, the number of PDU Sets of XR services received per unit time is less than the first threshold, which means that the XR service user experience is poor, so the terminal device can request the network device to modify the QoS parameters to meet user needs. Here, sending a third message to the network device based on the fourth QoS parameter can be understood as adjusting one or more of the fourth PSDB, fourth PSER, or fourth PHISI included in the fourth QoS parameter, and using the corresponding adjusted parameters as the third PSDB, third PSER, or third PHISI carried in the third QoS parameter to send to the network device, which is highly operable and flexible.

[0060] In one possible design, the third message includes one or more of the following third QoS parameters expected by the terminal device:

[0061] a third PSDB, a third PSER, or a third PHISI;

[0062] The third QoS parameter is determined based on the fourth QoS parameter, or the third QoS parameter is determined based on the fifth QoS parameter.

[0063] The method of carrying the third QoS flow parameter by the third message to request the establishment of a QoS flow is similar to the existing mechanism and is easy to implement. In one possible design, the QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device:

[0064] A sixth PSDB, a sixth PSER, or a sixth PHISI.

[0065] In this implementation, the network device sends the reconfigured QoS parameters of the network device to the terminal device, which can be used to confirm the configuration of the network device. At the same time, it is convenient for the terminal device to perceive the parameters of the current QoS flow, so as to find that the QoS requirements are not met in the future and initiate modification.

[0066] In a possible design, the PDU session establishment accept message also includes a fourth QoS parameter, where the fourth QoS parameter includes one or more of the following information: a fourth 5QI, a first tag value, or a third tag value; the first tag value is used to indicate support for processing of PDU Set in an uplink direction and / or a downlink direction, and the third tag value is used to indicate that the third QoS flow supports processing based on PDU Set;

[0067] The terminal device sends a third message to the network device, including:

[0068] Acquire a fifth QoS parameter of the XR service, where the fifth QoS parameter includes a fifth 5QI;

[0069] In a case where the fourth 5QI and the fifth 5QI do not match, the third message is sent to the network device based on the fifth 5QI.

[0070] In this implementation, the terminal device obtains the fifth QoS parameter of the XR service, which can be understood as: the application inside the terminal device for providing the XR service can open QoS information to the terminal device, so the application can actively report the fifth QoS parameter corresponding to the XR service to the upper layer (such as the application layer) of the terminal device, or, the terminal device can periodically read the fifth QoS parameter of the XR service provided by the application from the application inside the terminal device. The mismatch between the fourth 5QI and the fifth 5QI can be understood as the PDB or PER indicated by the fourth 5QI is different from the PDB or PER indicated by the fifth 5QI. Sending a third message to the network device based on the fifth 5QI can be understood as carrying the fifth 5QI in the third message and sending it to the network device, that is, the fifth 5QI is used as the third 5QI expected by the terminal device.

[0071] In a possible design, the PDU session establishment accept message also includes a fourth QoS parameter, where the fourth QoS parameter includes one or more of the following information: a fourth 5QI, a first tag value, or a third tag value; the first tag value is used to indicate support for processing of PDU Set in an uplink direction and / or a downlink direction, and the third tag value is used to indicate that the third QoS flow supports processing based on PDU Set;

[0072] The terminal device sends a third message to the network device, including:

[0073] When the number of PDU Sets of the XR service received in a unit time is less than a first threshold, the third message is sent to the network device based on the fourth 5QI.

[0074] In this implementation, the number of PDU Sets of XR services received per unit time is less than the first threshold, which means that the XR service user experience is poor, so the terminal device can request the network device to modify the QoS parameters to meet user needs. Here, sending the third message to the network device based on the fourth QoS parameter can be understood as adjusting the PDB or PER indicated by the fourth 5QI, and using the corresponding adjusted parameters as the third 5QI to send to the network device, which is highly operable.

[0075] In one possible design, the third message includes one or more of the following third QoS parameters expected by the terminal device:

[0076] A third 5QI, or a third marking value;

[0077] The third 5QI is determined based on the fourth 5QI parameter, or the third QoS parameter is determined based on the fifth 5QI.

[0078] In this implementation, the network device can determine that the PDB or PER indicated by the third 5QI is actually PSDB or PSER in combination with the third mark value, which can save signaling overhead.

[0079] In one possible design, the QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device:

[0080] Sixth 5QI, or third marker value.

[0081] In this implementation, the network device sends the reconfigured QoS parameters of the network device to the terminal device, which can be used to confirm the configuration of the network device. At the same time, it is convenient for the terminal device to perceive the parameters of the current QoS flow, so as to find that the QoS requirements are not met in the future and initiate modification.

[0082] In one possible design, the third message is a PDU session modification request message, and / or the fourth message is a PDU session modification command message.

[0083] In this implementation, the third message is a PDU session modification request message, and the fourth message is a PDU session modification command message. This implementation method of enhancing existing messages can reduce the impact on the protocol and is conducive to forward compatibility of the protocol.

[0084] In a third aspect, the present application provides a communication method, which is performed by a network device, and the network device may be the network device itself, or a unit or module (such as a chip) in the network device with corresponding functions. In the method, the network device receives a first message from a terminal device, and the first message is used to create a first quality of service flow QoS flow for an extended reality XR service request, and the first QoS flow supports processing based on a packet data unit set PDU Set;

[0085] The network device sends a second message to the terminal device, where the second message includes a first QoS parameter corresponding to the first QoS flow.

[0086] In one possible design, before receiving the first message from the terminal device, the method further includes:

[0087] The network device receives a PDU session establishment request from the terminal device;

[0088] The network device sends a PDU session establishment acceptance message to the terminal device; the PDU session establishment acceptance message is used to indicate whether the second QoS flow corresponding to the XR service supports PDU Set-based processing.

[0089] In one possible design, the PDU session establishment accept message includes first indication information and second indication information;

[0090] The first indication information indicates the second QoS flow;

[0091] The second indication information indicates whether the second QoS flow supports PDU Set-based processing.

[0092] In one possible design, the first message includes one or more of the following third QoS parameters expected by the terminal device:

[0093] a third PSDB, a third PSER, a third PHISI, or a first tag value;

[0094] The first flag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction.

[0095] In one possible design, the first QoS parameter includes one or more of the following QoS parameters configured by the network device:

[0096] A first PSDB, a first PSER, a first PHISI, or a first tag value.

[0097] In one possible design, the first message includes one or more of the following third QoS parameters expected by the terminal device:

[0098] A first tag value, a second tag value, or a first 5QI; the first tag value is used to indicate support for PDU Set processing in the uplink direction and / or downlink direction, the second tag value is used to indicate that the first QoS flow supports PDU Set-based processing, the parameters indicated by the first 5QI include a packet delay budget PDB and a packet error rate PER, and the first 5QI is the 5QI associated with the second QoS flow.

[0099] In one possible design, the first QoS parameter includes one or more of the following QoS parameters configured by the network device:

[0100] A first tag value, a second tag value, or a second 5QI.

[0101] In one possible design, the first message is a PDU session modification request message, and / or the second message is a PDU session modification command message.

[0102] In one possible design, the first message includes flow information of the XR service.

[0103] In a fourth aspect, the present application provides a communication method, which is performed by a network device, which may be the network device itself, or a unit or module (such as a chip) in the network device with corresponding functions. In this method, the network device receives a third message from a terminal device, wherein the third message is used to request modification of a fourth QoS parameter corresponding to a third quality of service flow QoS flow created for an extended reality XR service; the third QoS flow supports processing based on a packet data unit set PDU Set;

[0104] The network device sends a fourth message to the terminal device, where the fourth message includes QoS parameter update information corresponding to the third QoS flow.

[0105] In one possible design, before the network device receives the third message from the terminal device, the method further includes:

[0106] The network device receives a PDU session establishment request from the terminal device;

[0107] The network device sends a PDU session establishment accept message to the terminal device, wherein the PDU session establishment accept message includes third indication information, and the third indication information indicates the third QoS flow.

[0108] In one possible design, the third message includes one or more of the following third QoS parameters expected by the terminal device:

[0109] A third PSDB, a third PSER, or a third PHISI.

[0110] In one possible design, the QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device:

[0111] A sixth PSDB, a sixth PSER, or a sixth PHISI.

[0112] In one possible design, the third message includes one or more of the following third QoS parameters expected by the terminal device:

[0113] Third 5QI, or third marking value.

[0114] In one possible design, the QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device:

[0115] Sixth 5QI, or third marker value.

[0116] In one possible design, the third message is a PDU session modification request message, and / or the fourth message is a PDU session modification command message.

[0117] In a fifth aspect, the present application provides a communication device, which may be the communication device itself, or a module, chip or unit in the communication device. Exemplarily, the communication device may be a terminal device. The communication device includes:

[0118] A transceiver unit, configured to send a first message to a network device, where the first message is used to create a first quality of service flow QoS flow for an extended reality XR service request, where the first QoS flow supports processing based on a packet data unit set PDUSet;

[0119] The transceiver unit is used to receive a second message from the network device, where the second message includes a first QoS parameter corresponding to the first QoS flow.

[0120] In one possible design, before sending the first message to the network device, the transceiver unit is used to:

[0121] Sending a PDU session establishment request to the network device;

[0122] Receiving a PDU session establishment acceptance message from the network device;

[0123] The communication device further comprises a processing unit, wherein:

[0124] The processing unit is configured to determine, according to the PDU session establishment acceptance message, whether the second QoS flow corresponding to the XR service supports PDU Set-based processing;

[0125] The transceiver unit is configured to send the first message to the network device when the second QoS flow does not support PDU Set-based processing.

[0126] In one possible design, the PDU session establishment accept message includes first indication information and second indication information;

[0127] The first indication information indicates the second QoS flow;

[0128] The second indication information indicates whether the second QoS flow supports PDU Set-based processing.

[0129] In one possible design, when sending the first message to the network device, the processing unit is configured to obtain first information of the XR service, where the first information includes a second QoS parameter of the XR service, where the second QoS parameter includes one or more of the following information: a second PSDB, a second PSER, or a second PHISI;

[0130] The transceiver unit is used to send the first message to the network device according to the first information.

[0131] In one possible design, the first message includes one or more of the following third QoS parameters expected by the terminal device:

[0132] a third PSDB, a third PSER, a third PHISI, or a first tag value;

[0133] The first marking value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction, and the third QoS parameter is determined based on the second QoS parameter.

[0134] In one possible design, the first QoS parameter includes one or more of the following QoS parameters configured by the network device:

[0135] A first PSDB, a first PSER, a first PHISI, or a first tag value.

[0136] In a possible design, when sending the first message to the network device, the transceiver unit is used to:

[0137] When the XR service is determined according to the traffic characteristics, the first message is sent to the network device.

[0138] In one possible design, the first message includes one or more of the following third QoS parameters expected by the terminal device:

[0139] A first tag value, a second tag value, or a first 5QI; the first tag value is used to indicate support for PDU Set processing in the uplink direction and / or downlink direction, the second tag value is used to indicate that the first QoS flow supports PDU Set-based processing, the parameters indicated by the first 5QI include a packet delay budget PDB and a packet error rate PER, and the first 5QI is the 5QI associated with the second QoS flow.

[0140] In one possible design, the first QoS parameter includes one or more of the following QoS parameters configured by the network device:

[0141] A first tag value, a second tag value, or a second 5QI.

[0142] In one possible design, the first message is a PDU session modification request message, and / or the second message is a PDU session modification command message.

[0143] In one possible design, the first message includes flow information of the XR service.

[0144] In a sixth aspect, the present application provides a communication device, which may be the communication device itself, or a module, chip or unit in the communication device. Exemplarily, the communication device may be a terminal device. The communication device includes:

[0145] A transceiver unit, configured to send a third message to the network device, wherein the third message is used to request modification of a fourth QoS parameter corresponding to a third quality of service flow QoS flow created for the extended reality XR service; the third QoS flow supports processing based on a packet data unit set PDU Set;

[0146] The transceiver unit is used to receive a fourth message from the network device, where the fourth message includes QoS parameter update information corresponding to the third QoS flow.

[0147] In one possible design, before sending the third message to the network device, the transceiver unit is used to:

[0148] Sending a PDU session establishment request to the network device;

[0149] A PDU session establishment accept message is received from the network device, where the PDU session establishment accept message includes third indication information, and the third indication information indicates the third QoS flow.

[0150] In a possible design, the PDU session establishment accept message also includes a fourth QoS parameter, where the fourth QoS parameter includes one or more of the following information: a fourth PDU Set delay budget PSDB, a fourth PDU Set error rate PSER, a fourth PDU Set integrated processing information PHISI, or a first tag value; the first tag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction;

[0151] When sending the third message to the network device, the transceiver unit is used to:

[0152] Acquire a fifth QoS parameter of the XR service, where the fifth QoS parameter includes one or more of the following information: a fifth PSDB, a fifth PSER, or a fifth PHISI;

[0153] In a case where the fourth QoS parameter does not match the fifth QoS parameter, the third message is sent to the network device based on the fifth QoS parameter.

[0154] In one possible design, the PDU session establishment acceptance message also includes a fourth QoS parameter, and the fourth QoS parameter includes one or more of the following information: a fourth PSDB, a fourth PSER, a fourth PHISI, or a first tag value; the first tag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction;

[0155] When sending the third message to the network device, the transceiver unit is used to:

[0156] When the number of PDU Sets of the XR service received in a unit time is less than a first threshold, the third message is sent to the network device based on the fourth QoS parameter.

[0157] In one possible design, the third message includes one or more of the following third QoS parameters expected by the terminal device:

[0158] a third PSDB, a third PSER, or a third PHISI;

[0159] The third QoS parameter is determined based on the fourth QoS parameter, or the third QoS parameter is determined based on the fifth QoS parameter.

[0160] In one possible design, the QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device:

[0161] A sixth PSDB, a sixth PSER, or a sixth PHISI.

[0162] In a possible design, the PDU session establishment accept message also includes a fourth QoS parameter, where the fourth QoS parameter includes one or more of the following information: a fourth 5QI, a first tag value, or a third tag value; the first tag value is used to indicate support for processing of PDU Set in an uplink direction and / or a downlink direction, and the third tag value is used to indicate that the third QoS flow supports processing based on PDU Set;

[0163] When sending the third message to the network device, the transceiver unit is used to:

[0164] Acquire a fifth QoS parameter of the XR service, where the fifth QoS parameter includes a fifth 5QI;

[0165] In a case where the fourth 5QI and the fifth 5QI do not match, the third message is sent to the network device based on the fifth 5QI.

[0166] In a possible design, the PDU session establishment accept message also includes a fourth QoS parameter, where the fourth QoS parameter includes one or more of the following information: a fourth 5QI, a first tag value, or a third tag value; the first tag value is used to indicate support for processing of PDU Set in an uplink direction and / or a downlink direction, and the third tag value is used to indicate that the third QoS flow supports processing based on PDU Set;

[0167] When sending the third message to the network device, the transceiver unit is used to:

[0168] When the number of PDU Sets of the XR service received in a unit time is less than a first threshold, the third message is sent to the network device based on the fourth 5QI.

[0169] In one possible design, the third message includes one or more of the following third QoS parameters expected by the terminal device:

[0170] A third 5QI, or a third marking value;

[0171] The third 5QI is determined based on the fourth 5QI parameter, or the third QoS parameter is determined based on the fifth 5QI.

[0172] In one possible design, the QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device:

[0173] Sixth 5QI, or third marker value.

[0174] In one possible design, the third message is a PDU session modification request message, and / or the fourth message is a PDU session modification command message.

[0175] In a seventh aspect, the present application provides a communication device, which may be the communication device itself, or a module, chip or unit in the communication device. Exemplarily, the communication device may be a network device, such as an SMF. The communication device includes:

[0176] A transceiver unit, configured to receive a first message from a terminal device, where the first message is used to create a first quality of service flow QoS flow for an extended reality XR service request, where the first QoS flow supports processing based on a packet data unit set PDU Set;

[0177] The transceiver unit is used to send a second message to the terminal device, where the second message includes a first QoS parameter corresponding to the first QoS flow.

[0178] In a possible design, before receiving the first message from the terminal device, the transceiver unit is used to:

[0179] Receiving a PDU session establishment request from the terminal device;

[0180] Send a PDU session establishment accept message to the terminal device; the PDU session establishment accept message is used to determine whether the second QoS flow corresponding to the XR service supports PDU Set-based processing.

[0181] In one possible design, the PDU session establishment accept message includes first indication information and second indication information;

[0182] The first indication information indicates the second QoS flow;

[0183] The second indication information indicates whether the second QoS flow supports PDU Set-based processing.

[0184] In one possible design, the first message includes one or more of the following third QoS parameters expected by the terminal device:

[0185] a third PSDB, a third PSER, a third PHISI, or a first tag value;

[0186] The first flag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction.

[0187] In one possible design, the first QoS parameter includes one or more of the following QoS parameters configured by the network device:

[0188] A first PSDB, a first PSER, a first PHISI, or a first tag value.

[0189] In one possible design, the first message includes one or more of the following third QoS parameters expected by the terminal device:

[0190] A first tag value, a second tag value, or a first 5QI; the first tag value is used to indicate support for PDU Set processing in the uplink direction and / or downlink direction, the second tag value is used to indicate that the first QoS flow supports PDU Set-based processing, the parameters indicated by the first 5QI include a packet delay budget PDB and a packet error rate PER, and the first 5QI is the 5QI associated with the second QoS flow.

[0191] In one possible design, the first QoS parameter includes one or more of the following QoS parameters configured by the network device:

[0192] A first tag value, a second tag value, or a second 5QI.

[0193] In one possible design, the first message is a PDU session modification request message, and / or the second message is a PDU session modification command message.

[0194] In one possible design, the first message includes flow information of the XR service.

[0195] In an eighth aspect, the present application provides a communication device, which may be the communication device itself, or a module, chip or unit in the communication device. Exemplarily, the communication device may be a network device, such as an SMF. The communication device includes:

[0196] A transceiver unit, configured to receive a third message from a terminal device, wherein the third message is used to request modification of a fourth QoS parameter corresponding to a third quality of service flow QoS flow created for an extended reality XR service; wherein the third QoS flow supports processing based on a packet data unit set PDU Set;

[0197] The transceiver unit is used to send a fourth message to the terminal device, and the fourth message includes QoS parameter update information corresponding to the third QoS flow.

[0198] In a possible design, before receiving the third message from the terminal device, the transceiver unit is used to:

[0199] Receiving a PDU session establishment request from the terminal device;

[0200] A PDU session establishment acceptance message is sent to the terminal device, wherein the PDU session establishment acceptance message includes third indication information, and the third indication information indicates the third QoS flow.

[0201] In one possible design, the third message includes one or more of the following third QoS parameters expected by the terminal device:

[0202] A third PSDB, a third PSER, or a third PHISI.

[0203] In one possible design, the QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device:

[0204] A sixth PSDB, a sixth PSER, or a sixth PHISI.

[0205] In one possible design, the third message includes one or more of the following third QoS parameters expected by the terminal device:

[0206] Third 5QI, or third marking value.

[0207] In one possible design, the QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device:

[0208] Sixth 5QI, or third marker value.

[0209] In one possible design, the third message is a PDU session modification request message, and / or the fourth message is a PDU session modification command message.

[0210] In a ninth aspect, the present application provides a communication device, comprising a processor, wherein the processor is configured to execute a computer program so that the communication device executes any of the methods described in any of the first to fourth aspects.

[0211] In one possible design, the communication device may be a chip that implements the method of any one of the first to fourth aspects or a device including a chip.

[0212] In one possible design, the communication device further includes a transceiver, and the processor is coupled to the transceiver.

[0213] In a possible design, the communication device further includes a memory. The processor is coupled to the memory, a computer program is stored in the memory, and the processor is further used to call the computer program in the memory. Optionally, the processor and the memory may also be integrated together.

[0214] In the tenth aspect, the present application provides a communication device, which includes a processor and an interface circuit, the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement any method described in any one of the first to fourth aspects through logic circuits or execution code instructions.

[0215] In an eleventh aspect, the present application provides a computer-readable storage medium storing a computer program or instruction. When the computer program or instruction is executed by a computer, the method described in any one of the first to fourth aspects is implemented.

[0216] In a twelfth aspect, the present application provides a computer program product. When a computer reads and executes the computer program product, the computer executes any one of the methods described in any one of the first to fourth aspects.

[0217] In a thirteenth aspect, the present application provides a communication system, which includes a communication device for implementing any method described in the first aspect above, and a communication device for implementing any method described in the second aspect above.

[0218] The beneficial effects of the third to thirteenth aspects can refer to the beneficial effects of the first aspect and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0219] Figure 1 It is a schematic diagram of the architecture of the communication system used in this application;

[0220] Figure 2 A QoS model based on QoS flow provided for this application;

[0221] Figure 3 A schematic diagram of a process for establishing a QoS flow provided in this application;

[0222] Figure 4 is a schematic diagram of a bidirectional QoS flow provided in an embodiment of the present application;

[0223] Figure 5 It is a schematic diagram of an interaction process of the communication method provided in an embodiment of the present application;

[0224] Figure 6 is another interactive flow diagram of the communication method provided in an embodiment of the present application;

[0225] Figure 7 is a structural diagram of a communication device provided in an embodiment of the present application;

[0226] Figure 8 is a structural diagram of another communication device provided in an embodiment of the present application;

[0227] Fig. 9 It is a structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0228] The specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0229] The terms "first" and "second" and the like in the specification, claims and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

[0230] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0231] In the present application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0232] In order to better understand the embodiments of the present application, the system architecture involved in the embodiments of the present application is first introduced below:

[0233] See also Figure 1 , Figure 1 This is a schematic diagram of the architecture of the communication system used in this application. Figure 1As shown, the communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, the communication system 1000 may also include the Internet 300, which may also be called a data network (DN), and whose main function is to provide specific data services, such as operator services, Internet access or third-party services. The RAN 100 includes at least one RAN node (such as Figure 1 110a and 110b, collectively referred to as 110) and at least one terminal (such as Figure 1 RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment ( Figure 1 The terminal 120 is connected to the RAN node 110 in a wireless manner. The RAN node 110 is connected to the core network 200 in a wireless or wired manner. The core network device in the core network 200 and the RAN node 110 in the RAN 100 may be different physical devices, or may be the same physical device that integrates the core network logical function and the radio access network logical function.

[0234] RAN 100 may be a cellular system related to the third generation partnership project (3GPP), for example, a 4G, 5G mobile communication system, or a future evolution system (for example, a 6G mobile communication system). RAN 100 may also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloud radio access network, CRAN), or a wireless fidelity (wireless fidelity, WiFi) system. RAN 100 may also be a communication system that integrates two or more of the above systems.

[0235] The RAN node 110, which may also be sometimes referred to as an access network device, a RAN entity or an access node, constitutes a part of the communication system to help the terminal achieve wireless access. The multiple RAN nodes 110 in the communication system 1000 may be nodes of the same type or nodes of different types. In some scenarios, the roles of the RAN node 110 and the terminal 120 are relative, for example, Figure 1The network element 120i may be a helicopter or a drone, which may be configured as a mobile base station. For the terminals 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal. The RAN node 110 and the terminal 120 are sometimes referred to as communication devices, for example Figure 1 The base stations 110a and 110b may be understood as communication devices having base station functions, and the terminals 120a-120j may be understood as communication devices having terminal functions.

[0236] In one possible scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), 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 WiFi system. A RAN node may be a macro base station (e.g. Figure 1 110a in), micro base stations or indoor stations (such as Figure 1 110b in the description), a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The RAN node in the present application may also be a logical node, a logical module or software that can implement all or part of the functions of the RAN node.

[0237] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU here completes the functions of the radio resource control protocol and the packet data convergence layer protocol (PDCP) of the base station, and can also complete the function of the service data adaptation protocol (SDAP); the DU completes the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also complete the functions of part of the physical layer or all of the physical layer. For the specific description of the above-mentioned various protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The CU and DU can be set separately, or can also be included in the same network element, such as the baseband unit (BBU). The RU may be included in a radio frequency device or a radio frequency unit, for example, in a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0238] Optionally, the RAN node may also be expressed in different ways, such as access network equipment. Unless otherwise specified in this application, access network equipment is used for expression.

[0239] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, CU, CU-CP, CU-UP, DU and RU are described as examples in this application. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0240] The terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, mobile equipment (ME), etc. The terminal can be widely used in various scenarios, for example, device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a mechanical arm, a smart home device, etc. The embodiments of the present application do not limit the device form of the terminal.

[0241] The core network may include one or more functional entities (or core network elements, network elements, entities, etc.), such as policy control function (PCF), access and mobility management function (AMF), session management function (SMF), application function (AF), user plane function (UPF), etc.

[0242] The following is an introduction to the functions of each device:

[0243] The access and mobility management function (also referred to as access and mobility management equipment, access and mobility management function entity, access and mobility management function network element, mobile management equipment, access management equipment, mobile management network element, mobile management entity or AMF, etc.) is a type of core network equipment. The device can be used to manage the access control and mobility of the user equipment. In practical applications, it includes the access and mobility management function in the mobility management entity (MME) in the network framework of long term evolution (LTE), and adds the access management function, which can be responsible for the registration, mobility management, tracking area update process, reachability detection, selection of session management network element, mobile state transition management, etc. of the user equipment. For example, in 5G, the access and mobility management network element can be an AMF network element. In future communications, such as 6G, the access and mobility management network element can still be an AMF network element, or have other names, which are not limited in this application. When the access and mobility management network element is an AMF network element, the AMF can provide Namf services.

[0244] The user plane function (also called user plane device or UPF, etc.) is a type of core network device. This device can be responsible for forwarding and receiving user data in the user equipment. It can receive user data from the data network and transmit it to the user equipment through the access network element; the user plane function network element can also receive user data from the user equipment through the access network element and forward it to the data network. The transmission resources and scheduling functions that provide services to the user equipment in the user plane function network element are managed and controlled by the session management function network element.

[0245] The session management function (also known as session management device or SMF, etc.) is a type of core network device. The device can be used to be responsible for the session management of the user equipment (including session establishment, modification and release), selection and reselection of user plane function network elements, allocation of Internet Protocol (IP) addresses of the user equipment, quality of service (QoS) control, etc. For example, in 5G, the session management network element may be a session management function (SMF) network element. In future communication systems, such as 6G, the session management network element may still be an SMF network element, or have other names, which are not limited in this application. When the session management network element is an SMF network element, the SMF can provide Nsmf services.

[0246] The policy control function (also known as policy control network element, policy control function network element, policy control equipment, policy control function entity, PCF, etc.) is mainly responsible for providing a unified policy framework for network behavior management, providing policy rules for control plane functions, and obtaining registration information related to policy decisions.

[0247] The application function (also known as application function network element, application function device, application function entity, AF, etc.) can be either a third-party application control platform or a device deployed by an operator. Its main functions include providing application-related information and providing services for multiple application servers.

[0248] It should be noted that in actual deployment, different functions or network elements can be co-located. For example, the access and mobility management network element can be co-located with the session management network element; the session management network element can be co-located with the user plane network element. When two network elements are co-located, the interaction between the two network elements provided in the embodiment of the present application becomes the internal operation of the co-located network element or can be omitted.

[0249] It should be noted that the above functional entity is only a name, and the name itself does not limit the entity. For example, the session management function may also be replaced by "session management function entity" or other names. Moreover, the session management function entity may also correspond to an entity including other functions in addition to the session management function. The user plane function may also be replaced by "user plane function entity" or other names, and the user plane function entity may also correspond to an entity including other functions in addition to the user plane function. A unified explanation is given here, and no further description is given below.

[0250] It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of the present application are merely examples, and other names may be used in specific implementations, and the embodiments of the present application do not impose any specific limitations on this.

[0251] In this application, "sending information to...(terminal)" can be understood as the destination of the information being the terminal. It can include sending information to the terminal directly or indirectly. "Receiving information from...(terminal)" can be understood as the source of the information being the terminal, which can include receiving information from the terminal directly or indirectly. The information may be processed as necessary between the source and destination of the information, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.

[0252] It should be understood that the terminal device in the embodiment of the present application can be any of the above-mentioned devices or chips, which are not specifically limited here. Whether as a device or as a chip, the terminal device can be manufactured, sold or used as an independent product. In this embodiment and subsequent embodiments, only the terminal device is used as an example for introduction.

[0253] It should be understood that the device for realizing the function of the network device in the embodiment of the present application may be the network device itself, or a device that can support the network device to realize the function, such as a chip system or a combination device or component that can realize the function of the network device, and the device can be installed in the network device. In the embodiment of the present application, the chip system can be composed of chips, or it can include chips and other discrete devices. In this embodiment and subsequent embodiments, only the network device is used as an example for introduction.

[0254] Exemplarily, the network device in the embodiment of the present application may specifically be an SMF.

[0255] The following is an explanation of the relevant technical features involved in the embodiments of the present application. It should be noted that these explanations are intended to make the embodiments of the present application easier to understand and should not be regarded as limiting the scope of protection claimed by the present application.

[0256] 1. QoS Model

[0257] At present, in order to ensure the end-to-end service quality of the service in the 5G communication system, a QoS model based on QoSflow is proposed. Figure 2 As shown, the terminal device can establish at least one PDU session (PDU session) between the access network device and the UPF on the core network side. For each PDU session, at least one QoS flow can be established between the terminal device, the access network device, and the UPF network element. Each QoS flow is identified by a QoS flow identifier (QoS flow identifier, QFI), and the QFI uniquely identifies a QoS flow in the session. In addition, each QoS flow corresponds to a data radio bearer (data radio bearer, DRB), and a DRB can correspond to one or more QoS flows.

[0258] The QoS model supports QoS flows that guarantee bit rate (GBR QoS flows) and QoS flows that do not guarantee bit rate (non-GBR QoS flows). Data packets entering the same QoS flow receive the same transmission processing (such as scheduling, admission threshold, etc.). Whether a QoS flow is a GBR QoS flow or a Non-GBR QoS flow is determined by the corresponding QoS profile.

[0259] For example, see Figure 3 , Figure 3 It is a flowchart of establishing a QoS flow. Figure 3 As shown in the figure, the interaction process between network elements or devices includes:

[0260] Step 301, the SMF network element instructs the terminal device, access network device, and UPF network element to establish a QoS flow according to the local policy or the policy and charging control (PCC) rules sent by the PCF network element. The specific establishment process is divided into three stages:

[0261] Step 301A, the SMF network element sends service data flow (SDF) information to the UPF network element, where the SDF information includes a packet detection rule;

[0262] Step 301B, the SMF network element sends the QoS file of QoSflow to the access network device through the AMF network element;

[0263] Step 301C, the SMF network element sends the QoS rule (QoSrule) to the terminal device through the AMF network element and / or the access network device, which includes the packet filter information (packet filter). It should be noted that the QoS file and the packet filter are generated by the SMF according to the local policy or PCC rule.

[0264] Step 302: Establish QoS flow between terminal equipment, access network equipment, and UPF network element. The access network equipment can establish the wireless data bearer (DRB) of the air interface according to the QoS file and store the binding relationship between the QoS flow and the DBR. The specific establishment process is divided into three stages:

[0265] 302A, UPF performs QoS control of downlink data packets and QoS verification of uplink data packets according to the data packet detection rules included in the SDF information;

[0266] 302B. The access network device executes DRB establishment according to the QoS file, and establishes a mapping relationship between DRB and QoS flow;

[0267] 302C. The terminal device performs QoS control of the uplink data packet according to the QoS rule.

[0268] When data packets are transmitted between terminal devices, access network devices, and UPF network elements:

[0269] In the downstream direction, when the UPF network element receives a downstream data packet, it detects the data packet according to the SDF information sent by the SMF network element, finds the matching QoS flow according to the data packet detection rules, and carries the service quality flow identifier (QoS flow identifier, QFI) information used to identify the QoS flow in the packet header of the downstream data packet. When the access network device receives a downstream data packet, it confirms the available QoS flow by parsing the QFI in the packet header, and places the downstream data packet on the corresponding DRB for transmission according to the binding relationship between the stored QoS flow and DRB.

[0270] In the uplink direction, when the terminal device needs to send an uplink data packet, it can determine the QoS flow according to the QoS rules, carry the QFI in the packet header of the uplink data packet, and then, based on the binding relationship between the QoS flow and the DBR, place the uplink data packet on the corresponding DRB for transmission. When the access network device receives the uplink data packet, based on the QFI in the packet header, the packet header of the uplink data packet forwarded to the UPF network element carries the QFI. When the UPF network element receives the uplink data packet sent by the access network device, it verifies whether the uplink data packet is transmitted using the correct QoS flow.

[0271] Among them, due to the difference in QoS files generated by SMF, the established QoS flow can include two types:

[0272] Type one is: guaranteed bit rate (GBR) QoS flow. In this case, the QoS file may include a 5G QoS identifier (5G QoS identifier, 5QI) for identifying QoS attribute information, allocation and retention priority (ARP), guaranteed flow bitrate (GFBR), and maximum bit rate (MBR). Optionally, the QoS file may also include notification control information. When the QoS file includes notification control information, the GBR QoS flow is a GBR QoS flow that requires notification control, otherwise it is a GBR QoS flow that does not require notification control. Among them, for the GBR QoS flow that requires notification control, when the access network device detects that the corresponding QoS flow resources cannot be met, the access network device notifies the session management function (SMF) network element of the event. Further, the SMF network element can initiate a QoS flow deletion or modification process. For example, when transmitting a data packet on the DRB corresponding to a GBR QoS flow, if the access network device detects that the service quality requirements of the GBR QoS flow cannot be met and the GBR QoS flow is configured to require notification control, then the access network device can notify the SMF network element through the AMF network element that the service quality requirements of the GBR QoS flow cannot be met, so that the SMF network element can modify or delete the GBR QoS flow according to the local policy, or the SMF network element instructs the PCF network element to modify or delete the GBR QoS flow. In one example, when the bit rate of the transmitted data packet does not reach the expected bit rate specified by the GFBR, it can be considered that the service quality requirements of the GBR QoS flow cannot be met. In another example, when the transmission delay (or packet loss rate, etc.) when transmitting the data packet does not meet the transmission delay (or packet loss rate, etc.) included in the 5QI, it can also be considered that the service quality requirements of the GBR QoS flow cannot be met.

[0273] Type 2 is: non-guaranteed bit rate (non-GBR) QoS flow. In this case, the QoS file may include 5QI, ARP, etc.

[0274] 2. PDU Session

[0275] A PDU session is a connection between a terminal device and a data network (DN), which is used to provide a PDU connection service.

[0276] 3.5QI

[0277] 5QI is a scalar used to index the corresponding 5G QoS features. 5QI mainly includes one or more of the following parameters: resource type, packet delay budget (PDB), packet error rate (PER), averaging window (AW), priority level (PL) and maximum data burst volume (MDBV). Exemplarily, as shown in Table 1, when the 5QI value is 1, it means that the resource type is a guaranteed bitrate (GBR) type, the priority is 20, the packet delay budget is 100ms, the packet error rate is 10-2, the maximum data burst volume is a parameter to be defined, and the average time window is 2000ms. In other words, a 5QI value of 1 represents a set of parameters specified in the network protocol. It should be understood that Table 1 only shows the standard QoS parameters corresponding to a 5QI value. In practice, there may be different standard QoS parameters corresponding to different 5QI values, which will not be repeated in this application.

[0278] Table 1

[0279] 5QI Value Resource Type Priority Packet delay budget Packet Error Rate Maximum data burst Averaging time window Service Examples 1 GBR 20 100ms 10-2 N / A 2000ms Language Services

[0280] 4. Quintuple

[0281] The quintuple includes the source IP address, destination IP address, IP protocol type, source port number, and destination port number.

[0282] 5. PDU Set

[0283] A collection of multiple data packets in the transport layer corresponds to the minimum granularity of data processing in the application layer, such as a collection of frames. If the video is encoded in slices, PDU Set refers to a collection of slice data packets. In some application scenarios, the application layer can only correctly parse the corresponding data unit if it correctly receives all the data packets in a PDU Set. In other application scenarios, the application layer can parse the corresponding data unit if it correctly receives a certain proportion of the data packets in the PDU Set.

[0284] 6. PDB and PER

[0285] PDB defines the upper limit of the transmission delay that a data packet may experience between the terminal device and the N6 interface of the UPF. PER defines an upper limit, that is, the upper limit of the ratio of data packets that have been processed by the link layer (such as the RLC layer) of the sender but have not been submitted to the upper layer (such as the PDCP layer) by the corresponding receiver. The packet error rate can also be called the packet error rate, and the two can be used interchangeably.

[0286] 7. PSDB and PSER

[0287] PSDB defines the upper limit of the transmission delay that a data packet set (PDU Set) may experience between the terminal device and the N6 interface of the UPF. For the uplink, the delay refers to the delay from the first data packet in the PDU Set being sent from the terminal device side to the last data packet in the PDU Set arriving at the UPF N6 interface; for the downlink, it refers to the delay from the first data packet from the UPF N6 interface to the last data packet arriving at the terminal device. PSER defines an upper limit, that is, the upper limit of the ratio of the data packet set that has been processed by the link layer (such as the RLC layer) of the sender but has not been submitted to the upper layer (such as the PDCP layer) by the corresponding receiver.

[0288] 8. PDU Set integrated handling information (PHISI)

[0289] The PHISI indicates whether a packet set requires all packets to be received.

[0290] 9. Processing of PDU Set for XR Services

[0291] Support for PDU Set-based processing includes, for example, support for identifying packet data unit sets and support for packet data unit-based integrity processing, wherein support for packet data unit-based integrity processing includes support for packet data unit-based integrity scheduling and packet loss processing.

[0292] 10. Streaming information of XR services

[0293] The flow information of the XR service refers to one or more attributes of the XR service, such as the IP address, port number, MAC address, etc. Typically, the flow information can be identified by an IP quintuple.

[0294] 11. Packet filter

[0295] Packet filters contain rules such as IP addresses, port numbers, MAC addresses, etc. Typically, packet filters can be in the form of IP quintuples.

[0296] 12. QoS profile

[0297] The traditional QoS profile contains information such as 5QI, GFBR, and MFBR to describe the characteristics or requirements of the QoS flow. The QoS profile that supports the PDUSet-based QoS flow also contains information such as PSDB and PSER.

[0298] 13. QoS rule

[0299] QoS rule contains packet filter and associated QFI information. Packet filter is used to match data packets, and the QoS flow associated with the matching packet filter is the QoS flow that the data packet will enter.

[0300] 14. Bidirectional QoS flow

[0301] If a QoS flow can have both uplink and downlink service data, then the QoS flow is a bidirectional QoS flow. Figure 4 , Figure 4 Schematic diagram of a bidirectional QoS flow provided by an embodiment of the present application. Figure 4 As shown, the service data flow of application 1 is downstream, and the service data flow of application 2 is upstream, wherein the service data flow of application 1 and service data 2 can be transmitted through the same QFI (e.g. Figure 4 The QoS flow corresponding to QFI1) in is transmitted, and this QoS flow is a bidirectional QoS flow.

[0302] The communication method and communication device provided by this application are described in detail below:

[0303] See also Figure 5 , Figure 5 Schematic diagram of an interactive process of the communication method provided in the embodiment of the present application. Figure 5As shown, the communication method includes the following steps S500 to S503. Figure 5 The method shown may be performed by a terminal device and a network device, or, Figure 5 The execution subject of the method shown may also be a chip in a terminal device and a chip in a network device. For the convenience of description, Figure 5 The following mainly uses terminal devices and network devices as the execution subjects of the method as examples. It should be noted that: Figure 5 is a schematic flow chart of a method embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are only examples, and the present application embodiment may also perform other operations or Figure 5 In addition, Figure 5 The steps in Figure 5 are executed in a different order than those presented, and may not be executed in the order Figure 5 All operations in . Among them:

[0304] S500: The terminal device sends a PDU session establishment request to the network device. Correspondingly, the network device receives the PDU session establishment request from the terminal device.

[0305] Generally speaking, the terminal device may carry the capability information of the terminal device in the PDU session establishment request sent. For example, the capability information of the terminal device may indicate that the terminal device supports PDU Set-based processing.

[0306] Therefore, the network device can create a second QoS flow corresponding to the XR service during the PDU session establishment process according to the capability information carried in the received PDU session establishment request. According to the network policy or configuration, the second QoS flow does not support PDU Set-based processing. Exemplarily, the XR service can be a video service.

[0307] Optionally, the network device may also create corresponding QoS flows for other services (eg, voice services), which is not limited in this application.

[0308] Understandably, the specific steps for creating a QoS flow during the PDU session establishment process can be found in Figure 3 The process shown in this application will not be repeated here.

[0309] S501: The network device sends a PDU session establishment acceptance message to the terminal device. Correspondingly, the terminal device receives the PDU session establishment acceptance message from the network device.

[0310] In some feasible implementations, the PDU session establishment acceptance message may include first indication information and second indication information, the first indication information indicating the second QoS flow, and the second indication information indicating whether the second QoS flow supports PDU Set-based processing. Optionally, the PDU session establishment acceptance message may also include a 5QI associated with the second QoS flow (hereinafter described as the first 5QI for ease of description). The parameters indicated by the first 5QI may include information such as the PDB and PER of the second QoS flow.

[0311] Optionally, after the network device completes the creation of the second QoS flow, the network device may also send the QoS file of the second QoS flow to the access network device ( Figure 5 (not shown), the QoS file is used to create a data radio bearer for a second QoS flow. Specifically, the QoS file may include parameters such as 5QI, which are not limited here.

[0312] S502: The terminal device sends a first message to the network device. Correspondingly, the network device receives the first message from the terminal device.

[0313] Among them, the first message is used to create a first QoS flow for the XR service request, and the first QoS flow supports PDU Set-based processing. Generally speaking, the terminal device can determine whether the second QoS flow corresponding to the XR service supports PDU Set-based processing according to the PDU session establishment acceptance message. Exemplarily, the terminal device can determine the second QoS flow corresponding to the XR service according to the first indication information carried in the PDU session establishment acceptance message, and determine whether the second QoS flow corresponding to the XR service supports PDU Set-based processing according to the second indication information. That is, the first indication information and the second indication information carried in the PDU session establishment acceptance message, wherein the first indication information indicates the second QoS flow (this is because the PDU session establishment process may not only create the second QoS flow corresponding to the XR service, but also may create QoS flows for other services, that is, multiple QoS flows may be created during the PDU session establishment process, therefore, the first indication information is required to indicate the second QoS flow corresponding to the XR service), and the second indication information indicates whether the second QoS flow supports PDU Set-based processing. In an embodiment of the present application, the terminal device can send a first message to the network device when the second QoS flow does not support PDU Set-based processing. Optionally, when the second QoS flow supports PDUSet-based processing, if the QoS parameters corresponding to the second QoS flow do not meet the QoS requirements, the terminal device may send a third message to the network device, where the third message is used to request modification of the QoS parameters corresponding to the QoS flow (for example, the second QoS flow) created for the XR service.

[0314] Exemplarily, the first indication information includes packet filter information and an identifier of an associated QoS flow, and the second QoS flow may be determined according to the packet filter information and the identifier of the associated QoS flow.

[0315] As another example, packet filter information is included in a QoS rule of a QoS rule element, and the component type of the packet filter may be an IP address, a port number, a MAC address, etc. A packet filter may include a five-tuple of information or a three-tuple of information, and a five-tuple of information includes a source IP address, a destination IP address, an IP protocol type, a source port number, and a destination port number. The terminal device obtains the flow information of the XR service from the inside. Optionally, if the flow information is identified by the five-tuple information, and at least one five-tuple information indicated by the first indication information matches the five-tuple information of the obtained XR service, the QoS flow corresponding to the matching five-tuple information can be determined as the second QoS flow. Here, the match between a five-tuple information and the five-tuple information of the XR service can be understood as each group of information being exactly the same or a hash match.

[0316] Exemplarily, the length of the second indication information can be 1 bit. When the value of this 1 bit is 1, it indicates that the second QoS flow supports PDU Set-based processing. When the value of this 1 bit is 0, it indicates that the second QoS flow does not support PDU Set-based processing. If the second indication information is not carried, it can be considered that PDU Set-based processing is not supported.

[0317] As another example, the second indication information may be QoS parameter information associated with the second QoS flow. If the QoS parameter information includes PDU Set information such as PSDB and PSER, it indicates that the second QoS flow supports PDU Set-based processing; if the QoS parameter information does not include PSDB, PSER, etc., it indicates that the second QoS flow does not support PDU Set-based processing.

[0318] In a possible implementation method ①, the terminal device may also obtain the first information of the XR service, the first information including the second QoS parameter of the XR service, and the second QoS parameter includes one or more of the following information: a second PSDB, a second PSER, a second PHISI, or a first tag value. Therefore, the terminal device may send a first message to the network device according to the first information. Exemplarily, the first message may include one or more of the following third QoS parameters expected by the terminal device: a third PSDB, a third PSER, a third PHISI, or a first tag value. Among them, the first tag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction. It can be understood that the terminal device sends the expected first tag value to the network device, so the network device can establish a QoSflow supporting the processing of the PDU Set in the uplink direction and / or the downlink direction according to the first tag value. The third QoS parameter can be determined based on the second QoS parameter (or it can be understood that the terminal device can use the second QoS parameter as the third QoS parameter expected by the terminal device). The third QoS parameter carried by the first message can be understood as the QoS parameter expected by the terminal device. In a specific implementation, the above-mentioned terminal device obtains the first information of the XR service, which can be understood as: the application inside the terminal device for providing the XR service can open QoS information to the terminal device. Therefore, the application can actively report the first information corresponding to the XR service to the upper layer (such as the application layer) of the terminal device, or the terminal device can periodically read the first information of the XR service provided by the application from the application inside the terminal device. This application does not impose any restrictions on this.

[0319] For example, assume that the second PSDB in the second QoS parameter carried in the first information of the XR service obtained from the application is 100ms, and the second PSER is 10 -2 , then the terminal device can use 100ms and 10 -2 The third PSDB and third PSER expected by the terminal device are respectively sent to the network device.

[0320] In a possible implementation method ②, the terminal device may also send a first message to the network device when determining the XR service according to the traffic characteristics. Here, the traffic characteristics can be understood as the characteristics presented in terms of packet size, number of packets, periodicity, etc. Generally speaking, the burst type of traffic of the XR service appears in the form of burst. In this implementation method ②, the terminal device can reuse the first 5QI as the third QoS parameter expected by the terminal device. Optionally, the third QoS parameter may also include one or more parameters such as the first tag value or the second tag value. Optionally, the terminal device may determine the first tag value by the source of the traffic (or service data flow) and determine the second tag value by the traffic characteristics. The first tag value is used to indicate the support of PDU Set processing in the uplink direction and / or downlink direction, and the second tag value is used to indicate whether the first QoS flow supports PDU Set-based processing. Here, the second tag value is mainly used to indicate that the first QoS flow supports PDU Set-based processing. When the network device receives a first message carrying one or more information such as the first tag value, the second tag value, or the first 5QI, the network device can determine, based on the second tag value, that the first QoS flow to be established must support PDU Set-based processing, and then the network device can use the PDB and PER indicated by the first 5QI as the PSDB and PSER expected by the terminal device, respectively, to establish the first QoS flow.

[0321] Exemplarily, the length of the first tag value may be 2 bits, wherein when the value of the 2 bits is 01, it indicates that the XR service is a downlink service, when the value of the 2 bits is 10, it indicates that the XR service is an uplink service, and when the value of the 2 bits is 11, it indicates that the XR service can be either an uplink service or a downlink service. Another exemplary embodiment of the first tag value may also be a 2-bit bitmap, wherein each bit corresponds to a service direction, and when the value of the corresponding bit is "1", it indicates that the XR service is the corresponding service direction. For example, assuming that the service direction corresponding to the high bit is the uplink service, and the service direction corresponding to the low bit is the downlink service, when the bitmap value is 01, it indicates that the XR service is a downlink service, when the value of the 2 bits is 10, it indicates that the XR service is an uplink service, and when the value of the 2 bits is 11, it indicates that the XR service can be either an uplink service or a downlink service.

[0322] Exemplarily, the length of the second tag value can be 1 bit. When the value of the 1 bit is 1, it indicates that the first QoS flow supports PDU Set-based processing. When the value of the 1 bit is 0, it indicates that the first QoS flow does not support PDU Set-based processing. If the second tag value is not carried, it indicates that the first QoS flow does not support PDU Set-based processing.

[0323] Optionally, in addition to including the third QoS parameter expected by the terminal device, the first message may also include flow information of the XR service. It can be understood that the flow information is used to identify the XR service flow, and specifically may be in the form of a packet filter.

[0324] It is understandable that the first message involved in the present application may specifically be a PDU session modification request message, etc., and the present application does not impose any limitation on this.

[0325] S503: The network device sends a second message to the terminal device. Correspondingly, the terminal device receives the second message from the network device.

[0326] Generally speaking, the network device can create a first QoS flow for the XR service according to the first message, and send the first QoS parameter corresponding to the first QoS flow to the terminal device. The first QoS parameter corresponding to the first QoS flow can be carried in the second message. Here, the first QoS parameter is the QoS parameter actually configured by the network device.

[0327] It is understandable that when the above implementation method ① is adopted, the first QoS parameter may include one or more of the first PSDB, the first PSER, the first PHISI, or the first tag value. When the above implementation method ② is adopted, the first QoS parameter may include one or more of the first tag value, the second tag value, or the second 5QI. After the terminal device receives the first tag value sent by the network device, the terminal device can determine that the QoSflow established by the network device supports the processing of the PDU Set in the uplink direction and / or the downlink direction according to the first tag value.

[0328] It is understandable that the second message involved in the present application may specifically be a PDU session modification command message, etc., and the present application does not impose any limitation on this.

[0329] In an embodiment of the present application, after the PDU session is established, the terminal device can actively apply for / request the creation of a QoS flow for the XR service, wherein the terminal device can define and report the QoS parameters of the desired QoS flow, such as one or more of the desired PSDB, PSER, PHISI, etc. Optionally, the terminal device can also report the service direction of the XR service that is desired to be created. After the network device completes the creation of the QoS flow for the XR service based on the request of the terminal device, the network device can send to the terminal device the QoS parameters configured when the network device is actually created, such as the actually configured PSDB, PSER, PHISI or service direction, etc.

[0330] See also Figure 6 , Figure 6 is another interactive flow diagram of the communication method provided in the embodiment of the present application. Figure 6 As shown, the communication method includes the following steps S600 to S603. Figure 6 The method shown may be performed by a terminal device and a network device, or, Figure 6 The execution subject of the method shown may also be a chip in a terminal device and a chip in a network device. For the convenience of description, Figure 6 The following mainly uses terminal devices and network devices as the execution subjects of the method as examples. It should be noted that: Figure 6 is a schematic flow chart of a method embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are only examples, and the present application embodiment may also perform other operations or Figure 6 In addition, Figure 6 The steps in Figure 6 are executed in a different order than those presented, and may not be executed in the order Figure 6 All operations in . Among them:

[0331] S600: The terminal device sends a PDU session establishment request to the network device. Correspondingly, the network device receives the PDU session establishment request from the terminal device.

[0332] Generally speaking, the terminal device may carry the capability information of the terminal device in the PDU session establishment request sent. For example, the capability information of the terminal device may indicate that the terminal device supports PDU Set-based processing.

[0333] Therefore, the network device can create a third QoS flow corresponding to the XR service during the PDU session establishment process based on the capability information carried in the received PDU session establishment request. According to the network policy or configuration, the third QoS flow supports PDU Set-based processing.

[0334] Optionally, the network device may also create corresponding QoS flows for other services (eg, voice services), which is not limited in this application.

[0335] Understandably, the specific steps for creating a QoS flow during the PDU session establishment process can be found in Figure 3 The process shown in this application will not be repeated here.

[0336] S601: The network device sends a PDU session establishment acceptance message to the terminal device. Correspondingly, the terminal device receives the PDU session establishment acceptance message from the network device.

[0337] In some feasible implementation manners, the PDU session establishment accept message may include third indication information, where the third indication information indicates a third QoS flow.

[0338] Optionally, in a case 1, the PDU session establishment accept message also includes a fourth QoS parameter, and the fourth QoS parameter includes one or more of the following information: a fourth PDU Set delay budget PSDB, a fourth PDU Set error rate PSER, a fourth PDU Set integrated processing information PHISI, or a first tag value. The first tag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction.

[0339] Optionally, in case 2, the PDU session establishment acceptance message may also include a 5QI associated with the third QoS flow (hereinafter described as the fourth 5QI for the convenience of description). The parameters indicated by the fourth 5QI may include information such as the PDB and PER of the third QoS flow. Optionally, in addition to the fourth 5QI, the PDU session establishment acceptance message may also include a first tag value and / or a third tag value. The third tag value is used to indicate that the third QoS flow supports PDU Set-based processing.

[0340] Optionally, the network device may also send a QoS file of a third QoS flow to the access network device ( Figure 6 (not shown), the QoS file is used to create a data radio bearer for a second QoS flow. Specifically, the QoS file may include parameters such as PSDB and PSER, which are not limited here.

[0341] S602: The terminal device sends a third message to the network device. Correspondingly, the network device receives the third message from the terminal device.

[0342] The third message is used to request modification of a fourth QoS parameter corresponding to a third QoS flow created for the XR service.

[0343] In one implementation (1-1), if the content included in the PDU session establishment acceptance message is the above situation 1, then sending a third message to the network device can be understood as: the terminal device obtains the fifth QoS parameter of the XR service, and the fifth QoS parameter includes one or more of the following information: the fifth PSDB, the fifth PSER, or the fifth PHISI. In the case where the fourth QoS parameter and the fifth QoS parameter do not match, the terminal device sends a third message to the network device based on the fifth QoS parameter. Here, the mismatch between the fourth QoS parameter and the fifth QoS parameter can be understood as one or more parameters are different, for example, such as PSDB is different. It can be understood that the first tag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction. Optionally, sending a third message to the network device based on the fifth QoS parameter can be understood as determining the third QoS parameter expected by the terminal device carried in the third message based on the fifth QoS parameter. In this implementation (1-1), the third QoS parameter includes one or more of the third PSDB, the third PSER, or the third PHISI. Exemplarily, the terminal device may use the fifth PSDB, the fifth PSER, or the fifth PHISI carried in the five QoS parameters as the third PSDB, the third PSER, or the third PHISI carried in the third QoS parameter, respectively. In specific implementation, the above-mentioned terminal device obtains the fifth QoS parameter of the XR service, which can be understood as: the application inside the terminal device for providing the XR service can open QoS information to the terminal device, so the application can actively report the fifth QoS parameter corresponding to the XR service to the upper layer (such as the application layer) of the terminal device, or the terminal device can periodically read the fifth QoS parameter of the XR service provided by the application from the application inside the terminal device, and this application does not limit this.

[0344] In one implementation (1-2), if the content included in the PDU session establishment acceptance message is the above-mentioned situation 1, then sending a third message to the network device can also be understood as: when the number of PDU Sets of XR services received within a unit time is less than the first threshold, a third message is sent to the network device based on the fourth QoS parameter. Among them, the number of PDU Sets of XR services received within a unit time is less than the first threshold, which means that the user experience of the XR service is poor. That is to say, this implementation (1-2) is mainly to apply / request the network device to modify the fourth QoS parameter of the XR service through a third message when the terminal device perceives that the effect of the XR service is not good, such as video freezes. Among them, sending a third message to the network device based on the fourth QoS parameter can be understood as determining the third QoS parameter expected by the terminal device carried in the third message based on the fourth QoS parameter. In this implementation (1-2), the third QoS parameter includes one or more of a third PSDB, a third PSER, or a third PHISI. Exemplarily, the terminal device may adjust one or more of the fourth PSDB, the fourth PSER, or the fourth PHISI included in the fourth QoS parameter, and use the corresponding adjusted parameters as the third PSDB, the third PSER, or the third PHISI carried in the third QoS parameter. For example, assuming that the PSDB carried by the fourth QoS parameter is 100ms, and based on 100ms, the adjustment can obtain the value of the PSDB carried in the third QoS parameter after the adjustment, such as 90ms as the PSDB that needs to be carried in the third QoS parameter. For another example, assuming that the PSER carried by the fourth QoS parameter is 10 -2 , with 10 -2 The PSER value carried in the third QoS parameter after adjustment can be obtained, for example, 10 -3 The PSER needs to be carried in the third QoS parameter.

[0345] In one implementation (2-1), if the content included in the PDU session establishment acceptance message is the above-mentioned situation 2, then sending a third message to the network device can be understood as: the terminal device obtains the fifth QoS parameter of the XR service, and the fifth QoS parameter includes the fifth 5QI. In the case where the fourth 5QI and the fifth 5QI do not match, a third message is sent to the network device based on the fifth 5QI. Here, the mismatch between the fourth 5QI and the fifth 5QI can be understood as the PDB or PER indicated by the fourth 5QI is different from the PDB or PER indicated by the fifth 5QI. For example, the PDB indicated by the fourth 5QI is 100ms, while the PDB indicated by the fifth 5QI is 50ms. It can be understood that the first tag value is used to indicate support for the processing of the PDU Set in the uplink direction and / or the downlink direction, and the third tag value is used to indicate that the third QoS flow supports processing based on the PDU Set. Optionally, sending a third message to the network device based on the fifth 5QI here can be understood as determining the third QoS parameter expected by the terminal device carried in the third message based on the fifth 5QI. In this implementation (2-1), the third QoS parameter includes one or more of the third 5QI or the third tag value. Exemplarily, the terminal device may use the fifth 5QI carried in the five QoS parameters as the third 5QI carried in the third QoS parameter. In specific implementation, the above-mentioned terminal device obtains the fifth QoS parameter of the XR service, which can be understood as: the application inside the terminal device for providing XR services can open QoS information to the terminal device, so the application can actively report the fifth QoS parameter corresponding to the XR service to the upper layer of the terminal device (such as the application layer), or the terminal device can periodically read the fifth QoS parameter of the XR service provided by the application from the application inside the terminal device, and this application does not impose any restrictions on this.

[0346] In one implementation (2-2), if the content included in the PDU session establishment acceptance message is the above situation 2, then sending a third message to the network device can also be understood as: when the number of PDU Sets of XR services received in a unit time is less than the first threshold, a third message is sent to the network device based on the fourth 5QI. Among them, the number of PDU Sets of XR services received in a unit time is less than the first threshold, which means that the user experience of the XR service is poor. That is to say, this implementation (2-2) is mainly to apply / request the network device to modify the fourth QoS parameter of the XR service through a third message when the terminal device perceives that the effect of the XR service is not good, such as when the video is stuck. Among them, sending a third message to the network device based on the fourth QoS parameter can be understood as determining the third QoS parameter expected by the terminal device carried in the third message based on the fourth QoS parameter. In this implementation (2-2), the third QoS parameter includes one or more of the third 5QI or the third tag value. Exemplarily, the terminal device can adjust the fourth 5QI included in the fourth QoS parameter, and use the corresponding adjusted parameter as the third 5QI carried in the third QoS parameter. For example, if the PDB indicated by the fourth 5QI is 100ms, an adjustment can be made based on 100ms to obtain the value of the PDB carried in the adjusted third QoS parameter. For example, 90ms is the PDB that needs to be carried in the third QoS parameter, and then the third 5QI is determined based on the mapping relationship between 5QI and PDB.

[0347] S603: The network device sends a fourth message to the terminal device. Correspondingly, the terminal device receives the fourth message from the network device.

[0348] Among them, the fourth message includes QoS parameter update information corresponding to the third QoS flow. Generally speaking, the network device can modify / reconfigure the fourth QoS parameter corresponding to the third QoS flow created for the XR service according to the third message, and send the modified QoS parameter corresponding to the third QoS flow (for the convenience of distinction, it is subsequently described as the sixth QoS parameter) to the terminal device. Among them, the sixth QoS parameter can be carried in the fourth message, that is, the QoS parameter reconfigured by the network device is carried in the fourth message.

[0349] It is understandable that when the above implementations (1-1) and (1-2) are adopted, the sixth QoS parameter may include one or more of the sixth PSDB, the sixth PSER, or the sixth PHISI, etc. When the above implementations (2-1) and (2-2) are adopted, the sixth QoS parameter may include one or more of the sixth 5QI, or the third tag value, etc.

[0350] It is understandable that the fourth message involved in the present application may specifically be a PDU session modification command message, etc., and the present application does not impose any limitation on this.

[0351] In an embodiment of the present application, after the PDU session is established, the terminal device may actively apply for / request to modify the QoS parameters corresponding to the QoS flow established for the XR service during the PDU session establishment process, wherein the terminal device may define and report the desired QoS parameters of the QoS flow, such as one or more of the desired PSDB, PSER, PHISI (or the desired 5QI), etc. After the network device completes the modification of the QoS parameters corresponding to the QoS flow of the XR service based on the request of the terminal device, the network device may send the QoS parameters reconfigured by the network device to the terminal device, such as the reconfigured PSDB, PSER, PHISI (or the reconfigured 5QI), etc.

[0352] It should be noted that the above Figure 5 Steps S502 and S503 in the corresponding embodiment can be used as an embodiment alone, or can also be used together with Figure 6 One or more steps in the illustrated embodiments are combined to form a new embodiment. For example, after executing step S502 and step S503, if the terminal device needs to modify the XR QoS parameters corresponding to the QoS flow established in S502-S503, the terminal device can continue to execute steps S602-S603 to modify the corresponding XR QoS parameters. It should be noted that when steps S502, S503, S602 and S603 are combined to form a new embodiment, the third QoS flow in S602 and S603 should be replaced with the first QoS flow in S502 and S503, and accordingly, the parameters / information related to the third QoS flow should also be replaced with the parameters / information related to the first QoS flow.

[0353] The following will be combined Figure 7 to Figure 9 The communication device provided in this application is described in detail.

[0354] It is understandable that, in order to realize the above functions, each device for implementing the above functions includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0355] The embodiment of the present application can divide the terminal device or network device (such as SMF) into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0356] See also Figure 7 , Figure 7 It is a structural diagram of a communication device provided in an embodiment of the present application. Figure 7 The communication device 700 shown can be used to perform the above Figure 5 and Figure 6 Part or all of the functions of the terminal device in the described method embodiment. The device can be a terminal device, or a device in a terminal device, or a device that can be used in conjunction with the terminal device. The communication device can also be a chip or a chip system. Figure 7 The communication device shown may include a transceiver unit 701 and a processing unit 702. The processing unit 702 is used for data processing. The transceiver unit 701 integrates a receiving unit and a sending unit. The transceiver unit 701 may also be called a communication unit. Alternatively, the transceiver unit 701 may be split into a receiving unit and a sending unit. The processing unit 702 and the transceiver unit 701 below are similar, and will not be described in detail below.

[0357] In one implementation:

[0358] The transceiver unit 701 is configured to send a first message to a network device, where the first message is used to create a first quality of service flow QoS flow for an extended reality XR service request, where the first QoS flow supports processing based on a packet data unit set PDUSet;

[0359] The transceiver unit 701 is configured to receive a second message from the network device, where the second message includes a first QoS parameter corresponding to the first QoS flow.

[0360] The processing unit 702 is used to generate a first message, process a second message, etc.

[0361] In another implementation:

[0362] The transceiver unit 701 is configured to send a third message to the network device, where the third message is used to request modification of a fourth QoS parameter corresponding to a third quality of service flow QoS flow created for the extended reality XR service; the third QoS flow supports processing based on a packet data unit set PDU Set;

[0363] The transceiver unit 701 is configured to receive a fourth message from the network device, where the fourth message includes QoS parameter update information corresponding to the third QoS flow.

[0364] The processing unit 702 is configured to generate a third message, process a fourth message, and so on.

[0365] For other possible implementations of the communication device, see the above Figure 5 and Figure 6 The relevant description of the terminal device functions in the corresponding method embodiments will not be repeated here.

[0366] See also Figure 8 , Figure 8 It is a structural diagram of another communication device provided in an embodiment of the present application. Figure 8 The communication device 800 shown can be used to perform the above Figure 5 and Figure 6 Part or all of the functions of the network device in the described method embodiment. The device can be a network device, or a device in a network device, or a device that can be used in conjunction with a network device. Exemplarily, the network device can be a network element such as an SMF. The communication device can also be a chip or a chip system. Figure 8 The communication device shown may include a transceiver unit 801 and a processing unit 802. Among them:

[0367] In one implementation:

[0368] The transceiver unit 801 is configured to receive a first message from a terminal device, where the first message is used to create a first quality of service flow QoS flow for an extended reality XR service request, where the first QoS flow supports processing based on a packet data unit set PDU Set;

[0369] The transceiver unit 801 is used to send a second message to the terminal device, where the second message includes a first QoS parameter corresponding to the first QoS flow.

[0370] The processing unit 802 is used to process the first message, generate the second message, etc.

[0371] In another implementation:

[0372] The transceiver unit 801 is configured to receive a third message from a terminal device, where the third message is used to request modification of a fourth QoS parameter corresponding to a third quality of service flow QoS flow created for an extended reality XR service; the third QoS flow supports processing based on a packet data unit set PDU Set;

[0373] The transceiver unit 801 is used to send a fourth message to the terminal device, where the fourth message includes QoS parameter update information corresponding to the third QoS flow.

[0374] The processing unit 802 is configured to process the third message, generate a fourth message, and so on.

[0375] For other possible implementations of the communication device, see the above Figure 5 and Figure 6 The relevant description of the network device functions in the corresponding method embodiments will not be repeated here.

[0376] In a possible implementation, when the terminal device or network device (such as SMF) is a chip, the transceiver unit can be a communication interface, a pin or a circuit, etc. The communication interface can be used to input the data to be processed to the processor, and can output the processing results of the processor to the outside. In a specific implementation, the communication interface can be a general purpose input output (GPIO) interface, which can be connected to multiple peripheral devices (such as a display (LCD), a camera (camara), a radio frequency (RF) module, an antenna, etc.). The communication interface is connected to the processor through a bus.

[0377] The processing unit may be a processor that can execute computer-executable instructions stored in the storage unit to enable the chip to execute Figure 5 and Figure 6 The methods involved.

[0378] Furthermore, the processor may include a controller, an arithmetic unit and a register. Exemplarily, the controller is mainly responsible for decoding instructions and issuing control signals for operations corresponding to the instructions. The arithmetic unit is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logical operations, etc., and may also perform address operations and conversions. The register is mainly responsible for storing register operands and intermediate operation results temporarily stored during the execution of instructions. In a specific implementation, the hardware architecture of the processor may be an ASIC architecture, a microprocessor without interlockedpiped stages architecture (MIPS) architecture, an advanced RISCmachines (ARM) architecture, or a network processor (NP) architecture, etc. The processor may be single-core or multi-core.

[0379] The storage unit may be a storage unit within the chip, such as a register, a cache, etc. The storage unit may also be a storage unit located outside the chip, such as a ROM or other types of static storage devices that can store static information and instructions, a RAM, etc.

[0380] It should be noted that the functions corresponding to the processor and the interface can be implemented through hardware design, software design, or a combination of hardware and software, and there is no limitation here.

[0381] See also Fig. 9 , Fig. 9 9 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device 900 includes a processor 910 and an interface circuit 920. The processor 910 and the interface circuit 920 are coupled to each other. It is understood that the interface circuit 920 can be a transceiver or an input-output interface. Optionally, the communication device may further include a memory 930 for storing instructions executed by the processor 910 or storing input data required by the processor 910 to execute instructions or storing data generated after the processor 910 executes instructions.

[0382] When the communication device is used to implement the method in the above method embodiment, the processor 910 is used to execute the function of the above processing unit, and the interface circuit 920 is used to execute the function of the above transceiver unit.

[0383] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or 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.

[0384] 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, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, CD-ROMs 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. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a terminal device or a network device. Of course, the processor and the storage medium can also be present in a terminal device or a network device as discrete components.

[0385] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is 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. The computer program or instruction can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it can also be an optical medium, such as a digital versatile disc (DVD); it can also be a semiconductor medium, such as a solid state drive (SSD).

[0386] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0387] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.

[0388] An embodiment of the present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed, the method executed by the terminal device or the network device in the above method embodiment is implemented.

[0389] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed, the method executed by the terminal device or the network device in the above method embodiment is implemented.

[0390] The embodiment of the present application also provides a communication system, which includes a terminal device or a network device. The terminal device is used to execute the method executed by the terminal device in the above method embodiment. The network device is used to execute the method executed by the network device in the above method embodiment.

[0391] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0392] The descriptions of the various embodiments provided in this application can refer to each other, and the descriptions of the various embodiments have their own emphasis. For parts that are not described in detail in a certain embodiment, refer to the relevant descriptions of other embodiments. For the convenience and simplicity of description, for example, the functions of the various devices and equipment provided in the embodiments of this application and the steps of execution can refer to the relevant descriptions of the method embodiments of this application, and the various method embodiments and the various device embodiments can also refer to, combine or quote each other.

[0393] Those of ordinary skill in the art will appreciate that the units and steps of each example 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 performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0394] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0395] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned computer-readable storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, computer-readable media may include random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), universal serial bus flash disk, mobile hard disk, or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer. In addition, by way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), or direct rambus RAM (DR RAM).

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

Claims

1. A communication method, characterized in that: Applied to a terminal device, the method comprises: Sending a first message to a network device, where the first message is used to create a first quality of service flow QoSflow for an extended reality XR service request, where the first QoSflow supports processing based on a packet data unit set PDU Set; A second message is received from the network device, where the second message includes a first QoS parameter corresponding to the first QoS flow.

2. The method according to claim 1, characterized in that Before sending the first message to the network device, the method further includes: Sending a PDU session establishment request to the network device; Receiving a PDU session establishment acceptance message from the network device; The sending a first message to the network device includes: Determining, according to the PDU session establishment acceptance message, whether the second QoS flow corresponding to the XR service supports PDU Set-based processing; In a case where the second QoS flow does not support PDU Set-based processing, the first message is sent to the network device.

3. The method according to claim 2, characterized in that The PDU session establishment acceptance message includes first indication information and second indication information; The first indication information indicates the second QoS flow; The second indication information indicates whether the second QoS flow supports PDU Set-based processing.

4. The method according to any one of claims 1 to 3, characterized in that: The sending a first message to the network device includes: Acquire first information of the XR service, where the first information includes a second QoS parameter of the XR service, where the second QoS parameter includes one or more of the following information: a second PDU Set delay budget PSDB, a second PDU Set error rate PSER, or second PDU Set integrated processing information PHISI; The first message is sent to the network device according to the first information.

5. The method according to claim 4, characterized in that The first message includes one or more of the following third QoS parameters expected by the terminal device: a third PSDB, a third PSER, a third PHISI, or a first tag value; The first marking value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction, and the third QoS parameter is determined based on the second QoS parameter.

6. The method according to claim 5, characterized in that The first QoS parameter includes one or more of the following QoS parameters configured by the network device: A first PSDB, a first PSER, a first PHISI, or a first tag value.

7. The method according to any one of claims 1 to 3, characterized in that: The sending a first message to the network device includes: When the XR service is determined according to the traffic characteristics, the first message is sent to the network device.

8. The method according to claim 7, characterized in that The first message includes one or more of the following third QoS parameters expected by the terminal device: A first tag value, a second tag value, or a first 5QI; the first tag value is used to indicate support for PDU Set processing in the uplink direction and / or downlink direction, the second tag value is used to indicate that the first QoS flow supports PDU Set-based processing, the parameters indicated by the first 5QI include packet delay budget PDB and packet error rate PER, and the first 5QI is the 5QI associated with the second QoS flow.

9. The method according to claim 7, characterized in that: The first QoS parameter includes one or more of the following QoS parameters configured by the network device: A first tag value, a second tag value, or a second 5QI.

10. The method according to any one of claims 1 to 9, characterized in that: The first message is a PDU session modification request message, and / or the second message is a PDU session modification command message.

11. The method according to any one of claims 1 to 10, characterized in that: The first message includes flow information of the XR service.

12. A communication method, characterized in that: Applied to a terminal device, the method comprises: Sending a third message to the network device, where the third message is used to request modification of a fourth QoS parameter corresponding to a third quality of service flow QoSflow created for the extended reality XR service; where the third QoSflow supports processing based on a packet data unit set PDUSet; A fourth message is received from the network device, where the fourth message includes QoS parameter update information corresponding to the third QoS flow.

13. The method according to claim 12, characterized in that Before sending the third message to the network device, the method further includes: Sending a PDU session establishment request to the network device; A PDU session establishment accept message is received from the network device, where the PDU session establishment accept message includes third indication information, and the third indication information indicates the third QoS flow.

14. The method according to claim 13, characterized in that The PDU session establishment acceptance message also includes the fourth QoS parameter, where the fourth QoS parameter includes one or more of the following information: a fourth PDU Set delay budget PSDB, a fourth PDU Set error rate PSER, a fourth PDU Set integrated processing information PHISI, or a first tag value; The first flag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction; The sending a third message to the network device includes: Acquire a fifth QoS parameter of the XR service, where the fifth QoS parameter includes one or more of the following information: a fifth PSDB, a fifth PSER, or a fifth PHISI; In a case where the fourth QoS parameter does not match the fifth QoS parameter, the third message is sent to the network device based on the fifth QoS parameter.

15. The method according to claim 13, characterized in that The PDU session establishment accept message also includes the fourth QoS parameter, where the fourth QoS parameter includes one or more of the following information: a fourth PSDB, a fourth PSER, a fourth PHISI, or a first tag value; The first flag value is used to indicate the processing of the PDU Set supporting the uplink direction and / or the downlink direction; The sending a third message to the network device includes: When the number of PDU Sets of the XR service received in a unit time is less than a first threshold, the third message is sent to the network device based on the fourth QoS parameter.

16. The method according to claim 14 or 15, characterized in that The third message includes one or more of the following third QoS parameters expected by the terminal device: a third PSDB, a third PSER, or a third PHISI; The third QoS parameter is determined based on the fourth QoS parameter, or the third QoS parameter is determined based on the fifth QoS parameter.

17. The method according to claim 16, characterized in that The QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device: A sixth PSDB, a sixth PSER, or a sixth PHISI.

18. The method according to claim 13, characterized in that The PDU session establishment accept message also includes a fourth QoS parameter, and the fourth QoS parameter includes one or more of the following information: a fourth 5QI, a first tag value, or a third tag value; the first tag value is used to indicate that the processing of the PDU Set in the uplink direction and / or the downlink direction is supported, and the third tag value is used to indicate that the third QoS flow supports the processing based on the PDU Set; The sending a third message to the network device includes: Acquire a fifth QoS parameter of the XR service, where the fifth QoS parameter includes a fifth 5QI; In a case where the fourth 5QI and the fifth 5QI do not match, the third message is sent to the network device based on the fifth 5QI.

19. The method according to claim 13, characterized in that The PDU session establishment accept message also includes a fourth QoS parameter, and the fourth QoS parameter includes one or more of the following information: a fourth 5QI, a first tag value, or a third tag value; the first tag value is used to indicate that the processing of the PDU Set in the uplink direction and / or the downlink direction is supported, and the third tag value is used to indicate that the third QoS flow supports the processing based on the PDU Set; The sending a third message to the network device includes: When the number of PDU Sets of the XR service received in a unit time is less than a first threshold, the third message is sent to the network device based on the fourth 5QI.

20. The method according to claim 18 or 19, characterized in that The third message includes one or more of the following third QoS parameters expected by the terminal device: A third 5QI, or a third marking value; The third 5QI is determined based on the fourth 5QI parameter, or the third QoS parameter is determined based on the fifth 5QI.

21. The method according to claim 20, characterized in that The QoS parameter update information includes one or more of the following sixth QoS parameters reconfigured by the network device: Sixth 5QI, or third marker value.

22. The method according to any one of claims 12 to 21, characterized in that: The third message is a PDU session modification request message, and / or the fourth message is a PDU session modification command message.

23. A communication method, characterized in that: Applied to a network device, the method comprises: Receive a first message from a terminal device, where the first message is used to create a first quality of service flow QoS flow for an extended reality XR service request, where the first QoS flow supports processing based on a packet data unit set PDU Set; A second message is sent to the terminal device, where the second message includes a first QoS parameter corresponding to the first QoS flow.

24. The method according to claim 23, characterized in that Before receiving the first message from the terminal device, the method further includes: Receiving a PDU session establishment request from the terminal device; Send a PDU session establishment accept message to the terminal device; the PDU session establishment accept message is used to determine whether the second QoS flow corresponding to the XR service supports PDU Set-based processing.

25. A communication method, characterized in that: Applied to a network device, the method comprises: receiving a third message from the terminal device, wherein the third message is used to request modification of a fourth QoS parameter corresponding to a third quality of service flow QoS flow created for the extended reality XR service; wherein the third QoS flow supports processing based on a packet data unit set PDU Set; A fourth message is sent to the terminal device, where the fourth message includes QoS parameter update information corresponding to the third QoS flow.

26. The method according to claim 25, characterized in that Before receiving the third message from the terminal device, the method further includes: Receiving a PDU session establishment request from the terminal device; A PDU session establishment acceptance message is sent to the terminal device, wherein the PDU session establishment acceptance message includes third indication information, and the third indication information indicates the third QoS flow.

27. A communication device, comprising a unit or module for executing the method as described in any one of claims 1-11, or a unit or module for executing the method as described in any one of claims 12-22, or a unit or module for executing the method as described in any one of claims 23-24, or a unit or module for executing the method as described in any one of claims 25-26.

28. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1-11, or implement the method as described in any one of claims 12-22, or implement the method as described in any one of claims 23-24, or implement the method as described in any one of claims 25-26 through logic circuits or execution code instructions.

29. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, it implements the method as described in any one of claims 1 to 11, or implements the method as described in any one of claims 12 to 22, or implements the method as described in any one of claims 23 to 24, or implements the method as described in any one of claims 25 to 26.

30. A computer program product, characterized in that Comprising computer program code, when the computer program code is run on a computer, to implement the method as claimed in any one of claims 1 to 11, or to implement the method as claimed in any one of claims 12 to 22, or to implement the method as claimed in any one of claims 23 to 24, or to implement the method as claimed in any one of claims 25 to 26.

31. A communication system, characterized in that: It includes a terminal device and a network device, wherein the terminal device is used to implement the method described in any one of claims 1 to 11 or the method described in any one of claims 12 to 22, and the network device is used to implement the method described in any one of claims 23 to 24 or the method described in any one of claims 25 to 26.

Images