WO2023016331A1 - 锚点确定方法、基站、终端、设备及计算机可读存储介质 - Google Patents

锚点确定方法、基站、终端、设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2023016331A1
WO2023016331A1 PCT/CN2022/110231 CN2022110231W WO2023016331A1 WO 2023016331 A1 WO2023016331 A1 WO 2023016331A1 CN 2022110231 W CN2022110231 W CN 2022110231W WO 2023016331 A1 WO2023016331 A1 WO 2023016331A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
anchor point
terminal
data
configuration information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/110231
Other languages
English (en)
French (fr)
Inventor
许森
刘悦
郑成林
熊尚坤
信金灿
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
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 China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Publication of WO2023016331A1 publication Critical patent/WO2023016331A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to the technical field of mobile communication, and in particular, to a method for determining a party anchor point, a base station, a terminal, a device, and a computer-readable storage medium.
  • 5G 5th Generation Mobile Communication Technology, fifth-generation mobile communication technology
  • 5G introduces a new state, that is, the Inactive state.
  • the delay in the data packet transmission process reduces the power consumption of the terminal.
  • the UE User Equipment, user terminal
  • the UE In the inactive state, the UE (User Equipment, user terminal) remains connected, and the UE can move within the RNA (RAN-based Notification Area, radio access network notification area) area without going through the RRC (Radio Resource Control , radio resource control) signaling to notify the NG-RAN.
  • RNA Radio Resource Control
  • RRC Radio Resource Control
  • the last serving gNB (next Generation Node B, next-generation base station) retains the UE context and UE-related AMF (Access and Mobility Management Function, access and mobility management function) and UPF (User Port Function , user port function) of the NG connection, generally referred to as "anchor".
  • AMF Access and Mobility Management Function, access and mobility management function
  • UPF User Port Function , user port function
  • the slave core network does not perceive that the UE is in the inactive state, and considers it to be the same as being in the connected state.
  • the anchor base station determines whether to change the anchor point. Usually when the anchor needs to be changed, the anchor base station will send the relevant UE context and security information to the current serving base station.
  • the base station and the UE are allowed to save the context of the AS (Access Stratum, access stratum) layer.
  • the base station When turning into an inactive state, the base station needs to send an RRCRelease (RRC release) message and carry suspendConfig indication information.
  • the base station side needs to include a new I-RNTI (Radio Network Temporary Identifier, wireless network temporary identifier) and an NCC (Next Hop Chaining Count, next hop chain counter) in the message, where the I-RNTI is used as the context identified.
  • I-RNTI Radio Network Temporary Identifier, wireless network temporary identifier
  • NCC Next Hop Chaining Count, next hop chain counter
  • RRCResumeRequest RRC resume request
  • PCI Physical-layer Cell Identity, physical layer cell identity
  • ARFCN Absolute Radio Frequency Channel Number, absolute radio frequency channel number
  • the multiplexing function of the MAC (Medium Access Control, Media Access Control) layer at the sending end loads the data of multiple logical channels into one transmission channel, that is, multiple MAC SDUs (Service Data Unit, Service Data Unit) (RLC (Radio Link Control) , radio link control) PDU (protocol data unit)) is multiplexed into a MAC PDU and sent out through the physical layer channel.
  • RLC Radio Link Control
  • PDU protocol data unit
  • the logical channel identifier in the current protocol is mainly used to associate a mapping relationship between a logical channel of the MAC layer and an RLC bearer.
  • resource application and transmission are usually performed in the form of logical channel groups, and which logical channels are mapped to the same logical channel group generally needs to be notified to the terminal through an RRC message.
  • Rel-16 In versions prior to 3GPP (3rd Generation Partnership Project, Third Generation Cooperation Project) Rel-16, if there is a small data packet to be transmitted in the inactive state, the terminal first needs to change from the inactive state to the connected (Connected) state. Data is sent after the control plane and user plane on the network side are established. Considering that users in the actual network need to send a large number of background services, on the one hand, the Rel-16 mechanism does not improve the access delay significantly; Need to go back to the inactive state, so it still brings too much signaling interaction between the terminal and the network.
  • 3GPP carried out research on Small Data Transmission (SDT) in Rel-17, the purpose of which is to reduce the access delay of terminals sending small data packets when they are inactive, which has been determined in the current standard Support data packet transmission based on RACH (Random Access Channel) and data packet transmission based on ConfiguredGrant.
  • RACH Random Access Channel
  • ConfiguredGrant The ability to transmit small packets during inactivity is currently in the standards research phase
  • the purpose of the present disclosure is to provide an anchor point determination method, a base station, a terminal, a device, and a computer-readable storage medium, at least to a certain extent, to overcome the problem of inconsistency between the terminal and the network in related technologies.
  • a method for determining an anchor point including: a first base station sends first RRC release information to a terminal, and the first RRC release information includes a mapping relationship between a DRB and a logical channel, a logical channel and a logical channel The mapping relationship of the group, or/and the user plane security policy adopted by the terminal when sending the small data packet in the inactive state, so that the terminal can determine the anchor base station when sending the small data packet in the inactive state.
  • the method further includes: the first base station receiving first anchor point configuration information sent by the second base station, the first anchor point configuration information including the security capability of the second base station and the terminal The service characteristics; wherein, the first anchor point configuration information is sent by the second base station after buffering the data sent by the terminal at the MAC layer during the random access process; the first base station according to the second base station The security capabilities of the terminal and the service characteristics of the terminal determine the second anchor point configuration information; the first base station sends the second anchor point configuration information to the second base station, so that the second base station according to the first Two anchor point configuration information generates RRC information sent to the terminal.
  • a method for determining an anchor point including: the second base station receives the RRCResumeRequest or RRCResumeRequest1 sent by the terminal, and also carries the filled BSR and MAC SDU information, wherein the LCG ID carried in the BSR is the first The configuration information of the base station, the logical channel number of the MAC SDU adopts the configuration of the first base station; the second base station caches the data sent by the terminal, and sends the first anchor configuration information to the first base station, and the first anchor
  • the point configuration information includes the security capability of the second base station and the service feature of the terminal, so that the first base station determines an anchor point according to the first anchor point configuration information.
  • a base station including: a security policy determination unit configured to configure a user plane security policy adopted when a terminal sends a small data packet in an inactive state according to the security capabilities of surrounding base stations; A unit, configured to send first RRC release information to the terminal, where the first RRC release information includes a mapping relationship between a DRB and a logical channel, a mapping relationship between a logical channel and a logical channel group, and the terminal sends a small data packet in an inactive state
  • the user plane security policy adopted at the time so that the terminal can determine the anchor base station when sending a small data packet in an inactive state.
  • a terminal including: a release information receiving unit, configured to receive first RRC release information sent by a first base station, and the first RRC release information includes a mapping relationship between a DRB and a logical channel, a logical The mapping relationship between channels and logical channel groups, or/and the user plane security policy adopted by the terminal when sending small data packets in an inactive state, so that the terminal can determine the anchor base station when sending small data packets in an inactive state;
  • the release information storage unit is used to save the inactive context configuration information of the end user, including updating KgNB and KRRCint, saving the user identifier I-RNTI or ShortI-RNTI, saving the mapping relationship between DRB and logical channels, and saving logical channels and logical channel groups If the DRB list of SDT is configured and it is confirmed that the corresponding DRB can support the transmission of small data packets, then the encryption keeping indication, encryption algorithm, integrity protection keeping indication, and integrity protection algorithm are saved; otherwise, no encryption and integrity are
  • a base station including: a recovery request receiving unit, configured to receive the RRCResumeRequest or RRCResumeRequest1 sent by the terminal, and also carry the filled BSR and MAC SDU information, wherein the LCG ID carried in the BSR is the first Configuration information of a base station, the logical channel number of the MAC SDU adopts the configuration of the first base station; the first anchor point information sending unit is used to send the first anchor point configuration information to the first base station, and the first anchor point configuration
  • the information includes the security capability of the second base station and the service feature of the terminal, so that the first base station determines the anchor point according to the first anchor point configuration information.
  • a device including: a memory, a processor, and executable instructions stored in the memory and executable in the processor, wherein the processor executes the The above-mentioned anchor point determination method is implemented when the above-mentioned executable instructions are used.
  • a computer-readable storage medium on which computer-executable instructions are stored, wherein the executable instructions implement the above-mentioned anchor point determination method when executed by a processor.
  • the anchor point determination method provided by the embodiments of the present disclosure includes in the RRC release information the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and logical channel group, or/and the terminal sends small data in an inactive state
  • the user plane security policy adopted by the package helps the terminal to configure reasonable encryption and/or integrity protection configurations when it enters the inactive state, avoiding the security risks caused by disabling the user plane security function, and maintaining the connection between the terminal and the network.
  • the consistency of user security understanding among users solves the problem of interoperability between terminals and networks.
  • FIG. 1 shows a schematic diagram of an architecture of cross-5G base station handover based on an Xn interface in an embodiment of the present disclosure
  • FIG. 2 shows a flowchart of an anchor point determination method in one embodiment of the present disclosure
  • FIG. 3 shows a flowchart of an anchor point determination method in another embodiment of the present disclosure
  • FIG. 4 shows a flowchart of an anchor point determination method in another embodiment of the present disclosure
  • FIG. 5 shows a flowchart of an anchor point determination method in another embodiment of the present disclosure
  • FIG. 6 shows a flowchart of an anchor point determination method in another embodiment of the present disclosure
  • FIG. 7 shows a block diagram of a base station in an embodiment of the present disclosure
  • FIG. 8 shows a block diagram of a terminal in an embodiment of the present disclosure
  • Figure 9 shows a block diagram of a base station in another embodiment of the present disclosure.
  • Fig. 10 shows a schematic structural diagram of an electronic device in an embodiment of the present disclosure.
  • Example embodiments will now be described more fully with reference to the accompanying drawings.
  • Example embodiments may, however, be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.
  • the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale.
  • the same reference numerals in the drawings denote the same or similar parts, and thus repeated descriptions thereof will be omitted.
  • first, second, etc. are used for descriptive purposes only, and should not be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, a feature defined as “first” and “second” may explicitly or implicitly include one or more of these features.
  • “plurality” means at least two, such as two, three, etc., unless otherwise specifically defined.
  • the symbol “/” generally indicates that the contextual objects are an “or” relationship.
  • connection should be interpreted in a broad sense, for example, it can be electrically connected or can communicate with each other; it can be directly connected or indirectly connected through an intermediary.
  • Xn handover is a cross-5G base station (gNB) handover based on the Xn interface.
  • gNB cross-5G base station
  • UE 11 has registered in the 5G network and established a PDU session (Protocol Data Unit Session, protocol data unit session).
  • PDU session Protocol Data Unit Session, protocol data unit session.
  • the source gNB (Source gNB) 12 is connected to the 5G network and is surfing the Internet. If the location of UE 11 has moved, leaving the cell served by the source gNB 12, it will soon enter the cell served by the new target gNB (Target gNB) 13.
  • the terminal cannot determine whether to use integrity and/or encryption to send small data packets in an inactive state.
  • the current inactive mechanism sends data only after the signaling is established, and at this time the network side has notified the terminal whether to use encryption and integrity protection. Based on the existing method, it may lead to data discarding due to inconsistency between the user plane mechanism adopted by the terminal and the network side.
  • the target base station cannot distinguish service types during the initial access process of the terminal.
  • the uplink data carried by the terminal in the process of sending RRCResume is first buffered at the MAC layer, and waits for the negotiation process between the target base station and the anchor base station.
  • the MAC layer can only see the logical channel group sent, and this The logical channel group is configured by the source base station, so the target base station does not know the mapping relationship between LCG and DRB, so it cannot determine which DRB is sending the service, resulting in the target side not knowing the subsequent transmission behavior of the terminal, and unable to provide valid information to the source side.
  • the target base station cannot determine which information is provided to the source base station for determining the anchor point.
  • the standard has not clarified what information to carry to the source base station to determine the anchor base station. According to the content carried in the Retrieve UE Context Request/Response message in the inactive state of the target Rel-16, it may cause the target base station to fail to satisfy the source base station.
  • the encryption/integrity protection requirement of the base station causes the data previously sent by the UE to be discarded.
  • the current 3GPP NR New Radio, new air interface
  • 3GPP NR New Radio, new air interface
  • Fig. 2 shows a flowchart of an anchor point determination method in an embodiment of the present disclosure.
  • the first base station sends the first RRC release information to the terminal
  • the first RRC release information includes the mapping relationship between DRB (Data Radio Bearer, data resource bearer) and logical channel, logical channel and logical channel group
  • DRB Data Radio Bearer, data resource bearer
  • S204 Determine, based on the first RRC release information, an anchor base station when the terminal sends a small data packet in an inactive state.
  • Fig. 3 shows a flow chart of an anchor point determination method in another embodiment of the present disclosure.
  • the first base station configures a user plane security policy adopted when a user sends a small data packet in an inactive state according to security capabilities of surrounding base stations.
  • the first base station sends first RRC release information to the terminal.
  • the terminal sends data to the second base station in an inactive state.
  • the first base station receives the first anchor point configuration information sent by the second base station.
  • the first anchor point configuration information includes the security capabilities of the base station and the service characteristics of the terminal; wherein, the first anchor point configuration information is randomly connected by the second base station
  • the data sent by the terminal is cached at the MAC layer and then sent.
  • the second base station caches the data sent by the terminal at the MAC layer, and sends the security capability of the second base station and the service feature of the terminal as auxiliary information to the first base station.
  • the first base station determines configuration information of the second anchor point according to the security capability of the second base station and the service feature of the terminal.
  • the first base station determines the location of the anchor point according to the security capability of the second base station and the service characteristics of the terminal, and sends the protocol and bearer configuration information to the second base station.
  • the first base station sends the second anchor point configuration information to the second base station, so that the second base station generates RRC information to be sent to the terminal according to the second anchor point configuration information.
  • the second anchor configuration information includes anchor location, protocol and bearer configuration information.
  • the anchor base station is helped to correctly choose whether to change the anchor point location, and avoids problems such as security mismatch between the access base station and the anchor point, and terminal data discarding caused by inconsistent understanding of business behavior.
  • Fig. 4 shows a flowchart of an anchor point determination method in another embodiment of the present disclosure. It introduces the signaling process of determining the anchor point when the terminal initially sends the uplink small data packet. The specific process is as follows:
  • the first base station control plane entity acquires encryption algorithms and/or integrity protection algorithms of all base stations in the configured RNA area.
  • Algorithm configuration of each base station can be configured through the network management or determined according to signaling instructions between base stations in the RNA area.
  • the first base station control plane entity determines that the terminal needs to enter the inactive state, check whether the encryption algorithm and the integrity protection algorithm currently used by the terminal are supported by all base stations in the RNA area. If it can be supported by all base stations or at least one base station, it is determined that the terminal needs to maintain encryption or integrity protection configuration when sending small data packets in an inactive state; if not supported by all, it is determined that the terminal sends small data packets in an inactive state Do not keep the encryption or integrity protection configuration, or replace it with the corresponding encryption/integrity protection algorithm. Generate corresponding first RRC release information. Wherein the first RRC release information includes but is not limited to the following:
  • I-RNTI or ShortI-RNTI can be used.
  • Encryption retention indication enumeration or Boolean type, used to indicate whether to maintain data encryption when inactive state initiates data. When this option is not carried, it means not to keep.
  • Encryption algorithm enumeration type. Can include 128-NEA1, 128-NEA2 and 128-NEA3. When this option is not carried, it means that the encryption algorithm needs not to be changed, and when it is carried, it means that the encryption algorithm needs to be applied when inactive data is initiated.
  • Integrity protection maintenance indication enumerated or Boolean type, used to indicate whether to maintain integrity protection when inactive state initiates data. When this option is not carried, it means not to keep.
  • Integrity protection algorithm enumeration type. Can include 128-NIA1, 128-NIA2 and 128-NIA3. When this option is not carried, it means that the encryption algorithm needs not to be changed, and when it is carried, it means that the encryption algorithm needs to be applied when inactive data is initiated.
  • a list of DRBs configured as SDT one or more DRB identifiers. When this identifier is included, it means that the DRB can support sending small data packets in an inactive state.
  • the first base station control plane entity sends a user context modification message including the first RRC release information of the terminal user to the first base station detachment entity.
  • the first base station control plane entity and the first base station separation entity may be deployed separately or jointly.
  • the first base station separation entity sends a first RRC release message (RRCRelease (UP security active (uplink security activity))) to the terminal user.
  • RRCRelease UP security active (uplink security activity)
  • the UE enters an inactive (inactive) state.
  • the terminal user receives the first RRC release message, if the suspend configuration information is included for responding to RRCResumeRequest or RRCResumeRequest1, stop the running timer T319, save the inactive context configuration information of the terminal user, including updating KgNB and KRRCint, and save User ID I-RNTI or ShortI-RNTI, save the mapping relationship between DRB and logical channel, and save the mapping relationship between logical channel and logical channel group.
  • the DRB list of SDT is configured to determine that the corresponding DRB can support small data packet transmission, it means yes If it is necessary to transmit small data packets in the inactive state, then save the encryption keeping indication, encryption algorithm, integrity protection keeping indication, and integrity protection algorithm; otherwise, it does not include any encryption and integrity protection configuration information, and is not allowed in the inactive state Status sends small packets.
  • the terminal triggers the sending of RRCResumeRequest (Uplink Data with security active) or RRCResumeRequest1 according to the data to be sent on the DRB of the configured SDT, and determines the user plane security policy of the uplink data to be sent according to the saved inactive context configuration information.
  • the PDCP Packet Data Convergence Protocol
  • the PDCP layer of the terminal performs an integrity protection operation on the data, and determines whether to change the integrity protection algorithm according to whether the integrity protection algorithm is configured.
  • the terminal In addition to sending RRCResumeRequest or RRCResumeRequest1 in the uplink resource configured by the second base station, the terminal also carries the filled BSR (Buffer Status Report, buffer status report) and MAC SDU information.
  • BSR Buffer Status Report, buffer status report
  • the LCG (Logical channel Group) ID carried in the BSR is the configuration information of the first base station, and the logical channel number of the MAC SDU adopts the configuration of the first base station.
  • the second base station separation entity After receiving the RRCResumeRequest or RRCResumeRequest1, the second base station separation entity also obtains the uplink data, and buffers the MAC SDU. Determine that the terminal supports small data transmission in an inactive state, and determine the data information for uplink transmission according to the BSR information reported by the terminal, the LCG used for uplink data transmission, and the LC ID information used for data transmission.
  • the second base station separation entity sends an Initial UL Message Transfer (Initial UL Message Transfer) message including the first service data configuration information to the second base station control plane entity through the interface with the second base station control plane entity.
  • the first business data configuration information includes but is not limited to the following:
  • SDT indication information enumeration or Boolean type, indicating that the terminal has uplink data to send at the same time.
  • Uplink LCG ID the uplink logical channel group ID used for data transmission, as defined in TS38.321.
  • the LCG field carried in the BSR report does not include the logical channel group identifier for signaling.
  • Logical channel list of data to be transmitted contains one or more logical channel numbers, which are logical signal identifiers contained in the MAC SDU.
  • the second base station control plane entity After receiving the Initial UL Message Transfer message, the second base station control plane entity sends the first anchor configuration information to the first base station control plane entity through the Xn interface Anchor decision Request (anchor decision request).
  • the first anchor point configuration information includes but is not limited to the following information:
  • User XnAP identifier assigned by the second base station an identifier assigned to the UE by the second base station on the Xn interface.
  • the encryption algorithm support list of the second base station including one or more defined algorithms.
  • SDT indication information enumeration or Boolean type, indicating that the terminal has uplink data to be sent at the same time.
  • the amount of data to be transmitted uplink the size of the BSR reported by the terminal.
  • Uplink LCG ID the uplink logical channel group ID used for data transmission, as defined in TS38.321.
  • Logical channel list of data to be transmitted contains one or more logical channel numbers, which are logical signal identifiers contained in the MAC SDU.
  • the first base station control plane entity determines an anchor point according to the first anchor point configuration information. After the first base station control plane entity receives the configuration information of the first anchor point, it determines the amount of data to be transmitted uplink and the corresponding DRB information according to the amount of uplink data to be transmitted and the LCG ID and LC ID, and determines whether to There are subsequent transmissions. If one transmission is completed and the second base station supports the encryption and/or integrity protection algorithm previously configured by the end user, the anchor point is updated to the second base station; if one of the encryption or integrity protection algorithms cannot support , the anchor point is still maintained at the first base station; if there are multiple transmissions, the anchor point is still maintained at the first base station.
  • the first base station control plane entity determines the second anchor point configuration information according to the anchor point configuration information, and sends the second anchor point configuration information to the second base station control through the interface between the first base station and the second base station surface entities.
  • case 1 there are two different cases: case 1 and case 2.
  • the configuration information of the second anchor point includes but is not limited to:
  • the user XnAP ID assigned by the second base station the same as the value provided by the second base station in the first anchor point configuration information.
  • AMF identification information such as GUAMI (AMF global identification information) information defined in the protocol.
  • User context configuration information including but not limited to the following:
  • Address and port of the AMF including the IP address of the AMF, or the IP address and port number of the AMF.
  • UE security capabilities list of NR encryption algorithms supported by UE, list of NR integrity protection algorithms supported by UE, list of E-UTRA encryption algorithms supported by UE, list of E-UTRA integrity protection algorithms supported by UE.
  • UE maximum aggregation rate the maximum transmission rate defined for all Non-GBR uplink and downlink respectively.
  • each PDU session includes but not limited to the following:
  • each direction includes IP address and port address;
  • -User plane security policy activation configuration of encryption and integrity protection
  • PDCP configuration information DRB configuration in the PDCP configuration adopted by the first base station.
  • RLC configuration information the mapping configuration of RLC bearers and logical channels adopted by the first base station.
  • the configuration information of the second anchor point includes but is not limited to:
  • UE maximum aggregation rate the maximum transmission rate defined for all Non-GBR uplink and downlink respectively;
  • RLC configuration information including the mapping relationship between RLC bearers and logical channels;
  • each PDU session includes but not limited to the following:
  • Uplink address information allocated by the first base station including IP address and port address;
  • the RRC message sent to the terminal the RRCRelease message used to let the user return to the inactive state.
  • the second base station control plane entity After receiving the second anchor point configuration information, the second base station control plane entity determines the home configuration of the anchor point, and configures protocol stack related parameters and bearer related parameters according to the second anchor point configuration information.
  • S424A if the anchor point is the second base station, buffer the RRC message of the user, and do not receive any transmission of uplink user data or receive a bearer release request message from the user plane entity of the second base station after the first timer expires After that, send the buffered RRC message to the terminal.
  • the anchor point is the first base station, after the relevant protocol parameters and bearer parameters are configured, perform RLC layer processing on the buffered MAC SDU according to the configuration information of the second anchor point, and according to the uplink address information allocated by the first base station Forward the processed uplink data.
  • the PDU session list includes at least one session that needs to be configured with a downlink address
  • the second base station triggers an interface address indication message to the first base station.
  • the interface address indication information includes but is not limited to the following information:
  • PDU session address list a list of sessions that can receive PDU session downlink data, where the configuration of each PDU session includes but is not limited to the following:
  • Downlink address information including IP address and port address.
  • Step 13 If the control plane entity of the second base station receives the authentication failure message from the first base station, it generates an RRCsetup message and sends it to the separation entity of the second base station through a user context release message.
  • the second base station separation entity deletes the cached MAC SDU data sent by the user after receiving it, and sends the RRCsetup message to the terminal, and the terminal deletes the data in the cache, and establishes signaling from the connected state.
  • Step 14 If the control plane entity of the first base station receives the interface address indication information from the first base station, then according to the downlink PDU session address information in the indication, pass the data from the core network between the first base station and the second base station The user plane interface of is sent to the control plane entity of the second base station according to the downlink address information. At the same time, the second base station forwards the uplink data corresponding to the LCG to the uplink address information in the PDU session establishment list as the destination address.
  • Step 15 If the anchor point is the second base station, the control plane entity of the second base station sends a path switching request message to the core network control plane entity, indicating the reception information of the downlink address of the service bearer that needs to be changed.
  • Step 16 The core network control plane entity configures the new uplink transmission address information of the related bearer through the path switching response message and sends it to the second base station control plane entity.
  • Step 17 The control plane entity of the second base station notifies the user plane entity of the second base station through a user bearer modification message, and notifies the user plane entity of the second base station of the uplink address information sent to the core network.
  • the second base station user plane entity notifies the second base station control plane entity of the configuration result.
  • Step 18 The second base station completes the protocol stack and service configuration of the second base station according to the second anchor point configuration information, and sends the first RLC layer configuration information to the second base station separation entity through the interface with the second base station separation entity .
  • the first RLC layer configuration information includes but not limited to the following:
  • the second base station separation entity identifies the label assigned by the user on the F1 interface
  • Configuration information of the RLC layer including the mapping relationship between LCG and RLC bearers, and protocol stack parameters
  • Each DRB corresponds to the uplink channel address information: including IP address and port address
  • Step 19 After the second base station separation entity receives the first RLC layer configuration information, it completes the configuration of relevant protocol stack parameters and bearers, and performs data for the buffered MAC SDU based on the RLC layer configuration information, and passes the processed data through The uplink channel address information corresponding to the DRB is sent to the user plane entity of the second base station.
  • Step 20 After the inactivation timer expires, the second base station user plane entity instructs the second base station control plane entity that the user is in an inactive state.
  • Step 21 The second base station control plane entity generates an RRCRelease message, wherein the RRCRelease message contains Suspend configuration information and which bearers need to activate encryption and/or integrity protection when sending data, and the second base station control plane entity sends the RRCRelease message Sent to the end user, causing the end user to return to an inactive state.
  • Fig. 5 shows a flowchart of an anchor point determination method in another embodiment of the present disclosure.
  • This embodiment describes the process in which the terminal enters the inactive state from base station 1 and moves to base station 2 to initiate the transmission of small data packets, where base station 1 and base station 2 support the same encryption and integrity protection capabilities, and the DRB number initiated by the terminal It is DRB#1.
  • the implementation of carrying data packets when the network side is configured to initiate a random process at the terminal side is described below in combination with specific steps.
  • gNB1-CU-CP obtains encryption and/or integrity protection algorithms of all base stations in the configured RNA area.
  • the algorithm configuration of each base station can be configured through the network management.
  • the gNB1-CU-CP sends to the gNB1-DU a user context modification message including the terminal user's first RRC release information.
  • the first RRC release information includes as follows:
  • Integrity protection algorithm 128-NIA1.
  • DRB list configured as SDT: DRB#1.
  • the gNB1-DU sends the first RRC release message (RRCRelease (UP security active (uplink security activity))) to the terminal user.
  • RRCRelease UP security active (uplink security activity)
  • the terminal triggers the sending of RRCResumeRequest (Uplink Data with security active (uplink data with security activity)) according to the data to be sent on DRB#1 of the configured SDT, and determines the uplink data to be sent according to the saved inactive context configuration information If the user plane security policy is specified, the PDCP layer of the terminal encrypts the data, and determines to change the encryption algorithm to 128-NEA1. At the same time, if the integrity protection maintenance indication information is configured, the PDCP layer of the terminal performs an integrity protection operation on the data, and determines that the integrity protection algorithm adopts 128-NIA1.
  • RRCResumeRequest Uplink Data with security active (uplink data with security activity)
  • the terminal In addition to sending RRCResumeRequest or RRCResumeRequest1 in the uplink resources configured by gNB2, the terminal also carries the filled BSR and MAC SDU information.
  • the LCG ID carried in the BSR is the configuration information of the first base station, and the logical channel number of the MAC SDU adopts the configuration LCG#2 of gNB1.
  • Fig. 6 shows a flow chart of an anchor point determination method in another embodiment of the present disclosure. This embodiment mainly describes the process that the terminal needs to send small uplink data packets on DRB1, gNB2 is related to the previous anchor base station gNB1 to determine that the anchor point is still on gNB1, and sends its own uplink data packets to gNB1 through the Xn interface .
  • the terminal sends the RRCResumeRequest or RRCResumeRequest1 in the uplink resources configured by gNB2, and also carries the filled BSR and MAC SDU information.
  • the LCG ID carried in the BSR is the configuration information of the first base station, and the logical channel number of the MAC SDU adopts the configuration of the first base station.
  • gNB2-DU After receiving RRCResumeRequest or RRCResumeRequest1, gNB2-DU also obtains uplink data to determine that the terminal supports small data transmission in an inactive state. According to the BSR information reported by the terminal, the LCG used for uplink data transmission and the LCID used for data transmission The information determines the data information sent uplink.
  • the gNB2-DU sends an Initial UL Message Transfer message including the first service data configuration information to the gNB2-CU-CP through the interface with the gNB2-CU-CP, where the first service data configuration information includes the following:
  • Uplink data volume to be transmitted 100Kbytes
  • Logical channel list for data to be transmitted LC#4.
  • the gNB2-CU-CP After receiving the Initial UL Message Transfer message, the gNB2-CU-CP sends the configuration information of the first anchor point to the gNB1-CU-CP through the Xn interface.
  • the first anchor point configuration information includes the following information:
  • Logical channel list of data to be transmitted LC#4.
  • the gNB1-CU-CP After receiving the first anchor point configuration information, the gNB1-CU-CP determines the amount of uplink data to be transmitted and the corresponding DRB information according to the amount of uplink data to be transmitted and the LCG ID and LC ID. And once the transmission is completed and gNB2 supports the encryption and/or integrity protection algorithm previously configured by the terminal user, the anchor point is updated to gNB2.
  • gNB1-CU-CP determines second anchor point configuration information according to the anchor point configuration information, and sends the second anchor point configuration information to gNB2-CU-CP through the interface between the first base station and gNB2.
  • the configuration information of the second anchor point includes:
  • AMF identification information :
  • User context configuration information including the following:
  • the configuration of each PDU session includes the following:
  • the gNB2-CU-CP After receiving the configuration information of the second anchor point, the gNB2-CU-CP determines the home configuration of the anchor point, and configures parameters related to the protocol stack and related parameters of the bearer according to the configuration information of the second anchor point. If the anchor point is gNB2, cache the RRC message of the user, and send the cached RRC message to the terminal after receiving no uplink user data transmission or receiving a bearer release request message from gNB2-CU-UP after the first timer expires RRC messages.
  • the anchor point is gNB2
  • the gNB2-CU-CP sends a path switching request message to the core network control plane entity, indicating the reception information of the downlink address of the service bearer that needs to be changed.
  • the core network control plane entity configures the new uplink transmission address information of the relevant bearer through the path switching response message and sends it to the gNB2-CU-CP.
  • the gNB2-CU-CP notifies the gNB2-CU-UP through a user bearer modification message, and notifies the gNB2-CU-UP of the uplink address information sent to the core network.
  • gNB2-CU-UP notifies gNB2-CU-CP of the configuration result.
  • the gNB2 completes the protocol stack and service configuration of the gNB2 according to the second anchor point configuration information, and sends the first RLC layer configuration information to the gNB2-DU through the interface with the gNB2-DU.
  • the first RLC layer configuration information includes as follows:
  • gNB2-CU-CP is the identifier assigned by the user on the F1 interface
  • gNB2-DU is the identifier assigned by the user on the F1 interface
  • Each DRB corresponds to uplink channel address information.
  • the gNB2-DU After receiving the first RLC layer configuration information, the gNB2-DU completes the configuration of relevant protocol stack parameters and bearers, and performs data for the cached MAC SDU based on the RLC layer configuration information, and passes the processed data through the DRB corresponding
  • the uplink channel address information is sent to gNB2-CU-UP.
  • the gNB2-CU-UP instructs the gNB2-CU-CP user to be in an inactive state.
  • gNB2-CU-CP produces a RRCRelease message, wherein the RRCRelease message contains Suspend configuration information and which bearers need to activate encryption and/or integrity protection when sending data, and gNB2-CU-CP sends the RRCRelease message to the terminal user, which returns the end user to an inactive state.
  • This patent proposes a method for determining the anchor point, which ensures the correctness of the user plane security when data is sent and received, and avoids data loss caused by incorrect configuration and anchor point selection; this method can also effectively reduce the distance between the base station and the terminal. signaling overhead, reduce the transmission delay of uplink data, and improve user experience and perception.
  • Fig. 7 shows a block diagram of a base station in one embodiment of the present disclosure.
  • the base station in this embodiment includes: a security policy determination unit 71, configured to configure the user plane security policy adopted by the terminal when sending small data packets in an inactive state according to the security capabilities of surrounding base stations; a release information sending unit 72. It is used to send the first RRC release information to the terminal, the first RRC release information includes the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and logical channel group, and the terminal when sending small data packets in an inactive state.
  • the user plane security policy is adopted so that the terminal can determine the anchor base station when sending small data packets in an inactive state.
  • FIG. 8 shows a block diagram of a terminal in one embodiment of the present disclosure.
  • the terminal in this embodiment includes: a release information receiving unit 81, configured to receive the first RRC release information sent by the first base station.
  • the first RRC release information includes the mapping relationship between DRB and logical channel, the logical channel and The mapping relationship of logical channel groups, or/and the user plane security policy adopted by the terminal when sending small data packets in an inactive state, so that the terminal can determine the anchor base station when sending small data packets in an inactive state; release the information storage unit 82.
  • the terminal further includes: a small data sending unit 83, configured to send data on the DRB of the configured SDT, trigger sending RRCResumeRequest or RRCResumeRequest1, and determine the uplink data to be sent according to the saved inactive context configuration information User plane security policy; among them, if the encryption maintenance indication information is configured, the PDCP layer of the terminal performs encryption operation on the data, and determines whether to change the encryption algorithm according to whether the encryption algorithm is configured; if the integrity protection maintenance indication information is configured, Then the PDCP layer of the terminal performs an integrity protection operation on the data, and determines whether to change the integrity protection algorithm according to whether the integrity protection algorithm is configured.
  • a small data sending unit 83 configured to send data on the DRB of the configured SDT, trigger sending RRCResumeRequest or RRCResumeRequest1, and determine the uplink data to be sent according to the saved inactive context configuration information User plane security policy; among them, if the encryption maintenance indication information is configured, the PDCP layer of the terminal perform
  • Fig. 9 shows a block diagram of a base station in another embodiment of the present disclosure.
  • the base station includes: a recovery request receiving unit 91, which is used to receive the RRCResumeRequest or RRCResumeRequest1 sent by the terminal, and also carries the filled BSR and MAC SDU information, wherein the LCG ID carried in the BSR is the configuration of the first base station information, the logical channel number of the MAC SDU adopts the configuration of the first base station; the first anchor point information sending unit 92 is used to send the first anchor point configuration information to the first base station, and the first anchor point configuration information includes the second base station The security capabilities of the terminal and the service characteristics of the terminal, so that the first base station determines the anchor point according to the first anchor point configuration information.
  • the solution disclosed in the present disclosure requires little modification to the terminal, and has good backward compatibility and deployment feasibility. This solution is to enhance the existing protocol and borrow the existing protocol process, which is less difficult to implement.
  • Fig. 10 shows a schematic structural diagram of an electronic device in an embodiment of the present disclosure. It should be noted that the device shown in FIG. 10 is only an example of a computer system, and should not limit the functions and scope of use of the embodiments of the present disclosure.
  • a device 1000 includes a central processing unit (CPU) 1001 that can operate according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage section 1008 into a random access memory (RAM) 1003 Various appropriate actions and processes are performed. In the RAM 1003, various programs and data necessary for the operation of the device 1000 are also stored.
  • the CPU 1001, ROM 1002, and RAM 1003 are connected to each other via a bus 1004.
  • An input/output (I/O) interface 1005 is also connected to the bus 1004 .
  • the following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 1008 including a hard disk, etc. and a communication section 1009 including a network interface card such as a LAN card, a modem, or the like.
  • the communication section 1009 performs communication processing via a network such as the Internet.
  • a drive 1010 is also connected to the I/O interface 1005 as needed.
  • a removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 1010 as necessary so that a computer program read therefrom is installed into the storage section 1008 as necessary.
  • embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, where the computer program includes program codes for executing the methods shown in the flowcharts.
  • the computer program may be downloaded and installed from a network via communication portion 1009 and/or installed from removable media 1011 .
  • this computer program is executed by a central processing unit (CPU) 1001, the above-described functions defined in the system of the present disclosure are performed.
  • CPU central processing unit
  • the computer-readable medium shown in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two.
  • a computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
  • each block in a flowchart or block diagram may represent a module, program segment, or portion of code that includes one or more logical functions for implementing specified executable instructions.
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved.
  • each block in the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a A combination of dedicated hardware and computer instructions.
  • the present disclosure also provides a computer-readable medium, which may be contained in the device described in the above-mentioned embodiments, or may exist independently without being assembled into the device.
  • the above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by a device, the device is made to implement the above-mentioned method for determining an anchor point.

