+

WO2018137443A1 - Procédé et dispositif de mise en correspondance de données et appareil sans fil - Google Patents

Procédé et dispositif de mise en correspondance de données et appareil sans fil Download PDF

Info

Publication number
WO2018137443A1
WO2018137443A1 PCT/CN2017/117113 CN2017117113W WO2018137443A1 WO 2018137443 A1 WO2018137443 A1 WO 2018137443A1 CN 2017117113 W CN2017117113 W CN 2017117113W WO 2018137443 A1 WO2018137443 A1 WO 2018137443A1
Authority
WO
WIPO (PCT)
Prior art keywords
control information
user plane
qos
plane entity
network element
Prior art date
Application number
PCT/CN2017/117113
Other languages
English (en)
Chinese (zh)
Inventor
施小娟
黄河
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018137443A1 publication Critical patent/WO2018137443A1/fr

Links

Images

Classifications

    • 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]

Definitions

  • the present disclosure relates to the field of wireless communication technologies, and in particular, to a data mapping method and apparatus, and a wireless device.
  • the 5G system will not be a single system using only one wireless access technology, but can be used in combination.
  • eLTE evolved Long Term Evolution
  • WLAN Wireless Local Area Network
  • newly designed wireless access technology in 5G using these different wireless connections
  • the incoming radio access network (RAN) accesses the unified 5G core network.
  • the above radio access networks using different radio access technologies access the unified 5G core network.
  • the 5G system needs to decouple the core network and the access network, that is, the core network and The access network can evolve independently without causing synchronization enhancement or change on the other side network due to enhancement or change of one side network.
  • the decoupling design of the core network and the access network one of the important issues is how to meet the requirements of QoS (Quality of Service) for different services in different scenarios.
  • the QoS architecture is a coupling design of the core network and the access network.
  • the bearer is used as the minimum QoS processing unit for data transmission.
  • FIG. 1 is a schematic structural diagram of performing QoS processing for data transmission at the bearer granularity in LTE.
  • FIG. 1 illustrates only a case where a PDN connection is established between a User Equipment (UE) and a Packet Data Network (PDN), and a service that serves different QoS requirements on the PDN connection, the core network.
  • UE User Equipment
  • PDN Packet Data Network
  • An Evolved Packet System bearer may be established between the UE and the PDN gateway (P-GW), and each EPS bearer carries one or more data service flows (service) Traffic flow (SDF for short), one or more SDFs carried on an EPS bearer will have the same QoS.
  • the EPS bearer is an end-to-end logical bearer between the UE and the P-GW.
  • the EPS bearer establishes three segments of bearers on the three network interfaces that pass through the LTE network architecture, including establishing the P-GW and the serving gateway ( The S5/S8 bearer on the Serving Gateway (S-GW) interface, the S1-bearer established on the S-GW and the base station (eNB) interface, and the air interface established between the eNB and the UE.
  • Data Radio Bearer DRB
  • S1-bearer and DRB are defined together as an evolved universal terrestrial radio access bearer (E-UTRAN Radio Access Bearer, E for short) between the UE and the S-GW. -RAB).
  • the core network When the core network establishes an EPS bearer, it will notify the eNB of each E-RAB (ie, a section of the EPS bearer on the E-URTAN side).
  • the QoS parameter of the bearer can only be passively accepted or rejected by the eNB. If accepted, the DRB between the UE and the UE is established on the air interface, and the data is scheduled to be transmitted according to the received QoS parameters of the E-RAB level.
  • the QoS policy and parameters, and the mapping relationship between the SDF and the bearer are completely controlled by the core network, and the base station can only passively accept or refuse to establish the DRB.
  • the wireless interface is the key to truly implement and satisfy the QoS.
  • the base station cannot adjust the SDF mapped on each DRB according to the actual wireless load and the quality of the wireless link, so it is not the most efficient. Perform QoS.
  • the core network and the access network are too coupled, and the modification of the core network will directly affect the access network and need to make corresponding modifications, and the independent expansion or evolution of the core network and the access network cannot be realized.
  • 3GPP proposes a flow-based QoS architecture in the 5G system design.
  • the bearer is removed between the core network and the radio access network, but the DRB is retained on the air interface.
  • Figure 2 shows a schematic diagram of a flow-based QoS architecture.
  • the 5G core network receives SDF (such as IP Flow) from a packet data network (such as the Internet), and maps the SDF into a QoS Flow. For example, multiple or the same may be used.
  • SDF such as IP Flow
  • packet data network such as the Internet
  • the SDF of QoS requirements is aggregated into one QoS Flow, and of course, an SDF can be mapped into a QoS Flow.
  • the 5G core network generates a QoS rule according to the QoS policy of the core network, the QoS requirement of the SDF, the subscription information of the user, and completes the mapping of the SDF to the QoS Flow.
  • the QoS rule includes a QoS profile and a precedence order of the QoS feature parameter, and optionally includes a packet filter/data service filter of the SDF using the QoS feature parameter ( Packet filter/traffic filter), where the QoS characteristic parameter may include a QoS flag (QoS ID or QoS marking or QoS flow ID) for identifying or indicating the QoS characteristic parameter, and includes a Maximum Flow Bit Rate (MBR) ), GBR (Guaranteed Flow Bit Rate), Priority level (Priority), PDB (Packet Delay Budget), PER (Packet Error Rate), Admission control Control) and at least one of the parameters.
  • MLR Maximum Flow Bit Rate
  • the 5G core network sends the QoS characteristic parameters in the QoS rule generated by the decision to the RAN through the control plane interface with the RAN (for example, a 5G base station, an eLTE base station, etc.), and the 5G core network passes the user plane interface with the RAN.
  • the QoS Flow is sent to the RAN, and the QoS ID of the QoS characteristic parameter used by the packet is included in the header of each packet containing the QoS flow sent to the RAN.
  • the RAN maps the data packet to the DRB of the air interface according to the QoS characteristic parameter received from the core network, and maps the data packet to the DRB of the air interface to complete the mapping between the QoS Flow and the DRB. In this process, the RAN side can fully consider the actual wireless load, radio link quality and other factors, decide to establish the DRB and decide which QoS flows to map to which DRBs.
  • the technical problem to be solved by the present disclosure is to provide a data mapping method and apparatus and a wireless device to solve how a data stream is transmitted over an air interface in a flow-based QoS architecture, in particular, how the UE performs uplink data and QoS flow. , QoS flow and DRB mapping for uplink data transmission.
  • a data mapping method including: a third network element receives a first user plane entity control protocol data unit from a first network element; and a third network element is configured according to the first user plane
  • the entity control protocol data unit performs a reflected mirror mapping quality of service reflective QoS operation.
  • the first user plane entity control protocol data unit includes at least one of the following control information:
  • Control information 1 control protocol data unit type indication
  • Control information 2 an indication to start or stop the Reflective QoS
  • Control information 3 an indication to start or stop NAS Reflective QoS
  • Control information 4 an indication to start or stop the AS Reflective QoS
  • Control information 5 DRB ID;
  • Control information 6 QoS ID
  • Control information 7 QoS flow and DRB mapping relationship update indication and QoS ID.
  • the reflective QoS operation includes at least one of the following operations:
  • Operation 1 determining whether to initiate a reflective QoS detection for the first user plane entity data protocol data unit
  • Operation 2 Determine the mapping relationship between QoS flow and DRB
  • Operation 3 determining a mapping relationship between the data packet and the QoS flow
  • Operation 4 detecting whether the mapping relationship between the QoS flow of the first user plane entity data protocol unit and the DRB transmitting the data protocol unit is changed, and if a change occurs, updating the mapping relationship between the QoS flow and the DRB;
  • Operation 5 detecting whether the mapping relationship between the data packet acquired from the first user plane entity data protocol unit and the QoS flow is changed, and if a change occurs, updating the mapping relationship between the data packet and the QoS flow.
  • the determining the mapping relationship between the QoS flow and the DRB includes:
  • the third network element performs the operation 1, Operation 2 and operation 3; or,
  • the third network element performs the operation 1 and the operation 3;
  • the third network element performs the operation 1 and the operation 2;
  • the first user plane entity control protocol data unit includes only control information 5, or includes control information 1 and control information 5, or includes control information 2 and control information 5, or includes control information 1, control information 2, and control information. 5, the third network element performs the operation 1, the operation 2 and the operation 3 on the DRB indicated in the control information 5; or
  • the third network element indicates the indication in the control information 5.
  • the third network element indicates the indication in the control information 5.
  • the first user plane entity control protocol data unit includes only control information 6, or includes control information 1 and control information 6, or includes control information 2 and control information 6, or includes control information 1, control information 2, and control information.
  • the third network element performs the operation 2 and the operation 3 according to the first user plane entity control protocol data unit, or according to the first user plane entity data protocol data unit received from the first network element Performing the operation 1, the operation 2 and the operation 3;
  • the third network element is only indicated in the control information 6.
  • the operation 1 and the operation 3 are performed on the DRB mapped by the QoS ID; or,
  • the third network element is based on the first user plane entity. Controlling the data unit to perform the operation 2, or performing the operation 1 and the operation 2 according to the first user plane entity data protocol data unit received from the first network element;
  • the first user plane entity control protocol data unit includes control information 7, or includes control information 1 and control information 6, or contains control information 2 or control information 6, or contains control information 4 and control information 6, or includes control The information, the control information 2, and the control information 6, or the control information 1, the control information 4, and the control information 6, the third network element performs the operation 4 and the operation 5.
  • the third network element maps the DRB mapped by the QoS ID indicated in the control information 6.
  • the operation 1, the operation 2 and the operation 3 are performed on the above.
  • the third network element When the operation 2 is performed according to the first user plane entity data protocol data unit, the third network element performs the operation 1 and the operation 2 on the DRB mapped by the QoS ID indicated in the control information 6.
  • the method further includes:
  • the first user plane entity confirms that the control protocol unit includes a QoS ID.
  • the acknowledgment control protocol unit is sent on the DRB that receives the first user plane entity data protocol data unit,
  • the method further includes:
  • the third network element receives a first user plane entity second control protocol data unit from the first network element, the second control protocol data unit including an indication to stop performing the reflective QoS operation.
  • the method further includes:
  • the third network element receives a first user plane entity data protocol data unit of the first network element, where the first user plane entity data protocol data unit header includes an indication of whether a QoS ID exists.
  • a data mapping apparatus comprising: a receiving module configured to receive a first user plane entity control protocol data unit from a first network element; and an execution module configured to be according to the A user plane entity control protocol data unit performs a reflective QoS operation.
  • the first user plane entity control protocol data unit includes at least one of the following control information:
  • Control information 1 control protocol data unit type indication
  • Control information 2 an indication to start or stop the Reflective QoS
  • Control information 3 an indication to start or stop NAS Reflective QoS
  • Control information 4 an indication to start or stop the AS Reflective QoS
  • Control information 5 DRB ID;
  • Control information 6 QoS ID
  • Control information 7 QoS flow and DRB mapping relationship update indication and QoS ID.
  • the reflective QoS operation includes at least one of the following operations:
  • Operation 1 determining whether to initiate a reflective QoS detection for the first user plane entity data protocol data unit
  • Operation 2 Determine the mapping relationship between QoS flow and DRB
  • Operation 3 determining a mapping relationship between the data packet and the QoS flow
  • Operation 4 detecting whether the mapping relationship between the QoS flow of the first user plane entity data protocol unit and the DRB transmitting the data protocol unit is changed, and if a change occurs, updating the mapping between the QoS flow and the DRB system;
  • Operation 5 detecting whether the mapping relationship between the data packet acquired from the first user plane entity data protocol unit and the QoS flow is changed, and if a change occurs, updating the mapping relationship between the data packet and the QoS flow.
  • the data mapping apparatus further includes: an acknowledgment sending module, configured to send the first user plane entity acknowledgment control protocol unit to the first network element.
  • the first user plane entity confirms that the control protocol unit includes a QoS ID.
  • the acknowledgment control protocol unit is sent on the DRB that receives the first user plane entity data protocol data unit, or is sent on the default DRB, or on any DRB corresponding to the first user plane entity. send.
  • the receiving module is further configured to: receive a first user plane entity second control protocol data unit from the first network element.
  • the execution module is further configured to stop performing the reflective QoS operation according to the second control protocol data unit.
  • an apparatus for operating in wireless communication comprising a processor configured to receive a first user plane entity control protocol data unit from a first network element; A user plane entity control protocol data unit performs a reflective QoS operation;
  • a memory coupled to the processor.
  • the processor is further configured to send the first user plane entity acknowledgement control protocol unit to the first network element.
  • the processor is further configured to receive the first user plane entity second control protocol data unit from the first network element.
  • the processor is further configured to stop performing the reflective QoS operation according to the first user plane entity second control protocol data unit.
  • the present disclosure provides a data mapping method and apparatus, and a wireless device, which can implement data transmission on an air interface, and in particular, can implement mapping of uplink data and QoS flow, QoS flow and DRB, and ensure QoS of QoS flow to the greatest extent. To ensure user experience.
  • 1 is a QoS architecture diagram of an LTE system with a minimum granularity
  • FIG. 2 is a flow-based QoS architecture diagram of a 5G system
  • Figure 3 is a simplified schematic diagram of a 5G system
  • FIG. 4 is a structural diagram of a user plane protocol of a first network element and a third network element
  • FIG. 5 is a schematic diagram of establishing a DRB between a first network element and a third network element
  • FIG. 6 is a protocol structure diagram of a third network element when performing a data mapping process according to an embodiment of the present disclosure
  • FIG. 8 is a flowchart of a method of a data mapping method according to Embodiment 4 of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a data mapping apparatus according to Embodiment 5 of the present disclosure.
  • FIG. 10 is a structural block diagram of a wireless device according to Embodiment 6 of the present disclosure.
  • FIG. 3 is a simplified schematic diagram of a 5G system, including the following network elements:
  • the first network element is a network element that completes the function of the access network (Radio Access Network).
  • it may be an integrated base station that performs all RAN functions, or a RAN device formed by a baseband processing unit (BBU, BaseBand Unit) and a remote radio unit (RRU), or a central processing unit (CU).
  • BBU baseband processing unit
  • RRU remote radio unit
  • CU central processing unit
  • the RAN device that is formed by the Central Unit and the Distributed Processing Unit (DU), the present disclosure does not limit the specific RAN device existence form.
  • the second network element is a network element that performs the Next Generation Core (NG-Core) function.
  • NG-Core Next Generation Core
  • an integrated core network device that implements all core network functions, or a core network device that implements a mobility management function, a session management function, a user plane function, and the like of the core network, respectively.
  • the present disclosure does not limit the form in which a particular NG-Core device exists.
  • the third network element is a network element that performs the function of the user terminal.
  • the third network element can be various user equipments, such as mobile phones, computers, tablet devices, and the like.
  • the first network element and the third network element communicate through a wireless air interface (Uu interface).
  • the control information is transmitted between the first network element and the second network element through the control plane interface (NG-C), and the user plane data packet is transmitted through the user plane interface (NG-U).
  • the third network element exchanges control information with the second network element via the NG-C and Uu interfaces.
  • SRB Signal Radio Bearer
  • DRB Data Radio Bearer
  • a PDU session needs to be established between the third network element and the external network, and more than one PDU session may be established between the third network element and the external network.
  • the session is indicated by the PDU session ID.
  • the first network element establishes a DRB for transmitting data of the PDU session on the Uu interface, multiple DRBs may be established for one PDU session, but different DRBs are established between different PDU sessions, that is, the same DRB. Data from different PDU sessions cannot be transmitted on.
  • the first network element establishes a corresponding default DRB (default DRB) for each PDU session of the third network element.
  • 3gpp angle from the external network (3 rd generation partnership project) organization the network is outside the scope of the definition of 3gpp, such as the data network (data network), the Internet.
  • FIG. 4 is a user plane protocol structure diagram of a first network element and a third network element, including a first user plane entity, a second user plane entity, and a third user plane entity:
  • the first user plane entity is located above the second user plane entity, and one PDU session corresponds to a first user plane entity;
  • a PDU session can correspond to more than one DRB, and these DRBs are used to carry data on the PDU session.
  • Transmission one DRB corresponds to a second user plane entity.
  • a second user plane entity may include multiple second user plane sub-entries, such as a Packet Data Convergence Protocol (PDCP) and a Radio Link Control (RLC). Therefore, a first user plane entity may correspond to multiple second user plane entities, that is, one first user plane entity may correspond to multiple DRBs.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the third user plane entity is located below the second user plane entity, and all the second user plane entities correspond to the same third user plane entity.
  • FIG. 5 is a schematic diagram of establishing a DRB on a first network element and a third network element according to an embodiment of the present disclosure.
  • the control function entity of the second network element generates a QoS rule (QoS rule) parameter according to the data service type; the second network element sends (sends) the generated QoS rule parameter to the third network element;
  • the QoS rule parameter that is sent to the third network element includes: a QoS characteristic parameter and a priority of the QoS characteristic parameter; optionally, the QoS rule parameter may further include: a packet filter using the QoS characteristic parameter;
  • the QoS characteristic parameter includes a QoS label (QoS ID or QoS marking, and the QoS ID is subsequently used in the embodiment of the present disclosure).
  • the QoS ID is used to identify or indicate the QoS characteristic parameter QoS characteristic parameter, or to identify or mark the QoS flow using the QoS characteristic parameter.
  • the QoS characteristic parameter may further include: one or more of MBR, GBR, Priority level, PDB, PER, and Admission control; and the second network element sends the QoS profile parameter in the generated QoS rule.
  • the control plane of the first network element triggers the establishment of the DRB, maps the QoS profile to the DRB, or maps the QoS flow to the DRB.
  • the mapping relationship between the QoS flow and the DRB may be specifically represented by a mapping relationship between the QoS ID and the radio resource bearer identifier (DRB ID), where the DRB ID is used to identify the DRB.
  • DRB ID radio resource bearer identifier
  • the first network element saves the mapping relationship between the QoS flow and the DRB in the first network element. Then, the first network element notifies the third network element to establish the established DRB, and maps the QoS flow to the DRB. The third network element is notified; after receiving the third network element, the DRB is established, and the mapping relationship between the QoS flow and the DRB notified by the first network element is saved.
  • the first network element obtains the DRB after receiving the QoS profile parameter from the second network element, and the first network element does not necessarily establish a DRB for all received QoS profiles, so the above
  • the mapping relationship between the QoS flow and the DRB does not necessarily include the mapping relationship between the QoS ID and the DRB received by the first network element from the second network element. Which QoS profiles or QoS flows are used to establish the DRB. Which DRBs are mapped to the QoS profile or QoS flow depends on the decision of the first network element.
  • the third network element After the third network element receives the mapping relationship between the QoS flow and the DRB as described in FIG. 5, when the third network element has data to be sent to the first network element, the third network element performs the following data mapping process:
  • FIG. 6 is a protocol structure diagram of a third network element when a data mapping process is performed according to an embodiment of the present disclosure.
  • the non-access stratum entity is located above the first user plane entity, and the non-access stratum entity can implement end-to-end communication with the second network element.
  • the QoS rule parameter set received by the third network element from the second network element is received and saved by the non-access stratum entity of the third network element.
  • the third network element After the non-access stratum entity of the third network element receives the data packet from the upper layer, such as the application layer, the third network element The non-access stratum entity parses the data packet, obtains a packet filter in the data packet, and then the non-access stratum entity of the third network element compares the acquired packet filter with the saved slave first network element The packet filters of the QoS rule parameters in the received QoS rule parameter set are matched. After the matching is successful, the non-access stratum of the third network element determines the QoS ID that the data packet should use.
  • the non-access stratum of the third network element performs the matching operation between the packet filter and the QoS rule according to the packet filter in the data packet, and is referred to as determining the mapping relationship between the data packet and the QoS flow, or determining the mapping relationship between the SDF and the QoS flow, or The above three names are used interchangeably in the embodiments of the present disclosure to determine the mapping relationship between the data packet or the SDF and the QoS ID.
  • the non-access stratum sends the determined QoS ID to the first user plane entity.
  • the QoS ID is used to match the "QoS flow and DRB mapping relationship" stored in the first user plane entity, and if the corresponding DRB is matched, Then, the first user plane entity delivers the data packet to the matched second user plane high layer entity corresponding to the DRB.
  • the first user plane entity passes the data packet to the default DRB.
  • the operation of the first user plane entity to match the QoS ID and the mapping relationship between the QoS flow and the DRB is referred to as determining the mapping relationship between the QoS flow and the DRB.
  • control function entity of the second network element generates a QoS rule according to the data service type, and the second network element sends the generated QoS rule parameter to the third network element, where the second network element The QoS profile parameter in the generated QoS rule is sent to the first network element.
  • the data services have different types.
  • the external network providing the data services can provide a relatively stable packet filter.
  • the control function entity of the second network element is generated according to the data service type.
  • the QoS rule includes a packet filter, and the QoS rule sent by the corresponding second network element to the third network element also includes a packet filter.
  • the servers that provide these data services cannot provide relatively stable packet filters.
  • the packet filters of such data services often change, or the number of packet filters for such data services is large.
  • the QoS rule generated by the second network element does not include a packet filter
  • the QoS rule sent by the second network element to the third network element naturally does not include a packet filter, that is, does not include corresponding use of each QoS. Packet filter for QoS flow of feature parameters.
  • the third network element cannot perform the data mapping process as described in the first embodiment, specifically:
  • the QoS rule parameter set received by the third network element from the second network element is received and saved by the non-access stratum entity of the third network element, where the QoS rule does not include a packet filter corresponding to each QoS characteristic parameter.
  • the non-access stratum entity of the third network element receives the data packet from the upper layer, such as the application layer, the non-access stratum entity of the third network element parses the data packet to obtain a packet filter in the data packet.
  • the non-access stratum entity of the third network element matches the obtained packet filter with each saved QoS rule parameter in the QoS rule parameter set received from the first network element, at this time, as described above
  • the second network element does not provide the packet filter of the data service to the third network element, that is, the QoS rule saved by the non-access stratum of the third network element does not include the QoS corresponding to the data service.
  • reflective QoS may be adopted, which is different from the following.
  • the reflective QoS applied to the non-access stratum is called a non-access stratum.
  • Reflective QoS or NAS reflective QoS.
  • the second network element sends the QoS rule parameter to the third network element, it will notify which QoS characteristic parameters will use reflective QoS, such as including a reflective QoS indicator in the QoS characteristic parameter.
  • the second network element when the second network element sends the QoS profile parameter in the QoS rule to the first network element, it is notified which QoS characteristic parameters will use the NAS reflective QoS, for example, the reflective QoS indicator is included in the QoS characteristic parameter; or the second network element
  • the data packet of such data service is sent to the first network element through the NG-U, in addition to the QoS ID in the NG-U interface data packet header, a reflective QoS indicator is also applied.
  • the first network element can know which QoS characteristic parameters need to adopt NAS reflective QoS, or which packets received from the second network element are to adopt NAS reflective QoS.
  • the first network element When the first network element knows which QoS characteristic parameters need to adopt NAS reflective QoS, or which packets received from the second network element are to adopt NAS reflective QoS, the first network element is sent to the third network.
  • the downlink data packet of the element ie, the first user plane entity data protocol data unit
  • the QoS ID is included in the header of the first user plane entity data protocol data unit (ie, the data packet of the first user plane entity) .
  • the third network element in this embodiment still adopts the structure shown in FIG. 6. After the third network element receives the downlink data packet, the first user plane entity of the third network element parses the QoS ID in the data packet header, and sets the QoS ID.
  • the non-access stratum entity submits the non-access stratum entity together with the QoS rule received from the second network element to determine the QoS characteristic parameter indicated by the QoS ID, and needs to adopt NAS reflective QoS, non-access
  • the layer parses out the packet filter from the data packet submitted by the first user plane entity, and saves the packet filter to the QoS characteristic parameter corresponding to the QoS ID.
  • the non-access stratum entity of the third network element parses the data packet to obtain the packet in the data packet.
  • the non-access stratum entity of the third network element matches the acquired packet filter with the packet filter previously obtained from the downlink data packet and stored in the QoS characteristic parameter in the QoS rule parameter set, and matches
  • the non-access stratum of the third network element determines the QoS characteristic parameters that the data packet should use, and then the non-access stratum of the third network element will be used to identify or indicate the QoS ID of the QoS characteristic parameter.
  • the processing procedure is the same as that of the first embodiment.
  • the first network element after the first network element receives the QoS profile parameter from the second network element, the first network element does not necessarily establish a DRB for all received QoS characteristic parameters, that is, The QoS characteristic parameter received by the first network element from the second network element is not necessarily mapped to the DRB. Therefore, as shown in FIG. 5, the first network element notifies the QoS ID of the third network element and the DRB.
  • the mapping relationship does not necessarily include the mapping relationship between the QoS ID and the DRB of the QoS characteristic parameters received by the first network element from the second network element.
  • the first network element does not map the QoS characteristic parameter to the corresponding uplink data wireless.
  • the bearer, or the first network element although the mapping of the QoS characteristic parameter and the DRB is completed, but the mapping relationship is not notified to the third network element, the reflective QoS applied to the access layer may be adopted, which is called the access layer reflective QoS. , that is, AS reflective QoS. specific:
  • the first network element decides to use the AS reflective QoS mode to map from the first user plane entity to the DRB using the QoS flow of the QoS characteristic parameter
  • the first network element is in the downlink data packet sent to the third network element.
  • the QoS ID is included, and the QoS ID is included in the packet header of the first user plane entity.
  • the first user plane entity of the third network element parses the QoS ID in the data packet header, and maps the QoS ID to the DRB used to transmit the downlink data packet. Save to the QoS flow and DRB mapping relationship.
  • the QoS ID can be used to match the saved mapping relationship, thereby The packet is passed to the second user plane entity of the matched DRB.
  • the reflective QoS as described in the second embodiment whether the NAS reflective QoS is used by the second network element, whether the AS reflective QoS is used by the first network element, so the two may use only one of them, or maybe both use. In either case, the use of reflective QoS requires the inclusion of a QoS ID in the downstream packet header.
  • the third network element needs to detect each downstream packet to detect whether the QoS ID is included in the packet header for the foregoing related processing. This will increase the detection and processing overhead of the third network element.
  • the embodiment adopts the method shown in FIG. 7 and includes:
  • the first network element decision needs to perform AS reflective QoS and/or determine that NAS reflective QoS needs to be performed.
  • the first network element needs to perform AS reflective QoS according to resource usage, its own policy and other decisions.
  • the first network element can specifically determine the decision for a certain QoS characteristic parameter, or use the QoSflow of a certain QoS characteristic parameter to perform AS reflective QoS, and determine QoS ID.
  • the first network element determines whether to perform NAS reflective QoS according to which QoS characteristic parameters received from the second network element will use NAS reflective QoS information or according to a reflective QoS indicator in the data packet received from the second network element.
  • the first network element may specifically determine which QoS characteristic parameter is used according to the information, or which QoS flow of which QoS characteristic parameter is used to perform AS reflective QoS, and determine the QoS ID.
  • the first user plane entity of the first network element sends the first user plane entity control protocol data unit to the first user plane entity of the third network element.
  • the first user plane entity control protocol data unit is configured to notify the third network element to perform reflective QoS.
  • the first user plane entity control protocol data unit may include at least one of the following control information:
  • Control information 1 control protocol data unit type indication
  • Control information 2 an indication to start or stop the Reflective QoS
  • Control information 3 an indication to start or stop NAS Reflective QoS
  • Control information 4 an indication to start or stop the AS Reflective QoS
  • Control information 5 DRB ID;
  • Control information 6 QoS ID
  • Control information 7 QoS flow and DRB mapping relationship update indication and QoS ID;
  • the third network element and the first network element perform reflective QoS.
  • the indications in the control information 2 to the control information 4 are all activation instructions.
  • the third network element and the first network element perform a reflective QoS operation according to the first user plane entity control protocol data unit received in the S702.
  • the third network element performs a reflective QoS operation according to the first user plane entity control protocol data unit, and includes at least one of the following operations:
  • Operation 1 determining whether to initiate a reflective QoS detection for the first user plane entity data protocol data unit
  • Operation 2 Determine the mapping relationship between QoS flow and DRB
  • Operation 3 determining a mapping relationship between the data packet and the QoS flow
  • Operation 4 detecting whether the mapping relationship between the QoS flow of the first user plane entity data protocol unit and the DRB transmitting the data protocol unit is changed, and if a change occurs, updating the mapping relationship between the QoS flow and the DRB;
  • Operation 5 detecting whether the mapping relationship between the data packet acquired from the first user plane entity data protocol unit and the QoS flow is changed, and if a change occurs, updating the mapping relationship between the data packet and the QoS flow.
  • the operation is also different, specifically the following cases:
  • the first user plane entity control protocol data unit contains only control information 1 or only control information 2, or both control information 1 and control information 2.
  • Control information 1 (control protocol data unit type indication) is used to indicate that the first user plane entity control protocol data unit is a control protocol data unit for reflective QoS.
  • the third network element performs operation 1, operation 2 and operation 3. among them:
  • Operation 1 The first user plane entity of the third network element determines to initiate the reflective QoS detection for the first user plane entity data protocol data unit, that is, the third network element performs any of the received first during the reflective QoS The user plane entity data protocol data unit, the first user plane entity needs to resolve the QoS ID in the data protocol unit header.
  • the first user plane entity of the third network element determines a mapping relationship between the QoS flow and the DRB.
  • the first user plane entity of the third network element determines the QoS flow and the DRB according to the first user plane entity data protocol data unit.
  • Mapping relationship that is, during the performing reflective QoS, the third network element parses out the QoS ID in the data protocol unit header for any first user plane entity data protocol data unit received, and determines the transmission.
  • the DRB of the first user plane physical data protocol data unit saves the mapping relationship between the determined QoS ID and the DRB to a mapping relationship between the uplink QoS ID and the DRB.
  • the non-access stratum entity of the third network element determines a mapping relationship between the data packet and the QoS flow, that is, the third network element receives any of the first user plane entity data protocol data units during the performing reflective QoS.
  • the first user plane entity parses the QoS ID in the data protocol unit header, and sends the parsed QoS ID and the data packet to the non-access stratum.
  • the non-access stratum entity needs to adopt NAS when determining the QoS characteristic parameter (or QoS flow) indicated by the QoS ID.
  • the reflective QoS, the non-access stratum parses the packet filter from the data packet, and saves the packet filter to the QoS characteristic parameter corresponding to the QoS ID.
  • the data packet refers to an end-to-end data packet, such as an IP packet, for communication between the third network element and an external network.
  • the non-access stratum entity of the third network element After performing the above three operations, after the non-access stratum entity of the third network element receives the data packet from the upper layer, the non-access stratum entity of the third network element parses the data packet to obtain the data packet. a packet filter, and then the non-access stratum entity of the third network element matches the acquired packet filter with the packet filter obtained by the foregoing three operations and stored in the QoS characteristic parameter in the QoS rule parameter set, and matches After success, the non-access stratum of the third network element determines the QoS characteristic parameters that the data packet should use, and then the non-access stratum of the third network element will be used to identify or indicate the QoS ID of the QoS characteristic parameter. The first user plane entity of the third network element.
  • the first user plane entity control protocol data unit contains only the control information 3, or contains the control information 1 and the control information 3.
  • the third network element After the first user plane entity of the third network element receives the control protocol data unit, the third network element performs operation 1 and operation 3. These operations are the same as those of case 1.
  • the first user plane entity control protocol data unit contains only the control information 4, or contains the control information 1 and the control information 4.
  • the third network element After the first user plane entity of the third network element receives the control protocol data unit, the third network element performs operation 1 and operation 2, which are the same as the description of case 1.
  • the first network element performs the reflective QoS: the first network element includes the QoS ID in all the downlink data packets sent to the third network element during the performing reflective QoS.
  • the first user plane entity control protocol data unit contains only control information 5, or contains control information 1 and control information 5, or contains control information 2 and control information 5, or contains control information 1, control information 2, and control Information 5.
  • the third network element performs only operation 1, operation 2 and operation 3 on the DRB indicated in the control information 5, ie :
  • Operation 1 The first user plane entity of the third network element determines to initiate the reflective QoS detection of the first user plane entity data protocol data unit on the DRB indicated in the control information 5, that is, the third network element performs during the reflective QoS For any first user plane entity data protocol data unit received on the DRB indicated in the control information 5, the first user plane entity needs to resolve the QoS ID in the data protocol unit header.
  • Operation 2 The first user plane entity of the third network element determines a mapping relationship between the QoS flow and the DRB, that is, any one received by the third network element on the DRB indicated in the control information 5 during the performing reflective QoS a user plane entity data protocol data unit, the first user plane entity parses out the QoS ID in the data protocol unit header, and determines a DRB that transmits the first user plane entity data protocol data unit, and determines the determined QoS ID
  • the mapping relationship with the DRB is saved in the mapping relationship between the uplink QoS ID and the DRB.
  • Operation 3 The non-access stratum entity of the third network element determines a mapping relationship between the data packet and the QoS flow, that is, any third received by the third network element on the DRB indicated in the control information 5 during the performing reflective QoS
  • the first user plane entity data protocol data unit, the first user plane entity parses out the QoS ID in the data protocol unit header, and parses out The QoS ID and data packets are sent to the non-access stratum.
  • the non-access stratum entity determines that the QoS characteristic parameter (or QoS flow) indicated by the QoS ID needs to adopt NAS reflective QoS, and the non-access stratum layer parses out the packet filter from the data packet, and saves the packet filter to the The QoS characteristic parameter corresponding to the QoS ID.
  • the DRB included in the control protocol data unit may exceed one, which will be described later.
  • the first user plane entity control protocol data unit includes control information 3 and control information 5, or includes control information 1, control information 3, and control information 5.
  • the third network element performs only operation 1 and operation 3 on the DRB indicated in the control information 5, and these operations are the same. 4 instructions.
  • the first user plane entity control protocol data unit includes control information 4 and control information 5, or includes control information 1, control information 4, and control information 5.
  • the third network element performs only operation 1 and operation 2 on the DRB indicated in the control information 5, and these operations are the same as those of the case 4.
  • the first network element performs reflective QoS: the first network element sends all the downlink data packets to the third network element on the DRB indicated by the control information 5 during the performing reflective QoS. Contains the QoS ID.
  • the first user plane entity control protocol data unit contains only control information 6, or contains control information 1 and control information 6, or contains control information 2 and control information 6, or contains control information 1, control information 2 and control Information 6.
  • the first user plane entity of the third network element determines the mapping relationship between the QoS flow and the DRB according to the first user plane entity control protocol data unit or according to the first user plane entity data protocol data unit.
  • the mapping relationship between the QoS flow and the DRB is determined according to the first user plane entity data protocol data unit
  • the third network element Operation 1, operation 2, and operation 3 are performed only on the DRB to which the QoS ID indicated in the control information 6 is mapped, and these operations are the same as those of the case 4.
  • the QoS ID included in the control protocol data unit may exceed one, which will be described later.
  • the control protocol data unit may further include the DRB mapped by the QoS ID, when the mapping relationship between the QoS flow and the DRB is determined according to the first user plane entity control protocol data unit.
  • operations 2 and 3 are performed. Different from the above description, in operation 2, the first user plane entity of the third network element can determine the mapping relationship between the QoS flow and the DRB according to the DRB mapped by the QoS ID included in the control protocol data unit. .
  • the first network element sends the first user plane on the DRB-X when determining the mapping relationship between the QoS flow and the DRB according to the first user plane entity control protocol data unit.
  • An entity control protocol data unit wherein the first network element is to map the QoS flow identified by the QoS ID to the DRB-X.
  • operations 2 and 3 are performed. Different from the above description, where operation 2 is performed, the first user plane entity of the third network element according to the QoS ID included in the control protocol data unit and the DRB (ie, DRB-X) receiving the control protocol data unit
  • the mapping relationship between the QoS flow and the DRB can be determined.
  • the first user plane entity control protocol data unit includes control information 3 and control information 6, or control information 1, control information 3, and control information 6.
  • the third network element performs only operation 1 and operation 3 on the DRB mapped by the QoS ID indicated in the control information 6. These operations are the same as in Case 4.
  • the first user plane entity control protocol data unit includes control information 4 and control information 6, or control information 1, control information 4, and control information 6.
  • the first user plane entity of the third network element determines the mapping relationship between the QoS flow and the DRB according to the first user plane entity control protocol data unit or according to the first user plane entity data protocol data unit.
  • the third network element Operation 1 and operation 2 are performed only on the DRB to which the QoS ID indicated in the control information 6 is mapped, and these operations are the same as those of the case 4.
  • the control protocol data unit may further include the DRB mapped by the QoS ID, when the mapping relationship between the QoS flow and the DRB is determined according to the first user plane entity control protocol data unit.
  • operation 2 is performed. Different from the above description, in operation 2, the first user plane entity of the third network element can determine the mapping relationship between the QoS flow and the DRB according to the DRB mapped by the QoS ID included in the control protocol data unit. .
  • the first network element sends the first user plane on the DRB-X when determining the mapping relationship between the QoS flow and the DRB according to the first user plane entity control protocol data unit.
  • An entity control protocol data unit wherein the first network element is to map the QoS flow identified by the QoS ID to the DRB-X.
  • operation 2 is performed. Different from the above description, where operation 2 is performed, the first user plane entity of the third network element according to the QoS ID included in the control protocol data unit and the DRB (ie, DRB-X) receiving the control protocol data unit
  • the mapping relationship between the QoS flow and the DRB can be determined.
  • the first network element performs reflective QoS: all downlink packets sent by the first network element to the third network element on the DRB mapped by the QoS ID indicated in the control information 6 during the performing reflective QoS Contains the QoS ID.
  • the first user plane entity data protocol data unit header sent by the first network element to the third network element includes an indication of whether there is a QoS ID in the packet header.
  • the third network element determines the mapping relationship between the QoS flow and the DRB according to the first user plane entity control protocol data unit, the “indication of whether the QoS ID exists” is set to No, and the third network element is based on the first user plane entity.
  • the data protocol data unit determines the mapping relationship between the QoS flow and the DRB, and the "whether or not there is an indication of the QoS ID" is set to Yes.
  • Case 10 the first user plane entity control protocol data unit contains control information 7, or contains control information 1 and control information 6, or contains control information 2 or control information 6, or contains control information 4 and control information 6, or The person includes control information 1, control information 2 and control information 6, or control information 1, control information 4 and control information 6.
  • the third network element performs operations 4 and 5:
  • Operation 4 The first user plane entity detects whether the mapping relationship between the QoS flow of the first user plane entity data protocol unit and the DRB transmitting the data protocol unit changes, that is, detects the first user plane entity data protocol unit header Whether the mapping relationship between the QoS ID and the DRB transmitting the data protocol unit changes, and if a change occurs, updating the mapping relationship between the QoS flow and the DRB;
  • Operation 5 The non-access stratum detects whether the mapping relationship between the data packet obtained from the first user plane entity data protocol unit and the QoS flow changes, that is, the non-access stratum detection is sent to the user according to the first user plane entity.
  • the data packet and the QoS ID are used to detect whether the packet filter of the data packet changes with the packet filter corresponding to the QoS ID, and if a change occurs, update the mapping relationship between the data packet and the QoS flow.
  • the reflective QoS is performed on the first network element: the first network element sends all the downlinks to the third network element on the DRB of the mapping relationship between the QoS flow and the DRB that needs to be updated during the performing reflective QoS.
  • the QoS ID is included in the packet.
  • the QoS flow and DRB mapping relationship update indication in the control information 7 may also be implicitly represented by the control protocol data unit type, that is, a type of control protocol data unit type is defined to represent the QoS flow and DRB mapping relationship update.
  • the first user plane entity of the third network element sends a first user plane entity acknowledgement control protocol unit to the first user plane entity of the first network element.
  • the acknowledgment control protocol unit is configured to notify the first network element that the third network element has received the downlink data packet including the QoS ID.
  • the confirmation control protocol unit includes at least one of the following features:
  • the acknowledgment control protocol unit includes a QoS ID
  • the acknowledgment control protocol unit transmits on the DRB that receives the first user plane entity data protocol data unit, wherein the first user plane entity data protocol data unit header includes a QoS ID.
  • the acknowledgment control protocol unit includes a QoS ID, which is sent on the default DRB, or is sent on any DRB corresponding to the first user plane entity;
  • the first user plane entity of the first network element sends the first user plane entity second control protocol data unit to the first user plane entity of the third network element.
  • the first user plane entity second control protocol data unit in this step is used to notify the third network element to stop performing reflective QoS, and the first user plane entity second control protocol data unit may include at least one of the following control information. :
  • Control information 1 control protocol data unit type indication
  • Control information 2 an indication to start or stop the Reflective QoS
  • Control information 3 an indication to start or stop NAS Reflective QoS
  • Control information 4 an indication to start or stop the AS Reflective QoS
  • Control information 5 DRB ID;
  • Control information 6 QoS ID
  • the indications in the control information 2 to the control information 4 are all stop instructions.
  • the third network element After receiving the first control plane data unit of the first user plane entity, the third network element stops performing the reflective QoS operation.
  • the situation in which the reflective QoS operation is stopped is different according to the control information included in the second control protocol data unit of the first user plane entity.
  • the combination of the first user plane entity second control protocol data unit is the same as the case 1 to case 9 in S703, and the third network element stops the corresponding operation described in S703 cases 1 to 9.
  • the first user plane entity second control protocol data unit and the first user plane entity control protocol data unit may be designed in the same control packet format, and the control information is used in the data packet format (for example, control information 1 to control) At least one of the information 4 distinguishes whether the control protocol data unit is for notifying the third network element to perform reflective QoS or for notifying the third network element to stop performing reflective QoS.
  • FIG. 8 is a flowchart of a method for data mapping according to an embodiment of the present disclosure, including:
  • the first user plane entity of the third network element receives the first user plane entity control protocol data unit of the first user plane entity from the first network element.
  • the first user plane entity control protocol data unit includes at least one of the following control information:
  • Control information 1 control protocol data unit type indication
  • Control information 2 an indication to start or stop the Reflective QoS
  • Control information 3 an indication to start or stop NAS Reflective QoS
  • Control information 4 an indication to start or stop the AS Reflective QoS
  • Control information 5 DRB ID;
  • Control information 6 QoS ID
  • Control information 7 QoS flow and DRB mapping relationship update indication and QoS ID;
  • the third network element performs a reflective mirror mapping quality of service (reflective QoS) operation according to the first user plane entity control protocol data unit.
  • Reflective QoS reflective mirror mapping quality of service
  • the reflective QoS operation includes at least one of the following operations:
  • Operation 1 determining whether to initiate a reflective QoS detection for the first user plane entity data protocol data unit
  • Operation 2 Determine the mapping relationship between QoS flow and DRB
  • Operation 3 determining a mapping relationship between the data packet and the QoS flow
  • Operation 4 detecting whether the mapping relationship between the QoS flow of the first user plane entity data protocol unit and the DRB transmitting the data protocol unit is changed, and if a change occurs, updating the mapping relationship between the QoS flow and the DRB;
  • Operation 5 detecting whether a mapping relationship between the data packet acquired from the first user plane entity data protocol unit and the QoS flow is changed, and if a change occurs, updating a mapping relationship between the data packet and the QoS flow;
  • the third network element performs operation 1, operation 2 and Operation 3;
  • the third network element performs operations 1 and 3;
  • the third network element performs operations 1 and 2;
  • the third network element performs operation 1, operation 2 and operation 3 on the DRB indicated in the control information 5;
  • the first user plane entity control protocol data unit includes the control information 3 and the control information 5, or includes the control information 1, the control information 3, and the control information 5, the third network element pairs the DRB indicated in the control information 5. Perform operation 1 and operation 3 on;
  • the first user plane entity control protocol data unit includes the control information 4 and the control information 5, or includes the control information 1, the control information 4, and the control information 5, the third network element pairs the DRB indicated in the control information 5. Perform operation 1 and operation 2 on;
  • the first user plane entity of the third network element determines the mapping relationship between the QoS flow and the DRB according to the first user plane entity control protocol data unit or according to the first user plane entity data protocol data unit.
  • the third network element When the mapping relationship between the QoS flow and the DRB is determined according to the first user plane entity data protocol data unit, the third network element performs operation 1, operation 2, and operation 3 on the DRB mapped by the QoS ID indicated in the control information 6. .
  • the control protocol data unit may further include the DRB mapped by the QoS ID, when the mapping relationship between the QoS flow and the DRB is determined according to the first user plane entity control protocol data unit.
  • operations 2 and 3 are performed. Different from the above description, in operation 2, the first user plane entity of the third network element can determine the mapping relationship between the QoS flow and the DRB according to the DRB mapped by the QoS ID included in the control protocol data unit. .
  • the first network element sends the first user plane on the DRB-X when determining the mapping relationship between the QoS flow and the DRB according to the first user plane entity control protocol data unit.
  • An entity control protocol data unit wherein the first network element is to map the QoS flow identified by the QoS ID to the DRB-X.
  • operations 2 and 3 are performed. Different from the above description, where operation 2 is performed, the first user plane entity of the third network element according to the QoS ID included in the control protocol data unit and the DRB (ie, DRB-X) receiving the control protocol data unit
  • the mapping relationship between the QoS flow and the DRB can be determined.
  • the third network element is only indicated by the control information 6.
  • QoS ID Perform operation 1 and operation 3 on the shot DRB;
  • the first user plane entity control protocol data unit includes the control information 4 and the control information 6, or includes the control information 1, the control information 4, and the control information 6, the first user plane entity of the third network element is according to the first The user plane entity controls the protocol data unit or determines the mapping relationship between the QoS flow and the DRB according to the first user plane entity data protocol data unit.
  • the third network element performs operations 1 and 2 on the DRB mapped by the QoS ID indicated in the control information 6 when determining the mapping relationship between the QoS flow and the DRB according to the first user plane entity data protocol data unit;
  • the control protocol data unit may further include the DRB mapped by the QoS ID, when the mapping relationship between the QoS flow and the DRB is determined according to the first user plane entity control protocol data unit.
  • operation 2 is performed. Different from the above description, in operation 2, the first user plane entity of the third network element can determine the mapping relationship between the QoS flow and the DRB according to the DRB mapped by the QoS ID included in the control protocol data unit. .
  • the first network element sends the first user plane on the DRB-X when determining the mapping relationship between the QoS flow and the DRB according to the first user plane entity control protocol data unit.
  • An entity control protocol data unit wherein the first network element is to map the QoS flow identified by the QoS ID to the DRB-X.
  • operation 2 is performed. Different from the above description, where operation 2 is performed, the first user plane entity of the third network element according to the QoS ID included in the control protocol data unit and the DRB (ie, DRB-X) receiving the control protocol data unit
  • the mapping relationship between the QoS flow and the DRB can be determined.
  • the third network element performs operations 4 and 5;
  • the first user plane entity of the third network element sends a first user plane entity acknowledgement control protocol unit to the first user plane entity of the first network element.
  • the confirmation control protocol unit includes at least one of the following features:
  • the acknowledgment control protocol unit includes a QoS ID
  • the acknowledgment control protocol unit is sent on the DRB of the first user plane entity data protocol data unit, where the first user plane entity data protocol data unit header includes a QoS ID;
  • the acknowledgment control protocol unit includes a QoS ID, which is sent on the default DRB, or is sent on any DRB corresponding to the first user plane entity;
  • the method in the embodiment of the present disclosure may further include:
  • the first user plane entity of the third network element receives the first user plane entity second control protocol data unit of the first user plane entity from the first network element, and the third network element is configured according to the first user plane entity.
  • the first user plane entity second control protocol data unit includes at least one of the following control information:
  • Control information 1 control protocol data unit type indication
  • Control information 2 an indication to start or stop the Reflective QoS
  • Control information 3 an indication to start or stop NAS Reflective QoS
  • Control information 4 an indication to start or stop the AS Reflective QoS
  • Control information 5 DRB ID;
  • Control information 6 QoS ID
  • the first user plane entity second control protocol data unit and the first user plane entity control protocol data unit may be designed in the same control packet format, and the control information is used to distinguish the control protocol in the data packet format.
  • the data unit is configured to notify the third network element to perform reflective QoS or to notify the third network element to stop performing reflective QoS.
  • control information may be at least one of the control information 1 to the control information 4.
  • FIG. 9 is a schematic structural diagram of a data mapping apparatus according to an embodiment of the present disclosure.
  • the apparatus is applied to a third network element, as shown in FIG.
  • the receiving module 901, the first user plane entity for the third network element receives the first user plane entity control protocol data unit of the first user plane entity from the first network element;
  • the first user plane entity control protocol data unit includes at least one of the following control information:
  • Control information 1 control protocol data unit type indication
  • Control information 2 an indication to start or stop the Reflective QoS
  • Control information 3 an indication to start or stop NAS Reflective QoS
  • Control information 4 an indication to start or stop the AS Reflective QoS
  • Control information 5 DRB ID;
  • Control information 6 QoS ID
  • Control information 7 QoS flow and DRB mapping relationship update indication and QoS ID;
  • the executing module 902 is configured to perform, by the third network element, a reflective mirror mapping service quality (reflective QoS) operation according to the first user plane entity control protocol data unit.
  • a reflective mirror mapping service quality reflective QoS
  • the reflective QoS operation includes at least one of the following operations:
  • Operation 1 determining whether to initiate a reflective QoS detection for the first user plane entity data protocol data unit
  • Operation 2 Determine the mapping relationship between QoS flow and DRB
  • Operation 3 determining a mapping relationship between the data packet and the QoS flow
  • Operation 4 detecting whether the mapping relationship between the QoS flow of the first user plane entity data protocol unit and the DRB transmitting the data protocol unit is changed, and if a change occurs, updating the mapping relationship between the QoS flow and the DRB;
  • Operation 5 detecting whether a mapping relationship between the data packet acquired from the first user plane entity data protocol unit and the QoS flow is changed, and if a change occurs, updating a mapping relationship between the data packet and the QoS flow;
  • the acknowledgment control protocol unit sending module 903, the first user plane entity for the third network element sends the first user plane entity acknowledgment control protocol unit to the first user plane entity of the first network element.
  • the confirmation control protocol unit includes at least one of the following features:
  • the acknowledgment control protocol unit includes a QoS ID
  • the acknowledgment control protocol unit is sent on the DRB of the first user plane entity data protocol data unit, where the first user plane entity data protocol data unit header includes a QoS ID.
  • the acknowledgment control protocol unit includes a QoS ID, which is sent on the default DRB, or is sent on any DRB corresponding to the first user plane entity;
  • the receiving module 901 in the data mapping apparatus of the embodiment of the present disclosure may be further configured to: the first user plane entity of the third network element receives the first user plane entity of the first user plane entity from the first network element Second control protocol data unit.
  • the executing module 902 in the data mapping apparatus of the embodiment of the present disclosure may be further configured to: stop, by the third network element, the performing the reflective QoS operation according to the first user plane entity second control protocol data unit.
  • the first user plane entity second control protocol data unit includes at least one of the following control information:
  • Control information 1 control protocol data unit type indication
  • Control information 2 an indication to start or stop the Reflective QoS
  • Control information 3 an indication to start or stop NAS Reflective QoS
  • Control information 4 an indication to start or stop the AS Reflective QoS
  • Control information 5 DRB ID;
  • Control information 6 QoS ID
  • the first user plane entity second control protocol data unit and the first user plane entity control protocol data unit may be designed in the same control packet format, and the control information is used to distinguish the control protocol in the data packet format.
  • the data unit is configured to notify the third network element to perform reflective QoS or to notify the third network element to stop performing reflective QoS.
  • an embodiment of the present disclosure further provides a wireless device.
  • a block diagram of a wireless device according to an embodiment of the present disclosure includes a processor and a memory.
  • the processor is configured to receive a first user plane entity control protocol data unit from the first network element, and perform a reflective QoS operation according to the first user plane entity control protocol data unit;
  • a memory coupled to the processor.
  • the processor is further configured to transmit a first user plane entity acknowledgement control protocol unit to the first network element.
  • the processor is further configured to receive a first user plane entity second control protocol data unit from the first network element.
  • the processor is further configured to stop performing the reflective QoS operation described above according to the first user plane entity second control protocol data unit.
  • the device can be controlled by a gesture (such as selecting a function, a configuration parameter, etc.) without the user facing the device. ), and the device itself has a lower cost.
  • a gesture such as selecting a function, a configuration parameter, etc.
  • embodiments of the present disclosure can be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware aspects. Moreover, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the present disclosure is applicable to the field of wireless communication technologies, and is used to implement data transmission on an air interface.
  • the UE can perform uplink data and QoS flow, QoS flow and DRB mapping, and ensure QoS of QoS flow to the greatest extent, and ensure user experience. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé et un dispositif de mise en correspondance de données et un appareil sans fil. Le procédé comprend : la réception par un troisième élément de réseau d'une première unité de données de protocole de commande d'entité de plan utilisateur d'un premier élément de réseau ; et l'exécution par le troisième élément de réseau, en fonction de la première unité de données de protocole de commande d'entité de plan utilisateur, d'une opération de qualité de service par mise en miroir réflexive (QoS réflexive). Le procédé et le dispositif de mise en correspondance de données et l'appareil sans fil de la présente invention peuvent permettre une transmission de données sur une interface radio, et plus particulièrement, ils peuvent permettre à un ensemble équipement utilisateur de mettre en œuvre une mise en correspondance entre des données de liaison montante et un flux QoS, et entre le flux QoS et un DRB, ce qui garantit une QoS maximale d'un flux QoS, et assure une expérience utilisateur de qualité.
