Communication methods, communication equipment, communication systems, storage media and software products

Abstract

This disclosure relates to a communication method, communication device, communication system, storage medium, and program product. The method is executed by a first network device and includes: acquiring first information, wherein the first information indicates a first rule, the first rule being used by a terminal to route QUIC traffic. This disclosure enables efficient control of service data flows.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] As communication technologies continue to evolve, the demand for Quality of Service (QoS) of data streams in business processes is constantly increasing. Summary of the Invention

[0003] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0004] According to a first aspect of the present disclosure, a communication method is provided. The communication method is performed by a terminal. The communication method includes: acquiring first information, wherein the first information indicates a first rule, the first rule being used by the terminal to route user datagram protocol (UDP) internet connection (QUIC) traffic.

[0005] According to a second aspect of the present disclosure, a communication method is provided. This communication method is performed by a network device. The communication method includes: sending first information to a terminal, wherein the first information indicates a first rule, the first rule being used by the terminal to route QUIC traffic.

[0006] According to a third aspect of the present disclosure, a communication method is provided. The communication method is performed by a communication system. The communication system includes a network device and a terminal. The communication method includes: the network device sending first information to the terminal, wherein the first information indicates a first rule, the first rule being used by the terminal to route QUIC traffic.

[0007] According to a fourth aspect of the present disclosure, a communication device is provided. This communication device is used to perform the communication method as described in any one of the first to second aspects.

[0008] According to a fifth aspect of the present disclosure, a communication system is provided. The communication system includes at least one of the following: a network device and a terminal. The terminal is configured to perform the communication method as described in the first aspect. The network device is configured to perform the communication method as described in the second aspect.

[0009] According to a sixth aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any one of the first to third aspects.

[0010] According to a seventh aspect of the present disclosure, a program product is provided. The program product includes at least one of a program and instructions. When the program or instructions are executed by a communication device, they implement the communication method as described in any one of the first to third aspects.

[0011] According to an eighth aspect of the present disclosure, a computer program is provided. When this computer program is run on a computer, it causes the computer to perform the communication method as described in any one of the first to third aspects.

[0012] According to a ninth aspect of the present disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication method as described in any one of the first to third aspects.

[0013] According to embodiments of this disclosure, efficient control of business data flow can be achieved.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on the embodiments of this disclosure. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0016] Figure 1 This is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0017] Figure 2 This is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0018] Figure 3 This is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure.

[0019] Figure 4 This is an interactive schematic diagram of an exemplary implementation of the communication method provided in the embodiments of this disclosure.

[0020] Figure 5 This is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0021] Figure 6AThis is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure.

[0022] Figure 6B This is a schematic diagram of the chip structure provided according to an embodiment of the present disclosure. Detailed Implementation

[0023] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0024] In a first aspect, embodiments of this disclosure provide a communication method. This communication method is performed by a terminal. The communication method includes: acquiring first information, wherein the first information indicates a first rule, the first rule being used by the terminal to route QUIC traffic.

[0025] In this embodiment, the terminal can obtain first information. The first information indicates a first rule for routing QUIC traffic. After obtaining the first rule, the terminal can directly perform routing processing for QUIC traffic based on the first rule, without waiting for QoS parameters of data streams for specific services, thus speeding up the processing of QUIC traffic and improving communication efficiency.

[0026] In conjunction with some embodiments of the first aspect, in some embodiments, QUIC traffic includes standard communications with network elements (SCONE) data packets.

[0027] In this embodiment, QUIC traffic may include SCONE packets, and the terminal can implement routing for SCONE packets based on the first rule.

[0028] In conjunction with some embodiments of the first aspect, in some embodiments, the first rule includes at least one of the following: first indication information indicating QoS parameters applied to SCONE traffic; and second indication information indicating that traffic in a SCONE traffic group or connection is delivered based on federated QoS or session.

[0029] In this embodiment, the first rule includes first indication information and / or second indication information. On one hand, the first indication information indicates the QoS parameters applied to SCONE traffic, so the terminal can perform corresponding QoS processing based on the obtained first indication information. On the other hand, the second information can indicate that traffic in a SCONE traffic group or connection is transmitted based on federated QoS or session, so the terminal can implement federated QoS or session-based transmission of traffic in the SCONE traffic group or connection based on the obtained second information, thereby achieving consistent routing processing of traffic in the SCONE traffic group or connection and ensuring the transmission consistency of traffic in the SCONE traffic group or connection.

[0030] In conjunction with some embodiments of the first aspect, in some embodiments, the traffic in a SCONE traffic group or connection includes at least one of the following: uplink traffic; downlink traffic.

[0031] In conjunction with some embodiments of the first aspect, in some embodiments, the first rule includes a user equipment (UE) routing selection policy (URSP) rule, and the first indication information and / or the second indication information are contained in the traffic descriptor of the URSP rule.

[0032] In this embodiment, the first indication information and / or the second indication information are included in the traffic descriptor of the URSP rule. Thus, when the terminal uses the URSP rule for traffic matching, it can obtain the first indication information and / or the second indication information, thereby considering the first indication information and / or the second indication information when determining the route selection descriptor, ensuring that a more accurate routing path can be found and improving the efficiency of routing processing.

[0033] In conjunction with some embodiments of the first aspect, in some embodiments, the first rule includes a routing descriptor, and first indication information and / or second indication information are included in the routing descriptor.

[0034] In this embodiment, the first indication information and / or the second indication information are included in the routing descriptor. Thus, when the terminal uses the routing descriptor to route traffic, it can obtain the first indication information and / or the second indication information, avoiding any impact on the matching of traffic descriptors and improving the accuracy of traffic matching.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the operation of obtaining the first information includes at least one of the following: obtaining pre-configured first information; receiving first information sent by a network function.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is obtained during or after the registration process of the terminal.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the above method further includes: performing routing processing and / or QoS processing on QUIC traffic based on the first information.

[0038] In a second aspect, embodiments of this disclosure provide a communication method. This communication method is performed by a network device. The communication method includes: sending first information to a terminal, wherein the first information indicates a first rule, the first rule being used by the terminal to route QUIC traffic.

[0039] In this embodiment, the network device can provide first information to the terminal. The first information indicates a first rule for routing QUIC traffic. After obtaining the first rule, the terminal can directly perform routing processing for QUIC traffic based on the first rule, without waiting for QoS parameters of data streams for specific services, thus speeding up the processing of QUIC traffic and improving communication efficiency.

[0040] In conjunction with some embodiments of the second aspect, in some embodiments, QUIC traffic includes network element standard communication SCONE data packets.

[0041] In conjunction with some embodiments of the second aspect, in some embodiments, the first rule includes at least one of the following: first indication information indicating QoS parameters applied to SCONE traffic; and second indication information indicating that traffic in a SCONE traffic group or connection is delivered based on federated QoS or session.

[0042] In conjunction with some embodiments of the second aspect, in some embodiments, the traffic in a SCONE traffic group or connection includes at least one of the following: uplink traffic; downlink traffic.

[0043] In conjunction with some embodiments of the second aspect, in some embodiments, the first rule includes a URSP rule, and the first indication information and / or the second indication information are contained in the traffic descriptor of the URSP rule.

[0044] In conjunction with some embodiments of the second aspect, in some embodiments, the first rule includes a routing descriptor, and first indication information and / or second indication information are included in the routing descriptor.

[0045] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is sent during or after the registration process of the terminal.

[0046] In a third aspect, embodiments of this disclosure provide a communication method. This communication method is executed by a communication system. The communication system includes a network device and a terminal. The communication method includes: the network device sending first information to the terminal, wherein the first information indicates a first rule, the first rule being used by the terminal to route QUIC traffic.

[0047] In a fourth aspect, embodiments of this disclosure provide a communication device. The communication device is a terminal. The communication device includes a transceiver module. The transceiver module is configured to: acquire first information, wherein the first information indicates a first rule, the first rule being used by the terminal to route QUIC traffic.

[0048] In conjunction with some embodiments of the fourth aspect, in some embodiments, QUIC traffic includes network element standard communication SCONE data packets.

[0049] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first rule includes at least one of the following: first indication information indicating QoS parameters applied to SCONE traffic; and second indication information indicating that traffic in a SCONE traffic group or connection is delivered based on federated QoS or session.

[0050] In conjunction with some embodiments of the fourth aspect, in some embodiments, the traffic in a SCONE traffic group or connection includes at least one of the following: uplink traffic; downlink traffic.

[0051] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first rule includes a URSP rule, and first indication information and / or second indication information are contained in the traffic descriptor of the URSP rule.

[0052] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first rule includes a routing descriptor, and first indication information and / or second indication information are included in the routing descriptor.

[0053] In conjunction with some embodiments of the fourth aspect, in some embodiments, the operation of obtaining the first information includes at least one of the following: obtaining pre-configured first information; receiving first information sent by a network function.

[0054] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first information is obtained during or after the registration process of the terminal.

[0055] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above-described communication device further includes a processing module; the processing module is configured to perform routing processing and / or QoS processing of QUIC traffic based on the first information.

[0056] In a fifth aspect, embodiments of this disclosure provide a communication device. This communication device is a network device. The communication device includes a transceiver module. The transceiver module is configured to send first information to a terminal, wherein the first information indicates a first rule, the first rule being used by the terminal to route QUIC traffic.

[0057] In conjunction with some embodiments of the fifth aspect, in some embodiments, QUIC traffic includes network element standard communication SCONE data packets.

[0058] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first rule includes at least one of the following: first indication information indicating QoS parameters applied to SCONE traffic; and second indication information indicating that traffic in a SCONE traffic group or connection is delivered based on federated QoS or session.

[0059] In conjunction with some embodiments of the fifth aspect, in some embodiments, the traffic in a SCONE traffic group or connection includes at least one of the following: uplink traffic; downlink traffic.

[0060] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first rule includes a URSP rule, and first indication information and / or second indication information are contained in the traffic descriptor of the URSP rule.

[0061] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first rule includes a routing descriptor, and first indication information and / or second indication information are included in the routing descriptor.

[0062] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first information is sent during or after the registration process of the terminal.

[0063] In a sixth aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication methods described in any of the first to second aspects and their possible implementations.

[0064] In a seventh aspect, embodiments of this disclosure provide a communication system. The communication system includes a network device and a terminal. The terminal is configured to perform the communication method as described in any of the first aspect and its possible embodiments. The network device is configured to perform the communication method as described in any of the second aspect and its possible embodiments.

[0065] In an eighth aspect, embodiments of this disclosure provide a storage medium storing instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in any of the first to third aspects and their possible implementations.

[0066] In a ninth aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the communication method as described in any of the first to third aspects and their possible implementations.

[0067] In a tenth aspect, embodiments of this disclosure provide a computer program. When this computer program is run on a computer, it causes the computer to perform the communication methods described in any of the first to third aspects and their possible implementations.

[0068] In an eleventh aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in any of the first to third aspects and their possible implementations.

[0069] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0070] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method, information processing method, and information transmission method can be used interchangeably; terms such as communication device, communication equipment, network equipment, network function, and network entity can be used interchangeably; and terms such as communication system and information processing system can be used interchangeably.

[0071] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0072] In the embodiments disclosed herein, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the various embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0073] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0074] In this disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular or a plural expression.

[0075] In the embodiments of this disclosure, "a plurality of" means two or more.

[0076] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0077] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0078] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0079] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0080] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0081] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0082] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0083] In some embodiments, terms such as “greater than,” “more than,” “higher than,” and “exceeding” can be used interchangeably; terms such as “greater than or equal to,” “not less than,” “more than or equal to,” “not less than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably; terms such as “less than,” “less than,” and “lower than” can be used interchangeably; and terms such as “less than or equal to,” “not greater than,” “less than or equal to,” “not more than,” “lower than or equal to,” “not higher than,” and “below” can be used interchangeably.

[0084] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0085] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0086] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0087] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

[0088] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0089] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0090] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0091] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0092] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0093] Figure 1 This is a schematic diagram of the architecture of a communication system provided according to embodiments of this disclosure. Figure 1 As shown, the communication system 100 includes a terminal 101, an access network device 102, and a core network 103.

[0094] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0095] In some embodiments, the access network device 102 may be a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0096] In some embodiments, the technical solutions of this disclosure can be applied to Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be internal interfaces of OpenRAN. The processes and information exchanges between these internal interfaces can be implemented by software or programs.

[0097] In some embodiments, the access network device 102 may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0098] In some embodiments, the core network 103 may be a single device, including a first network device 1031, a second network device 1032, a third network device 1033, a fourth network device 1034, a fifth network device 1035, etc., or it may be multiple devices or a group of devices, each including all or part of the first network device 1031, the second network device 1032, the third network device 1033, the fourth network device 1034, the fifth network device 1035, etc. Network elements in the core network 103 may be virtual or physical. The core network 103 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and a 6GCN.

[0099] In some embodiments, the first network device 1031, the second network device 1032, the third network device 1033, the fourth network device 1034, and the fifth network device 1035 may be referred to as the first network function 1031, the second network function 1032, the third network function 1033, the fourth network function 1034, and the fifth network function 1035.

[0100] In some embodiments, the first network device 1031 may be a user plane network element or a data plane network element.

[0101] In some embodiments, the first network device 1031 may be responsible for implementing data routing and forwarding, policy enforcement and flow control, QoS management, etc.

[0102] In some embodiments, the first network device 1031 may be a user plane function (UPF). In one example, the first network device 1031 may be an access UPF, an insert UPF, a PDU session anchor (PSA) UPF, etc.

[0103] In some embodiments, the first network device 1031 may also be other network functions, such as an access network device.

[0104] In some embodiments, the second network device 1032 may be a control plane network element.

[0105] In some embodiments, the second network device 1032 may be responsible for session management, UPF selection and control, QoS policy implementation, etc.

[0106] In some embodiments, the second network device 1032 may be, for example, a session management function (SMF).

[0107] In some embodiments, the third network device 1033 may be a control plane network element.

[0108] In some embodiments, the third network device 1033 may be used to support a unified policy framework and provide policy rules, the names of which are not limited thereto.

[0109] In some embodiments, the third network device 1033 may be, for example, a policy control function (PCF).

[0110] In some embodiments, the third network device 1033 may be, for example, a policy control function in a 6GCN.

[0111] In some embodiments, the fourth network device 1034 may provide application services, the names of which are not limited thereto.

[0112] In some embodiments, the fourth network device 1034 may include, for example, an application function (AF) and / or an application server (AS).

[0113] In some embodiments, the fourth network device 1034 may be located in a data network (DN).

[0114] In some embodiments, the fourth network device 1034 may be located outside the core network 103, or inside the core network 103, or partially inside and partially outside the core network 103. This disclosure does not specifically limit this.

[0115] In some embodiments, the AF and AS in the fourth network device 1034 can be deployed centrally or independently, and this disclosure does not specifically limit this.

[0116] In some embodiments, the fifth network device 1035 may be a control plane network element.

[0117] In some embodiments, the fifth network device 1035 may be used to perform mobility management, non-access stratum mobility management signaling processing, non-access stratum session management, security anchor point and security context management, etc., and the name is not limited thereto.

[0118] In some embodiments, the fifth network device 1035 may be, for example, an access and mobility management function (AMF).

[0119] In some embodiments, the communication system 100 described above may be a 5G communication system or a 6G communication system. It should be noted that the communication system 100 may also be other communication systems, such as a 4G communication system or a 5G-A (5G-advanced) communication system, and this disclosure does not specifically limit it in this regard.

[0120] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0121] The following embodiments of this disclosure can be applied to Figure 1 The communication system 100 shown, or a part of the main body of the communication system 100, but not limited thereto. Figure 1 The entities shown are illustrative; the communication system 100 may include... Figure 1 All or part of the main body, or may include Figure 1 Other entities besides the main body, the number and form of each entity are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is illustrative, the entities can be unconnected or connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0122] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0123] Immersive communication is an extension of enhanced mobile broadband (eMBB) and covers a wide range of cases. In these cases, it can provide users with rich, interactive (immersive) video experiences, including interactions with machine interfaces.

[0124] In some embodiments, with the development of communication technology, immersive extended reality (XR) services in communication systems aim to provide an excellent user experience through capabilities such as ultra-high resolution, high frame rate, wide color gamut, high dynamic range, wide viewing angle, and advanced encoding / compression technologies.

[0125] In some embodiments, immersive XR services can support more natural interaction methods, such as voice interaction, gesture interaction, head interaction, and eye tracking, thereby achieving complex user and environmental awareness. Communication systems and service platforms can collaborate to perform functions such as rendering, synchronization, encoding, distribution, storage, and management of immersive XR services, and support real-time transmission and processing of panoramic video data, field of view (FOV) video data, etc.

[0126] In some embodiments, users of immersive communication technologies expect to work, play, and interact seamlessly in both the real and virtual worlds. Such immersive experiences can be achieved through advanced extended reality (AXR) and multimedia features. These features include, for example, user interaction via a combination of avatar-holographic conferencing, spatial collaboration with high-fidelity three-dimensional (3D) objects, high-resolution immersive 2D-3D cloud gaming, high-resolution 360-degree 2D-3D content streaming, and AI-based multimodal user experiences.

[0127] In further scenarios, XR services and interactive media services require communication systems to comprehensively consider the QoS characteristics of service data streams. These QoS characteristics include, for example, at least one of the following: whether parameters such as delay-sensitive guaranteed bitrate (GBR) data streams, guaranteed flow bit rate (GFBR), packet PDU set delay budget (PDB), and default maximum data burst volume (MDBV) can be simultaneously met and consistently maintained. This involves ensuring consistent QoS authentication and execution across multiple XR data streams from a single terminal and XR data streams from multiple terminals.

[0128] In some embodiments, the SDF of XR can support PDU set-based processing, thereby enhancing QoS awareness and assurance of the SDF and improving the user's quality of experience (QoE).

[0129] In some embodiments, such as 4G, 5G, 6G, and V2X systems, the AF (Active Front-End) can provide PDU set QoS parameters and a protocol description. In some embodiments, the PDU set QoS parameters may include at least one of the following: PDU set delay budget (PSDB), PDU set error rate (PSER), and PDU set integrated handling information (PSIHI). Then, the SMF (Service Provider Framework) and UPF (User Provider Framework) can combine the protocol description and header extensions provided by the AF to extend the packet headers of the PDUs in the SDF's PDU set to carry PDU set information. The carried PDU information can be used by the access network for PDU set-based QoS handling.

[0130] In some embodiments, the PDU set information may include at least one of the following: PDU set sequence number, the starting or ending PDU of the PDU set, the PDU sequence number within the PDU set, the number of PDUs within the PDU set, the importance of the PDU set, and the size of the PDU set. Here, the importance of the PDU set is used to characterize the importance of a PDU set relative to other PDU sets in the same QoS flow.

[0131] In some embodiments, immersive services typically feature delay-critical traffic. Delay-critical traffic is characterized by extremely low latency and high reliability to guarantee high quality of service (QoS) and quality of experience (QoE) for users. To this end, communication systems can support more features, such as round-trip time (RTT) latency, PDU-based processing, low latency, low loss, and scalable throughout (L4S) throughput, explicit congestion notification (ECN) control, data burst marking, next burst time stamping, and data enhancement to accelerate transmission. However, despite the introduction of these features, the requirements for delay-critical traffic remain difficult to meet in terms of power consumption, adaptive QoS, and deterministic user experience.

[0132] In some embodiments, the continuous development of communication networks always requires consideration of improving existing services and supporting new services. Therefore, the design of the QoS architecture in a communication network needs to consider the following aspects:

[0133] 1. Consider emerging traffic characteristics and application requirements (e.g., traffic from AI / ML applications), whether new features are needed in the QoS architecture, and what new features are required.

[0134] 2. Whether to enhance the QoS mechanism and how to enhance it:

[0135] (1) Support QoS objectives that meet the application’s QoS requirements (e.g., dynamic QoS requirements) in a way that is less resource-intensive than existing GBR, delay-critical GBR, etc.

[0136] 3. If the current QoS objective cannot be met, is it necessary to adjust the QoS objective, and what kind of enhancements are needed to adjust the QoS objective in order to minimize the impact on application operation or user experience?

[0137] 4. How to support QoS cooperation between UE, application and network to improve the 6G system's (6GS) awareness of application traffic (e.g., traffic patterns, dynamic QoS requirements) and improve the application and / or UE's awareness of the content provided to the network (e.g., maximum bit rate).

[0138] 5. Whether and how to improve QoS monitoring based on identified needs, such as determining end-to-end packet latency, PSA-UPF and packet loss rate between UE, to verify whether QoS goals have been achieved.

[0139] 6. Whether enhancements are needed and what enhancements are required to implement QoS differentiation, for example, when the server address changes frequently or when application traffic has multiplexed media streams.

[0140] In some embodiments, the communication network is enhanced to directly interact with the application on the video bitrate (e.g., throughput recommendations), for example, through SCONE rate control. This is beneficial for efficiently meeting QoS objectives and improving user experience.

[0141] Therefore, how to achieve rate control of data streams is a technical problem that urgently needs to be solved.

[0142] Figure 2 This is an interactive schematic diagram of a communication method provided according to an embodiment of this disclosure. The communication method involved in this embodiment can be applied to a communication system 100. Figure 2 As shown, the communication method of this embodiment includes steps S201 to S213.

[0143] In step S201, terminal 101 registers with the network.

[0144] In some embodiments, terminal 101 may initiate a registration process to register with the network. In some embodiments, terminal 101 may send a registration request message to trigger a registration process for terminal 101.