Landscapes

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

Abstract

本公开提供一种锚点确定方法、基站、终端、设备及计算机可读存储介质，涉及领域移动通信技术领域。该方法包括：第一基站向终端发送第一RRC释放信息，第一RRC释放信息包括DRB与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和所述终端在非活动状态发送小数据包时所采用的用户面安全策略，以便所述终端在非活动状态发送小数据包时确定锚点基站。该方法帮助终端在进入非活动状态时可以配置合理的加密和/或完整性保护配置，避免关闭用户面安全功能所带来的安全风险，保持了终端和网络之间对于用户安全性理解的一致性，解决了终端和网络间的互操作问题。

Description

锚点确定方法、基站、终端、设备及计算机可读存储介质
相关申请的交叉引用
本公开要求于2021年08月10日提交的申请号为202110915015.0、名称为“锚点确定方法、基站、终端、设备及计算机可读存储介质”的中国专利申请的优先权，该中国专利申请的全部内容通过引用全部并入本文。
技术领域
本公开涉及移动通信技术领域，具体而言，涉及一种方锚点确定方法、基站、终端、设备及计算机可读存储介质。
背景技术
5G(5th Generation Mobile Communication Technology，第五代移动通信技术)作为下一代无线网络的主要技术，具有支持超宽带、大连接等技术特征。针对普通终端的数据业务传输，相比于4G(4th Generation Mobile Communication Technology，第四代移动通信技术)系统，5G引入了一种新的状态即非活动(Inactive)状态，其目的主要是降低小数据包传输过程中的时延，减少终端功耗。在非活动状态下，UE(User Equipment，用户终端)仍然保持在连接状态、且UE可以在RNA(RAN-based Notification Area，无线接入网通知区域)区域内移动而不用通过RRC(Radio Resource Control，无线资源控制)信令去通知NG-RAN。UE处于非活动状态时，最后一个服务gNB(next Generation Node B，下一代基站)保留UE的上下文和UE相关AMF(Access and Mobility Management Function，接入和移动性管理功能)和UPF(User Port Function，用户端口功能)的NG连接，一般称之为“锚点”。从核心网对于UE在非活动状态并不感知，认为其和处于连接态一样。在目前机制中，由锚点基站确定是否更换锚点。通常当需要更换锚点时，锚点基站会将相关的UE的上下文以及安全信息发送给当前服务基站。
在用户面处理过程中，当用户从连接态转换为非活动状态时，允许基站和UE保存AS(Access Stratum，接入层)层的上下文。在转入非活动状态时，基站需要发送RRCRelease(RRC释放)消息并携带suspendConfig指示信息。基站侧需要包括一个新的I-RNTI(Radio Network Temporary Identifier，无线网络临时标识)和一个NCC(Next Hop Chaining Count，下一跳链计数器)在消息中，其中I-RNTI是用来作为上下文的识别标识的。对于NCC而言，是否采用一个新的NCC主要是取决于基站侧，基站侧可以使用一个未使用过的NCC和NH组合，或者使用之前的NCC信息，这些内容都需要放置在RRCRelease消息里携带给终端，终端因此可以在从非活动状态正确使用上述信息。
当UE从非活动到连接(Connected)状态转换过程中，UE需要发送一个RRCResumeRequest(RRC恢复请求)消息，该消息的发送不采用任何完整性保护。对于后续其他(除了RRCreject之外)的RRC消息，UE需要根据当前接入小区的PCI(Physical-layer Cell Identity，物理层小区标识)，ARFCN(Absolute Radio Frequency Channel Number，绝对无线频道编号)-DL和KgNB/NH去做水平或者垂直密钥推导，从而获得KNG-RAN*。然后根据KNG-RAN*去计算获得KRRCint,KRRCenc,KUPenc,和KUPint。在收到目标基站发送的RRCResume(RRC恢复)消息之前终端不会建立任何用户面承载，不会从基站侧接收和向基站发送任何数据，需要与网络侧恢复信令连接后才能进行数据传输。
发送端MAC(Medium Access Control，媒体访问控制)层的复用功能将多个逻辑信道的数据装入一个传输信道，即将多个MAC SDU(Service Data Unit，服务数据单元)(RLC(Radio Link Control，无线链路控制)PDU(协议数据单元))复用到一个MAC PDU内，通过物理层信道发送出去。目前协议中逻辑信道标识，主要用来关联一个MAC层的逻辑信道和RLC承载之间的映射关系。而在上行发射过程中，通常采用的是逻辑信道组的方式进行资源申请和发射，哪些逻辑信道被映射到一个相同的逻辑信道组，一般需要通过RRC消息通知给终端。
在3GPP(3rd Generation Partnership Project，第三代合作计划)Rel-16之前的版本中，非活动状态时如果有小数据包需要传输，终端首先需要从非活动状态转变连接(Connected)状态，在与网络侧的控制面和用户面建立之后然后再进行数据的发送。考虑到实际网络中用户都有大量的背景业务需要进行发送，因此Rel-16这种机制一方面对于接入时延的改善不明显，另一方面由于终端完成一个或者多个数据包发送后仍然需要回到非活动状态，因此仍然会带来终端和网络之间过多的信令交互。
针对上述问题，3GPP在Rel-17中开展了小数据传输(Small Data Transmission，SDT)的研究工作，其目的是缩小终端在非活动时发送小数据包的接入时延，目前标准中已经确定支持基于RACH(Random Access Channel，随机接入信道)的数据包传输以及基于ConfiguredGrant的数据包传输。目前在非活动状态时传输小数据包的功能尚处于标准研究阶段
在所述背景技术部分公开的上述信息仅用于加强对本公开的背景的理解，因此它可以包括不构成对本领域普通技术人员已知的现有技术的信息。
发明内容
本公开的目的在于提供一种锚点确定方法、基站、终端、设备及计算机可读存储介质，至少在一定程度上克服由于相关技术终端和网络之间不一致的问题。
本公开的其他特性和优点将通过下面的详细描述变得显然，或部分地 通过本公开的实践而习得。
根据本公开的一方面，提供一种锚点确定方法，包括：第一基站向终端发送第一RRC释放信息，所述第一RRC释放信息包括DRB与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和所述终端在非活动状态发送小数据包时所采用的用户面安全策略，以便所述终端在非活动状态发送小数据包时确定锚点基站。
根据本公开的一个实施例，该方法还包括：所述第一基站接收第二基站发送的第一锚点配置信息，所述第一锚点配置信息包括第二基站的安全能力和所述终端的业务特征；其中，所述第一锚点配置信息由所述第二基站在随机接入过程中在MAC层缓存所述终端发送的数据后发送；所述第一基站根据所述第二基站的安全能力和所述终端的业务特征确定第二锚点配置信息；所述第一基站将所述第二锚点配置信息发送给所述第二基站，以便所述第二基站根据所述第二锚点配置信息生成发送给所述终端的RRC信息。
根据本公开的又一方面，提供一种锚点确定方法，包括：第二基站接收终端发送的RRCResumeRequest或者RRCResumeRequest1，还携带填报了的BSR和MAC SDU信息，其中BSR中携带的LCG ID为第一基站的配置信息，MAC SDU的逻辑信道编号采用第一基站的配置；所述第二基站缓存所述终端发送的数据，向所述第一基站发送第一锚点配置信息，所述第一锚点配置信息包括第二基站的安全能力和所述终端的业务特征，以便所述第一基站根据所述第一锚点配置信息确定锚点。
根据本公开的又一方面，提供一种基站，包括：安全策略确定单元，用于根据周边基站的安全能力配置终端在非活动状态发送小数据包时所采用的用户面安全策略；释放信息发送单元，用于向终端发送第一RRC释放信息，所述第一RRC释放信息包括DRB与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、所述终端在非活动状态发送小数据包时所采用的用户面安全策略，以便所述终端在非活动状态发送小数据包时确定锚点基站。
根据本公开的又一方面，提供一种终端，包括：释放信息接收单元，用于接收第一基站发送第一RRC释放信息，所述第一RRC释放信息包括DRB与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和所述终端在非活动状态发送小数据包时所采用的用户面安全策略，以便所述终端在非活动状态发送小数据包时确定锚点基站；释放信息存储单元，用于保存终端用户的非活动上下文配置信息，包括更新KgNB和KRRCint，保存用户标识I-RNTI或者ShortI-RNTI，保存DRB和逻辑信道的映射关系，保存逻辑信道和逻辑信道组的映射关系，若配置SDT的DRB列表确定相应的DRB可支持小数据包发送，则保存加密保持指示、加密算法、完整性保护保持指示、完整性保护算法，否则按照不包括任何加密和完整 性保护配置信息，不允许在非活动状态发送小数据包。
根据本公开的又一方面，提供一种基站，包括：恢复请求接收单元，用于接收终端发送的RRCResumeRequest或者RRCResumeRequest1，还携带填报了的BSR和MAC SDU信息，其中BSR中携带的LCG ID为第一基站的配置信息，MAC SDU的逻辑信道编号采用第一基站的配置；第一锚点信息发送单元，用于向所述第一基站发送第一锚点配置信息，所述第一锚点配置信息包括第二基站的安全能力和所述终端的业务特征，以便所述第一基站根据所述第一锚点配置信息确定锚点。
根据本公开的又一方面，提供一种设备，包括：存储器、处理器及存储在所述存储器中并可在所述处理器中运行的可执行指令，其特征在于，所述处理器执行所述可执行指令时实现如上所述的锚点确定方法。
根据本公开的又一方面，提供一种计算机可读存储介质，其上存储有计算机可执行指令，其特征在于，所述可执行指令被处理器执行时实现如上所述的锚点确定方法。
本公开的实施例提供的锚点确定方法，通过在RRC释放信息中包括DRB与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和所述终端在非活动状态发送小数据包时所采用的用户面安全策略，帮助终端在进入非活动状态时可以配置合理的加密和/或完整性保护配置，避免关闭用户面安全功能所带来的安全风险，保持了终端和网络之间对于用户安全性理解的一致性，解决了终端和网络间的互操作问题。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性的，并不能限制本公开。
附图说明
通过参照附图详细描述其示例实施例，本公开的上述和其它目标、特征及优点将变得更加显而易见。
图1示出本公开实施例中基于Xn接口的跨5G基站切换的架构示意图；
图2示出本公开一个实施例中锚点确定方法的流程图；
图3示出本公开另一个实施例中锚点确定方法的流程图；
图4示出本公开再一个实施例中锚点确定方法的流程图；
图5示出本公开又一个实施例中锚点确定方法的流程图；
图6示出本公开又一个实施例中锚点确定方法的流程图；
图7示出本公开一个实施例中基站的框图；
图8示出本公开一个实施例中终端的框图；
图9示出本公开另一个实施例中基站的框图；和
图10示出本公开实施例中一种电子设备的结构示意图。
具体实施方式
现在将参考附图更全面地描述示例实施例。然而，示例实施例能够以多种形式实施，且不应被理解为限于在此阐述的范例；相反，提供这些实施例使得本公开将更加全面和完整，并将示例实施例的构思全面地传达给本领域的技术人员。附图仅为本公开的示意性图解，并非一定是按比例绘制。图中相同的附图标记表示相同或类似的部分，因而将省略对它们的重复描述。
此外，所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多实施例中。在下面的描述中，提供许多具体细节从而给出对本公开的实施例的充分理解。然而，本领域技术人员将意识到，可以实践本公开的技术方案而省略所述特定细节中的一个或更多，或者可以采用其它的方法、装置、步骤等。在其它情况下，不详细示出或描述公知结构、方法、装置、实现或者操作以避免喧宾夺主而使得本公开的各方面变得模糊。
此外，术语“第一”、“第二”等仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本公开的描述中，“多个”的含义是至少两个，例如两个，三个等，除非另有明确具体的限定。符号“/”一般表示前后关联对象是一种“或”的关系。
在本公开中，除非另有明确的规定和限定，“连接”等术语应做广义理解，例如，可以是电连接或可以互相通讯；可以是直接相连，也可以通过中间媒介间接相连。对于本领域的普通技术人员而言，可以根据具体情况理解上述术语在本公开中的具体含义。
在5G网络中，Xn切换是一种基于Xn接口的跨5G基站(gNB)切换，参照图1，UE 11已经在5G网络注册并建立了PDU会话(Protocol Data Unit Session，协议数据单元会话)，例如，如图1中，通过源gNB(Source gNB)12接入到5G网络并正在上网。如果UE 11发生了位置移动，离开了源gNB 12服务的小区，即将进入新的目标gNB(Target gNB)13所服务的小区。
本公开的发明人发现：目前的标准协议中存在以下缺陷：
(1)终端无法确定非活动状态发送小数据包是否采用完整性和/或加密。
目前的非活动机制都是在信令建立后才发送数据，而此时网络侧已经通知了终端是否采用加密和完整性保护。基于现有方法，可能导致终端采用的用户面机制和网络侧不统一而导致的数据丢弃。
(2)目标基站在终端初始接入过程中无法区分业务类型。
终端发送RRCResume过程中携带的上行数据首先被缓存在MAC层，并等待目标基站和锚点基站之间的协商过程，在MAC层处理过程中，MAC层仅能看见发送的逻辑信道组，而这个逻辑信道组是由源基站配置的， 因此目标基站不知道LCG和DRB之间的映射关系，因此无法确定到底是哪个DRB发送的业务，从而导致目标侧不清楚终端后续的发送行为，而无法提供有效的信息给源侧。
(3)目标基站无法确定哪些信息提供给源基站用于确定锚点。
目前标准中尚未明确采用哪些信息携带给源基站用于确定锚点基站，若按照目标Rel-16的非活动状态中Retrieve UE Context Request/Response消息所携带的内容，可能导致因为目标基站无法满足源基站的加密/完整性保护要求，而导致UE之前发送的数据被丢弃。
基于上述需求和原因分析，目前的3GPP NR(New Radio，新空口)的协议都无法满足需求，需要通过新的方式来进行增强以满足网络部署和优化的需求。
图2示出本公开一个实施例中锚点确定方法的流程图。
如图2所示，S202，第一基站向终端发送第一RRC释放信息，第一RRC释放信息包括DRB(Data Radio Bearer，数据资源承载)与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和所述终端在非活动(Inactive)状态发送小数据包时所采用的用户面安全策略。
S204，基于第一RRC释放信息确定终端在非活动状态发送小数据包时的锚点基站。
上述实施例中，通过在RRC释放信息中包括DRB与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和该终端在非活动状态发送小数据包时所采用的用户面安全策略，帮助终端在进入非活动状态时可以配置合理的加密和/或完整性保护配置，避免关闭用户面安全功能所带来的安全风险，保持了终端和网络之间对于用户安全性理解的一致性，解决了终端和网络间的互操作问题。
图3示出本公开另一个实施例中锚点确定方法的流程图。
如图3所示，S301，第一基站根据周边基站的安全能力配置用户在非活动状态发送小数据包时所采用的用户面安全策略。
S302，第一基站向终端发送第一RRC释放信息。
S303，终端在非活动状态向第二基站发送数据。
S304，第一基站接收第二基站发送的第一锚点配置信息，第一锚点配置信息包括基站的安全能力和终端的业务特征；其中，第一锚点配置信息由第二基站在随机接入过程中将终端发送的数据缓存在MAC层后发送。第二基站在随机接入过程中将终端发送的数据缓存在MAC层，将第二基站的安全能力和终端的业务特征作为辅助信息发送到第一基站。
S306，第一基站根据第二基站的安全能力和终端的业务特征以确定第二锚点配置信息。第一基站根据第二基站的安全能力和终端的业务特征确定锚点位置，并将协议和承载配置信息发送给第二基站。
S308，第一基站将第二锚点配置信息发送给第二基站，以便第二基站 根据第二锚点配置信息生成发送给终端的RRC信息。第二锚点配置信息包括锚点位置、协议和承载配置信息。
上述实施例中，帮助锚点基站正确的选择是否更改锚点位置，避免了接入基站和锚点之间安全性不匹配、对业务行为理解不一致所引发的终端数据丢弃等问题。
图4示出本公开再一个实施例中锚点确定方法的流程图。其中介绍了终端初始发送上行小数据包时确定锚点的信令过程。具体过程如下：
S402，第一基站控制面实体(源gNB-CU)获取所配置的RNA区域内所有基站的加密算法和/或完整性保护算法。每个基站的算法配置情况可通过网管进行配置或者根据RNA区域中基站间的信令指示来进行确定。
S404，第一基站控制面实体确定终端需要进入非活动状态时，检查终端当前采用的加密算法和完整性保护算法是否被RNA区域内所有的基站支持。如果可以被全部基站或者至少存在一个基站所支持，则确定终端在非活动状态发送小数据包时需保持加密或完整性保护配置；若全部不支持，则确定终端在非活动状态发送小数据包时不保持加密或完整性保护配置，或者更换成相应的加密/完整性保护算法。生成相应的第一RRC释放信息。其中第一RRC释放信息包括但不限于如下：
1)非活动状态标识。可以采用I-RNTI或者ShortI-RNTI。
2)加密保持指示：枚举或者布尔类型，用于指示在非活动状态发起数据时是否保持数据加密。当该选项不携带时表示不保持。
3)加密算法：枚举型。可以包括128-NEA1，128-NEA2和128-NEA3。当该选项不携带时，表示需要加密算法不改变，携带时表示在非活动发起数据时需要应用该加密算法。
4)完整性保护保持指示：枚举或者布尔类型，用于指示在非活动状态发起数据时是否保持完整性保护。当该选项不携带时表示不保持。
5)完整性保护算法：枚举型。可以包括128-NIA1，128-NIA2和128-NIA3。当该选项不携带时，表示需要加密算法不改变，携带时表示在非活动发起数据时需要应用该加密算法。
6)配置为SDT的DRB列表：一个或者多个DRB标识，包含该标识时，表示该DRB可支持在非活动状态发送小数据包。
S406，第一基站控制面实体发送给第一基站分离实体包含终端用户第一RRC释放信息的用户上下文修改消息。其中第一基站控制面实体可以与第一基站分离实体分开部署或者合设部署。
S408，第一基站分离实体将第一RRC释放消息(RRCRelease(UP security active(上行安全活动)))发送给终端用户。
S410，UE进入非活动(inactive)状态。终端用户收到第一RRC释放信息后，如果包含了suspend配置信息用于响应RRCResumeRequest或者RRCResumeRequest1，则停止已经运行的定时器T319，保存终端用户的非 活动上下文配置信息，包括更新KgNB和KRRCint，保存用户标识I-RNTI或者ShortI-RNTI，保存DRB和逻辑信道的映射关系，保存逻辑信道和逻辑信道组的映射关系，若配置SDT的DRB列表确定相应的DRB可支持小数据包发送，则表示是需要在非活动状态进行小数据包传输，则保存加密保持指示、加密算法、完整性保护保持指示、完整性保护算法，否则按照不包括任何加密和完整性保护配置信息，并且不允许在非活动状态发送小数据包。
S412，终端根据配置的SDT的DRB上有数据要发送，触发发送RRCResumeRequest(Uplink Data with security active)或者RRCResumeRequest1，根据保存的非活动上下文配置信息确定发送的上行数据的用户面安全策略。其中若配置了加密保持指示信息，则终端的PDCP(Packet Data Convergence Protocol，分组数据汇聚)层对数据进行加密操作，并根据是否配置了加密算法，确定是否变更加密算法。若配置了完整性保护保持指示信息，则终端的PDCP层对数据进行完整性保护操作，并根据是否配置了完整性保护算法，确定是否变更完整性保护算法。
终端在第二基站配置的上行资源中除了发送RRCResumeRequest或者RRCResumeRequest1，还携带填报了的BSR(Buffer Status Report，缓冲状态报告)和MAC SDU信息。其中BSR中携带的LCG(Logical channel Group，逻辑信道组)ID为第一基站的配置信息，MAC SDU的逻辑信道编号采用第一基站的配置。
S414，第二基站分离实体在收到RRCResumeRequest或者RRCResumeRequest1后同时也得到了上行数据，缓存MAC SDU。确定终端是支持非活动状态的小数据发送，根据终端上报的BSR信息，上行发送时数据采用的LCG以及数据发送采用的LC ID信息确定上行发送的数据信息。
S416，第二基站分离实体通过与第二基站控制面实体间的接口向第二基站控制面实体发送包括第一业务数据配置信息的初始UL消息传输(Initial UL Message Transfer)消息。其中第一业务数据配置信息包括但不限于如下：
1)SDT指示信息：枚举或者布尔类型，表示终端同时有上行数据需要发送。
2)上行待传数数据量：终端上报的BSR大小。
3)上行LCG标识：用于数据传输的上行逻辑信道组标识，如TS38.321中定义。在BSR上报中携带的LCG域，这里不包括传递信令的逻辑信道组标识。
4)待传数据的逻辑信道列表：包含了一个或者多个逻辑信道编号，为MAC SDU中包含的逻辑信号标识。
S418，第二基站控制面实体收到Initial UL Message Transfer消息后， 将第一锚点配置信息通过Xn接口Anchor decision Request(锚点决定请求)发送给第一基站控制面实体。其中第一锚点配置信息包括但不限于如下信息：
1)第二基站分配的用户XnAP标识：在Xn接口上第二基站为UE分配的标识。
2)第二基站对于加密算法的支持列表：包括一个或者多个已定义算法。
3)第二基站对于完整性保护算法的支持列表：包括一个或者多个已定义算法。
4)SDT指示信息：枚举或者布尔类型，表终端同时有上行数据需要发送。
5)上行待传数数据量：终端上报的BSR大小。
6)上行LCG标识：用于数据传输的上行逻辑信道组标识，如TS38.321中定义。在BSR上报中携带的LCG域。这里不包括传递信令的逻辑信道组标识。
7)待传数据的逻辑信道列表：包含了一个或者多个逻辑信道编号，为MAC SDU中包含的逻辑信号标识。
S420，第一基站控制面实体根据第一锚点配置信息确定锚点。第一基站控制面实体收到第一锚点配置信息后，根据上行待传数据量以及LCG ID和LC ID确定上行需要传输的数据量以及对应的DRB信息，并根据这些DRB的业务特征确定是否还有后续传输，如果是一次传输就完毕且第二基站支持终端用户之前配置的加密和/或完整性保护算法，则锚点更新为第二基站；若加密或完整性保护算法之一无法支持，则锚点仍然维持在第一基站；如果是多次传输，则锚点仍然维持在第一基站。
S422A、S422B，第一基站控制面实体根据锚点的配置信息确定第二锚点配置信息，并将第二锚点配置信息通过第一基站和第二基站之间的接口发送给第二基站控制面实体。具体分两种不同的情况：情况1和情况2。
其中，S422A，若锚点为第二基站，则第二锚点配置信息包括但不限于：
1)第一基站分配的用户XnAP标识。
2)第二基站分配的用户XnAP标识：与第一锚点配置信息中第二基站提供的数值相同。
3)AMF标识信息：如协议中定义的GUAMI(AMF全局标识信息)信息。
4)用户上下文配置信息，包括但不限于如下：
a)AMF给UE分配的NG接口标识。
b)AMF的地址和端口：包括AMF的IP地址，或者AMF的IP地址和端口号。
c)UE安全能力：UE支持的NR加密算法列表，UE支持的NR完整 性保护算法列表，UE支持的E-UTRA加密算法列表，UE支持的E-UTRA完整性保护算法列表。
d)AS层安全配置：KNG-RAN*和Next Hop Chaining Count(NCC)。
e)UE最大聚合速率：针对所有Non-GBR的上行和下行分别定义的最大传输速率。
f)PDU会话建立列表，每个PDU会话的配置包括但不限于如下：
-PDU会话标识；
-切片ID：S-NASSI；
-UPF分配的上行和下行地址信息：每个方向包括IP地址和端口地址；
-用户面安全策略：加密和完整性保护的激活配置；
-E-RAB建立的列表：枚举值为0-15。
5)PDCP配置信息：第一基站采用的PDCP配置中DRB配置。
6)RLC配置信息：第一基站采用的RLC承载和逻辑信道的映射配置。
其中，S422B，若锚点为第一基站，则第二锚点配置信息包括但不限于：
1)第一基站分配的用户XnAP标识；
2)第二基站分配的用户XnAP标识：与第一锚点配置信息中第二基站提供的数值相同；
3)UE最大聚合速率：针对所有Non-GBR的上行和下行分别定义的最大传输速率；
4)RLC配置信息：包括RLC承载和逻辑信道的映射关系；
5)PDU会话建立列表，每个PDU会话的配置包括但不限于如下：
a)PDU会话标识；
b)切片ID：S-NASSI；
c)第一基站分配的上行地址信息：包括IP地址和端口地址；
d)是否需要下行地址信息：枚举或布尔类型；
e)E-RAB建立的列表：枚举值为0-15。
6)发送给终端的RRC消息：用于让用户返回非活动状态的RRCRelease消息。
S424A，S424B，第二基站控制面实体收到第二锚点配置信息后，确定锚点的归属配置，并根据第二锚点配置信息配置协议栈相关参数和承载的相关参数。
其中，S424A，若锚点是第二基站，则缓存用户的RRC消息，在第一定时器超时后未收到任何上行用户数据的传输或者收到来自第二基站用户面实体的承载释放请求消息后，向终端发送缓存的RRC消息。
S424B，若锚点是第一基站，则在配置完成相关的协议参数和承载参数后，按照第二锚点配置信息对于缓存的MAC SDU进行RLC层处理， 并根据第一基站分配的上行地址信息转发处理后的上行数据。若PDU会话列表中包含了至少一个会话需要配置下行地址，则第二基站触发一个接口地址指示信息给第一基站。其中接口地址指示信息包括但不限于如下信息：
1)第一基站分配的用户XnAP标识；
2)第二基站分配的用户XnAP标识：与第一锚点配置信息中第二基站提供的数值相同；
3)PDU会话地址列表：可以接收PDU会话下行数据的会话列表，其中每个PDU会话的配置包括但不限于如下：
a)PDU会话标识；
b)下行地址信息：包括IP地址和端口地址。
在一个实施例中，还可以包括如下步骤：
步骤13：如果第二基站控制面实体收到来自第一基站的认证失败消息，则生产RRCsetup消息，并通过用户上下文释放消息发送给第二基站分离实体。第二基站分离实体收到后删除缓存的用户发送的MAC SDU数据，并将RRCsetup消息发送给终端，终端删除缓存中的数据，从连接态开始建立信令。
步骤14：如果第一基站控制面实体收到来自第一基站的接口地址指示信息后，则根据指示中的下行PDU会话地址信息，将来自核心网的数据通过第一基站和第二基站之间的用户面接口按照下行地址信息发送给第二基站控制面实体。同时第二基站将上行数据向PDU会话建立列表中的上行地址信息作为目的地址转发对应LCG的上行数据。
步骤15：如果锚点是第二基站，则第二基站控制面实体向核心网控制面实体发送路径倒换请求消息，指示需要变更的业务承载的下行地址接收信息。
步骤16：核心网控制面实体通过路径倒换响应消息配置相关承载新的上行发送地址信息发送给第二基站控制面实体。
步骤17：第二基站控制面实体通过用户承载修改消息通知第二基站用户面实体，将发送到核心网的上行地址信息通知给第二基站用户面实体。第二基站用户面实体将配置结果通知给第二基站控制面实体。
步骤18：第二基站根据第二锚点配置信息，完成第二基站的协议栈和业务配置，并将第一RLC层配置信息通过与第二基站分离实体间的接口发送给第二基站分离实体。其中第一RLC层配置信息包括但不限于如下：
第二基站控制面实体为用户在F1接口上分配的标识
第二基站分离实体为用户在F1接口上分配的标识别
RLC层的配置信息：包括LCG和RLC承载的映射关系，和协议栈参数
每个DRB对应上行通道地址信息：包括IP地址和端口地址
步骤19：第二基站分离实体收到第一RLC层配置信息后，完成相关协议栈参数和承载的配置，并给基于RLC层配置信息对于缓存的MAC SDU进行数据，并将处理完的数据通过DRB对应的上行通道地址信息发送给第二基站用户面实体。
步骤20：第二基站用户面实体在不激活定时器超时后，指示第二基站控制面实体用户处于非激活状态。
步骤21：第二基站控制面实体生产RRCRelease消息，其中RRCRelease消息中包含了Suspend配置信息以及哪些承载在发送数据时是否需要激活加密和/或完整性保护，第二基站控制面实体将该RRCRelease消息发送给终端用户，使得终端用户返回非活动状态。
图5示出本公开又一个实施例中锚点确定方法的流程图。该实施例中描述了终端从基站1进入非活动状态，并移动到基站2发起小数据包的传输的过程，其中基站1和基站2支持相同的加密和完整性保护能力，终端发起的DRB编号为DRB#1。下面结合具体的步骤描述一个网络侧配置到终端侧发起随机过程时携带数据包的实现。
如图5所示，S502，gNB1-CU-CP获取所配置的RNA区域内所有基站的加密和/或完整性保护算法。其中每个基站的算法配置情况可通过网管进行配置。
S504，gNB1-CU-CP确定终端需要进入非活动状态时，检查终端当前采用的加密和完整性保护算法是否被RNA区域内所有的基站都支持，用户面安全性可以被全部基站所支持，则确定终端在非活动状态发送小数据包时需保持加密或完整性保护配置。
S506，gNB1-CU-CP发送给gNB1-DU包含终端用户第一RRC释放信息的用户上下文修改消息。其中第一RRC释放信息包括如下：
非活动状态标识：采用I-RNTI
加密保持指示：1
加密算法：128-NEA1
完整性保护保持指示：1
完整性保护算法：128-NIA1。
配置为SDT的DRB列表：DRB#1。
S508，gNB1-DU将第一RRC释放消息(RRCRelease(UP security active(上行安全活动)))发送给终端用户。
S510，终端用户收到RRCRelease信息后，由于包含了suspend配置信息用于响应RRCResumeRequest，则停止已经运行的定时器T319，保存终端用户的非活动上下文配置信息，包括更新KgNB and KRRCint，保存用户标识I-RNTI或者ShortI-RNTI，保存DRB和逻辑信道的映射关系，保存逻辑信道和逻辑信道组的映射关系，确定相应的DRB#1可支持小数据包发送，需要在非活动状态进行小数据包传输，保存加密保持指示、加 密算法、完整性保护保持指示、完整性保护算法。
S512，终端根据配置的SDT的DRB#1上有数据要发送，触发发送RRCResumeRequest(Uplink Data with security active(具有安全活动的上行数据))，并且根据保存的非活动上下文配置信息确定发送的上行数据的用户面安全策略，则终端的PDCP层对数据进行加密操作，确定变更加密算法为128-NEA1。同时配置了完整性保护保持指示信息，则终端的PDCP层对数据进行完整性保护操作，确定完整性保护算法采用128-NIA1。
终端在gNB2配置的上行资源中除了发送RRCResumeRequest或者RRCResumeRequest1，还携带填报了的BSR和MAC SDU信息。其中BSR中携带的LCG ID为第一基站的配置信息，MAC SDU的逻辑信道编号采用gNB1的配置LCG#2。
图6示出本公开又一个实施例中锚点确定方法的流程图。该实施例主要描述终端需要在DRB1上发送上行小数据包，gNB2与之前的锚点基站gNB1相关确定锚点仍然维持在gNB1之上，并将自己的上行数据包通过Xn接口发送给gNB1的过程。
如图6所示，S602，终端在gNB2配置的上行资源中除了发送RRCResumeRequest或者RRCResumeRequest1，还携带填报了的BSR和MAC SDU信息。其中BSR中携带的LCG ID为第一基站的配置信息，MAC SDU的逻辑信道编号采用第一基站的配置。
S604，gNB2-DU在收到RRCResumeRequest或者RRCResumeRequest1后同时也得到了上行数据确定终端是支持非活动状态的小数据发送，根据终端上报的BSR信息，上行发送时数据采用的LCG以及数据发送采用的LCID信息确定上行发送的数据信息。
S606，gNB2-DU通过与gNB2-CU-CP间的接口向gNB2-CU-CP发送包括第一业务数据配置信息的Initial UL Message Transfer消息，其中第一业务数据配置信息包括如下：
SDT指示信息：1；
上行待传数数据量：100Kbytes；
上行LCG标识：LCG#2；
待传数据的逻辑信道列表：LC#4。
S608，gNB2-CU-CP收到Initial UL Message Transfer消息后，将第一锚点配置信息通过Xn接口发送给gNB1-CU-CP。其中第一锚点配置信息包括如下信息：
gNB2分配的用户XnAP标识：
gNB2对于加密算法的支持列表
gNB2对于完整性保护算法的支持列表
SDT指示信息：1
上行待传数数据量：100kbytes
上行LCG标识：LCG#2
待传数据的逻辑信道列表：LC#4。
S610，gNB1-CU-CP收到第一锚点配置信息后，根据上行待传数据量以及LCG ID和LC ID确定上行需要传输的数据量以及对应的DRB信息。并一次传输就完毕且gNB2支持终端用户之前配置的加密和/或完整性保护算法，则锚点更新为gNB2。
S612，gNB1-CU-CP根据锚点的配置信息确定第二锚点配置信息，并将第二锚点配置信息通过第一基站和gNB2之间的接口发送给gNB2-CU-CP。其中若锚点为gNB2，则第二锚点配置信息包括：
第一基站分配的用户XnAP标识
gNB2分配的用户XnAP标识：
AMF标识信息：
用户上下文配置信息，包括如下：
AMF给UE分配的NG接口标识
AMF的地址和端口：
UE安全能力：，
AS层安全配置：KNG-RAN*和Next Hop Chaining Count(NCC)
UE最大聚合速率：
PDU会话建立列表，每个PDU会话的配置包括如下：
-PDU会话标识
-切片ID：
-UPF分配的上行和下行地址信息：
-用户面安全策略：加密和完整性保护的激活配置
-E-RAB建立的列表
PDCP配置信息
RLC配置信息
S614，gNB2-CU-CP收到第二锚点配置信息后，确定锚点的归属配置，并根据第二锚点配置信息配置协议栈相关参数和承载的相关参数。若锚点是gNB2，则缓存用户的RRC消息，在第一定时器超时后未收到任何上行用户数据的传输或者收到来自gNB2-CU-UP的承载释放请求消息后，向终端发送缓存的RRC消息。
S616，锚点是gNB2，则gNB2-CU-CP向核心网控制面实体发送路径倒换请求消息，指示需要变更的业务承载的下行地址接收信息。
S618，核心网控制面实体通过路径倒换响应消息配置相关承载新的上行发送地址信息发送给gNB2-CU-CP。
S620，gNB2-CU-CP通过用户承载修改消息通知gNB2-CU-UP，将发送到核心网的上行地址信息通知给gNB2-CU-UP。gNB2-CU-UP将配置结 果通知给gNB2-CU-CP。
S622，gNB2根据第二锚点配置信息，完成gNB2的协议栈和业务配置，并将第一RLC层配置信息通过与gNB2-DU间的接口发送给gNB2-DU。其中第一RLC层配置信息包括如下：
gNB2-CU-CP为用户在F1接口上分配的标识；
gNB2-DU为用户在F1接口上分配的标识别；
RLC层的配置信息：
每个DRB对应上行通道地址信息。
S624，gNB2-DU收到第一RLC层配置信息后，完成相关协议栈参数和承载的配置，并给基于RLC层配置信息对于缓存的MAC SDU进行数据，并将处理完的数据通过DRB对应的上行通道地址信息发送给gNB2-CU-UP。
S626，gNB2-CU-UP在不激活定时器超时后，指示gNB2-CU-CP用户处于非激活状态。
S628，gNB2-CU-CP生产RRCRelease消息，其中RRCRelease消息中包含了Suspend配置信息以及哪些承载在发送数据时是否需要激活加密和/或完整性保护，gNB2-CU-CP将该RRCRelease消息发送给终端用户，使得终端用户返回非活动状态。
本专利提出了一种确定锚点的方法，保证数据收发时用户面安全性的正确性，避免了错误的配置和锚点选择导致的数据丢失；该方法还可以有效的降低基站和终端之间的信令开销，降低上行数据的传输时延，提升用户的体验和感知。
图7示出本公开一个实施例中基站的框图。如图7所示，该实施例中基站包括：安全策略确定单元71，用于根据周边基站的安全能力配置终端在非活动状态发送小数据包时所采用的用户面安全策略；释放信息发送单元72，用于向终端发送第一RRC释放信息，该第一RRC释放信息包括DRB与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、该终端在非活动状态发送小数据包时所采用的用户面安全策略，以便该终端在非活动状态发送小数据包时确定锚点基站。
图8示出本公开一个实施例中终端的框图。如图8所示，该实施例中终端包括：释放信息接收单元81，用于接收第一基站发送第一RRC释放信息，该第一RRC释放信息包括DRB与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和该终端在非活动状态发送小数据包时所采用的用户面安全策略，以便该终端在非活动状态发送小数据包时确定锚点基站；释放信息存储单元82，用于保存终端用户的非活动上下文配置信息，包括更新KgNB和KRRCint，保存用户标识I-RNTI或者ShortI-RNTI，保存DRB和逻辑信道的映射关系，保存逻辑信道和逻辑信道组的映射关系，若配置SDT的DRB列表确定相应的DRB可支持小数据包发送，则保存 加密保持指示、加密算法、完整性保护保持指示、完整性保护算法，否则按照不包括任何加密和完整性保护配置信息，不允许在非活动状态发送小数据包。
在一个实施例中，终端还包括：小数据发送单元83，用于据配置的SDT的DRB上有数据要发送，触发发送RRCResumeRequest或者RRCResumeRequest1，根据保存的非活动上下文配置信息确定发送的上行数据的用户面安全策略；其中，若配置了加密保持指示信息，则该终端的PDCP层对数据进行加密操作，根据是否配置了加密算法，确定是否变更加密算法；若配置了完整性保护保持指示信息，则该终端的PDCP层对数据进行完整性保护操作，并且根据是否配置了完整性保护算法，确定是否变更完整性保护算法。
图9示出本公开另一个实施例中基站的框图。如图9所示，该基站包括：恢复请求接收单元91，用于接收终端发送的RRCResumeRequest或者RRCResumeRequest1，还携带填报了的BSR和MAC SDU信息，其中BSR中携带的LCG ID为第一基站的配置信息，MAC SDU的逻辑信道编号采用第一基站的配置；第一锚点信息发送单元92，用于向该第一基站发送第一锚点配置信息，该第一锚点配置信息包括第二基站的安全能力和该终端的业务特征，以便该第一基站根据所述第一锚点配置信息确定锚点。
本公开的方案对终端改动较小，有良好的后向兼容性和部署可行性。本方案是在现有协议上进行增强，借用已有的协议过程，实现难度较低。
本公开实施例提供的基站和终端中的各个模块的具体实现可以参照上述方法中的内容，此处不再赘述。
图10示出本公开实施例中一种电子设备的结构示意图。需要说明的是，图10示出的设备仅以计算机系统为示例，不应对本公开实施例的功能和使用范围带来任何限制。
如图10所示，设备1000包括中央处理单元(CPU)1001，其可以根据存储在只读存储器(ROM)1002中的程序或者从存储部分1008加载到随机访问存储器(RAM)1003中的程序而执行各种适当的动作和处理。在RAM 1003中，还存储有设备1000操作所需的各种程序和数据。CPU1001、ROM 1002以及RAM 1003通过总线1004彼此相连。输入/输出(I/O)接口1005也连接至总线1004。
以下部件连接至I/O接口1005：包括键盘、鼠标等的输入部分1006；包括诸如阴极射线管(CRT)、液晶显示器(LCD)等以及扬声器等的输出部分1007；包括硬盘等的存储部分1008；以及包括诸如LAN卡、调制解调器等的网络接口卡的通信部分1009。通信部分1009经由诸如因特网的网络执行通信处理。驱动器1010也根据需要连接至I/O接口1005。可拆卸介质1011，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器1010上，以便于从其上读出的计算机程序根据需要被安装 入存储部分1008。
特别地，根据本公开的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本公开的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信部分1009从网络上被下载和安装，和/或从可拆卸介质1011被安装。在该计算机程序被中央处理单元(CPU)1001执行时，执行本公开的系统中限定的上述功能。
需要说明的是，本公开所示的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本公开中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本公开中，计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、RF等等，或者上述的任意合适的组合。
附图中的流程图和框图，图示了按照本公开各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，上述模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图或流程图中的每个方框、以及框图或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
作为另一方面，本公开还提供了一种计算机可读介质，该计算机可读介质可以是上述实施例中描述的设备中所包含的；也可以是单独存在，而 未装配入该设备中。上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被一个该设备执行时，使得该设备实现上述的锚点确定方法。
以上具体地示出和描述了本公开的示例性实施例。应可理解的是，本公开不限于这里描述的详细结构、设置方式或实现方法；相反，本公开意图涵盖包含在所附权利要求的精神和范围内的各种修改和等效设置。

