WO2019192382A1 - 服务数据适配协议sdap实体的配置方法及设备 - Google Patents

服务数据适配协议sdap实体的配置方法及设备 Download PDF

Info

Publication number
WO2019192382A1
WO2019192382A1 PCT/CN2019/080092 CN2019080092W WO2019192382A1 WO 2019192382 A1 WO2019192382 A1 WO 2019192382A1 CN 2019080092 W CN2019080092 W CN 2019080092W WO 2019192382 A1 WO2019192382 A1 WO 2019192382A1
Authority
WO
WIPO (PCT)
Prior art keywords
sdap entity
drb
configuration information
target
entity
Prior art date
Application number
PCT/CN2019/080092
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 EP19782222.4A priority Critical patent/EP3780492A4/en
Priority to KR1020207030779A priority patent/KR102479784B1/ko
Priority to JP2020554263A priority patent/JP7335262B2/ja
Publication of WO2019192382A1 publication Critical patent/WO2019192382A1/zh
Priority to US17/037,391 priority patent/US11968728B2/en
Priority to US17/853,826 priority patent/US20220330356A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and a device for configuring a service data adaptation protocol SDAP entity.
  • the fifth generation of mobile communication technology has emerged.
  • the network side indication mechanism of the quality of service Qos
  • IP Internet Protocol
  • the indication information of the Qos for example, the QoS flow ID
  • a new protocol layer Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • SDAP Packet Data Convergence Protocol
  • a SDAP entity corresponds to a high-level Packet Data Unit (PDU Session), and a SDAP entity can send multiple data streams to a plurality of different Data Radio Bearers (DRBs), where One DRB corresponds to one PDCP entity.
  • PDU Session Packet Data Unit
  • DRBs Data Radio Bearers
  • the configuration of the SDAP entity of the terminal device is generally performed by the network side device sending the configuration command to the terminal device.
  • the configuration signaling requires a certain overhead, which causes the overhead when configuring the SDAP entity. Increase.
  • An object of the embodiments of the present disclosure is to provide a configuration method of a service data adaptation protocol SDAP entity to reduce the overhead of the SDAP entity configuration.
  • an embodiment of the present disclosure provides a method for configuring a service data adaptation protocol (SDAP) entity, which is applied to a terminal device, and the method includes:
  • the configuration information includes an identifier of the data radio bearer DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured;
  • the embodiment of the present disclosure further provides a method for configuring a service data adaptation protocol (SDAP) entity, which is applied to a network side device, and the method includes:
  • SDAP service data adaptation protocol
  • the configuration information includes an identifier of the data radio bearer DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured;
  • the configuration information is used by the terminal device to configure the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information.
  • an embodiment of the present disclosure further provides a terminal device, where the device includes:
  • a receiving module configured to receive configuration information, where the configuration information includes an identifier of a data radio bearer DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured;
  • a configuration module configured to configure, according to the configuration information, the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier.
  • the embodiment of the present disclosure further provides a network side device, where the device includes:
  • a sending module configured to send configuration information, where the configuration information includes an identifier of a data radio bearer DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured;
  • the configuration information is used by the terminal device to configure the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information.
  • an embodiment of the present disclosure further provides a terminal device, including:
  • the embodiment of the present disclosure further provides a network side device, including:
  • the embodiment of the present disclosure further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by the processor, implements the service described in the first aspect.
  • an embodiment of the present disclosure further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by a processor, implements the service described in the second aspect.
  • the configuration method and the device for adapting the SDAP entity are provided by the service data protocol provided by the embodiment of the present disclosure.
  • the configuration of the DRB can be configured to configure the target SDAP entity corresponding to the SDAP entity identifier. That is, in the embodiment of the present disclosure, the SDAP entity is configured in an implicit manner, so that the configuration signaling for configuring the SDAP entity is resent, and the configuration signaling overhead for configuring the SDAP entity is saved. Thereby reducing the overhead of the SDAP entity configuration.
  • SDAP Service Data Adaptation Protocol
  • FIG. 2 is a schematic diagram of a correspondence between a DRB and a SDAP entity in a method for configuring a data service adaptation protocol SDAP entity according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a correspondence between a SDAP entity, a PDU session, and a PDCP entity in a method for configuring a data service adaptation protocol SDAP entity according to an embodiment of the present disclosure
  • SDAP Service Data Adaptation Protocol
  • FIG. 5 is a flowchart of a third method for configuring a service data adaptation protocol SDAP entity according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a module composition of a terminal device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a module of a network side device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a network side device according to an embodiment of the present disclosure.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution advanced
  • New Radio, NR New Radio
  • the UE may also be referred to as a client, a mobile terminal, a mobile user device, or the like.
  • the UE may communicate with one or more core networks via a radio access network, such as a Radio Access Network (RAN).
  • RAN Radio Access Network
  • the terminal device may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket, handheld, computer built-in or in-vehicle mobile device that is wireless with The access network exchanges languages and/or data.
  • the network side device is configured to communicate with the terminal device, and may be a Base Transceiver Station (BTS) in GSM or CDMA, or a base station (NodeB) in WCDMA, or an evolved base station in LTE (evolutional Node) B, eNB or e-NodeB) and 5G base station (gNB), the embodiments of the present disclosure are not limited, but for convenience of description, the following embodiments are described by taking gNB as an example.
  • BTS Base Transceiver Station
  • NodeB base station
  • LTE evolutional Node
  • eNB evolved Node
  • gNB 5G base station
  • SDAP Service Data Adaptation Protocol
  • DRB Data Radio Bearer
  • PDCP Packet Data Convergence Protocol
  • Protocol Data Unit (PDU);
  • Non-access stratum NAS
  • An embodiment of the present disclosure provides a method for configuring a SDAP entity, where the method is applied to a terminal device, and may be performed by a terminal device.
  • 1 is a schematic flowchart of a method for configuring a SDAP entity according to an embodiment of the present disclosure. As shown in FIG. 1, the method includes:
  • Step 102 Receive configuration information, where the configuration information includes an identifier of the DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured.
  • the configuration information received in step 102 may be sent by the network side device.
  • the identifier of the DRB may be a unique identifier (ID) of the DRB
  • the identifier of the SDAP entity may be an ID of the SDAP entity.
  • the number of the DRBs to be configured may be one or more, and the number of the included SDAP entities may also be one or more.
  • a DRB to be configured corresponds to one SDAP entity, that is, one DRB can only be configured to one SDAP entity.
  • one SDAP entity can correspond to multiple DRBs.
  • the DRBs to be configured are DRB1, DRB2, and DRB3, DRB1 and DRB2 are corresponding to SDAP1, and DRB3 is corresponding to SDAP2, that is, both DRB1 and DRB2 are configured as SDAP1, and DRB3 is configured as SDAP2.
  • DRB1 and DRB2 can no longer be configured with SDAP2.
  • DRB3 can no longer be configured as SDAP1.
  • the correspondence between DRB1, DRB2, and DRB3 and SDAP1 and SDAP2 is as shown in FIG. 2.
  • one DRB can only correspond to one SDAP entity, so that the DRB can clearly know which SDAP entity to send data to, and avoid when the DRB corresponds to multiple SDAP entities, the DRB does not know which SDAP to send data to. Entity, and the situation where data transmission is confusing.
  • Step 104 Configure the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information.
  • the configuration of the DRB to be configured may include deleting or establishing a DRB to be configured, modifying a SDAP entity corresponding to the DBR to be configured, and the foregoing configuring the target SDAP entity corresponding to the SDAP entity identifier. This includes deleting the target SDAP entity, establishing the target SDAP entity, and so on.
  • the received configuration information includes the identifier of the DRB to be configured, and the SDAP entity identifier corresponding to the DRB to be configured, and the DRB to be configured according to the configuration information is configured, and the DRB is configured.
  • the configuration can be configured to configure the target SDAP entity corresponding to the SDAP entity identifier. That is, in the embodiment of the present disclosure, the SDAP entity is configured in an implicit manner, so that the configuration signaling for configuring the SDAP entity is resent, and the configuration signaling overhead for configuring the SDAP entity is saved. Thereby reducing the overhead of the SDAP entity configuration.
  • the foregoing configuration information is used to indicate that a DRB to be configured is established
  • the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier are configured according to the foregoing configuration information, which specifically includes:
  • the DRB to be configured is established and the target SDAP entity is established.
  • the terminal device searches whether the target SDAP entity has been established. If the target SDAP entity has not been established, the terminal device establishes the DRB to be configured and The target SDAP entity, and also needs to establish a correspondence between the DRB to be configured and the target SDAP entity.
  • the terminal device only needs to establish the DRB to be configured, and establish a correspondence between the DRB to be configured and the target SDAP entity.
  • the configuration information indicates that the DRB to be configured is set up, and the terminal device itself may be triggered to check whether the target SDAP entity has been established. If not, the terminal device is triggered to establish the target SDAP entity, and the network side device is not required to resend.
  • Establishing the configuration signaling of the target SDAP entity saves the configuration signaling overhead of establishing the target SDAP entity, thereby reducing the overhead of the SDAP entity configuration.
  • the SDAP entity corresponds to the PDU session of the upper layer, and the SDAP entity corresponds to a PDU session.
  • the corresponding relationship between the SDAP entity, the PDU session, and the DRB is shown in FIG. 3 .
  • one SDAP entity corresponds to two PDCPs.
  • the number of PDCP entities corresponding to one SDAP entity is not limited thereto.
  • the foregoing configuration information further includes a PDU session unit corresponding to the SDAP entity identifier
  • the method provided by the embodiment of the present disclosure further includes:
  • the target PDCP entity corresponding to the DRB to be configured may receive the data.
  • the data is sent to the target SDAP entity, thereby implementing data transmission between the DRB to be configured and the target SDAP entity.
  • the foregoing configuration information is used to indicate that the first SDAP entity corresponding to the DRB to be configured is modified into a target SDAP entity.
  • the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier are configured according to the foregoing configuration information, including:
  • the target SDAP entity is not established, the target SDAP entity is established, and the correspondence between the DRB to be configured and the target SDAP entity is established.
  • the first SDAP entity corresponding to the DRB to be configured is modified into the target SDAP entity, which is to modify the correspondence between the DRBs already existing on the terminal device, that is, the DRB and the first SDAP entity that are to be configured on the terminal device.
  • the corresponding relationship between the DRB and the target SDAP entity to be configured is required to be modified, and the corresponding relationship between the DRB to be configured and the first SDAP entity needs to be deleted.
  • the terminal device After the terminal device receives the configuration information, it searches for the target SDAP entity. If the target SDAP entity is not established, the target SDAP entity needs to be established, and the corresponding relationship between the DRB to be configured and the target SDAP entity is established. At the same time, the correspondence between the DRB to be configured and the target SDAP entity is released.
  • the mapping between the DRB to be configured and the target SDAP entity is required to be established, and the corresponding relationship between the DRB to be configured and the first SDAP entity is removed.
  • the configuration information indicates that the SDAP entity corresponding to the DRB to be configured existing on the terminal device is modified, and the terminal device may be triggered to detect whether the target SDAP entity has been established. If the target SDAP entity has not been established, The triggering terminal device establishes the target SDAP entity, and the network side device does not need to send the configuration signaling of the target SDAP entity, which saves the configuration signaling overhead of establishing the target SDAP entity, thereby reducing the configuration overhead of the SDAP entity.
  • the method provided by the embodiment of the present disclosure further includes:
  • the first SDAP entity corresponds to three DRBs, which are respectively recorded as DRB1, DRB2, and DRB3. If yes, the DRB to be configured in the configuration information is just DRB1, DRB2, and DRB3, but is established. After the mapping between the DRB1, the DRB2, and the DRB3 and the target SDAP entity, and deleting the correspondence between the DRB1, the DRB2, and the DRB3 and the first SDAP entity, the first SDAP entity does not have a corresponding DRB. In this case, the terminal device is triggered to delete the first SDAP entity.
  • the trigger may be triggered.
  • the terminal device deletes the first SDAP entity, and the network side device does not need to send the configuration signaling for deleting the first SDAP entity, which saves the configuration signaling overhead of configuring the first SDAP entity, thereby reducing the overhead of the SDAP entity configuration.
  • the foregoing configuration information is used to indicate that the DRB to be configured is deleted
  • the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier are configured according to the configuration information, including:
  • the DRB to be configured is all DRBs corresponding to the target SDAP entity, the DRB to be configured and the target SDAP entity are deleted.
  • the terminal device receives the configuration information, it is detected whether the target SDAP entity has been established, and whether the DRB to be configured is determined. All the DRBs corresponding to the target SDAP entity, if yes, delete the DRB to be configured and the target SDAP entity; if the DRB to be configured is not all DRBs corresponding to the target SDAP entity, the terminal device only needs to delete the DRB to be configured. Just fine.
  • the DRBs to be configured included in the foregoing configuration information are DRB1, DRB2, and DRB3, and DRB1, DRB2, and DRB3 correspond to the SDAP entity 1, and DRB1, DRB2, and DRB3 are all DRBs corresponding to the SDAP entity 1.
  • the information is used to delete DRB1, DRB2, and DRB3, the SDAP entity 1 is deleted while DRB1, DRB2, and DRB3 are deleted.
  • the configuration information indicates that the DRB to be configured is deleted, and the terminal device may be triggered to delete the target DRAP entity corresponding to the DRB, and the DRB to be configured is deleted.
  • the target SDAP entity so that when the number of the DRBs corresponding to the target SDAP entity is zero, the terminal device can be directly deleted to delete the target SDAP entity, and the network side device is not required to send the configuration signaling of the deleted target SDAP entity, saving The overhead of configuring signaling for configuring the target SDAP entity, thereby reducing the overhead of the SDAP entity configuration.
  • the foregoing configuration information further includes: a PDU session identifier corresponding to the SDAP entity identifier;
  • the method provided by the embodiment of the present disclosure further includes:
  • the correspondence between the target SDAP entity and the target PDU session corresponding to the PDU session identifier is deleted.
  • the method provided by the embodiment of the present disclosure further includes:
  • the delete notification message is used to notify the NAS entity that the target SDAP entity has been deleted.
  • the deletion notification message may be sent to the NAS while deleting the target SDAP entity, or may be sent to the NAS after the target SDAP entity is deleted.
  • the NAS by notifying the NAS of the message of deleting the target SDAP entity, the NAS can be prevented from continuing to send data to the target SDAP entity.
  • the foregoing deletion notification message includes at least one of the following information:
  • the SDAP entity identifier corresponding to the target SDAP entity is the SDAP entity identifier corresponding to the target SDAP entity.
  • the DRB identifier corresponding to the target SDAP entity is the DRB identifier corresponding to the target SDAP entity.
  • the foregoing deletion notification message may include one, two or three types of the SDAP entity identifier corresponding to the target entity, the PDU session identifier of the target PDU session corresponding to the target SDAP entity, and the DRB identifier corresponding to the target SDAP entity.
  • the configuration of the DRB can be configured to configure the target SDAP entity corresponding to the SDAP entity identifier. That is, in the embodiment of the present disclosure, the SDAP entity is configured in an implicit manner, so that the configuration signaling for configuring the SDAP entity is resent, and the configuration signaling overhead for configuring the SDAP entity is saved. Thereby reducing the overhead of the SDAP entity configuration.
  • FIG. 4 is a flowchart of a second method for configuring a service data adaptation protocol SDAP entity according to an embodiment of the present disclosure. The method shown in FIG. 4 includes at least the following steps:
  • Step 202 Send configuration information, where the configuration information includes an identifier of the DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured.
  • the configuration information is used by the terminal device to configure the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information.
  • step 202 the configuration information is sent to the terminal device, and the terminal device configures the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information.
  • the identifier of the DRB may be the ID of the DRB
  • the identifier of the SDAP entity may be the ID of the SDAP entity.
  • the number of the DRBs to be configured may be one or more, and the number of the included SDAP entities may also be one or more.
  • a DRB to be configured corresponds to one SDAP entity, that is, one DRB can only be configured to one SDAP entity.
  • one SDAP entity can correspond to multiple DRBs.
  • the DRBs to be configured are DRB1, DRB2, and DRB3, DRB1 and DRB2 are corresponding to SDAP1, and DRB3 is corresponding to SDAP2, that is, both DRB1 and DRB2 are configured as SDAP1, and DRB3 is configured as SDAP2.
  • DRB1 and DRB2 can no longer be configured as SDAP2.
  • DRB3 can no longer be configured as SDAP1.
  • one DRB can only correspond to one SDAP entity, so that the DRB can clearly know which SDAP entity to send data to, and avoid when the DRB corresponds to multiple SDAP entities, the DRB does not know which SDAP to send data to. Entity, and the situation where data transmission is confusing.
  • the configuration of the DRB to be configured according to the configuration information may be that the DRB to be configured is deleted, the DRB to be configured is established, or the SDAP entity corresponding to the DRB to be configured is modified, and the target SDAP entity corresponding to the SDAP entity identifier is configured. It can be to delete the target SDAP entity, establish the target SDAP entity, and so on.
  • the terminal device can be configured to configure the DRB to be configured according to the configuration information by sending the identifier of the DRB to be configured to the terminal device and the configuration information of the SDAP entity identifier corresponding to the DRB to be configured. And configuring the target SDAP entity corresponding to the SDAP entity identifier by configuring the DRB. That is, in the embodiment of the present disclosure, the SDAP entity is configured in an implicit manner, so that configuration signaling for configuring the SDAP entity is further sent to the terminal device, and configuration signaling for configuring the SDAP entity is saved. Overhead, which reduces the overhead of SDAP entity configuration.
  • the configuration information is used to indicate that the DRB to be configured is established in a specific embodiment of the disclosure.
  • the foregoing configuration information is further used to establish a DRB to be configured according to the foregoing configuration information, and establish a target SDAP entity, if the target SDAP entity is not established.
  • the terminal device searches whether the target SDAP entity has been established. If the target SDAP entity has not been established, the terminal device establishes according to the configuration information. The DRB and the target SDAP entity to be configured, and the corresponding relationship between the DRB to be configured and the target SDAP entity.
  • the terminal device only needs to establish the DRB to be configured, and establish a correspondence between the DRB to be configured and the target SDAP entity.
  • the configuration information sent to the terminal device indicates that the DRB to be configured is established, and the terminal device itself may be triggered to check whether the target SDAP entity has been established. If not, the terminal device is triggered to establish the target SDAP entity.
  • the configuration signaling of the target SDAP entity is sent to the terminal device, which saves the configuration signaling overhead for establishing the target SDAP entity, thereby reducing the overhead of the SDAP entity configuration.
  • the foregoing configuration information further includes a PDU session unit corresponding to the SDAP entity identifier
  • the foregoing configuration information is further used by the terminal device to establish, according to the configuration information, a correspondence between the target SDAP entity and the target PDU session corresponding to the PDU session identifier.
  • the foregoing configuration information is used to indicate that the first SDAP entity corresponding to the DRB to be configured is modified into a target SDAP entity.
  • the foregoing configuration information is further used to: if the target SDAP entity is not established, the terminal device establishes a target SDAP entity according to the configuration information, and establishes a correspondence between the DRB to be configured and the target SDAP entity.
  • the first SDAP entity corresponding to the DRB to be configured is modified into the target SDAP entity, which is to modify the correspondence between the DRBs already existing on the terminal device, that is, the DRB and the first SDAP entity that are to be configured on the terminal device.
  • the correspondence between the DRB to be configured and the target SDAP entity needs to be set to be corresponding to the target SDAP entity, that is, the mapping between the DRB to be configured and the first SDAP entity is required.
  • the terminal device searches for the target SDAP entity. If the target SDAP entity is not established, the target SDAP entity is established according to the configuration information, and the configuration is to be configured. Correspondence between the DRB and the target SDAP entity, and the corresponding relationship between the DRB to be configured and the target SDAP entity.
  • the terminal device establishes a correspondence between the DRB to be configured and the target SDAP entity according to the configuration information, and cancels the correspondence between the DRB to be configured and the first SDAP entity.
  • the configuration information sent to the terminal device indicates that the first SDAP entity corresponding to the DRB to be configured is modified to be the target SDAP entity, and the terminal device may be triggered to detect whether the target SDAP entity has been established.
  • the establishment of the target SDAP entity triggers the terminal device to establish the target SDAP entity, and does not need to resend the configuration signaling of the target SDAP entity to the terminal device, thereby saving the configuration signaling overhead for establishing the target SDAP entity, thereby reducing the SDAP entity.
  • the overhead of the configuration is not be used to detect whether the target SDAP entity has been established.
  • the DRB to be configured is all DRBs corresponding to the first SDAP entity
  • the foregoing configuration information is further used by the terminal device to delete the first SDAP entity according to the configuration information.
  • the first SDAP entity corresponds to three DRBs, which are respectively recorded as DRB1, DRB2, and DRB3. If yes, the DRB to be configured in the configuration information is just DRB1, DRB2, and DRB3, but is established. After the mapping between the DRB1, the DRB2, and the DRB3 and the target SDAP entity, and deleting the correspondence between the DRB1, the DRB2, and the DRB3 and the first SDAP entity, the first SDAP entity does not have a corresponding DRB. In this case, the terminal device is triggered to delete the first SDAP entity.
  • the terminal device when the configuration information sent to the terminal device indicates that the SDAP entity corresponding to the DRB to be configured already exists on the terminal device is modified, if the DRB to be configured is all DRBs corresponding to the first SDAP entity, The terminal device can be triggered to delete the first SDAP entity, and the configuration signaling of deleting the first SDAP entity is not required to be sent to the terminal device, thereby saving the configuration signaling overhead of configuring the first SDAP entity, thereby reducing the SDAP entity.
  • the overhead of the configuration when the configuration information sent to the terminal device indicates that the SDAP entity corresponding to the DRB to be configured already exists on the terminal device is modified, if the DRB to be configured is all DRBs corresponding to the first SDAP entity, The terminal device can be triggered to delete the first SDAP entity, and the configuration signaling of deleting the first SDAP entity is not required to be sent to the terminal device, thereby saving the configuration signaling overhead of configuring the first SDAP entity, thereby reducing the SDAP entity.
  • the foregoing configuration information is used to indicate that the DRB to be configured is deleted
  • the foregoing configuration information is further configured to: if the target SDAP entity has been established, and the DRB to be configured is all the DRBs corresponding to the target SDAP entity, the terminal device deletes the DRB to be configured and the target SDAP entity according to the configuration information.
  • the terminal device sends the configuration information to the terminal device, and the terminal device detects, according to the configuration information, whether the target SDAP entity has been established, and determines Whether the DRB to be configured is all the DRBs corresponding to the target SDAP entity, and if so, the DRB to be configured and the target SDAP entity are deleted; if the DRB to be configured is not all DRBs corresponding to the target SDAP entity, the terminal device only You need to delete the DRB to be configured.
  • the DRBs to be configured included in the foregoing configuration information are DRB1, DRB2, and DRB3, and DRB1, DRB2, and DRB3 correspond to the SDAP entity 1, and DRB1, DRB2, and DRB3 are all DRBs corresponding to the SDAP entity 1.
  • the information is used to delete DRB1, DRB2, and DRB3, the SDAP entity 1 is deleted while DRB1, DRB2, and DRB3 are deleted.
  • the configuration information sent to the terminal device indicates that the DRB to be configured is deleted, and the terminal device can be triggered to detect that the target SDAP entity corresponding to the DRB has been established, and the DRB to be configured is all corresponding to the target SDAP entity.
  • the target SDAP entity is deleted, so that when the number of the DRBs corresponding to the target SDAP entity is zero, the terminal device may be triggered to directly delete the target SDAP entity, and the network side device is not required to send the deleted target SDAP entity.
  • the configuration signaling saves the configuration signaling overhead of configuring the target SDAP entity, thereby reducing the overhead of the SDAP entity configuration.
  • the foregoing configuration information further includes: a PDU session identifier corresponding to the SDAP entity identifier;
  • the foregoing configuration information is further used by the terminal device to delete the correspondence between the target SDAP entity and the target PDU session corresponding to the PDU session identifier according to the configuration information.
  • the terminal may be configured to send the identifier of the DRB to be configured to the terminal device and the configuration information of the SDAP entity identifier corresponding to the DRB to be configured.
  • the device configures the DRB to be configured according to the configuration information, and configures the target SDAP entity corresponding to the SDAP entity identifier by configuring the DRB. That is, in the embodiment of the present disclosure, the SDAP entity is configured in an implicit manner, so that configuration signaling for configuring the SDAP entity is further sent to the terminal device, and configuration signaling for configuring the SDAP entity is saved. Overhead, which reduces the overhead of SDAP entity configuration.
  • FIG. 5 is a flowchart of a third method for configuring a service data adaptation protocol SDAP entity according to an embodiment of the present disclosure. The method shown in FIG. 5 includes at least the following steps:
  • Step 302 The network side device sends the configuration information to the terminal device, where the configuration information includes the identifier of the DRB to be configured, and the SDAP entity identifier corresponding to the DRB to be configured.
  • Step 304 The terminal device receives the foregoing configuration information sent by the network side device.
  • Step 306 The terminal device configures the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information.
  • the configuration method of the service data adaptation protocol SDAP entity provided by the embodiment of the present disclosure implements the configuration of the SDAP entity in an implicit manner, so that the configuration signaling for configuring the SDAP entity is further sent to the terminal device.
  • the overhead of configuration signaling for configuring the SDAP entity is saved, thereby reducing the overhead of the SDAP entity configuration.
  • the embodiment of the present disclosure provides a terminal device, and the terminal device provided by the embodiment of the present disclosure can implement various processes implemented by the terminal device in the foregoing embodiment.
  • FIG. 6 is a schematic diagram of a module structure of a terminal device according to an embodiment of the present disclosure.
  • the terminal device shown in FIG. 6 includes at least:
  • the receiving module 401 is configured to receive configuration information, where the configuration information includes an identifier of the DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured.
  • the configuration module 402 is configured to configure the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the foregoing configuration information.
  • the foregoing configuration information is used to indicate that the DRB to be configured is established
  • the foregoing configuration module 402 is specifically configured to:
  • the DRB to be configured is established and the target SDAP entity is established.
  • the foregoing configuration information is used to indicate that the first SDAP entity corresponding to the DRB to be configured is modified to be the target SDAP entity.
  • the foregoing configuration module 402 is specifically configured to:
  • the target SDAP entity is not established, the target SDAP entity is established, and the correspondence between the DRB to be configured and the target SDAP entity is established.
  • the device further includes:
  • the first deleting module is configured to delete the first SDAP entity.
  • the foregoing configuration information is used to indicate that the DRB to be configured is deleted.
  • the foregoing configuration module 402 is specifically configured to:
  • the DRB to be configured is all DRBs corresponding to the target SDAP entity, the DRB to be configured and the target SDAP entity are deleted.
  • one DRB to be configured corresponds to one SDAP entity.
  • the foregoing configuration information further includes: a PDU session identifier corresponding to the SDAP entity identifier;
  • the above equipment further includes:
  • a second deleting module configured to delete a correspondence between the target SDAP entity and the target PDU session corresponding to the PDU session identifier.
  • the foregoing apparatus further includes:
  • a sending module configured to send a delete notification message to the NAS entity, where the delete notification message is used to notify the NAS entity that the target SDAP entity has been deleted.
  • the foregoing deletion notification message includes at least one of the following information:
  • the DRB identifier corresponding to the target SDAP entity is the DRB identifier corresponding to the target SDAP entity.
  • the terminal device provided by the embodiment of the present disclosure can implement the configuration of the target SDAP entity corresponding to the SDAP entity identifier by configuring the DRB. That is, in the embodiment of the present disclosure, the SDAP entity is configured in an implicit manner, so that the configuration signaling for configuring the SDAP entity is resent, and the configuration signaling overhead for configuring the SDAP entity is saved. Thereby reducing the overhead of the SDAP entity configuration.
  • this embodiment provides a network side device, and the network side device provided by the embodiment of the present disclosure can implement various processes implemented by the network side device in the foregoing embodiment. .
  • FIG. 7 is a schematic structural diagram of a module of a network side device according to an embodiment of the present disclosure.
  • the network side device shown in FIG. 7 includes at least:
  • the sending module 501 is configured to send configuration information, where the configuration information includes an identifier of the DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured.
  • the configuration information is used by the terminal device to configure the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information.
  • the foregoing configuration information is used to indicate that the DRB to be configured is established
  • the configuration information is further configured to: if the target SDAP entity is not established, the terminal device establishes a DRB to be configured according to the configuration information, and establishes a target SDAP entity.
  • the foregoing configuration information is used to indicate that the first SDAP entity corresponding to the DRB to be configured is modified to be the target SDAP entity.
  • the configuration information is further configured to: if the target SDAP entity is not established, the terminal device establishes a target SDAP entity according to the configuration information, and establishes a correspondence between the DRB to be configured and the target SDAP entity.
  • the DRB to be configured is all DRBs corresponding to the first SDAP entity
  • the foregoing configuration information is further used by the terminal device to delete the first SDAP entity according to the configuration information.
  • the foregoing configuration information is used to indicate that the DRB to be configured is deleted.
  • the foregoing configuration information is further configured to: if the target SDAP entity has been established, and the DRB to be configured is all the DRBs corresponding to the target SDAP entity, the terminal device deletes the DRB to be configured and the target SDAP entity according to the configuration information.
  • one DRB to be configured corresponds to one SDAP entity.
  • the foregoing configuration information further includes: a protocol data unit PDU session identifier corresponding to the SDAP entity identifier;
  • the configuration information is further used by the terminal device to delete the correspondence between the target SDAP entity and the target PDU session corresponding to the PDU session identifier according to the configuration information.
  • the network side device provided by the embodiment of the present disclosure can enable the terminal device to be configured according to the configuration information by sending the identifier of the DRB to be configured to the terminal device and the configuration information of the SDAP entity identifier corresponding to the DRB to be configured.
  • the DRB is configured, and the configuration of the DRB can be configured to configure the target SDAP entity corresponding to the SDAP entity identifier. That is, in the embodiment of the present disclosure, the SDAP entity is configured in an implicit manner, so that configuration signaling for configuring the SDAP entity is further sent to the terminal device, and configuration signaling for configuring the SDAP entity is saved. Overhead, which reduces the overhead of SDAP entity configuration.
  • this embodiment provides a terminal device, and the terminal device provided by the embodiment of the present disclosure can implement various processes implemented by the terminal device in the foregoing embodiment.
  • FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • the terminal device 600 includes: at least one processor 601, a memory 602, at least one network interface 604, and a user interface 603.
  • the various components in terminal device 600 are coupled together by a bus system 605.
  • the bus system 605 is used to implement connection communication between these components.
  • the bus system 605 includes a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as bus system 605 in FIG.
  • the user interface 603 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touchpad, or a touch screen, etc.).
  • a pointing device eg, a mouse, a trackball, a touchpad, or a touch screen, etc.
  • the memory 602 in an embodiment of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • the memory 602 of the systems and methods described in the embodiments of the present disclosure is intended to comprise, without being limited to, these and any other suitable types of memory.
  • memory 602 stores elements, executable modules or data structures, or a subset thereof, or their set of extensions: operating system 6021 and application 6022.
  • the operating system 6021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks.
  • the application 6022 includes various applications, such as a media player (Media Player), a browser, and the like, for implementing various application services.
  • a program implementing the method of the embodiments of the present disclosure may be included in the application 6022.
  • the terminal device 600 further includes: a memory 602, a processor 601, a computer program stored on the memory 602 and executable on the processor 601.
  • a computer program stored on the memory 602 and executable on the processor 601.
  • the configuration information includes an identifier of the data radio bearer DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured;
  • Processor 601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 601 or an instruction in a form of software.
  • the processor 601 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present disclosure may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software modules can be located in a conventional computer readable storage medium of the art, such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the computer readable storage medium is located in a memory 602, and the processor 601 reads the information in the memory 602 and, in conjunction with its hardware, performs the steps of the above method.
  • the computer readable storage medium stores a computer program, and when the computer program is executed by the processor 601, the steps in the above embodiments are implemented.
  • the embodiments described in the embodiments of the present disclosure may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processing (DSP), Digital Signal Processing Equipment (DSP Device, DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general purpose processor, controller, microcontroller, microprocessor, other for performing the functions described in this disclosure In an electronic unit or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device Digital Signal Processing Equipment
  • PLD programmable Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the techniques described in the embodiments of the present disclosure may be implemented by modules (eg, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • the software code can be stored in memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • the configuration information is used to indicate that the DRB to be configured is established
  • the configuring the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information including:
  • the DRB to be configured is established, and the target SDAP entity is established.
  • the configuration information is used to indicate that the first SDAP entity corresponding to the DRB to be configured is modified to the target SDAP entity;
  • the configuring the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information including:
  • the target SDAP entity is not established, the target SDAP entity is established, and the correspondence between the DRB to be configured and the target SDAP entity is established.
  • the method further includes:
  • the first SDAP entity is deleted.
  • the configuration information is used to indicate deleting the DRB to be configured
  • the configuring the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information including:
  • the DRB to be configured is all DRBs corresponding to the target SDAP entity, the DRB to be configured and the target SDAP entity are deleted.
  • a DRB to be configured corresponds to one SDAP entity.
  • the configuration information further includes: a protocol data unit PDU session identifier corresponding to the SDAP entity identifier;
  • the method further includes: after deleting the DRB to be configured and the target SDAP entity, the method further includes:
  • the method further includes:
  • the deletion notification message includes at least one of the following information:
  • the DRB identifier corresponding to the target SDAP entity is the DRB identifier corresponding to the target SDAP entity.
  • the target SDAP entity corresponding to the SDAP entity identifier can be configured by using the terminal device provided by the embodiment of the present disclosure. That is, in the embodiment of the present disclosure, the SDAP entity is configured in an implicit manner, so that the configuration signaling for configuring the SDAP entity is resent, and the configuration signaling overhead for configuring the SDAP entity is saved. Thereby reducing the overhead of the SDAP entity configuration.
  • the terminal device 600 can implement various processes implemented by the terminal device in the foregoing embodiment. To avoid repetition, details are not described herein again.
  • this embodiment provides a network side device, and the network side device provided by the embodiment of the present disclosure can implement various processes implemented by the network side device in the foregoing embodiment. .
  • FIG. 9 is a schematic structural diagram of a network side device according to an embodiment of the present disclosure.
  • the network side device 700 includes a processor 701, a transceiver 702, a memory 703, a user interface 704, and a bus interface.
  • the network side device 700 further includes: a computer program stored on the memory 703 and executable on the processor 701. When the computer program is executed by the processor 701, the following steps are implemented:
  • the configuration information includes an identifier of the data radio bearer DRB to be configured, and a SDAP entity identifier corresponding to the DRB to be configured;
  • the configuration information is used by the terminal device to configure the DRB to be configured and the target SDAP entity corresponding to the SDAP entity identifier according to the configuration information.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 701 and various circuits of memory represented by memory 703.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 702 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the user interface 704 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 701 is responsible for managing the bus architecture and general processing, and the memory 703 can store data used by the processor 701 in performing operations.
  • the configuration information is used to indicate that the DRB to be configured is established
  • the configuration information is further used to establish the DRB to be configured according to the configuration information, and establish the target SDAP entity, if the target SDAP entity is not established.
  • the configuration information is used to indicate that the first SDAP entity corresponding to the DRB to be configured is modified to the target SDAP entity;
  • the configuration information is further configured to: if the target SDAP entity is not established, the terminal device establishes the target SDAP entity according to the configuration information, and establish a correspondence between the DRB to be configured and the target SDAP entity.
  • the computer program stored in the memory 703 is executed by the processor 701, if the DRB to be configured is all DRBs corresponding to the first SDAP entity;
  • the configuration information is further used by the terminal device to delete the first SDAP entity according to the configuration information.
  • the configuration information is used to indicate deleting the DRB to be configured
  • the configuration information is further configured to: if the target SDAP entity has been established, and the DRB to be configured is all DRBs corresponding to the target SDAP entity, the terminal device deletes the to-be-configured according to the configuration information. DRB and the target SDAP entity.
  • a DRB to be configured corresponds to one SDAP entity.
  • the configuration information further includes: a protocol data unit PDU session identifier corresponding to the SDAP entity identifier;
  • the configuration information is further used by the terminal device to delete a correspondence between the target SDAP entity and the target PDU session corresponding to the PDU session identifier according to the configuration information.
  • the terminal device can be configured to configure the DRB to be configured according to the configuration information by sending the identifier of the DRB to be configured to the terminal device and the configuration information of the SDAP entity identifier corresponding to the DRB to be configured. And configuring the target SDAP entity corresponding to the SDAP entity identifier by configuring the DRB. That is, in the embodiment of the present disclosure, the SDAP entity is configured in an implicit manner, so that configuration signaling for configuring the SDAP entity is further sent to the terminal device, and configuration signaling for configuring the SDAP entity is saved. Overhead, which reduces the overhead of SDAP entity configuration.
  • the network side device 700 can implement various processes implemented by the network side device in the foregoing embodiment, and achieve the same technical effect. To avoid repetition, details are not described herein again.
  • the embodiment of the present disclosure further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by the processor, the method for configuring the service data adaptation protocol SDAP entity in the foregoing embodiment is implemented.
  • the process of the embodiment of the service data adaptation protocol SDAP entity in the foregoing embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, we will not repeat them here.
  • the computer readable storage medium such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the embodiments of the present disclosure, or the part contributing to the related art, or the part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the presently disclosed embodiments.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

本公开实施例公开了一种服务数据适配协议SDAP实体的配置方法及设备，该方法包括：接收配置信息；其中，该配置信息中包括待配置的DRB的标识，及与待配置的DRB对应的SDAP实体标识；根据上述配置信息，配置待配置的DRB及与SDAP实体标识对应的目标SDAP实体。

Description

服务数据适配协议SDAP实体的配置方法及设备
相关申请的交叉引用
本申请主张在2018年4月2日在中国提交的中国专利申请号No.201810284821.0的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种服务数据适配协议SDAP实体的配置方法及设备。
背景技术
随着通信技术的发展，出现了第五代移动通信技术(fifth-generation，5G)。并且在5G系统中引入了服务质量(Quality of Service，Qos)的网络侧指示机制，因此，需要在上行数据和下行数据的发送过程中加入终端设备的互联网协议(Internet Protocol，IP)数据流的Qos的指示信息(例如，QoSflow ID)，因此，在现有的包数据汇聚协议(Packet Data Convergence Protocol，PDCP)层之上引入一个新的协议层，服务数据适配协议(Service Data Adaptation Protocol，SDAP)层。
并且，一个SDAP实体对应一个高层的包数据单元会话(Packet Data Unit，PDU Session),一个SDAP实体可以将多个数据流发送给多个不同的数据无线承载(Data Radio Bearer，DRB)，其中，一个DRB对应一个PDCP实体。
相关技术中，在对终端设备的SDAP实体进行配置时，一般通过网络侧设备向终端设备发送配置指令的方式进行，但是，配置信令需要一定的开销，从而导致在进行SDAP实体配置时，开销增大。
发明内容
本公开实施例的目的是提供一种服务数据适配协议SDAP实体的配置方法，以减少SDAP实体配置的开销。
为解决上述技术问题，本公开实施例是这样实现的：
第一方面，本公开实施例提供了一种服务数据适配协议SDAP实体的配置方法，应用于终端设备，该方法包括：
接收配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
第二方面，本公开实施例还提供了一种服务数据适配协议SDAP实体的配置方法，应用于网络侧设备，该方法包括：
发送配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
其中，所述配置信息用于终端设备根据所述配置信息配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
第三方面，本公开实施例还提供了一种终端设备，该设备包括：
接收模块，用于接收配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
配置模块，用于根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
第四方面，本公开实施例还提供了一种网络侧设备，该设备包括：
发送模块，用于发送配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
其中，所述配置信息用于终端设备根据所述配置信息配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
第五方面，本公开实施例还提供了一种终端设备，包括：
存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述第一方面所述的服务数据适配协议SDAP实体的配置方法的步骤。
第六方面，本公开实施例还提供了一种网络侧设备，包括：
存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述第二方面所述的服务 数据适配协议SDAP实体的配置方法的步骤。
第七方面，本公开实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现上述第一方面所述的服务数据适配协议SDAP实体的配置方法的步骤。
第八方面，本公开实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现上述第二方面所述的服务数据适配协议SDAP实体的配置方法的步骤。
通过本公开实施例提供的服务数据协议适配SDAP实体的配置方法及设备，通过对DRB的配置可以实现对SDAP实体标识对应的目标SDAP实体进行配置。即在本公开实施例中实现了通过隐式的方式对SDAP实体进行配置，这样，避免了再发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本公开的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是本公开的一个实施例中一种服务数据适配协议SDAP实体的配置方法的第一种方法流程图。
图2为本公开的一个实施例中一种数据服务适配协议SDAP实体的配置方法中，DRB与SDAP实体的对应关系示意图；
图3为本公开的一个实施例中一种数据服务适配协议SDAP实体的配置方法中，SDAP实体、PDU会话以及PDCP实体对应关系的示意图；
图4是本公开的一个实施例中一种服务数据适配协议SDAP实体的配置方法的第二种方法流程图。
图5为本公开的一个实施例中一种服务数据适配协议SDAP实体的配置方法的第三种方法流程图。
图6是本公开的一个实施例中一种终端设备的模块组成示意图。
图7为本公开的一个实施例中一种网络侧设备的模块组成示意图。
图8为本公开的一个实施例中一种终端设备的结构示意图。
图9为本公开的一个实施例中一种网络侧设备的结构示意图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。说明书以及权利要求中使用“和/或”表示连接对象至少其中之一。
本公开的技术方案，可以应用于各种通信系统，例如：全球移动通讯系统(Global System of Mobile communication，GSM)、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)、增强长期演进(Long Term Evolution advanced，LTE-A)、新空口(New Radio，NR)等。
UE，也可称之为用户端、移动终端(Mobile Terminal)、移动用户设备等。UE可以经无线接入网，例如无线电接入网(Radio Access Network，RAN)，与一个或多个核心网进行通信。终端设备可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。
网络侧设备，用于与终端设备通信，可以是GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB)，还可以是LTE中的演进型基站(evolutional Node B，eNB或e-NodeB)及5G基站(gNB)，本公开实施例并不限定，但为描述方便，下述实施例以gNB为例进行说明。
以下结合附图，详细说明本公开各实施例提供的技术方案。
本公开实施例中涉及到的英文缩写注释如下。
服务数据适配协议(Service Data Adaptation Protocol，SDAP)；
数据无线承载(Data Radio Bearer，DRB)；
包数据汇聚协议(Packet Data Convergence Protocol，PDCP)；
协议数据单元(Protocol Data Unit，PDU)；
非接入层(Non-access stratum，NAS)。
本公开一实施例提供了一种SDAP实体的配置方法，该方法应用于终端设备，可以由终端设备执行。图1是本公开一个实施例提供的SDAP实体的配置方法的流程示意图，如图1所示，该方法包括：
步骤102，接收配置信息；其中，该配置信息中包括待配置的DRB的标识，及与所述待配置的DRB对应的SDAP实体标识。
具体的，在步骤102中接收的配置信息可以是由网络侧设备发送的。其中，上述DRB的标识可以是DRB的唯一编码(identification，ID)，上述SDAP实体标识可以是SDAP实体的ID。
在上述配置信息中，包括的待配置的DRB的数量可以为一个或者多个，包括的SDAP实体的数量也可以为一个或者多个。但是，一个待配置的DRB对应一个SDAP实体，即一个DRB只能被配置给一个SDAP实体。然而，一个SDAP实体可以对应多个DRB。
例如，上述配置信息中，待配置的DRB为DRB1、DRB2和DRB3，DRB1和DRB2对应SDAP1，DRB3对应SDAP2，即DRB1和DRB2均被配置为SDAP1，DRB3被配置为SDAP2，在该种情况下，DRB1和DRB2不能再被配置SDAP2,同样的，DRB3也不能再被配置为SDAP1。在该种情况下，DRB1、DRB2、DRB3与SDAP1、SDAP2的对应关系如图2所示。
在本公开实施例中，一个DRB只能对应一个SDAP实体，使得DRB可以清楚的知道将数据发送至哪个SDAP实体，避免出现当DRB对应多个SDAP实体时，DRB不清楚将数据发送给哪个SDAP实体，而出现数据发送混乱的情况。
步骤104，根据上述配置信息，配置待配置的DRB及与上述SDAP实体标识对应的目标SDAP实体。
具体的，在本公开实施例中，上述配置待配置的DRB可以包括删除或建立待配置的DRB，修改待配置的DBR对应的SDAP实体等，上述对SDAP 实体标识对应的目标SDAP实体进行配置可以包括删除目标SDAP实体、建立目标SDAP实体等。
在本公开实施例中，接收到的配置信息中包括待配置的DRB的标识，以及与该待配置的DRB对应的SDAP实体标识，根据该配置信息对待配置的DRB进行配置，并且通过对DRB的配置可以实现对SDAP实体标识对应的目标SDAP实体进行配置。即在本公开实施例中实现了通过隐式的方式对SDAP实体进行配置，这样，避免了再发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
在本公开的一个具体实施例中，上述配置信息用于指示建立待配置的DRB；
相应的，上述步骤104中，根据上述配置信息，配置待配置的DRB及与SDAP实体标识对应的目标SDAP实体，具体包括：
若未建立目标SDAP实体，则建立待配置的DRB，并建立目标SDAP实体。
具体的，在本公开实施例中，当终端设备接收到上述配置信息后，终端设备查找当前是否已经建立了上述目标SDAP实体，若是还未建立目标SDAP实体，则终端设备建立上述待配置DRB以及目标SDAP实体，并且还需要建立待配置的DRB与目标SDAP实体的对应关系。
若是终端设备已经建立了目标SDAP实体，则终端设备只需要建立上述待配置的DRB，并建立待配置的DRB与目标SDAP实体的对应关系即可。
在本公开实施例中，通过配置信息指示建立待配置的DRB，可以触发终端设备自身检查是否已经建立目标SDAP实体，若是没有，则触发终端设备建立该目标SDAP实体，不需要网络侧设备再发送建立目标SDAP实体的配置信令，节省了对目标SDAP实体进行建立的配置信令的开销，从而降低了SDAP实体配置的开销。
由于SDAP实体除了与DRB对应外，SDAP实体还与高层的PDU会话对应，一个SDAP实体对应一个PDU会话，其中，SDAP实体、PDU会话以及DRB的一种对应关系如图3所示。
在图3所示的为SDAP实体与PDU会话，以及DRB对应的PDCP实体的对应关系，一个DRB对应一个PDCP实体。在图3所示的情况中，列举了一个SDAP实体对应两个PDCP的情况，实际上一个SDAP实体对应的PDCP实体的个数并不局限于此。
因此，在本公开实施例中，上述配置信息中还包括与SDAP实体标识对应的PDU会话单元；
相应的，在上述建立待配置的DRB，并建立目标SDAP实体后，本公开实施例提供的方法还包括：
建立目标SDAP实体与PDU会话标识对应的目标PDU会话的对应关系。
另外，在本公开实施例中，当建立了待配置的DRB、目标SDAP实体以及待配置的DRB与目标SDAP实体的对应关系后，待配置的DRB对应的目标PDCP实体在接收到数据后，可以将该数据发送给目标SDAP实体，从而实现了待配置的DRB与目标SDAP实体之间的数据传输。
在本公开的一个具体实施例中，上述配置信息用于指示将待配置的DRB对应的第一SDAP实体修改为目标SDAP实体；
相应的，在上述步骤104中，根据上述配置信息，配置待配置的DRB以及与SDAP实体标识对应的目标SDAP实体，包括：
若未建立目标SDAP实体，则建立目标SDAP实体，并建立待配置的DRB与目标SDAP实体的对应关系。
其中，上述将待配置的DRB对应的第一SDAP实体修改为目标SDAP实体，指的是修改终端设备上已经存在的DRB的对应关系，即原来在终端设备上待配置的DRB与第一SDAP实体对应，需要将待配置的DRB的对应关系修改为与目标SDAP实体对应，即需要解除待配置的DRB与第一SDAP实体的对应关系，并建立待配置的DRB与目标SDAP实体的对应关系。
在该种情况下，当终端设备接收到配置信息后，查找是否已经建立目标SDAP实体，若是未建立目标SDAP实体，则需要建立目标SDAP实体，并建立待配置的DRB与目标SDAP实体的对应关系，同时解除待配置的DRB与目标SDAP实体的对应关系。
若是终端设备已经建立上述目标SDAP实体，则只需要建立待配置的 DRB与目标SDAP实体的对应关系，并解除待配置的DRB与第一SDAP实体的对应关系即可。
在本公开实施例中，通过配置信息指示修改终端设备上已经存在的待配置的DRB所对应的SDAP实体，可以触发终端设备检测自身是否已经建立目标SDAP实体，若是还未建立目标SDAP实体，则触发终端设备建立目标SDAP实体，不需要网络侧设备再发送建立目标SDAP实体的配置信令，节省了对目标SDAP实体进行建立的配置信令的开销，从而降低了SDAP实体配置的开销。
在一种具体实施方式中，若上述待配置的DRB为第一SDAP实体对应的所有的DRB，则本公开实施例提供的方法，还包括：
删除第一SDAP实体。
例如，在一种具体实施方式中，第一SDAP实体对应三个DRB，分别记为DRB1、DRB2和DRB3，若是，上述配置信息中的待配置的DRB刚好为DRB1、DRB2和DRB3，则在建立DRB1、DRB2和DRB3与目标SDAP实体的对应关系，并删除DRB1、DRB2和DRB3与第一SDAP实体的对应关系后，第一SDAP实体不存在对应的DRB，这时，触发终端设备删除该第一SDAP实体。
在本公开实施例中，当配置信息指示修改终端设备上已经存在的待配置的DRB所对应的SDAP实体时，若是待配置的DRB为第一SDAP实体对应的所有的DRB，这时，可以触发终端设备删除第一SDAP实体，不需要网络侧设备再发送删除第一SDAP实体的配置信令，节省了对第一SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
另外，在本公开的另一个具体实施例中，上述配置信息用于指示删除待配置的DRB；
在该种情况下，上述步骤104中，根据配置信息，配置待配置的DRB以及与SDAP实体标识对应的目标SDAP实体，包括：
若已经建立目标SDAP实体且待配置的DRB为目标SDAP实体对应的所有DRB，则删除待配置的DRB以及目标SDAP实体。
具体的，在本公开实施例中，若是上述配置信息用于指示删除待配置的 DRB，则当终端设备接收到该配置信息后，检测是否已经建立目标SDAP实体，以及判断上述待配置的DRB是否为目标SDAP实体对应的所有的DRB，若是，则删除上述待配置的DRB以及目标SDAP实体；若是待配置的DRB并不是目标SDAP实体对应的所有的DRB，则终端设备只需要删除待配置的DRB即可。
例如，上述配置信息中包括的待配置的DRB为DRB1、DRB2和DRB3，DRB1、DRB2和DRB3对应SDAP实体1，并且，DRB1、DRB2和DRB3为SDAP实体1对应的所有的DRB，则当上述配置信息用于指示删除DRB1、DRB2和DRB3时，则在删除DRB1、DRB2和DRB3的同时，删除SDAP实体1。
在本公开实施例中，通过配置信息指示删除待配置的DRB，可以触发终端设备在检测到DRB对应的目标SDAP实体已经建立，并且待配置的DRB为目标SDAP实体对应的所有的DRB时，删除目标SDAP实体，这样，在检测到目标SDAP实体对应的DRB的数量为零个时，可以触发终端设备直接删除该目标SDAP实体，不需要网络侧设备再发送删除目标SDAP实体的配置信令，节省了对目标SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
另外，在本公开实施例中，当删除了目标SDAP实体后，目标SDAP实体对应的PDU会话不存在对应的SDAP实体，因此，还需要删除目标SDAP实体对应的PDU会话。因此，在本公开实施例中，上述配置信息中，还包括：与SDAP实体标识对应的PDU会话标识；
相应的，在上述删除待配置的DRB及目标SDAP实体之后，本公开实施例提供的方法还包括：
删除目标SDAP实体与PDU会话标识对应的目标PDU会话的对应关系。
另外，在本公开实施例中，为了避免出现NAS向已经删除的SDAP实体发送数据的情况，需要将目标SDAP实体被删除的消息通知给NAS，因此，本公开实施例提供的方法，还包括：
向NAS实体发送删除通知消息，该删除通知消息用于通知NAS实体目标SDAP实体已经被删除。
具体的，可以在删除目标SDAP实体的同时向NAS发送上述删除通知消息，也可以是在目标SDAP实体删除完毕后，向NAS发送上述删除通知消息。
在本公开实施例中，通过将目标SDAP实体删除的消息通知给NAS，可以避免NAS继续向目标SDAP实体发送数据。
其中，上述删除通知消息包括以下信息中的至少一种：
目标SDAP实体对应的SDAP实体标识；
目标SDAP实体对应的目标PDU会话的PDU会话标识；
目标SDAP实体对应的DRB标识。
具体的，上述删除通知消息可以包括目标实体对应的SDAP实体标识、目标SDAP实体对应的目标PDU会话的PDU会话标识以及目标SDAP实体对应的DRB标识中的一种、两种或者三种。
通过本公开实施例提供的服务数据适配协议SDAP实体的配置方法，通过对DRB的配置可以实现对SDAP实体标识对应的目标SDAP实体进行配置。即在本公开实施例中实现了通过隐式的方式对SDAP实体进行配置，这样，避免了再发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
与上述实施例相对应，本公开一个实施例还提供了一种服务数据适配协议SDAP实体的配置方法，应用于网络侧设备，在本公开实施例中，与上述实施例相同的部分的详细描述可参考上述实施例的内容，本实施例不再重复。图4为本公开实施例提供的服务数据适配协议SDAP实体的配置方法的第二种方法流程图，图4所示的方法，至少包括如下步骤：
步骤202，发送配置信息；其中，该配置信息中包括待配置的DRB的标识，及与待配置的DRB对应的SDAP实体标识；
其中，上述配置信息用于终端设备根据配置信息配置待配置的DRB及与SDAP实体标识对应的目标SDAP实体。
具体的，在步骤202中，将配置信息发送给终端设备，由终端设备根据该配置信息配置待配置的DRB及与上述SDAP实体标识对应的目标SDAP实体。
其中，上述DRB的标识可以是DRB的ID，上述SDAP实体标识可以是SDAP实体的ID。
在上述配置信息中，包括的待配置的DRB的数量可以为一个或者多个，包括的SDAP实体的数量也可以为一个或者多个。但是，一个待配置的DRB对应一个SDAP实体，即一个DRB只能被配置给一个SDAP实体。然而，一个SDAP实体可以对应多个DRB。
例如，上述配置信息中，待配置的DRB为DRB1、DRB2和DRB3，DRB1和DRB2对应SDAP1，DRB3对应SDAP2，即DRB1和DRB2均被配置为SDAP1，DRB3被配置为SDAP2，在该种情况下，DRB1和DRB2不能再被配置为SDAP2,同样的，DRB3也不能再被配置为SDAP1。
在本公开实施例中，一个DRB只能对应一个SDAP实体，使得DRB可以清楚的知道将数据发送至哪个SDAP实体，避免出现当DRB对应多个SDAP实体时，DRB不清楚将数据发送给哪个SDAP实体，而出现数据发送混乱的情况。
其中，上述终端设备根据配置信息配置待配置的DRB可以是删除待配置的DRB、建立待配置的DRB，或者修改待配置的DRB对应的SDAP实体等；上述配置与SDAP实体标识对应的目标SDAP实体，可以是删除目标SDAP实体、建立目标SDAP实体等。
在本公开实施例中，通过向终端设备发送包括待配置的DRB的标识，以及与该待配置的DRB对应的SDAP实体标识的配置信息，可以使终端设备根据该配置信息对待配置的DRB进行配置，并且通过对DRB的配置可以实现对SDAP实体标识对应的目标SDAP实体进行配置。即在本公开实施例中实现了通过隐式的方式对SDAP实体进行配置，这样，避免了再向终端设备发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
其中，在本公开的一个具体实施例中，上述配置信息用于指示建立待配置的DRB；
相应的，上述配置信息还用于若未建立目标SDAP实体，则终端设备根据上述配置信息建立待配置的DRB，并建立目标SDAP实体。
具体的，在本公开实施例中，当将上述配置信息发送给终端设备后，终端设备查找当前是否已经建立了上述目标SDAP实体，若是还未建立目标SDAP实体，则终端设备根据上述配置信息建立上述待配置DRB以及目标SDAP实体，并且还需要建立待配置的DRB与目标SDAP实体的对应关系。
若是终端设备已经建立了目标SDAP实体，则终端设备只需要建立上述待配置的DRB，并建立待配置的DRB与目标SDAP实体的对应关系即可。
在本公开实施例中，通过发送给终端设备的配置信息指示建立待配置的DRB，可以触发终端设备自身检查是否已经建立目标SDAP实体，若是没有，则触发终端设备建立该目标SDAP实体，不需要再向终端设备发送建立目标SDAP实体的配置信令，节省了对目标SDAP实体进行建立的配置信令的开销，从而降低了SDAP实体配置的开销。
另外，在本公开实施例中，上述配置信息中还包括与SDAP实体标识对应的PDU会话单元；
相应的，上述配置信息还用于，终端设备根据该配置信息建立目标SDAP实体与PDU会话标识对应的目标PDU会话的对应关系。
在本公开的一个具体实施例中，上述配置信息用于指示将待配置的DRB对应的第一SDAP实体修改为目标SDAP实体；
相应的，上述配置信息还用于，若未建立目标SDAP实体，则终端设备根据上述配置信息建立目标SDAP实体，并建立待配置的DRB与目标SDAP实体的对应关系。
其中，上述将待配置的DRB对应的第一SDAP实体修改为目标SDAP实体，指的是修改终端设备上已经存在的DRB的对应关系，即原来在终端设备上待配置的DRB与第一SDAP实体对应，需要将待配置的DRB的对应关系修改为与目标SDAP实体对应，即需要接触待配置的DRB与第一SDAP实体的对应关系，并建立待配置的DRB与目标SDAP实体的对应关系。
在该种情况下，网络侧设备将上述配置信息发送给终端设备后，终端设备查找是否已经建立目标SDAP实体，若是未建立目标SDAP实体，则根据该配置信息建立目标SDAP实体，并建立待配置的DRB与目标SDAP实体的对应关系，同时解除待配置的DRB与目标SDAP实体的对应关系。
若是终端设备已经建立上述目标SDAP实体，则终端设备根据上述配置信息建立待配置的DRB与目标SDAP实体的对应关系，并解除待配置的DRB与第一SDAP实体的对应关系即可。
在本公开实施例中，通过发送给终端设备的配置信息将指示将待配置的DRB对应的第一SDAP实体修改为目标SDAP实体，可以触发终端设备检测自身是否已经建立目标SDAP实体，若是还未建立目标SDAP实体，则触发终端设备建立目标SDAP实体，不需要向终端设备再发送建立目标SDAP实体的配置信令，节省了对目标SDAP实体进行建立的配置信令的开销，从而降低了SDAP实体配置的开销。
在一种具体实施方式中，若待配置的DRB为第一SDAP实体对应的所有的DRB；
相应的，上述配置信息，还用于终端设备根据该配置信息删除第一SDAP实体。
例如，在一种具体实施方式中，第一SDAP实体对应三个DRB，分别记为DRB1、DRB2和DRB3，若是，上述配置信息中的待配置的DRB刚好为DRB1、DRB2和DRB3，则在建立DRB1、DRB2和DRB3与目标SDAP实体的对应关系，并删除DRB1、DRB2和DRB3与第一SDAP实体的对应关系后，第一SDAP实体不存在对应的DRB，这时，触发终端设备删除该第一SDAP实体。
在本公开实施例中，当发送给终端设备的配置信息指示修改终端设备上已经存在的待配置的DRB所对应的SDAP实体，若是待配置的DRB为第一SDAP实体对应的所有的DRB，这时，可以触发终端设备删除第一SDAP实体，不需要再向终端设备发送删除第一SDAP实体的配置信令，节省了对第一SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
另外，在本公开的一个具体实施方式中，上述配置信息用于指示删除待配置的DRB；
相应的，上述配置信息还用于，若已经建立目标SDAP实体且待配置的DRB为目标SDAP实体对应的所有DRB，则终端设备根据该配置信息删除待 配置的DRB及目标SDAP实体。
具体的，在本公开实施例中，若是上述配置信息用于指示删除待配置的DRB，则将该配置信息发送给终端设备后，终端设备根据该配置信息检测是否已经建立目标SDAP实体，以及判断上述待配置的DRB是否为目标SDAP实体对应的所有的DRB，若是，则删除上述待配置的DRB以及目标SDAP实体；若是待配置的DRB并不是目标SDAP实体对应的所有的DRB，则终端设备只需要删除待配置的DRB即可。
例如，上述配置信息中包括的待配置的DRB为DRB1、DRB2和DRB3，DRB1、DRB2和DRB3对应SDAP实体1，并且，DRB1、DRB2和DRB3为SDAP实体1对应的所有的DRB，则当上述配置信息用于指示删除DRB1、DRB2和DRB3时，则在删除DRB1、DRB2和DRB3的同时，删除SDAP实体1。
在本公开实施例中，通过发送给终端设备的配置信息指示删除待配置的DRB，可以触发终端设备在检测到DRB对应的目标SDAP实体已经建立，并且待配置的DRB为目标SDAP实体对应的所有的DRB时，删除目标SDAP实体，这样，在检测到目标SDAP实体对应的DRB的数量为零个时，可以触发终端设备直接删除该目标SDAP实体，不需要网络侧设备再发送删除目标SDAP实体的配置信令，节省了对目标SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
另外，在本公开实施例中，当终端设备删除了目标SDAP实体后，终端设备上的目标SDAP实体对应的PDU会话不存在对应的SDAP实体，因此，还需要终端设备删除目标SDAP实体对应的PDU会话。因此，在本公开实施例中，上述配置信息中，还包括：与SDAP实体标识对应的PDU会话标识；
相应的，上述配置信息，还用于终端设备根据该配置信息删除目标SDAP实体与PDU会话标识对应的目标PDU会话的对应关系。
通过本公开实施例提供的服务数据适配协议SDAP实体的配置方法，通过向终端设备发送包括待配置的DRB的标识，以及与该待配置的DRB对应的SDAP实体标识的配置信息，可以使终端设备根据该配置信息对待配置的DRB进行配置，并且通过对DRB的配置可以实现对SDAP实体标识对应的 目标SDAP实体进行配置。即在本公开实施例中实现了通过隐式的方式对SDAP实体进行配置，这样，避免了再向终端设备发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
图5为本公开实施例提供的服务数据适配协议SDAP实体的配置方法的第三种方法流程图，图5所示的方法至少包括如下步骤：
步骤302，网络侧设备向终端设备发送配置信息；其中，该配置信息中包括待配置的DRB的标识，及与待配置的DRB对应的SDAP实体标识。
步骤304，终端设备接收网络侧设备发送的上述配置信息。
步骤306，终端设备根据上述配置信息，配置待配置的DRB及与SDAP实体标识对应的目标SDAP实体。
本公开实施例的具体实施过程可以参考前述实施例的描述，这里不再重复。
通过本公开实施例提供的服务数据适配协议SDAP实体的配置方法，实现了通过隐式的方式对SDAP实体进行配置，这样，避免了再向终端设备发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
对应上述实施例提供的服务数据适配协议SDAP实体的配置方法，本公开实施例提供了一种终端设备，本公开实施例提供的终端设备能够实现上述实施例中终端设备实现的各个过程。
图6为本公开实施例提供的终端设备的模块组成示意图，图6所示的终端设备，至少包括：
接收模块401，用于接收配置信息；其中，该配置信息中包括待配置的DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
配置模块402，用于根据上述配置信息，配置待配置的DRB及与SDAP实体标识对应的目标SDAP实体。
可选地，上述配置信息用于指示建立所述待配置的DRB；
相应的，上述配置模块402，具体用于：
若未建立目标SDAP实体，则建立待配置的DRB，并建立目标SDAP实体。
可选地，上述配置信息用于指示将待配置的DRB对应的第一SDAP实体修改为目标SDAP实体；
相应的，上述配置模块402，具体用于：
若未建立目标SDAP实体，则建立目标SDAP实体，并建立待配置的DRB与目标SDAP实体的对应关系。
可选地，若上述待配置的DRB为第一SDAP实体对应的所有的DRB，上述设备还包括：
第一删除模块，用于删除第一SDAP实体。
可选地，上述配置信息用于指示删除待配置的DRB；
相应的，上述配置模块402，具体用于：
若已经建立目标SDAP实体且待配置的DRB为目标SDAP实体对应的所有DRB，则删除待配置的DRB以及目标SDAP实体。
可选地，在上述配置信息中，一个待配置的DRB对应一个SDAP实体。
可选地，上述配置信息中还包括：与SDAP实体标识对应的PDU会话标识；
相应的，上述设备还包括：
第二删除模块，用于删除目标SDAP实体与PDU会话标识对应的目标PDU会话的对应关系。
可选地，上述设备还包括：
发送模块，用于向NAS实体发送删除通知消息，该删除通知消息用于通知NAS实体目标SDAP实体已被删除。
可选地，上述删除通知消息包括以下信息中的至少一种：
目标SDAP实体的SDAP实体标识；
目标SDAP实体对应的目标PDU会话的PDU会话标识；
目标SDAP实体对应的DRB标识。
本公开实施例提供的终端设备，通过对DRB的配置可以实现对SDAP实体标识对应的目标SDAP实体进行配置。即在本公开实施例中实现了通过 隐式的方式对SDAP实体进行配置，这样，避免了再发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
对应上述实施例提供的服务数据适配协议SDAP实体的配置方法，本实施例提供了一种网络侧设备，本公开实施例提供的网络侧设备能够实现上述实施例中网络侧设备实现的各个过程。
图7为本公开实施例提供的网络侧设备的模块组成示意图，图7所示的网络侧设备，至少包括：
发送模块501，用于发送配置信息；其中，该配置信息中包括待配置的DRB的标识，及与待配置的DRB对应的SDAP实体标识；
其中，上述配置信息用于终端设备根据该配置信息配置待配置的DRB及与SDAP实体标识对应的目标SDAP实体。
可选地，上述配置信息用于指示建立待配置的DRB；
其中，上述配置信息还用于若未建立目标SDAP实体，则终端设备根据该配置信息建立待配置的DRB，并建立目标SDAP实体。
可选地，上述配置信息用于指示将待配置的DRB对应的第一SDAP实体修改为目标SDAP实体；
上述配置信息还用于，若未建立目标SDAP实体，则终端设备根据该配置信息建立目标SDAP实体，并建立待配置的DRB与目标SDAP实体的对应关系。
可选地，若待配置的DRB为第一SDAP实体对应的所有的DRB；
上述配置信息，还用于终端设备根据该配置信息删除第一SDAP实体。
可选地，上述配置信息用于指示删除待配置的DRB；
其中，上述配置信息还用于，若已经建立目标SDAP实体且待配置的DRB为目标SDAP实体对应的所有DRB，则终端设备根据该配置信息删除待配置的DRB及目标SDAP实体。
可选地，在上述配置信息中，一个待配置的DRB对应一个SDAP实体。
可选地，上述配置信息中还包括：与SDAP实体标识对应的协议数据单 元PDU会话标识；
上述配置信息，还用于终端设备根据该配置信息删除目标SDAP实体与PDU会话标识对应的目标PDU会话的对应关系。
本公开实施例提供的网络侧设备，通过向终端设备发送包括待配置的DRB的标识，以及与该待配置的DRB对应的SDAP实体标识的配置信息，可以使终端设备根据该配置信息对待配置的DRB进行配置，并且通过对DRB的配置可以实现对SDAP实体标识对应的目标SDAP实体进行配置。即在本公开实施例中实现了通过隐式的方式对SDAP实体进行配置，这样，避免了再向终端设备发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
对应上述实施例提供的服务数据适配协议SDAP实体的配置方法，本实施例提供了一种终端设备，本公开实施例提供的终端设备能够实现上述实施例中终端设备实现的各个过程。
图8为本公开一个实施例提供的终端设备的结构示意图，如图8所示，该终端设备600包括：至少一个处理器601、存储器602、至少一个网络接口604和用户接口603。终端设备600中的各个组件通过总线系统605耦合在一起。可理解，总线系统605用于实现这些组件之间的连接通信。总线系统605除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图8中将各种总线都标为总线系统605。
其中，用户接口603可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球(trackball)、触感板或者触摸屏等。
可以理解，本公开实施例中的存储器602可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可 用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double DataRate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本公开实施例描述的系统和方法的存储器602旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器602存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统6021和应用程序6022。
其中，操作系统6021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序6022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本公开实施例方法的程序可以包含在应用程序6022中。
在本公开实施例中，终端设备600还包括：存储器602、处理器601、存储在存储器上602并可在处理器601上运行的计算机程序，计算机程序被处理器601执行时实现如下步骤：
接收配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
上述本公开实施例揭示的方法可以应用于处理器601中，或者由处理器601实现。处理器601可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器601中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器601可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array， FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的计算机可读存储介质中。该计算机可读存储介质位于存储器602，处理器601读取存储器602中的信息，结合其硬件完成上述方法的步骤。具体地，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器601执行时实现如上述实施例中的各步骤。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
可选地，计算机程序被处理器601执行时，所述配置信息用于指示建立所述待配置的DRB；
其中，所述根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体，包括：
若未建立所述目标SDAP实体，则建立所述待配置的DRB，并建立所述目标SDAP实体。
可选地，计算机程序被处理器601执行时，所述配置信息用于指示将所述待配置的DRB对应的第一SDAP实体修改为所述目标SDAP实体；
其中，所述根据所述配置信息，配置所述待配置的DRB及与所述SDAP 实体标识对应的目标SDAP实体，包括：
若未建立所述目标SDAP实体，则建立所述目标SDAP实体，并建立所述待配置的DRB与所述目标SDAP实体的对应关系。
可选地，计算机程序被处理器601执行时，若所述待配置的DRB为第一SDAP实体对应的所有的DRB，所述方法还包括：
删除所述第一SDAP实体。
可选地，计算机程序被处理器601执行时，所述配置信息用于指示删除所述待配置的DRB；
其中，所述根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体，包括：
若已经建立所述目标SDAP实体且所述待配置的DRB为所述目标SDAP实体对应的所有DRB，则删除所述待配置的DRB以及所述目标SDAP实体。
可选地，计算机程序被处理器601执行时，在所述配置信息中，一个待配置的DRB对应一个SDAP实体。
可选地，计算机程序被处理器601执行时，所述配置信息中还包括：与所述SDAP实体标识对应的协议数据单元PDU会话标识；
其中，在删除所述待配置的DRB及所述目标SDAP实体之后，所述方法还包括：
删除所述目标SDAP实体与所述PDU会话标识对应的目标PDU会话的对应关系。
可选地，计算机程序被处理器601执行时，所述方法还包括：
向非接入层NAS实体发送删除通知消息，所述删除通知消息用于通知所述NAS实体所述目标SDAP实体已被删除。
可选地，计算机程序被处理器601执行时，所述删除通知消息包括以下信息中的至少一种：
所述目标SDAP实体的SDAP实体标识；
所述目标SDAP实体对应的目标PDU会话的PDU会话标识；
所述目标SDAP实体对应的DRB标识。
通过本公开实施例提供的终端设备，通过对DRB的配置可以实现对 SDAP实体标识对应的目标SDAP实体进行配置。即在本公开实施例中实现了通过隐式的方式对SDAP实体进行配置，这样，避免了再发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
终端设备600能够实现前述实施例中终端设备实现的各个过程，为避免重复，这里不再赘述。
对应上述实施例提供的服务数据适配协议SDAP实体配置的方法，本实施例提供了一种网络侧设备，本公开实施例提供的网络侧设备能够实现上述实施例中网络侧设备实现的各个过程。
图9为本公开一个实施例提供的网络侧设备的结构示意图，如图9所示，该网络侧设备700包括：处理器701、收发机702、存储器703、用户接口704和总线接口。
在本公开实施例中，网络侧设备700还包括：存储在存储器703上并可在处理器701上运行的计算机程序，计算机程序被处理器701执行时实现如下步骤：
发送配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
其中，所述配置信息用于终端设备根据所述配置信息配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
在图9中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器701代表的一个或多个处理器和存储器703代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机702可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的终端设备，用户接口704还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器701负责管理总线架构和通常的处理，存储器703可以存储处理 器701在执行操作时所使用的数据。
可选地，存储器703存储的计算机程序被处理器701执行时，所述配置信息用于指示建立所述待配置的DRB；
其中，所述配置信息还用于若未建立所述目标SDAP实体，则终端设备根据所述配置信息建立所述待配置的DRB，并建立所述目标SDAP实体。
可选地，存储器703存储的计算机程序被处理器701执行时，所述配置信息用于指示将所述待配置的DRB对应的第一SDAP实体修改为所述目标SDAP实体；
所述配置信息还用于，若未建立所述目标SDAP实体，则终端设备根据所述配置信息建立所述目标SDAP实体，并建立所述待配置的DRB与所述目标SDAP实体的对应关系。
可选地，存储器703存储的计算机程序被处理器701执行时，若所述待配置的DRB为第一SDAP实体对应的所有的DRB；
所述配置信息，还用于终端设备根据所述配置信息删除所述第一SDAP实体。
可选地，存储器703存储的计算机程序被处理器701执行时，所述配置信息用于指示删除所述待配置的DRB；
其中，所述配置信息还用于，若已经建立所述目标SDAP实体且所述待配置的DRB为所述目标SDAP实体对应的所有DRB，则终端设备根据所述配置信息删除所述待配置的DRB及所述目标SDAP实体。
可选地，存储器703存储的计算机程序被处理器701执行时，在所述配置信息中，一个待配置的DRB对应一个SDAP实体。
可选地，存储器703存储的计算机程序被处理器701执行时，所述配置信息中还包括：与所述SDAP实体标识对应的协议数据单元PDU会话标识；
所述配置信息，还用于终端设备根据所述配置信息删除所述目标SDAP实体与所述PDU会话标识对应的目标PDU会话的对应关系。
在本公开实施例中，通过向终端设备发送包括待配置的DRB的标识，以及与该待配置的DRB对应的SDAP实体标识的配置信息，可以使终端设备根据该配置信息对待配置的DRB进行配置，并且通过对DRB的配置可以实现 对SDAP实体标识对应的目标SDAP实体进行配置。即在本公开实施例中实现了通过隐式的方式对SDAP实体进行配置，这样，避免了再向终端设备发送对SDAP实体进行配置的配置信令，节省了对SDAP实体进行配置的配置信令的开销，从而降低了SDAP实体配置的开销。
网络侧设备700能够实现前述实施例中网络侧设备实现的各个过程，并到达相同的技术效果，为避免重复，这里不再赘述。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述实施例中服务数据适配协议SDAP实体的配置方法实施例的各个过程，且能达到相同的技术效果，或者，该计算机程序被处理器执行时实现上述实施例中服务数据适配协议SDAP实体的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开实施例的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本公开实施例所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开实施例各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开实施例的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开实施例各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅为本公开的实施例而已，并不用于限制本公开。对于本领域技术人员来说，本公开可以有各种更改和变化。凡在本公开的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本公开的权利要求范围之内。

Claims (36)

  1. 一种服务数据适配协议SDAP实体的配置方法，应用于终端设备，所述方法包括：
    接收配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
    根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
  2. 如权利要求1所述的方法，其中，所述配置信息用于指示建立所述待配置的DRB；
    其中，所述根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体，包括：
    若未建立所述目标SDAP实体，则建立所述待配置的DRB，并建立所述目标SDAP实体。
  3. 如权利要求1所述的方法，其中，所述配置信息用于指示将所述待配置的DRB对应的第一SDAP实体修改为所述目标SDAP实体；
    其中，所述根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体，包括：
    若未建立所述目标SDAP实体，则建立所述目标SDAP实体，并建立所述待配置的DRB与所述目标SDAP实体的对应关系。
  4. 如权利要求3所述的方法，其中，若所述待配置的DRB为第一SDAP实体对应的所有的DRB，所述方法还包括：
    删除所述第一SDAP实体。
  5. 如权利要求1所述的方法，其中，所述配置信息用于指示删除所述待配置的DRB；
    其中，所述根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体，包括：
    若已经建立所述目标SDAP实体且所述待配置的DRB为所述目标SDAP实体对应的所有DRB，则删除所述待配置的DRB以及所述目标SDAP实体。
  6. 如权利要求1-5任一项所述的方法，其中，在所述配置信息中，一个待配置的DRB对应一个SDAP实体。
  7. 如权利要求5所述的方法，其中，所述配置信息中还包括：与所述SDAP实体标识对应的协议数据单元PDU会话标识；
    其中，在删除所述待配置的DRB及所述目标SDAP实体之后，所述方法还包括：
    删除所述目标SDAP实体与所述PDU会话标识对应的目标PDU会话的对应关系。
  8. 如权利要求7所述的方法，其中，所述方法还包括：
    向非接入层NAS实体发送删除通知消息，所述删除通知消息用于通知所述NAS实体所述目标SDAP实体已被删除。
  9. 如权利要求8所述的方法，其中，所述删除通知消息包括以下信息中的至少一种：
    所述目标SDAP实体的SDAP实体标识；
    所述目标SDAP实体对应的目标PDU会话的PDU会话标识；
    所述目标SDAP实体对应的DRB标识。
  10. 一种服务数据适配协议SDAP实体的配置方法，应用于网络侧设备，所述方法包括：
    发送配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
    其中，所述配置信息用于终端设备根据所述配置信息配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
  11. 如权利要求10所述的方法，其中，所述配置信息用于指示建立所述待配置的DRB；
    其中，所述配置信息还用于若未建立所述目标SDAP实体，则终端设备根据所述配置信息建立所述待配置的DRB，并建立所述目标SDAP实体。
  12. 如权利要求10所述的方法，其中，所述配置信息用于指示将所述待配置的DRB对应的第一SDAP实体修改为所述目标SDAP实体；
    所述配置信息还用于，若未建立所述目标SDAP实体，则终端设备根据 所述配置信息建立所述目标SDAP实体，并建立所述待配置的DRB与所述目标SDAP实体的对应关系。
  13. 如权利要求12所述的方法，其中，若所述待配置的DRB为第一SDAP实体对应的所有的DRB；
    所述配置信息，还用于终端设备根据所述配置信息删除所述第一SDAP实体。
  14. 如权利要求10所述的方法，其中，所述配置信息用于指示删除所述待配置的DRB；
    其中，所述配置信息还用于，若已经建立所述目标SDAP实体且所述待配置的DRB为所述目标SDAP实体对应的所有DRB，则终端设备根据所述配置信息删除所述待配置的DRB及所述目标SDAP实体。
  15. 如权利要求10-14任一项所述的方法，其中，在所述配置信息中，一个待配置的DRB对应一个SDAP实体。
  16. 如权利要求12所述的方法，其中，所述配置信息中还包括：与所述SDAP实体标识对应的协议数据单元PDU会话标识；
    所述配置信息，还用于终端设备根据所述配置信息删除所述目标SDAP实体与所述PDU会话标识对应的目标PDU会话的对应关系。
  17. 一种终端设备，包括：
    接收模块，用于接收配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
    配置模块，用于根据所述配置信息，配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
  18. 如权利要求17所述的设备，其中，所述配置信息用于指示建立所述待配置的DRB；
    其中，所述配置模块，具体用于：
    若未建立所述目标SDAP实体，则建立所述待配置的DRB，并建立所述目标SDAP实体。
  19. 如权利要求17所述的设备，其中，所述配置信息用于指示将所述待配置的DRB对应的第一SDAP实体修改为所述目标SDAP实体；
    其中，所述配置模块，具体用于：
    若未建立所述目标SDAP实体，则建立所述目标SDAP实体，并建立所述待配置的DRB与所述目标SDAP实体的对应关系。
  20. 如权利要求19所述的设备，其中，若所述待配置的DRB为第一SDAP实体对应的所有的DRB，所述设备还包括：
    第一删除模块，用于删除所述第一SDAP实体。
  21. 如权利要求17所述的设备，其中，所述配置信息用于指示删除所述待配置的DRB；
    其中，所述配置模块，具体用于：
    若已经建立所述目标SDAP实体且所述待配置的DRB为所述目标SDAP实体对应的所有DRB，则删除所述待配置的DRB以及所述目标SDAP实体。
  22. 如权利要求17-21任一项所述的设备，其中，在所述配置信息中，一个待配置的DRB对应一个SDAP实体。
  23. 如权利要求21所述的设备，其中，所述配置信息中还包括：与所述SDAP实体标识对应的协议数据单元PDU会话标识；
    其中，所述设备还包括：
    第二删除模块，用于删除所述目标SDAP实体与所述PDU会话标识对应的目标PDU会话的对应关系。
  24. 如权利要求23所述的设备，其中，所述设备还包括：
    发送模块，用于向非接入层NAS实体发送删除通知消息，所述删除通知消息用于通知所述NAS实体所述目标SDAP实体已被删除。
  25. 如权利要求24所述的设备，其中，所述删除通知消息包括以下信息中的至少一种：
    所述目标SDAP实体的SDAP实体标识；
    所述目标SDAP实体对应的目标PDU会话的PDU会话标识；
    所述目标SDAP实体对应的DRB标识。
  26. 一种网络侧设备，包括：
    发送模块，用于发送配置信息；其中，所述配置信息中包括待配置的数据无线承载DRB的标识，及与所述待配置的DRB对应的SDAP实体标识；
    其中，所述配置信息用于终端设备根据所述配置信息配置所述待配置的DRB及与所述SDAP实体标识对应的目标SDAP实体。
  27. 如权利要求26所述的设备，其中，所述配置信息用于指示建立所述待配置的DRB；
    其中，所述配置信息还用于若未建立所述目标SDAP实体，则终端设备根据所述配置信息建立所述待配置的DRB，并建立所述目标SDAP实体。
  28. 如权利要求26所述的设备，其中，所述配置信息用于指示将所述待配置的DRB对应的第一SDAP实体修改为所述目标SDAP实体；
    所述配置信息还用于，若未建立所述目标SDAP实体，则终端设备根据所述配置信息建立所述目标SDAP实体，并建立所述待配置的DRB与所述目标SDAP实体的对应关系。
  29. 如权利要求28所述的设备，其中，若所述待配置的DRB为第一SDAP实体对应的所有的DRB；
    所述配置信息，还用于终端设备根据所述配置信息删除所述第一SDAP实体。
  30. 如权利要求26所述的设备，其中，所述配置信息用于指示删除所述待配置的DRB；
    其中，所述配置信息还用于，若已经建立所述目标SDAP实体且所述待配置的DRB为所述目标SDAP实体对应的所有DRB，则终端设备根据所述配置信息删除所述待配置的DRB及所述目标SDAP实体。
  31. 如权利要求26-30任一项所述的设备，其中，在所述配置信息中，一个待配置的DRB对应一个SDAP实体。
  32. 如权利要求28所述的设备，其中，所述配置信息中还包括：与所述SDAP实体标识对应的协议数据单元PDU会话标识；
    所述配置信息，还用于终端设备根据所述配置信息删除所述目标SDAP实体与所述PDU会话标识对应的目标PDU会话的对应关系。
  33. 一种终端设备，包括：
    存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至9中任一 项所述的服务数据适配协议SDAP实体的配置方法的步骤。
  34. 一种网络侧设备，包括：
    存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求10至16中任一项所述的服务数据适配协议SDAP实体的配置方法的步骤。
  35. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至9中任一项所述的服务数据适配协议SDAP实体的配置方法的步骤。
  36. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求10至16中任一项所述的服务数据适配协议SDAP实体的配置方法的步骤。
