Multi-stream multiplexing identification method, device, equipment, storage medium and program product

Abstract

The application discloses a multi-flow multiplexing identification method and device, equipment, storage medium and program product, and relates to the technical field of communication, to support multi-flow multiplexing stream identification based on a multimedia transmission protocol. The method comprises the following steps: receiving first information sent by a first node, wherein the first information is used to indicate that a first service or application has a multi-flow multiplexing condition and / or has a multi-flow multiplexing identification demand; sending second information to the first node, wherein the second information is used to indicate a result responding to the first information; if the result indicates that multi-flow multiplexing identification of the first service or application is supported, performing multi-flow multiplexing identification on a data stream of the first service or application in a case where a service stream of the first service or application is received, and / or performing multi-flow multiplexing identification on a data stream of the first service or application identified based on the first information. The embodiment of the application can support multi-flow multiplexing stream identification based on a multimedia transmission protocol.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a multi-stream multiplexing identification method, apparatus, device, storage medium, and program product. Background Technology

[0002] Extended Reality (XR) and interactive media services can send data traffic of different media streams with different Quality of Service (QoS) requirements. Multiple media streams can be multiplexed over the same end-to-end transport layer connection.

[0003] To uniquely identify each media stream, IP packet filters can distinguish multiple media streams that share the same transport layer-related elements within the packet filter. However, existing solutions have limited applicability and cannot support the identification of multiplexed streams based on more multimedia transport protocols. Summary of the Invention

[0004] This application provides a multi-stream multiplexing identification method, apparatus, device, storage medium, and program product to support multi-stream multiplexing identification based on multimedia transmission protocols.

[0005] In a first aspect, embodiments of this application provide a multi-stream multiplexing identification method, applied to a first client, comprising:

[0006] Receive first information sent by the first node, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation and / or has a multi-stream multiplexing identification requirement;

[0007] Send a second message to the first node, the second message being used to indicate the result of responding to the first message;

[0008] If the result indicates support for multi-stream multiplexing identification of the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the first information.

[0009] Optionally, the first information includes one or more of the following:

[0010] Multi-stream multiplexing service activation instruction;

[0011] The identifier of the first service or application;

[0012] Stream description information;

[0013] User ID;

[0014] Security information;

[0015] Service enabler application layer data delivery (SEALDD) connection information;

[0016] Agreement information;

[0017] Multi-stream multiplexing identification information;

[0018] Information about the first node.

[0019] Optionally, the first information is also used to indicate the requirement of the first service to have multi-stream differentiated Quality of Service (QoS) guarantee, and the first information further includes: differentiated QoS information;

[0020] The method further includes:

[0021] Upon receiving the service flow of the first service or application, differentiated QoS guarantee is performed on the data flow of the first service or application, and / or, differentiated QoS guarantee is performed on the data flow identified by the first service or application based on the first information.

[0022] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0023] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0024] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0025] Agreement information;

[0026] Information about the location or domain of the stream type;

[0027] Attribute information;

[0028] Flow identification information;

[0029] Stream type meaning information.

[0030] Optionally, if the first client does not support multi-stream multiplexing identification for the first service or application, the result includes:

[0031] Information about the protocols supported by the first client.

[0032] Optionally, the method further includes:

[0033] Send third information to the Edge Execution Server (EES), the third information being used to discover the target first node, wherein the discovery of the target first node is based on the protocols supported by the first client and the protocols supported by the target first node;

[0034] Receive the fourth information sent by the EES, the fourth information including the information of the target first node.

[0035] Optionally, if the first node includes a SEALDD server, the receiving of the first information sent by the first node and the sending of the second information to the first node are performed during the process of establishing a SEALDD connection.

[0036] Optionally, different primary services or applications may support the same or different protocols.

[0037] Secondly, embodiments of this application provide a multi-stream multiplexing identification method, applied to a first node, including:

[0038] Receive the fifth information sent by the second node, the fifth information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement;

[0039] If multi-stream multiplexing identification is supported for the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the fifth information.

[0040] Optionally, the method further includes:

[0041] Send first information to the first client, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a need for multi-stream multiplexing identification.

[0042] Optionally, the first information includes one or more of the following:

[0043] Multi-stream multiplexing service activation instruction;

[0044] The identifier of the first service or application;

[0045] Stream description information;

[0046] User ID;

[0047] Security information;

[0048] SEALDD connection information;

[0049] Agreement information;

[0050] Multi-stream multiplexing identification information;

[0051] Information about the first node.

[0052] Optionally, the fifth piece of information includes one or more of the following:

[0053] Multi-stream multiplexing service activation instruction;

[0054] The identifier of the first service or application;

[0055] Stream description information;

[0056] User ID;

[0057] Security information;

[0058] SEALDD connection information;

[0059] Agreement information;

[0060] Multi-stream multiplexing identification information.

[0061] Optionally, the first information or the fifth information is further used to indicate that the first service has a requirement for multi-stream differentiated QoS guarantee, and the first information or the fifth information further includes: differentiated QoS information;

[0062] The method further includes:

[0063] Upon receiving the service flow of the first service or application, differentiated QoS guarantee is performed on the data flow of the first service, and / or differentiated QoS guarantee is performed on the data flow identified by the first service or application based on the first information.

[0064] Optionally, the differentiated QoS guarantee includes:

[0065] Send a sixth message to the third node, the sixth message indicating the QoS requirements needed for network assurance, the sixth message including at least one of the following:

[0066] User address;

[0067] First node identifier;

[0068] Stream description information;

[0069] QoS requirement information;

[0070] Flow characteristic information.

[0071] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0072] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0073] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0074] Agreement information;

[0075] Information about the location or domain of the stream type;

[0076] Attribute information;

[0077] Flow identification information;

[0078] Stream type meaning information.

[0079] Optionally, the first node includes a SEALDD server, and the method further includes:

[0080] A seventh message is sent to the second node, the seventh message being used to indicate the result of the first client's response to the first message and / or the result of the first node's response to the fifth message.

[0081] Optionally, if the first client and / or the first node does not support multi-stream multiplexing identification for the first service or application, the result includes: information on the protocols supported by the first client and / or the first node.

[0082] Optionally, the first node includes a User Plane Function (UPF), and the method further includes:

[0083] Send an eighth message to the second node, the eighth message being used to indicate whether the second node can obtain the service for multi-stream multiplexing identification.

[0084] Optionally, if the first node includes a SEALDD server, the receiving of the fifth information sent by the second node and the sending of the first information to the first client are performed during the process of establishing a SEALDD connection.

[0085] Optionally, if the first node includes a SEALDD server, the method further includes:

[0086] Send a ninth message to the Common API Framework (CAPIF) core functionality or EES, the ninth message indicating that the first node supports multi-stream multiplexing identification and / or differentiated QoS guarantees, the ninth message including at least one of the following:

[0087] First node identifier;

[0088] Supports multi-stream multiplexing identification;

[0089] Supported protocol information;

[0090] Supports multi-stream differentiated QoS services.

[0091] Thirdly, embodiments of this application provide a multi-stream multiplexing identification device, applied to a first client, comprising:

[0092] The first receiving module is used to receive first information sent by the first node, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation and / or has a multi-stream multiplexing identification requirement;

[0093] A first sending module is configured to send second information to the first node, wherein the second information is used to indicate the result of responding to the first information;

[0094] The first processing module is configured to, if the result indicates support for multi-stream multiplexing identification of the first service or application, perform multi-stream multiplexing identification on the data stream of the first service or application upon receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the first information.

[0095] Optionally, the first information includes one or more of the following:

[0096] Multi-stream multiplexing service activation instruction;

[0097] The identifier of the first service or application;

[0098] Stream description information;

[0099] User ID;

[0100] Security information;

[0101] Service-enabled application layer data transmission SEALDD connection information;

[0102] Agreement information;

[0103] Multi-stream multiplexing identification information;

[0104] Information about the first node.

