Communication method and apparatus

Abstract

This application provides a communication method and apparatus, belonging to the field of communication, to enable more flexible transmission of uplink data of different types. This communication method can be applied to a first device, or the chip or chip system of the first device, or an apparatus containing the first device; for ease of understanding, it will be described using an application to a first device as an example. The method includes: acquiring uplink transmission information of the first device and sending the uplink transmission information of the first device to a network device. The uplink transmission information of the first device includes the transmission period of the uplink data and information of at least two data streams, wherein different types of data in the uplink data are respectively carried on at least two data streams.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a communication method and apparatus. Background Technology

[0002] Data generated by extended reality (XR) services can be categorized into I-frames (intra-coded pictures) and P-frames (predictive-coded pictures) based on their importance (or type). For example, a group of pictures (GOP) contains several consecutive video frames. The first video frame is called an I-frame, and the remaining frames are called P-frames. I-frames contain complete image information and can be encoded and decoded independently. P-frames contain partial image information and require the help of previous frames for encoding and decoding. In other words, an I-frame affects not only the playback of the current I-frame but also the playback of the following P-frames, and vice versa.

[0003] How to enable flexible transmission of I-frames and P-frames is a current research question. Summary of the Invention

[0004] This application provides a communication method and apparatus to enable more flexible transmission of different types of uplink data.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a communication method is provided, which can be applied to a first device, or a chip or chip system of the first device, or a device containing the first device. For ease of understanding, the method will be described using an application to a first device as an example. The method includes: acquiring uplink transmission information of the first device and sending the uplink transmission information of the first device to a network device. The uplink transmission information of the first device includes the transmission period of uplink data and information about at least two data streams, wherein different types of data in the uplink data are respectively carried on at least two data streams.

[0007] As described in the first aspect, for periodically transmitted uplink data, if different types of data in the uplink data are carried on at least two data streams, the first device can jointly report the information of at least two data streams through uplink transmission information. In this way, the network device can not only configure transmission resources for the uplink data as a whole, such as periodic transmission resources, but also ensure the transmission of at least two data streams separately, thus meeting the transmission needs of different types of data and making transmission more flexible.

[0008] In one possible design, the information for at least two data streams includes the identifiers of each data stream, used to distinguish them and avoid confusion. For example, if a data stream is a QoS stream, its identifier could be a QFI.

[0009] In one possible design, the method described in the first aspect may further include: sending capability information of the first device to the network device and receiving response information from the network device. The capability information indicates that the first device supports the ability to combine information from different data streams into a single uplink transmission message for reporting, and the response information indicates that the first device is permitted to combine information from different data streams into a single uplink transmission message for reporting. In other words, the first device needs to use the capability as instructed by the network device to avoid data transmission errors, such as the network device being unable to configure appropriate transmission resources because it cannot recognize the information from different data streams.

[0010] Optionally, the method in the first aspect may further include: receiving capability query information from a network device, the capability query information being used to query whether the first device supports the capability to combine information from different data streams into one uplink transmission information for reporting; and sending capability information of the first device to the network device, including: sending capability information to the network device according to the capability query information to achieve on-demand capability reporting.

[0011] In one possible design, the method described in the first aspect may further include: receiving configuration information from a session management network element, the session management network element serving the first device, the configuration information indicating the data stream to which different types of data in the uplink data are carried.

[0012] In one possible design, the method described in the first aspect may further include: determining which types of data in the upstream data of the service are carried to their respective corresponding data streams based on the data type in the upstream data. For example, more important data among different types of data can be carried to higher-priority data streams to ensure the reliability of transmission.

[0013] In one possible design, the method described in the first aspect may further include: receiving resource information from a network device, the resource information indicating transmission resources (such as periodic transmission resources) shared by at least two data streams to save resource overhead.

[0014] In one possible design, the uplink data is the uplink data for Extended Reality (XR) services. This uplink data includes different types of data, including I-frames and P-frames of XR services, to ensure the reliability and flexibility of I-frame and P-frame transmission.

[0015] Secondly, a communication method is provided, which can be applied to a network device, a chip or chip system of a network device, or a device containing a network device. For ease of understanding, an application to a network device will be used as an example for explanation. The method includes: receiving uplink transmission information from a first device; and configuring uplink data transmission resources based on the uplink transmission information from the first device. The uplink transmission information from the first device includes the uplink data transmission period and information about at least two data streams, wherein different types of data in the uplink data are respectively carried to at least two data streams.

[0016] In one possible design, the information of at least two data streams includes the identifiers of each of the at least two data streams.

[0017] In one possible design, configuring uplink data transmission resources based on uplink transmission information of the first device includes: sending resource information to the first device based on the uplink transmission information of the first device, wherein the resource information indicates transmission resources shared by at least two data streams.

[0018] In one possible design, the method described in the second aspect may further include: receiving capability information of the first device, and sending response information to the first device based on the capability information. The capability information indicates that the first device supports the capability to combine information from different data streams into a single uplink transmission message for reporting; the response information indicates that the first device is permitted to combine information from different data streams into a single uplink transmission message for reporting.

[0019] Optionally, the method in the second aspect may further include: sending capability query information to the first device, the capability query information being used to query whether the first device supports the capability to combine information from different data streams into a single uplink transmission information for reporting.

[0020] In one possible design, the uplink data is the uplink data for Extended Reality (XR) services, and the different types of data include I-frames and P-frames for XR services.

[0021] Furthermore, the technical effects of the method described in the second aspect can be referred to the description of the method in the first aspect, and will not be repeated here.

[0022] Thirdly, a communication method is provided, which can be applied to a first device, or a chip or chip system of the first device, or a device containing the first device. For ease of understanding, the method will be described using an application to a first device as an example. The method includes: acquiring indication information from the first device and sending the indication information to a network device. The indication information indicates the size of the data to be transmitted in the uplink data of the first device and the data stream carried by the data to be transmitted. The uplink data is periodically transmitted data, and different types of data in the uplink data are carried on at least two data streams.

[0023] As can be seen from the method described in the third aspect, for periodically transmitted uplink data, and where different types of data in the uplink data are carried by at least two data streams, the first device can report the status of the data to be transmitted in the uplink data through indication information, such as the size of the data to be transmitted and the data stream carried by the data to be transmitted, so that the network device can schedule the transmission of the data to be transmitted in a timely manner and achieve the protection of the data stream.

[0024] In one possible design, the indication information includes an identifier of the data stream carried by the data to be transmitted, used to accurately indicate the data stream and avoid confusion. For example, if the data stream is a QoS stream, the identifier of the data stream could be QFI.

[0025] In one possible design, the indication information is carried in the Media Access Layer Control Unit (MAC-CE), which reuses existing signaling, resulting in lower implementation complexity and greater standard compatibility. Alternatively, the indication information can be carried in newly defined signaling, achieving decoupling from existing signaling and enabling more flexible transmission.

[0026] In one possible design, the method described in the third aspect may further include: sending capability information of the first device to the network device and receiving response information from the network device, wherein the capability information indicates the first device's ability to report the size of data to be transmitted periodically; and the response information indicates that the first device is allowed to report the size of the data to be transmitted periodically. That is, the first device needs to use the capability as instructed by the network device to avoid redundant reporting.

[0027] Optionally, the method in the third aspect may further include: receiving capability query information from a network device, the capability query information being used to query whether the first device supports the capability to report the size of data to be transmitted periodically; and sending capability information of the terminal device to the network device, including: sending capability information to the network device according to the capability query information, so as to achieve on-demand capability reporting and avoid redundancy.

[0028] In one possible design, the uplink data is the uplink data of the extended reality XR service, and the data to be transmitted includes at least one frame of data from the XR service to ensure the reliability of the transmission of each frame of data.

[0029] Fourthly, a communication method is provided, which can be applied to a network device, or a chip or chip system of a network device, or a device containing a network device. For ease of understanding, an application to a network device will be used as an example for explanation. The method includes: receiving indication information from a first device, and scheduling the transmission of data to be transmitted according to the indication information. The indication information indicates the size of the data to be transmitted in the uplink data of the first device and the data stream carried by the data to be transmitted. The uplink data is periodically transmitted data, and different types of data in the uplink data are carried on at least two data streams.

[0030] In one possible design, the indication information includes an identifier of the data stream carried by the data to be transmitted.

[0031] In one possible design, the instruction information is carried in the Media Access Layer Control Unit (MAC-CE).

[0032] In one possible design, the method described in the third aspect may further include: receiving capability information of the first device and sending response information to the first device. The capability information indicates the first device's ability to support reporting the size of data to be transmitted periodically, and the response information indicates that the first device is permitted to report the size of the data to be transmitted periodically.

[0033] In one possible design, the method described in the third aspect may further include: sending capability query information to the first device, the capability query information being used to query whether the first device supports the capability to report the size of data to be transmitted periodically.

[0034] In one possible design, the uplink data is the uplink data of the extended reality XR service, and the data to be transmitted includes at least one frame of data from the XR service.

[0035] Furthermore, the technical effects of the method described in the fourth aspect can be referred to the description of the method in the third aspect, and will not be repeated here.

[0036] Fifthly, a communication method is provided, which can be applied to a first device, or a chip or chip system of the first device, or a device containing the first device. For ease of understanding, it will be described using an application to a first device as an example. The method includes: determining the timing duration of a first timer; starting the first timer when the transmission of the first device's data set begins; and discarding the first device's data set if the transmission of the first device's data set is not completed when the first timer expires. The timing duration of the first timer is longer than a first duration, and the first device's data set needs to be transmitted within the first duration.

[0037] As can be seen from the method described in the fifth aspect, by setting the timing duration of the first timer to be greater than the duration required for the data transmission of the first device (such as the first duration), even if the data of the first device has not been transmitted after the first duration, as long as the first timer has not expired, the first device will continue to transmit the data of the first device, thereby reducing the possibility that the data of the first device will be discarded, and thus ensuring the reliability and stability of the transmission.

[0038] In one possible design, the dataset of the first device is any one of the uplink datasets periodically transmitted by the first device, and the timing duration of the first timer is longer than the period of the uplink dataset. For example, the timing duration of the first timer is the sum of the first duration and the period of the uplink dataset. That is, even if the transmission time of the dataset of the first device exceeds the first duration, the dataset of the first device should be transmitted within the next period as much as possible to avoid the dataset of the first device becoming invalid due to excessive transmission time.

[0039] In one possible design, the dataset of the first device includes at least one set of Protocol Data Units (PDUs), and the first duration is the delay budget (PSDB) of the PDU set. That is, the timing duration of the first timer exceeds the original duration (i.e., PSDB) of the dataset of the first device, so as to reduce the possibility of the dataset of the first device being discarded.

[0040] In one possible design, the method described in the fifth aspect may further include: receiving information from a first timer of a network device, wherein the information of the first timer indicates the timing duration of the first timer. Determining the timing duration of the first timer includes: determining the timing duration of the first timer based on the information of the first timer. That is, the timing duration of the first timer can be configured on demand by the network side to avoid affecting the reliability of data transmission due to the timing duration determined by the first device itself failing to meet the needs of the network side.

