Communication method, device and system

Abstract

The embodiment of the invention provides a communication method, device and system, and a terminal device can select a QoS flow with a longer duration of a corresponding non-active period so as to improve the energy-saving effect of access network equipment. The method comprises: a terminal device obtaining a first non-active period parameter and a second non-active period parameter, the first non-active period parameter corresponding to a first quality of service (QoS) flow between the terminal device and a user plane network element, the second non-active period parameter corresponding to a second QoS flow between the terminal device and the user plane network element, the duration of the first non-active period indicated by the first non-active period parameter is greater than the duration of the second non-active period indicated by the second non-active period parameter; the terminal device determines the first QoS flow for downlink data transmission; the terminal device sends first information, wherein the first information is used for identifying the first QoS flow; and the terminal device monitors a channel between the terminal device and the access network equipment to receive downlink data at a time outside the first non-active period.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, and in particular to a communication method, device and system. BACKGROUND

[0002] In order to reduce energy consumption, the terminal device and the access network device can use cell discontinuous transmission (DTX) technology to transmit data of one or more services. For example, the access network device can configure a cell DTX period for the terminal device, as shown in Figure 1 One cell DTX period includes an active period and a non-active period. In the active period, the terminal device monitors the physical downlink control channel (PDCCH), so the access network device can send information indicating the resource through the PDCCH to the terminal device in the active period after allocating the resource for the data to be transmitted. After receiving the information on the PDCCH, the terminal device can transmit data on the resource indicated by the information. In the non-active period, the terminal device does not monitor the PDCCH, and the access network device can achieve energy saving at the cost of transmission delay of data if it does not send any information through the PDCCH.

[0003] In the prior art, the access network device usually configures a cell DTX period according to the requirements of services sensitive to transmission delay, and applies the period to data transmission of different services, which leads to poor energy saving effect of the access network device. SUMMARY

[0004] Embodiments of the present application provide a communication method, device and system for improving the energy saving effect of the access network device.

[0005] To achieve the above-mentioned purpose, embodiments of the present application adopt the following technical solutions:

[0006] In a first aspect, a communication method is provided. The apparatus performing the communication method can be a terminal device, or a module (e.g., a chip or a chip system) applied in the terminal device. Hereinafter, the terminal device is taken as an example for description. The communication method includes: obtaining, by the terminal device, a first inactivity period parameter and a second inactivity period parameter, the first inactivity period parameter corresponding to a first quality of service (QoS) flow between the terminal device and a user plane network element, the second inactivity period parameter corresponding to a second QoS flow between the terminal device and the user plane network element, a time length of a first inactivity period indicated by the first inactivity period parameter being greater than a time length of a second inactivity period indicated by the second inactivity period parameter; determining, by the terminal device, that the first QoS flow is used for downlink data transmission; sending, by the terminal device, first information, the first information being used for identifying the first QoS flow; and monitoring, by the terminal device, a channel between the terminal device and an access network device at a time other than the first inactivity period to receive downlink data.

[0007] In the communication method provided in the embodiments of the present application, when the time length of the first inactivity period is greater than the time length of the second inactivity period, the terminal device can determine that the first QoS flow, instead of the second QoS flow, is used for downlink data transmission. That is, the terminal device can select the QoS flow corresponding to the longer time length of the inactivity period, instead of the QoS flow corresponding to the shorter time length of the inactivity period, to improve the energy saving effect of the access network device.

[0008] With reference to the first aspect above, in a possible implementation, the first inactivity period includes all or part of a time period of the second inactivity period. In this scheme, the first inactivity period and the second inactivity period overlap in a time period, and the overlapping time period can be all or part of the time period of the second inactivity period.

[0009] With reference to the first aspect above, in a possible implementation, a starting time of the first inactivity period is the same as a starting time of the second inactivity period. In this scheme, the overlapping time period of the first inactivity period and the second inactivity period can be all of the time period of the second inactivity period.

[0010] With reference to the first aspect above, in a possible implementation, an ending time of the first inactivity period is the same as an ending time of the second inactivity period. In this scheme, the overlapping time period of the first inactivity period and the second inactivity period can be all of the time period of the second inactivity period.

[0011] In a possible implementation of the first aspect, the time other than the first inactivity period comprises all or part of the time period other than the first inactivity period. In this solution, the terminal device can monitor the channel in all or part of the time period other than the first inactivity period. When the terminal device monitors the channel in all of the time period other than the first inactivity period, the monitoring time is longer, so as to avoid missing receiving information. When the terminal device monitors the channel in part of the time period other than the first inactivity period, the monitoring time is shorter, so as to save the power consumption of the terminal device.

[0012] In a possible implementation of the first aspect, the time other than the first inactivity period comprises all or part of the time period in the active period corresponding to the first QoS flow. In this solution, the terminal device can monitor the channel in all or part of the time period in the active period corresponding to the first QoS flow. When the terminal device monitors the channel in all of the time period in the active period corresponding to the first QoS flow, the monitoring time is longer, so as to avoid missing receiving information. When the terminal device monitors the channel in part of the time period in the active period corresponding to the first QoS flow, the monitoring time is shorter, so as to save the power consumption of the terminal device.

[0013] In a possible implementation of the first aspect, the time length of the active period corresponding to the first QoS flow is the same as the time length of the active period corresponding to the second QoS flow.

[0014] In a possible implementation of the first aspect, the channel is used to carry downlink control information, and the downlink control information is used to indicate the resource of the downlink data transmission. In this solution, the terminal device can obtain the downlink control information by monitoring the channel, and then determine the resource of the downlink data transmission.

[0015] In a possible implementation of the first aspect, the method further includes: receiving, by the terminal device, the downlink data on the resource of the downlink data transmission according to the downlink control information. In this solution, the terminal device can receive the downlink data on the resource indicated by the downlink control information, so as to improve the success rate of data transmission.

[0016] In a possible implementation of the first aspect, the terminal device determines that the first QoS flow is used for the downlink data transmission, including: determining, by the terminal device, that the first QoS flow is used for transmitting downlink data of a first service; the method further includes: determining, by the terminal device, that the second QoS flow is used for transmitting downlink data of a second service; and sending, by the terminal device, second information used for identifying the second QoS flow. In this solution, similar to the transmission of the first information, the terminal device sends the second information after determining that the second QoS flow is used for transmitting the downlink data of the second service, so as to notify the access network device and the core network device of the determined second QoS flow.

[0017] With reference to the first aspect as above, in a possible implementation form of the first aspect, the first service is different from the second service. In this implementation form, the terminal device can select different QoS flows for transmitting downlink data of different services.

[0018] With reference to the first aspect as above, in a possible implementation form of the first aspect, the method further comprises: monitoring, by the terminal device, the channel between the terminal device and the access network device to receive downlink data at a time other than the second inactive period. In this implementation form, the terminal device can monitor the channel to receive downlink data of the second service at a time other than the second inactive period.

[0019] With reference to the first aspect as above, in a possible implementation form of the first aspect, the terminal device monitors the channel at a time other than the first inactive period and the second inactive period. In this implementation form, the terminal device can receive the related information of the downlink data of the first service at a time other than the first inactive period, and receive the related information of the downlink data of the second service at a time other than the second inactive period. Therefore, the terminal device can monitor the channel at a time other than the first inactive period and the second inactive period to receive downlink data of the first service and the second service.

[0020] With reference to the first aspect as above, in a possible implementation form of the first aspect, the terminal device determines the first QoS flow for transmitting downlink data of the first service comprises: selecting, by the terminal device, the first QoS flow for transmitting data of the first service according to a latency requirement of the first service; and the terminal device determines the second QoS flow for transmitting downlink data of the second service comprises: selecting, by the terminal device, the second QoS flow for transmitting data of the second service according to a latency requirement of the second service; and the latency requirement of the second service is higher than the latency requirement of the first service. In this implementation form, in addition to the length of the active period, the terminal device can also select a QoS flow according to the latency requirement of a service, on the basis of the terminal device selecting different QoS flows for transmitting downlink data of different services.

[0021] With reference to the first aspect as above, in a possible implementation form of the first aspect, the terminal device obtains the first inactive period parameter and the second inactive period parameter comprises: receiving, by the terminal device, configuration information of the first QoS flow and configuration information of the second QoS flow from a session management network element in a session establishment or modification process, the configuration information of the first QoS flow comprising the first inactive period parameter, and the configuration information of the second QoS flow comprising the second inactive period parameter, the first QoS flow and the second QoS flow belonging to the session. In this implementation form, the correspondence between the inactive period parameter and the QoS flow can be determined by the session management network element.

[0022] In conjunction with the first aspect described above, in one possible implementation, the terminal device acquires a first inactive period parameter and a second inactive period parameter, including: the terminal device receiving the first inactive period parameter and the second inactive period parameter from the access network device. In this scheme, the correspondence between the inactive period parameter and the QoS flow can be determined by the access network device.

[0023] In conjunction with the first aspect described above, in one possible implementation, the terminal device sending first information includes: the terminal device sending a first data packet, the first data packet including data of the first service, and the header of the first data packet including the first information. In this scheme, the first information may be included in the header of the first data packet, and the first data packet also carries uplink data of the first service. The first information does not require a dedicated signaling bearer, thereby saving signaling overhead.

[0024] In conjunction with the first aspect above, in one possible implementation, the header of the first data packet includes the first information, including: the Service Data Adaptation Protocol (SDAP) header or the Network Protocol (IP) header of the first data packet includes the first information.

[0025] In conjunction with the first aspect described above, in one possible implementation, the Data Radio Bearer (DRB) corresponding to the first QoS stream is different from the DRB corresponding to the second QoS stream. The terminal device sends a first data packet, comprising: the terminal device sending the first data packet through the DRB corresponding to the first QoS stream, wherein the first information is used to indicate that the QoS stream carrying the first information is used for data transmission of the first service. In this scheme, the first information and the QoS stream carrying the first information can be used to uniquely identify the first QoS stream. The first information can be, for example, an RQI (Radio Quality Index).

[0026] In conjunction with the first aspect described above, in one possible implementation, the first information is an identifier for the first QoS flow. In this scheme, the first information can be used to uniquely identify the first QoS flow. The first information can be, for example, a QFI.

[0027] Secondly, a communication method is provided. The device executing this communication method can be an access network device, or a module applied in the access network device, such as a chip or chip system. The following description uses an access network device as the executing entity. The communication method includes: an access network device sending a first inactive period parameter and a second inactive period parameter to a terminal device, the first inactive period parameter corresponding to a first Quality of Service (QoS) flow between the terminal device and a user plane network element, the second inactive period parameter corresponding to a second QoS flow between the terminal device and the user plane network element, the duration of the first inactive period indicated by the first inactive period parameter being greater than the duration of the second inactive period indicated by the second inactive period parameter; the access network device receiving first information from the terminal device, the first information being used to identify the first QoS flow, the first QoS flow being used for downlink data transmission; the access network device sending the first information to the user plane network element; the access network device receiving downlink data from the user plane network element through the first QoS flow; and, outside the first inactive period, the access network device sending downlink control information to the terminal device through a channel between the terminal device and the access network device, the downlink control information being used to indicate the transmission resources for the downlink data.

[0028] In the communication method provided in this application embodiment, the access network device can receive first information for identifying a first QoS flow and send the first information to the user plane network element to receive downlink data through the first QoS flow. Since the access network device can send downlink control information outside the first inactive period, but not outside the second inactive period, and the duration of the first inactive period is longer than the duration of the second inactive period, the access network device can refrain from sending downlink control information for a longer period (i.e., the duration of the first inactive period), thereby improving the energy-saving effect of the access network device.

[0029] In conjunction with the second aspect described above, in one possible implementation, the first inactive period includes all or part of the second inactive period. In this scheme, the first inactive period and the second inactive period overlap, and the overlapping period can be all or part of the second inactive period.

[0030] In conjunction with the second aspect described above, in one possible implementation, the start time of the first inactive period is the same as the start time of the second inactive period. In this scheme, the overlapping period between the first and second inactive periods can be the entire duration of the second inactive period.

[0031] In conjunction with the second aspect described above, in one possible implementation, the end time of the first inactive period is the same as the end time of the second inactive period. In this scheme, the overlapping period between the first and second inactive periods can be the entire duration of the second inactive period.

[0032] In conjunction with the second aspect described above, in one possible implementation, the time outside the first inactive period includes all or part of the time period outside the first inactive period. In this scheme, the access network device can transmit downlink control information during all or part of the time period outside the first inactive period. When the access network device transmits downlink control information during all time periods outside the first inactive period, the timing of downlink control information transmission is more flexible. When the access network device transmits downlink control information during part of the time period outside the first inactive period, the time period available for the access network device to transmit downlink control information is shorter, thereby further improving the energy-saving effect of the access network device.

[0033] In conjunction with the second aspect described above, in one possible implementation, the time outside the first inactive period includes all or part of the time period within the active period corresponding to the first QoS flow. In this scheme, the access network device can send downlink control information within all or part of the time period within the active period corresponding to the first QoS flow. When the access network device sends downlink control information within all the time periods within the active period corresponding to the first QoS flow, the timing of downlink control information transmission is more flexible. When the access network device sends downlink control information within part of the active period corresponding to the first QoS flow, the time period available for the access network device to send downlink control information is shorter, thereby further improving the energy-saving effect of the access network device.

[0034] In conjunction with the second aspect above, in one possible implementation, the duration of the active period corresponding to the first QoS flow is the same as the duration of the active period corresponding to the second QoS flow.

[0035] In conjunction with the second aspect described above, in one possible implementation, the method further includes: the access network device sending the first inactive period parameter and the second inactive period parameter to the session management network element; the access network device receiving configuration information of the first QoS flow and the second QoS flow from the session management network element during the establishment or modification of a session, wherein the configuration information of the first QoS flow includes the first inactive period parameter, the configuration information of the second QoS flow includes the second inactive period parameter, and the first QoS flow and the second QoS flow belong to the session. In this scheme, the correspondence between the inactive period parameter and the QoS flow can be determined by the session management network element.

[0036] In conjunction with the second aspect described above, in one possible implementation, the method further includes: the access network device receiving configuration information of the first QoS flow and configuration information of the second QoS flow from the session management network element during the establishment or modification of a session, wherein the first QoS flow and the second QoS flow belong to the session; the access network device determining that the first inactive period parameter corresponds to the first QoS flow, and the second inactive period parameter corresponds to the second QoS flow. In this scheme, the correspondence between the inactive period parameter and the QoS flow can be determined by the access network device.

[0037] In conjunction with the second aspect described above, in one possible implementation, the access network device receiving the first information from the terminal device includes: the access network device receiving a first data packet from the terminal device, the first data packet including data of the first service, and the header of the first data packet including the first information; the access network device sending the first information to the user plane network element includes: the access network device sending a second data packet to the user plane network element, the second data packet including data of the first service, and the header of the second data packet including the first information. In this scheme, the first information may be included in the header of the first data packet (or the second data packet), and the first data packet (or the second data packet) also carries uplink data of the first service. The first information does not require a dedicated signaling bearer, thereby saving signaling overhead.

[0038] In conjunction with the second aspect described above, in one possible implementation, the header of the first data packet includes the first information, including: the Service Data Adaptation Protocol (SDAP) header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the General Packet Radio Service Channel Protocol User Plane (GTP-U) header of the second data packet includes the first information. In this scheme, the access network device can parse the first information from the SDAP header of the first data packet and generate a second data packet with the GTP-U header including the first information.

[0039] In conjunction with the second aspect described above, in one possible implementation, the header of the first data packet includes the first information, including: the Internet Protocol (IP) header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the IP header of the second data packet includes the first information. In this scheme, the first data packet and the second data packet can have the same format, meaning that the access network device can directly forward the first data packet without parsing its IP header, thereby achieving the technical effect of improving the transmission speed of the first information.

[0040] In conjunction with the second aspect above, in one possible implementation, the access network device receiving a first data packet from the terminal device includes: the access network device receiving the first data packet from the terminal device through the data radio bearer (DRB) corresponding to the first QoS flow; the access network device sending a second data packet to the user plane network element includes: the access network device sending the second data packet to the user plane network element through the first QoS flow.

[0041] In conjunction with the second aspect described above, in one possible implementation, the first information is used to indicate that the QoS stream carrying the first information is used for data transmission of the first service. In this scheme, the first information and the QoS stream carrying the first information can be used to uniquely identify the first QoS stream. The first information can be, for example, an RQI (Rate Quality Index).

[0042] In conjunction with the second aspect described above, in one possible implementation, the first information is an identifier for the first QoS flow. In this scheme, the first information can be used to uniquely identify the first QoS flow. The first information can be, for example, a QFI.

[0043] Thirdly, a communication method is provided. For example, the access network device sends a first inactive period parameter and a second inactive period parameter to the terminal device. The first inactive period parameter corresponds to a first Quality of Service (QoS) flow between the terminal device and the user plane network element, and the second inactive period parameter corresponds to a second QoS flow between the terminal device and the user plane network element. The duration of the first inactive period indicated by the first inactive period parameter is greater than the duration of the second inactive period indicated by the second inactive period parameter. The access network device receives first information from the terminal device, which is used to identify the first QoS flow and is used to transmit downlink data. The access network device sends the first information to the user plane network element. The user plane network element receives the first information from the access network device. The user plane network element sends the downlink data to the access network device through the first QoS. The access network device receives the downlink data from the user plane network element through the first QoS flow. Outside of the first inactive period, the access network device sends downlink control information to the terminal device through the channel between the terminal device and the access network device. The downlink control information is used to indicate the transmission resources for the downlink data.

[0044] In conjunction with the third aspect above, in one possible implementation, the method further includes: the terminal device acquiring the first inactive period parameter and the second inactive period parameter; the terminal device determining that the first QoS flow is used for downlink data transmission; the terminal device sending the first information to the access network device; and the terminal device monitoring the channel between the terminal device and the access network device to receive downlink data during times other than the first inactive period.

