WO2019019486A1 - 下行数据包配置方法及装置 - Google Patents

下行数据包配置方法及装置 Download PDF

Info

Publication number
WO2019019486A1
WO2019019486A1 PCT/CN2017/110944 CN2017110944W WO2019019486A1 WO 2019019486 A1 WO2019019486 A1 WO 2019019486A1 CN 2017110944 W CN2017110944 W CN 2017110944W WO 2019019486 A1 WO2019019486 A1 WO 2019019486A1
Authority
WO
WIPO (PCT)
Prior art keywords
downlink
data packet
processing attribute
downlink data
base station
Prior art date
Application number
PCT/CN2017/110944
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 ES17919504T priority Critical patent/ES2911923T3/es
Priority to US16/633,156 priority patent/US11190967B2/en
Priority to EP17919504.5A priority patent/EP3661260B1/en
Priority to CN201780001600.1A priority patent/CN108476508B/zh
Publication of WO2019019486A1 publication Critical patent/WO2019019486A1/zh

Links

Images

Classifications

    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
    • 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/0226—Traffic management, e.g. flow control or congestion control based on location or mobility
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00—Encapsulation of packets
    • 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/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • 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/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a downlink data packet configuration method and apparatus.
  • the fourth-generation mobile communication (4G-Generation, 4G) technology divides the communication process into a Non-Access Stratum (NAS) layer and an Access (Standard Stratum, AS) layer.
  • the AS layer mainly includes four sub-layers, from top to bottom, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the media access control (MediaAccess). Control, MAC) layer and physical (Physical Layer, PHY) layer.
  • the AS layer introduces a new sub-layer above the PDCP layer, namely the service data assimilation protocol.
  • SDAP Service DataAdaptation Protocol
  • the SDAP layer is used to implement mapping between data streams and Data Radio Bearers (DRBs), that is, to allocate DRBs for data streams to transmit data packets through the mapped DRBs.
  • DRBs Data Radio Bearers
  • the SDAP layer also adds a QOS Flow ID (QFI) to the data packet so that the terminal determines the DRB to which the data packet is mapped.
  • QFI QOS Flow ID
  • each sublayer of the AS layer encapsulates and decapsulates the downlink data packet, which occupies a large amount of processing resources of the device.
  • the present disclosure provides a downlink data packet configuration method and apparatus.
  • the technical solution is as follows:
  • a downlink data packet configuration method is provided, which is applied to a base station, where the method includes:
  • the target downlink processing attribute includes whether to support the non-access reflection quality of service NAS Reflective QoS function, and whether to support Ingressive Quality of Service AS Reflective QoS function;
  • the target downlink processing attribute is to support the NAS Reflective QoS function or the AS Reflective QoS function, add the service data assimilation protocol SDAP header in the process of encapsulating the downlink data packet; if the target downlink processing attribute is not supporting the NAS
  • the Reflective QoS function does not support the AS Reflective QoS function.
  • the SDAP packet header is not added during the process of encapsulating the downlink data packet.
  • the adding the service data assimilation protocol SDAP header in the process of encapsulating the downlink data packet includes:
  • the target downlink processing attribute is to support the NAS Reflective QoS function, add a SDAP header in the process of encapsulating the downlink data packet, and add an RQI field and a data flow identifier QFI field in the SDAP packet header;
  • the target downlink processing attribute is only supporting the AS Reflective QoS function, adding a SDAP header in the process of encapsulating the downlink data packet, and adding indication information and a QFI field to the SDAP packet header, where the indication information It is used to indicate whether the QFI field is included in the SDAP header.
  • the RQI field has a length of 1 bit
  • the QFI field has a length of 7 bits.
  • the method before the sending the downlink data packet to the terminal, the method further includes:
  • the sending, by the terminal, the correspondence between the DRB and the downlink processing attribute includes:
  • the corresponding relationship between the DRB and the downlink processing attribute is sent to the terminal by using an RRC configuration message.
  • the method before the sending the encapsulated downlink data packet to the terminal, the method further includes:
  • the method further includes:
  • the first configuration information includes a correspondence between the QFI and a downlink processing attribute, and/or the DRB and Corresponding relationship of the downlink processing attributes;
  • a downlink data packet configuration method is provided, which is applied to a terminal, where the method includes:
  • the downlink processing attribute includes a serving quality NAS Reflective QoS that supports non-access reflection Function, and whether it supports access reflection quality of service AS Reflective QoS function;
  • the target downlink processing attribute is to support the NAS Reflective QoS function or the AS Reflective QoS function, determine that the downlink data packet is encapsulated with a SDAP packet header; if the target downlink processing attribute does not support the NAS Reflective QoS function and does not support the AS The Reflective QoS function determines that the downlink data packet is not encapsulated with a SDAP packet header;
  • the downlink data packet is processed based on whether the determined downlink data packet is encapsulated with a SDAP packet header.
  • the processing, by the downlink data packet includes:
  • the SDAP header carries the RQI field and the QFI field, processing the downlink data packet in the NAS layer;
  • the downlink data packet is processed in the AS layer, where the indication information is used to indicate whether the QFI field is included in the SDAP header.
  • the RQI field has a length of 1 bit
  • the QFI field has a length of 7 bits.
  • the method before the receiving the downlink data packet sent by the base station, the method further includes:
  • the receiving the correspondence between the DRB and the downlink processing attribute sent by the base station includes:
  • the method before the receiving the downlink data packet sent by the base station, the method further includes:
  • the processing, by the downlink data packet includes:
  • the downlink data packet is processed in the AS layer.
  • the method further includes:
  • the base station Receiving and storing the second configuration information that is sent by the base station, where the second configuration information is that, after the predetermined condition is met, the base station sends the first configuration information corresponding to the terminal to the target base station, and the target base station Information obtained;
  • the first configuration information includes a correspondence between the QFI and the downlink processing attribute, and/or a correspondence between the DRB and the downlink processing attribute, where the second configuration information includes at least the target base station. Correspondence between the QFI and the downlink processing attribute, and the correspondence between the DRB corresponding to the target base station and the downlink processing attribute.
  • a downlink data packet configuration apparatus which is applied to a base station, where the apparatus includes:
  • a first determining module configured to determine a target data bearer DRB corresponding to the downlink data packet to be sent
  • the second determining module is configured to determine, according to the correspondence between the stored DRB and the processing attribute, the target downlink processing attribute corresponding to the target DRB, where the downlink processing attribute includes whether the NAS Reflective QoS function is supported, and whether the support is supported.
  • AS Reflective QoS function ;
  • the processing module is configured to add a service data assimilation protocol (SDAP) header in the process of encapsulating the downlink data packet if the target downlink processing attribute is to support the NAS Reflective QoS function or the AS Reflective QoS function; if the target downlink If the processing attribute is that the NAS Reflective QoS function is not supported and the AS Reflective QoS function is not supported, the SDAP header is not added in the process of encapsulating the downlink data packet.
  • SDAP service data assimilation protocol
  • the first sending module is configured to send the encapsulated downlink data packet to the terminal.
  • the processing module includes:
  • a first adding unit configured to add a SDAP packet header in the process of encapsulating the downlink data packet, and add an RQI field and a data stream in the SDAP packet header, if the target downlink processing attribute is a NAS reflective QoS function. Identify the QFI field;
  • a second adding unit configured to add a SDAP packet header in the process of encapsulating the downlink data packet, and add indication information and QFI in the SDAP packet header, if the target downlink processing attribute is only supporting the AS Reflective QoS function. a field, wherein the indication information is used to indicate whether a QFI field is included in the SDAP header.
  • the RQI field has a length of 1 bit
  • the QFI field has a length of 7 bits.
  • the device further includes:
  • the second sending module is configured to send the corresponding relationship between the DRB and the downlink processing attribute to the terminal before the sending the downlink data packet to the terminal, where the terminal corresponds to the DRB and the downlink processing attribute Relationships are stored.
  • the second sending module is further configured to:
  • the corresponding relationship between the DRB and the downlink processing attribute is sent to the terminal by using an RRC configuration message.
  • the device further includes:
  • the obtaining module is configured to obtain a correspondence between the QFI and the downlink processing attribute before the sending the encapsulated downlink data packet to the terminal;
  • the third sending module is configured to send a correspondence between the QFI and a downlink processing attribute to the terminal, and the terminal stores a correspondence between the QFI and a downlink processing attribute.
  • the device further includes:
  • a fourth sending module configured to: when the terminal performs a base station handover to the target base station, send the first configuration information corresponding to the terminal to the target base station, where the first configuration information includes the Correspondence between the QFI and the downlink processing attribute, and/or the correspondence between the DRB and the downlink processing attribute;
  • the fifth sending module is configured to receive the second configuration information that is set by the target base station according to the first configuration information, and send the second configuration information to the terminal, where the terminal stores the second configuration And the second configuration information includes a correspondence between the QFI and the downlink processing attribute corresponding to the target base station, and a correspondence between the DRB corresponding to the target base station and the downlink processing attribute.
  • a downlink data packet configuration apparatus which is applied to a terminal, where the apparatus includes:
  • the first receiving module is configured to receive a downlink data packet sent by the base station
  • the first determining module is configured to determine, according to the correspondence between the pre-configured DRB and the downlink processing attribute, a target downlink processing attribute corresponding to the target DRB that transmits the downlink data packet, where the downlink processing attribute is a non-contact In-reflection quality of service NAS Reflective QoS function, and whether or not to support access reflection quality of service AS Reflective QoS function;
  • a second determining module configured to: if the target downlink processing attribute is a NAS Reflective QoS function or an AS Reflective QoS function, determine that the downlink data packet is encapsulated with a SDAP packet header; if the target downlink processing attribute is not supported The NAS Reflective QoS function does not support the AS Reflective QoS function, and determines that the downlink data packet is not encapsulated with a SDAP packet header;
  • the processing module is configured to process the downlink data packet based on whether the determined downlink data packet is encapsulated with a SDAP packet header.
  • the processing module includes:
  • a first parsing unit configured to parse the SDAP header of the downlink data packet
  • a first processing unit configured to process the downlink data packet in a NAS layer if the SDAP packet header carries an RQI field and a QFI field;
  • the second processing unit is configured to process the downlink data packet in the AS layer if the SDAP packet header carries the indication information and the QFI field.
  • the RQI field has a length of 1 bit
  • the QFI field has a length of 7 bits.
  • the device further includes:
  • a storage module configured to receive the downlink data packet sent by the base station, and receive the base station Corresponding relationship between the transmitted DRB and the downlink processing attribute, and storing the correspondence between the DRB and the downlink processing attribute.
  • the storage module is further configured to:
  • the device further includes:
  • the second receiving module is configured to receive and store a correspondence between the QFI and the downlink processing attribute sent by the base station before receiving the downlink data packet sent by the base station;
  • the processing module further includes:
  • a second parsing unit configured to parse a SDAP packet header of the downlink data packet, to obtain a QFI field carried in the SDAP packet header
  • a determining unit configured to determine, according to the correspondence between the QFI and the downlink processing attribute, a downlink processing attribute corresponding to the QFI carried by the SDAP packet header;
  • the third processing unit is configured to process the downlink data packet in the NAS layer if the downlink processing attribute corresponding to the QFI is a NAS Reflective QoS function;
  • the fourth processing unit is configured to process the downlink data packet in the AS layer if the downlink processing attribute corresponding to the QFI is to support the AS Reflective QoS function.
  • the device further includes:
  • a third receiving module configured to receive and store second configuration information that is sent by the base station, where the second configuration information is that, when the predetermined condition is met, the base station sends the first configuration information corresponding to the terminal to the target Information obtained from the target base station after the base station;
  • the first configuration information includes a correspondence between the QFI and the downlink processing attribute, and/or a correspondence between the DRB and the downlink processing attribute, where the second configuration information includes at least the target base station. Correspondence between the QFI and the downlink processing attribute, and the correspondence between the DRB corresponding to the target base station and the downlink processing attribute.
  • a base station includes a processor and a memory, where the memory stores at least one instruction, at least one program, a code set, or a set of instructions, the at least one instruction, The at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement a downlink packet configuration method as described in the first aspect of the embodiments of the present application.
  • a computer readable storage medium stores at least one instruction, at least one program, a code set, or a set of instructions, the at least one piece
  • the instructions, the at least one program, the set of codes, or the set of instructions are loaded and executed by a processor to implement a downlink packet configuration method as described in the first aspect of the embodiments of the present application.
  • a terminal including a processor and a memory, where the memory stores at least one instruction, at least one program, a code set or a set of instructions, the at least one instruction, The at least one program, the set of codes, or the set of instructions is loaded and executed by the processor to implement a downlink packet configuration method as described in the second aspect of the embodiments of the present application.
  • a computer readable storage medium stores at least one instruction, at least one program, a code set, or a set of instructions, the at least one instruction, the at least one segment
  • the program, the set of codes, or the set of instructions is loaded and executed by a processor to implement a downstream packet configuration method as described in the second aspect of the embodiments of the present application.
  • Adding a SDAP packet header to a downlink packet that supports the NAS Reflective QoS function or the AS Reflective QoS function is a downlink packet that does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function.
  • the SDAP packet header is added to solve the problem in the prior art that each downlink layer of the AS layer encapsulates and decapsulates the downlink data packet regardless of the downlink processing attribute of the downlink data packet, which occupies a problem of increasing the processing resources of the device. The effect of reducing the occupation of processing resources of the device.
  • FIG. 1 is a protocol architecture diagram of a mobile communication system shown in an exemplary embodiment of the present application
  • FIG. 2 is a flowchart of a method for configuring a downlink data packet according to an exemplary embodiment
  • FIG. 3A is a flowchart of a method for configuring a downlink data packet according to another exemplary embodiment
  • FIG. 3B is a structural diagram of a downlink data packet whose target downlink processing attribute is a NAS Reflective QoS function according to an exemplary embodiment
  • FIG. 3C illustrates that the target downlink processing attribute is only supporting AS according to an exemplary embodiment.
  • FIG. 3D is a flowchart of a method for processing a downlink data packet by a terminal according to an exemplary embodiment
  • FIG. 4A is a flowchart of a method for configuring a downlink data packet according to still another exemplary embodiment
  • FIG. 4B is a flowchart of a method for processing a downlink data packet by a terminal according to an exemplary embodiment
  • FIG. 5 is a flowchart of a method for mapping a correspondence relationship according to an exemplary embodiment
  • FIG. 6 is a block diagram of a downlink data packet configuration apparatus according to an exemplary embodiment
  • FIG. 7 is a block diagram of a downlink data packet configuration apparatus according to an exemplary embodiment
  • FIG. 8 is a block diagram of a terminal according to an exemplary embodiment
  • FIG. 9 is a block diagram of a base station according to an exemplary embodiment.
  • a “module” as referred to herein generally refers to a program or instruction stored in a memory that is capable of performing certain functions;
  • "unit” as referred to herein generally refers to a functional structure that is logically divided, the "unit” It can be implemented by pure hardware or a combination of hardware and software.
  • Multiple as referred to herein means two or more. "and/or”, describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately.
  • the character "/" generally indicates that the contextual object is an "or" relationship.
  • the embodiment of the invention provides a downlink data packet configuration method, which can be implemented by a terminal and a base station.
  • the terminal refers to a device that performs data communication with a base station. Terminal can be accessed via wireless
  • the RadioAccess Network (RAN) communicates with one or more core networks.
  • the terminal may also be called a Subscriber Unit, a Subscriber Station, a Mobile Station, a Mobile, and a Remote. Remote Station, Access Point, Remote Terminal, Access Terminal, User Terminal, UserAgent, User Device.
  • the terminal may also be a relay device, which is not limited in this embodiment.
  • the wireless air interface is a wireless air interface based on a 5G standard, for example, the wireless air interface is a New Radio (NR); or the wireless air interface may also be a wireless air interface based on a 5G more next-generation mobile communication network technology. .
  • the wireless air interface is also compatible with wireless air interfaces of earlier generation mobile communication network technologies such as 2G, 3G and 4G.
  • the base station can be used to convert the received radio frame with the IP packet message, and can also coordinate the attribute management of the air interface.
  • the base station may be a base station (gNode-B, gNB) in a 5G system.
  • the gNB is a base station employing a centralized distributed architecture.
  • the access network device 140 adopts a centralized distributed architecture it generally includes a central unit (CU) and at least two distributed units (DUs).
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • media access control are set in the centralized unit.
  • the protocol stack of the Media Access Control (MAC) layer is not limited in this embodiment.
  • FIG. 1 is a protocol architecture diagram of a mobile communication system according to an exemplary embodiment of the present application.
  • the devices involved in the protocol architecture include: a terminal 120 and a base station 140.
  • the layers included in the communication infrastructure include the application layer, the NAS layer, and the AS layer from top to bottom.
  • the AS layer includes the SDAP layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY. Floor.
  • the terminal 120 establishes a session with the base station 140, multiple data streams may be transmitted during the session, and each data stream may include multiple data packets, and the data packets are submitted in the communication infrastructure of the terminal 120 from top to bottom.
  • each layer has submodules that support each DRB, and the module can be a virtual software module.
  • the data packets are allocated in the corresponding sub-modules of the DRB corresponding to the data packet.
  • FIG. 2 is a flowchart of a method for configuring a downlink data packet according to an exemplary embodiment. As shown in FIG. 2, the downlink data packet configuration method is applied to the mobile communication system shown in FIG. 1. The method includes The following steps.
  • step 201 the base station determines a target data bearer DRB corresponding to the downlink data packet to be transmitted.
  • step 202 the base station determines the target downlink processing attribute corresponding to the target DRB according to the correspondence between the pre-configured DRB and the downlink processing attribute.
  • the downlink processing attribute includes whether to support the non-access reflection quality of service (NAS Reflective QoS) function, and whether to support the access reflected quality of service (AS Reflective QoS) function.
  • NAS Reflective QoS non-access reflection quality of service
  • AS Reflective QoS access reflected quality of service
  • step 203 if the target downlink processing attribute supports the NAS Reflective QoS function or supports the AS Reflective QoS function, the base station adds the service data assimilation protocol SDAP header in the process of encapsulating the downlink data packet; if the target downlink processing attribute is not supporting the NAS Reflective QoS does not support the AS Reflective QoS function. The base station does not add the SDAP header during the process of encapsulating downstream packets.
  • step 204 the base station sends the encapsulated downlink data packet to the terminal.
  • the terminal receives the downlink data packet sent by the base station.
  • step 205 the terminal determines, according to the correspondence between the pre-configured DRB and the downlink processing attribute, the target downlink processing attribute corresponding to the target DRB that transmits the downlink data packet.
  • step 206 if the target downlink processing attribute supports the NAS Reflective QoS function or supports the AS Reflective QoS function, the terminal determines that the downlink data packet is encapsulated with the SDAP header; if the target downlink processing attribute does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function, the terminal determines that the downlink data packet is not encapsulated with the SDAP header.
  • step 207 the terminal processes the downlink data packet based on whether the determined downlink data packet is encapsulated with the SDAP packet header.
  • the downlink data packet configuration method adds a SDAP packet header only to a downlink data packet whose downlink processing attribute is a NAS Reflective QoS function or an AS Reflective QoS function, because the base station does not process the downlink processing attribute.
  • each sub-layer of the AS layer encapsulates and decapsulates the downlink data packet, occupies a problem of increasing the processing resources of the device, and reduces the processing of the device. The effect of the occupation of resources.
  • FIG. 3A is a flowchart of a method for configuring a downlink data packet according to another exemplary embodiment. As shown in FIG. 3A, the downlink data packet configuration method is applied to the mobile communication system shown in FIG. Includes the following steps.
  • step 301 the base station determines a target DRB corresponding to the downlink data packet to be transmitted.
  • a data stream is transmitted in a session between the terminal and the base station, and each data stream includes multiple data packets.
  • the data packet sent by the terminal to the base station is called an uplink data packet, and the data packet sent by the base station to the terminal is called downlink data. package.
  • the base station After the terminal establishes a connection with the base station, the base station establishes multiple DRBs with the terminal, and each DRB corresponds to a different service. Since the base station knows the service attribute of the downlink data packet, after the base station acquires the downlink data packet, the base station determines the target DRB corresponding to the service attribute of the downlink data packet according to the correspondence between the pre-stored service attribute and the DRB.
  • the base station determines the target downlink processing attribute corresponding to the target DRB according to the correspondence between the pre-configured DRB and the downlink processing attribute.
  • the one-to-one correspondence between the DRB and the downlink processing attribute refers to the downlink processing attribute corresponding to the data packet in the data stream transmitted by the one DRB.
  • the downlink processing attributes include whether to support the non-access-reflected QoS-based NAS Reflective QoS function, and whether to support the access-reflected quality of service AS Reflective QoS function.
  • the data packet in the data stream transmitted by the target DRB does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function.
  • step 303 if the target downlink processing attribute supports the NAS Reflective QoS function or supports the AS Reflective QoS function, the base station adds a SDAP header in the process of encapsulating the downlink data packet; if the target downlink processing attribute does not support the NAS Reflective QoS function, The AS Reflective QoS function is not supported, and the base station does not add the SDAP header in the process of encapsulating downlink packets.
  • FIG. 3B is a structural diagram of a downlink data packet whose target downlink processing attribute is a NAS Reflective QoS function according to an exemplary embodiment. As shown in FIG. 3B, if the target downlink processing attribute supports the NAS Reflective QoS function, the packet is encapsulated. Added in the process of downstream packets The SDAP header is added with the RQI field and the data stream identification QFI field in the SDAP header. The QFI field is used to identify the data flow to which the downlink data packet belongs.
  • FIG. 3C is a structural diagram of a downlink data packet whose target downlink processing attribute is only supported by the AS Reflective QoS function, as shown in FIG. 3C. If the target downlink processing attribute supports only the AS Reflective QoS function, The SDAP packet header is added in the process of encapsulating the downlink data packet, and the indication information and the QFI field are added in the SDAP packet header, where the indication information is used to indicate whether the QFI field is included in the SDAP packet header.
  • the length of the RQI field and the indication information are both 1 bit, and the length of the QFI field is 7 bits.
  • the indication information is used to indicate the absence of the QFI field in the SDAP header, and is also used to fill in the missing of the RQI field in the SDAP header, so that the SDAP header includes other fields in the RQI field regardless of whether the SDAP header includes the RQI field. The position is unchanged.
  • the size of the SDAP header can be effectively controlled, and the QFI field can effectively ensure that the QFI field can carry enough information.
  • the bits are reserved in the position of the QFI field.
  • the downlink data packet is transmitted to the first layer on the base station side, and each sublayer of the AS layer on the base station side is processed accordingly.
  • the processing manner of the corresponding processing of the downlink data packet may be specifically the data packet decapsulation, the data packet, the data encoding, the data encryption, and the like.
  • the specific processing of the downlink data packet by the base station in the AS layer is not performed. The processing method is limited.
  • the base station encapsulates the data packet in each sublayer of the AS layer. Specifically, when the downlink data packet is in the SDAP layer, the base station adds a SDAP packet header to the downlink data packet in the SDAP layer, and sends the downlink data packet after the SDAP packet header is added to the next layer, the PDCP layer; When the packet is in the PDCP layer, the base station adds a PDCP header to the downlink data packet in the PDCP layer, and sends the downlink data packet after the PDCP packet header is added to the next layer, the RLC layer; when the downlink data packet is in the RLC layer, The base station adds an RLC packet header to the downlink data packet in the RLC layer, and sends the downlink data packet after the RLC packet header is added to the next layer, the MAC layer; when the downlink data packet is in the MAC layer, the base station is in the MAC layer.
  • the downlink data packet is added with a MAC header, and the downlink data packet after the MAC header is added is sent to the next layer, the PHY layer; when the downlink data packet is at the PHY layer, the base station converts the downlink data packet into the PHY layer into The bit stream is sent to the terminal.
  • the base station when the downlink data packet is in the SDAP layer, the base station does not add the SDAP packet header in the process of encapsulating the downlink data packet in the SDAP layer, The downlink data packet is sent to the next layer, the PDCP layer.
  • the base station adds a PDCP packet header to the downlink data packet in the PDCP layer, and sends the downlink data packet after the PDCP packet header is added to the downlink data packet.
  • One layer - RLC layer when the downlink data packet is in the RLC layer, the base station adds an RLC packet header to the downlink data packet in the RLC layer, and sends the downlink data packet after the RLC packet header is added to the next layer - the MAC layer
  • the base station adds a MAC packet header to the downlink data packet in the MAC layer, and sends the downlink data packet after the MAC packet header is added to the next layer, the PHY layer; when the downlink data packet is in the In the PHY layer, the base station converts the downlink data packet into a bit stream in the PHY layer and transmits it to the terminal.
  • step 304 the base station sends the encapsulated downlink data packet to the terminal.
  • the terminal receives the downlink data packet sent by the base station.
  • step 305 the terminal determines, according to the correspondence between the pre-configured DRB and the downlink processing attribute, the target downlink processing attribute corresponding to the target DRB that transmits the downlink data packet.
  • the terminal determines that the downlink data packet does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function.
  • the terminal determines that the downlink data packet supports the NAS Reflective QoS function.
  • step 306 if the target downlink processing attribute supports the NAS Reflective QoS function or supports the AS Reflective QoS function, the terminal determines that the downlink data packet is encapsulated with the SDAP header; if the target downlink processing attribute does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function, the terminal determines that the downlink data packet is not encapsulated with the SDAP header.
  • step 307 the downlink data packet is processed based on whether the determined downlink data packet is encapsulated with a SDAP packet header.
  • FIG. 3D is a flowchart of a method for processing a downlink data packet by a terminal according to an exemplary embodiment. As shown in FIG. 3D, in a possible manner, if it is determined that a downlink data packet is encapsulated with a SDAP packet header, the terminal is configured.
  • the method for processing the downlink data packet includes the following steps.
  • step 307a the SDAP header of the downstream packet is parsed.
  • the target downlink processing attribute is if the target downlink processing attribute is supported by NAS Reflective If the QoS function or the AS Reflective QoS function is supported, the downlink data packet is uploaded to one layer on the terminal side, and each sub-layer of the AS layer on the terminal side performs corresponding processing, wherein the downlink data packet corresponds to
  • the processing manner of the processing may be specifically the data packet decapsulation, the data grouping, the data decoding, the data decryption, and the like. The embodiment does not limit the specific processing manner in which the terminal processes the downlink data packet in the AS layer.
  • the terminal decapsulates the data packet in each sublayer of the AS layer. Specifically, when the terminal receives the bit stream corresponding to the downlink data packet in the PHY layer, the bit stream is converted into a downlink data packet and then sent to the upper layer, the MAC layer; when the downlink data packet is received in the MAC layer, The downlink data packet decapsulates the MAC packet header, and sends the downlink data packet after decapsulating the MAC packet header to the upper layer, the RLC layer; when the downlink data packet is in the RLC layer, the terminal decapsulates the downlink data packet in the RLC layer.
  • RLC packet header, and the downlink data packet after decapsulating the RLC packet header is sent to the upper layer - the PDCP layer; when the downlink data packet is in the PDCP layer, the terminal decapsulates the PDCP packet header for the downlink data packet in the PDCP layer, and the solution
  • the downlink data packet after the PDCP packet header is encapsulated is sent to the upper layer, the SDAP layer.
  • the terminal decapsulates the SDAP packet header for the downlink data packet in the SDAP layer.
  • step 307b if the SDAP header carries the RQI field and the QFI field, the downlink packet is processed in the NAS layer.
  • the terminal may extract the RQI field and the QFI field from the SDAP header, and submit the RQI field and the QFI field to the NAS layer.
  • the NAS layer processes the downlink data packet according to the RQI field and the QFI field, and sends the processed downlink data packet to the application layer.
  • step 307c if the SDAP header carries the indication information and the QFI field, the downlink packet is processed in the AS layer.
  • the downlink data packet supports the AS Reflective QoS function, and the terminal parses the SDAP packet header of the downlink data packet to obtain the indication information.
  • the indication information indicates that the SDAP packet header includes the QFI field
  • the terminal The QFI field in the SDAP header is obtained first, and then the downlink packet is processed according to the QFI field at the AS layer, and the processed downlink packet is sent to the application layer.
  • the terminal transparently transmits the downlink data packet to the next layer.
  • the downlink data packet configuration method provided in the embodiment of the present application is only for the downlink
  • the SAPI header is added to the downlink packets that support the NAS Reflective QoS function or the AS Reflective QoS function.
  • the base station does not add the SDAP header to the downlink packets that do not support the NAS Reflective QoS function and do not support the AS Reflective QoS function.
  • each sub-layer of the AS layer encapsulates and decapsulates the downlink data packet, occupies a large number of processing resources of the device, and reduces the device. The effect of processing the occupation of resources.
  • the mapping between the pre-configured DRB and the downlink processing attribute of the terminal may be performed by the terminal after the base station and the terminal establish multiple DRBs, and the base station sends the terminal to the terminal. Before the downlink data packet, the receiving base station obtains the correspondence between the DRB and the downlink processing attribute to the terminal.
  • step 308 the base station sends a correspondence between the DRB and the downlink processing attribute to the terminal, and the terminal stores the correspondence between the DRB and the downlink processing attribute.
  • the base station sends the correspondence between the DRB and the downlink processing attribute to the terminal by using an RRC configuration message.
  • the terminal receives the correspondence between the DRB and the downlink processing attribute sent by the base station, and stores the correspondence between the DRB and the downlink processing attribute.
  • the terminal receives a correspondence between the DRB sent by the base station and the downlink processing attribute by using the RRC configuration message.
  • step 308 can be implemented before or after any of the steps 301 and 303.
  • the position of the step 308 in the flowchart shown in FIG. 3A is for example only, and the embodiment cannot limit the step 308.
  • FIG. 4A is a flowchart of a method for configuring a downlink data packet according to still another exemplary embodiment. As shown in FIG. 4A, the downlink data packet configuration method is applied to the mobile communication system shown in FIG. Includes the following steps.
  • step 401 the base station determines a target DRB corresponding to the downlink data packet to be transmitted.
  • the base station determines the target downlink processing attribute corresponding to the target DRB according to the correspondence between the pre-configured DRB and the downlink processing attribute.
  • step 403 if the target downlink processing attribute supports the NAS Reflective QoS function or supports the AS Reflective QoS function, the base station adds the SDAP in the process of encapsulating the downlink data packet. If the target downlink processing attribute does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function, the base station does not add the SDAP header in the process of encapsulating the downstream data packet.
  • step 404 the base station acquires a correspondence between the QFI and the downlink processing attribute.
  • QFI is a unique identifier of a QoS Flow, and each terminal corresponds to multiple QoS Flows.
  • the corresponding relationship between the QFI and the downlink processing attributes includes at least the following: the downlink processing attribute corresponding to the QFI supports the NAS Reflective QoS function, the downlink processing attribute corresponding to the QFI supports the AS Reflective QoS function, and the downlink processing attribute corresponding to the QFI does not support the NAS. Reflective QoS and does not support AS Reflective QoS.
  • the downlink processing attribute corresponding to the QFI of the core network supports the NAS Reflective QoS function.
  • the base station obtains the corresponding downlink processing attribute from the core network to the QFI that supports the NAS Reflective QoS function
  • the QFI and the supported NAS Reflective QoS function are used as one.
  • the group correspondence is added to the corresponding relationship between the QFI and the downlink processing attribute.
  • the downlink processing attribute corresponding to the base station configuration is the QFI that supports the AS Reflective QoS function
  • the QFI and the supported AS Reflective QoS function are added to the QFI as a set of correspondences.
  • the corresponding relationship between the downlink processing attributes and the corresponding unconfigured downlink attributes are the QFIs that support the NAS Reflective QoS function and the AS Reflective QoS function, and the NAS Reflective QoS function that does not support the AS Reflective QoS function.
  • the relationship is added to the correspondence between the QFI and the downstream processing attribute.
  • the base station configures a correspondence between the QFI and the DRB according to the correspondence between the QFI and the downlink processing attribute and the correspondence between the DRB and the downlink processing attribute.
  • one DRB corresponds to multiple QFIs.
  • the downlink processing attribute corresponding to the DRB includes the NAS Reflective QoS function
  • the downlink processing attribute of the DRB includes the AS Reflective QoS function
  • the multiple QFIs corresponding to the DRB include at least one QFI that supports the AS Reflective QoS function.
  • step 405 the base station sends a correspondence between the QFI and the downlink processing attribute to the terminal.
  • the terminal receives and stores a correspondence between the QFI and the downlink processing attribute sent by the base station.
  • the base station sends a correspondence between the QFI and the downlink processing attribute to the terminal by using an RRC configuration message.
  • the terminal receives the correspondence between the QFI and the downlink processing attribute sent by the base station through the RRC configuration message.
  • step 406 the base station sends the encapsulated downlink data packet to the terminal.
  • the terminal receives the downlink data packet sent by the base station.
  • step 407 the terminal determines, according to the correspondence between the pre-configured DRB and the downlink processing attribute, the target downlink processing attribute corresponding to the target DRB that transmits the downlink data packet.
  • step 408 if the target downlink processing attribute supports the NAS Reflective QoS function or supports the AS Reflective QoS function, the terminal determines that the downlink data packet is encapsulated with the SDAP header; if the target downlink processing attribute does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function, the terminal determines that the downlink data packet is not encapsulated with the SDAP header.
  • step 409 the downlink data packet is processed based on whether the determined downlink data packet is encapsulated with a SDAP packet header.
  • FIG. 4B is a flowchart of a method for processing a downlink data packet by a terminal according to an exemplary embodiment. As shown in FIG. 4B, in a possible manner, if it is determined that a downlink data packet is encapsulated with a SDAP packet header, the terminal is configured.
  • the method for processing the downlink data packet includes the following steps.
  • step 409a the SDAP packet header of the downlink data packet is parsed to obtain a QFI field carried in the SDAP packet header.
  • the QFI field carried in the SDAP header of the downlink packet is the QFI corresponding to the QoS Flow of the downlink packet.
  • step 409b the downlink processing attribute corresponding to the QFI carried by the SDAP packet header is determined according to the correspondence between the QFI and the downlink processing attribute.
  • the terminal can only determine that the downlink data packet is encapsulated with the SDAP header, but cannot determine the downlink data packet.
  • the downlink processing attribute supports the NAS Reflective QoS function or the AS Reflective QoS function. Therefore, after the terminal parses the SDAP header of the downlink packet and obtains the QFI field carried in the SDAP header, the SDAP can be determined according to the correspondence between the QFI and the downlink processing attribute.
  • the downlink processing attribute of the downlink packet corresponding to the QFI carried by the packet header.
  • step 409c if the downlink processing attribute corresponding to the QFI supports the NAS Reflective QoS function, the downlink data packet is processed in the NAS layer.
  • the downlink processing attribute corresponding to the QFI carried in the SDAP packet header of the downlink data packet supports the NAS Reflective QoS function
  • the downlink data packet supports the NAS Reflective QoS function
  • the terminal may extract the RQI field and the QFI field from the SDAP packet header, and The RQI field and the QFI field are submitted to the NAS layer, and the downlink layer is used by the NAS layer according to the RQI field and the QFI field. Processing is performed, and the processed downlink data packet is sent to the application layer.
  • step 409d if the downlink processing attribute corresponding to the QFI supports the AS Reflective QoS function, the downlink data packet is processed in the AS layer.
  • the downlink processing attribute of the QFI carried in the SDAP packet header of the downlink data packet is the AS Reflective QoS function
  • the downlink data packet supports the AS Reflective QoS function
  • the terminal parses the SDAP packet header of the downlink data packet to obtain the indication information.
  • the terminal first obtains the QFI field in the header of the SDAP packet, and then processes the downlink data packet according to the QFI field at the AS layer, and sends the processed downlink data packet to the application layer.
  • the steps 401 to 403 are respectively corresponding to the steps 301 to 303, and the steps 406 to 408 are similar to the steps 304 to 306, respectively. Steps 406 to 408 are described in detail.
  • the downlink data packet configuration method adds a SDAP packet header only to a downlink data packet whose downlink processing attribute is a NAS Reflective QoS function or an AS Reflective QoS function, because the base station does not process the downlink processing attribute.
  • Adding a SDAP header to a downlink packet that does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function solves the problem in the prior art that each sublayer of the AS layer should be down, regardless of the downlink processing attribute of the downlink packet.
  • the data packet is encapsulated and decapsulated, which occupies the problem of increasing the processing resources of the device, and achieves the effect of reducing the occupation of the processing resources of the device.
  • the original base station when the terminal performs base station handover to the target base station, the original base station sends configuration information related to the terminal in the original base station to the target base station, and improves the target base station to configure the target base station and the terminal. The efficiency of related configuration information.
  • FIG. 5 is a flowchart of a method for configuring a correspondence relationship according to an exemplary embodiment. As shown in FIG. 5, the correspondence configuration method is applied to the mobile communication system shown in FIG. 1, and the method includes the following steps.
  • Step 501 When the terminal performs base station handover to the target base station, the base station sends the first configuration information corresponding to the terminal to the target base station.
  • the first configuration information includes a correspondence between the QFI and the downlink processing attribute, and/or a correspondence between the DRB and the downlink processing attribute.
  • the base station is handed over to the target base station; in the scenario where the terminal is simultaneously connected to two or even multiple base stations, the target base station is sent to the target terminal. Downlink data, the terminal may switch from the base station to the target base station.
  • Step 502 The base station receives the second configuration information that is set by the target base station according to the first configuration information, and sends the second configuration information to the terminal.
  • the target server uses the first configuration information in the process of setting the second configuration information, or modifies the first configuration information according to the information about the service load, the QoS guarantee, and the like to obtain the second configuration information.
  • the corresponding downlink attribute is configured by the core network to support the NAS Reflective QoS function. Therefore, after receiving the first configuration information that carries the corresponding relationship between the QFI and the downlink processing attribute, the target base station can directly use the corresponding
  • the downlink attribute supports the QFI-related configuration information of the NAS Reflective QoS function, and the QFI-related configuration information of the downlink attribute supporting the NAS Reflective QoS function is added to the second configuration information.
  • a DRB corresponds to multiple QFIs
  • the target base station may Change the number of QFIs for each DRB.
  • the processing attributes corresponding to the part of the DRB are modified from the supported AS Reflective QoS function to support the NAS Reflective QoS function and support the AS Reflective QoS function, or part of the DRB.
  • the corresponding processing attribute is modified to support the NAS Reflective QoS function by supporting the AS Reflective QoS function, thereby obtaining the second configuration information.
  • the terminal receives and stores the second configuration information sent by the base station.
  • the second configuration information includes a correspondence between a QFI and a downlink processing attribute corresponding to the target base station, and a correspondence between the DRB and the downlink processing attribute corresponding to the target base station.
  • the downlink data packet configuration method adds a SDAP packet header only to a downlink data packet whose downlink processing attribute is a NAS Reflective QoS function or an AS Reflective QoS function, because the base station does not process the downlink processing attribute.
  • Adding a SDAP header to a downlink packet that does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function solves the problem in the prior art that each sublayer of the AS layer should be down, regardless of the downlink processing attribute of the downlink packet.
  • the data packet is encapsulated and decapsulated, which occupies the problem of increasing the processing resources of the device, and achieves the effect of reducing the occupation of the processing resources of the device.
  • the original base station when the terminal performs base station handover to the target base station, the original base station will The configuration information related to the terminal is sent to the target base station, and the efficiency of configuring the configuration information related to the terminal in the target base station by the target base station is improved.
  • FIG. 6 is a block diagram of a downlink packet configuration apparatus according to an exemplary embodiment. As shown in FIG. 6, the downlink packet configuration apparatus is applied to a base station in the mobile communication system shown in FIG.
  • the packet configuration device includes but is not limited to: a first determining module 601, a second determining module 602, a processing module 603, and a first sending module 604.
  • the first determining module 601 is configured to determine a target data bearer DRB corresponding to the downlink data packet to be sent;
  • the second determining module 602 is configured to determine, according to the mapping between the stored DRB and the downlink processing attribute, the target downlink processing attribute corresponding to the target DRB, where the downlink processing attribute includes whether the NAS Reflective QoS function is supported, and whether the AS Reflective is supported. QoS function;
  • the processing module 603 is configured to add a service data assimilation protocol (SDAP) header in the process of encapsulating the downlink data packet if the target downlink processing attribute is to support the NAS Reflective QoS function or the AS Reflective QoS function; if the target downlink processing attribute is not supported The NAS Reflective QoS function does not support the AS Reflective QoS function.
  • SDAP service data assimilation protocol
  • the first sending module 604 is configured to send the encapsulated downlink data packet to the terminal.
  • the processing module 603 includes: a first adding unit 603a and a second adding unit 603b.
  • the first adding unit 603a is configured to add a SDAP packet header in the process of encapsulating the downlink data packet, and add an RQI field and a data flow identifier QFI field in the SDAP packet header, if the target downlink processing attribute is a NAS reflective QoS function.
  • the second adding unit 603b is configured to add a SDAP packet header in the process of encapsulating the downlink data packet, and add the indication information and the QFI field in the SDAP packet header, if the target downlink processing attribute is only supporting the AS Reflective QoS function, where the indication is Information is used to indicate whether the SDAP header is included Contains the QFI field.
  • the length of the RQI field is 1 bit, and the length of the QFI field is 7 bits.
  • the device further includes: a second sending module.
  • the second sending module is configured to send a correspondence between the DRB and the downlink processing attribute to the terminal before the downlink data packet is sent to the terminal, and the terminal stores the correspondence between the DRB and the downlink processing attribute.
  • the second sending module is further configured to:
  • the correspondence between the DRB and the downlink processing attribute is sent to the terminal through the RRC configuration message.
  • the device further includes:
  • the acquiring module is configured to obtain a correspondence between the QFI and the downlink processing attribute before sending the encapsulated downlink data packet to the terminal;
  • the third sending module is configured to send a correspondence between the QFI and the downlink processing attribute to the terminal, and the terminal stores the correspondence between the QFI and the downlink processing attribute.
  • the device further includes:
  • the fourth sending module is configured to: when the terminal performs the base station handover to the target base station, send the first configuration information corresponding to the terminal to the target base station, where the first configuration information includes a correspondence between the QFI and the downlink processing attribute, and/or the DRB and the Corresponding relationship of downlink processing attributes;
  • the fifth sending module is configured to receive the second configuration information that is set by the target base station according to the first configuration information, and send the second configuration information to the terminal, where the terminal stores the second configuration information, where the second configuration information includes the QFI corresponding to the target base station.
  • the downlink data packet configuration apparatus adds a SDAP packet header only to a downlink data packet whose downlink processing attribute is a NAS Reflective QoS function or an AS Reflective QoS function, because the base station does not process the downlink processing attribute.
  • Adding a SDAP header to a downlink packet that does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function solves the problem in the prior art that each sublayer of the AS layer should be down, regardless of the downlink processing attribute of the downlink packet.
  • the data packet is encapsulated and decapsulated, which occupies the problem of increasing the processing resources of the device, and achieves the effect of reducing the occupation of the processing resources of the device.
  • FIG. 7 is a block diagram of a downlink packet configuration apparatus according to an exemplary embodiment. As shown in FIG. 7, the downlink packet configuration apparatus is applied to a terminal in the mobile communication system shown in FIG.
  • the downlink data packet configuration apparatus includes, but is not limited to, a first receiving module 701, a determining module 702, a processing module 703, and a transparent transmission module 704.
  • the first receiving module 701 is configured to receive a downlink data packet sent by the base station;
  • the first determining module 702 is configured to determine, according to the correspondence between the pre-configured DRB and the downlink processing attribute, a target downlink processing attribute corresponding to the target DRB that transmits the downlink data packet, where the downlink processing attribute is whether to support non-access reflection Quality of Service NAS Reflective QoS function, and whether it supports access reflection quality of service AS Reflective QoS function;
  • the second determining module 703 is configured to: if the target downlink processing attribute supports the NAS Reflective QoS function or the AS Reflective QoS function, determine that the downlink data packet is encapsulated with a SDAP header; if the target downlink processing attribute does not support the NAS Reflective QoS function, If the AS Reflective QoS function is not supported, it is determined that the downlink data packet is not encapsulated with the SDAP header.
  • the processing module 704 is configured to process the downlink data packet based on whether the determined downlink data packet is encapsulated with a SDAP packet header.
  • the processing module 704 includes: a first parsing unit, a first processing unit, and a second processing unit.
  • a first parsing unit configured to parse a SDAP header of the downlink packet
  • the first processing unit is configured to process the downlink data packet in the NAS layer if the SDAP packet header carries the RQI field and the QFI field;
  • the second processing unit is configured to process the downlink data packet in the AS layer if the SDAP packet header carries the indication information and the QFI field.
  • the length of the RQI field is 1 bit, and the length of the QFI field is 7 bits.
  • the device further includes: a storage module.
  • the storage module is configured to receive a correspondence between the DRB and the downlink processing attribute sent by the base station before receiving the downlink data packet sent by the base station, and store the correspondence between the DRB and the downlink processing attribute.
  • the storage module is further configured to:
  • the device further includes:
  • the second receiving module is configured to receive and store a correspondence between the QFI and the downlink processing attribute sent by the base station before receiving the downlink data packet sent by the base station;
  • the processing module further includes:
  • a second parsing unit configured to parse the SDAP header of the downlink data packet to obtain a QFI field carried in the SDAP packet header
  • a determining unit configured to determine, according to a correspondence between the QFI and the downlink processing attribute, a downlink processing attribute corresponding to the QFI carried by the SDAP packet header;
  • the third processing unit is configured to process the downlink data packet in the NAS layer if the downlink processing attribute corresponding to the QFI is the NAS Reflective QoS function;
  • the fourth processing unit is configured to process the downlink data packet in the AS layer if the downlink processing attribute corresponding to the QFI supports the AS Reflective QoS function.
  • the device further includes:
  • the third receiving module is configured to receive and store the second configuration information sent by the base station, where the second configuration information is obtained by the base station after the first configuration information corresponding to the terminal is sent to the target base station, when the predetermined condition is met. information;
  • the first configuration information includes a correspondence between the QFI and the downlink processing attribute, and/or a correspondence between the DRB and the downlink processing attribute, where the second configuration information includes at least a correspondence between the QFI and the downlink processing attribute corresponding to the target base station, and the target base station. Correspondence between the corresponding DRB and the downlink processing attribute.
  • the downlink data packet configuration apparatus adds a SDAP packet header only to a downlink data packet whose downlink processing attribute is a NAS Reflective QoS function or an AS Reflective QoS function, because the base station does not process the downlink processing attribute.
  • Adding a SDAP header to a downlink packet that does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function solves the problem in the prior art that each sublayer of the AS layer should be down, regardless of the downlink processing attribute of the downlink packet.
  • the data packet is encapsulated and decapsulated, which occupies the problem of increasing the processing resources of the device, and achieves the effect of reducing the occupation of the processing resources of the device.
  • An exemplary embodiment of the present application provides a base station, which can implement a downlink data packet configuration method provided by the present application, where the user equipment includes: a processor, a memory for storing processor executable instructions;
  • processor is configured to:
  • the target DRB Determining the target DRB according to the correspondence between the pre-configured DRB and the downlink processing attribute Target downlink processing attribute, wherein the downlink processing attribute includes a QoS function that supports non-access reflection, and a service quality AS Reflective QoS function that supports access reflection;
  • the target downlink processing attribute supports the NAS Reflective QoS function or supports the AS Reflective QoS function, add the service data assimilation protocol SDAP header in the process of encapsulating the downlink data packet; if the target downlink processing attribute does not support the NAS Reflective QoS function and does not support The AS Reflective QoS function does not add a SDAP header during the process of encapsulating downstream packets.
  • the encapsulated downlink data packet is sent to the terminal.
  • An exemplary embodiment of the present application provides a terminal that can implement the state maintaining method provided by the application, where the user equipment includes: a processor, a memory for storing processor executable instructions;
  • processor is configured to:
  • the downlink processing attribute includes whether to support the non-access reflection quality of service NAS Reflective QoS function, and whether Supports access reflection quality of service AS Reflective QoS function;
  • the target downlink processing attribute supports the NAS Reflective QoS function or supports the AS Reflective QoS function, it is determined that the downlink data packet is encapsulated with the SDAP header; if the target downlink processing attribute does not support the NAS Reflective QoS function and does not support the AS Reflective QoS function, The downlink packet is not encapsulated with a SDAP header;
  • the downlink data packet is processed based on whether the determined downlink data packet is encapsulated with a SDAP packet header.
  • FIG. 8 is a block diagram of a terminal, according to an exemplary embodiment.
  • the terminal 800 is implemented as the terminal 120 in FIG.
  • terminal 800 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • terminal 800 can include one or more of the following components: processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and Communication component 816.
  • Processing component 802 typically controls the overall operation of terminal 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 802 can include one or more processors 818 to execute instructions to perform all or part of the steps described above.
  • processing component 802 can include one or more modules to facilitate interaction between component 802 and other components.
  • processing component 802 can include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
  • Memory 804 is configured to store various types of data to support operation at terminal 800. Examples of such data include instructions for any application or method operating on terminal 800, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 804 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Electrically erasable programmable read only memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power component 806 provides power to various components of terminal 800.
  • Power component 806 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for terminal 800.
  • the multimedia component 808 includes a screen that provides an output interface between the terminal 800 and the user.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can sense not only the boundaries of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 808 includes a front camera and/or a rear camera. When the terminal 800 is in an operation mode such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 810 is configured to output and/or input an audio signal.
  • the audio component 810 includes a microphone (MIC) that is configured to receive an external audio signal when the terminal 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in memory 804 or transmitted via communication component 816.
  • the audio component 810 also includes a speaker for outputting an audio signal.
  • the I/O interface 812 provides an interface between the processing component 802 and the peripheral interface module, the peripheral connection
  • the port module can be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 814 includes one or more sensors for providing terminal 800 with various aspects of status assessment.
  • sensor component 814 can detect an open/closed state of terminal 800, a relative positioning of components, such as a display and a keypad of terminal 800, and sensor component 814 can also detect a change in position of a component of terminal 800 or terminal 800, the user The presence or absence of contact with the terminal 800, the orientation or acceleration/deceleration of the terminal 800 and the temperature change of the terminal 800.
  • Sensor assembly 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 814 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communication between terminal 800 and other devices.
  • the terminal 800 can access a wireless network based on a communication standard such as Wi-Fi, 2G or 3G, or a combination thereof.
  • communication component 816 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • communication component 816 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • terminal 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), a controller, a microcontroller, a microprocessor, or other electronic component implementation is used to perform the downlink packet configuration method provided by the foregoing method embodiments.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller a controller
  • microcontroller a microcontroller
  • microprocessor or other electronic component implementation is used to perform the downlink packet configuration method provided by the foregoing method embodiments.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 804 comprising instructions executable by processor 818 of terminal 800 to perform the downstream packet configuration method described above.
  • the non-transitory computer readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.
  • FIG. 9 is a block diagram of a base station according to an exemplary embodiment.
  • the base station 900 is implemented as the base station 140 of FIG. Specifically:
  • the base station 900 includes a central processing unit (CPU) 901 including random access memory (RAM) System memory 904 of 902 and read only memory (ROM) 903, and system bus 905 connecting system memory 904 and central processing unit 901.
  • CPU central processing unit
  • RAM random access memory
  • ROM read only memory
  • system bus 905 connecting system memory 904 and central processing unit 901.
  • the base station 900 also includes a basic input/output system (I/O system) 906 that facilitates transfer of information between various devices within the computer, and mass storage for storing the operating system 913, applications 914, and other program modules 915.
  • I/O system basic input/output system
  • the basic input/output system 906 includes a display 908 for displaying information and an input device 909 such as a mouse or keyboard for user input of information. Both the display 908 and the input device 909 are connected to the central processing unit 901 via an input and output controller 910 that is coupled to the system bus 905.
  • the basic input/output system 906 can also include an input output controller 910 for receiving and processing input from a plurality of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input and output controller 910 also provides output to a display screen, printer, or other type of output device.
  • the mass storage device 907 is connected to the central processing unit 901 by a mass storage controller (not shown) connected to the system bus 905.
  • the mass storage device 907 and its associated computer readable medium provide non-volatile storage for the base station 900. That is, the mass storage device 907 can include a computer readable medium (not shown) such as a hard disk or a CD-ROM drive.
  • the computer readable medium can include computer storage media and communication media.
  • Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
  • Computer storage media include RAM, ROM, EPROM, EEPROM, flash memory or other solid state storage technologies, CD-ROM, DVD or other optical storage, tape cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices.
  • RAM random access memory
  • ROM read only memory
  • EPROM Erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • the base station 900 can also be operated by a remote computer connected to the network through a network such as the Internet. That is, the base station 900 can be connected to the network 912 through a network interface unit 911 connected to the system bus 905, or can be connected to other types of networks or remote computer systems (not shown) using the network interface unit 911. .
  • the memory further includes one or more programs, the one or more programs being stored in a memory, the one or more programs including instructions for performing a sound effect evaluation display method provided by an embodiment of the present invention.
  • the program may be stored in a computer readable storage medium.
  • the storage medium may include a read only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 904 comprising instructions executable by processor 918 of user equipment 900 to perform the above described downstream data packet configuration method .
  • the non-transitory computer readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.