[0041] In one possible design, the method described in the fifth aspect may further include: determining a threshold duration, and when the remaining defined duration of the first timer reaches the threshold duration, sending an indication message to the network device, the indication message indicating the untransmitted data in the dataset of the first device, so that the network device can perceive the current transmission status and perform timely scheduling to ensure that the dataset of the first device can be transmitted as soon as possible and avoid transmission timeout.

[0042] Optionally, the method in the fifth aspect may further include: receiving information from the network device indicating the duration of the threshold.

[0043] In one possible design, the dataset of the first device is a frame of data from an extended reality (XR) service. In XR services, the data of the previous frame usually affects the playback of the next frame / multiple frames. Therefore, by setting the timing duration of the first timer to be greater than a first duration, it can be ensured that even if the data transmission of the previous frame times out (greater than the first duration), as long as the first timer does not time out, it will not affect the playback of the next frame / multiple frames, thereby improving the user experience.

[0044] Sixthly, a communication method is provided, which can be applied to a network device, a chip or chip system of a network device, or a device containing a network device. For ease of understanding, an application to a network device will be used as an example for explanation. The method includes: determining the timing duration of a first timer and configuring the timing duration of the first timer for a first device. The timing duration of the first timer is longer than a first duration, and the data set of the first device needs to be transmitted within the first duration. If the data set of the first device fails to be transmitted when the first timer expires, the data set of the first device needs to be discarded.

[0045] In one possible design, the dataset of the first device is any one of the uplink datasets periodically transmitted by the first device, and the timing duration of the first timer is greater than the period of the uplink dataset.

[0046] Optionally, determining the timing duration of the first timer includes: determining the timing duration of the first timer based on the first duration.

[0047] Furthermore, based on the first duration, the timing duration of the first timer is determined, including: the sum of the first duration and the period of the uplink dataset is determined as the timing duration of the first timer. In other words, the dataset of the first device needs to be transmitted within the next period as much as possible to avoid the dataset of the first device becoming invalid due to excessive transmission time.

[0048] In one possible design, the method described in the sixth aspect may further include: receiving configuration information from a session management network element, the session management network element serving the first device, the configuration information indicating a second duration, the second duration being longer than the first duration; determining the timing duration of a first timer, including: determining the second duration as the timing duration of the first timer, that is, the timing duration of the first timer can be indicated by a core network element, so as to avoid the overhead caused by the network device determining the timing duration itself.

[0049] In one possible design, configuring the timing duration of the first timer for the first device includes: sending information about the first timer to the first device, wherein the information about the first timer indicates the timing duration of the first timer.

[0050] In one possible design, the dataset of the first device includes at least one set of Protocol Data Units (PDUs), and the first duration is the PDU set delay budget (PSDB).

[0051] In one possible design, the dataset of the first device is a frame of data from an extended reality XR service.

[0052] Furthermore, the technical effects of the method described in the sixth aspect can be referred to the description of the method in the fifth aspect, and will not be repeated here.

[0053] A seventh aspect provides a communication apparatus. This communication apparatus is used to perform the communication method described in any one of the first to sixth aspects.

[0054] In this application, the communication device described in the seventh aspect can be the communication device itself, a chip (system) or other components or assemblies, or a device containing the communication device. The aforementioned chip (system) or other components or assemblies can all be disposed within the communication device.

[0055] It should be understood that the communication apparatus described in the seventh aspect includes modules, units, or means that implement the communication methods described in any of the first to sixth aspects. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units for performing the functions involved in the aforementioned communication methods.

[0056] Eighthly, a communication device is provided. The communication device includes a processor configured to execute the communication method described in any one of the first to sixth aspects.

[0057] In one possible design, the communication device described in the eighth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eighth aspect and other communication devices.

[0058] In one possible design, the communication device described in the eighth aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data related to the communication method described in any of the first aspects.

[0059] In this application, the communication device described in the eighth aspect can be the communication device itself, a chip (system) or other components or assemblies, or a device containing the communication device. The aforementioned chip (system) or other components or assemblies can all be disposed within the communication device.

[0060] A ninth aspect provides a communication device. The communication device includes a processor coupled to a memory, the processor being configured to execute a computer program stored in the memory, such that the communication device performs the communication method described in any one of the first to sixth aspects.

[0061] In one possible design, the communication device described in the ninth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the ninth aspect and other communication devices.

[0062] In this application, the communication device described in the ninth aspect can be the communication device itself, a chip (system) or other component or assembly, or a device containing the communication device. The aforementioned chip (system) or other component or assembly can all be disposed within the communication device.

[0063] A tenth aspect provides a communication device, comprising: a processor and a memory; the memory being used to store a computer program, which, when executed by the processor, causes the communication device to perform the communication method described in any one of the first to sixth aspects.

[0064] In one possible design, the communication device described in the tenth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the tenth aspect and other communication devices.

[0065] In this application, the communication device described in the tenth aspect can be the communication device itself, a chip (system) or other component or assembly, or a device containing the communication device. The aforementioned chip (system) or other component or assembly can all be disposed within the communication device.

[0066] Eleventhly, a communication device is provided, comprising: a processor; the processor being configured to be coupled to a memory, and after reading a computer program from the memory, to execute a communication method as described in any one of the first to sixth aspects according to the computer program.

[0067] In one possible design, the communication device described in the eleventh aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eleventh aspect and other communication devices.

[0068] In this application, the communication device described in the eleventh aspect can be the communication device itself, a chip (system) or other components or assemblies, or a device containing the communication device. The aforementioned chip (system) or other components or assemblies can all be disposed within the communication device.

[0069] In a twelfth aspect, a processor is provided. The processor is configured to execute the communication method described in any one of the first to sixth aspects.

[0070] In a thirteenth aspect, a communication system is provided. The communication system includes a first means for performing the method described in any one of the first, third, or fifth aspects, and a network device for performing the method described in any one of the second, fourth, or sixth aspects.

[0071] In a fourteenth aspect, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed on a computer, causing the computer to perform the communication method described in any one of the first to sixth aspects.

[0072] In a fifteenth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method described in any one of the first to sixth aspects. Attached Figure Description

[0073] Figure 1 This is a schematic diagram illustrating the mapping relationship of QoS flows;

[0074] Figure 2 This is a schematic diagram of XR service transmission.

[0075] Figure 3 This is a flowchart illustrating the UAI process.

[0076] Figure 4 A schematic diagram of I-frame and P-frame transmission for XR services. Figure 1 ;

[0077] Figure 5 A schematic diagram of I-frame and P-frame transmission for XR services. Figure 2 ;

[0078] Figure 6 A schematic diagram of the architecture of a communication system provided in this application;

[0079] Figure 7 A flowchart illustrating a communication method provided in this application Figure 1 ;

[0080] Figure 8 A flowchart illustrating a communication method provided in this application Figure 2 ;

[0081] Figure 9 A flowchart illustrating a communication method provided in this application Figure 3 ;

[0082] Figure 10A flowchart illustrating a communication method provided in this application Figure 4 ;

[0083] Figure 11 A flowchart illustrating a communication method provided in this application Figure 5 ;

[0084] Figure 12 A flowchart illustrating a communication method provided in this application Figure 6 ;

[0085] Figure 13 A flowchart illustrating a communication method provided in this application Figure 7 ;

[0086] Figure 14 A schematic diagram of the structure of a communication device provided in this application Figure 1 ;

[0087] Figure 15 A schematic diagram of the structure of a communication device provided in this application Figure 2 . Detailed Implementation

[0088] The technical solutions of this application embodiment can be applied to various communication systems, such as Wi-Fi systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, fourth-generation (4G) mobile communication systems, such as long-term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems.

[0089] The technical terms and related technical solutions in this application will be described below with reference to the accompanying drawings.

[0090] 1. Quality of Service (QoS) flow:

[0091] The 5G system (5GS) forwards and processes data at the granularity of QoS streams to ensure data QoS.

[0092] like Figure 1As shown, the 5G core network (5GC) establishes one or more PDU sessions for a user equipment (UE). A QoS flow is a data flow within a PDU session that has the same source and destination addresses and the same QoS requirements. For downlink data, the 5GC identifies the characteristics of the data packets, such as the source Internet Protocol (IP) address, destination IP address, source port number, destination port number, and transport layer protocol number. It maps data packets with the same characteristics to the same QoS flow and carries the identifier of the QoS flow, such as the QoS flow ID (QFI), in the packet header to identify which QoS flow the data packet belongs to. For uplink data, the 5GC can explicitly or implicitly configure the mapping relationship between the above data packet characteristics and QoS flows to the UE. The UE then maps the data packets to be transmitted to the corresponding QoS flow for uplink transmission.

[0093] Different QoS streams are transmitted independently in 5GS. For each QoS stream, 5GC sends a QoS profile to the corresponding radio access network (RAN) device to indicate the QoS requirements of that stream, including common QoS parameters such as packet delay budget (PDB) and packet error rate (PER). PDB represents the upper limit of data packet transmission delay between the core network (e.g., user plane function (UPF)) and the UE; data packets that fail to complete transmission within the PDB are considered to have timed out. PER represents the upper limit of packet error rate during QoS stream transmission, i.e., the percentage of data packets processed by the sender but not correctly received by the receiver. These QoS parameters indicate the expected QoS of the data in that QoS stream during transmission, and the network should strive to ensure that these requirements are met to guarantee a good user experience.

[0094] For a PDU session, the RAN establishes one or more data radio bearers (DRBs) and maps each QoS stream to these DRBs for air interface transmission. Multiple QoS streams can be mapped to a single DRB, but a single QoS stream typically cannot be mapped to multiple DRBs. QoS streams with the same or similar QoS requirements are usually mapped to the same DRB, thus providing the same or similar QoS guarantees over the air interface.

[0095] 2. Extended Reality (XR):

[0096] XR refers to various environments that combine reality and virtuality, generated by computing technology and wearable devices, as well as human-computer interaction. Specifically, it includes the following typical forms: augmented reality (AR), mixed reality (MR), and virtual reality (VR).

[0097] XR is one of the key 5G multimedia applications currently being considered in the industrial sector. The 3rd Generation Partnership Project (3GPP) Release-18 (R-17) modeled and analyzed the service characteristics of XR. XR services typically generate data frames periodically. Taking an AR service with a frame rate of 60 frames per second (fps) as an example, 60 video frames are generated per second, approximately one video frame every 16.67 milliseconds (ms). A video frame may be transmitted by multiple data packets, which may be divided into one or more Protocol Data Unit (PDU) sets. The size of the data frames is not fixed and usually follows a truncated Gaussian distribution. The mean of the data frames can be expressed as mean = R / F, where F is the frame rate and R is the data stream rate. For example, with F = 60 fps and R = 20 megabits per second (Mbps), the mean = 41.67 kilobytes (Kbytes). The size of the data frame can be distributed between 0.5*mean and 1.5*mean.

