Dynamic traffic characteristic variation in user plane

Abstract

The invention relates to dynamic traffic characteristic variation in user plane. An apparatus is disclosed. The apparatus includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: send information to a user plane function, the information indicating: at least one change in at least one traffic characteristic associated with a service data stream; wherein the at least one traffic characteristic comprises at least one of the following: a periodicity that is a time period between the start of two data bursts of the service data stream; a maximum data burst size of a data burst of the service data stream; a forward error correction rate associated with successful decoding of each data burst of the service data stream; or transmitting the duration of the data burst of the service data stream.

Description

Technical Field

[0001] The various example embodiments disclosed herein relate to a method, apparatus, system, and computer program, and specifically, but not limited to, a method, apparatus, and system for supporting dynamic changes in service characteristics in the user plane. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices may be served by application servers.

[0003] Communication networks operate according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards provided by 3GPP include so-called 3GPP standards for generations of cellular technology, such as 3GPP standards for 4G technology, 5G technology, etc. Summary of the Invention

[0004] Some exemplary embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various exemplary embodiments of this disclosure, nor are they intended to be used to limit its scope. In view of this disclosure, other features, aspects, and elements will be apparent to those skilled in the art. For example, it should be understood that additional aspects may be provided by any combination of any two or more of the aspects described below.

[0005] According to one aspect, an apparatus is provided, the apparatus comprising: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least:

[0006] Send information to the user plane function indicating at least one change in at least one business characteristic associated with the service data stream;

[0007] At least one of the following business characteristics is included:

[0008] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0009] The maximum burst size of the data stream for this service;

[0010] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0011] The duration of the data burst that sends the data stream for this service.

[0012] According to one embodiment, the information indicating at least one change in at least one business characteristic of a service data stream includes at least one of the following:

[0013] Identifier for the configuration file;

[0014] At least one parameter identifier for at least one business characteristic; or

[0015] At least one value of at least one business characteristic.

[0016] According to one embodiment, information indicating at least one change in at least one service characteristic of the service data stream is in the Real-Time Transport Protocol (RTP) header or the RTP payload type header.

[0017] According to one embodiment, information indicating at least one change in at least one business characteristic of a service data stream is sent as per-packet metadata of the service data stream.

[0018] According to one embodiment, the apparatus is further configured to send an indication of at least one QoS profile associated with information to a user plane function, the information indicating at least one change in at least one service characteristic of the service data stream.

[0019] According to one embodiment, at least one QoS profile includes: at least one target QoS profile to be adopted based on at least one variation of at least one service characteristic of the service data stream.

[0020] According to one embodiment, at least one QoS profile includes a QoS profile that is adopted when at least one change occurs in at least one service characteristic of the service data stream.

[0021] According to one embodiment, the device includes an application client or an application server.

[0022] According to one aspect, an apparatus is provided, the apparatus comprising: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least:

[0023] Send a request to the network associated with establishing a service data stream.

[0024] The request includes information indicating at least one profile of at least one service characteristic of the service data stream, the at least one profile being available after a Quality of Service (QoS) stream associated with the service data stream is established;

[0025] At least one of the following business characteristics is included:

[0026] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0027] Jitter associated with periodicity;

[0028] The maximum burst size of the service data stream;

[0029] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0030] The duration of the data burst that sends the service data stream.

[0031] According to one embodiment, at least one configuration file includes: an initial configuration file indicating that at least one initial value of at least one service characteristic is to be initially adopted after a QoS flow associated with a service data flow is established.

[0032] According to one embodiment, the request further includes: an indication of the time for adopting the initial configuration file.

[0033] According to one embodiment, the information indicating at least one configuration file includes at least one of the following:

[0034] At least one identifier for at least one configuration file;

[0035] Includes a configuration file containing one or more parameter identifiers for each business characteristic; or

[0036] One or more values ​​for each business characteristic.

[0037] According to one embodiment, the device is further configured to:

[0038] After a QoS flow associated with a service data flow is established, a minimum time value for applying the change to the QoS flow associated with the service data flow is received from the network based on at least one change in at least one service characteristic of the service data flow.

[0039] According to one embodiment, after a QoS flow associated with a service data flow is established, applying a change to the QoS flow associated with the service data flow based on at least one change in at least one service characteristic of the service data flow includes at least one of the following:

[0040] After a QoS flow associated with a service data flow is established, the QoS profile of the QoS flow associated with the service data flow is changed based on at least one change in at least one service characteristic of the service data flow.

[0041] After a QoS flow associated with a service data flow is established, based on at least one change in at least one service characteristic of the service data flow, at least one connection mode discontinuous reception parameter of the QoS flow associated with the service data flow is changed; or

[0042] After a QoS flow associated with a service data flow is established, the scheduling of the QoS flow associated with the service data flow is changed based on at least one change in at least one service characteristic of the service data flow.

[0043] According to one embodiment, the device is further configured to:

[0044] Receive a response associated with establishing a service data stream from the network, wherein the response includes information indicating at least one initial value of at least one business characteristic of the service data stream, the at least one initial value being initially adopted after the service data stream is established.

[0045] According to one aspect, an apparatus is provided, the apparatus comprising: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least:

[0046] Detecting at least one change in at least one business characteristic associated with one or more packets carried by a service data stream; and

[0047] Send information to network nodes indicating at least one change in at least one service characteristic associated with at least one quality of service (QoS) flow associated with the service data flow;

[0048] At least one of the following business characteristics is included:

[0049] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0050] The jitter associated with this periodicity;

[0051] The maximum burst size of the data stream for this service;

[0052] The forward error correction rate associated with each data burst of the service's data stream that is successfully decoded; or

[0053] The duration of the data burst that sends the data stream for this service.

[0054] According to one embodiment, detecting at least one change in at least one service characteristic associated with one or more packets carried by a service data stream includes:

[0055] Receive information from the application entity indicating at least one of at least one changes to at least one business characteristic associated with one or more packets of the service data stream.

[0056] According to one embodiment, the information indicating at least one change in at least one of at least one business characteristic of a service data stream includes at least one of the following:

[0057] Identifier of the configuration file

[0058] At least one parameter identifier for at least one business characteristic, or

[0059] At least one value for at least one business characteristic.

[0060] According to one embodiment, information indicating at least one of at least one variation of at least one service characteristic associated with one or more packets carried by a service data stream is carried in the following: a downlink General Packet Radio Service Tunneling Protocol User Plane (GTP-U) packet of a QoS stream associated with the service data stream, a virtual GTP-U packet, or an information element including a GTP-U header.

[0061] According to one embodiment, the apparatus is further configured to: receive from a network node a response indicating the status of received information, the information indicating at least one change in at least one service characteristic associated with one or more packets carried by the service data stream.

[0062] According to one embodiment, the apparatus is configured to send information to a network node indicating at least one change in at least one service characteristic associated with a service data stream via:

[0063] Send a message to the session management function indicating at least one change in at least one service characteristic associated with one or more packets carried by the service data stream in the Packet Forwarding Control Protocol (PFCP) report.

[0064] According to one aspect, an apparatus is provided, the apparatus comprising: at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least:

[0065] Information received from the network indicates at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow, and

[0066] Based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow, apply the change associated with the QoS flow;

[0067] At least one of the following business characteristics is included:

[0068] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0069] The jitter associated with this periodicity;

[0070] The maximum burst size of the data stream for this service;

[0071] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0072] The duration of the data burst that sends the service data stream.

[0073] According to one embodiment, the information indicating at least one change in at least one service characteristic associated with a QoS flow related to a service data flow includes at least one of the following:

[0074] Identifier of the configuration file

[0075] At least one parameter identifier for at least one business characteristic, or

[0076] At least one value of at least one business characteristic.

[0077] According to one embodiment, the device is further configured to:

[0078] Send a response to the network indicating the status of received information, which indicates at least one change in at least one service characteristic associated with a QoS flow related to the service data flow.

[0079] According to one embodiment, the apparatus is configured to apply a change associated with a QoS flow by at least one of the following changes based on at least one service characteristic of the QoS flow:

[0080] After a QoS flow is established, the QoS profile of the QoS flow is changed based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow.

[0081] After a QoS flow is established, at least one connection mode discontinuous reception parameter is changed based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow; or

[0082] After a QoS flow is established, the scheduling of the QoS flow is changed based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow.

[0083] According to one embodiment, the device is further configured to:

[0084] Receive a request from the network associated with establishing a QoS flow, wherein the request includes information indicating at least one profile of at least one service characteristic associated with the QoS flow of the service data flow, the profile being to be used after the QoS flow is established.

[0085] According to one embodiment, at least one configuration file includes: an initial configuration file indicating at least one initial value of at least one service characteristic to be initially adopted after the QoS flow is established.

[0086] According to one embodiment, the request further includes: an indication of the time for adopting the initial configuration file.

[0087] According to one embodiment, the information indicating at least one configuration file includes at least one of the following:

[0088] At least one identifier for at least one configuration file;

[0089] This includes configuration files containing one or more parameter identifiers for each business characteristic, or

[0090] One or more values ​​for each business characteristic.

[0091] According to one embodiment, the device is further configured to:

[0092] After a QoS flow is established, based on at least one change in at least one service characteristic of the QoS flow, the minimum time value of the change associated with the application and the QoS flow is sent to the network.

[0093] According to one embodiment, the device is further configured to:

[0094] Send a response to the network associated with establishing a QoS flow, wherein the response includes information indicating at least one initial value of at least one service characteristic of the QoS flow, the at least one initial value being initially adopted after the QoS flow is established.

[0095] According to one aspect, an apparatus is provided, comprising:

[0096] A component for sending information to user plane functions, the information indicating at least one change in at least one business characteristic associated with the service data stream;

[0097] At least one of the following business characteristics is included:

[0098] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0099] The maximum burst size of the data stream for this service;

[0100] The forward error correction rate associated with each data burst of the service's data stream that is successfully decoded; or

[0101] The duration of the data burst that sends the data stream for this service.

[0102] According to one embodiment, the information indicating at least one change in at least one business characteristic of a service data stream includes at least one of the following:

[0103] Identifier for the configuration file;

[0104] At least one parameter identifier for at least one business characteristic; or

[0105] At least one value of at least one business characteristic.

[0106] According to one embodiment, information indicating at least one change in at least one service characteristic of the service data stream is in the Real-Time Transport Protocol (RTP) header or the RTP payload type header.

[0107] According to one embodiment, information indicating at least one change in at least one business characteristic of a service data stream is sent as per-packet metadata of the service data stream.

[0108] According to one embodiment, the device further includes:

[0109] A component for sending an indication of at least one QoS profile associated with information to a user plane function, the information indicating at least one change in at least one service characteristic of a service data stream.

[0110] According to one embodiment, at least one QoS profile includes: at least one target QoS profile to be adopted based on at least one variation of at least one service characteristic of the service data stream.

[0111] According to one embodiment, at least one QoS profile includes a QoS profile that is adopted when at least one change occurs in at least one service characteristic of the service data stream.

[0112] According to one embodiment, the device includes an application client or an application server.

[0113] According to one aspect, an apparatus is provided, the apparatus comprising:

[0114] A component used to send requests to the network associated with establishing a service data stream.

[0115] The request includes information indicating at least one profile of at least one service characteristic of the service data stream, the at least one profile being available for use after a Quality of Service (QoS) stream associated with the service data stream is established;

[0116] At least one of the following business characteristics is included:

[0117] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0118] Jitter associated with periodicity;

[0119] The maximum burst size of the service data stream;

[0120] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0121] The duration of the data burst that sends the service data stream.

[0122] According to one embodiment, at least one configuration file includes: an initial configuration file indicating that at least one initial value of at least one service characteristic is to be initially adopted by the service characteristic after a QoS flow associated with the service data flow is established.

[0123] According to one embodiment, the request further includes: an indication of the time for adopting the initial configuration file.

[0124] According to one embodiment, the information indicating at least one configuration file includes at least one of the following:

[0125] At least one identifier for at least one configuration file;

[0126] Includes a configuration file containing one or more parameter identifiers for each business characteristic; or

[0127] One or more values ​​for each business characteristic.

[0128] According to one embodiment, the device further includes:

[0129] A component for receiving from the network, after a QoS flow associated with a service data flow has been established, a minimum time value for applying the change to the QoS flow associated with the service data flow based on at least one change in at least one service characteristic of the service data flow.

[0130] According to one embodiment, after a QoS flow associated with a service data flow is established, applying a change to the QoS flow associated with the service data flow based on at least one change in at least one service characteristic of the service data flow includes at least one of the following:

[0131] After a QoS flow associated with a service data flow is established, the QoS profile of the QoS flow associated with the service data flow is changed based on at least one change in at least one service characteristic of the service data flow.

[0132] After a QoS flow associated with a service data flow is established, based on at least one change in at least one service characteristic of the service data flow, at least one connection mode discontinuous reception parameter of the QoS flow associated with the service data flow is changed; or

[0133] After a QoS flow associated with a service data flow is established, the scheduling of the QoS flow associated with the service data flow is changed based on at least one change in at least one service characteristic of the service data flow.

[0134] According to one embodiment, the device further includes:

[0135] A component for receiving a response associated with establishing a service data stream from a network, wherein the response includes: information indicating at least one initial value of at least one service characteristic of the service data stream, the at least one initial value being initially adopted after the service data stream is established.

[0136] According to one aspect, an apparatus is provided, the apparatus comprising:

[0137] A component for detecting at least one change in at least one business characteristic associated with one or more packets carried by a service data stream; and

[0138] A component for sending information to a network node, the information indicating at least one change in at least one service characteristic associated with at least one quality of service (QoS) flow associated with the service data flow;

[0139] At least one of the following business characteristics is included:

[0140] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0141] The jitter associated with this periodicity;

[0142] The maximum burst size of the data stream for this service;

[0143] The forward error correction rate associated with each data burst of the service's data stream that is successfully decoded; or

[0144] The duration of the data burst that sends the data stream for this service.

[0145] According to one embodiment, the component for detecting at least one change in at least one service characteristic associated with one or more packets carried by a service data stream includes:

[0146] A component for receiving information from an application entity, the information indicating at least one of at least one changes in at least one business characteristic associated with one or more packets of a service data stream.

[0147] According to one embodiment, the information indicating at least one change in at least one of at least one business characteristic of a service data stream includes at least one of the following:

[0148] Identifier of the configuration file

[0149] At least one parameter identifier for at least one business characteristic, or

[0150] At least one value for at least one business characteristic.

[0151] According to one embodiment, information indicating at least one of at least one variation of at least one service characteristic associated with one or more packets carried by a service data stream is carried in: a downlink General Packet Radio Service Tunneling Protocol User Plane (GTP-U) packet of a QoS stream associated with the service data stream, a virtual GTP-U packet, or an information element including a GTP-U header.

[0152] According to one embodiment, the device further includes:

[0153] A component for receiving a response from a network node indicating the status of received information, the information indicating at least one change in at least one service characteristic associated with one or more packets carried by the service data stream.

[0154] According to one embodiment, the component for sending information to a network node indicating at least one change in at least one service characteristic associated with a service data stream includes:

[0155] A component for sending information to the session management function, the information indicating at least one change in at least one business characteristic associated with one or more packets carried by the service data stream.

[0156] According to one aspect, an apparatus is provided, the apparatus comprising:

[0157] A component for receiving information from the network, the information indicating: at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow, and

[0158] A component for applying a change associated with a QoS flow based on at least one change of at least one service characteristic associated with a QoS flow related to a service data flow;

[0159] At least one of the following business characteristics is included:

[0160] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0161] The jitter associated with this periodicity;

[0162] The maximum burst size of the data stream for this service;

[0163] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0164] The duration of the data burst that sends the service data stream.

[0165] According to one embodiment, the information indicating at least one change in at least one service characteristic associated with at least one QoS flow associated with a service data flow includes at least one of the following:

[0166] Identifier of the configuration file

[0167] At least one parameter identifier for at least one business characteristic, or

[0168] At least one value of at least one business characteristic.

[0169] According to one embodiment, information indicating at least one of at least one variation of at least one service characteristic associated with one or more packets carried by a service data stream is carried in the following: a downlink General Packet Radio Service Tunneling Protocol User Plane (GTP-U) packet of a QoS stream associated with the service data stream, a virtual GTP-U packet, or an information element including a GTP-U header.

[0170] According to one embodiment, the device further includes:

[0171] A component for sending a response to the network indicating the status of received information, the information indicating at least one change in at least one service characteristic associated with: the QoS flow associated with the service data flow.

[0172] According to one embodiment, the component for applying a change associated with a QoS flow based on at least one change in at least one service characteristic of the QoS flow includes at least one of the following:

[0173] A component for modifying the QoS profile of a QoS flow after the QoS flow has been established, based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow.

[0174] A component for changing at least one connection mode discontinuous reception parameter based on at least one change in at least one service characteristic associated with the QoS flow after the QoS flow is established; or

[0175] A component for changing the scheduling of a QoS flow after the QoS flow is established based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow.

[0176] According to one embodiment, the device further includes:

[0177] A component for receiving a request from the network associated with establishing a QoS flow, wherein the request includes: information indicating at least one profile of at least one service characteristic associated with the QoS flow of the service data flow, the profile being to be adopted after the QoS flow is established.

[0178] According to one embodiment, at least one configuration file includes: an initial configuration file indicating at least one initial value of at least one service characteristic to be initially adopted after the QoS flow is established.

[0179] According to one embodiment, the request further includes: an indication of the time for adopting the initial configuration file.

[0180] According to one embodiment, the information indicating at least one configuration file includes at least one of the following:

[0181] At least one identifier for at least one configuration file;

[0182] This includes configuration files containing one or more parameter identifiers for each business characteristic, or

[0183] One or more values ​​for each business characteristic.

[0184] According to one embodiment, the device further includes:

[0185] A component for sending to the network a minimum time value of the application-associated change of the QoS flow based on at least one change of at least one service characteristic of the QoS flow after the QoS flow is established.

[0186] According to one embodiment, the device further includes:

[0187] A component for sending a response to the network associated with the establishment of a QoS flow, wherein the response includes information indicating at least one initial value of at least one service characteristic of the QoS flow, the at least one initial value being initially adopted after the QoS flow is established.

[0188] According to one aspect, a method is provided, the method comprising:

[0189] Send information to the user plane function indicating at least one change in at least one business characteristic associated with the service data stream;

[0190] At least one of the following business characteristics is included:

[0191] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0192] The maximum burst size of the service data stream;

[0193] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0194] The duration of the data burst that sends the service data stream.

[0195] According to one aspect, a method is provided, the method comprising:

[0196] Send a request to the network associated with establishing a service data stream.

[0197] The request includes information indicating at least one profile of at least one service characteristic of the service data flow, the at least one profile being available for use after a Quality of Service (QoS) flow associated with the service data flow is established;

[0198] The at least one business characteristic includes at least one of the following:

[0199] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0200] Jitter associated with periodicity;

[0201] The maximum burst size of the service data stream;

[0202] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0203] The duration of the data burst that sends the service data stream.

[0204] According to one aspect, a method is provided, the method comprising:

[0205] Detecting at least one change in at least one business characteristic associated with one or more packets carried by a service data stream; and

[0206] Send a message to a network node indicating at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow;

[0207] At least one of the following business characteristics is included:

[0208] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0209] Jitter associated with periodicity;

[0210] The maximum burst size of the service data stream;

[0211] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0212] The duration of the data burst that sends the service data stream.

[0213] According to one aspect, a method is provided, including:

[0214] Information received from the network indicates at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow, and

[0215] Based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow, apply the change associated with the QoS flow;

[0216] At least one of the following business characteristics is included:

[0217] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0218] Jitter associated with periodicity;

[0219] The maximum data burst size of the data burst in the service data stream;

[0220] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0221] The duration of the data burst that sends the service data stream.

[0222] According to one aspect, a computer-readable medium including instructions, which, when executed by a device, cause the device to perform at least the following:

[0223] Send information to the user plane function indicating at least one change in at least one business characteristic associated with the service data stream;

[0224] At least one of the following business characteristics is included:

[0225] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0226] The maximum burst size of the service data stream;

[0227] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0228] The duration of the data burst that sends the service data stream.

[0229] According to one aspect, a computer-readable medium including instructions, which, when executed by a device, cause the device to perform at least the following:

[0230] Send a request to the network associated with establishing a service data stream.

[0231] The request includes information indicating at least one profile of at least one service characteristic of the service data flow, the at least one profile being available for use after a Quality of Service (QoS) flow associated with the service data flow is established;

[0232] The at least one business characteristic includes at least one of the following:

[0233] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0234] Jitter associated with periodicity;

[0235] The maximum burst size of the service data stream;

[0236] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0237] The duration of the data burst that sends the service data stream.

[0238] According to one aspect, a computer-readable medium including instructions, which, when executed by a device, cause the device to perform at least the following:

[0239] Detecting at least one change in at least one business characteristic associated with one or more packets carried by a service data stream; and

[0240] Send a message to a network node indicating at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow;

[0241] At least one of the following business characteristics is included:

[0242] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0243] Jitter associated with periodicity;

[0244] The maximum burst size of the service data stream;

[0245] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0246] The duration of the data burst that sends the service data stream.

[0247] According to one aspect, a computer-readable medium including instructions, which, when executed by a device, cause the device to perform at least the following:

[0248] Information received from the network indicates at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow, and

[0249] Based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow, apply the change associated with the QoS flow;

[0250] At least one of the following business characteristics is included:

[0251] Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0252] Jitter associated with periodicity;

[0253] The maximum data burst size of the data burst in the service data stream;

[0254] The forward error correction rate associated with each data burst of the successfully decoded service data stream; or

[0255] The duration of the data burst that sends the service data stream.

[0256] According to one aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium including program instructions that, when executed by a device, cause the device to perform at least the method according to any of the preceding aspects.

[0257] Many different aspects have been described above. As previously mentioned, it should be understood that additional aspects can be provided by combining two or more of the aforementioned aspects. Other features, aspects, and elements will become apparent from the following. Attached Figure Description

[0258] The above and other aspects, and their implementations, are described in more detail in the accompanying drawings, description, and claims.

[0259] Figure 1 An example of a fifth-generation communication system is shown;

[0260] Figure 2 Some embodiments of the present disclosure are shown for use with Figure 1 Examples of devices for communication systems;

[0261] Figure 3 Examples of apparatuses according to some embodiments of the present disclosure are shown;

[0262] Figure 4 A schematic diagram of a process according to an embodiment of the present disclosure is shown;

[0263] Figure 5 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0264] Figure 6 A flowchart illustrating a process according to an embodiment of the present disclosure is shown;

[0265] Figure 7 A flowchart illustrating a process according to an embodiment of the present disclosure is shown;

[0266] Figure 8 A flowchart illustrating a process according to an embodiment of the present disclosure is shown; and

[0267] Figure 9 A flowchart of a process according to an embodiment of the present disclosure is shown. Detailed Implementation

[0268] In the following description, various example embodiments are illustrated with reference to communication devices capable of communicating with a communication system. To aid in a better understanding of the various example embodiments in the context, fifth-generation communication systems (5GS), their access networks and 5G core networks (5GC), and communication devices will be referenced. Figure 1 , Figure 2 as well as Figure 3 Described for illustrative purposes. Note that the methods and apparatus in each embodiment of this disclosure are not limited to applications in 5G and can also be applied to communication systems of 6G and above.

[0269] Figure 1A schematic representation of 5GS is shown. 5GS may include user equipment (UE) (or terminal (node)), access network (such as (Radio) Access Network ((R)AN) or Next Generation Radio Access Network (NG-RAN), 5GC, and one or more application functions (AFs). An AF can be deployed in the 5GS as a trusted AF. Alternatively, an AF can be deployed or hosted on one or more application servers in the data network (DN). In this example, this AF is an untrusted AF. 5GS connects the UE to the DN via the access network and 5GC (e.g., the 5GC's User Plane Function (UPF)).

[0270] (R)AN may include one or more radio access nodes, such as gNodeB (gNB). gNB may include one or more gNB distributed units (DUs) connected to one or more gNB centralized units (CUs).

[0271] 5GC may include the following network functions: Network Slice Selection Function (NSSF) (not included in...) Figure 1 (shown in the image); Network Exposure Function (NEF); Network Repository Function (NRF) (not shown in the image). Figure 1 (shown in the image); Policy Control Function (PCF) (not shown in the image) Figure 1 (shown in the image); Unified Data Management (UDM); (multiple) Application Functions (AF) (not shown in the image) Figure 1 (as shown in the diagram); Authentication Server Function (AUSF); Access and Mobility Management Function (AMF); Session Management Function (SMF); and UPF. Figure 1 The various interfaces (N1, N2, etc.) implemented between the various elements of the system are also shown.

[0272] Figure 2 It shows the control / implementation Figure 1 The 5GS shown includes one or more (network) functions or one or more network entities (e.g., Figure 1Examples of network devices 20 shown include (R)AN, Next Generation RAN (NG-RAN), Base Station (BS), gNB Central Unit (gNB-CU), gNB Distributed Unit (gNB-DU), NEF, UDM, AUSF, AMF, SMF, UPF, etc. That is, in some embodiments, each (network) function or each network entity of the 5GC is deployed or hosted on a network device 20. In alternative embodiments, two or more (network) functions or network entities accessing network 102 may share a single control device 20. Network device 20 may include at least one processor 200 (such as a microprocessor or application-specific integrated circuit (ASIC)), a storage unit 210, and a communication unit 220. Storage unit 210 may be any data storage device storing program code 212, which is accessed and executed by processor 200. Examples of storage unit 210 include, but are not limited to, read-only memory (ROM), flash memory, random access memory (RAM), hard disk, and optical data storage devices. Communication unit 220 may be a transceiver and is used to send and receive signals (e.g., signaling, messages, or packets) based on the processing results of processor 200. In one example, communication unit 220 sends and / or receives signals via interface unit 222. In some embodiments, interface unit 222 may be arranged inside or outside network device 20 and may include one or more antenna elements. The antenna arrangement may be a multiple-input multiple-output (MIMO) antenna. In some embodiments, communication unit 220 and / or interface unit 222 may be implemented by an external device (electrically) coupled to network device 20.

[0273] In some embodiments, the processor 200, storage unit 210 (e.g., ROM and RAM), communication unit 220, and other circuitry (e.g., modem) of the network device 20 may be provided on a circuit board, in a chipset, or in a system-on-a-chip.

[0274] Figure 3 An example of a communication device 30 is shown, such as Figure 1The UE (e.g., terminal (device)) in the communication device 30 can be implemented by any device capable of transmitting and receiving radio signals. Non-limiting examples of the communication device 30 include mobile stations (MS) or mobile devices, such as mobile phones or so-called "smartphones," computers provided with wireless interface cards or other wireless interface facilities (e.g., USB (Universal Serial Bus) dongles), personal data assistants (PDAs), or tablet computers provided with wireless communication capabilities, machine-type communication (MTC) devices, Internet of Things (IoT) type communication devices, or any combination of these devices. The communication device 30 may include at least one processor 300 (such as a microprocessor or ASIC), a storage unit 310, and a communication unit 320. The storage unit 310 can be any data storage device storing program code 312, which is accessed and executed by the processor 300. Examples of the storage unit 310 include, but are not limited to, subscriber identity modules (SIM cards), ROM, flash memory, RAM, hard disks, and optical data storage devices. The communication unit 320 can be a transceiver and is used to transmit and receive signals (e.g., signaling, messages, or packets) based on the processing results of the processor 300. In one example, communication unit 320 transmits and / or receives signals via interface unit 322. In some embodiments, interface unit 322 may be arranged inside or outside network device 30 and may include one or more antenna elements. The antenna arrangement may be a multiple-input multiple-output (MIMO) antenna. In some embodiments, communication unit 320 and / or interface unit 322 may be implemented via an external device (electrically) coupled to network device 30.

[0275] In some embodiments, the communication device 30 may optionally have a user interface, such as a keyboard 305, a touchscreen or touchpad, or a combination thereof. Optionally, depending on the type of communication device 30, one or more of a display, a speaker, and a microphone may be provided.

[0276] In some embodiments, the processor 300, storage unit 310 (e.g., ROM and RAM), communication unit 320, and other circuitry of the communication device 30 (e.g., modem) may be provided on a circuit board, in a chipset, or in a system-on-a-chip.

[0277] Many applications (such as extended reality (XR) media streaming, including video, audio, and haptic streaming) can be characterized by a set of parameters, including the service cycle (the frequency at which the application sends bursts of packets (i.e., data bursts)) or the maximum burst size. Other relevant characteristics may also exist, such as burst duration, forward error correction protection level, or burst / packet level latency. This knowledge of characteristics can be used in the network (especially in the (5G / 6G) RAN) to optimize service processing with regard to power savings or scheduling. Some of these parameters are defined as ancillary information, which can be provided to the RAN for optimization purposes. Since service characteristics can change dynamically, having an efficient method for updating ancillary information from the application to the network / RAN would be advantageous. Therefore, whether and how to support dynamic changes in service characteristics (e.g., burst-related parameters) provided by the application in the DN becomes a topic for discussion. The discussion may need to consider at least the following aspects:

[0278] -Which business characteristics are / need to be dynamically changed?

[0279] - Whether and how the network can be enhanced to understand dynamic changes in the service characteristics of Quality of Service (QoS) flows (e.g., Guaranteed Bit Rate (GBR) flows and / or non-GBR flows);

[0280] - What information (if any) from applications in the DN is needed by the network to understand dynamic changes in service characteristics, and how that information is provided by applications in the DN;

[0281] - At what granularity does the network need to understand changes in service characteristics (e.g., QoS flow granularity);

[0282] - When the network becomes aware of changes in service characteristics, which processes might be required?

[0283] In the following text, the technology related to this disclosure is briefly discussed.

[0284] PDU set processing

[0285] For XR and Media Services (XRM), processing based on Protocol Data Unit (PDU) sets is defined in standard specifications (e.g., 3GPP TS23.501 V18.6.0 and 3GPP TS23.502 V18.6.0) to support QoS for XR and bring application awareness to 5GS. A PDU set comprises one or more PDUs carrying a payload of one information unit generated at the application level (e.g., multiple frames or video slices for XRM services).

[0286] To support PDU set identification and marking, a dedicated Real-time Transport Protocol (RTP) header extension was introduced in 3GPP TS 26.522 V18.0.0 Clause 4.4, which includes single-byte or double-byte RTP header extensions. The RTP header extension for PDU set marking can be used by the application server (AS) or the sending UE, which uses RTP to transmit media to the receiving UE (e.g., an application client (AC) configured / deployed within the UE).

[0287] Alternative QoS

[0288] The AF can request QoS from the 5GS by specifying QoS service requirements and optional alternative service requirements in a request sent to the NEF / PCF (e.g., see 3GPP TS23.502V18.6.0, Clause 4.15.6.6). Alternative service requirements include one or more sets of the requested alternative QoS parameters (e.g., one or more of Guaranteed Stream Bit Rate (GFBR), Packet Delay Budget (PDB), or Packet Error Rate (PER), or reference those parameter sets in order of priority. Based on information provided by the AF or local configuration, the PCF develops a Policy and Charging Control (PCC) rule that includes the QoS parameters, which is then sent to the SMF. If alternative service requirements (QoS references or individual parameters) are also provided, the PCF includes the alternative QoS parameter set in the PCC rule(s).

[0289] Business Support Information

[0290] In addition to QoS parameters, the AF can also provide the 5GS with a set of auxiliary information about traffic flows. These include traffic characteristics such as direction (uplink (UL) or downlink (DL)), periodicity, burst arrival time, and maximum burst size. Initially, the auxiliary information was defined as part of Time-Sensitive Communication (TSC) and was therefore called TSC Auxiliary Information (TSCAI). However, it is applicable to any type of periodic traffic. TSCAI is provided to the RAN by the 5GC, and the RAN uses it for purposes such as power saving or scheduling.

[0291] Note that in existing technologies, the TSCAI parameter is not part of the QoS profile or alternative QoS profile. Each AF session or QoS flow has only one TSCAI set, with no alternatives.

[0292] Periodic negotiation between AF and 5GS / RAN

[0293] While each AF session or QoS flow has only one TSCAI set, a feature is introduced for negotiating the optimal cycle value between the application (e.g., AF) and 5GS / RAN. The AF can suggest multiple cycle values ​​or a range of cycle values ​​that the application is willing to support, and 5GS / RAN can select the best value from the suggested cycle values ​​or ranges from its own perspective. However, once 5GS / RAN selects a cycle value, only the selected cycle value will be associated with and used in the QoS flow. Unselected values ​​suggested by the AF are not "remembered" by 5GS / RAN and cannot be referenced in subsequent processes.

[0294] Note that in the existing technology, changing the periodicity of the service flow or any other TSCAI parameter requires a new AF request. Updating such changes to the RAN, which requires a PDU session modification process, takes a certain amount of time and may not be applied quickly enough to change the relevant parameters of the service flow.

[0295] In this disclosure, how an application can effectively indicate to the RAN that its service characteristics have changed will be discussed. For effective indication, this indication may need to be implemented at the user plane (UP), as indication via the AF session update process and the PDU session update process via the control plane (CP) may be too slow and / or unscalable. In the prior art, there is no framework describing the mechanisms required to support dynamic service characteristic changes. Such mechanisms refer to changes / capabilities required at the AF, 5GC, and RAN levels, where changes required at the 5GC level include changes / capabilities required at one or more of the NEF, PCF, SMF, and UPF.

[0296] On the other hand, a relevant parameter in the service characteristics could be the service cycle, which is expected to change relatively frequently (within seconds). In this case, using an exposure / CP-based process to update the service cycle may not be scalable for the RAN to meaningfully self-adjust before the next change in the service cycle. Other relevant parameters similar to the service cycle (e.g., parameters that change dynamically / rapidly) could include the maximum data burst size, the forward error correction level / ratio for the PDU set, the data burst duration, etc. In this disclosure, one or more such parameters may be included in an auxiliary information profile to flexibly cover any future expansions beyond the parameters listed in this disclosure. In this disclosure, parameters included in the auxiliary information profile are referred to as an auxiliary information parameter set or an auxiliary information set. The auxiliary information profile includes / indicates multiple values ​​of the auxiliary information (multiple) parameter set.

[0297] Furthermore, various encoding mechanisms exist within the media layer, such as chunked encoding, variable resolution streaming, or content-aware coding (CAE), to handle different types of services or provide different media delivery schemes. In these scenarios, the bitrate may change periodically. For example, as the scene changes, the optimal bitrate for each resolution may be adjusted, or the bitrate may be derived by the encoder to achieve the desired minimum quality level. In this case, the application-layer encoder can use variable durations to encode different content (e.g., scenes or frames). Therefore, the jitter in the arrival times of different content will also change along with the bitrate and may need to be considered and included in the auxiliary information profile.

[0298] Last but not least, many applications support bitrate adaptation based on congestion control methods under any circumstances. These methods include traditional loss rate-based approaches, the more recent Low Latency Low Loss Scalable Throughput (L4S) approach, or explicit signals from the network regarding available bitrates, the application's QoS profile, congestion levels, etc. Such bitrate adaptation mechanisms can support various bitrates or quality levels and seek to adapt to available bitrates or quality levels dynamically. In doing so, their service characteristics are also dynamically updated.

[0299] In one aspect, a solution might be needed that does not extend the QoS / Alt-QoS profile and meets the requirements for rapid changes in the aforementioned parameters (e.g., periodicity, burst size, etc.). Other parameters are not exclusive.

[0300] This disclosure presents a set of frameworks and methods to allow applications (e.g., AS and / or AC) to efficiently indicate to the network multiple updates / changes in their service characteristics. The framework is discussed in at least the following three sections:

[0301] 1) Negotiation between the AF and the network via the exposed interface regarding the supported in-band (i.e., user plane) update methods, and the (multiple) auxiliary information profiles describing the service features to be used in the application session and / or the initial auxiliary information profile.

[0302] 2) A method for performing in-band service feature updates from the application (e.g., the AC or AS behind the UPF in the UE) to the core network (e.g., the UPF). These updates may or may not reference a configuration file negotiated between the AF and the network.

[0303] 3) A method for performing in-band service characteristic detection and labeling on the UP from the core network (e.g., user plane functions) to the (access) network. This update may or may not refer to a configuration file negotiated between the AF and the network.

[0304] In some embodiments, the application consists of an AS and an AC. In this disclosure, the AF and AS / AC are assumed to be able to coordinate with each other. In some embodiments, the AC is located in / included in / deployed in the UE.

[0305] In some embodiments, these methods allow for service characteristic changes initiated by an application (e.g., an AC in the UE or an AS behind the UPF) through negotiation between the 5GS and the AF regarding service characteristics in the service characteristic set (in terms of auxiliary information profiles or parameter values) and when they will be applied. Following negotiation, the actual service characteristic can be detected in the UPF, then indicated to the RAN, and applied in the RAN. Detection of updated service characteristics is based on various methods, including updates from the application (e.g., an AC in the UE or an AS behind the UPF).

[0306] In some embodiments, when / if the AF / AS / AC anticipates the potential use of different codec profiles (i.e., a set of specific encoding tools and algorithms), the AF / AS / AC provides the 5GS via the NEF with information that allows the 5GS to associate a profile ID with a set of actual auxiliary information and optional protocol descriptions(s). Optionally, the profile ID may also be associated with a QoS / Alt-QoS profile.

[0307] In some embodiments, the SMF provides auxiliary information (multiple parameters or multiple profiles) to the RAN and UPF. Applications (e.g., an AC in the UE or an AS behind the UPF) may send indications of changes in the auxiliary information (multiple parameters or profiles) to the RAN / UPF from the UP. For example, the SMF may send a new auxiliary information profile ID or multiple new parameter values ​​to be applied to an existing auxiliary information profile. This new auxiliary information profile ID or multiple new parameter values ​​is provided to the RAN by the UPF on the 5GS UP (e.g., on a GTP-U) and may also be used by the UPF for processing its DL PDUs. The RAN then considers / determines the updated or most recently applied auxiliary information (multiple parameters or profiles), and optionally a set of protocol descriptions corresponding to the new auxiliary information profile ID or multiple new parameter values ​​received from the UPF. In some embodiments, the auxiliary information profile ID may also be associated with a QoS / Alt-QoS profile.

[0308] In some embodiments, only one auxiliary information profile and an optional set of protocol descriptions(s) are applied at a given time. In some embodiments, an auxiliary information (parameter / profile) may also be associated with a QoS / Alt-QoS profile.

[0309] In some embodiments, the business characteristics (included in auxiliary information (configuration file)) or auxiliary information (parameters) include at least one of the following:

[0310] - Periodicity, which refers to the time interval between the start of two data bursts;

[0311] - Jitter, which is associated with periodicity (updated by UPF);

[0312] - Maximum burst size of the data burst;

[0313] - Forward error correction level or the rate at which each data burst is successfully decoded;

[0314] - Duration of data bursts.

[0315] Figure 4 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 4 The process shown includes at least the following steps:

[0316] Step 401: The AF provides the 5GS with one or more (alternative) auxiliary information profiles or auxiliary information parameter values ​​(i.e., values ​​of auxiliary information (parameters)) and the service requirements of the application service via the NEF. In some embodiments, one of the provided auxiliary information profiles or provided parameter values ​​may be indicated as the initial / default auxiliary information profile / parameter value to be applied (e.g., the first in the list of provided (alternative) auxiliary information profiles or auxiliary information parameter values), or as the default auxiliary information profile / parameter value to be used when / if no "auxiliary information" is available via the UP. Alternatively or additionally, RAN selection of the initial auxiliary information profile / parameter value may be supported. That is, in Figure 4 In steps 406 to 408 shown, the RAN selection for the initial auxiliary information profile / parameter value reported to the AF can be optional.

[0317] Steps 402 and 403: (Optional) Auxiliary information configuration files or parameter values ​​are transmitted via 5GC (e.g., NEF, PCF, SMF, and AMF). Figure 4 (not shown in the image) is transmitted to the RAN.

[0318] Step 404: The SMF provides / sends a protocol description for the application to the UPF. The protocol description can be based on the service requirements of the application business and the initial / default auxiliary information configuration file / parameter values.

[0319] Step 405: The RAN selects / determines one of the auxiliary information profiles or parameter values ​​as the initial auxiliary information profile or parameter value. In some embodiments, the initial / default auxiliary information profile / parameter value is indicated in the information received from the 5GC / AF. In these embodiments, the RAN applies the initial auxiliary information profile or parameter value based on this indication. In some embodiments, RAN selection of the initial auxiliary information profile / parameter value is supported. In these embodiments, the RAN may ignore any indication received from the 5GC / AF (if any), determine / select an auxiliary information profile / parameter value (e.g., based on service requirements of the application service), and perform steps 406 to 408 to report the determined / selected auxiliary information profile / parameter value.

[0320] Steps 406 to 408: The RAN feeds back the determined / selected initial auxiliary information profile or parameter values ​​to the AF via the 5GC. In some embodiments, the RAN may indicate to the AF via the 5GC the minimum time value required for changes to the auxiliary information profile or parameter values ​​and / or associated QoS / Alt-QoS profiles. Specifically, this minimum time value refers to or indicates the minimum time required for the RAN to switch / change from (applying / using) profile A to (applying / using) another profile B, where profiles A and B can be auxiliary information profiles and / or (associated) QoS profiles. In some embodiments, the RAN switching / changing (applying / using) or applying / using a profile means that the RAN applies / adopts the corresponding parameter / service characteristics indicated in the profile.

[0321] As described above, in the AF request sent / transmitted via NEF, one of the auxiliary information profiles or parameter values ​​can be indicated as the initial / default auxiliary information profile or parameter value to be used when no "auxiliary information" is available via UP. Alternatively, the RAN selection for the initial auxiliary information can be supported. That is, the RAN selection for reporting the initial auxiliary information to the AF in steps 406 to 408 can be optional.

[0322] In some embodiments, steps 406 and 408 are performed (only) for reporting the minimum time values ​​for changes to the auxiliary information profile or parameter values ​​and / or associated QoS / Alt-QoS profiles. In these embodiments, regardless of whether the initial auxiliary information profile / parameter value RAN selection is supported, the RAN can report the minimum time values ​​for changes to the auxiliary information profile or parameter values ​​and / or associated QoS / Alt-QoS profiles to the AF via the 5GC.

[0323] Steps 409a and 409b: Figure 4The process illustrated applies to both downlink (DL) and uplink (UL) traffic. For DL, step 409a is performed. For UL, step 409b is performed. In step 409a, the UE (e.g., an AC configured / deployed within the UE) sends auxiliary information to the UPF (i.e., via the UP) to indicate changes in the auxiliary information for UL traffic. Similarly, in step 409b, the AS sends auxiliary information to the UPF (i.e., via the UP) to indicate changes in the auxiliary information for DL ​​traffic. In some embodiments, at least one of steps 409a and 409b is performed.

[0324] Steps 410 and 411: The UPF detects changes in the auxiliary information or parameter values ​​and updates the auxiliary information configuration file or parameter values ​​to the RAN.

[0325] Step 412 (optional): The RAN sends feedback to the UPF to indicate successful reception of the (updated) auxiliary information profile or (multiple) parameter values.

[0326] Step 413: The RAN adapts to the updated auxiliary information configuration file or parameter values.

[0327] Step 414 (optional): The RAN decides whether to change the (alternative) QoS profile based on the updated auxiliary information profile or parameter values.

[0328] In some embodiments, the auxiliary information in steps 409a, 409b, and 410 may include a configuration file ID or an actual value.

[0329] To support switching QoS / Alt-QoS profiles, a minimum time value may be required for changes to updated auxiliary information profiles or (multiple) auxiliary information parameter values, and for the associated QoS / Alt-QoS profiles or switching between QoS / Alt-QoS profiles. If the minimum time value is violated, the RAN is not expected to change the auxiliary information profile / parameter value and / or the associated QoS / Alt-QoS profile. Therefore, the RAN may also be allowed to specify a minimum time value to the AF via the 5GC. For example, in step 408, the NEF may provide the AF with the minimum allowed time value between two QoS / Alt-QoS profile changes performed in step 413. This minimum time value may be provided as feedback from the RAN in steps 406 and 407, or as a policy configured on the PCF and / or NEF's local policy.

[0330] Further embodiments of this disclosure are described below.

[0331] In the following embodiments, Option-1 refers to a (predefined) mapping relationship between the auxiliary information profile / parameter value and the QoS / Alt-QoS profile. Option-2 refers to a (predefined) mapping relationship between the auxiliary information profile and the QoS / Alt-QoS profile. That is, the auxiliary information profile / parameter value is unrelated to the QoS / Alt-QoS profile.

[0332] In the following embodiments, method A refers to a method of identifying / indicating the value of auxiliary information (multiple parameters) by using / indicating auxiliary information profile (ID). Method B refers to a method of identifying / indicating the identification value of auxiliary information (multiple parameters) by using / indicating the ID of auxiliary information (multiple parameters). Method C refers to a method of identifying / indicating the identification / indication value of auxiliary information (multiple parameters) by using / indicating the actual value of auxiliary information (multiple parameters).

[0333] In some embodiments, the behavior of an application (e.g., an AS behind a (configured / deployed) AC or UPF in a UE) may include at least one of the following:

[0334] An AS behind an AC or UPF in a UE can have a communication context with the UPF via a tunnel through which the AS passes its traffic to the AC. Similarly, an AC can also have a communication context with the UPF via a tunnel used to pass its traffic to the AS.

[0335] - The AS and / or AC can learn whether and how the network (e.g., 5GS) supports dynamic changes to auxiliary information profiles or parameter values ​​via UP-based methods, through AF-based negotiation or configuration. The AS and / or AC can also learn how the network supports dynamic changes during tunnel establishment with the UPF. Both the UPF and the AS / AC indicate the methods they support, and based on these indications, the AS / AC understands which method(s) can be used and which parameters that method is used for.

[0336] -AS / AC can at any time indicate to UPF via UP changes in one or more auxiliary information profiles or parameter values ​​having an identifier (ID) (method A / B) or the actual value of an auxiliary information parameter (method C) using one of the following methods. In some embodiments, this indication can be reliably made through a request sent by AS, which is acknowledged by UPF.

[0337] ○ For RTP-based services in the absence of a tunnel between AS / AC and UPF:

[0338] ■ The ID of the selected auxiliary information profile or each parameter value (Method A or B) is included in the RTP protocol header. Alternatively, the RTP protocol header may contain multiple actual values ​​of the auxiliary information parameters (Method C). This header can be:

[0339] • Existing RTP Payload Type (PT) header; or

[0340] • The RTP “Service Feature ID” header extension supports multiple independent profile IDs (Method A) or parameter value IDs (Method B). In some embodiments, this header or PT can be included in all RTP packets, provided that these values ​​are applicable or are included in a limited number of RTP packets after an update to reduce overhead.

[0341] ■ Using RTP, AC can only update auxiliary information related to UL business, while AS can only update auxiliary information related to DL business.

[0342] ○ In the case of the AS / AC to UPF tunnel:

[0343] ■ The ID of the applied auxiliary information configuration file (Method A), or (multiple) auxiliary information parameter values ​​(Method B), or (multiple) actual values ​​of the auxiliary information (Method C) are provided to the UPF as new per-group metadata using per-group metadata. The metadata is a single "business characteristic configuration file / parameter value ID," or the actual value defined for each parameter. Based on this method, both AC and AS can update UP and / or DL ​​related information depending on the application's internal behavior.

[0344] - The (alternative) auxiliary information profile or (alternative) auxiliary information value for each parameter can be associated with a specific QoS / Alt-QoS profile (option-1) or independent of the QoS / Alt-QoS profile (option-2).

[0345] In UP services, applications include IDs (in the QoS / Alt-QoS configuration file) pointing to (multiple) QoS parameters, as well as corresponding auxiliary information. Note that if changes in (multiple) auxiliary information require changes in QoS / Alt-QoS, the same or different IDs can simultaneously point to the corresponding QoS / Alt-QoS configuration file.

[0346] In some embodiments, the behavior of AF may include at least one of the following:

[0347] - The AF provides (alternative) service characteristics (i.e., (alternative) auxiliary information profiles or (alternative) auxiliary information parameter values) to the network (e.g., 5GS) and negotiates initial values ​​for the service characteristics with the network. In some embodiments, the AF may instruct the network when to apply the initial values ​​of the service characteristics. Alternative service characteristics can be provided to the network in different ways discussed below:

[0348] Method A:

[0349] ■AF provides one or more (alternative) auxiliary information profiles to the network along with the service requirements of application services. These auxiliary information profiles can be separate from / independent of the QoS / Alt-QoS profiles. The purpose of providing auxiliary information profiles is to assist the RAN in its processing, for example, in scheduling or power saving.

[0350] ■AF may provide and update one or more (optional) auxiliary information profiles at any time via publicly available methods.

[0351] ■AF can designate one of the auxiliary information profiles as the initial auxiliary information profile, and optionally when the initial auxiliary information profile is expected to be applied. Alternatively, AF can indicate the priority order for auxiliary information profiles, or alternative auxiliary information profiles, and depends on the RAN determining the initial auxiliary information profile or initial auxiliary information parameter value during the QoS flow establishment process.

[0352] ■ Each (alternative) auxiliary information configuration file has an ID, which can be referenced via subsequent CP or UP processes.

[0353] ■ (Alternative) Auxiliary information profiles are provided to the network in the manner of option-1: they are provided separately from the primary QoS profile, and each alternative QoS profile is inlined within the QoS profile or via a reference to its ID; or they are provided to the network in the manner of option-2: auxiliary information profiles are provided independently of the QoS / Alt-QoS profiles.

[0354] Method B:

[0355] ■ Instead of providing multiple (alternative) auxiliary information profiles, AF provides only a single auxiliary information profile, which contains / includes at least one (e.g., two or more) alternative parameter values ​​for a single auxiliary information parameter.

[0356] ■ Similar to method A, each parameter value has an ID, which can be referenced via subsequent CP or UP procedures.

[0357] ■AF can indicate which of the values ​​is the initial value for each auxiliary information parameter. Alternatively, AF can indicate the priority order of the alternative values ​​and depends on the RAN to determine the initial applied values ​​of the auxiliary information parameters(s) during the QoS flow establishment process.

[0358] ■Note that for both Method A and Method B, if the RAN is capable, the AF can also receive RAN instructions for the selected initial auxiliary information profile or parameter(s) values. The AF then uses the received initial auxiliary information profile or parameter(s) values ​​to instruct the AS to perform traffic transmission. Additionally, the AF can indicate its ability to support auxiliary information profile or parameter value updates via the UP, and understand the same network capabilities. Based on this, the application will understand which type of update method it can use. These capabilities can indicate which auxiliary information parameters are updatable and by which method.

[0359] Method C:

[0360] ■ During the QoS flow establishment process, the AF does not provide a 5GS auxiliary information profile or parameter values(s) with IDs as a prerequisite for dynamic updates to the UP. The AF sends the AF-supported dynamic update via the UP using (multiple) explicit auxiliary information parameter values ​​and optional (multiple) initial auxiliary information parameter values. If the network (e.g., 5GS and / or RAN) supports dynamic updates using (multiple) explicit auxiliary information parameter values, the network indicates this support back to the AF. In some embodiments, the AF and the network (e.g., 5GS / RAN) may exchange a list of preferred values ​​for each auxiliary information parameter.

[0361] ■ After the QoS flow is successfully established, a direct in-band (UP) update is performed, and the actual values ​​of the auxiliary information (multiple parameters) are directly transmitted from the AS / AC to the UPF.

[0362] In some embodiments, the behavior of the UPF may include at least one of the following:

[0363] The UPF detects changes in the auxiliary information configuration file or parameter values(s) using the methods described above, and updates the changed auxiliary information configuration file or parameter values(s) to the RAN. The UPF can also send an auxiliary information update indication to the RAN.

[0364] ○ The auxiliary information update indication will be carried in any DL GTP-U (GPRS tunneling protocol for UP) packet of the corresponding QoS flow, or in a virtual GTP-U packet with a new GTP-U header or an information element containing / including an existing GTP-U header. This indication may include an “Auxiliary Information Profile ID” (Method A), a parameter value ID for each supported auxiliary parameter (Method B) (the same as listed above for AS / AC to UPF), or (multiple) actual values ​​of the auxiliary information parameters (Method C).

[0365] In some embodiments, an auxiliary information update response indication (e.g., carried in a real GTP-U packet or a virtual GTP-U packet) can be specified, indicating that the RAN has successfully received the auxiliary information update indication. The RAN sends the auxiliary information update response indication in response to this indication. When / if the auxiliary information update response indication is received, the UPF acknowledges that the RAN has successfully received the auxiliary information update indication. When / if the UPF receives feedback after a timer expires, the UPF considers / determines that the transmission of the auxiliary information update indication has failed, and the transmission failure can be notified to the AF / AS.

[0366] In some embodiments, the auxiliary information update indication may alternatively be sent from the UPF to the RAN via the control plane using new PFCP reporting parameters. In these embodiments, the PFCP reporting parameters, including the auxiliary information update indication, are sent from the UPF to the SMF, and the SMF updates the PFCP reporting parameters to the RAN using the PDU session modification procedure. The UPF may send its acknowledgment in response to an update request from the AC / AS only after it has been acknowledged by the RAN.

[0367] In some embodiments, the behavior of the RAN may include at least one of the following:

[0368] When / if the RAN receives an in-band (dynamic) change indication (i.e., ancillary information update indication) from the UPF, the RAN stores the updated (alternative) ancillary information profile or (multiple) (alternative) parameter values ​​received from the UPF, and (optionally) selects one of the (alternative) ancillary information profile or (alternative) parameter values ​​as the ancillary information profile or parameter value to be applied to the corresponding service based on the updated ancillary information profile or (multiple) parameter values. Thereafter, the RAN may send an ancillary information update response indication to the UPF to indicate successful reception of the indication from the core network (e.g., 5GC (UPF or SMF)), as described in the UPF behavior section above.

[0369] ○ During the QoS flow establishment process, the selection of the (initial) auxiliary information profile or (multiple) parameter values ​​has the following options:

[0370] ■ Option-1: The RAN selects a QoS / Alt-QoS profile based on the admission control results. The auxiliary information profile or parameter value(s) is selected from the profiles associated with the selected QoS / Alt-QoS profile. If one of the auxiliary information profiles or parameter values(s) is indicated as the initial auxiliary information profile or parameter value(s), the RAN applies it. If there is an indicator of when the initial profile or parameter value(s) is expected to be applied, the RAN determines RAN processing (e.g., resource allocation) based on that indicator. If there is a priority order for the auxiliary information profiles or auxiliary information parameter values(s), the RAN selects one of them based on the priority order and its own preferences.

[0371] ■Option-2: In this option, it is assumed that there is no association between the (alternate) auxiliary information profile or parameter value and the QoS / Alt-QoS profile. In this case, the RAN applies the indicated (alternate) auxiliary information profile or parameter value as the initial auxiliary information profile or (multiple) auxiliary information parameter value. Alternatively, the RAN selects the (alternate) auxiliary information profile or (multiple) auxiliary information parameter value based on the provided priority order and its own preferences.

[0372] ■Note that regardless of whether option 1 or 2 is applied, the RAN will send the application's auxiliary information configuration file or parameter values ​​to the SMF.

[0373] - After a QoS flow is established, when / if the RAN reselects a QoS / Alt-QoS profile, the RAN reapplies or reselects the auxiliary information profile or(s) parameter values. Reselection of the auxiliary information profile or(s) parameter values ​​has the following options:

[0374] Option 1: After an auxiliary information profile or parameter value is selected, the RAN determines whether the associated QoS / Alt-QoS profile can be applied or (re)selected. If so, the RAN notifies the network (e.g., CN), and the network notifies the AF of the (re)selected QoS / Alt-QoS profile.

[0375] Option 2: The RAN can further enforce QoS using the received / updated / changed auxiliary information profile / (multiple) parameter values. If the RAN decides to update the QoS / Alt-QoS profile based on the received / updated / changed auxiliary information profile / (multiple) parameter values, the RAN notifies the network (e.g., CN) and informs the AF of the selected QoS / Alt-QoS profile.

[0376] - To support switching QoS / Alt-QoS profiles, a minimum time value is required for changing auxiliary information profiles or parameter values. The AF may need to know this minimum time value. If this minimum time value is violated or not met, the RAN is not expected to change / switch the QoS / Alt-QoS profile. The RAN may be allowed to specify this minimum time value to the AF via the network (e.g., CN or 5GC).

[0377] In some embodiments, the behavior of a network (e.g., a core network (CN) or 5GC) may include at least one of the following:

[0378] - Updated auxiliary information profiles or auxiliary parameter values, and changes to associated QoS / Alt-QoS profiles or the minimum time required to switch between QoS / Alt-QoS profiles, will be reported to the AF based on at least one of the following:

[0379] - Feedback from RAN;

[0380] - The policy configured on PCF; or

[0381] -NEF's local strategy.

[0382] Figure 5 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 5 In this context, it is assumed that QoS Notification Control (QNC) is enabled for a given GBR QoS flow. Additionally, the RAN (e.g., NG-RAN) has received a list of (multiple) alternative QoS profiles for this QoS flow and supports alternative QoS profile processing. Figure 5 The process shown includes the following steps:

[0383] Steps 500a to 500c: The UE establishes at least one PDU session (step 500b). In some embodiments, a tunnel is established between the AS and the UPF (step 500c). In embodiments applying option 1, step 500a is performed, and the predefined mapping between the auxiliary information profile and the QoS / Alt-QoS profile is predefined / configured in the RAN.

[0384] Step 501: The AF sends an AF request to the NEF and PCF to establish a service data stream for the established PDU session. This AF request includes (multiple) service requests, (multiple) alternative service requests, and (multiple) (alternative) auxiliary information profiles. In some embodiments, step 501 is performed via an existing exposure mechanism, such as the AFSessionWithQoS API defined in Clause 5.2.6.9 of 3GPP TS 23.502 V18.6.0.

[0385] Step 502: The PCF generates PCC rules that include multiple ancillary information profiles. For example, the ancillary information profile ID and its associated ancillary information parameter values ​​are added to the definition of the PCC rule in Clause 6.3.1 of 3GPP TS 23.503 V18.6.0.

[0386] Step 503: The PCC rule is forwarded to the SMF (e.g., via the Npcf_SMPolicyControl service as defined in Clause 5.2.5.4 of 3GPP TS 23.502 V18.6.0).

[0387] Step 504: The SMF updates the RAN using the auxiliary information profile, which may mean / require changes to QoS PDU session-related information for the NGAP protocol as defined in 3GPP TS38.413 V18.2.0.

[0388] Step 505: The SMF updates the UPF using the protocol description in the Packet Detection Rules (PDR) to facilitate the UPF's implementation of auxiliary information identification and marking. This may mean changes to or changes to the PDR and QoS Enforcement Rules (QER) definitions in 3GPP TS 29.244 V18.6.0 (e.g., controlling the UPF may require information provided in the GTP-u extension).

[0389] Step 506: The RAN performs admission control on the new QoS flow. This occurs if / when the RAN receives a request from the SMF to select an initial auxiliary information profile. In step 507, the RAN selects an initial auxiliary information profile and notifies the SMF of the selected profile.

[0390] In some embodiments, the RAN provides feedback on the minimum time required to change the auxiliary information profile (or auxiliary information parameter values ​​and associated QoS / Alt-QoS profiles) or to switch between QoS / Alt-QoS profiles. The change / switch can occur at any time during the QoS flow's lifetime (e.g., in step 515).

[0391] Steps 508 to 510: The selected initial auxiliary information profile or parameter(s) value is sent to the AF. In some embodiments, a minimum time value may also be provided to the AF from the RAN in steps 507 to 510. In some embodiments, the NEF provides the minimum time value to the AF as a policy configured on the PCF or a local policy of the NEF.

[0392] In some embodiments, steps 507 to 510 may be omitted if / when the RAN is not allowed to select an initial auxiliary information profile.

[0393] In some embodiments, steps 507 to 510 are performed only to provide the minimum time required to change the auxiliary information profile (or (multiple) auxiliary information parameter values), and the associated QoS / Alt-QoS profile, or to switch between QoS / Alt-QoS profiles.

[0394] Steps 511a and 511b: The AS behind the AC and / or UPF in the UE can decide to update auxiliary information (profile / (multiple) parameter values) at any time after the QoS flow is established.

[0395] In some embodiments, updated auxiliary information (configuration file / (multiple) parameter values) is updated using application data. The application data is received by the UPF from the AS or from the UE / AC.

[0396] In embodiments where metadata exchange occurs via tunnels from UE / AC to UPF or AS to UPF, auxiliary information updates from UE / AC or AS to UPF may not be carried within UL or DL ​​traffic data. Instead, they may be provided via the tunnel in the form of specific flow metadata updates or auxiliary information update requests and responses. In these embodiments, the UPF may send a response either after receiving a request or immediately after receiving a corresponding response from the RAN. Alternatively, the UPF may send a specific type of response in both stages. Detailed information about the service flow or auxiliary information metadata update can be provided using HTTP requests and responses. For example, if only an AS-to-UPF tunnel exists, and no AC-to-UPF tunnel exists, the AS will update information regarding both the UL and DL directions.

[0397] Step 512: The UPF detects dynamic changes in the auxiliary information configuration file or parameter values(s). This detection can be based on RTP (header extension or payload header extension) traffic detection, or on XRM metadata information received in the tunnel through which the AS transmits its services to the AC via the UPF.

[0398] When dynamic changes are indicated by the RTP protocol header, a dedicated RTP header extension or an existing RTP payload header can be applied. When a PT is used, the PT value corresponds to a profile ID or parameter value ID. In some embodiments, if the dynamic PT value starts from 96, and the profile / parameter ID may be limited to 0 to 15, the AF provides the 5GS with a mapping between PT values ​​and profile / parameter IDs (e.g., 96->0, 97->1, etc.) during the AF / 5GS process. This mapping with profile IDs is provided to the RAN or UPF, which may also act as a mapper.

[0399] UPF performs GTP-U grouping by using detected update auxiliary information ((multiple) changes).

[0400] For the auxiliary information parameter "jitter", the UPF detects changes without involving AS. The UPF can use the mechanism defined in Clause 5.37.8.2 of TS23.501 V18.6.0 to derive N6 jitter and periodicity when the auxiliary information parameter "jitter" changes in the detected auxiliary information.

[0401] Step 513: The UPF may send ancillary information update indications to the RAN (e.g., carried in GTP-U packets sent in DL services, and these packets may carry actual data or correspond to virtual packets). The UPF uses the detected ancillary information(s) changes to mark the GTP-U header(s) to the RAN.

[0402] Step 514: If possible, the RAN changes / updates the currently applied auxiliary information profile or parameter(s) values ​​to the detected updated auxiliary information profile or parameter(s) values ​​received from the UPF. Note that at any given time, only one auxiliary information profile (e.g., maximum burst size and period) is applicable to the service (on QoS flows / DRBs).

[0403] Step 515 (Optional): If / when the auxiliary information (profile / (multiple) parameter values) is updated in step 514, the RAN may need to determine whether to use / adopt a new QoS / Alt-QoS profile. If Option-1 is applied, the RAN can use the applied / updated auxiliary information profile / (multiple) parameter values ​​to determine the associated QoS / Alt-QoS profile based on the mapping between the applied / updated auxiliary information (profile / (multiple) parameter values) and the QoS / Alt-QoS profile. If Option-2 is applied, the RAN determines the newly adopted QoS / Alt-QoS profile based on the updated auxiliary information (profile / (multiple) parameter values). If the RAN decides to adopt / apply the new QoS / Alt-QoS profile, the RAN notifies the AF of the newly applied QoS / Alt-QoS profile via 5GC in step 517.

[0404] Step 516: (Optional): The RAN sends an Auxiliary Information Update Response Indicator (carried in a real or virtual GTP-U packet) in response to the indication received by the UPF. If / if an Auxiliary Information Update Response Indicator is received, the UPF knows that the RAN has successfully received the Auxiliary Information Update Indicator. Feedback received after this time has expired will be considered a failure. The failure information will be sent via CP or UP (…). Figure 5 (Not shown in the text) was notified to AF / AS.

[0405] Step 517 (optional): The RAN notifies the AF of the QoS / Alt-QoS profile for the new application via 5GC.

[0406] In some embodiments, after a QoS flow is established, the RAN attempts to satisfy a QoS profile or any alternative QoS profile with higher priority, as QNC is enabled for GBR flows. If the RAN decides to update / change the satisfied alternative QoS profile, the RAN can determine whether the (alternative) auxiliary information (profile / (multiple) parameter values) needs to be reselected. If there is no mapping between the (alternative) QoS profile and the auxiliary information (profile / (multiple) parameter values), or if the RAN selects a different auxiliary information (profile / (multiple) parameter values) linked to the selected (alternative) QoS profile, the RAN can indicate the selected auxiliary information (profile or(multiple) parameter values) for the alternative QoS profile used for the indicated QoS flow via CP (e.g., together with QNC notification) or UP. Alternatively, the RAN can leave the auxiliary information (profile / parameter values) unchanged until it receives an explicit indication from the UPF to change the auxiliary information (profile / parameter values).

[0407] Figure 6 A flowchart of a process / method according to an embodiment of the present disclosure is shown. Figure 6 The procedures / methods shown can be used in applications (entities), such as AC (configured in the UE), UE, or AS, and include the following steps:

[0408] Step 601: Send information to the UPF indicating changes to (multiple) service characteristics associated with the service data stream.

[0409] exist Figure 6 In this embodiment, the application sends information to the UPF indicating changes in (multiple) service characteristics associated with the service data stream, thereby updating (multiple) service characteristics of the service data stream via the UP. Based on the updated (multiple) service characteristics, the network (e.g., RAN) can update the corresponding parameters of the service data stream in a timely manner. In this embodiment, the service characteristics include at least one of the following: periodicity, which is the time interval between the start of two data bursts of the service data stream; the maximum data burst size of the data bursts of the service data stream; the forward error correction rate associated with successfully decoding each data burst of the service data stream; or the duration of sending the data bursts of the service data stream. Note that (multiple) service characteristics refer to the aforementioned auxiliary information profile, one or more auxiliary information parameters included in the auxiliary information profile, auxiliary information, or (multiple) auxiliary information parameters.

[0410] In some embodiments, the information indicating changes in (multiple) business characteristics of a service data stream includes at least one of the following: the ID of the configuration file (i.e., method A); the parameter IDs (i.e., method B) for (multiple) business characteristics; or the values ​​of (multiple) business characteristics. That is, the application indicates changes in (multiple) business characteristics of the service data stream by indicating / updating (multiple) changed business characteristic values. In some embodiments, the application indicates changes in (multiple) business characteristics of the service data stream by indicating / updating (multiple) differences between the changed business characteristic values ​​and the currently used business characteristic values.

[0411] In some embodiments, the application sends information in an RTP header or an RTP payload type header.

[0412] In some embodiments, the application sends information about the metadata of each packet as a service data stream.

[0413] In some embodiments, the application also sends an indication of multiple QoS profiles to the UPF to indicate multiple QoS profiles associated with multiple changes in multiple service characteristics of the service data flow. For example, the indicated multiple QoS profiles may be multiple QoS profile candidates to be adopted (by the network) if / when the network updates corresponding parameters of the service data flow based on multiple changes in multiple service characteristics of the service data flow. Specifically, the multiple QoS profiles include a target QoS profile to be adopted based on at least one change in at least one service characteristic of the service data flow. Alternatively, the multiple QoS profiles include a QoS profile that is adopted when at least one change in at least one service characteristic of the service data flow occurs (i.e., when / if the multiple service characteristics of the service data flow are changed / updated to the indicated changes in multiple service characteristics of the service data flow).

[0414] Figure 7 A flowchart of a process / method according to an embodiment of the present disclosure is shown. Figure 7 The illustrated process / method can be used in an AF (e.g., a network device / apparatus / entity / node that includes an AF, or a network device / apparatus / entity / node that performs at least part of the functions of an AF), and includes the following steps:

[0415] Step 701: Send a request to the network associated with establishing a service data stream.

[0416] exist Figure 7 In this process, the AF sends a request to the network (node) (e.g., PCF / NEF) associated with establishing a service data flow. This request includes information from (multiple) profiles indicating (multiple) service characteristics of the service data flow, which can be adopted after the QoS flow associated with the service data flow is established. The service characteristics include at least one of the following: periodicity, which is the time interval between the start of two data bursts of the service data flow; jitter associated with the periodicity; the maximum data burst size of the service data flow's data bursts; the forward error correction rate associated with successfully decoding each data burst of the service data flow; or the duration of sending the data bursts of the service data flow.

[0417] In some embodiments, the AF indicates in the request an initial profile that indicates / includes initial values ​​of(a) service characteristics to be initially adopted after the QoS flow associated with the service data flow is established.

[0418] In some embodiments, AF indicates in the request the time when the initial configuration file is adopted.

[0419] In some embodiments, the information indicating the configuration files includes at least one of the following: multiple IDs of the configuration files; a configuration file including multiple parameter IDs for each business characteristic; or multiple values ​​for each business characteristic.

[0420] In some embodiments, after a QoS flow associated with a service data flow is established, based on changes in / of multiple service characteristics of the service data flow, the AF can receive from the network a minimum time to apply the changes to the QoS flow associated with the service data flow. It should be noted that the changes applied to the QoS flow may include at least one of the following:

[0421] - Change / switch the QoS profile of the QoS stream;

[0422] - Change at least one connection mode discontinuous receive parameter of the QoS stream;

[0423] -Change the scheduling of QoS flows;

[0424] - Change / update the values ​​of (multiple) business characteristics of the service data stream.

[0425] In some embodiments, the AF can receive a response from the network associated with establishing a service data flow. This response includes information indicating initial values ​​of multiple service characteristics of the service data flow, which will be initially adopted after the service flow is established.

[0426] Figure 8 A flowchart of a process / method according to an embodiment of the present disclosure is shown. Figure 8 The process / method shown can be used in a UPF (e.g., a network device / entity / node that includes a UPF, or a network device / entity / node that performs at least some of the functions of a UPF), and includes the following steps:

[0427] Step 801: Detect multiple changes in multiple service characteristics associated with multiple packets carried by the service data stream.

[0428] Step 802: Send information to the network node indicating changes in (multiple) service characteristics associated with the QoS flow related to the service data flow.

[0429] exist Figure 8In this embodiment, the UPF is configured to detect changes in multiple service characteristics associated with multiple packets carried by the service data stream, and to notify network nodes (e.g., BS, RAN, NG-RAN) of the detected changes in the multiple service characteristics associated with the multiple packets. In this embodiment, the multiple service characteristics include at least one of the following:

[0430] - Periodicity, which is the time interval between the start of two data bursts in the service data stream;

[0431] - Jitter associated with periodicity;

[0432] - Maximum burst size of data bursts in the service data stream;

[0433] - The forward error correction rate of the face associated with each data burst of the successfully decoded service data stream; or

[0434] - The duration of the data burst that sends the service data stream.

[0435] Note that (multiple) business characteristics refer to the aforementioned auxiliary information configuration file, one or more auxiliary information parameters included in the auxiliary information configuration file, auxiliary information, or (multiple) auxiliary information parameters.

[0436] Based on transmissions indicated by changes in (multiple) detected service characteristics, network nodes can promptly apply changes to the transmission parameters of the QoS stream associated with the service data stream. Therefore, communication quality and / or resource efficiency can be improved.

[0437] In some embodiments, the UPF detects changes in multiple service characteristics associated with the packets carried by the service data stream via information received from an application entity (e.g., an AC configured in the UE, UE, or AS) indicating at least one change in multiple service characteristics associated with one or more packets of the service data stream. For example, the application entity may send information indicating changes in at least one of the following: the periodicity of data bursts of the service data stream; the maximum data burst size of the data bursts of the service data stream; the forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or the duration of the data bursts of the service data stream.

[0438] In some embodiments, information indicating changes is configured / carried in DL GTP-U packets, virtual GTP-U packets, or information elements including GTP-U headers in QoS flows associated with service data flows.

[0439] In some embodiments, the UPF receives a response from a network node. This response may indicate successful reception of information indicating changes in multiple service characteristics associated with the packets carried by the service data stream.

[0440] In some embodiments, the UPF sends information in the PFCP report indicating changes in multiple service characteristics associated with multiple packets carried by the service data stream.

[0441] Figure 9 A flowchart of a process / method according to an embodiment of the present disclosure is shown. Figure 9 The procedure / method shown can be used on network nodes (e.g., BS, RAN, NG-RAN) and includes the following steps:

[0442] Step 901: Receive from the network information indicating changes in (multiple) service characteristics associated with the QoS flow associated with the service data flow.

[0443] Step 902: Apply the changes associated with the QoS flow based on at least one service characteristic(s) of the QoS flow.

[0444] exist Figure 9 In this implementation, a network node receives information from the network (e.g., UPF, SMF, core network, 5GC) indicating changes in multiple service characteristics associated with a QoS stream associated with a service data stream. Note that the service data stream is mapped to a QoS stream by the network. From the network node's perspective, the network node may only identify the QoS stream. Therefore, the network node may consider this information to indicate changes in multiple service characteristics associated with the QoS stream. Based on the indicated changes in multiple service characteristics, the network node applies the changes associated with the QoS stream. In this embodiment, the multiple service characteristics include at least one of the following: periodicity, which is the time interval between the start of two data bursts of the service data stream; jitter associated with the periodicity; the maximum data burst size of the data bursts of the service data stream; the forward error correction rate associated with successfully decoding each data burst of the service data stream; or the duration of the data bursts of the service data stream.

[0445] In some embodiments, information indicating changes in multiple service characteristics associated with a QoS flow associated with a service data flow is provided via / through an indication / including at least one of the following:

[0446] - The ID of the configuration file (Method A)

[0447] - Multiple parameter IDs for (multiple) business characteristics, (Method B) or

[0448] - (Multiple) values ​​of (multiple) business characteristics, (method C).

[0449] In some embodiments, information indicating changes in multiple service characteristics associated with a QoS flow associated with a service data flow is carried in the DL GTP-U packet, virtual GTP-U packet, or IE including a GTP-U header of the QoS flow.

[0450] In some embodiments, a network node sends a response to the network indicating the status of received information, which indicates at least one change in at least one service characteristic associated with the QoS flow associated with the service data flow. For example, if / when the information is successfully received, the network node may send a response to the network indicating successful reception of the information.

[0451] In some embodiments, application changes associated with QoS flows may include at least one of the following:

[0452] - Changes to the ' / ' in the QoS profile of the QoS stream;

[0453] - (Multiple) variations of / in the discontinuous reception parameters of (multiple) connection modes;

[0454] - Multiple changes to / in the scheduling of QoS flows;

[0455] - Changes in / of (multiple) service characteristics of -QoS flow.

[0456] Note that these changes are applied after the QoS flow is established. In other words, network nodes apply the initial / default settings when the QoS flow is established. Based on the received changes in the service characteristics associated with the QoS flow (associated with the service data flow), the network node performs changes on the QoS flow to correspondingly modify the initial / default settings.

[0457] In some embodiments, a network node receives a request to establish a QoS flow from a network (e.g., core network, 5GC, SMF). This request includes information indicating at least one service characteristic associated with the QoS flow (associated with the service data flow) and / or a configuration file(s) therefor, which may be used after the QoS flow is established.

[0458] In some embodiments, the request includes an indication of an initial profile that indicates initial values ​​of (multiple) service characteristics to be initially adopted after a QoS flow is established. The request may also include an indication of when the initial profile will be adopted.

[0459] In some embodiments, information indicating / for which at least one service characteristic associated with a QoS flow (associated with a service data flow) is a profile, similar to information indicating / for which changes in / of service characteristics(s), includes at least one of the following:

[0460] - At least one configuration file(s) ID;

[0461] -Includes configuration files with (multiple) parameter IDs for each business characteristic, or

[0462] - Values ​​for each traffic characteristic (multiple values).

[0463] In some embodiments, after a QoS flow is established, a network node sends to the network a minimum time value (information / indication) of the changes associated with the application in relation to the QoS flow, based on changes in the (multiple) service characteristics associated with the QoS flow (associated with the service data flow).

[0464] In some embodiments, a network node may, based on its performance, be allowed / able to determine / decide / select (or select) multiple initial values ​​for (or selectable initial values ​​for) service characteristics associated with a QoS flow (associated with a service data flow). In these embodiments, the network node sends a response to the network associated with establishing a QoS flow, wherein the response includes information indicating the determined / decided / selected initial values ​​for (or selectable initial values ​​for) service characteristics associated with the QoS flow, which will be initially adopted after the QoS flow is established.

[0465] It should be understood that the references to various network functions (e.g., AMF, SMF, TNF, etc.) in the foregoing can be implemented by means (e.g., network means 20) that perform at least some of the functions associated with these network functions. Furthermore, means configured to implement network functions can also be configured as virtual network function instances that implement those network functions.

[0466] In some embodiments, the apparatus may be or include network functions, such as AF, NEF, UDM / UDR, AMF, etc. In this disclosure, an apparatus that is / includes network functions refers to an apparatus / device configured to provide / perform at least a portion of the functions of that network function.

[0467] It should be understood that these devices may include or be coupled to other units or modules used for / for transmission and / or reception, such as radio components or radio heads. Although these devices have been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0468] It should be noted that while some embodiments have been described with respect to 5G networks, similar example embodiments can be applied to other networks and communication systems. Therefore, although some example embodiments have been described above by way of example with reference to certain example architectures of wireless networks, technologies, and standards, other example embodiments can be applied to any other suitable form of communication system besides those shown and described herein.