[0045] In conjunction with the third aspect above, in one possible implementation, the method further includes: the terminal device receiving the downlink data on the downlink data transmission resource according to the downlink control information.

[0046] In conjunction with the third aspect described above, in one possible implementation, the terminal device determines that the first QoS stream is used for downlink data transmission, comprising: the terminal device determining that the first QoS stream is used to transmit downlink data of a first service; the method further comprising: the terminal device determining that the second QoS stream is used to transmit downlink data of a second service; the terminal device sending second information to the access network device, the second information being used to identify the second QoS stream; the access network device receiving the second information from the terminal device; the access network device sending the second information to the user plane network element; the user plane network element receiving the second information from the access network device; the user plane network element sending the downlink data of the second service to the access network device through the second QoS; and the access network device receiving the downlink data of the second service from the user plane network element through the second QoS stream.

[0047] In conjunction with the third aspect above, in one possible implementation, the method further includes: the terminal device monitoring the channel between the terminal device and the access network device to receive downlink data during times other than the second inactive period.

[0048] In conjunction with the third aspect above, in one possible implementation, the terminal device monitors the channel outside of the first inactive period and the second inactive period.

[0049] In conjunction with the third aspect above, in one possible implementation, the terminal device determines that the first QoS stream is used to transmit downlink data of the first service, including: the terminal device selects the first QoS stream to transmit data of the first service based on the latency requirements of the first service; the terminal device determines that the second QoS stream is used to transmit downlink data of the second service, including: the terminal device selects the second QoS stream to transmit data of the second service based on the latency requirements of the second service; the latency requirements of the second service are higher than the latency requirements of the first service.

[0050] In conjunction with the third aspect above, in one possible implementation, the terminal device obtains the first inactive period parameter and the second inactive period parameter, including: during the establishment or modification of a session, the terminal device receives configuration information of the first QoS flow and configuration information of the second QoS flow from a session management network element, wherein the configuration information of the first QoS flow includes the first inactive period parameter, the configuration information of the second QoS flow includes the second inactive period parameter, and the first QoS flow and the second QoS flow belong to the session.

[0051] In conjunction with the third aspect described above, in one possible implementation, the method further includes: the access network device sending the first inactive period parameter and the second inactive period parameter to the session management network element; the session management network element sending the configuration information of the first QoS flow and the configuration information of the second QoS flow to the access network device and the terminal device during the establishment or modification of the session; and the access network device receiving the configuration information of the first QoS flow and the configuration information of the second QoS flow from the session management network element during the establishment or modification of the session.

[0052] In conjunction with the third aspect above, in one possible implementation, the terminal device acquires the first inactive period parameter and the second inactive period parameter, including: the terminal device receiving the first inactive period parameter and the second inactive period parameter from the access network device.

[0053] In conjunction with the third aspect described above, in one possible implementation, the method further includes: the session management network element sending configuration information of the first QoS flow and configuration information of the second QoS flow to the access network device during the establishment or modification of a session; the access network device receiving the configuration information of the first QoS flow and the configuration information of the second QoS flow from the session management network element during the establishment or modification of a session; the first QoS flow and the second QoS flow belonging to the session; the access network device determining that the first inactive period parameter corresponds to the first QoS flow and the second inactive period parameter corresponds to the second QoS flow; and the access network device sending the first inactive period parameter and the second inactive period parameter to the terminal device.

[0054] In conjunction with the third aspect above, in one possible implementation, the terminal device sends first information to the access network device, and the access network device receives the first information from the terminal device, including: the terminal device sending a first data packet to the access network device, and the access network device receiving the first data packet from the terminal device; the first data packet includes data of the first service, and the header of the first data packet includes the first information.

[0055] In conjunction with the third aspect above, in one possible implementation, the access network device sends the first information to the user plane network element, and the user plane network element receives the first information from the access network device, including: the access network device sending a second data packet to the user plane network element, and the user plane network element receiving the second data packet from the access network device; the second data packet includes the data of the first service, and the header of the second data packet includes the first information.

[0056] In conjunction with the third aspect above, in one possible implementation, the header of the first data packet includes the first information, including: the Service Data Adaptation Protocol (SDAP) header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the General Packet Radio Service Channel Protocol (GTP-U) user plane header of the second data packet includes the first information.

[0057] In conjunction with the third aspect above, in one possible implementation, the header of the first data packet includes the first information, including: the Internet Protocol (IP) header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the IP header of the second data packet includes the first information.

[0058] In conjunction with the third aspect above, in one possible implementation, the data radio bearer (DRB) corresponding to the first QoS stream is different from the DRB corresponding to the second QoS stream; the terminal device sends a first data packet to the access network device, and the access network device receives the first data packet from the terminal device, including: the terminal device sending the first data packet to the access network device through the DRB corresponding to the first QoS stream, and the access network device receiving the first data packet from the terminal device through the DRB corresponding to the first QoS stream; the first information is used to indicate that the QoS stream carrying the first information is used for data transmission of the first service.

[0059] In conjunction with the third aspect above, in one possible implementation, the access network device sends a second data packet to the user plane network element, and the user plane network element receives the second data packet from the access network device, including: the access network device sending the second data packet to the user plane network element through the first QoS flow, and the user plane network element receiving the second data packet from the access network device through the first QoS flow.

[0060] In conjunction with the third aspect mentioned above, in one possible implementation, the first information is the identifier of the first QoS flow.

[0061] In conjunction with the third aspect above, in one possible implementation, the first inactive period includes all or part of the second inactive period.

[0062] In conjunction with the third aspect mentioned above, in one possible implementation, the start time of the first inactive period is the same as the start time of the second inactive period.

[0063] In conjunction with the third aspect mentioned above, in one possible implementation, the end time of the first inactive period is the same as the end time of the second inactive period.

[0064] In conjunction with the third aspect above, in one possible implementation, the time outside the first inactive period includes all or part of the time period outside the first inactive period.

[0065] In conjunction with the third aspect above, in one possible implementation, the time outside the first inactive period includes all or part of the active period corresponding to the first QoS flow.

[0066] In conjunction with the third aspect mentioned above, in one possible implementation, the duration of the active period corresponding to the first QoS flow is the same as the duration of the active period corresponding to the second QoS flow.

[0067] The technical effects of any possible implementation of the third aspect can be found in the technical effects of different implementations of the first or second aspect mentioned above, and will not be repeated here.

[0068] Fourthly, a communication device is provided for implementing the above-described method. This communication device includes modules, units, or means corresponding to the implementation of the above-described method. 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 corresponding to the above-described functions.

[0069] In conjunction with the fourth aspect above, in one possible implementation, the communication device includes: a transceiver module and a processing module; the transceiver module is configured to acquire a first inactive period parameter and a second inactive period parameter, the first inactive period parameter corresponding to a first Quality of Service (QoS) flow between the terminal device and the user plane network element, the second inactive period parameter corresponding to a second QoS flow between the terminal device and the user plane network element, wherein the duration of the first inactive period indicated by the first inactive period parameter is greater than the duration of the second inactive period indicated by the second inactive period parameter; the processing module is configured to determine that the first QoS flow is used for downlink data transmission; the transceiver module is further configured to send first information, the first information being used to identify the first QoS flow; the processing module is further configured to monitor the channel between the terminal device and the access network device to receive downlink data during times other than the first inactive period.

[0070] In conjunction with the fourth aspect above, in one possible implementation, the first inactive period includes all or part of the second inactive period.

[0071] In conjunction with the fourth aspect above, in one possible implementation, the start time of the first inactive period is the same as the start time of the second inactive period.

[0072] In conjunction with the fourth aspect above, in one possible implementation, the end time of the first inactive period is the same as the end time of the second inactive period.

[0073] In conjunction with the fourth aspect above, in one possible implementation, the time outside the first inactive period includes all or part of the time period outside the first inactive period.

[0074] In conjunction with the fourth aspect above, in one possible implementation, the time outside the first inactive period includes all or part of the active period corresponding to the first QoS flow.

[0075] In conjunction with the fourth aspect above, in one possible implementation, the duration of the active period corresponding to the first QoS flow is the same as the duration of the active period corresponding to the second QoS flow.

[0076] In conjunction with the fourth aspect above, in one possible implementation, the channel is used to carry downlink control information, which is used to indicate the resources for the downlink data transmission.

[0077] In conjunction with the fourth aspect above, in one possible implementation, the transceiver module is further configured to receive the downlink data on the resources for transmitting the downlink data, based on the downlink control information.

[0078] In conjunction with the fourth aspect above, in one possible implementation, the processing module is configured to determine that the first QoS stream is used for downlink data transmission, including: determining that the first QoS stream is used to transmit downlink data of a first service; the processing module is further configured to determine that the second QoS stream is used to transmit downlink data of a second service; the sending module is further configured to send second information, the second information being used to identify the second QoS stream.

[0079] In conjunction with the fourth aspect mentioned above, in one possible implementation, the first service and the second service are different.

[0080] In conjunction with the fourth aspect above, in one possible implementation, the processing module is further configured to monitor the channel between the terminal device and the access network device to receive downlink data during times other than the second inactive period.

[0081] In conjunction with the fourth aspect above, in one possible implementation, the terminal device monitors the channel outside of the first inactive period and the second inactive period.

[0082] In conjunction with the fourth aspect above, in one possible implementation, the processing module is configured to determine that the first QoS stream is used to transmit downlink data of the first service, including: selecting the first QoS stream for transmitting data of the first service based on the latency requirements of the first service; the processing module is further configured to determine that the second QoS stream is used to transmit downlink data of the second service, including: selecting the second QoS stream for transmitting data of the second service based on the latency requirements of the second service; the latency requirements of the second service are higher than the latency requirements of the first service.

[0083] In conjunction with the fourth aspect above, in one possible implementation, the transceiver module is used to obtain a first inactive period parameter and a second inactive period parameter, including: receiving configuration information of the first QoS flow and configuration information of the second QoS flow from the session management network element during the establishment or modification of the session, wherein the configuration information of the first QoS flow includes the first inactive period parameter, the configuration information of the second QoS flow includes the second inactive period parameter, and the first QoS flow and the second QoS flow belong to the session.

[0084] In conjunction with the fourth aspect above, in one possible implementation, the transceiver module is used to obtain a first inactive period parameter and a second inactive period parameter, including: receiving the first inactive period parameter and the second inactive period parameter from the access network device.

[0085] In conjunction with the fourth aspect above, in one possible implementation, the transceiver module is further configured to send first information, including: sending a first data packet, the first data packet including the data of the first service, the header of the first data packet including the first information.

[0086] In conjunction with the fourth aspect above, in one possible implementation, the header of the first data packet includes the first information, including: the Service Data Adaptation Protocol (SDAP) header or the Network Protocol (IP) header of the first data packet includes the first information.

[0087] In conjunction with the fourth aspect above, in one possible implementation, the data radio bearer (DRB) corresponding to the first QoS stream is different from the DRB corresponding to the second QoS stream. The transceiver module is further configured to send a first data packet, including: sending the first data packet through the DRB corresponding to the first QoS stream, wherein the first information is used to indicate that the QoS stream carrying the first information is used for data transmission of the first service.

[0088] In conjunction with the fourth aspect above, in one possible implementation, the first information is the identifier of the first QoS flow.

[0089] The technical effects of any possible implementation of the fourth aspect can be found in the technical effects of different implementations of the first aspect mentioned above, and will not be repeated here.

[0090] Fifthly, a communication device is provided for implementing the above-described method. This communication device includes modules, units, or means corresponding to the implementation of the above-described method. 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 corresponding to the above-described functions.

[0091] In conjunction with the fifth aspect above, in one possible implementation, the communication device includes: a transceiver module; the transceiver module is configured to send a first inactive period parameter and a second inactive period parameter to a terminal device, the first inactive period parameter corresponding to a first Quality of Service (QoS) flow between the terminal device and a user plane network element, the second inactive period parameter corresponding to a second QoS flow between the terminal device and the user plane network element, the duration of the first inactive period indicated by the first inactive period parameter being greater than the duration of the second inactive period indicated by the second inactive period parameter; the transceiver module is further configured to receive first information from the terminal device, the first information being used to identify the first QoS flow, the first QoS flow being used for downlink data transmission; the transceiver module is further configured to send the first information to the user plane network element; the transceiver module is further configured to receive downlink data from the user plane network element through the first QoS flow; the transceiver module is further configured to send downlink control information to the terminal device through a channel between the terminal device and the access network device during times other than the first inactive period, the downlink control information being used to indicate the transmission resources of the downlink data.

[0092] In conjunction with the fifth aspect above, in one possible implementation, the first inactive period includes all or part of the second inactive period.

[0093] In conjunction with the fifth aspect above, in one possible implementation, the start time of the first inactive period is the same as the start time of the second inactive period.

[0094] In conjunction with the fifth aspect above, in one possible implementation, the end time of the first inactive period is the same as the end time of the second inactive period.

[0095] In conjunction with the fifth aspect above, in one possible implementation, the time outside the first inactive period includes all or part of the time period outside the first inactive period.

[0096] In conjunction with the fifth aspect above, in one possible implementation, the time outside the first inactive period includes all or part of the active period corresponding to the first QoS flow.

[0097] In conjunction with the fifth aspect above, in one possible implementation, the duration of the active period corresponding to the first QoS flow is the same as the duration of the active period corresponding to the second QoS flow.

[0098] In conjunction with the fifth aspect above, in one possible implementation, the transceiver module is further configured to send the first inactive period parameter and the second inactive period parameter to the session management network element; the transceiver module is further configured to receive configuration information of the first QoS flow and configuration information of the second QoS flow from the session management network element during the establishment or modification of the session, wherein the configuration information of the first QoS flow includes the first inactive period parameter, the configuration information of the second QoS flow includes the second inactive period parameter, and the first QoS flow and the second QoS flow belong to the session.

[0099] In conjunction with the fifth aspect above, in one possible implementation, the communication device further includes: a processing module; the transceiver module is further configured to receive configuration information of the first QoS flow and configuration information of the second QoS flow from the session management network element during the establishment or modification of a session, wherein the first QoS flow and the second QoS flow belong to the session; the processing module is configured to determine that the first inactive period parameter corresponds to the first QoS flow and the second inactive period parameter corresponds to the second QoS flow.

[0100] In conjunction with the fifth aspect above, in one possible implementation, the transceiver module is further configured to receive the first information from the terminal device, including: receiving a first data packet from the terminal device, the first data packet including data of the first service, the header of the first data packet including the first information; the transceiver module is further configured to send the first information to the user plane network element, including: sending a second data packet to the user plane network element, the second data packet including data of the first service, the header of the second data packet including the first information.

[0101] In conjunction with the fifth aspect above, in one possible implementation, the header of the first data packet includes the first information, including: the Service Data Adaptation Protocol (SDAP) header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the General Packet Radio Service Channel Protocol (GTP-U) user plane header of the second data packet includes the first information.

[0102] In conjunction with the fifth aspect above, in one possible implementation, the header of the first data packet includes the first information, including: the Internet Protocol (IP) header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the IP header of the second data packet includes the first information.

[0103] In conjunction with the fifth aspect above, in one possible implementation, the transceiver module is further configured to receive a first data packet from the terminal device, including: receiving the first data packet from the terminal device through the data radio bearer (DRB) corresponding to the first QoS flow; the transceiver module is further configured to send a second data packet to the user plane network element, including: sending the second data packet to the user plane network element through the first QoS flow.

[0104] In conjunction with the fifth aspect above, in one possible implementation, the first information is used to indicate that the QoS stream carrying the first information is used for data transmission of the first service.

[0105] In conjunction with the fifth aspect above, in one possible implementation, the first information is the identifier of the first QoS flow.

[0106] The technical effects of any possible implementation of the fifth aspect can be found in the technical effects of different implementations of the second aspect mentioned above, and will not be repeated here.

[0107] In a sixth aspect, a communication system is provided, including an access network device and a user plane network element; wherein the access network device is configured to send a first inactivity period parameter and a second inactivity period parameter to a terminal device, the first inactivity period parameter corresponding to a first Quality of Service (QoS) flow between the terminal device and the user plane network element, the second inactivity period parameter corresponding to a second QoS flow between the terminal device and the user plane network element, the duration of the first inactivity period indicated by the first inactivity period parameter being greater than the duration of the second inactivity period indicated by the second inactivity period parameter; the access network device is further configured to receive first information from the terminal device, the first information being used to identify the first... The first QoS stream is used to transmit downlink data; the access network device is also used to send the first information to the user plane network element; the user plane network element is used to receive the first information from the access network device; the user plane network element is also used to send the downlink data to the access network device through the first QoS; the access network device is also used to receive the downlink data from the user plane network element through the first QoS stream; the access network device is also used to send downlink control information to the terminal device through the channel between the terminal device and the access network device during times other than the first inactive period, the downlink control information being used to indicate the transmission resources of the downlink data.

[0108] In conjunction with the sixth aspect above, in one possible implementation, the communication system further includes a terminal device, which is configured to acquire the first inactive period parameter and the second inactive period parameter; the terminal device is also configured to determine that the first QoS flow is used for downlink data transmission; the terminal device is also configured to send the first information to the access network device; and the terminal device is also configured to monitor the channel between the terminal device and the access network device to receive downlink data during times other than the first inactive period.

[0109] In conjunction with the sixth aspect above, in one possible implementation, the terminal device is further configured to receive the downlink data on the resources for the downlink data transmission based on the downlink control information.