Claims (41)

  1. 一种锚点确定方法，包括：
    第一基站向终端发送第一无线资源控制RRC释放信息，所述第一RRC释放信息包括数据资源承载与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和所述终端在非活动状态发送小数据包时所采用的用户面安全策略；
    所述第一基站接收第二基站发送的第一锚点配置信息，所述第一锚点配置信息包括第二基站的安全能力和所述终端的业务特征；其中，所述第一锚点配置信息由所述第二基站在随机接入过程中在MAC层缓存所述终端发送的数据后发送；
    所述第一基站根据所述第二基站的安全能力和所述终端的业务特征确定第二锚点配置信息；
    所述第一基站将所述第二锚点配置信息发送给所述第二基站，以便所述第二基站根据所述第二锚点配置信息生成发送给所述终端的RRC信息。
  2. 根据权利要求1所述的锚点确定方法，其中，所述第一RRC释放信息包括所述终端在非活动状态发送小数据包时所采用的用户面安全策略，所述方法还包括：
    所述第一基站根据周边基站的安全能力配置终端在非活动状态发送小数据包时所采用的用户面安全策略。
  3. 根据权利要求2所述的锚点确定方法，其中，基站的安全能力包括加密算法和/或完整性保护算法；
    该方法还包括：
    所述第一基站的控制面实体获取所配置的无线接入网通知区域内所有基站的加密和/算法或完整性保护算法。
  4. 根据权利要求3的锚点确定方法，其中，还包括：
    通过网管配置基站的加密和/算法或完整性保护算法；或
    根据无线接入网通知区域中基站间的信令指示确定基站的加密算法和/或完整性保护算法。
  5. 根据权利要求2的锚点确定方法，其中，所述第一基站根据周边基站的安全能力配置终端在非活动状态发送小数据包时所采用的用户面安全策略包括：
    当所述第一基站控制面实体确定所述终端需要进入非活动状态时，检查所述终端当前配置的加密算法或完整性保护算法是否被无线接入网通知区域内的基站支持，如果无线接入网通知区域内至少一个基站所支持，则确定终端在非活动状态发送小数据包时需保持加密或完整性保护配置，若全部不支持，则确定终端在非活动状态发送小数据包时不保持加密或完整性保护配置，或者更换成相应的加密算法或完整性保护算法，生成所述 第一RRC释放信息。
  6. 根据权利要求1所述的锚点确定方法，其中，所述第一RRC释放信息包括：非活动状态标识、加密保持指示、加密算法、完整性保护保持指示、完整性保护算法、配置为小数据传输的数据资源承载列表。
  7. 根据权利要求6所述的锚点确定方法，其中，所述第一基站向终端发送第一RRC释放信息包括：
    第一基站控制面实体发送给第一基站分离实体包含终端用户的第一RRC释放信息的用户上下文修改消息；
    所述第一基站分离实体将所述第一RRC释放消息发送给所述终端。
  8. 根据权利要求7所述的锚点确定方法，其中，还包括：
    所述终端收到所述第一RRC释放信息后，如果包含了暂停suspend配置信息用于响应RRCResumeRequest或者RRCResumeRequest1，则停止已经运行的定时器T319；
    所述终端保存终端用户的非活动上下文配置信息，包括更新KgNB和KRRCint，保存用户标识I-RNTI或者ShortI-RNTI，保存数据资源承载和逻辑信道的映射关系，保存逻辑信道和逻辑信道组的映射关系，若配置小数据传输的数据资源承载列表确定相应的数据资源承载可支持小数据包发送，则保存加密保持指示、加密算法、完整性保护保持指示、完整性保护算法，否则按照不包括任何加密和完整性保护配置信息，不允许在非活动状态发送小数据包。
  9. 根据权利要求8所述的锚点确定方法，其中，还包括：
    所述终端根据配置的小数据传输的数据资源承载上有数据要发送，触发发送RRCResumeRequest或者RRCResumeRequest1，根据保存的非活动上下文配置信息确定发送的上行数据的用户面安全策略；
    其中，
    若配置了加密保持指示信息，则所述终端的分组数据汇聚层对数据进行加密操作，根据是否配置了加密算法，确定是否变更加密算法；
    若配置了完整性保护保持指示信息，则所述终端的分组数据汇聚层对数据进行完整性保护操作，并且根据是否配置了完整性保护算法，确定是否变更完整性保护算法。
  10. 根据权利要求9所述的锚点确定方法，其中，还包括：
    所述终端在所述第二基站配置的上行资源中除了发送RRCResumeRequest或者RRCResumeRequest1，还携带填报了的缓冲状态报告和媒体访问控制服务数据单元信息，其中所述缓冲状态报告中携带的逻辑信道组标识为所述第一基站的配置信息，媒体访问控制服务数据单元的逻辑信道编号采用所述第一基站的配置。
  11. 根据权利要求10所述的锚点确定方法，其中，还包括：
    所述第二基站分离实体在收到RRCResumeRequest或者 RRCResumeRequest1后，得到上行数据，确定所述终端是支持非活动状态的小数据发送；
    所述第二基站分离实体根据所述终端上报的缓冲状态报告信息、上行发送时数据采用的逻辑信道组以及数据发送采用的待传数据的逻辑信道列表标识信息确定上行发送的数据信息。
  12. 根据权利要求11所述的锚点确定方法，其中，所述第一基站接收所述第二基站发送的第一锚点配置信息包括：
    所述第二基站分离实体通过与第二基站控制面实体间的接口向所述所述第二基站控制面实体发送包括第一业务数据配置信息的初始上行消息传输Initial UL Message Transfer消息；
    所述第二基站控制面实体收到Initial UL Message Transfer消息后，将所述第一锚点配置信息通过Xn接口发送给所述第一基站控制面实体。
  13. 根据权利要求12所述的锚点确定方法，其中，所述第一业务数据配置信息包括小数据传输指示信息、上行待传数数据量、上行逻辑信道组标识、在缓冲状态报告上报中携带的逻辑信道组域、待传数据的逻辑信道列表，所述逻辑信道列表包含了一个或者多个逻辑信道编号、为媒体访问控制服务数据单元中包含的逻辑信号标识。
  14. 根据权利要求12所述的锚点确定方法，其中，所述第一锚点配置信息包括：
    所述第二基站分配的用户XnAP标识；
    所述第二基站对于加密算法的支持列表；
    所述第二基站对于完整性保护算法的支持列表；
    小数据传输指示信息；
    上行待传数数据量；
    上行逻辑信道组标识，其中，在缓冲状态报告上报中携带的逻辑信道组域；
    待传数据的逻辑信道列表，其中包含了一个或者多个逻辑信道编号，为媒体访问控制服务数据单元中包含的逻辑信号标识。
  15. 根据权利要求14所述的锚点确定方法，其中，所述第一基站根据所述第二基站的安全能力和所述终端的业务特征以确定第二锚点配置信息包括：
    所述第一基站控制面实体收到所述第一锚点配置信息后，根据所述上行待传数据量以及逻辑信道组标识和待传数据的逻辑信道列表标识定上行需要传输的数据量以及对应的数据资源承载信息；根据数据资源承载的业务特征确定是否还有后续传输，如果是一次传输就完毕且第二基站支持终端用户之前配置的加密和/或完整性保护算法，则锚点更新为所述第二基站，若加密或完整性保护算法之一无法支持，则锚点仍然维持在所述第一基站；如果是多次传输，则锚点仍然维持在所述第一基站。
  16. 根据权利要求1所述的锚点确定方法，其中，所述第一基站将所述第二锚点配置信息发送给所述第二基站包括：
    所述第一基站控制面实体将所述第二锚点配置信息通过所述第一基站和所述第二基站之间的接口发送给所述第二基站控制面实体。
  17. 根据权利要求16所述的锚点确定方法，其中，若锚点为所述第二基站，则所述第二锚点配置信息包括：
    第一基站分配的用户XnAP标识；
    第二基站分配的用户XnAP标识，且与第一锚点配置信息中第二基站提供的数值相同；
    接入和移动性管理功能AMF标识信息；
    用户上下文配置信息，包括：
    AMF给用户终端UE分配的NG接口标识；
    AMF的地址和端口，所述AMF的地址和端口包括AMF的IP地址，或者AMF的IP地址和端口号；
    UE安全能力，其中包括UE支持的NR加密算法列表，UE支持的NR完整性保护算法列表，UE支持的E-UTRA加密算法列表，UE支持的E-UTRA完整性保护算法列表，
    AS层安全配置，包括KNG-RAN*和NCC；
    UE最大聚合速率；
    PDU会话建立列表，每个PDU会话的配置包括：
    PDU会话标识；
    切片ID；
    UPF分配的上行和下行地址信息；
    用户面安全策略；
    E-RAB建立的列表；
    分组数据汇聚配置信息；
    无线链路控制RLC配置信息。
  18. 根据权利要求16所述的锚点确定方法，其中，若锚点为所述第一基站，所述第二锚点配置信息包括：
    第一基站分配的用户XnAP标识；
    第二基站分配的用户XnAP标识，与第一锚点配置信息中第二基站提供的数值相同；
    UE最大聚合速率；
    RLC配置信息，所述RLC配置信息包括RLC承载和逻辑信道的映射关系；
    PDU会话建立列表，每个PDU会话的配置包括：
    PDU会话标识；
    切片ID：S-NASSI；
    第一基站分配的上行地址信息，包括IP地址和端口地址；
    是否需要下行地址信息；
    E-RAB建立的列表；
    发送给终端的RRC消息。
  19. 根据权利要求1所述的锚点确定方法，其中，还包括：
    第二基站控制面实体收到第二锚点配置信息后，确定锚点的归属配置，并根据第二锚点配置信息配置协议栈相关参数和承载的相关参数；
    若锚点是第二基站，则缓存用户的RRC消息，在第一定时器超时后未收到任何上行用户数据的传输或者收到来自第二基站用户面实体的承载释放请求消息后，向终端发送缓存的RRC消息；
    若锚点是第一基站，则在配置完成相关的协议参数和承载参数后，按照第二锚点配置信息对于缓存的媒体访问控制服务数据单元进行RLC层处理，并根据第一基站分配的上行地址信息转发处理后的上行数据；
    若PDU会话列表中包含了至少一个会话需要配置下行地址，则第二基站触发一个接口地址指示信息给第一基站。
  20. 根据权利要求19所述的锚点确定方法，其中，接口地址指示信息包括：
    第一基站分配的用户XnAP标识；
    第二基站分配的用户XnAP标识，与第一锚点配置信息中第二基站提供的数值相同；
    PDU会话地址列表，其中每个PDU会话的配置包括：
    PDU会话标识；
    下行地址信息，包括IP地址和端口地址。
  21. 根据权利要求1所述的锚点确定方法，其中，还包括：
    如果第二基站控制面实体收到来自所述第一基站的认证失败消息，则生成RRCsetup消息，通过用户上下文释放消息发送给第二基站分离实体；
    所述第二基站分离实体收到后删除缓存的用户发送的媒体访问控制服务数据单元数据，将RRCsetup消息发送给所述终端；
    所述终端删除缓存中的数据，从连接态开始建立信令。
  22. 根据权利要求19所述的锚点确定方法，其中，还包括：
    如果第一基站控制面实体收到来自所述第一基站的接口地址指示信息后，则根据指示中的下行PDU会话地址信息，将来自核心网的数据通过第一基站和第二基站之间的用户面接口按照下行地址信息发送给第二基站控制面实体；
    所述第二基站将上行数据向PDU会话建立列表中的上行地址信息作为目的地址转发对应逻辑信道组的上行数据。
  23. 根据权利要求19所述的锚点确定方法，其中，还包括：
    如果锚点是所述第二基站，则所述第二基站控制面实体向核心网控制 面实体发送路径倒换请求消息，指示需要变更的业务承载的下行地址接收信息；
    所述第二基站控制面实体接收核心网控制面实体通过路径倒换响应消息发送的相关承载新的上行发送地址信息。
  24. 根据权利要求19所述的锚点确定方法，其中，还包括：
    第二基站控制面实体通过用户承载修改消息通知第二基站用户面实体，将发送到核心网的上行地址信息通知给第二基站用户面实体；
    第二基站用户面实体将配置结果通知给第二基站控制面实体。
  25. 根据权利要求19所述的锚点确定方法，其中，还包括：
    第二基站根据第二锚点配置信息，完成第二基站的协议栈和业务配置，并将第一RLC层配置信息通过与第二基站分离实体间的接口发送给第二基站分离实体。
  26. 根据权利要求25所述的锚点确定方法，其中，第一RLC层配置信息包括：
    第二基站控制面实体为用户在F1接口上分配的标识；
    第二基站分离实体为用户在F1接口上分配的标识别；
    RLC层的配置信息：包括逻辑信道组和RLC承载的映射关系，和协议栈参数；
    每个数据资源承载对应上行通道地址信息：包括IP地址和端口地址。
  27. 根据权利要求25所述的锚点确定方法，其中，还包括：
    第二基站分离实体收到第一RLC层配置信息后，完成相关协议栈参数和承载的配置，并给基于RLC层配置信息对于缓存的媒体访问控制服务数据单元进行数据，并将处理完的数据通过数据资源承载对应的上行通道地址信息发送给第二基站用户面实体。
  28. 根据权利要求1所述的锚点确定方法，其中，还包括：
    第二基站用户面实体在不激活定时器超时后，指示第二基站控制面实体用户处于非激活状态。
  29. 根据权利要求1所述的锚点确定方法，其中，还包括：
    第二基站控制面实体生产RRCRelease消息，其中RRCRelease消息中包含了Suspend配置信息以及哪些承载在发送数据时是否需要激活加密和/或完整性保护，第二基站控制面实体将该RRCRelease消息发送给终端，使得终端用户返回非活动状态。
  30. 一种锚点确定方法，包括：
    终端接收第一基站发送第一RRC释放信息，所述第一RRC释放信息包括数据资源承载与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和所述终端在非活动状态发送小数据包时所采用的用户面安全策略，以便所述终端在非活动状态发送小数据包时确定锚点基站。
  31. 根据权利要求30所述的锚点确定方法，其中，还包括：
    所述终端收到第一RRC释放信息后，保存终端用户的非活动上下文配置信息，包括更新KgNB和KRRCint，保存用户标识I-RNTI或者ShortI-RNTI，保存数据资源承载和逻辑信道的映射关系，保存逻辑信道和逻辑信道组的映射关系，若配置小数据传输的数据资源承载列表确定相应的数据资源承载可支持小数据包发送，则保存加密保持指示、加密算法、完整性保护保持指示、完整性保护算法，否则按照不包括任何加密和完整性保护配置信息，不允许在非活动状态发送小数据包。
  32. 根据权利要求31所述的锚点确定方法，其中，还包括：
    所述终端根据配置的小数据传输的数据资源承载上有数据要发送，触发发送RRCResumeRequest或者RRCResumeRequest1，根据保存的非活动上下文配置信息确定发送的上行数据的用户面安全策略；
    其中，
    若配置了加密保持指示信息，则所述终端的分组数据汇聚层对数据进行加密操作，根据是否配置了加密算法，确定是否变更加密算法；
    若配置了完整性保护保持指示信息，则所述终端的分组数据汇聚层对数据进行完整性保护操作，并且根据是否配置了完整性保护算法，确定是否变更完整性保护算法。
  33. 根据权利要求32所述的锚点确定方法，其中，还包括：
    所述终端在第二基站配置的上行资源中除了发送RRCResumeRequest或者RRCResumeRequest1，还携带填报了的缓冲状态报告和媒体访问控制服务数据单元信息，其中缓冲状态报告中携带的逻辑信道组标识为第一基站的配置信息，媒体访问控制服务数据单元的逻辑信道编号采用第一基站的配置。
  34. 一种锚点确定方法，包括：
    第二基站接收终端发送的RRCResumeRequest或者RRCResumeRequest1，还携带填报了的缓冲状态报告和媒体访问控制服务数据单元信息，其中缓冲状态报告中携带的逻辑信道组标识为第一基站的配置信息，媒体访问控制服务数据单元的逻辑信道编号采用第一基站的配置；
    所述第二基站缓存所述终端发送的数据，向所述第一基站发送第一锚点配置信息，所述第一锚点配置信息包括第二基站的安全能力和所述终端的业务特征，以便所述第一基站根据所述第一锚点配置信息确定锚点。
  35. 根据权利要求34所述的锚点确定方法，其中，还包括：
    所述第二基站接收所述第一基站发送的第二锚点配置信息；
    所述第二基站根据所述第二锚点配置信息生成发送给所述终端的RRC信息。
  36. 一种基站，包括：
    安全策略确定单元，用于根据周边基站的安全能力配置终端在非活动 状态发送小数据包时所采用的用户面安全策略；
    释放信息发送单元，用于向终端发送第一RRC释放信息，所述第一RRC释放信息包括数据资源承载与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、所述终端在非活动状态发送小数据包时所采用的用户面安全策略，以便所述终端在非活动状态发送小数据包时确定锚点基站。
  37. 一种终端，包括：
    释放信息接收单元，用于接收第一基站发送第一RRC释放信息，所述第一RRC释放信息包括数据资源承载与逻辑信道的映射关系、逻辑信道与逻辑信道组的映射关系、或/和所述终端在非活动状态发送小数据包时所采用的用户面安全策略，以便所述终端在非活动状态发送小数据包时确定锚点基站；
    释放信息存储单元，用于保存终端用户的非活动上下文配置信息，包括更新KgNB和KRRCint，保存用户标识I-RNTI或者ShortI-RNTI，保存数据资源承载和逻辑信道的映射关系，保存逻辑信道和逻辑信道组的映射关系，若配置小数据传输的数据资源承载列表确定相应的数据资源承载可支持小数据包发送，则保存加密保持指示、加密算法、完整性保护保持指示、完整性保护算法，否则按照不包括任何加密和完整性保护配置信息，不允许在非活动状态发送小数据包。
  38. 根据权利要求37所述的终端，其中，还包括：
    小数据发送单元，用于据配置的小数据传输的数据资源承载上有数据要发送，触发发送RRCResumeRequest或者RRCResumeRequest1，根据保存的非活动上下文配置信息确定发送的上行数据的用户面安全策略；
    其中，
    若配置了加密保持指示信息，则所述终端的分组数据汇聚层对数据进行加密操作，根据是否配置了加密算法，确定是否变更加密算法；
    若配置了完整性保护保持指示信息，则所述终端的分组数据汇聚层对数据进行完整性保护操作，并且根据是否配置了完整性保护算法，确定是否变更完整性保护算法。
  39. 一种基站，包括：
    恢复请求接收单元，用于接收终端发送的RRCResumeRequest或者RRCResumeRequest1，还携带填报了的缓冲状态报告和媒体访问控制服务数据单元信息，其中缓冲状态报告中携带的逻辑信道组ID为第一基站的配置信息，媒体访问控制服务数据单元的逻辑信道编号采用第一基站的配置；
    第一锚点信息发送单元，用于向所述第一基站发送第一锚点配置信息，所述第一锚点配置信息包括第二基站的安全能力和所述终端的业务特征，以便所述第一基站根据所述第一锚点配置信息确定锚点。
  40. 一种设备，包括：存储器、处理器及存储在所述存储器中并可在 所述处理器中运行的可执行指令，所述处理器执行所述可执行指令时实现如权利要求1-29任一项所述的锚点确定方法。
  41. 一种计算机可读存储介质，其上存储有计算机可执行指令，所述可执行指令被处理器执行时实现如权利要求1-29任一项所述的锚点确定方法。