[0098] Because of potential time delays during data frame encoding, the arrival time of each data frame at the air interface (e.g., base station) can fluctuate, meaning the data frame may arrive earlier or later than expected, typically within a few milliseconds. Figure 2 As shown in the schematic diagram of the XR downlink service model given by 3GPP, the k-th data frame of the XR service arrives at the base station at time t. Theoretically, the (k+1)-th data frame should arrive at the base station at an average period of 1 / fps, that is, at time t+1 / fps. However, due to jitter, the (k+1)-th data frame may actually arrive at the base station within a certain period before or after t+1 / fps. This period is called the jitter range, and the jitter at the arrival time of the (k+1)-th data frame also follows a certain probability distribution.

[0099] An XR service may contain data frames of varying importance (or different types). Taking video as an example, XR service video frames are sent periodically, and these frames can be encoded based on groups of pictures (GOPs). A GOP contains several consecutive video frames. The first video frame is called an I-frame (intra-coded picture), which contains complete image information and uses intra-frame coding, meaning it can be encoded and decoded independently. The remaining video frames are called P-frames (predictive-coded pictures), which contain partial image information and use predictive coding, meaning they require the previous frames for encoding and decoding.

[0100] 3. PDU set QoS parameters:

[0101] Unlike ordinary services, XR services typically require QoS guarantees at the PDU (Program Data Unit) level. For example, since a PDU corresponds to the smallest unit of application-layer data processing, such as a video frame, the receiver can only successfully decode the video frame if all data packets in that PDU are correctly received. Therefore, XR services require the network to provide overall QoS guarantees for the PDU set to prevent timeouts or errors in some data packets from causing the entire video frame encoding / decoding to fail.

[0102] To address this, 3GPP Release 18 (R18) designed new QoS parameters for XR services, called PDU set QoS parameters. These mainly include the PDU set delay budget (PSDB), PDU set error rate (PSER), and PDU set integrated information (PSIHI). PSDB and PSER correspond to the traditional PDB and PER, respectively. PSDB represents the upper limit of the delay from the first data packet in the PDU set being transmitted between the UPF and UE, until the last data packet in the PDU set is transmitted between the core network and UE. PDU sets that fail to be fully transmitted correctly within the PSDB are considered to have timed out. PSER represents the upper limit of the percentage of PDU sets that failed to be transmitted correctly during transmission; that is, the upper limit of the percentage of PDU sets processed by the sender but not correctly received by the receiver. Currently, 3GPP stipulates that if all data packets in a PDU set are correctly received, the PDU set is considered to have been correctly received. PSIHI indicates whether the application layer (such as the sending end's application layer) requires the receiving end to correctly receive all data packets within the PDU set when processing the PDU set.

[0103] Therefore, by using PDU set QoS parameters, the core network can require RAN devices to provide PDU set-level QoS guarantees for QoS flows based on PDU sets (such as QoS flows for XR services), thereby improving the user experience for XR users.

[0104] 4. Uplink (UL) transmission information:

[0105] XR services are periodic, and in uplink scheduling, static / semi-static configuration grant (CG) scheduling is usually adopted. For example, the UE reports the relevant uplink transmission information of scheduling parameters to the base station through UE assistance information (UAI) so that the base station can configure CG resources for the UE.

[0106] Figure 3 This is a flowchart of UAI, such as Figure 3 As shown, after the UE and base station interact with each other via radio resource control (RRC) reconfiguration signaling, the UE reports uplink transmission information according to the QoS stream level, including at least one of the following information for XR services: QFI, burst arrival time, jitter interval, traffic periodicity, PDU set identifier (pdu-SetIdentification), or PSI identifier (psi-Identification). QFI indicates the QoS stream to which the XR service data is mapped (or carried). Burst arrival time refers to the estimated time it takes for data from a video frame (such as the first video frame) to arrive at the base station. The traffic periodicity can be the period of each video frame, such as 1 / 60 = 16.67ms as mentioned above. The PDU set identifier indicates that data transmission is at the PDU set granularity, and the PSI identifier indicates the importance of the PDU set. Therefore, the base station can configure CG resources and perform QoS guarantees based on at least one of the above information.

[0107] 5. Delay Status Report (DSR):

[0108] As mentioned earlier, XR services have high latency requirements. For uplink XR services, to enable the base station to understand the latency consumption of data in the UE's buffer and complete data transmission before the PSDB (Power Supply Depository) is exhausted, Release 18 introduces the concept of remaining time and a reporting mechanism. For example, when each video frame's data is buffered by the UE (i.e., queued for transmission, or considered as the start of transmission), the UE starts a discard timer for that data. Typically, the duration of this discard timer is the same as the PSDB of the data. If the data has not been fully transmitted after the timer expires (e.g., some data has not been transmitted), the UE will discard the data. To ensure that data transmission is completed before the discard timer expires, the UE can report the remaining time of the data in the UE's buffer to the base station. This remaining time can be the remaining time in the PSDB. For example, the UE can send a medium access control (MAC) control element (MAC-CE) to the base station. This MAC-CE can be called a DSR. The MAC-CE can explicitly or implicitly indicate the remaining time of some or all of the data (or data to be sent) in the UE's buffer, or it can indicate the amount of data to be sent corresponding to a certain remaining time, such as the amount of data with a remaining time of less than 10ms.

[0109] In summary, data generated by XR services can be categorized into I-frames and P-frames based on their importance (or type). I-frames and P-frames map to the same QoS stream. The UE reports uplink transmission information according to this QoS stream level, and the base station uses CG scheduling based on the uplink transmission information. However, if... Figure 4 As shown, I-frames are not only more important than P-frames, but also have a larger data volume. If CG scheduling is used, the amount of resources allocated in each cycle will be the same. If this amount of resources can guarantee the transmission of I-frames, then P-frames may have low resource utilization due to their smaller data volume. If this amount of resources can just guarantee the transmission of P-frames, then this amount of resources may not be able to complete the transmission of I-frames, affecting transmission reliability and potentially causing multiple consecutive video frames to fail to play properly.

[0110] To address this issue and achieve more flexible resource allocation, one approach is to carry I-frames and P-frames on different QoS streams. This allows I-frames and P-frames to be configured with different QoS requirements, thus balancing resource utilization and transmission reliability. However, if... Figure 5As shown, if I-frames and P-frames are carried to different QoS streams, such as QoS stream #1 and QoS stream #2, then there may be no periodicity between two I-frames, such as the interval between two I-frames may be different. Similarly, there may also be no periodicity between two P-frames, such as the interval between two P-frames may be different. This makes it impossible for the base station to use CG scheduling, and the signaling indication overhead required to transmit I-frames and P-frames may be greater.

[0111] Furthermore, as mentioned above, there are several P-frames between two I-frames. I-frames not only affect the playback of the current I-frame but also the playback of the following P-frames (such as P-frames in a GOP). Similarly, P-frames not only affect the playback of the current P-frame but also the playback of the following P-frames. If the data of a frame is discarded due to a timer expiration, not only will that frame fail to play due to decoding failure, but it will also cause one or more subsequent frames to malfunction, impacting the user experience.

[0112] To address the aforementioned technical problems, this application proposes the following technical solutions. The technical solutions in this application will now be described in conjunction with the accompanying drawings.

[0113] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0114] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as an "example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Rather, the use of the word "example" is intended to present the concept in a specific manner.

[0115] First, in this application, "for indicating" can include both direct and indirect indication. When describing "information" for indicating A, it can include whether the information directly indicates A or indirectly indicates A, but does not necessarily mean that the information carries A.

[0116] The information indicated by a given piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent. Simultaneously, the common parts of various pieces of information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information. Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be elaborated upon here. As can be seen from the above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required instruction method can be selected according to specific needs. This application embodiment does not limit the selected instruction method. Therefore, the instruction methods involved in this application embodiment should be understood to cover various methods that can enable the party to be instructed to know the information to be instructed.

[0117] The information to be indicated can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, one or a combination of at least two of RRC signaling, MAC layer signaling, and physical layer signaling. MAC layer signaling includes, for example, MAC-CE; physical (PHY) layer signaling includes, for example, downlink control information (DCI).

[0118] Second, in the embodiments shown below, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, they distinguish different indication information.

[0119] Third, "pre-defined," "pre-configured," or "pre-specified" can be achieved by pre-saving corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminal devices and network devices), or by pre-defining them in a protocol. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0120] Fourth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as 3GPP’s LTE protocols (such as technical specification (TS) 36, i.e., the TS36 series of technical specifications), NR protocols (such as the TS38 series of technical specifications), and related protocols applied to future communication systems. This application does not limit this.

[0121] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0122] To facilitate understanding of the embodiments of this application, let's first take... Figure 6 The communication system illustrated herein is used as an example to illustrate a communication system applicable to embodiments of this application. For example, Figure 6 This is a schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application applies.

[0123] Figure 6 This is a schematic diagram of the architecture of a communication system, which mainly includes: a first device and network equipment.

[0124] The first device can be a terminal with transceiver functions, or it can be a chip or chip system installed in the terminal, or it can be a device containing the terminal. The terminal can also be referred to as UE, access terminal, user unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. The terminals in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, and roadside units with terminal functions. The terminal can be an onboard unit (RSU), or a flight device (e.g., an intelligent robot, hot air balloon, drone, or airplane). The terminal in this application can also be an onboard module, onboard unit, onboard component, onboard chip, or onboard unit built into a vehicle as one or more components or units. The terminal can also be other devices with terminal functions; for example, it can be a device that performs terminal functions in D2D communication. The embodiments of this application do not limit the device form of the terminal; the device used to implement the terminal function can be a terminal itself; it can also be a device capable of supporting the terminal in implementing this function, such as a chip system. This device can be installed in the terminal or used in conjunction with the terminal. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices.

[0125] Network devices can be devices within an access network (AN), such as radio access network (RAN) devices. RAN devices can also be called access network devices. Access network devices can be devices with wireless transceiver capabilities, or they can be chips or chip systems embedded in the device, or devices that contain access network equipment. Access network devices are located in the access network (AN) of a communication system and are used to provide access services to terminals. Access network equipment can also include 5G, such as the next-generation node B (gNB) in a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a 5G base station, or network nodes constituting a gNB, transmission and reception point (TRP) or transmission point (TP), or transmission measurement function (TMF), such as a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), an RSU with base station functionality, or a wired access gateway, or core network elements of 5G, etc. Alternatively, access network equipment can also include: access points (APs) in Wi-Fi systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also known as small cells), relay stations, access points, wearable devices, vehicle-mounted equipment, etc. In future mobile communication systems, access network devices may have other naming methods, and this application does not impose any restrictions on this.

[0126] CU and DU can be configured separately or included in the same network element, such as a baseband unit (BBU). RU can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that network equipment can be CU nodes, DU nodes, or a combination of CU and DU nodes. Furthermore, CUs can be classified as network equipment within an AN or a network equipment within a CN; no restrictions are placed here.

[0127] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open radio access network (ORAN) system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0128] In this communication system, for periodically transmitted uplink data (such as uplink data for XR services), if different types of data in the uplink data are carried by at least two data streams (such as at least two QoS streams), the first device can jointly report the information of at least two data streams through uplink transmission information. In this way, the network device can not only configure transmission resources for the uplink data as a whole, such as periodic transmission resources, but also guarantee the transmission of at least two data streams separately, to meet the transmission needs of different types of data, making transmission more flexible. Furthermore, the first device can also report the status of data to be transmitted in the uplink data (such as each frame of data in an XR service) through indication information, such as the size of the data to be transmitted and the data stream carried by the data to be transmitted, so that the network device can schedule the transmission of the data to be transmitted in a timely manner, thus ensuring the transmission of the data stream.