[0110] In conjunction with the sixth aspect above, in one possible implementation, the terminal device is further configured to determine that the first QoS flow is used for downlink data transmission, including: determining that the first QoS flow is used to transmit downlink data of a first service; the terminal device is further configured to determine that the second QoS flow is used to transmit downlink data of a second service; the terminal device is further configured to send second information to the access network device, the second information being used to identify the second QoS flow; the access network device is further configured to receive the second information from the terminal device; the access network device is further configured to send the second information to the user plane network element; the user plane network element is further configured to receive the second information from the access network device; the user plane network element is further configured to send downlink data of the second service to the access network device through the second QoS; the access network device is further configured to receive downlink data of the second service from the user plane network element through the second QoS flow.

[0111] In conjunction with the sixth aspect above, in one possible implementation, the terminal device is further configured to monitor the channel between the terminal device and the access network device to receive downlink data during times other than the second inactive period.

[0112] In conjunction with the sixth aspect above, in one possible implementation, the terminal device monitors the channel outside of the first inactive period and the second inactive period.

[0113] In conjunction with the sixth aspect above, in one possible implementation, the terminal device is further configured to determine that the first QoS stream is used to transmit downlink data of the first service, including: selecting the first QoS stream for transmitting data of the first service based on the latency requirements of the first service; the terminal device is further configured to determine that the second QoS stream is used to transmit downlink data of the second service, including: selecting the second QoS stream for transmitting data of the second service based on the latency requirements of the second service; the latency requirements of the second service are higher than the latency requirements of the first service.

[0114] In conjunction with the sixth aspect above, in one possible implementation, the communication system further includes: a session management network element; and a terminal device configured to acquire a first inactive period parameter and a second inactive period parameter, comprising: receiving configuration information of the first QoS flow and configuration information of the second QoS flow from the session management network element during the establishment or modification of a session, wherein the configuration information of the first QoS flow includes the first inactive period parameter, the configuration information of the second QoS flow includes the second inactive period parameter, and the first QoS flow and the second QoS flow belong to the session.

[0115] In conjunction with the sixth aspect above, in one possible implementation, the access network device is further configured to send the first inactive period parameter and the second inactive period parameter to the session management network element; the session management network element is configured to send the configuration information of the first QoS flow and the configuration information of the second QoS flow to the access network device and the terminal device during the establishment or modification of the session; the access network device is further configured to receive the configuration information of the first QoS flow and the configuration information of the second QoS flow from the session management network element during the establishment or modification of the session.

[0116] In conjunction with the sixth aspect above, in one possible implementation, the terminal device is configured to acquire a first inactive period parameter and a second inactive period parameter, including: receiving the first inactive period parameter and the second inactive period parameter from the access network device.

[0117] In conjunction with the sixth aspect above, in one possible implementation, the communication system further includes: a session management network element; the session management network element is configured to send configuration information of the first QoS flow and configuration information of the second QoS flow to the access network device during the establishment or modification of a session; the access network device is further configured to receive the configuration information of the first QoS flow and the configuration information of the second QoS flow from the session management network element during the establishment or modification of a session, wherein the first QoS flow and the second QoS flow belong to the session; the access network device is further configured to determine that the first inactive period parameter corresponds to the first QoS flow and the second inactive period parameter corresponds to the second QoS flow; the access network device is further configured to send the first inactive period parameter and the second inactive period parameter to the terminal device.

[0118] In conjunction with the sixth aspect above, in one possible implementation, the terminal device is further configured to send first information to the access network device, and the access network device is configured to receive the first information from the terminal device, including: the terminal device is further configured to send a first data packet to the access network device, and the access network device is further configured to receive the first data packet from the terminal device; the first data packet includes data of the first service, and the header of the first data packet includes the first information.

[0119] In conjunction with the sixth aspect above, in one possible implementation, the access network device is further configured to send the first information to the user plane network element; the user plane network element is configured to receive the first information from the access network device, including: the access network device is further configured to send a second data packet to the user plane network element, and the user plane network element is further configured to receive the second data packet from the access network device; the second data packet includes data of the first service, and the header of the second data packet includes the first information.

[0120] In conjunction with the sixth aspect above, in one possible implementation, the header of the first data packet includes the first information, including: the Service Data Adaptation Protocol (SDAP) header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the General Packet Radio Service Channel Protocol (GTP-U) user plane header of the second data packet includes the first information.

[0121] In conjunction with the sixth aspect above, in one possible implementation, the header of the first data packet includes the first information, including: the Internet Protocol (IP) header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the IP header of the second data packet includes the first information.

[0122] In conjunction with the sixth aspect above, in one possible implementation, the data radio bearer (DRB) corresponding to the first QoS stream is different from the DRB corresponding to the second QoS stream; the terminal device is further configured to send a first data packet to the access network device, and the access network device is further configured to receive the first data packet from the terminal device, including: the terminal device is further configured to send the first data packet to the access network device through the DRB corresponding to the first QoS stream, and the access network device is further configured to receive the first data packet from the terminal device through the DRB corresponding to the first QoS stream; the first information is used to indicate that the QoS stream carrying the first information is used for data transmission of the first service.

[0123] In conjunction with the sixth aspect above, in one possible implementation, the access network device is further configured to send a second data packet to the user plane network element, and the user plane network element is further configured to receive the second data packet from the access network device, including: the access network device is further configured to send the second data packet to the user plane network element through the first QoS flow, and the user plane network element is further configured to receive the second data packet from the access network device through the first QoS flow.

[0124] In conjunction with the sixth aspect above, in one possible implementation, the first information is the identifier of the first QoS flow.

[0125] In conjunction with the sixth aspect above, in one possible implementation, the first inactive period includes all or part of the second inactive period.

[0126] In conjunction with the sixth aspect above, in one possible implementation, the start time of the first inactive period is the same as the start time of the second inactive period.

[0127] In conjunction with the sixth aspect above, in one possible implementation, the end time of the first inactive period is the same as the end time of the second inactive period.

[0128] In conjunction with the sixth aspect above, in one possible implementation, the time outside the first inactive period includes all or part of the time period outside the first inactive period.

[0129] In conjunction with the sixth aspect above, in one possible implementation, the time outside the first inactive period includes all or part of the active period corresponding to the first QoS flow.

[0130] In conjunction with the sixth aspect above, in one possible implementation, the duration of the active period corresponding to the first QoS flow is the same as the duration of the active period corresponding to the second QoS flow.

[0131] A seventh aspect provides a communication device comprising: a processor; the processor being configured to be coupled to a memory, and after reading computer instructions stored in the memory, to execute, according to the instructions, the method described in the first or second aspect above.

[0132] In conjunction with the seventh aspect above, in one possible implementation, the communication device further includes a memory for storing computer instructions.

[0133] In conjunction with the seventh aspect above, in one possible implementation, the communication device further includes a communication interface; this communication interface is used for the communication device to communicate with other devices. For example, the communication interface may be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc.

[0134] In conjunction with the seventh aspect above, in one possible implementation, the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0135] In conjunction with the seventh aspect above, in one possible implementation, when the communication device is a chip or chip system, the aforementioned communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The aforementioned processor can also be embodied as a processing circuit or logic circuit.

[0136] Eighthly, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, enable the computer to perform the methods described in the first or second aspect above.

[0137] Ninthly, a computer program product containing instructions is provided that, when run on a computer, enables the computer to perform the methods described in the first or second aspect above.

[0138] In a tenth aspect, a chip is provided, the chip comprising: a processor configured to execute instructions that cause a device including the chip to perform the method described in the first or second aspect.

[0139] In conjunction with the tenth aspect above, in one possible implementation, the chip also includes a memory for storing instructions.

[0140] The technical effects of any of the possible implementations of aspects six through ten can be found in the technical effects of different implementations of aspects one or two above, and will not be repeated here. Attached Figure Description

[0141] Figure 1 This is a schematic diagram of the DTX technology in the community.

[0142] Figure 2 This is a schematic diagram of the architecture of the communication system used in the embodiments of this application;

[0143] Figure 3 A schematic diagram illustrating the splitting of the gNB's protocol layer for CU and DU nodes;

[0144] Figure 4 This diagram illustrates the network elements included in the core network, as well as the connection relationships between the core network and access network equipment and terminal equipment.

[0145] Figure 5 Flowchart of the communication method provided in the embodiments of this application Figure 1 ;

[0146] Figure 6 Flowchart of the communication method provided in the embodiments of this application Figure 2 ;

[0147] Figure 7 A schematic diagram showing the temporal location of the first inactive period and the second inactive period provided for embodiments of this application;

[0148] Figure 8 Flowchart of the communication method provided in the embodiments of this application Figure 3 ;

[0149] Figure 9 Flowchart of a specific example of the communication method provided in the embodiments of this application Figure 1 ;

[0150] Figure 10 A schematic diagram of UE-RAN interaction provided in the embodiments of this application. Figure 1 ;

[0151] Figure 11 Flowchart of a specific example of the communication method provided in the embodiments of this application Figure 2 ;

[0152] Figure 12 Flowchart of a specific example of the communication method provided in the embodiments of this application Figure 3 ;

[0153] Figure 13 Flowchart of a specific example of the communication method provided in the embodiments of this application Figure 4 ;

[0154] Figure 14 A schematic diagram of UE-RAN interaction provided in the embodiments of this application. Figure 2 ;

[0155] Figure 15 Flowchart of a specific example of the communication method provided in the embodiments of this application Figure 5 ;

[0156] Figure 16 Flowchart of a specific example of the communication method provided in the embodiments of this application Figure 6 ;

[0157] Figure 17 Flowchart of a specific example of the communication method provided in the embodiments of this application Figure 7 ;

[0158] Figure 18 Flowchart of a specific example of the communication method provided in the embodiments of this application Figure 8 ;

[0159] Figure 19 Schematic diagram of the communication device provided in the embodiments of this application Figure 1 ;

[0160] Figure 20 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 . Detailed Implementation

[0161] Cell DTX technology can be used to reduce the energy consumption of access network equipment and lower operator costs. For example, a terminal device can receive radio resource control (RRC) configuration information from the access network equipment and obtain the cell DTX cycle length (e.g., celldtx-Cycle) and the length of the active period included in the cell DTX cycle (e.g., celldtx-onDurationTimer) based on the RRC configuration information. When the access network equipment determines that cell DTX technology needs to be used to transmit service data, it can send downlink control information (DCI) to the terminal device. Accordingly, the terminal device can obtain the DCI through blind detection and activate cell DTX technology based on the DCI. Then, during the active period, the terminal device can monitor the PDCCH, and the access network equipment can send information to the terminal device through the PDCCH, which indicates the resources for data transmission. After receiving this information on the PDCCH, the terminal device can transmit data on the resources indicated by the information. During the inactive period, the terminal device can not monitor the PDCCH, so the access network equipment can reduce its energy consumption and achieve energy saving by not sending any information through the PDCCH. The longer the inactive period, the better the energy saving effect of the access network equipment, but the greater the data transmission latency.

[0162] Typically, an active period can also be referred to as an activation period, a non-dormant period, or a non-deactivation period. Similarly, a cell or access network device being in an active period can be described as being in an active state, an activated state, a non-dormant state, or a non-deactivation state. Conversely, an inactive period can also be referred to as a deactivation period, a dormant period, or an inactive period. The same applies to a cell or access network device being in an inactive period.

[0163] In existing technologies, access network equipment typically configures the cell DTX period according to the needs of services that are sensitive to transmission latency. In other words, in order to meet the latency requirements of most services as much as possible, access network equipment will configure the inactive period as short as possible, which leads to poorer energy-saving performance of access network equipment.

[0164] Based on this, embodiments of this application provide a communication method in which a terminal device can determine a first quality of service (QoS) stream for downlink data transmission, wherein the duration of a first inactive period corresponding to the first QoS stream is greater than the duration of a second inactive period corresponding to the second QoS stream. In other words, between the first QoS stream and the second QoS stream, the terminal device can determine that the first QoS stream with the longer corresponding inactive period is used for downlink data transmission, thereby improving the energy-saving effect of the access network device.

[0165] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application 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 alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0166] Figure 2 This is a schematic diagram of the architecture of the communication system 1000 used in an embodiment of this application. Figure 2 As shown, the communication system includes at least one terminal device (such as...) Figure 2 The network consists of 120a-120j (collectively referred to as 120), access network 100, core network (CN) 200, and data network (DN) 300. Access network 100 can be a radio access network (RAN), and it may include at least one RAN node (e.g., Figure 2 110a and 110b (collectively referred to as 110) are connected wirelessly to RAN node 110. RAN node 110 is connected to core network 200 wirelessly or via wired connection. The core network equipment in core network 200 and RAN node 110 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0167] The following sections will introduce the terminal device 120, RAN node 110, access network 100, and core network (CN) 200 respectively.

[0168] 1) Terminal equipment 120.

[0169] Terminal device 120 can also be referred to as a terminal device, terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the device form of the terminal device.

[0170] 2) RAN node.

[0171] RAN node 110, also known as RAN entity or access node, may include access network (AN) equipment. RAN nodes are part of the communication system and assist terminal device 120 in achieving wireless access. Multiple RAN nodes 110 in the communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal device 120 are relative, for example... Figure 2 Network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminal devices 120j that access RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal device. RAN node 110 and terminal device 120 are sometimes referred to as communication devices, for example... Figure 2 Network elements 110a and 110b can be understood as communication devices with base station functions, while network elements 120a-120j can be understood as communication devices with terminal equipment functions.

[0172] Communication between access network devices and terminal devices follows a specific protocol layer structure. This protocol layer may include a control plane protocol layer and a user plane protocol layer. The control plane protocol layer may include at least one of the following: RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, or Physical (PHY) layer, etc. The user plane protocol layer may include at least one of the following: Service Data Adaptation Protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, or Physical layer, etc.

[0173] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system. A RAN node can also be a macro base station (such as...) Figure 3 110a), micro base stations or indoor stations (such as Figure 3 In V2X technology, the access network device can be a 110b node, a relay node or donor node, or a radio controller in a cloud radio access network (CRAN) scenario. Optionally, the RAN node can also be a server, wearable device, vehicle or in-vehicle equipment, etc. For example, the access network device in V2X technology can be a roadside unit (RSU).

[0174] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes implementing some of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as the baseband unit (BBU). CU and DU nodes separate the gNB's protocol layers; some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU. As one implementation, the CU deploys the Radio Resource Control (RRC) layer, PDCP layer, and SDAP layer from the protocol stack; the DU deploys the RLC layer, MAC layer, and PHY layer from the protocol stack. Thus, the CU has RRC, PDCP, and SDAP processing capabilities, while the DU has RLC, MAC, and PHY processing capabilities. It is understood that the above functional division is only an example and does not constitute a limitation on CU and DU. RU can be included in radio frequency equipment or radio frequency units, such as in remote radio units (RRU), active antenna units (AAU), or remote radio heads (RRH).

[0175] Figure 3 This diagram illustrates how the CU and DU nodes decompose the gNB's protocol layer. Figure 4 In (a), a CU node can include CU-CP and CU-UP, which can communicate with each other via an E1 interface. CU-CP can deploy a control plane (PDCP-C) with RRC and PDCP layers; CU-UP can deploy a user plane (PDCP-U) with PDCP layers and an SDAP layer. DU can deploy an RLC layer, a MAC layer, and a PHY layer. CU-CP and DU can communicate via an F1-C interface; CU-UP and DU can communicate via an F1-U interface.

[0176] exist Figure 4In (b), two DU nodes can be deployed, each with an RLC layer, a MAC layer, and a PHY layer. The CU can have an RRC layer, a PDCP layer, and an SDAP layer deployed. Each DU node can communicate with the CU via the F1 interface.

[0177] 3) Access Network 100.

[0178] Access network 100 may be included in cellular systems related to the 3rd generation partnership project (3GPP), such as 4th generation (4G), 5th generation (5G) mobile communication systems, non-terrestrial network (NTN) systems, or future-oriented evolution systems.

[0179] Access network 100 can also be an open access network (open RAN, O-RAN or ORAN), CRAN, or WiFi system, or a communication system that integrates two or more of the above systems. Among them, ORAN aims to realize an intelligent and open access network. The main feature of the ORAN architecture is the separation of software and hardware, thereby realizing the virtualization of network functions and the standardization of hardware. In addition, ORAN also introduces artificial intelligence (AI).

[0180] For example, ORAN includes the following network elements: Service Management and Orchestration Framework (SMO), Non-Real-Time RAN Intelligent Controller (Non-RT RIC or NRT RIC), Near-Real-Time RAN Intelligent Controller (Near-RT RIC or nRT RIC), Enhanced NodeB (eNB), and O-RAN Cloud (O-Cloud). Detailed functional descriptions of the above network elements can be found in existing protocols.

[0181] 4) Core network 200.

[0182] For example, Figure 4The diagram illustrates the network elements included in the core network, as well as the connection relationships between the core network and access network equipment and terminal equipment. The core network includes at least one of the following network elements: network open network element, network repository network element, network data analysis network element, application function network element, policy control network element, network storage network element, mobility management network element, session management network element, binding support network element, or user plane network element.

[0183] The mobility management network element is used for terminal equipment access authentication, mobility management, signaling interaction between various functional network elements, and termination of non-access stratum (NAS) layer signaling security. This includes managing user registration status, reachability status, N1 / N2 interface signaling transmission, access authentication and authorization, user connection status, user registration and network access, tracking area updates, cell handover user authentication, and key security. The mobility management network element can be the access and mobility management function (AMF) in a 5G communication system.

[0184] The session management network element is used to manage the sessions of terminal devices (such as session establishment, modification, and release), allocate and manage internet protocol (IP) addresses, and select and control user plane network elements. The session management network element can be the session management function (SMF) in a 5G communication system.

[0185] Among them, the policy control network element is used to generate policies such as terminal equipment access policies and QoS policies, and can also provide the generated policies to the mobility management network element and the session management network element. The policy control network element can be the policy control function (PCF) in the 5G communication system.

[0186] Among them, network storage elements are used to provide storage capabilities for contracted data, policy data, and capability-related data. Network storage elements can be network repository functions (NRF), unified data repositories (UDR), or unified data management (UDM) in 5G communication systems.