[0145] In some embodiments, step S201 may include: terminal 101 sending second information. In some embodiments, the second information may indicate the capabilities of terminal 101. For example, the second information may include capability information of terminal 101.

[0146] In some embodiments, the second information may indicate the terminal 101's support capability for QoS configuration and / or negotiation based on UE policies. In some embodiments, the second information may indicate that the terminal 101 supports performing QoS configuration and / or negotiation based on UE policies. In some embodiments, the second information may indicate the UE policy-related functions supported by the terminal 101. In some embodiments, the second information may also indicate the terminal 101's support capability for SCONE rate control.

[0147] In some embodiments, the second information may be included in the registration request message. In some embodiments, the second information may be sent independently of the registration request message. In some embodiments, the second information sent by terminal 101 may reach third network device 1033 and / or unified data management (UDM) and / or unified data repository (UDR) via at least one of access network device 102, fifth network device 1035, and first network device 1031.

[0148] In some embodiments, step S201 may include establishing a UE policy association between the fifth network device 1035 and the third network device 1033. In one example, the registration request message sent by the terminal 101 to the fifth network device 1035 may contain a UE policy container. The fifth network device 1035 can determine to establish a UE policy association with the third network device 1033 upon obtaining the UE policy container. In one example, the fifth network device 1035 can determine to establish a UE policy association with the third network device 1033 based on its own configuration.

[0149] In some embodiments, the fifth network device 1035 may send a request message to the third network device 1033 to request the establishment of a UE policy association. For example, the request message may be an Npcf_UEPolicyControl_Create request. In some embodiments, the request message may include at least one of the following: the identifier of the terminal 101, the location of the terminal 101, and a UE policy container. In some embodiments, the fifth network device 1035 may send a response message to the third network device 1033 to establish a UE policy association based on the policy information subscribed to by the terminal 101 obtained from the UDM and / or UDR.

[0150] In some embodiments, the second information may also indicate the terminal 101's support capability for SCONE rate control. In some embodiments, the second information may indicate whether the terminal 101 supports functions related to SCONE rate control. For example, the second information may indicate that the terminal 101 supports functions related to SCONE rate control, and / or the terminal supports functions related to SCONE rate control.

[0151] In some embodiments, the functions related to SCONE rate control may include at least one of the following: identification of data streams subject to SCONE rate control, reporting of data streams subject to SCONE rate control, and marking of rate limits in SCONE packets.

[0152] In some embodiments, the rate limit marker in a SCONE packet may refer to marking a rate limit in a SCONE packet. In some embodiments, the rate limit marker in a SCONE packet may include at least one of the following: detecting a rate limit in a SCONE packet; determining a rate limit in a SCONE packet; inserting a rate limit in a SCONE packet; or updating a rate limit in a SCONE packet.

[0153] In step S202, the third network device 1033 sends the first information to the terminal 101.

[0154] In some embodiments, the third network device 1033 may send the first information. In some embodiments, the first information may be sent by the third network device 1033, but is not limited thereto, and may also be sent by other entities.

[0155] In some embodiments, terminal 101 may receive first information. In some embodiments, the first information may be received by terminal 101, but is not limited thereto, and may also be received by other entities.

[0156] In some embodiments, the first information may indicate a first rule. In some embodiments, the first information may be used to issue a first rule. In some embodiments, the first information may be used to provide a first rule to terminal 101.

[0157] In some embodiments, the name of the first information is not limited, and may be, for example, information to be distributed, configuration information, policy information, rule information, etc.

[0158] In some embodiments, the first rule may include at least one of the following: UE policy and QoS parameters.

[0159] In some embodiments, the UE policy (or UE policy information) may be policy information configured or provided for the terminal 101, used for access selection, PDU session selection, etc. of the terminal 101.

[0160] In some embodiments, the UE policy may include a UE route selection policy (URSP). In some embodiments, the URSP can be used by terminal 101 to determine the route to SCONE traffic. For example, based on the URSP, SCONE traffic may be routed to an existing PDU session or trigger the establishment of a new PDU session.

[0161] In some embodiments, the QoS parameter may be a parameter related to the QoS processing performed on SCONE traffic. In some embodiments, the QoS parameter may include QoS processing guidance.

[0162] In some embodiments, a URSP may include URSP rules and routing descriptors. URSP rules can be used to identify and match traffic. Routing descriptors can be used to determine the routing process for matched traffic. In some embodiments, a URSP may include one or more URSP rules. Each URSP rule may correspond to one or more routing descriptors. In some embodiments, routing descriptors corresponding to a URSP rule may have different priorities. In some embodiments, routing descriptors corresponding to different URSP rules may be the same or at least partially different, and / or have different priority orders.

[0163] In some embodiments, a URSP rule may include at least one of the following: rule priority and one or more traffic descriptors. In some embodiments, rule priority may be used to determine the order in which different URSP rules are implemented on terminal 101. It is understood that rule priority may also be referred to as rule preference, and traffic descriptors may also be referred to as traffic descriptor composition.

[0164] In some embodiments, the traffic descriptor in the URSP rule may include at least one of the following: application descriptor, Internet Protocol (IP) descriptor, domain descriptor, non-IP descriptor, connection capabilities, and connectivity group ID. In some embodiments, the application descriptor includes the identifier of the operating system and / or the identifier of the operating system application. In some embodiments, the IP descriptor may include a triple of the destination IP address. For example, the triple may include the IP address, port number, and the protocol identifier of the protocol over the IP. In some embodiments, the domain descriptor may include at least one of the following: fully qualified domain name (FQDN) and a rule expression used as the domain name. In some embodiments, the non-IP descriptor may include a descriptor for destination information of non-IP traffic. In some embodiments, the connectivity capabilities may be matched with information provided by the UE application.

[0165] In some implementation sets, a route selection descriptor may include at least one of the following: a route selection descriptor priority, or one or more route selection components. In some embodiments, the route selection descriptor priority may be used to determine the selection order of different route selection descriptors on terminal 101. It is understood that the route selection descriptor priority may also be referred to as a route selection descriptor preference.

[0166] In some embodiments, the first rule may include first indication information and / or second indication information. In some embodiments, the first indication information may indicate QoS parameters applied to SCONE traffic. In some embodiments, the second indication information may indicate a SCONE traffic group or connection. In some embodiments, the first indication information may include at least one of the following: URSP rules and routing descriptors. In some embodiments, the second indication information may include at least one of the following: URSP rules and routing descriptors.

[0167] In some embodiments, the first indication information and / or the second indication information may be included in the traffic descriptor of the URSP rule in the first rule, as shown in Table 1 below. In some embodiments, the first indication information for indicating QoS parameters applied to SCONE traffic may be included in the URSP rule. For example, the first indication information may be a traffic descriptor in the URSP rule. In some embodiments, the second indication information for indicating whether traffic in a SCONE traffic group or connection is delivered based on federated QoS or session may be included in the URSP rule. For example, the second indication information may be a traffic descriptor in the URSP rule.

[0168]

[0169]

[0170] Table 1: UE Routing Selection Policy Rules

[0171] In some embodiments, the first indication information and / or the second indication information may be included in the routing descriptor of the first rule, as shown in Table 2 below. In some embodiments, the first indication information for indicating QoS parameters applied to SCONE traffic may be included in the routing descriptor. For example, the first indication information may be a routing component in the routing descriptor. In some embodiments, the second indication information for indicating whether traffic in a SCONE traffic group or connection is delivered based on federated QoS or session may be included in the routing descriptor. For example, the second indication information may be a routing component in the routing descriptor.

[0172]

[0173]

[0174] Table 2: Routing Descriptors

[0175] In some embodiments, traffic in a SCONE traffic group or connection includes at least one of the following: uplink traffic; downlink traffic. For example, a SCONE traffic group or connection may include multiple uplink traffic. For example, a SCONE traffic group or connection may include multiple downlink traffic. For example, a SCONE traffic group or connection may include at least one uplink traffic and at least one downlink traffic.

[0176] In some embodiments, all or part of the traffic in a SCONE traffic group or connection may be delivered using joint QoS.

[0177] In some embodiments, all or part of the traffic in a SCONE traffic group or connection may be delivered using the same PDU session.

[0178] In some embodiments, terminal 101 may receive first information determined and sent by third network device 1033. In some embodiments, the determination of the first information by third network device 1033 may be based on at least one of the following: second information, subscription information of terminal 101, and configuration of third network device 1033. For example, the configuration of third network device 1033 may include at least one of the following: operations administration and maintenance (OAM) configuration, operator policy, and local configuration.

[0179] In some embodiments, terminal 101 may receive first information sent by a network function. In one example, the network function may be a third network device 1033. In another example, the network function may be other network devices, such as access network device 102 or a fifth network device 1035.

[0180] In some embodiments, the first information may be pre-configured. For example, terminal 101 may obtain the pre-configured first information locally. In one example, step S202 may not be executed, and terminal 101 may obtain the first information locally. In another example, step S202 may be executed, and terminal 101 may obtain the final first information based on the locally pre-configured first information and the first information received from the third network device 1033.

[0181] In some embodiments, step S202 may be performed during the registration process of terminal 101. In some embodiments, step S202 may be performed after the registration process of terminal 101.

[0182] In step S203, the first network device 1031 receives the fifth information.

[0183] In some embodiments, the first network device 1031 may receive the fifth information. In some embodiments, the fifth information may be received by the first network device 1031, but is not limited thereto, and may also be received by other entities.

[0184] In some embodiments, the fifth information can be used to enable SCONE rate control. In some embodiments, the fifth information can be used to determine whether to perform SCONE rate control for a data flow of a first service. In some embodiments, the fifth information can be used to instruct one or more network devices to perform SCONE rate control.

[0185] In some embodiments, the fifth information can be used to enable or disable SCONE rate control. In some embodiments, the fifth information can be used to activate or deactivate SCONE rate control. In some embodiments, the fifth information can be used to determine whether SCONE rate control is performed or not for a data flow of a first service. In some embodiments, the fifth information can be used to instruct one or more network devices to perform or not perform SCONE rate control.

[0186] In some embodiments, the name of the fifth message is not limited, and it may be, for example, indication message, notification message, activation message, enable message, etc.

[0187] In some embodiments, the first service can be any type of service. In some embodiments, the first service may include immersive services, media streaming services, AI / ML-related services, and other types of services, which are not specifically limited in this disclosure. In some embodiments, the first service may be a QoS-critical service. In some embodiments, the traffic of the data stream of the first service may change dynamically. For example, the traffic size of the data stream of the first service may change rapidly. In one example, the first service may be a media streaming service, and the traffic size of the media stream may change with the resolution of the media.

[0188] In some embodiments, the data stream of the first service can be rate-controlled based on the SCONE mechanism. In some embodiments, under the SCONE mechanism, SCONE packets can be added to data packets in the data stream of the first service. The presence of SCONE packets allows the data stream of the first service to be detected as SCONE traffic.