[0129] Additionally, by setting the duration of the first timer to be longer than the transmission duration required for the dataset (such as each frame of data in an XR service) of the first device (such as the first duration), even if the dataset of the first device has not been transmitted after the first duration, the first device will continue to transmit the dataset of the first device as long as the first timer has not expired, thereby reducing the possibility of the dataset of the first device being discarded and ensuring the reliability and stability of the transmission.

[0130] It should be understood that the communication method provided in the embodiments of this application can be applied to... Figure 6 The devices shown, such as the first device and the network device, can be specifically implemented as described in the following method embodiments, which will not be repeated here. The solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0131] It should also be understood that Figure 6This is a simplified diagram for ease of understanding only. The communication system may also include other network devices and / or other terminal devices. Figure 6 It was not drawn in the middle.

[0132] The following will combine Figures 7-13 This paper details the interaction process between devices in the aforementioned communication system through specific method embodiments. The communication method provided in this application can be applied to the aforementioned communication system, such as the interaction between terminal devices and network devices, which will be described in detail below.

[0133] Figure 7 This is a flowchart illustrating the communication method. Figure 1 ,like Figure 7 As shown, this communication method enables the transmission of different types of data in the uplink to be carried onto at least two data streams, and the information from at least two data streams to be reported in the same uplink transmission information, so that the network side can still configure periodic transmission resources. Specifically, the process of this communication method is as follows:

[0134] S701, the first device acquires the uplink transmission information of the first device.

[0135] The uplink transmission information of the first device includes the transmission period of the uplink data and information about at least two data streams. "Uplink transmission information" is an exemplary designation; it may also be referred to as transmission information, indication information, uplink indication information, etc. Any information used to indicate uplink service characteristics can be understood as uplink transmission information and is included within the scope of this application.

[0136] Uplink data can be uplink data that needs to be transmitted periodically, or data that is periodically transmitted uplink. For example, uplink data for XR services, or uplink data for any other possible services, such as uplink data for regular video call services. Any periodic uplink data that transmits different types of data can be applied to the method of the embodiments of this application. Taking XR services as an example, the uplink data can be data from multiple consecutive frames of XR services, or data from multiple consecutive video frames.

[0137] The uplink data transmission period can be the duration between two uplink data transmissions. For example, if the frame rate of an XR service is 60fps, the uplink data transmission period is 1 / 60, approximately 16.67ms. In uplink transmission information, the uplink data transmission period can be indicated by the "data stream period" cell, or by a newly defined cell; there is no specific restriction.

[0138] The data stream can be a QoS stream, or any other possible stream, such as a transport stream, or any other possible representation, without any specific limitation. Any stream that can be used to carry data between a terminal and a network can be understood as the data stream described in this application. The information of at least two data streams includes the respective identifiers of at least two data streams, such as QFI or stream descriptions, or any other identifiers that can be used to indicate the data streams, in order to distinguish these at least two data streams by the identifiers and avoid confusion.

[0139] In the uplink data transmission, different types of data are carried across at least two data streams. These different types of data can be data with different formats or functions. For example, in XR services, different types of data can include I-frames and P-frames to ensure the reliability and flexibility of I-frame and P-frame transmission. Similarly, in regular video call services, different types of data can include video frames with associated audio information and video frames without associated audio information. It should be understood that "different types of data" is an illustrative description and can be replaced with "data with different formats or functions." Furthermore, due to differences in format or function, different types of data may have different levels of importance to the service. Therefore, "different types of data" can also be replaced with "data with different levels of importance," such as I-frames in XR services typically having higher importance than P-frames. The priorities of the at least two data streams can be different. For example, the data stream carrying more important data of different types can have a higher priority to ensure the transmission of more important data. Taking XR services as an example, I-frame data is carried across QoS stream #1, and P-frame data is carried across QoS stream #2. QoS stream #1 has a higher priority than QoS stream #2 to minimize the impact of I-frame loss on the normal playback of subsequent P-frames. Of course, the above example is based on the premise that QoS flow #1 has a higher priority than QoS flow #2. In this embodiment, the priority relationship between the QoS flow carrying I-frames and the QoS flow carrying P-frames may not be restricted.

[0140] In addition, uplink transmission information may also include other information about the uplink data, such as jitter intervals and burst arrival times. For details, please refer to the relevant introduction in "4. Uplink Transmission Information" above, which will not be repeated here. The transmission period and other information of the uplink transmission information can be associated with information from at least two data streams to indicate that even when different types of data are carried on at least two data streams, the overall uplink data is still periodically transmitted. It also indicates the specific details of the periodic transmission so that network devices can decide to allocate periodic transmission resources. For details, please refer to the relevant introduction in S703 below, which will not be repeated here.

[0141] For ease of understanding, an exemplary configuration for uplink information transmission can be shown below:

[0142]

[0143] It can be seen that when at least two data streams are two QoS streams, the identifiers of the two QoS streams are QFI1 and QFI2, respectively. QFI1 and QFI2 have relatively high cell levels. Jitter intervals (including the lower and upper boundaries) have cell levels below QFI1 and QFI2, indicating association with QFI1 and QFI2. Similarly, burst arrival time, data stream period, PDU set identifier, and PSI identifier also have cell levels below QFI1 and QFI2, indicating association with QFI1 and QFI2. In one possible implementation, the network side (such as the session management network element) can pre-configure the data streams carried by different types of data in the uplink data for the first device (i.e., the mapping relationship between different types of data in the uplink data and at least two data streams). Specific implementation details can be found in the relevant description below and will not be repeated here. Therefore, the first device can determine that different types of data in the uplink data of the service are carried to their respective corresponding data streams, totaling at least two data streams, based on the data type in the service's uplink data.

[0144] S702, the first device sends its uplink transmission information to the network device. The network device receives the uplink transmission information from the first device.

[0145] Uplink transmission information can be carried in RRC signaling, that is, by reusing existing signaling to reduce implementation difficulty, or it can be carried in newly defined signaling to decouple it from existing signaling. The transmission of uplink transmission information can be more flexible, and there are no restrictions on the specific implementation.

[0146] S703, the network device configures the uplink data transmission resources according to the uplink transmission information of the first device.

[0147] For example, the network device can send resource information to the first device based on the aforementioned uplink transmission information, and the first device can receive the resource information from the network device. The resource information can indicate transmission resources shared by at least two data streams, such as periodic transmission resources, to save resource overhead. Periodic transmission resources can be matched with the period of the uplink data, meaning that data to be transmitted within each period can use this transmission resource for transmission. For data of higher importance, the data stream it carries has a higher priority, so that it can be prioritized for transmission by the first device when competing for the transmission resource, thus ensuring the transmission of important data. Taking XR services as an example, QoS stream #1 has the highest priority; therefore, during the transmission of each I-frame, this transmission resource can be used preferentially by each I-frame to ensure the reliability of I-frame transmission. QoS stream #2 has a priority only lower than QoS stream #1; during the transmission of each P-frame, this transmission resource is also highly likely to be occupied by each P-frame to ensure the reliability of P-frame transmission as much as possible.

[0148] Alternatively, the network device can dynamically allocate transmission resources based on the aforementioned uplink transmission information, such as sending a DCI to the first device, which can indicate the transmission resources for the next cycle.

[0149] It is understandable that S703 is optional. For example, network devices can pre-configure uplink data transmission resources. The network devices can perform data transmission based on the uplink transmission information mentioned above. For example, if uplink data is received on the transmission resources, the network devices can map different types of uplink data to the corresponding data streams based on the uplink transmission information and then send them to the user plane nodes (such as user plane function (UPF) network elements).

[0150] In summary, for periodically transmitted uplink data, if different types of data within this uplink data are carried on at least two data streams, the first device can jointly report the information from the at least two data streams via uplink transmission information. In this way, the network device can not only configure transmission resources for the uplink data as a whole, such as periodic transmission resources, but also ensure the transmission of at least two data streams separately, thus meeting the individual transmission needs of different types of data and making transmission more flexible.

[0151] Optionally, in conjunction with the above S701-S703, the method further includes: the first device receiving configuration information from the session management network element.

[0152] The session management network element can be a session management function (SMF) network element, or in a future communication system, any network element that can be used to implement session management can be understood as the session management network element of this application. The session management network element serves the first device, such as providing services for the first device to establish / modify / release sessions.

[0153] The configuration information can be QoS rules, or any other information that can be named as such, without any restrictions.

[0154] Configuration information can indicate the data stream to which different types of data in the uplink are carried, or the data stream to which data of different importance in the uplink are carried. For example, configuration information can include information about at least two data streams, such as their respective identifiers and priorities. Configuration information can also include uplink data information, which can be a packet filter set containing characteristics of the uplink data, such as a 5-tuple (indicating the uplink data), and can also include new parameters, such as data type parameters / importance parameters, with different parameters representing different data types / importance levels. In the configuration information, different data type parameters / importance parameters in the packet filter set can associate information about different data streams; that is, there is a mapping relationship between data streams and data types / importance levels, indicating the data stream to which different types of data in the uplink are carried. For example, if type #1 / importance #1 in the packet filter set is associated with the identifier of data stream #1, it means that data of type #1 / importance #1 in the uplink data is carried to data stream #1. Similarly, if type #2 / importance #2 in the packet filter set is associated with the identifier of data stream #2, it means that data of type #2 / importance #2 in the uplink data is carried to data stream #2.

[0155] The session management network element can determine which new parameters to add to the packet filtering set based on the type of the aforementioned service. For example, the session management network element can determine which new parameters to add to the packet filtering set based on the service type being XR service. Alternatively, the session management network element can also obtain the new parameters from other network elements. For instance, the requester of the service, such as the application function (AF), can pass the new parameters to the policy control function (PCF) network element when the service is established / updated. The PCF network element can then include the new parameters in the service's policy and charging control (PCC) rules and send the PCC rules to the session management network element, which can then add the new parameters to the packet filtering set according to the PCC rules.

[0156] The session management network element can send configuration information to the first device during the process of establishing a session for the first device, or it can send configuration information to the first device at any other possible time, such as during session modification / update / release, without any specific restrictions.

[0157] It is understandable that the session management network element can be configured for the first device in an existing manner, that is, the packet filtering set in the configuration information does not need to carry the above-mentioned new parameters, and the first device can by default carry different types of data in the uplink data to at least two data streams.

[0158] Optionally, in conjunction with the above S701-S703, the method may further include:

[0159] Step 1: The first device sends its capability information to the network device, and the network device receives the capability information of the first device.