[0105] Optionally, the first information is further used to indicate that the first service has a requirement for multi-stream differentiated quality of service (QoS) assurance, and the first information further includes: differentiated QoS information;

[0106] The device further includes:

[0107] The second processing module is configured to, upon receiving the service flow of the first service or application, perform differentiated QoS guarantee on the data flow of the first service or application, and / or perform differentiated QoS guarantee on the data flow identified by the first service or application based on the first information.

[0108] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0109] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0110] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0111] Agreement information;

[0112] Information about the location or domain of the stream type;

[0113] Attribute information;

[0114] Flow identification information;

[0115] Stream type meaning information.

[0116] Optionally, if the first client does not support multi-stream multiplexing identification for the first service or application, the result includes:

[0117] Information about the protocols supported by the first client.

[0118] Optionally, the device further includes:

[0119] The second sending module is used to send third information to the EES, the third information being used to discover the target first node, wherein the discovery of the target first node is based on the protocol supported by the first client and the protocol supported by the target first node;

[0120] Receive the fourth information sent by the EES, the fourth information including the information of the target first node.

[0121] Optionally, if the first node includes a SEALDD server, the receiving of the first information sent by the first node and the sending of the second information to the first node are performed during the process of establishing a SEALDD connection.

[0122] Optionally, different primary services or applications may support the same or different protocols.

[0123] Fourthly, embodiments of this application provide a multi-stream multiplexing identification device, applied to a first node, comprising:

[0124] The first receiving module is used to receive the fifth information sent by the second node. The fifth information is used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement.

[0125] The first processing module is configured to, if it supports multi-stream multiplexing identification for the first service or application, perform multi-stream multiplexing identification on the data stream of the first service or application upon receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the fifth information.

[0126] Optionally, the device further includes:

[0127] The first sending module is used to send first information to the first client, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement.

[0128] Optionally, the first information includes one or more of the following:

[0129] Multi-stream multiplexing service activation instruction;

[0130] The identifier of the first service or application;

[0131] Stream description information;

[0132] User ID;

[0133] Security information;

[0134] SEALDD connection information;

[0135] Agreement information;

[0136] Multi-stream multiplexing identification information;

[0137] Information about the first node.

[0138] Optionally, the fifth piece of information includes one or more of the following:

[0139] Multi-stream multiplexing service activation instruction;

[0140] The identifier of the first service or application;

[0141] Stream description information;

[0142] User ID;

[0143] Security information;

[0144] SEALDD connection information;

[0145] Agreement information;

[0146] Multi-stream multiplexing identification information.

[0147] Optionally, the first information or the fifth information is further used to indicate that the first service has a requirement for multi-stream differentiated QoS guarantee, and the first information or the fifth information further includes: differentiated QoS information;

[0148] The device further includes:

[0149] The second processing module is used to perform differentiated QoS guarantee on the data stream of the first service when the service stream of the first service or application is received, and / or to perform differentiated QoS guarantee on the data stream identified by the first service or application based on the first information.

[0150] Optionally, the apparatus further includes: a third processing module, configured to send sixth information to a third node, the sixth information indicating QoS requirements for network assurance, the sixth information including at least one of the following:

[0151] User address;

[0152] First node identifier;

[0153] Stream description information;

[0154] QoS requirement information;

[0155] Flow characteristic information.

[0156] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0157] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0158] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0159] Agreement information;

[0160] Information about the location or domain of the stream type;

[0161] Attribute information;

[0162] Flow identification information;

[0163] Stream type meaning information.

[0164] Optionally, the first node includes a SEALDD server, and the apparatus further includes:

[0165] The third sending module is used to send a seventh message to the second node, the seventh message being used to indicate the result of the first client's response to the first message and / or the result of the first node's response to the fifth message.

[0166] Optionally, if the first client and / or the first node does not support multi-stream multiplexing identification for the first service or application, the result includes: information on the protocols supported by the first client and / or the first node.

[0167] Optionally, the first node includes a UPF, and the device further includes:

[0168] The fourth sending module is used to send eighth information to the second node, the eighth information being used to indicate whether the second node can obtain the service for multi-stream multiplexing identification.

[0169] Optionally, if the first node includes a SEALDD server, the receiving of the fifth information sent by the second node and the sending of the first information to the first client are performed during the process of establishing a SEALDD connection.

[0170] Optionally, if the first node includes a SEALDD server, the apparatus further includes:

[0171] The fifth sending module is used to send the ninth message to the CAPIF core function or EES. The ninth message is used to indicate that the first node supports multi-stream multiplexing identification and / or differentiated QoS guarantee. The ninth message includes at least one of the following:

[0172] First node identifier;

[0173] Supports multi-stream multiplexing identification;

[0174] Supported protocol information;

[0175] Supports multi-stream differentiated QoS services.

[0176] Fifthly, embodiments of this application provide a multi-stream multiplexing identification device applied to a first client, comprising: a processor and a transceiver; wherein the processor is used for:

[0177] Receive first information sent by the first node, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation and / or has a multi-stream multiplexing identification requirement;

[0178] Send a second message to the first node, the second message being used to indicate the result of responding to the first message;

[0179] If the result indicates support for multi-stream multiplexing identification of the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the first information.

[0180] Optionally, the first information includes one or more of the following:

[0181] Multi-stream multiplexing service activation instruction;

[0182] The identifier of the first service or application;

[0183] Stream description information;

[0184] User ID;

[0185] Security information;

[0186] Service-enabled application layer data transmission SEALDD connection information;

[0187] Agreement information;

[0188] Multi-stream multiplexing identification information;

[0189] Information about the first node.

[0190] Optionally, the first information is further used to indicate that the first service has a requirement for multi-stream differentiated QoS guarantees, and the first information further includes: differentiated QoS information; the processor is further used to:

[0191] Upon receiving the service flow of the first service or application, differentiated QoS guarantee is performed on the data flow of the first service or application, and / or, differentiated QoS guarantee is performed on the data flow identified by the first service or application based on the first information.

[0192] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0193] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0194] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0195] Agreement information;

[0196] Information about the location or domain of the stream type;

[0197] Attribute information;

[0198] Flow identification information;

[0199] Stream type meaning information.

[0200] Optionally, if the first client does not support multi-stream multiplexing identification for the first service or application, the result includes:

[0201] Information about the protocols supported by the first client.

[0202] Optionally, the processor is further configured to: send third information to the edge execution server EES, the third information being used to discover the target first node, wherein the discovery of the target first node is based on the protocol supported by the first client and the protocol supported by the target first node;

[0203] Receive the fourth information sent by the EES, the fourth information including the information of the target first node.

[0204] Optionally, if the first node includes a SEALDD server, the receiving of the first information sent by the first node and the sending of the second information to the first node are performed during the process of establishing a SEALDD connection.

[0205] Optionally, different primary services or applications may support the same or different protocols.

[0206] Sixthly, embodiments of this application provide a multi-stream multiplexing identification device applied to a first node, comprising: a processor and a transceiver; wherein the processor is used for:

[0207] Receive the fifth information sent by the second node, the fifth information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement;

[0208] If multi-stream multiplexing identification is supported for the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the fifth information.

[0209] Optionally, the processor is further configured to: send first information to a first client, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement.

[0210] Optionally, the first information includes one or more of the following:

[0211] Multi-stream multiplexing service activation instruction;

[0212] The identifier of the first service or application;

[0213] Stream description information;

[0214] User ID;

[0215] Security information;

[0216] SEALDD connection information;

[0217] Agreement information;

[0218] Multi-stream multiplexing identification information;

[0219] Information about the first node.

[0220] Optionally, the fifth piece of information includes one or more of the following:

[0221] Multi-stream multiplexing service activation instruction;

[0222] The identifier of the first service or application;

[0223] Stream description information;

[0224] User ID;

[0225] Security information;

[0226] SEALDD connection information;

[0227] Agreement information;

[0228] Multi-stream multiplexing identification information.

[0229] Optionally, the first information or the fifth information is further used to indicate that the first service has a requirement for multi-stream differentiated QoS guarantee, and the first information or the fifth information further includes: differentiated QoS information; the processor is further used to:

[0230] Upon receiving the service flow of the first service or application, differentiated QoS guarantee is performed on the data flow of the first service, and / or differentiated QoS guarantee is performed on the data flow identified by the first service or application based on the first information.

[0231] Optionally, the processor is further configured to perform differentiated QoS guarantees, including:

[0232] Send a sixth message to the third node, the sixth message indicating the QoS requirements needed for network assurance, the sixth message including at least one of the following:

[0233] User address;

[0234] First node identifier;

[0235] Stream description information;

[0236] QoS requirement information;

[0237] Flow characteristic information.

[0238] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0239] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0240] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0241] Agreement information;

[0242] Information about the location or domain of the stream type;

[0243] Attribute information;

[0244] Flow identification information;

[0245] Stream type meaning information.

[0246] Optionally, the first node includes: a SEALDD server, and the processor is further configured to:

[0247] A seventh message is sent to the second node, the seventh message being used to indicate the result of the first client's response to the first message and / or the result of the first node's response to the fifth message.

[0248] Optionally, if the first client and / or the first node does not support multi-stream multiplexing identification for the first service or application, the result includes: information on the protocols supported by the first client and / or the first node.

[0249] Optionally, the first node includes a UPF, and the processor is further configured to:

[0250] Send an eighth message to the second node, the eighth message being used to indicate whether the second node can obtain the service for multi-stream multiplexing identification.

[0251] Optionally, if the first node includes a SEALDD server, the receiving of the fifth information sent by the second node and the sending of the first information to the first client are performed during the process of establishing a SEALDD connection.

[0252] Optionally, if the first node includes a SEALDD server, the processor is further configured to:

[0253] Send a ninth message to the CAPIF core function or EES, the ninth message being used to indicate that the first node supports multi-stream multiplexing identification and / or differentiated QoS guarantee, the ninth message including at least one of the following:

[0254] First node identifier;

[0255] Supports multi-stream multiplexing identification;

[0256] Supported protocol information;

[0257] Supports multi-stream differentiated QoS services.

[0258] In a seventh aspect, embodiments of this application also provide a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps in the multi-stream multiplexing identification method as described above.

[0259] Eighthly, embodiments of this application also provide a readable storage medium storing a program that, when executed by a processor, implements the steps in the multi-stream multiplexing identification method as described above.

[0260] In a ninth aspect, embodiments of this application also provide a computer program product, including computer instructions, which, when executed by a processor, implement the steps in the multi-stream multiplexing identification method as described above.

[0261] In this embodiment of the application, the first client or the first node may, based on the first information or the fifth information, perform multi-stream multiplexing identification on the data stream of the first service or application upon receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the first information, thereby supporting multi-stream multiplexing stream identification based on multimedia transmission protocols. Attached Figure Description

[0262] Figure 1 This is one of the flowcharts of the multi-stream multiplexing identification method provided in the embodiments of this application;

[0263] Figure 2 This is the second flowchart of the multi-stream multiplexing identification method provided in the embodiments of this application;

[0264] Figure 3 This is the third flowchart of the multi-stream multiplexing identification method provided in the embodiments of this application;

[0265] Figure 4 This is the fourth flowchart of the multi-stream multiplexing identification method provided in the embodiments of this application;

[0266] Figure 5 This is a schematic diagram illustrating the process of the VAL server selecting the SEALDD server in an embodiment of this application;

[0267] Figure 6 This is a schematic diagram illustrating the process of a SEALDD client selecting a SEALDD server in an embodiment of this application;

[0268] Figure 7 This is the fifth flowchart of the multi-stream multiplexing identification method provided in the embodiments of this application;

[0269] Figure 8 This is one of the structural diagrams of the multi-stream multiplexing identification device provided in the embodiments of this application;

[0270] Figure 9 This is the second structural diagram of the multi-stream multiplexing identification device provided in the embodiments of this application;

[0271] Figure 10 This is the third structural diagram of the multi-stream multiplexing identification device provided in the embodiments of this application;

[0272] Figure 11 This is the fourth structural diagram of the multi-stream multiplexing identification device provided in the embodiments of this application. Detailed Implementation

[0273] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0274] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0275] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0276] See Figure 1 , Figure 1 The flowchart of the multi-stream multiplexing identification method provided in this application embodiment is applied to the first client, such as... Figure 1 As shown, it includes the following steps:

[0277] Step 101: Receive first information sent by the first node, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation and / or has a multi-stream multiplexing identification requirement.

[0278] The first node includes, but is not limited to, a SEALDD server, a UPF, etc., and the first client includes, but is not limited to, a SEALDD client, a terminal, etc. The first information includes one or more of the following:

[0279] Multi-stream multiplexing service enable instruction, used to indicate whether multi-stream multiplexing service is enabled;

[0280] The identifier of the first service or application, such as an ID;

[0281] Flow description information, which can be a flow description or a packet-level identifier / description;

[0282] User identifiers, such as IDs;

[0283] Security information is used for identity authentication, authorization, etc.

[0284] SEALDD connection information, such as SEALDD Connection ID;

[0285] Protocol information, including protocol name, version number, etc.;

[0286] Multi-stream multiplexing identification information;

[0287] Information about the first node, such as ID.

[0288] The first information is further used to indicate that the first service has a requirement for multi-stream differentiated QoS guarantee. The first information also includes: differentiated QoS information. Then, the first client can also perform differentiated QoS guarantee on the data stream of the first service or application when receiving the service stream of the first service or application, and / or perform differentiated QoS guarantee on the data stream identified by the first service or application based on the first information.

[0289] The differentiated QoS information refers to the different QoS requirements for different flows, which may include latency, bandwidth, reliability, packet loss rate, and service requirements such as slicing requirements and redundant transmission requirements. The differentiated QoS guarantee refers to the QoS requirement guarantee provided for the different QoS requirements of different flows, such as QoS requirement guarantees for different flows' latency, bandwidth, reliability, packet loss rate, slicing requirements, and redundant transmission requirements.

[0290] In this embodiment, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in a multi-stream multiplexed stream. Specifically, the multi-stream multiplexing identification information is carried through a first position or first field in the protocol header or extension header; alternatively, the multi-stream multiplexing identification information is indicated by a first file; or, the multi-stream multiplexing identification information is indicated by first information in a first file.

[0291] Wherein, the first location or first field can be any location or field, such as the opcode of a WebSocket protocol definition; the first file can be any file, such as an MPEG-DASH Media Presentation Description (MPD) file; the first information can be any information from the first file. Wherein, the multi-stream multiplexing identification information includes at least one of the following:

[0292] Protocol information, including protocol name, version number, etc.;

[0293] Information about the location or domain of the stream type. There may be one or more locations or domains, such as location information, domain information, file information, etc.

[0294] Attribute information, such as attribute information indicating the stream type;

[0295] Stream identification information, such as identification information indicating the stream type;

[0296] The stream type information includes one or more stream types, and there may be a certain correspondence between the stream type meaning and the stream type location or domain name information. Stream types may include, for example, audio streams, video streams, haptic streams, etc.

[0297] For example, in this embodiment of the application, a signal can be sent to the haptic media via an MPEG-DASH Media Presentation Description (MPD) file to achieve adaptive media transmission. The MPD with a MIME type of "haptic / mp4" indicates a haptic stream. The multi-stream multiplexing identification information provided in this scenario may include:

[0298] (MPEG-DASH, MIME type, {"haptic / mp4"-haptic}; {"video / mp4"-video}).

[0299] Among them, MPEG-DASH is the protocol information, and MIME type is the attribute information, which indicates the stream type. {"haptic / mp4"-haptic} and {"video / mp4"-video} are the stream type meaning information, respectively.