[0189] In some embodiments, a SCONE packet may include a throughput advice for traffic. This throughput advice can be used to indicate to the application layer the recommended rate for a data flow of a first service. In some embodiments, the throughput advice can be implemented as a rate limit in the SCONE packet. This rate limit can be used to indicate the recommended rate value. In some embodiments, the field carrying the rate limit may include 7 bits, and the value of this field ranges from 0 to 127. For example, 127 can be the default value. For example, the default value of 127 can indicate that the data flow (or traffic) containing this packet uses SCONE rate control.

[0190] In some embodiments, rate control of data streams based on the SCONE mechanism can be referred to as SCONE rate control. In some embodiments, SCONE rate control may include at least one of the following: increasing the rate, decreasing the rate, or maintaining a constant rate.

[0191] In some embodiments, the fifth information may indicate at least one of the following: applying SCONE rate control to the data stream of the first service; or the terminal 101's support for SCONE rate control.

[0192] In some embodiments, the fifth information may include a SCONE rate control indication. In some embodiments, the SCONE rate control indication may indicate a characteristic of SCONE rate control. In some embodiments, the SCONE rate control indication may indicate that the data stream of the first service supports SCONE rate control. In some embodiments, the SCONE rate control indication may indicate that the data stream of the first service has the characteristic of SCONE rate control. In some embodiments, the SCONE rate control indication may indicate that SCONE rate control is implemented on the data stream of the first service.

[0193] In some embodiments, the fifth information may include capability information of terminal 101. In some embodiments, the capability information may indicate the terminal 101's support capability for SCONE rate control. In some embodiments, the capability information may indicate whether terminal 101 supports functions related to SCONE rate control. For example, the capability information may indicate that terminal 101 supports functions related to SCONE rate control, and / or the SCONE rate control-related functions supported by the terminal.

[0194] In some embodiments, the functions related to SCONE rate control may include at least one of the following: identification of data streams subject to SCONE rate control, reporting of data streams subject to SCONE rate control, and marking of rate limits in SCONE packets.

[0195] In some embodiments, the rate limit marker in a SCONE packet may refer to marking a rate limit in a SCONE packet. In some embodiments, the rate limit marker in a SCONE packet may include at least one of the following: detecting a rate limit in a SCONE packet; determining a rate limit in a SCONE packet; inserting a rate limit in a SCONE packet; or updating a rate limit in a SCONE packet.

[0196] In some embodiments, the fifth information may be sent by terminal 101. In some embodiments, terminal 101 may send the fifth information to first network device 1031. For example, the fifth information sent by terminal 101 may reach first network device 1031 via access network device 102 and / or fifth network device 1035.

[0197] In one example, when terminal 101 registers with the network, terminal 101 may send fifth information to the first network device 1031. The fifth information may indicate at least one of the following: applying SCONE rate control to the data flow of the first service, or terminal 101's support for SCONE rate control.

[0198] In one example, during the process of establishing a PDU session between terminal 101 and fourth network device 1034, terminal 101 may send fifth information to first network device 1031. This fifth information may indicate at least one of the following: applying SCONE rate control to the data flow of the first service, or terminal 101's support for SCONE rate control. For example, the fifth information may include a SCONE rate control indication.

[0199] In some embodiments, the fifth information may be sent by the fourth network device 1034. In some embodiments, the fourth network device 1034 may send the fifth information to the first network device 1031. For example, the fifth information sent by the terminal 101 may reach the first network device 1031 via a network exposure function (NEF) and / or a third network device 1033. The fifth information may instruct the application of SCONE rate control to the data flow of the first service. For example, the fifth information may include a SCONE rate control indication.

[0200] In some embodiments, the fifth information may be sent by the third network device 1033. In some embodiments, the fifth information sent by the third network device 1033 to the first network device 1031 may instruct the application of SCONE rate control to the data flow of the first service. For example, the fifth information may include a SCONE rate control instruction. In some embodiments, the fifth information may be included in a second rule determined by the third network device 1033 for the data flow of the first service. For example, the second rule may include a policy and charging control (PCC) rule.

[0201] In one example, the third network device 1033 may determine the second rule based on at least one of the following: SCONE rate control indication and / or capability information from terminal 101, and / or SCONE rate control indication from fourth network device 1034, and the configuration of the third network device 1033.

[0202] In some embodiments, the configuration of the third network device 1033 may include at least one of the following: OAM configuration, carrier policy, and local configuration.

[0203] In some embodiments, the third network device 1033 may send fifth information to the first network device 1031 if it determines that SCONE rate control is authorized for the data stream of the first service.

[0204] It should be noted that the fifth piece of information can also be sent by other network devices, such as UPF, AMF, and UDM. This disclosure does not specifically limit this type of information.

[0205] In step S204, the first network device 1031 sends the sixth information to the second network device 1032.

[0206] In some embodiments, the first network device 1031 may send a sixth message. In some embodiments, the sixth message may be sent by the first network device 1031, but is not limited thereto, and may also be sent by other entities.

[0207] In some embodiments, the second network device 1032 may receive the sixth information. In some embodiments, the sixth information may be received by the second network device 1032, but is not limited thereto, and may also be received by other entities.

[0208] In some embodiments, the sixth information may be sent by the first network device 1031 upon receiving the fifth information.

[0209] In some embodiments, the sixth information may indicate that SCONE rate control is applied to the data stream of the first service. In some embodiments, the sixth information may include a SCONE rate control indication. The SCONE rate control indication applies SCONE rate control to the data stream of the first service.

[0210] In some embodiments, the SCONE rate control indication in the sixth message may be authorized.

[0211] In some embodiments, the sixth information may be sent to the second network device 1032 during the PDU session establishment process or the PDU session modification process.

[0212] In some embodiments, the sixth message may trigger the second network device 1032 to perform SCONE rate control. In some embodiments, upon receiving a SCONE rate control indication in the sixth message, the second network device 1032 may determine to perform SCONE rate control. In some embodiments, the second network device 1032 may perform functions related to SCONE rate control based on the sixth message.

[0213] In some embodiments, the functions related to SCONE rate control may include at least one of the following: identification of data streams subject to SCONE rate control, reporting of data streams subject to SCONE rate control, and marking of rate limits in SCONE packets.

[0214] In some embodiments, identification of a data stream subject to SCONE rate control may include detecting SCONE packets. In some embodiments, if SCONE packets are detected in a data stream, the data stream may be determined to be a data stream subject to SCONE rate control (or a SCONE data stream). Thus, identification of a data stream subject to SCONE rate control is achieved.

[0215] In some embodiments, reporting of data flows subject to SCONE rate control may include reporting detected SCONE data flows. In some embodiments, this reporting may be triggered by a first event. The first event may include a "SCONE flow detection" policy control request trigger. For example, the trigger may be used to trigger reporting of data flows subject to SCONE rate control. In one example, when a new data flow subject to SCONE rate control is detected, the first event may be triggered, and the second network device 1032 may perform reporting of the new data flow subject to SCONE rate control. For example, the second network device 1032 may report that a new data flow subject to SCONE rate control has been established. In some embodiments, the second network device 1032 may report to at least one of the first network device 1031 and the third network device 1033.

[0216] In some embodiments, the rate limit marker in a SCONE packet may refer to marking a rate limit in a SCONE packet. In some embodiments, the rate limit marker in a SCONE packet may include at least one of the following: detecting a rate limit in a SCONE packet; determining a rate limit in a SCONE packet; inserting a rate limit in a SCONE packet; or updating a rate limit in a SCONE packet.

[0217] In some embodiments, the operation of detecting rate limits in SCONE packets may include: detecting rate limits already carried in SCONE packets.

[0218] In some embodiments, determining the rate limit in a SCONE packet may include determining the value of the rate limit in the SCONE packet. In some embodiments, determining the rate limit in a SCONE packet may be implemented by determining the value of the rate limit in the SCONE packet based on at least one of the configuration of the second network device 1032 and the user plane QoS implementation for the SCONE data flow. For example, the value of the rate limit may indicate a throughput recommendation for the data flow.

[0219] In some embodiments, inserting a rate limit into a SCONE packet may include inserting the determined rate limit value into the SCONE packet. For example, inserting a rate limit into a SCONE packet that does not have a rate limit.

[0220] In some embodiments, updating the rate limit in a SCONE packet may include updating the value of the rate limit in the SCONE packet. For example, updating the rate limit in a SCONE packet that carries a rate limit.

[0221] In some embodiments, the functions related to SCONE rate control may have at least one of the following characteristics: detecting SCONE packets in traffic; updating SCONE rate limits on traffic; reporting the establishment of data streams subject to SCONE; and reporting data streams subject to SCONE rate control for updating data stream-related policies.

[0222] In some embodiments, rate limiting may be carried in the header of the SCONE packet.

[0223] In some embodiments, the functionality associated with SCONE rate control may be related to at least one of the following: the magnitude of rate control, the QoS characteristics of the data stream of the first service, and the granularity of rate control.

[0224] In some embodiments, the functionality related to SCONE rate control may be related to QoS features. In some embodiments, QoS features may include at least one of the following: dynamic QoS configuration and media type.

[0225] In some embodiments, the functionality associated with SCONE rate control may be related to the granularity of rate control. In some embodiments, the functionality associated with SCONE rate control may include the execution granularity of SCONE rate control. In some embodiments, the granularity of SCONE rate control may include at least one of the following: traffic, application session, PDU session, connection, and SDF.

[0226] In step S205, terminal 101 determines the demand related to SCONE traffic.

[0227] In some embodiments, terminal 101 can acquire requirements related to SCONE traffic. In some embodiments, the data stream of the first service may include SCONE traffic (or SCONE data stream). Terminal 101 can acquire requirements related to this SCONE traffic.

[0228] In some embodiments, terminal 101 may independently determine the requirements related to SCONE traffic. For example, terminal 101 may be the recipient of a data stream for a first service, and terminal 101 may determine the requirements related to SCONE traffic.

[0229] In some embodiments, terminal 101 can receive requests related to SCONE traffic. For example, terminal 101 may be the sender of a data stream for a first service, and fourth network device 1034 may be the receiver. In this case, terminal 101 can receive requests related to SCONE traffic provided by fourth network device 1034 through the application layer.

[0230] In some embodiments, requirements related to SCONE traffic may include at least one of the following: latency requirements, bit rate requirements, and priority. In some embodiments, priority may include at least one of the following: relative priority between SCONE traffic and non-SCONE traffic, and relative priority between different SCONE traffic types.

[0231] In some embodiments, requirements related to SCONE traffic may include throughput recommendations for SCONE rate control and / or packet processing targets. In some embodiments, packet processing targets may include at least one of the following: throughput, latency limits, and data volume.