[0160] The capability information of the first device can be called UE Capability information, or any other possible name, without limitation. This capability information can indicate that the first device supports new capabilities, such as the ability to combine information from different data streams into a single uplink transmission information for reporting, or the ability to map different types of data in uplink data to different data streams. For example, the UE-NR-Capability of this capability information can include new information elements, such as multi-data stream capability, specifically multi-QoS flow capability (combine-qos-flow-capability) or any other name without limitation, to indicate that the first device supports the ability to combine information from different data streams into a single uplink transmission information for reporting.

[0161] The first device can independently report its capability information to the network device. For example, when the first device establishes an RRC connection with the network device, the first device sends RRC signaling to the network device through the RRC connection. The RRC signaling may contain the capability information of the first device, or the capability information of the first device may be carried in any other possible signaling. There are no restrictions on the specific implementation.

[0162] Alternatively, the first device can also report its capability information to the network device according to the network device's instructions. For example, the network device can send capability query information to the first device, and the first device can receive the capability query information from the network device. The capability query information can be used to query whether the first device supports new capabilities, such as the ability to combine information from different data streams into a single uplink transmission, or whether it supports the ability to map different types of data in the uplink data to different data streams. For example, when the first device establishes an RRC connection with the network device, the network device sends RRC signaling to the first device through this RRC connection. This RRC signaling can contain capability query information, or the capability query information can be carried in any other possible signaling; the specific implementation is not limited. Thus, the first device can send its capability information to the network device according to the capability query information to achieve on-demand capability reporting and avoid redundant reporting.

[0163] Step 2: The network device sends a response message to the first device, and the first device receives the response message from the network device.

[0164] The response information may indicate that the first device is permitted to use new capabilities, such as multi-QoS stream capabilities, which allow information from different data streams to be combined into a single uplink transmission message for reporting, or allow different types of data in the uplink data to be mapped to different data streams. In other words, the first device needs to use the capability as instructed by the network device to avoid data transmission errors, such as the network device being unable to configure appropriate transmission resources because it cannot recognize the information of different data streams.

[0165] The response information can be carried in existing signaling. For example, a new information element can be defined in the other configuration of the RRC to represent the response information. This information element can be a 1-bit information element, where 1 indicates that the first device is allowed to use the new capability, and 0 indicates that the first device is not allowed to use the new capability. Alternatively, the response information can also be carried in newly defined signaling, and there are no restrictions on the specific implementation.

[0166] Based on current resource availability and other factors, the network device can decide whether to allow the first device to use new capabilities, such as whether the network device supports the new capabilities. Specifically, it can be whether the network device supports processing new types of uplink transmission information, which may include uplink transmission information containing information from different data streams. If the network device supports the new capabilities, it can send response information to the first device.

[0167] It is understood that steps 1-2 are optional, or the first device may be required to support the new capability by default or predefined by the protocol.

[0168] The above combination Figure 7 The workflow of the communication method provided in the embodiments of this application is described below. Figure 8 The specific process of the communication method provided in the embodiments of this application is described in detail.

[0169] Figure 8 Flowchart of the communication method provided in the embodiments of this application Figure 2 . Figure 8 The process shown mainly involves the interaction between UE (such as the first device), RAN equipment (such as network equipment) and SMF network elements (such as session management network elements), and is introduced using XR service as an example.

[0170] Specifically, such as Figure 8 As shown, the flow of this communication method is as follows:

[0171] S801, the SMF network element sends QoS rules to the UE.

[0172] QoS rules can include a packet filtering set for XR services and information on multiple QoS flows. The packet filtering set can include a 5-tuple (a 5-tuple containing packets of I-frames and P-frames) and data type / importance parameters to indicate different types / importances of XR services, such as I-frames and P-frames being mapped / carried to different QoS flows.

[0173] It should be understood that the S801 can also refer to the relevant introduction in the "Configuration Information" section above, and will not be repeated here.

[0174] S802, the RAN device sends RRC signaling #1 to the UE.

[0175] S803, the UE sends RRC signaling #2 to the RAN device.

[0176] S804, the RAN device sends RRC configuration to the UE.

[0177] RRC signaling #1 can include capability query information to check whether the UE supports a new capability, such as the ability to combine information from different data streams into a single uplink transmission, or the ability to map different types of data in uplink data to different data streams. Correspondingly, RRC signaling #2 can include the UE's capability information to indicate whether the UE supports the new capability. RRC configuration can instruct the UE to use the new capability.

[0178] It is understandable that S802-S804 can also refer to the relevant introduction of steps 1-2 above, and will not be repeated here.

[0179] It is also understandable that the execution order between S802-S804 and S801 is not restricted.

[0180] S805, the UE determines, according to the QoS rules, that I-frames are carried to QoS stream #1 and P-frames are carried to QoS stream #2.

[0181] QoS flow #1 has a higher priority than QoS flow #2.

[0182] It is understandable that there are no restrictions on the execution order between S805 and S802-S804.

[0183] S806, the UE sends a UAI to the RAN device.

[0184] UAI includes uplink transmission information, which includes the QFI of QoS stream #1 and the QFI of QoS stream #2. The QFI of QoS stream #1 and the QFI of QoS stream #2 are associated with relevant information of the XR service in the uplink transmission information, such as burst arrival time, jitter interval, data stream period, etc.

[0185] Optionally, in S807, the RAN configures CG resources for the UE's XR services.

[0186] It is understandable that S805-S807 can also refer to the relevant introductions of S701-S703 mentioned above, and will not be repeated here.

[0187] S808, the UE uses CG resources to transmit XR service data.

[0188] For example, the UE uses CG resources to periodically transmit each video frame of the XR service.

[0189] Figure 9 This is a flowchart illustrating the communication method. Figure 3 ,like Figure 9 As shown, this communication method enables the first device to report the size of the data to be transmitted in real time, allowing the network side to flexibly schedule the transmission of the data and ensure transmission reliability. Specifically, the process of this communication method is as follows:

[0190] S901, the first device obtains instruction information from the first device.

[0191] The indication information indicates the size of the data to be transmitted in the uplink data of the first device.

[0192] The uplink data of the first device is periodically transmitted data. Different types of data in this uplink data are carried on at least two data streams. For specific implementation details, please refer to the relevant introduction of S701 above, which will not be repeated here.

[0193] The data to be transmitted can be a portion of the uplink data. Taking XR services as an example, the uplink data can be multiple consecutive frames, while the data to be transmitted can include at least one frame to ensure the reliability of each frame's transmission. The data to be transmitted can also be data that the first device is preparing to transmit. For example, the application layer of the first device (such as an application providing XR services) can generate the data that needs to be transmitted (such as at least one frame) and send it to the transport layer (such as the MAC layer). The transport layer can then place at least one frame in a buffer for queuing and transmission; in this case, the at least one frame can be the data to be transmitted. Alternatively, the data to be transmitted can also be data that the first device anticipates might be transmitted. For example, if the application layer has not yet generated the data to be transmitted, the size of the data to be transmitted can also be the size estimated by the first device, such as estimating the size based on the size of the data already transmitted / acquired in the uplink data. Taking XR services as an example, when transmitting an I-frame, the first device knows that the next few frames are P-frames, and can therefore estimate the size of the next P-frame to be transmitted based on the typical size of a P-frame. The size of the data to be transmitted can be represented by the number of units, such as 340 / 718 units or any other possible number of units. These units can be bits, bytes, kilobytes, or megabytes, and can be set according to the actual situation without limitation. Alternatively, the size of the data to be transmitted can also be represented by levels, with different levels corresponding to different numbers of units. For example, level #1 corresponds to 128 units, indicating that the maximum size of the data to be transmitted is 128 units; level #2 corresponds to 256 units, indicating that the maximum size of the data to be transmitted is 256 units; level #3 corresponds to 512 units, indicating that the maximum size of the data to be transmitted is 512 units. Other levels, or even more levels, are also possible without limitation.

[0194] The indication information also indicates the data stream carried by the data to be transmitted. For example, the indication information may include an identifier of the data stream carried by the data to be transmitted, so as to accurately indicate the data stream through the identifier and avoid confusion. For example, if the data stream is a QoS stream, the identifier of the data stream can be QFI. For specific implementation, please refer to the relevant introduction of S701 above, which will not be repeated here.

[0195] The first device can obtain the size of the data to be transmitted and the data stream carried by the data to be transmitted, thereby generating indication information.

[0196] S902, the first device sends instruction information to the network device. The network device receives the instruction information from the first device.

[0197] Indication information can be carried within MAC-CE signaling, reusing existing signaling, which reduces implementation complexity and is more standards-friendly. Alternatively, indication information can be carried within newly defined signaling, achieving decoupling from existing signaling and enabling more flexible transmission.

[0198] S903: Network devices schedule the transmission of data to be transmitted based on the instructions.

[0199] Network devices can set periodic semi-static scheduling parameters based on indication information, such as updating / reconfiguring periodic transmission resources, which can be matched with the period of uplink data. For example, network devices can determine the size of the data to be transmitted based on indication information, configure periodic transmission resources suitable for the size of the data to be transmitted, and send information indicating the periodic transmission resources to the first device. Alternatively, network devices can also dynamically schedule transmission resources based on indication information. For example, network devices can determine the size of the data to be transmitted and the data stream carried by the data to be transmitted based on indication information. In one possible approach, network devices can decide whether to guarantee the transmission of the data to be transmitted based on the current guarantee status of the data stream. For example, if the current guarantee status of the data stream is good, such as a very low packet loss rate, even if packet loss occurs in the data to be transmitted, it will not affect the overall guarantee of the data stream. Therefore, network devices can choose not to configure additional transmission resources for the transmission of the data to be transmitted. For example, if the current data stream is only adequately protected, such as the packet loss rate just meeting the packet loss rate threshold, the network device can choose to ensure the transmission of the data to be transmitted by configuring additional transmission resources for the transmission of the data to be transmitted, or by configuring transmission resources specifically for the transmission of the data to be transmitted, so as to ensure that the data to be transmitted can be transmitted successfully without packet loss.

[0200] In summary, for periodically transmitted uplink data, where different types of data in the uplink data are carried on at least two data streams, the first device can report the status of the data to be transmitted in the uplink data through indication information, such as the size of the data to be transmitted and the data stream carried by the data to be transmitted, so that the network device can schedule the transmission of the data to be transmitted in a timely manner and ensure the data stream.

[0201] Optionally, in conjunction with the above S901-S903, the method may further include:

[0202] Step A: The first device sends its capability information to the network device, and the network device receives the capability information of the first device.

[0203] The capability information of the first device can also be called UE capability information, or any other possible name, without any limitation. This capability information can indicate that the first device supports new capabilities, such as the ability to report the size of data to be transmitted periodically. For example, the UE NR capability in this capability information may include new information elements, such as reporting capabilities or any other name, without any limitation, to indicate that the first device supports the ability to report the size of data to be transmitted periodically.

[0204] The first device can independently report its capability information to the network device. The specific implementation is similar to "Step 1" above and can be understood by referring to it; it will not be repeated here. Alternatively, the first device can also report its capability information to the network device according to the network device's instructions. For example, the network device can first send capability query information to the first device. The first device receives the capability query information from the network device to query whether it supports new capabilities, such as the ability to report the size of periodically transmitted data. Correspondingly, the first device can send its capability information to the network device based on the capability query information to achieve on-demand capability reporting and avoid redundant reporting. The specific implementation is also similar to "Step 1" above and can be understood by referring to it; it will not be repeated here.

