CN108366397B - Data mapping method and device and wireless equipment - Google Patents
Data mapping method and device and wireless equipment Download PDFInfo
- Publication number
- CN108366397B CN108366397B CN201710064249.2A CN201710064249A CN108366397B CN 108366397 B CN108366397 B CN 108366397B CN 201710064249 A CN201710064249 A CN 201710064249A CN 108366397 B CN108366397 B CN 108366397B
- Authority
- CN
- China
- Prior art keywords
- control information
- user plane
- plane entity
- qos
- data unit
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000013506 data mapping Methods 0.000 title claims abstract description 28
- 238000013507 mapping Methods 0.000 claims abstract description 145
- XHSQDZXAVJRBMX-UHFFFAOYSA-N 2-(5,6-dichlorobenzimidazol-1-yl)-5-(hydroxymethyl)oxolane-3,4-diol Chemical compound OC1C(O)C(CO)OC1N1C2=CC(Cl)=C(Cl)C=C2N=C1 XHSQDZXAVJRBMX-UHFFFAOYSA-N 0.000 claims description 17
- 238000001514 detection method Methods 0.000 claims description 17
- 238000004891 communication Methods 0.000 claims description 10
- 230000005540 biological transmission Effects 0.000 abstract description 9
- 238000010586 diagram Methods 0.000 description 22
- 230000006870 function Effects 0.000 description 14
- 238000012545 processing Methods 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 238000010295 mobile communication Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 4
- 238000012790 confirmation Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
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]
Landscapes
- Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A data mapping method and device and wireless equipment, a third network element receives a first user plane entity control protocol data unit of a first network element; and the third network element executes reflection mirror mapping service quality (reflective QoS) operation according to the first user plane entity control protocol data unit. The data mapping method and device and the wireless equipment can realize the transmission of data on an air interface, and particularly can realize the mapping of uplink data and QoS flow and DRB (data rate control) performed by UE (user equipment), so that QoS of the QoS flow is ensured to the greatest extent and user experience is ensured.
Description
Technical Field
The present invention relates to the field of wireless communications technologies, and in particular, to a data mapping method and apparatus, and a wireless device.
Background
During the last decades, mobile communication networks have undergone continuous development, from 2G (the second Generation Mobile Communication System, second generation mobile communication system), 3G has been developed to 4G, in which new communication devices, such as intelligent terminals, handheld tablet computers, etc., are continuously emerging, and the advent of new communication devices has in turn prompted the creation of a large number of new applications, new communication scenarios, whereby it is expected that within the coming years, an exponential increase will occur, both in the number of devices connected to the wireless network, the data transmission rate of each user, and the network capacity. Accordingly, with the full commercialization of 4G technology, the industry is beginning to study next generation mobile communication, i.e., 5 th generation (5G) mobile communication technology.
To achieve the improvement of the demands of 1000 times of network throughput, 100 times of equipment connection number and 10 times of low delay compared with the 4G system, the 5G system is not a system which singly uses only one wireless access technology, but can be used together with the technology of eLTE (evolved Long Term Evolution, further evolution long term evolution) after the 4G is further evolved, the related technology of wireless local area network (Wireless Local Area Network, WLAN for short) and the newly designed wireless access technology in the 5G, and the wireless access networks (RAN) adopting the different wireless access technologies are accessed into a unified 5G core network.
The above wireless access networks adopting different wireless access technologies are accessed into a unified 5G core network, in order to ensure the expandability of the network, the 5G system needs to decouple the design of the core network and the access network, that is, the core network and the access network need to be independently evolved, and the synchronous enhancement or change of the network on the other side is not caused by the enhancement or change of the network on the one side. One of the important issues in decoupling the core network from the access network is how to meet the QoS (Quality of Service ) requirements of different services in different scenarios.
In the related system defined by the third generation partnership project (the 3rd Generation Partnership Project, abbreviated as 3 GPP), the QoS architecture is a design of coupling a core network and an access network. Taking the QoS architecture of the 4G LTE system as an example, a bearer (bearer) is taken as a minimum QoS processing unit during data transmission, and fig. 1 is a schematic diagram of a structure for performing QoS processing with a bearer granularity for data transmission in LTE. Fig. 1 illustrates only a case where a PDN connection is established between a User Equipment (UE) and a packet data network (Public Data Network, PDN), and to serve traffic with different QoS requirements on the PDN connection, the core network may establish a plurality of evolved packet system bearers (Evolved Packet System bearer, EPS bearer) between the UE and a PDN gateway (P-GW), each EPS bearer having one or more data traffic flows (service traffic flow, SDFs) thereon, and one or more SDFs carried on one EPS bearer will have the same QoS. EPS bearer is an end-to-end logical bearer between UE and P-GW, and the EPS bearer correspondingly establishes three segments of bearers over three network interfaces passing through in LTE network architecture, including S5/S8bearer established over P-GW and Serving Gateway (S-GW) interface, S1-bearer established over S-GW and base station (eNB) interface, and data radio bearer (Data Radio Bearer, DRB) established over air interface between eNB and UE, where S1-bearer and DRB are defined together as evolved universal terrestrial radio access network bearer (E-UTRAN Radio Access Bearer, E-RAB) between UE and S-GW. The establishment of EPS bearer and mapping of SDFs to which EPS bearer is transmitted are completely decided and controlled by a core network, when the core network establishes the EPS bearer, the eNB is informed of QoS parameters of each E-RAB (namely, a section of bearer of the EPS bearer on the E-URTAN side), the eNB can only passively accept or stop, if so, the eNB can correspondingly establish DRBs between an air interface and UE, and data scheduling transmission is carried out according to the received QoS parameters of the E-RAB level.
In LTE systems, qoS policies and parameters, and mapping between SDFs and bearers are controlled entirely by the core network, and the base station can only passively accept or refuse to establish DRBs. In a wireless communication system, a wireless interface is a key point of actually performing and satisfying QoS, but in the current QoS architecture, a base station cannot adjust SDFs mapped on each DRB according to actual wireless load and wireless link quality, and thus cannot perform QoS most efficiently. In addition, the coupling between the core network and the access network is too strong, and the modification of the core network directly affects the access network to make corresponding modification, so that independent expansion or evolution of the core network and the access network cannot be realized.
To overcome the above drawbacks in the 4G QoS architecture, and achieve maximum decoupling design of the 5G core network and the access network, 3GPP proposes a flow-based QoS architecture in the 5G system design. In the flow-based QoS architecture, the bearer is cancelled between the core network and the radio access network, but the DRB continues to be reserved on the air interface. As shown in fig. 2, which is a schematic diagram of a Flow-based QoS architecture, the 5G core network receives SDFs (such as IP flows) from a packet data network (such as the Internet), maps the SDFs to QoS flows, for example, multiple SDFs with the same or similar QoS requirements may be aggregated to form one QoS Flow, or alternatively, one SDF may be mapped to form one QoS Flow. Here, the 5G core network generates QoS rules (QoS rule) according to QoS policies of the core network, qoS requirements of the SDF, subscription information of the user, and the like, and completes mapping of the SDF to the QoS Flow. The QoS rule includes a QoS profile and a Priority (Priority) of the QoS profile, and optionally may further include a packet filter/data traffic filter (packet filter/traffic filter) of an SDF using the QoS profile, where the QoS profile may include a QoS tag (QoS ID or QoS marking or QoS flow ID) for identifying or indicating the QoS profile, and at least one of parameters such as MBR (Maximum Flow Bit Rate, maximum stream bit rate), GBR (Guaranteed Flow Bit Rate, guaranteed stream bit rate), priority level (Priority), PDB (Packet Delay Budget ), PER (Packet Error rate, packet error rate), admission control (admission control). The 5G core network sends the QoS characteristic parameter in the QoS rule generated by the decision to the RAN (such as a 5G base station, an eLTE base station and the like) through a control surface interface between the 5G core network and the RAN, the 5G core network sends the QoS Flow to the RAN through a user surface interface between the 5G core network and the RAN, and a QoS ID (QoS marking) of the QoS characteristic parameter used by each data packet containing the QoS Flow is contained in a packet header of the data packet 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 the QoS ID in the packet header received from the core network, and the mapping between the QoS Flow and the DRB is completed. In this process, the RAN side can fully consider factors such as actual radio load, radio link quality, etc., and decide to establish DRBs and decide which QoS flows to map onto which DRBs.
In the above flow-based QoS architecture currently proposed by 3GPP, there is no effective solution for how data is transmitted over the air interface, especially how the UE performs mapping of uplink data and QoS flow, qoS flow and DRB, so that uplink data transmission is performed.
Disclosure of Invention
The invention aims to provide a data mapping method, a data mapping device and wireless equipment, which are used for solving the problem that how to transmit data flow on an air interface in a flow-based QoS architecture, and especially how to perform mapping between uplink data and QoS flow and mapping between QoS flow and DRB for UE so as to transmit the uplink data.
According to an embodiment of the present invention, there is provided a data mapping method including: the third network element receives a first user plane entity control protocol data unit from the first network element; and the third network element executes reflection mirror mapping service quality reflective QoS operation according to the first user plane entity control protocol data unit.
Optionally, the first user plane entity control protocol data unit includes at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
Control information 3: an indication to start or stop NAS Reflective QoS;
control information 4: an indication to start or stop AS Reflective QoS;
control information 5: DRB ID;
control information 6: qoS ID;
control information 7: and updating the indication and QoS ID of the mapping relation between QoS flow and DRB.
Optionally, the reflective QoS operation includes at least one of:
operation 1: determining whether to initiate a reflective QoS detection for the first user plane entity data protocol data unit;
operation 2: determining a mapping relation between QoS flow and DRB;
operation 3: determining the mapping relation between the data packet and the QoS flow;
operation 4: detecting whether the mapping relation between the QoS flow to which the first user plane entity data protocol unit belongs and the DRB transmitting the data protocol unit is changed, if so, updating the mapping relation between the QoS flow and the DRB;
operation 5: and detecting whether the mapping relation between the data packet and the QoS flow acquired from the first user plane entity data protocol unit is changed, and if so, updating the mapping relation between the data packet and the QoS flow.
Alternatively to this, the method may comprise,
the determining the mapping relation between the QoS flow and the DRB comprises the following steps:
Determining a mapping relation between the QoS flow and the DRB according to the DRB mapped by the QoS ID contained in the first user plane entity control protocol data unit; or,
and determining the mapping relation between the QoS flow and the DRB according to the QoS ID contained in the first user plane entity control protocol data unit and the DRB which receives the first user plane entity control protocol data unit.
Alternatively to this, the method may comprise,
when the first user plane entity control protocol data unit only contains control information 1 or only contains control information 2, or contains both control information 1 and control information 2, the third network element executes the operation 1, the operation 2 and the operation 3; or,
when the first user plane entity control protocol data unit only contains control information 3, or contains control information 1 and control information 3, the third network element executes the operation 1 and the operation 3; or,
when the first user plane entity control protocol data unit only contains control information 4, or contains control information 1 and control information 4, the third network element executes the operation 1 and the operation 2; or,
when the first user plane entity control protocol data unit only includes 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 executes the operation 1 on the DRB indicated in the control information 5, the operation 2 and the operation 3; or,
When the first user plane entity control protocol data unit contains control information 3 and control information 5, or contains control information 1, control information 3 and control information 5, the third network element executes the operation 1 and the operation 3 on the DRB indicated in the control information 5; or,
when the first user plane entity control protocol data unit contains control information 4 and control information 5, or contains control information 1, control information 4 and control information 5, the third network element executes the operation 1 and the operation 2 on the DRB indicated in the control information 5; or,
the first ue entity control protocol data unit only includes 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 6, when the third network element performs the operation 2 and the operation 3 according to the first ue entity control protocol data unit, or performs the operation 1 according to the first ue entity data protocol data unit received from the first network element, the operation 2 and the operation 3;
or,
when the first user plane entity control protocol data unit includes control information 3 and control information 6, or includes control information 1, control information 3 and control information 6, the third network element only executes the operation 1 and the operation 3 on the DRB mapped by the QoS ID indicated in the control information 6; or,
When the first user plane entity control protocol data unit contains control information 4 and control information 6, or contains control information 1, control information 4 and control information 6, the third network element executes the operation 2 according to the first user plane entity control protocol data unit, or executes the operation 1 and the operation 2 according to the first user plane entity data protocol data unit received from the first network element;
or,
the first user plane entity controls the control protocol data unit to include control information 7, or include control information 1 and control information 6, or include control information 2 or control information 6, or include control information 4 and control information 6, or include control information 1, control information 2 and control information 6, or include control information 1, control information 4 and control information 6, and the third network element performs the operation 4 and the operation 5.
Alternatively to this, the method may comprise,
when performing the operation 1, the operation 2, and the operation 3 according to the first user plane entity data protocol data unit, the third network element performs the operation 1, the operation 2, and the operation 3 on the DRB mapped by the QoS ID indicated in the control information 6.
Alternatively to this, the method may comprise,
when performing operation 2 according to the first user plane entity data protocol data unit, the third network element performs operation 1 and operation 2 on the DRB mapped by the QoS ID indicated in the control information 6.
Alternatively to this, the method may comprise,
after the third network element executes the reflective QoS operation according to the first user plane entity control protocol data unit, the method further includes:
and sending a first user plane entity acknowledgement control protocol unit to the first network element.
Optionally, the first user plane entity confirms that the control protocol unit contains a QoS ID.
Optionally, the acknowledgement control protocol unit is sent on a DRB that received the first user plane entity data protocol data unit,
or on a default DRB and,
or sending the message on any DRB corresponding to the first user plane entity.
Optionally, after the third network element performs the reflective QoS operation according to the first user plane entity control protocol data unit, the method further includes:
the third network element receives a second control protocol data unit from the first user plane entity of the first network element, wherein the second control protocol data unit comprises an indication of stopping executing the reflective QoS operation.
Optionally, the method further comprises,
the third network element receives a first user plane entity data protocol data unit of the first network element, and the first user plane entity data protocol data unit packet head contains an indication whether a QoS ID exists.
According to still another embodiment of the present invention, there is provided a data mapping apparatus including: a receiving module, configured to receive a first user plane entity control protocol data unit from a first network element; and the execution module is used for executing the reflective QoS operation according to the first user plane entity control protocol data unit.
Optionally, the first user plane entity control protocol data unit includes at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop NAS Reflective QoS;
control information 4: an indication to start or stop AS Reflective QoS;
control information 5: DRB ID;
control information 6: qoS ID;
control information 7: and updating the indication and QoS ID of the mapping relation between QoS flow and DRB.
Optionally, the reflective QoS operation includes at least one of:
Operation 1: determining whether to initiate a reflective QoS detection for the first user plane entity data protocol data unit;
operation 2: determining a mapping relation between QoS flow and DRB;
operation 3: determining the mapping relation between the data packet and the QoS flow;
operation 4: detecting whether the mapping relation between the QoS flow to which the first user plane entity data protocol unit belongs and the DRB transmitting the data protocol unit is changed, if so, updating the mapping relation between the QoS flow and the DRB;
operation 5: and detecting whether the mapping relation between the data packet and the QoS flow acquired from the first user plane entity data protocol unit is changed, and if so, updating the mapping relation between the data packet and the QoS flow.
Optionally, the data mapping device further includes: and the acknowledgement sending module is used for sending a first user plane entity acknowledgement control protocol unit to the first network element.
Optionally, the first user plane entity confirms that the control protocol unit contains a QoS ID.
Optionally, the acknowledgement control protocol unit is sent on a DRB that receives the data protocol data unit of the first user plane entity, or sent on a default DRB, or sent on any DRB corresponding to the first user plane entity.
Optionally, the receiving module is further configured to: and receiving a first user plane entity second control protocol data unit from the first network element.
Optionally, the executing module is further configured to stop executing the reflective QoS operation according to the second control protocol data unit.
According to yet another embodiment of the present invention, there is provided 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; executing reflective QoS operation according to the first user plane entity control protocol data unit;
a memory coupled with the processor.
Optionally, the processor is further configured to process sending the first user plane entity acknowledgement control protocol unit to the first network element.
Optionally, the processor is further configured to receive a first user plane entity second control protocol data unit from the first network element.
Optionally, the processor is further configured to stop executing the reflective QoS operation according to the second control protocol data unit of the first user plane entity.
The invention provides a data mapping method and device and wireless equipment, which can realize the transmission of data on an air interface, and particularly can realize the mapping of uplink data and QoS flow and DRB (data rate control) performed by UE (user equipment), so that the QoS of the QoS flow is ensured to the greatest extent and the user experience is ensured.
Drawings
Fig. 1 is a QoS architecture diagram of an LTE system with a minimum granularity of bearers;
FIG. 2 is a flow-based QoS architecture diagram of a 5G system;
FIG. 3 is a simplified schematic diagram of a 5G system;
fig. 4 is a user plane protocol structure diagram of the first network element and the 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 procedure according to an embodiment of the present invention;
FIG. 7 is a flow chart of performing data mapping according to a third embodiment of the present invention;
FIG. 8 is a flow chart of a method of data mapping according to a fourth embodiment of the present invention;
FIG. 9 is a schematic structural diagram of a data mapping device according to a fifth embodiment of the present invention;
fig. 10 is a block diagram of a wireless device according to a sixth embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail hereinafter with reference to the accompanying drawings. It should be noted that, without conflict, the embodiments of the present invention and features of the embodiments may be arbitrarily combined with each other.
The technical solution of the embodiment of the present invention is applied to, but not limited to, a 5G system, as shown in fig. 3, which is a simplified schematic diagram of the 5G system, and includes the following network elements:
A first network element: the first network element is a network element that performs the function of the access network (Radio Access Network). For example, the present invention may be an integrated base station that performs all RAN functions, or a RAN device that is formed by a BaseBand processing Unit (BBU) and a remote radio Unit (RRU, remote Radio Unit), or a RAN device that is formed by a Central processing Unit (CU) and a Distributed processing Unit (DU), where the present invention is not limited to a specific RAN device existence form.
A second network element: the second network element is a network element that performs the function of the Core network (Next Generation Core, NG-Core). Such as an integrated core network device for implementing all core network functions, or a core network device formed by devices for implementing mobility management functions, session management functions, user plane functions, etc. of the core network respectively. The present invention is not limited to a particular NG-Core device form.
Third network element: the third network element is a network element that performs the function of the user terminal. The third network element may be various user devices such as a cell phone, a computer, a tablet device, etc.
The first network element and the third network element communicate via a radio air interface (Uu interface). Control information is transmitted between the first network element and the second network element through a control plane interface (NG-C), and user plane data packets are transmitted through a user plane interface (NG-U). The third network element interacts control information with the second network element via NG-C and Uu interfaces. Without specific illustration, control plane information between the first network element and the third network element is transmitted over a signaling radio bearer (Signal Radio Bearer, SRB) over the Uu interface, and user plane data is transmitted over a data radio bearer (Data Radio Bearer, DRB) over the Uu interface.
In order to perform data transmission between the third network element and the external network, a PDU session (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, where the PDU session is marked by a PDU session identifier (PDU session ID). When the first network element establishes a DRB for transmitting data of PDU session over the Uu interface, multiple DRBs may be established for one PDU session, but different DRBs are established between different PDU sessions, that is, data from different PDU sessions cannot be transmitted on the same DRB. The first network element establishes a corresponding default DRB (default DRB) for each PDU session of the third network element. Here the external network is a network from 3gpp (3 rd generation partnership project) are described in terms of organization, networks outside the 3gpp definition, such as data networks (data networks), the internet, etc.
Fig. 4 is a diagram of a user plane protocol structure 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 positioned above the second user plane entity, and one PDU session corresponds to one first user plane entity;
One PDU session may correspond to more than one DRB, where the DRBs are used to carry data transmission on the PDU session, and one DRB corresponds to one second user plane entity. One second user plane entity may comprise a plurality of second user plane sub-entities, e.g. comprising a packet convergence protocol (Packet Data Convergence Protocol, PDCP), radio link control protocol (Radio Link Control, RLC). Accordingly, one first user plane entity may correspond to a plurality of second user plane entities, i.e. one first user plane entity may correspond to a plurality of DRBs.
The third user plane entity is located below the second user plane entities, and all the second user plane entities correspond to the same third user plane entity.
Example 1
Fig. 5 is a schematic diagram of the establishment of DRBs on a first network element and a third network element according to a preferred embodiment of the invention. As shown in fig. 5: the control function entity of the second network element generates QoS rule (QoS rule) parameters according to the data service type; the second network element transmits (sends) the generated QoS rule parameters to a third network element; the QoS rule parameters issued to the third network element include: qoS characteristic parameters and priorities of the QoS characteristic parameters; optionally, the QoS rule parameter may further include: a packet filter using the QoS characteristic parameter; wherein the QoS characteristic parameter includes QoS tag (QoS ID or QoS marking), the present invention subsequently unifies QoS IDs. The QoS ID is used to identify or indicate the QoS characteristic parameter, or to identify or indicate the QoS flow using the QoS characteristic parameter. In addition, the QoS characteristic parameters may further include: any one or more of MBR, GBR, priority level, PDB, PER, and Admission control; the second network element transmits the QoS profile parameters in the generated QoS rule to the first network element; after the first network element receives the QoS profile parameters from the second network element, the control plane of the first network element triggers to establish a DRB, maps the QoS profile to the DRB, or maps the QoS flow to the DRB, because the QoS ID is used to identify or mark the QoS flow using the QoS characteristic parameters, so it can also be said that the QoS ID is mapped to the DRB, and in the present invention, the above three can be used interchangeably. The mapping relationship between QoS flow and DRB may be specifically represented by a mapping relationship between QoS ID and radio resource bearer identifier (DRB ID), where DRB ID is used to identify DRB. The first network element stores the mapping relation between QoS flow and DRB in the first network element; then, the first network element informs the third network element to establish the DRB established by the first network element, and informs the third network element of the mapping relation between the QoS flow and the DRB; after the third network element receives the information, the DRB is established, and the mapping relation between the QoS flow notified by the first network element and the DRB is stored.
In the above DRB establishment process, the first network element establishes a DRB after receiving the QoS profile parameters from the second network element, and the first network element does not necessarily establish a DRB for all the received QoS profiles, so that the mapping relationship between QoS flows and DRBs described above does not necessarily include the mapping relationship between QoS IDs received by all the first network element from the second network element and DRBs; the DRBs are specifically established for which QoSprofile or QoS flow, which QoSprofile or QoS flow is mapped to which DRBs, depending on the decision of the first network element.
After the third network element receives the mapping relationship between QoS flow and DRB as described in fig. 5, when the third network element has data to send 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 performing a data mapping procedure according to a preferred embodiment of the present invention. The non-access layer entity is located above the first user plane entity, and the non-access layer entity can realize end-to-end communication with the second network element. As shown in fig. 6, the QoS rule parameter set received by the third network element from the second network element is received and stored by the non-access stratum entity of the third network element. After receiving a data packet from an upper layer, such as an application layer, the non-access layer entity of the third network element analyzes the data packet to obtain a packet filter in the data packet, then the non-access layer entity of the third network element matches the obtained packet filter with the stored packet filters of each QoS rule parameter in the QoS rule parameter set received from the first network element, and after the matching is successful, the non-access layer of the third network element determines the QoS ID which should be used by the data packet. The above operation that the non-access layer of the third network element performs matching according to the packet filter in the data packet and the QoS rule is called 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 determining the mapping relationship between the data packet or the SDF and the QoS ID, and the above three names may be used interchangeably in the present invention. And the non-access layer transmits the determined QoS ID to the first user plane entity. After the first user plane entity receives the QoS ID from the non-access layer, the QoS ID is used for matching the mapping relation between QoS flow and DRB stored in the first user plane entity, if the mapping relation is matched with the corresponding DRB, the first user plane entity transmits the data packet to a second user plane higher-layer entity corresponding to the matched DRB. Otherwise, if the corresponding DRB is not matched, that is, the QoS ID is not found in the "mapping relationship between QoS flow and DRB", the first user plane entity transfers the data packet to a default DRB. The above operation that the first user plane entity performs matching according to the QoS ID and the "mapping relationship between QoS flow and DRB" is referred to as determining the mapping relationship between QoS flow and DRB.
Example two
In the data mapping process in the first embodiment, the control functional entity of the second network element generates a QoS rule according to the data service type, the second network element issues the generated QoS rule parameter to the third network element, and the second network element issues the QoS profile parameter in the generated QoS rule to the first network element.
For some data services, the external network providing the data services can provide relatively stable packet filters, for such data services, the control functional entity of the second network element includes the packet filters in QoS rule generated according to the data service type, and the corresponding QoS rule issued by the second network element to the third network element also includes the packet filters.
However, for some data services, the server providing these data services cannot provide a relatively stable packet filter, the packet filter of such data services is often changed, or the number of packet filters of such data services is large, in which case the packet filter is not included in the QoS rule generated by the second network element, and thus the packet filter is not naturally included in the QoS rule sent by the second network element to the third network element, that is, the packet filter corresponding to the QoS flow using each QoS characteristic parameter is not included. Thus, for such data traffic, the third network element will not be able to perform the data mapping procedure as described in embodiment one, in particular:
The QoS rule parameter set received by the third network element from the second network element is received and stored by a non-access stratum entity of the third network element, where the QoS rule does not include a packet filter corresponding to use of each QoS characteristic parameter. After the non-access layer entity of the third network element receives the data packet from the upper layer, such as the application layer, the non-access layer entity of the third network element analyzes the data packet to obtain a packet filter in the data packet, and then the non-access layer entity of the third network element matches the obtained packet filter with each QoS rule parameter in the stored QoS rule parameter set received from the first network element.
To solve the above problem, a reflection mirror mapping QoS (reflective QoS) may be used, and in order to distinguish from the following, the reflective QoS applied to the Non-Access Stratum (NAS) is referred to as a Non-Access Stratum reflective QoS, namely NAS reflective QoS. The second network element informs the third network element of which QoS characteristic parameters will use the reflective QoS when sending the QoS rule parameter, for example, the QoS characteristic parameters include a reflective QoS indication (reflective QoS indicator). In addition, the second network element informs the first network element of which QoS characteristic parameters are to be used NAS reflective QoS when the QoS profile parameters in the QoS rule are issued to the first network element, for example, reflective QoS indicator is included in the QoS characteristic parameters; alternatively, the second network element may, when sending packets of such data traffic to the first network element via NG-U, tag reflective QoS indicator in addition to QoS ID in the NG-U interface packet header (header). In either way, the first network element can learn which QoS characteristics parameters are to be employed NAS reflective QoS, or which packets received from the second network element are to be employed NAS reflective QoS.
When the first network element knows which QoS characteristic parameters need to be adopted NAS reflective QoS, or which packets received from the second network element need to be adopted NAS reflective QoS, the first network element includes a QoS ID in a downstream packet (i.e., a first user plane entity data protocol data unit) sent to the third network element, where the QoS ID is included in a header of the first user plane entity data protocol data unit (i.e., a packet of the first user plane entity). In this embodiment, the third network element 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 analyzes the QoS ID in the packet header, and submits the QoS ID together with the data packet to the non-access layer entity, where the non-access layer entity determines that the QoS characteristic parameter marked by the QoS ID needs to adopt NAS reflective QoS according to the QoS rule received from the second network element, and the non-access layer analyzes the packet filter from the data packet delivered by the first user plane entity, and stores the packet filter in the QoS characteristic parameter corresponding to the QoS ID. Thus, after the non-access layer entity of the third network element receives the data packet from the upper layer, such as the application layer, the non-access layer entity of the third network element analyzes the data packet to obtain a packet filter in the data packet, then the non-access layer entity of the third network element matches the obtained packet filter with the packet filter in the QoS characteristic parameter obtained from the downlink data packet and stored in the QoS rule parameter set, after the matching is successful, the non-access layer of the third network element determines the QoS characteristic parameter that should be used by the data packet, and then the non-access layer of the third network element sends the QoS ID for identifying or marking the QoS characteristic parameter to the user plane upper layer entity of the third network element. After receiving the data packet from the non-access stratum and the QoS ID, the ue processes the same as in the first embodiment.
In addition, as described in embodiment one, the first network element establishes the DRB after receiving the QoS profile parameter from the second network element, and the first network element does not necessarily establish the DRB for all the received QoS characteristic parameters, i.e. the QoS characteristic parameters received by the first network element from the second network element are not necessarily mapped onto the DRB, so that the mapping relationship between the QoS ID and the DRB of the first network element notified by the first network element does not necessarily include the mapping relationship between the QoS ID and the DRB of all the QoS characteristic parameters received by the first network element from the second network element, as shown in fig. 5. In order to reduce signaling overhead of the first network element informing and updating the mapping relationship between the QoS ID and the DRB to the third network element, when the first network element receives the QoS characteristic parameter, the first network element does not map the QoS characteristic parameter to the corresponding uplink data radio bearer, or the first network element does not inform the mapping relationship to the third network element although mapping of the QoS characteristic parameter and the DRB is completed, reflective QoS applied to the access layer, that is, AS reflective QoS may be adopted. Specific:
when the first network element decides which DRB to map from the first user plane entity to for QoS flows using certain QoS characteristics parameters in AS reflective QoS, the first network element includes a QoS ID in the downstream packet sent to the third network element, where the QoS ID is included in the packet header of the first user plane entity. After the third network element receives the downlink data packet, the first user plane entity of the third network element analyzes the QoS ID in the packet header of the data packet, and stores the mapping relation between the QoS ID and the DRB used for transmitting the downlink data packet into the mapping relation between QoS flow and the DRB. Thus, after the first user plane entity of the third network element receives the data packet from the non-access layer entity and the corresponding QoS ID, the QoS ID can be used to match the stored mapping relationship, so as to transfer the data packet to the second user plane entity of the matched DRB.
Example III
As in embodiment two, the decision of whether to use NAS reflective QoS is made by the second network element, and the decision of whether to use AS reflective QoS is made by the first network element, so that either one or both may be used. In either case, however, the use of reflective QoS requires that the QoS ID be included in the downstream packet header, and the third network element needs to detect each downstream packet to detect whether the QoS ID is included in the packet header to perform the foregoing correlation processing, which increases the detection and processing overhead of the third network element.
In order to reduce the detection and processing overhead of the third network element when implementing the reflective QoS, the present embodiment adopts a method as shown in fig. 7, which includes:
s701, the first network element decides that execution is needed AS reflective QoS and/or determines that execution is needed NAS reflective QoS.
The first network element may specifically determine that the decision needs to be performed AS reflective QoS according to the resource usage, its policy, etc., or perform AS reflective QoS on a certain QoS characteristic parameter or QoSflow using a certain QoS characteristic parameter, so as to determine the QoS ID. The first network element determines NAS reflective QoS that QoS ID needs to be performed according to the information of which QoS characteristic parameters are to be used NAS reflective QoS received from the second network element, or according to reflective QoS indicator in the data packet received from the second network element, and the first network element may specifically determine AS reflective QoS which QoS characteristic parameters are to be performed for which QoS characteristic parameters, or which QoS flow of which QoS characteristic parameters are to be used, according to these information.
S702, a first user plane entity of a first network element sends a first user plane entity control protocol data unit to a first user plane entity of a third network element.
The first user plane entity control protocol data unit is used for notifying the third network element to execute reflective QoS. The first user plane entity control protocol data unit may comprise at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop NAS Reflective QoS;
control information 4: an indication to start or stop AS Reflective QoS;
control information 5: DRB ID;
control information 6: qoS ID;
control information 7: updating the QoS flow and DRB mapping relation, and indicating and QoS ID;
s703, the third network element and the first network element execute reflective QoS.
In this step, the instructions in the control information 2 to the control information 4 are all start instructions.
And the third network element and the first network element perform the reflective QoS operation according to the first user plane entity control protocol data unit received in S702. The third network element performs a reflective QoS operation according to the first user plane entity control protocol data unit, including 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: determining a mapping relation between QoS flow and DRB;
operation 3: determining the mapping relation between the data packet and the QoS flow;
operation 4: detecting whether the mapping relation between the QoS flow to which the first user plane entity data protocol unit belongs and the DRB transmitting the data protocol unit is changed, if so, updating the mapping relation between the QoS flow and the DRB;
operation 5: and detecting whether the mapping relation between the data packet and the QoS flow acquired from the first user plane entity data protocol unit is changed, and if so, updating the mapping relation between the data packet and the QoS flow.
According to the difference of the control information contained in the first user plane entity control protocol data unit, the operation is different, and the following situations are specific:
case 1: the first user plane entity control protocol data unit only comprises control information 1 or only comprises control information 2, or comprises control information 1 and control information 2 at the same time.
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.
For this case, after the first user plane entity of the third network element receives the control protocol data unit, the third network element performs operation 1, operation 2 and operation 3. Wherein:
operation 1: the first user plane entity of the third network element determines to start reflective QoS detection for the first user plane entity data protocol data unit, that is, during the period of executing reflective QoS, for any received first user plane entity data protocol data unit, the first user plane entity needs to analyze the QoS ID in the data protocol unit header (header).
Operation 2: the first user plane entity of the third network element determines the mapping relation between the QoS flow and the DRB, wherein the first user plane entity of the third network element determines the mapping relation between the QoS flow and the DRB according to the first user plane entity data protocol data unit, namely, the third network element analyzes the QoS ID in a data protocol unit header for any received first user plane entity data protocol unit during the period of executing the reflective QoS, determines the DRB for transmitting the first user plane entity data protocol data unit, and stores the determined mapping relation between the QoS ID and the DRB into the mapping relation between the uplink QoS ID and the DRB.
Operation 3: the non-access layer entity of the third network element determines the mapping relation between the data packet and the QoS flow, namely, during the execution of the reflective QoS, the third network element analyzes the QoS ID in the data protocol unit header for any received data protocol data unit of the first user plane entity, and sends the analyzed QoS ID and the data packet to the non-access layer. The non-access layer entity judges that the QoS characteristic parameter (or QoS flow) marked by the QoS ID needs to be NAS reflective QoS, and the non-access layer analyzes a packet filter from the data packet and stores the packet filter into the QoS characteristic parameter corresponding to the QoS ID. Here, the data packet refers to an end-to-end data packet, such as an IP packet, communicated between the third network element and the external network.
After the above three operations are executed, when the non-access layer entity of the third network element receives the data packet from the upper layer, the non-access layer entity of the third network element analyzes the data packet to obtain a packet filter in the data packet, then the non-access layer entity of the third network element matches the obtained packet filter with the packet filter in the QoS characteristic parameters obtained and stored in the QoS rule parameter set after the above three operations are executed, after the matching is successful, the non-access layer of the third network element determines the QoS characteristic parameters which should be used by the data packet, and then the non-access layer of the third network element sends the QoS ID for identifying or marking the QoS characteristic parameters to the first user plane entity of the third network element.
Case 2: the first user plane entity control protocol data unit only comprises control information 3, or comprises control information 1 and control information 3.
For this case, after the first user plane entity of the third network element receives the control protocol data unit, the third network element performs operations 1 and 3, which are the same as the description of case 1.
Case 3: the first user plane entity control protocol data unit only contains control information 4, or contains control information 1 and control information 4.
For this case, after the first user plane entity of the third network element receives the control protocol data unit, the third network element performs operations 1 and 2, which are the same as the description of case 1.
In cases 1 to 3, the first network element performs the reflective QoS as follows: the first network element includes QoS IDs in all downstream packets sent to the third network element during the reflective QoS execution.
Case 4: the first user plane entity control protocol data unit only comprises control information 5, or comprises control information 1 and control information 5, or comprises control information 2 and control information 5, or comprises control information 1, control information 2 and control information 5.
For this case, after the first user plane entity of the third network element receives the control protocol data unit, the third network element performs operation 1, operation 2 and operation 3 only on the DRB indicated in the control information 5, i.e.:
Operation 1: the first ue determines to initiate a reflective QoS detection for the first ue data protocol data unit on the DRB indicated in the control information 5, i.e. the third ue needs to parse the QoS ID in the header of the data protocol unit for any first ue data protocol data unit received on the DRB indicated in the control information 5 during the execution of the reflective QoS.
Operation 2: the first user plane entity of the third network element determines the mapping relation between QoS flow and DRB, namely, during the period of executing the reflective QoS, the third network element analyzes the QoS ID in the header of the data protocol unit for any first user plane entity data protocol data unit received on the DRB indicated in the control information 5, determines the DRB for transmitting the first user plane entity data protocol data unit, and stores the determined mapping relation between the QoS ID and the DRB into the mapping relation between the uplink QoS ID and the DRB.
Operation 3: the non-access layer entity of the third network element determines the mapping relation between the data packet and the QoS flow, that is, during the period of executing the reflective QoS, the third network element analyzes the QoS ID in the header of the data protocol unit for any one of the first user plane entity data protocol data units received on the DRB indicated in the control information 5, and sends the analyzed QoS ID and the data packet to the non-access layer. The non-access layer entity judges that the QoS characteristic parameter (or QoS flow) marked by the QoS ID needs to be NAS reflective QoS, and the non-access layer analyzes a packet filter from the data packet and stores the packet filter into the QoS characteristic parameter corresponding to the QoS ID.
The DRBs contained in the control protocol data unit may be more than one, as will be described later.
Case 5: the first user plane entity control protocol data unit contains control information 3 and control information 5, or contains control information 1, control information 3 and control information 5.
For this case, after the first user plane entity of the third network element receives the control protocol data unit, the third network element performs operations 1 and 3 only on the DRB indicated in the control information 5, which are the same as the description of case 4.
Case 6: the first user plane entity control protocol data unit contains control information 4 and control information 5, or contains control information 1, control information 4 and control information 5.
For this case, the third network element performs operations 1 and 2 only on the DRB indicated in the control information 5, which are the same as the description of case 4.
In cases 4 to 6, the first network element performs the reflective QoS as follows: and the first network element comprises QoS IDs in all downlink data packets sent to the third network element on the DRB indicated by the control information 5 during the execution of the reflective QoS.
Case 7: the first user plane entity control protocol data unit only comprises control information 6, or comprises control information 1 and control information 6, or comprises control information 2 and control information 6, or comprises control information 1, control information 2 and control information 6.
Here, the first user plane entity of the third network element determines the mapping relationship between QoS flow and DRB according to the first user plane entity control protocol data unit or according to the first user plane entity data protocol data unit.
When determining the mapping relationship between QoS flow and DRB according to the first user plane entity data protocol data unit, for this case, after the first user plane entity of the third network element receives the control protocol data unit, the third network element only executes operation 1, operation 2 and operation 3 on the DRB mapped by the QoS ID indicated in the control information 6, which are the same as the description of case 4. The QoS ID contained in the control protocol data unit may be more than one, as will be described later.
When determining the mapping relation between the QoS flow and the DRB according to the first user plane entity control protocol data unit, the control protocol data unit can also comprise the DRB mapped by the QoS ID. After the first user plane entity of the third network element receives the control protocol data unit, operation 2 and operation 3 are performed. Unlike the above description, operation 2 is performed herein, where 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.
Or,
when the control protocol data unit only contains one QoS ID, and when the mapping relation between QoS flow and DRB is determined according to the first user plane entity control protocol data unit, the first network element sends the first user plane entity control protocol data unit on DRB-X, wherein the first network element maps the QoS flow marked by the QoS ID to the DRB-X. After the first user plane entity of the third network element receives the control protocol data unit, operation 2 and operation 3 are performed. Unlike the above description, operation 2 is performed herein, where 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 QoS ID included in the control protocol data unit and the DRB (i.e., DRB-X) that receives the control protocol data unit.
Case 8: the first user plane entity control protocol data unit contains control information 3 and control information 6, or contains control information 1, control information 3 and control information 6.
For this case, after the first user plane entity of the third network element receives the control protocol data unit, the third network element performs operations 1 and 3 only on the DRB mapped by the QoS ID indicated in the control information 6, which are the same as the description of case 4.
Case 9: the first user plane entity control protocol data unit contains control information 4 and control information 6, or contains control information 1, control information 4 and control information 6.
Similarly, in case 7, the first user plane entity of the third network element determines the mapping relationship between QoS flow and DRB according to the first user plane entity control protocol data unit or according to the first user plane entity data protocol data unit.
When determining the mapping relationship between QoS flow and DRB according to the first user plane entity data protocol data unit, for this case, after the first user plane entity of the third network element receives the control protocol data unit, the third network element only executes operation 1 and operation 2 on the DRB mapped by the QoS ID indicated in the control information 6, which are the same as the description of case 4.
When determining the mapping relation between the QoS flow and the DRB according to the first user plane entity control protocol data unit, the control protocol data unit can also comprise the DRB mapped by the QoS ID. After the first user plane entity of the third network element receives the control protocol data unit, operation 2 is performed. Unlike the above description, operation 2 is performed herein, where 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.
Or,
when the control protocol data unit only contains one QoS ID, and when the mapping relation between QoS flow and DRB is determined according to the first user plane entity control protocol data unit, the first network element sends the first user plane entity control protocol data unit on DRB-X, wherein the first network element maps the QoS flow marked by the QoS ID to the DRB-X. After the first user plane entity of the third network element receives the control protocol data unit, operation 2 is performed. Unlike the above description, operation 2 is performed herein, where 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 QoS ID included in the control protocol data unit and the DRB (i.e., DRB-X) that receives the control protocol data unit.
In case 8, the first network element performs reflective QoS is: the first network element includes QoS IDs in all downlink packets sent to the third network element on DRBs mapped by QoS IDs indicated in the control information 6 during execution of the reflective QoS.
In case 7 and case 9, 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 the QoS ID exists in the header. And for the case that the third network element determines the mapping relation between the QoS flow and the DRB according to the first user plane entity control protocol data unit, setting the 'indication whether the QoS ID exists' as no, and for the case that the third network element determines the mapping relation between the QoS flow and the DRB according to the first user plane entity control protocol data unit, setting the 'indication whether the QoS ID exists' as yes.
Case 10: the first user plane entity control protocol data unit comprises control information 7, or comprises control information 1 and control information 6, or comprises control information 2 or control information 6, or comprises control information 4 and control information 6, or comprises control information 1, control information 2 and control information 6, or comprises control information 1, control information 4 and control information 6.
For case 10, the third network element performs operations 4 and 5:
operation 4: the first user plane entity detects whether the mapping relation between the QoS flow to which the first user plane entity data protocol unit belongs and the DRB for transmitting the data protocol unit is changed, namely, detects whether the mapping relation between the QoS ID in the header of the first user plane entity data protocol unit and the DRB for transmitting the data protocol unit is changed, and if the mapping relation is changed, the mapping relation between the QoS flow and the DRB is updated;
operation 5: the non-access layer detects whether the mapping relation between the data packet and QoS flow obtained from the first user plane entity data protocol unit is changed, namely, the non-access layer detects whether the packet filter of the data packet and the packet filter stored in the QoS ID are changed according to the data packet and QoS ID sent to the first user plane entity, and if so, the mapping relation between the data packet and QoS flow is updated.
In case 10, performing the reflective QoS at the first network element is: and the first network element comprises QoS IDs in all downlink data packets sent to the third network element on the DRB of the mapping relation between the QoS flow and the DRB which need to be updated during the execution of the reflective QoS.
In the present invention, the update indication of the mapping relationship between QoS flow and DRB in the control information 7 may also be implicitly indicated by the control protocol data unit type, i.e. a type of control protocol data unit type is defined to indicate the update of the mapping relationship between QoS flow and DRB.
S704, 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 acknowledgement control protocol unit is configured to notify the first network element that the third network element has received the downlink data packet containing the certain QoS ID or IDs.
The acknowledgement control protocol unit comprises at least one of the following features:
the acknowledgment control protocol unit contains a QoS ID;
the acknowledgement control protocol unit is sent on the DRB which receives the first user plane entity data protocol data unit, wherein the first user plane entity data protocol data unit header comprises QoS ID.
The confirmation control protocol unit comprises QoS ID and is sent on default DRB or on any DRB corresponding to the first user plane entity;
S705, the first user plane entity of the first network element sends the second control protocol data unit of the first user plane entity to the first user plane entity of the third network element.
This step is an optional step. The second control protocol data unit of the first user plane entity in this step is configured to notify the third network element to stop executing the reflective QoS, where the second control protocol data unit of the first user plane entity may include at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop NAS Reflective QoS;
control information 4: an indication to start or stop AS Reflective QoS;
control information 5: DRB ID;
control information 6: qoS ID;
in this step, the instructions in the control information 2 to the control information 4 are all stop instructions.
After receiving the second control protocol data unit of the first user plane entity, the third network element stops executing the reflective QoS operation. The stopping situation of the reflective QoS operation is different according to the difference of the control information included in the second control protocol data unit of the first user plane entity. In this embodiment, the combination of the first user plane entity and the second control protocol data unit is the same as the combination of the case 1 to the case 9 in S703, and the third network element stops the corresponding operations described in the case 1 to the case 9 in S703.
The second control protocol data unit of the first user plane entity and the first user plane entity control protocol data unit may be designed in the same control packet format, and control information (for example, at least one of control information 1 to control information 4) is used to distinguish and indicate that the control protocol data unit is used to inform the third network element to execute the reflective QoS or is used to inform the third network element to stop executing the reflective QoS in the data packet format.
Example IV
Based on the above specific embodiments, fig. 8 is a flowchart of a method of the data mapping method of the present invention, which includes:
801. the first user plane entity of the third network element receives a first user plane entity control protocol data unit from the first user plane entity of the first network element.
Wherein the first user plane entity control protocol data unit comprises at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop NAS Reflective QoS;
control information 4: an indication to start or stop AS Reflective QoS;
control information 5: DRB ID;
control information 6: qoS ID;
Control information 7: updating the QoS flow and DRB mapping relation, and indicating and QoS ID;
802. and the third network element executes reflection mirror mapping service quality (reflective QoS) operation according to the first user plane entity control protocol data unit.
Wherein the reflective QoS operation includes at least one of:
operation 1: determining whether to initiate a reflective QoS detection for the first user plane entity data protocol data unit;
operation 2: determining a mapping relation between QoS flow and DRB;
operation 3: determining the mapping relation between the data packet and the QoS flow;
operation 4: detecting whether the mapping relation between the QoS flow to which the first user plane entity data protocol unit belongs and the DRB transmitting the data protocol unit is changed, if so, updating the mapping relation between the QoS flow and the DRB;
operation 5: detecting whether the mapping relation between the data packet and the QoS flow acquired from the first user plane entity data protocol unit is changed, and if so, updating the mapping relation between the data packet and the QoS flow;
here, when the first user plane entity control protocol data unit includes only control information 1 or only control information 2, or includes both control information 1 and control information 2, the third network element performs operation 1, operation 2 and operation 3;
When the first user plane entity control protocol data unit only contains control information 3 or contains control information 1 and control information 3, a third network element executes operation 1 and operation 3;
when the first user plane entity control protocol data unit only contains control information 4, or contains control information 1 and control information 4, a third network element executes operation 1 and operation 2;
when the first user plane entity control protocol data unit only contains 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, a third network element executes operation 1, operation 2 and operation 3 on the DRB indicated in control information 5;
when the first user plane entity control protocol data unit contains control information 3 and control information 5 or contains control information 1, control information 3 and control information 5, a third network element executes operation 1 and operation 3 on the DRB indicated in the control information 5;
when the first user plane entity control protocol data unit contains control information 4 and control information 5, or contains control information 1, control information 4 and control information 5, a third network element executes operation 1 and operation 2 on the DRB indicated in the control information 5;
When the first user plane entity control protocol data unit only contains the control information 6, or contains the control information 1 and the control information 6, or contains the control information 2 and the control information 6, or contains the control information 1, the control information 2 and the control information 6, the first user plane entity of the third network element determines the mapping relation 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.
When determining 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 operation 1, operation 2 and operation 3 on the DRB mapped by the QoS ID indicated in the control information 6.
When determining the mapping relation between the QoS flow and the DRB according to the first user plane entity control protocol data unit, the control protocol data unit can also comprise the DRB mapped by the QoS ID. After the first user plane entity of the third network element receives the control protocol data unit, operation 2 and operation 3 are performed. Unlike the above description, operation 2 is performed herein, where 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.
Or,
when the control protocol data unit only contains one QoS ID, and when the mapping relation between QoS flow and DRB is determined according to the first user plane entity control protocol data unit, the first network element sends the first user plane entity control protocol data unit on DRB-X, wherein the first network element maps the QoS flow marked by the QoS ID to the DRB-X. After the first user plane entity of the third network element receives the control protocol data unit, operation 2 and operation 3 are performed. Unlike the above description, operation 2 is performed herein, where 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 QoS ID included in the control protocol data unit and the DRB (i.e., DRB-X) that receives the control protocol data unit.
When the first user plane entity control protocol data unit contains control information 3 and control information 6, or contains control information 1, control information 3 and control information 6, the third network element only executes operation 1 and operation 3 on the DRB mapped by the QoS ID indicated in the control information 6;
when the first user plane entity control protocol data unit contains the control information 4 and the control information 6 or contains the control information 1, the control information 4 and the control information 6, the first user plane entity of the third network element determines the mapping relation 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.
When determining the mapping relation between the QoS flow and the DRB according to the data unit of the first user plane entity data protocol, the third network element executes operation 1 and operation 2 on the DRB mapped by the QoS ID indicated in the control information 6;
when determining the mapping relation between the QoS flow and the DRB according to the first user plane entity control protocol data unit, the control protocol data unit can also comprise the DRB mapped by the QoS ID. After the first user plane entity of the third network element receives the control protocol data unit, operation 2 is performed. Unlike the above description, operation 2 is performed herein, where 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.
Or,
when the control protocol data unit only contains one QoS ID, and when the mapping relation between QoS flow and DRB is determined according to the first user plane entity control protocol data unit, the first network element sends the first user plane entity control protocol data unit on DRB-X, wherein the first network element maps the QoS flow marked by the QoS ID to the DRB-X. After the first user plane entity of the third network element receives the control protocol data unit, operation 2 is performed. Unlike the above description, operation 2 is performed herein, where 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 QoS ID included in the control protocol data unit and the DRB (i.e., DRB-X) that receives the control protocol data unit.
When 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 contains control information 1, control information 2 and control information 6, or contains control information 1, control information 4 and control information 6, the third network element executes operation 4 and operation 5;
the method of the invention can also comprise the following steps:
803. 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.
Wherein the acknowledgement control protocol unit comprises at least one of the following features:
the acknowledgment control protocol unit contains a QoS ID;
the acknowledgement control protocol unit is sent on the DRB that the first user plane entity receives the first user plane entity data protocol data unit, wherein the first user plane entity data protocol data unit head contains QoS ID;
the confirmation control protocol unit comprises QoS ID and is sent on default DRB or on any DRB corresponding to the first user plane entity;
further, the method of the present invention may further include:
804. The first user plane entity of the third network element receives the first user plane entity second control protocol data unit from the first user plane entity of the first network element, and the third network element stops executing the reflective QoS operation according to the first user plane entity second control protocol data unit.
Wherein the first user plane entity second control protocol data unit includes at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop NAS Reflective QoS;
control information 4: an indication to start or stop AS Reflective QoS;
control information 5: DRB ID;
control information 6: qoS ID;
the second control protocol data unit of the first user plane entity 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 in the data packet format to indicate whether the control protocol data unit is used to inform the third network element to execute the reflective QoS or to inform the third network element to stop executing the reflective QoS.
Here, the control information may be at least one of control information 1 to control information 4.
Example five
Based on the above embodiments, fig. 9 is a schematic structural diagram of a data mapping apparatus according to an embodiment of the present invention, where the apparatus is applied to a third network element, as shown in fig. 9, and includes:
a receiving module 901, configured to receive, by a first user plane entity of a third network element, a first user plane entity control protocol data unit from the first user plane entity of the first network element;
wherein the first user plane entity control protocol data unit comprises at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop NAS Reflective QoS;
control information 4: an indication to start or stop AS Reflective QoS;
control information 5: DRB ID;
control information 6: qoS ID;
control information 7: updating the QoS flow and DRB mapping relation, and indicating and QoS ID;
an execution module 902, configured to execute a reflection mapping quality of service (reflective QoS) operation according to the first user plane entity control protocol data unit by using a third network element.
Wherein the reflective QoS operation includes at least one of:
operation 1: determining whether to initiate a reflective QoS detection for the first user plane entity data protocol data unit;
Operation 2: determining a mapping relation between QoS flow and DRB;
operation 3: determining the mapping relation between the data packet and the QoS flow;
operation 4: detecting whether the mapping relation between the QoS flow to which the first user plane entity data protocol unit belongs and the DRB transmitting the data protocol unit is changed, if so, updating the mapping relation between the QoS flow and the DRB;
operation 5: detecting whether the mapping relation between the data packet and the QoS flow acquired from the first user plane entity data protocol unit is changed, and if so, updating the mapping relation between the data packet and the QoS flow;
the data mapping apparatus of the present invention may further include:
the acknowledgement control protocol unit sending module 903 is configured to send, to the first user plane entity of the first network element, the first user plane entity acknowledgement control protocol unit of the first user plane entity of the third network element.
Wherein the acknowledgement control protocol unit comprises at least one of the following features:
the acknowledgment control protocol unit contains a QoS ID;
and the acknowledgement control protocol unit is sent on the DRB that the first user plane entity receives the first user plane entity data protocol data unit, wherein the first user plane entity data protocol data unit header comprises the QoS ID.
The confirmation control protocol unit comprises QoS ID and is sent on default DRB or on any DRB corresponding to the first user plane entity;
further, the receiving module 901 in the data mapping apparatus of the present invention may be further configured to: the first user plane entity of the third network element receives the first user plane entity second control protocol data unit from the first user plane entity of the first network element.
Furthermore, the execution module 902 in the data mapping apparatus of the present invention may be further configured to stop executing the reflective QoS operation according to the second control protocol data unit of the first user plane entity by the third network element.
Wherein the first user plane entity second control protocol data unit includes at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop NAS Reflective QoS;
control information 4: an indication to start or stop AS Reflective QoS;
control information 5: DRB ID;
control information 6: qoS ID;
the second control protocol data unit of the first user plane entity 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 in the data packet format to indicate whether the control protocol data unit is used to inform the third network element to execute the reflective QoS or to inform the third network element to stop executing the reflective QoS.
Those skilled in the art will appreciate that the implementation functions of the modules in the data mapping apparatus shown in fig. 9 can be understood with reference to the foregoing description of the data mapping method.
Example six
Based on the above embodiments, the present invention further provides a wireless device, and as shown in fig. 10, a block diagram of a wireless device according to an embodiment of the present invention includes a processor and a memory.
Wherein the processor: the method comprises the steps of configuring a first user plane entity control protocol data unit for receiving from a first network element; executing reflective QoS operation according to the first user plane entity control protocol data unit;
and a memory coupled to the processor.
The processor is further configured to process sending 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 executing the reflective QoS operation according to the second control protocol data unit of the first user plane entity.
According to the technical scheme provided by the embodiment of the invention, for the equipment without a gesture recognition component (such as the equipment without a camera), a user does not need to face the equipment, the equipment can be controlled by gestures (such as selection functions, configuration parameters and the like), and the equipment per se increases the cost to be low.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the present invention.
Claims (30)
1. A data mapping method, comprising:
the user equipment receives a first user plane entity control protocol data unit from a base station, wherein the first user plane entity is positioned on an access layer data packet convergence protocol;
The user equipment executes reflection mirror mapping service quality reflective QoS operation according to the first user plane entity control protocol data unit;
wherein the first user plane entity control protocol data unit includes: control information 4: an indication to start or stop access layer Reflective QoS;
wherein the reflective QoS operation includes: operation 1: determining whether to initiate reflective QoS detection for the first user plane entity data protocol data unit, and operation 2: determining a mapping relation between QoS flow and DRB;
after the ue performs the reflective QoS operation according to the first ue control protocol data unit, the method further includes: and sending a first user plane entity acknowledgement control protocol unit to the base station.
2. The method of claim 1, wherein the first user plane entity control protocol data unit further comprises at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop non-access stratum Reflective QoS;
control information 5: a data radio bearer identification, DRB ID;
Control information 6: quality of service identification QoS ID;
control information 7: the mapping relation between the QoS flow and the data radio bearer DRB updates the indication and the QoS ID.
3. The method of claim 2, wherein the reflective QoS operation further comprises at least one of:
operation 3: determining the mapping relation between the data packet and the QoS flow;
operation 4: detecting whether the mapping relation between the QoS flow to which the first user plane entity data protocol unit belongs and the DRB transmitting the data protocol unit is changed, if so, updating the mapping relation between the QoS flow and the DRB;
operation 5: and detecting whether the mapping relation between the data packet and the QoS flow acquired from the first user plane entity data protocol unit is changed, and if so, updating the mapping relation between the data packet and the QoS flow.
4. The method of claim 1, wherein the determining the mapping relationship between QoS flows and DRBs comprises:
determining a mapping relation between the QoS flow and the DRB according to the DRB mapped by the QoS ID contained in the first user plane entity control protocol data unit; or,
and determining the mapping relation between the QoS flow and the DRB according to the QoS ID contained in the first user plane entity control protocol data unit and the DRB which receives the first user plane entity control protocol data unit.
5. The method of claim 3, wherein the step of,
when the first user plane entity control protocol data unit only contains control information 1 or only contains control information 2, or contains control information 1 and control information 2 at the same time, the user equipment executes the operation 1, the operation 2 and the operation 3; or,
when the first user plane entity control protocol data unit only contains control information 3 or contains control information 1 and control information 3, the user equipment executes the operation 1 and the operation 3; or,
when the first user plane entity control protocol data unit only contains control information 4, or contains control information 1 and control information 4, the user equipment executes the operation 1 and the operation 2; or,
when the first user plane entity control protocol data unit only contains 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 user equipment executes the operation 1, the operation 2 and the operation 3 on the DRB indicated in the control information 5; or,
When the first user plane entity control protocol data unit contains control information 3 and control information 5, or contains control information 1, control information 3 and control information 5, the user equipment executes the operation 1 and the operation 3 on the DRB indicated in the control information 5; or,
when the first user plane entity control protocol data unit contains control information 4 and control information 5, or contains control information 1, control information 4 and control information 5, the user equipment executes the operation 1 and the operation 2 on the DRB indicated in the control information 5; or,
when the first user plane entity control protocol data unit only contains 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 user equipment performs the operation 2 and the operation 3 according to the first user plane entity control protocol data unit, or performs the operation 1 according to the first user plane entity data protocol data unit received from a base station, and the operation 2 and the operation 3;
or,
when the first user plane entity control protocol data unit contains control information 3 and control information 6, or contains control information 1, control information 3 and control information 6, the user equipment only executes the operation 1 and the operation 3 on the DRB mapped by the QoS ID indicated in the control information 6; or,
When the first user plane entity control protocol data unit contains control information 4 and control information 6, or contains control information 1, control information 4 and control information 6, the user equipment executes the operation 2 according to the first user plane entity control protocol data unit, or executes the operation 1 and the operation 2 according to the first user plane entity data protocol data unit received from a base station;
or,
the first user plane entity controls the control protocol data unit to include control information 7, or include control information 1 and control information 6, or include control information 2 or control information 6, or include control information 4 and control information 6, or include control information 1, control information 2 and control information 6, or include control information 1, control information 4 and control information 6, and the user equipment performs the operation 4 and the operation 5.
6. The method of claim 5 wherein when performing the operations 1, 2 and 3 according to the first user plane entity data protocol data unit, the user equipment performs the operations 1, 2 and 3 on DRBs to which QoS IDs indicated in control information 6 are mapped.
7. The method of claim 5, when performing operation 2 according to the first user plane entity data protocol data unit, the user equipment performs the operations 1 and 2 on DRBs mapped with QoS IDs indicated in control information 6.
8. The method of claim 1 wherein the first user plane entity acknowledgement control protocol unit contains a QoS ID.
9. The method of claim 1, wherein the ACL is sent on a DRB that receives the first user plane entity data protocol data unit,
or on a default DRB and,
or sending the message on any DRB corresponding to the first user plane entity.
10. The method of claim 1, wherein after the ue performs the reflective QoS operation according to the first ue control protocol data unit, the method further comprises:
the user equipment receives a second control protocol data unit from a first user plane entity of the base station, wherein the second control protocol data unit comprises an indication of stopping executing the reflective QoS operation.
11. The method of claim 1, further comprising,
The user equipment receives a first user plane entity data protocol data unit of the base station, and the first user plane entity data protocol data unit packet head contains an indication of whether a QoS ID exists or not.
12. A data mapping apparatus comprising:
the receiving module is used for receiving a first user plane entity control protocol data unit from a base station, wherein the first user plane entity is positioned on an access layer data packet convergence protocol;
an execution module, configured to execute a reflective QoS operation according to the first user plane entity control protocol data unit;
wherein the first user plane entity control protocol data unit includes: control information 4: an indication to start or stop AS Reflective QoS;
wherein the reflective QoS operation includes: operation 1: determining whether to initiate reflective QoS detection for the first user plane entity data protocol data unit, and operation 2: determining a mapping relation between QoS flow and DRB;
wherein the apparatus further comprises: and the acknowledgement sending module is used for sending the first user plane entity acknowledgement control protocol unit to the base station.
13. The apparatus of claim 12, wherein the first user plane entity control protocol data unit further comprises at least one of the following control information:
Control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop NAS Reflective QoS;
control information 5: DRB ID;
control information 6: qoS ID;
control information 7: and updating the indication and QoS ID of the mapping relation between QoS flow and DRB.
14. The apparatus of claim 12, wherein the means for performing, by the user equipment, a reflective QoS operation according to the first user plane entity control protocol data unit, the reflective QoS operation further comprising at least one of:
operation 3: determining the mapping relation between the data packet and the QoS flow;
operation 4: detecting whether the mapping relation between the QoS flow to which the first user plane entity data protocol unit belongs and the DRB transmitting the data protocol unit is changed, if so, updating the mapping relation between the QoS flow and the DRB;
operation 5: and detecting whether the mapping relation between the data packet and the QoS flow acquired from the first user plane entity data protocol unit is changed, and if so, updating the mapping relation between the data packet and the QoS flow.
15. The apparatus of claim 12, wherein the first user plane entity acknowledgement control protocol unit includes a QoS ID.
16. The apparatus of claim 12, wherein the acknowledgement control protocol unit is sent on a DRB that received the first user plane entity data protocol data unit, or on a default DRB, or on any DRB corresponding to the first user plane entity.
17. The apparatus of claim 12, wherein the receiving module is further configured to: and receiving a second control protocol data unit from the first user plane entity of the base station.
18. The apparatus of claim 12, wherein the means for performing is further configured to stop performing the reflective QoS operation based on a second control protocol data unit.
19. An apparatus operable in wireless communication, comprising:
a processor configured to receive a first user plane entity control protocol data unit from a base station, wherein the first user plane entity is located above an access layer packet convergence protocol;
executing reflective QoS operation according to the first user plane entity control protocol data unit;
A memory coupled with the processor;
wherein the first user plane entity control protocol data unit includes: control information 4: an indication to start or stop access layer Reflective QoS;
wherein the reflective QoS operation includes: operation 1: determining whether to initiate reflective QoS detection for the first user plane entity data protocol data unit, and operation 2: determining a mapping relation between QoS flow and DRB;
the processor is further configured to send a first user plane entity acknowledgement control protocol unit to the base station.
20. The apparatus of claim 19, wherein the device comprises a plurality of sensors,
the processor is further configured to receive a first user plane entity second control protocol data unit from the base station.
21. The apparatus of claim 19, wherein the device comprises a plurality of sensors,
the processor is further configured to stop executing the reflective QoS operation according to the second control protocol data unit of the first user plane entity.
22. A computer storage medium comprising a computer readable medium, comprising:
a receiving code for receiving a first user plane entity control protocol data unit from a base station;
an operation code for executing a reflective QoS operation according to the first user plane entity control protocol data unit;
Wherein the first user plane entity control protocol data unit includes: control information 4: an indication to start or stop access layer Reflective QoS;
wherein the reflective QoS operation includes: operation 1: determining whether to initiate reflective QoS detection for the first user plane entity data protocol data unit, and operation 2: determining a mapping relation between QoS flow and DRB;
the operation code is further configured to send a first user plane entity acknowledgement control protocol unit to the base station.
23. A method, comprising:
transmitting a first user plane entity control protocol data unit, wherein the first user plane entity control protocol data unit is used for indicating a receiving end to execute a reflective QoS operation;
receiving a first user plane entity acknowledgement control protocol unit;
wherein the first user plane entity is located above an access layer packet convergence protocol;
wherein the first user plane entity control protocol data unit includes control information 4: an indication to start or stop access layer Reflective QoS;
wherein the reflective QoS operation includes: operation 1: determining whether to initiate reflective QoS detection for the first user plane entity data protocol data unit, and operation 2: and determining the mapping relation between the QoS flow and the DRB.
24. The method of claim 23 further comprising sending a first user plane entity a second control protocol data unit, the second control protocol data unit being configured to instruct the receiving end to stop performing the reflective QoS operation.
25. The method of claim 23, the first user plane entity control protocol data unit comprising at least one of the following control information:
control information 1: a control protocol data unit type indication;
control information 2: an indication to start or stop Reflective QoS;
control information 3: an indication to start or stop non-access stratum Reflective QoS;
control information 5: a data radio bearer identification, DRB ID;
control information 6: quality of service identification QoS ID;
control information 7: the mapping relation between the QoS flow and the data radio bearer DRB updates the indication and the QoS ID.
26. The method of claim 23, the first user plane entity acknowledgement control protocol unit includes a QoS ID.
27. The method of claim 23, further comprising transmitting a first user plane entity data protocol data unit, the first user plane entity data protocol data unit header including an indication of whether a QoS ID is present.
28. A wireless communications apparatus, comprising:
a sending module, configured to send a first user plane entity control protocol data unit, where the first user plane entity control protocol data unit is configured to instruct a receiving end to execute a reflective QoS operation;
and a receiving module: the method comprises the steps of receiving a first user plane entity acknowledgement control protocol unit;
wherein the first user plane entity is located above an access layer packet convergence protocol;
wherein the first user plane entity control protocol data unit includes control information 4: an indication to start or stop access layer Reflective QoS;
wherein the reflective QoS operation includes: operation 1: determining whether to initiate reflective QoS detection for the first user plane entity data protocol data unit, and operation 2: and determining the mapping relation between the QoS flow and the DRB.
29. An apparatus operable in wireless communication, comprising:
the processor is configured to send a first user plane entity control protocol data unit, where the first user plane entity control protocol data unit is configured to instruct a receiving end to execute a reflective QoS operation; receiving a first user plane entity acknowledgement control protocol unit;
a memory coupled with the processor;
Wherein the first user plane entity is located above an access layer packet convergence protocol;
wherein the first user plane entity control protocol data unit includes control information 4: an indication to start or stop access layer Reflective QoS;
wherein the reflective QoS operation includes: operation 1: determining whether to initiate reflective QoS detection for the first user plane entity data protocol data unit, and operation 2: and determining the mapping relation between the QoS flow and the DRB.
30. A computer storage medium comprising a computer readable medium, comprising:
a transmitting code, configured to transmit a first user plane entity control protocol data unit, where the first user plane entity control protocol data unit is configured to instruct a receiving end to execute a reflective QoS operation;
a receiving code, configured to receive a first user plane entity acknowledgement control protocol unit;
wherein the first user plane entity is located above an access layer packet convergence protocol;
wherein the first user plane entity control protocol data unit includes control information 4: an indication to start or stop access layer Reflective QoS;
wherein the reflective QoS operation includes: operation 1: determining whether to initiate reflective QoS detection for the first user plane entity data protocol data unit, and operation 2: and determining the mapping relation between the QoS flow and the DRB.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710064249.2A CN108366397B (en) | 2017-01-26 | 2017-01-26 | Data mapping method and device and wireless equipment |
PCT/CN2017/117113 WO2018137443A1 (en) | 2017-01-26 | 2017-12-19 | Data mapping method and device, and wireless apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710064249.2A CN108366397B (en) | 2017-01-26 | 2017-01-26 | Data mapping method and device and wireless equipment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN108366397A CN108366397A (en) | 2018-08-03 |
CN108366397B true CN108366397B (en) | 2024-02-23 |
Family
ID=62979046
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710064249.2A Active CN108366397B (en) | 2017-01-26 | 2017-01-26 | Data mapping method and device and wireless equipment |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN108366397B (en) |
WO (1) | WO2018137443A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111866906B (en) * | 2019-04-29 | 2021-07-23 | 大唐移动通信设备有限公司 | Data transmission method and device |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101064664A (en) * | 2006-04-30 | 2007-10-31 | 中兴通讯股份有限公司 | Method for mapping and guaranteeing quality of service of high-speed downlink packet accessing system |
CN102231894A (en) * | 2011-07-20 | 2011-11-02 | 电信科学技术研究院 | Method and device for transmitting parameters required for QoS (quality of service) verification |
CN102612095A (en) * | 2012-03-05 | 2012-07-25 | 电信科学技术研究院 | Transmission method and equipment of IP data packet |
CN103959884A (en) * | 2011-10-31 | 2014-07-30 | 亚马逊技术股份有限公司 | Prioritizing application data for transmission in a wireless user devices |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101005440A (en) * | 2006-01-21 | 2007-07-25 | 华为技术有限公司 | Metod for realizing different service quality control in radio network |
CN103118401B (en) * | 2009-06-19 | 2015-09-30 | 华为技术有限公司 | Service bearing mapping method and communication equipment |
CN101932102B (en) * | 2009-06-19 | 2013-01-23 | 华为技术有限公司 | Service bearing mapping method and communication equipment thereof |
CN103716881B (en) * | 2012-10-08 | 2018-08-14 | 华为技术有限公司 | It eats dishes without rice or wine information processing system, method and apparatus |
-
2017
- 2017-01-26 CN CN201710064249.2A patent/CN108366397B/en active Active
- 2017-12-19 WO PCT/CN2017/117113 patent/WO2018137443A1/en active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101064664A (en) * | 2006-04-30 | 2007-10-31 | 中兴通讯股份有限公司 | Method for mapping and guaranteeing quality of service of high-speed downlink packet accessing system |
CN102231894A (en) * | 2011-07-20 | 2011-11-02 | 电信科学技术研究院 | Method and device for transmitting parameters required for QoS (quality of service) verification |
CN103959884A (en) * | 2011-10-31 | 2014-07-30 | 亚马逊技术股份有限公司 | Prioritizing application data for transmission in a wireless user devices |
CN102612095A (en) * | 2012-03-05 | 2012-07-25 | 电信科学技术研究院 | Transmission method and equipment of IP data packet |
Also Published As
Publication number | Publication date |
---|---|
WO2018137443A1 (en) | 2018-08-02 |
CN108366397A (en) | 2018-08-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111052790B (en) | Enhancement processing of a quality of service flow description | |
CN115175257B (en) | Default service quality rule management method and user equipment | |
CN110831075B (en) | Data transmission method and device, service switching method and device | |
US11240699B2 (en) | Insufficient resources in the UE during PDU session establishment procedure | |
CN107040398B (en) | Data transmission method, device and system | |
AU2019272364C1 (en) | Communication method and communications apparatus | |
EP3048845A1 (en) | Device and method for data transmission | |
TWI719836B (en) | Methods and user equipment for handling of eps bearer | |
EP3378249B1 (en) | Method and apparatus for reducing signaling overhead and reducing battery of terminal | |
WO2018121096A1 (en) | Flow control method, device, cu, du and storage medium | |
TWI664864B (en) | Device and method for handling a new radio connection in inter-system mobility | |
TWI710270B (en) | Methods and user equipments for enhanced handling on qos operations | |
CN106954280B (en) | Data transmission method, device and system | |
CN108156633A (en) | Data flow remaps method and device and user equipment, RAN equipment | |
CN109429366B (en) | PDU session processing method and device | |
US20190045575A1 (en) | A method, apparatus, and system for data transmission | |
EP3755056A1 (en) | Communication method, device and system, and storage medium | |
CN107295564A (en) | A kind of load bearing management method based on stream, data transmission method and device | |
CN112106402B (en) | QoS rule management method and user equipment | |
CN111937438B (en) | Method and apparatus for terminating cellular network connection of unauthenticated terminal | |
CN108366397B (en) | Data mapping method and device and wireless equipment | |
CN112913322A (en) | Terminal device, base station device, and method | |
WO2023276986A1 (en) | Master node, communication device, and communication control method | |
WO2020164614A1 (en) | Assistance information and method and apparatus for delivering same | |
GB2624512A (en) | Methods and apparatus for handling AI/ML data |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |