Method for splitting end-to-end qos requirement information, terminal and network side device

Abstract

This application discloses a method for splitting end-to-end QoS requirement information, a terminal, and a network-side device, belonging to the field of communication technology, and can solve the problem of limited application scenarios for meeting QoS requirements. The method includes a target device splitting end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, wherein the target device includes a target UE and an access network device.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a method for splitting end-to-end QoS requirement information, a terminal, and network-side equipment. Background Technology

[0002] In related technologies, during relay communication, the end-to-end communication quality needs to meet the Quality of Service (QoS) requirements. Specifically, during relay communication, network-side devices can generate Uu-segment QoS information based on relevant rules (e.g., Policy and Charging Control Rules, PCC) or local policy configurations, and send it to the relay UE. After receiving the Uu-segment QoS information, the relay UE can convert the Uu-segment QoS information into PC5-segment QoS parameters according to the mapping relationship configured for the terminal UE by the network-side device, thereby meeting the end-to-end QoS requirements.

[0003] Currently, since only the service requirements provided by network-side devices are considered, the application scenarios that meet QoS requirements are relatively limited. Summary of the Invention

[0004] The purpose of this application is to provide a method for splitting end-to-end QoS requirement information, a terminal, and a network-side device, which can solve the problem that application scenarios that meet QoS requirements are relatively limited.

[0005] To solve the above-mentioned technical problems, this application is implemented as follows:

[0006] Firstly, a method for splitting end-to-end QoS requirement information is provided. The method includes: a target device splitting end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, wherein the target device includes a target UE and an access network device.

[0007] Secondly, a method for splitting end-to-end QoS requirement information is provided, the method comprising: the core network device sending end-to-end QoS requirement information to the access network device, wherein the end-to-end QoS requirement information includes end-to-end QoS requirement text.

[0008] Thirdly, a method for splitting end-to-end QoS requirement information is provided. This method includes: a target core network device splitting the end-to-end QoS requirement information to obtain PC5 segment QoS information and Uu segment QoS information; before the target core network device splits the end-to-end QoS requirement information, the target core network device receives the end-to-end QoS requirement information from a relay UE, and the end-to-end QoS requirement information is sent to the relay UE by a remote UE; or, after the target core network device splits the end-to-end QoS requirement information, the target core network device sends the PC5 segment QoS information and the Uu segment QoS information to an access network device; wherein the PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes; the PC5 segment QoS parameters include PQI, and the PC5 segment QoS attributes include PDB; the Uu segment QoS information includes Uu segment QoS parameters and Uu segment QoS attributes; the Uu segment QoS parameters include 5QI, and the Uu segment QoS attributes include PDB.

[0009] Fourthly, a method for splitting end-to-end QoS requirement information is provided. The method includes: an access network device receiving PC5 segment QoS information and Uu segment QoS information from a target core network device; the PC5 segment QoS information and the Uu segment QoS information are obtained by splitting end-to-end QoS requirement information; and the access network device establishing the PC5 segment bearer and the Uu segment bearer based on the PC5 segment QoS information and the Uu segment QoS information.

[0010] Fifthly, a method for splitting end-to-end QoS requirement information is provided, the method comprising: a relay UE receiving end-to-end QoS requirement information from a remote UE; the relay UE sending the end-to-end QoS requirement information to a target core network device.

[0011] In a sixth aspect, an end-to-end QoS requirement information splitting device is provided, the device comprising: a splitting module; the splitting module being used to split the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, the target device including a target UE and an access network device.

[0012] In a seventh aspect, an apparatus for splitting end-to-end QoS requirement information is provided. The apparatus includes: a sending module; the sending module is used to send end-to-end QoS requirement information to an access network device, wherein the end-to-end QoS requirement information includes end-to-end QoS requirement text.

[0013] Eighthly, an apparatus for splitting end-to-end QoS requirement information is provided. The apparatus includes: a splitting module and a receiving module. The splitting module is used to split the end-to-end QoS requirement information to obtain PC5 segment QoS information and Uu segment QoS information. The receiving module is used to receive the end-to-end QoS requirement information from a relay UE before the target core network device splits the end-to-end QoS requirement information, wherein the end-to-end QoS requirement information is sent by a remote UE to the relay UE. Alternatively, the sending module is used to send the PC5 segment QoS information and the Uu segment QoS information to an access network device after the target core network device splits the end-to-end QoS requirement information. The PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes; the PC5 segment QoS parameters include PQI, and the PC5 segment QoS attributes include PDB. The Uu segment QoS information includes Uu segment QoS parameters and Uu segment QoS attributes; the Uu segment QoS parameters include 5QI, and the Uu segment QoS attributes include PDB.

[0014] A ninth aspect provides an end-to-end QoS requirement information splitting apparatus, the apparatus comprising: a receiving module and an establishing module; the receiving module being configured to receive PC5 segment QoS information and Uu segment QoS information from a target core network device; the PC5 segment QoS information and the Uu segment QoS information being obtained by splitting end-to-end QoS requirement information; the establishing module being configured to establish the PC5 segment bearer and the Uu segment bearer based on the PC5 segment QoS information and the Uu segment QoS information.

[0015] In a tenth aspect, an apparatus for splitting end-to-end QoS requirement information is provided. The apparatus includes a receiving module and a sending module. The receiving module is used to receive end-to-end QoS requirement information from a remote UE. The sending module is used to send the end-to-end QoS requirement information received by the receiving module to a target core network device.

[0016] Eleventhly, a terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein when the program or instructions are executed by the processor, they implement the steps of the method as described in the first aspect, or implement the steps of the method as described in the second aspect, the third aspect, the fourth aspect, or the fifth aspect.

[0017] In a twelfth aspect, a network-side device is provided, the network-side device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein when the program or instructions are executed by the processor, they implement the steps of the method as described in the first aspect, or implement the steps of the method as described in the second aspect, the third aspect, the fourth aspect, or the fifth aspect.

[0018] In a thirteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method as described in the first aspect, or implement the steps of the method as described in the second aspect, the third aspect, the fourth aspect, or the fifth aspect.

[0019] In a fourteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a network-side device program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect, the third aspect, the fourth aspect, or the fifth aspect.

[0020] In this embodiment, the target device splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information. Thus, the subject of splitting the end-to-end QoS requirement information is no longer limited to network-side devices, allowing for more diverse and varied splitting scenarios, facilitating the splitting of end-to-end QoS requirement information in any scenario. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of a possible structure of the communication system involved in the embodiments of this application;

[0022] Figure 2 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 1 ;

[0023] Figure 3 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 2 ;

[0024] Figure 4 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 3 ;

[0025] Figure 5 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 4 ;

[0026] Figure 6 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 5 ;

[0027] Figure 7 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 6 ;

[0028] Figure 8 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 7 ;

[0029] Figure 9 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 8 ;

[0030] Figure 10 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 9 ;

[0031] Figure 11 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 10 ;

[0032] Figure 12 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 10 one;

[0033] Figure 13 A flowchart illustrating a method for splitting end-to-end QoS requirement information provided in this application embodiment. Figure 10 two;

[0034] Figure 14 A schematic diagram of the structure of an end-to-end QoS requirement information splitting device provided in an embodiment of this application. Figure 1 ;

[0035] Figure 15 A schematic diagram of the structure of an end-to-end QoS requirement information splitting device provided in an embodiment of this application. Figure 2 ;

[0036] Figure 16 A schematic diagram of the structure of an end-to-end QoS requirement information splitting device provided in an embodiment of this application. Figure 3 ;

[0037] Figure 17 A schematic diagram of the structure of an end-to-end QoS requirement information splitting device provided in an embodiment of this application. Figure 4 ;

[0038] Figure 18 A schematic diagram of the structure of an end-to-end QoS requirement information splitting device provided in an embodiment of this application. Figure 5 ;

[0039] Figure 19 A schematic diagram of a communication device provided in an embodiment of this application;