Abstract

本申请揭示了一种下行数据包配置方法及装置，属于通信技术领域。方法包括：确定待发送的下行数据包对应的目标数据承载DRB；根据配置的DRB与处理属性的对应关系，确定目标DRB对应的目标下行处理属性；如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则在封装下行数据包的过程中添加服务数据同化协议SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则在封装下行数据包的过程中不添加SDAP包头。解决了占用设备大量的处理资源的问题，达到了节省设备的处理资源的效果。

Description

下行数据包配置方法及装置 技术领域
本申请涉及通信技术领域，特别涉及一种下行数据包配置方法及装置。
背景技术
第四代移动通信(4h-Generation，4G)技术是将通信过程分为非接入(Non-Access Stratum，NAS)层和接入(Access Stratum，AS)层。其中，AS层中主要包括四个子层，由上至下依次是分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路控制(Radio Link Control，RLC)层、媒体接入控制(MediaAccess Control，MAC)层以及以物理(Physical Layer，PHY)层。
随着对第五代移动通信(5th-Generation，5G)技术中的深入研究，AS层中除了上述四个子层之外，在PDCP层之上引入了一个新的子层，即服务数据同化协议(Service DataAdaptation Protocol，SDAP)层。SDAP层用于实现数据流与数据承载(Data Radio Bearer，DRB)间的映射，即为数据流分配DRB，以通过映射后的DRB传输数据包。SDAP层还会对为数据包添加数据流标识(QOS Flow ID，QFI)，以便终端确定该数据包所映射的DRB。
相关技术中，AS层的每一个子层都要对下行数据包进行封装和解封装，这样，会占用设备大量的处理资源。
发明内容
为了解决占用设备大量的处理资源的问题，本公开提供一种下行数据包配置方法及装置。所述技术方案如下：
根据本申请实施例的第一方面，提供一种下行数据包配置方法，应用于基站，所述方法包括：
确定待发送的下行数据包对应的目标数据承载DRB；
根据预先配置的DRB与处理属性的对应关系，确定所述目标DRB对应的目标下行处理属性，其中，所述下行处理属性包括是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能；
如果所述目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则在封装所述下行数据包的过程中添加服务数据同化协议SDAP包头；如果所述目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则在封装所述下行数据包的过程中不添加SDAP包头；
向所述终端发送封装后的下行数据包。
可选地，所述在封装所述下行数据包的过程中添加服务数据同化协议SDAP包头，包括：
如果所述目标下行处理属性为支持NAS Reflective QoS功能，则在封装所述下行数据包的过程中添加SDAP包头，并在所述SDAP包头中添加RQI字段和数据流标识QFI字段；
如果所述目标下行处理属性为仅支持AS Reflective QoS功能，则在封装所述下行数据包的过程中添加SDAP包头，并在所述SDAP包头中添加指示信息和QFI字段，其中，所述指示信息用于指示所述SDAP包头中是否包含QFI字段。
可选地，所述RQI字段的长度为1个比特，所述QFI字段的长度为7个比特。
可选地，所述向终端发送所述下行数据包之前，所述方法还包括：
向所述终端发送所述DRB与下行处理属性的对应关系，由所述终端对所述DRB与下行处理属性的对应关系进行存储。
可选地，所述向所述终端发送所述DRB与下行处理属性的对应关系，包括：
通过RRC配置消息，向所述终端发送所述DRB与下行处理属性的对应关系。
可选地，所述向所述终端发送封装后的下行数据包之前，所述方法还包括：
获取QFI与下行处理属性的对应关系；
向所述终端发送所述QFI与下行处理属性的对应关系，由所述终端存储所述QFI与下行处理属性的对应关系。
可选地，所述方法还包括：
当满足预定条件时，将所述终端对应的第一配置信息发送至目标基站，所述第一配置信息包括所述QFI与下行处理属性的对应关系、和/或所述DRB与 所述下行处理属性的对应关系；
接收所述目标基站根据所述第一配置信息设置的第二配置信息，将所述第二配置信息发送至所述终端，由所述终端存储所述第二配置信息，所述第二配置信息包括所述目标基站对应的QFI与下行处理属性的对应关系、以及所述目标基站对应的DRB与所述下行处理属性的对应关系。
根据本申请实施例的第二方面，提供一种下行数据包配置方法，应用于终端，所述方法包括：
接收基站发送的下行数据包；
根据预先配置的DRB与下行处理属性的对应关系，确定传输所述下行数据包的目标DRB对应的目标下行处理属性，其中，所述下行处理属性包括是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能；
如果所述目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则确定所述下行数据包封装有SDAP包头；如果所述目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则确定所述下行数据包未封装有SDAP包头；
基于确定出的所述下行数据包是否封装有SDAP包头的情况，对所述下行数据包进行处理。
可选地，如果确定出所述下行数据包封装有SDAP包头的情况，所述对所述下行数据包进行处理，包括：
解析所述下行数据包的SDAP包头；
如果所述SDAP包头携带有RQI字段和QFI字段，则在NAS层中处理所述下行数据包；
如果所述SDAP包头携带有指示信息和QFI字段，则在AS层中处理所述下行数据包，其中，所述指示信息用于指示所述SDAP包头中是否包含QFI字段。
可选地，所述RQI字段的长度为1个比特，所述QFI字段的长度为7个比特。
可选地，所述接收基站发送的下行数据包之前，所述方法还包括：
接收所述基站发送的所述DRB与下行处理属性的对应关系，对所述DRB与下行处理属性的对应关系进行存储。
可选地，所述接收所述基站发送的所述DRB与下行处理属性的对应关系，包括：
接收所述基站通过RRC配置消息发送的所述DRB与下行处理属性的对应关系。
可选地，所述接收基站发送的下行数据包之前，所述方法还包括：
接收并存储所述基站发送的QFI与下行处理属性的对应关系；
如果确定出所述下行数据包封装有SDAP包头，所述对所述下行数据包进行处理，包括：
解析所述下行数据包的SDAP包头，得到所述SDAP包头中携带的QFI字段；
根据所述QFI与下行处理属性的对应关系，确定所述SDAP包头携带的QFI对应的下行处理属性；
如果所述QFI对应的下行处理属性为支持NAS Reflective QoS功能，则在NAS层中处理所述下行数据包；
如果所述QFI对应的下行处理属性为支持AS Reflective QoS功能，则在AS层中处理所述下行数据包。
可选地，所述方法还包括：
接收并存储所述基站发送的第二配置信息，所述第二配置信息为当满足预定条件时，所述基站将所述终端对应的第一配置信息发送至目标基站后，从所述目标基站获取的信息；
其中，所述第一配置信息包括所述QFI与下行处理属性的对应关系、和/或所述DRB与所述下行处理属性的对应关系，所述第二配置信息至少包括所述目标基站对应的QFI与下行处理属性的对应关系、以及所述目标基站对应的DRB与所述下行处理属性的对应关系。
根据本申请实施例的第三方面，提供一种下行数据包配置装置，应用于基站，所述装置包括：
第一确定模块，被配置为确定待发送的下行数据包对应的目标数据承载DRB；
第二确定模块，被配置为根据配置存储的DRB与处理属性的对应关系，确定所述目标DRB对应的目标下行处理属性，其中，所述下行处理属性包括是否支持NAS Reflective QoS功能、以及是否支持AS Reflective QoS功能；
处理模块，被配置为如果所述目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则在封装所述下行数据包的过程中添加服务数据同化协议SDAP包头；如果所述目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则在封装所述下行数据包的过程中不添加SDAP包头；
第一发送模块，被配置为向所述终端发送封装后的下行数据包。
可选地，所述处理模块，包括：
第一添加单元，被配置为如果所述目标下行处理属性为支持NAS Reflective QoS功能，则在封装所述下行数据包的过程中添加SDAP包头，并在所述SDAP包头中添加RQI字段和数据流标识QFI字段；
第二添加单元，被配置为如果所述目标下行处理属性为仅支持AS Reflective QoS功能，则在封装所述下行数据包的过程中添加SDAP包头，并在所述SDAP包头中添加指示信息和QFI字段，其中，所述指示信息用于指示所述SDAP包头中是否包含QFI字段。
可选地，所述RQI字段的长度为1个比特，所述QFI字段的长度为7个比特。
可选地，所述装置还包括：
第二发送模块，被配置为所述向终端发送所述下行数据包之前，向所述终端发送所述DRB与下行处理属性的对应关系，由所述终端对所述DRB与下行处理属性的对应关系进行存储。
可选地，所述第二发送模块，还被配置为：
通过RRC配置消息，向所述终端发送所述DRB与下行处理属性的对应关系。
可选地，所述装置还包括：
获取模块，被配置为所述向所述终端发送封装后的下行数据包之前，获取QFI与下行处理属性的对应关系；
第三发送模块，被配置为向所述终端发送所述QFI与下行处理属性的对应关系，由所述终端存储所述QFI与下行处理属性的对应关系。
可选地，所述装置还包括：
第四发送模块，被配置为当所述终端向所述目标基站进行基站切换时，将所述终端对应的第一配置信息发送至目标基站，所述第一配置信息包括所述 QFI与下行处理属性的对应关系、和/或所述DRB与所述下行处理属性的对应关系；
第五发送模块，被配置为接收所述目标基站根据所述第一配置信息设置的第二配置信息，将所述第二配置信息发送至所述终端，由所述终端存储所述第二配置信息，所述第二配置信息包括所述目标基站对应的QFI与下行处理属性的对应关系、以及所述目标基站对应的DRB与所述下行处理属性的对应关系。
根据本申请实施例的第四方面，提供一种下行数据包配置装置，应用于终端，所述装置包括：
第一接收模块，被配置为接收基站发送的下行数据包；
第一确定模块，被配置为根据预先配置的DRB与下行处理属性的对应关系，确定传输所述下行数据包的目标DRB对应的目标下行处理属性，其中，所述下行处理属性为是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能；
第二确定模块，被配置为如果所述目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则确定所述下行数据包封装有SDAP包头；如果所述目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则确定所述下行数据包未封装有SDAP包头；
处理模块，被配置为基于确定出的所述下行数据包是否封装有SDAP包头的情况，对所述下行数据包进行处理。
可选地，如果确定出所述下行数据包封装有SDAP包头的情况，所述处理模块，包括：
第一解析单元，被配置为解析所述下行数据包的SDAP包头；
第一处理单元，被配置为如果所述SDAP包头携带有RQI字段和QFI字段，则在NAS层中处理所述下行数据包；
第二处理单元，被配置为如果所述SDAP包头携带有指示信息和QFI字段，则在AS层中处理所述下行数据包。
可选地，所述RQI字段的长度为1个比特，所述QFI字段的长度为7个比特。
可选地，所述装置还包括：
存储模块，被配置为所述接收基站发送的下行数据包之前，接收所述基站 发送的所述DRB与下行处理属性的对应关系，对所述DRB与下行处理属性的对应关系进行存储。
可选地，所述存储模块，还被配置为：
接收所述基站通过RRC配置消息发送的所述DRB与下行处理属性的对应关系。
可选地，所述装置还包括：
第二接收模块，被配置为所述接收基站发送的下行数据包之前，接收并存储所述基站发送的QFI与下行处理属性的对应关系；
如果确定出所述下行数据包封装有SDAP包头，所述处理模块，还包括：
第二解析单元，被配置为解析所述下行数据包的SDAP包头，得到所述SDAP包头中携带的QFI字段；
确定单元，被配置为根据所述QFI与下行处理属性的对应关系，确定所述SDAP包头携带的QFI对应的下行处理属性；
第三处理单元，被配置为如果所述QFI对应的下行处理属性为支持NAS Reflective QoS功能，则在NAS层中处理所述下行数据包；
第四处理单元，被配置为如果所述QFI对应的下行处理属性为支持AS Reflective QoS功能，则在AS层中处理所述下行数据包。
可选地，所述装置还包括：
第三接收模块，被配置为接收并存储所述基站发送的第二配置信息，所述第二配置信息为当满足预定条件时，所述基站将所述终端对应的第一配置信息发送至目标基站后，从所述目标基站获取的信息；
其中，所述第一配置信息包括所述QFI与下行处理属性的对应关系、和/或所述DRB与所述下行处理属性的对应关系，所述第二配置信息至少包括所述目标基站对应的QFI与下行处理属性的对应关系、以及所述目标基站对应的DRB与所述下行处理属性的对应关系。
根据本申请实施例的第五方面，提供一种基站，所述基站包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如本申请实施例的第一方面所述的下行数据包配置方法。
根据本申请实施例的第六方面，提供一种计算机可读存储介质，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条 指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如本申请实施例的第一方面所述的下行数据包配置方法。
根据本申请实施例的第七方面，提供一种终端，所述终端包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如本申请实施例的第二方面所述的下行数据包配置方法。
根据本申请实施例的第八方面，提供一种计算机可读存储介质，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如本申请实施例的第二方面所述的下行数据包配置方法。
本申请实施例提供的技术方案可以包括以下有益效果：
通过仅对下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能的下行数据包添加SDAP包头，由于基站不对下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能的下行数据包添加SDAP包头，解决了现有技术中，无论下行数据包是何下行处理属性，AS层的每一个子层都要对下行数据包进行封装和解封装，占用设备大量的处理资源的增加问题，达到了降低设备的处理资源的占用的效果。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性的，并不能限制本申请。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请的实施例，并与说明书一起用于解释本申请的原理。
图1是本申请一个示例性实施例示出的移动通信系统的协议架构图；
图2是根据一示例性实施例示出的一种下行数据包配置方法的方法流程图；
图3A是根据另一示例性实施例示出的一种下行数据包配置方法的方法流程图；
图3B是根据一示例性实施例示出的目标下行处理属性为支持NAS Reflective QoS功能的下行数据包的结构图；
图3C是根据一示例性实施例示出的目标下行处理属性为仅支持AS  Reflective QoS功能的下行数据包的结构图；
图3D是根据一示例性实施例示出的终端对下行数据包进行处理方法的方法流程图；
图4A是根据再一示例性实施例示出的一种下行数据包配置方法的方法流程图；
图4B是根据一示例性实施例示出的终端对下行数据包进行处理方法的方法流程图；
图5是根据一示例性实施例示出的对应关系配置方法的方法流程图；
图6是根据一示例性实施例示出的一种下行数据包配置装置的框图；
图7是根据一示例性实施例示出的一种下行数据包配置装置的框图；
图8是根据一示例性实施例示出的一种终端的框图；
图9是根据一示例性实施例示出的一种基站的框图。
具体实施方式
本文所提及的“第一”、“第二”以及类似的词语并不表示任何顺序、数量或者重要性，而只是用来区分不同的组成部分。同样，“一个”或者“一”等类似词语也不表示数量限制，而是表示存在至少一个。“连接”或者“相连”等类似的词语并非限定于物理的或者机械的连接，而是可以包括电性的连接，不管是直接的还是间接的。
在本文提及的“模块”通常是指存储在存储器中的能够实现某些功能的程序或指令；在本文中提及的“单元”通常是指按照逻辑划分的功能性结构，该“单元”可以由纯硬件实现，或者，软硬件的结合实现。
在本文中提及的“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
为使本公开的目的、技术方案和优点更加清楚，下面将结合附图对本公开实施方式作进一步地详细描述。
本发明实施例提供了一种下行数据包配置方法，该方法可以由终端和基站配合实现。其中，终端是指与基站进行数据通信的设备。终端可以经无线接入 网(RadioAccess Network，RAN)与一个或多个核心网进行通信，终端还可以称为订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、接入点(Access Point)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户装置(User Terminal)、用户代理(UserAgent)、终端(User Device)。可选地，终端还可以为中继(Relay)设备，本实施例对此不作限定。
终端和基站之间通过无线空口建立无线连接。可选地，该无线空口是基于5G标准的无线空口，比如该无线空口是新空口(New Radio，NR)；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术的无线空口。可选地，该无线空口还兼容2G、3G和4G等更早代移动通信网络技术的无线空口。
该基站可用于将接收到的无线帧与IP分组报文进行相互转换，还可协调对空中接口的属性管理。例如，基站可以是5G系统中的基站(gNode-B，gNB)。可选地，该gNB是采用集中分布式架构的基站。当接入网设备140采用集中分布式架构时，通常包括集中单元(Central Unit，CU)和至少两个分布单元(Distributed Unit，DU)。集中单元中设置服务数据同化协议(Service Data Adaptation Protocol，SDAP)、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层和媒体访问控制(MediaAccess Control，MAC)层的协议栈，本实施例对接入网设备140的具体实现方式不加以限定。
需要说明的是，图1是本申请一个示例性实施例示出的移动通信系统的协议架构图。该协议架构中涉及的设备包括：终端120和基站140。如图1所示，在5G技术中，通信底层架构中包括的层由上至下依次是应用层、NAS和AS层，其中，AS层包括SDAP层、PDCP层、RLC层、MAC层以及PHY层。当终端120建立与基站140的会话时，可以在会话的过程中传输多条数据流，各数据流中可以包含多个数据包，数据包在终端120的通信底层架构中从上至下依次递交，直至通过最后一层向基站140发出。这些数据包在被切分成数据包之前是以数据流的形式存在于终端120中，SDAP层可以为这些数据流分配传输这些数据流的DRB。当SDAP层为这些数据流分配好DRB之后，数据流就会以数据包的形式往下层递交。在初始分配时，同一数据流被分配的DRB是相同的。
在实际传输中，存在多个DRB。在PDCP层、RLC层以及MAC层中，每 层都存在分别支撑各DRB的子模块，该模块可以是虚拟的软件模块。当每一层接收到从上一层递交下来的数据包时，这些数据包都会被分配在每一层对应的支撑与所述数据包对应的DRB的子模块中进行处理。
图2是根据一示例性实施例示出的一种下行数据包配置方法的方法流程图，如图2所示，该下行数据包配置方法应用于图1所示的移动通信系统中，该方法包括以下步骤。
在步骤201中，基站确定待发送的下行数据包对应的目标数据承载DRB。
在步骤202中，基站根据预先配置的DRB与下行处理属性的对应关系，确定目标DRB对应的目标下行处理属性。
其中，下行处理属性包括是否支持非接入反射的服务质量(NAS Reflective QoS)功能、以及是否支持接入反射的服务质量(AS Reflective QoS)功能。
在步骤203中，如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，基站则在封装下行数据包的过程中添加服务数据同化协议SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，基站则在封装下行数据包的过程中不添加SDAP包头。
在步骤204中，基站向终端发送封装后的下行数据包。
对应的，终端接收基站发送的下行数据包。
在步骤205中，终端根据预先配置的DRB与下行处理属性的对应关系，确定传输下行数据包的目标DRB对应的目标下行处理属性。
在步骤206中，如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，终端则确定下行数据包封装有SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，终端则确定下行数据包未封装有SDAP包头。
在步骤207中，终端基于确定出的下行数据包是否封装有SDAP包头的情况，对下行数据包进行处理。
综上所述，本申请实施例中提供的下行数据包配置方法，通过仅对下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能的下行数据包添加SDAP包头，由于基站不对下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能的下行数据包添加SDAP包头，解决 了现有技术中，无论下行数据包是何下行处理属性，AS层的每一个子层都要对下行数据包进行封装和解封装，占用设备大量的处理资源的增加问题，达到了降低设备的处理资源的占用的效果。
图3A是根据另一示例性实施例示出的一种下行数据包配置方法的方法流程图，如图3A所示，该下行数据包配置方法应用于图1所示的移动通信系统中，该方法包括以下步骤。
在步骤301中，基站确定待发送的下行数据包对应的目标DRB。
终端与基站的一次会话中会传输多条数据流，各数据流中包含多个数据包，其中，终端向基站发送的数据包称为上行数据包，基站向终端发送的数据包称为下行数据包。
终端与基站建立连接后，基站会和终端建立起多个DRB，每个DRB分别对应不同业务。由于基站已知下行数据包的业务属性，因此当基站获取到下行数据包后，会根据预存的业务属性与DRB的对应关系，确定该下行数据包的业务属性所对应的目标DRB。
在步骤302中，基站根据预先配置的DRB与下行处理属性的对应关系，确定目标DRB对应的目标下行处理属性。
DRB与下行处理属性的对应关系中的一项对应关系是指，某一个DRB所传输的数据流中数据包对应的下行处理属性。其中，下行处理属性包括是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能。
当目标DRB对应的目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能时，说明该目标DRB所传输的数据流中数据包不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能。
在步骤303中，如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，基站则在封装下行数据包的过程中添加SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，基站则在封装下行数据包的过程中不添加SDAP包头。
图3B是根据一示例性实施例示出的目标下行处理属性为支持NAS Reflective QoS功能的下行数据包的结构图，如图3B所示，如果目标下行处理属性为支持NAS Reflective QoS功能，则在封装下行数据包的过程中添加 SDAP包头，并在SDAP包头中添加RQI字段和数据流标识QFI字段。其中，QFI字段用于标识下行数据包所属的数据流。
图3C是根据一示例性实施例示出的目标下行处理属性为仅支持AS Reflective QoS功能的下行数据包的结构图，如图3C所示，如果目标下行处理属性为仅支持AS Reflective QoS功能，则在封装下行数据包的过程中添加SDAP包头，并在SDAP包头中添加指示信息和QFI字段，其中，指示信息用于指示SDAP包头中是否包含QFI字段。
可选的，RQI字段和指示信息的长度均为1个比特，QFI字段的长度为7个比特。其中，指示信息的作用除了用于指示SDAP包头中是否包含QFI字段外，还用于填补SDAP包头中RQI字段的缺失，使得无论SDAP包头是否包含RQI字段，该SDAP包头中除RQI字段的其他字段位置不变。
由于SDAP包头只占用一个字节，且QFI字段至少能包含7个比特，因此可以有效控制SDAP包头的大小，且有效保证QFI字段能够携带足够多的信息。
需要说明的是，当SDAP包头中不包含QFI字段时，在QFI字段的位置预留比特。
如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则该下行数据包在基站侧每被下传至一层，基站侧的AS层的每一个子层都要进行相应的处理，其中，对该下行数据包相应的处理的处理方式可以具体为数据包解封装、数据分组、数据编码、数据加密等等，本实施例不对基站在AS层中对下行数据包进行处理的具体处理方式进行限制。
以相应的处理的处理方式为数据包封装为例，基站在AS层的每一个子层中均要为该数据包进行封装。具体的，当下行数据包在SDAP层时，基站在SDAP层中为该下行数据包添加SDAP包头，并将被添加SDAP包头后的下行数据包发送至下一层——PDCP层；当下行数据包在PDCP层时，基站在PDCP层中为该下行数据包添加PDCP包头，并将被添加PDCP包头后的下行数据包发送至下一层——RLC层；当下行数据包在RLC层时，基站在RLC层中为该下行数据包添加RLC包头，并将被添加RLC包头后的下行数据包发送至下一层——MAC层；当下行数据包在MAC层时，基站在MAC层中为该下行数据包添加MAC包头，并将被添加MAC包头后的下行数据包发送至下一层——PHY层；当下行数据包在PHY层时，基站在PHY层中将该下行数据包转换为比特流发送至终端。
如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则当下行数据包在SDAP层时，基站在SDAP层中封装该下行数据包的过程中不添加SDAP包头，将该下行数据包发送至下一层——PDCP层；当下行数据包在PDCP层时，基站在PDCP层中为该下行数据包添加PDCP包头，并将被添加PDCP包头后的下行数据包发送至下一层——RLC层；当下行数据包在RLC层时，基站在RLC层中为该下行数据包添加RLC包头，并将被添加RLC包头后的下行数据包发送至下一层——MAC层；当下行数据包在MAC层时，基站在MAC层中为该下行数据包添加MAC包头，并将被添加MAC包头后的下行数据包发送至下一层——PHY层；当下行数据包在PHY层时，基站在PHY层中将该下行数据包转换为比特流发送至终端。
在步骤304中，基站向终端发送封装后的下行数据包。
对应的，终端接收基站发送的下行数据包。
在步骤305中，终端根据预先配置的DRB与下行处理属性的对应关系，确定传输下行数据包的目标DRB对应的目标下行处理属性。
如果传输下行数据包的目标DRB对应的目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，终端则判定该下行数据包不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能。
如果传输下行数据包的目标DRB对应的目标下行处理属性为支持NAS Reflective QoS功能，终端则判定该下行数据包支持NAS Reflective QoS功能。
在步骤306中，如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，终端则确定下行数据包封装有SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，终端则确定下行数据包未封装有SDAP包头。
在步骤307中，基于确定出的下行数据包是否封装有SDAP包头的情况，对下行数据包进行处理。
图3D是根据一示例性实施例示出的终端对下行数据包进行处理方法的方法流程图，如图3D所示，在一种可能的方式中，如果确定出下行数据包封装有SDAP包头，终端对下行数据包进行处理方法包括以下步骤。
在步骤307a中，解析下行数据包的SDAP包头。
如果目标下行处理属性为如果目标下行处理属性为支持NAS Reflective  QoS功能或支持AS Reflective QoS功能，则该下行数据包在终端侧每被上传至一层，终端侧的AS层的每一个子层都要进行相应的处理，其中，对该下行数据包相应的处理的处理方式可以具体为数据包解封装、数据合组、数据解码、数据解密等等，本实施例不对终端在AS层中对下行数据包进行处理的具体处理方式进行限制。
以相应的处理的处理方式为数据包解封装为例，终端在AS层的每一个子层中均要为该数据包进行解封装。具体的，当终端在PHY层中接收到下行数据包对应的比特流时，将该比特流转换为下行数据包后发送至上一层——MAC层；MAC层中接收到下行数据包时，为该下行数据包解封装MAC包头，并将解封装MAC包头后的下行数据包发送至上一层——RLC层；当下行数据包在RLC层时，终端在RLC层中为该下行数据包解封装RLC包头，并将解封装RLC包头后的下行数据包发送至上一层——PDCP层；当下行数据包在PDCP层时，终端在PDCP层中为该下行数据包解封装PDCP包头，并将解封装PDCP包头后的下行数据包发送至上一层——SDAP层；当下行数据包在SDAP层时，终端在SDAP层中为该下行数据包解封装SDAP包头。
在步骤307b中，如果SDAP包头携带有RQI字段和QFI字段，则在NAS层中处理下行数据包。
如果SDAP包头携带有RQI字段和QFI字段，说明该下行数据包支持NAS Reflective QoS功能，终端则可从SDAP包头中提取出RQI字段和QFI字段，并将RQI字段和QFI字段递交至NAS层，由NAS层根据RQI字段和QFI字段，对该下行数据包进行处理，并将处理后的下行数据包发送至应用层。
在步骤307c中，如果SDAP包头携带有指示信息和QFI字段，则在AS层中处理下行数据包。
如果SDAP包头携带有指示信息和QFI字段，说明该下行数据包支持AS Reflective QoS功能，终端则解析下行数据包的SDAP包头，获取指示信息，当该指示信息指示SDAP包头中包含QFI字段时，终端先获取SDAP包头中的QFI字段，再在AS层根据QFI字段对下行数据包进行处理，并将处理后的下行数据包发送至应用层。
需要说明的是，如果确定出下行数据包未封装有SDAP包头，终端则将该下行数据包透传至下一层。
综上所述，本申请实施例中提供的下行数据包配置方法，通过仅对下行处 理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能的下行数据包添加SDAP包头，由于基站不对下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能的下行数据包添加SDAP包头，解决了现有技术中，无论下行数据包是何下行处理属性，AS层的每一个子层都要对下行数据包进行封装和解封装，占用设备大量的处理资源的增加问题，达到了降低设备的处理资源的占用的效果。
在一种可能实现的方式中，终端预先配置的DRB与下行处理属性的对应关系除了由人为配置或者系统预置外，终端还可以在基站和终端建立起多个DRB之后，且基站向终端发送下行数据包之前，通过接收基站向终端发送DRB与下行处理属性的对应关系得到。
在步骤308中，基站向终端发送DRB与下行处理属性的对应关系，由终端对DRB与下行处理属性的对应关系进行存储。
可选的，基站通过RRC配置消息，向终端发送DRB与下行处理属性的对应关系。
对应的，终端接收基站发送的DRB与下行处理属性的对应关系，对DRB与下行处理属性的对应关系进行存储。
可选的，终端接收基站通过RRC配置消息发送的DRB与下行处理属性的对应关系。
需要说明的是，步骤308可在步骤301和步骤303中任一步骤之前或者任一步骤之后实施，图3A所示的流程图中步骤308的位置仅用于示例，本实施例不能限定步骤308与步骤301和步骤303之间的实施顺序。
图4A是根据再一示例性实施例示出的一种下行数据包配置方法的方法流程图，如图4A所示，该下行数据包配置方法应用于图1所示的移动通信系统中，该方法包括以下步骤。
在步骤401中，基站确定待发送的下行数据包对应的目标DRB。
在步骤402中，基站根据预先配置的DRB与下行处理属性的对应关系，确定目标DRB对应的目标下行处理属性。
在步骤403中，如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，基站则在封装下行数据包的过程中添加SDAP 包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，基站则在封装下行数据包的过程中不添加SDAP包头。
在步骤404中，基站获取QFI与下行处理属性的对应关系。
QFI为数据流(QoS Flow)的唯一标识，每个终端分别对应多个QoS Flow。
QFI与下行处理属性的对应关系至少包括以下几种：QFI对应的下行处理属性为支持NAS Reflective QoS功能，QFI对应的下行处理属性为支持AS Reflective QoS功能，QFI对应的下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能。
其中，由核心网配置QFI对应的下行处理属性是否支持NAS Reflective QoS功能，当基站从核心网获取对应的下行处理属性为支持NAS Reflective QoS功能的QFI后，将QFI和支持NAS Reflective QoS功能作为一组对应关系添加到QFI与下行处理属性的对应关系中，基站配置对应的下行处理属性为支持AS Reflective QoS功能的QFI后，将该QFI和支持AS Reflective QoS功能作为一组对应关系添加到QFI与下行处理属性的对应关系中，以及将对应的未被配置下行属性为支持NAS Reflective QoS功能和支持AS Reflective QoS功能的QFI，和不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能作为一组对应关系添加到QFI与下行处理属性的对应关系中。
可选的，基站根据QFI与下行处理属性的对应关系，以及DRB与下行处理属性的对应关系，配置QFI与DRB的对应关系。
需要说明的是，一个DRB与多个QFI对应，当DRB对应的下行处理属性包括支持NAS Reflective QoS功能时，说明该DRB对应的多个QFI中，至少包含一个支持NAS Reflective QoS功能的QFI。当DRB对应的下行处理属性包括支持AS Reflective QoS功能时，说明该DRB对应的多个QFI中，至少包含一个支持AS Reflective QoS功能的QFI。
在步骤405中，基站向所述终端发送所述QFI与下行处理属性的对应关系。
对应的，终端接收并存储所述基站发送的QFI与下行处理属性的对应关系。
可选的，基站通过RRC配置消息，向终端发送QFI与下行处理属性的对应关系。对应的，终端接收基站通过RRC配置消息发送的QFI与下行处理属性的对应关系。
在步骤406中，基站向终端发送封装后的下行数据包。
对应的，终端接收基站发送的下行数据包。
在步骤407中，终端根据预先配置的DRB与下行处理属性的对应关系，确定传输下行数据包的目标DRB对应的目标下行处理属性。
在步骤408中，如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，终端则确定下行数据包封装有SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，终端则确定下行数据包未封装有SDAP包头。
在步骤409中，基于确定出的下行数据包是否封装有SDAP包头的情况，对下行数据包进行处理。
图4B是根据一示例性实施例示出的终端对下行数据包进行处理方法的方法流程图，如图4B所示，在一种可能的方式中，如果确定出下行数据包封装有SDAP包头，终端对下行数据包进行处理方法包括以下步骤。
在步骤409a中，解析下行数据包的SDAP包头，得到SDAP包头中携带的QFI字段。
下行数据包的SDAP包头中携带的QFI字段，为该传输该下行数据包的QoS Flow对应的QFI。
在步骤409b中，根据QFI与下行处理属性的对应关系，确定SDAP包头携带的QFI对应的下行处理属性。
由于一个DRB与多个QFI对应，如果DRB对应的下行处理属性包括支持NAS Reflective QoS功能和支持AS Reflective QoS功能时，终端仅能判定下行数据包封装有SDAP包头，但无法判断下行数据包对应的下行处理属性为支持NAS Reflective QoS功能还是支持AS Reflective QoS功能，因此在终端解析下行数据包的SDAP包头，得到SDAP包头中携带的QFI字段之后，可根据QFI与下行处理属性的对应关系，确定SDAP包头携带的QFI所对应的下行数据包的下行处理属性。
在步骤409c中，如果QFI对应的下行处理属性为支持NAS Reflective QoS功能，则在NAS层中处理下行数据包。
如果下行数据包的SDAP包头中携带的QFI对应的下行处理属性为支持NAS Reflective QoS功能，说明该下行数据包支持NAS Reflective QoS功能，终端则可从SDAP包头中提取出RQI字段和QFI字段，并将RQI字段和QFI字段递交至NAS层，由NAS层根据RQI字段和QFI字段，对该下行数据包 进行处理，并将处理后的下行数据包发送至应用层。
在步骤409d中，如果QFI对应的下行处理属性为支持AS Reflective QoS功能，则在AS层中处理下行数据包。
如果下行数据包的SDAP包头中携带的QFI对应的下行处理属性为支持AS Reflective QoS功能，说明该下行数据包支持AS Reflective QoS功能，终端则解析下行数据包的SDAP包头，获取指示信息，当该指示信息指示SDAP包头中包含QFI字段时，终端先获取SDAP包头中的QFI字段，再在AS层根据QFI字段对下行数据包进行处理，并将处理后的下行数据包发送至应用层。
需要说明的是，由于本实施例中步骤401至步骤403分别与步骤301至步骤303对应，步骤406至步骤408分别与步骤304至步骤306类似，因此本实施例不再对步骤401至步骤403、步骤406至步骤408赘述说明。
综上所述，本申请实施例中提供的下行数据包配置方法，通过仅对下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能的下行数据包添加SDAP包头，由于基站不对下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能的下行数据包添加SDAP包头，解决了现有技术中，无论下行数据包是何下行处理属性，AS层的每一个子层都要对下行数据包进行封装和解封装，占用设备大量的处理资源的增加问题，达到了降低设备的处理资源的占用的效果。
在一种可能实现的方式中，当终端向目标基站进行基站切换时，原基站会将该原基站中与该终端相关的配置信息发送给目标基站，提高目标基站配置该目标基站中与该终端相关的配置信息的效率。
图5是根据一示例性实施例示出的对应关系配置方法的方法流程图，如图5所示，该对应关系配置方法应用于图1所示的移动通信系统中，该方法包括以下步骤。
步骤501，当终端向目标基站进行基站切换时，基站将终端对应的第一配置信息发送至目标基站。
其中，第一配置信息包括QFI与下行处理属性的对应关系、和/或DRB与下行处理属性的对应关系。
需要说明的是，在终端进行网络切换的过程中，会从该基站切换到目标基站；在终端同时与两个甚至多个基站连接的场景下，在目标基站有向终端发送 的下行数据，终端可能会从该基站切换到目标基站。
步骤502，基站接收目标基站根据第一配置信息设置的第二配置信息，将第二配置信息发送至终端。
可选的，目标服务器在设置第二配置信息的过程中沿用第一配置信息，或者，根据业务负载情况、QoS保证等信息，对第一配置信息修改得到第二配置信息。
比如，由于对应的下行属性为支持NAS Reflective QoS功能的QFI是由核心网配置的，因此目标基站在接收到携带有QFI与下行处理属性的对应关系的第一配置信息后，可直接沿用对应的下行属性支持NAS Reflective QoS功能的QFI相关的配置信息，并将下行属性支持NAS Reflective QoS功能的QFI相关的配置信息添加到第二配置信息中。
再比如，由于一个DRB与多个QFI对应，当某个DRB的业务负载过大时，可能无法保证为该业务提供良好的QoS保证，因此当目标基站接收到第一配置信息后，可根据每个DRB的实际负载情况，更改每个DRB对应的QFI的数量(举例：减少业务负载过大的DRB对应的QFI的数量，增加业务负载较小的DRB对应的QFI的数量)，或者更改DRB与处理属性的对应关系(举例：当需要NAS处理的下行数据较多时，将部分DRB对应的处理属性由支持AS Reflective QoS功能修改为支持NAS Reflective QoS功能且支持AS Reflective QoS功能，或者，将部分DRB对应的处理属性由支持AS Reflective QoS功能修改为支持NAS Reflective QoS功能)，从而得到第二配置信息。
对应的，终端接收并存储基站发送的第二配置信息。
其中，第二配置信息包括目标基站对应的QFI与下行处理属性的对应关系、以及目标基站对应的DRB与下行处理属性的对应关系。
综上所述，本申请实施例中提供的下行数据包配置方法，通过仅对下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能的下行数据包添加SDAP包头，由于基站不对下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能的下行数据包添加SDAP包头，解决了现有技术中，无论下行数据包是何下行处理属性，AS层的每一个子层都要对下行数据包进行封装和解封装，占用设备大量的处理资源的增加问题，达到了降低设备的处理资源的占用的效果。
本实施例中，当终端向目标基站进行基站切换时，原基站会将该原基站中 与该终端相关的配置信息发送给目标基站，提高目标基站配置该目标基站中与该终端相关的配置信息的效率。
需要说明的是，上述各个实施例中提及的状态名称、消息名称均为示意性的，本实施例并不限制上述实施例中提及的状态名称、消息名称。只要是具有相同状态特征或者相同消息功能，即视为本申请的保护范围。
下述为本申请装置实施例，可以用于执行本申请方法实施例。对于本申请装置实施例中未披露的细节，请参照本申请方法实施例。
图6是根据一示例性实施例示出的一种下行数据包配置装置的框图，如图6所示，该下行数据包配置装置应用于图1所示的移动通信系统中的基站中，该下行数据包配置装置包括但不限于：第一确定模块601、第二确定模块602、处理模块603和第一发送模块604。
第一确定模块601，被配置为确定待发送的下行数据包对应的目标数据承载DRB；
第二确定模块602，被配置为根据配置存储的DRB与下行处理属性的对应关系，确定目标DRB对应的目标下行处理属性，其中，下行处理属性包括是否支持NAS Reflective QoS功能、以及是否支持AS Reflective QoS功能；
处理模块603，被配置为如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则在封装下行数据包的过程中添加服务数据同化协议SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则在封装下行数据包的过程中不添加SDAP包头；
第一发送模块604，被配置为向终端发送封装后的下行数据包。
可选地，该处理模块603，包括：第一添加单元603a和第二添加单元603b。
第一添加单元603a，被配置为如果目标下行处理属性为支持NAS Reflective QoS功能，则在封装下行数据包的过程中添加SDAP包头，并在SDAP包头中添加RQI字段和数据流标识QFI字段；
第二添加单元603b，被配置为如果目标下行处理属性为仅支持AS Reflective QoS功能，则在封装下行数据包的过程中添加SDAP包头，并在SDAP包头中添加指示信息和QFI字段，其中，指示信息用于指示SDAP包头中是否 包含QFI字段。
可选地，RQI字段的长度为1个比特，QFI字段的长度为7个比特。
可选地，该装置还包括：第二发送模块。
第二发送模块，被配置为向终端发送下行数据包之前，向终端发送DRB与下行处理属性的对应关系，由终端对DRB与下行处理属性的对应关系进行存储。
可选地，该第二发送模块，还被配置为：
通过RRC配置消息，向终端发送DRB与下行处理属性的对应关系。
可选地，该装置还包括：
获取模块，被配置为向终端发送封装后的下行数据包之前，获取QFI与下行处理属性的对应关系；
第三发送模块，被配置为向终端发送QFI与下行处理属性的对应关系，由终端存储QFI与下行处理属性的对应关系。
可选地，该装置还包括：
第四发送模块，被配置为当终端向目标基站进行基站切换时，将终端对应的第一配置信息发送至目标基站，第一配置信息包括QFI与下行处理属性的对应关系、和/或DRB与下行处理属性的对应关系；
第五发送模块，被配置为接收目标基站根据第一配置信息设置的第二配置信息，将第二配置信息发送至终端，由终端存储第二配置信息，第二配置信息包括目标基站对应的QFI与下行处理属性的对应关系、以及目标基站对应的DRB与下行处理属性的对应关系。
综上所述，本申请实施例中提供的下行数据包配置装置，通过仅对下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能的下行数据包添加SDAP包头，由于基站不对下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能的下行数据包添加SDAP包头，解决了现有技术中，无论下行数据包是何下行处理属性，AS层的每一个子层都要对下行数据包进行封装和解封装，占用设备大量的处理资源的增加问题，达到了降低设备的处理资源的占用的效果。
图7是根据一示例性实施例示出的一种下行数据包配置装置的框图，如图7所示，该下行数据包配置装置应用于图1所示的移动通信系统中的终端中， 该下行数据包配置装置包括但不限于：第一接收模块701、确定模块702、处理模块703和透传模块704。
第一接收模块701，被配置为接收基站发送的下行数据包；
第一确定模块702，被配置为根据预先配置的DRB与下行处理属性的对应关系，确定传输下行数据包的目标DRB对应的目标下行处理属性，其中，下行处理属性为是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能；
第二确定模块703，被配置为如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则确定下行数据包封装有SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则确定下行数据包未封装有SDAP包头；
处理模块704，被配置为基于确定出的下行数据包是否封装有SDAP包头的情况，对下行数据包进行处理。
可选地，如果确定出下行数据包封装有SDAP包头的情况，处理模块704，包括：第一解析单元、第一处理单元和第二处理单元。
第一解析单元，被配置为解析下行数据包的SDAP包头；
第一处理单元，被配置为如果SDAP包头携带有RQI字段和QFI字段，则在NAS层中处理下行数据包；
第二处理单元，被配置为如果SDAP包头携带有指示信息和QFI字段，则在AS层中处理下行数据包。
可选地，RQI字段的长度为1个比特，QFI字段的长度为7个比特。
可选地，该装置还包括：存储模块。
存储模块，被配置为接收基站发送的下行数据包之前，接收基站发送的DRB与下行处理属性的对应关系，对DRB与下行处理属性的对应关系进行存储。
可选地，该存储模块，还被配置为：
接收基站通过RRC配置消息发送的DRB与下行处理属性的对应关系。
可选地，该装置还包括：
第二接收模块，被配置为接收基站发送的下行数据包之前，接收并存储基站发送的QFI与下行处理属性的对应关系；
如果确定出下行数据包封装有SDAP包头，该处理模块，还包括：
第二解析单元，被配置为解析下行数据包的SDAP包头，得到SDAP包头中携带的QFI字段；
确定单元，被配置为根据QFI与下行处理属性的对应关系，确定SDAP包头携带的QFI对应的下行处理属性；
第三处理单元，被配置为如果QFI对应的下行处理属性为支持NAS Reflective QoS功能，则在NAS层中处理下行数据包；
第四处理单元，被配置为如果QFI对应的下行处理属性为支持AS Reflective QoS功能，则在AS层中处理下行数据包。
可选地，该装置还包括：
第三接收模块，被配置为接收并存储基站发送的第二配置信息，第二配置信息为当满足预定条件时，基站将终端对应的第一配置信息发送至目标基站后，从目标基站获取的信息；
其中，第一配置信息包括QFI与下行处理属性的对应关系、和/或DRB与下行处理属性的对应关系，第二配置信息至少包括目标基站对应的QFI与下行处理属性的对应关系、以及目标基站对应的DRB与下行处理属性的对应关系。
综上所述，本申请实施例中提供的下行数据包配置装置，通过仅对下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能的下行数据包添加SDAP包头，由于基站不对下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能的下行数据包添加SDAP包头，解决了现有技术中，无论下行数据包是何下行处理属性，AS层的每一个子层都要对下行数据包进行封装和解封装，占用设备大量的处理资源的增加问题，达到了降低设备的处理资源的占用的效果。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本申请一示例性实施例提供了一种基站，能够实现本申请提供的下行数据包配置方法，该用户设备包括：处理器、用于存储处理器可执行指令的存储器；
其中，处理器被配置为：
确定待发送的下行数据包对应的目标数据承载DRB；
根据预先配置的DRB与下行处理属性的对应关系，确定目标DRB对应的 目标下行处理属性，其中，下行处理属性包括是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能；
如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则在封装下行数据包的过程中添加服务数据同化协议SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则在封装下行数据包的过程中不添加SDAP包头；
向终端发送封装后的下行数据包。
本申请一示例性实施例提供了一种终端，能够实现本申请提供的状态保持方法，该用户设备包括：处理器、用于存储处理器可执行指令的存储器；
其中，处理器被配置为：
接收基站发送的下行数据包；
根据预先配置的DRB与下行处理属性的对应关系，确定传输下行数据包的目标DRB对应的目标下行处理属性，其中，下行处理属性包括是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能；
如果目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则确定下行数据包封装有SDAP包头；如果目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则确定下行数据包未封装有SDAP包头；
基于确定出的下行数据包是否封装有SDAP包头的情况，对下行数据包进行处理。
图8是根据一示例性实施例示出的一种终端的框图。该终端800实现为图1中的终端120。例如，终端800可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图8，终端800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)接口812，传感器组件814，以及通信组件816。
处理组件802通常控制终端800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器818来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在终端800的操作。这些数据的示例包括用于在终端800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为终端800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或多个电源，及其他与为终端800生成、管理和分配电力相关联的组件。
多媒体组件808包括在终端800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当终端800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当终端800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接 口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为终端800提供各个方面的状态评估。例如，传感器组件814可以检测到终端800的打开/关闭状态，组件的相对定位，例如组件为终端800的显示器和小键盘，传感器组件814还可以检测终端800或终端800一个组件的位置改变，用户与终端800接触的存在或不存在，终端800方位或加速/减速和终端800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于终端800和其他设备之间有线或无线方式的通信。终端800可以接入基于通信标准的无线网络，如Wi-Fi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，终端800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述各个方法实施例提供的下行数据包配置方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由终端800的处理器818执行以完成上述下行数据包配置方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
图9是根据一示例性实施例示出的一种基站的框图。该基站900实现为图1中的基站140。具体来讲：
基站900包括中央处理单元(CPU)901、包括随机存取存储器(RAM) 902和只读存储器(ROM)903的系统存储器904，以及连接系统存储器904和中央处理单元901的系统总线905。所述基站900还包括帮助计算机内的各个器件之间传输信息的基本输入/输出系统(I/O系统)906，和用于存储操作系统913、应用程序914和其他程序模块915的大容量存储设备907。
所述基本输入/输出系统906包括有用于显示信息的显示器908和用于用户输入信息的诸如鼠标、键盘之类的输入设备909。其中所述显示器908和输入设备909都通过连接到系统总线905的输入输出控制器910连接到中央处理单元901。所述基本输入/输出系统906还可以包括输入输出控制器910以用于接收和处理来自键盘、鼠标、或电子触控笔等多个其他设备的输入。类似地，输入输出控制器910还提供输出到显示屏、打印机或其他类型的输出设备。
所述大容量存储设备907通过连接到系统总线905的大容量存储控制器(未示出)连接到中央处理单元901。所述大容量存储设备907及其相关联的计算机可读介质为基站900提供非易失性存储。也就是说，所述大容量存储设备907可以包括诸如硬盘或者CD-ROM驱动器之类的计算机可读介质(未示出)。
不失一般性，所述计算机可读介质可以包括计算机存储介质和通信介质。计算机存储介质包括以用于存储诸如计算机可读指令、数据结构、程序模块或其他数据等信息的任何方法或技术实现的易失性和非易失性、可移动和不可移动介质。计算机存储介质包括RAM、ROM、EPROM、EEPROM、闪存或其他固态存储其技术，CD-ROM、DVD或其他光学存储、磁带盒、磁带、磁盘存储或其他磁性存储设备。当然，本领域技术人员可知所述计算机存储介质不局限于上述几种。上述的系统存储器904和大容量存储设备907可以统称为存储器。
根据本发明的各种实施例，所述基站900还可以通过诸如因特网等网络连接到网络上的远程计算机运行。也即基站900可以通过连接在所述系统总线905上的网络接口单元911连接到网络912，或者说，也可以使用网络接口单元911来连接到其他类型的网络或远程计算机系统(未示出)。
所述存储器还包括一个或者一个以上的程序，所述一个或者一个以上程序存储于存储器中，所述一个或者一个以上程序包含用于进行本发明实施例提供的音效评价显示方法的指令。本领域普通技术人员可以理解上述实施例的音效评价显示方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成， 该程序可以存储于一计算机可读存储介质中，存储介质可以包括：只读存储器(ROM，Read Only Memory)、随机存取记忆体(RAM，Random Access Memory)、磁盘或光盘等。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器904，上述指令可由用户设备900的处理器918执行以完成上述下行数据包配置方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
应当理解的是，在本文中使用的，除非上下文清楚地支持例外情况，单数形式“一个”(“a”、“an”、“the”)旨在也包括复数形式。还应当理解的是，在本文中使用的“和/或”是指包括一个或者一个以上相关联地列出的项目的任意和所有可能组合。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本申请的真正范围和精神由下面的权利要求指出。
应当理解的是，本申请并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本申请的范围仅由所附的权利要求来限制。

Claims (32)

  1. 一种下行数据包配置方法，其特征在于，应用于基站，所述方法包括：
    确定待发送的下行数据包对应的目标数据承载DRB；
    根据预先配置的DRB与下行处理属性的对应关系，确定所述目标DRB对应的目标下行处理属性，其中，所述下行处理属性包括是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能；
    如果所述目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则在封装所述下行数据包的过程中添加服务数据同化协议SDAP包头；如果所述目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则在封装所述下行数据包的过程中不添加SDAP包头；
    向所述终端发送封装后的下行数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述在封装所述下行数据包的过程中添加服务数据同化协议SDAP包头，包括：
    如果所述目标下行处理属性为支持NAS Reflective QoS功能，则在封装所述下行数据包的过程中添加SDAP包头，并在所述SDAP包头中添加RQI字段和数据流标识QFI字段；
    如果所述目标下行处理属性为仅支持AS Reflective QoS功能，则在封装所述下行数据包的过程中添加SDAP包头，并在所述SDAP包头中添加指示信息和QFI字段，其中，所述指示信息用于指示所述SDAP包头中是否包含QFI字段。
  3. 根据权利要求2所述的方法，其特征在于，所述RQI字段的长度为1个比特，所述QFI字段的长度为7个比特。
  4. 根据权利要求1-3任一所述的方法，其特征在于，所述向终端发送所述下行数据包之前，所述方法还包括：
    向所述终端发送所述DRB与下行处理属性的对应关系，由所述终端对所述 DRB与下行处理属性的对应关系进行存储。
  5. 根据权利要求4所述的方法，其特征在于，所述向所述终端发送所述DRB与下行处理属性的对应关系，包括：
    通过RRC配置消息，向所述终端发送所述DRB与下行处理属性的对应关系。
  6. 根据权利要求1所述的方法，其特征在于，所述向所述终端发送封装后的下行数据包之前，所述方法还包括：
    获取QFI与下行处理属性的对应关系；
    向所述终端发送所述QFI与下行处理属性的对应关系，由所述终端存储所述QFI与下行处理属性的对应关系。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    当所述终端向所述目标基站进行基站切换时，将所述终端对应的第一配置信息发送至目标基站，所述第一配置信息包括所述QFI与下行处理属性的对应关系、和/或所述DRB与所述下行处理属性的对应关系；
    接收所述目标基站根据所述第一配置信息设置的第二配置信息，将所述第二配置信息发送至所述终端，由所述终端存储所述第二配置信息，所述第二配置信息包括所述目标基站对应的QFI与下行处理属性的对应关系、以及所述目标基站对应的DRB与所述下行处理属性的对应关系。
  8. 一种下行数据包配置方法，其特征在于，应用于终端，所述方法包括：
    接收基站发送的下行数据包；
    根据预先配置的DRB与下行处理属性的对应关系，确定传输所述下行数据包的目标DRB对应的目标下行处理属性，其中，所述下行处理属性包括是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能；
    如果所述目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则确定所述下行数据包封装有SDAP包头；如果所述目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功 能，则确定所述下行数据包未封装有SDAP包头；
    基于确定出的所述下行数据包是否封装有SDAP包头的情况，对所述下行数据包进行处理。
  9. 根据权利要求8所述的方法，其特征在于，如果确定出所述下行数据包封装有SDAP包头，所述对所述下行数据包进行处理，包括：
    解析所述下行数据包的SDAP包头；
    如果所述SDAP包头携带有RQI字段和QFI字段，则在NAS层中处理所述下行数据包；
    如果所述SDAP包头携带有指示信息和QFI字段，则在AS层中处理所述下行数据包，其中，所述指示信息用于指示所述SDAP包头中是否包含QFI字段。
  10. 根据权利要求9所述的方法，其特征在于，所述RQI字段的长度为1个比特，所述QFI字段的长度为7个比特。
  11. 根据权利要求8-10任一所述的方法，其特征在于，所述接收基站发送的下行数据包之前，所述方法还包括：
    接收所述基站发送的所述DRB与下行处理属性的对应关系，对所述DRB与下行处理属性的对应关系进行存储。
  12. 根据权利要求11所述的方法，其特征在于，所述接收所述基站发送的所述DRB与下行处理属性的对应关系，包括：
    接收所述基站通过RRC配置消息发送的所述DRB与下行处理属性的对应关系。
  13. 根据权利要求8所述的方法，其特征在于，所述接收基站发送的下行数据包之前，所述方法还包括：
    接收并存储所述基站发送的QFI与下行处理属性的对应关系；
    如果确定出所述下行数据包封装有SDAP包头，所述对所述下行数据包进行处理，包括：
    解析所述下行数据包的SDAP包头，得到所述SDAP包头中携带的QFI字段；
    根据所述QFI与下行处理属性的对应关系，确定所述SDAP包头携带的QFI对应的下行处理属性；
    如果所述QFI对应的下行处理属性为支持NAS Reflective QoS功能，则在NAS层中处理所述下行数据包；
    如果所述QFI对应的下行处理属性为支持AS Reflective QoS功能，则在AS层中处理所述下行数据包。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    接收并存储所述基站发送的第二配置信息，所述第二配置信息为当满足预定条件时，所述基站将所述终端对应的第一配置信息发送至目标基站后，从所述目标基站获取的信息；
    其中，所述第一配置信息包括所述QFI与下行处理属性的对应关系、和/或所述DRB与所述下行处理属性的对应关系，所述第二配置信息至少包括所述目标基站对应的QFI与下行处理属性的对应关系、以及所述目标基站对应的DRB与所述下行处理属性的对应关系。
  15. 一种下行数据包配置装置，其特征在于，应用于基站，所述装置包括：
    第一确定模块，被配置为确定待发送的下行数据包对应的目标数据承载DRB；
    第二确定模块，被配置为根据配置存储的DRB与下行处理属性的对应关系，确定所述目标DRB对应的目标下行处理属性，其中，所述下行处理属性包括是否支持NAS Reflective QoS功能、以及是否支持AS Reflective QoS功能；
    处理模块，被配置为如果所述目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则在封装所述下行数据包的过程中添加服务数据同化协议SDAP包头；如果所述目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则在封装所述下行数据包的过程中不添加SDAP包头；
    第一发送模块，被配置为向所述终端发送封装后的下行数据包。
  16. 根据权利要求15所述的装置，其特征在于，所述处理模块，包括：
    第一添加单元，被配置为如果所述目标下行处理属性为支持NAS Reflective QoS功能，则在封装所述下行数据包的过程中添加SDAP包头，并在所述SDAP包头中添加RQI字段和数据流标识QFI字段；
    第二添加单元，被配置为如果所述目标下行处理属性为仅支持AS Reflective QoS功能，则在封装所述下行数据包的过程中添加SDAP包头，并在所述SDAP包头中添加指示信息和QFI字段，其中，所述指示信息用于指示所述SDAP包头中是否包含QFI字段。
  17. 根据权利要求16所述的装置，其特征在于，所述RQI字段的长度为1个比特，所述QFI字段的长度为7个比特。
  18. 根据权利要求15-17任一所述的装置，其特征在于，所述装置还包括：
    第二发送模块，被配置为所述向终端发送所述下行数据包之前，向所述终端发送所述DRB与下行处理属性的对应关系，由所述终端对所述DRB与下行处理属性的对应关系进行存储。
  19. 根据权利要求18所述的装置，其特征在于，所述第二发送模块，还被配置为：
    通过RRC配置消息，向所述终端发送所述DRB与下行处理属性的对应关系。
  20. 根据权利要求15所述的装置，其特征在于，所述装置还包括：
    获取模块，被配置为所述向所述终端发送封装后的下行数据包之前，获取QFI与下行处理属性的对应关系；
    第三发送模块，被配置为向所述终端发送所述QFI与下行处理属性的对应关系，由所述终端存储所述QFI与下行处理属性的对应关系。
  21. 根据权利要求20所述的装置，其特征在于，所述装置还包括：
    第四发送模块，被配置为当所述终端向所述目标基站进行基站切换时，将所述终端对应的第一配置信息发送至目标基站，所述第一配置信息包括所述QFI 与下行处理属性的对应关系、和/或所述DRB与所述下行处理属性的对应关系；
    第五发送模块，被配置为接收所述目标基站根据所述第一配置信息设置的第二配置信息，将所述第二配置信息发送至所述终端，由所述终端存储所述第二配置信息，所述第二配置信息包括所述目标基站对应的QFI与下行处理属性的对应关系、以及所述目标基站对应的DRB与所述下行处理属性的对应关系。
  22. 一种下行数据包配置装置，其特征在于，应用于终端，所述装置包括：
    第一接收模块，被配置为接收基站发送的下行数据包；
    第一确定模块，被配置为根据预先配置的DRB与下行处理属性的对应关系，确定传输所述下行数据包的目标DRB对应的目标下行处理属性，其中，所述下行处理属性为是否支持非接入反射的服务质量NAS Reflective QoS功能、以及是否支持接入反射的服务质量AS Reflective QoS功能；
    第二确定模块，被配置为如果所述目标下行处理属性为支持NAS Reflective QoS功能或支持AS Reflective QoS功能，则确定所述下行数据包封装有SDAP包头；如果所述目标下行处理属性为不支持NAS Reflective QoS功能且不支持AS Reflective QoS功能，则确定所述下行数据包未封装有SDAP包头；
    处理模块，被配置为基于确定出的所述下行数据包是否封装有SDAP包头的情况，对所述下行数据包进行处理。
  23. 根据权利要求22所述的装置，其特征在于，如果确定出所述下行数据包封装有SDAP包头的情况，所述处理模块，包括：
    第一解析单元，被配置为解析所述下行数据包的SDAP包头；
    第一处理单元，被配置为如果所述SDAP包头携带有RQI字段和QFI字段，则在NAS层中处理所述下行数据包；
    第二处理单元，被配置为如果所述SDAP包头携带有指示信息和QFI字段，则在AS层中处理所述下行数据包。
  24. 根据权利要求23所述的装置，其特征在于，所述RQI字段的长度为1个比特，所述QFI字段的长度为7个比特。
  25. 根据权利要求22-24任一所述的装置，其特征在于，所述装置还包括：
    存储模块，被配置为所述接收基站发送的下行数据包之前，接收所述基站发送的所述DRB与下行处理属性的对应关系，对所述DRB与下行处理属性的对应关系进行存储。
  26. 根据权利要求25所述的装置，其特征在于，所述存储模块，还被配置为：
    接收所述基站通过RRC配置消息发送的所述DRB与下行处理属性的对应关系。
  27. 根据权利要求22所述的装置，其特征在于，所述装置还包括：
    第二接收模块，被配置为所述接收基站发送的下行数据包之前，接收并存储所述基站发送的QFI与下行处理属性的对应关系；
    如果确定出所述下行数据包封装有SDAP包头，所述处理模块，还包括：
    第二解析单元，被配置为解析所述下行数据包的SDAP包头，得到所述SDAP包头中携带的QFI字段；
    确定单元，被配置为根据所述QFI与下行处理属性的对应关系，确定所述SDAP包头携带的QFI对应的下行处理属性；
    第三处理单元，被配置为如果所述QFI对应的下行处理属性为支持NAS Reflective QoS功能，则在NAS层中处理所述下行数据包；
    第四处理单元，被配置为如果所述QFI对应的下行处理属性为支持AS Reflective QoS功能，则在AS层中处理所述下行数据包。
  28. 根据权利要求27所述的装置，其特征在于，所述装置还包括：
    第三接收模块，被配置为接收并存储所述基站发送的第二配置信息，所述第二配置信息为当满足预定条件时，所述基站将所述终端对应的第一配置信息发送至目标基站后，从所述目标基站获取的信息；
    其中，所述第一配置信息包括所述QFI与下行处理属性的对应关系、和/或所述DRB与所述下行处理属性的对应关系，所述第二配置信息至少包括所述目标基站对应的QFI与下行处理属性的对应关系、以及所述目标基站对应的DRB与所述下行处理属性的对应关系。
  29. 一种基站，其特征在于，所述终端包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如权利要求1-7任一所述的下行数据包配置方法。
  30. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如权利要求1-7任一所述的下行数据包配置方法。
  31. 一种终端，其特征在于，所述终端包括处理器和存储器，所述存储器中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现如权利要求8-14任一所述的下行数据包配置方法。
  32. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如权利要求8-14任一所述的下行数据包配置方法。
