Patent Application
20250203449
Embodiments of this application relate to the field of wireless communication technologies, and in particular, to an information processing method, a device, and a readable storage medium.
An external application or terminal may request congestion status information (for example, congestion start, a congestion technique, and a congestion level) of a service data flow from a 5th Generation System (5GS).
However, a core network of the 5GS is managed based on a Quality of Service (QOS) flow. A radio access network of the 5GS is scheduled based on a radio channel (for example, a Data Radio Bearer (DRB), and a Logical channel (LCH)). One or more QoS flows may be mapped to the radio channel, and one or more service data flows may be mapped to one QoS flow. In the related art, a RAN is required to report a congestion in each QoS flow.
Embodiments of this application provide an information processing method, a device, and a readable storage medium.
According to a first aspect, an information processing method is provided, and applied to a first communication device. The method includes: acquiring, by the first communication device, a congestion monitoring requirement corresponding to a first quality of service QoS flow; and performing, by the first communication device, a first operation according to the congestion monitoring requirement corresponding to the first QoS flow, where the first operation includes one or more of the following: monitoring a congestion status of a first object; using the congestion status of the first object as a congestion status of the first QoS flow; reporting the congestion status of the first object or reporting the congestion status of the first QoS flow through signaling corresponding to the first QoS flow and/or a data packet in the first QoS flow; mapping the first QoS flow to a first radio bearer; and sending a first requirement, where the first requirement is an uplink congestion monitoring requirement corresponding to the first QoS flow, and/or, the first requirement is configured for requiring one or more of the following: monitoring and/or reporting an uplink congestion status of a second object; reporting the uplink congestion status of the second object through signaling corresponding to a third object and/or a data packet in the third object; and using a congestion status of the second object as a congestion status of the third object, where the first object includes one or more of the following: the first QoS flow; the first radio bearer; a first logical channel; a first logical channel group; a first cell; and the first communication device or a first radio access network RAN network element; the second object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; andthe first logical channel group; andthe third object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; andthe first logical channel group.
According to a second aspect, an information processing method is provided, and applied to a second communication device. The method includes: acquiring, by the second communication device, a first requirement; and performing, by the second communication device, a second operation according to the first requirement, where the first requirement is an uplink congestion monitoring requirement corresponding to a first QoS flow, and/or, the first requirement is configured for requiring one or more of the following: monitoring and/or reporting an uplink congestion status of a second object; using a congestion status of the second object as a congestion status of a third object; and reporting the uplink congestion status of the second object or reporting the congestion status of the third object through signaling corresponding to the third object and/or a data packet in the third object; the second operation includes one or more of the following: monitoring the uplink congestion status of the second object; using the uplink congestion status of the second object as an uplink congestion status of the third object; and reporting the uplink congestion status of the second object or reporting the uplink congestion status of the third object through the signaling corresponding to the third object and/or the data packet in the third object; the second object includes one or more of the following: the first QoS flow; a first radio bearer; a first logical channel; and a first logical channel group; and the third object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; and the first logical channel group.
According to a third aspect, an information processing method is provided, and applied to a third communication device. The method includes: performing, by the third communication device, a third operation, where the third operation includes one or more of the following: mapping each QoS flow having a congestion monitoring requirement to an independent fourth object; determining, based on whether a QoS flow has a congestion monitoring requirement, to map the QoS flow to a same fourth object or different fourth objects; mapping one or more QoS flows having a congestion monitoring requirement to a same fourth object; mapping one or more QoS flows having a congestion monitoring requirement to a target fourth object, where a QoS flow having no congestion monitoring requirement does not exist in the target fourth object; determining and/or saving a congestion monitoring requirement of a fourth object, where the congestion monitoring requirement of the fourth object meets congestion monitoring requirements of all QoS flows mapped to the fourth object, or, is the same as congestion monitoring requirements of all QoS flows mapped to the fourth object; andusing a congestion status of the fourth object to which the QoS flow is mapped as a congestion status of the QoS flow, where the fourth object includes one or more of the following: a radio bearer; anda logical channel.
According to a fourth aspect, an information processing method is provided, and applied to a fourth communication device. The method includes: performing, by the fourth communication device, a fourth operation, where the fourth operation includes one or more of the following: mapping each service data flow having a congestion monitoring requirement to an independent QoS flow; determining, based on whether a service data flow has a congestion monitoring requirement, to map the service data flow to a same QoS flow or different QoS flows; mapping one or more service data flows having a congestion monitoring requirement to a same QoS flow; mapping one or more service data flows having a congestion monitoring requirement to a target QoS flow, where a service data flow having no congestion monitoring requirement does not exist in the target QoS flow; determining and/or saving a congestion monitoring requirement corresponding to the QoS flow, where the congestion monitoring requirement corresponding to the QoS flow meets congestion monitoring requirements of all service data flows to which the QoS flow is mapped, or, is the same as congestion monitoring requirements of all service data flows to which the QoS flow is mapped; using a congestion status of the QoS flow to which the service data flow is mapped as a congestion status of the service data flow; and sending the congestion monitoring requirement corresponding to the QoS flow.
According to a fifth aspect, an information processing method is provided, and applied to a fifth communication device. The method includes: performing, by the fifth communication device, a fifth operation, where the fifth operation includes at least one of the following: determining a congestion monitoring requirement corresponding to a first QoS flow; sending the congestion monitoring requirement corresponding to the first QoS flow; determining a first requirement; andsending the first requirement, where the first requirement is an uplink congestion monitoring requirement corresponding to the first QoS flow, and/or, the first requirement is configured for requiring one or more of the following: monitoring and/or reporting an uplink congestion status of a second object; reporting the uplink congestion status of the second object through signaling corresponding to a third object and/or a data packet in the third object; andusing a congestion status of the second object as a congestion status of the third object; and the second object includes one or more of the following: the first QoS flow; a first radio bearer; a first logical channel; and a first logical channel group; and the third object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; and the first logical channel group.
According to a sixth aspect, an information processing method is provided, and applied to a sixth communication device. The method includes: acquiring, by the sixth communication device, congestion status information of a first QoS flow; and performing, by the sixth communication device, a sixth operation based on the congestion status information of the first QoS flow, where the sixth operation includes at least one of the following: determining a congestion status of a first service data flow; and sending congestion status information of the first service data flow, where the first service data flow is a service data flow to which the first QoS flow is mapped.
According to a seventh aspect, a communication device is provided, and is a first communication device. The device includes: a first acquisition module, configured to acquire a congestion monitoring requirement corresponding to a first QoS flow; and a first execution module, configured to perform a first operation according to the congestion monitoring requirement corresponding to the first QoS flow, where the first operation includes one or more of the following: monitoring a congestion status of a first object; using the congestion status of the first object as a congestion status of the first QoS flow; reporting the congestion status of the first object or reporting the congestion status of the first QoS flow through signaling corresponding to the first QoS flow and/or a data packet in the first QoS flow; mapping the first QoS flow to a first radio bearer; andsending a first requirement, where the first requirement is an uplink congestion monitoring requirement corresponding to the first QoS flow, and/or, the first requirement is configured for requiring one or more of the following: monitoring and/or reporting an uplink congestion status of a second object; reporting the uplink congestion status of the second object through signaling corresponding to a third object and/or a data packet in the third object; and using a congestion status of the second object as a congestion status of the third object; the first object includes one or more of the following: the first QoS flow; the first radio bearer; a first logical channel; a first logical channel group; a first cell; and the first communication device or a first radio access network RAN network element; the second object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; and the first logical channel group; and the third object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; and the first logical channel group.
According to an eighth aspect, a communication device is provided, and is a second communication device. The device includes: a second acquisition module, configured to acquire a first requirement; and a second execution module, configured to perform a second operation according to the first requirement, where the first requirement is an uplink congestion monitoring requirement corresponding to a first QoS flow, and/or, the first requirement is configured for requiring one or more of the following: monitoring and/or reporting an uplink congestion status of a second object; using a congestion status of the second object as a congestion status of the third object; and reporting the uplink congestion status of the second object or reporting the congestion status of the third object through signaling corresponding to the third object and/or a data packet in the third object; the second operation includes one or more of the following: monitoring the uplink congestion status of the second object; using the uplink congestion status of the second object as an uplink congestion status of a third object; and reporting the uplink congestion status of the second object or reporting the uplink congestion status of the third object through the signaling corresponding to the third object and/or the data packet in the third object; the second object includes one or more of the following: the first QoS flow; a first radio bearer; a first logical channel; and a first logical channel group; and the third object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; and the first logical channel group.
According to a ninth aspect, a communication device is provided, and is a third communication device. The device includes: a third execution module, configured to perform a third operation, where the third operation includes one or more of the following: mapping each QoS flow having a congestion monitoring requirement to an independent fourth object; determining, based on whether a QoS flow has a congestion monitoring requirement, to map the QoS flow to a same fourth object or different fourth objects; mapping one or more QoS flows having a congestion monitoring requirement to a same fourth object; mapping one or more QoS flows having a congestion monitoring requirement to a target fourth object, where a QoS flow having no congestion monitoring requirement does not exist in the target fourth object; determining and/or saving a congestion monitoring requirement of a fourth object, where the congestion monitoring requirement of the fourth object meets congestion monitoring requirements of all QoS flows mapped to the fourth object, or, is the same as congestion monitoring requirements of all QoS flows mapped to the fourth object; and using a congestion status of the fourth object to which the QoS flow is mapped as a congestion status of the QoS flow, where the fourth object includes one or more of the following: a radio bearer; and a logical channel.
According to a tenth aspect, a communication device is provided, and is a fourth communication device. The device includes: a fourth execution module, configured to perform a fourth operation, where the fourth operation includes one or more of the following: mapping each service data flow having a congestion monitoring requirement to an independent QoS flow; determining, based on whether a service data flow has a congestion monitoring requirement, to map the service data flow to a same QoS flow or different QoS flows; mapping one or more service data flows having a congestion monitoring requirement to a same QoS flow; mapping one or more service data flows having a congestion monitoring requirement to a target QoS flow, where a service data flow having no congestion monitoring requirement does not exist in the target QoS flow; determining and/or saving a congestion monitoring requirement corresponding to the QoS flow, where the congestion monitoring requirement corresponding to the QoS flow meets congestion monitoring requirements of all service data flows to which the QoS flow is mapped, or, is the same as congestion monitoring requirements of all service data flows to which the QoS flow is mapped; using a congestion status of the QoS flow to which the service data flow is mapped as a congestion status of the service data flow; and sending the congestion monitoring requirement corresponding to the QoS flow.
According to an eleventh aspect, a communication device is provided, and is a fifth communication device. The device includes: a fifth execution module, configured to perform a fifth operation, where the fifth operation includes at least one of the following: determining a congestion monitoring requirement corresponding to a first QoS flow; sending the congestion monitoring requirement corresponding to the first QoS flow; determining a first requirement; and sending the first requirement, where the first requirement is an uplink congestion monitoring requirement corresponding to the first QoS flow, and/or, the first requirement is configured for requiring one or more of the following: monitoring and/or reporting an uplink congestion status of a second object; reporting the uplink congestion status of the second object through signaling corresponding to a third object and/or a data packet in the third object; and using a congestion status of the second object as a congestion status of the third object; the second object includes one or more of the following: the first QoS flow; a first radio bearer; a first logical channel; and a first logical channel group; and the third object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; and the first logical channel group.
According to a twelfth aspect, a communication device is provided, and is a sixth communication device. The device includes: a third acquisition module, configured to acquire congestion status information of a first QoS flow; and a sixth execution module, configured to perform a sixth operation based on the congestion status information of the first QoS flow, where the sixth operation includes at least one of the following: determining a congestion status of a first service data flow; and sending congestion status information of the first service data flow, where the first service data flow is a service data flow to which the first QoS flow is mapped.
According to a thirteenth aspect, a communication device is provided, including a processor, a memory, and a computer program stored in the memory and executable on the processor. The computer program, when being executed by the processor, implements the steps of the information processing method according to the first aspect, or implements the steps of the information processing method according to the second aspect, or implements the steps of the information processing method according to the third aspect, or implements the steps of the information processing method according to the fourth aspect, or implements the steps of the information processing method according to the fifth aspect, or implements the steps of the information processing method according to the sixth aspect.
According to a fourteenth aspect, a communication system is provided, and includes: a first communication device, a second communication device, a third communication device, a fourth communication device, a fifth communication device, and a sixth communication device. The first communication device may be configured to perform the steps of the method according to the first aspect. The second communication device may be configured to perform the steps of the method according to the second aspect. The third communication device may be configured to perform the steps of the method according to the third aspect. The fourth communication device may be configured to perform the steps of the method according to the fourth aspect. The fifth communication device may be configured to perform the steps of the method according to the fifth aspect. The sixth communication device may be configured to perform the steps of the method according to the sixth aspect.
According to a fifteenth aspect, a non-tranitory computer-readable storage medium is provided. The computer-readable storage medium stores a program or instructions. The program or instructions, when being executed by a processor, implement the steps of the method according to the first aspect, or implement the steps of the method according to the second aspect, or implement the steps of the method according to the third aspect, or implement the steps of the method according to the fourth aspect, or implement the steps of the method according to the fifth aspect, or implement the steps of the method according to the sixth aspect.
According to a sixteenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a program or instructions to implement the steps of the method according to the first aspect, or implement the steps of the method according to the second aspect, or implement the steps of the method according to the third aspect, or implement the steps of the method according to the fourth aspect, or implement the steps of the method according to the fifth aspect, or implement the steps of the method according to the sixth aspect.
According to a seventeenth aspect, a computer program/program product is provided. The computer program/program product is stored in a storage medium. The computer program/program product, when being executed by at least one processor, implements the steps of the method according to the first aspect, or implements the steps of the method according to the second aspect, or implements the steps of the method according to the third aspect, or implements the steps of the method according to the fourth aspect, or implements the steps of the method according to the fifth aspect, or implements the steps of the method according to the sixth aspect.
The following clearly and completely describes the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Apparently, the described embodiments are only some embodiments of the present application rather than all the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on embodiments of this application without creative efforts fall within the protection scope of this application.
The term “comprise” or any variation of such terms in in the description and claims of the present application is intended to cover a non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units not only includes those steps or units specified expressly, but also includes other steps or units that are not specified expressly or are inherent to the process, method, product or device. In addition, the term “and/or” used in the description and claims represents at least one of associated objects. For example, A and/or B represents the following three cases: A exists separately, B exists separately, and both A and B exist.
In embodiments of this application, the term “example”, “for example”, or the like is used to represent giving an example, an illustration, or a description. Any embodiment or design scheme described as an “example” or “for example” in embodiments of this application should not be explained as being more preferred or having more advantages than another embodiment or design scheme. Exactly, use of the term such as “exemplary” or “for example” is intended to present a related concept in a specific manner.
The technology described herein is not limited to a 5th-generation (5G) system and a future evolved communication system, and is not limited to an LTE/LTE-Advanced (LTE-A) system, and may also be applied to various wireless communication systems, for example, Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems.
The terms “system” and “network” are often used interchangeably. The CDMA system may implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). The UTRA includes Wideband Code Division Multiple Access (CDMA) and another CDMA variant. The TDMA system may implement radio technologies such as Global System for Mobile Communications (GSM). The OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. The UTRA and the E-UTRA are parts of a Universal Mobile Telecommunications System (UMTS). The LTE and more advanced LTE (for example, LTE-A) are new UMTS versions using E-UTRA. The UTRA, the E-UTRA, the UMTS, the LTE, the LTE-A, and the GSM are described in the documents from the 3rd Generation Partnership Project (3GPP). The CDMA2000 and the UMB are described in the documents from the “Third Generation Partnership Project 2” (3GPP2). The technology described herein may be applied to the systems and radio technologies mentioned above, and may also be applied to other systems and radio technologies.
To implement congestion monitoring and reporting per QoS flow, the following problems further need to be resolved.
Problem 1: A RAN cannot necessarily support congestion monitoring per QoS flow, but can support monitoring of a DRB/LCH, an LCH Group, a cell (for example, video resources of the cell are insufficient), and whether a congestion occurs in the entire RAN node.
In an idea for a solution, in a case that a congestion occurs in these objects with granularities larger than a granularity of a QoS flow, it is considered that a congestion occurs in a data flow in the QoS flow, and congestion status information is reported through signaling and/or user plane data with a granularity of a QoS flow, for example, (1). through signaling of a QoS flow; (2). congestion reporting through a first protocol layer (for example, a General packet radio service Tunnel Protocol-Uplink (GTP-U), a network layer (an IP layer) of an N3 interface, and an Explicit Congestion Notification (ECN) marking of an IP layer) of a data packet in a QoS flow; and (3). an ECN.
Problem 2: In a case that a congestion occurs in a radio channel, congestions do not necessarily occur in all of a plurality of QoS flows mapped to the radio channel. For example, a data amount of a QoS flow 1 is very large, and a data amount of a QoS flow 2 is very small. It appears that a congestion occurs in the QoS flow 1, and it appears that a congestion does not occur in the QoS flow 2.
An idea for a solution is to allocate an independent DRB to each QoS flow that requires congestion reporting.
Problem 3: It is possible that only UE can learn uplink per QoS flow/per DRB congestion, because only data packets are queued in a PDCP layer or a logical channel of a DBR on a UE side. Buffer Data Status reported by the UE has a granularity of an LCH logical channel group. The RAN cannot learn a queue status per LCH channel.
Manner 1: The RAN does not support uplink congestion monitoring. Considering to avoid affecting the UE, the RAN is indicated to perform downlink congestion control.
Manner 2: The RAN does not support monitoring of an uplink congestion at an air interface (Uu), and only supports monitoring of an uplink congestion at the N3 interface. In other words, only a congestion status of uplink data that has already reached the RAN is queued at the RAN to wait to be sent to the N3 interface is considered. If a congestion that occurs in a case that the RAN sends data to a UPF, the congestion is reported.
Manner 3: The RAN or a CN requires monitoring and reporting of uplink congestion from the UE, and sends congestion information reported by the UE to the UPF through a GTP-U header. Alternatively, the UE is required to directly add congestion markings corresponding to ECN/Low Latency Low Loss Scalable Throughput (L4S) technology.
It is noted that the wireless communication system shown in
Optionally, in embodiments of this application, the expression “acquiring” may be understood as obtaining from a configuration, receiving, receiving after a request, acquiring through self-learning, acquiring through inference based on unreceived information, or obtaining through processing based on received information, which may be specifically determined according to an actual requirement, and is not limited in embodiments of this application. For example, if information indicating a capability sent by a device is not received, it may be inferred that the device does not support the capability.
Optionally, “sending” may include broadcasting, broadcasting in a system message, or returning in response to a request. In an optional embodiment of this application, a communication device may include at least one of the following: a communication network element and a terminal. In an embodiment of this application, the communication network element may include at least one of the following: a core network element and a radio access network element.
In embodiments of this application, the core network element (CN network element) may include, but is not limited to, at least one of the following: a core network device, a core network node, a core network function, a core network element, a Mobility Management Entity (MME), an Access Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a serving gateway (serving GW, SGW), a PDN gateway, a Policy Control Function (PCF), a Policy and Charging Rules Function (PCRF), a Serving GPRS Support Node (SGSN), a Gateway GPRS Support Node (GGSN), and an application function.
In embodiments of this application, the RAN network element may include, but is not limited to, at least one of the following: a radio access network device, a radio access network node, a radio access network function, a radio access network unit, a 3GPP radio access network, a non-3GPP radio access network, a Centralized Unit (CU), a Distributed Unit (DU), a base station, an evolved Node B (eNB), a 5G gNodeB (gNB), a Radio Network Controller (RNC), a Node B (NodeB), a Non-3GPP InterWorking Function (N3IWF), an Access Controller (AC) node, an Access Point (AP) device, or a Wireless Local Area Network (WLAN) node.
The base station may be a Base Transceiver Station (BTS) in a GSM or CDMA, or may be a nodeB (NodeB) in WCDMA, or may be an evolved node B (eNB or e-NodeB) in LTE, or a 5G gNodeB (gNB). This is not limited in embodiments of this application.
In an optional embodiment of this application, the UE may include one of the following: a terminal device, a terminal device and a card, and a card. In an optional embodiment of this application, the card may include one of the following: a SIM card, a USIM card, and an eSIM.
In an optional embodiment of this application, the terminal may include a relay that supports terminal functions and/or a terminal that supports relay functions. The terminal may also be referred to as a terminal device or a User Equipment (UE). The terminal may be a terminal side device, for example, a mobile phone, a tablet personal computer, a laptop computer, a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a wearable device, or an in-vehicle device. It is noted that the specific type of the terminal is not limited in embodiments of this application.
The terms in the specific implementation of this application are described and explained below.
In an optional embodiment of this application, congestion monitoring may include at least one of the following: congestion status monitoring, congestion status measurement, and/or congestion status reporting. The congestion status includes at least one of the following: a congestion starts or a congestion occurs, a congestion ends or no congestion occurs, a congestion de-escalates, and a congestion escalates. In an optional embodiment of this application, when a congestion occurs in an Nth object, a congestion occurs in data transfer in the Nth object. In an optional embodiment of this application, congestion status information of the Nth object is congestion status information of the data transfer in the Nth object. In an optional embodiment of this application, congestion status information in the Nth object is congestion status information of the data transfer in the Nth object.
In an optional embodiment of this application, that a congestion occurs in the Nth object (the Nth object includes one of the following: a first object, a second object, a third object, a fourth object, a QoS flow, a service data flow, a first QoS flow, a first DRB, a first cell, and a first RAN network element) includes one of the following: QoS of the Nth object cannot be met, a data sending rate of the Nth object is less than a data receiving rate of the Nth object, time domain resources are insufficient, a buffer overflows, and a queue overflows.
In an implementation, time domain resources being insufficient is, for example, time domain resources of a first cell are insufficient for transferring all received data or buffered data.
In an implementation, a congestion occurring in a first DRB includes one of the following: QoS of the first DRB cannot be met, and a data sending rate of the first DRB is less than a data receiving rate of the first DRB. That QoS cannot be met is, for example: a rate cannot be ensured, a packet loss rate cannot be ensured, a packet loss ratio cannot be ensured, and a PER cannot be ensured.
In an implementation, the data sending rate of the Nth object being less than the data receiving rate of the Nth object includes: a sending rate of data of the Nth object sent to a first interface is less than a sending rate of data of the Nth object received from a second interface. The first interface or the second interface includes one of the following: a Uu interface, an N9 or N3 interface, and an N6 interface. When the first interface is a Uu interface, the second interface may be an N3 interface. When the first interface is an N3 interface, the second interface may be a Uu interface. When the first interface is an N6 interface, the second interface may be an N3 or N9 interface. When the first interface is an N3 or N9 interface, the second interface may be an N6 interface.
In an optional embodiment of this application, the QoS includes at least one of the following: a guaranteed bit rate (for example, a Guaranteed Flow Bit Rate (GFBR)), a minimum transmission rate (for example, a minimum flow bit rate), a Packet Error Rate (PER), a packet loss rate, a transmission delay budget, and a buffering delay budget.
That the QoS cannot be met includes at least one of the following: the guaranteed flow bit rate cannot be ensured (for example, an actual transmission rate is lower than the guaranteed flow bit rate), the minimum transmission rate cannot be met (for example, an actual minimum transmission rate is less than the minimum transmission rate), the packet error rate cannot be met (for example, an actual packet error rate is greater than a packet error rate in QoS), the packet loss rate cannot be met (for example, an actual packet loss rate is greater than a packet loss rate in QoS), the transmission delay budget cannot be met (an actual transmission delay overhead is greater than the transmission delay budget), and the buffering delay budget cannot be met (an actual buffering delay overhead of data is greater than the buffering delay budget).
In an optional embodiment of this application, a data packet includes a Protocol Data Unit (PDU)/packet data unit. In an optional embodiment of this application, all described ECNs represent ECNs and/or ECN markings for L4S.
In an optional embodiment of this application, the QoS flow having a congestion monitoring requirement is that the congestion monitoring requirement corresponding to the QoS flow is acquired. If the congestion monitoring requirement corresponding to the QoS flow is not acquired, it may be considered that the QoS flow does not have a congestion monitoring requirement.
In an optional embodiment of this application, a tunnel includes at least one of the following: a session (session) (for example, a PDU session, or a session between a RAN and a CN), a QoS flow, a QoS subflow, an Evolved Packet System (EPS) bearer, a PDP context, a DRB, a SignalingRadio Bearer (SRB), an IPsec association, and a GPRS TunnelingProtocol (GTP) tunnel (tunnel). The tunnel may be instantiated as a tunnel of any foregoing type.
In an optional embodiment of this application, a reporting event is that when the event occurs, the event is reported. The event includes at least one of the following: a congestion occurs, the congestion ends, the congestion escalates, and the congestion de-escalates. In an embodiment of this application, the NG interface may also be referred to as an S1 interface or an N2 interface, the name of which is not limited. In an embodiment of this application, a wireless communication network may be at least one of the following: a public network, and a non-public network. Alternatively, the first network may be a non-public network.
In an embodiment of this application, an NPN is short for a non-public network. The non-public network may be referred to as one of the following: a non-public communication network. The non-public network may include at least one of the following deployment manners: a physical non-public network, a virtual non-public network, a non-public network implemented on a public network. In an implementation, the public network is a Closed Access Group (CAG). One CAG may be formed by one group of terminals.
In an embodiment of this application, the non-public network may include or may be referred to as a private network. The private network may be referred to as one of the following: a private communication network, a private network, a Local Area Network (LAN), a Private Virtual Network (PVN), an isolated communication network, a dedicated communication network, or another name. It is noted that a naming manner is not specifically limited in embodiments of this application.
In an embodiment of this application, a PN is short for a public network. The public network may be referred to as one of the following: a public communication network or another name. It is noted that a naming manner is not specifically limited in embodiments of this application.
In an embodiment of this application, a size of the data packet may be referred to as a length of the data packet. In an embodiment of this application, the data packet may be referred to as a data frame. In an optional embodiment of this application, a communication device may include at least one of the following: a communication network element and a terminal. In an embodiment of this application, the communication network element may include at least one of the following: a core network element and a radio access network element. An information processing method provided in embodiments of this application is described below.
Referring to
Step 301: The first communication device acquires a congestion monitoring requirement corresponding to a first QoS flow.
Step 302: The first communication device performs a first operation according to the congestion monitoring requirement corresponding to the first QoS flow.
The first operation includes one or more of the following: monitoring a congestion status of a first object; using the congestion status of the first object as a congestion status of the first QoS flow; reporting the congestion status of the first object or reporting the congestion status of the first QoS flow through signaling corresponding to the first QoS flow and/or a data packet in the first QoS flow; mapping the first QoS flow to a first radio bearer; and sending a first requirement, where the first requirement is an uplink congestion monitoring requirement corresponding to the first QoS flow, and/or, the first requirement is configured for requiring one or more of the following: monitoring and/or reporting an uplink congestion status of a second object; reporting the uplink congestion status of the second object through signaling corresponding to a third object and/or a data packet in the third object; and using a congestion status of the second object as a congestion status of the third object; and the first object includes one or more of the following: the first QoS flow; the first radio bearer; a first logical channel; a first logical channel group; a first cell; and the first communication device or a first radio access network RAN network element; the second object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; and the first logical channel group; and the third object includes one or more of the following: the first QoS flow; the first radio bearer; the first logical channel; and the first logical channel group.
In an implementation, the first communication device is the first RAN network element. In another implementation, the first communication device is a terminal.
Optionally, the first communication device acquires the congestion monitoring requirement corresponding to the first QoS flow from a first target end. The first target end includes at least one of the following: a fourth communication device, a fifth communication device, an AMF, an SMF, and a PCF.
Optionally, the first communication device sends congestion status information of the first object to the first target end.
In an implementation, the congestion monitoring requirement corresponding to the first QoS flow does not include the uplink congestion monitoring requirement corresponding to the first QoS flow. The congestion monitoring requirement corresponding to the first QoS flow may be only configured for monitoring a downlink congestion status of the first QoS flow or the first object.
Optionally, the first communication device sends the first requirement to a second communication device. In an implementation, the congestion status of the first object includes an uplink and/or downlink congestion status of the first object.
In an implementation, the first object includes the second object. The first object includes the third object. The second object and the third object may be the same, and for example, are both the first radio bearer. The second object and the third object may be different. For example, the second object is the first radio bearer, and the third object is the first QoS flow.
A granularity of the second object is greater than or equal to a granularity of the third object. In a case that the third object is the first QoS flow, the second object includes one or more of the following: the first QoS flow, the first radio bearer, the first logical channel, and the first logical channel group. For example, in a case that the third object is the first radio bearer, the second object includes one or more of the following: the first radio bearer, the first logical channel, and the first logical channel group. In a case that the third object is the first logical channel group, the second object includes one or more of the following: the first logical channel group. The using a congestion status of the second object as a congestion status of the third object includes: using congestion status information of the second object as congestion status information of the third object. In an implementation, the third object is the first QoS flow, and the congestion status of the second object is reported through signaling corresponding to the first QoS flow or a data packet in the first QoS flow. In another implementation, the third object is the first radio bearer, and the congestion status of the second object is reported through signaling corresponding to the first radio bearer or a data packet in the first radio bearer.
The congestion monitoring requirement corresponding to the first QoS flow may be included in an information element of the first QoS flow. The first QoS flow may be one or more QoS flows. In an implementation, the congestion monitoring requirement includes one of the following: a congestion monitoring requirement configured for an ECN and/or L4S congestion marking, or a congestion monitoring requirement configured for another congestion marking different from the ECN and/or L4S congestion marking.
In an implementation, information configured for indicating that uplink and/or downlink congestion monitoring (for example, monitoring) requires to be performed may be a specific 5QI value.
In an implementation, the congestion monitoring requirement corresponding to the first QoS flow is configured for requiring one or more of the following: monitoring and/or reporting a congestion status of the first QoS flow; monitoring and/or reporting the congestion status of the first object; and reporting the congestion status of the first object or reporting the congestion status of the first QoS flow through signaling corresponding to the first QoS flow and/or a data packet in the first QoS flow; and/or a parameter in the congestion monitoring requirement corresponding to the first QoS flow includes one or more of the following: information configured for indicating that uplink and/or downlink congestion monitoring requires to be performed, a reporting event, a reporting frequency, and information configured for describing a congestion level.
It is noted that the reporting event is, for example, one of the following: a congestion starts or a congestion occurs, the congestion ends, the congestion reaches an Nth congestion level, a congestion level escalates, and a congestion level decreases. One or more congestion levels may be provided. N may be one or more positive integers.
The monitoring and/or reporting a congestion status of the first QoS flow includes: monitoring and/or reporting an uplink and/or downlink congestion status of the first QoS flow; and the monitoring and/or reporting the congestion status of the first object includes: monitoring and/or reporting the uplink and/or downlink congestion status of the first object. The congestion status information of the first object includes uplink and/or downlink congestion status information of the first object.
In an implementation, the uplink congestion monitoring requirement corresponding to the first QoS flow is configured for requiring one or more of the following: monitoring and/or reporting an uplink congestion status of the first QoS flow; monitoring and/or reporting an uplink congestion status of a second object; using a congestion status of the second object as a congestion status of the third object; and reporting the congestion status of the second object or the congestion status of the third object through the signaling corresponding to the third object and/or the data packet in the third object; and/or a parameter in the uplink congestion monitoring requirement corresponding to the first QoS flow or the first requirement includes one or more of the following: information configured for indicating that uplink congestion monitoring requires to be performed, a reporting event, a reporting frequency, and information configured for describing a congestion level.
It is noted that the reporting event is, for example, one of the following: a congestion starts or a congestion occurs, the congestion ends, the congestion reaches an Nth congestion level, a congestion level increases, and a congestion level decreases. One or more congestion levels may be provided. N may be one or more positive integers.
The congestion status information of the second object includes uplink congestion status information of the second object. In an implementation, the using the congestion status of the first object as a congestion status of the first QoS flow includes at least one of the following: determining, in a case that a congestion occurs in the first object, that a congestion occurs in the first QoS flow; determining, in a case that the congestion in the first object ends, that the congestion in the first QoS flow ends; determining, in a case that the congestion in the first object escalates, that the congestion in the first QoS flow escalates; determining, in a case that the congestion in the first object de-escalates, that the congestion in the first QoS flow de-escalates; and using congestion status information of the first object as congestion status information of the first QoS flow; and/or the using a congestion status of the second object as a congestion status of the third object includes at least one of the following: determining, in a case that a congestion occurs in the second object, that a congestion occurs in the third object; determining, in a case that the congestion in the second object ends, that the congestion in the third object ends; determining, in a case that the congestion in the second object escalates, that the congestion in the third object escalates; determining, in a case that the congestion in the second object de-escalates, that the congestion in the third object de-escalates; and using congestion status information of the second object as congestion status information of the third object.
In an implementation, the sending a first requirement includes: sending the first requirement in a case that a first condition is met, where the first condition includes at least one of the following: the congestion monitoring requirement corresponding to the first QoS flow includes the uplink congestion monitoring requirement corresponding to the first QoS flow; and the first object includes at least one of the following: the first QoS flow, the first radio bearer, the first logical channel, and the first logical channel group.
It is understandable that the uplink congestion monitoring requirement may need to be performed by the second communication device.
In an implementation, the reporting the congestion status of the first object or reporting the congestion status of the first QoS flow through signaling corresponding to the first QoS flow includes: sending uplink and/or downlink congestion status information of the first object or uplink and/or downlink congestion status information of the first QoS flow through an information element and/or a first interface message corresponding to the first QoS flow; or the reporting the congestion status of the first object or reporting the congestion status of the first QoS flow through the data packet in the first QoS flow includes at least one of the following: making a packet header of the data packet in the first QoS flow carry congestion status information of the first object or congestion status information of the first QoS flow; and sending the data packet in the first QoS flow to a second interface, where a first interface is a control plane interface between a core network and an access network; and a second interface is a user plane interface between the core network and the access network.
In an implementation, the packet header of the data packet includes at least one of the following: a GTP-U header, and an IP header.
That the packet header of the data packet carries the congestion status information of the first object is, for example, one of the following: the GTP-U header carries the congestion status information, and the IP header carries an ECN marking (for example, CE in the ECN marking, and a congestion occurrence marking).
In an implementation, the information element corresponding to the first QoS flow is an information element corresponding to the first QoS flow in the first interface message.
In an implementation, the making a packet header of the data packet in the first QoS flow carry congestion status information of the first object or congestion status information of the first QoS flow includes at least one of the following:
In an implementation, the downlink congestion status information and/or the uplink congestion status information does not need to be reflected by information with a direction. For example, the congestion status information carried in the uplink data packet may represent the uplink congestion status information. For example, the congestion status information carried in the downlink data packet may represent the downlink congestion status information.
In another implementation, the downlink congestion status information and/or the uplink congestion status information needs to be reflected by a direction. For example, the uplink congestion status information carried in the uplink data packet may represent the uplink congestion status information. For example, the downlink congestion status information carried in the uplink data packet may represent the downlink congestion status information. Alternatively, the uplink congestion status information carried in the information element or message may represent the uplink congestion status information. The downlink congestion status information carried in the information element or message may represent the downlink congestion status information.
In an implementation, the first radio bearer includes: a radio bearer to which the first QoS flow is mapped;
In an implementation, for example, the first radio bearer is a first DRB, and the first DRB may include one or more DRBs. Similarly, the first logical channel may include one or more logical channels. For example, in Extended Reality (XR), one QoS flow may correspond to a plurality of DRBs or a plurality of logical channels.
In an implementation, the monitoring a congestion status of a first object includes one or more of the following:
In an implementation, after the sending a first requirement, the method further includes:
In an implementation, the first object includes the second object.
The related information of the uplink congestion status includes at least one of the following: the uplink congestion status information, and an average queuing duration of the second object.
After acquiring the uplink congestion status information of the second object, the first communication device reports the uplink congestion status information of the second object as one piece of the congestion status information of the first object.
In an implementation, the congestion status includes one or more of the following:
In an implementation, the downlink congestion status information and/or the uplink congestion status information does not need to be reflected by information with a direction. For example, the congestion status information carried in the uplink data packet may represent the uplink congestion status information. For example, the congestion status information carried in the downlink data packet may represent the downlink congestion status information.
In another implementation, the downlink congestion status information and/or the uplink congestion status information needs to be reflected by a direction. For example, the uplink congestion status information carried in the uplink data packet may represent the uplink congestion status information. For example, the downlink congestion status information carried in the uplink data packet may represent the downlink congestion status information. Alternatively, the uplink congestion status information carried in the information element or message may represent the uplink congestion status information. The downlink congestion status information carried in the information element or message may represent the downlink congestion status information.
In an implementation, the downlink congestion level and/or a downlink congestion state level does not need to be reflected by information with a direction. For example, through information of the uplink congestion occurring together with the congestion level, it may be learned that the congestion level is the uplink congestion level.
In an implementation, the reporting the congestion status of the first object or reporting the congestion status of the first QoS flow includes one or more of the following: sending first congestion status information in a case that a congestion occurs in the first object; sending second congestion status information in a case that the congestion in the first object ends; sending third congestion status information in a case that a congestion level of the first object changes; sending the first congestion status information or fourth congestion status information in a case that an uplink congestion occurs in the first object; sending the second congestion status information or fifth congestion status information in a case that the uplink congestion in the first object ends; sending the third congestion status information or sixth congestion status information in a case that an uplink congestion level of the first object changes; sending the first congestion status information or seventh congestion status information in a case that the downlink congestion occurs in the first object; sending the second congestion status information or reporting eighth congestion status information in a case that the downlink congestion in the first object ends; and sending the third congestion status information or ninth congestion status information in a case that a downlink congestion level of the first object changes; where the first congestion status information includes first information and/or third information; the second congestion status information includes second information; the third congestion status information includes the third information; the fourth congestion status information includes fourth information and/or sixth information; the fifth congestion status information includes fifth information; and the sixth congestion status information includes the sixth information; the seventh congestion status information includes seventh information and/or ninth information; the eighth congestion status information includes eighth information; and the ninth congestion status information includes the ninth information.
In an implementation, in a case that a congestion occurs in an object (for example, another first object other than the first QoS flow) with a larger granularity than the first QoS flow, it may be considered that a congestion occurs in the first QoS flow, and the first congestion status information may be reported through signaling and/or user plane data with the granularity of the first QoS flow, for example, reported (1) through the signaling corresponding to the first QoS flow, or (2) through a packet header (for example, a GTP-U, an IP layer of an N3 interface, and an ECN marking of the IP layer) of the data packet in the first QoS flow, where the first congestion status information includes information configured for indicating that a congestion starts.
In another implementation, in a case that a congestion in an object (for example, another first object other than the first QoS flow) with a larger granularity than the first QoS flow ends, it is considered that the congestion in the first QoS flow ends, the second congestion status information is reported through signaling and/or user plane data with the granularity of the first QoS flow, and the second congestion status information includes information configured for indicating that the congestion ends.
In another implementation, in a case that a congestion level of an object (for example, another first object other than the first QoS flow) with a larger granularity than a granularity of a QOS flow changes (the level increases or decreases), it is considered that a congestion level of a data flow in the QoS flow changes, the third congestion status information is reported through signaling and/or user plane data with the granularity of the first QoS flow, and the third congestion status information includes information configured for indicating the congestion level.
In an implementation, that a congestion starts or a congestion occurs includes at least one of the following: QoS cannot be met, a data sending rate is less than a data receiving rate of an Nth object, time domain resources are insufficient, a buffer overflows, and a queue overflows;
In an implementation, the congestion status of the first object includes at least one of the following:
Through embodiments of this application, the first communication device performs one or more following operations according to the first requirement corresponding to a QoS flow: monitoring a congestion status of the QoS flow or an object with a larger granularity than the QoS flow, reporting congestion status information through signaling corresponding to the QoS flow or a data packet in the QoS flow, mapping the QoS flow to an independent radio bearer, and sending a first requirement, thereby implementing congestion monitoring and reporting of the QoS flow.
Referring to
The first requirement is an uplink congestion monitoring requirement corresponding to a first QoS flow, and/or, the first requirement is configured for requiring one or more of the following:
In an implementation, congestion status information in this embodiment includes uplink congestion status information.
Optionally, the second communication device acquires the first requirement from a second target end. The second target end includes at least one of the following: a first communication device, a fourth communication device, a fifth communication device, an AMF, an SMF, and a PCF.
Optionally, the second communication device reports the uplink congestion status of the second object or the uplink congestion status of the third object to the second target end.
In an implementation, the second object and the third object may be the same, and for example, are both the first radio bearer. The second object and the third object may be different. For example, the second object is the first radio bearer, and the third object is the first QoS flow.
In an implementation, a granularity of the second object is greater than or equal to a granularity of the third object.
In a case that the third object is the first QoS flow, the second object includes one or more of the following: the first QoS flow, the first radio bearer, the first logical channel, and the first logical channel group.
For example, in a case that the third object is the first radio bearer, the second object includes one or more of the following: the first radio bearer, the first logical channel, and the first logical channel group.
In a case that the third object is the first logical channel group, the second object includes one or more of the following: the first logical channel group.
In an implementation, the third object is the first QoS flow, and the uplink congestion status of the second object is reported or the uplink congestion status of the third object is reported through signaling corresponding to the first QoS flow or a data packet in the first QoS flow.
In another implementation, the third object is the first radio bearer, and the uplink congestion status of the second object is reported or the uplink congestion status of the third object is reported through signaling corresponding to the first radio bearer or a data packet in the first radio bearer.
In an implementation, the using a congestion status of the second object as a congestion status of a third object includes at least one of the following:
In an implementation, the reporting the uplink congestion status of the second object or reporting the uplink congestion status of the third object through the signaling corresponding to the third object includes:
In an implementation, the packet header of the data packet includes at least one of the following: a PDCP header, an RLC header, a MAC header, an IP header, a header (for example, a TCP header, an RTP header, or the like) of a protocol above an IP layer.
That the packet header of the data packet carries congestion status information of a first object is, for example, one of the following: a PDCP header, an RLC header, or a MAC header carries congestion status information (for example, a congestion starts, the congestion ends, and/or an uplink congestion level), and the IP header carries an ECN marking (for example, CE in the ECN marking, and a congestion occurrence marking). In an implementation, the foregoing congestion status information includes uplink congestion status information.
In an implementation, the information element corresponding to the third object is an information element corresponding to the third object in the Uu interface message. The Uu interface message is, for example, an RRC message.
In an implementation, the first radio bearer includes: a radio bearer to which the first QoS flow is mapped;
In an implementation, a first DRB may include one or more DRBs. Similarly, the first logical channel may include one or more logical channels. For example, in Extended Reality (XR), one QoS flow may correspond to a plurality of DRBs or a plurality of logical channels.
In an implementation, an uplink congestion status includes one or more of the following:
In an implementation, the uplink congestion status information does not need to be reflected by information with a direction. For example, the congestion status information carried in the uplink data packet may represent the uplink congestion status information.
In another implementation, the uplink congestion status information needs to be reflected by a direction. For example, the uplink congestion status information carried in the information element or message may represent the uplink congestion status information.
In an implementation, the reporting the uplink congestion status of the second object or reporting the uplink congestion status of the third object through the data packet in the third object includes one or more of the following:
In an implementation, in a case that a congestion occurs in an object (for example, another second object other than the first QoS flow) with a larger granularity than the first QoS flow, it may be considered that a congestion occurs in the first QoS flow.
In an implementation, in a case that a congestion in an object with a granularity larger than the granularity of the first QoS flow ends, it is considered that the congestion in the first Qos flow ends.
In an implementation, in a case that a congestion level of an object with a granularity larger than the granularity of the first QoS flow changes (the level increases or decreases), it is considered that a congestion level of a data flow in the first QoS flow changes.
In an implementation, that a congestion starts or a congestion occurs includes at least one of the following: QoS cannot be met, a data sending rate is less than a data receiving rate of an Nth object, time domain resources are insufficient, a buffer overflows, and a queue overflows;
Through embodiments of this application, UE performs uplink congestion monitoring and reporting according to an uplink congestion monitoring requirement, to implement that congestion monitoring and reporting of a QoS flow are performed on a UE side.
Referring to
The third operation includes one or more of the following:
Optionally, that the QoS flow has the congestion monitoring requirement is: acquiring the congestion monitoring requirement corresponding to the QoS flow.
Optionally, the QoS flow may be one or more QoS flows.
In an implementation, the mapping each QoS flow having a congestion monitoring requirement to an independent fourth object is: the QoS flow and the fourth object have a one-to-one correspondence. Another QoS flow is not mapped to the fourth object. The one fourth object is dedicated to one QoS flow.
Optionally, the “determining, based on whether a QoS flow has a congestion monitoring requirement, to map the QoS flow to a same fourth object or different fourth objects” is: using whether a QoS flow has a congestion monitoring requirement as one of the factors that determine to map the QoS flow to a radio bearer (for example, a DRB) or a logical channel.
For example, a first QOS flow, a second QoS flow, and a third QoS flow may be mapped to one same DRB according to a related rule (QOS parameters are the same or similar). However, the first QoS flow and the second QoS flow have congestion monitoring requirements, and the third QoS flow has no congestion monitoring requirement. In an implementation, the first QoS flow and the second QoS flow are mapped to one same DRB (referred to as a first DRB). The first DRB is different from a second DRB (the second DRB is a DRB to which the third QoS flow is mapped). In another implementation, the first QoS flow and the second QoS flow are respectively mapped to two independent DRBs.
In an implementation, the determining, based on whether a QoS flow has a congestion monitoring requirement, to map the QoS flow to a same fourth object or different fourth objects includes any one of the following:
The plurality of QoS flows are data flows of two or more QoS flows.
The “mapping, in a case that a second condition is met, a plurality of QoS flows to a same fourth object, where the second condition includes that the QoS flows have congestion monitoring requirements” may be represented as: in a case that a plurality of QoS flows are mapped to a fourth object, the plurality of QoS flows all have congestion monitoring requirements.
The second condition may further include at least one of the following: 5QIs of the plurality of QoS flows are the same, and QoS parameters of the plurality of QoS flows are the same.
For example, when the first QoS flow and the second QoS flow both have congestion monitoring requirements and have the same 5QI, the two may be mapped to one same fourth object. For example, when the first QoS flow and the second QoS flow both have congestion monitoring requirements but different 5QIs, the first QoS flow and the second QoS flow are mapped to different QoS flows.
In a case that the congestion monitoring requirements of the plurality of QoS flows are the same, it is understandable that the congestion monitoring requirement of the fourth object and the congestion monitoring requirement of the QoS flows are the same.
In a case that the congestion monitoring requirements of the plurality of QoS flows are different, the congestion monitoring requirement of the fourth object needs to meet congestion monitoring requirements of all QoS flows mapped to the fourth object. For example, for congestion monitoring, a QoS flow 1 requires reporting once every half hour, and a QoS flow 2 requires reporting once every one hour. In this case, the fourth object may require reporting once every half hour. For example, the QoS flow 1 requires reporting when a congestion level 1 is met, and the QoS flow 2 requires reporting when a congestion level 2 is met. In this case, the fourth object may require reporting when either the congestion level 1 or 2 is met.
In an implementation, before the performing, by the third communication device, a third operation, the method further includes:
It is noted that, the QoS flow may be one or more QoS flows.
In an implementation, that the QoS flow has the congestion monitoring requirement includes: acquiring the congestion monitoring requirement corresponding to the QoS flow;
In an implementation, the reporting the congestion status of the fourth object or reporting the congestion status of the QoS flow through signaling corresponding to the QoS flow and/or a data packet in the QoS flow includes:
In an implementation, the using the congestion status of the fourth object to which the QoS flow is mapped as the congestion status of the QoS flow includes at least one of the following:
In an implementation, the congestion status includes one or more of the following:
That a congestion starts or a congestion occurs includes at least one of the following: QoS cannot be met, a data sending rate is less than a data receiving rate of an Nth object, time domain resources are insufficient, a buffer overflows, and a queue overflows;
Through embodiments of this application, a QoS flow is mapped to a fourth object with a larger granularity. In this way, a congestion status of the QoS flow can be obtained by performing congestion monitoring on the fourth object.
Referring to
The fourth operation includes one or more of the following:
In an example, the congestion monitoring requirement corresponding to the QoS flow is sent to a third target end. The third target end includes at least one of the following: a first communication device, a second communication device, a sixth communication device, UE, a RAN network element, and a UPF.
In an implementation, the mapping each service data flow having a congestion monitoring requirement to an independent QoS flow is: the service data flow and the QoS flow have a one-to-one correspondence. Another service data flow is not mapped to the QoS flow. One QoS flow is dedicated to one service data flow.
In an implementation, the “determining, based on whether a service data flow has a congestion monitoring requirement, to map the service data flow to a same QoS flow or different QoS flows” is: using whether a service data flow has a congestion monitoring requirement as one of the factors that determine to map the service data flow to the QoS flow.
For example, a first service data flow, a second service data flow, and a third service data flow may be mapped to one same QoS flow according to a related rule (service data flows are the same or similar). However, the first service data flow and the second service data flow have congestion monitoring requirements, and the third service data flow has no congestion monitoring requirement. In an implementation, the first service data flow and the second service data flow are mapped to one same QoS flow (referred to as a first QoS flow). The first QoS flow is different from a second QoS flow (the second QoS flow is a QoS flow to which the third service data flow is mapped). In another implementation, the first service data flow and the second service data flow are respectively mapped to two independent QoS flows.
In an implementation, the determining, based on whether a service data flow has a congestion monitoring requirement, to map the service data flow to a same QoS flow or different QoS flows includes any one of the following:
It is noted that the plurality of service data flows are two or more service data flows.
The “mapping, in a case that a third condition is met, a plurality of service data flows to a same QoS flow, where the third condition includes that the service data flows have congestion monitoring requirements” may be reflected as: in a case that a plurality of service data flows are mapped to a QoS flow, the plurality of service data flows all have congestion monitoring requirements.
The third condition may further include at least one of the following: 5QIs of the plurality of service data flows are the same, and QoS parameters of the plurality of service data flows are the same.
For example, the first service data flow and the second service data flow both have congestion monitoring requirements and the same 5QI, and the two may be mapped to one same QoS flow.
For example, the first service data flow and the second service data flow both have congestion monitoring requirements but different 5QIs, in this case, the first service data flow and the second service data flow are mapped to different QoS flows.
In a case that the congestion monitoring requirements of the plurality of service data flows are the same, it is understandable that the congestion monitoring requirement of the QoS flow and the congestion monitoring requirement of the service data flows are the same.
In a case that the congestion monitoring requirements of the plurality of service data flows are different, the congestion monitoring requirement of the QoS flow needs to meet congestion monitoring requirements of all service data flows mapped to a fourth object. For example, for congestion monitoring, a service data flow 1 requires reporting once every half hour, and a service data flow 2 requires reporting once every one hour. In this case, the QoS flow may require reporting once every half hour. For example, the service data flow 1 requires reporting when a congestion level 1 is met, and the service data flow 2 requires reporting when a congestion level 2 is met. In this case, the QoS flow may require reporting when either the congestion level 1 or 2 is met.
In an implementation, before the performing, by the fourth communication device, the fourth operation, the method further includes:
It is noted that, the service data flows may be one or more service data flows.
In an implementation, the congestion monitoring requirement corresponding to the service data flow is acquired from a first source end. The first source end includes at least one of the following: a PCF, an AF, and a NEF.
In an implementation, that the service data flow has the congestion monitoring requirement includes: acquiring the congestion monitoring requirement corresponding to the service data flow;
In an implementation, the reporting the congestion status of the QoS flow or reporting the congestion status of the service data flow through signaling corresponding to the service data flow and/or a data packet in the service data flow includes:
In an implementation, the using a congestion status of the QoS flow to which the service data flow is mapped as a congestion status of the service data flow includes at least one of the following:
In an implementation, the reporting the congestion status of the fourth object or reporting the congestion status of the QoS flow through signaling corresponding to the QoS flow and/or a data packet in the QoS flow includes:
In an implementation, the using the congestion status of the fourth object to which the QoS flow is mapped as the congestion status of the QoS flow includes at least one of the following:
In an implementation, the congestion status includes one or more of the following:
Through embodiments of this application, a service data flow is mapped to a QoS flow. In this way, a congestion status of the service data flow can be obtained by performing congestion monitoring on the QoS flow.
Referring to
The fifth operation includes at least one of the following:
In an example, the congestion monitoring requirement corresponding to the first QoS flow is sent to a fourth target end. The fourth target end includes one or more of the following: a first communication device, a sixth communication device, a terminal, a RAN, and a UPF.
In an implementation, the first requirement is sent to a fifth target end. The fifth target end includes one or more of the following: a terminal.
In an implementation, the congestion monitoring requirement corresponding to the first QoS flow is configured for requiring one or more of the following:
In an implementation, the first object includes one or more of the following:
The foregoing first RAN network element is a RAN network element that allocates a radio resource to the first QoS flow.
In an implementation, the step of performing a fifth operation includes: acquiring a congestion monitoring requirement corresponding to a first service data flow, and performing the fifth operation according to the congestion monitoring requirement corresponding to the first service data flow, where
In an implementation, the congestion monitoring requirement corresponding to the first service data flow is configured for requiring one or more of the following:
Through embodiments of this application, a congestion monitoring requirement and/or a first requirement corresponding to a first QoS flow is sent, and a corresponding device performs a congestion monitoring operation.
Referring to
The sixth operation includes at least one of the following:
In an implementation, the congestion status information of the first QoS flow is acquired from a second source end. The second source end includes one or more of the following: a first communication device, and a terminal.
In an implementation, a plurality of service data flows may be mapped to one QoS flow. In other words, data of the plurality of service data flows may be transferred through one QoS flow. Generally, one service data flow may be mapped to one QoS flow, or may be mapped to a plurality of QoS flows.
The first service data flow may be all service data flows of the first QoS flow, or the first QoS flow has a service data flow with a congestion monitoring requirement.
In an implementation, the determining, by the sixth communication device, a congestion status of a first service data flow based on the congestion status information of the first QoS flow includes at least one of the following:
In an implementation, the determining, in a case that a congestion occurs in the first QoS flow, that a congestion occurs in the first service data flow includes at least one of the following: determining, in a case that an uplink congestion occurs in the first QoS flow, that an uplink congestion occurs in the first service data flow; and determining, in a case that a downlink congestion occurs in the first QoS flow, that a downlink congestion occurs in the first service data flow;
In an implementation, the congestion status includes one or more of the following:
In an implementation, the method further includes at least one of the following:
In an implementation, the acquiring, by the sixth communication device, congestion status information of a first QoS flow includes:
In an implementation, the acquiring, by the sixth communication device, congestion
status information of a first object or the congestion status information of the first QoS flow through signaling corresponding to the first QoS flow includes:
In an implementation, the acquiring the congestion status information of the first object or the congestion status information of the first QoS flow through the congestion status information of the first object carried in a packet header of the data packet in the first QoS flow includes:
In an implementation, the performing, by the sixth communication device, a sixth operation based on the congestion status information of the first QoS flow includes:
In an implementation, the congestion monitoring requirement corresponding to the first service data flow is configured for requiring one or more of the following:
Through embodiments of this application, based on acquired congestion status information of a QoS flow, a congestion status of a first service data flow is determined, and/or, congestion status information of the first service data flow is sent, thereby implementing congestion monitoring and reporting with a granularity of a service data flow.
The following describes technical solutions of this application with reference to the specific application scenarios.
Referring to
As shown in steps 1 and 2, a core network element sends the congestion monitoring requirement corresponding to a first QoS flow to the RAN. Details are as follows.
Step 1: A PCF sends a policy and charging control rule (Policy and Charging Control Rule, PCC rule) carrying the congestion monitoring requirement to an SMF. Step 2: The SMF sends the congestion monitoring requirement corresponding to the first QoS flow to the RAN.
The SMF may determine the congestion monitoring requirement of the first QoS flow according to a congestion monitoring requirement of a first service data flow, as shown in the embodiment in
Step 3: A user plane (for example, a UPF) of the CN sends downlink data to the RAN.
Step 4: In a case that a downlink congestion occurs in a first DRB, the RAN performs a first operation according to the congestion monitoring requirement corresponding to the first QoS flow, for example, reports a congestion status of a first object (for example, the first DRB) or reports a congestion status of the first QoS flow through signaling corresponding to the first QoS flow and/or a data packet in the first QoS flow. The process may enter step 5a and step 5b.
Step 5a: Add an ECN marking (for example, a CE value) corresponding to a congestion to downlink data that supports L4S (ECT (1)) in the first DRB.
Step 5b: Make a packet header of the data packet in the first QoS flow carry congestion status information of the first QoS flow, for example, report downlink congestion information through a GTP-U header corresponding to the first QoS flow. Because both uplink and downlink congestions need to be reported through the GTP-U header corresponding to the first QoS flow, direction information needs to be carried in congestion information in a GTP-U. For example, a packet header of an uplink data packet in the first QoS flow carries uplink congestion status information, where the uplink congestion status information is information describing an uplink congestion status of the first object or an uplink congestion status of the first QoS flow. The packet header of the uplink data packet in the first QoS flow carries downlink congestion status information, where the downlink congestion status information is information describing a downlink congestion status of the first object or a downlink congestion status of the first QoS flow.
Step 5C: Report the downlink congestion information through an NG interface message.
Step 6: In a case that an uplink congestion occurs in the first QoS flow in a Service Data Adaptation Protocol (SDAP) layer or above the SDAP layer, the process may enter step 7a or step 7b. Because the terminal is not affected in this embodiment, monitoring of a congestion at the air interface is not supported, and only a congestion status of data that has already reached the RAN is queued at the RAN to wait to be sent to the N3 interface can be monitored in the uplink. If a congestion that occurs in a case that the RAN sends data to a UPF, the congestion is reported.
Step 7a: Add an ECN marking (for example, a CE value) corresponding to a congestion to uplink data that supports LAS (ECT (1)) in the first QoS flow.
Step 7b: Make a packet header of the data packet in the first QoS flow carry congestion status information of the first QoS flow, for example, report downlink congestion information through a GTP-U header corresponding to the first QoS flow. Because both uplink and downlink congestions need to be reported through the GTP-U header corresponding to the first QoS flow, direction information needs to be carried in congestion information in a GTP-U. For example, a packet header of an uplink data packet in the first QoS flow carries uplink congestion status information, where the uplink congestion status information is information describing an uplink congestion status of the first object or an uplink congestion status of the first QoS flow. The packet header of the uplink data packet in the first QoS flow carries downlink congestion status information, where the downlink congestion status information is information describing a downlink congestion status of the first object or a downlink congestion status of the first QoS flow.
Step 5C: Report uplink congestion information through an NG interface message. An AMF then forwards the uplink congestion information to the SMF, and the SMF then forwards the uplink congestion information to the PCF.
Referring to
As shown in steps 1 and 2, a core network element sends a congestion monitoring requirement corresponding to the first QoS flow to the RAN. Details are as follows.
Step 1: A PCF sends a policy and charging control rule (Policy and Charging Control Rule, PCC rule) carrying a congestion monitoring requirement of a first service data flow to an SMF.
Step 2: The SMF sends the congestion monitoring requirement of the first QoS flow, for example, through an NG interface request message.
The SMF may determine the congestion monitoring requirement of the first QoS flow according to the congestion monitoring requirement of the first service data flow, as shown in the embodiment in
Step 3: The RAN sends an uplink congestion monitoring requirement of the first QoS flow to the UE.
In an implementation, in a case that the congestion monitoring requirement of the first QoS flow includes the uplink congestion monitoring requirement, the RAN sends the uplink congestion monitoring requirement, i.e., a first requirement, of the first QoS flow to the UE.
Step 4: The RAN sends an NG interface response message to the SMF.
Step 5: In a case that an uplink congestion occurs in a first DRB or the first QoS flow, the UE performs a second operation according to the first requirement, for example, sends one of the following through an information element and/or a Uu interface message corresponding to a third object (for example, the first DRB or the first QoS flow): congestion status information of a second object (for example, the first DRB or the first QoS flow), congestion status information of the third object, uplink congestion status information of the second object, uplink congestion status information of the third object, where specifically, the process may enter step 6a or step 6b. On a UE side, it is possible that a congestion with a granularity of a QoS flow can be monitored.
Step 6a: Add an ECN marking (for example, a CE value) corresponding to a congestion or an indication (another congestion indication different from the ECN marking) corresponding to a congestion to uplink data that supports LAS (ECT (1)) in the first DRB or the first QoS flow.
Step 6b: Report uplink congestion information to the RAN through RRC signaling.
Step 6C: Report the uplink congestion information to the CN through NAS signaling.
Step 7a: Optionally, report the uplink congestion information through a GTP-U header corresponding to the first QoS flow in a non-ECN marking manner.
Step 7b: Optionally, report the uplink congestion information through an NG message in a non-ECN marking manner.
Referring to
Optionally, the congestion monitoring requirement corresponding to the first QoS flow is configured for requiring one or more of the following:
Optionally, the uplink congestion monitoring requirement corresponding to the first QoS flow is configured for requiring one or more of the following:
Optionally, when using the congestion status of the first object as a congestion status of the first QoS flow, the first execution module is specifically configured to perform at least one of the following:
Optionally, when sending the first requirement, the first execution module is specifically configured to:
Optionally, when reporting the congestion status of the first object or reporting the congestion status of the first QoS flow through the signaling corresponding to the first QoS flow, the first execution module is specifically configured to:
Optionally, when making the packet header of the data packet in the first QoS flow carry the congestion status information of the first object or the congestion status information of the first QoS flow, the first execution module is specifically configured to perform at least one of the following:
Optionally, the first radio bearer includes: a radio bearer to which the first QoS flow is mapped;
Optionally, when monitoring the congestion status of the first object, the first execution module is specifically configured to perform one or more of the following:
Optionally, the communication device further includes:
Optionally, the congestion status includes one or more of the following:
Optionally, when reporting the congestion status of the first object or reporting the congestion status of the first QoS flow, the first execution module is specifically configured to perform one or more of the following:
Optionally, that a congestion starts or a congestion occurs includes at least one of the following: QoS cannot be met, a data sending rate is less than a data receiving rate of an Nth object, time domain resources are insufficient, a buffer overflows, and a queue overflows;
Optionally, the congestion status of the first object includes at least one of the following:
Referring to
Optionally, when using the congestion status of the second object as the congestion status of the third object, the second execution module is specifically configured to perform at least one of the following:
Optionally, when reporting the uplink congestion status of the second object or reporting the uplink congestion status of the third object through the signaling corresponding to the third object, the second execution module is specifically configured to:
Optionally, the first radio bearer includes: a radio bearer to which the first QoS flow is mapped;
Optionally, an uplink congestion status includes one or more of the following:
Optionally, when reporting the uplink congestion status of the second object or reporting the uplink congestion status of the third object, the second execution module is specifically configured to one or more of the following:
Optionally, that a congestion starts or a congestion occurs includes at least one of the following: QoS cannot be met, a data sending rate is less than a data receiving rate of an Nth object, time domain resources are insufficient, a buffer overflows, and a queue overflows;
Referring to
Optionally, when determining, based on whether a QoS flow has a congestion monitoring requirement, to map the QoS flow to a same fourth object or different fourth objects, the third execution module is specifically configured to perform any one of the following:
Optionally, the communication device further includes:
Optionally, that the QoS flow has the congestion monitoring requirement includes: acquiring the congestion monitoring requirement corresponding to the QoS flow;
Referring to
Optionally, before the determining, based on whether a service data flow has a congestion monitoring requirement, to map the service data flow to a same QoS flow or different QoS flows, the fourth execution module is specifically configured to perform any one of the following:
Optionally, the communication device further includes:
Optionally, that the service data flow has the congestion monitoring requirement includes: acquiring the congestion monitoring requirement corresponding to the service data flow;
Referring to
Optionally, the congestion monitoring requirement corresponding to the first QoS flow is configured for requiring one or more of the following:
Optionally, the first object includes one or more of the following:
Optionally, the step of performing the fifth operation by the fifth execution module includes: acquiring a congestion monitoring requirement corresponding to a first service data flow, and performing the fifth operation according to the congestion monitoring requirement corresponding to the first service data flow, where
Optionally, the congestion monitoring requirement corresponding to the first service data flow is configured for requiring one or more of the following:
Referring to
Optionally, when the sixth communication device determines the congestion status of the first service data flow based on the congestion status information of the first QoS flow, the sixth execution module is specifically configured to perform at least one of the following:
Optionally, the sixth execution module is specifically configured to:
Optionally, the congestion status includes one or more of the following: a congestion starts or a congestion occurs; a congestion ends or no congestion occurs; and a congestion level; and/or an uplink congestion status includes one or more of the following: an uplink congestion starts or an uplink congestion occurs; an uplink congestion ends or no uplink congestion occurs; and a congestion level or an uplink congestion level; and/or a downlink congestion status includes one or more of the following: a downlink congestion starts or a downlink congestion occurs; a downlink congestion ends or no downlink congestion occurs; and a congestion level or an uplink congestion level; and/or the congestion status information, downlink congestion status information, and/or uplink congestion status information includes one or more of the following: first information, configured for indicating that a congestion starts or a congestion occurs; second information, configured for indicating that a congestion ends or no congestion occurs; and third information, configured for indicating a congestion level; and/or the uplink congestion status information includes one or more of the following: fourth information, configured for indicating that an uplink congestion starts or an uplink congestion occurs; fifth information, configured for indicating that an uplink congestion ends or no uplink congestion occurs; and sixth information, configured for indicating a congestion level or an uplink congestion level; and/or the downlink congestion status information includes one or more of the following: seventh information, configured for indicating that a downlink congestion starts or a downlink congestion occurs; eighth information, configured for indicating that a downlink congestion ends or no downlink congestion occurs; and ninth information, configured for indicating a congestion level or a downlink congestion level.
Optionally, the sixth execution module is specifically configured to perform at least one of the following:
Optionally, when the sixth communication device acquires the congestion status information of the first QoS flow, the third acquisition module is specifically configured to:
Optionally, when the sixth communication device acquires the congestion status information of the first object or the congestion status information of the first QoS flow through the signaling corresponding to the first QoS flow, the third acquisition module is specifically configured to: acquire the congestion status information of the first object or the congestion status information of the first QoS flow through an information element corresponding to the first QoS flow and/or a first interface message, where or the acquiring, by the sixth communication device, the congestion status information of the first object or the congestion status information of the first QoS flow through the data packet in the first QoS flow includes: acquiring, by the sixth communication device, the congestion status information of the first object or the congestion status information of the first QoS flow through the congestion status information of the first object carried in a packet header of the data packet in the first QoS flow, where a first interface is a control plane interface between a core network and an access network; and a second interface is a user plane interface between the core network and the access network.
Optionally, when acquiring the congestion status information of the first object or the congestion status information of the first QoS flow through the congestion status information of the first object carried in the packet header of the data packet in the first QoS flow, the third acquisition module is specifically configured to:
Optionally, the step of performing, by the sixth communication device, the sixth operation based on the congestion status information of the first QoS flow performed by the sixth execution module includes:
Optionally, the congestion monitoring requirement corresponding to the first service data flow is configured for requiring one or more of the following:
The communication device in embodiments of this application may be an electronic device, for example, an electronic device with an operating system, or may be a component, for example, an integrated circuit or a chip, in an electronic device. The electronic device may be a terminal, or may be another device other than the terminal. For example, the terminal may include, but not limited to, the types of the terminal 11 listed above. The another device may be a server, a Network Attached Storage (NAS), or the like. This is not specifically limited in embodiments of this application.
The communication device in embodiments of this application can implement various processes implemented in the method embodiments in
Optionally, as shown in
Embodiments of this application further provide a terminal, including a processor and a communication interface. The terminal embodiment corresponds to the embodiments of the foregoing methods involving a terminal side. Various implementation processes and implementations in the foregoing method embodiments are applicable to the terminal embodiment, and can achieve the same technical effects. Specifically,
The terminal 1700 includes, but is not limited to, at least some components such as a radio frequency unit 1701, a network module 1702, an audio output unit 1703, an input unit 1704, a sensor 1705, a display unit 1706, a user input unit 1707, an interface unit 1708, a memory 1709, and a processor 1710.
It is understandable that the terminal 1700 may further include a power supply (for example, a battery) for supplying power to the components. The power supply may be logically connected to the processor 1710 by a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in
It should be understood that, in embodiments of this application, the input unit 1704 may include a Graphics Processing Unit (GPU) 17041 and a microphone 17042. The graphics processing unit 17041 performs processing on image data of a static picture or a video that is obtained by an image acquisition device (for example, a camera) in a video acquisition mode or an image acquisition mode. The display unit 1706 may include a display panel 17061. The display panel 17061 may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1707 includes at least one of a touch panel 17071 and another input device 17072. The touch panel 17071 is also referred to as a touchscreen. The touch panel 17071 may include two parts: a touch detection apparatus and a touch controller. The another input device 17072 may include, but not limited to, a physical keyboard, a functional key (for example, a volume control key or a switch key), a track ball, a mouse, and a joystick, which are not described herein in detail.
In embodiments of this application, after receiving downlink data from the network side device, the radio frequency unit 1701 may transmit the downlink data to the processor 1710 for processing. In addition, the radio frequency unit 1701 may send uplink data to the network side device. Generally, the radio frequency unit 1701 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
The memory 1709 may be configured to store a software program or instructions and various data. The memory 1709 may mainly include a first storage area for storing a program or instructions and a second storage area for storing data. The first storage area may store an operating system, an application or instructions required by at least one function (for example, a sound playback function and an image display function), and the like. In addition, the memory 1709 may include a volatile memory or a non-volatile memory, or the memory 1709 may include both a volatile memory and a non-volatile memory. The non-volatile memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM) or a flash memory. The volatile memory may be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDRSDRAM), an Enhanced SDRAM (ESDRAM), a Synchlink DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM). The memory 1709 in embodiments of this application includes, but is not limited to, these memories and any other suitable types.
The processor 1710 may include one or more processing units. Optionally, the processor 1710 integrates an application processor and a modem processor. The application processor mainly processes operations involving an operating system, a user interface, an application, and the like. The modem processor mainly processes a wireless communication signal, and is, for example, a baseband processor. It may be understood that the modem processor may either not be integrated into the processor 1710.
The processor 1710 is configured to perform the foregoing method involving a terminal side.
Embodiments of this application further provide a network side device. The network side device may be an access network device or a core network device, and includes a processor and a communication interface. The network side device embodiment corresponds to the embodiments of the foregoing method involving a network side device. Various implementation processes and implementations in the foregoing method embodiments are applicable to the network side device embodiment, and can achieve the same technical effects.
Specifically, embodiments of this application further provide a network side device. The network side device is an access network device. As shown in
The method performed by the network side device in the foregoing embodiments may be implemented in the baseband apparatus 183. The baseband apparatus 183 includes a baseband processor.
The baseband apparatus 183 may include, for example, at least one baseband board. A plurality of chips are disposed on the baseband board, as shown in
The network side device may further include a network interface 186. The interface is, for example, a Common Public Radio Interface (CPRI).
Specifically, the network side device 1800 in embodiments of this application further includes instructions or a program that are stored in the memory 185 and executable on the processor 184. The processor 184 calls the instructions or program in the memory 185 to perform the methods involving an access network device on a network side, and achieve the same technical effects. To avoid repetition, details are not described herein again.
Specifically, embodiments of this application further provide a network side device. The network side device is a core network device. As shown in
Specifically, the network side device 1900 in embodiments of this application further includes instructions or a program that are stored in the memory 1903 and executable on the processor 1901. The processor 1901 calls the instructions or program in the memory 1903 to perform the foregoing methods involving a core network device on a network side, and achieve the same technical effects. To avoid repetition, details are not described herein again.
Embodiments of this application provide a communication system is provided, and includes: a first communication device, a second communication device, a third communication device, a fourth communication device, a fifth communication device, and a sixth communication device. The first communication device may be configured to perform the steps of the method according to the first aspect. The second communication device may be configured to perform the steps of the method according to the second aspect. The third communication device may be configured to perform the steps of the method according to the third aspect. The fourth communication device may be configured to perform the steps of the method according to the fourth aspect. The fifth communication device may be configured to perform the steps of the method according to the fifth aspect. The sixth communication device may be configured to perform the steps of the method according to the sixth aspect.
Embodiments of this application further provide a readable storage medium. The readable storage medium stores a program or instructions. The program or instructions, when executed by a processor, implement various processes of the embodiments of the foregoing information processing method, and the same technical effects can be achieved. To avoid repetition, details are not described herein again.
The processor is a processor in the terminal in the foregoing embodiments. The readable storage medium includes a computer-readable storage medium, for example, a computer read-only memory ROM, a random access memory RAM, a magnetic disk, an optical disc, or the like.
Embodiments of this application further provide a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a program or instructions, to implement various processes of the foregoing embodiments of the information processing method, and can achieve the same technical effects. To avoid repetition, details are not described herein again.
It is understood that the chip in embodiments of this application may also be referred to as a system-level chip, a system chip, a chip system, a system-on-a-chip, or the like.
Embodiments of this application further provide a computer program/program product. The computer program/program product is stored in a storage medium. The computer program/program product, when being executed by at least one processor, implements various processes of the foregoing embodiments of the information processing method, and the same technical effects can be achieved. To avoid repetition, details are not described herein again.
Embodiments of this application further provide a communication system, including: a terminal and a network side device. The terminal may be configured to perform the steps of the foregoing method on a terminal side. The network side device may be configured to perform the steps of the foregoing method on a network side.
It should be noted that the terms “include”, “comprise”, or any other variation thereof in this specification is intended to cover a non-exclusive inclusion, which specifies the presence of stated processes, methods, objects, or apparatuses, but do not preclude the presence or addition of one or more other processes, methods, objects, or apparatuses. Without more limitations, elements defined by the sentence “including one . . . ” does not exclude that there are still other same elements in the processes, methods, objects, or apparatuses. In addition, it is noted that the scope of the methods and apparatuses in the implementations of this application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in reverse order based on the features involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Further, features described with reference to some examples may be combined in other examples.
Through the descriptions of the foregoing implementations, a person skilled in the art may clearly understand that the methods in the foregoing embodiments may be implemented by means of software and a necessary general hardware platform, and certainly, may also be implemented by hardware, but in many cases, the former manner is a better implementation. Based on such an understanding, the technical solutions of this application essentially or the part contributing to the related art may be implemented in a form of a computer software product. The computer software product is stored in a storage medium (for example, a ROM/RAM, a magnetic disk, or an optical disc) and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network side device, or the like) to perform the methods described in embodiments of this application.
Embodiments of this application are described above with reference to the accompanying drawings. However, this application is not limited to the foregoing specific implementations. The foregoing specific implementations are illustrative instead of limitative. Enlightened by this application, a person of ordinary skill in the art can make many forms without departing from the idea of this application and the scope of protection of the claims. All of the forms fall within the protection of this application.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202211081007.1 | Sep 2022 | CN | national |
This application is a continuation application of International Application No. PCT/CN2023/115666, filed on Aug. 30, 2023, which claims priority to Chinese Patent Application No. 202211081007.1 filed on Monday, Sep. 5, 2022, both of which are incorporated herein by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2023/115666 | Aug 2023 | WO |
| Child | 19070696 | US |