[0187] User plane network elements are used for routing and forwarding user plane data packets in the core network. User plane network elements can be user plane functions (UPFs) in 5G communication systems.

[0188] It should be noted that the terminal device, access network device, and core network device in the embodiments of this application can all be one or more chips, or they can be system on chip (SOC), etc. Figure 4 The accompanying drawings are for illustrative purposes only, and the number of devices included is not limited. Figure 5 The names of the various devices and links are unrestricted, except... Figure 6 In addition to the names shown, each device and each link can be named in other ways without restriction.

[0189] Based on the above description of the communication system, the following process can be used to describe in detail the concept, generation process, distribution process and execution process of QoS policy.

[0190] a) The concept of QoS policy.

[0191] The purpose of a QoS policy is to provide differentiated service quality to businesses by customizing services on demand, given limited resources. Typically, a QoS policy has two meanings: first, the quality of service, i.e., the specific indicators characterizing QoS, i.e., QoS parameters; and second, how to guarantee these indicators, i.e., the mechanisms for implementing QoS parameters.

[0192] Unlike the Evolved Packet System (EPS) bearer in 4G mobile communication technology, 5G mobile communication technology introduces a more granular QoS stream. Typically, all data streams within the same QoS stream receive the same QoS guarantee; different QoS guarantees require different QoS streams to provide them. QoS guarantees can include scheduling policies, buffer queue management, and more.

[0193] b) The process of generating QoS policies.

[0194] Once a user goes online or a terminal device connects to the network, the SMF can obtain subscription data from the UDM. This subscription data includes at least one of the following: session-aggregate maximum bitrate (AMBR), default QoS flow allocation and retention priority (ARP), or 5G QoS identifier (5QI).

[0195] Based on the subscription data, the SMF can send a request message to the PCF to request the generation of a QoS policy.

[0196] In one possible implementation, the PCF can generate QoS policies based on the slice and location information carried by the user upon login. The generation of the QoS policy is entirely decided by the PCF, without any negotiation process between the PCF and the UDM or SMF. The PCF can then send the generated QoS policy to the SMF via a response message, allowing the SMF to configure the QoS policy locally.

[0197] In another possible implementation, if a PCF malfunction causes the N7 session to be unreachable or if the policy control and charging (PCC) function is not enabled in the network, the SMF can also configure QoS policies locally.

[0198] However, the difference between the QoS policy configured locally by the SMF and the QoS policy generated by the PCF lies in the fact that the QoS policy generated by the PCF is more granular. For example, the PCF can flexibly customize the QoS policy based on at least one of the following: user location, user level, user online time period, user quota status, or holidays. It should be noted that the PCF has the highest decision-making authority over QoS parameters. The SMF preferentially obtains QoS parameters from the PCF, but if the PCF does not issue QoS parameters, the SMF can decide whether to authorize the user to use the requested QoS parameters based on its local configuration. The SMF can save the QoS parameters that are ultimately used.

[0199] c) The process of issuing QoS policies.

[0200] After determining the final QoS parameters to be used, SMF can determine QoS flow information based on the QoS parameters and service information. QoS flow information may include at least one of the following: QoS flow identifier (QFI), packet filter set (PFS) rules, or QoS parameters. SMF can use QoS flow information to control the creation, modification, and deletion of QoS flows.

[0201] For example, the SMF can send QoS flow information to the user plane function (UPF), RAN, and UE respectively, to instruct the UPF, RAN, and UE on how to process data packets. The QoS flow information sent by the SMF to the RAN or UE needs to be transparently transmitted through the access and mobility management function (AMF).

[0202] d) The execution process of QoS policies.

[0203] For uplink transmission, the UE can map data packets to the corresponding QoS stream based on QoS stream information, and then map the data packets on the QoS stream to the data radio bearer (DRB) corresponding to the QoS stream. The RAN can map the data packets on the DRB to the QoS stream corresponding to the DRB based on QoS stream information.

[0204] For downlink transmission, the UPF can map data packets to the corresponding QoS flow based on QoS flow information; the RAN can map data packets on the QoS flow to the corresponding DRB based on the QoS flow information; and the UE can map data packets on the DRB to the corresponding QoS flow based on the QoS flow information. Based on this, the UPF, RAN, and UE can provide the corresponding quality of service.

[0205] The following uses the DTX technology of a residential community as an example to specifically illustrate the communication method provided in the embodiments of this application.

[0206] Figure 8 The flowchart of the communication method provided in the embodiments of this application includes the following steps:

[0207] Step S501: The terminal device obtains at least two inactive period parameters, including a first inactive period parameter and a second inactive period parameter.

[0208] Alternatively, the terminal device acquires multiple inactive period parameters, including a first inactive period parameter and a second inactive period parameter. This application embodiment uses the first inactive period parameter and the second inactive period parameter as examples for illustration.

[0209] The first inactive period parameter corresponds to the first QoS flow between the terminal device and the user plane network element, and the second inactive period parameter corresponds to the second QoS flow between the terminal device and the user plane network element. The first inactive period parameter indicates the duration of the first inactive period, and the second inactive period parameter indicates the duration of the second inactive period.

[0210] In this embodiment, the inactive period parameter can be a parameter related to the inactive period, such as the duration of the inactive period. Alternatively, the inactive period parameter can be a period (e.g., the cell DTX period) and the duration of the active period. The terminal device can calculate the duration of the inactive period based on the period and the duration of the active period. The specific meaning of the period in this embodiment can be found in the detailed description of subsequent step S801, and will not be repeated here.

[0211] In one possible implementation, the correspondence between the inactive period parameter and the QoS flow can be determined by the session management network element. In step S501, the terminal device can obtain the first inactive period parameter and the second inactive period parameter from the session management network element. For example, the communication method provided in this application embodiment further includes: the access network device sending the first inactive period parameter and the second inactive period parameter to the session management network element. Correspondingly, the session management network element receives the first inactive period parameter and the second inactive period parameter from the access network device. During the establishment or modification of a session, the session management network element sends configuration information of the first QoS flow and configuration information of the second QoS flow to the access network device and the terminal device; correspondingly, the access network device and the terminal device receive the configuration information of the first QoS flow and the second QoS flow from the session management network element. The configuration information of the first QoS flow includes the first inactive period parameter, the configuration information of the second QoS flow includes the second inactive period parameter, and the first QoS flow and the second QoS flow belong to a session.

[0212] In another possible implementation, the correspondence between the inactive period parameter and the QoS flow can be determined by the access network device. In step S501, the terminal device can obtain the first inactive period parameter and the second inactive period parameter from the access network device. For example, the communication method provided in this application embodiment further includes: during the establishment or modification of a session, the session management network element sends configuration information of the first QoS flow and the second QoS flow to the access network device; correspondingly, the access network device receives the configuration information of the first QoS flow and the second QoS flow from the session management network element. Wherein, the first QoS flow and the second QoS flow belong to a session. The access network device determines that the first inactive period parameter corresponds to the first QoS flow, and the second inactive period parameter corresponds to the second QoS flow. The access network device sends the correspondence between the first inactive period parameter and the first QoS flow, and the correspondence between the second inactive period parameter and the second QoS flow to the terminal device. Correspondingly, the terminal device receives the correspondence between the first inactive period parameter and the first QoS flow, and the correspondence between the second inactive period parameter and the second QoS flow from the access network device.

[0213] Furthermore, the first QoS flow and the second QoS flow can belong to different sessions. The process of establishing or modifying the aforementioned session can also be the process of establishing or modifying the session to which the first QoS flow or the second QoS flow belongs. That is, during the establishment or modification process of the session to which the first QoS flow belongs, the session management network element sends configuration information of the first QoS flow and the second QoS flow to the access network device; correspondingly, the access network device receives the configuration information of the first QoS flow and the second QoS flow from the session management network element. Alternatively, during the establishment or modification process of the session to which the second QoS flow belongs, the session management network element sends configuration information of the first QoS flow and the second QoS flow to the access network device; correspondingly, the access network device receives the configuration information of the first QoS flow and the second QoS flow from the session management network element.

[0214] Alternatively, the process of establishing or modifying the aforementioned session can also be the process of establishing or modifying a session to which other QoS flows belong. That is, during the process of establishing or modifying a session to which other QoS flows belong, the session management network element sends the configuration information of the first QoS flow and the configuration information of the second QoS flow to the access network device; correspondingly, the access network device receives the configuration information of the first QoS flow and the configuration information of the second QoS flow from the session management network element.

[0215] For example, the terminal device can obtain the inactive period parameters through the QoS flow configuration information by referring to the method shown in step S901 below, which will not be elaborated here.

[0216] Step S502: The terminal device determines the target QoS stream for downlink data transmission. The target QoS stream is either a first QoS stream or a second QoS stream.

[0217] For example, the terminal device can determine the target QoS flow based on the duration of the inactive period. Alternatively, the terminal device can determine the target QoS flow based on the duration of the inactive period and the latency requirements of the service. See below for details. Figure 5 The relevant descriptions are not elaborated here.

[0218] For example, the terminal device can determine the target QoS flow based on the latency requirements of the service. See below for details. Figure 9 The relevant descriptions are not elaborated here.

[0219] Step S503: The terminal device sends first information to the access network device, the first information being used to identify the target QoS flow. Correspondingly, the access network device receives the first information from the terminal device.

[0220] Figure 5 The "first information" in this context can also be understood as "information about the target QoS flow".

[0221] In one possible implementation, the first information can be used to directly identify or indicate the target QoS flow, that is, the access network device can directly determine the target QoS flow based on the first information. For example, the first information can be the QFI of the target QoS flow.

[0222] In another possible implementation, the first information can be used to indirectly identify or indicate the target QoS flow. That is, the access network device can indirectly determine the target QoS flow based on the first information. For example, the access network device can identify the QoS flow used to carry the first information as the target QoS flow.

[0223] Optionally, the communication method provided in this application embodiment further includes: the access network device sending an activation signaling message to the terminal device. The activation signaling message indicates that the cell DTX technology has been activated; in other words, the activation signaling message instructs the access network device to use cell DTX technology for signal transmission. Correspondingly, the terminal device receives the activation signaling message from the access network device. The transmission of the aforementioned activation signaling message can occur before or after step S503. For example, after the access network device receives downlink data from the user plane network element in step S505, the access network device sends an activation signaling message to the terminal device; that is, the access network device sends an activation signaling message to the terminal device in response to the downlink data. Another example is that the transmission of the activation signaling message can occur after the access network device sends downlink data to the terminal device. Yet another example is that the transmission of the activation signaling message can occur after a period of downlink data transmission between the user plane network element and the access network device, or between the access network device and the terminal device.

[0224] For example, the terminal device can send first information to the access network device through the DRB, as detailed below. Figure 6 The relevant descriptions in the text will not be repeated here.

[0225] The specific implementation of step S503 can be found in the description of step S603, and will not be repeated here.

[0226] Step S504: The access network device sends first information to the user plane network element. Correspondingly, the user plane network element receives the first information from the access network device.

[0227] The specific implementation of step S504 can be found in the description of step S604, and will not be repeated here.

[0228] Step S505: The user plane network element sends downlink data to the access network device through the target QoS flow. Correspondingly, the access network device receives downlink data from the user plane network element through the target QoS flow.

[0229] Optionally, after the downlink data arrives at the user plane network element, the user plane network element can map the downlink data to the target QoS flow according to the first information. The implementation of the user plane network element can be found in step S907 below, which will not be elaborated here.

[0230] Step S506: Outside of the inactive period corresponding to the target QoS flow, the access network device sends downlink control information to the terminal device through the channel between the terminal device and the access network device.

[0231] Optionally, the time outside the inactive period corresponding to the target QoS flow includes all or part of the time period outside the inactive period corresponding to the target QoS flow. In this scheme, the access network device can send downlink control information during all or part of the time period outside the inactive period corresponding to the target QoS flow. When the access network device sends downlink control information during all time periods outside the inactive period corresponding to the target QoS flow, the timing of downlink control information transmission is more flexible. When the access network device sends downlink control information during part of the time period outside the inactive period corresponding to the target QoS flow, the time period available for the access network device to send downlink control information is shorter, thereby further improving the energy-saving effect of the access network device.

[0232] Optionally, the time outside the inactive period corresponding to the target QoS flow includes all or part of the active period corresponding to the target QoS flow. In this scheme, the access network device can send downlink control information during all or part of the active period corresponding to the target QoS flow. When the access network device sends downlink control information during all of the active period corresponding to the target QoS flow, the timing of downlink control information transmission is more flexible. When the access network device sends downlink control information during part of the active period corresponding to the target QoS flow, the time period available for the access network device to send downlink control information is shorter, thereby further improving the energy-saving effect of the access network device.

[0233] Step S507: During periods other than the inactive period corresponding to the target QoS flow, the terminal device monitors the channel between the terminal device and the access network equipment to receive downlink data.

[0234] Optionally, the time outside the inactive period corresponding to the target QoS flow includes all or part of the time period outside the inactive period corresponding to the target QoS flow. In this scheme, when the time outside the inactive period corresponding to the target QoS flow includes all the time periods outside the inactive period corresponding to the target QoS flow, the terminal device monitors the channel for a longer period, thereby avoiding missing downlink data reception. When the time outside the inactive period corresponding to the target QoS flow includes only part of the time periods outside the inactive period corresponding to the target QoS flow, the terminal device monitors the channel for a shorter period, thereby saving power consumption of the terminal device.

[0235] Optionally, the time outside the inactive period corresponding to the target QoS flow includes all or part of the active period corresponding to the target QoS flow. In this scheme, when the time outside the inactive period corresponding to the target QoS flow includes all the active period corresponding to the target QoS flow, the terminal device monitors the channel for a longer time, thereby avoiding missing downlink data reception. When the time outside the inactive period corresponding to the target QoS flow includes part of the active period corresponding to the target QoS flow, the terminal device monitors the channel for a shorter time, thereby saving power consumption of the terminal device.

[0236] Optionally, the communication method provided in this application embodiment further includes: the terminal device receiving downlink data on downlink data transmission resources according to downlink control information.

[0237] When the target QoS flow is the first QoS flow, the inactive period corresponding to the target QoS flow is the first inactive period; when the target QoS flow is the second QoS flow, the inactive period corresponding to the target QoS flow is the second inactive period.

[0238] exist Figure 6 In the illustrated embodiment, when the first inactive period parameter and the second inactive period parameter are different, the energy-saving effects of the access network devices corresponding to the first QoS flow and the second QoS flow are different. When the terminal device selects different target QoS flows for downlink data transmission, different energy-saving effects of the access network devices can be flexibly achieved.

[0239] Furthermore, in step S502 above, the terminal device can determine the target QoS flow based on all or part of the parameters involved in the cell DTX technology (e.g., the duration of the first inactive period and the second inactive period). For example, if the duration of the first inactive period is longer than the duration of the second inactive period, the terminal device can determine the target QoS flow as the first QoS flow corresponding to the first inactive period. In other words, the terminal device can select the first QoS flow with better energy-saving performance from the access network equipment, thereby improving the energy-saving performance of the access network equipment. For details, please refer to [link to relevant documentation]. Figure 6 . Figure 5 The flowchart shown includes the following steps:

[0240] Step S601: The terminal device obtains the first inactive period parameter and the second inactive period parameter.

[0241] Wherein, the duration of the first inactive period indicated by the first inactive period parameter is greater than the duration of the second inactive period indicated by the second inactive period parameter. The relevant description of step S601 can be referred to the relevant description of step S501 above, and will not be repeated here.

[0242] Step S602: The terminal device determines that the first QoS stream is used for downlink data transmission.

[0243] When the duration of the first inactive period corresponding to the first QoS flow is greater than the duration of the second inactive period corresponding to the second QoS flow, the terminal device can determine the first QoS flow, rather than the second QoS flow, for downlink data transmission. In other words, the terminal device can select a QoS flow with a longer corresponding inactive period, rather than a QoS flow with a shorter corresponding inactive period, to improve the energy efficiency of the access network equipment.

[0244] exist Figure 6 In this process, the terminal device can determine the QoS stream with a longer corresponding inactive period (e.g., the first QoS stream) as... Figure 7 The target QoS flow in the process.

[0245] Step S603: The terminal device sends first information to the access network device, the first information being used to identify the first QoS flow. Correspondingly, the access network device receives the first information from the terminal device.

[0246] Figure 7 The “first information” in this context can also be understood as “information about the first QoS stream”.

[0247] Step S604: The access network device sends first information to the user plane network element. Correspondingly, the user plane network element receives the first information from the access network device.

[0248] For the specific implementation of step S604, please refer to Figure 7 The description of step S604 following the illustrated embodiment will not be repeated here.

[0249] Step S605: The user plane network element sends downlink data to the access network device through the first QoS flow. Correspondingly, the access network device receives downlink data from the user plane network element through the first QoS flow.

[0250] Step S606: Outside of the first inactive period, the access network device sends downlink control information to the terminal device through the channel between the terminal device and the access network device. The downlink control information indicates the resources for downlink data transmission.

[0251] Step S607: Outside of the first inactive period, the terminal device monitors the channel between the terminal device and the access network equipment to receive downlink data.

[0252] Optionally, the time outside the first inactive period includes all or part of the time period outside the first inactive period.

[0253] Optionally, the time outside the first inactive period includes all or part of the active period corresponding to the first QoS flow.

[0254] The relevant descriptions of steps S603 to S607 can be found in steps S503 to S507, and will not be repeated here.

[0255] Optionally, the communication method provided in this application embodiment further includes: the terminal device receiving downlink data on downlink data transmission resources according to downlink control information.

[0256] The following is combined Figure 7 The temporal locations of the first and second inactive periods are described. Figure 7 In this context, the first active period is the active period corresponding to the first QoS flow, and the second active period is the active period corresponding to the second QoS flow.