PCT/CN2017/110944 2017-07-25 2017-11-14 下行数据包配置方法及装置 WO2019019486A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
ES17919504T ES2911923T3 (es) 2017-07-25 2017-11-14 Método y dispositivo de configuración de paquete de datos de enlace descendente
US16/633,156 US11190967B2 (en) 2017-07-25 2017-11-14 Downlink data packet configuration method and device
EP17919504.5A EP3661260B1 (en) 2017-07-25 2017-11-14 Downlink data packet configuration method and device
CN201780001600.1A CN108476508B (zh) 2017-07-25 2017-11-14 下行数据包配置方法及装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2017/094407 2017-07-25
PCT/CN2017/094407 WO2019019032A1 (zh) 2017-07-25 2017-07-25 下行数据包配置方法及装置

Publications (1)

Publication Number Publication Date
WO2019019486A1 true WO2019019486A1 (zh) 2019-01-31

Family

ID=65039342

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2017/094407 WO2019019032A1 (zh) 2017-07-25 2017-07-25 下行数据包配置方法及装置
PCT/CN2017/110944 WO2019019486A1 (zh) 2017-07-25 2017-11-14 下行数据包配置方法及装置

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/094407 WO2019019032A1 (zh) 2017-07-25 2017-07-25 下行数据包配置方法及装置

Country Status (5)

Country Link
US (1) US11190967B2 (zh)
EP (1) EP3661260B1 (zh)
CN (2) CN109451828B (zh)
ES (1) ES2911923T3 (zh)
WO (2) WO2019019032A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11419009B2 (en) * 2018-02-15 2022-08-16 Telefonaktiebolaget Lm Ericsson (Publ) Methods providing QFI harmonization between RAN and 5GC and related wireless terminals, base stations, and core network nodes
CN110636544B (zh) * 2018-06-22 2022-09-23 华为技术有限公司 一种数据传输方法及装置
CN110972192B (zh) * 2018-09-28 2023-05-05 中国移动通信有限公司研究院 信息传输方法、装置、相关设备及存储介质
CN110312282B (zh) 2018-09-28 2021-06-29 华为技术有限公司 数据传输的方法和装置
CN109526026B (zh) * 2018-10-29 2021-11-23 中国电子科技集团公司第三十六研究所 一种基于End/Start Mark的上行SDAP重映射方法和装置
CN111491333B (zh) * 2019-01-29 2023-05-05 中国移动通信有限公司研究院 一种数据处理方法、发送端设备和接收端设备
CN111586750B (zh) * 2019-02-15 2023-01-10 中国移动通信有限公司研究院 一种数据发送、接收的方法、装置、电子设备及介质
CN110995750B (zh) * 2019-12-18 2021-09-28 展讯通信（上海）有限公司 终端设备
JP2024514748A (ja) * 2021-05-28 2024-04-03 インテル・コーポレーション 次世代セルラーネットワークにおけるサービス機能チェイニングのための拡張サービス分類

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102612095A (zh) * 2012-03-05 2012-07-25 电信科学技术研究院 一种ip数据包的传输方法和设备
WO2013064070A1 (zh) * 2011-11-01 2013-05-10 中兴通讯股份有限公司 一种实现反射QoS机制的方法、系统和PCRF

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140233380A1 (en) * 2011-10-27 2014-08-21 Lg Electronics Inc. Method and apparatus for managing quality of service of uplink in wireless communication system
US9578647B2 (en) * 2013-08-29 2017-02-21 Telefonaktiebolaget Lm Ericsson (Publ) 3GPP bearer-based QoS model support on WiFi
US9521679B2 (en) 2014-03-06 2016-12-13 Cisco Technology, Inc. Systems and methods for implementing reflective EPS bearers to ensure uplink quality of service
US20180213540A1 (en) * 2017-01-25 2018-07-26 Acer Incorporated Method of mapping data packets and related apparatuses using the same
WO2018143593A1 (en) * 2017-02-01 2018-08-09 Lg Electronics Inc. Method for performing reflective quality of service (qos) in wireless communication system and a device therefor
US20180324631A1 (en) * 2017-05-05 2018-11-08 Mediatek Inc. Using sdap headers for handling of as/nas reflective qos and to ensure in-sequence packet delivery during remapping in 5g communication systems
US11109262B2 (en) * 2017-07-20 2021-08-31 Asustek Computer Inc. Method and apparatus for servicing QoS (quality of service) flow in a wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013064070A1 (zh) * 2011-11-01 2013-05-10 中兴通讯股份有限公司 一种实现反射QoS机制的方法、系统和PCRF
CN102612095A (zh) * 2012-03-05 2012-07-25 电信科学技术研究院 一种ip数据包的传输方法和设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15)", 3GPP STANDARD ; TECHNICAL SPECIFICATION ; 3GPP TS 38.300, vol. RAN WG2, no. V0.4.1, 12 June 2017 (2017-06-12), pages 1 - 55, XP051298402 *
MEDIATEK INC.: "pCR 23.501 - Corrections to UE-derived QoS rule", SA WG2 MEETING # 121 S2-173145, no. S2-173145, 31 March 2017 (2017-03-31), Hangzhou, China, pages 1 - 9, XP051268612 *
See also references of EP3661260A4 *

Also Published As

Publication number Publication date
EP3661260A4 (en) 2020-07-08
US11190967B2 (en) 2021-11-30
CN109451828A (zh) 2019-03-08
EP3661260B1 (en) 2022-02-23
ES2911923T3 (es) 2022-05-23
CN108476508B (zh) 2022-02-22
US20210160727A1 (en) 2021-05-27
EP3661260A1 (en) 2020-06-03
CN108476508A (zh) 2018-08-31
CN109451828B (zh) 2022-05-10
WO2019019032A1 (zh) 2019-01-31

Similar Documents

Publication Publication Date Title
WO2019019486A1 (zh) 下行数据包配置方法及装置
JP6017731B2 (ja) 音声通信およびデータ通信を遂行するためのＷｉ−Ｆｉディスプレイ移送機構を使用するための方法およびシステム
US11343704B2 (en) Method and apparatus for assigning identifier, base station and user equipment
CN107637123B (zh) 信息传递方法、装置及计算机可读存储介质
WO2021204003A1 (zh) 一种临近服务的业务处理方法、设备及系统
WO2020119596A1 (zh) 数据传送的保障方法及通信设备
WO2019128657A1 (zh) 数据发送方法、装置及设备
WO2018082033A1 (zh) 协议数据单元pdu包生成方法和装置
WO2018035839A1 (zh) 一种数据传输方法、相关设备及通信系统
WO2019033399A1 (zh) 反射业务质量配置的方法及装置和信息发送方法及装置
WO2020088585A1 (zh) 副链路连接建立、资源分配方法、终端及网络侧设备
WO2018196102A1 (zh) 信息传递方法、装置及计算机可读存储介质
JP7317236B2 (ja) データ処理方法、データ処理装置、通信機器及び記憶媒体
WO2017031699A1 (zh) 一种数据传输的方法、相关设备和系统
WO2020063452A1 (zh) 一种资源调度方法和装置
WO2022206270A1 (zh) 设备添加方法、装置、蓝牙芯片及设备
WO2021109141A1 (zh) 通信连接配置方法、装置、通信设备及存储介质
KR102044523B1 (ko) 근거리 무선 통신 장치 및 방법
WO2021017755A1 (zh) 数据发送方法及用户设备
WO2024088173A1 (zh) 组播通信方法及相关装置
WO2023016403A1 (zh) 数据传输方法、装置、终端及网络侧设备
WO2024093922A1 (zh) 音频控制方法、存储介质、程序产品及电子设备
WO2022021190A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2021087854A1 (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: 17919504

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

Country of ref document: EP

Effective date: 20200225