[0205] It should be understood that the capability query information is used to query whether the first device supports new capabilities. The first device can also report new capabilities other than the capability to report the size of the data to be transmitted periodically, without any specific restrictions.

[0206] Step B: The network device sends a response message to the first device, and the first device receives the response message from the network device.

[0207] The response information may indicate that the first device is allowed to use the new capability, namely, to report the size of the periodically transmitted data to be transmitted. In other words, the first device needs to use the capability as instructed by the network device. The specific implementation is similar to "Step 2" above, and can be understood by referring to it; it will not be repeated here. The network device may decide whether to allow the first device to use the new capability based on current resource conditions and other factors, such as whether the network device supports the new capability. Specifically, it may determine whether the network device supports processing new types of information reported by the terminal, which are information indicating the size of the periodically transmitted data to be transmitted. If the network device supports the new capability, it will send a response information to the first device.

[0208] It is understandable that steps A and B are optional, or the first device may be required to support the new capability by default or predefined by the protocol.

[0209] It is understandable that the above Figure 9 The method shown can also be used with Figure 7 The method shown decouples, for example, in Figure 9 In the method shown, different types of data in the upstream data can also be carried into the same data stream. Figure 9 The method shown is based on XR services. Any data with periodic transmission characteristics can be applied to this method. For example, in the field of perception, the heartbeat packets periodically sent by the first device can also be applied to the method of this application embodiment. For specific implementation, please refer to the above-mentioned related introduction, which will not be repeated here.

[0210] The above combination Figure 9 The workflow of the communication method provided in the embodiments of this application is described below. Figure 10 The specific process of the communication method provided in the embodiments of this application is described in detail.

[0211] Figure 10 Flowchart of the communication method provided in the embodiments of this application Figure 4 . Figure 10 The process shown mainly involves the interaction between the UE (such as the first device) and the RAN equipment (such as network equipment), and is introduced using XR services as an example.

[0212] Specifically, such as Figure 10 As shown, the flow of this communication method is as follows:

[0213] S1001, the RAN device sends RRC signaling #1 to the UE.

[0214] S1002, the UE sends RRC signaling #2 to the RAN device.

[0215] S1003, the RAN device sends RRC configuration to the UE.

[0216] RRC signaling #1 can include capability query information to check whether the UE supports a new capability, such as the ability to report the size of periodically transmitted data to be transmitted. Correspondingly, RRC signaling #2 can include the UE's capability information to indicate that the UE supports the new capability. RRC configuration can instruct the UE to use the new capability.

[0217] It is understandable that S1001-S1003 can also refer to the relevant introduction of steps 1-2 above, and will not be repeated here.

[0218] S1004, the UE determines the size of the k-th frame and the QoS flow carried by the k-th frame.

[0219] The UE can obtain the next frame (i.e., the size of the kth frame) from the application during the transmission of the current frame of the XR service (denoted as the (k-1)th frame, where k is an integer greater than 1). The UE can determine the QoS stream carried by the kth frame based on its type. For example, if the kth frame is an I-frame, it will be carried in QoS stream #1; or if the kth frame is a P-frame, it will be carried in QoS stream #2.

[0220] S1005, the UE sends a MAC-CE to the RAN device.

[0221] MAC-CE can indicate the size of the k-th frame and the QoS stream carried by the k-th frame, such as the QFI of QoS stream #1 / QoS stream #2.

[0222] S1006, RAN equipment is configured with dynamically scheduled transmission resources.

[0223] The RAN device can determine whether to configure dynamically scheduled transmission resources for the transmission of the k-th frame based on the received MAC-CE, such as configuring additional transmission resources for the transmission of the k-th frame, or configuring transmission resources specifically for the transmission of the k-th frame, without any specific restrictions.

[0224] It is understood that S1006 is optional. If the RAN device does not configure dynamically scheduled transmission resources for the transmission of the k-th frame, that is, does not execute S1006, the k-th frame can reuse the pre-configured CG resources for transmission.

[0225] It is understandable that S1004-S1006 can also refer to the relevant introductions of S901-S903 mentioned above, and will not be repeated here.

[0226] S1007, the UE sends the kth frame to the RAN device.

[0227] The UE can use pre-configured CG resources and / or dynamically scheduled transmission resources via S1006 to send the data of the k-th frame to the RAN device.

[0228] Figure 11 This is a flowchart illustrating the communication method. Figure 5 ,like Figure 11 As shown, this communication method enables network devices to configure a timer for data transmission with a duration longer than the original packet loss duration (as described below as the first duration). Even if the data has not been transmitted after the original packet loss duration has expired, the data will continue to be transmitted as long as the timer has not expired, thus ensuring the reliability of the transmission.

[0229] Specifically, the communication method's flow is as follows:

[0230] S1101, the network device determines the duration of the first timer.

[0231] The first timer can be used to determine whether the dataset of the first device needs to be discarded during transmission.

[0232] For example, if the dataset is not transmitted successfully before the first timer expires, it must be discarded; otherwise, the dataset can continue to be transmitted. The first timer can be an existing timer, such as a discard timer, or it can be a newly defined / designed timer, such as a timer set for a specific service. Taking XR services as an example, the first timer could be an XR service discard timer, or any other possible name; there are no specific restrictions.

[0233] The dataset of the first device can be any of the uplink datasets periodically transmitted by the first device. This periodically transmitted uplink dataset can be the uplink data mentioned above; that is, the transmission of uplink data can be done at the dataset granularity, with each dataset being sent periodically. For details, please refer to the relevant description in S701, which will not be repeated here. Taking XR services as an example, this dataset is the dataset of the XR service. For example, it can be the data of one frame of the XR service. The data contained in each I-frame or each P-frame can be considered a dataset. The dataset of the first device (such as a dataset) can include at least one set of data packets, such as a set of PDUs.

[0234] The timing duration of the first timer is greater than the first duration.

[0235] The first duration can be the required transmission time for the dataset of the first device, indicating that the dataset of the first device needs to be transmitted within the first duration. For example, the first duration can be PSDB. That is to say, in existing transmission mechanisms, the timing duration of the discard timer is usually PSDB, meaning that if the dataset of the first device is not transmitted within PSDB, the dataset needs to be discarded. However, since the timing duration of the first timer exceeds the original time required for the dataset of the first device to be discarded (i.e., PSDB), even if PSDB times out, the dataset can still continue to be transmitted, thereby reducing the possibility of the dataset being discarded.

[0236] For example, the timing duration of the first timer can be greater than the period of the uplink dataset (i.e., the transmission period of the uplink data), such as the duration between every two datasets. The timing duration of the first timer can be the sum of the first duration and the period of the uplink dataset, or it can be other durations, such as the sum of the first duration and 1 / 2 or 2 / 3 of the period of the uplink dataset; there are no specific restrictions. In other words, the timing duration of the first timer can not exceed two periods of the uplink dataset. Even if the transmission time of the dataset from the first device exceeds the first duration, the dataset should be transmitted as completely as possible within the next period to avoid the dataset becoming invalid due to excessive transmission time.

[0237] Network devices can determine the duration of the first timer themselves, or the core network element can indicate the duration of the first timer to avoid the overhead caused by the network device determining the duration itself. The following sections will describe the different scenarios.

[0238] Scenario 1:

[0239] The network device can determine the timing duration of the first timer based on the first duration.

[0240] For example, a network device can obtain the first duration and the period of the uplink dataset. Taking XR services as an example, the network device can obtain the PSDB of the XR service, i.e., the first duration, from the configuration information of the XR service (such as QoS configuration). The network device can also obtain the transmission period, i.e., the period of the uplink dataset, from the uplink transmission information reported by the first device. The network device can determine the timing duration of the first timer by summing the first duration and the period of the uplink dataset. Optionally, if the first timer is a newly defined / designed timer, the network device can also determine the timing duration of the second timer. The second timer can be a discarded timer, and the timing duration of the second timer can be the first duration, i.e., the PSDB.

[0241] Scenario 2:

[0242] Network devices can receive configuration information from session management network elements.

[0243] The session management network element can be an SMF network element, or in a future communication system, any network element that can be used to implement session management can be understood as the session management network element of this application. The session management network element serves the first device, such as providing services for the first device to establish / modify / release sessions.

[0244] The configuration information can indicate the second duration.

[0245] The second duration can be a new packet loss duration, different from the original packet loss duration. This new duration is longer than the original packet loss duration, meaning it is longer than the first duration. This indicates that if the dataset from the first device is not transmitted within the second duration, the dataset needs to be discarded. It could be called a discarded PSDB or any other possible name; there are no restrictions. The second duration is longer than the first duration, and it can also be longer than the period of the upstream dataset. For example, the second duration can be the sum of the first duration and the period of the upstream dataset, or it can be any other duration, such as the sum of the first duration and 1 / 2 or 2 / 3 of the period of the upstream dataset; there are no specific restrictions.

[0246] The configuration information can be QoS configuration or any other possible configuration information, without any restrictions. Taking QoS configuration as an example, the second duration can replace an existing QoS parameter in the configuration information. For example, the first duration originally indicated by the configuration information (such as PSDB, i.e., an existing QoS parameter) is replaced with the second duration (such as a discarded PSDB), which means extending the duration of PSDB. Alternatively, the second duration can also be a newly added parameter in the configuration information as a new QoS parameter. In this case, the configuration information can indicate not only the second duration but also the first duration.

[0247] The session management element can obtain the second duration from other network elements and incorporate it into its configuration information. For example, the AF (Active Filter) can inform the PCF (Process Control Filter) of the second duration during service establishment / update. The PCF can then update the PCC (Process Control Code) rules for that service with this second duration and send the PCC rules to the session management element. The session management element can then obtain the second duration based on the PCC rules and incorporate it into its configuration information. Thus, the network device can determine the second duration as the timing duration of the first timer.

[0248] Optionally, if the configuration information also indicates a first duration, and the first timer is a newly defined / designed timer, then the network device can also determine the first duration as the timing duration of the second timer (an existing discard timer).

[0249] S1102, the network device configures the timing duration of the first timer for the first device, and correspondingly, the first device determines the timing duration of the first timer.

[0250] In one possible implementation, the first timer is a discard timer. The network device can send information about the first timer to the first device, and the first device can receive this information. The information about the first timer indicates its duration. This information can be carried in RRC signaling, i.e., reusing existing signaling to reduce implementation difficulty, or it can be carried in newly defined signaling, decoupled from existing signaling; the specific implementation is not limited. Therefore, the first device can determine the duration of the first timer based on its information. In other words, the duration of the first timer is configured on demand by the network side, which avoids affecting the reliability of data transmission if the duration determined by the first device cannot meet the network side's requirements.

[0251] Alternatively, in another possible implementation, the first timer is an XR service discard timer. The network device can send information about the first timer to the first device, and it can also send information about a second timer to the first device. The first device can also receive information about the second timer from the network device. The second timer can be a discard timer. The information about the second timer can indicate its duration, such as a first duration. The information about the second timer and the first timer can be carried in the same signaling, or they can be transmitted separately, such as the second timer information being carried separately in an RRC signaling or a newly defined signaling; the specific implementation is not limited. Therefore, the first device can determine the duration of the second timer based on its information.