[0257] Optionally, the first inactive period includes a portion of the second inactive period. That is, the first and second inactive periods overlap, and this overlapping period can be a portion of the second inactive period, such as... Figure 7 As shown in (a) above. For example, the access network device can configure the overlapping time periods to be as long as possible.

[0258] Optionally, the first inactive period includes the entire duration of the second inactive period. That is, the first and second inactive periods overlap, and the overlapping period is the entire duration of the second inactive period. For example, the access network device can configure the overlapping period to be as long as possible. In one possible implementation, the start time of the first inactive period is the same as the start time of the second inactive period, such as... Figure 7 As shown in (b) above. In another possible implementation, the end time of the first inactive period is the same as the end time of the second inactive period, as shown in [example missing]. Figure 7 As shown in (c) in the figure.

[0259] Optionally, the duration of the active period corresponding to the first QoS flow can be the same as the duration of the active period corresponding to the second QoS flow, such as... Figure 7 As shown in (c) above. Alternatively, the duration of the active period corresponding to the first QoS flow can also be different from the duration of the active period corresponding to the second QoS flow, such as... Figure 7 As shown in (a) and (b) in the figure.

[0260] Furthermore, active and inactive periods can alternate and occur periodically. For example, the start or end time of the first active period #1 and the second active period #1 can be the same. The first active period #1 is one of multiple first active periods, and the second active period #1 is one of multiple second active periods. Alternatively, the start time of the first active period #1 and the second active period #1 can be the same, and the end time of both can be the same. Alternatively, the duration of the first inactive period #1 can be the same as the duration of the second inactive period #1. The first inactive period #1 is one of multiple first inactive periods, and the second inactive period #1 is one of multiple second inactive periods. Alternatively, the first inactive period #1 can include the second inactive period #1, the second active period #2, and the second inactive period #2. The second active period #2 and the second inactive period #2 can belong to cell DTX cycle #2, the second inactive period #1 can belong to cell DTX cycle #1, and cell DTX cycle #1 can be different from cell DTX cycle #2. In step S602 above, the terminal device can select a first QoS stream with a longer inactive period to improve the energy-saving effect of the access network device. Further, the terminal device can select different QoS streams for transmitting downlink data of different services. That is, the first QoS stream used for downlink data transmission includes: the first QoS stream being used to transmit downlink data of a first service; the communication method provided in this application embodiment further includes: the terminal device determining a second QoS stream for transmitting downlink data of a second service; the terminal device sending second information to the access network device, the second information being used to identify the second QoS stream. Accordingly, the access network device receives the second information from the terminal device.

[0261] Optionally, the first business and the second business are different businesses.

[0262] The following describes the specific implementation of step S603, namely the interaction of the first information between the terminal device and the access network device, when the first QoS stream is used to transmit downlink data of the first service.

[0263] Optionally, the terminal device sends first information to the access network device, and correspondingly, the access network device receives the first information from the terminal device. This includes: the terminal device sending a first data packet to the access network device, and correspondingly, the access network device receiving the first data packet from the terminal device. The first data packet includes data for a first service, and the header of the first data packet includes first information. In this scheme, the first information may be included in the header of the first data packet, and the first data packet also carries uplink data for the first service. The first information does not require a dedicated signaling bearer, thereby saving signaling overhead.

[0264] Optionally, the header of the first data packet includes first information, including: the SDAP header or IP header of the first data packet including the first information. When the SDAP header of the first data packet includes the first information, the access network device can parse the first information from the SDAP header of the first data packet. The specific process is detailed in step S906 below and will not be elaborated here. When the IP header of the first data packet includes the first information, the access network device can directly forward the first data packet without parsing the IP header of the first data packet. The specific process is detailed in step S1205 below, thereby achieving the technical effect of improving the transmission speed of the first information.

[0265] Optionally, the DRB corresponding to the first QoS flow is different from the DRB corresponding to the second QoS flow. The terminal device sends a first data packet to the access network device, and correspondingly, the access network device receives the first data packet from the terminal device, including: the terminal device sending a data packet to the access network device through the DRB corresponding to the first QoS flow, and correspondingly, the access network device receiving the first data packet from the terminal device through the DRB corresponding to the first QoS flow. Wherein, the first information is used to indicate that the QoS flow carrying the first information is used for data transmission of the first service. In this scheme, the first information can be used to indirectly identify or indicate the first QoS flow; that is, the first information and the QoS flow or DRB carrying the first information can be used to uniquely identify the first QoS flow. The first information can be, for example, a reflective QoS indicator (RQI).

[0266] Optionally, the first information is an identifier for the first QoS flow. In this scheme, the first information can be used to directly identify or indicate the first QoS flow; that is, the first information can be used to uniquely identify the first QoS flow. The first information can be, for example, a QFI.

[0267] The following describes the specific implementation of step S604, namely the interaction of the first information between the access network device and the user plane network element, when the first QoS flow is used to transmit the downlink data of the first service.

[0268] Optionally, the access network device sends first information to the user plane network element, and correspondingly, the user plane network element receives the first information from the access network device. This includes: the access network device sending a second data packet to the user plane network element, and correspondingly, the user plane network element receiving the second data packet from the access network device. The second data packet includes data for the first service, and its header includes the first information. In this scheme, the first information can be included in the header of the second data packet, and the second data packet also carries uplink data for the first service. The first information does not require a dedicated signaling bearer, thus saving signaling overhead.

[0269] Optionally, the header of the first data packet includes first information, including: the SDAP header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the General Packet Radio Service Tunnel Protocol-User Plane (GPRS Tunnel Protocol-User Plane, GTP-U) header of the second data packet includes the first information. In this scheme, the access network device can parse the first information from the SDAP header of the first data packet and generate a second data packet with the first information in the GTP-U header. The specific process can be found in step S906 below, and will not be elaborated here.

[0270] Optionally, the header of the first data packet includes first information, including: the IP header of the first data packet includes the first information; the header of the second data packet includes the first information, including: the IP header of the second data packet includes the first information. In this scheme, the formats of the first data packet and the second data packet can be the same, that is, the access network device can directly forward the first data packet without parsing the IP header of the first data packet. For details, please refer to step S1205 below, thereby achieving the technical effect of improving the transmission speed of the first information.

[0271] Optionally, the access network device sends a second data packet to the user plane network element, and correspondingly, the user plane network element receives the second data packet from the access network device, including: the access network device sending the second data packet to the user plane network element through a first QoS flow. Wherein, the first information is used to indicate that the QoS flow carrying the first information is used for data transmission of the first service. In this scheme, the first information can be used to indirectly identify or indicate the first QoS flow; that is, the first information and the QoS flow carrying the first information can be used to uniquely identify the first QoS flow. The first information can be, for example, an RQI (Real Quality Index).

[0272] When the second QoS stream is used to transmit downlink data of the second service, the interaction process of the second information can refer to the interaction process of the first information above, that is, replace "first information" with "second information", "first QoS stream" with "second QoS stream", and "first service" with "second service" in the interaction process, which will not be elaborated here.

[0273] Optionally, the communication method provided in this application embodiment further includes: the terminal device monitoring the channel between the terminal device and the access network device to receive downlink data during a time other than the second inactive period.

[0274] The time outside the second inactive period includes all or part of the time period outside the second inactive period. Alternatively, the time outside the second inactive period includes all or part of the time period within the active period corresponding to the second QoS flow.

[0275] Optionally, the terminal device monitors the channel outside of the first and second inactive periods. Figure 7 ,exist Figure 7 In (a), the terminal device monitors the channel for the entire channel monitoring period or only a portion of the channel monitoring time. Figure 8 In (b) of this example, the terminal device can monitor the channel for the entire or a portion of the first active period. Figure 8 In (c), the time for the terminal device to monitor the channel can be the entire period or a part of the channel monitoring time.

[0276] Based on the terminal device selecting different QoS streams for transmitting downlink data of different services, in addition to the duration of the inactive period, the terminal device can also select QoS streams based on the latency requirements of the services. Specifically, the terminal device determines that a first QoS stream is used to transmit downlink data for a first service, including: the terminal device selects the first QoS stream for transmitting the data of the first service based on the latency requirements of the first service; the terminal device determines that a second QoS stream is used to transmit downlink data for a second service, including: the terminal device selects the second QoS stream for transmitting the data of the second service based on the latency requirements of the second service; the latency requirements of the second service are higher than those of the first service. In this scheme, the latency requirements of the second service are higher than those of the first service. Selecting a second QoS stream with a shorter inactive period to transmit the data of the second service helps reduce the transmission latency of the second service data, thus meeting the latency requirements of the second service. Selecting a first QoS stream with a longer inactive period to transmit the data of the first service not only helps meet the latency requirements of the first service but also improves the energy efficiency of the access network equipment.

[0277] For example, the first QoS flow satisfies the latency requirements of the first service. For instance, the cell DTX period corresponding to the first QoS flow is less than or equal to the latency requirements of the first service. The process by which the terminal device selects the first QoS flow based on the latency requirements of the first service is described in step S903 below, and will not be repeated here.

[0278] When the first service and the second service are different services, their latency requirements can also be different.

[0279] In the embodiments of this application, the higher the latency requirement of a service, the more sensitive the service is to transmission latency; conversely, the lower the latency requirement of a service, the less sensitive the service is to transmission latency.

[0280] For example, the latency requirements of a service can be represented by the packet delay budget (PDB). The higher the latency requirements of the service, the smaller the PDB; conversely, the lower the latency requirements of the service, the larger the PDB.

[0281] For example, the second service can be a service sensitive to transmission latency, such as autonomous driving, industrial remote control, or telemedicine. The first service can be a service insensitive to transmission latency, such as smart meter reading.

[0282] Optionally, the terminal device can select the QoS flow based on the latency requirements of the service, thereby achieving energy saving of the access network equipment while meeting service requirements. For details, please refer to [link to documentation]. Figure 6 The detailed descriptions of steps S803 to S807 can be found in the detailed descriptions of steps S603 to S607, and will not be repeated here. The following is an introduction... Figure 8 and Figure 5 to Figure 8 The different steps are S801 and S802.

[0283] Step S801: The terminal device obtains the first inactive period parameter and the second inactive period parameter.

[0284] The first inactive period parameter corresponds to the first QoS flow between the terminal device and the user plane network element, and the second inactive period parameter corresponds to the second QoS flow between the terminal device and the user plane network element. The inactive period parameter includes a period. For example, the first inactive period parameter is the duration of the first period and the first active period; the second inactive period parameter is the duration of the second period and the second active period.

[0285] The correspondence between inactive period parameters and QoS flows can be determined by the session management network element or access network device. For details, please refer to the relevant description in step S501, which will not be repeated here.

[0286] Optionally, for each period, the period can correspond to a QoS flow, or it can correspond to a QoS subflow.

[0287] In this application, multiple QoS sub-streams corresponding to multiple periods can belong to the same QoS stream or different QoS streams, and this embodiment does not impose any limitations on this. For example, 100ms can correspond to the first QoS sub-stream, and 200ms can also correspond to the first QoS sub-stream. Furthermore, the first QoS sub-stream and the second QoS sub-stream can belong to the same QoS stream.

[0288] Optionally, multiple QoS sub-streams belonging to the same QoS flow may correspond to different periods, and the QoS rules (such as priority) corresponding to multiple QoS sub-streams belonging to the same QoS flow may be the same. It is understood that these multiple QoS sub-streams can be considered to belong to the same QoS flow, or they can be considered to be multiple independent QoS flows, such as QoS flows with the same priority, without restriction.

[0289] The following explanation uses a periodic QoS flow as an example. The description of a periodic QoS subflow can be found in the following description of a periodic QoS flow, and will not be repeated here.

[0290] For each QoS flow, the period can include an active period and an inactive period. During the active period, the terminal device can monitor the PDCCH, and the access network device can send information to the terminal device through the PDCCH, which indicates the resources for data transmission. After receiving this information on the PDCCH, the terminal device can transmit data on the resources indicated by the information. During the inactive period, the terminal device may not monitor the PDCCH, and the access network device may not send any information through the PDCCH.

[0291] For example, the period in the embodiments of this application can be a cell DTX cycle or a cell DTX cycle period. The period or cycle period can also be referred to as a time interval.

[0292] For example, the period in this application embodiment can be time-domain information added to the QoS parameters.

[0293] When the correspondence between the period and the QoS flow is determined by the session management network element, when the access network device transmits data through the RB corresponding to the QoS flow, it can use the period corresponding to the QoS flow determined by the session management network element, or it can use a period smaller than the period corresponding to the QoS flow determined by the session management network element. The device will then send the information of the actual period corresponding to the QoS flow used to the terminal device. For example, when the load on the access network device is low, or the network throughput is low, the access network device can use a period smaller than the period corresponding to the QoS flow determined by the session management network element for data transmission.

[0294] For example, if the QoS flow 1 determined by the session management network element has a period of 100ms, when the RAN transmits data through the RB corresponding to the QoS flow, it can transmit data with a period of 100ms, or it can transmit data with a period smaller than 100ms, such as 80ms.

[0295] Step S802: The terminal device determines that the first QoS stream is used for downlink data transmission.

[0296] Among them, the first QoS flow meets the latency requirements of the first service to which the downlink data belongs, that is, the first period is less than or equal to the latency requirements of the first service.

[0297] exist Figure 9 In this process, the terminal device can determine the QoS flow (e.g., the first QoS flow) that meets the service latency requirements of the first service as the target QoS flow. Specific examples can be found in the description of step S903 below, and will not be repeated here.

[0298] Combination Figure 11 , Figure 10 A flowchart illustrating a specific example of the communication method provided in this application is shown, including the following steps:

[0299] In step S901, the SMF can send configuration information for one or more QoS flows to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive configuration information for one or more QoS flows from the SMF.

[0300] The multiple QoS flows include a first QoS flow and a second QoS flow. For example, the multiple QoS flows may be a default QoS flow. The configuration information for the QoS flows may include the mapping (or association) between QoS flows and periods. Optionally, the configuration information for the QoS flows may also include one or more of the following: QFI, QoS parameters, or PFS rules.

[0301] The SMF can acquire one or more periods, determine the corresponding (or associated) QoS flow for each period, and send the configuration information of the QoS flow corresponding to each period to the UE, RAN, and UPF.

[0302] In one possible implementation, the RAN can send one or more cycles of information to the SMF, and the SMF determines the configuration information of the aforementioned QoS flow based on the one or more cycles of information sent by the RAN.

[0303] The RAN can generate one or more periods, such as 100 milliseconds (ms), 200 ms, and 500 ms, based on its energy-saving needs or strategies. Optionally, the RAN's energy-saving needs or strategies can be determined based on the RAN's load at different times. When the RAN's load is low, a longer period is generated; when the RAN's load is high, a shorter period is generated. The RAN can send one or more periods of information to the SMF. Correspondingly, the SMF can receive one or more periods of information from the RAN, thereby generating configuration information for the corresponding QoS flow for each period. For example, 100 ms can correspond to QoS flow 1, 200 ms to QoS flow 2, and 500 ms to QoS flow 3.

[0304] Optionally, information from one or more cycles can be carried in the NG setup request message, or in the initial UE message, as detailed below. Figure 9 The relevant descriptions in the text will not be repeated here.

[0305] Optionally, unlike the above-mentioned method where the SMF determines the QoS flow configuration information corresponding to each period based on one or more periods sent by the RAN, after the RAN generates one or more periods, it may not need to send one or more periods to the SMF. The SMF can determine the configuration information of one or more QoS flows by referring to the relevant description in the communication protocol and send it to the RAN. This QoS flow configuration information does not include periods (i.e., it does not include the correspondence between periods and QoS flows). After receiving the configuration information of one or more QoS flows from the SMF, the RAN can establish the correspondence between QoS flows and periods and send the correspondence to the UE so that the UE can subsequently determine the QoS flows that meet the service requirements.

[0306] When establishing the correspondence between QoS flows and periods, the RAN can determine the maximum value of the delay for the RAN to send data to the UE through the RB corresponding to the QoS flow, based on the service quality (or data transmission delay) corresponding to the QoS flow. This maximum value can be the difference between the data transmission delay corresponding to the QoS flow and the data transmission delay between the UPF and the RAN. The period corresponding to the QoS flow is then determined based on this maximum value, wherein the period corresponding to the QoS flow is less than or equal to the maximum value corresponding to the QoS flow.

[0307] Optionally, when the SMF communicates with the UE or RAN, it can be transparently transmitted through the AMF.

[0308] Optionally, the multiple QoS flows configured in step S901 can be core network (CN), such as those pre-authorized by the SMF. In other words, the CN (or SMF) can establish multiple QoS flows for the UE before service data arrives or is transmitted, for the UE to use. For example, the UE's successful access to the network can trigger the CN to establish multiple QoS flows.

[0309] Step S902: The RAN may send configuration information of one or more RBs to the UE. Accordingly, the UE receives configuration information of one or more RBs from the RAN. In this embodiment, the RB may include at least one of a DRB or a signaling radio bearer (SRB).

[0310] One Resource Block (RB) can correspond to one or more QoS flows, and one QoS flow can correspond to one RB. For example, as Figure 10 As shown, QoS flow 1 can correspond to DRB 1, QoS flow 2 can correspond to DRB 2, and QoS flow 3 can correspond to DRB 3.

[0311] The RAN can configure the corresponding QoS flow based on the received QoS flow configuration information. The RAN can also configure the corresponding RB for the QoS flow and send the RB configuration information to the UE. The UE can then configure the RB corresponding to the QoS flow based on the received RB configuration information.

[0312] For example, when the QoS flow configuration information does not include the mapping between QoS flows and periods, the method by which the RAN configures the corresponding QoS flow based on the QoS flow configuration information can be found in existing protocols. When the QoS flow configuration information includes the mapping between QoS flows and periods, the RAN can also control the RAN to send data on the RB corresponding to the QoS flow of the period according to the period.

[0313] Step S903: The UE determines the first QoS flow based on the latency requirements of the first service.

[0314] exist Figure 16 to Figure 18 In this process, the terminal device can determine the QoS flow (e.g., the first QoS flow) that meets the service latency requirements of the first service as the target QoS flow.

[0315] Among them, the period corresponding to the first QoS flow is less than or equal to the latency requirement of the first service to which the downlink data belongs.

[0316] For example, the UE's modem can obtain the application's (APP's) service requirements through the attention (AT) command set. These service requirements can be statistically analyzed by the operating system (OS) and may include the latency requirements corresponding to the service.

[0317] Service latency requirements are positively correlated with one or more of the following: the size of the UE's transport layer buffer, or the size of the UE's network layer buffer. The more data buffered, the better the user experience is guaranteed. Even if the UE doesn't receive new downlink data for a short period, it won't affect the user's experience. For example, with a large amount of buffered video data, if the UE doesn't receive new downlink video data for a short time, the UE can use the buffered video data for playback, preventing video stuttering and ensuring a good user experience. In other words, the larger the UE's transport layer and / or network layer buffers, the lower the service latency requirements. Figure 10 Taking the service to which the downlink data belongs as the first service, APP2, as an example, step S903 will be explained. The UE's OS can statistically analyze the service requirements of APP1, APP2, and APP3. The UE's modem can obtain the service requirements of APP2 from the OS and select QoS stream 1 from QoS stream 1, QoS stream 2, and QoS stream 3 based on the obtained service requirements; that is, the first QoS stream is QoS stream 1. For example, assuming the service latency requirement is 120ms, the period corresponding to QoS stream 1 is 100ms, the period corresponding to QoS stream 2 is 200ms, and the period corresponding to QoS stream 3 is 500ms, then the first QoS stream selected by the UE's modem can be QoS stream 1. This is because the period corresponding to QoS stream 1 is less than the latency requirement of the first service to which the downlink data belongs, which can meet the latency requirement of the service and thus ensure user experience. For example, the second QoS stream can be QoS stream 2 or QoS stream 3.

[0318] In one possible implementation, when only one QoS flow is configured in step S901 and only one RB corresponding to the QoS flow is configured in step S902, the UE can determine in step S903 whether this QoS flow meets the requirements of the first service to which the downlink data belongs. If it does, the QoS flow can be considered the first QoS flow, meaning the period corresponding to the first QoS flow is less than or equal to the latency requirement of the first service to which the downlink data belongs. If it does not meet the requirements, see the following... Figure 10 The embodiments shown are not described in detail here.

[0319] Step S904: The UE can map the uplink data of the service to the first RB corresponding to the first QoS flow, and add the first information to the SDAP header of the data packet.

[0320] For example, the first information can be RQI or QFI.

[0321] Combination Figure 10 Uplink data can be mapped to DRB1 corresponding to the selected QoS stream 1.

[0322] Optionally, when registering with the network, the UE may send indication information to the SMF and UDM to indicate that the UE has the ability to add first information. Correspondingly, the SMF and UDM may receive the indication information from the UE indicating that the UE has the ability to add first information. The SMF may send control information to the UE, RAN, and UPF. The control information may be used to indicate that the UE, RAN, and UPF are allowed to use the first information. Correspondingly, the UE, RAN, and UPF may receive the control information from the SMF and, according to the control information, execute step S904, which involves the UE adding the first information to the SDAP header of the data packet, as well as steps S905 and S906.

[0323] Steps S904 to S906 below are used to add an RQI to the header of a data packet including uplink data and transmit it via DRB1 or QoS stream 1. The purpose is to enable the network to be aware of the first QoS stream selected by the UE for transmitting downlink data. That is, the RQI and the RB or QoS stream carrying the RQI can be used to uniquely identify the first QoS stream.

[0324] Alternatively, steps S904 to S906 below are used to add a QFI to the header of a data packet including uplink data and transmit it via DRB1 or any QoS stream, with the aim of enabling the network to be aware of the first QoS stream selected by the UE for transmitting downlink data. That is, the QFI can be used to uniquely identify the first QoS stream.

[0325] For example, step S904 can be performed by the SDAP layer of the UE.

[0326] In step S905, the UE may send a data packet with the SDAP header including the first information to the RAN. Correspondingly, the RAN may receive the data packet with the SDAP header including the first information from the UE.

[0327] Combination Figure 9 Data packets carrying RQI or QFI can reach the RAN's SDAP layer via the UE's SDAP layer, UE's MAC layer, UE's PHY layer, RAN's PHY layer, and RAN's MAC layer.

[0328] In step S906, the RAN can parse the first information from the SDAP header, add the first information to the GTP-U header of the data packet, and send the data packet with the first information in the GTP-U header to the UPF through the first QoS flow. Correspondingly, the UPF can receive the data packet with the first information in the GTP-U header from the RAN through the first QoS flow.

[0329] Combination Figure 9 The RAN can parse the RQI or QFI from the SDAP header and add the RQI or QFI to the GTP-U header of the data packet. That is, the RAN can parse the RQI from the SDAP header and add the RQI or QFI to the GTP-U header of the data packet; or, the RAN can parse the QFI from the SDAP header and add the RQI or QFI to the GTP-U header of the data packet.

[0330] When the GTP-U header of a data packet includes RQI, the data packet can be transmitted via the first QoS stream.

[0331] When the GTP-U header of a data packet includes a QFI, the data packet can be transmitted via any QoS stream. This is because the QFI can uniquely identify a QoS stream, so after receiving the QFI, the UPF can determine that the first QoS stream selected by the UE is the QoS stream corresponding to that QFI, regardless of which QoS stream the QFI is transmitted through.

[0332] For example, when the GTP-U header of a data packet includes QFI=1, even if the data packet is transmitted through QoS stream 2 or QoS stream 3, the UPF can still determine that the first QoS stream selected by the UE is QoS stream 1 after receiving QFI=1.

[0333] Step S907: The UPF can generate downlink data processing rules. These downlink data processing rules may include at least one of a forwarding action rule (FAR) or a packet detection rule (PDR).

[0334] In one possible implementation, the UPF can use the source IP address A included in the uplink data packet as the destination IP address B, and the destination IP address A included in the uplink data packet as the source IP address B, and associate the swapped source IP address B and destination IP address B with the first QoS flow. Therefore, when the downlink data packet arrives at the UPF, if the downlink data packet includes both source IP address B and destination IP address B, then the UPF can execute step S908.

[0335] In another possible implementation, the UPF can associate the target server with the first QoS flow. Therefore, when a downstream data packet arrives at the UPF, if the downstream data packet originates from the target server, the UPF can execute step S908.

[0336] Optionally, the downlink data processing rules can be CN, specifically pre-authorized by SMF. In other words, the CN (or SMF) can authorize the UPF to use the downlink data processing rules before the service data arrives or is transmitted; or, the downlink data processing rules are default.

[0337] In step S908, the UPF can map downlink data onto the first QoS stream.

[0338] In step S909, the UPF can send downlink data to the RAN through the first QoS stream. Correspondingly, the RAN can receive downlink data from the UPF through the first QoS stream.

[0339] In step S910, the RAN can send information indicating resources for downlink data transmission to the UE through the channel between the UE and the RAN during periods other than the inactive period corresponding to the first QoS flow. Correspondingly, the UE can monitor the channel between the UE and the RAN to receive downlink data during periods other than the inactive period corresponding to the first QoS flow.

[0340] The information used to indicate the resources for downlink data transmission can be, for example, DCI, or other information used to indicate the resources for downlink data transmission.

[0341] In step S911, the RAN can send downlink data to the UE through the first RB. Accordingly, the UE can receive downlink data from the RAN through the first RB on the resource indicated by the above information.

[0342] exist Figure 11 In the illustrated embodiment, the UE can determine the first QoS flow based on the latency requirements of the first service. On one hand, the determination of the first QoS flow takes into account the latency requirements of the first service, thus using the first QoS flow to transmit downlink data is beneficial for meeting service requirements. On the other hand, when the SMF configures multiple QoS flows, the first QoS flow can be the QoS flow selected by the UE that meets the service requirements. Since the communication method provided in this application embodiment offers QoS flow selectivity, the flexibility of energy-saving scheme implementation can be improved.

[0343] Based on the above Figure 11 The method shown above, specifically the timing of sending one or more periods of information mentioned in step S901, can be found in [reference needed]. Figure 9 The flowchart shown.

[0344] Before establishing an RRC connection, the RAN may send and save one or more cycles of information to the AMF, referring to steps S1101 and S1102 below; or, after establishing an RRC connection, the RAN may send and save one or more cycles of information to the AMF, referring to steps S1105 and S1106 below.

[0345] Step S1101: The RAN can send an NG interface establishment request message to the AMF. The NG interface establishment request message includes information from one or more cycles. Correspondingly, the AMF can receive the NG interface establishment request message from the RAN.

[0346] Step S1102: The AMF can store information for one or more cycles.

[0347] Optionally, such as Figure 9 As shown in step S1103, the AMF can also send an NG interface establishment response message to the RAN. Accordingly, the RAN can receive the NG interface establishment response message from the AMF.

[0348] Step S1104: Establish an RRC connection between the UE and the RAN.

[0349] In step S1105, the RAN can send an initial UE message to the AMF, which includes information from one or more cycles. Correspondingly, the AMF can receive the initial UE message from the RAN.

[0350] Step S1106: The AMF can store information for one or more cycles.

[0351] Based on the above steps, after obtaining information for one or more cycles, the AMF can send information for one or more cycles to the SMF by referring to the following steps, so that the SMF can determine and distribute the QoS flow configuration information corresponding to each cycle based on the information for one or more cycles.

[0352] Step S1107: The UE can send a PDU session establishment request to the AMF through the RAN. Correspondingly, the AMF can receive the PDU session establishment request from the UE through the RAN.

[0353] Step S1108: The AMF can send a PDU session establishment request to the SMF. The PDU session establishment request includes information from one or more cycles. Correspondingly, the SMF can receive the PDU session establishment request from the AMF.

[0354] Step S1109: SMF can generate configuration information for the corresponding QoS flow for each period.

[0355] The SMF can obtain subscription data from the UDM. For each period, such as period 1, in one possible implementation, the SMF can send the subscription data and period 1 to the PCF, which then generates a QoS policy for period 1 and sends the generated QoS policy back to the SMF. Thus, the SMF can generate the corresponding QoS flow configuration information for period 1. In another possible implementation, the SMF can generate a QoS policy based on the subscription data and period 1, and also generate the corresponding QoS flow configuration information for period 1.

[0356] After SMF generates the configuration information for the corresponding QoS flow for each period, it can be referenced. Figure 9 The method shown sends the configuration information of the QoS flow to the UE, RAN and UPF, so that the UE can determine the first QoS flow according to the latency requirements of the service, and notify the UPF of the determined first QoS flow through the RAN.

[0357] Optionally, the AMF can send a PDU session resourcesetup request message to the RAN. Correspondingly, the RAN can receive a PDU session resources setup request message from the AMF. The RAN can also send a PDU session resources setup response message to the AMF. Correspondingly, the AMF can receive a PDU session resources setup response message from the RAN.

[0358] Optionally, with the above Figure 12 Unlike the UE which adds the first information to the SDAP header of the data packet, the UE can also add the first information to the IP header of the data packet. Based on this, the RAN can directly forward the data packets sent by the UE without parsing the IP header of the data packet, thereby achieving the technical effect of improving the transmission speed of the first information.

[0359] Combination Figure 9 to Figure 12 A flowchart of a specific example can be found here. Figure 13 This includes the following steps:

[0360] In step S1201, the SMF can send configuration information for one or more QoS flows to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive configuration information for one or more QoS flows from the SMF.

[0361] For a detailed description of step S1201, please refer to the detailed description of step S901, which will not be repeated here.

[0362] In step S1202, the RAN can send configuration information of one or more RBs to the UE. Accordingly, the UE receives configuration information from one or more RBs of the RAN.

[0363] For a detailed description of step S1202, please refer to the detailed description of step S902, which will not be repeated here.

[0364] Step S1203: The UE determines the first QoS flow based on the latency requirements of the first service. The period corresponding to the first QoS flow is less than or equal to the latency requirements of the first service.

[0365] For a detailed description of step S1203, please refer to the detailed description of step S903, which will not be repeated here.

[0366] Step S1204: The UE can map the uplink data of the first service to the first RB corresponding to the first QoS flow, and add the first information to the IP header of the data packet.

[0367] For example, the first information can be RQI or QFI.

[0368] The mapping process of the upstream data of the business can be found in the description of step S904, and will not be repeated here.

[0369] In step S1205, the UE can send a data packet with the first information in the IP header to the UPF via the RAN. Correspondingly, the UPF can receive a data packet with the first information in the IP header from the UE via the RAN.

[0370] The UE and RAN can communicate through the first RB.

[0371] The QoS flow used for communication between the RAN and UPF depends on whether the IP packet header includes QFI or RQI. For example, when the IP packet header includes RQI, the RAN and UPF can communicate through the first QoS flow. This is because RQI cannot uniquely identify a QoS flow; it needs to be used in conjunction with the QoS flow carrying the RQI to uniquely identify a QoS flow. After receiving an RQI through a certain QoS flow, the UPF can determine the QoS flow carrying the RQI as the first QoS flow selected by the UE.

[0372] When the IP header of a data packet includes a QFI, the RAN and UPF can communicate through any QoS flow. This is because the QFI uniquely identifies the QoS flow. After receiving the QFI, the UPF can determine that the UE has selected the first QoS flow, regardless of which QoS flow the QFI was transmitted through.

[0373] For example, when the IP header of a data packet includes QFI=1, even if the data packet is transmitted through QoS flow 2 or QoS flow 3, the UPF can still determine that the first QoS flow selected by the UE is QoS flow 1 after receiving QFI=1.

[0374] Step S1206: UPF can generate processing rules for downlink data.

[0375] For a detailed description of step S1206, please refer to the detailed description of step S907, which will not be repeated here.

[0376] Step S1207: After the downlink data arrives, the UPF can map the downlink data to the first QoS stream.

[0377] For a detailed description of step S1207, please refer to the detailed description of step S908, which will not be repeated here.

[0378] In step S1208, the UPF can send downlink data to the RAN through the first QoS stream. Correspondingly, the RAN can receive downlink data from the UPF through the first QoS stream.

[0379] Step S1209: Outside of the inactive period corresponding to the first QoS flow, the RAN can send information about resources indicating downlink data transmission to the UE through the channel between the UE and the RAN. The UE can monitor the channel between the UE and the RAN to receive downlink data.

[0380] For a detailed description of step S1209, please refer to the detailed description of step S910, which will not be repeated here.

[0381] In step S1210, the RAN can send downlink data to the UE through the first RB. Accordingly, the UE can receive downlink data from the RAN through the first RB on the resource indicated by the above information.

[0382] With the above Figure 14 The RAN and UE establish and maintain a single RB for each QoS flow, unlike other systems, to conserve air interface resources, allowing the RAN and UE to establish and maintain only one RB for multiple QoS flows. When data transmission occurs on the first QoS flow selected by the terminal device, a first RB can be established for that first QoS flow, allowing downlink data to be transmitted through the first RB to meet service requirements. A flowchart illustrating this can be found in [link to flowchart example]. Figure 14 This includes the following steps:

[0383] In step S1301, the SMF can send configuration information for multiple QoS flows to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive configuration information for multiple QoS flows from the SMF.

[0384] For a detailed description of step S1301, please refer to the detailed description of step S901, which will not be repeated here.

[0385] Step S1302: The RAN can send an RB configuration information to the UE.

[0386] The UE can configure an RB based on the received configuration information of that RB. The RAN can configure the corresponding QoS flow based on the received QoS flow configuration information. The RAN can also configure that RB. The RB configured by the UE and the RAN can correspond to one of multiple QoS flows.

[0387] For example, this RB can be a default RB.

[0388] It is understood that the RB configured by the UE and RAN can be used to transmit uplink data packets including different values ​​of QFI. In other words, the RB in this embodiment can be used for uplink transmission of data packets corresponding to different QoS flows. Figure 13 As shown, this RB can be used to transmit data packets including those with QFI values ​​of 1, 2, or 3; or, this RB can be used to transmit data packets corresponding to QoS stream 1, QoS stream 2, or QoS stream 3 uplink.

[0389] Step S1303: The UE can determine the first QoS flow based on the latency requirements of the first service. The period corresponding to the first QoS flow is less than or equal to the latency requirements of the first service.

[0390] For a detailed description of step S1303, please refer to the detailed description of step S903, which will not be repeated here.

[0391] Step S1304: The UE can map the uplink data of the first service to this RB and add QFI in the SDAP packet header.

[0392] In step S1305, the UE can send a data packet with the SDAP header including the first information to the RAN. Correspondingly, the RAN can receive the data packet with the SDAP header including the first information from the UE.

[0393] For example, the first information can be QFI.

[0394] Combination Figure 15Data packets carrying QFI can travel through the UE's SDAP layer, UE's MAC layer, UE's PHY layer, RAN's PHY layer, and RAN's MAC layer to reach the RAN's SDAP layer. The UE and RAN can communicate through a single RB. The RAN can determine the first QoS flow selected by the terminal device based on the QFI in the data packet.

[0395] In step S1306, the RAN can parse the first information from the SDAP header, add the first information to the GTP-U header of the data packet, and send the data packet with the first information in the GTP-U header to the UPF. Correspondingly, the UPF can receive the data packet with the first information in the GTP-U header from the RAN.

[0396] For example, the RAN can parse the QFI from the SDAP header, add the QFI or RQI to the GTP-U header of the data packet, and send the data packet with the QFI or RQI included in the GTP-U header to the UPF. Accordingly, the UPF can receive the data packet with the QFI or RQI included in the GTP-U header from the RAN.

[0397] For a detailed description of step S1306, please refer to the detailed description of step S906, which will not be repeated here.

[0398] Step S1307: UPF can generate processing rules for downlink data.

[0399] For a detailed description of step S1307, please refer to the detailed description of step S907, which will not be repeated here.

[0400] Step S1308: After the downlink data arrives, the UPF can map the downlink data to the first QoS stream.

[0401] For a detailed description of step S1308, please refer to the detailed description of step S908, which will not be repeated here.

[0402] In step S1309, the UPF can send downlink data to the RAN through the first QoS flow. Correspondingly, the RAN can receive downlink data from the UPF through the first QoS flow.

[0403] Step S1310: Outside of the inactive period corresponding to the first QoS flow, the RAN can send information about resources indicating downlink data transmission to the UE through the channel between the UE and the RAN. The UE can monitor the channel between the UE and the RAN to receive downlink data.

[0404] For a detailed description of step S1310, please refer to the detailed description of step S910, which will not be repeated here.

[0405] In step S1310, the RAN can send downlink data to the UE through the first RB. Correspondingly, the UE can receive downlink data from the RAN through the first RB on the resource indicated by the above information. The first RB can be the existing RB or a newly established RB.

[0406] Optionally, the RAN and UE may determine the first RB based on either method one or method two:

[0407] Method 1: Designate this RB as the first RB.

[0408] Optionally, the RAN can determine whether the RB is the first RB corresponding to the first QoS flow. As described in step S1302, the RB corresponds to one of the multiple QoS flows. When the first QoS flow indicated by the QFI is the RB, the RAN can determine that the RB is the first RB corresponding to the first QoS flow; when the first QoS flow indicated by the QFI is not the RB, the RAN can determine that the RB is not the first RB corresponding to the first QoS flow. If the RB is the first RB corresponding to the first QoS flow, then the RB is determined to be the first RB. If the RB is not the first RB corresponding to the first QoS flow, then the RAN executes method two.

[0409] The process of determining whether an RB is the first RB corresponding to the first QoS flow can be performed when the RAN receives the QFI, or when it receives downlink data.

[0410] Method 2: Create a new RB for the first QoS flow.

[0411] Among them, the RAN can send RRC configuration information to the UE, triggering the RAN and UE to create a new RB for the first QoS flow.

[0412] Optionally, the RAN can determine whether an RB corresponds to the first QoS flow when it receives QFI. If not, it can send RRC configuration information to the UE to trigger the establishment of the first RB. Alternatively, the RAN can determine whether an RB corresponds to the first QoS flow when it receives downlink data. If not, it can send RRC configuration information to the UE to trigger the establishment of the first RB.

[0413] In addition, with the above Figure 13 The difference between how UE adds QFI to the SDAP header of data packets is as follows: Figure 15 As shown, the UE can also add QFI to the IP header of the data packet. Based on this, the RAN can directly forward the data packets sent by the UE without parsing the IP header of the data packet, thereby achieving the technical effect of improving the transmission speed of QFI.

[0414] Combination Figure 9 to Figure 15 A flowchart of a specific example can be found here. Figure 16 to Figure 18 This includes the following steps:

[0415] In step S1501, the SMF can send configuration information for multiple QoS flows to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive configuration information for multiple QoS flows from the SMF.

[0416] For a detailed description of step S1501, please refer to the detailed description of step S1301, which will not be repeated here.

[0417] Step S1502: The RAN can send an RB configuration information to the UE.

[0418] For a detailed description of step S1502, please refer to the detailed description of step S1302, which will not be repeated here.

[0419] Step S1503: The UE can determine the first QoS flow based on the latency requirements of the first service. The period corresponding to the first QoS flow is less than or equal to the latency requirements of the first service.

[0420] For a detailed description of step S1503, please refer to the detailed description of step S1303, which will not be repeated here.

[0421] Step S1504: The UE can map the uplink data of the first service to this RB and add QFI in the IP packet header.

[0422] The relevant description of the mapping process of the business's upstream data can be found in the relevant description of step S1304, and will not be repeated here.

[0423] Step S1505: The UE sends a data packet with the QFI header to the UPF via the RAN. Correspondingly, the UPF can receive a data packet with the first information in the IP header from the UE via the RAN.

[0424] For example, the first information can be QFI or RQI.

[0425] The UE and RAN can communicate through this single RB. The RAN and UPF can communicate through any QoS flow. For a detailed description, please refer to the relevant description in step S1205, which will not be repeated here.

[0426] Step S1506: UPF can generate processing rules for downlink data.

[0427] For a detailed description of step S1506, please refer to the detailed description of step S1307, which will not be repeated here.

[0428] Step S1507: After the downlink data arrives, the UPF can map the downlink data to the first QoS stream.

[0429] For a detailed description of step S1507, please refer to the detailed description of step S1308, which will not be repeated here.

[0430] In step S1508, the UPF can send downlink data to the RAN through the first QoS stream. Correspondingly, the RAN can receive downlink data from the UPF through the first QoS stream.

[0431] Step S1510: Outside of the inactive period corresponding to the first QoS flow, the RAN can send information about resources indicating downlink data transmission to the UE through the channel between the UE and the RAN. The UE can monitor the channel between the UE and the RAN to receive downlink data.

[0432] For a detailed description of step S1510, please refer to the detailed description of step S910, which will not be repeated here.

[0433] Step S1511: The RAN can send downlink data to the UE through the first RB. Correspondingly, the UE can receive downlink data from the RAN through the first RB on the resource indicated by the above information. The first RB can be the existing RB or a newly established RB.

[0434] Optionally, the RAN and UE may determine the first RB based on either method one or method two:

[0435] Method 1: Designate this RB as the first RB.

[0436] Because the QFI is added to the IP packet header, the RAN does not parse it. Therefore, the RAN does not determine whether a received RB is the first RB corresponding to the first QoS flow upon receiving the QFI. The RAN can determine whether a received RB is the first RB corresponding to the first QoS flow upon receiving downlink data; if so, it will identify that RB as the first RB.

[0437] Method 2: Create a new RB for the first QoS flow.

[0438] Among them, the RAN can send RRC configuration information to the UE, triggering the RAN and UE to create a new RB for the first QoS flow.

[0439] Based on the reasoning in Method 1, when the RAN receives downlink data, it can determine whether the RB is the first RB corresponding to the first QoS flow. If not, it can send RRC configuration information to the UE as shown in step S1509 to trigger the establishment of the first RB.

[0440] In the above Figure 16 In the illustrated embodiment, for steps S903, S1203, S1303, and S1503, the UE can determine a first QoS flow that meets the service requirements. In other words, a first QoS flow exists among the configured one or more QoS flows, and the first QoS flow satisfies the condition that its corresponding period is less than or equal to the latency requirement of the first service. However, there may not be a first QoS flow that meets the service requirements among the configured one or more QoS flows, i.e., the periods corresponding to one or more QoS flows are all greater than the latency requirement of the first service. For example, the configured multiple QoS flows are QoS flow 1, QoS flow 2, and QoS flow 3, with corresponding periods of 100ms, 200ms, and 500ms, respectively. The latency requirement of the first service is 10ms. The periods corresponding to all three QoS flows are greater than the latency requirement of the first service, therefore none of the three QoS flows can meet the latency requirement of the first service. In this case, Figure 17 Flowcharts for different specific examples are shown. Among them, in Figure 18 and Figure 16 In the illustrated embodiment, the UE can trigger the core network to configure QoS flows from the control plane; Figure 17 In the embodiment shown, the UE can trigger the core network to configure QoS flows from the user plane.

[0441] In one possible implementation, after determining that the first QoS flow does not exist among one or more QoS flows, the UE can request the SMF to configure a first QoS flow that meets the service requirements via control signaling (e.g., a NAS message). The control signaling may carry the QoS parameters of the requested first QoS flow. For details, please refer to [link to specific procedures]. Figure 17 It includes the following steps:

[0442] In step S1601, the SMF can send configuration information for one or more QoS flows to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive configuration information for one or more QoS flows from the SMF.

[0443] For a detailed description of step S1601, please refer to the detailed description of step S901, which will not be repeated here.

[0444] Step S1602: The RAN can send configuration information of one or more RBs to the UE.

[0445] Optionally, there is a one-to-one correspondence between RBs and QoS flows, as detailed in step S902. Alternatively, the RAN may configure only one RB, as detailed in step S1302. This application embodiment does not impose any limitations on this.

[0446] Step S1603: The UE can determine that there is no first QoS flow that meets the service requirements among one or more QoS flows.

[0447] Step S1604: The UE sends a NAS message to the SMF via the RAN. Correspondingly, the SMF receives the NAS message from the UE via the RAN. The NAS message carries the QoS parameters of the requested first QoS flow, used to request the SMF to configure the first QoS flow.

[0448] Optionally, the QoS parameters of the first QoS stream carried in the NAS message may include the period corresponding to the first QoS stream. That is, the NAS message may carry a period, and this period is less than or equal to the latency requirement of the first service. For example, if the latency requirement of the first service is 10ms, the NAS message may carry 5ms. Optionally, the NAS message may also carry 0ms to indicate that the first QoS stream can be the default QoS stream, or to indicate that the RAN needs to exit power-saving mode when sending downlink data through the first RB corresponding to the first QoS stream.

[0449] Alternatively, the QoS parameters of the first QoS stream carried in the NAS message may not include the period corresponding to the first QoS stream. For example, the NAS message may carry the QoS parameters of the default QoS stream to indicate that the first QoS stream is the default QoS stream, or to indicate that the RAN needs to exit power saving mode when sending downlink data through the first RB corresponding to the first QoS stream.

[0450] Specifically, for the default QoS flow, as long as downlink data reaches the RAN through the default QoS flow, the RAN will continuously send downlink data to the UE.

[0451] Optionally, the NAS message may also carry the QFI of the first QoS flow. Assuming the multiple QoS flows configured in step S1601 are QoS flow 1, QoS flow 2, and QoS flow 3, with corresponding periods of 100ms, 200ms, and 500ms respectively, if the NAS message carries QFI=1, then the NAS message is used to request the SMF to modify the configuration information of QoS flow 1; that is, the NAS message is used to request the SMF to change the period corresponding to QoS flow 1 from 100ms to 5ms. If the NAS message carries QFI=4, then the NAS message is used to request the SMF to add QoS flow 4, and the period corresponding to QoS flow 4 is 5ms.

[0452] When a NAS message carries the QoS parameters of the requested first QoS stream but not the QFI of the first QoS stream, whether to modify the configuration information of an already configured QoS stream or to add the configuration information of a new QoS stream to obtain the configuration information of the first QoS stream, the decision can be made by the SMF or specified by the protocol.

[0453] In step S1605, the SMF can send the configuration information of the first QoS flow to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive the configuration information of the first QoS flow from the SMF.

[0454] Optionally, the SMF can send the QFI and PFS rules corresponding to the first QoS flow to the UPF. If the downlink data satisfies the PFS rules corresponding to the first QoS flow, the UPF can map the downlink data to the first QoS flow. Optionally, the SMF can also send the QoS parameters of the first QoS flow to the UPF. The SMF can send the QFI and QoS parameters to the RAN, so that the RAN can map the first QoS flow to the corresponding first RB. The SMF can send the QFI and PFS rules to the UE. If the uplink data satisfies the PFS rules, the UE can map the uplink data packets to the first QoS flow. The specific process can be referred to in the prior art for the issuance and execution of QoS policies, and will not be elaborated here.

[0455] For example, the first QoS flow can be the default QoS flow in the prior art. That is, the configuration information of the first QoS flow can be the configuration information of the default QoS flow in the prior art, excluding the period.

[0456] Step S1606: The RAN sends an RRC reconfiguration message to the UE. The RRC reconfiguration message is used to reconfigure the first RB corresponding to the first QoS flow. Correspondingly, the UE receives the RRC reconfiguration message from the RAN.

[0457] Reconfiguring the first RB can be understood as re-establishing or adding the first RB; or, reconfiguring the first RB can be understood as obtaining the first RB by modifying an already configured RB.

[0458] As described in steps S1604 and S1605, in one possible implementation, the SMF can modify the configuration information of the already configured QoS flow to ensure that the modified QoS flow meets the latency requirements of the first service. That is, the SMF can obtain the configuration information of the first QoS flow by modifying the configuration information of the already configured QoS flow. If the RB corresponding to the aforementioned configured QoS flow has also been configured, the RAN can modify the configuration information of that RB to obtain the configuration information of the first RB.

[0459] For example, if the RAN changes the period corresponding to QoS flow 1 from 100ms to 5ms to obtain the first QoS flow, the first RB can be obtained by modifying the configuration information of DRB 1 corresponding to QoS flow 1. For example, the PDCP discard timer in the configuration information of DRB 1 can be modified to obtain the first RB corresponding to the first QoS flow.

[0460] As described in steps S1604 and S1605, in another possible implementation, the SMF can add configuration information for the QoS flow to obtain the configuration information for the first QoS flow. In this case, the RAN can add or re-establish the first RB corresponding to the first QoS flow.

[0461] For example, if the RAN adds a new QoS flow 4 with a corresponding period of 5ms to obtain the first QoS flow, then the first RB can be the newly added DRB 4.

[0462] Step S1607: After the downlink data arrives, the UPF can map the downlink data to the first QoS stream according to the configuration information of the first QoS stream received in step S1605.

[0463] Furthermore, the UPF can map downlink data to the first QoS stream according to the QFI and PFS rules corresponding to the first QoS stream received in step S1605. For example, if the downlink data satisfies the PFS rules corresponding to the first QoS stream, the UPF can map the downlink data to the first QoS stream.

[0464] In step S1608, the UPF can send downlink data to the RAN through the first QoS stream. Correspondingly, the RAN can receive downlink data from the UPF through the first QoS stream.

[0465] Step S1609: Outside of the inactive period corresponding to the first QoS flow, the RAN can send information about resources indicating downlink data transmission to the UE through the channel between the UE and the RAN. The UE can monitor the channel between the UE and the RAN to receive downlink data.

[0466] For a detailed description of step S1609, please refer to the detailed description of step S910, which will not be repeated here.

[0467] In step S1610, the RAN can send downlink data to the UE through the first RB. Accordingly, the UE can receive downlink data from the RAN through the first RB on the resource indicated by the above information.

[0468] In another possible implementation, after the UE determines that the first QoS flow does not exist in one or more QoS flows, it can report the absence of the first QoS flow via control signaling (e.g., RRC reconstruction message), thereby triggering the SMF to configure the first QoS flow that meets the service requirements. For details, please refer to [link to specific procedures]. Figure 16 . Figure 16 and Figure 17 The difference in the illustrated embodiment is that, Figure 17 In the illustrated embodiment, the QoS parameters of the first QoS stream can be determined by the UE, while... Figure 16 In the embodiment shown, the QoS parameters of the first QoS flow can be determined by the SMF. Figure 17 The flowchart shown includes the following steps:

[0469] In step S1701, the SMF can send configuration information for one or more QoS flows to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive configuration information for one or more QoS flows from the SMF.

[0470] For a detailed description of step S1701, please refer to the detailed description of step S1601, which will not be repeated here.

[0471] Step S1702: The RAN can send configuration information of one or more RBs to the UE.

[0472] For a detailed description of step S1702, please refer to the detailed description of step S1602, which will not be repeated here.

[0473] Step S1703: The UE can determine that there is no first QoS flow that meets the service requirements among one or more QoS flows.

[0474] Step S1704: The UE may send an RRC re-establishment message to the RAN. The re-establishment message includes a cause: the first QoS flow is not present in one or more configured QoS flows. Accordingly, the RAN may receive the RRC re-establishment message from the UE.

[0475] In step S1705, the RAN can send indication information to the SMF. This indication information indicates that the first QoS flow is not present among the configured QoS flows. Correspondingly, the SMF can receive the indication information from the RAN.

[0476] Optionally, the RRC re-establishment message in step S1704 and the indication information in step S1705 may also include the latency requirements of the first service, so that the SMF can quickly configure the first QoS flow that meets the service requirements.

[0477] In step S1706, the SMF can send the configuration information of the first QoS flow to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive the configuration information of the first QoS flow from the SMF.

[0478] SMF can modify the configuration information of an already configured QoS flow, or add the configuration information of a new QoS flow to obtain the configuration information of the first QoS flow.

[0479] For example, the first QoS flow can be the default QoS flow.

[0480] For a detailed description of step S1706, please refer to the detailed description of step S1605, which will not be repeated here.

[0481] In step S1707, the RAN can send an RRC reconfiguration message to the UE. The RRC reconfiguration message is used to trigger the establishment of the first RB corresponding to the first QoS flow. Correspondingly, the UE can receive the RRC reconfiguration message from the RAN.

[0482] For a detailed description of step S1707, please refer to the detailed description of step S1606, which will not be repeated here.

[0483] Step S1708: After the downlink data arrives, the UPF can map the downlink data to the first QoS stream according to the configuration information of the first QoS stream received in step S1706.

[0484] In step S1709, the UPF can send downlink data to the RAN through the first QoS stream. Correspondingly, the RAN can receive downlink data from the UPF through the first QoS stream.

[0485] Step S1710: Outside of the inactive period corresponding to the first QoS flow, the RAN can send information about resources indicating downlink data transmission to the UE through the channel between the UE and the RAN. The UE can monitor the channel between the UE and the RAN to receive downlink data.

[0486] For a detailed description of step S1710, please refer to the detailed description of step S910, which will not be repeated here.

[0487] In step S1711, the RAN can send downlink data to the UE through the first RB. Accordingly, the UE can receive downlink data from the RAN through the first RB on the resource indicated by the above information.

[0488] With the above Figure 18 or Figure 13 The differences between the UE triggering core network configuration of QoS flows from the control plane and the UE are as follows: Figure 19As shown, the UE can also trigger the core network to configure QoS flows from the user plane. For example, after determining that a first QoS flow does not exist among one or more QoS flows, the UE can report the absence of a first QoS flow via a data packet, thereby triggering the SMF to configure a first QoS flow that meets service requirements. The data packet may include a QFI with a preset value. The specific process includes the following steps:

[0489] In step S1801, the SMF can send configuration information for one or more QoS flows to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive configuration information for one or more QoS flows from the SMF.

[0490] For a detailed description of step S1801, please refer to the detailed description of step S1601, which will not be repeated here.

[0491] Step S1802: The RAN can send configuration information of one or more RBs to the UE.

[0492] For a detailed description of step S1802, please refer to the detailed description of step S1602, which will not be repeated here.

[0493] Step S1803: The UE can determine that there is no first QoS flow that meets the service requirements among one or more QoS flows.

[0494] Step S1804: When uplink data arrives, the UE can send a data packet with QFI=X in the SDAP header to the RAN. Correspondingly, the RAN can receive the data packet from the UE with QFI=X in the SDAP header.

[0495] Where X is a preset value, QFI=X is used to indicate that none of the configured QoS flows meet the service requirements. Assuming X=10, and the configured multiple QoS flows include QoS flow 1 corresponding to QFI=1, QoS flow 2 corresponding to QFI=2, and QoS flow 3 corresponding to QFI=3, then X=10 is used to indicate that QoS flow 1, QoS flow 2, and QoS flow 3 all fail to meet the service requirements.

[0496] In step S1804, the UE may also send a data packet to the RAN with an IP header including QFI=X. In this embodiment of the application, no limitation is made on which layer's header the UE adds QFI to.

[0497] Step S1805: The RAN can send a data packet to the UPF with a GTP-U header including QFI=X. Correspondingly, the UPF can receive a data packet from the RAN with a GTP-U header including QFI=X.

[0498] Data packets with a GTP-U header including QFI=X can be transmitted through QoS stream 1, QoS stream 2, or QoS stream 3.

[0499] In step S1805, the RAN can also send a data packet to the UPF with an IP header including QFI=X.

[0500] In step S1806, the UPF can parse the QFI=X included in the GTP-U packet header and send indication information to the SMF. This indication information indicates that the first QoS flow does not exist among one or more configured QoS flows. Accordingly, the SMF receives the indication information from the UPF.

[0501] For example, in step S1801, the UPF obtains QFI = 1, 2, and 3. In step S1806, if the GTP-U header includes a value other than 1, 2, or 3, such as 10, then the UPF can send indication information to the SMF. If the GTP-U header includes 1, 2, or 3, then the UPF does not send indication information to the SMF.

[0502] Optionally, the data packets in steps S1804 and S1805, and the indication information in step S1806, may also include the latency requirements of the first service, so that the SMF can quickly configure a QoS flow that meets the service requirements.

[0503] In step S1807, the SMF can send the configuration information of the first QoS flow to the UE, RAN, and UPF. Correspondingly, the UE, RAN, and UPF can receive the configuration information of the first QoS flow from the SMF.

[0504] For a detailed description of step S1807, please refer to the detailed description of step S1605, which will not be repeated here.

[0505] Step S1808: The RAN sends an RRC reconfiguration message to the UE. The RRC reconfiguration message is used to trigger the establishment of the first RB corresponding to the first QoS flow. Correspondingly, the UE receives the RRC reconfiguration message from the RAN.

[0506] For a detailed description of step S1808, please refer to the detailed description of step S1606, which will not be repeated here.

[0507] Step S1809: After the downlink data arrives, the UPF can map the downlink data to the first QoS stream according to the configuration information of the first QoS stream received in step S1807.

[0508] In step S1810, the UPF can send downlink data to the RAN through the first QoS stream. Correspondingly, the RAN can receive downlink data from the UPF through the first QoS stream.

[0509] Step S1811: Outside of the inactive period corresponding to the first QoS flow, the RAN can send information about resources indicating downlink data transmission to the UE through the channel between the UE and the RAN. The UE can monitor the channel between the UE and the RAN to receive downlink data.

[0510] For a detailed description of step S1811, please refer to the detailed description of step S910, which will not be repeated here.

[0511] In step S1812, the RAN can send downlink data to the UE through the first RB. Accordingly, the UE can receive downlink data from the RAN through the first RB on the resource indicated by the above information.

[0512] The above embodiments use cell DTX technology as an example for illustration. The following describes cell discontinuous reception (DRX) technology.

[0513] In cell DRX technology, access network devices can receive data from terminal devices during a specified time period (such as an active period); and during other time periods (such as inactive periods), access network devices can not receive any data. The configurations of cell DTX and cell DRX are independent. That is, cell DTX and cell DRX can be configured simultaneously, or only one of them can be configured.

[0514] For example, the terminal device can receive RRC configuration information from the access network equipment and obtain the cell DRX cycle length (e.g., celldrx-Cycle) and the length of the active period included in the cell DRX cycle (e.g., celldrx-onDurationTimer) based on the RRC configuration information.

[0515] When the RAN access network equipment determines that cell DRX technology needs to be used to transmit service data, it can send a DCI to the UE terminal device. Accordingly, the UE terminal device can obtain the DCI through blind detection and activate cell DRX technology based on the DCI.

[0516] Subsequently, during the active period, the terminal device can transmit uplink information on uplink resources. Correspondingly, the access network device can receive the uplink information. In one possible implementation, the uplink resources may be pre-configured. In another possible implementation, the uplink resource information may be sent to the terminal device by the access network device. That is, the terminal device monitors the PDCCH, and the access network device can send information to the terminal device via the PDCCH, which indicates the resources for data transmission. After receiving this information on the PDCCH, the terminal device can transmit uplink information on the resources indicated by the information.

[0517] For example, uplink information may include at least one of the following: uplink data or uplink signaling. The uplink data may be carried on a configured grant (CG) physical uplink shared channel (PUSCH). The uplink signaling may include at least one of the following: a hybrid automatic repeat request-acknowledgement (HARQ-ACK) or a scheduling request (SR) on a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH). Alternatively, the uplink signaling may be carried on a physical random access channel (PRACH).

