WO2018028061A1 - 用户面数据的映射方法、装置、系统及存储介质 - Google Patents

用户面数据的映射方法、装置、系统及存储介质 Download PDF

Info

Publication number
WO2018028061A1
WO2018028061A1 PCT/CN2016/104761 CN2016104761W WO2018028061A1 WO 2018028061 A1 WO2018028061 A1 WO 2018028061A1 CN 2016104761 W CN2016104761 W CN 2016104761W WO 2018028061 A1 WO2018028061 A1 WO 2018028061A1
Authority
WO
WIPO (PCT)
Prior art keywords
user plane
entity
network element
data packet
layer entity
Prior art date
Application number
PCT/CN2016/104761
Other languages
English (en)
French (fr)
Inventor
何青春
黄河
施小娟
李楠
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP16912515.0A priority Critical patent/EP3499922B1/en
Publication of WO2018028061A1 publication Critical patent/WO2018028061A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • the present invention relates to the field of communications, and in particular to a method, an apparatus, a system, and a storage medium for mapping user plane data.
  • the 5G system will use all possible networks, so in terms of mobile communication technology itself, the 5G system is not a single system using only one wireless access technology, but can be used including existing wireless connections.
  • Incorporating technology and newly designed wireless access technology convergence systems such as the use of Long Term Evaluation (LTE) access technology in 4G, enhanced long term evolution after 4G further evolution (enhanced Long Term Evolution, Referred to as eLTE) technology, wireless local area network (Wireless Local Area Network, WLAN for short), newly designed wireless access technology in 5G, radio access network (Radio Access Network)
  • the RAN (referred to as the access network) is connected to the unified core network in a flexible and pluggable manner.
  • the 5G system needs to decouple the core network (Core Network, CN for short) and the access network, that is, the core network and the access network can evolve independently, not because of the enhancement of one side network or The change causes the other side network to need to make synchronization enhancements or changes.
  • the design of the core network in the 5G system needs to be non-aware of different radio access networks.
  • QoS Quality of Service
  • EPS bearer the minimum granularity of QoS management in LTE is EPS bearer.
  • a PDN connection corresponds to a default EPS bearer.
  • dedicated bearers can be built in addition to EPS bearers.
  • EPS bearer In order to provide services with different QoS guarantees for UEs with the same IP address (PDN connection), dedicated bearers can be built in addition to EPS bearers. EPS bearer.
  • the mapping process between the service flow and the EPS bearer is as follows: After the EPSF/PCEF of the core network generates the EPS bearer level QoS according to the QoS policy, if the EPS bearer is not established, the MME initiates the establishment of the EPS bearer, and when the core network establishes the EPS bearer, Notifying the eNB of the QoS parameters of each E-RAB (ie, a bearer of the EPS bearer on the E-URTAN side), the eNB correspondingly establishes an RB between the UE and the UE on the air interface, wherein the eNB according to the received E-RAB granularity QoS
  • the parameter determines the parameter setting of the corresponding RB, and the eNB and the UE perform data scheduling transmission according to the determined RB parameter setting, and ensure QoS of the RB level on the air interface.
  • the core network and the access network are coupled together to carry out QoS processing for carrying out the QoS processing, which obviously does not meet the goal of decoupling design of the core network and the access network of the future 5G system.
  • the more companies are proposing new QoS architectures, such as per flow-based QoS architectures.
  • new QoS architectures such as per flow-based QoS architectures.
  • the concept of RB and logical channel is retained on the access network side. Therefore, the access network needs to obtain QoS parameters by other means.
  • the access network In order for the access network to determine the parameters for establishing the RB and/or the LCH, and to consider how the access network is mapped to the corresponding user plane lower layer entity and/or RB and/ after receiving the service flow of the core network. Or on the LCH, so that the access network protocol stack performs different priority scheduling processing on different service flows.
  • the embodiment of the invention provides a method, a device, a system and a storage medium for mapping user plane data, so as to at least solve the problem that the data packet is mapped between the user plane high and low layer entities in the 5G system architecture in the related art.
  • a method for mapping user plane data including:
  • the user plane high-level entity of the first network element receives the data packet that is sent by the second network element and carries the specified identifier.
  • the specified identifier is set by the second network element.
  • the user plane high layer entity maps the data packet to at least one of the following according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the method further includes:
  • the first network element establishes a mapping relationship with the radio bearer RB and/or the logical channel LCH according to the specified identifier of the data packet, and stores the mapping relationship in the mapping table;
  • the user plane high layer entity maps the data packet to at least one of the following according to the mapping table: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the first network element detects that the RB corresponding to the specified identifier is not established. In the case that the first network element establishes an RB corresponding to the specified identifier, and The mapping relationship between the specified identifier and the RB is recorded as a mapping relationship, and the mapping relationship is stored in the mapping table.
  • the user plane high layer entity of the first network element performs data transmission with the second network element by using one of the following protocols:
  • GTP-U tunneling protocol network protocol IP protocol
  • IP-Sec tunneling protocol IP-Sec tunneling protocol
  • the specified identifier comprises one of the following:
  • QoS identification ID QoS identification ID
  • priority indicator PRI IP differential service code point DSCP.
  • the user plane high level entity comprises one of the following:
  • the user plane lower layer entity includes one of the following:
  • the user plane lower layer entity includes at least one of the following: a PDCP entity, an RLC entity, and a MAC entity;
  • the user plane lower layer entity includes a user plane entity other than the first user plane entity in the L2 protocol stack, where The first user plane entity is one of the following: a PDCP entity, an RLC entity, and a MAC entity.
  • the user plane high layer entity maps the data packet to at least one of the following according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH, including :
  • the user plane high layer entity After the user plane high layer entity receives the data packet, storing the data packet in a cache buffer;
  • the user plane upper layer entity After receiving the transmission indication of the user plane lower layer entity, the user plane upper layer entity maps the data packet to at least one of: a user plane low layer entity of the first network element,
  • the line carries the RB, the logical channel LCH, where the transmission indication is used to indicate that the user plane lower layer entity and the user plane upper layer entity have transmission opportunities.
  • a method for mapping user plane data which includes:
  • the user plane high layer entity maps the data packet to at least one of the following: the user plane lower layer entity of the first network element, the radio bearer RB, and the logical channel LCH.
  • the second network element performs data transmission with a user-level high-level entity of the first network element by using one of the following protocols:
  • GTP-U tunneling protocol network protocol IP protocol
  • IP-Sec tunneling protocol IP-Sec tunneling protocol
  • the specified identifier comprises one of the following:
  • QoS identification ID QoS identification ID
  • priority indicator PRI IP differential service code point DSCP.
  • a mapping system for user plane data including: a first network element, a second network element, where the first network element includes: a user plane Entity, user plane low-level entity;
  • the user plane high-level entity of the first network element receives the data packet that is sent by the second network element and carries the specified identifier
  • the user plane high layer entity maps the data packet to at least one of the following according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the system further includes:
  • the first network element establishes a mapping relationship with the radio bearer RB and/or the logical channel LCH according to the specified identifier of the data packet, and stores the mapping relationship in the mapping table;
  • the user plane high layer entity maps the data packet to at least one of the following according to the mapping table: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the user plane high layer entity of the first network element performs data transmission with the second network element by using one of the following protocols:
  • GTP-U tunneling protocol network protocol IP protocol
  • IP-Sec tunneling protocol IP-Sec tunneling protocol
  • the specified identifier comprises one of the following:
  • QoS identification ID QoS identification ID
  • priority indicator PRI IP differential service code point DSCP.
  • the user plane high level entity comprises one of the following:
  • the user plane lower layer entity includes one of the following:
  • the user plane lower layer entity includes at least one of the following: a PDCP entity, an RLC entity, and a MAC entity;
  • the user plane lower layer entity includes a user plane entity other than the first user plane entity in the L2 protocol stack, where The first user plane entity is one of the following: a PDCP entity, an RLC entity, and a MAC entity.
  • the user plane high layer entity maps the data packet to at least one of the following according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH, including :
  • the user plane high layer entity After the user plane high layer entity receives the data packet, storing the data packet in a cache buffer;
  • the user plane lower layer entity sends a transmission indication to the user plane upper layer entity, where the transmission indication is used to indicate that the user plane lower layer entity and the user plane upper layer entity have transmission opportunity;
  • the user plane high layer entity maps the data packet to at least one of the following: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • a mapping device for user plane data is further provided, which is applied to a first network element, and includes:
  • the receiving module is configured to receive, by the user plane high-level entity of the first network element, a data packet that is sent by the second network element and carries the specified identifier;
  • the mapping module is configured to map the data packet to at least one of the following by the user plane high layer entity according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the receiving module is further configured to: after the user plane high-level entity of the first network element receives the data packet sent by the second network element, establish a radio bearer RB and/or according to the specified identifier of the data packet. Mapping relationship of the logical channel LCH, and storing the mapping relationship in the mapping table;
  • the receiving module is further configured to map the data packet to at least one of the following by the user plane upper layer entity according to the mapping table: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH .
  • the user plane high layer entity of the first network element performs data transmission with the second network element by using one of the following protocols:
  • GTP-U tunneling protocol network protocol IP protocol
  • IP-Sec tunneling protocol IP-Sec tunneling protocol
  • the specified identifier comprises one of the following:
  • QoS identification ID QoS identification ID
  • priority indicator PRI IP differential service code point DSCP.
  • the user plane high level entity comprises one of the following:
  • the user plane lower layer entity includes one of the following:
  • the user plane lower layer entity includes at least one of the following: a PDCP entity, an RLC entity, and a MAC entity;
  • the user plane lower layer entity includes a user plane entity other than the first user plane entity in the L2 protocol stack, where The first user plane entity is one of the following: a PDCP entity, an RLC entity, and a MAC entity.
  • mapping module is further configured to: after the user plane high layer entity receives the data packet, store the data packet in a cache buffer;
  • the mapping module is further configured to: after receiving the transmission indication of the user plane lower layer entity, mapping, by the user plane upper layer entity, the data packet to at least one of: a lower layer of the user plane of the first network element Entity, radio bearer RB, logical channel LCH; wherein the transmission indication is used to indicate that the user plane lower layer entity and the user plane upper layer entity have transmission opportunities.
  • a mapping device for user plane data is provided, which is applied to a second network element, and includes:
  • a sending module configured to send a data packet to a user plane high-level entity of the first network element, where the data packet carries a specified identifier set by the second network element, where the user plane high-level entity is configured according to the
  • the designation identifier maps the data packet to at least one of the following: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the second network element performs data transmission with a user-level high-level entity of the first network element by using one of the following protocols:
  • GTP-U tunneling protocol network protocol IP protocol
  • IP-Sec tunneling protocol IP-Sec tunneling protocol
  • the specified identifier comprises one of the following:
  • QoS identification ID QoS identification ID
  • priority indicator PRI IP differential service code point DSCP.
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • the user plane high-level entity of the first network element receives the data packet that is sent by the second network element and carries the specified identifier
  • the user plane high layer entity maps the data packet to at least one of the following according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the second network element sends a data packet to the user plane high-level entity of the first network element, where the data packet carries a specified identifier set by the second network element, where the user plane high-level entity is configured according to the specified
  • the identifier maps the data packet to at least one of: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the embodiment of the present invention further provides a method for mapping user plane data, including: a user plane high layer entity of a third network element obtains a QoS identifier ID for identifying a QoS characteristic parameter from a non-access stratum entity;
  • the user plane high layer entity matches the QoS ID with a pre-stored mapping rule
  • the data packet is encapsulated and delivered to the matching user plane lower layer entity, and/or DRB, and/or LCH;
  • the packet is encapsulated and passed to the default user plane lower layer entity, and/or DRB, and/or LCH.
  • the method before the user plane high layer entity of the third network element obtains the QoS identifier ID from the non-access stratum entity, the method further includes:
  • the non-access stratum entity determines, according to the data packet filter or data service filter, a pre-stored QoS policy parameter, a QoS characteristic parameter corresponding to the data packet, including:
  • the third network element receives and saves a QoS policy parameter set
  • the non-access stratum entity matches the packet filter or data traffic filter with each QoS policy parameter in the QoS policy parameter set to obtain a QoS policy parameter applied to the data packet.
  • the user plane high layer entity carries the QoS ID when encapsulating the data packet.
  • the embodiment of the present invention further provides a mapping device for user plane data, which is applied to a third network element, and includes a matching module: the matching module is configured to obtain a QoS identifier ID for identifying a QoS characteristic parameter, and the QoS ID is used. Matches the pre-stored mapping rules.
  • the matching module is configured to obtain a QoS identifier ID for identifying a QoS characteristic parameter, and the QoS ID is used. Matches the pre-stored mapping rules.
  • the matching is successful, the data packet is encapsulated and passed to the matching user plane lower layer entity, and/or DRB, and/or LCH.
  • the matching is unsuccessful, the data packet is encapsulated and transmitted to Default user plane lower layer entity, and/or DRB, and/or LCH.
  • the apparatus further includes: a parsing module and a determining module;
  • the parsing module is configured to receive the data packet, and obtain a data packet filter or a data service filter from the data packet;
  • the determining module is configured to determine a QoS characteristic parameter corresponding to the data packet based on the data packet filter or data service filter, a pre-stored QoS policy parameter, and use the identifier to identify the QoS characteristic parameter
  • the QoS identification ID is passed to the matching module.
  • the determining module is configured to receive and save a QoS policy parameter set, and match the data packet filter or the data service filter with each QoS policy parameter in the QoS policy parameter set to obtain The QoS policy parameters applied to the packet.
  • the matching module carries the QoS ID when the data packet is encapsulated.
  • the embodiment of the present invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used in the mapping method of the user plane data according to the embodiment of the present invention.
  • the data packet when the second network element sends a data packet to the first network element, the data packet carries a user plane low layer entity corresponding to the data packet, or a radio bearer, or a designated identifier of the logical channel.
  • the high-level entity of the user plane completes the mapping of the data packet according to the specified identifier, and solves the problem that the data packet is mapped between the upper and lower layers of the user plane in the 5G system architecture in the related art, and the user plane is implemented in the 5G system. And mapping data packets to lower layer entities and/or RBs and/or LCHs.
  • FIG. 1 is a flowchart of a method for mapping user plane data according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of two protocol stack architectures of a network element 1 in accordance with a preferred implementation of the present invention
  • FIG. 3 is a schematic diagram of a mapping process of a data packet in a network element according to a preferred embodiment of the present invention
  • FIG. 4 is a schematic diagram of establishing a new data radio bearer in accordance with a preferred embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a format of a data packet according to a preferred embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a method 1 for mapping a data packet in a network element 1 according to a preferred embodiment of the present invention
  • FIG. 7 is a schematic diagram of a method 2 for mapping a data packet in a network element 1 according to a preferred embodiment of the present invention.
  • FIG. 8 is a flowchart of a method for processing a user plane data processing method according to Embodiment 1 of the present invention.
  • FIG. 9 is a mapping diagram of user plane data applied to a first network element according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of establishing a data radio bearer between a first network element and a third network element according to an embodiment of the present invention
  • FIG. 11 is a schematic diagram of a process of performing data packet mapping by a third network element according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram of a device for mapping user plane data applied to a third network element according to an embodiment of the present invention.
  • the embodiment described in this application file can be run in a new 5G system.
  • the first network element is a device in the access network
  • the second network element is a device in the core network.
  • FIG. 1 is a flowchart of a method for mapping user plane data according to an embodiment of the present invention. As shown in Figure 1, the process includes the following steps:
  • the user plane high-level entity of the first network element receives the data packet that is sent by the second network element and carries the specified identifier.
  • the specified identifier is set by the second network element.
  • the user plane high layer entity maps the data packet to at least one of the following: the user plane lower layer entity of the first network element, the radio bearer RB, and the logical channel LCH.
  • the problem of mapping data packets between the user plane high and low layer entities in the 5G system architecture is solved in the related art, and in the 5G system, the user plane upper layer and the data packet are mapped to the lower layer entity and/or Or RB and / or LCH.
  • the first network element after the user plane high layer entity of the first network element receives the data packet sent by the second network element, the first network element establishes a radio bearer RB and/or a logical channel LCH according to the specified identifier of the data packet. Mapping the relationship, and storing the mapping relationship in the mapping mapping table; the user plane high-level entity maps the data packet to at least one of the following according to the mapping table: a user plane lower layer entity of the first network element, and a radio bearer RB, Logical channel LCH. It should be noted that there is a one-to-one correspondence between the radio bearer and the logical channel and the user plane bottom layer entity.
  • the user plane high layer entity of the first network element performs data transmission with the second network element by one of the following protocols: a GTP-U tunneling protocol; a network protocol IP protocol; and an IP-Sec tunneling protocol.
  • the specified identifier comprises one of: a QoS identification ID; a priority indicator PRI; a differential service code point DSCP of the IP.
  • the user plane high layer entity comprises one of: an independent entity above the L2 protocol stack user plane entity; and a user plane entity in the L2 protocol stack.
  • the user plane lower layer entity includes one of the following:
  • the user plane lower layer entity includes at least one of the following: a PDCP entity, an RLC entity, and a MAC entity;
  • the user plane lower layer entity includes a user plane entity other than the first user plane entity in the L2 protocol stack, where the first The user plane entity is one of the following: a PDCP entity, an RLC entity, and a MAC entity.
  • the user plane high layer entity maps the data packet to at least one of the following: the user plane lower layer entity of the first network element, the radio bearer RB, and the logical channel LCH, including:
  • the data packet is stored in the cache buffer
  • the user plane upper layer entity After receiving the transmission indication of the user plane lower layer entity, the user plane upper layer entity maps the data packet to at least one of: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH;
  • the transmission indication is used to indicate that the user plane low layer entity has a transmission opportunity with the user plane high layer entity.
  • a method for mapping user plane data which includes:
  • the second network element sends a data packet to the user plane high-level entity of the first network element, where the data packet carries a specified identifier set by the second network element, where the user plane high-level entity sends the data according to the specified identifier.
  • the packet is mapped to at least one of the following: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the second network element performs data transmission with the user plane high layer entity of the first network element by one of the following protocols: a GTP-U tunneling protocol; a network protocol IP protocol; and an IP-Sec tunneling protocol.
  • the specified identifier comprises one of: a QoS identification ID; a priority indicator PRI; a differential service code point DSCP of the IP.
  • a user plane high layer entity obtains a data packet from a preconfigured data channel, and maps the data packet to a user plane lower layer entity and/or RB and/or LCH according to a pre-configured mapping rule.
  • An optional embodiment of the present invention provides a method for mapping user plane data, including a user plane high layer entity of the network element 1 acquiring a data packet from a preconfigured data channel, and mapping the data packet according to a pre-configured mapping rule.
  • the user plane of the network element 1 is on the lower layer entity and/or on the RB and/or LCH.
  • the network element 1 in the present embodiment is equivalent to the first network element in the foregoing embodiment
  • the network element 2 is equivalent to the second network element in the foregoing embodiment
  • the identifier 1 is equivalent to the foregoing implementation.
  • the data channel is configured to transmit data between the user plane high layer entity of the network element 1 and the network element 2, and can be implemented according to one of the following protocols: GTP-U tunneling protocol, IP protocol, and IP-Sec tunneling protocol.
  • the network element 2 adds "identity 1" in front of the data packet and then sends the data packet to the network element 1.
  • the mapping rule is a mapping table that is saved locally when the network element 1 establishes the RB and/or the LCH, and the mapping table is maintained by the user plane high layer entity.
  • the user plane upper layer entity is an independent entity above the L2 user plane entity, or an enhanced entity of the LTE protocol stack L2 entity (ie, the PDCP entity or the RLC entity or the MAC entity).
  • the user plane high layer entity maps the data packet to one and/or multiple user plane lower layer entities and/or RBs and/or LCHs according to the mapping rule.
  • the user plane high layer entity includes, but is not limited to, a function of mapping data packets from the data channel to one and/or multiple user plane lower layer entities and/or RBs and/or LCHs.
  • the user plane high layer entity maps the data packet to the user plane lower layer entity and/or RB and/or LCH once the data packet is obtained from the preconfigured data channel.
  • the user plane upper layer entity receives the data packet in the pre-configured data channel and places it in the buffer buffer, and maps the data packet to the user plane lower layer entity and/or RB and/or LCH when there is a transmission opportunity at the lower layer. .
  • the user plane low layer entity is relative to the user plane high layer entity, and is a protocol layer in the 5G-NR L2 protocol stack except the user plane high layer entity in this document.
  • a possible L2 protocol stack reconstruction design idea in the 5G era is to use the function of "non-high processing time requirement" in the RLC layer and PDCP.
  • Layer functions are combined into one protocol sub-layer implementation, and for the "high processing time requirement" function in the RLC layer, depending on different requirements, it may be considered to merge the functions of the MAC layer into a protocol sub-layer, or continue to be retained.
  • a separate protocol sublayer implements these functions.
  • L2 is described as two protocol sub-layers, namely user-level high-level entity L2-high (abbreviated as L2-H) and user-surface low-level entity L2-Low (abbreviated as L2-L). ).
  • L2-H user-level high-level entity L2-high
  • L2-L user-surface low-level entity
  • the L2-H is a new functional entity independent of the PDCP layer in the LTE technology, and the L2-H maps the data packet in the pre-configured data channel to the user plane lower layer entity L2-L according to the mapping rule.
  • L2-L includes, but is not limited to, the functions of the PDCP, RLC, and MAC layers in the LTE technology, wherein the PDCP/RLC/MAC layer in the L2-L can be re-divided according to the 5G design concept of the L2 protocol stack.
  • L2 is described as two protocol sub-layers, namely user-level high-level entity L2-high (abbreviated as L2-H) and user-surface low-level entity L2-Low (abbreviated as L2-L). ).
  • the L2-H includes, but is not limited to, the PDCP layer in the LTE technology, and has a data packet mapping function, and maps the data packets in the pre-configured data channel to the user plane lower layer entity L2-L according to the mapping rule, and the layer L2-L. Mapping of H packets to RBs and/or LCHs.
  • L2-L includes, but is not limited to, the functions of the RLC and MAC layers in LTE technology.
  • the division mode of L2 in FIG. 2 is only used to help explain the mapping function of the user plane high-level entity data, and does not limit the specific division scheme of L2.
  • FIG. 3 is a schematic diagram of a mapping process of data packets in a network element according to a preferred embodiment of the present invention.
  • the network element 2 is a core network of the 5G-NR, and includes some or all functional entities of the LTE core network (eg, a mobility management entity MME, a policy control entity PCRF/PCEF, a packet data gateway P-GW, and a serving gateway S-GW).
  • the functional entities are defined as two parts: the user plane and the control plane.
  • the data packet is marked with "identity 1" in the network element 2 and then sent to the user plane high-level entity L2-H in the network element 1, and the structure of the data packet labeled "identity 1" is as shown in FIG.
  • the user plane high-layer entity L2-H in the network element 1 After receiving the data packet of the network element 2, the user plane high-layer entity L2-H in the network element 1 performs data according to a pre-configured mapping rule.
  • the packet is mapped to the user plane lower layer entity and/or RB and/or LCH.
  • the mapping rule is a mapping table that is stored locally when the network element 1 establishes the RB and/or the LCH when the network element 1 receives the QoS policy of the network element 2.
  • the mapping table reflects the "identification 1" and The mapping relationship between RBs and/or LCHs, Table 1 is a mapping table in accordance with a preferred embodiment of the present invention, as shown in Table 1.
  • the user plane higher layer entity L2-H maps the data packet to the user plane lower layer entity (L2-L) and/or RB and/or LCH according to "identity 1" in the data packet.
  • the user plane data mapping method of the present invention is applied to the L2-H sublayers of FIGS. 2 and 3, and the data packets in the preconfigured data channel are mapped to the user plane lower layer entity and/or RB and/or LCH.
  • FIG. 4 is a schematic diagram of establishing a new data radio bearer according to a preferred embodiment of the present invention.
  • the control function entity of the network element 2 generates a QoS policy policy according to the data service type and sends the QoS policy policy to the control module in the network element 1.
  • the network element 1 After receiving the QoS policy, the network element 1 first checks whether there is a data radio bearer that satisfies the QoS parameter on the network element 1 side. If not, the control module of the network element 1 establishes a new data radio bearer according to the QoS policy, and simultaneously sets the data.
  • the mapping rules of the package are saved in the mapping table.
  • FIG. 5 is a schematic diagram of a format of a data packet according to a preferred embodiment of the present invention.
  • the data packet first passes through a network element 2, and the network element 2 is added before the data packet before the data packet is sent to the network element 1.
  • "Identity 1" is either a QoS ID, or a PRI (Priority Indicator), or directly uses the DSCP in the IP header.
  • the user plane higher layer entity L2-H in the network element 1 maps the data packet to the user plane lower layer entity (L2-L) and/or RB and/or LCH according to the "identity 1".
  • FIG. 6 is a schematic diagram of a method 1 for mapping a data packet in a network element 1 according to a preferred embodiment of the present invention.
  • the user plane high-layer entity L2-H of the network element 1 selects the user plane lower layer entity (L2-L) and/or RB that satisfies the QoS parameter according to the pre-configured mapping rule. And / or LCH mapping.
  • the data channel is used to transfer data between the user plane high layer entity of the network element 1 and the network element 2, and can be implemented according to one of the following protocols: GTP-U tunnel Road protocol, IP protocol, IP-Sec tunneling protocol.
  • the mapping rule is a mapping table that is stored locally when the network element 1 establishes the RB and/or the LCH when the network element 1 receives the QoS policy of the network element 2.
  • the mapping table reflects the "identification 1" and
  • the mapping relationship between RB and/or LCH is shown in Table 1.
  • the data packet in the user plane upper layer entity L2-H is from the network element 2, and the network element 2 is "identified 1" in the header of the data packet, and the "identity 1" is either a QoS ID or a PRI (Priority Indicator). ), or directly use the DSCP inside the IP header.
  • the structure of the data packet is shown in Figure 5.
  • the user plane high layer entity is an independent entity above the LTE PDCP, or is a function enhancement part of the PDCP entity in the LTE, and is used to map the data packet marked with "identity 1" from the network element 2 to the user plane satisfying the QoS parameter.
  • FIG. 7 is a schematic diagram of a second method for mapping data packets in a network element 1 according to a preferred embodiment of the present invention.
  • FIG. 7 is another data mapping method different from FIG. 6.
  • the user plane high-level entity L2-H of the network element 1 obtains the data packet on the pre-configured data channel, it is placed in the buffer buffer, and waits for the user plane low-level entity L2.
  • -L transmission opportunity when the user plane high layer entity L2-H receives the transmission opportunity notification of the user plane low layer entity L2-L, the user plane high layer entity L2-H maps the data packet to meet the QoS parameter according to the preconfigured mapping rule.
  • User plane low layer entities (L2-L) and / or RB and / or LCH User plane low layer entities (L2-L) and / or RB and / or LCH.
  • Table 1 is a mapping rule mapping table stored locally when the QoS policy of the network element 2 is received by the network element 1 when the network element 1 receives the QoS policy of the network element 2, which reflects the "identity 1" and the RB and / or LCH mapping relationship, "Identity 1" and RB ID / LCID are represented by simple numbers, and this is only a better description of the mapping relationship between them, QCI, GBR, MBR in the mapping table and ARP is optional, and the options describe the specific parameters of QoS, as shown in Table 1.
  • the user plane data mapping method proposed in Embodiment 1 is applied to a new QoS architecture in the 5G-NR, and the user plane high layer entity of the network element 1 acquires a data packet from a preconfigured data channel, and the data is obtained according to a pre-configured mapping rule.
  • the packet is mapped to the user plane lower layer entity (L2-L) and/or RB and/or LCH of network element 1.
  • FIG. 8 is a flowchart of a method for processing a user plane data according to a specific embodiment of the present invention. The detailed flow of the method for processing the user plane data by each part of the network element 1 and the network element 2 is shown.
  • Step 1 The network element 2 generates a QoS policy parameter according to the service type, and sends the QoS policy parameter to the network element 1.
  • the QoS policy is configured to add, delete, and reconfigure QoS IDs and their corresponding QoS parameters.
  • the QoS parameter includes the QCI, the GBR, the MBR, the ARP, and the corresponding QoS ID, and is dynamically configured by the network element 2 to the network element 1.
  • the QoS ID is in one-to-one correspondence with a certain QoS parameter of the service flow, and the QoS ID index in the data packet can determine the QoS requirement that needs to be provided for the data packet, that is, the data is determined by the QoS ID.
  • the packet is mapped to a radio bearer and/or user plane lower layer entity (L2-L) and/or RB and/or LCH that meet the QoS parameters requirements.
  • the control module of the network element 1 After receiving the QoS policy policy, the control module of the network element 1 first checks whether there is a data radio bearer DRB that satisfies the QoS parameter, and if not, establishes a new data radio bearer DRB.
  • the network element 1 saves the mapping rule in the local mapping table when establishing the RB and/or the LCH, and the mapping table reflects the mapping relationship between the "identity 1" and the RB and/or the LCH and its QoS parameters, such as Table 1 shows.
  • the "identity 1" is either a QoS ID or a PRI (Priority Indicator), or directly uses the DSCP in the IP header.
  • the mapping table is maintained by the user plane high layer entity, and the user plane high layer entity updates the mapping relationship according to the control plane signaling of the network element 1.
  • the user plane high layer entity L2-H maps the data packet to the user plane lower layer entity (L2-L) and/or RB and/or LCH according to the mapping rule in the mapping table.
  • the user plane high layer entity L2-H is an independent entity above the PDCP layer in the LTE technology, or is a function enhancement part of the PDCP layer entity in the LTE technology, and is configured to put the data packet of the "identity 1" from the network element 2 Map to user plane lower layer entities (L2-L) and/or RBs and/or LCHs that meet QoS and priority requirements.
  • the user plane high layer entity functions include, but are not limited to, mapping data packets to user plane lower layer entities (L2-L) and/or RBs and/or LCHs according to pre-configured mapping rules.
  • the network element 1 is a 5G-NR access network, and includes L2 and L1 two-part protocol contents.
  • L2 is divided into L2-high (abbreviated as L2-H) and L2-Low (abbreviated as L2).
  • L2-H L2-high
  • L2-Low abbreviated as L2
  • -L Two sublayers. A description of the two sublayers is shown in Figure 2.
  • the network element 2 is a core network of the 5G-NR, and includes some or all functional entities of the LTE core network (eg, a mobility management entity MME, a policy control entity PCRF/PCEF, a packet data gateway P-GW, a service gateway S-GW, etc.) Functional entity), defined as two parts of the user plane and the control plane.
  • a mobility management entity MME e.g., a mobility management entity MME, a policy control entity PCRF/PCEF, a packet data gateway P-GW, a service gateway S-GW, etc.
  • Functional entity eg, a packet data gateway P-GW, a service gateway S-GW, etc.
  • step 2 the network element 2 sends the data packet marked with "identity 1" to the user plane high-level entity of the network element 1.
  • the "identity 1" is either a QoS ID or a PRI (Priority Indicator), or directly uses the DSCP in the IP header.
  • the user plane higher layer entity determines by which index of "identity 1" the data packet is sent to which user plane lower layer entity (L2-L) and/or RB and/or LCH.
  • mapping relationship between the "identity 1" and its corresponding QoS parameters and RB and/or LCH is stored in the mapping table, as shown in Table 1.
  • the user plane high layer entity parses the received data packet, obtains "identity 1" in the data packet, and maps the data packet to the user plane low layer entity (L2-L) that satisfies the QoS parameter according to the mapping rule in the mapping table. And / or RB and / or LCH.
  • the mapping rule is the mapping relationship between the "identity 1" and the RB and/or the LCH.
  • the user plane high-level entity searches for the mapping table according to the "identity 1”, finds the RB and/or LCH corresponding to the "identity 1", and then carries The data packet with the "identity 1" is mapped to the corresponding RB and/or LCH.
  • the user plane high layer entity maps the data packet to the user plane lower layer entity (L2-L) and/or RB and/or LCH.
  • the user plane high layer entity maps the data packet to the user plane lower layer entity and/or RB and/or LCH once the data packet is obtained from the preconfigured data channel.
  • the user plane upper layer entity receives the data packet in the pre-configured data channel and places it in the buffer buffer, and maps the data packet to the user plane lower layer entity and/or RB and/or LCH when there is a transmission opportunity at the lower layer. .
  • the user plane lower layer entity is relative to the user plane high layer entity, and is a protocol layer in the 5G-NR L2 protocol stack except the user plane high layer entity in this document.
  • the service data flow in the pre-configured data channel is mapped to the user plane lower layer entity and/or the RB and/or the LCH under the new QoS architecture.
  • Table 2 is a list of technical terms according to an embodiment of the present invention, as shown in Table 2, Please refer to the full name in English and Chinese for the technical terms mentioned in the document.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of various embodiments of the present invention.
  • FIG. 9 is a structural block diagram of a device for mapping user plane data applied to a first network element according to an embodiment of the present invention. As shown in FIG. 9, the apparatus includes:
  • the receiving module 92 is configured to receive, by the user plane high-level entity of the first network element, a data packet that is sent by the second network element and carries the specified identifier;
  • the mapping module 94 is connected to the receiving module 92, and configured to map the data packet to at least one of the following by the user plane high layer entity according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the receiving module 92 is further configured to: after the user plane high-level entity of the first network element receives the data packet sent by the second network element, establish a radio bearer RB and/or logic according to the specified identifier of the data packet. a mapping relationship of the channel LCH, and storing the mapping relationship in the mapping table;
  • the receiving module 92 is further configured to map the data packet to at least one of the following by the user plane high layer entity according to the mapping table: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the user plane high layer entity of the first network element performs data transmission with the second network element by using one of the following protocols:
  • GTP-U tunneling protocol network protocol IP protocol
  • IP-Sec tunneling protocol IP-Sec tunneling protocol
  • the specified identifier comprises one of the following:
  • QoS identification ID QoS identification ID
  • priority indicator PRI IP differential service code point DSCP.
  • the user plane high level entity comprises one of the following:
  • the user plane lower layer entity includes one of the following:
  • the user plane lower layer entity includes at least one of the following: a PDCP entity, an RLC entity, and a MAC entity;
  • the user plane lower layer entity includes a user plane entity other than the first user plane entity in the L2 protocol stack, where the first The user plane entity is one of the following: a PDCP entity, an RLC entity, and a MAC entity.
  • mapping module 94 is further configured to store the data packet in the cache buffer after the user plane high layer entity receives the data packet;
  • the mapping module 94 is further configured to: after receiving the transmission indication of the user plane lower layer entity, the data packet is mapped to the at least one of the following by the user plane upper layer entity: the user plane lower layer entity of the first network element, the radio bearer RB, a logical channel LCH; wherein the transmission indication is used to indicate that the user plane lower layer entity has a transmission opportunity with the user plane upper layer entity.
  • a mapping device for user plane data is provided, which is applied to a second network element, and includes:
  • a sending module configured to send a data packet to a user plane high-level entity of the first network element, where the data packet carries a specified identifier set by the second network element, where the user plane high-level entity And mapping the data packet to at least one of the following: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the second network element performs data transmission with a user-level high-level entity of the first network element by one of the following protocols:
  • GTP-U tunneling protocol network protocol IP protocol
  • IP-Sec tunneling protocol IP-Sec tunneling protocol
  • the specified identifier comprises one of the following:
  • QoS identification ID QoS identification ID
  • priority indicator PRI IP differential service code point DSCP.
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • the user plane high-level entity of the first network element receives the data packet that is sent by the second network element and carries the specified identifier
  • the user plane high layer entity maps the data packet to at least one of the following according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the second network element sends a data packet to the user plane high-level entity of the first network element, where the data packet carries a specified identifier set by the second network element, where the user plane high-level entity sends the data according to the specified identifier.
  • the packet is mapped to at least one of the following: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • a mapping system for user plane data including: a first network element, a second network element, where the first network element includes: a user plane high layer entity , the user's low-level entity;
  • the user plane high-level entity of the first network element receives the data packet that is sent by the second network element and carries the specified identifier
  • the user plane high layer entity maps the data packet to at least one of the following according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the system further includes:
  • the first network element establishes a mapping relationship with the radio bearer RB and/or the logical channel LCH according to the specified identifier of the data packet, and stores the mapping relationship in the mapping table;
  • the user plane high layer entity maps the data packet to at least one of the following according to the mapping table: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the user plane high layer entity of the first network element performs data transmission with the second network element by using one of the following protocols:
  • GTP-U tunneling protocol network protocol IP protocol
  • IP-Sec tunneling protocol IP-Sec tunneling protocol
  • the specified identifier comprises one of the following:
  • QoS identification ID QoS identification ID
  • priority indicator PRI IP differential service code point DSCP.
  • the user plane high level entity comprises one of the following:
  • the user plane lower layer entity includes one of the following:
  • the user plane lower layer entity includes at least one of the following: a PDCP entity, an RLC entity, and a MAC entity;
  • the user plane lower layer entity includes a user plane entity other than the first user plane entity in the L2 protocol stack, where the first The user plane entity is one of the following: a PDCP entity, an RLC entity, and a MAC entity.
  • the user plane high layer entity maps the data packet to at least one of the following: the user plane lower layer entity of the first network element, the radio bearer RB, and the logical channel LCH, including:
  • the data packet is stored in the cache buffer
  • the user plane lower layer entity sends a transmission indication to the user plane upper layer entity, where the transmission indication is used to indicate that the user plane lower layer entity has a transmission opportunity with the user plane upper layer entity;
  • the user plane high layer entity maps the data packet to at least one of the following: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the user plane high-level entity of the first network element receives the data packet that is sent by the second network element and carries the specified identifier.
  • the user plane high layer entity maps the data packet to at least one of the following: the user plane lower layer entity of the first network element, the radio bearer RB, and the logical channel LCH.
  • the storage medium is further configured to store program code for performing the following steps:
  • the second network element sends, to the user plane high-level entity of the first network element, a data packet carrying the specified identifier.
  • the user plane high layer entity maps the data packet to at least one of the following according to the specified identifier: a user plane lower layer entity of the first network element, a radio bearer RB, and a logical channel LCH.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • the processor performs the method steps in the foregoing embodiments according to the stored program code in the storage medium.
  • the first network element is a device in the access network, such as a base station device.
  • the present invention also provides a third network element, which is a terminal device that operates in a new 5G system, and the third network element can communicate with the first network element through the air interface, or can be transmitted through the first network element. After communicating with the second network element.
  • the third network element can be various user equipments, such as mobile phones, computers, tablet devices, and the like.
  • the third network element communicates with the first network element through the air interface, and serves as a communication peer end of the first network element on the wireless interface.
  • the two protocol stack architecture diagrams shown in FIG. 2 are also applicable to the third network element, the third network.
  • the element adopts a protocol stack structure corresponding to the first network element.
  • the control function entity of the second network element generates a QoS policy according to the data service type; the second network element sends the generated QoS policy parameter to the third network element;
  • the QoS policy parameter of the three network elements includes: a QoS characteristic parameter and a priority of the QoS characteristic parameter; preferably, the QoS policy parameter may further include: a packet filter/data service using the QoS characteristic parameter a QoS characteristic parameter includes a QoS ID for identifying or indicating the QoS characteristic parameter, and the QoS characteristic parameter may further include: MBR, GBR, Priority level, Packet Delay Budget (PDB) Any one or more of a packet error rate (PER) and an admission control.
  • PDB Packet Delay Budget
  • the second network element sends the generated QoS policy parameter to the first network element, where the information is sent to the first network element.
  • the QoS policy parameter of a network element may include All the parameters sent to and from the third network element may also include only the QoS characteristic parameters.
  • the control plane of the first network element triggers the establishment of the data radio bearer.
  • the mapping rules of the data packets are saved in the mapping table.
  • the mapping rule of the specifically saved data packet may be a mapping manner between the QoS ID and the user plane lower layer entity and/or the DRB and/or the LCH. Then, the first network element notifies the third network element to establish the established data.
  • Radio bearer and notifying the mapping rule of the data packet to the third network element, where the notification may be only a mapping rule of the data packet used for uplink transmission; after receiving the third network element, establishing a data radio bearer, and The mapping rule of the data notified by the first network element is saved.
  • the QoS policy parameter sent by the second network element to the third network element includes a default QoS policy parameter, and the value of the QoS ID used to identify or mark the QoS characteristic parameter in the default QoS policy parameter is different.
  • the first network element establishes a data radio bearer after receiving the QoS policy parameter from the second network element, and the first network element does not necessarily establish a data radio bearer for all received QoS characteristic parameters, that is, the first The QoS characteristic parameters received by a network element from the second network element are not necessarily mapped to the data radio bearer. Therefore, the mapping rules of the foregoing data packet do not necessarily include all the first network elements from the second network.
  • the first network element establishes a data radio bearer after receiving the QoS policy parameter from the second network element, and the established data radio bearer includes at least: a default DRB, a user plane lower layer entity used by the Default DRB, and/or a corresponding LCH. The difference is called the default user plane low layer entity / Default LCH.
  • FIG. 11 is a schematic diagram of a third network element performing a data packet mapping process according to a preferred embodiment of the present invention.
  • the non-access stratum entity of the third network element is a protocol entity located above the user plane high-level entity of the third network element, and the non-access stratum entity can implement end-to-end communication with the second network element.
  • the QoS policy parameter set received by the third network element from the second network element is received and saved by the non-access stratum entity of the third network element.
  • the non-access stratum entity of the third network element After the non-access stratum entity of the third network element receives the data packet from the upper layer, such as the application layer, the non-access stratum entity of the third network element parses the data packet, and obtains data packet filtering in the data packet. a data/filter of data traffic, and then the non-access stratum entity of the third network element compares the acquired packet filter/data traffic filter with the saved set of QoS policy parameters received from the first network element The QoS policy parameter is matched. After the matching is successful, the non-access stratum of the third network element determines the QoS characteristic parameter that should be used by the data packet, and then the non-access stratum of the third network element is used to identify or mark the QoS policy.
  • the QoS ID of the QoS characteristic parameter is sent to the user plane high layer entity (L2-H) of the third network element; after the user plane high layer entity receives the QoS ID from the non-access stratum, the QoS ID is used to match and save in the third
  • the mapping rule of the data packet in the network element such as the mapping relationship between the QoS ID and the user plane lower layer entity and/or the DRB and/or the LCH, if it matches the corresponding user plane lower layer entity and/or DRB and/or LCH, then
  • the user plane high level entity will Passing the packet to the matched user plane lower layer entity, and/or DRB, and/or LCH, and the user plane high layer entity, when the packet is generated to generate a PDU, the QoS ID Put in the PDU.
  • the user plane high layer entity will use the data.
  • the packet is passed to a default user plane lower layer entity and/or a default DRB and/or a default LCH, and the user plane upper layer entity puts the QoS ID into the PDU when grouping the data packet into a PDU. in.
  • the user plane high-level entity of the first network element It is determined that the default user plane lower layer entity and/or the default DRB and/or the default LCH receive the PDU whose QoS ID is not the default QoS ID, and the user plane upper layer entity may establish the DRB for the QoS characteristic parameter identified or indicated by the QoS ID. Or mapping the QoS characteristic parameters identified or indicated by the QoS ID to the established non-default DRB.
  • a device for mapping user plane data is applied to a third network element, and a schematic structural diagram of the mapping device, as shown in FIG. 12, includes: a matching module 30;
  • the matching module 30 is configured to obtain a QoS identifier ID for identifying a QoS characteristic parameter, and the QoS ID is matched with a pre-stored mapping rule.
  • the matching is successful, the data packet is encapsulated and then transmitted to the matched one.
  • the device further includes a parsing module 10 and a determining module 20;
  • the parsing module 10 is configured to receive the data packet, and obtain a data packet filter or a data service filter from the data packet;
  • the determining module 20 is configured to determine a QoS characteristic parameter corresponding to the data packet based on the data packet filter or a data service filter, a pre-stored QoS policy parameter, and use the identifier to identify the QoS characteristic
  • the QoS identification ID of the parameter is passed to the matching module.
  • the determining module 20 is configured to receive and save a QoS policy parameter set, and match the data packet filter or the data service filter with each QoS policy parameter in the QoS policy parameter set to obtain an application.
  • the QoS policy parameters of the data packet are configured to receive and save a QoS policy parameter set, and match the data packet filter or the data service filter with each QoS policy parameter in the QoS policy parameter set to obtain an application.
  • the QoS policy parameters of the data packet is configured to receive and save a QoS policy parameter set, and match the data packet filter or the data service filter with each QoS policy parameter in the QoS policy parameter set to obtain an application.
  • the matching module 30 when the matching module 30 encapsulates the data packet, the QoS ID is carried.
  • the receiving module and the mapping module in the mapping device of the user plane data proposed in the embodiment of the present invention can all be implemented by a processor, and can also be implemented by a specific logic circuit.
  • the processor can be a processor on a network element. In practical applications, The processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA).
  • mapping method of the user plane data described above is implemented in the form of a software function module, and is sold or used as an independent product, it may also be stored in a computer readable storage medium.
  • the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • program codes such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores a computer program for performing the mapping method of the user plane data according to the embodiment of the present invention.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.