PCT/CN2017/117113 2017-01-26 2017-12-19 Procédé et dispositif de mise en correspondance de données et appareil sans fil WO2018137443A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710064249.2A CN108366397B (zh) 2017-01-26 2017-01-26 数据映射方法及装置和无线设备
CN201710064249.2 2017-01-26

Publications (1)

Publication Number Publication Date
WO2018137443A1 true WO2018137443A1 (fr) 2018-08-02

Family

ID=62979046

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/117113 WO2018137443A1 (fr) 2017-01-26 2017-12-19 Procédé et dispositif de mise en correspondance de données et appareil sans fil

Country Status (2)

Country Link
CN (1) CN108366397B (fr)
WO (1) WO2018137443A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3912387A4 (fr) * 2019-01-17 2022-07-27 ZTE Corporation Procédés, appareils et systèmes de mappage de données dans une communication sans fil
CN111866906B (zh) * 2019-04-29 2021-07-23 大唐移动通信设备有限公司 一种数据传输方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101005440A (zh) * 2006-01-21 2007-07-25 华为技术有限公司 在无线网络中实现差异化服务质量控制的方法
CN101932102A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 业务承载映射方法及通信设备
CN102612095A (zh) * 2012-03-05 2012-07-25 电信科学技术研究院 一种ip数据包的传输方法和设备
CN103118401A (zh) * 2009-06-19 2013-05-22 华为技术有限公司 业务承载映射方法及通信设备
US20150215918A1 (en) * 2012-10-08 2015-07-30 Huawei Technologies Co., Ltd. System, method, and device for processing air interface information

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101064664B (zh) * 2006-04-30 2011-03-02 中兴通讯股份有限公司 一种高速下行分组接入系统服务质量映射与保证方法
CN102231894B (zh) * 2011-07-20 2013-12-25 电信科学技术研究院 一种服务质量验证所需参数的传输方法及装置
US8711699B2 (en) * 2011-10-31 2014-04-29 Amazon Technologies, Inc. Prioritizing application data for transmission in a wireless user device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101005440A (zh) * 2006-01-21 2007-07-25 华为技术有限公司 在无线网络中实现差异化服务质量控制的方法
CN101932102A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 业务承载映射方法及通信设备
CN103118401A (zh) * 2009-06-19 2013-05-22 华为技术有限公司 业务承载映射方法及通信设备
CN102612095A (zh) * 2012-03-05 2012-07-25 电信科学技术研究院 一种ip数据包的传输方法和设备
US20150215918A1 (en) * 2012-10-08 2015-07-30 Huawei Technologies Co., Ltd. System, method, and device for processing air interface information

Also Published As

Publication number Publication date
CN108366397A (zh) 2018-08-03
CN108366397B (zh) 2024-02-23

Similar Documents

Publication Publication Date Title
TWI705715B (zh) 預設服務品質規則管理方法及使用者設備
TWI757621B (zh) 處理qos 操作錯誤的方法及使用者設備
US11159976B2 (en) Handling of mapped EPS bearer context for invalid QoS flow description
CN109005127B (zh) 一种QoS流处理方法、设备和通信系统
WO2018006253A1 (fr) Procédé de traitement de défaillance de liaison radio, dispositif associé et système de communication
TWI719836B (zh) Eps承載處理方法及使用者設備
TWI710270B (zh) 增強型QoS 操作處理方法及使用者設備
WO2018103675A1 (fr) Procédé et appareil de remappage de flux de données, équipement utilisateur et dispositif de réseau d'accès radio
WO2016191963A1 (fr) Procédé pour l'établissement de porteuses, équipement d'utilisateur et station de base
JP2021114800A (ja) 基地局、無線通信システムおよび通信方法
CN108781376A (zh) 数据传输方法、用户设备及接入网设备
CN107295564A (zh) 一种基于流的承载管理方法、数据传输方法及装置
TWI754252B (zh) ＱｏＳ規則管理方法及使用者設備
WO2018137443A1 (fr) Procédé et dispositif de mise en correspondance de données et appareil sans fil
WO2016161724A1 (fr) Procédé de transmission et système de transmission pour signalisation de commande des ressources radio
CN111373834B (zh) 用于建立数据无线承载的客户端设备、接入网设备、方法及计算机程序
CN111699715A (zh) 没有有效EPS承载上下文的QoS流描述的处理
WO2023185608A1 (fr) Procédé de transmission de données et appareil de communication
WO2020164614A1 (fr) Informations d'assistance ainsi que procédé et appareil pour les distribuer
KR20250068709A (ko) Ai/ml 데이터를 처리하는 방법 및 장치

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: 17894028

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17894028

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载