[0518] During inactive periods, terminal devices can refrain from sending any uplink information, and correspondingly, access network devices can refrain from receiving any uplink information, thus achieving energy savings at the cost of data transmission latency.

[0519] In existing technologies, access network equipment typically configures the cell DRX period based on the needs of services that are sensitive to transmission latency, and applies this period to the data transmission of different services, which results in poor energy-saving performance of access network equipment.

[0520] For example, the period in the embodiments of this application may also be the cell DRX cycle or the cell DRX cyclic cycle.

[0521] In the application scenario of DRX in a cell, the method for determining the first QoS flow provided in this application embodiment is still applicable. The difference is that after the terminal device determines that the first QoS flow is used for uplink data transmission, when the uplink data arrives, the terminal device can send the uplink data to the access network device through the first RB corresponding to the first QoS flow, and the access network device can then send the uplink data to the UPF through the first QoS flow to complete the uplink data transmission.

[0522] In one possible implementation, if the first QoS flow corresponds to a first RB that has not yet been configured (e.g., in...), Figure 19In the illustrated embodiment, multiple QoS flows are configured in step S1301, but only one RB is configured in step S1302. The terminal device can then send uplink data and the identifier of the first QoS flow to the access network device via the configured RB. The access network device then sends the uplink data to the UPF via the first QoS flow to complete the uplink data transmission. The related functions of the terminal device, access network device, user plane network element, or session management network element involved in this application can be implemented by a single device, or by a combination of multiple devices, or by one or more functional modules within a single device. Alternatively, it can be one or more chips, or a System-on-a-Chip (SoC) or chip system. A chip system can consist of chips or include chips and other discrete components; this embodiment does not specifically limit these limitations.