[0232] In some embodiments, terminal 101 may obtain SCONE rate limits. In one example, the SCONE rate limit is used as a throughput suggestion. In some embodiments, terminal 101 may obtain SCONE rate limits for uplink data flows from at least one of the following: terminal 101, access network device 102, second network device 1032, and fourth network device 1034. In some embodiments, terminal 101 may obtain SCONE rate limits for downlink data flows from at least one of the following: terminal 101, access network device 102, second network device 1032, and fourth network device 1034.

[0233] In some embodiments, the SCONE traffic-related requirements obtained by terminal 101 may be related to at least one of the following: application, traffic pattern.

[0234] In step S206, terminal 101 performs routing processing and / or QoS processing.

[0235] In some embodiments, when terminal 101 has an uplink data stream of a first service to send, terminal 101 may perform routing processing and / or QoS processing on that data stream. In some embodiments, the routing processing and / or QoS processing performed by terminal 101 may be performed based on the first information obtained in step S202.

[0236] In some embodiments, terminal 101 can perform routing processing for the data flow of the first service based on the UE policy in the first rule. In some embodiments, terminal 101 can match the data flow of the first service with the UE policy to determine the URSP rule corresponding to the data flow. Then, terminal 101 can use the routing descriptor corresponding to the determined URSP rule to perform routing processing for the data flow. For example, terminal 101 can route the data flow to an existing session or establish a new session to carry the data flow based on the routing descriptor.

[0237] In some embodiments, terminal 101 may perform QoS processing on the data stream of the first service based on the QoS parameters in the first rule. For example, the QoS parameters in the first rule may be QoS parameters suggested by the third network device 1033. Terminal 101 may perform QoS processing on the data stream of the first service based on these QoS parameters.

[0238] It is understandable that when SCONE rate control is applied to the data flow of the first service, the routing and / or QoS processing of the data flow of the first service can be considered as the routing and / or QoS processing of the SCONE traffic.

[0239] In step S207, terminal 101 interacts with the fourth network device 1034.

[0240] In some embodiments, terminal 101 can interact with fourth network device 1034 to exchange data in the data stream of the first service.

[0241] In some embodiments, terminal 101 may send uplink data to fourth network device 1034. For example, the uplink data sent by terminal 101 passes through access network device 102 and second network device 1032 to reach fourth network device 1034.

[0242] In some embodiments, the fourth network device 1034 may send downlink data to the terminal 101. For example, the downlink data sent by the fourth network device 1034 may reach the terminal 101 via the second network device 1032 and the access network device 102.

[0243] In some embodiments, during the transmission of uplink data, terminal 101 may insert a SCONE rate limit into SCONE packets in the data stream of the first service. In some embodiments, the SCONE rate limit may be added to the header of the SCONE packets. In some embodiments, the data stream of the first service may include QUIC traffic, and SCONE packets may be included in the QUIC traffic. In some embodiments, the SCONE rate limit inserted by terminal 101 may be a default value.

[0244] In some embodiments, during the transmission of downlink data, the fourth network device 1034 may insert a SCONE rate limit into SCONE packets in the data stream of the first service. In some embodiments, the SCONE rate limit may be added to the header of the SCONE packets. In some embodiments, the data stream of the first service may include QUIC traffic, and SCONE packets may be included in the QUIC traffic. In some embodiments, the SCONE rate limit inserted by the fourth network device 1034 may be a default value. In some embodiments, the SCONE rate limit inserted by the fourth network device 1034 may be a value other than the default value.

[0245] In some embodiments, the second network device 1032 may perform SCONE rate control based on the sixth information. In some embodiments, the second network device 1032 may perform SCONE rate control on the data stream of the first service.

[0246] In some embodiments, the SCONE rate control performed by the second network device 1032 may include at least one of the following: identification of data flows subject to SCONE rate control, reporting of data flows subject to SCONE rate control, and marking rate limits in SCONE packets. In some embodiments, marking rate limits in SCONE packets may include at least one of the following: detecting rate limits in SCONE packets; determining rate limits in SCONE packets; inserting rate limits in SCONE packets; and updating rate limits in SCONE packets.

[0247] In some embodiments, the second network device 1032 may perform SCONE rate control by considering at least one of the following: SCONE rate limits detected from SCONE packets, network status, QoS authorization, dynamic QoS requirements, and received monitoring reports related to bit rate status.

[0248] In some embodiments, the second network device 1032 may send uplink data with inserted or updated SCONE rate limits to the fourth network device 1034. In some embodiments, the second network device 1032 may send downlink data with inserted or updated SCONE rate limits to the terminal 101.

[0249] In step S208, terminal 101 sends third information to first network device 1031.

[0250] In some embodiments, terminal 101 may send third information. In some embodiments, the third information may be sent by terminal 101, but is not limited thereto, and may also be sent by other entities.

[0251] In some embodiments, the first network device 1031 may receive third information. In some embodiments, the third information may be received by the first network device 1031, but is not limited thereto, and may also be received by other entities.

[0252] In some embodiments, if there are new or updated QoS requirements in the data stream of the first service corresponding to the application on terminal 101, terminal 101 may send third information. In some embodiments, the QoS requirements of the application corresponding to the first service may be dynamically changing, so terminal 101 may send third information whenever the QoS requirements change.

[0253] In some embodiments, the third information can be used to provide the QoS requirements of the data stream of the first service. In some embodiments, the third information can indicate the QoS requirements of the data stream of the first service.

[0254] In some embodiments, the third information may indicate at least one of the following: 5QI, GFBR, MFBR, window, throughput, latency limit, data volume, PDB, priority, packet filter set, QoS parameters of PDU set, and QoS parameter set of PDU set.

[0255] In some embodiments, the third information may include at least one of the following: QoS-related requirement information for the data flow of the first service, and requirement information related to SCONE traffic.

[0256] In some embodiments, QoS-related requirement information may indicate at least one of the following: 5QI, GFBR, MFBR, PDB, priority, packet filtering set, QoS parameters of PDU set, and QoS parameter set of PDU set.

[0257] In some embodiments, demand information related to SCONE traffic can indicate demand related to SCONE traffic. For example, demand information related to SCONE traffic can indicate at least a portion of the demand related to SCONE traffic obtained in step S203. For example, demand information related to SCONE traffic can indicate at least one of the following: SCONE rate limit, window, throughput, latency limit, data volume.

[0258] In some embodiments, throughput can refer to the maximum sustainable bit rate on a link. It is understood that throughput can also be referred to as link throughput. In some embodiments, throughput can be the bit rate required and authorized for QoS streams and / or data streams and / or connections. In one example, throughput is determined based on at least one of the following: QoS stream, data stream, and connection. For example, throughput can be the maximum sustainable bit rate for a QoS stream. For example, throughput can be the maximum sustainable bit rate for a data stream. For example, throughput can be the maximum sustainable bit rate for a connected stream.

[0259] In some embodiments, throughput can be obtained by measuring and monitoring the links over a period of time. Therefore, throughput can be the average throughput obtained over that period. In some embodiments, the size of this period can be predefined or determined based on the specific implementation.

[0260] In some embodiments, the delay limit and data volume can be defined for latency-critical business operations that have increased data volume during the window period. This window can be, for example, a finite time window.

[0261] In some embodiments, where latency constraints are sufficient, the throughput is less than or equal to the data volume.

[0262] In some embodiments, throughput increases when latency constraints are insufficient. It is understood that since latency constraints take precedence over data volume, increased throughput is necessary to complete the current data volume within a limited time when latency constraints are insufficient. Furthermore, the application can adjust to a lower bitrate to correspond to a smaller data volume, thereby ensuring that data transmission meets latency constraints. For example, if the data stream in the first service includes video data, throughput increases to ensure the current data volume is transmitted when latency constraints are insufficient. In some embodiments, the application corresponding to the first service can switch to a lower bitrate, thereby reducing the data volume (e.g., the data volume of a video segment).

[0263] In some embodiments, third information may be sent during the PDU session modification process. In some embodiments, terminal 101 may send a PDU session modification request message to first network device 1031, which includes the third information.

[0264] In step S209, terminal 101 sends third information and / or fourth information to second network device 1032.

[0265] In some embodiments, terminal 101 may insert third and / or fourth information into the data packets of uplink data within the data stream of the first service.

[0266] In some embodiments, the fourth information may be related to the data stream of the first service.

[0267] In some embodiments, the fourth information may include rate limits in the data stream of the first service. In some embodiments, the first network device 1031 may obtain the SCONE rate limit carried in the SCONE data packet. For example, for uplink data, the SCONE rate limit may be added by the terminal 101.

[0268] In some embodiments, the fourth information may also include other information, such as the transmission status of the data stream of the first service, the network status, etc., which are not specifically limited in this disclosure.

[0269] In some embodiments, during the transmission of uplink data, terminal 101 may insert a SCONE rate limit into SCONE packets in the data stream of the first service. In some embodiments, the SCONE rate limit may be added to the header of the SCONE packets. In some embodiments, the data stream of the first service may include QUIC traffic, and SCONE packets may be included in the QUIC traffic. In some embodiments, the SCONE rate limit inserted by terminal 101 may be a default value.

[0270] In some embodiments, during the transmission of downlink data, the fourth network device 1034 may insert a SCONE rate limit into SCONE packets in the data stream of the first service. In some embodiments, the SCONE rate limit may be added to the header of the SCONE packets. In some embodiments, the data stream of the first service may include QUIC traffic, and SCONE packets may be included in the QUIC traffic. In some embodiments, the SCONE rate limit inserted by the fourth network device 1034 may be a default value. In some embodiments, the SCONE rate limit inserted by the fourth network device 1034 may be a value other than the default value.

[0271] In some embodiments, the first network device 1031 may perform SCONE rate control based on the sixth information. In some embodiments, the first network device 1031 may perform SCONE rate control on the data stream of the first service.

[0272] In some embodiments, the SCONE rate control performed by the first network device 1031 may include at least one of the following: identifying data flows subject to SCONE rate control, reporting data flows subject to SCONE rate control, and marking rate limits in SCONE packets. In some embodiments, marking rate limits in SCONE packets may include at least one of the following: detecting rate limits in SCONE packets; determining rate limits in SCONE packets; inserting rate limits in SCONE packets; and updating rate limits in SCONE packets.

[0273] In some embodiments, the execution of SCONE rate control by the first network device 1031 may consider at least one of the following: SCONE rate limits detected from SCONE packets, network status, QoS authorization, dynamic QoS requirements, and received monitoring reports related to bit rate status.

[0274] In some embodiments, the first network device 1031 may send uplink data with inserted or updated SCONE rate limits to the fourth network device 1034. In some embodiments, the first network device 1031 may send downlink data with inserted or updated SCONE rate limits to the terminal 101.

[0275] In some embodiments, during the transmission of uplink data, terminal 101 may insert third information into the data packets of the first service's data stream. In some embodiments, the third information may be added by terminal 101 to the header of the data packets.