[0040] Figure 20 A schematic diagram of the hardware structure of a terminal provided in an embodiment of this application;

[0041] Figure 21 This is a schematic diagram of a network-side device provided in an embodiment of this application. Detailed Implementation

[0042] 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 some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0043] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0044] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. However, the following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description, although these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0045] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or user equipment (UE). The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this embodiment of the application, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0046] The method for splitting end-to-end QoS requirement information provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0047] Figure 2 This diagram illustrates a flowchart of a method for splitting end-to-end QoS requirement information according to an embodiment of the present invention. The method may include step 201:

[0048] Step 201: The target device splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information.

[0049] In this embodiment of the application, the target device includes a target UE and an access network device.

[0050] For example, the target UE mentioned above can be a remote UE (i.e., Remote UE) or a relay UE (i.e., Relay UE).

[0051] For example, the access network device described above may include a Radio Access Network (RAN) device.

[0052] In this embodiment, the aforementioned end-to-end QoS requirement information can be: priority requirements, latency requirements, reliability requirements, etc., required by a relay service. In one example, the aforementioned end-to-end QoS requirement information can be: QoS parameters and QoS attributes corresponding to the end-to-end QoS requirements satisfied by the transmission of data from a remote UE to a UPF (User Plane Function) anchor point, such as 5QI, guaranteed stream bit rate, maximum stream bit rate, latency, packet error rate, etc.

[0053] In this embodiment of the application, the aforementioned end-to-end QoS requirement information can be: end-to-end QoS requirement information when a remote UE establishes a non-direct link with a network-side device through a relay UE.

[0054] In this embodiment, when a relay UE is involved in the end-to-end communication, the QoS requirement information needs to be split into PC5 segment QoS information and Uu segment QoS information to meet the end-to-end QoS requirements. Specifically, the QoS information between the remote UE and the relay UE is PC5 segment QoS information, and the QoS information between the relay UE and the network-side UE is Uu segment QoS information. Since the communication is a non-direct interface via relay, end-to-end QoS assurance requires segmented support. If there is no specific PC5 segment QoS information and Uu segment QoS information to support end-to-end QoS assurance, the network side will be unable to perform accurate radio resource allocation to meet the end-to-end QoS requirements. Therefore, in this application, by splitting the end-to-end QoS requirement information as described above, the communication quality of the non-direct interface communication can be guaranteed.

[0055] The end-to-end QoS requirement information splitting method provided in this application embodiment splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information by the target device. Thus, the subject of splitting end-to-end QoS requirement information is no longer limited to network-side devices, and the scenarios for splitting can become more diverse and richer, facilitating the splitting of end-to-end QoS requirement information in any scenario.

[0056] Optionally, in the embodiments provided in this application, the PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes; the Uu segment QoS information includes Uu segment QoS parameters and Uu segment QoS attributes.

[0057] For example, the QoS parameters of the PC5 segment mentioned above may include PQI, the QoS attributes of the PC5 segment mentioned above may include PDB, the QoS parameters of the Uu segment mentioned above may include 5QI, and the QoS attributes of the Uu segment mentioned above may include PDB.

[0058] For example, the QoS parameters of the PC5 segment may also include Maximum Flow Bit Rate (MFBR) and Guaranteed Bit Rate (GFBR). The QoS attributes of the PC5 segment may also include Packet Error Rate (PER). The QoS parameters of the Uu segment include PC5QoS identifier (PQI), MFBR, and GFBR. The QoS attributes of the Uu segment include PER.

[0059] Optionally, in the embodiments provided in this application, the PC5 segment QoS information and the Uu segment QoS information satisfy the end-to-end QoS requirement information.

[0060] For example, the end-to-end QoS requirement information mentioned above can be: the split PC5 segment QoS information and the Uu segment QoS information mentioned above satisfy the end-to-end QoS requirement information.

[0061] In one example, the QoS information of the above-mentioned split PC5 segment that meets the end-to-end QoS requirements can be: the QoS parameters of the above-mentioned split PC5 segment meet the end-to-end QoS parameters; the QoS information attributes of the split PC5 segment meet the end-to-end QoS attributes, for example, the PDB of the split PC5 segment meets the end-to-end PDB.

[0062] In another example, the QoS information of the split Uu segment described above can satisfy the end-to-end QoS requirements as follows: the QoS parameters of the split Uu segment described above satisfy the end-to-end QoS parameters; the QoS information attributes of the split Uu segment satisfy the end-to-end QoS attributes, for example, the PDB of the split Uu segment satisfies the end-to-end PDB.

[0063] For example, after the target device splits the end-to-end QoS requirement information, the combination of the PC5 segment QoS parameters / attributes and the Uu segment QoS parameters / attributes must meet the end-to-end QoS requirements. For instance, taking the Packet Delay Budget (PDB) in the end-to-end QoS requirement information as an example, the sum of the PC5 segment PDB and the Uu segment PDB should be less than or equal to the PDB requirement in the end-to-end QoS requirement information, as specifically described in Example 1 below:

[0064] Example 1: When a relay UE is involved between a remote UE and the UPF anchor point (i.e., the end-to-end connection mentioned above), to meet the QoS requirements between the remote UE and the UPF anchor point, the QoS requirements need to be split into PC5 segment QoS information and Uu segment QoS. If the PDB in the end-to-end QoS requirements is 100ms, then after the target device splits the QoS requirements between the remote UE and the UPF anchor point, the PC5 segment PDB (i.e., the PC5 segment QoS information mentioned above) between the remote UE and the relay UE can be 20ms, and the Uu segment PDB (i.e., the Uu segment QoS information mentioned above) between the relay UE and the UPF anchor point can be 80ms. Thus, when information is transmitted between the remote UE and the UPF, after passing through the PC5 segment and the Uu segment, its PDB still meets the requirement of a 100ms PDB in the QoS requirements between the remote UE and the UPF anchor point.

[0065] Thus, when the target device splits the aforementioned end-to-end QoS requirement information, the split PC5 segment QoS information and Uu segment QoS information still meet the end-to-end transmission QoS requirement information, ensuring the normal transmission of information.

[0066] Figure 2 This diagram illustrates a flowchart of a method for splitting end-to-end QoS requirement information according to an embodiment of the present invention. The method may include steps 202a to 202c.

[0067] For example, when the target UE is the remote UE, after step 201, the end-to-end QoS requirement information splitting method provided in this application may further include the following steps 202a to 202c:

[0068] Step 202a: The remote UE sends the above-mentioned Uu segment QoS information and the above-mentioned PC5 segment QoS information to the above-mentioned relay UE.

[0069] Step 202b: The relay UE initiates a PDU session establishment or modification process to establish the corresponding Uu segment QoS flow based on the Uu segment QoS information.

[0070] Step 202c: The relay UE initiates a direct link change procedure to establish the corresponding PC5 segment QoS flow based on the PC5 segment QoS information.

[0071] For example, when the target device is a remote UE, the remote UE can split the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information. The PC5 segment QoS information can be PC5 segment QoS configuration information, and the Uu segment QoS information can be Uu segment QoS configuration information.

[0072] In one example, the PC5 segment QoS configuration information described above can be used to indicate the QoS parameters (e.g., PQI, MFBR, GFBR, etc.) and QoS attributes (e.g., PDB, PER, etc.) of the PC5 QoS flow between the remote UE and the relay UE.

[0073] In one example, the QoS configuration information of the Uu segment mentioned above can be used to indicate the QoS parameters (e.g., PQI, MFBR, GFBR, etc.) and QoS attributes (e.g., PDB, PER, etc.) of the QoS flow between the relay UE and the network-side device (e.g., UPF).

[0074] For example, during the process of the remote UE sending the Uu segment QoS information and the PC5 segment QoS information to the relay UE, the remote UE can send a direct link modification request message to the relay UE.

[0075] Example 1: In relay communication, taking the target device as a remote UE as an example. For example... Figure 3 As shown, the technical solution for remotely splitting end-to-end QoS requirement information for UEs includes the following steps:

[0076] Step 11: The remote UE first splits the end-to-end QoS requirement information into PC5 segment QoS configuration information (i.e., the PC5 segment QoS information mentioned above) and Uu segment QoS configuration information (i.e., the Uu segment QoS information mentioned above).

[0077] Step 12: The remote UE sends the split PC5 segment QoS configuration information and Uu segment QoS configuration information to the relay UE.

[0078] Step 13: Based on the Uu segment QoS requirement configuration information provided by the remote UE, the relay UE can establish the corresponding Uu segment QoS flow through the PDU sessionmodification process or the PDU session Establishment process.

[0079] Step 14: Based on the PC5 segment QoS configuration information provided by the remote UE, the relay UE initiates a direct link change process and establishes a corresponding PC5 QoS flow with the remote UE.

[0080] Thus, when the target device is a remote UE, the remote UE can complete the end-to-end QoS requirement information splitting process on its own without the network side's involvement, reducing signaling overhead.

[0081] Figure 4 This diagram illustrates a flowchart of a method for splitting end-to-end QoS requirement information according to an embodiment of the present invention. The method may include steps 203a to 203c.

[0082] For example, when the target UE is the relay UE, before step 201, the end-to-end QoS requirement information splitting method provided in this application may further include the following steps 203a and 203b:

[0083] Step 203a: The remote UE sends end-to-end QoS requirement information to the relay UE.

[0084] Step 203b: The relay UE receives the end-to-end QoS requirement information from the aforementioned remote UE.

[0085] Based on step 203 above, after step 201 above, the method for splitting end-to-end QoS requirement information provided in this application may further include the following step 203c:

[0086] Step 203c: The relay UE initiates a PDU session establishment or modification process based on the above Uu segment QoS information to establish the corresponding Uu segment QoS flow, and the above relay UE initiates a direct link modification process based on the above PC5 segment QoS information to establish the corresponding PC5 segment QoS flow.

[0087] For example, the link change process described above is used to change the link information of the direct link between the remote UE and the relay UE.

[0088] For example, the aforementioned end-to-end QoS requirement information can be carried in a direct link modification request message.

[0089] In one example, the PC5 segment QoS configuration information described above can be used to indicate the QoS parameters (e.g., PQI, MFBR, GFBR, etc.) and QoS attributes (e.g., PDB, PER, etc.) of the PC5 QoS flow between the remote UE and the relay UE.

[0090] In one example, the QoS configuration information of the Uu segment mentioned above can be used to indicate the QoS parameters (e.g., PQI, MFBR, GFBR, etc.) and QoS attributes (e.g., PDB, PER, etc.) of the QoS flow between the relay UE and the network-side device (e.g., UPF).

[0091] Example 2: In relay communication, taking the target device as the relay UE as an example. For example... Figure 5 As shown, the technical solution for remotely splitting end-to-end QoS requirement information for UEs includes the following steps:

[0092] Step 21: The remote UE sends end-to-end QoS requirement information to the relay UE.

[0093] Step 22: The relay UE receives the end-to-end QoS requirement information.

[0094] Step 23: The relay UE splits the end-to-end QoS requirement information into PC5 segment QoS configuration information (i.e., the PC5 segment QoS information mentioned above) and Uu segment QoS configuration information (i.e., the Uu segment QoS information mentioned above).

[0095] Step 24: Based on the Uu segment QoS configuration information, the relay UE can establish the corresponding Uu segment QoS flow through the PDU session modification procedure or the PDU session establishment procedure. After the Uu segment QoS flow is established, the relay UE establishes the corresponding PC5 QoS flow through the direct link modification procedure based on the PC5 segment QoS configuration information obtained from the splitting.

[0096] Thus, when the target device is a relay UE, the relay UE can complete the end-to-end QoS requirement information splitting process on its own without the network side's involvement, reducing signaling overhead.

[0097] Optionally, in the embodiments provided in this application, the method for splitting end-to-end QoS requirement information provided in step 201 above may include the following step 204:

[0098] Step 204: The target UE splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information according to the first mapping relationship or the first information.

[0099] For example, the first mapping relationship mentioned above includes the mapping relationship between the end-to-end QoS requirement information and the PC5 segment QoS information and the Uu segment QoS information.

[0100] Optionally, in this embodiment of the application, the first mapping relationship described above is configured on the network side or pre-configured.

[0101] For example, this mapping relationship can map end-to-end QoS requirement information to the PC5 segment and the Uu segment to obtain PC5 segment QoS information and Uu segment QoS information.

[0102] In one example, the first mapping relationship described above can be represented as shown in the table below:

[0103]

[0104] It should be noted that the aforementioned end-to-end QoS identifier can be 5QI in direct communication.

[0105] Example 2: When a remote UE or a relay UE is splitting end-to-end QoS requirement information, it can find the PC5 segment QoS information and the Uu segment QoS information according to the specific parameter categories in the end-to-end QoS requirement information and the first mapping relationship table. For example, when a remote UE is splitting end-to-end QoS requirement information, if the specific parameter to be split is the end-to-end PDB, then the PC5 segment PDB and the Uu segment PDB can be found accordingly in the first mapping relationship table using the end-to-end PDB as the index.

[0106] For example, the first information mentioned above includes: the QoS information that the target UE can support on the PC5 interface and the QoS information of the Uu interface, based on the wireless resource utilization or air interface link quality.

[0107] For example, the target device can perform end-to-end QoS splitting based on the first information mentioned above (for example, if the PDB supported by the PC5 segment is 20ms and the PDB supported by the Uu segment is 80ms, then the end-to-end QoS requirement can be split (100ms) based on the supported parameters).

[0108] Thus, a remote UE or a relay UE can split the aforementioned end-to-end QoS information based on the first mapping relationship or the first information.

[0109] Figure 6 This diagram illustrates a flowchart of a method for splitting end-to-end QoS requirement information according to an embodiment of the present invention. The method may include steps 205a to 205c.

[0110] For example, when the target device is the access network device, before step 201, the end-to-end QoS requirement information splitting method provided in this application embodiment may further include the following steps 205a and 205b:

[0111] Step 205a: The core network equipment sends end-to-end QoS requirement information to the access network equipment.

[0112] Step 205b: The access network device receives the above end-to-end QoS requirement information.

[0113] Based on step 205a above, after step 201, the method for splitting end-to-end QoS requirement information provided in this application embodiment may further include the following steps 205b and 205c:

[0114] Step 205c: The access network device establishes the bearer of the PC5 segment based on the QoS information of the PC5 segment, and establishes the bearer of the Uu segment based on the QoS information of the Uu segment.

[0115] For example, the target core network device described above can be any device among the core network devices. For example, SMF.

[0116] In one example, the target core network device can send end-to-end QoS requirement information to the access network device during the establishment or modification of a PDU session.

[0117] For example, the end-to-end QoS requirement information sent by the core network device to the access network device includes end-to-end QoS requirement text.

[0118] Thus, when the target device is an access network device, the access network can complete the end-to-end QoS requirement information splitting process on its own, simplifying the interaction between the access network and the core network and reducing signaling procedures.

[0119] Optionally, in this embodiment of the application, when the target device is the access network device, the end-to-end QoS requirement information splitting method provided in step 201 may include the following step 206:

[0120] Step 206: The access network device above splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information according to the second mapping relationship or the second information.

[0121] For example, the second mapping relationship mentioned above includes: the mapping relationship between the end-to-end QoS requirement information and the PC5 segment QoS information and the Uu segment QoS information; the second information includes: the QoS parameters of the PC5 interface and the QoS parameters of the Uu interface detected by the access network device.

[0122] Optionally, in this embodiment of the application, the second mapping relationship described above is configured on the network side or pre-configured.

[0123] It should be noted that, since the access network device is a network-side device, the second mapping relationship it obtains may not be entirely the same as the first mapping relationship obtained by the UE. Similarly, the second information obtained by the access network device and the first information obtained by the UE may also be not entirely the same or different.

[0124] It is understandable that when the access network device splits the end-to-end QoS requirement information according to the above-mentioned second mapping relationship or second information, the splitting method is similar to that in Examples 2 and 3 above, and will not be repeated here.

[0125] Example 3: In the case of relay communication, taking the target device as the access network device RAN as an example. For example... Figure 7 As shown, the technical solution for splitting end-to-end QoS requirement information in the access network equipment RAN includes the following steps:

[0126] Step 31: During the PDU session establishment or modification process, the SMF (i.e., the core network equipment mentioned above) sends end-to-end QoS requirement information to the RAN.

[0127] Step 32: The RAN receives the above end-to-end QoS requirement information.

[0128] Step 33: The RAN performs end-to-end QoS requirement information splitting based on the network-side configuration mapping rules (i.e., the second mapping rule mentioned above) to obtain Uu segment QoS text (i.e., the Uu segment QoS information mentioned above) and PC5 segment QoS text (i.e., the Uu segment QoS information mentioned above).

[0129] Step 34: The RAN establishes the corresponding Uu segment bearer based on the above Uu segment QoS text, and establishes the corresponding PC5 segment bearer based on the above PC5 segment QoS text.

[0130] Thus, the access network device can split the end-to-end QoS information according to the first mapping relationship or the first information.

[0131] The method for splitting end-to-end QoS requirement information provided in this application embodiment may include the following steps 301 to 303:

[0132] Step 301: The target core network device splits the end-to-end QoS requirement information to obtain PC5 segment QoS information and Uu segment QoS information.

[0133] For example, the target core network device mentioned above can be any device in the core network equipment, such as SMF or PCF.

[0134] Prior to step 301 above, the method for splitting end-to-end QoS requirement information provided in this application embodiment may further include the following step 302:

[0135] Step 302: The target core network device receives the above end-to-end QoS requirement information from the relay UE.

[0136] In this embodiment of the application, the aforementioned end-to-end QoS requirement information is sent by the remote UE to the relay UE.

[0137] or,

[0138] Following step 301 above, the method for splitting end-to-end QoS requirement information provided in this application embodiment may further include the following step 303:

[0139] Step 303: The target core network device sends the above PC5 segment QoS information and the above Uu segment QoS information to the access network device.

[0140] In this embodiment, the PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes; the PC5 segment QoS parameters include PQI, and the PC5 segment QoS attributes include PDB; the Uu segment QoS information includes Uu segment QoS parameters and Uu segment QoS attributes; the Uu segment QoS parameters include 5QI; and the Uu segment QoS attributes include PDB.

[0141] In the embodiments of this application, the descriptions of the PC5 segment QoS information, Uu segment QoS information, PC5 segment QoS parameters, PC5 segment QoS attributes, Uu segment QoS parameters, and Uu segment QoS attributes can refer to the foregoing descriptions, and will not be repeated here.

[0142] In this embodiment, the relationship between the PC5 segment QoS information, PC5 segment QoS parameters, and PC5 segment QoS attributes can be referred to the foregoing description, and will not be repeated here. Similarly, the relationship between the Uu segment QoS information, Uu segment QoS parameters, and Uu segment QoS attributes can be referred to the foregoing description, and will not be repeated here.

[0143] In the embodiments of this application, the descriptions of PQI, PDB, and 5QI can be referred to the foregoing descriptions, and will not be repeated here.

[0144] The end-to-end QoS requirement information splitting method provided in this application allows the target core network device to split end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information based on the end-to-end QoS requirement information provided by the relay UE. Alternatively, the split PC5 segment QoS information and Uu segment QoS information can be sent to the access network and then used on the communication link. This diversifies and enriches the splitting methods available to the target core network device when splitting end-to-end QoS requirement information.

[0145] Optionally, in this embodiment of the application, the target core network device includes a first core network device and a second core network device. In step 301 above, the method for splitting end-to-end QoS requirement information provided in this embodiment of the application may include the following steps 304 and 305:

[0146] Step 304: The aforementioned first core network device splits the end-to-end QoS requirement information to obtain PC5 segment QoS information and the first rule.

[0147] Step 305: The first core network device sends the PC5 segment QoS information and the first rule to the second core network device.

[0148] For example, the first rule mentioned above is used by the second core network device to generate Uu segment QoS information.

[0149] In one example, the first rule mentioned above could be a PCC rule.

[0150] Understandably, the first rule mentioned above can be used by the second core network to generate Uu segment QoS configuration information (such as QoS rules sent to the UE, QoS text sent to the RAN, and PDR (Packet Detection Rule) sent to the UPF). Therefore, Uu segment QoS information can be determined.

[0151] For example, the first core network device mentioned above can be a PCF in the core network.

[0152] For example, the second core network device described above can be an SMF in the core network.

[0153] For example, the QoS information of the PC5 segment and the QoS information of the Uu segment mentioned above can be referred to the foregoing description, and will not be repeated here.

[0154] Optionally, in this embodiment of the application, in step 304 above, the method for splitting end-to-end QoS requirement information provided in this embodiment of the application may include the following step 306:

[0155] Step 306: The first core network device described above splits the end-to-end QoS requirement information according to the target information to obtain PC5 segment QoS information and the first rule.

[0156] For example, the target information mentioned above includes at least one of the following: subscription information of the remote UE, subscription information of the relay UE, payment policy, relay communication policy information authorized by the remote UE, and relay communication policy information authorized by the relay UE.

[0157] For example, the target information described above is used to formulate the splitting strategy information.

[0158] In one example, the subscription information of the remote UE and the subscription information of the relay UE are used to determine whether the terminal authorizes relay communication.

[0159] In one example, the above payment strategy is used to determine the PC5 segment payment information and the Uu segment payment information.

[0160] In this way, the first core network device can obtain the PC5 segment QoS information and the first rule that meet the end-to-end QoS requirements based on the target information, so as to obtain the Uu segment QoS information that meets the end-to-end QoS requirements in the future.

[0161] Figure 8 This diagram illustrates a flowchart of a method for splitting end-to-end QoS requirement information according to an embodiment of the present invention. The method may include steps 307a to 307d:

[0162] For example, when the target core network device includes a first core network device, in step 301 above, the method for splitting end-to-end QoS requirement information provided in this application embodiment may include the following step 307a:

[0163] Step 307a: The first core network device splits the above end-to-end QoS requirement information to obtain the above first rule and the above PC5 segment QoS information.

[0164] Following step 301 above, the method for splitting end-to-end QoS requirement information provided in this application embodiment may include the following step 307b:

[0165] Step 307b: The first core network device sends the aforementioned PC5 segment QoS information and the aforementioned Uu segment QoS information to the access network device.

[0166] Step 307c: The access network device receives PC5 segment QoS information and Uu segment QoS information from the target core network device.

[0167] Step 307d: The access network device establishes the bearer for the PC5 segment and the bearer for the Uu segment based on the QoS information of the PC5 segment and the QoS information of the Uu segment.

[0168] For example, the access network device receives PC5 segment QoS information and Uu segment QoS information from the target core network device; the aforementioned PC5 segment QoS information and Uu segment QoS information are obtained by splitting the end-to-end QoS requirement information.

[0169] For example, the scheme corresponding to step 307 above can be applied to the splitting of end-to-end QoS requirement information in a layer-2 based protocol architecture.

[0170] For example, during the establishment of a PDU session or the direct link change process, the first core network device splits the end-to-end QoS requirement information to obtain the first rule and the PC5 segment QoS information.

[0171] In one example, the aforementioned PDU session can be a PDU session initiated by a terminal-side device (e.g., a remote UE) or a PDU session initiated by a network-side device (e.g., an application server). This application embodiment does not limit this.