Abstract

本发明提供了一种用户面数据的映射方法、装置、系统及存储介质，其中，该方法包括：第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。采用上述技术方案，解决了相关技术中在5G系统架构下，缺乏用户面高低层实体之间映射数据包的问题，实现了在5G系统中，用户面高层与将数据包映射到低层实体和/或RB和/或LCH。

Description

用户面数据的映射方法、装置、系统及存储介质 技术领域
本发明涉及通信领域，具体而言，涉及一种用户面数据的映射方法、装置、系统及存储介质。
背景技术
在过去的几十年间，移动通信网络经历了持续的发展，从2G、3G一直发展到4G，在此过程中新型通信设备，比如智能终端，手持式平板电脑等不断涌现，而新型通信设备的出现又催生了大量新型应用、新型通信场景的产生，从而使得下一代/5G移动通信系统，将从目前以人为中心的通信发展到既包括人际间通信也包括物体间通信的万物互联系统。
为实现万物互联，5G系统将使用一切有可能使用的网络，因此就移动通信技术本身而言，5G系统不是单一的仅使用一种无线接入技术的系统，而是可以使用包括现有无线接入技术以及新设计的无线接入技术的融合系统，比如融合使用4G中的长期演进(Long Term Evaluation，简称为LTE)接入技术，4G进一步演进之后的增强型长期演进(enhanced Long Term Evolution，简称为eLTE)技术，无线本地局域网相关技术(Wireless Local Area Network，简称为WLAN)，5G中新设计的无线接入技术，采用这些不同无线接入技术的无线接入网(Radio Access Network，简称为RAN)(简称接入网)以灵活可插拔的方式接入到统一的核心网中。
为确保网络的可扩展性，5G系统需要去耦合设计核心网(Core Network，简称为CN)和接入网，也即核心网和接入网可以独立演进，不会因为一侧网络的增强或改变而导致另一侧网络需要做出同步增强或改变，换句话说，5G系统中核心网的设计需要做到对不同的无线接入网无感知。
无论是支持人际间通信还是支持物体间通信，不同的应用服务、不同的应用场景都对通信过程中的服务质量(Quality of Service，简称为QoS)有相应的要求，保证一致的QoS是5G系统中需要考虑的一个重要因素。
目前LTE中QoS管理的最小粒度是EPS bearer，一个PDN连接对应一个default EPS bearer，为了给具有相同IP地址(PDN连接)的UE提供具有不同QoS保障的业务，在EPS bearer之外还可以建dedicated EPS bearer。业务流与EPS bearer之间的映射过程为：核心网的PCRF/PCEF根据QoS policy生成EPS bearer level QoS后，如果没有建立EPS bearer，MME会发起EPS bearer的建立，核心网建立EPS bearer时，会通知eNB每个E-RAB(即EPS bearer在E-URTAN侧的一段承载)的QoS参数，eNB对应在空中接口上建立和UE之间的RB，其中eNB根据收到的E-RAB粒度的QoS参数，确定对应RB的参数设置，eNB和UE根据所确定的RB参数设置，进行数据调度传输，保证空中接口上RB级别的QoS。
3GPP系统中这种核心网和接入网耦合在一起的以承载为粒度执行QoS处理进行传输的方法，显然不满足未来5G系统核心网和接入网去耦合设计的目标，为此，越来越多的公司关提出新的QoS架构，如基于per flow的QoS架构。针对per flow的QoS架构，由于在接入网与核心网之间没有RAB的概念，但在接入网侧继续保留RB和逻辑信道的概念，因此，接入网需要通过其他方式来获取QoS参数，以便接入网确定建立RB和/或LCH的参数，以及需要考虑接入网接在收到核心网的业务流后，如何将数据流映射到相应的用户面低层实体和/或RB和/或LCH上，以便接入网协议栈对不同的业务流进行不同的优先级调度处理。
因此，为了实现5G-NR新的QoS架构，需要对L2协议架构进行重新设计，对L2协议功能进行重新分配以及对L2功能进行增强。其中一种可能的设计思路为，将RLC层中“非高处理时间要求”的功能与PDCP层的 功能合并到一个协议子层实现，而对于RLC层中“高处理时间要求”的功能，根据不同的需求，可以考虑将其与MAC层的功能合并到一个协议子层实现，或者继续保留一个单独的协议子层实现这些功能。目前，业界只是提出了以上设计理念，尚未有针对新的QoS架构下数据包的具体映射方案的提出。
针对相关技术中在5G系统架构下，缺乏用户面高低层设备之间映射数据包的问题，目前还没有有效的解决方案。
发明内容
本发明实施例提供了一种用户面数据的映射方法、装置、系统及存储介质，以至少解决相关技术中在5G系统架构下，缺乏用户面高低层实体之间映射数据包的问题。
根据本发明的一个实施例，提供了一种用户面数据的映射方法，包括：
第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包，在一实施例中，所述指定标识由第二网元设置；
所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，第一网元的用户面高层实体接收第二网元发送的数据包之后，所述方法还包括：
所述第一网元根据所述数据包的指定标识建立与无线承载RB和/或逻辑信道LCH的映射关系，并将所述映射关系存储在mapping表中；
所述用户面高层实体依据所述mapping表将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包之后，在所述第一网元检测到未建立与所述指定标识对应的RB的情况下，所述第一网元建立与所述指定标识对应的RB，并将 所述指定标识与所述RB的对应关系记为映射关系，将所述映射关系存储于所述mapping表中。
在一实施例中，所述第一网元的用户面高层实体通过以下协议之一与第二网元进行数据传输：
GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，所述指定标识包括以下之一：
QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
在一实施例中，所述用户面高层实体包括以下之一：
L2协议栈用户面实体之上的独立实体；
L2协议栈中的用户面实体。
在一实施例中，所述用户面低层实体，包括以下之一：
在所述用户面高层实体为L2协议栈用户面实体之上的独立实体的情况下，所述用户面低层实体包括以下至少之一：PDCP实体，RLC实体，MAC实体；
在所述用户面高层实体为L2协议栈中的第一用户面实体的情况下，所述用户面低层实体包括L2协议栈中除所述第一用户面实体之外的用户面实体，其中，所述第一用户面实体为以下之一：PDCP实体，RLC实体，MAC实体。
在一实施例中，所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH，包括：
在所述用户面高层实体接收到所述数据包之后，将所述数据包存储于缓存buffer中；
在接收到所述用户面低层实体的传输指示之后，所述用户面高层实体将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无 线承载RB，逻辑信道LCH；其中，所述传输指示用于指示所述用户面低层实体与所述用户面高层实体存在传输机会。
根据本发明的另一个实施例，还提供了一种用户面数据的映射方法，其特征在于，包括：
第二网元向第一网元的用户面高层实体发送数据包，其中，所述数据包携带有由所述第二网元设置的指定标识；
其中，所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，所述第二网元通过以下协议之一与第一网元的用户面高层实体进行数据传输：
GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，所述指定标识包括以下之一：
QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
根据本发明的另一个实施例，还提供了一种用户面数据的映射系统，其特征在于，包括：第一网元，第二网元，其中，所述第一网元包括：用户面高层实体，用户面低层实体；
第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，第一网元的用户面高层实体接收第二网元发送的数据包之后，所述系统还包括：
所述第一网元根据所述数据包的指定标识建立与无线承载RB和/或逻辑信道LCH的映射关系，并将所述映射关系存储在mapping表中；
所述用户面高层实体依据所述mapping表将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，所述第一网元的用户面高层实体通过以下协议之一与第二网元进行数据传输：
GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，所述指定标识包括以下之一：
QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
在一实施例中，所述用户面高层实体包括以下之一：
L2协议栈用户面实体之上的独立实体；
L2协议栈中的用户面实体。
在一实施例中，所述用户面低层实体，包括以下之一：
在所述用户面高层实体为L2协议栈用户面实体之上的独立实体的情况下，所述用户面低层实体包括以下至少之一：PDCP实体，RLC实体，MAC实体；
在所述用户面高层实体为L2协议栈中的第一用户面实体的情况下，所述用户面低层实体包括L2协议栈中除所述第一用户面实体之外的用户面实体，其中，所述第一用户面实体为以下之一：PDCP实体，RLC实体，MAC实体。
在一实施例中，所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH，包括：
在所述用户面高层实体接收到所述数据包之后，将所述数据包存储于缓存buffer中；
所述用户面低层实体向所述用户面高层实体发送传输指示，其中，所述传输指示用于指示所述用户面低层实体与所述用户面高层实体存在传输 机会；
所述用户面高层实体将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
根据本发明的另一个实施例，还提供了一种用户面数据的映射装置，应用于第一网元，其特征在于，包括：
接收模块，配置为通过所述第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
映射模块，配置为通过所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，所述接收模块还配置为在第一网元的用户面高层实体接收第二网元发送的数据包之后，根据所述数据包的指定标识建立与无线承载RB和/或逻辑信道LCH的映射关系，并将所述映射关系存储在mapping表中；
所述接收模块还配置为通过所述用户面高层实体依据所述mapping表将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，所述第一网元的用户面高层实体通过以下协议之一与第二网元进行数据传输：
GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，所述指定标识包括以下之一：
QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
在一实施例中，所述用户面高层实体包括以下之一：
L2协议栈用户面实体之上的独立实体；
L2协议栈中的用户面实体。
在一实施例中，所述用户面低层实体，包括以下之一：
在所述用户面高层实体为L2协议栈用户面实体之上的独立实体的情况下，所述用户面低层实体包括以下至少之一：PDCP实体，RLC实体，MAC实体；
在所述用户面高层实体为L2协议栈中的第一用户面实体的情况下，所述用户面低层实体包括L2协议栈中除所述第一用户面实体之外的用户面实体，其中，所述第一用户面实体为以下之一：PDCP实体，RLC实体，MAC实体。
在一实施例中，所述映射模块还配置为在所述用户面高层实体接收到所述数据包之后，将所述数据包存储于缓存buffer中；
所述映射模块还配置为在接收到所述用户面低层实体的传输指示之后，通过所述用户面高层实体将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH；其中，所述传输指示用于指示所述用户面低层实体与所述用户面高层实体存在传输机会。
根据本发明的另一个实施例，提供了一种用户面数据的映射装置，应用于第二网元，其特征在于，包括：
发送模块，配置为向第一网元的用户面高层实体发送数据包，其中，所述数据包携带有由所述第二网元设置的指定标识；其中，所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，所述第二网元通过以下协议之一与第一网元的用户面高层实体进行数据传输：
GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，所述指定标识包括以下之一：
QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，存储介质还设置为存储用于执行以下步骤的程序代码：
第二网元向第一网元的用户面高层实体发送数据包，其中，所述数据包携带有由所述第二网元设置的指定标识；其中，所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
本发明实施例还提供一种用户面数据的映射方法，包括：第三网元的用户面高层实体获得来自非接入层实体的用于识别QoS特性参数的QoS标识ID；
所述用户面高层实体将所述QoS ID与预先存储的映射规则匹配；
匹配成功时，将数据包封装后传递至匹配得到的用户面低层实体、和/或DRB、和/或LCH；
匹配不成功时，将数据包封装后传递至默认用户面低层实体、和/或DRB、和/或LCH。
在一实施例中，所述第三网元的用户面高层实体获得来自非接入层实体的所述QoS标识ID之前，还包括：
所述非接入层实体接收所述数据包，并从所述数据包中获取数据包过滤器或数据业务过滤器；
所述非接入层实体基于所述数据包过滤器或数据业务过滤器、预先存储的QoS策略参数确定与所述数据包对应的QoS特性参数，将用于识别所 述QoS特性参数的QoS标识ID传递至用户面高层实体。
在一实施例中，所述非接入层实体基于所述数据包过滤器或数据业务过滤器、预先存储的QoS策略参数确定与所述数据包对应的QoS特性参数，包括：
所述第三网元接收并保存QoS策略参数集合；
所述非接入层实体将所述数据包过滤器或数据业务过滤器与所述QoS策略参数集合中的各个QoS策略参数进行匹配，获取应用于所述数据包的QoS策略参数。
在一实施例中，所述用户面高层实体在对所述数据包进行封装时，携带所述QoS ID。
本发明实施例还提供一种用户面数据的映射装置，应用于第三网元，包括匹配模块：所述匹配模块，配置为获得用于识别QoS特性参数的QoS标识ID，将所述QoS ID与预先储的映射规则匹配，在匹配成功时，将数据包封装后传递至匹配得到的用户面低层实体、和/或DRB、和/或LCH；匹配不成功时，将数据包封装后传递至默认用户面低层实体、和/或DRB、和/或LCH。
在一实施例中，所述装置还包括：解析模块和确定模块；
所述解析模块，配置为接收所述数据包，并从所述数据包中获取数据包过滤器或数据业务过滤器；
所述确定模块，配置为基于所述数据包过滤器或数据业务过滤器、预先存储的QoS策略参数确定与所述数据包对应的QoS特性参数，并将所述用于识别所述QoS特性参数的QoS标识ID传递至所述匹配模块。
在一实施例中，所述确定模块，配置为接收并保存QoS策略参数集合，将所述数据包过滤器或数据业务过滤器与所述QoS策略参数集合中的各个QoS策略参数进行匹配，获取应用于所述数据包的QoS策略参数。
在一实施例中，所述匹配模块对所述数据包进行封装时，携带所述QoS ID。
本发明实施例还提供一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，该计算机可执行指令用于本发明实施例的上述用户面数据的映射方法。
通过本发明，在第二网元向第一网元下发数据包时，在数据包内携带有用于指示与该数据包对应的用户面低层实体，或者无线承载，或者逻辑信道的指定标识，用户面高层实体依据该指定标识完成该数据包的映射，解决了相关技术中在5G系统架构下，缺乏用户面高低层实体之间映射数据包的问题，实现了在5G系统中，用户面高层与将数据包映射到低层实体和/或RB和/或LCH。
附图说明
图1是根据本发明实施例提供的一种用户面数据的映射方法流程图；
图2是根据本发明优选实施的网元1的两种协议栈架构的示意图；
图3是根据本发明优选实施例提供的数据包在网元中的映射过程的示意图；
图4为是根据本发明优选实施例的建立新的数据无线承载的示意图；
图5是根据本发明优选实施例的数据包的格式示意图；
图6是根据本发明优选实施例的数据包在网元1中的映射方法一的示意图；
图7是根据本发明优选实施例的数据包在网元1中的映射方法二的示意图；
图8是根据本发明具体实施例1应用于用户面数据处理方法的方法流程图；
图9是根据本发明实施例应用于第一网元的一种用户面数据的映射装 置结构框图；
图10是根据本发明实施例在第一网元和第三网元间建立数据无线承载的示意图；
图11是根据本发明实施例第三网元执行数据包映射的过程示意图；
图12是本发明是实施例应用于第三网元的一种用户面数据的映射装置结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请文件中记载的实施例可以运行在5G新系统中，第一网元是接入网中的设备，第二网元是核心网中的设备，
在本申请文件中的实施例提供一种可以运行于上述系统架构的一种用户面数据的映射方法，图1是根据本发明实施例提供的一种用户面数据的映射方法流程图，如图1所示，该流程包括以下步骤：
S102，第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；在一实施例中，所述指定标识由第二网元设置；
S104，该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
采用上述方法步骤，解决了相关技术中在5G系统架构下，缺乏用户面高低层实体之间映射数据包的问题，实现了在5G系统中，用户面高层与将数据包映射到低层实体和/或RB和/或LCH。
在一实施例中，第一网元的用户面高层实体接收第二网元发送的数据包之后，该第一网元根据该数据包的指定标识建立与无线承载RB和/或逻辑信道LCH的映射关系，并将该映射关系存储在映射mapping表中；该用户面高层实体依据该mapping表将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。需要说明的是，无线承载与逻辑信道和用户面底层实体三者之间，是一一对应的。
在一实施例中，该第一网元的用户面高层实体通过以下协议之一与第二网元进行数据传输：GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，该指定标识包括以下之一：QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
在一实施例中，该用户面高层实体包括以下之一：L2协议栈用户面实体之上的独立实体；L2协议栈中的用户面实体。
在一实施例中，该用户面低层实体，包括以下之一：
在该用户面高层实体为L2协议栈用户面实体之上的独立实体的情况下，该用户面低层实体包括以下至少之一：PDCP实体，RLC实体，MAC实体；
在该用户面高层实体为L2协议栈中的第一用户面实体的情况下，该用户面低层实体包括L2协议栈中除该第一用户面实体之外的用户面实体，其中，该第一用户面实体为以下之一：PDCP实体，RLC实体，MAC实体。
在一实施例中，该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH，包括：
在该用户面高层实体接收到该数据包之后，将该数据包存储于缓存buffer中；
在接收到该用户面低层实体的传输指示之后，该用户面高层实体将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH；其中，该传输指示用于指示该用户面低层实体与该用户面高层实体存在传输机会。
根据本发明的另一个实施例，还提供了一种用户面数据的映射方法，其特征在于，包括：
第二网元向第一网元的用户面高层实体发送数据包，其中，该数据包携带有由该第二网元设置的指定标识；其中，该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，该第二网元通过以下协议之一与第一网元的用户面高层实体进行数据传输：GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，该指定标识包括以下之一：QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
以下结合本发明可选实施例进行详细说明。
本发明可选实施例采用以下技术方案：用户面高层实体从预配置的数据通道中获取数据包，根据预先配置的映射规则将数据包映射到用户面低层实体和/或RB和/或LCH上。
本发明的可选实施例，提供了一种用户面数据的映射方法，包括网元1的用户面高层实体从预配置的数据通道中获取数据包，根据预先配置的映射规则将数据包映射到网元1的用户面低层实体和/或RB和/或LCH上。
在此需要说明的是，本可选实施例中的网元1相当于上述实施例中的第一网元，网元2相当于上述实施例中的第二网元，标识1相当于上述实施例中的指定标识。
该数据通道配置为在网元1的用户面高层实体与网元2间传递数据，可以基于如下协议之一实现：GTP-U隧道协议，IP协议，IP-Sec隧道协议。
该网元2在数据包前添加“标识1”后再将数据包发往该网元1。
需要指出的是，在本申请文件中，该映射规则为该网元1在建立RB和/或LCH的时候所保存在本地的一个mapping表，该mapping表由用户面高层实体维护。
该用户面高层实体或者是L2用户面实体之上的独立实体，或者是对LTE协议栈L2某实体(即PDCP实体或者RLC实体或者MAC实体)的功能增强后的实体。
该用户面高层实体根据该映射规则将数据包映射到一个和/或多个用户面低层实体和/或RB和/或LCH上。
需要补充的是，该用户面高层实体包括但不限于对来自数据通道的数据包映射到一个和/或多个用户面低层实体和/或RB和/或LCH上的功能。
对于用户面高层实体的详细映射步骤，可能包括以下两种情况：
该用户面高层实体一旦从预配置的数据通道中获取到数据包就将数据包映射到用户面低层实体和/或RB和/或LCH。
或者，该用户面高层实体接收到预配置的数据通道中的数据包后放在缓存buffer中，当低层有传输机会的时候才将数据包映射到用户面低层实体和/或RB和/或LCH。
需要补充的是，在本申请文件中，该用户面低层实体是相对于用户面高层实体而言的，为5G-NR L2协议栈中除了本文中该用户面高层实体之外的协议层。
以下结合本发明优选实施例的具体实施方式对本申请文件进行说明。
在相关技术中，根据业界的相关设计理念，5G时代一种可能的L2协议栈重构设计的思路为，将RLC层中“非高处理时间要求”的功能与PDCP 层的功能合并到一个协议子层实现，而对于RLC层中“高处理时间要求”的功能，根据不同的需求，可以考虑将其与MAC层的功能合并到一个协议子层实现，或者继续保留一个单独的协议子层实现这些功能。
图2是根据本发明优选实施的网元1的两种协议栈架构的示意图。在图2-(a)中，将L2描述成两个协议子层，即用户面高层实体L2-high(简记为L2-H)和用户面低层实体L2-Low(简记为L2-L)。其中，L2-H为独立于LTE技术中的PDCP层之上的新的功能实体，L2-H根据映射规则将预配置的数据通道中的数据包映射到用户面低层实体L2-L中。L2-L包括但不限于LTE技术中的PDCP、RLC和MAC层的功能，其中，根据5G对L2协议栈的重构设计思想，可以对L2-L中的PDCP/RLC/MAC层进行再次划分成两个和/或三个子层。在图2-(b)中，将L2描述成两个协议子层，即用户面高层实体L2-high(简记为L2-H)和用户面低层实体L2-Low(简记为L2-L)。其中，L2-H包括但不限于LTE技术中的PDCP层，具有数据包映射功能，根据映射规则将预配置的数据通道中的数据包映射到用户面低层实体L2-L，以及本层L2-H数据包到RB和/或LCH的映射。L2-L包括但不限于LTE技术中的RLC和MAC层的功能。图2中对L2的划分方式仅用于帮助对用户面高层实体数据包映射功能的说明，并不对L2的具体划分方案进行限定。
图3是根据本发明优选实施例提供的数据包在网元中的映射过程的示意图。其中，网元2为5G-NR的核心网，包括部分或全部LTE核心网的功能实体(如：移动管理实体MME，策略控制实体PCRF/PCEF，分组数据网关P-GW，服务网关S-GW等功能实体)，定义成用户面和控制面两大部分。数据包在网元2中打上“标识1”后再发送到网元1中的用户面高层实体L2-H，数据包打上“标识1”后的结构如图5所示。网元1中的用户面高层实体L2-H接收到网元2的数据包后，根据预先配置的映射规则将数据 包映射到用户面低层实体和/或RB和/或LCH上。该映射规则为该网元1收到该网元2的QoS policy时，该网元1建立RB和/或LCH的时候所保存在本地的一个mapping表，该mapping表反映了“标识1”与RB和/或LCH之间的映射关系，表1是根据本发明优选实施例的mapping表，如表1所示。用户面高层实体L2-H根据数据包中的“标识1”将数据包映射到用户面低层实体(L2-L)和/或RB和/或LCH上。
本发明的用户面数据映射方法应用于图2、图3的L2-H子层，对预配置的数据通道中的数据包映射到用户面低层实体和/或RB和/或LCH上。
图4为是根据本发明优选实施例的建立新的数据无线承载的示意图，图4中，网元2的控制功能实体根据数据业务类型生成QoS策略policy并发送给网元1中的控制模块，网元1收到QoS policy后，首先检查网元1侧是否存在满足QoS参数的数据无线承载，如果不存在，则网元1的控制模块根据该QoS policy建立新的数据无线承载，同时将数据包的映射规则保存在mapping表中。
图5是根据本发明优选实施例的数据包的格式示意图，如图5所示，数据包首先经过网元2，该网元2在数据包发往该网元1前，在数据包前添加“标识1”，该“标识1”或者为QoS ID，或者为PRI(优先指示符，Priority Indicator)，或者直接使用IP头里面的DSCP。网元1中的用户面高层实体L2-H根据该“标识1”将数据包映射到用户面低层实体(L2-L)和/或RB和/或LCH上。
图6是根据本发明优选实施例的数据包在网元1中的映射方法一的示意图。网元1的用户面高层实体L2-H一旦获取到预配置的数据通道上的数据包后，就根据预先配置的映射规则选择满足QoS参数的用户面低层实体(L2-L)和/或RB和/或LCH进行映射。该数据通道用于在网元1的用户面高层实体与网元2间传递数据，可以基于如下协议之一实现：GTP-U隧 道协议，IP协议，IP-Sec隧道协议。该映射规则为该网元1收到该网元2的QoS policy时，该网元1建立RB和/或LCH的时候所保存在本地的一个mapping表，该mapping表反映了“标识1”与RB和/或LCH之间的映射关系，如表1所示。该用户面高层实体L2-H中的数据包来自于网元2，由该网元2在数据包的头中“标识1”，该“标识1”或者为QoS ID，或者为PRI(Priority Indicator)，或者直接使用IP头里面的DSCP。数据包的结构如图5所示。该用户面高层实体或者是LTE PDCP之上的独立实体，或者是LTE中PDCP实体的功能增强部分，用于将来自网元2的打上“标识1”的数据包映射到满足QoS参数的用户面低层实体(L2-L)和/或RB和/或LCH上。
图7是根据本发明优选实施例的数据包在网元1中的映射方法二的示意图。图7为区别于图6的另一数据映射方法，网元1的用户面高层实体L2-H获取到预配置的数据通道上的数据包后，放在缓存buffer中，等待用户面低层实体L2-L的传输机会，当用户面高层实体L2-H收到用户面低层实体L2-L的传输机会通知后，用户面高层实体L2-H根据预配置的映射规则将数据包映射到满足QoS参数的用户面低层实体(L2-L)和/或RB和/或LCH上。
表1为本发明提供的在网元1收到网元2的QoS policy时，建立RB和/或LCH的时候所保存在本地的一个映射规则mapping表，其反映了“标识1”与RB和/或LCH之间的映射关系，“标识1”以及RB ID/LCID用了简单的数字表示，再此仅为了更好的说明他们之间的映射关系，mapping表中的QCI、GBR、MBR以及ARP为可选项，可选项描述了QoS的具体参数，如表1所示。
表1
Figure PCTCN2016104761-appb-000001
具体实施例1
具体实施例1提出的用户面数据映射方法应用于5G-NR中新的QoS架构，包括网元1的用户面高层实体从预配置的数据通道中获取数据包，根据预先配置的映射规则将数据包映射到网元1的用户面低层实体(L2-L)和/或RB和/或LCH上。
图8是根据本发明具体实施例1应用于用户面数据处理方法的方法流程图，展示了网元1各个部分和网元2执行该用户面数据处理方法的详细流程。
在具体实施例一中，包括以下步骤：
步骤一，网元2根据业务类型，生成QoS policy参数，并发送给网元1。
该QoS policy配置为添加、删除、重配置QoS ID及其相应的QoS参数。
该QoS参数包括QCI、GBR、MBR、ARP及其对应的QoS ID，由该网元2动态配置给该网元1。
该QoS ID与业务流的某个QoS参数一一对应，通过数据包中的QoS ID索引可以确定需要为数据包提供的QoS要求，也就是说通过QoS ID将数据 包映射到满足QoS参数要求的无线承载和/或用户面低层实体(L2-L)和/或RB和/或LCH上。
该网元1的控制模块收到QoS policy策略后，首先检查是否存在满足QoS参数的数据无线承载DRB，如果没有，则建立新的数据无线承载DRB。该网元1在建立RB和/或LCH的时候将映射规则保存在本地的mapping表中，该mapping表反映了“标识1”与RB和/或LCH之间及其QoS参数的映射关系，如表1所示。
该“标识1”或者为QoS ID，或者为PRI(Priority Indicator)，或者直接使用IP头里面的DSCP。
该mapping表由用户面高层实体维护，该用户面高层实体根据该网元1的控制面信令去更新该的映射关系。
该用户面高层实体L2-H根据mapping表中的映射规则将数据包映射到用户面低层实体(L2-L)和/或RB和/或LCH上。
该用户面高层实体L2-H或者是LTE技术中PDCP层之上的独立实体，或者是LTE技术中PDCP层实体的功能增强部分，配置为将来自网元2的打上“标识1”的数据包映射到满足QoS及优先级要求的用户面低层实体(L2-L)和/或RB和/或LCH上。
该用户面高层实体功能包括但不限于根据预配置的映射规则将数据包映射到用户面低层实体(L2-L)和/或RB和/或LCH上。
该网元1为5G-NR的接入网，包括L2，L1两部分协议内容，为方便表述，对L2划分成L2-high(简记为L2-H)和L2-Low(简记为L2-L)两个子层。对两个子层的描述如图2所示。
该网元2为5G-NR的核心网，包括部分或全部LTE核心网的功能实体(如：移动管理实体MME，策略控制实体PCRF/PCEF，分组数据网关P-GW，服务网关S-GW等功能实体)，定义成用户面和控制面两大部分。
步骤二，网元2将打上“标识1”的数据包发送到网元1的用户面高层实体中。
该“标识1”或者为QoS ID，或者为PRI(Priority Indicator)，或者直接使用IP头里面的DSCP。该用户面高层实体通过“标识1”的索引确定将数据包发送到哪个用户面低层实体(L2-L)和/或RB和/或LCH上。
该“标识1”及其对应的QoS参数与RB和/或LCH的映射关系保存在mapping表里，如表1所示。
该用户面高层实体对收到的数据包进行解析，获取数据包中的“标识1”，根据mapping表中的映射规则，将数据包映射到满足QoS参数的用户面低层实体(L2-L)和/或RB和/或LCH上。
该映射规则就是“标识1”与RB和/或LCH之间映射关系，该用户面高层实体根据“标识1”，查找mapping表，找到“标识1”对应的RB和/或LCH，再将携带有该“标识1”的数据包映射到对应的RB和/或LCH上。
步骤三，用户面高层实体将数据包映射到用户面低层实体(L2-L)和/或RB和/或LCH上。
该用户面高层实体一旦从预配置的数据通道中获取到数据包就将数据包映射到用户面低层实体和/或RB和/或LCH。
或者，该用户面高层实体接收到预配置的数据通道中的数据包后放在缓存buffer中，当低层有传输机会的时候才将数据包映射到用户面低层实体和/或RB和/或LCH。
该用户面低层实体是相对于用户面高层实体而言的，为5G-NR L2协议栈中除了本文中该用户面高层实体之外的协议层。
采用本申请文件中的技术方案，解决在新的QoS架构下，将预配置的数据通道中的业务数据流映射到用户面低层实体和/或RB和/或LCH上。
表2是根据本发明实施例的技术用语一览表，如表2所示，记载了申 请文件中涉及到的技术用语的中英文全称。
表2
Figure PCTCN2016104761-appb-000002
Figure PCTCN2016104761-appb-000003
Figure PCTCN2016104761-appb-000004
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例该的方法。
实施例2
图9是根据本发明实施例应用于第一网元的一种用户面数据的映射装置结构框图，如图9所示，该装置包括：
接收模块92，配置为通过该第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
映射模块94，与接收模块92连接，配置为通过该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，该接收模块92还配置为在第一网元的用户面高层实体接收第二网元发送的数据包之后，根据该数据包的指定标识建立与无线承载RB和/或逻辑信道LCH的映射关系，并将该映射关系存储在mapping表中；
该接收模块92还配置为通过该用户面高层实体依据该mapping表将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，该第一网元的用户面高层实体通过以下协议之一与第二网元进行数据传输：
GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，该指定标识包括以下之一：
QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
在一实施例中，该用户面高层实体包括以下之一：
L2协议栈用户面实体之上的独立实体；
L2协议栈中的用户面实体。
在一实施例中，该用户面低层实体，包括以下之一：
在该用户面高层实体为L2协议栈用户面实体之上的独立实体的情况下，该用户面低层实体包括以下至少之一：PDCP实体，RLC实体，MAC实体；
在该用户面高层实体为L2协议栈中的第一用户面实体的情况下，该用户面低层实体包括L2协议栈中除该第一用户面实体之外的用户面实体，其中，该第一用户面实体为以下之一：PDCP实体，RLC实体，MAC实体。
在一实施例中，该映射模块94还配置为在该用户面高层实体接收到该数据包之后，将该数据包存储于缓存buffer中；
该映射模块94还配置为在接收到该用户面低层实体的传输指示之后，通过该用户面高层实体将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH；其中，该传输指示用于指示该用户面低层实体与该用户面高层实体存在传输机会。
根据本发明的另一个实施例，提供了一种用户面数据的映射装置，应用于第二网元，其特征在于，包括：
发送模块，配置为向第一网元的用户面高层实体发送数据包，其中，该数据包携带有由该第二网元设置的指定标识；其中，该用户面高层实体 依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，该第二网元通过以下协议之一与第一网元的用户面高层实体进行数据传输：
GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，该指定标识包括以下之一：
QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，存储介质还设置为存储用于执行以下步骤的程序代码：
第二网元向第一网元的用户面高层实体发送数据包，其中，该数据包携带有由该第二网元设置的指定标识；其中，该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
根据本发明的另一个实施例，还提供了一种用户面数据的映射系统，其特征在于，包括：第一网元，第二网元，其中，该第一网元包括：用户面高层实体，用户面低层实体；
第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，第一网元的用户面高层实体接收第二网元发送的数据包之后，该系统还包括：
该第一网元根据该数据包的指定标识建立与无线承载RB和/或逻辑信道LCH的映射关系，并将该映射关系存储在mapping表中；
该用户面高层实体依据该mapping表将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，该第一网元的用户面高层实体通过以下协议之一与第二网元进行数据传输：
GTP-U隧道协议；网络协议IP协议；IP-Sec隧道协议。
在一实施例中，该指定标识包括以下之一：
QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
在一实施例中，该用户面高层实体包括以下之一：
L2协议栈用户面实体之上的独立实体；
L2协议栈中的用户面实体。
在一实施例中，该用户面低层实体，包括以下之一：
在该用户面高层实体为L2协议栈用户面实体之上的独立实体的情况下，该用户面低层实体包括以下至少之一：PDCP实体，RLC实体，MAC实体；
在该用户面高层实体为L2协议栈中的第一用户面实体的情况下，该用户面低层实体包括L2协议栈中除该第一用户面实体之外的用户面实体，其中，该第一用户面实体为以下之一：PDCP实体，RLC实体，MAC实体。
在一实施例中，该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH，包括：
在该用户面高层实体接收到该数据包之后，将该数据包存储于缓存buffer中；
该用户面低层实体向该用户面高层实体发送传输指示，其中，该传输指示用于指示该用户面低层实体与该用户面高层实体存在传输机会；
该用户面高层实体将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
实施例4
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
S2，该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
在一实施例中，存储介质还被设置为存储用于执行以下步骤的程序代码：
S3，第二网元向第一网元的用户面高层实体发送携带有指定标识的数据包；
S4，其中，该用户面高层实体依据该指定标识将该数据包映射到以下至少之一：该第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介 质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行上述实施例中方法步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
实施例5
以上实施例中，第一网元是接入网中的设备，比如基站设备。此外，本发明还提出第三网元，第三网元为运行于5G新系统中的终端设备，第三网元可以通过空中接口与第一网元通信，也可以经由第一网元中转传输后与第二网元通信。第三网元可以是各种用户设备，比如手机，电脑，平板设备等等。
第三网元通过空中接口与第一网元通信，作为第一网元在无线接口上的通信对端，图2所示的两种协议栈架构图同样适用于第三网元，第三网元采用与第一网元对应的协议栈架构。
图10是根据本发明优选实施例在第一网元和第三网元上建立数据无线承载的示意图。如图10所示，第二网元的控制功能实体根据数据业务类型生成QoS策略(policy)；第二网元将所生成的QoS policy参数下发给第三网元；其中，下发给第三网元的QoS policy参数包括：QoS特性参数和该QoS特性参数的优先级；优选的，所述QoS policy参数还可以包括：使用该QoS特性参数的数据包过滤器(packet filter)/数据业务过滤器(traffic filter)；其中，QoS特性参数包括用于识别或者标示该QoS特性参数的QoS ID，QoS特性参数还可以包括：MBR、GBR、Priority level、包延迟预算(Packet Delay Budget，PDB)、包错误率(Packet Error rate，PER)和接纳控制(Admission control)中的任意一个或多个；第二网元将所生成的QoS policy参数下发给第一网元，其中下发给第一网元的QoS policy参数可以包括以 上下发给第三网元的所有参数，也可以只包括其中的QoS特性参数；第一网元收到来自第二网元的QoS policy参数后，第一网元的控制面触发建立数据无线承载，同时将数据包的映射规则保存在mapping表中。具体保存的数据包的映射规则，其记录方式可以是QoS ID与用户面低层实体和/或DRB和/或LCH的映射关系；然后，第一网元通知第三网元建立其所建立的数据无线承载，并将所述数据包的映射规则通知给第三网元，这里通知的可以仅仅是用于上行传输的数据包的映射规则；第三网元收到后，建立数据无线承载，并保存所述第一网元通知的数据的映射规则。
图10所述无线承载过程中，存在以下几个特点：
(1)第二网元下发给第三网元的QoS policy参数中，包括默认(default)QoS policy参数，default QoS policy参数中用于识别或者标示QoS特性参数的QoS ID的取值为区别与其他用于识别或标示非默认QoS policy参数的QoS特性参数的QoS ID取值。
(2)第一网元收到来自第二网元的QoS policy参数后建立数据无线承载，第一网元并不一定会为所有的收到的QoS特性参数建立数据无线承载，也即，第一网元从第二网元收到的QoS特性参数并不一定会被映射到数据无线承载上，因此以上所述数据包的映射规则中，并不一定包含所有第一网元从第二网元所接收到的QoS特性参数的QoS ID与用户面低层实体和/或DRB和/或LCH的映射关系；具体为哪些QoS特性参数建立数据无线承载，将哪些QoS特性参数映射到哪些用户面低层实体和/或DRB和/或LCH上，取决于第一网元的决策。
(3)第一网元收到来自第二网元的QoS policy参数后建立数据无线承载，所建立的数据无线承载中至少包括：Default DRB、Default DRB所使用的用户面低层实体和/LCH相应的分别叫做默认用户面低层实体/Default LCH。
第三网元接收到如图10中所述的数据包的映射规则后，当第三网元有数据需要发送给第一网元时，第三网元执行以下数据包的映射过程。如图11是根据本发明优选实施例提供的第三网元执行数据包映射过程的示意图。其中，第三网元的非接入层实体为如图3所示位于第三网元的用户面高层实体之上的协议实体，非接入层实体可以实现端到端与第二网元通信，如图10所示第三网元从第二网元所接收到的QoS policy参数集合由第三网元的非接入层实体接收并保存。当第三网元的非接入层实体接收到来自上层，比如应用层的数据包之后，第三网元的非接入层实体解析所述数据包，获取所述数据包中的数据包过滤器/数据业务过滤器，然后第三网元的非接入层实体将所获取的数据包过滤器/数据业务过滤器与所保存的从第一网元接收到的QoS policy参数集合中的各个QoS policy参数进行匹配，匹配成功后，第三网元的非接入层就确定了该数据包所应该使用的QoS特性参数，然后第三网元的非接入层将用于识别或者标示该QoS特性参数的QoS ID发送给第三网元的用户面高层实体(L2-H)；用户面高层实体接收到来自非接入层的QoS ID之后，用所述QoS ID去匹配保存在第三网元中的数据包的映射规则，比如QoS ID与用户面低层实体和/或DRB和/或LCH的映射关系，若匹配到对应的用户面低层实体和/或DRB和/或LCH，则所述用户面高层实体将所述数据包传递给匹配出来的所述用户面低层实体、和/或DRB、和/或LCH，并且，所述用户面高层实体在对所述数据包进行组包生成PDU时，将所述QoS ID放入所述PDU中。反之，若匹配不到对应的用户面低层实体和/或DRB和/或LCH，也即所述数据包的映射规则中并未找到所述QoS ID，则所述用户面高层实体将所述数据包传递给默认用户面低层实体和/或默认DRB和/或默认LCH，并且，所述用户面高层实体在对所述数据包进行组包生成PDU时，将所述QoS ID放入所述PDU中。由此，当数据包经过空中接口发送给第一网元之后，第一网元的用户面高层实体 判断在默认用户面低层实体和/或默认DRB和/或默认LCH接收到了QoS ID并不是默认QoS ID的PDU，用户面高层实体可以为所述QoS ID所识别或者标示的QoS特性参数建立DRB，或者将所述QoS ID所识别或者标示的QoS特性参数映射到已经建立的非默认DRB上。
实施例6
本发明实施例提供的一种用户面数据的映射装置应用于第三网元，所述映射装置的组成结构示意图，如图12所示，包括：匹配模块30；其中，
所述匹配模块30，配置为将获得用于识别QoS特性参数的QoS标识ID，所述QoS ID与预先储的映射规则匹配，在匹配成功时，将所述数据包封装后传递至匹配得到的用户面低层实体、和/或DRB、和/或LCH；匹配不成功时，将所述数据包封装后传递至默认用户面低层实体、和/或DRB、和/或LCH。
上述方案中，所述装置还包括解析模块10和确定模块20；其中，
所述解析模块10，配置为接收所述数据包，并从所述数据包中获取数据包过滤器或数据业务过滤器；
所述确定模块20，配置为基于所述数据包过滤器或数据业务过滤器、预先存储的QoS策略参数确定与所述数据包对应的QoS特性参数，并将所述用于识别所述QoS特性参数的QoS标识ID传递至所述匹配模块。
上述方案中，所述确定模块20，配置为接收并保存QoS策略参数集合，将所述数据包过滤器或数据业务过滤器与所述QoS策略参数集合中的各个QoS策略参数进行匹配，获取应用于所述数据包的QoS策略参数。
上述方案中，所述匹配模块30对所述数据包进行封装时，携带所述QoS ID。
本发明实施例中提出的用户面数据的映射装置中的接收模块、映射模 块、发送模块、解析模块、确定模块和匹配模块都可以通过处理器来实现，当然也可通过具体的逻辑电路实现；其中所述处理器可以是网元上的处理器，在实际应用中，处理器可以为中央处理器(CPU)、微处理器(MPU)、数字信号处理器(DSP)或现场可编程门阵列(FPGA)等。
本发明实施例中，如果以软件功能模块的形式实现上述用户面数据的映射方法，并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read Only Memory，ROM)、磁碟或者光盘等各种可以存储程序代码的介质。这样，本发明实施例不限制于任何特定的硬件和软件结合。
相应地，本发明实施例还提供一种计算机存储介质，该计算机存储介质中存储有计算机程序，该计算机程序用于执行本发明实施例的上述用户面数据的映方法。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于 本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (38)

  1. 一种用户面数据的映射方法，包括：
    第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
    所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
  2. 根据权利要求1所述的方法，其中，所述指定标识是由所述第二网元设置的标识。
  3. 根据权利要求1所述的方法，其中，第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包之后，所述方法还包括：
    所述第一网元根据所述数据包的指定标识建立与RB和/或LCH的映射关系，并将所述映射关系存储在映射mapping表中；
    所述用户面高层实体依据所述mapping表将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，RB，LCH。
  4. 根据权利要求3所述的方法，其中，第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包之后，所述方法还包括：
    在所述第一网元检测到未建立与所述指定标识对应的RB的情况下，所述第一网元建立与所述指定标识对应的RB，并将所述指定标识与所述RB的对应关系记为映射关系，将所述映射关系存储于所述mapping表中。
  5. 根据权利要求1所述的方法，其中，所述第一网元的用户面高层实体通过以下协议之一与第二网元进行数据传输：
    用户层面的GPRS隧道协议GTP-U；网络协议IP；网际协议安全IP-Sec隧道协议。
  6. 根据权利要求1所述的方法，其中，所述指定标识包括以下之一：
    QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
  7. 根据权利要求1所述的方法，其中，所述用户面高层实体包括以下之一：
    L2协议栈用户面实体之上的独立实体；
    L2协议栈中的用户面实体。
  8. 根据权利要求7所述的方法，其中，所述用户面低层实体，包括以下之一：
    在所述用户面高层实体为L2协议栈用户面实体之上的独立实体的情况下，所述用户面低层实体包括以下至少之一：分组数据汇聚协议PDCP实体，无线链路控制RLC实体，媒体接入控制MAC实体；
    在所述用户面高层实体为L2协议栈中的第一用户面实体的情况下，所述用户面低层实体包括L2协议栈中除所述第一用户面实体之外的用户面实体，其中，所述第一用户面实体为以下之一：PDCP实体，RLC实体，MAC实体。
  9. 根据权利要求1所述的方法，其中，所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，RB，LCH，包括：
    在所述用户面高层实体接收到所述数据包之后，将所述数据包存储于缓存buffer中；
    在接收到所述用户面低层实体的传输指示之后，所述用户面高层实体将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，RB，LCH；其中，所述传输指示用于指示所述用户面低层实体与 所述用户面高层实体存在传输机会。
  10. 一种用户面数据的映射方法，包括：
    第二网元向第一网元的用户面高层实体发送携带有指定标识的数据包；
    其中，所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
  11. 根据权利要求10所述的方法，其中，所述指定标识是由所述第二网元设置的标识。
  12. 根据权利要求10所述的方法，其中，所述指定标识包括以下之一：
    QoS标识ID；优先指示符PRI；网络协议IP的差分服务代码点DSCP。
  13. 一种用户面数据的映射系统，包括：第一网元，第二网元，其中，所述第一网元包括：用户面高层实体，用户面低层实体；
    第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
    所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
  14. 根据权利要求13所述的系统，其中，第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包之后，所述系统还包括：
    所述第一网元根据所述数据包的指定标识建立与RB和/或LCH的映射关系，并将所述映射关系存储在映射mapping表中；
    所述用户面高层实体依据所述mapping表将所述数据包映射到以 下至少之一：所述第一网元的用户面低层实体，RB，LCH。
  15. 根据权利要求14所述的系统，其中，第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包之后，在所述第一网元检测到未建立与所述指定标识对应的RB的情况下，所述第一网元建立与所述指定标识对应的RB，并将所述指定标识与所述RB的对应关系记为映射关系，将所述映射关系存储于所述mapping表中。
  16. 根据权利要求13所述的系统，其中，所述指定标识包括以下之一：
    QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
  17. 根据权利要求13所述的系统，其中，所述用户面高层实体包括以下之一：
    L2协议栈用户面实体之上的独立实体；
    L2协议栈中的用户面实体。
  18. 根据权利要求17所述的系统，其中，所述用户面低层实体，包括以下之一：
    在所述用户面高层实体为L2协议栈用户面实体之上的独立实体的情况下，所述用户面低层实体包括以下至少之一：分组数据汇聚协议PDCP实体，无线链路控制RLC实体，媒体接入控制MAC实体；
    在所述用户面高层实体为L2协议栈中的第一用户面实体的情况下，所述用户面低层实体包括L2协议栈中除所述第一用户面实体之外的用户面实体，其中，所述第一用户面实体为以下之一：PDCP实体，RLC实体，MAC实体。
  19. 根据权利要求13所述的系统，其中，所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH，包括：
    在所述用户面高层实体接收到所述数据包之后，将所述数据包存 储于缓存buffer中；
    所述用户面低层实体向所述用户面高层实体发送传输指示，其中，所述传输指示用于指示所述用户面低层实体与所述用户面高层实体存在传输机会；
    所述用户面高层实体将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，RB，LCH。
  20. 一种用户面数据的映射装置，应用于第一网元，包括：
    接收模块，配置为通过所述第一网元的用户面高层实体接收第二网元发送的携带有指定标识的数据包；
    映射模块，配置为通过所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
  21. 根据权利要求20所述的装置，其中，所述接收模块还配置为在第一网元的用户面高层实体接收第二网元发送的数据包之后，根据所述数据包的指定标识建立与RB和/或LCH的映射关系，并将所述映射关系存储在映射mapping表中；
    所述接收模块还配置为通过所述用户面高层实体依据所述mapping表将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，RB，LCH。
  22. 根据权利要求20所述的装置，其中，所述第一网元的用户面高层实体通过以下协议之一与第二网元进行数据传输：
    用户层面的GPRS隧道协议GTP-U；网络协议IP；网际协议安全IP-Sec隧道协议。
  23. 根据权利要求20所述的装置，其中，所述指定标识包括以下之一：
    QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
  24. 根据权利要求20所述的装置，其中，所述用户面高层实体包括以下之一：
    L2协议栈用户面实体之上的独立实体；
    L2协议栈中的用户面实体。
  25. 根据权利要求24所述的装置，其中，所述用户面低层实体，包括以下之一：
    在所述用户面高层实体为L2协议栈用户面实体之上的独立实体的情况下，所述用户面低层实体包括以下至少之一：分组数据汇聚协议PDCP实体，无线链路控制RLC实体，媒体接入控制MAC实体；
    在所述用户面高层实体为L2协议栈中的第一用户面实体的情况下，所述用户面低层实体包括L2协议栈中除所述第一用户面实体之外的用户面实体，其中，所述第一用户面实体为以下之一：PDCP实体，RLC实体，MAC实体。
  26. 根据权利要求20所述的装置，其中，所述映射模块还配置为在所述用户面高层实体接收到所述数据包之后，将所述数据包存储于缓存buffer中；
    所述映射模块还配置为在接收到所述用户面低层实体的传输指示之后，通过所述用户面高层实体将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，RB，LCH；其中，所述传输指示用于指示所述用户面低层实体与所述用户面高层实体存在传输机会。
  27. 一种用户面数据的映射装置，应用于第二网元，包括：
    发送模块，配置为向第一网元的用户面高层实体发送数据包，其中，所述数据包携带有由所述第二网元设置的指定标识；其中，所述用户面高层实体依据所述指定标识将所述数据包映射到以下至少之一：所述第一网元的用户面低层实体，无线承载RB，逻辑信道LCH。
  28. 根据权利要求27所述的装置，其中，所述第二网元通过以下协议之一与第一网元的用户面高层实体进行数据传输：
    用户层面的GPRS隧道协议GTP-U；网络协议IP；网际协议安全IP-Sec隧道协议。
  29. 根据权利要求27所述的装置，其中，所述指定标识包括以下之一：
    QoS标识ID；优先指示符PRI；IP的差分服务代码点DSCP。
  30. 一种用户面数据的映射方法，所述方法包括：
    第三网元的用户面高层实体获得来自非接入层实体的用于识别QoS特性参数的QoS标识ID；
    所述用户面高层实体将所述QoS ID与预先存储的映射规则匹配；
    匹配成功时，将数据包封装后传递至匹配得到的用户面低层实体、和/或DRB、和/或LCH；
    匹配不成功时，将数据包封装后传递至默认用户面低层实体、和/或DRB、和/或LCH。
  31. 根据权利要求30所述的方法，其中，所述第三网元的用户面高层实体获得来自非接入层实体的所述QoS标识ID之前，还包括：
    所述非接入层实体接收所述数据包，并从所述数据包中获取数据包过滤器或数据业务过滤器；
    所述非接入层实体基于所述数据包过滤器或数据业务过滤器、预先存储的QoS策略参数确定与所述数据包对应的QoS特性参数，将用于识别所述QoS特性参数的QoS标识ID传递至用户面高层实体。
  32. 根据权利要求31所述的方法，其中，所述非接入层实体基于所述数据包过滤器或数据业务过滤器、预先存储的QoS策略参数确定与所述数据包对应的QoS特性参数，包括：
    所述第三网元接收并保存QoS策略参数集合；
    所述非接入层实体将所述数据包过滤器或数据业务过滤器与所述QoS策略参数集合中的各个QoS策略参数进行匹配，获取应用于所述数据包的QoS策略参数。
  33. 根据权利要求30或31所述的方法，其中，所述用户面高层实体在对所述数据包进行封装时，携带所述QoS ID。
  34. 一种用户面数据的映射装置，应用于第三网元，包括匹配模块；
    所述匹配模块，配置为获得用于识别QoS特性参数的QoS标识ID，将所述QoS ID与预先储的映射规则匹配，在匹配成功时，将数据包封装后传递至匹配得到的用户面低层实体、和/或DRB、和/或LCH；匹配不成功时，将数据包封装后传递至默认用户面低层实体、和/或DRB、和/或LCH。
  35. 根据权利要求34所述的装置，其中，所述装置还包括：解析模块和确定模块；
    所述解析模块，配置为接收所述数据包，并从所述数据包中获取数据包过滤器或数据业务过滤器；
    所述确定模块，配置为基于所述数据包过滤器或数据业务过滤器、预先存储的QoS策略参数确定与所述数据包对应的QoS特性参数，并将所述用于识别所述QoS特性参数的QoS标识ID传递至所述匹配模块。
  36. 根据权利要求34所述的装置，其中，所述确定模块，配置为接收并保存QoS策略参数集合，将所述数据包过滤器或数据业务过滤器与所述QoS策略参数集合中的各个QoS策略参数进行匹配，获取应用于所述数据包的QoS策略参数。
  37. 根据权利要求34或35所述的装置，其中，所述匹配模块对所述数据包进行封装时，携带所述QoS ID。
  38. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，该计算机可执行指令用于执行权利要求1至9任一项所述的用户面数据的映射方法；或，该计算机可执行指令用于执行权利要求10至12任一项所述的用户面数据的映射方法；或该计算机可执行指令用于执行权利要求30至33任一项所述的用户面数据的映射方法。
