WO2023019895A1 - Procédé de transmission de paquet de données sur la base de la qualité de service d'un réseau, et dispositif associé - Google Patents
Procédé de transmission de paquet de données sur la base de la qualité de service d'un réseau, et dispositif associé Download PDFInfo
- Publication number
- WO2023019895A1 WO2023019895A1 PCT/CN2022/076794 CN2022076794W WO2023019895A1 WO 2023019895 A1 WO2023019895 A1 WO 2023019895A1 CN 2022076794 W CN2022076794 W CN 2022076794W WO 2023019895 A1 WO2023019895 A1 WO 2023019895A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network node
- sent
- mapping relationship
- qos
- data packet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
Definitions
- the present application mainly relates to the technical field of wireless communication, and more specifically relates to a data packet transmission method and related equipment based on network quality of service.
- the first network node (such as user equipment UE, or T-Node defined by Sparklink) passes through the second network node (such as trusted non-3GPP access node TNAP, or G-Node defined by Sparklink), the third Network nodes (such as Trusted Non-3GPP Gateway Function (TNGF) and 5G (5th Generation, fifth generation) core network perform data packet transmission.
- the second network node such as trusted non-3GPP access node TNAP, or G-Node defined by Sparklink
- the third Network nodes such as Trusted Non-3GPP Gateway Function (TNGF) and 5G (5th Generation, fifth generation) core network perform data packet transmission.
- TNGF Trusted Non-3GPP Gateway Function
- 5G (5th Generation, fifth generation, fifth generation) core network perform data packet transmission.
- the Sparklink user plane protocol stack in the 5G communication network structure it usually refers to the user plane protocol stack accessed by the trusted non-3GPP (3rd Generation Partnership Project, third generation partnership project), such as directly using the non- The 3GPP access layer protocol is replaced by the Sparklink access layer, and two user plane protocol stacks are obtained as shown in Figure 1a and Figure 1b, so that in the application of uplink data packet/downlink data packet transmission of the user equipment UE, it can be realized accordingly End-to-end QoS (Quality of Service, service quality) management, to meet the QoS requirements of the corresponding application business.
- QoS Quality of Service, service quality
- GRE Generic Routing Encapsulation, general routing encapsulation
- Inner IP and IPSec protocol stack between the first network node and the third network node
- GTP-U GPRS Tunnel Protocol-User, user plane GPRS Tunneling Protocol
- UDP User Datagram Protocol
- an end-to-end IPSec child security channel IPSec Child Security Association
- the first network node and the third network node directly establish an end-to-end GTP-U tunnel.
- the second network node cannot determine the The QoS requirements of the data packets transmitted by the U tunnel can easily cause the processing of the data packets by the second network node to fail to meet the actual QoS requirements, affecting the efficiency and reliability of data packet transmission.
- the present application provides a data packet transmission method based on network quality of service, the method comprising:
- the traffic mapping information includes a first mapping relationship between different first IP header information and different quality of service QoS information
- the first IP header information includes the first network The local IP address of the node and the second IP header information
- the second IP header information includes a priority attribute value configured for the first channel between the first network node and the third network node
- the QoS information includes QoS parameters, or QoS parameters and QoS identifiers
- the second channel information is used to identify the first network node a second channel with a second network node;
- the obtaining the second channel information and QoS parameters of the data packets to be sent according to the first mapping relationship and the first IP header information of the data packets to be sent includes:
- the first identifier is used to identify access to the second network node each of the first network nodes;
- Figure 1a is a schematic diagram of an optional structure of the Sparklink user plane protocol stack based on IPSec;
- FIG. 3 is a schematic diagram of a system architecture in an optional application environment for realizing the data packet transmission method based on network quality of service proposed by the present application;
- FIG. 6 is a schematic flowchart of another optional example of a data packet transmission method based on network quality of service implemented by the first network node side proposed in this application;
- FIG. 8 is a schematic flow diagram of another optional example of a data packet transmission method based on network quality of service implemented by the second network node side proposed in this application;
- FIG. 10 is a schematic diagram of a signaling flow of another optional example of a data packet transmission method based on network quality of service proposed by the present application.
- FIG. 13 is a schematic structural diagram of another optional example of a data packet transmission device based on network quality of service proposed in this application;
- the first network node after the first network node applies to the core network to establish a PDU session, it can obtain at least one QoS flow identifier (QFI, QoS Flow Identifier) included in the PDU session provided by the core network
- QFI QoS flow identifier
- QFI QoS flow identifier
- the application layer of the first network node When the application layer of the first network node subsequently generates a data packet, after the first network node determines the PDU session associated with the data packet, it can determine the QFI associated with the data packet based on the QoS rule, and the implementation process will not be described in detail in this application.
- the second network node can only obtain the IP header information (such as DSCP value) of the received data packet, and realize the processing of the data packet on the second channel (such as Sparklink air interface or other non-3GPP air interface), but cannot know the transmission
- the specific QoS requirements of the data packet will not be able to achieve precise QoS parameter control, which will lead to the inconsistency between the QoS processing implemented by the second network node based on the DSCP value and the specific QoS requirements of the corresponding data packet, and it will not be possible to truly realize the first network node. End-to-end QoS requirements for data packet transmission between nodes in the third network.
- this application hopes that the sending end of the data packet, such as the first network node or the second network node, can accurately obtain the specific QoS parameters corresponding to the data packet, so as to meet different QoS control requirements.
- the unified data management (UDM, Unified Data Management) network element of the core network passes through the access and mobility management function (AMF, Access and Mobility Management Function) network element, through the N2 interface
- AMF Access and Mobility Management Function
- the AMF of the core network since the AMF of the core network will send a PDU session establishment acceptance message to the first network node, which contains QoS parameters, the first network node will receive Redundant QoS parameters cause a waste of storage resources; moreover, the AMF of the core network sends the mapping relationship A to the third network node through the N2 interface, which requires modifying the traditional N2 interface message to enable it to support the mapping relationship
- the transmission of A reduces the processing of messages; in addition, compared with the mapping relationship contained in the traditional PDU session request message, the core network UDM needs to establish the mapping relationship A, which requires adjustment of the UDM processing function, which increases the workload and reduces the Processing efficiency.
- this application proposes to provide corresponding indication information, that is, to indicate whether to send QoS parameters to the first network node. For example, in the above implementation process, it is possible to instruct AMF not to send The first network node feeds back the QoS parameters to solve the redundancy problem, but cannot solve the above-mentioned other technical problems.
- the 5G wireless network architecture and the 5G air interface protocol stack structure referring to Figure 3, it is a schematic diagram of the system architecture in the application environment for implementing the network quality of service-based data packet transmission method proposed in this application.
- the components of its system architecture may include but are not limited to: the first network node 100, the second network node 200, the third network node 300, and the core network 400, wherein:
- the first network node can access the 5G core network through the access network to realize communication with other data networks DN, and the entire communication architecture can be determined in conjunction with the 5G wireless network architecture, which will not be described in detail in this application.
- the application plane protocol followed by the first network node can be combined with the relevant description of the 5G air interface protocol stack structure above, which is not described in detail in this embodiment of the present application.
- the core network 400 can be used to separate the control plane and the user plane, and can transfer call requests or data requests sent by the user side to different data networks to meet service requirements.
- the core network of this application may be a 5G core network (i.e. 5GC), which mainly includes AMF, UPF and SMF (Session Management Function, session management function). Do elaborate.
- the core network 400 can be connected to the corresponding data network DN to meet the business needs of the corresponding scenarios. detail.
- a flow chart is used in this application to illustrate the operations performed by the system or its constituent devices according to the embodiment of this application. It should be understood that the preceding or following operations are not necessarily performed in the exact order. Instead, various steps may be processed in reverse order or simultaneously. At the same time, other operations can also be added to these processes, or a certain step or several steps of operations can be removed from these processes, and the present application does not describe in detail one by one.
- Step S11 obtaining the PDU session identifier, QoS flow identifier and QoS parameters of the data packet to be sent;
- the first network node can apply to the 5G core network for establishing a PDU session, and after receiving the PDU session establishment request, the 5G core network can determine the PDU session identifier of the applied PDU session (used to distinguish Different PDU sessions), and information such as QoS flow identifiers (ie, QFI) and QoS parameters (ie, QoS flow-level QoS parameters) corresponding to one or more QoS flows included in the PDU session.
- QoS flow identifiers ie, QFI
- QoS parameters ie, QoS flow-level QoS parameters
- a PDU session establishment acceptance message is formed.
- the first network node may receive a PDU session establishment acceptance message sent by the core network for the PDU session that it applies for establishment.
- the PDU session identifier of the PDU session establishment acceptance message can correspond to at least one QFI
- the QFI corresponds to the QoS parameters one by one, that is, each QoS flow contained in the PDU session has a corresponding QFI and QoS parameter.
- the QoS parameters may include, but are not limited to, dynamic 5QI (QoS identifier defined by 5G) descriptors (for dynamically allocated QFIs), non-dynamic 5QI descriptors (for non-dynamically allocated QFIs), allocation and Preserve priority, GBR QoS flow information, reflective QoS attributes, additional QoS flow information, etc.
- the NAS message (PDU session acceptance message) includes the QoS parameter, that is, the core network
- the network may send the PDU session identifier, the QoS flow identifier and corresponding QoS parameters to the first network node.
- the first network node may acquire the PDU session identifier, QoS flow identifier and QoS parameters corresponding to the data packets to be sent from the core network, wherein the QoS parameters are corresponding QoS parameters determined according to the QFI associated with the data packets to be sent.
- GBR QoS Flow Information can include maximum flow bit rate downlink, maximum flow bit rate uplink, guaranteed flow bit rate downlink, guaranteed flow bit rate uplink, notification control, maximum packet loss rate downlink, maximum packet loss rate uplink, list of alternative QoS parameter settings, etc.
- the content of QoS requirements included in the QoS parameters corresponding to each QoS flow can be determined according to actual application requirements, which is not limited in this application.
- the NAS message sent by the SMF of the core network to the first network node through the AMF may include, in addition to the above-mentioned PDU session identifier, at least one QFI and its corresponding QoS parameter (optional), the QoS message corresponding to the QFI Rule (that is, QoS rule), the QoS rule may include a packet filter device (Packet Filter Set).
- the parameters of its data packet filtering device may include but not limited to the parameter content shown in the following table 1:
- the first network node may first determine the PDU session corresponding to the data packet to be sent, that is, determine the PDU session identifier of the data packet to be sent. Afterwards, according to the mapping relationship between the QoS rule corresponding to the PDU session and the QFI, the data packet to be sent can be matched through the data packet filtering device to obtain the QFI of the data packet to be sent, that is, to determine which PDU session the data packet to be sent belongs to For the QoS flow, the QFI and QoS parameters of the QoS flow are determined as the QoS flow identifier and QoS parameters of the data packet to be sent. The specific acquisition process of the QoS parameters of the data packets to be sent is as described above.
- each QoS flow included in the PDU session may be mapped to a different first channel, that is, an IPSec sub-secure channel or a GTP-U tunnel between the first network node and the third network node, so that different first Channels have QoS parameters corresponding to the QoS flow level of one or more QoS flows, and thus determine the corresponding DSCP value (determined based on IPv4 (Internet Protocol Version 4, Internet Protocol Version 4) protocol requirements), or determine For the corresponding DSCP value and IPv6 flow label (flow label), this application does not describe in detail the implementation process of determining DSCP and IPv6 flow label.
- the first network node in order to enable the first network node to determine the first network node that transmits the mapping of the data packet to be sent to the second network node according to one or more contents of the received PDU session resource request message.
- the first network node may obtain the third mapping relationship determined for the above-mentioned PDU session (that is, the PDU session to which the data packet to be sent is mapped) that it applies to establish.
- the third mapping relationship may be established by the second network node and/or the third network node accessed by the first network node and sent to the first network node, that is, the first network node may receive
- the third mapping relationship sent by the third network node may also receive the third mapping relationship sent by the second network node, and may also receive a part of the mapping relationship included in the third mapping relationship sent by the third network node, and receive the third mapping relationship sent by the second network node
- the sent third mapping relationship includes another part of the mapping relationship, etc., and this application does not limit the way of obtaining the third mapping relationship.
- the third network node may be determined by the third network node or the second network node and then sent to the first network node, or it may be determined by the third network node and the second network node and then sent to the first network node.
- the network node is not determined by the core network to determine the mapping relationship and sent to the third network node, without changing the core network protocol standard and functional configuration.
- the above-mentioned third mapping relationship may represent the mapping relationship among information such as PDU session identifier, QoS flow identifier, QoS identifier, first channel information, second IP packet header information, and second channel information. It needs to be explained that between different information
- the mapping relationship can be a direct mapping relationship or an indirect mapping relationship, which can be analyzed and described in conjunction with the context, and will not be described in detail in this embodiment.
- the QoS identifier may not be included in the third mapping relationship, and the corresponding QoS identifier is determined according to information such as protocol rules and QoS flow identifiers when necessary.
- the second IP packet header information may include the priority attribute value for the first channel configuration between the first network node and the third network node, such as for the first channel established (such as the established IPSec For different first channels, the configured DSCP or (DSCP, IPv6 flow identifier) is often different.
- the above-mentioned second channel information can include the second channel identifier of the second channel (such as Sparklink air interface, non-3GPP air interface, etc., which can be determined according to the type of access network) between the first network node and the second network node.
- the second channel identifier may be different, which may be a transmission channel identifier TCID, a logical channel identifier LCID, and at least one of WLAN (Wireless Local Area Network, wireless local area network) access classification (AC, Access Category) one.
- TCID transmission channel identifier
- LCID logical channel identifier
- AC Access Category
- the QoS flow identifier and the QoS identifier of the QoS flow may have a 1:1 mapping relationship or an N:1 mapping relationship.
- mapping relationship between the QoS identifier (or QoS flow identifier) and the second IP packet header information may be N:1; if one QoS flow is mapped to a first channel, then, there may be a 1:1 mapping relationship between the QoS identifier (or QoS flow identifier) and the second IP packet header information, which depends on the situation.
- the specific mapping relationship between them is not limited.
- Step S13 according to the QoS flow identifier of the data packet to be sent and the third mapping relationship, obtain the second channel information of the data packet to be sent;
- the first network node After the first network node receives the third mapping relationship corresponding to the data packet to be sent, it can query the third mapping relationship according to the determined QoS flow identifier of the data packet to be sent, and can determine the mapping relationship of the QoS flow with the QoS flow identifier
- the first channel information and the first packet header information of the first channel obtained can also determine the QoS identifier (such as XQI) mapped with the QoS flow identifier (QFI), and then, according to the QoS identifier and/or the second IP packet header information and
- the mapping relationship between the second channel information is used to obtain the second channel information corresponding to the determined QoS identifier and/or the second IP packet header information, that is, the second channel information of the data packet to be sent.
- mapping relationship between the QoS identifier and/or the second IP header information and the second channel information may be determined by the third network node or the second network node, and the implementation process may refer to the description of the corresponding part of the following embodiments.
- Step S14 Send the data packet to be sent to the second network node through the second channel corresponding to the second channel information of the data packet to be sent according to the QoS parameter of the data packet to be sent.
- the data packet to be sent is usually encapsulated according to the obtained relevant information, so that the second network node can From the IP header information of the packet, obtain information such as the required DSCP or DSCP+IPv6 flow identifier, and continue forwarding to the third network node.
- the first network node may add a GRE header to the header of the data packet to be sent, the GRE header may contain the QFI corresponding to the data packet to be sent, and then continue to encapsulate the Inner IP header , if the source address and target address are written in the Inner IP packet header, the source address can be the UE_IP_ADDRESS allocated by the third network node to the first network node after the first network node accesses the third network node, and the target address can be The first channel information, that is, the user-side IP address assigned to the first network node for the first channel, that is, UP_IP_ADDRESS, can continue to encapsulate the IPSec packet header and the IP packet header.
- the IP header of the final encapsulation contains the IP address of the first network node, such as the intranet IP address or local IP address obtained by the first network node, which can be used by the second network node based on the local IP address of the first network node
- the address identifies the identifier (referred to as the first identifier) used by the corresponding first network node on the Sparklink or non-3GPP air interface, such as the Sparklink identifier or MAC address, so as to realize communication with the first network node accordingly.
- the first network node completes the encapsulation of the IP layer, and the encapsulated IP data packet (that is, the data packet to be sent) can be Continue to write to Sparklink’s media access layer for encapsulation, and write the above-identified second channel information in the media access layer header, such as the logical channel identifier LCID, which is the second channel identifier, and encapsulate it into the Sparklink physical layer, and finally encapsulate
- the obtained data packet to be sent is sent to the second network node through the determined second channel (Sparklink air interface).
- the Sparklink air interface contains the DTADP protocol layer
- the first network node after the first network node is encapsulated into the IP layer, it can continue to encapsulate the DTADP protocol layer header so that the header includes the second channel such as TCID Information, after that, perform Sparklink access layer (make its header include the second channel identifier such as LCID) and physical layer encapsulation according to the method described above, and send the final encapsulated data packet to be sent through the second channel to the second network node.
- the second channel such as TCID Information
- encapsulation can be performed layer by layer according to the user plane protocol stack, and the final encapsulated data packets to be sent can be determined by The second channel is sent to the second network node, and the implementation process is not described in detail in this application.
- the PDU session identifier of the PDU session corresponding to the data packet to be sent, and the data packet to be sent can be obtained
- the QoS flow identifier and QoS parameters of the QoS flow corresponding to the packet can be determined by the first network node, or sent after being determined by the core network
- the QoS parameters can be determined by the first network node, or sent after being determined by the core network
- the third network node and/or the second network node after the establishment of the sent The above-mentioned third mapping relationship, in this way, based on the third mapping relationship and the QoS flow identifier corresponding to the data packet to be sent, the second channel information of the second channel used to transmit the data packet to be sent can be determined, so as to realize the first network
- the end-to-end QoS processing between the node and the second network node meets the QoS requirements of the data packets to be sent.
- the core network in the whole implementation process, there is no need for the core network to establish the above mapping relationship, and it is transmitted to the third network node through the N2 interface, so there is no need to change the core network function configuration, which reduces the core network configuration workload and improves data transmission efficiency. and reliability.
- FIG. 6 it is a schematic flowchart of another optional example of a data packet transmission method based on network quality of service implemented by the first network node side proposed in this application.
- the embodiment of this application may be a network-based method described in the above embodiments.
- An optional fine-grained implementation of the quality of service packet transmission method but not limited to this optional fine-grained implementation.
- the method may be performed by the first network node, and as shown in FIG. 6, the method may include:
- Step S21 obtaining the PDU session identifier, QoS flow identifier and QoS parameters of the data packet to be sent;
- step S21 For the implementation method of step S21, reference may be made to the description of the corresponding part of the above embodiment, and details are not described in this embodiment.
- Step S22 receiving the fourth mapping relationship sent by the third network node
- the fourth mapping relationship can represent the PDU session identifier, QoS flow identifier (i.e. one or more QFI), QoS identifier, first channel information and the mapping relationship between the second IP header information, or indicate the PDU session identifier, QoS flow identifier, first channel information and the second IP header information mapping relationship.
- the fourth mapping relationship may be determined by the third network node according to information sent by the core network and then sent to the first network node.
- the above-mentioned second mapping relationship may represent the mapping relationship between the second channel information and the second IP packet header information and/or QoS identifier, which may be determined by the second network node according to the information sent by the third network node and sent to the first network node.
- the implementation method of determining the fourth mapping relationship by the third network node and the implementation method of determining the second mapping relationship by the second network node reference may be made to the implementation of the network quality-of-service-based data packet transmission method described below from the corresponding node side. For example, the embodiment of the present application will not be described in detail here.
- Step S23 based on the fourth mapping relationship, obtain the first channel information, the second IP packet header information and the QoS identifier corresponding to the QoS flow identifier of the data packet to be sent;
- the core network can determine the QoS flows included in the established PDU session, and the QoS flow identifiers and QoS parameters corresponding to each QoS flow, and the third network node can , determine which first channel each QoS flow is mapped to, determine the first channel information of each first channel, and also determine the QoS identifier corresponding to each QoS flow identifier, and the implementation process will not be described in detail.
- the first network node After the first network node obtains the QoS flow identifier of a certain QoS flow of the PDU session mapped by the data packet to be sent, it can query the above-mentioned fourth mapping relationship sent by the third network node, and gradually analyze and determine the corresponding QoS flow of the data packet to be sent.
- the first channel information, the second IP packet header information and the QoS identifier After the first network node obtains the QoS flow identifier of a certain QoS flow of the PDU session mapped by the data packet to be sent, it can query the above-mentioned fourth mapping relationship sent by the third network node, and gradually analyze and determine the corresponding QoS flow of the data packet to be sent.
- the first channel information, the second IP packet header information and the QoS identifier The first channel information, the second IP packet header information and the QoS identifier.
- Step S24 receiving the second mapping relationship sent by the second network node
- Step S25 based on the second mapping relationship, determine the obtained second IP packet header information or the second channel information mapped by the QoS identifier as the second channel information of the data packet to be sent;
- the content of the relationship is not limited and may vary depending on the circumstances.
- Step S26 according to the QoS parameter of the data packet to be sent, send the data packet to be sent to the second network node through the second channel corresponding to the second channel information of the data packet to be sent.
- the first network node when the first network node needs to send a data packet to be sent to the second network node, the first network node can use the PDU session identifier, QoS flow identifier, and the second network node provided by the third network node.
- the fourth mapping relationship between the two IP header information and/or the QoS identifier (whether it includes the QoS identifier, whether it is consistent with whether the second mapping relationship includes the QoS identifier), to obtain the second IP header information or the QoS identifier corresponding to the data packet to be sent .
- the second channel information corresponding to the data packet to be sent is determined, such as the second channel information such as TCID/LCID, etc.
- the channel identifier determines which second channel the first network node passes through according to what QoS parameters, and sends the encapsulated data packet to be sent to the second network node to realize QoS control between the first network node and the second network node .
- the first network node A is connected to the third network node through the second network node B, and can send the first network node to the third network node
- the identification of A communicating in Sparklink after the first network node A accesses the second network node C, it can also send its identification in Sparklink communication to the third network node through the second network node C.
- the third network node It can be known that the first network node A accessed through the second network node C is
- the traffic mapping information sent by the third network node to the second network node C may include the mapping relationship between the second IP packet header information and the QoS information as described above, and may also include the first network node A’s information in the Sparklink
- the air interface identifier that is, the identifier used when the first network node A and the second network node C communicate through Sparklink
- the second network node C can obtain the third mapping relationship and send it to The implementation process of the first network node A is not described in detail.
- the second network node B and the second network node C are connected to different third network nodes
- the second network node B is connected to the third network node 1
- the second network node B is connected to the third network node 2
- the first network node Node A can send to the third network node 2 the identity of the second network node B in Sparklink and the identity of the first network node A in Sparklink, so that the third network node 2 can use the previously obtained second network node and the first network node relationship, or send a message to other third network nodes around, asking whether the second network node B is connected to the third network node around, and obtain the context information of the corresponding first network node A, such as the third network node 1 to the first network node
- the corresponding mapping relationship sent by network node A/second network node B, the content of the mapping relationship can be combined with the description of the corresponding part of the above embodiment, so as to send the required mapping relationship to the second network node C accordingly, so that the second network node C
- the third mapping relationship described in the above embodiments may also be determined by the third network node and then sent to the first network node, and the determination of the third mapping relationship on the third network node
- the implementation process reference may be made to the description of the corresponding part of the embodiment below, and details are not described in this embodiment here.
- the implementation process of the first network node determining the second channel information of the data packet to be sent according to the third mapping relationship sent by the third network node, and sending the data packet to be sent to the second network node through the second channel please refer to The description of the corresponding parts of the above embodiments will not be repeated in this embodiment of the present application.
- the PDU session establishment acceptance message sent by the core network to the first network node may not include the QoS parameter corresponding to the QoS flow identifier.
- the first network node may obtain QoS parameter indication information for indicating whether the core network feeds back the QoS parameter to the first network node,
- the above-mentioned QoS parameter indication information may be added to the registration request message and then sent, so as to From this, the core network can know whether to send the QoS parameter to the first network node registered this time.
- the QoS parameter indication information can take a value of 1 or true, indicating that the NAS message fed back by the core network (for example, a registration request acceptance, or a PDU session establishment acceptance message, or a PDU session modification acceptance message) needs to include QFI corresponding QoS parameters.
- the QoS parameter indication information can take a value of 0 or false, indicating that the NAS message fed back by the core network (such as registration request acceptance, or PDU session establishment acceptance message, or PDU session modification acceptance message) does not need to include the QoS parameter corresponding to QFI.
- the latter QoS parameter indication information can only take a value of 0 or false, or as long as the registration request message contains the QoS parameter indication information, it means that the NAS message fed back by the core network (such as registration request acceptance, or PDU session establishment acceptance message , or the PDU session modification acceptance message) does not need to include the QoS parameters corresponding to the QFI.
- the specific form of the above-mentioned QoS parameter indication information can also be Sparklink indication information or the first network node indication information in the Sparklink system, so as to determine whether the first network node is the first network node in the Sparklink system, etc., so that It is determined that the NAS message fed back by the core network (for example, the registration request acceptance, or the PDU session establishment acceptance message, or the PDU session modification acceptance message) does not need to include the QoS parameter corresponding to the QFI.
- the core network for example, the registration request acceptance, or the PDU session establishment acceptance message, or the PDU session modification acceptance message
- the above-mentioned different QoS parameter indication information may be sent by the first network node to the AMF of the core network, or forwarded to the AMF by the third network node, or stored as part of the subscription information of the first network node in the
- the UDM of the core network enables the AMF to obtain the corresponding QoS parameter indication information from the requested subscription information.
- This application does not limit the implementation process of the AMF of the core network to obtain each indication information, and it depends on the situation.
- the first network node sends a registration request message (not including the QoS parameter indication) to the third network node through the second network node, and the third network node forwards the registration request message to the AMF of the core network while carrying the first An identifier of a network node on the N2 interface and required QoS parameter indication information
- the QoS parameter indication information may be determined by the third network node or the second network node, for example, the user location sent by the second network node to the third network node
- the process of obtaining indication information for non-3GPP nodes is similar, and will not be described in detail in this application.
- the SMF can determine the feedback PDU session according to the QoS parameter indication information in the indication information Whether the QoS parameter corresponding to the QoS flow identifier is included in the establishment acceptance message.
- the core network may instruct the third network node that the fourth mapping relationship established includes the QoS parameter corresponding to the QoS flow identifier, that is, the above fourth mapping relationship It can represent the mapping relationship between the PDU session identifier, QoS parameter, QoS flow identifier, QoS identifier (may not be included), the first channel information, and the second IP packet header information, and the fourth mapping about how the first network node uses the content Relationship, the implementation process of determining the second communication information of the data packet to be sent is similar to the implementation process described in the above embodiment, and will not be described in detail in this application.
- FIG. 7 it is a schematic flowchart of an optional example of a data packet transmission method based on network quality of service implemented by the second network node side proposed in this application, that is, the data packet based on network quality of service described in this embodiment
- the transmission method may be performed by the second network node, and may describe the implementation process of the second network node sending data packets to the first network node.
- This method may be applicable to Sparklink access or trusted non-3GPP access network scenarios, such as As shown in Figure 7, the method may include:
- Step S31 receiving traffic mapping information sent by the third network node
- the traffic mapping information (IP to Sparklink Traffic Mapping Info or IP to non-3GPP Traffic Mapping Info) sent by the third network node to the second network node may include but not limited to different first IP headers A first mapping relationship between information and different QoS information.
- the first IP header information may include the local IP address of the first network node (such as the local IP address assigned by the first network node in Sparklink) and the second IP header information.
- the second IP header information For the content and functions of , refer to the description of the corresponding part of the above embodiment.
- the QoS information may include QoS parameters, or include QoS parameters and QoS identifiers (such as XOI or 5QI), depending on the situation.
- the respective contents of the QoS parameter and the QoS identifier reference may be made to the description in the corresponding part of the above embodiment, and details are not described in this embodiment.
- Step S32 receiving the data packet to be sent sent by the third network node
- Step S33 according to the first mapping relationship included in the traffic mapping information and the first IP header information of the data packet to be sent, obtain the second channel information and QoS parameters of the data packet to be sent.
- the second network node receives the data packet to be sent sent by the core network forwarded by the third network node, and can obtain the IP header information from the header of the data packet to be sent, record is the first IP header information, combined with the relevant description of the content of the first IP header information above, after the second network node obtains the local IP address of the first network node, it can determine the first identifier of its corresponding first network node, For example, the Sparklink air interface identifier, that is, the identifier of the first network node at the Sparklink media access layer MAC layer, etc.; for non-3GPP access, it may be a non-3GPP air interface identifier, such as a MAC address. So that the second network node can distinguish different first network nodes that are accessed based on this.
- the second network node may acquire the second channel information of the corresponding second channel between the first network node and the second network node with the determined first identifier, and determine different second IP packet header information and/or QoS identifiers
- the mapping relationship with the second channel information that is, the second mapping relationship described above, so as to combine the first mapping relationship between the first IP header information sent by the third network node and the QoS information to obtain the second IP header information and/or second channel information mapped to the QoS identifier.
- the foregoing second mapping relationship may be determined by the second network node, and sent by the second network node to the first network node.
- the above-mentioned second mapping relationship may also be determined by the third network node, and then included in the traffic mapping information and sent to the second network node. This application does not limit this, and it depends on the situation.
- the second channel information of the data packet to be sent can be determined by the second network node based on the second mapping relationship and the first mapping relationship, that is, the second IP address in the first IP header information of the data packet to be sent is obtained.
- the header information, or the QoS identifier mapped to the first IP header information is used to determine the second IP header information or the second channel information mapped to the QoS identifier.
- the second network node may directly determine the QoS parameters mapped to the first IP header information of the data packets to be sent as the QoS parameters of the data packets to be sent according to the first mapping relationship.
- this application does not address how the second network node determines the first identifier of the first network node based on the local IP address of the first network node in the first IP header information of the data packet to be sent. limit.
- the second network node directly receives the first identifier of the first network node sent by the third network node and corresponding to the local IP address of the first network node.
- the traffic mapping information sent by the third network node to the second network node may also include the first identifier of the first network node accessing the second network node, such as the communication between the first network node and the second network node through Sparklink The air interface identification used at the time, or the air interface identification other than 3GPP.
- the second network node can determine the correspondence between the local IP addresses of different first network nodes and the first identifiers of different first network nodes according to the historical data packets from different first network nodes, so that , the second network node can obtain the first identifier of the first network node according to the corresponding relationship and the local IP address of the first network node in the first IP header information of the data packet to be sent, thereby identifying that the data packet to be sent will be received of the first network node.
- Step S34 Send the data packet to be sent to the corresponding first network node through the second channel corresponding to the second channel information of the data packet to be sent according to the QoS parameter of the data packet to be sent.
- the third network node determines the first mapping relationship as described above based on the information sent by the core network.
- the second network node needs to report to the first network
- a node sends a data packet to be sent
- it can be based on the local IP address of the first network node contained in the first IP header information of the data packet to be sent, the second IP header information or the QoS identifier, and the received first mapping relationship , determine the QoS parameters of the data packets to be sent, and which second channel to transmit the data packets to be sent, so as to ensure that the second network node sends the data packets to be sent to the first network node, satisfying various QoS of the data packets to be sent
- the requirement is to ensure that the end-to-end QoS requirement between the first network node and the third network node is consistent with the end-to-end QoS requirement between the first network node and the second network node.
- FIG. 8 it is a schematic flow diagram of another optional example of a data packet transmission method based on network quality of service implemented by the second network node side proposed in this application. As shown in FIG. 8, the method may include:
- Step S41 receiving traffic mapping information sent by the third network node
- the traffic mapping information received by the second network node may include the above-mentioned first mapping relationship, and the relationship between the second channel information and the second IP packet header information and/or QoS identifier
- the acquisition process of the second mapping relationship can be combined with the description of the corresponding part of the above embodiment.
- the third network node can determine the second network node accessed by the first network node and the first network The IP address of the node, such as the IP address assigned by the first network node to access the third network node, or the IP address assigned by the third network node to the corresponding first network node when the GTP-U tunnel is established.
- the IP address can be written into the data packet header and sent to the second network node as part of the first IP header information, and then the second network node can follow this embodiment
- the proposed data packet transmission method based on network quality of service implemented by the second network node side forwards the data packet sent by the third network node to the first network node, and ensures the consistency of end-to-end QoS requirements.
- Step S42 receiving the data packet to be sent sent by the third network node
- Step S43 according to the first mapping relationship included in the traffic mapping information, obtain the QoS parameter mapped to the first IP header information of the data packet to be sent;
- Step S44 according to the second mapping relationship contained in the traffic mapping information, the second channel information corresponding to the second IP header information in the first IP header information of the data packet to be sent is determined as the second channel information of the data packet to be sent ;
- the second network node may also obtain the QoS parameter and QoS identifier mapped to the first IP header information of the data packet to be sent according to the first mapping relationship, and then, according to the second mapping relationship, The second channel information corresponding to the QoS identifier is determined as the second channel information of the data packet to be sent, and the implementation process is not described in detail in this application.
- the second mapping relationship may be established by the third network node, or may be established by the second network node itself, which is not limited in this application.
- the third network node may also form the above-mentioned first mapping relationship and the second mapping relationship into a fifth mapping relationship, that is, the first IP packet header information, QoS information and second channel information directly send it to the second network node, so that the second network node obtains the second channel information and the QoS parameter of the data packet to be sent according to the fifth mapping relationship.
- Step S45 Send the data packet to be sent to the corresponding first network node through the second channel corresponding to the second channel information of the data packet to be sent according to the QoS parameter of the data packet to be sent.
- the second network node can receive the first IP packet header information sent by the third network node (the first network node's local IP address and the second IP packet header information), QoS information (QoS parameters, or the combination information of QoS parameters and QoS identifiers) and the mapping relationship between the second channel information, based on the mapping relationship, the second network node can determine the Send the QoS parameters and second channel information mapped by the first IP header information in the header of the data packet, that is, know the QoS requirements for transmitting the data packet to be sent, and which second channel is used to transmit the data packet to be sent, and then , the data packet to be sent can be sent to the first network node through the determined second channel according to the QoS parameter, so as to ensure the QoS processing between the first network node and the second network node, and the data packet to be sent
- the QoS requirements are consistent, and
- FIG. 9 it is a schematic diagram of a signaling flow of another optional example of a data packet transmission method based on network quality of service proposed in this application. As shown in FIG. 9, the method may include:
- Step S51 the third network node receives the PDU session resource request message sent by the core network
- the first network node described in the above embodiments registers with the core network. After the registration is completed, the first network node applies to the core network for the description content of establishing a PDU session. After the core network receives the PDU session establishment request, it can generate a corresponding PDU session request message, which may include but not limited to the PDU session identifier of the PDU session applied for establishment, the QoS flow identifier and QoS parameters corresponding to each QoS flow contained in the PDU session, etc., the application of the PDU session request message The acquisition process is not described in detail.
- Step S52 the third network node obtains the fourth mapping relationship according to the QoS parameter in the PDU session resource request message
- the fourth mapping relationship may represent the mapping relationship between the PDU session identifier, the QoS flow identifier, the QoS identifier, the first channel information, and the second IP packet header information; or represent the PDU session identifier,
- the mapping relationship between the QoS flow identifier, the first channel information, and the second IP header information, and the meaning of each information contained in the mapping relationship can be combined with the description of the corresponding part of the above embodiment, and will not be described in this embodiment.
- the third network node may obtain the first correspondence between the corresponding QoS flow identifier and the first channel information according to the received QoS parameters of each QoS flow relationship, such as mapping QoS flows with similar QoS parameters to a first channel, determining the mapping relationship between the QoS flow identifiers corresponding to these similar QoS parameters and the first channel information of the first channel, which is recorded as the first corresponding relationship, It can be a 1:1 or N:1 mapping relationship.
- the configuration method of the first channel information it can be combined with the description of the corresponding part of the above embodiment. This embodiment will not describe it in detail. It can be understood that the first channel information of different first channels is different. Therefore, the first channel The information may be used to identify a first channel between the third network node and the first network node connected to the third network node;
- the third network node can configure corresponding priority attribute values such as DSCP/(DSCP and IPv6 flow identifier) for each first channel to form the second IP packet header information of the first channel, that is, the second
- the IP packet header information includes a priority attribute value configured for the first channel between the first network node and the third network node. It can be seen that there may be a second correspondence relationship of one-to-one correspondence between the second IP packet header information and the above-mentioned determined first channel information of the first channel.
- the corresponding QoS identifier can be obtained, so in combination with the correspondence described above, the third correspondence between the QoS identifier and the QoS flow identifier can be determined, such as 1:1 mapping relationship.
- the third network node may generate the fourth mapping relationship including the above content by combining the obtained first correspondence relationship, second correspondence relationship and third correspondence relationship.
- Step S53 the third network node obtains the third mapping relationship according to the fourth mapping relationship and the N2 interface identifier of the first network node in the PDU session request message;
- the third network node After the third network node receives the PDU session resource request message sent by the AMF through the N2 interface, it can also determine the second network node accessed by the first network node according to the identifier of the first network node on the N2 interface included in it, and The local IP address of the first network node, so as to determine the first identification of the first network node (ie, the air interface identification of the access network) according to the IP address, and obtain the first network node corresponding to the first identification.
- the second mapping relationship between the second channel information and the second IP header information and/or QoS identifier may be established, which is denoted as the second mapping relationship.
- the third network node may form a third mapping relationship according to the foregoing fourth mapping relationship and the second mapping relationship.
- the third network node may directly send the fourth mapping relationship and the second mapping relationship to the corresponding first network node, so that the first network node implements the second network access to it accordingly.
- the node sends the data packet to be sent, and the implementation process may refer to the content of the corresponding embodiment described above from the side of the first network node.
- Step S54 the third network node sends the third mapping relationship to the corresponding first network node
- Step S55 the first network node obtains the PDU session identifier, QoS flow identifier and QoS parameters of the data packet to be sent;
- Step S56 the first network node obtains the second channel information of the data packet to be sent according to the QoS flow identifier of the data packet to be sent and the third mapping relationship;
- Step S57 the first network node sends the data packet to be sent to the second network node through the second channel corresponding to the second channel information of the data packet to be sent according to the QoS parameter of the data packet to be sent;
- step S54 to step S57 may be combined with the description of the corresponding part of the above embodiment, and will not be described in detail in this embodiment.
- Step S58 the second network node forwards the data packet to be sent to the third network node.
- the second network node can directly forward the received data packet to be sent to the third network node through the wired communication channel, and then report to the core network, and then sent to the corresponding data network by the core network.
- the second network node may also determine the to-be-sent packet header information according to the received packet header information, such as the first channel information, QFI, XQI, second IP packet header information, etc., and the obtained corresponding mapping relationship. send the QoS parameter of the data packet, so that the data packet to be sent is forwarded to the third network node according to the QoS parameter. Make restrictions, depending on the situation.
- the third network node can obtain the third mapping relationship of the above content according to the content of the PDU session request message sent by the core network, and send it to the corresponding first
- the network node is the first network node that applies for establishing the corresponding PDU session.
- the first network node when it needs to report the data packet to be sent generated by the application layer, it can directly determine the data to be sent based on the third mapping relationship
- the first channel information, the second IP header information, the QoS parameter and the second channel information of the packet so as to use the first channel information, the second IP header information, and the second channel information in combination with the user plane protocol stack to realize the processing of the data packets to be sent Layer-by-layer encapsulation, and then according to the obtained QoS parameters, the encapsulated data packets to be sent are sent to the second network node through the second channel, and forwarded by the second network node to the third network node. Send to the corresponding data network to meet the corresponding application requirements.
- FIG. 10 it is a schematic flow diagram of another optional example of a data packet transmission method based on network quality of service proposed in this application. As shown in FIG. 10 , the method may include:
- Step S61 the third network node receives the PDU session resource request message sent by the core network
- Step S62 the third network node obtains the fourth mapping relationship according to the QoS parameter in the PDU session request message
- Step S63 the third network node sends the fourth mapping relationship to the corresponding first network node
- step S61 to step S63 For the implementation process of step S61 to step S63, reference may be made to the description of the corresponding part of the above embodiment.
- Step S64 the third network node obtains the first mapping relationship according to the PDU session resource request message
- the first mapping relationship may represent the mapping relationship between different first IP header information and different QoS information, for example, the first IP header information includes the local IP address of the corresponding first network node connected to the third network node address and second IP packet header information.
- the local IP address of the corresponding first network node and the second network node accessed by the first network node can be obtained, and then, can be combined with Other information in the PDU session resource request message is used to determine the QoS parameter and QoS flow identifier mapped to the local IP address of the first network node, obtain the QoS identifier corresponding to the QoS flow identifier, and obtain the first mapping relationship, but not limited to Based on this mapping relationship acquisition method.
- Step S65 the third network node sends the first mapping relationship to the second network node accessed by the first network node;
- the third network node may send the first mapping relationship as traffic mapping information to the second network node accessed by the first network node.
- Step S66 the second network node obtains the second mapping relationship according to the first mapping relationship
- the second mapping relationship may represent the mapping relationship between the second channel information and the second IP packet header information and/or QoS identifier, and the specific acquisition process may be combined with the description of the corresponding part of the above embodiment, which will not be described in detail in this embodiment .
- Step S67 the second network node sends the second mapping relationship to the first network node.
- FIG. 11 it is a schematic flow diagram of another optional example of a data packet transmission method based on network quality of service proposed in this application. As shown in FIG. 10 , the method may include:
- Step S71 the third network node receives the PDU session resource request message sent by the core network
- Step S72 the third network node obtains the first mapping relationship according to the PDU session resource request message
- step S71 and step S72 reference may be made to the description of the corresponding part of the above embodiment.
- Step S73 the third network node obtains a fifth mapping relationship according to the first mapping relationship and the first identifier of the first network node corresponding to the local IP address of the first network node;
- the fifth mapping relationship may represent the mapping relationship between the first IP packet header information, QoS information (which includes QoS parameters, or QoS parameters and QoS identifiers, such as XQI, 5QI, etc.) and the second channel information
- the third network node may include the fifth mapping relationship in the traffic mapping information and send it to the second network node.
- the traffic mapping information may also include a first identifier of the first network node accessing the base station, such as an air interface identifier of the Sparklink.
- Step S74 the third network node sends the fifth mapping relationship to the second network node accessed by the corresponding first network node;
- Step S75 the second network node receives the data packet to be sent sent by the third network node
- Step S76 the second network node obtains the second channel information and QoS parameters of the data packet to be sent according to the fifth mapping relationship and the first IP header information of the data packet to be sent;
- Step S77 the second network node sends the data packet to be sent to the corresponding first network node through the second channel corresponding to the second channel information of the data packet to be sent according to the QoS parameter of the data packet to be sent.
- the third network node may determine different first IP packet header information and different QoS information, as well as the mapping relationship between them, for the related information of each first network node accessed, and then, may According to the PDU session resource request message sent by the core network for the PDU session established by each first network node, the above-mentioned fifth mapping relationship is obtained and sent to the second network node.
- the second network node sends data to the first network node
- the QoS parameter and the second channel information of the data packet can be determined directly according to the fifth mapping relationship, that is, the QoS requirements of the data packet to be sent for the first network node are known, thereby ensuring that the data packet In the process of sending the packet to the first network node, the consistency of end-to-end QoS processing.
- the third network node knows that the first network node it accesses through the second network node C After A is the first network node A originally accessed through the second network node, the third network node can send the traffic mapping information including the fifth mapping relationship to the second network node C, so that the second network node C According to this, the distribution of data packets is realized, and the end-to-end QoS requirements are met.
- the second network node B and the second network node C are connected to different third network nodes, refer to the description of the corresponding part above, and this embodiment will not describe in detail.
- FIG. 12 it is a schematic structural diagram of an optional example of a data packet transmission device based on network quality of service proposed in this application.
- the device can be deployed on the first network node. As shown in FIG. 12, the device can include:
- PDU session information acquisition module 110 used to obtain the protocol data unit PDU session identification, quality of service QoS flow identification and QoS parameters of the data packet to be sent;
- the third mapping relationship acquiring module 120 configured to acquire a third mapping relationship including the PDU session identifier
- the third mapping relationship is established and provided by the second network node and/or the third network node accessed by the first network node, and includes the PDU session identifier, QoS flow identifier, first channel information, second IP A mapping relationship between header information and second channel information;
- the first channel information is used to identify the first channel between the first network node and the third network node;
- the second IP header information includes information for the first The priority attribute value of the first channel configuration between a network node and the third network node;
- the second channel information is used to identify the second channel between the first network node and the second network node aisle;
- the second channel information determination module 130 is configured to obtain the second channel information of the data packet to be sent according to the QoS flow identifier of the data packet to be sent and the third mapping relationship;
- the QoS control module 140 is configured to send the data packet to be sent to the second network node through the second channel corresponding to the second channel information of the data packet to be sent according to the QoS parameter of the data packet to be sent.
- the above-mentioned third mapping relationship includes a fourth mapping relationship and a second mapping relationship
- the fourth mapping relationship represents the relationship between the PDU session identifier, the QoS flow identifier, the first channel information, and the second IP packet header information.
- the second mapping relationship represents the second channel information and the The second IP packet header information or the mapping relationship between the QoS identifiers.
- the above-mentioned third mapping relationship acquisition module 120 may include:
- a fourth mapping relationship receiving unit configured to receive the fourth mapping relationship sent by the third network node and including the target PDU session identifier
- a second mapping relationship receiving unit configured to receive the second mapping relationship sent by the second network node.
- the above-mentioned second channel information determination module 130 may include:
- the first information obtaining unit is configured to obtain, based on the fourth mapping relationship, the first channel information and the QoS identifier corresponding to the QoS flow identifier of the data packet to be sent, and/or the second IP corresponding to the first channel information Baotou information;
- the second channel information determining unit is configured to determine, based on the second mapping relationship, the obtained second IP packet header information or the second channel information to which the QoS identifier is mapped, as the second channel information of the data packet to be sent. Two channel information.
- the above-mentioned third mapping relationship acquisition module 120 may also include:
- the third mapping relationship receiving unit is configured to receive the third mapping relationship including the PDU session identifier of the data packet to be sent sent by the third network node.
- FIG. 13 it is a schematic structural diagram of another optional example of a data packet transmission device based on network quality of service proposed in this application.
- the device can be deployed on a second network node.
- the device can include:
- a traffic mapping information receiving module 210 configured to receive the traffic mapping information sent by the third network node
- the traffic mapping information includes a first mapping relationship between different first IP header information and different QoS information;
- the first IP header information includes a local IP address of a first network node and second IP header information;
- the second IP header information includes a priority attribute value configured for the first channel between the first network node and the third network node;
- the QoS information includes QoS parameters, or includes QoS parameters and QoS identifiers;
- a data packet to be sent receiving module 220 configured to receive a data packet to be sent sent by the third network node
- a transmission control information obtaining module 230 configured to obtain second channel information and QoS parameters of the data packet to be sent according to the first mapping relationship and the first IP header information of the data packet to be sent;
- the second channel information is used to identify the second channel between the first network node and the second network node;
- the QoS control module 240 is configured to send the data packet to be sent to the corresponding second channel through the second channel corresponding to the second channel information of the data packet to be sent according to the QoS parameter of the data packet to be sent Two network nodes.
- the transmission control information obtaining module 230 may include:
- a second mapping relation acquiring unit configured to determine second channel information of a second channel between the first network node with the first identifier and the second network node, and acquire the second channel information and the second IP packet header A second mapping relationship between information or QoS identifiers;
- the first obtaining unit is configured to obtain the QoS parameter of the data packet to be sent, or the QoS parameter and the QoS identifier according to the first mapping relationship and the first IP header information of the data packet to be sent.
- the second obtaining unit is configured to obtain the information of the data packet to be sent according to the second mapping relationship and the second IP header information in the first IP header information of the data packet to be sent, or the QoS identifier. Second channel information.
- the above-mentioned first determining unit may include:
- the first receiving unit is configured to receive the first identifier of the first network node corresponding to the local IP address of the first network node sent by the third network node; or,
- a correspondence determining unit configured to determine the correspondence between local IP addresses of different first network nodes and first identifiers of different first network nodes according to historical data packets from different first network nodes;
- the third obtaining unit is configured to obtain the first identifier of the first network node according to the corresponding relationship and the local IP address of the first network node in the first IP header information of the data packet to be sent to obtain the first network Second channel information corresponding to the local IP address of the node.
- the above-mentioned second mapping relationship obtaining unit may include:
- a first establishing unit configured to establish a second mapping relationship between the second IP packet header information or the QoS identifier and the second channel information; or,
- the fourth obtaining unit is configured to obtain a second mapping relationship between the second channel information included in the traffic mapping information and the second IP packet header information or QoS identifier.
- the device may also include:
- the second mapping relationship sending module is configured to send the second mapping relationship to the first network node, so that the first network node determines to send the information of the first network node to the second network node according to the second mapping relationship Second channel to send packets.
- FIG. 14 it is a schematic structural diagram of another optional example of a data packet transmission device based on network quality of service proposed in this application.
- the device may be deployed on a third network node.
- the device may include:
- the PDU session resource request message receiving module 310 is used to receive the PDU session request message sent by the core network;
- the PDU session resource request message includes a PDU session identifier, a QoS flow identifier and a QoS parameter;
- a fourth mapping relationship obtaining module 320 configured to obtain a fourth mapping relationship according to the QoS parameter
- the fourth mapping relationship may represent the mapping relationship between the PDU session identifier, QoS flow identifier, first channel information, and second IP header information; or represent the PDU session identifier, QoS flow identifier, QoS The mapping relationship between the identification, the first channel information, and the second IP header information; so the first channel information is used to identify the first channel between the corresponding first network node and the third network node; the second IP header information including a priority attribute value configured for the first channel between the first network node and the third network node;
- the fourth mapping relationship sending module 330 configured to send the fourth mapping relationship to a corresponding first network node.
- the above PDU session request message also includes the N2 interface identifier of the first network node, and the device may also include:
- a second mapping relationship obtaining module configured to obtain a second mapping relationship according to the second mapping relationship and the N2 interface identifier of the first network node; the second mapping relationship represents the second channel information and the second IP packet header A mapping relationship between information and/or QoS identifiers; the second channel information is used to identify a second channel between the first network node and the second network node;
- a second mapping relationship sending module configured to send the second mapping relationship to a corresponding first network node
- the above PDU session resource request message also includes the N2 interface identifier of the first network node, and the device may also include:
- the third mapping relationship obtaining module is configured to obtain a third mapping relationship according to the second mapping relationship and the N2 interface identifier of the first network node; the third mapping relationship represents a PDU session identifier, a QoS flow identifier, a first The mapping relationship between channel information, second IP header information, and second channel information; or the mapping between PDU session identifiers, QoS flow identifiers, QoS identifiers, first channel information, second IP header information, and second channel information relation.
- a third mapping relationship sending module configured to send the third mapping relationship to the first network node.
- the device may further include:
- the first mapping relationship obtaining module is configured to obtain a first mapping relationship according to the PDU session request message; wherein the first mapping relationship represents a mapping relationship between different first IP packet header information and different QoS information, and the first mapping relationship
- An IP header information includes the local IP address of the first network node and the second IP header information;
- a first mapping relationship sending module configured to send the fourth mapping relationship to a second network node
- the second mapping relationship obtaining module is used to obtain the second mapping relationship between the second channel information and the second IP packet header information or QoS identifier;
- a mapping relationship sending module configured to send the second mapping relationship and the first mapping relationship to the second network node; or, obtain a fifth mapping relationship from the first mapping relationship and the second mapping relationship, and send sending the fifth mapping relationship to a second network node;
- the fifth mapping relationship represents the mapping relationship among the first IP packet header information, QoS information and second channel information; the QoS information includes QoS parameters, or QoS parameters and QoS identifiers.
- the various modules, units, etc. in the above-mentioned device embodiments can all be stored in the memory as program modules, and the processor executes the above-mentioned program modules stored in the memory to realize corresponding functions.
- the functions realized by each program module and its combination, as well as the technical effects achieved reference may be made to the description of the corresponding parts of the above method embodiments, and details will not be repeated in this embodiment.
- the present application also provides a computer-readable storage medium, on which a computer program can be stored, and the computer program can be called and loaded by a processor included in each node, so as to realize the data based on network quality of service described in the above-mentioned corresponding node-side embodiments.
- a computer program can be stored, and the computer program can be called and loaded by a processor included in each node, so as to realize the data based on network quality of service described in the above-mentioned corresponding node-side embodiments.
- FIG. 15 it is a schematic diagram of the hardware structure of an optional example of computer equipment suitable for the data packet transmission method based on network quality of service proposed in this application.
- the computer equipment can be configured as the above-mentioned first network node or second network node Or the third network node, it can be understood that the computer device is configured as a different network node in the communication system, and its product type can be different, which is not limited in the present application and can be determined according to the scene requirements.
- the computer device may include: a communication module 1 and a processing circuit 2, wherein:
- the communication module 1 may be configured to implement data communication between the network node and other nodes in the communication system, and the implementation process will not be described in detail in this embodiment.
- the communication module 1 may include a communication module capable of using a wireless communication network to realize data interaction, such as a WIFI module, a 5G/6G (fifth generation mobile communication network/sixth generation mobile communication network) module, a GPRS module, etc. , to communicate with other nodes.
- the communication module 1 can also include a communication interface that realizes data interaction between the internal components of the computer equipment, such as a USB interface, a serial/parallel port, etc.
- the application does not limit the specific content contained in the communication module 1, and it can be based on the computer. The type of device is determined.
- the communication module 1 may be configured to realize data communication between the second network node and the first network node and the third network node respectively.
- the processing circuit 2 may be configured to control the communication module 1: receive traffic mapping information sent by the third network node, and receive a data packet to be sent sent by the third network node; wherein, the traffic mapping information includes different A first mapping relationship between IP header information and different quality of service QoS information; the first IP header information includes the local IP address of the first network node and the second IP header information; the second IP header information includes information for The priority attribute value of the first channel configuration between the first network node and the third network node; the QoS information includes QoS parameters, or QoS parameters and QoS identifiers; the processing circuit 2 is further configured to according to the first channel configuration A mapping relationship and the first IP header information of the data packet to be sent, obtaining the second channel information and QoS parameters of the data packet to be sent; the second channel information is used to identify the first network no
- the communication module 1 may be configured to implement data communication between the first network node and the second network node; the processing circuit 2 may be configured to obtain a data packet to be sent The protocol data unit PDU session identifier, QoS flow identifier and QoS parameters; obtain the third mapping relationship including the PDU session identifier; wherein, the third mapping relationship is accessed by the first network node and/or the second network node Or the third network node establishes and provides, and includes the mapping relationship between the PDU session identifier, QoS flow identifier, first channel information, second IP packet header information, and second channel information; the first channel information is used to identify The first channel between the first network node and the third network node; the second IP packet header information includes a priority attribute value configured for the first channel between the first network node and the third network node ; The second channel information is used to identify the second channel between the first network node and the second network node; According to the QoS flow identifier of
- the communication module 1 may be configured to realize data communication between the third network node and the second network node and the core network; the processing circuit 2 may be configured as Control the communication module to receive the PDU session resource request message sent by the core network; the PDU session resource request message includes a PDU session identifier, a QoS flow identifier, and a QoS parameter; the processing circuit 2 can also be configured to obtain the PDU session resource request message based on the QoS parameter A fourth mapping relationship; wherein, the fourth mapping relationship represents the mapping relationship between the PDU session identifier, the QoS flow identifier, the first channel information, and the second IP packet header information, or represents the PDU session identifier, the QoS flow identifier, The mapping relationship between the QoS identifier, the first channel information, and the second IP header information; the first channel information is used to identify the first channel between the corresponding first network node and the third network node; the second IP The packet header information includes a
- the computer device further includes a storage device 3, which is configured to be accessible by the processing circuit and stores instructions, and the instructions are configured to be executed by the processor to realize the computer device on the corresponding side described above.
- a storage device 3 which is configured to be accessible by the processing circuit and stores instructions, and the instructions are configured to be executed by the processor to realize the computer device on the corresponding side described above.
- the storage device 3 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device or other volatile solid-state storage devices.
- the processor 3 can be a central processing unit (Central Processing Unit, CPU), an application-specific integrated circuit (application-specific integrated circuit, ASIC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a ready-made programmable gate array (FPGA) or other programmable logic devices, etc.
- CPU Central Processing Unit
- ASIC application-specific integrated circuit
- DSP digital signal processor
- ASIC application-specific integrated circuit
- FPGA ready-made programmable gate array
- the structure of the computer device shown in FIG. 15 does not constitute a limitation on the computer device in the embodiment of the present application.
- the computer device as different nodes may include more or more nodes than those shown in FIG. 15 A few parts, or some combination of parts, the present application does not list them all here.
- each embodiment in this specification is described in a progressive or parallel manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other .
- the description is relatively simple, and for relevant details, please refer to the description of the method part.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
La présente demande concerne un procédé de transmission de paquet de données sur la base de la qualité de service (QoS) d'un réseau, et un dispositif associé. Durant la transmission d'un paquet de données entre un premier nœud de réseau et un second nœud de réseau, selon une relation de mappage entre les premières informations d'en-tête de paquet IP (telles que l'adresse IP locale du premier nœud de réseau et des secondes informations d'en-tête de paquet IP) et des informations QoS envoyées par un troisième nœud de réseau, le deuxième nœud de réseau détermine un paramètre QoS et des secondes informations de canal d'un paquet de données à envoyer ; selon une relation de mappage, qui est envoyée après la construction du troisième nœud de réseau et/ou du deuxième nœud de réseau, entre des informations, telles que les secondes informations de canal, et un identifiant de flux QoS, le premier nœud de réseau détermine les secondes informations de canal dudit paquet de données, de sorte que le premier/deuxième nœud de réseau envoie ledit paquet de données à l'autre nœud selon le paramètre QoS obtenu et les secondes informations de canal, ce qui satisfait la cohérence d'exigences de QoS de bout en bout ; et un réseau central ne doit pas construire les relations de mappage susmentionnées, de sorte qu'une augmentation de charge de travail dans le changement de configuration de fonction du réseau central est évitée.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110956447.6A CN113630902B (zh) | 2021-08-19 | 2021-08-19 | 基于网络服务质量的数据包传输方法及相关设备 |
| CN202110956447.6 | 2021-08-19 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2023019895A1 true WO2023019895A1 (fr) | 2023-02-23 |
Family
ID=78386799
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2022/076794 Ceased WO2023019895A1 (fr) | 2021-08-19 | 2022-02-18 | Procédé de transmission de paquet de données sur la base de la qualité de service d'un réseau, et dispositif associé |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113630902B (fr) |
| WO (1) | WO2023019895A1 (fr) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119562388A (zh) * | 2024-11-13 | 2025-03-04 | 中国移动通信有限公司研究院 | 一种设备组网方法、装置、设备、存储介质及产品 |
| WO2025140671A1 (fr) * | 2023-12-29 | 2025-07-03 | 华为技术有限公司 | Procédé de communication et appareil de communication |
| WO2025167957A1 (fr) * | 2024-02-07 | 2025-08-14 | 维沃移动通信有限公司 | Procédé et appareil de traitement de données, procédé et appareil de traitement d'informations, et dispositif de communication |
| WO2025232747A1 (fr) * | 2024-05-10 | 2025-11-13 | 华为技术有限公司 | Procédé, appareil et système de communication de relais |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113630902B (zh) * | 2021-08-19 | 2023-04-28 | 联想(北京)有限公司 | 基于网络服务质量的数据包传输方法及相关设备 |
| CN116112447B (zh) * | 2021-11-11 | 2025-09-26 | 华为终端有限公司 | 配置用于传输组播业务的通道的方法及装置 |
| CN116260889A (zh) * | 2021-12-10 | 2023-06-13 | Tcl通讯科技(成都)有限公司 | 通信方法及相关设备 |
| CN114449602B (zh) * | 2022-01-27 | 2024-02-06 | 深圳Tcl新技术有限公司 | 切换方法、存储介质及无线通信装置 |
| JP7644310B2 (ja) * | 2022-04-21 | 2025-03-11 | 京セラ株式会社 | 通信制御方法 |
| CN117319163A (zh) * | 2022-06-22 | 2023-12-29 | 中兴通讯股份有限公司 | 业务数据的传输方法、设备、电子设备和存储介质 |
| WO2024007134A1 (fr) * | 2022-07-04 | 2024-01-11 | 华为技术有限公司 | Procédé et appareil de transmission de données |
| EP4560985A4 (fr) * | 2022-07-29 | 2025-08-20 | Huawei Tech Co Ltd | Procédé et appareil de communication |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108430077A (zh) * | 2017-02-14 | 2018-08-21 | 中国移动通信有限公司研究院 | 一种业务质量标识的方法及无线接入网元设备 |
| CN109565703A (zh) * | 2016-08-01 | 2019-04-02 | 三星电子株式会社 | 用于管理无线通信网络中的数据通信的方法和设备 |
| CN111436081A (zh) * | 2019-03-06 | 2020-07-21 | 维沃移动通信有限公司 | 数据传送的保障方法及通信设备 |
| US20210112437A1 (en) * | 2018-03-16 | 2021-04-15 | Telefonaktiebolaget Lm Ericsson (Publ) | User Plane QOS Bearer Control Method for 5G Fixed Access |
| CN112740630A (zh) * | 2019-02-01 | 2021-04-30 | Oppo广东移动通信有限公司 | 业务处理方法、设备、芯片及计算机程序 |
| CN113630902A (zh) * | 2021-08-19 | 2021-11-09 | 联想(北京)有限公司 | 基于网络服务质量的数据包传输方法及相关设备 |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102036315A (zh) * | 2009-09-29 | 2011-04-27 | 大唐移动通信设备有限公司 | 承载映射方法和设备 |
| CN102098651B (zh) * | 2011-01-21 | 2013-08-14 | 北京邮电大学 | 利用用户服务标识usid实施策略标识与控制的方法 |
| CN110995773B (zh) * | 2016-05-24 | 2021-01-05 | 华为技术有限公司 | QoS控制方法及设备 |
| KR102325344B1 (ko) * | 2016-09-30 | 2021-11-12 | 삼성전자주식회사 | 신규 무선 통신 아키텍쳐에서 듀얼-커넥티비티를 성립하여 데이터를 송신하는 방법 및 장치 |
| US20190132251A1 (en) * | 2017-10-31 | 2019-05-02 | Huawei Technologies Co., Ltd. | Method and system for supporting multiple qos flows for unstructured pdu sessions |
| CN110418427B (zh) * | 2018-04-28 | 2021-06-08 | 华为技术有限公司 | 一种通信方法及装置 |
| US11159976B2 (en) * | 2018-11-19 | 2021-10-26 | Mediatek Inc. | Handling of mapped EPS bearer context for invalid QoS flow description |
| WO2020104925A1 (fr) * | 2018-11-19 | 2020-05-28 | Telefonaktiebolaget Lm Ericsson (Publ) | Interfonctionnement d'un premier réseau central vers un second réseau central tout en réduisant l'utilisation des ressources par défaut du second réseau central |
| CN111586860B (zh) * | 2019-02-19 | 2023-01-06 | 华为技术有限公司 | 一种通信方法及装置 |
-
2021
- 2021-08-19 CN CN202110956447.6A patent/CN113630902B/zh active Active
-
2022
- 2022-02-18 WO PCT/CN2022/076794 patent/WO2023019895A1/fr not_active Ceased
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109565703A (zh) * | 2016-08-01 | 2019-04-02 | 三星电子株式会社 | 用于管理无线通信网络中的数据通信的方法和设备 |
| CN108430077A (zh) * | 2017-02-14 | 2018-08-21 | 中国移动通信有限公司研究院 | 一种业务质量标识的方法及无线接入网元设备 |
| US20210112437A1 (en) * | 2018-03-16 | 2021-04-15 | Telefonaktiebolaget Lm Ericsson (Publ) | User Plane QOS Bearer Control Method for 5G Fixed Access |
| CN112740630A (zh) * | 2019-02-01 | 2021-04-30 | Oppo广东移动通信有限公司 | 业务处理方法、设备、芯片及计算机程序 |
| CN111436081A (zh) * | 2019-03-06 | 2020-07-21 | 维沃移动通信有限公司 | 数据传送的保障方法及通信设备 |
| CN113630902A (zh) * | 2021-08-19 | 2021-11-09 | 联想(北京)有限公司 | 基于网络服务质量的数据包传输方法及相关设备 |
Non-Patent Citations (2)
| Title |
|---|
| MOTOROLA MOBILITY, LENOVO, BROADCOM: "Aligning Trusted and Untrusted Non-3GPP Access with respect to the "Additional QoS Information"", 3GPP DRAFT; S2-1907666_5327_5WWC_ADDITIONAL QOS INFORMATION_V1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Sapporo, Japan; 20190624 - 20190628, 18 June 2019 (2019-06-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051752629 * |
| MOTOROLA MOBILITY, LENOVO, BROADCOM: "PDU Session Establishment / Modification for Trusted Non-3GPP Access", 3GPP DRAFT; S2-1903343_5WWC_PDU SESSION ESTABL_DISC_V1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Xi’an, P.R. China; 20190408 - 20190412, 2 April 2019 (2019-04-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051719506 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2025140671A1 (fr) * | 2023-12-29 | 2025-07-03 | 华为技术有限公司 | Procédé de communication et appareil de communication |
| WO2025167957A1 (fr) * | 2024-02-07 | 2025-08-14 | 维沃移动通信有限公司 | Procédé et appareil de traitement de données, procédé et appareil de traitement d'informations, et dispositif de communication |
| WO2025232747A1 (fr) * | 2024-05-10 | 2025-11-13 | 华为技术有限公司 | Procédé, appareil et système de communication de relais |
| CN119562388A (zh) * | 2024-11-13 | 2025-03-04 | 中国移动通信有限公司研究院 | 一种设备组网方法、装置、设备、存储介质及产品 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113630902B (zh) | 2023-04-28 |
| CN113630902A (zh) | 2021-11-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2023019895A1 (fr) | Procédé de transmission de paquet de données sur la base de la qualité de service d'un réseau, et dispositif associé | |
| US20220182871A1 (en) | Base station, and qos control method of wireless section | |
| CN109196918B (zh) | 一种数据传输控制方法、通信设备及核心网设备 | |
| US10812292B2 (en) | Packet processing method and device | |
| WO2022001761A1 (fr) | Procédé et appareil de communication | |
| WO2016173078A1 (fr) | Procédé et système de transfert de données et ue doté d'une fonction de relais | |
| US12425942B2 (en) | Communication method and apparatus for sending a handover request | |
| US12238154B2 (en) | Multicast session establishment method and network device | |
| WO2019084822A1 (fr) | Procédé, dispositif et système de communication | |
| WO2024051313A1 (fr) | Procédé, appareil et système de gestion de ressources de communication, et support d'enregistrement | |
| US20230199870A1 (en) | Application method of computing bearer and apparatus | |
| WO2023020046A1 (fr) | Procédé de communication et appareil de communication | |
| CN115348665A (zh) | 一种通信方法、设备及系统 | |
| CN115529637A (zh) | 一种通信方法、通信装置及通信系统 | |
| WO2019085635A1 (fr) | Procédé et appareil de détermination d'une adresse mac ethernet | |
| CN113438108B (zh) | 通信加速方法、装置、基站和计算机可读存储介质 | |
| WO2024007134A1 (fr) | Procédé et appareil de transmission de données | |
| CN115915196A (zh) | 一种链路状态检测方法、通信装置及通信系统 | |
| WO2022012361A1 (fr) | Procédé et appareil de communication | |
| CN114424498B (zh) | 数据传输方法、装置、系统和存储介质 | |
| US20250310264A1 (en) | Service flow scheduling method and apparatus | |
| WO2022257629A1 (fr) | Procédé de communication sans fil et appareil de communication | |
| WO2020211538A1 (fr) | Procédé et appareil de transmission de données | |
| US20240121201A1 (en) | Communication method and apparatus | |
| WO2023207637A1 (fr) | Procédé et appareil de communication |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22857217 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12/06/2024) |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 22857217 Country of ref document: EP Kind code of ref document: A1 |