PCT/CN2022/110231 2021-08-10 2022-08-04 锚点确定方法、基站、终端、设备及计算机可读存储介质 Ceased WO2023016331A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110915015.0A CN115706980A (zh) 2021-08-10 2021-08-10 锚点确定方法、基站、终端、设备及计算机可读存储介质
CN202110915015.0 2021-08-10

Publications (1)

Publication Number Publication Date
WO2023016331A1 true WO2023016331A1 (zh) 2023-02-16

Family

ID=85179548

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/110231 Ceased WO2023016331A1 (zh) 2021-08-10 2022-08-04 锚点确定方法、基站、终端、设备及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN115706980A (zh)
WO (1) WO2023016331A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118433739A (zh) * 2023-05-19 2024-08-02 中国电信股份有限公司北京研究院 用户面数据到达的通知方法及相关设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115996192B (zh) * 2023-03-14 2023-08-15 阿里巴巴（中国）有限公司 数据转发方法、车辆控制方法、专网设备及设备
CN117793941B (zh) * 2024-02-26 2024-06-18 深圳国人无线通信有限公司 随机接入场景中优化基站与终端通信连接的方法和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180270713A1 (en) * 2017-03-17 2018-09-20 Ofinno Technologies, Llc Cell Selection of Inactive State Wireless Device
WO2020191059A1 (en) * 2019-03-19 2020-09-24 Apple Inc. Signaling for inactive small data transmission without path switching
US20200314701A1 (en) * 2019-03-28 2020-10-01 Peyman TALEBI FARD Handover For Closed Access Group
WO2021067149A1 (en) * 2019-10-02 2021-04-08 Google Llc Systems and methods for managing radio bearer compatibility in a communication network

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110401918B (zh) * 2017-05-05 2021-07-20 华为技术有限公司 一种通信方法及设备
CN110636499B (zh) * 2018-06-22 2022-12-02 大唐移动通信设备有限公司 一种无线接入网通知区域更新方法、装置、终端及基站
AU2018437006A1 (en) * 2018-08-17 2020-09-24 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Information transmission method and apparatus, and communication device
WO2020154868A1 (zh) * 2019-01-28 2020-08-06 Oppo广东移动通信有限公司 一种参数配置方法及装置、网络设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180270713A1 (en) * 2017-03-17 2018-09-20 Ofinno Technologies, Llc Cell Selection of Inactive State Wireless Device
WO2020191059A1 (en) * 2019-03-19 2020-09-24 Apple Inc. Signaling for inactive small data transmission without path switching
US20200314701A1 (en) * 2019-03-28 2020-10-01 Peyman TALEBI FARD Handover For Closed Access Group
WO2021067149A1 (en) * 2019-10-02 2021-04-08 Google Llc Systems and methods for managing radio bearer compatibility in a communication network

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118433739A (zh) * 2023-05-19 2024-08-02 中国电信股份有限公司北京研究院 用户面数据到达的通知方法及相关设备