[0300] For example, based on certain protocols, it can be defined or negotiated that a certain field in the protocol's packet header / extension header can be used to carry multi-stream multiplexing identification information to indicate the stream type. For instance, the protocol defines the WebSocket opcode as follows: 1 indicates a text type (string) data packet; 2 indicates a binary data type ([]byte) data packet; 8 indicates a connection closure signal; 3 indicates video stream data; 4 indicates audio stream data, and so on.

[0301] In the embodiments of this application, the first service or application can be any service or application, and different first services or applications may support the same or different protocols, thereby supporting the identification of multiple streams multiplexing of multiple protocols.

[0302] Step 102: Send a second message to the first node, the second message being used to indicate the result of responding to the first message.

[0303] The result indicates whether the first client supports or does not support multi-stream multiplexing identification for the first service or application. If it does not support it, the result may also include information about the protocols supported by the first client, such as the protocol name and version number.

[0304] Step 103: If the result indicates support for multi-stream multiplexing identification of the first service or application, upon receiving the service flow of the first service or application, perform multi-stream multiplexing identification on the data flow of the first service or application, and / or perform multi-stream multiplexing identification on the data flow identified by the first service or application based on the first information.

[0305] In this embodiment of the application, the first client can, based on the first information, perform multi-stream multiplexing identification on the data stream of the first service or application upon receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the first information, thereby supporting multi-stream multiplexing stream identification based on multimedia transmission protocols.

[0306] Corresponding to the first node being a SEALDD server, the first client can be a SEALDD client. In this embodiment, the first client can select a SEALDD server for connection. Therefore, the first client can send third information to the EES, which is used to discover the target first node. The discovery of the target first node is based on the protocols supported by the first client and the protocols supported by the target first node. That is, the purpose of discovering the target first node is to find a target first node whose supported protocols are the same as those supported by the first client. The EES stores information about the SEALDD server. Afterwards, the first client receives fourth information sent by the EES, which includes information about the target first node, such as supported protocols. The target first node may include the aforementioned first node. The third information may, for example, be a request to discover a bundled Edge Application Service (EAS). The second node may be a Vertical Application Server (VAL Server), Application Function (AF), Application Server (AS), etc.

[0307] in, Figure 1 Steps 101 and 102 of the illustrated embodiment can be executed after a SEALDD connection has been established between the first client and the SEALDD server. However, for... Figure 1 The receiving of the first information sent by the first node and the sending of the second information to the first node (steps 101 and 102) can also be performed during the establishment of the SEALDD connection. That is, during the establishment phase of the SEALDD connection, the first client and the SEALDD server can negotiate multi-stream multiplexing identification and differentiated QoS requirements.

[0308] See Figure 2 , Figure 2 This is a flowchart of the multi-stream multiplexing identification method provided in the embodiments of this application, applied to the first node, such as... Figure 2 As shown, it includes the following steps:

[0309] Step 201: Receive the fifth information sent by the second node, the fifth information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement.

[0310] The second node can be AF, AS, etc. The fifth piece of information includes one or more of the following:

[0311] Multi-stream multiplexing service enable instruction, used to indicate whether multi-stream multiplexing service is enabled;

[0312] The identifier of the first service or application, such as an ID;

[0313] Flow description information, which can be a flow description or a packet-level identifier / description;

[0314] User identifiers, such as IDs;

[0315] Security information is used for identity authentication, authorization, etc.

[0316] SEALDD connection information, such as SEALDD Connection ID;

[0317] Protocol information, including protocol name, version number, etc.;

[0318] Multi-stream multiplexing identification information.

[0319] Optionally, the first node may also send first information to the first client, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement, so that the first client can perform multi-stream multiplexing identification on the data stream of the first service or application when receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the first information.

[0320] The meaning of the first information can be as described in the foregoing embodiments, and the specific interpretation of the multi-stream multiplexing identification information can also refer to the foregoing embodiments.

[0321] The fifth information is further used to indicate that the first service has a requirement for multi-stream differentiated quality of service (QoS) assurance. The fifth information also includes differentiated QoS information. Therefore, the first node can also perform differentiated QoS assurance on the data stream of the first service when it receives the service stream of the first service or application, and / or perform differentiated QoS assurance on the data stream identified by the first service or application based on the first information.

[0322] The differentiated QoS information refers to the different QoS requirements for different flows, which may include latency, bandwidth, reliability, packet loss rate, and service requirements such as slicing requirements and redundant transmission requirements. The differentiated QoS guarantee refers to the QoS requirement guarantee provided for the different QoS requirements of different flows, such as QoS requirement guarantees for different flows' latency, bandwidth, reliability, packet loss rate, slicing requirements, and redundant transmission requirements.

[0323] In the case of differentiated QoS assurance, the first node sends a sixth message to the third node, which indicates the QoS requirements for network assurance (AF session with required QoS service). The third node can be a Network Exposure Function (NEF) or a Policy Control Function (PCF). The sixth message includes at least one of the following:

[0324] User address, such as the address of the first client;

[0325] First node identifier;

[0326] Stream description information, different stream description information corresponds to different streams identified, such as multi-stream multiplexing identification information corresponding to the identified audio stream and control stream, and / or different flow labels or different types of services (TOS);

[0327] QoS requirement information includes: QoS reference or independent QoS parameters, Alternative Service Requirements, QoS monitoring requirements, L4S ECN Marking Indication, Data Burst Size Marking Support Indication, and Time to Next Burst Support Indication.

[0328] Flow characteristic information includes: flow direction, burst arrival time at UE (uplink) or UPF (downlink), periodicity, time domain, survival time, burst arrival time (BAT) adaptability or BAT window capability, period range, etc.

[0329] In this embodiment, the first node may also send a seventh message to the second node, the seventh message being used to indicate the result of the first client's response to the first message and / or the result of the first node's response to the fifth message. If the first client and / or the first node does not support multi-stream multiplexing identification for the first service or application, the result includes: information about the protocols supported by the first client and / or the first node.

[0330] If the first node is a UPF, the UPF can also send an eighth message to the second node, which indicates whether the second node can obtain the service for multi-stream multiplexing identification. The UPF sends this eighth message to the second node via a PCF or NEF. If the eighth message indicates that the second node cannot obtain the service for multi-stream multiplexing identification, the process can end. If the first node includes a SEALDD server, receiving the fifth message from the second node and sending the first message to the first client are performed during the establishment of the SEALDD connection. That is, the above process can be performed either when the first client and the SEALDD server have established a connection, or during the process of establishing a connection between the first client and the SEALDD server.

[0331] Step 202: If multi-stream multiplexing identification is supported for the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the fifth information.

[0332] In this embodiment of the application, the first node may, based on the fifth information, perform multi-stream multiplexing identification on the data stream of the first service or application upon receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the first information, thereby supporting multi-stream multiplexing stream identification based on multimedia transmission protocols.

[0333] In this embodiment of the application, if the first node includes a SEALDD server, the SEALDD server may also send a ninth message to the core functionality of the general API framework CAPIF or EES. The ninth message is used to indicate that the first node supports multi-stream multiplexing identification and / or differentiated QoS guarantee. The ninth message includes at least one of the following:

[0334] First node identifier;

[0335] Supports multi-stream multiplexing identification;

[0336] Supported protocol information, including protocol name, version number, etc.;

[0337] Supports multi-stream differentiated QoS services, such as redundant transmission and bandwidth limiting.

[0338] exist Figure 3 In the illustrated embodiment, the SEALDD server is the first node, and the SEALDD client is the first client. Assuming that the SEALDD server and SEALDD client have already established a SEALDD connection, this embodiment may include the following steps:

[0339] Step 301: AF / AS sends a multi-stream multiplexing identification request to the SEALDD server to indicate that a certain service or application has multi-stream multiplexing and / or has a need for multi-stream multiplexing identification. Furthermore, it can also indicate that the service or application has a need for differentiated QoS guarantees.