[0469] While various embodiments of this disclosure have been described above, it should be understood that these embodiments are presented by way of example only and not as limitations. Similarly, various diagrams may depict exemplary architectures or configurations, provided to enable those skilled in the art to understand the exemplary features and functionality of this disclosure. However, those skilled in the art should understand that this disclosure is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as understood by those skilled in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0470] As used herein, phrases such as “at least one of the following: ” and “at least one of the following ”, and similar wording, wherein the list of two or more elements is connected by “and” or “or”, mean at least one element, at least two or more elements, or at least all elements. As used herein, the expression “and / or” includes any and all combinations of the listed terms, including at least one element, at least two or more elements, or at least all elements.

[0471] As used herein, the term “or” means non-exclusive “or” unless otherwise specified (e.g., “or other” or “or alternative”).

[0472] As used herein, unless explicitly stated otherwise, “responding to A” does not indicate that the step is executed immediately after “A” occurs, and one or more intermediate steps may be included. Similarly, “based on A” does not indicate that the step or function is executed solely based on “A”, as one or more additional conditions may be included.

[0473] Generally, various embodiments can be implemented in hardware, or a dedicated circuit system, software, logic, or any combination thereof. Some aspects of this disclosure can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but this disclosure is not limited thereto. While various aspects of this disclosure may be shown or described as block diagrams, flowcharts, or using some other graphical representation, it should be well understood that these blocks, apparatuses, systems, techniques, or methods described herein are intended as non-limiting and illustrative examples implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0474] As used herein, the term "circuit system" may refer to one or more or all of the following:

[0475] (a) Hardware circuit implementation only (e.g., implementation only in analog and / or digital circuit systems); and

[0476] (b) A combination of hardware circuitry and software, such as (if applicable):

[0477] (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and

[0478] (ii) Any part of the (multiple) hardware processors having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions; and

[0479] (c) (a ...

[0480] This definition of "circuit system" applies to all uses of the term herein (including in any claim). As another example, as used herein, the term "circuit system" also covers implementations consisting solely of hardware circuitry or a processor (or processors) or a portion thereof and its accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0481] Embodiments of this disclosure can be implemented by computer software executable by a data processor of a mobile device (such as a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs, also known as program products, include software routines, applets, and / or macros, and can be stored in any device-readable data storage medium, and they include program instructions for performing a specific task. A computer program product may include one or more computer-executable components that are configured to perform the embodiments when the program is run. The one or more computer-executable components may be at least one piece of software code or a portion thereof.

[0482] Furthermore, those skilled in the art will understand that the various exemplary steps, logical flows, logic blocks, units, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, units, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, these functions may be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein may be implemented as software (code) stored on a (non-transitory) computer-readable medium.

[0483] As used herein, the term “non-transient” refers to the limitations of the medium itself (e.g., tangible, not signal-based), rather than the limitations of data storage persistence (e.g., RAM vs. ROM).

[0484] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, DSPs, ASICs, FPGAs, gate-level circuits, and processors based on multi-core processor architectures.

[0485] In this disclosure, as used herein, the term "unit" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Furthermore, for purposes of discussion, individual units are described as discrete units; however, it will be apparent to those skilled in the art that two or more units may be combined to form a single unit that performs the associated functions according to embodiments of this disclosure.

[0486] For illustrative purposes, exemplary embodiments of this application are provided below.

[0487] Example 1. An apparatus comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least:

[0488] Send information to the user plane function, the information indicating at least one change in at least one business characteristic associated with the service data stream;

[0489] The at least one business characteristic mentioned above includes at least one of the following:

[0490] Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream;

[0491] The maximum data burst size of the data burst in the service data stream;

[0492] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0493] The duration of the data burst that sends the service data stream.

[0494] Example 2. The apparatus according to Example 1, wherein the information indicating the at least one change in the at least one service characteristic of the service data stream includes at least one of the following:

[0495] Identifier for the configuration file;

[0496] At least one parameter identifier for the at least one business characteristic; or

[0497] At least one value of the at least one business characteristic.

[0498] Example 3. The apparatus according to Example 1 or 2, wherein the information indicating at least one change of at least one service characteristic of the service data stream is in a Real-Time Transport Protocol (RTP) header or an RTP payload type header.

[0499] Example 4. The apparatus according to Example 1 or 2, wherein the information indicating at least one change of at least one service characteristic of the service data stream is sent as per-packet metadata of the service data stream.

[0500] Example 5. The apparatus according to any one of Examples 1 to 4, wherein the apparatus is further configured to:

[0501] Send to the user plane function an indication of at least one QoS profile associated with the information, the information indicating at least one change in at least one service characteristic of the service data stream.

[0502] Example 6. The apparatus according to Example 5, wherein the at least one QoS profile includes: at least one target QoS profile to be adopted based on the at least one variation of the at least one service characteristic of the service data stream.

[0503] Example 7. The apparatus according to Example 5 or 6, wherein the at least one QoS profile includes: a QoS profile adopted when the at least one change in the at least one service characteristic of the service data stream occurs.

[0504] Example 8. The apparatus according to any one of Examples 1 to 7, wherein the apparatus comprises: an application client or an application server.

[0505] Example 9. An apparatus comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least:

[0506] Send a request to the network associated with establishing a service data stream.

[0507] The request includes information indicating at least one profile of at least one service characteristic of the service data stream, the at least one profile being available for use after a Quality of Service (QoS) stream associated with the service data stream is established;

[0508] The at least one business characteristic mentioned above includes at least one of the following:

[0509] Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream;

[0510] Jitter associated with the periodicity;

[0511] The maximum data burst size of the data burst in the service data stream;

[0512] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0513] The duration of the data burst that sends the service data stream.