[0252] It should be understood that the first device determining the timing duration of the first timer can also be understood as the first device acquiring / knowing / being aware of the timing duration of the first timer.

[0253] S1103, when the first device starts transmitting the dataset, the first device starts the first timer.

[0254] The timing for starting the transmission of the dataset from the first device can be either when the dataset is placed in the buffer of the first device awaiting transmission, or when the transmission of the dataset begins; there is no specific limitation. Optionally, if the network device is configured with a second timer, the first device can also start the second timer when the transmission of the dataset from the first device begins.

[0255] S1104, if the first device's dataset has not been transmitted before the first timer expires, the first device discards the dataset.

[0256] The first device may discard any untransmitted data in the dataset, or it may discard the entire dataset; there is no specific limitation.

[0257] The first device is configured with a first timer (such as a discard timer), and the first device can determine whether to discard the dataset of the first device based on whether the discard timer has timed out.

[0258] Alternatively, the first device can be configured with a first timer (e.g., an XR service discard timer) and a second timer (e.g., a discard timer). In this case, the first device can determine whether to discard its dataset based on whether the XR service discard timer has expired. That is, if the transmission time of the dataset exceeds a certain duration (i.e., the discard timer expires), but the XR service discard timer has not yet expired, the first device does not process the data and continues transmitting its dataset. As long as the dataset is transmitted before the XR service discard timer expires, it can still be used to implement other functions. For example, in XR services, the data of the previous frame often affects the playback of the next / multiple frames. By setting the duration of the first timer to be greater than the first duration, it can be ensured that even if the data transmission of the previous frame times out (greater than the first duration), as long as the first timer has not expired, the data of that frame can still be transmitted completely, without affecting the playback of the next / multiple frames, thus improving the user experience. If the XR service discard timer expires and the first device's dataset has not been transmitted, then the first device discards its dataset.

[0259] In summary, by setting the duration of the first timer to be longer than the duration required for the data transmission of the first device (such as the first duration), even if the data transmission of the first device exceeds the first duration, the first device will continue to transmit the data of the first device as long as the first timer does not expire, thereby reducing the possibility of the data of the first device being discarded and ensuring the reliability and stability of the transmission.

[0260] Optionally, in conjunction with the above S1101-S1104, the method may further include:

[0261] Step x1: The first device determines the threshold duration.

[0262] The threshold duration can be applied to the first timer, such as representing a threshold indicating the remaining defined duration of the first timer. Reaching this threshold typically requires triggering a DSR. For example, if the network device configures a first timer only for the first device (e.g., indicating the timing duration of the first timer), the first timer can be the aforementioned discard timer, and the threshold duration can represent a threshold indicating the remaining defined duration of the discard timer. As another example, if the network device configures a first timer and a second timer for the first device (e.g., indicating the timing duration of the first and second timers respectively), then the first timer can be the aforementioned XR service discard timer, the second timer can be a discard timer, and the threshold duration can represent a threshold indicating the remaining defined duration of the XR service discard timer.

[0263] The threshold duration can be a remaining time threshold (remainTimeThreshold) or any other possible name; there are no restrictions on its specific designation. In one implementation, the threshold duration can be a specific duration, such as 12ms or 15ms, or it can be represented as a proportion of the defined duration of the first timer, such as 3 / 4 or 2 / 3 of the defined duration of the first timer; the specific implementation method is not limited. The difference between the threshold duration and the timing duration of the first timer is less than the first duration (e.g., PSDB), meaning that DSR needs to be triggered before PSDB expires. For example, if the timing duration of the first timer is 20ms and the first duration is 10ms, the threshold duration can be between 10ms and 20ms, such as 15ms. When the remaining defined duration of the first timer is 15ms, the threshold is reached, triggering DSR. At this point, there are still 5ms left before PSDB expires. The network device can use these 5ms to schedule the transmission of any untransmitted data in the first device's dataset as quickly as possible, in order to complete the transmission before PSDB expires.

[0264] The threshold duration can be determined by the network device itself, or it can be configured to the network device by the session management network element. This application embodiment does not restrict how the session management network element determines the threshold duration; it can be provided by the AF (Automatic Information Center) or determined by the session management network element itself. Based on this, the network device can send information indicating the threshold duration (such as RRC signaling or newly defined signaling carrying this information) to the first device, and the first device can receive the information indicating the threshold duration from the network device to determine the threshold duration.

[0265] It should be understood that the threshold determination time of the first device can also be understood as the threshold acquisition / knowledge / awareness time of the first device.

[0266] Step x2: When the remaining defined duration of the first timer reaches the threshold duration, the first device sends an indication message to the network device.

[0267] The indication information can indicate the data that has not been transmitted in the dataset of the first device. The indication information can be carried in the DSR. The first device sending the indication information to the network device can also be understood as triggering the DRS, so that the network device can be aware of the current transmission status and thus perform timely scheduling to ensure that the dataset of the first device can be transmitted as soon as possible and avoid transmission timeout (such as exceeding the PSDB). For specific implementation, please refer to the relevant introduction in "5. DSR" above, which will not be repeated here.

[0268] It is understood that the above example uses the threshold duration as an example of the first timer. Optionally, when the network device configures the first timer and the second timer for the first device, the threshold duration can also be applied to the second timer, that is, the timer can be discarded. For example, when the first device starts transmitting the dataset, the first device can also start the second timer, and when the remaining defined duration of the second timer reaches the threshold duration, the first device sends an indication message to the network device to trigger the DSR.

[0269] It is understandable that the above Figure 11 The methods shown can be implemented alone, or they can be combined with... Figure 7 and / or Figure 9 The methods shown can be implemented in combination, and there are no specific limitations. Furthermore, the above... Figure 11 The method shown is based on XR services. This method can be applied to any data that requires delay and packet loss. For specific implementation details, please refer to the above introduction.

[0270] The above combination Figure 11 The workflow of the communication method provided in the embodiments of this application is described below. Figures 12-13 The specific process of the communication method provided in the embodiments of this application is described in detail.

[0271] Figure 12 Flowchart of the communication method provided in the embodiments of this application Figure 6 . Figure 12 The process shown mainly involves the interaction between UE (such as the first device), RAN equipment (such as network equipment) and SMF network elements (such as session management network elements), and is introduced using XR service as an example.

[0272] Specifically, such as Figure 12 As shown, the flow of this communication method is as follows:

[0273] S1201, the SMF network element sends QoS configuration to the RAN device.

[0274] QoS configuration can include QoS parameters for XR services, such as PSDB (e.g., first duration) and dropped PSDB (second duration).

[0275] It should be understood that S1201 can also refer to the relevant introduction in "Situation 2" above, and will not be repeated here.

[0276] S1202, the RAN device determines the timing duration and threshold duration of the discard timer.

[0277] The timing duration of the discarded timer (such as the first timer) can be a second duration, as detailed in the relevant introduction of S1101 above, and will not be repeated here. The difference between the second duration and the threshold duration is less than the first duration, as detailed in the relevant introduction of steps x1-x2 above, and will not be repeated here.

[0278] S1203, the RAN device sends RRC configuration #1 to the UE.

[0279] RRC configuration #1 can indicate the duration of the timer to be discarded. For details, please refer to the relevant introduction of S1102 above, which will not be repeated here.

[0280] S1204, the RAN device sends RRC configuration #2 to the UE.

[0281] RRC configuration #2 can indicate the threshold duration. For details, please refer to the relevant introductions of steps x1-x2 above, which will not be repeated here.

[0282] In addition, RRC configuration #1 and RRC configuration #2 can also be the same information.

[0283] S1205, when the UE starts transmitting a frame of XR service data, it starts a discard timer.

[0284] It is understandable that S1205 can refer to the relevant introduction of S1103 above, and will not be repeated here.

[0285] S1206, the remaining timer duration is discarded when the threshold duration is reached, and the UE triggers DSR.

[0286] It is understood that S1206 can refer to the relevant descriptions of steps x1-x2 above, and will not be repeated here. S1206 is optional. If the UE completes the transmission of one frame of data for the above XR service before the remaining timeout duration of the discard timer reaches the threshold duration, DSR will not be triggered, and S1206 will not be executed.

[0287] S1207 If a frame of XR service data has not been transmitted before the discard timer expires, the UE discards the frame of data.

[0288] It is understandable that S1207 can be referred to in the relevant introduction of S1104 above, and will not be repeated here. S1207 is optional. If the UE completes the transmission of one frame of the XR service before the discard timer expires, then S1207 will not be executed.

[0289] Figure 13 Flowchart of the communication method provided in the embodiments of this application Figure 7 . Figure 13The process shown mainly involves the interaction between the UE (such as the first device) and the RAN equipment (such as network equipment), and is introduced using XR services as an example.

[0290] Specifically, such as Figure 13 As shown, the flow of this communication method is as follows:

[0291] S1301, the RAN equipment determines the timing duration of the XR service discard timer, the timing duration of the discard timer, and the threshold duration.

[0292] The timing duration of the XR service discard timer (such as the first timer) can be longer than the first duration, and the timing duration of the discard timer (such as the second timer) can be the first duration. Please refer to the relevant description in S1101 above for details. The threshold duration can be applied to the second timer, such as if it is shorter than the timing duration of the second timer.

[0293] S1302, the RAN device sends RRC configuration #1 to the UE.

[0294] RRC configuration #1 can indicate the duration of the XR service discard timer. For details, please refer to the relevant introduction of S1102 above, which will not be repeated here.

[0295] S1303, the RAN device sends RRC configuration #2 to the UE.

[0296] RRC configuration #2 can indicate the timing duration and threshold duration of the discard timer, indicating that the threshold duration applies to the discard timer.

[0297] S1304, When the UE starts transmitting a frame of data for the XR service, it starts the XR service discard timer and the discard timer.

[0298] It is understandable that S1304 is similar to S1103 above, and can be understood by referring to it, so it will not be repeated here.

[0299] S1305, the remaining timer duration is discarded when the threshold duration is reached, and the UE triggers DSR.

[0300] S1305 is optional. If the UE transmits a frame of data for the above-mentioned XR service before the remaining timeout duration of the discard timer reaches the threshold duration, DSR will not be triggered and S1305 will not be executed.

[0301] S1306, UE determines that the discard timer has timed out.

[0302] S1307 If a frame of XR service data has not been transmitted before the XR service discard timer expires, the UE discards the frame of data.

[0303] S1307 is optional. If the UE completes the transmission of one frame of the XR service before the discard timer expires, then S1307 will not be executed. It can be understood that S1306-S1307 can be referred to the relevant introduction of S1104 above, and will not be repeated here.

[0304] The above combination Figures 7-13 The communication method provided in the embodiments of this application is described in detail below. Figure 14 and Figure 15 This document describes in detail the communication apparatus used to perform the communication method provided in the embodiments of this application.