Also Published As

Publication number Publication date
CN115706980A (zh) 2023-02-17

Similar Documents

Publication Publication Date Title
US11510175B2 (en) Method and device for sending uplink data by an inactive terminal
US11490436B2 (en) User plane relocation techniques in wireless communication systems
US11658817B2 (en) Security key usage across handover that keeps the same wireless termination
US12464464B2 (en) Managing a ue preferred configuration
EP3017636B1 (en) User plane idle mode buffering within software defined network architecture
EP3322252B1 (en) Communication methods, network side device, and user equipment
WO2023016331A1 (zh) 锚点确定方法、基站、终端、设备及计算机可读存储介质
WO2018171703A1 (zh) 通信方法与设备
US11895617B2 (en) Message identification method and apparatus
CN106211244B (zh) 一种实现蜂窝网络重定位的方法和基站
CN103096294A (zh) 控制隧道标识分配的方法、装置和系统
CN106465435A (zh) 双连接重建
TWI657679B (zh) 處理系統間行動中的封包資料流的裝置及方法
US12225603B2 (en) Communication method and apparatus for reducing data transmission delay and reducing signaling overheads
US11039346B2 (en) Handover of a device which uses another device as relay
CN101686510B (zh) 切换过程中传递ue无线能力信息的方法和装置
CN105792292B (zh) 一种基站切换方法、系统及相关装置
EP4117338B1 (en) Data transmission with qfi mapping for multicast/broadcast service handover
EP2809109A1 (en) Wireless communication system, radio base station, radio terminal, and wireless communication method
WO2019019917A1 (zh) 一种通信方法及设备
CN105165103B (zh) 无线连接建立方法和装置
CN103079189A (zh) 控制隧道标识分配的方法、装置和系统
TW200939838A (en) Method and arrangement in a communication network
KR20230165287A (ko) Sdt를 사용한 srb 전송 방법 및 장치
CN119865859A (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: 22855314

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22855314

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 11/06/2024)

122 Ep: pct application non-entry in european phase

Ref document number: 22855314

Country of ref document: EP

Kind code of ref document: A1