[0276] In some embodiments, the third information may be sent when there are new or updated QoS requirements in the data stream of the first service corresponding to the application on terminal 101. In some embodiments, the QoS requirements of the application corresponding to the first service may change dynamically, so terminal 101 may send the third information whenever the QoS requirements change.

[0277] In some embodiments, at least one of the third and fourth information may be carried in the header of the data packet of the first service.

[0278] In some embodiments, the header may include at least one of the following: a SCONE packet header, UDP options, and a GTPU packet header. For example, third and / or fourth information may be carried in the SCONE packet header. For example, first and / or second information may be carried in the UDP options header. For example, third and / or fourth information may be carried in the GTPU packet header.

[0279] It is understandable that the third and fourth information can be carried in the header of the same data packet or in the header of different data packets. Furthermore, the third and fourth information can be carried in headers of the same type or in headers of different types.

[0280] It should be noted that the packet header carrying the third and / or fourth information can also be other types of packet headers, and this disclosure does not specifically limit this.

[0281] In some embodiments, upon receiving uplink data from terminal 101, the first network device 1031 can detect SCONE packets in the uplink data. For example, the first network device 1031 can identify SCONE packets. For example, if the SCONE packet carries a SCONE rate limit inserted by terminal 101, the first network device 1031 can update or maintain the SCONE rate limit. For example, if the SCONE packet does not contain a SCONE rate limit, the first network device 1031 can insert or not insert the SCONE rate limit. Afterwards, the first network device 1031 can send downlink data to the fourth network device 1034.

[0282] In some embodiments, upon receiving uplink data from the fourth network device 1034, the first network device 1031 can detect SCONE packets in the downlink data. For example, the first network device 1031 can identify SCONE packets. For example, if the SCONE packet carries a SCONE rate limit inserted by the fourth network device 1034, the first network device 1031 can update or maintain the SCONE rate limit. For example, if the SCONE packet does not contain a SCONE rate limit, the first network device 1031 can insert or not insert the SCONE rate limit. Afterwards, the first network device 1031 can send the downlink data to the terminal 101 via the access network device 102.

[0283] It should be noted that terminal 101 may send third information to either the first network device 1031 or the second network device 1032. For example, if terminal 101 sends third information to the first network device 1031, it may not need to send third information to the second network device 1032. Similarly, if terminal 101 sends third information to the second network device 1032, it may not need to send third information to the first network device 1031.

[0284] In step S210, the second network device 1032 sends third and / or fourth information to the first network device 1031.

[0285] In some embodiments, the second network device 1032 may send third and / or fourth information. In some embodiments, the third and / or fourth information may be sent by the second network device 1032, but is not limited thereto, and may also be sent by other entities.

[0286] In some embodiments, the first network device 1031 may receive third information and / or fourth information. In some embodiments, the third information and / or fourth information may be received by the first network device 1031, but is not limited thereto, and may also be received by other entities.

[0287] In step S211, the first network device 1031 acquires QoS-related parameters.

[0288] In some embodiments, upon obtaining third and / or fourth information, the first network device 1031 can determine whether QoS-related parameters need to be updated. For example, the first network device 1031 can determine, based on the third and / or fourth information, to update the QoS-related parameters of the data stream of the first service. In some embodiments, if it is determined that QoS-related parameters need to be updated, the first network device 1031 can obtain the QoS-related parameters.

[0289] In some embodiments, the first network device 1031 may not need to determine whether QoS-related parameters need to be updated. For example, if third information and / or fourth information are obtained, the first network device 1031 may directly obtain the QoS-related parameters.

[0290] In some embodiments, the third and / or fourth information can be used to determine the QoS parameters for the data flow of the first service. The first network device 1031 can obtain QoS-related parameters based on the third and / or fourth information. In some embodiments, the QoS-related parameters can be updated QoS-related parameters. For example, the QoS-related parameters can be updated based on the third and / or fourth information.

[0291] In some embodiments, step S211 may include: the first network device 1031 sending third information and / or fourth information to the third network device 1033; and the third network device 1033 sending seventh information to the first network device 1031.

[0292] In some embodiments, the first network device 1031 sends third information and / or fourth information to the third network device 1033. The third network device 1033 updates the second rule based on the received first and / or second information. The second rule may be a QoS-related parameter determined by the third network device 1033. For example, the second rule may include a PCC rule. Subsequently, the third network device 1033 may send seventh information to the first network device 1031 to indicate QoS-related parameters, such as the second rule.

[0293] In some embodiments, upon receiving seventh information from third network device 1033, first network device 1031 may determine QoS-related parameters based on the seventh information. First network device 1031 may determine at least one of the following based on the second rule in the seventh information: a third rule, a fourth rule, or a fifth rule.

[0294] In some embodiments, the seventh information may also include a SCONE rate control indication.

[0295] In some embodiments, step S211 may include: the first network device 1031 determining QoS-related parameters.

[0296] In some embodiments, the first network device 1031 may determine QoS-related parameters based on the acquired third and / or fourth information. In some embodiments, the QoS-related parameters determined by the first network device 1031 may include at least one of the following: a third rule, a fourth rule, and a fifth rule.

[0297] In some embodiments, the third rule can be used by the second network device 1032 to perform QoS processing on the data flow of the first service. For example, the third rule may include the N4 rule.

[0298] In some embodiments, the fourth rule can be used by the access network device 102 to perform QoS processing on the data flow of the first service. For example, the fourth rule may include a QoS profile.

[0299] In some embodiments, the fifth rule can be used by terminal 101 to perform QoS processing on the data stream of the first service. For example, the fifth rule may include QoS rules.

[0300] In some embodiments, the operation of the first network device 1031 in determining QoS-related parameters based on third information and / or fourth information may consider at least one of the following: the configuration of the first network device 1031, or the second rule stored in the first network device 1031.

[0301] In step S212, the first network device 1031 sends the eighth message.

[0302] In some embodiments, the first network device 1031 may send an eighth message. In some embodiments, the eighth message may be sent by the first network device 1031, but is not limited thereto, and may also be sent by other entities.

[0303] In some embodiments, step S212 may include: the first network device 1031 sending an eighth message to the second network device 1032. The eighth message indicates a third rule.

[0304] In some embodiments, step S212 may include: the first network device 1031 sending an eighth message to the access network device 102. The eighth message indicates a fourth rule.

[0305] In some embodiments, step S212 may include: the first network device 1031 sending an eighth message to the terminal 101. The eighth message indicates the fifth rule.

[0306] In some embodiments, the eighth information may also include a SCONE rate control indication.

[0307] In step S213, terminal 101 exchanges data with the fourth network device 1034.

[0308] In some embodiments, terminal 101 can interact with fourth network device 1034 to exchange data in the data stream of the first service.

[0309] In some embodiments, terminal 101 may send uplink data to fourth network device 1034. For example, the uplink data sent by terminal 101 passes through access network device 102 and second network device 1032 to reach fourth network device 1034.

[0310] In some embodiments, the fourth network device 1034 may send downlink data to the terminal 101. For example, the downlink data sent by the fourth network device 1034 may reach the terminal 101 via the second network device 1032 and the access network device 102.

[0311] In some embodiments, the second network device 1032 may perform QoS processing on the data stream of the first service based on the eighth information.

[0312] In some embodiments, the access network device 102 may perform QoS processing on the data stream of the first service based on the eighth information.

[0313] In some embodiments, terminal 101 may perform QoS processing on the data stream of the first service based on the eighth information.

[0314] In some embodiments, the second network device 1032 may perform SCONE rate control based on the eighth information. In some embodiments, the second network device 1032 may perform SCONE rate control on the data stream of the first service.

[0315] The communication method of this embodiment can be implemented through steps S201 to S213.

[0316] It should be noted that the solutions in this disclosure are applicable to QUIC traffic. Although SCONE traffic is used as an example for illustration, the methods in this disclosure are also applicable to other types of QUIC traffic, and this disclosure does not specifically limit them.

[0317] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0318] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0319] In some embodiments, the terms “radio”, “wireless”, “radioaccess network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0320] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0321] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0322] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0323] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0324] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0325] In some embodiments, the terms "packet", "message", "packet data unit (PDU)" and "packet data packet" can be used interchangeably.

[0326] In some embodiments, the terms "QoS processing", "QoS implementation", "QoS control", and "QoS operation" can be used interchangeably.

[0327] In some embodiments, the terms “stream,” “data stream,” “flow,” and “flow component” can be used interchangeably.

[0328] In some embodiments, the terms “rate limit”, “rate control”, “SCONE rate limit”, “SCONE rate limit marker”, “SCONE rate limit control”, and “SCONE rate control” can be used interchangeably.

[0329] In some embodiments, terms such as “throughput recommendation,” “rate limit,” and “rate signal” can be used interchangeably.

[0330] In some embodiments, the terms "SCONE rate control indication", "SCONE indication", and "rate control indication" can be used interchangeably.

[0331] In some embodiments, the terms "configuration file", "configuration", and "configuration information" can be used interchangeably.

[0332] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0333] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0334] In some embodiments, if the arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects. For example, steps S202, S205, S207, S208, S209, S210, and S213.

[0335] The communication method involved in the embodiments of this disclosure may include at least one of steps S201 to S213. For example, step S202 may be implemented as a standalone embodiment, but is not limited thereto.

[0336] In some embodiments, steps S202 and S203 may be performed in a different order or simultaneously, steps S205 and S206 may be performed in a different order or simultaneously, and steps S208 and S210 may be performed in a different order or simultaneously.

[0337] In some embodiments, steps S201, S203, S204, S205, S206, S207, S208, S209, S210, S211, S212, and S213 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0338] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0339] Figure 3 This is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. Embodiments of this disclosure relate to communication methods. For example... Figure 3 As shown, the above method includes step S301.

[0340] In step S301, the network device sends the first information to the terminal.

[0341] For optional implementations of step S301, please refer to [link / reference]. Figure 2 Optional implementations of step S202, and Figure 2 Other related parts in the embodiments involved will not be described in detail here.

[0342] In some embodiments, the network device may include a third network device 1033. It is understood that the network device may also be other network devices, and this disclosure does not specifically limit the specific network device.

[0343] In some embodiments, the first information indicates a first rule. The first rule is used by the terminal to route QUIC traffic.

[0344] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0345] In the following, specific embodiments of the present disclosure will be described by way of example.

[0346] In some embodiments, this disclosure proposes that the UE applies QoS according to network provision (e.g., UE policy enhancement) and provides the network with detected traffic and QoS processing for further QoS updates and PCC rule modifications.

[0347] In some embodiments, the UE obtains UE policies along with QoS handling guidance, which are either pre-configured or configured by the network during registration, including QUIC (e.g., SCONE) traffic descriptors and QoS information (e.g., traffic descriptors associated with SCONE traffic, and recommended QoS parameters for SCONE traffic / video streaming / immersive traffic / AI traffic).