[0514] Example 10. The apparatus according to Example 9, wherein the at least one configuration file includes: an initial configuration file indicating that at least one initial value of the at least one service characteristic is to be initially adopted after the QoS flow associated with the service data flow is established.

[0515] Example 11. The apparatus according to Example 10, wherein the request further includes: an indication of the time for adopting the initial configuration file.

[0516] Example 12. The apparatus according to any one of Examples 10 to 11, wherein the information indicating the at least one configuration file includes at least one of the following:

[0517] At least one identifier of the at least one configuration file;

[0518] Includes a configuration file containing one or more parameter identifiers for each business characteristic; or

[0519] One or more values ​​for each business characteristic.

[0520] Example 13. The apparatus according to any one of Examples 10 to 12, wherein the apparatus is further configured to:

[0521] After the QoS flow associated with the service data flow is established, a minimum time value for applying the change to the QoS flow associated with the service data flow is received from the network based on at least one change in at least one service characteristic of the service data flow.

[0522] Example 14. The apparatus according to Example 13, wherein after the QoS flow associated with the service data flow is established, applying the change to the QoS flow associated with the service data flow based on the at least one change of the at least one service characteristic of the service data flow includes at least one of the following:

[0523] After the QoS flow associated with the service data flow is established, the QoS profile of the QoS flow associated with the service data flow is changed based on the at least one change in the at least one service characteristic of the service data flow.