[0172] Example 4: In the case of relay communication, taking the target core network equipment including PCF and the communication protocol architecture as a layer-2 based (layer 2 relay) protocol architecture as an example. Figure 9 As shown, the technical solution for PCF to split end-to-end QoS requirement information includes the following steps:

[0173] Step 41: During the establishment or modification of a PDU session, the PCF can decompose the end-to-end QoS requirements based on the aforementioned end-to-end QoS requirement information, operator policy information, and billing information, and decompose the aforementioned end-to-end QoS requirement information into corresponding PCC rules (i.e., the aforementioned first rule) PC5 segment QoS information, wherein the PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes.

[0174] Step 42: PCF sends the above PCC rules and PC5 segment QoS information to SMF.

[0175] Step 43: SMF receives the above PCC rules and PC5 segment QoS information.

[0176] Step 44: Based on the above PCC rules and PC5QoS parameters, SMF generates the QoS text for the Uu segment and the QoS text for the PC5 segment, and sends the above Uu segment QoS text and PC5 segment QoS text to RAN (i.e., the above access network device).

[0177] Step 45: The access network receives the above-mentioned Uu segment QoS text and PC5 segment QoS text.

[0178] Step 46: The access network device RAN establishes the bearer for the Uu segment based on the QoS text of the Uu segment mentioned above, and establishes the bearer for the PC5 segment based on the QoS text of the PC5 segment mentioned above.

[0179] Figure 10 This diagram illustrates a flowchart of a method for splitting end-to-end QoS requirement information according to an embodiment of the present invention. The method may include steps 308a to 308d:

[0180] For example, prior to step 301 above, the method for splitting end-to-end QoS requirement information provided in this application embodiment may include the following steps 308a to 308c:

[0181] Step 308a: The remote UE sends end-to-end QoS requirement information to the relay UE.

[0182] Step 308b: The relay UE receives end-to-end QoS requirement information from the remote UE.

[0183] Step 308c: The relay UE sends the above end-to-end QoS requirement information to the target core network device.

[0184] Based on steps 308a to 308c above, when the target core network device includes a first core network device, in step 302 above, the method for splitting end-to-end QoS requirement information provided in this application embodiment may include the following step 308d:

[0185] Step 308d: The first core network device receives the end-to-end QoS requirement information forwarded by the relay UE through the second core network device.

[0186] For example, the schemes corresponding to steps 309a to 309b above can be applied to the splitting of end-to-end QoS requirement information in a layer-3 based protocol architecture.

[0187] For example, steps 308a to 308d described above can be applied to split end-to-end QoS requirement information in a layer-3 based protocol architecture.

[0188] For example, the aforementioned end-to-end QoS requirement information is sent by the remote UE to the relay UE.

[0189] In this embodiment of the application, the aforementioned end-to-end QoS requirement information can be carried in a direct link modification request message.

[0190] In this embodiment of the application, the aforementioned end-to-end QoS requirement information can be carried in a Remote UE Report message or other NAS information and sent to the target core network device through the Remote UE Report message.

[0191] In this embodiment, the aforementioned end-to-end QoS requirement information represents the parameters and attributes of the corresponding end-to-end QoS requirement information when the end-to-end QoS requirements are met. Specifically, the parameters and attributes of the aforementioned end-to-end QoS requirement information can be referred to the foregoing description, and will not be repeated here.

[0192] In this embodiment of the application, the target core network device can be any device in the core network. For example, SMF.

[0193] In this embodiment of the application, the first core network device and the second core network device described above can be referred to the foregoing description, and will not be repeated here.

[0194] Example 5: In the case where there is a relay UE between the remote UE and the UPF anchor point, taking the first core network device as the PCF and the communication protocol architecture as a layer-2 based (layer 2 relay) protocol architecture as an example. Figure 11 As shown, the technical solution for PCF to split end-to-end QoS requirement information includes the following steps:

[0195] Step 51: The remote UE sends end-to-end QoS requirement information to the relay UE.

[0196] Step 52: The relay UE receives the above end-to-end QoS requirement information.

[0197] Step 53: After receiving the above end-to-end QoS requirement information, the relay UE sends the end-to-end QoS requirement information to the SMF (i.e., the above-mentioned second core network device).

[0198] Step 54: SMF receives the above end-to-end QoS requirement information.

[0199] Step 55: After receiving the end-to-end QoS requirement information, the SMF sends the end-to-end QoS requirement information to the PCF through the SM policy association modification request.

[0200] Step 56: PCF receives the above end-to-end QoS requirement information.

[0201] Step 57: PCF decomposes the end-to-end QoS requirements based on the end-to-end QoS requirement information, operator policy information, and payment information, and decomposes the end-to-end QoS requirement information into corresponding PCC rules (i.e. the first rule mentioned above), PC5QoS parameters (e.g., PQI, GFBR, MFBR, etc.) and PC5QoS attributes (e.g., PDB, PER, Maximum Data Burst Volume (MDBV)).

[0202] Step 58: PCF sends the above PCC rules, PC5QoS parameters and PC5QoS attributes to SMF.

[0203] Step 59: SMF receives the above PCC rules, PC5QoS parameters and PC5QoS attributes.

[0204] Step 5A: SMF determines the Uu segment QoS information (such as Uu segment QoS parameters, Uu segment QoS rules, Uu segment QoS text, etc.) based on the above PCC rules.

[0205] Step 5B: The SMF sends the PDU session change procedure to the relay UE and RAN (i.e., the access network equipment mentioned above). During the PDU session change procedure, the SMF sends the PC5QoS parameters to the relay UE.

[0206] Step 5C: The relay UE receives the QoS parameters of the PC5 segment mentioned above.

[0207] Step 5D: The relay UE performs a direct link change procedure based on the received PC5 segment QoS parameters.

[0208] Optionally, in this embodiment, the target core network device includes a first core network device; in step 308c, the method for splitting end-to-end QoS requirement information provided in this embodiment may include the following step 308c0:

[0209] Step 308c0: The aforementioned relay UE forwards the aforementioned end-to-end QoS requirement information to the aforementioned first core network device through the second core network device.

[0210] For example, the first core network device and the second core network device described above can be referred to the foregoing description, and will not be repeated here.

[0211] In one example, when the first core network device is PCF and the second core network device is SMF, SMF can send the end-to-end QoS requirement information to PCF through a Session Function Policy Association Modification (SM policy association modification) request.

[0212] Figure 12 This diagram illustrates a flowchart of a method for splitting end-to-end QoS requirement information according to an embodiment of the present invention. The method may include steps 309a to 309d:

[0213] Optionally, in this embodiment of the application, the target core network device includes a second core network device. Before step 303, in step 301, the method for splitting end-to-end QoS requirement information provided in this embodiment of the application may include the following step 309a:

[0214] Step 309a: The aforementioned second core network device splits the end-to-end QoS requirement information to obtain PC5 segment QoS information and Uu segment QoS information.

[0215] Following step 301 above, the method for splitting end-to-end QoS requirement information provided in this application embodiment may include the following step 309b:

[0216] Step 309b: The second core network device sends the aforementioned PC5 segment QoS information and the aforementioned Uu segment QoS information to the access network device.

[0217] Step 309c: The access network device receives PC5 segment QoS information and Uu segment QoS information from the second core network device.

[0218] Step 309d: The access network device establishes the bearer for the PC5 segment and the bearer for the Uu segment based on the QoS information of the PC5 segment and the QoS information of the Uu segment.

[0219] For example, the access network device receives PC5 segment QoS information and Uu segment QoS information from the target core network device; the aforementioned PC5 segment QoS information and Uu segment QoS information are obtained by splitting the end-to-end QoS requirement information.

[0220] For example, the schemes corresponding to steps 309a to 309b above can be applied to the splitting of end-to-end QoS requirement information in a layer-2 based protocol architecture.

[0221] For example, the aforementioned second core network device can be described in the foregoing description, and will not be repeated here.