[0305] For example, Figure 14 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 1 .like Figure 14 As shown, the communication device 1400 includes a processing module 1401 and a transceiver module 1402. For ease of explanation, Figure 14 Only the main components of the communication device are shown.

[0306] In some embodiments, the communication device 1400 may be adapted to Figure 5 In the communication system shown, the execution Figures 7-13 The function of the first device in the communication method shown.

[0307] The transceiver module 1402 is used to perform the transceiver function of the first device.

[0308] The processing module 1401 is used to perform functions of the first device other than the transmitting and receiving functions.

[0309] Optionally, the communication device 1400 may also include a storage module. Figure 14 (Not shown in the image), this storage module stores programs or instructions. When the processing module 1401 executes the program or instructions, it enables the communication device 1400 to perform operations. Figures 7-13 The function of the first device in the communication method shown.

[0310] It should be understood that the processing module 1401 involved in the communication device 1400 can be implemented by a processor or processor-related circuit components, and can be a processor or processing unit; the transceiver module 1402 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver unit.

[0311] Furthermore, the communication device 1400 may be the first device, or a chip (system) or other component or assembly disposed in the aforementioned first device, or a device containing the first device; this application embodiment does not limit this. The technical effects of the communication device 1400 can be referred to separately. Figures 7-13 The technical effects of any of the communication methods shown in the examples are not elaborated here.

[0312] In other embodiments, the communication device 1400 may be adapted to Figure 5 In the communication system shown, the execution Figures 7-13 The function of the network device in the communication method shown.

[0313] The transceiver module 1402 is used to perform the transceiver functions of the network device.

[0314] The processing module 1401 is used to perform functions of the network device other than the sending and receiving functions.

[0315] Optionally, the communication device 1400 may also include a storage module. Figure 14 (Not shown in the image), this storage module stores programs or instructions. When the processing module 1401 executes the program or instructions, it enables the communication device 1400 to perform operations. Figures 7-13 The functions of the network devices in the communication method shown.

[0316] It should be understood that the processing module 1401 involved in the communication device 1400 can be implemented by a processor or processor-related circuit components, and can be a processor or processing unit; the transceiver module 1402 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver unit.

[0317] Furthermore, the communication device 1400 may be a network device, a chip (system) or other component or assembly disposed within the aforementioned network device, or a device containing the network device; this application embodiment does not limit this. The technical effects of the communication device 1400 can be referred to separately. Figures 7-13 The technical effects of any of the communication methods shown in the examples are not elaborated here.

[0318] For example, Figure 15 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 The communication device can be a terminal device or a network device, or it can be a chip (system) or other component or assembly that can be installed in the terminal device or network device. For example... Figure 15 As shown, the communication device 1500 may include a processor 1501. Optionally, the communication device 1500 may also include a memory 1502 and / or a transceiver 1503. The processor 1501 is coupled to the memory 1502 and the transceiver 1503, for example, they may be connected via a communication bus.

[0319] The following is combined Figure 15 A detailed description of each component of the communication device 1500 is provided below:

[0320] The processor 1501 is the control center of the communication device 1500. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1501 can be one or more CPUs, an ASIC, or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more FPGAs.

[0321] Optionally, the processor 1501 can perform various functions of the communication device 1500 by running or executing software programs stored in the memory 1502 and calling data stored in the memory 1502.

[0322] In a specific implementation, as one example, the processor 1501 may include one or more CPUs, for example... Figure 15 CPU0 and CPU1 are shown in the diagram.

[0323] In a specific implementation, as one example, the communication device 1500 may also include multiple processors, for example... Figure 15 The processors 1501 and 1504 are shown. Each of these processors can be a single-core processor or a multi-core processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0324] The memory 1502 is used to store the software program that executes the solution of this application, and is controlled by the processor 1501 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0325] Optionally, the memory 1502 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1502 may be integrated with the processor 1501 or may exist independently, and may be connected via the interface circuit of the communication device 1500. Figure 15 (Not shown in the image) is coupled to processor 1501, and this embodiment of the application does not specifically limit this.

[0326] Transceiver 1503 is used for communication with other communication devices. For example, if communication device 1500 is a terminal device, transceiver 1503 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1500 is a network device, transceiver 1503 can be used to communicate with a terminal device or with another network device.

[0327] Alternatively, transceiver 1503 may include a receiver and a transmitter. Figure 15 (Not shown separately). The receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.

[0328] Alternatively, the transceiver 1503 can be integrated with the processor 1501, or it can exist independently and be connected via the interface circuit of the communication device 1500. Figure 15 (Not shown in the image) is coupled to processor 1501, and this embodiment of the application does not specifically limit this.

[0329] It should be noted that, Figure 15 The structure of the communication device 1500 shown does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0330] Furthermore, the technical effects of the communication device 1500 can be referred to the technical effects of the communication method described in the above method embodiments, and will not be repeated here.

[0331] It should be understood that the processor in the embodiments of this application can be a CPU, but it can also be other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0332] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), EEPROM, or flash memory. Volatile memory can be RAM, which is used as an external cache. 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 (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0333] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments 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 instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0334] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0335] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0336] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

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

[0338] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

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

[0341] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0342] If the aforementioned functions are implemented as 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 this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0343] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method includes: Acquire uplink transmission information of the first device; the uplink transmission information of the first device includes the transmission period of uplink data and information of at least two data streams, wherein different types of data in the uplink data are respectively carried to the at least two data streams; Send the uplink transmission information of the first device to the network device.

2. The method according to claim 1, characterized in that, The information of the at least two data streams includes the identifiers of the at least two data streams.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Send capability information of the first device to the network device, the capability information indicating that the first device supports the ability to combine information from different data streams into a single uplink transmission information for reporting; The device receives a response message from the network device, the response message indicating that the first device is allowed to combine information from different data streams into a single uplink transmission message for reporting.

4. The method according to claim 3, characterized in that, The method further includes: The first device receives capability query information from the network device, the capability query information being used to query whether the first device supports the ability to combine information from different data streams into a single uplink transmission information for reporting. Sending the capability information of the first device to the network device includes: Based on the capability query information, the capability information is sent to the network device.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: The system receives configuration information from a session management network element that serves the first device. The configuration information indicates the data stream to which different types of data in the uplink data are carried.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Based on the data type in the upstream data of the business, it is determined that different types of data in the upstream data are carried to their respective corresponding data streams.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Receive resource information from the network device, the resource information indicating the transmission resources shared by the at least two data streams.

8. The method according to any one of claims 1-7, characterized in that, The uplink data is the uplink data for extended reality (XR) services, and the different types of data include I-frames and P-frames of the XR services.

9. A communication method, characterized in that, Applied to network devices, the method includes: Receive uplink transmission information from a first device, the uplink transmission information of the first device including the transmission period of uplink data and information of at least two data streams, wherein different types of data in the uplink data are respectively carried to the at least two data streams; Configure the transmission resources for the uplink data based on the uplink transmission information from the first device.

10. The method according to claim 9, characterized in that, The information of the at least two data streams includes the identifiers of the at least two data streams.

11. The method according to claim 9 or 10, characterized in that, The step of configuring the uplink data transmission resources according to the uplink transmission information of the first device includes: Based on the uplink transmission information of the first device, resource information is sent to the first device, wherein the resource information indicates the transmission resources shared by the at least two data streams.

12. The method according to any one of claims 9-10, characterized in that, The method further includes: Receive capability information of the first device, the capability information indicating that the first device supports the ability to combine information from different data streams into a single uplink transmission information for reporting. Based on the capability information, a response message is sent to the first device, the response message indicating that the first device is allowed to combine information from different data streams into a single uplink transmission message for reporting.

13. The method according to claim 12, characterized in that, The method further includes: A capability query message is sent to the first device, the capability query message being used to query whether the first device supports the capability to combine information from different data streams into a single uplink transmission message for reporting.

14. The method according to any one of claims 9-13, characterized in that, The uplink data is the uplink data for extended reality (XR) services, and the different types of data include I-frames and P-frames of the XR services.

15. A communication method, characterized in that, The method includes: The timing duration of the first timer is determined. The timing duration of the first timer is longer than the first duration. The data set of the first device needs to be transmitted within the first duration. The first timer is started when the data set is transmitted. If the dataset is not transmitted before the first timer expires, the dataset is discarded.

16. The method according to claim 15, characterized in that, The dataset is any one of the uplink datasets periodically transmitted by the first device, and the timing duration of the first timer is greater than the period of the uplink dataset.

17. The method according to claim 16, characterized in that, The timing duration of the first timer is the sum of the first duration and the period of the uplink dataset.

18. The method according to any one of claims 15-17, characterized in that, The dataset includes at least one set of Protocol Data Units (PDUs), and the first duration is the PDU set latency budget (PSDB).

19. The method according to any one of claims 15-18, characterized in that, The method further includes: Receive information from the first timer of the network device, wherein the information of the first timer indicates the timing duration of the first timer; Determining the timing duration of the first timer includes: Based on the information from the first timer, determine the timing duration of the first timer.

20. The method according to any one of claims 15-19, characterized in that, The method further includes: Determine the threshold duration; If the remaining defined duration of the first timer reaches the threshold duration, an indication message is sent to the network device, the indication message indicating the data in the dataset that has not been transmitted.

21. The method according to any one of claims 15-20, characterized in that, The dataset is a frame of data from an extended reality XR service.

22. A communication method, characterized in that, Applied to network devices, the method includes: The timing duration of the first timer is determined. The timing duration of the first timer is longer than a first duration. The dataset of the first device needs to be transmitted within the first duration. If the dataset is not transmitted when the first timer expires, the dataset needs to be discarded. Configure the timing duration of the first timer for the first device.

23. The method according to claim 22, characterized in that, The method further includes: The system receives configuration information from a session management network element, which serves the first device. The configuration information indicates a second duration, which is longer than the first duration. Determining the timing duration of the first timer includes: The second duration is determined as the timing duration of the first timer.

24. The method according to claim 22 or 23, characterized in that, The step of configuring the timing duration of the first timer for the first device includes: The information of the first timer is sent to the first device, and the information of the first timer indicates the timing duration of the first timer.

25. The method according to any one of claims 22-24, characterized in that, The dataset includes at least one set of Protocol Data Units (PDUs), and the first duration is the PDU set latency budget (PSDB).

26. The method according to any one of claims 22-25, characterized in that, The dataset is a frame of data from an extended reality XR service.

27. A communication device, characterized in that, The communication device is used to perform the method as described in any one of claims 1-26.

28. A communication device, characterized in that, include: Processor and memory; The memory is used to store computer instructions, which, when executed by the processor, cause the communication device to perform the method as described in any one of claims 1-26.

29. A communication device, characterized in that, include: Processor and interface circuits; among which, The interface circuit is used to receive code instructions and transmit them to the processor; The processor is used to run the code instructions to perform the method as described in any one of claims 1-26.

30. A communication device, characterized in that, The communication device includes a processor and a transceiver, the transceiver being used for information exchange between the communication device and other communication devices, and the processor executing program instructions to perform the method as described in any one of claims 1-26.

31. The communication device according to any one of claims 27-30, characterized in that, The communication device is a chip.

32. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-26.

33. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-26.

Images