[0340] The information carried in the request includes one or more of the following: the identifier of the service / application, the flow identifier, the user identifier, the SEALDD Connection ID, the multi-stream multiplexing service enable instruction, the protocol information, the multi-stream multiplexing identification information (such as protocol, location / domain name, value-meaning, etc.), and the corresponding differentiated QoS information.

[0341] Step 302: After receiving the request, the SEALDD server sends one or more of the following messages to the SEALDD client:

[0342] The service / application identifier, flow identifier, user identifier, SEALDD Connection ID, multi-stream multiplexing service enable indication, protocol information, multi-stream multiplexing identification information (e.g., protocol, location / domain name, value-meaning, etc.), corresponding differentiated QoS information, and SEALDD server information.

[0343] The selection of the SEALDD server and the SEALDD client can be based on the user identifier, the SEALDD Connection ID, or both.

[0344] Step 303: The SEALDD client determines whether it can identify multi-stream multiplexing and perform QoS differentiation guarantees for uplink (UL) traffic based on the above information, such as whether it supports parsing the above protocols.

[0345] Step 304: The SEALDD client returns the configuration result. Optionally, if the SEALDD client does not support the protocol specified in this AF / AS, a protocol supported by the SEALDD client can be sent.

[0346] Step 305: Based on its own multi-stream multiplexing identification policy configuration result and the result sent by the SEALDD client, the SEALDD server returns the overall result to the AF / AS. Optionally, if the SEALDD server does not support the protocol specified by the AF / AS, it can send a list of protocols supported by the SEALDD server for the VAL server to further select and re-initiate. Optionally, protocols supported by the SEALDD client may also be included.

[0347] Step 306: If there is a downlink service flow, the SEALDD server identifies and marks the traffic that matches the service / application identifier, flow identifier, and other information based on the multi-stream multiplexing identification information. Optionally, it can further perform differentiated QoS guarantees based on the corresponding differentiated QoS information, such as bandwidth limiting, providing slicing services, providing redundant transmission requirements, and using AFsessionWithQoS service to guarantee latency, bandwidth, reliability, packet loss rate, etc.

[0348] Step 307: If there is an uplink service flow, the SEALDD client identifies the traffic that matches the service / application identifier, flow identifier, and other information based on the multi-flow multiplexing identification information, and performs differentiated QoS protection based on the corresponding differentiated QoS information, such as bandwidth limiting.

[0349] like Figure 4 As shown, the SEALDD server is the first node, and the SEALDD client is the first client. During the SEALDD connection establishment phase, the SEALDD server and SEALDD client can negotiate multi-stream multiplexing identification and differentiated QoS requirements, including:

[0350] Step 401: The Vertical Application Layer (VAL) server decides to use the SEALDD service to transmit application signaling and allocates SEALDD-S connection information to receive application signaling traffic from the SEALDD server. The VAL server sends an Sdd_RegularTransmission request to the SEALDD server, which carries: flow identifier, user identifier, multi-stream multiplexing service enable indication, protocol information, multi-stream multiplexing identification information (e.g., protocol, location / domain name, value-meaning, etc.) and corresponding differentiated QoS information.

[0351] Step 402: Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server allocates a specific address for transmitting SEALDD signaling traffic with the incoming SEALDD client and returns a response (Sdd_RegularTransmission response) to the VAL server.

[0352] Step 403: The VAL client sends a SEALDD service request to the SEALDD client. This service request also instructs the establishment of an application signaling transport connection. The VAL client receives a SEALDD service response from the SEALDD client. This response indicates whether the SEALDD service request was successful.

[0353] Step 404: The VAL / SEALDD client discovers and selects a suitable SEALDD server for the VAL application. After this step, the VAL server and its associated SEALDD server are discovered and selected, and the SEALDD client can obtain the address of the SEALDD server.

[0354] Step 405: The SEALDD client assigns a SEALDD-UU flow ID and maps it to application signaling traffic for application signaling transmission. The SEALDD client sends an Sdd_RegularTransmissionConnection_Establish request to the SEALDD server. This request includes the SEALDD client ID, SEALDD-UU flow ID, VAL server ID, VAL service ID, and the SEALDD client's SEALDD traffic descriptor (i.e., the SEALDD-S connection information used by the SEALDD client to receive downlink SEALDD-UU signaling traffic). The request message also includes the selected VAL server endpoint information. The SEALDD server retrieves the location information of the VALUE or SEALDD client from the defined Service Environment And Link Discovery (SEAL) Location Management (LM) service and verifies it according to the geofencing policy configured on the VAL server to allow or restrict the establishment of the signaling connection. If the location information matches the configured geofencing policy, the SEALDD server allows the establishment of the signaling connection; otherwise, the SEALDD server returns a failure result (e.g., connection rejection).

[0355] Step 406: The SEALDD server returns a response (Sdd_RegularTransmissionConnection_Establish_response) to the SEALDD client. The response contains the SEALDD traffic descriptor on the SEALDD server side (such as SEALDD-S connection information and transport layer protocol), which is mapped to the application traffic.

[0356] Step 407: The SEALDD server stores the SEALDD client ID and SEALDD-UU flow ID to identify SEALDD-UU signaling traffic and establishes a SEALDD-S connection with the VAL server so that VAL clients can transmit application signaling traffic mapped to SEALDD traffic. The SEALDD server may use different SEALDD connection information to establish SEALDD-S signaling transmission connections for different SEALDD clients and SEALDD-UU flows to achieve application signaling transmission to the VAL server. Therefore, each VAL client will have a different SEALDD-S signaling transmission connection on the SEALDD server side.

[0357] Step 408: The SEALDD client uses the SEALDD traffic descriptor on the SEALDD server to establish a SEALDD signaling connection. Upon receiving this request, the SEALDD server sends the service / application identifier, flow identifier, protocol information, multi-stream multiplexing identification information (e.g., protocol, location, value-meaning, etc.), corresponding differentiated QoS information, and SEALDD server information to the SEALDD client. The SEALDD client, upon receiving this information, determines whether it can perform multi-stream multiplexing identification and QoS differentiation guarantees for UL traffic based on the above, for example, whether it supports parsing the aforementioned protocols. The SEALDD client returns the configuration result. Optionally, if the SEALDD client does not support the protocol specified by the VAL server, it can send a protocol that the SEALDD client supports. The SEALDD server, based on its own multi-stream multiplexing identification policy configuration result and the result sent by the SEALDD client, returns the overall result to the VAL server. Optionally, if the SEALDD server does not support the protocol specified by the VAL server, it can send a protocol that the SEALDD server supports for the VAL server to further select and re-initiate.

[0358] In this embodiment, before the SEALDD connection is established, the SEALDD server can indicate the protocol types it supports, and AF / AS can be filtered when the SEALDD server discovers the connection. Figure 5 The illustrated embodiment shows the process by which the VALserver selects the SEALDD server, which may include:

[0359] Step 501: The SEALDD server sends a Service API publish or registration request to the CAPIF Core Function (CCF), carrying information that the SEALDD server supports multi-stream multiplexing identification based on the parsing protocol, and / or supports services with differentiated QoS for multiple streams.

[0360] If you reuse the Service API publish, you can specify in the Service API information description or a new instruction that the SEALDD server supports one or more of the following: multi-stream multiplexing identification based on the resolution protocol, SEALDD server identification, supported protocol for multiplexed mediaflows and / or differentiated QoS, and supported protocol information.

[0361] Step 502: The CAPIF Core Function sends a Service API publish or register response.

[0362] Steps 503-504: The VAL server sends a Service API discovery or discovery request to the CCF, carrying the SEALDD service ID, the protocols to be supported, and services that support differentiated QoS. Based on the VAL server's request, the CCF returns information about SEALDD servers that meet the requirements through the Service API discovery or discovery response.

[0363] exist Figure 6 The illustrated embodiment shows the process by which a SEALDD client selects a SEALDD server, including:

[0364] Step 601: The SEALDD server sends an EAS registration message to the EES server, indicating support for multi-stream multiplexing identification based on parsing protocols, support for differentiated QoS services, and supported protocol information (e.g., via EASFeature(s)).

[0365] Step 602: Select SEALDD server for VAL server. See the detailed process for reference. Figure 5 The illustrated embodiment shows the process of VALserver selecting SEALDD server.

[0366] Steps 603-604: The VAL server subscribes to the SEALDD service. For example, if the SEALDD server supports an update to the protocol, it can provide the updated information to the VAL server.

[0367] Step 605: VALserver sends EAS registration to EES server, carrying the information of the selected SEALDDserver.

[0368] Step 606: The VAL / SEALDD client initiates a VAL server / SEALDD server discovery procedure (EASdiscovery procedure) to EES, and can select a SEALDD server that supports the required protocol.

[0369] In one embodiment of this application, reference is made to Figure 7 In UPF-based multi-stream multiplexing flow identification based on multi-stream multiplexing flow flag negotiation, it can include:

[0370] Step 701: The AF sends a multi-stream multiplexing identification request to the PCF / NEF to indicate that a certain service or application has multi-stream multiplexing and / or has a need for multi-stream multiplexing identification. Furthermore, it can also indicate that the service or application has a need for differentiated QoS guarantees. The request carries one or more of the following information: the identifier of the service / application, flow identifier, user identifier, SEALDD Connection ID, multi-stream multiplexing service enable indication, protocol information, multi-stream multiplexing identification information (e.g., protocol, location / domain name, value-meaning, etc.), and corresponding differentiated QoS information. Upon receiving the request, the NEF / PCF forwards it to the UPF.

[0371] Step 702: After receiving the request, the UPF determines whether the AF / AS can obtain the service and whether identification based on the multi-stream multiplexing identification information can be achieved.

[0372] Step 703: If yes, the differentiated QoS requirements are converted into differentiated QoS information, and the UPF sends a multi-stream multiplexing identification request response to the AF / AS via the PCF / NEF. If no, the process ends after the UPF sends a multi-stream multiplexing identification request response to the AF / AS via the PCF / NEF.

[0373] Steps 704-705: If the AF / AS can obtain the service, the NEF / PCF will send the received service / application identifier, flow identifier, protocol information, multi-stream multiplexing identification information (such as protocol, location, value-meaning, etc.) and corresponding differentiated QoS information to the Session Management Function (SMF), and then send it to the UPF.

[0374] Steps 706-707: If the AF / AS can obtain the service, the NEF / PCF will send the received service / application identifier, flow identifier, protocol information, multi-stream multiplexing identification information (e.g., protocol, location, value-meaning, etc.), and corresponding differentiated QoS information to the User Equipment (UE) / Radio Access Network (RAN). The selection of UE / RAN can be based on the user identifier.

[0375] Step 708: If there is a downlink service flow, the UPF identifies the multi-stream multiplexing traffic based on the multi-stream multiplexing identification information for traffic that matches the service / application identifier, flow identifier, and other information, and performs differentiated QoS guarantee based on the corresponding differentiated QoS information.

[0376] Step 709: If there is an uplink service flow, the UE / RAN identifies the multi-stream multiplexing traffic based on the multi-stream multiplexing identification information for traffic that conforms to the service / application identifier, flow identifier, and other information, and performs differentiated QoS guarantee based on the corresponding differentiated QoS information.

[0377] See Figure 8 , Figure 8 This is a structural diagram of the multi-stream multiplexing identification device provided in an embodiment of this application, applied to a first client. For example... Figure 8 As shown, the multi-stream multiplexing identification device includes:

[0378] The first receiving module 801 is configured to receive first information sent by the first node, the first information indicating that the first service or application has a multi-stream multiplexing situation and / or a multi-stream multiplexing identification requirement; the first sending module 802 is configured to send second information to the first node, the second information indicating the result in response to the first information; the first processing module 803 is configured to, if the result indicates support for multi-stream multiplexing identification of the first service or application, perform multi-stream multiplexing identification on the data stream of the first service or application upon receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the first information.

[0379] Optionally, the first information includes one or more of the following:

[0380] Multi-stream multiplexing service activation instruction;

[0381] The identifier of the first service or application;

[0382] Stream description information;

[0383] User ID;

[0384] Security information;

[0385] Service-enabled application layer data transmission SEALDD connection information;

[0386] Agreement information;

[0387] Multi-stream multiplexing identification information;

[0388] Information about the first node.

[0389] Optionally, the first information is further used to indicate that the first service has a requirement for multi-stream differentiated quality of service (QoS) assurance, and the first information further includes: differentiated QoS information; the device further includes:

[0390] The second processing module is configured to, upon receiving the service flow of the first service or application, perform differentiated QoS guarantee on the data flow of the first service or application, and / or perform differentiated QoS guarantee on the data flow identified by the first service or application based on the first information.

[0391] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0392] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0393] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0394] Agreement information;

[0395] Information about the location or domain of the stream type;

[0396] Attribute information;

[0397] Flow identification information;

[0398] Stream type meaning information.

[0399] Optionally, if the first client does not support multi-stream multiplexing identification for the first service or application, the result includes:

[0400] Information about the protocols supported by the first client.

[0401] Optionally, the device further includes:

[0402] The second sending module is used to send third information to the EES, the third information being used to discover the target first node, wherein the discovery of the target first node is based on the protocol supported by the first client and the protocol supported by the target first node;

[0403] Receive the fourth information sent by the EES, the fourth information including the information of the target first node.

[0404] Optionally, if the first node includes a SEALDD server, the receiving of the first information sent by the first node and the sending of the second information to the first node are performed during the process of establishing a SEALDD connection.

[0405] Optionally, different primary services or applications may support the same or different protocols.

[0406] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0407] See Figure 9 , Figure 9 This is a structural diagram of the multi-stream multiplexing identification device provided in an embodiment of this application, applied to the first node. For example... Figure 9 As shown, the multi-stream multiplexing identification device includes:

[0408] The first receiving module 901 is configured to receive fifth information sent by the second node, the fifth information indicating that the first service or application has multi-stream multiplexing and / or has a need for multi-stream multiplexing identification; the first processing module 902 is configured to, if multi-stream multiplexing identification of the first service or application is supported, perform multi-stream multiplexing identification on the data stream of the first service or application upon receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the fifth information.

[0409] Optionally, the device further includes:

[0410] The first sending module is used to send first information to the first client, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement.

[0411] Optionally, the first information includes one or more of the following:

[0412] Multi-stream multiplexing service activation instruction;

[0413] The identifier of the first service or application;

[0414] Stream description information;

[0415] User ID;

[0416] Security information;

[0417] SEALDD connection information;

[0418] Agreement information;

[0419] Multi-stream multiplexing identification information;

[0420] Information about the first node.

[0421] Optionally, the fifth piece of information includes one or more of the following:

[0422] Multi-stream multiplexing service activation instruction;

[0423] The identifier of the first service or application;

[0424] Stream description information;

[0425] User ID;

[0426] Security information;

[0427] SEALDD connection information;

[0428] Agreement information;

[0429] Multi-stream multiplexing identification information.

[0430] Optionally, the first information or the fifth information is further used to indicate that the first service has a requirement for multi-stream differentiated QoS guarantee, and the first information or the fifth information further includes: differentiated QoS information;

[0431] The device further includes:

[0432] The second processing module is used to perform differentiated QoS guarantee on the data stream of the first service when the service stream of the first service or application is received, and / or to perform differentiated QoS guarantee on the data stream identified by the first service or application based on the first information.

[0433] Optionally, the apparatus further includes: a third processing module, configured to send sixth information to a third node, the sixth information indicating QoS requirements for network assurance, the sixth information including at least one of the following:

[0434] User address;

[0435] First node identifier;