PCT/CN2019/080092 2018-04-02 2019-03-28 服务数据适配协议sdap实体的配置方法及设备 WO2019192382A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP19782222.4A EP3780492A4 (en) 2018-04-02 2019-03-28 CONFIGURATION PROCEDURE FOR INSTANCE WITH SERVICE DATA ADAPTATION PROTOCOL (SDAP) AND DEVICE
KR1020207030779A KR102479784B1 (ko) 2018-04-02 2019-03-28 서비스 데이터 어댑테이션 프로토콜 sdap 엔티티의 설정 방법 및 기기
JP2020554263A JP7335262B2 (ja) 2018-04-02 2019-03-28 サービスデータ適応プロトコルｓｄａｐエンティティの設定方法及び機器
US17/037,391 US11968728B2 (en) 2018-04-02 2020-09-29 Method of configuring service data adaptation protocol entity and device
US17/853,826 US20220330356A1 (en) 2018-04-02 2022-06-29 Method of configuring service data adaptation protocol entity and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810284821.0A CN110351103B (zh) 2018-04-02 2018-04-02 服务数据适配协议sdap实体的配置方法及设备
CN201810284821.0 2018-04-02

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US17/037,391 Continuation US11968728B2 (en) 2018-04-02 2020-09-29 Method of configuring service data adaptation protocol entity and device
US17/853,826 Continuation US20220330356A1 (en) 2018-04-02 2022-06-29 Method of configuring service data adaptation protocol entity and device

Publications (1)

Publication Number Publication Date
WO2019192382A1 true WO2019192382A1 (zh) 2019-10-10

Family

ID=68099896

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/080092 WO2019192382A1 (zh) 2018-04-02 2019-03-28 服务数据适配协议sdap实体的配置方法及设备

Country Status (6)

Country Link
US (2) US11968728B2 (zh)
EP (1) EP3780492A4 (zh)
JP (1) JP7335262B2 (zh)
KR (1) KR102479784B1 (zh)
CN (1) CN110351103B (zh)
WO (1) WO2019192382A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107637123A (zh) * 2017-04-27 2018-01-26 北京小米移动软件有限公司 信息传递方法、装置及计算机可读存储介质
WO2018026169A1 (en) * 2016-08-01 2018-02-08 Samsung Electronics Co., Ltd. Method and apparatus for managing data communication in wireless communication network

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2193621B1 (en) * 2007-09-28 2019-06-12 Rakuten, Inc. Method and apparatus for supporting uplink protocol changes
CN101572955B (zh) * 2008-04-29 2011-10-05 电信科学技术研究院 一种删除承载的方法与装置
EP4213530A1 (en) * 2016-08-03 2023-07-19 Samsung Electronics Co., Ltd. Methods and apparatuses for mapping a quality-of-service flow to a bearer
EP3494756A4 (en) * 2016-08-09 2019-07-31 Samsung Electronics Co., Ltd. METHOD AND DEVICE FOR MANAGING OPERATION AT USER LEVEL IN A WIRELESS COMMUNICATION SYSTEM
KR102359746B1 (ko) * 2017-06-05 2022-02-10 삼성전자 주식회사 차세대 이동통신 시스템에서 인액티브 모드 단말이 데이터를 전송하는 방법 및 장치
CN115397037A (zh) * 2017-08-11 2022-11-25 北京三星通信技术研究有限公司 建立双连接的方法及装置
US11032866B2 (en) * 2017-11-27 2021-06-08 FG Innovation Company Limited Methods and related devices for multi-connectivity
JP2019121829A (ja) * 2017-12-28 2019-07-22 シャープ株式会社 端末装置、方法、および、集積回路

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018026169A1 (en) * 2016-08-01 2018-02-08 Samsung Electronics Co., Ltd. Method and apparatus for managing data communication in wireless communication network
CN107637123A (zh) * 2017-04-27 2018-01-26 北京小米移动软件有限公司 信息传递方法、装置及计算机可读存储介质

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "SDAP Configuration Aspects, R2-1800699", 3GPP TSG-RAN WG2 NR AH#1801, 26 January 2018 (2018-01-26), XP051385817 *
ERICSSON: "SDAP Configuration Aspects, R2-1803158", 3GPP TSG-RAN WG2 #101, 2 March 2018 (2018-03-02), XP051399932 *
HUAWEI: "QoS message flows, R2-1704977", 3GPP TSG-RAN WG2 MEETING #98, 19 May 2017 (2017-05-19), XP051275485 *
See also references of EP3780492A4 *

Also Published As

Publication number Publication date
JP2021520133A (ja) 2021-08-12
US20220330356A1 (en) 2022-10-13
EP3780492A1 (en) 2021-02-17
KR20200135860A (ko) 2020-12-03
EP3780492A4 (en) 2021-05-26
CN110351103B (zh) 2020-11-17
US20210029755A1 (en) 2021-01-28
KR102479784B1 (ko) 2022-12-20
JP7335262B2 (ja) 2023-08-29
US11968728B2 (en) 2024-04-23
CN110351103A (zh) 2019-10-18

Similar Documents

Publication Publication Date Title
WO2018202094A1 (zh) 一种参数的确定方法及通信实体
WO2017091960A1 (zh) 切换移动边缘平台的方法、装置和系统
WO2018228365A1 (zh) 数据无线承载完整性保护配置方法、终端及网络设备
WO2018223965A1 (zh) 数据传输方法、数据发送端、数据接收端、数据传输系统及计算机可读存储介质
CN111800798B (zh) 副链路数据复制功能控制、信息配置方法和设备
EP3993349A1 (en) Session management method and apparatus
US11044609B2 (en) Method and device for integrity protection
US11310658B2 (en) Method and apparatus for determining status of terminal device, and device
WO2023066383A1 (zh) 数据传输方法、装置及存储介质
WO2018195943A1 (zh) 用于拥塞处理的方法和设备
WO2016205997A1 (zh) 一种寻呼的方法及装置
WO2019047159A1 (zh) 切换状态的方法、网络设备和终端设备
WO2018195971A1 (zh) 获取上下文配置信息的方法、终端设备和接入网设备
WO2017152360A1 (zh) 一种为无线承载进行安全配置方法和设备
WO2019192382A1 (zh) 服务数据适配协议sdap实体的配置方法及设备
WO2021000763A1 (zh) 数据传输方法及装置
EP4075859A1 (en) Session processing method and communication device
WO2020233496A1 (zh) 安全会话方法和装置
EP3672353B1 (en) Data processing method, receiving terminal and storage medium
WO2020156427A1 (zh) 处理方法及通信设备
WO2021208817A1 (zh) 网络资源控制的方法及设备
WO2022179391A1 (zh) 信息处理的方法及装置
WO2020024863A1 (zh) 一种连接建立方法及装置
WO2021056386A1 (zh) 无线通信的方法和终端设备
WO2019056389A1 (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: 19782222

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020554263

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207030779

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019782222

Country of ref document: EP

Effective date: 20201102