[0524] After the QoS flow associated with the service data flow is established, based on at least one change in at least one service characteristic of the service data flow, at least one connection mode discontinuous reception parameter of the QoS flow associated with the service data flow is changed; or

[0525] After the QoS flow associated with the service data flow is established, the scheduling of the QoS flow associated with the service data flow is changed based on the at least one change in the at least one service characteristic of the service data flow.

[0526] Example 15. The apparatus according to any one of Examples 9 to 14, wherein the apparatus is further configured to:

[0527] Receive a response associated with establishing the service data stream from the network, wherein the response includes information indicating at least one initial value of at least one service characteristic of the service data stream, the at least one initial value to be initially adopted after the service data stream is established.

[0528] Example 16. An apparatus comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least:

[0529] Detecting at least one change in at least one business characteristic associated with one or more packets carried by a service data stream; and

[0530] Sending information to network nodes, the information indicating at least one change in at least one service characteristic associated with the Quality of Service (QoS) flow of the service data flow;

[0531] The at least one business characteristic mentioned above includes at least one of the following:

[0532] Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream;

[0533] Jitter associated with the periodicity;

[0534] The maximum data burst size of the data burst in the service data stream;

[0535] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0536] The duration of the data burst that sends the service data stream.

[0537] Example 17. The apparatus according to Example 16, wherein detecting the at least one change in the at least one service characteristic associated with one or more packets carried by the service data stream comprises:

[0538] Information is received from the application entity indicating at least one of the at least one changes to the at least one business characteristic associated with the one or more packets of the service data stream.

[0539] Example 18. The apparatus according to Example 17, wherein the information indicating at least one of the at least one change in the at least one service characteristic of the service data stream includes at least one of the following:

[0540] Identifier of the configuration file

[0541] At least one parameter identifier for at least one business characteristic, or

[0542] At least one value for at least one business characteristic.

[0543] Example 19. The apparatus according to Example 17 or 18, wherein the information indicating at least one of the at least one variation of the at least one service characteristic associated with the one or more packets carried by the service data stream is carried in the following: a downlink General Packet Radio Service Tunneling Protocol User Plane (GTP-U) packet of the QoS stream associated with the service data stream, a virtual GTP-U packet, or an information element including a GTP-U header.

[0544] Example 20. The apparatus according to any one of Examples 16 to 19, wherein the apparatus is further configured to:

[0545] Receive a response from the network node indicating the status of receiving the information, the information indicating at least one change in at least one service characteristic associated with the one or more packets carried by the service data stream.

[0546] Example 21. The apparatus according to any one of Examples 16 to 20, wherein the apparatus is made to

[0547] The network node is sent information indicating at least one change in at least one service characteristic associated with the service data stream via the following methods:

[0548] Send a message to the session management function indicating at least one change in at least one service characteristic associated with the one or more packets carried by the service data stream in the Packet Forwarding Control Protocol (PFCP) report.

[0549] Example 22. An apparatus comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least:

[0550] Information received from the network indicates at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow, and

[0551] Based on the at least one change in the at least one service characteristic associated with the QoS flow related to the service data flow, apply the change associated with the QoS flow;

[0552] The at least one business characteristic mentioned above includes at least one of the following:

[0553] Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream;

[0554] Jitter associated with the periodicity;

[0555] The maximum data burst size of the data burst in the service data stream;

[0556] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0557] The duration of the data burst that sends the service data stream.

[0558] Example 23. The apparatus according to Example 22, wherein the information indicating the at least one change of the at least one service characteristic associated with the QoS flow associated with the service data flow includes at least one of the following:

[0559] Identifier of the configuration file

[0560] At least one parameter identifier for the at least one business characteristic, or

[0561] At least one value of the at least one business characteristic.

[0562] Example 24. The apparatus according to Example 22 or 23, wherein the information indicating at least one change of at least one service characteristic associated with the QoS flow associated with the service data flow is carried in: a downlink General Packet Radio Service Tunneling Protocol User Plane (GTP-U) packet of the QoS flow, a virtual GTP-U packet, or an information element including a GTP-U header.

[0563] Example 25. The apparatus according to any one of Examples 22 to 24, wherein the apparatus is further configured to: send a response to the network indicating a state of receiving the information, the information indicating: at least one change of the at least one service characteristic associated with the QoS flow associated with the service data flow.

[0564] Example 26. An apparatus according to any one of Examples 22 to 25, wherein the apparatus is configured to apply the change associated with the QoS flow based on the at least one change of the at least one service characteristic of the QoS flow by at least one of the following:

[0565] After the QoS flow is established, the QoS profile of the QoS flow is changed based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow.

[0566] After the QoS flow is established, at least one connection mode discontinuous reception parameter is changed based on at least one change in the at least one service characteristic associated with the QoS flow related to the service data flow; or

[0567] After the QoS flow is established, the scheduling of the QoS flow is changed based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow.

[0568] Example 27. The apparatus according to any one of Examples 22 to 26, wherein the apparatus is further configured to:

[0569] Receive a request from the network associated with establishing the QoS flow, wherein the request includes: information indicating at least one profile of at least one service characteristic associated with the QoS flow of the service data flow, the profile being to be adopted after the QoS flow is established.

[0570] Example 28. The apparatus according to Example 27, wherein the at least one configuration file includes: an initial configuration file indicating that at least one initial value of the at least one service characteristic is to be initially adopted after the QoS flow is established.

[0571] Example 29. The apparatus according to Example 28, wherein the request further includes: an indication of the time for adopting the initial configuration file.

[0572] Example 30. The apparatus according to any one of Examples 27 to 29, wherein the information indicating the at least one configuration file includes at least one of the following:

[0573] At least one identifier of the at least one configuration file;

[0574] This includes configuration files containing one or more parameter identifiers for each business characteristic, or

[0575] One or more values ​​for each business characteristic.

[0576] Example 31. The apparatus according to any one of Examples 27 to 30, wherein the apparatus is further configured to:

[0577] After the QoS flow is established, based on the at least one change in the at least one service characteristic of the QoS flow, a minimum time value of the change associated with the QoS flow is sent to the network.

[0578] Example 32. The apparatus according to any one of Examples 27 to 31, wherein the apparatus is further configured to:

[0579] Send a response to the network associated with establishing the QoS flow, wherein the response includes information indicating at least one initial value of the at least one service characteristic of the QoS flow, the at least one initial value to be initially adopted after the QoS flow is established.

[0580] Example 33. A method for use in an application entity, the method comprising:

[0581] Send information to the user plane function, the information indicating at least one change in at least one business characteristic associated with the service data stream;

[0582] The at least one business characteristic mentioned above includes at least one of the following:

[0583] Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream;