[0222] For example, the QoS information of the PC5 segment and the QoS information of the Uu segment mentioned above can be referred to the foregoing description, and will not be repeated here.

[0223] Optionally, in this embodiment of the application, in step 309 above, the method for splitting end-to-end QoS requirement information provided in this embodiment of the application may include the following step 310:

[0224] Step 310: The second core network device described above splits the end-to-end QoS requirement information according to the target information to obtain PC5 segment QoS information and Uu segment QoS information.

[0225] For example, the target information mentioned above includes at least one of the following: subscription information of the remote UE, subscription information of the relay UE, payment policy, relay communication policy information authorized by the remote UE, and relay communication policy information authorized by the relay UE.

[0226] For example, the aforementioned contract information, payment strategy, and relay communication strategy information can be referred to the foregoing description, and will not be repeated here.

[0227] Example 6: In the case where there is a relay UE between the remote UE and the UPF anchor point, taking the second core network device as SMF and the communication protocol architecture as a layer-2 based (layer 2 relay) protocol architecture as an example. Figure 13 As shown, the technical solution for splitting end-to-end QoS requirement information using SMF includes the following steps:

[0228] Step 61: Based on the above end-to-end QoS requirement information, operator policy information and billing information, SMF performs end-to-end QoS requirement splitting and generates Uu segment QoS text and PC5 segment QoS text.

[0229] Step 62: The SMF sends the Uu segment QoS text and PC5 segment QoS text to the RAN (i.e., the access network device mentioned above).

[0230] Step 63: The access network device RAN receives the above-mentioned Uu segment QoS text and PC5 segment QoS text.

[0231] Step 64: The access network device RAN establishes the bearer for the Uu segment based on the QoS text of the Uu segment mentioned above, and establishes the bearer for the PC5 segment based on the QoS text of the PC5 segment mentioned above.

[0232] Optionally, in this embodiment of the application, the method for splitting end-to-end QoS requirement information provided in this embodiment of the application, which involves sending the PC5 segment QoS information and the Uu segment QoS information to the access network device in step 303, may include the following step 311:

[0233] Step 311: The target core network device sends the PC5 segment QoS information and the Uu segment QoS information to the access network device through the PDU session establishment and direct link change process.

[0234] Optionally, in this embodiment, the PC5 segment QoS information includes PC5 segment QoS text, and the Uu segment QoS information includes Uu segment QoS text.

[0235] For example, the aforementioned Uu segment QoS text can be used to represent Uu segment QoS information, and correspondingly, the aforementioned PC5 segment QoS text can be used to represent PC5 segment QoS information.

[0236] It should be noted that the end-to-end QoS requirement information splitting method provided in this application embodiment can be executed by an end-to-end QoS requirement information splitting device, or by a control module in the end-to-end QoS requirement information splitting device for executing the end-to-end QoS requirement information splitting method. This application embodiment uses the execution of the end-to-end QoS requirement information splitting method by the end-to-end QoS requirement information splitting device as an example to illustrate the end-to-end QoS requirement information splitting device provided in this application embodiment.

[0237] Figure 14 To illustrate a possible structural diagram of the end-to-end QoS requirement information splitting device provided in the embodiments of this application, as follows: Figure 14 As shown, the end-to-end QoS requirement information splitting device 500 includes: a splitting module 501; the splitting module 501 is used to split the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, and the target device includes the target UE and the access network device.

[0238] In this embodiment, the end-to-end QoS requirement information splitting device splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information. Thus, the subject of splitting end-to-end QoS requirement information is no longer limited to network-side devices, and the splitting scenarios can become more diverse and richer, facilitating the splitting of end-to-end QoS requirement information in any scenario.

[0239] Optionally, in this embodiment, the PC5 segment QoS information and the Uu segment QoS information satisfy the end-to-end QoS requirement information.

[0240] Optionally, in this embodiment, the PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes; the PC5 segment QoS parameters include PQI, and the PC5 segment QoS attributes include PDB; the Uu segment QoS information includes Uu segment QoS parameters and Uu segment QoS attributes; the Uu segment QoS parameters include 5QI; and the Uu segment QoS attributes include PDB.

[0241] Optionally, in this embodiment of the application, when the target UE is the remote UE, the end-to-end QoS requirement information splitting device 500 may further include: a sending module 502; the sending module 502 is used to send the Uu segment QoS information and the PC5 segment QoS information split by the splitting module 501 to the relay UE; wherein, the Uu segment QoS information is used by the relay UE to establish a corresponding Uu segment QoS flow during the PDU session establishment or modification process; the PC5 segment QoS information is used by the relay UE to establish a corresponding PC5 segment QoS flow during the direct link modification process.

[0242] Optionally, in this embodiment of the application, when the target UE is the relay UE, the end-to-end QoS requirement information splitting device 500 may further include: a receiving module 503 and an establishing module 504; the receiving module 503 is used to receive the end-to-end QoS requirement information from the remote UE; the establishing module is used to initiate a PDU session establishment or modification process based on the Uu segment QoS information split by the splitting module 501, and establish a corresponding Uu segment QoS flow, and the relay UE initiates a direct link modification process based on the PC5 segment QoS information to establish a corresponding PC5 segment QoS flow.

[0243] Optionally, in this embodiment, the aforementioned splitting module is specifically used to split the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information according to the first mapping relationship or the first information; wherein, the aforementioned first mapping relationship includes: the mapping relationship between the aforementioned end-to-end QoS requirement information and the aforementioned PC5 segment QoS information and the aforementioned Uu segment QoS information; the aforementioned first information includes: the QoS parameters of the PC5 interface and the QoS parameters of the Uu interface detected by the aforementioned target UE.

[0244] Optionally, in this embodiment of the application, the first mapping relationship described above is configured on the network side or pre-configured.

[0245] Optionally, in this embodiment of the application, when the target device is the access network device, the end-to-end QoS requirement information splitting device 500 may further include a building module 504; the building module is used to build the bearer of the PC5 segment according to the PC5 segment QoS information split by the splitting module 501, and to build the bearer of the Uu segment according to the Uu segment QoS information.

[0246] Optionally, in this embodiment of the application, when the target device is the access network device, the splitting module 501 is specifically used to split the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information according to the second mapping relationship or the second information; wherein, the second mapping relationship includes: the mapping relationship between the end-to-end QoS requirement information and the PC5 segment QoS information and the Uu segment QoS information; the second information includes: the QoS parameters of the PC5 interface and the QoS parameters of the Uu interface detected by the access network device.

[0247] Optionally, in this embodiment of the application, the second mapping relationship described above is configured on the network side or pre-configured.

[0248] Figure 15 To illustrate a possible structural diagram of the end-to-end QoS requirement information splitting device provided in the embodiments of this application, as follows: Figure 15 As shown, the end-to-end QoS requirement information splitting device 600 includes: a sending module 601; the sending module 601 is used to send end-to-end QoS requirement information to the access network device, the end-to-end QoS requirement information including end-to-end QoS requirement text.

[0249] Figure 16 To illustrate a possible structural diagram of the end-to-end QoS requirement information splitting device provided in the embodiments of this application, as follows: Figure 16 As shown, the end-to-end QoS requirement information splitting device 700 includes: a splitting module 701, a receiving module 702, and a sending module 703; the splitting module 701 is used to split the end-to-end QoS requirement information to obtain PC5 segment QoS information and Uu segment QoS information; the receiving module 702 is used to receive the end-to-end QoS requirement information from a relay UE, and the end-to-end QoS requirement information is sent to the relay UE by a remote UE; or, the sending module 703 is used to send the PC5 segment QoS information and the Uu segment QoS information split by the splitting module 701 to the access network device; wherein, the PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes; the PC5 segment QoS parameters include PQI, and the PC5 segment QoS attributes include PDB; the Uu segment QoS information includes Uu segment QoS parameters and Uu segment QoS attributes; the Uu segment QoS parameters include 5QI; and the Uu segment QoS attributes include PDB.