PCT/CN2016/104761 2016-08-12 2016-11-04 用户面数据的映射方法、装置、系统及存储介质 WO2018028061A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP16912515.0A EP3499922B1 (en) 2016-08-12 2016-11-04 Method, device and computer-readable storage medium for applying qos based on user plane data mapping

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610665025.2A CN107734546B (zh) 2016-08-12 2016-08-12 用户面数据的映射方法、装置及系统
CN201610665025.2 2016-08-12

Publications (1)

Publication Number Publication Date
WO2018028061A1 true WO2018028061A1 (zh) 2018-02-15

Family

ID=61161763

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/104761 WO2018028061A1 (zh) 2016-08-12 2016-11-04 用户面数据的映射方法、装置、系统及存储介质

Country Status (3)

Country Link
EP (1) EP3499922B1 (zh)
CN (1) CN107734546B (zh)
WO (1) WO2018028061A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3355641A1 (en) * 2017-01-25 2018-08-01 Acer Incorporated Method of mapping data packets and related apparatuses using the same
CN110831251A (zh) * 2018-08-10 2020-02-21 展讯通信（上海）有限公司 数据发送方法及装置、存储介质、发送端

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324907B (zh) * 2018-03-30 2021-05-25 电信科学技术研究院有限公司 一种业务承载配置方法及装置
CN110351043A (zh) * 2018-04-04 2019-10-18 华为技术有限公司 通信方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102025732A (zh) * 2010-12-07 2011-04-20 南京邮电大学 动态自适应的认知网络QoS映射方法
US20130114446A1 (en) * 2011-11-04 2013-05-09 Interdigital Patent Holdings, Inc. Methods, apparatus and systems for minimization of drive tests (mdt) based on qos verifications
US20140126454A1 (en) * 2012-11-05 2014-05-08 Qualcomm Incorporated Embms support in heterogeneous network
WO2016091298A1 (en) * 2014-12-10 2016-06-16 Nokia Solutions And Networks Oy Updating flow-specific qos policies based on information reported from base station

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100596232C (zh) * 2006-08-22 2010-03-24 华为技术有限公司 一种服务质量承载建立和映射的实现方法和装置
CN101754304B (zh) * 2008-12-09 2012-11-28 中兴通讯股份有限公司 实现跨基站切换的用户面数据反传方法
CN101932102B (zh) * 2009-06-19 2013-01-23 华为技术有限公司 业务承载映射方法及通信设备
EP2843992B1 (en) * 2012-04-26 2017-11-22 NEC Corporation Wireless communication device, network node, user node, core network, and method mounted thereto
US9819469B2 (en) * 2013-07-01 2017-11-14 Qualcomm Incorporated Techniques for enabling quality of service (QoS) on WLAN for traffic related to a bearer on cellular networks
US9247529B2 (en) * 2013-07-30 2016-01-26 Qualcomm Incorporated Apparatus and methods of managing signaling radio bearer transmissions at a user equipment
CN104010370B (zh) * 2014-04-28 2019-07-09 北京邮电大学 异构系统融合控制方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102025732A (zh) * 2010-12-07 2011-04-20 南京邮电大学 动态自适应的认知网络QoS映射方法
US20130114446A1 (en) * 2011-11-04 2013-05-09 Interdigital Patent Holdings, Inc. Methods, apparatus and systems for minimization of drive tests (mdt) based on qos verifications
US20140126454A1 (en) * 2012-11-05 2014-05-08 Qualcomm Incorporated Embms support in heterogeneous network
WO2016091298A1 (en) * 2014-12-10 2016-06-16 Nokia Solutions And Networks Oy Updating flow-specific qos policies based on information reported from base station

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3499922A4 *
ZTE: "FURTHER DISCUSSION ON THE RAN QOS CONTROL", 3GPP TSG-RAN WG2 MEETING #94 R2-163746, 22 May 2016 (2016-05-22), XP051105157 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3355641A1 (en) * 2017-01-25 2018-08-01 Acer Incorporated Method of mapping data packets and related apparatuses using the same
CN110831251A (zh) * 2018-08-10 2020-02-21 展讯通信（上海）有限公司 数据发送方法及装置、存储介质、发送端
CN110831251B (zh) * 2018-08-10 2020-11-06 展讯通信（上海）有限公司 数据发送方法及装置、存储介质、发送端
US11601954B2 (en) 2018-08-10 2023-03-07 Spreadtrum Communications (Shanghai) Co., Ltd. Data sending method and apparatus, storage medium, and sending end