[0436] Stream description information;

[0437] QoS requirement information;

[0438] Flow characteristic information.

[0439] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0440] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0441] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0442] Agreement information;

[0443] Information about the location or domain of the stream type;

[0444] Attribute information;

[0445] Flow identification information;

[0446] Stream type meaning information.

[0447] Optionally, the first node includes a SEALDD server, and the apparatus further includes:

[0448] The third sending module is used to send a seventh message to the second node, the seventh message being used to indicate the result of the first client's response to the first message and / or the result of the first node's response to the fifth message.

[0449] Optionally, if the first client and / or the first node does not support multi-stream multiplexing identification for the first service or application, the result includes: information on the protocols supported by the first client and / or the first node.

[0450] Optionally, the first node includes a UPF, and the device further includes:

[0451] The fourth sending module is used to send eighth information to the second node, the eighth information being used to indicate whether the second node can obtain the service for multi-stream multiplexing identification.

[0452] Optionally, if the first node includes a SEALDD server, the receiving of the fifth information sent by the second node and the sending of the first information to the first client are performed during the process of establishing a SEALDD connection.

[0453] Optionally, if the first node includes a SEALDD server, the apparatus further includes:

[0454] The fifth sending module is used to send the ninth message to the CAPIF core function or EES. The ninth message is used to indicate that the first node supports multi-stream multiplexing identification and / or differentiated QoS guarantee. The ninth message includes at least one of the following:

[0455] First node identifier;

[0456] Supports multi-stream multiplexing identification;

[0457] Supported protocol information;

[0458] Supports multi-stream differentiated QoS services.

[0459] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0460] See Figure 10 , Figure 10 This is a structural diagram of the multi-stream multiplexing identification device provided in an embodiment of this application, applied to a first client. For example... Figure 10 As shown, the multi-stream multiplexing identification device includes: a processor 1001 and a transceiver 1002; wherein, the processor 1001 is used for:

[0461] Receive first information sent by the first node, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation and / or has a multi-stream multiplexing identification requirement;

[0462] Send a second message to the first node, the second message being used to indicate the result of responding to the first message;

[0463] If the result indicates support for multi-stream multiplexing identification of the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the first information.

[0464] Optionally, the first information includes one or more of the following:

[0465] Multi-stream multiplexing service activation instruction;

[0466] The identifier of the first service or application;

[0467] Stream description information;

[0468] User ID;

[0469] Security information;

[0470] Service-enabled application layer data transmission SEALDD connection information;

[0471] Agreement information;

[0472] Multi-stream multiplexing identification information;

[0473] Information about the first node.

[0474] Optionally, the first information is further used to indicate that the first service has a requirement for multi-stream differentiated QoS guarantee, and the first information further includes: differentiated QoS information; the processor 1001 is further used to:

[0475] Upon receiving the service flow of the first service or application, differentiated QoS guarantee is performed on the data flow of the first service or application, and / or, differentiated QoS guarantee is performed on the data flow identified by the first service or application based on the first information.

[0476] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0477] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0478] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0479] Agreement information;

[0480] Information about the location or domain of the stream type;

[0481] Attribute information;

[0482] Flow identification information;

[0483] Stream type meaning information.

[0484] Optionally, if the first client does not support multi-stream multiplexing identification for the first service or application, the result includes:

[0485] Information about the protocols supported by the first client.

[0486] Optionally, the processor 1001 is further configured to: send third information to the edge execution server EES, the third information being used to discover the target first node, wherein the discovery of the target first node is based on the protocol supported by the first client and the protocol supported by the target first node;

[0487] Receive the fourth information sent by the EES, the fourth information including the information of the target first node.

[0488] Optionally, if the first node includes a SEALDD server, the receiving of the first information sent by the first node and the sending of the second information to the first node are performed during the process of establishing a SEALDD connection.

[0489] Optionally, different primary services or applications may support the same or different protocols.

[0490] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0491] See Figure 11 , Figure 11 This is a structural diagram of the multi-stream multiplexing identification device provided in an embodiment of this application, applied to the first node. For example... Figure 11As shown, the multi-stream multiplexing identification device includes: a processor 1101 and a transceiver 1102; wherein, the processor 1101 is used for:

[0492] Receive the fifth information sent by the second node, the fifth information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement;

[0493] If multi-stream multiplexing identification is supported for the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the fifth information.

[0494] Optionally, the processor 1101 is further configured to: send first information to the first client, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement.

[0495] Optionally, the first information includes one or more of the following:

[0496] Multi-stream multiplexing service activation instruction;

[0497] The identifier of the first service or application;

[0498] Stream description information;

[0499] User ID;

[0500] Security information;

[0501] SEALDD connection information;

[0502] Agreement information;

[0503] Multi-stream multiplexing identification information;

[0504] Information about the first node.

[0505] Optionally, the fifth piece of information includes one or more of the following:

[0506] Multi-stream multiplexing service activation instruction;

[0507] The identifier of the first service or application;

[0508] Stream description information;

[0509] User ID;

[0510] Security information;

[0511] SEALDD connection information;

[0512] Agreement information;

[0513] Multi-stream multiplexing identification information.

[0514] Optionally, the first information or the fifth information is further used to indicate that the first service has a requirement for multi-stream differentiated QoS guarantee, and the first information or the fifth information further includes: differentiated QoS information; the processor 1101 is further used to:

[0515] Upon receiving the service flow of the first service or application, differentiated QoS guarantee is performed on the data flow of the first service, and / or differentiated QoS guarantee is performed on the data flow identified by the first service or application based on the first information.

[0516] Optionally, the processor 1101 is further configured to perform differentiated QoS guarantees, including:

[0517] Send a sixth message to the third node, the sixth message indicating the QoS requirements needed for network assurance, the sixth message including at least one of the following:

[0518] User address;

[0519] First node identifier;

[0520] Stream description information;

[0521] QoS requirement information;

[0522] Flow characteristic information.

[0523] Optionally, the multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexed stream;

[0524] The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

[0525] Optionally, the multi-stream multiplexing identification information includes at least one of the following:

[0526] Agreement information;

[0527] Information about the location or domain of the stream type;

[0528] Attribute information;

[0529] Flow identification information;

[0530] Stream type meaning information.

[0531] Optionally, the first node includes: a SEALDD server, and the processor 1101 is further configured to:

[0532] A seventh message is sent to the second node, the seventh message being used to indicate the result of the first client's response to the first message and / or the result of the first node's response to the fifth message.

[0533] Optionally, if the first client and / or the first node does not support multi-stream multiplexing identification for the first service or application, the result includes: information on the protocols supported by the first client and / or the first node.

[0534] Optionally, the first node includes a UPF, and the processor 1101 is further configured to:

[0535] Send an eighth message to the second node, the eighth message being used to indicate whether the second node can obtain the service for multi-stream multiplexing identification.

[0536] Optionally, if the first node includes a SEALDD server, the receiving of the fifth information sent by the second node and the sending of the first information to the first client are performed during the process of establishing a SEALDD connection.

[0537] Optionally, if the first node includes a SEALDD server, the processor 1101 is further configured to:

[0538] Send a ninth message to the CAPIF core function or EES, the ninth message being used to indicate that the first node supports multi-stream multiplexing identification and / or differentiated QoS guarantee, the ninth message including at least one of the following:

[0539] First node identifier;

[0540] Supports multi-stream multiplexing identification;

[0541] Supported protocol information;

[0542] Supports multi-stream differentiated QoS services.

[0543] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0544] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0545] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0546] This application provides a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor; the processor is configured to read the program in the memory to implement the steps in the multi-stream multiplexing identification method described above.

[0547] This application also provides a readable storage medium storing a program. When executed by a processor, this program implements the various processes of the above-described multi-stream multiplexing identification method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here. The readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0548] This application also provides a computer program product, including computer instructions. When executed by a processor, the computer instructions implement the various processes of the above-described multi-stream multiplexing identification method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0549] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0550] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0551] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A multi-stream multiplexing identification method, characterized in that, Applied to the first client, including: Receive first information sent by the first node, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation and / or has a multi-stream multiplexing identification requirement; Send a second message to the first node, the second message being used to indicate the result of responding to the first message; If the result indicates support for multi-stream multiplexing identification of the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the first information.

2. The method according to claim 1, characterized in that, The first information includes one or more of the following: Multi-stream multiplexing service activation instruction; The identifier of the first service or application; Stream description information; User ID; Security information; Service-enabled application layer data transmission SEALDD connection information; Agreement information; Multi-stream multiplexing identification information; Information about the first node.

3. The method according to claim 2, characterized in that, The first information is also used to indicate that the first service has a requirement for multi-stream differentiated quality of service (QoS) assurance, and the first information further includes: differentiated QoS information; The method further includes: Upon receiving the service flow of the first service or application, differentiated QoS guarantee is performed on the data flow of the first service or application, and / or, differentiated QoS guarantee is performed on the data flow identified by the first service or application based on the first information.

4. The method according to claim 2, characterized in that, The multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexing stream; The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

5. The method according to any one of claims 2-4, characterized in that, The multi-stream multiplexing identification information includes at least one of the following: Agreement information; Information about the location or domain of the stream type; Attribute information; Stream type meaning information.

6. The method according to claim 1, characterized in that, If the first client does not support multi-stream multiplexing identification for the first service or application, the result includes: Information about the protocols supported by the first client.

7. The method according to claim 1, characterized in that, The method further includes: Send third information to the Edge Execution Server (EES), the third information being used to discover the target first node, wherein the discovery of the target first node is based on the protocols supported by the first client and the protocols supported by the target first node; Receive the fourth information sent by the EES, the fourth information including the information of the target first node.

8. The method according to claim 1, characterized in that, If the first node includes a SEALDD server, the receiving of the first information sent by the first node and the sending of the second information to the first node are performed during the process of establishing a SEALDD connection.

9. The method according to claim 1, characterized in that, in, Different primary services or applications may support the same or different protocols.

10. A multi-stream multiplexing identification method, characterized in that, Applied to the first node, including: Receive the fifth information sent by the second node, the fifth information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement; If multi-stream multiplexing identification is supported for the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the fifth information.

11. The method according to claim 10, characterized in that, The method further includes: Send first information to the first client, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a need for multi-stream multiplexing identification.

12. The method according to claim 11, characterized in that, The first information includes one or more of the following: Multi-stream multiplexing service activation instruction; The identifier of the first service or application; Stream description information; User ID; Security information; SEALDD connection information; Agreement information; Multi-stream multiplexing identification information; Information about the first node.

13. The method according to claim 10, characterized in that, The fifth piece of information includes one or more of the following: Multi-stream multiplexing service activation instruction; The identifier of the first service or application; Stream description information; User ID; Security information; SEALDD connection information; Agreement information; Multi-stream multiplexing identification information.

14. The method according to claim 11, characterized in that, The first information or the fifth information is also used to indicate that the first service has a requirement for multi-stream differentiated QoS guarantee, and the first information or the fifth information further includes: differentiated QoS information; The method further includes: Upon receiving the service flow of the first service or application, differentiated QoS guarantee is performed on the data flow of the first service, and / or differentiated QoS guarantee is performed on the data flow identified by the first service or application based on the first information.

15. The method according to claim 14, characterized in that, The differentiated QoS guarantee includes: Send a sixth message to the third node, the sixth message indicating the QoS requirements needed for network assurance, the sixth message including at least one of the following: User address; First node identifier; Stream description information; QoS requirement information; Flow characteristic information.

16. The method according to claim 12 or 13, characterized in that, The multi-stream multiplexing identification information is used to indicate the identification of different types of streams in the multi-stream multiplexing stream; The multi-stream multiplexing identification information is carried through the first position or first field of the protocol header or extension header, or it is indicated by the first file, or it is indicated by the first information of the first file.

17. The method according to claim 12 or 13, characterized in that, The multi-stream multiplexing identification information includes at least one of the following: Agreement information; Information about the location or domain of the stream type; Attribute information; Flow identification information; Stream type meaning information.

18. The method according to claim 11, characterized in that, The first node includes: a SEALDD server, and the method further includes: A seventh message is sent to the second node, the seventh message being used to indicate the result of the first client's response to the first message and / or the result of the first node's response to the fifth message.

19. The method according to claim 18, characterized in that, If the first client and / or the first node does not support multi-stream multiplexing identification for the first service or application, the result includes: information on the protocols supported by the first client and / or the first node.

20. The method according to claim 10, characterized in that, The first node includes: a User Plane Function Entity (UPF), and the method further includes: Send an eighth message to the second node, the eighth message being used to indicate whether the second node can obtain the service for multi-stream multiplexing identification.

21. The method according to claim 11, characterized in that, If the first node includes a SEALDD server, the receiving of the fifth information sent by the second node and the sending of the first information to the first client are performed during the process of establishing a SEALDD connection.

22. The method according to claim 10, characterized in that, If the first node includes a SEALDD server, the method further includes: Send a ninth message to the core functionality of the general API framework CAPIF or EES. The ninth message is used to indicate that the first node supports multi-stream multiplexing identification and / or differentiated QoS guarantee. The ninth message includes at least one of the following: First node identifier; Supports multi-stream multiplexing identification; Supported protocol information; Supports multi-stream differentiated QoS services.

23. A multi-stream multiplexing identification device, characterized in that, Applied to the first client, including: The first receiving module is used to receive first information sent by the first node, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation and / or has a multi-stream multiplexing identification requirement; A first sending module is configured to send second information to the first node, wherein the second information is used to indicate the result of responding to the first information; The first processing module is configured to, if the result indicates support for multi-stream multiplexing identification of the first service or application, perform multi-stream multiplexing identification on the data stream of the first service or application upon receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the first information.

24. A multi-stream multiplexing identification device, characterized in that, Applied to the first node, including: The first receiving module is used to receive the fifth information sent by the second node. The fifth information is used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement. The first processing module is configured to, if it supports multi-stream multiplexing identification for the first service or application, perform multi-stream multiplexing identification on the data stream of the first service or application upon receiving the service stream of the first service or application, and / or perform multi-stream multiplexing identification on the data stream identified by the first service or application based on the fifth information.

25. A multi-stream multiplexing identification device, characterized in that, Applied to a first client, it includes: a processor and a transceiver; wherein, the processor is used for: Receive first information sent by the first node, the first information being used to indicate that the first service or application has a multi-stream multiplexing situation and / or has a multi-stream multiplexing identification requirement; Send a second message to the first node, the second message being used to indicate the result of responding to the first message; If the result indicates support for multi-stream multiplexing identification of the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the first information.

26. A multi-stream multiplexing identification device, characterized in that, Applied to the first node, it includes: a processor and a transceiver; wherein the processor is used for: Receive the fifth information sent by the second node, the fifth information being used to indicate that the first service or application has a multi-stream multiplexing situation, and / or has a multi-stream multiplexing identification requirement; If multi-stream multiplexing identification is supported for the first service or application, upon receiving the service flow of the first service or application, multi-stream multiplexing identification is performed on the data flow of the first service or application, and / or, multi-stream multiplexing identification is performed on the data flow identified by the first service or application based on the fifth information.

27. A communication device, comprising: A memory, a processor, and a program stored in the memory and executable on the processor; characterized in that the processor is configured to read the program from the memory to implement the steps in the multi-stream multiplexing identification method as described in any one of claims 1 to 26.

28. A computer-readable storage medium for storing a program, characterized in that, When the program is executed by the processor, it implements the steps in the multi-stream multiplexing identification method as described in any one of claims 1 to 26.

29. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the steps in the multi-stream multiplexing identification method as described in any one of claims 1 to 26.

Images