[0250] Optionally, in this embodiment, the end-to-end QoS requirement information splitting device further includes: the target core network device includes a first core network device and a second core network device; the splitting module 701 is specifically used to split the end-to-end QoS requirement information to obtain PC5 segment QoS information and a first rule; the sending module 703 is further used to send the PC5 segment QoS information and the first rule split by the splitting module 701 to the second core network device; the first rule is used by the second core network device to generate Uu segment QoS information.

[0251] Optionally, in this embodiment of the application, the above-mentioned splitting module 701 is specifically used to split the end-to-end QoS requirement information according to the target information to obtain PC5 segment QoS information and the first rule; wherein, the above-mentioned target information includes at least one of the following: subscription information of the remote UE, subscription information of the relay UE, payment policy, relay communication policy information authorized by the remote UE, and relay communication policy information authorized by the relay UE.

[0252] Optionally, in this embodiment of the application, when the target core network device includes a first core network device, the splitting module 701 is specifically used to split the end-to-end QoS requirement information to obtain the first rule and the PC5 segment QoS information.

[0253] Optionally, in this embodiment of the application, when the target core network device includes a first core network device, the receiving module 702 is specifically used to receive the end-to-end QoS requirement information forwarded by the relay UE through the second core network device, wherein the end-to-end QoS requirement information is sent by the remote UE to the relay UE.

[0254] Optionally, in this embodiment of the application, the target core network device includes a second core network device, and the splitting module 701 is specifically used to split the end-to-end QoS requirement information to obtain PC5 segment QoS information and Uu segment QoS information.

[0255] Optionally, in this embodiment of the application, the above-mentioned splitting module 701 is specifically used to split the end-to-end QoS requirement information according to the target information to obtain PC5 segment QoS information and Uu segment QoS information; wherein, the above-mentioned target information includes at least one of the following: subscription information of remote UE, subscription information of relay UE, payment policy, relay communication policy information authorized by the above-mentioned remote UE, and relay communication policy information authorized by the above-mentioned relay UE.

[0256] Optionally, in this embodiment of the application, the sending module 703 is specifically used to send the PC5 segment QoS information and the Uu segment QoS information to the access network device through the PDU session establishment and direct link change process.

[0257] Optionally, in this embodiment, the PC5 segment QoS information includes PC5 segment QoS text, and the Uu segment QoS information includes Uu segment QoS text.

[0258] Figure 17 To illustrate a possible structural diagram of the end-to-end QoS requirement information splitting device provided in the embodiments of this application, as follows: Figure 17 As shown, the end-to-end QoS requirement information splitting device 800 includes: a receiving module 801 and an establishing module 802; the receiving module 801 is used to receive PC5 segment QoS information and Uu segment QoS information from the target core network device; the PC5 segment QoS information and the Uu segment QoS information are obtained by splitting the end-to-end QoS requirement information; the establishing module 802 is used to establish the PC5 segment bearer and the Uu segment bearer based on the PC5 segment QoS information and the Uu segment QoS information.

[0259] Figure 18 To illustrate a possible structural diagram of the end-to-end QoS requirement information splitting device provided in the embodiments of this application, as follows: Figure 18 As shown, the end-to-end QoS requirement information splitting device 900 includes: a receiving module 901 and a sending module 902; the receiving module 901 is used to receive end-to-end QoS requirement information from a remote UE; the sending module 902 is used to send the end-to-end QoS requirement information received by the receiving module 901 to a target core network device.

[0260] Optionally, in this embodiment of the application, the target core network device includes a first core network device; the sending module 902 is specifically used to forward the end-to-end QoS requirement information to the first core network device through the second core network device.

[0261] The end-to-end QoS requirement information splitting device in this application embodiment can be a device, or it can be a component, integrated circuit, or chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminal 11 listed above, and a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not make specific limitations.

[0262] The end-to-end QoS requirement information splitting device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit it.

[0263] The end-to-end QoS requirement information splitting device provided in this application embodiment can achieve... Figures 2 to 13 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0264] Optional, such as Figure 19 As shown, this application embodiment also provides a communication device 1900, including a processor 1901, a memory 1902, and a program or instructions stored in the memory 1902 that can run on the processor 1901. For example, when the communication device 1900 is a terminal, the program or instructions executed by the processor 1901 implement the various processes of the above-described end-to-end QoS requirement information splitting method embodiment, and achieve the same technical effect. When the communication device 1900 is a network-side device, the program or instructions executed by the processor 1901 implement the various processes of the above-described end-to-end QoS requirement information splitting method embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0265] Figure 20 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0266] The terminal 100 includes, but is not limited to, components such as: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0267] Those skilled in the art will understand that the terminal 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 20 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0268] It should be understood that, in this embodiment, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0269] In this embodiment, the radio frequency unit 101 receives downlink data from the network-side device and processes it for the processor 110; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0270] The memory 109 can be used to store software programs or instructions and various data. The memory 109 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include high-speed random access memory and non-volatile memory, which may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0271] Processor 110 may include one or more processing units; optionally, processor 110 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0272] When the electronic device 100 is the target device, the processor 110 is used to split the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information. The target device includes the target UE and the access network device.

[0273] In this embodiment, the target device splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information. Thus, the subject of splitting the end-to-end QoS requirement information is no longer limited to network-side devices, allowing for more diverse and varied splitting scenarios, facilitating the splitting of end-to-end QoS requirement information in any scenario.

[0274] Optionally, when the target UE is the remote UE, the radio frequency unit 101 is used to send the Uu segment QoS information and the PC5 segment QoS information to the relay UE; wherein, the Uu segment QoS information is used by the relay UE to establish a corresponding Uu segment QoS flow during the PDU session establishment or modification process; the PC5 segment QoS information is used by the relay UE to establish a corresponding PC5 segment QoS flow during the direct link modification process.

[0275] Optionally, when the target UE is the relay UE, the user input unit 107 is configured to receive the end-to-end QoS requirement information from the remote UE; the processor 110 is further configured to initiate a PDU session establishment or modification process based on the Uu segment QoS information received by the user input unit 107, and establish a corresponding Uu segment QoS flow, and the relay UE initiates a direct link modification process based on the PC5 segment QoS information to establish a corresponding PC5 segment QoS flow.

[0276] Optionally, the processor 110 is specifically configured to split the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information according to the first mapping relationship or the first information; wherein, the first mapping relationship includes: the mapping relationship between the end-to-end QoS requirement information and the PC5 segment QoS information and the Uu segment QoS information; the first information includes: the QoS parameters of the PC5 interface and the QoS parameters of the Uu interface detected by the target UE.

[0277] When the electronic device 100 is a relay UE, the processor 110 is used to receive end-to-end QoS requirement information from the remote UE; the processor 110 is also used to send the end-to-end QoS requirement information to the target core network device.

[0278] Specifically, embodiments of this application also provide a network-side device. For example... Figure 21As shown, the network-side device 210 includes an antenna 211, a radio frequency (RF) device 212, and a baseband device 213. The antenna 211 is connected to the RF device 212. In the uplink direction, the RF device 212 receives information through the antenna 211 and transmits the received information to the baseband device 213 for processing. In the downlink direction, the baseband device 213 processes the information to be transmitted and sends it to the RF device 212. The RF device 212 processes the received information and transmits it through the antenna 211.

[0279] The aforementioned frequency band processing device can be located in the baseband device 213. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 213, which includes a processor 214 and a memory 215.

[0280] Baseband device 213 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 21 As shown, one of the chips, for example, is a processor 214, which is connected to a memory 215 to call the program in the memory 215 and execute the network device operation shown in the above method embodiment.

[0281] The baseband device 213 may also include a network interface 216 for exchanging information with the radio frequency device 212, such as a common public radio interface (CPRI).