[0584] The maximum data burst size of the data burst in the service data stream;

[0585] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0586] The duration of the data burst that sends the service data stream.

[0587] Example 34. A method for use in application functionality, the method comprising:

[0588] Send a request to the network associated with establishing a service data stream.

[0589] The request includes information indicating at least one profile of at least one service characteristic of the service data stream, the at least one profile being available for use after a Quality of Service (QoS) stream associated with the service data stream is established;

[0590] The at least one business characteristic mentioned above includes at least one of the following:

[0591] Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream;

[0592] Jitter associated with the periodicity;

[0593] The maximum data burst size of the data burst in the service data stream;

[0594] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0595] The duration of the data burst that sends the service data stream.

[0596] Example 35. A method for use in a user plane function, the method comprising:

[0597] Detecting at least one change in at least one business characteristic associated with one or more packets carried by a service data stream; and

[0598] Sending information to network nodes, the information indicating at least one change in at least one service characteristic associated with the Quality of Service (QoS) flow of the service data flow;

[0599] The at least one business characteristic mentioned above includes at least one of the following:

[0600] Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream;

[0601] Jitter associated with the periodicity;

[0602] The maximum data burst size of the data burst in the service data stream;

[0603] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0604] The duration of the data burst that sends the service data stream.

[0605] Example 36. A method for use in a network node, the method comprising:

[0606] Information received from the network indicates at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow, and

[0607] Based on the at least one change in the at least one service characteristic associated with the QoS flow related to the service data flow, apply the change associated with the QoS flow;

[0608] The at least one business characteristic mentioned above includes at least one of the following:

[0609] Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream;

[0610] Jitter associated with the periodicity;

[0611] The maximum data burst size of the data burst in the service data stream;

[0612] The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or

[0613] The duration of the data burst that sends the service data stream.

[0614] Example 37. A computer-readable medium including instructions, which, when executed by a device, cause the device to perform the method according to any one of Examples 33 to 36.

[0615] The scope of protection sought by the various exemplary embodiments of this disclosure is defined by the independent claims. Exemplary embodiments and features (if any) described in this disclosure that do not fall within the scope of the independent claims should be interpreted as examples that aid in understanding the various exemplary embodiments of this disclosure.

[0616] The foregoing description has provided a complete and detailed description of various exemplary implementations of this disclosure by way of non-limiting and illustrative examples. However, various modifications and adaptations will become apparent to those skilled in the art when read in conjunction with the accompanying drawings and claims, in view of this disclosure. Nevertheless, all such and similar modifications will still fall within the scope of the various exemplary embodiments of this disclosure. As a non-limiting and illustrative example, another exemplary embodiment is also provided, which includes a combination of one or more exemplary embodiments with any other exemplary embodiments discussed above.

Claims

1. An apparatus for communication, comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: Send information to the user plane function, the information indicating at least one change in at least one business characteristic associated with the service data stream; The at least one business characteristic mentioned above includes at least one of the following: Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream; The maximum data burst size of the data burst in the service data stream; The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or The duration of the data burst that sends the service data stream.

2. The apparatus of claim 1, wherein the information indicating the at least one change in the at least one service characteristic of the service data stream comprises at least one of the following: Identifier for the configuration file; At least one parameter identifier for the at least one business characteristic; or At least one value of the at least one business characteristic.

3. The apparatus of claim 1, wherein the information indicating at least one change in at least one service characteristic of the service data stream is in a Real-Time Transport Protocol (RTP) header or an RTP payload type header.

4. The apparatus of claim 1, wherein the information indicating at least one change in at least one service characteristic of the service data stream is sent as per-packet metadata of the service data stream.

5. The apparatus of claim 1, wherein the apparatus is further configured to: Send to the user plane function an indication of at least one QoS profile associated with the information, the information indicating at least one change in at least one service characteristic of the service data stream.

6. The apparatus of claim 5, wherein the at least one QoS profile comprises: At least one target QoS profile to be adopted based on at least one change in at least one service characteristic of the service data stream.

7. The apparatus of claim 5, wherein the at least one QoS profile comprises: The QoS profile used when the at least one change in the at least one service characteristic of the service data stream occurs.

8. The apparatus of claim 1, wherein the apparatus comprises: Application client or application server.

9. An apparatus for communication, comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: Send a request to the network associated with establishing a service data stream. The request includes information indicating at least one profile of at least one service characteristic of the service data stream, the at least one profile being available for use after a Quality of Service (QoS) stream associated with the service data stream is established; The at least one business characteristic mentioned above includes at least one of the following: Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream; Jitter associated with the periodicity; The maximum data burst size of the data burst in the service data stream; The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or The duration of the data burst that sends the service data stream.

10. The apparatus of claim 9, wherein the at least one configuration file comprises: An initial configuration file that indicates that at least one initial value of the at least one service characteristic is to be initially adopted after the QoS flow associated with the service data flow is established.

11. The apparatus of claim 10, wherein the request further comprises: Indication of the time when the initial configuration file is used.

12. The apparatus of claim 9, wherein the information indicating the at least one configuration file includes at least one of the following: At least one identifier of the at least one configuration file; Includes a configuration file containing one or more parameter identifiers for each business characteristic; or One or more values ​​for each business characteristic.

13. The apparatus of claim 9, wherein the apparatus is further configured to: After the QoS flow associated with the service data flow is established, a minimum time value for applying the change to the QoS flow associated with the service data flow is received from the network based on at least one change in at least one service characteristic of the service data flow.

14. The apparatus of claim 13, wherein after the QoS flow associated with the service data flow is established, applying the change to the QoS flow associated with the service data flow based on the at least one change of the at least one service characteristic of the service data flow comprises at least one of the following: After the QoS flow associated with the service data flow is established, the QoS profile of the QoS flow associated with the service data flow is changed based on the at least one change in the at least one service characteristic of the service data flow. After the QoS flow associated with the service data flow is established, at least one connection mode discontinuous reception parameter of the QoS flow associated with the service data flow is changed based on at least one change in at least one service characteristic of the service data flow. or After the QoS flow associated with the service data flow is established, the scheduling of the QoS flow associated with the service data flow is changed based on the at least one change in the at least one service characteristic of the service data flow.

15. The apparatus of claim 9, wherein the apparatus is further configured to: Receive a response associated with establishing the service data stream from the network, wherein the response includes: Information indicating at least one initial value of at least one service characteristic of the service data stream, the at least one initial value to be initially adopted after the service data stream is established.

16. An apparatus for communication, comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: Detecting at least one change in at least one business characteristic associated with one or more packets carried by a service data stream; and Sending information to network nodes, the information indicating at least one change in at least one service characteristic associated with the Quality of Service (QoS) flow of the service data flow; The at least one business characteristic mentioned above includes at least one of the following: Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream; Jitter associated with the periodicity; The maximum data burst size of the data burst in the service data stream; The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or The duration of the data burst that sends the service data stream.

17. The apparatus of claim 16, wherein detecting the at least one change in the at least one service characteristic associated with one or more packets carried by the service data stream comprises: Information is received from the application entity indicating at least one of the at least one changes to the at least one business characteristic associated with the one or more packets of the service data stream.

18. The apparatus of claim 17, wherein the information indicating at least one of the at least one change in the at least one service characteristic of the service data stream comprises at least one of the following: Identifier of the configuration file At least one parameter identifier for at least one business characteristic, or At least one value for at least one business characteristic.

19. The apparatus of claim 17, wherein the information indicating at least one of the at least one variation of the at least one service characteristic associated with the one or more packets carried by the service data stream is carried in one of the following: a downlink General Packet Radio Service Tunneling Protocol User Plane (GTP-U) packet, a virtual GTP-U packet, or an information element including a GTP-U header of the QoS stream associated with the service data stream.

20. The apparatus of claim 16, wherein the apparatus is further configured to: Receive a response from the network node indicating the status of receiving the information, the information indicating at least one change in at least one service characteristic associated with the one or more packets carried by the service data stream.

21. The apparatus of claim 16, wherein the apparatus is configured to: The network node is sent information indicating at least one change in at least one service characteristic associated with the service data stream via the following methods: Send a message to the session management function indicating at least one change in at least one service characteristic associated with the one or more packets carried by the service data stream in the Packet Forwarding Control Protocol (PFCP) report.

22. An apparatus for communication, comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: Information received from the network indicates at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow, and Based on the at least one change in the at least one service characteristic associated with the QoS flow related to the service data flow, apply the change associated with the QoS flow; The at least one business characteristic mentioned above includes at least one of the following: Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream; Jitter associated with the periodicity; The maximum data burst size of the data burst in the service data stream; The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or The duration of the data burst that sends the service data stream.

23. The apparatus of claim 22, wherein the information indicating the at least one change in the at least one service characteristic associated with the QoS flow associated with the service data flow includes at least one of the following: Identifier of the configuration file At least one parameter identifier for the at least one business characteristic, or At least one value of the at least one business characteristic.

24. The apparatus of claim 22, wherein the information indicating at least one change of at least one service characteristic associated with the QoS flow associated with the service data flow is carried in: a downlink General Packet Radio Service Tunneling Protocol User Plane (GTP-U) packet of the QoS flow, a virtual GTP-U packet, or an information element including a GTP-U header.

25. The apparatus of claim 22, wherein the apparatus is further configured to: Send a response to the network indicating the status of receiving the information, the information indicating: at least one change in at least one service characteristic associated with the QoS flow associated with the service data flow.

26. The apparatus of claim 22, wherein the apparatus is configured to apply the change associated with the QoS flow based on the at least one change of the at least one service characteristic of the QoS flow by at least one of the following: After the QoS flow is established, the QoS profile of the QoS flow is changed based on at least one change in at least one service characteristic of the QoS flow associated with the service data flow. After the QoS flow is established, at least one connection mode discontinuous reception parameter is changed based on at least one change in the at least one service characteristic associated with the QoS flow related to the service data flow. or After the QoS flow is established, the scheduling of the QoS flow is changed based on at least one change in at least one service characteristic associated with the QoS flow related to the service data flow.

27. The apparatus of claim 22, wherein the apparatus is further configured to: Receive a request associated with establishing the QoS flow from the network, wherein the request includes: Information indicating at least one configuration file of at least one service characteristic associated with the QoS flow of the service data flow, the configuration file being adopted after the QoS flow is established.

28. The apparatus of claim 27, wherein the at least one configuration file comprises: An initial configuration file, which indicates that at least one initial value of the at least one service characteristic shall be initially adopted after the QoS flow is established.

29. The apparatus of claim 28, wherein the request further comprises: Indication of the time when the initial configuration file is used.

30. The apparatus of claim 27, wherein the information indicating the at least one configuration file includes at least one of the following: At least one identifier of the at least one configuration file; This includes configuration files containing one or more parameter identifiers for each business characteristic, or One or more values ​​for each business characteristic.

31. The apparatus of claim 27, wherein the apparatus is further configured to: After the QoS flow is established, based on the at least one change in the at least one service characteristic of the QoS flow, a minimum time value of the change associated with the QoS flow is sent to the network.

32. The apparatus of claim 27, wherein the apparatus is further configured to: Send a response to the network associated with establishing the QoS flow, wherein the response includes information indicating at least one initial value of the at least one service characteristic of the QoS flow, the at least one initial value to be initially adopted after the QoS flow is established.

33. A method for use in an application entity, the method comprising: Send information to the user plane function, the information indicating at least one change in at least one business characteristic associated with the service data stream; The at least one business characteristic mentioned above includes at least one of the following: Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream; The maximum data burst size of the data burst in the service data stream; The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or The duration of the data burst that sends the service data stream.

34. A method for use in application functionality, the method comprising: Send a request to the network associated with establishing a service data stream. The request includes information indicating at least one profile of at least one service characteristic of the service data stream, the at least one profile being available for use after a Quality of Service (QoS) stream associated with the service data stream is established; The at least one business characteristic mentioned above includes at least one of the following: Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream; Jitter associated with the periodicity; The maximum data burst size of the data burst in the service data stream; The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or The duration of the data burst that sends the service data stream.

35. A method for use in a user plane function, the method comprising: Detect at least one change in at least one business characteristic associated with one or more packets carried by the service data stream; as well as Sending information to network nodes, the information indicating at least one change in at least one service characteristic associated with the Quality of Service (QoS) flow of the service data flow; The at least one business characteristic mentioned above includes at least one of the following: Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream; Jitter associated with the periodicity; The maximum data burst size of the data burst in the service data stream; The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or The duration of the data burst that sends the service data stream.

36. A method for use in a network node, the method comprising: Information received from the network indicates at least one change in at least one service characteristic associated with a Quality of Service (QoS) flow related to a service data flow, and Based on the at least one change in the at least one service characteristic associated with the QoS flow related to the service data flow, apply the change associated with the QoS flow; The at least one business characteristic mentioned above includes at least one of the following: Periodicity, where periodicity is the time interval between the start of two data bursts in the service data stream; Jitter associated with the periodicity; The maximum data burst size of the data burst in the service data stream; The forward error correction rate associated with each data burst of the service data stream that is successfully decoded; or The duration of the data burst that sends the service data stream.

37. A computer-readable medium comprising instructions that, when executed by a device, cause the device to perform the method according to any one of claims 33 to 36.

Images