[0523] It is understood that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0524] For example, the related functions of the terminal device, access network equipment, user plane network element, or session management network element in the embodiments of this application can be achieved through... Figure 19 The communication device 190 in the middle is used to achieve this.

[0525] Figure 19 The diagram shown is a structural schematic of a communication device 190 provided in an embodiment of this application. The communication device 190 includes one or more processors 1901, a communication line 1902, and at least one communication interface. Figure 19 (The illustration is merely exemplary, including a communication interface 1904 and a processor 1901; optionally, a memory 1903 may also be included.)

[0526] The processor 1901 may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of programs according to the present application.

[0527] The communication line 1902 may include a path for connecting different components.

[0528] The communication interface 1904 can be a transceiver module used to communicate with other devices or communication networks, such as Ethernet, access networks, and wireless local area networks (WLANs). For example, the transceiver module can be a transceiver or similar device. Optionally, the communication interface 1904 can also be a transceiver circuit located within the processor 1901, used to implement the processor's signal input and signal output.

[0529] The memory 1903 can be a device with storage functionality. For example, it can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; 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 can exist independently and be connected to the processor via communication line 1902. The memory can also be integrated with the processor.

[0530] The memory 1903 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 1901. The processor 1901 executes the computer execution instructions stored in the memory 1903, thereby implementing the communication method provided in the embodiments of this application.

[0531] Alternatively, in this embodiment, the processor 1901 may execute the processing-related functions in the communication method provided in the following embodiments of this application, and the communication interface 1904 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0532] The computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0533] In a specific implementation, as one example, the processor 1901 may include one or more CPUs, for example... Figure 20 CPU0 and CPU1 in the CPU.

[0534] In a specific implementation, as one example, the communication device 190 may include multiple processors, such as... Figure 5 to Figure 18 Processors 1901 and 1907 are mentioned. Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (such as computer program instructions).

[0535] Optionally, the communication device 190 may also include an output device 1905 and an input device 1906. The output device 1905 communicates with the processor 1901 and can display information in various ways.

[0536] It is understood that in the embodiments of this application, the executing entity may perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the various steps may be executed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to execute all the operations in the embodiments of this application.

[0537] The foregoing primarily describes the solutions provided in this application from the perspective of device-to-device interaction. It is understood that each device, in order to achieve the aforementioned functions, includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware 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.

[0538] This application embodiment can divide each device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0539] When dividing each function into modules according to its corresponding function. Figure 19A communication device 2000 is shown, which includes a transceiver module 2001. Optionally, the communication device 2000 may further include a processing module 2002. The communication device 2000 is used to implement the above-described... Figure 19 The actions performed by any of the following devices in the method described above—terminal device, access network device, mobility management network element, session management network element, or user plane network element—can all be referenced from the functional descriptions of the corresponding functional modules. The technical effects that can be obtained can be referred to in the above method embodiments, and will not be repeated here.

[0540] In this embodiment, the communication device 2000 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above-mentioned functions.

[0541] In a simplified embodiment, those skilled in the art will recognize that the communication device 2000 can employ... Figure 20 The communication device shown is in the form of 190.

[0542] for example, Figure 19 The processors 1901 and / or 1907 in the communication device 190 shown can execute the communication method in the above-described method embodiment by calling computer execution instructions stored in the memory 1903. Specifically, Figure 20 The transceiver module 2001 in the middle can be partially implemented through... Figure 19 The communication module connected to the communication interface 1904 in the middle is used to achieve this. ​ The processing module 2002 in the middle can be partially implemented through ​ The processors 1901 and / or 1907 in the communication device 190 shown call computer execution instructions stored in memory 1903 to implement the communication.

[0543] It should be noted that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes the software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement dedicated logic operations.

[0544] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0545] Optionally, embodiments of this application also provide a chip system, including: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instructions in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the communication device further includes a memory. Optionally, the chip system may be composed of chips, or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0546] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and 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 via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0547] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0548] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, include: The terminal device acquires a first inactive period parameter and a second inactive period parameter. The first inactive period parameter corresponds to a first QoS flow between the terminal device and the user plane network element, and the second inactive period parameter corresponds to a second QoS flow between the terminal device and the user plane network element. The duration of the first inactive period indicated by the first inactive period parameter is greater than the duration of the second inactive period indicated by the second inactive period parameter. The terminal device determines that the first QoS stream is used for downlink data transmission; The terminal device sends first information, which is used to identify the first QoS flow; Outside of the first inactive period, the terminal device monitors the channel between the terminal device and the access network device to receive downlink data.

2. The method according to claim 1, characterized in that, The first inactive period includes all or part of the second inactive period.

3. The method according to claim 2, characterized in that, The start time of the first inactive period is the same as the start time of the second inactive period.

4. The method according to claim 2, characterized in that, The end time of the first inactive period is the same as the end time of the second inactive period.

5. The method according to any one of claims 1-4, characterized in that, The time outside the first inactive period includes all or part of the time period outside the first inactive period.

6. The method according to any one of claims 1-4, characterized in that, The time outside the first inactive period includes all or part of the active period corresponding to the first QoS flow.

7. The method according to any one of claims 1-6, characterized in that, The duration of the active period corresponding to the first QoS flow is the same as the duration of the active period corresponding to the second QoS flow.

8. The method according to any one of claims 1-7, characterized in that, The channel is used to carry downlink control information, which is used to indicate the resources for the downlink data transmission.

9. The method according to claim 8, characterized in that, The method further includes: The terminal device receives the downlink data on the downlink data transmission resource according to the downlink control information.

10. The method according to any one of claims 1-9, characterized in that, The first QoS stream used for downlink data transmission includes: the first QoS stream used to transmit downlink data of the first service; The method further includes: The terminal device determines that the second QoS stream is used to transmit downlink data of the second service; The terminal device sends second information, which is used to identify the second QoS flow.

11. The method according to claim 10, characterized in that, The method further includes: Outside of the second inactive period, the terminal device monitors the channel between the terminal device and the access network device to receive downlink data.

12. The method according to claim 10, characterized in that, The terminal device monitors the channel outside of the first inactive period and the second inactive period.

13. The method according to any one of claims 10-12, characterized in that, The terminal device determines that the first QoS stream is used to transmit downlink data transmission of the first service, including: The terminal device selects the first QoS stream to transmit the data of the first service according to the latency requirements of the first service. The terminal device determines that the second QoS stream is used to transmit downlink data for the second service, including: The terminal device selects the second QoS stream to transmit the data of the second service according to the latency requirements of the second service; The latency requirement of the second service is higher than that of the first service.

14. The method according to any one of claims 1-13, characterized in that, The terminal device acquires the first inactive period parameter and the second inactive period parameter, including: During the establishment or modification of a session, the terminal device receives configuration information of the first QoS flow and configuration information of the second QoS flow from the session management network element. The configuration information of the first QoS flow includes the first inactive period parameter, and the configuration information of the second QoS flow includes the second inactive period parameter. The first QoS flow and the second QoS flow belong to the session.

15. A communication method, characterized in that, include: The access network device sends a first inactive period parameter and a second inactive period parameter to the terminal device. The first inactive period parameter corresponds to a first QoS flow between the terminal device and the user plane network element, and the second inactive period parameter corresponds to a second QoS flow between the terminal device and the user plane network element. The duration of the first inactive period indicated by the first inactive period parameter is greater than the duration of the second inactive period indicated by the second inactive period parameter. The access network device receives the first information from the terminal device, the first information being used to identify the first QoS flow, the first QoS flow being used to transmit downlink data; The access network device sends the first information to the user plane network element; The access network device receives the downlink data from the user plane network element through the first QoS stream; Outside of the first inactive period, the access network device sends downlink control information to the terminal device through the channel between the terminal device and the access network device. The downlink control information is used to indicate the transmission resources for the downlink data.

16. The method according to claim 15, characterized in that, The first inactive period includes all or part of the second inactive period.

17. The method according to claim 16, characterized in that, The start time of the first inactive period is the same as the start time of the second inactive period.

18. The method according to claim 16, characterized in that, The end time of the first inactive period is the same as the end time of the second inactive period.

19. The method according to any one of claims 15-18, characterized in that, The time outside the first inactive period includes all or part of the time period outside the first inactive period.

20. The method according to any one of claims 15-18, characterized in that, The time outside the first inactive period includes all or part of the active period corresponding to the first QoS flow.

21. The method according to any one of claims 15-20, characterized in that, The duration of the active period corresponding to the first QoS flow is the same as the duration of the active period corresponding to the second QoS flow.

22. The method according to any one of claims 15-21, characterized in that, The method further includes: The access network device sends the first inactive period parameter and the second inactive period parameter to the session management network element; During the establishment or modification of a session, the access network device receives configuration information of the first QoS flow and configuration information of the second QoS flow from the session management network element. The configuration information of the first QoS flow includes the first inactive period parameter, and the configuration information of the second QoS flow includes the second inactive period parameter. The first QoS flow and the second QoS flow belong to the session.

23. The method according to any one of claims 15-21, characterized in that, The method further includes: During the establishment or modification of a session, the access network device receives configuration information of the first QoS flow and configuration information of the second QoS flow from the session management network element, wherein the first QoS flow and the second QoS flow belong to the session; The access network device determines that the first inactive period parameter corresponds to the first QoS flow, and the second inactive period parameter corresponds to the second QoS flow.

24. A communication device, characterized in that, The communication device includes: a module or unit for implementing the method according to any one of claims 1-14; or a module or unit for implementing the method according to any one of claims 15-23.

25. A communication device, characterized in that, include: A memory and a processor coupled to the memory, the memory for storing a program, the processor for executing the program stored in the memory; when the communication device is running, the processor runs the program, causing the communication device to perform the method according to any one of claims 1-14; or, causing the communication device to perform the method according to any one of claims 15-23.

26. A communication system, characterized in that, The communication system includes a terminal device and an access network device; wherein the terminal device is configured to perform the method as described in any one of claims 1-14, and the access network device is configured to perform the method as described in any one of claims 15-23.

27. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a computer, causes the computer to perform the method according to any one of claims 1-14; or, when executed by a computer, causes the computer to perform the method according to any one of claims 15-23.

28. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1-14, or cause the computer to perform the method of any one of claims 15-23.

Images