[0282] Specifically, the network-side device in this embodiment of the invention further includes: instructions or programs stored in memory 215 and executable on processor 214, wherein processor 214 calls the instructions or programs in memory 215 to execute... Figures 14 to 18 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0283] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described end-to-end QoS requirement information splitting method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0284] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0285] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run network-side device programs or instructions to implement the various processes of the above-described end-to-end QoS requirement information splitting method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0286] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0287] 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. Without further limitations, 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. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0288] 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 software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic 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.

[0289] 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 method for splitting end-to-end QoS requirement information, characterized in that, The method includes: The target UE splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, wherein the PC5 segment QoS information and the Uu segment QoS information satisfy the end-to-end QoS requirement information; When the target UE is a relay UE, before the target UE splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, the method further includes: The relay UE receives the end-to-end QoS requirement information from the remote UE; After the target UE splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, the method further includes: The relay UE initiates a PDU session establishment or modification process based on the Uu segment QoS information to establish a corresponding Uu segment QoS flow. The relay UE initiates a direct link modification process based on the PC5 segment QoS information to establish a corresponding PC5 segment QoS flow. The target UE splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, including: The target UE splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information according to the first mapping relationship or the first information; The first mapping relationship includes: the mapping relationship between the end-to-end QoS requirement information and the PC5 segment QoS information and the Uu segment QoS information; The first information includes: the QoS parameters of the PC5 interface and the QoS parameters of the Uu interface detected by the target UE.

2. The method according to claim 1, characterized in that, The PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes; the PC5 segment QoS parameters include PQI, and the PC5 segment QoS attributes include PDB; the Uu segment QoS information includes Uu segment QoS parameters and Uu segment QoS attributes; the Uu segment QoS parameters include 5QI; the Uu segment QoS attributes include PDB.

3. The method according to claim 1, characterized in that, When the target UE is a remote UE, after the target UE splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, the method further includes: The remote UE sends the Uu segment QoS information and the PC5 segment QoS information to the relay UE; The Uu segment QoS information is used by the relay UE to establish the corresponding Uu segment QoS flow during the PDU session establishment or modification process; the PC5 segment QoS information is used by the relay UE to establish the corresponding PC5 segment QoS flow during the direct link modification process.

4. The method according to claim 1, characterized in that, The first mapping relationship is configured or pre-configured on the network side.

5. A method for splitting end-to-end QoS requirement information, characterized in that, The method includes: The target core network equipment splits the end-to-end QoS requirement information according to the target information to obtain PC5 segment QoS information and Uu segment QoS information. The target information includes at least one of the following: subscription information of remote UE, subscription information of relay UE, payment policy, relay communication policy information authorized by the remote UE, and relay communication policy information authorized by the relay UE. Before the target core network device splits the end-to-end QoS requirement information, the end-to-end QoS requirement information is received from the relay UE, and the end-to-end QoS requirement information is sent to the relay UE by the remote UE; or, after the target core network device splits the end-to-end QoS requirement information, the PC5 segment QoS information and the Uu segment QoS information are sent to the access network device; wherein, the PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes; the PC5 segment QoS parameters include PQI, and the PC5 segment QoS attributes include PDB; the Uu segment QoS information includes Uu segment QoS parameters and Uu segment QoS attributes; the Uu segment QoS parameters include 5QI; and the Uu segment QoS attributes include PDB.

6. The method according to claim 5, characterized in that, The target core network equipment includes a first core network equipment and a second core network equipment. The target core network equipment splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, including: The first core network device splits the end-to-end QoS requirement information to obtain PC5 segment QoS information and the first rule; The first core network device sends the PC5 segment QoS information and the first rule to the second core network device; the first rule is used by the second core network device to generate Uu segment QoS information.

7. The method according to claim 6, characterized in that, The first core network device splits the end-to-end QoS requirement information to obtain PC5 segment QoS information and the first rule, including: The first core network device splits the end-to-end QoS requirement information according to the target information to obtain PC5 segment QoS information and the first rule.

8. The method according to claim 5, characterized in that, When the target core network device includes a first core network device, the target core network device splits the end-to-end QoS requirement information to obtain PC5 segment QoS information and Uu segment QoS information, including: The first core network device splits the end-to-end QoS requirement information to obtain the first rule and the PC5 segment QoS information.

9. The method according to claim 5, characterized in that, When the target core network device includes a first core network device, receiving the end-to-end QoS requirement information from the relay UE includes: The first core network device receives the end-to-end QoS requirement information forwarded by the relay UE through the second core network device. The end-to-end QoS requirement information is sent by the remote UE to the relay UE.

10. The method according to claim 5, characterized in that, The target core network device includes a second core network device. Before sending the PC5 segment QoS information and the Uu segment QoS information to the access network device, the target core network device splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, including: The second core network device splits the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information.

11. The method according to claim 10, characterized in that, The second core network device splits the end-to-end QoS requirement information to obtain PC5 segment QoS information and Uu segment QoS information, including: The second core network device splits the end-to-end QoS requirement information according to the target information to obtain PC5 segment QoS information and Uu segment QoS information.

12. The method according to claim 5, characterized in that, The step of sending the PC5 segment QoS information and the Uu segment QoS information to the access network device includes: The target core network device sends the PC5 segment QoS information and the Uu segment QoS information to the access network device through the PDU session establishment and direct link change process.

13. The method according to any one of claims 5-12, characterized in that, The PC5 segment QoS information includes PC5 segment QoS text, and the Uu segment QoS information includes Uu segment QoS text.

14. A device for splitting end-to-end QoS requirement information, characterized in that, The device includes: a splitting module; The splitting module is used to split the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information. The PC5 segment QoS information and the Uu segment QoS information satisfy the end-to-end QoS requirement information. The receiving module is used to receive the end-to-end QoS requirement information from the remote UE before splitting the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information when the target UE is a relay UE. The module is used to, after splitting the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information, initiate a PDU session establishment or modification process based on the Uu segment QoS information to establish the corresponding Uu segment QoS flow, and initiate a direct link modification process based on the PC5 segment QoS information to establish the corresponding PC5 segment QoS flow. The splitting module is specifically used to split the end-to-end QoS requirement information into PC5 segment QoS information and Uu segment QoS information according to the first mapping relationship or the first information. The first mapping relationship includes: the mapping relationship between the end-to-end QoS requirement information and the PC5 segment QoS information and the Uu segment QoS information; the first information includes: the QoS parameters of the PC5 interface and the QoS parameters of the Uu interface detected by the target UE.

15. A device for splitting end-to-end QoS requirement information, characterized in that, The device includes: a splitting module, a receiving module, and a transmitting module; The splitting module is used to split the end-to-end QoS requirement information according to the target information to obtain PC5 segment QoS information and Uu segment QoS information. The target information includes at least one of the following: subscription information of remote UE, subscription information of relay UE, payment policy, relay communication policy information authorized by the remote UE, and relay communication policy information authorized by the relay UE. The receiving module is used to receive the end-to-end QoS requirement information from the relay UE before the target core network device splits the end-to-end QoS requirement information. The end-to-end QoS requirement information is sent to the relay UE by the remote UE. or, The sending module is used to send the PC5 segment QoS information and the Uu segment QoS information to the access network device after the target core network device splits the end-to-end QoS requirement information; The PC5 segment QoS information includes PC5 segment QoS parameters and PC5 segment QoS attributes; the PC5 segment QoS parameters include PQI, and the PC5 segment QoS attributes include PDB; the Uu segment QoS information includes Uu segment QoS parameters and Uu segment QoS attributes; the Uu segment QoS parameters include 5QI; and the Uu segment QoS attributes include PDB.

16. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the end-to-end QoS requirement information splitting method as described in any one of claims 1 to 4.

17. A network-side device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the end-to-end QoS requirement information splitting method as described in any one of claims 5 to 13.

18. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the method for splitting end-to-end QoS requirement information as described in any one of claims 1 to 4, or implement the steps of the method for splitting end-to-end QoS requirement information as described in any one of claims 5 to 13.

Images