Also Published As

Publication number Publication date
EP3499922A1 (en) 2019-06-19
EP3499922B1 (en) 2021-09-15
EP3499922A4 (en) 2020-02-26
CN107734546B (zh) 2022-10-28
CN107734546A (zh) 2018-02-23

Similar Documents

Publication Publication Date Title
US11510131B2 (en) Configuration method, data transmission method, and apparatus
JP6568270B2 (ja) サービス層サウスバウンドインターフェースおよびサービスの質
TWI764893B (zh) 用於建立無線資源控制連接的方法和裝置
JP7177259B2 (ja) データ伝送方法及び装置
WO2021032131A1 (zh) 一种用户面信息上报方法及装置
WO2018028061A1 (zh) 用户面数据的映射方法、装置、系统及存储介质
WO2019242749A1 (zh) 一种切换方法及装置
WO2019242714A1 (zh) 一种数据传输方法及装置
EP2963990B1 (en) Method and apparatus for connecting to packet data networks in wireless communication system
WO2019062498A1 (zh) 获取特征参数的方法和装置
CN111345064B (zh) 终端装置以及方法
WO2021243837A1 (zh) 基于ursp规则的应用数据路由方法及用户设备
WO2017177753A1 (zh) 一种基于流的承载管理方法、数据传输方法及装置
CN105325043A (zh) 承载建立装置和方法
WO2020063438A1 (zh) 一种协调重复传输的方法
GB2551485A (en) Providing service data flow description
US20150049612A1 (en) Determining a Traffic Bearer for Data Traffic Between a Terminal and a Content Data Source of a Content Data Network
BR112021012433A2 (pt) Método e dispositivo de comunicação, e meio de armazenamento
WO2019154160A1 (zh) 一种通信方法及装置
US20190104439A1 (en) Data transmission method, apparatus, and system
WO2021134723A1 (zh) 通信方法、设备及系统
CN111491370B (zh) 一种通信方法、网元、系统及存储介质
WO2019136925A1 (zh) 一种数据传输方法及装置、计算机存储介质
WO2017193363A1 (zh) 业务数据流发送方法及装置
WO2018171639A1 (zh) 无线通信方法、终端、接入网设备和网络系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16912515

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016912515

Country of ref document: EP

Effective date: 20190312