[0348] In some embodiments, the traffic descriptor defines a traffic descriptor component for URSP rules. The traffic descriptor component can be enhanced to provide the UE with, for example, IP descriptors, and / or domain descriptors, and / or connectivity capabilities for QUIC (e.g., SCONE) traffic detection and routing, and can provide a full description of the detected SDF using packet filters with information such as traffic characteristics, tuples, QUIC connection IDs, etc.

[0349] In some embodiments, the routing component in the routing descriptor may be enhanced to include a QoS parameter component that carries QoS parameters to be applied to QUIC (e.g., SCONE) traffic that matches the traffic descriptor of the URSP.

[0350] In some embodiments, a new component, the QoS parameter component, is added to the routing descriptor for use in routing (e.g., SCONE traffic) to indicate the QoS parameters of QUIC (e.g., SCONE) traffic that matches the traffic descriptor.

[0351] In some embodiments, QUIC (e.g., SCONE) traffic groups / connections are included as a new component in the routing descriptor, indicating that traffic matching SCONE traffic groups / connections is delivered by a combined QoS or PDU session (uplink, downlink, or uplink and downlink).

[0352] In some embodiments, a QoS parameter configuration policy is introduced to provide a list of QoS parameters and dynamic QoS profiles for matching and routing QUIC (e.g., SCONE) traffic. This is determined and provided after UE registration, taking into account subscription, service requirements, and operator policies (e.g., pre-configured).

[0353] In some embodiments, the UE detects SCONE traffic according to traffic detection rules (determines the service type of the traffic), matches the traffic with the aforementioned UE policy rules and QoS parameters, and applies QoS enforcement while taking into account the provided UE policy and QoS information and / or the UE's pre-configuration.

[0354] In some embodiments, the UE sends SCONE SDF descriptions (e.g., packet filters), uplink SCONE rate limiting suggestions, and QoS parameters to the UPF in different ways, such as through user face in-band packet headers or SCONE packet headers.

[0355] In some embodiments, the 6GC (e.g., UPF) implements QoS taking into account UE inputs (e.g., throughput recommendations, packet processing targets) for uplink and / or downlink traffic, which is implemented after QoS authorization or update.

[0356] In some embodiments, the UE provides traffic information and QoS parameters to the network, such as encapsulation headers for uplink data traffic and session modifications. In some embodiments, the 6GC implements QoS taking into account UE inputs for downlink traffic (e.g., throughput recommendations, packet processing targets) if relevant PCC rules are updated with UE inputs in mind (e.g., UPF reports to the PCF for QoS updates).

[0357] In some embodiments, the QoS information provided to the UE and provided by the UE includes a set of QoS flow level parameters, such as 5QI, uplink GFBR, downlink GFBR, uplink MFBR, downlink MFBR, average window, link throughput, delay limit, data volume, PDB, priority, packet filter set, PDU set QoS parameters, and optional QoS parameter set, which are included in the PDU session modification request or in the path of packets with extended headers of SCONE packets or other protocols (e.g., UDP options) to be sent to the 6G network for QoS determination and updates.

[0358] In some embodiments, link throughput, latency limits, and data volume for dynamic QoS request applications can be used as:

[0359] Link throughput is defined as the bit rate relative to stream / flow / connection demand and authorization. This link throughput can be measured and monitored over the link as an average throughput (the time period depends on the implementation).

[0360] - Latency limits and data volume are defined for latency-critical business operations that require increased data volume within a limited time window. In one example, if the latency limit is sufficient, the throughput will not exceed the data volume; otherwise, since the latency limit takes precedence over the data volume, the increased data volume will be transferred.

[0361] In some embodiments, as a QUIC receiver / sender, enhanced QoS signaling is initiated to provide sufficient QoS information from the UE to the 6G SM (session management, SM) function for QoS modification, taking into account effective rate limiters from communication (i.e., network rate limiters) to communicate directly with video applications at bitrate (throughput recommendation, the network's maximum bitrate in the same / opposite / both directions), including SCONE rate limiting.

[0362] In some embodiments, a UE with SCONE rate limiting support capability initiates enhanced QoS signaling to provide sufficient QoS information from the UE to the 6G SM function, taking into account the received “SCONE rate limiting”, such as uplink SCONE rate limiting obtained from the UE / RAN / access UPF / insertion UPF / PSAUPF, uplink / downlink SCONE rate limiting obtained from the UPF / network (e.g., packet (PDU) processing target).

[0363] In some embodiments, the SCONE rate limiting indication may be provided by the AF / application function located in the UE (which may be authorized by the PCF and provided by the SMF to the NG-RAN / Access UPF / Insertion UPF / PSA UPF for marking implementation).

[0364] In some embodiments, the SCONE rate limiting indication can indicate the characteristics and implementation of traffic for the identification and marking of rate limiting information (e.g., maximum bit rate) in the SCONE header of uplink and / or downlink packets of the PDU (e.g., to enable coordination of maximum bit rates between the UE, network, and application, and to trigger the application to update its application QoS requirements, or to trigger network QoS authorization updates for the same or opposite or both directions).

[0365] In some embodiments, the sender marks the SCONE packet rate limit as 127 as the default value to indicate that rate limiting is enabled; and authorized network functions can update and insert the determined value as a throughput recommendation. In some embodiments, if the application and the application located in the UE are enhanced to provide a true rate limit in the direction pointing to the receiver, the sender can enhance to insert a related value different from 127.

[0366] In some embodiments, for SCONE rate limiting enabled, only one or more network functions may be authorized for inserting and / or updating the SCONE rate limit. These network functions may insert / update / maintain the value, taking into account identified recommendations, network status, authorized QoS, dynamic QoS requirements, and received monitoring reports related to bit rate status as input.

[0367] In some embodiments, for SCONE rate limiting enabled, the SCONE rate limiting instruction for traffic authorization is negotiated for each SDF or UE per PDU session during the PDU session establishment or modification process.

[0368] In some embodiments, for SCONE rate limiting enabled, the UE can send SCONE rate limiting capability during the UE registration process to obtain authorization from the network.

[0369] In some embodiments, for SCONE rate limiting enablement for network functions (e.g., NG-RAN / Access UPF / Insertion UPF / PSAUPF, authorized for SCONE packet detection and rate limiting insertion or update), the SCONE rate limiting indication is provided during session establishment or modification to activate or deactivate the implementation of SCONE rate limiting.

[0370] Figure 4 This is an interactive schematic diagram of an exemplary implementation of the communication method provided according to embodiments of this disclosure. This implementation relates to UE QoS flow detection and control based on UE policies for QUIC traffic. Figure 4 As shown, the method includes steps S401 to S405.

[0371] In some embodiments, this process is applied when the UE is acting as a QUIC receiver / sender. The UE applies QoS according to network configuration (UE policy enforcement) and provides the network with detected traffic and QoS processing for further QoS updates and PCC rule modifications. In some embodiments, the UE obtains UE policy along with QoS processing guidance, which is either pre-configured or configured by the network during registration, including QUIC (e.g., SCONE) traffic descriptors and QoS information (e.g., traffic descriptors associated with SCONE traffic, and recommended QoS parameters for SCONE traffic / video streaming / immersive traffic / AI traffic).

[0372] In step S401, the UE registers with the 6GS, indicating its ability to support UE policies based on QoS configuration and negotiation. A UE policy association is established with the PCF.

[0373] In some embodiments, the UE obtains UE policies along with QoS processing guidance, which are pre-configured or configured by the network during registration, including QUIC (e.g., SCONE) traffic descriptors and QoS information (e.g., traffic descriptors associated with SCONE traffic, and recommended QoS parameters for SCONE traffic / video streaming / immersive traffic / AI traffic).

[0374] In some embodiments, for SCONE rate limiting enabled, the UE can send SCONE rate limiting capability during the UE registration process to obtain authorization from the network.

[0375] In some embodiments, the SCONE rate limiting indication may be provided by the AF / application function located in the UE (which may be authorized by the PCF and provided by the SMF to the NG-RAN / Access UPF / Insertion UPF / PSA UPF for marking implementation). In some embodiments, the SCONE rate limiting indication may indicate characteristic indications and implementations for traffic, used to identify and mark rate limiting information (e.g., maximum bit rate) in the SCONE header of uplink and / or downlink packets of the PDU (e.g., to enable coordination of maximum bit rate between the UE, network, and application, and to trigger the application to update application QoS requirements, or may trigger network QoS authorization updates for the same or opposite or both directions).

[0376] In step S402, the PCF provides (or pre-configures) enhanced UE policies and QoS information to the UE (e.g., traffic descriptors related to SCONE traffic, and recommended QoS parameters for SCONE traffic / video streaming / immersive traffic / AI traffic).

[0377] In some embodiments, the traffic descriptor defines a traffic descriptor composition for URSP rules. The traffic descriptor composition can be enhanced to provide the UE with, for example, IP descriptors, and / or domain descriptors, and / or connectivity capabilities for QUIC (e.g., SCONE) traffic detection and routing, and can provide a full description of the detected SDF using packet filters with information such as traffic characteristics, tuples, QUIC connection IDs, etc.

[0378] In some embodiments, the routing component in the routing descriptor may be enhanced to include a QoS parameter component that carries QoS parameters to be applied to QUIC (e.g., SCONE) traffic that matches the traffic descriptor of the URSP.

[0379] In some embodiments, a new component, the QoS parameter component, is added to the routing descriptor for use in routing (e.g., SCONE traffic) to indicate the QoS parameters of QUIC (e.g., SCONE) traffic that matches the traffic descriptor.

[0380] In some embodiments, QUIC (e.g., SCONE) traffic groups / connections are included as a new component in the routing descriptor, indicating that traffic matching SCONE traffic groups / connections is delivered by a combined QoS or PDU session (uplink, downlink, or uplink and downlink).

[0381] In some embodiments, a QoS parameter configuration policy is introduced to provide a list of QoS parameters and dynamic QoS profiles for matching and routing QUIC (e.g., SCONE) traffic. This is determined and provided after UE registration, taking into account subscription, service requirements, and operator policies (e.g., pre-configured).

[0382] In step S403, when the application starts and begins generating traffic (e.g., new SCONE traffic), a PDU session exists or a new PDU session is established when URSP rules are enforced. The UE obtains the corresponding traffic and QoS information, such as traffic descriptors related to the detected SCONE traffic.

[0383] In some embodiments, the UE detects SCONE traffic according to traffic detection rules (determines the service type of the traffic), matches the traffic with the aforementioned UE policy rules and QoS parameters, and applies QoS enforcement taking into account the provided UE policies and QoS information, and / or the UE's pre-configuration.

[0384] In some embodiments, SCONE rate limits from applications can be obtained by the receiver based on network reporting / exposure and forwarded to the receiver.

[0385] In some embodiments, SCONE packets may be marked with a rate limit of 127 as the default value to indicate that rate limiting is enabled; and authorized network functions may update and insert the determined value as a throughput recommendation. In some embodiments, if the application and the application located in the UE are enhanced to provide a true rate limit in the direction pointing to the receiver, the sender may enhance to insert a related value different from 127.

[0386] In some embodiments, for SCONE rate limiting enabled, only one or more network functions may be authorized for inserting and / or updating the SCONE rate limit. These network functions may insert / update / maintain the value, taking into account identified recommendations, network status, authorized QoS, dynamic QoS requirements, and received monitoring reports related to bit rate status as input.

[0387] In some embodiments, the UE inserts throughput into SCONE packets and sends UL QUIC traffic to the 6G RAN and UPF. The 6G RAN / Access UPF / Insertion UPF / PSA UPF receives, identifies, and updates the rate limit before forwarding, if an authorized SCONE traffic rate limit flag is present.

[0388] In step S404, taking into account the UE policy and QoS parameters provided in step S402, and / or the pre-configuration in the UE, the UE applies QoS enforcement.

[0389] In some embodiments, the UE sends SCONE SDF descriptions (e.g., packet filters), uplink SCONE rate limiting suggestions, and QoS parameters to the UPF in different ways, such as through user face in-band packet headers or SCONE packet headers.

[0390] In some embodiments, the 6GC (e.g., UPF) implements QoS taking into account UE inputs (e.g., throughput recommendations, packet processing targets) for uplink and / or downlink traffic, which is implemented after QoS authorization or update.

[0391] In some embodiments, the QoS information provided to the UE and provided by the UE includes a set of QoS flow level parameters, such as 5QI, uplink GFBR, downlink GFBR, uplink MFBR, downlink MFBR, average window, link throughput, latency limit, data volume, PDB, priority, packet filter set, PDU set QoS parameters, and optional QoS parameter set, which are included in the PDU session modification request or in the path of packets via extended headers of SCONE packets or other protocols (e.g., UDP options) to be sent to the 6G network for QoS determination and updates.

[0392] In some embodiments, link throughput, latency limits, and data volume for dynamic QoS request applications can be used as:

[0393] Link throughput is defined as the bit rate relative to stream / flow / connection demand and authorization. This link throughput can be measured and monitored over the link as an average throughput (the time period depends on the implementation).

[0394] - Latency limits and data volume are defined for latency-critical business operations that require increased data volume within a limited time window. In one example, if the latency limit is sufficient, the throughput will not exceed the data volume; otherwise, since the latency limit takes precedence over the data volume, the increased data volume will be shifted.

[0395] In some embodiments, for SCONE rate limiting enabled, the SCONE rate limiting instruction for traffic authorization is negotiated for each SDF or UE per PDU session during the PDU session establishment or modification process.

[0396] In some embodiments, for SCONE rate limiting enablement for network functions (e.g., NG-RAN / Access UPF / Insertion UPF / PSAUPF, authorized for SCONE packet detection and rate limiting insertion or update), the SCONE rate limiting indication is provided during session establishment or modification to activate or deactivate the implementation of SCONE rate limiting.

[0397] In step S405, in some embodiments, the UE provides traffic information and QoS parameters to the network, such as encapsulation headers for uplink data traffic and session modifications. In some embodiments, the 6GC implements QoS taking into account UE inputs for downlink traffic (e.g., throughput recommendations, packet processing targets) if relevant PCC rules are updated taking into account UE inputs (e.g., UPF reports to the PCF for QoS updates).

[0398] In some embodiments, the UPF obtains the inserted SCONE rate limit and QoS information from the packet header. In some embodiments, this information is reported to the PCF for QoS updates (e.g., triggering session modification) and traffic is forwarded to the data network. In some embodiments, if downlink traffic is received, the UPF forwards it to the UE, and may add an encapsulation header to provide downlink traffic information, such as throughput recommendations.

[0399] In some embodiments, taking into account the QoS requirements input by the UE and the UPF reporting, the 6G SM function authorizes and / or adjusts QoS (new QoS rules, QoS configurations, and parameters) as needed (this may include checking local configurations and PCC rules, or interacting with the 6GPCF). In some embodiments, the 6G SMF function sends updated QoS parameters for the QoS flow to the UE and / or RAN and / or UPF.

[0400] In some embodiments, the UE inserts throughput recommendations into the SCONE data packet and sends uplink QUIC traffic to the 6G RAN and UPF. The 6G RAN / Access UPF / PSA UPF receives, identifies, and can update the rate limits before forwarding.

[0401] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0402] In some embodiments, this disclosure proposes a UE as a QUIC receiver / sender. The UE applies QoS according to network configuration (e.g., UE policy enhancement) and provides the network with detected traffic and QoS processing for further QoS updates and PCC rule modifications. This enables rapid changes in media streams for efficient and effective QoS services in 6G, supports QoS negotiation between the UE, network, and applications, and is beneficial for efficiently meeting QoS objectives and user experience.

[0403] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network device, etc.) in any of the above methods.

[0404] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0405] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit, microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc.

[0406] Figure 5 This is a schematic diagram of the structure of a communication device provided according to an embodiment of this disclosure. For example... Figure 5 As shown, the communication device 500 may include at least one of the following: a transceiver module 501 and a processing module 502.

[0407] In some embodiments, the communication device 500 can be a terminal. In some embodiments, the transceiver module 501 can be configured to: acquire first information, wherein the first information indicates a first rule, and the first rule is used by the terminal to perform routing processing on QUIC traffic. Optionally, the transceiver module 501 can be used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods (e.g., steps S201, S202, S203, S207, S208, S209, S212, S213, but not limited thereto), which will not be elaborated here. Optionally, the processing module 502 is used to perform at least one of the other steps performed by the terminal in any of the above methods (e.g., steps S205, S206, but not limited thereto), which will not be elaborated here.

[0408] In some embodiments, the communication device 500 may be a network device. In some embodiments, the transceiver module 501 may be configured to send first information to the terminal, wherein the first information indicates a first rule, and the first rule is used by the terminal to perform routing processing on QUIC traffic. Optionally, the transceiver module 501 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods (e.g., steps S201, S202, S211, but not limited thereto), which will not be elaborated here.

[0409] In some embodiments, Figure 5 The communication device shown can also be implemented as a communication equipment.

[0410] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting and receiving modules may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0411] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0412] Figure 6A This is a schematic diagram of the structure of a communication device provided according to an embodiment of this disclosure. The communication device 6100 can be a terminal (e.g., a user equipment), a network device (e.g., a core network device, an access network device), a chip, chip system, or processor that supports the terminal in implementing any of the above methods, or a chip, chip system, or processor that supports the network device in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0413] like Figure 6A As shown, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 can be used to execute any of the above methods. Optionally, one or more processors 6101 can be used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0414] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceivers 6102 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S201, S202, S203, S204, S207, S208, S209, S210, S211, S212, S213, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S205, S206, S211, but not limited thereto). In optional embodiments, the transceivers may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be used interchangeably; and terms such as receiver, receiving unit, receiver, and receiving circuit can be used interchangeably.

[0415] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memories 6103 may be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6103 and can be used to receive data from the memories 6103 or other devices, and to send data to the memories 6103 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6103 and send that data to the processor 6101.

[0416] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may vary. Figure 6A The limitations. Communication equipment can be a standalone device or part of a larger device. For example, communication equipment can be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0417] Figure 6BThis is a schematic diagram of the chip structure provided according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to... Figure 6B The diagram shown is a schematic representation of the structure of chip 6200, but it is not limited to this.

[0418] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0419] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of the memories 6203 may be located outside chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.

[0420] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S201, S202, S203, S204, S207, S208, S209, S210, S211, S212, S213, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S205, S206, S211, but not limited thereto).

[0421] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0422] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 6100, cause the communication device 6100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0423] This disclosure also provides a program product that, when executed by a communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0424] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, executed by a terminal, wherein, The method includes: Obtain first information, wherein the first information indicates a first rule, the first rule being used by the terminal to route QUIC traffic for Fast UDP Internet Connection.

2. The method according to claim 1, wherein, The QUIC traffic includes network element standard communication SCONE data packets.

3. The method according to claim 1 or 2, wherein, The first rule includes at least one of the following: First indication information, the first indication information indicating QoS parameters applied to SCONE traffic; The second indication information indicates that traffic in a SCONE traffic group or connection is delivered based on federated QoS or session.

4. The method according to claim 3, wherein, Traffic in a SCONE traffic group or connection includes at least one of the following: Uplink traffic; Downlink traffic.

5. The method according to any one of claims 1 to 4, wherein, The first rule includes a User Equipment (UE) Routing Policy (URSP) rule, and the first indication information and / or the second indication information are contained in the traffic descriptor of the URSP rule.

6. The method according to any one of claims 1 to 5, wherein, The first rule includes a routing descriptor, and the first indication information and / or the second indication information are contained in the routing descriptor.

7. The method according to any one of claims 1 to 6, wherein, The acquisition of the first information includes at least one of the following: Obtain the pre-configured first information; Receive the first information sent by the network function.

8. The method according to any one of claims 1 to 7, wherein, The first information is obtained during or after the registration process of the terminal.

9. The method according to any one of claims 1 to 8, wherein, The method further includes: Based on the first information, perform routing and / or QoS processing on the QUIC traffic.

10. A communication method, performed by a network device, wherein, The method includes: Send first information to the terminal, wherein the first information indicates a first rule, the first rule being used by the terminal to route QUIC traffic for Fast UDP Internet Connection.

11. The method according to claim 10, wherein, The QUIC traffic includes network element standard communication SCONE data packets.

12. The method according to claim 10 or 11, wherein, The first rule includes at least one of the following: First indication information, the first indication information indicating QoS parameters applied to SCONE traffic; The second indication information indicates that traffic in a SCONE traffic group or connection is delivered based on federated QoS or session.

13. The method according to claim 12, wherein, Traffic in a SCONE traffic group or connection includes at least one of the following: Uplink traffic; Downlink traffic.

14. The method according to any one of claims 10 to 13, wherein, The first rule includes a User Equipment (UE) Routing Policy (URSP) rule, and the first indication information and / or the second indication information are contained in the traffic descriptor of the URSP rule.

15. The method according to any one of claims 10 to 14, wherein, The first rule includes a routing descriptor, and the first indication information and / or the second indication information are contained in the routing descriptor.

16. The method according to any one of claims 10 to 15, wherein, The first information is sent during or after the registration process of the terminal.

17. A communication device, wherein, The communication device is used to perform the communication method as described in any one of claims 1-16.

18. A communication system, wherein, The communication system includes at least one of network equipment and a terminal; The terminal is configured to implement the communication method as described in any one of claims 1-9, and the network device is configured to implement the communication method as described in any one of claims 10-16.

19. A storage medium storing instructions, wherein, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-16.

20. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by the communication device, it implements the communication method as described in any one of claims 1-16.

Images