WO2018143769A1 - Procédé et dispositif de commande de transmission de données, procédé et appareil de commande de continuité d'ue - Google Patents

Procédé et dispositif de commande de transmission de données, procédé et appareil de commande de continuité d'ue Download PDF

Info

Publication number
WO2018143769A1
WO2018143769A1 PCT/KR2018/001574 KR2018001574W WO2018143769A1 WO 2018143769 A1 WO2018143769 A1 WO 2018143769A1 KR 2018001574 W KR2018001574 W KR 2018001574W WO 2018143769 A1 WO2018143769 A1 WO 2018143769A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
information
node
key
radio access
Prior art date
Application number
PCT/KR2018/001574
Other languages
English (en)
Inventor
Xiaowan KE
Lixiang Xu
Hong Wang
Original Assignee
Samsung Electronics Co., 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
Priority claimed from CN201710067271.2A external-priority patent/CN108616944A/zh
Priority claimed from CN201710187207.8A external-priority patent/CN108924826B/zh
Application filed by Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Publication of WO2018143769A1 publication Critical patent/WO2018143769A1/fr

Links

Images

Classifications

    • 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/03—Protecting confidentiality, e.g. by encryption
    • H04W12/033—Protecting confidentiality, e.g. by encryption of the user plane, e.g. user's traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • the present disclosure relates to wireless communication technology, in particular to a method and a device for controlling data transmission, as well as a method and an apparatus for controlling continuity of user equipment.
  • the 5G or pre-5G communication system is also called a ‘Beyond 4G Network’ or a ‘Post LTE System’.
  • the 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates.
  • mmWave e.g., 60GHz bands
  • MIMO massive multiple-input multiple-output
  • FD-MIMO Full Dimensional MIMO
  • array antenna an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
  • RANs Cloud Radio Access Networks
  • D2D device-to-device
  • wireless backhaul moving network
  • cooperative communication Coordinated Multi-Points (CoMP), reception-end interference cancellation and the like.
  • CoMP Coordinated Multi-Points
  • Hybrid FSK and QAM Modulation FQAM
  • SWSC sliding window superposition coding
  • ACM advanced coding modulation
  • FBMC filter bank multi carrier
  • NOMA non-orthogonal multiple access
  • SCMA sparse code multiple access
  • Modern mobile communication is increasingly tending to provide users with multimedia services of high-speed transmission.
  • Fig. 1 is a system architecture schematic diagram of System Architecture Evolution (SAE), in which a user equipment (UE) 101 is a terminal device that supports a network protocol.
  • An Evolved-Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network that includes a base station (eNodeB/ NodeB) providing the UE with an interface for accessing to a wireless network.
  • a Mobility Management Entity (MME) 103 is responsible for managing mobile context, session context and security information of the UE.
  • MME Mobility Management Entity
  • a Service Gateway (SGW) 104 mainly provides functions of a user plane, and the MME 103 and the SGW 104 may be in the same physical entity.
  • a Packet Data Network Gateway (PGW) 105 is responsible for charging, legal monitoring and other functions, and the PGW 105 and the SGW 104 may be in the same physical entity.
  • a policy and charging rule functional entity (PCRF) 106 provide a Quality of Service (QoS) policy and a charging criterion.
  • a general packet radio service support node (SGSN) 108 is a network node device that provides routing for data transmission in a Universal Mobile Telecommunications System (UMTS).
  • a Home Subscriber Server (HSS) 109 is a home subsystem of the UE, and is responsible for protecting user information including a current location of the UE, an address of a serving node, user security information, and packet data context of the UE.
  • Fig. 2 is a schematic diagram of a next generation network (5G) initial system architecture, in which a next generation (NextGen) UE, a next generation access network or a next generation radio access network (Next Gen (R)AN), a next generation core network (NextGen Core) and a data network are included.
  • a control plane interface between the Next Gen (R)AN and the NextGen Core is NG2
  • a user plane interface between the Next Gen (R)AN and the NextGen Core is NG3. Names of these interfaces are only temporarily named, and main content of the present disclosure may not be affected if the 3GPP finally decides to use other names.
  • the NextGen Core further includes a user plane functional entity and a control plane functional entity.
  • Embodiments of the present disclosure provide a method of controlling data transmission, and a device for performing the corresponding method.
  • a method of controlling a data transmission state comprising:
  • the information on the UE data comprises at least one of: data information associated with the UE data, security information associated with the UE data, session information associated with a UE data-related session, bearer information associated with a UE data-related bearer, quality of service ‘QoS’ flow information associated with a UE data-related QoS flow, routing information associated with a UE data-related data channel, and information on a UE data-related operation; and/or the UE context comprises at least one of: security information associated with the UE, updated security information associated with the UE, and security information associated with the UE before being updated.
  • the data information associated with the UE data comprises at least one of: a size of the UE data, a data direction of the UE data, a data plane of the UE data, whether the UE data is the first UE data packet, whether there is any subsequent UE data, a UE data packet number, a type of a UE data packet, a transmission type of the UE data, a protocol layer of a UE data packet, and a state of the UE data; and/or the security information associated with the UE data comprises at least one of: whether the UE data is encrypted, whether the UE data is integrity protected, key information associated with the UE data, security algorithm information associated with the UE data, and whether there is a security information indication data packet; and/or the UE data-related session is a UE session to which the UE data belong, and the session information associated with the UE data-related session comprises at least one of: a session identity, a session default QoS, a related QoS flow, bearer
  • the UE data-related data channel is a data channel for transmitting or receiving the UE data
  • the routing information of the UE data-related data channel comprises at least one of: uplink routing information, downlink routing information, an uplink transport layer address, an uplink channel identity, a downlink transport layer address, and a downlink channel identity.
  • the type of the data packet comprises at least one of: a signaling data packet, a user data packet, a NAS data packet, a security information indication packet, a reception acknowledgment packet, and a transmission acknowledgment packet; and/or the transmission type of the UE data comprises at least one of: a reception acknowledgment being required, a reception acknowledgment not being required, a transmission acknowledgment being required, and a transmission acknowledgment not being required; and/or the state of the UE data comprises at least one of: a successful reception acknowledgment, and a successful transmission acknowledgment.
  • a first node is an old radio access network node
  • the UE data is transmitted to the UE by paging, and the UE returns a successful reception acknowledgment to the first node
  • the decryption request information comprises information associated with at least one of: decrypting with the old key, decrypting with the new key, a number of the key used for decryption, decrypting with the old security algorithm, decrypting with the new security algorithm, and a security algorithm used for decryption
  • the encryption request information comprises information associated with at least one of: encryption with the old key, encrypting with the new key, a number of the key used for encryption, encrypting with the old security algorithm, encrypting with the new security algorithm, and a security algorithm used for encryption
  • the integrity protection request information comprises information on at least one of: performing integrity protection with the old key, performing integrity protection with the new key, a number of the key used for integrity protection, performing integrity protection with the old security algorithm, performing integrity protection with
  • control for transmission of the UE data comprises at least one of: a resource occupation determination operation, a decryption operation, an integrity protection check operation, a data transmission operation, an encryption operation, an integrity protection operation, a paging control operation, and a resource occupation operation.
  • the resource occupation is performed or which of the UEs to occupy the resource is determined according to at least one of: the size of the UE data, the bearer information associated with the UE data-related bearer, the session information associated with the UE data-related session, the QoS flow information associated with the UE data-related QoS flow; and/or the decryption operation or the integrity protection check operation is performed according to at least one of: the UE data-related key information, the UE data-related security algorithm information, the indication data packet, whether the UE data is the first UE data packet, the UE data packet number, the old key, the new key, the data direction of the UE data, the bearer information associated with the UE data-related bearer, the session information associated with the UE data-related session, the QoS flow information associated with the UE data-related QoS flow, and the UE data-related operation information; and/or the data transmission control comprises at least one of: requesting to allocate an uplink data forwarding address, al
  • the method is performed at at least one of:
  • a radio access network node a core network node, a data termination point, a UE, a non-access stratum of the UE, an access stratum of the UE, an application layer of the UE, a centralized unit ‘CU’, a distributed unit ‘DU’, a core network user plane node, a core network control plane node, a source radio access network node in a movement process of the UE, a target radio access network node in a movement process of the UE, a radio access network node, other than a radio access network node which saves UE information, accessed by the UE in a light connection mode or an inactive state, the radio access network node which saves UE information and is accessed by the UE in the light connection mode or the inactive state, a radio access network node that suspends the UE, and a radio access network node the UE requests to resume a connection.
  • the method further comprises: transmitting the information on the UE data and/or the UE context, wherein the information on the UE data and/or the UE context is transmitted to at least one of: a radio access network node, a core network node, a data termination point, a UE, a non-access stratum of the UE, an access stratum of the UE, an application layer of the UE, a centralized unit ‘CU’, a distributed unit ‘DU’, a core network user plane node, a core network control plane node, a source radio access network node in a movement process of the UE, a target radio access network node in a movement process of the UE, a radio access network node, other than a radio access network node which saves UE information, accessed by the UE in a light connection mode or an inactive state, the radio access network node which saves UE information and is accessed by the UE in the light connection mode or the inactive state, a radio access network node which save
  • a method of controlling data transmission comprising: determining whether a predetermined condition is satisfied; and transmitting information on user equipment ‘UE’ data and/or a UE context, when it is determined that the predetermined condition is satisfied.
  • the predetermined condition at least comprises: transmitting the UE data in an inactive state.
  • the information on the UE data comprises at least one of: data information associated with the UE data, security information associated with the UE data, session information associated with a UE data-related session, bearer information associated with a UE data-related bearer, quality of service ‘QoS’ flow information associated with a UE data-related QoS flow, routing information associated with a UE data-related data channel, and information on a UE data-related operation; and/or the UE context comprises at least one of: security information associated with the UE, updated security information associated with the UE, and security information associated with the UE before being updated.
  • the data information associated with the UE data comprises at least one of: a size of the UE data, a data direction of the UE data, a data plane of the UE data, whether the UE data is the first UE data packet, whether there is any subsequent UE data, a UE data packet number, a type of a UE data packet, a transmission type of the UE data, a protocol layer of a UE data packet, and a state of the UE data; and/or the security information associated with the UE data comprises at least one of: whether the UE data is encrypted, whether the UE data is integrity protected, key information associated with the UE data, security algorithm information associated with the UE data, and whether there is a security information indication data packet; and/or the UE data-related session is a UE session to which the UE data belong, and the session information associated with the UE data-related session comprises at least one of: a session identity, a session default QoS, a related QoS flow, bearer
  • a device comprising: a communication interface, configured for communication;
  • a processor and a memory storing computer executable instructions, which when executed by the processor, cause the processor to: obtain information on user equipment ‘UE’ data and/or a UE context; and perform control for transmission of the UE data, according to the obtained information on the UE data and/or UE context.
  • UE user equipment
  • a device comprising: a communication interface, configured for communication; a processor; and a memory storing computer executable instructions, which when executed by the processor, cause the processor to: determine whether a predetermined condition is satisfied; and transmit information on user equipment ‘UE’ data and/or a UE context, when it is determined that the predetermined condition is satisfied.
  • UE user equipment
  • a method for controlling continuity of UE includes: learning, by a first node, at least one kind of continuity control information corresponding to the UE; and performing, by the first node according to the continuity control information, corresponding continuity control to the UE.
  • the continuity control information includes at least one of the following: service continuity mode information, keeping service continuity range information, data endpoint serving range information, service-permitted range information, service-prohibited range information, area information of an access-permitted area, area information of an access-prohibited area, information of an access-permitted network slice, area information of an area supported by a target node or a target cell, indication information about whether handover is performed, indication information about whether handover is prepared, release indication information, indication information about whether data is forwarded, indication information about whether an interoperable operation between networks is performed, indication information about whether a data endpoint is changed, indication information about whether a network slice is changed, indication information about whether there are multiple data endpoints, UE identifier information, session information, bearer information, QoS flow information, and service data flow information.
  • the operation of the performing, by the first node, corresponding continuity control to the UE includes at least one of: performing, by the first node, corresponding handover control to the UE; performing, by the first node, corresponding release control to the UE; performing, by the first node, corresponding data forwarding control to the UE; performing, by the first node, corresponding interoperable-operation-between-networks control to the UE; performing, by the first node, corresponding network slice changing or mapping control to the UE; and performing, by the first node, corresponding continuity operation information configuration to the UE.
  • an apparatus for controlling continuity of UE includes: n information receiving module, configured to receive, through a first node, at least one kind of continuity control information corresponding to the UE; and a control module, configured to perform, through the first node and based on the continuity control information, corresponding continuity control to the UE.
  • functions of decryption and encryption, integrity protection and integrity protection check, paging, determining the channel for data transmission, mapping the QoS flow etc. for transmission of small data in the inactive state may be achieved by cooperation between the UE, the new radio access network node, the old radio access network node, so as to support the data transmission in the inactive state.
  • the network may not allocate dedicated resource for the UE, which saves signaling and resource for establishing a dedicated channel.
  • various embodiments of the present disclosure propose a method for controlling continuity of the UE.
  • the first node may differentially implement continuity control to the UE according to different information corresponding to the UE, so as to save signaling overhead and reduce the delay for the UE accessing a network.
  • a UE moving process on the one hand, unnecessary resource allocation and data forwarding is reduced, and thus the handover process is accelerated; on the other hand, unnecessary interoperable operations between systems are reduced, so that the UE may access a new network system quickly; moreover, when the target cell does not support the current network slice, a service of the UE may be mapped to a network slice supported by the target cell according to a service type of the UE, and thereby the UE is served at full steam and serving experience of the UE is improved.
  • Fig. 1 is a schematic diagram of a system architecture evolution (SAE) system architecture
  • Fig. 2 is a schematic diagram of the next generation network (5G) initial system architecture
  • Fig. 3 is a schematic flowchart of a method of controlling data transmission according to a first exemplary embodiment of the present disclosure
  • Fig. 4 is a schematic flowchart of a method of controlling data transmission according to a second exemplary embodiment of the present disclosure
  • Fig. 5 is a schematic structure diagram of a device according to a first and a second exemplary embodiments of the present disclosure
  • Fig. 6 is a first schematic signal flow diagram between network entities to which a method according to an exemplary embodiment of the present disclosure is applied;
  • Fig. 7 is a second schematic signal flow diagram between network entities to which a method according to an exemplary embodiment of the present disclosure is applied;
  • Fig. 8 is a third schematic signal flow diagram between network entities to which a method according to an exemplary embodiment of the present disclosure is applied;
  • Fig. 9 is a fourth schematic signal flow diagram between network entities to which a method according to an exemplary embodiment of the present disclosure is applied.
  • Fig. 10 is a schematic flowchart of a method for controlling continuity of user equipment, according to an embodiment of the present disclosure
  • Fig. 11 is a schematic flowchart of a method for controlling continuity of user equipment, according to a first embodiment of the present disclosure
  • Fig. 12 is a schematic flowchart of a method for controlling continuity of user equipment, according to a second embodiment of the present disclosure
  • Fig. 13 is a schematic flowchart of a method for controlling continuity of user equipment, according to a third embodiment of the present disclosure
  • Fig. 14 is a schematic flowchart of a method for controlling continuity of user equipment, according to a fourth embodiment of the present disclosure.
  • Fig. 15 is a schematic flowchart of a method for controlling continuity of user equipment, according to a fifth embodiment of the present disclosure.
  • Fig. 16 is a schematic flowchart of a method for controlling continuity of user equipment, according to a sixth embodiment of the present disclosure.
  • Fig. 17 is a schematic diagram illustrating architecture of an apparatus for controlling continuity of user equipment, according to an embodiment of the present disclosure.
  • the inactive or light connection means that when a radio access network releases a UE related connection, the radio access network does not request a core network to release the UE related connection, such as a UE related connection between a base station and a core network control plane (a S1 interface control plane or a NG2 Interface), a UE related connection between a base station and a core network user plane (a S1 interface user plane or a NG3 interface).
  • a core network control plane a S1 interface control plane or a NG2 Interface
  • a UE related connection between a base station and a core network user plane a S1 interface user plane or a NG3 interface
  • the radio access network when the UE is in the inactive state, the radio access network still maintains context of the UE, and the core network may consider that the UE is still In the connected state.
  • the UE may transmit the data in two approaches: Approach 1, transmitting the uplink data directly in the inactive state, e.g., by grant free resource; and Approach 2: transmitting the uplink data after returning to the connected state.
  • Approach 1 transmitting the uplink data directly in the inactive state, e.g., by grant free resource
  • Approach 2 transmitting the uplink data after returning to the connected state.
  • a certain signaling overhead is required when the UE returns to the connected state from the inactive state. In a case of smaller data amount, the signaling may be saved using Approach 1.
  • the data packet of the UE is transmitted in the first Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • a radio access network node referred to as a new radio access network node below
  • the UE accesses is not a radio access network node that saves the UE context (referred to as the old radio access network node below)
  • the UE data is packaged by the old key.
  • the new radio access network node obtains the UE context from the old radio access network node, it is a new key that the old radio access network transmits to the new radio access network node, and thus the new radio access network node cannot decrypt the first data of the UE.
  • the radio access network node For uplink data, the radio access network node needs to transmit the uplink data to the core network after receiving the uplink data. Since common resource is used for data transmission in the inactive state, it is not possible to determine data channel information associated with the UE data. If the UE accesses from the new radio access network node, the new radio access network node transmits the data packet to the old radio access network node, and the old radio access network node does not know which of uplink channels for the UE between the radio access network and the core network is corresponding to the UE data.
  • the new radio access network node may need to transmit the data to the old radio access network node.
  • the UE For downlink data, the UE needs to transmit the downlink data to the application layer after receiving the downlink data. There is a mapping between the data flow of the application layer and the QoS flow. Since common resource is used for data transmission in the inactive state, it is not possible to determine the UE data-related QoS flow information, and the data cannot be transmitted to the application layer of the UE.
  • the radio access network node For the downlink data, if the radio access network node receives UE data of different UEs from other radio access network nodes and requests to transmit by paging, the radio access network node does not know how to determine priorities of respective related pagings.
  • the radio access network node may be a base station, an eNB, a NodeB, a radio access network central control unit, a radio access network node distributed unit, and the like.
  • the concept of nodes may be virtualized into functions or units.
  • the radio access network central control unit may connect a plurality of radio access network node distributed units.
  • the core network node may be a Mobility Management Entity (MME), a SGSN, an SGW, a Common Control Network Function (CCNF), an Access and Mobility Function (AMF), a Session Management Function (SMF), a core network control node (e.g., MME, CCNF, AMF), a core network user plane node (e.g., SMF, UDF), a core network control plane function, a core network user plane function, a core network control plane unit, or a core network user plane unit, etc.
  • MME Mobility Management Entity
  • CCNF Common Control Network Function
  • AMF Access and Mobility Function
  • SMF Session Management Function
  • MME Mobility Management Entity
  • CCNF Common Control Network Function
  • AMF Access and Mobility Function
  • SMF Session Management Function
  • a core network control node e.g., MME, CCNF, AMF
  • a core network user plane node e.g., SMF, UDF
  • the core network control node may be at least one of the following: an MME (Mobility Management entity), an SGSN, a core network control plane function, a core network control plane unit, a CCNF (Common Control Network Function), an AMF (Access and mobility function, an SMF (Session management function) and so on.
  • MME Mobility Management entity
  • SGSN Session Management entity
  • core network control plane function e.g., a core network control plane unit
  • CCNF Common Control Network Function
  • AMF Access and mobility function
  • SMF Session management function
  • the core network user plane node may be at least one of the following: a SGW, a SGSN, a core network user plane function (UPF), a core network user plane unit, a network slice and so on.
  • a UE information management node may be at least one of HSS and UDM.
  • a user plane data endpoint may be at least one of: PGW, UPF, and TUPF.
  • a user plane data endpoint of a UE session may be a user plane data endpoint selected when the UE session is set up.
  • a UE session may also be called as a session, a PDU session, or the like.
  • a network slice may also be referred to as a dedicated network, and an identifier of the network slice may also be referred to as a dedicated network identifier, and a service type supported by the network slice may also be referred to as a service type supported by the dedicated network.
  • the light connection may also be embodied as a radio access network triggering a paging function.
  • whether a UE may perform a light connection or not may be embodied as whether the UE is suitable for a light connection.
  • the connected state of the UE may be embodied as a connected mode of the UE, and the light connection state is embodied as a light connection mode.
  • the light connection also represents an inactive mode, or an inactive connection or disconnection between the UE and the radio access network, but in which the radio access network still maintains a UE related connection between the radio access network node and the core network node.
  • the radio access network node to which the UE has a light connection refers to a radio access network node which maintains a UE related connection between the radio access network node and the core network node when the UE is in a light connection.
  • the data mentioned herein may include control plane data (such as NAS signaling, TAU Request, Service Request, user plane data transmitted via data packets in the control plane), or user plane data.
  • the data packets mentioned herein may refer to data transmitted in a form of packets. Unless otherwise indicated, the term “data packet” herein may be used interchangeably with “data”.
  • An indication of whether there is data transmission may be divided into an indication of whether there is an uplink control plane data transmission requirement, an indication of whether there is an uplink user plane data transmission requirement.
  • the indication of whether there is data transmission may also be divided into an indication of whether there is an uplink data transmission requirement, an indication of whether there is a downlink data transmission requirement.
  • the paging area used herein may be a paging area configured by the radio access network node to the UE in the light connection.
  • a paging from the lightly connected radio access network node may reach the UE.
  • the paging from the lightly connected radio access network node may be forwarded through other radio access network node(s).
  • the old radio access network node may be a radio access network node which saves information of the UE, e.g., a radio access network node which saves the UE information in the light connection or inactive state.
  • the new radio access network node may be a radio access network node other than the old radio access network node.
  • node used herein may be an abbreviation of “node unit”.
  • exemplary embodiments of the present disclosure propose methods of controlling data transmission, which are shown in Figs. 3 and 4 respectively.
  • Fig. 3 is a schematic flowchart of the method of controlling the data transmission according to the first exemplary embodiment of the present disclosure.
  • the method 300 may comprise: Step 301 of obtaining information on UE data and/or a UE context; and Step 302 of performing control for transmission of the UE data, according to the obtained information on the UE data and/or UE context.
  • the control for the transmission of the UE data in Step 302 may be different depending on the node which performs the method. For example,
  • the control for the transmission of the UE data in Step 302 may be embodied as control of the UE data performed by the data receiving party.
  • the UE data may be the UE data being received, the received UE data or the UE data that need to be received but have not received yet;
  • the control for the transmission of the UE data in Step 302 may be embodied as control of the UE data performed by the data transmitting party.
  • the UE data may be the UE data being transmitted, the transmitted UE data or the UE data that need to be transmitted but have not transmitted yet.
  • a first node obtains the information on the UE data and/or the UE context.
  • the obtaining operation may include at least one of: the first node obtaining by receiving from another node, the first node obtaining according to information stored by itself, the first node obtaining by Operation Administration and Maintenance (OAM) configuration, but is not limited to this.
  • OAM Operation Administration and Maintenance
  • the information on the UE data may include at least one of: data information associated with the UE data, security information associated with the UE data, session information associated with a UE data-related session, bearer information associated with a UE data-related bearer, QoS flow information associated with a UE data-related QoS flow, routing information associated with a UE data-related data channel, and information on a UE data-related operation.
  • the information on the UE data is information on the UE data being transmitted or received, information on the UE data to be transmitted or received subsequently, or information on the UE data which have been transmitted or received.
  • the data information associated with the UE data may include at least one of: a size of the UE data (e.g., occupied bits, which may be used for determining how many resources are occupied), a data direction of the UE data (e.g., uplink, downlink), a data plane of the UE data (e.g., a control plane data, a user plane data), whether the UE data is the first UE data packet, whether there is any subsequent UE data, a UE data packet number (e.g., a Packet Data Convergence Protocol (PDCP) number), a type of a UE data packet, a transmission type of the UE data, a protocol layer of a UE data packet (e.g., a PDCP packet, a Radio Link Control (RLC) packet, a Media Access Control (MAC) packet), and a state of the UE data.
  • a size of the UE data e.g., occupied bits, which may be used for determining how many resources
  • the data direction, the data plane, the data packet number may be used as input to a security algorithm (e.g., the integrity protection algorithm, the encryption algorithm, the decryption algorithm).
  • a security algorithm e.g., the integrity protection algorithm, the encryption algorithm, the decryption algorithm.
  • Whether the UE data is the first UE data packet may be used to determine whether to use the old key or the new key. Whether there is any subsequent UE data may be used to determine whether it is necessary to allocate a data forwarding addresses to improve data reception efficiency.
  • the type of the UE data packet the transmission type of the UE data, the protocol layer of the UE data packet may be used to determine to return an acknowledgment.
  • the type of the UE data packet may include at least one of: a signaling data packet, a user data packet, a NAS layer data packet, a security information indication packet (e.g., a data packet that may be used to separate an old key encrypted packet from a new key encrypted data packet), a reception acknowledgement packet (an acknowledgement for receiving data, indicating that the transmitting party transmits successfully), and a transmission acknowledgment packet (an acknowledgement for indicating that the received data is successfully transmitted to the next node).
  • a signaling data packet e.g., a data packet that may be used to separate an old key encrypted packet from a new key encrypted data packet
  • a reception acknowledgement packet an acknowledgement for receiving data, indicating that the transmitting party transmits successfully
  • a transmission acknowledgment packet an acknowledgement for indicating that the received data is successfully transmitted to the next node.
  • the transmission type of the UE data may include at least one of: a reception acknowledgment being required (e.g. AM), a reception acknowledgment not being required (e.g., TM, UM), AM, TM, UM, a transmission acknowledgment being required, and a transmission acknowledgment not being required.
  • a reception acknowledgment being required e.g. AM
  • a reception acknowledgment not being required e.g., TM, UM
  • AM TM, UM
  • AM TM, UM
  • a transmission acknowledgment being required e.g., TM, UM
  • the type of the reception acknowledgment being required is necessary to return a reception acknowledgement packet after successful reception of the UE data.
  • the type of the transmission acknowledgment being required is necessary to return a transmission acknowledgement packet after the UE data are received and successfully transmitted to other node(s).
  • the state of the UE data may include at least one of: a successful reception acknowledgment, and a successful transmission acknowledgment.
  • the first node is an old radio access network node, the UE data is transmitted to the UE by paging, and the UE returns the successful reception acknowledgment to the first node.
  • the first node is a new radio access network node, and the successful reception acknowledgment or the successful transmission acknowledgment is received from the old radio access network node after the new radio access network node transmits the UE data to the old radio access network node.
  • the security information associated with the UE data may include at least one of: whether the UE data is encrypted (which may also be embodied as whether the UE data needs to be decrypted, whether the UE data are requested to be decrypted), whether the UE data is integrity protected (which may also be embodied as whether the UE data needs integrity protection check, whether the UE data requests integrity protection check), key information associated with the UE data, security algorithm information associated with the UE data, and whether there is a security information indication data packet.
  • the old key may be a key that is saved in the UE context.
  • the new key may be after the UE re-accesses the network or accesses a new radio access network node.
  • the security algorithm information associated with the UE data may include at least one of: a used encryption algorithm (e.g., EPS Encryption Algorithm (EEA), a used decryption algorithm, a used integrity protection algorithm (e.g. EPS Integrity Algorithm (EIA), EIA1, EIA2, EIA3), a used integrity protection check algorithm.
  • a used encryption algorithm e.g., EPS Encryption Algorithm (EEA)
  • EIA EPS Integrity Algorithm
  • EIA1 EIA2, EIA3 e.g. EPS Integrity Algorithm
  • EIA3 EPS Integrity Algorithm
  • the UE data-related session may be a UE session to which the UE data belong, wherein the session information may include at least one of: a session identity, a session default QoS, a related QoS flow, bearer information associated with a session-related bearer, and routing information associated with a session-related data channel.
  • the session information may include at least one of: a session identity, a session default QoS, a related QoS flow, bearer information associated with a session-related bearer, and routing information associated with a session-related data channel.
  • Content included in the session information of the UE data-related session is as described in the above session information.
  • the UE data-related bearer may be a UE bearer to which the UE data belong, wherein the bearer information associated with the UE data-related bearer may include at least one of: a bearer identity (e.g., a Data Radio Bearer (DRB), a logical channel ID, a Evolved-Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) ID), a bearer-related session identity, QoS information of the bearer, Address Resolution Protocol (ARP), routing information of a bearer-related data channel.
  • a bearer identity e.g., a Data Radio Bearer (DRB), a logical channel ID, a Evolved-Universal Terrestrial Radio Access Network (E-UTRAN) Radio Access Bearer (E-RAB) ID
  • E-RAB Evolved-Universal Terrestrial Radio Access Network
  • ARP Address Resolution Protocol
  • the UE data-related QoS flow may be a QoS flow to which the UE data belong, wherein the QoS flow information associated with the UE data-related QoS flow may include at least one of: a QoS flow information indication, a QoS flow information identity, a QoS flow type (Type A, Type B), QoS information of the QoS flow, ARP, and routing information associated with a QoS flow related data channel.
  • Content included in the QoS flow information of the UE data-related QoS flow is as described in the above QoS flow information.
  • the UE data-related data channel may be a data channel of transmitting or receiving the UE data.
  • the routing information of the data channel may include at least one of: uplink routing information, downlink routing information, an uplink transport layer address (e.g. an IP address), an uplink channel identity (e.g., TEID), a downlink transport layer address (e.g. an IP address), a downlink channel identity (e.g., TEID).
  • the information on the UE data-related operation may include at least one of: decryption request information, encryption request information, key update request information, key update complete notification information, integrity protection request information, integrity protection check request information, data transmission request information, requesting for determining a data transmission channel, and requesting for determining a QoS flow.
  • the decryption request information may include information on at least one of: decrypting with the old key, decrypting with the new key, a number of the key used for decryption, decrypting with the old security algorithm (e.g., decrypting with a security algorithm for which the old radio access network node has a priority), decrypting with the new security algorithm (e.g., decrypting with a security algorithm for which the new radio access network node has a priority), and a security algorithm used for decryption.
  • decrypting with the old key e.g., decrypting with a security algorithm for which the old radio access network node has a priority
  • decrypting with the new security algorithm e.g., decrypting with a security algorithm for which the new radio access network node has a priority
  • a security algorithm used for decryption e.g., decrypting with a security algorithm for which the new radio access network node has a priority
  • the encryption request information may include information on at least one of: encryption with the old key, encrypting with the new key, a number of the key used for encryption, encrypting with the old security algorithm (e.g., encrypting with a security algorithm for which the old radio access network node has a priority), encrypting with the new security algorithm (e.g., encrypting with a security algorithm for which the new radio access network node has a priority), and a security algorithm used for encryption; and/or
  • the integrity protection request information may include information on at least one of: performing integrity protection with the old key, performing integrity protection with the new key, a number of the key used for integrity protection, performing integrity protection with the old security algorithm (e.g., performing integrity protection with a security algorithm for which the old radio access network node has a priority), performing integrity protection with the new security algorithm (e.g., performing integrity protection with a security algorithm for which the new radio access network node has a priority), and a security algorithm used for integrity protection.
  • performing integrity protection with the old key e.g., performing integrity protection with a security algorithm for which the old radio access network node has a priority
  • performing integrity protection with the new security algorithm e.g., performing integrity protection with a security algorithm for which the new radio access network node has a priority
  • a security algorithm used for integrity protection e.g., performing integrity protection with a security algorithm for which the new radio access network node has a priority
  • the integrity protection check request information may include information on at least one of: performing integrity protection check with the old key, performing integrity protection check with the new key, a number of the key used for integrity protection check, performing integrity protection check with the old security algorithm (e.g., performing integrity protection check with a security algorithm for which the new radio access network node has a priority), performing integrity protection check with the new security algorithm (e.g., performing integrity protection check with a security algorithm for which the new radio access network node has a priority), and a security algorithm used for integrity protection check; and/or
  • the data transmission request information may include information on at least one of: whether the UE data needs a reception acknowledgement, whether the UE data needs to be transmitted after the UE data are received, whether the UE data need a transmission acknowledgement, transmitting the received data to a core network, transmitting the received data to the UE, requesting to determine the UE data-related data transmission channel for transmission, requesting to determine and transmit the UE data-related QoS flow.
  • the reception acknowledgment is a reception acknowledgment for the UE data, and may be achieved by returning a reception acknowledgment packet and a UE data packet number. It may be considered that the UE data packet corresponding to the reception acknowledgment packet number is successfully received.
  • the old radio access network node receives the UE data which needs a reception acknowledgment from the new radio access network node, and may return to the new radio access network node a reception acknowledgment data packet and a UE data packet number.
  • the UE may return to the access network to perform a paging response.
  • the first data packet transmitted by the UE after the UE accesses the network may be a reception acknowledgment data packet and/or a serial number of the UE data packet transmitted in the paging.
  • the UE context may include at least one of: security information associated with the UE, new security information associated with the UE, and old security information associated with the UE.
  • the new security information associated with the UE may refer to updated security information associated with the UE.
  • the old security information associated with the UE may refer to security information associated with the UE before being updated.
  • the UE needs to update its security context.
  • the security information associated with the UE may include at least one of: a key, an access stratum key (e.g., a key of a radio access network, such as KgNB, KeNB), a key next hop ‘NH’ parameter, a NH chaining count (NCC), a key number (e.g., NCC), a non-access stratum (NAS) count, an encrypted key, encryption algorithm information, an integrity protection key, integrity protection algorithm information (e.g., Kint, integrity protection algorithms preferentially adopted by different nodes being possible to be different), a security information indication.
  • an access stratum key e.g., a key of a radio access network, such as KgNB, KeNB
  • NH NH chaining count
  • NCC key number
  • NAS non-access stratum
  • NH may be used as an input for calculating a next key.
  • the security information indication may be used for indicating one of: the security information associated with the UE being indicated to be newly generated security information, the security information associated with the UE being indicated to be previously saved security information, and the security information associated with the UE being indicated to be security information currently used by the UE.
  • the new security information associated with the UE may include at least one of: a new key, a new access stratum key (e.g., a key of a radio access network, such as KgNB, KeNB), a new encryption key, a new security protection key, a new encryption algorithm, a new security protection algorithm, information necessary to generate the new key (e.g., NCC or NH), a security information update request indication (which may indicate a request update), a security information update complete indication (which may indicate update completed), and a new key indication.
  • a new access stratum key e.g., a key of a radio access network, such as KgNB, KeNB
  • a new encryption key e.g., a new security protection key
  • a new encryption algorithm e.g., a new encryption algorithm
  • a new security protection algorithm e.g., information necessary to generate the new key
  • information necessary to generate the new key e.g., NCC or NH
  • the old security information associated with the UE may include at least one of : an old key, an old access stratum key (e.g., a key of a radio access network, such as KgNB, KeNB), an old encryption key, an old security protection key, an old encryption algorithm, an old security protection algorithm, and an old key indication.
  • an old key e.g., a key of a radio access network, such as KgNB, KeNB
  • an old encryption key e.g., a key of a radio access network, such as KgNB, KeNB
  • an old encryption key e.g., an old security protection key
  • an old encryption algorithm e.g., an old encryption algorithm
  • an old security protection algorithm e.g., an old key indication.
  • the first node may be at least one of: a radio access network node, a core network node, a data termination point, a UE, a non-access stratum of the UE, an access stratum of the UE, an application layer of the UE, a centralized unit (CU), a distributed unit (DU), a core network user plane node, a core network control plane node, a source radio access network node in a movement process of the UE, a target radio access network node in a movement process of the UE, a new radio access network node the UE accesses in the light connection mode or the inactive state, an old radio access network node which saves the context of the UE in the light connection mode or the inactive state, a radio access network node that suspends the UE, and a radio access network node the UE requests to resume a connection.
  • a radio access network node a core network node, a data termination point, a UE, a non-access stratum of
  • the first node may obtain the information on the UE data and/or the UE context from at least one of: a radio access network node, a core network node, a data termination point, a UE, a non-access stratum of the UE, an access stratum of the UE, an application layer of the UE, a CU, a DU, a core network user plane node, a core network control plane node, a source radio access network node in a movement process of the UE, a target radio access network node in a movement process of the UE, a new radio access network node the UE accesses in the light connection mode or the inactive state, an old radio access network node which saves the context of the UE in the light connection mode or the inactive state, a radio access network node that suspends the UE, and a radio access network node the UE requests to resume a connection.
  • a radio access network node a core network node, a data termination point, a
  • Step 302 the first node performs control for transmission of the UE data, according to the obtained information on the UE data and/or UE context.
  • the control for transmission of the UE data may include at least one of: a resource occupation determination operation, a decryption operation, an integrity protection check operation, a data transmission operation, an encryption operation, an integrity protection operation, a paging control operation, and a resource occupation operation, e.g., determining whether the resource occupation is successful, performing an decryption operation on the received UE data, performing an integrity protection check on the received UE data, performing data transmission control on the received UE data, performing an encryption operation on the UE data to be transmitted, performing an integrity protection operation on the UE data to be transmitted, performing a resource occupation attempt operation, performing a paging control operation on the transmitted UE data.
  • the first node may be used as the data receiving party or the data transmitting party.
  • the first node is used as the receiving party of the UE data.
  • the control for the UE data may include at least one of: a resource allocation operation, a decryption operation, an integrity protection check operation, a data transmission operation.
  • the first node may perform the resource occupation or determine which of the UEs occupy (also referred to as “allocate”) the resource according to at least one of the information on the UE data and/or the UE context, e.g., the size of the UE data, the bearer information associated with the UE data-related bearer, the session information associated with the UE data-related session, the QoS flow information associated with the UE data-related QoS flow.
  • the resource occupation or determine which of the UEs occupy also referred to as “allocate” the resource according to at least one of the information on the UE data and/or the UE context, e.g., the size of the UE data, the bearer information associated with the UE data-related bearer, the session information associated with the UE data-related session, the QoS flow information associated with the UE data-related QoS flow.
  • the data are received on the common resource, which of the UEs may success depend on the priorities of the UEs and/or priorities of the UE data (e.g., QoS of the UE data-related bearer, ARP, QoS of the UE data-related QoS flow).
  • priorities of the UEs and/or priorities of the UE data e.g., QoS of the UE data-related bearer, ARP, QoS of the UE data-related QoS flow.
  • the first node may perform the decryption operation or the integrity protection check operation according to at least one of the information on the UE data and/or the UE context, e.g., the UE data-related key information, the UE data-related security algorithm information, the indication data packet, whether the UE data is the first UE data packet, the UE data packet number, the old key, the new key, the data direction of the UE data, the bearer information associated with the UE data-related bearer, the session information associated with the UE data-related session, the QoS flow information associated with the UE data-related QoS flow, and the UE data-related operation information.
  • the UE data-related key information e.g., the UE data-related key information, the UE data-related security algorithm information, the indication data packet, whether the UE data is the first UE data packet, the UE data packet number, the old key, the new key, the data direction of the UE data
  • the first UE data is encrypted or integrity protected by the old key or old security algorithm. Therefore, the first node uses the old key or the old security algorithm for performing the decryption or integrity protection check on the first UE data.
  • the new radio access network node does not have the old key or the old security algorithm.
  • the new radio access network node may transmit the first UE data, the information on the UE data and/or the UE context to the old radio access network node for decryption and/or integrity protection check.
  • the new radio access network node obtains the old security information (e.g., the old key, the old security algorithm) on the UE from the old radio access network node for decryption or integrity protection check on the first UE data.
  • the first uplink data may refer to the first UE data transmitted during a UE synchronization process (e.g., a RACH process) or during the first RRC process.
  • a UE synchronization process e.g., a RACH process
  • the UE generates a new key based on key update information provided by the network.
  • the UE After the connection between the UE and the old radio access network node is inactive, the UE still maintains the UE context, including the old key, the old security algorithm.
  • the first UE data may be carried in the synchronization process or in the first RRC message. At this time, only the old key or the old security algorithm may be used to perform encryption or integrity protection on the UE data.
  • the first node performs the decryption operation or the integrity protection check operation based on the key information associated with the UE data (the key information associated with the UE data being described in Step 301, and description thereof being omitted for simplicity).
  • the first node may use the old key for performing the decryption operation or the integrity protection check operation on the related UE data packet.
  • the first node may use the new key for performing the decryption operation or the integrity protection check operation on the related UE data packet.
  • the first node When the key information associated with the UE data indicates that the used key-related number is the N-th key, the first node first makes comparison on a corresponding key related number corresponding to the key. If the key-related number is consistent with the serial number corresponding to the old key, the old key may be used to perform decryption or integrity protection check on the associated UE data packet. If the key-related number is consistent with the serial number corresponding to the new key, the new key may be used to perform decryption or integrity protection check on the associated UE data packet.
  • the first node performs the decryption operation or the integrity protection check operation according to the UE data-related security algorithm information (UE data-related security algorithm information being described in Step 301, and description thereof being omitted for simplicity).
  • UE data-related security algorithm information being described in Step 301, and description thereof being omitted for simplicity.
  • the first node performs the decryption operation or the integrity protection check operation according to a security information indication packet.
  • the node performs decryption or integrity protection check with the old key on the received UE data before receiving the security information indication packet, and performs decryption or integrity protection check with the new key on the received UE data after receiving the security information indication packet.
  • the first node when the first node is the old radio access network node, the first node may receive the information on the UE data and/or the UE context from the UE or the new radio access network node for performing the decryption or integrity protection check operation on the UE data.
  • the first node when the first node is a new radio access network node, the first node may receive the information on the UE data and/or the UE context from the UE and/or the old radio access network node for performing the decryption or integrity protection check operation on the UE data. For example, the first node receives the old key and the new key from the old radio access network node for respectively performing decryption or integrity protection check on data encrypted by different keys. For example, the decryption or integrity protection check with the old key is performed on the first UE data packet, and the decryption or integrity protection check with the new key is performed on the subsequent UE data packet.
  • the first node is the UE, and the first node may receive the information on the UE data and/or the UE context from the new radio access network node or the old radio access network node for performing decryption or integrity protection check on the UE data.
  • the first node when the first node lacks necessary information for performing decryption or integrity protection check on the UE data, the first node may perform at least one of: transmitting the UE data to other nodes, transmitting the obtained information on the UE data and/or the UE context to other nodes, transmitting decryption request information (as described in Step 301) or integrity protection check request information, transmitting data transmission request information (e.g., whether a reception acknowledgment is required, whether decryption is required).
  • decryption request information as described in Step 301
  • integrity protection check request information transmitting data transmission request information (e.g., whether a reception acknowledgment is required, whether decryption is required).
  • the data transmission operation may include at least one of: requesting to allocate an uplink data forwarding address, allocating an uplink data forwarding address, determining a data channel for transmission of the UE data, and determining a QoS flow operation. Requesting to allocate the uplink data forwarding address may be embodied by whether there are subsequent data.
  • the data transmission operation on the received UE data may include:
  • determining a data channel for transmission of the UE data may be mapping, by the first node, a data channel related to the UE data according to the information on the UE data. In some implementations, after the radio access network node receives the uplink data of the UE, it needs to determine which data channel the UE data should be transmitted to.
  • determining a QoS flow operation may be mapping, by the first node, a data flow related to the UE data according to the information on the UE data. In some implementations, after the radio access network node receives the downlink data of the UE, it needs to determine which QoS flow the UE data belong to.
  • the first node may perform the data transmission operation on the UE data according to at least one of the information on the UE data and/or the UE context, e.g., the bearer information associated with the UE data-related bearer, the session information associated with the UE data-related session, the QoS flow information associated with the UE data-related QoS flow, the routing information of the data channel on the UE data, the routing information associated with a UE data-related data channel, the information associated with a UE data-related operation, whether the UE data is the first UE data packet, the UE data packet number.
  • the bearer information associated with the UE data-related bearer e.g., the session information associated with the UE data-related session, the QoS flow information associated with the UE data-related QoS flow
  • the routing information of the data channel on the UE data e.g., the routing information associated with a UE data-related data channel, the information associated with a UE data-related operation, whether the
  • the first node may determine the data channel for transmission of the UE data based on the bearer information associated with the UE data.
  • Each UE session has a one-to-one data channel between the radio access network and the core network, while each bearer establishes one or more bearers at the radio access network side accordingly. It is easily understood that the related UE session information may be associated by the bearer information.
  • the routing information of the session channel related to the UE session between the radio access network and the core network may be associated by means of the UE session information.
  • the first node may transmit the UE data to the data channel determined by the UE bearer information (the routing information of the data channel being described in Step 301).
  • the data channel for transmission of the UE data may be determined based on the UE session information associated with the UE data.
  • the first node may transmit the UE data to the data channel determined by the UE session information (the routing information of the data channel being described in Step 301).
  • the first node when the first node is the old radio access network node, the first node may perform one of: allocating the uplink data forwarding address, transmitting the UE data to the core network.
  • the first node when the first node is the new radio access network node, the first node may perform one of: transmitting the first UE data to the old radio access network node, indicating whether there is still subsequent uplink UE data (the old radio access network node may allocate the uplink data forwarding address according to the indication). For other data, the first node may switch the data channel to the first node after obtaining the UE context from the old radio access network node and then transmit, or may transmit according to the uplink data forwarding address allocated by the old radio access network node.
  • the first node is used as the transmitting party of the UE data.
  • the control for the UE data may include at least one of: an encryption operation, an integrity protection check operation, a paging control operation, a resource occupation operation, a data transmission control operation.
  • the first node may perform the encryption operation or the integrity protection operation according to at least one of the information on the UE data and/or the UE context, e.g., the UE data-related key information, the UE data-related security algorithm information, the indication data packet, whether the UE data is the first UE data packet, the UE data packet number, the old key, the new key, the data direction of the UE data, the bearer information associated with the UE data-related bearer, the session information associated with the UE data-related session, the QoS flow information associated with the UE data-related QoS flow, and the UE data-related operation information.
  • the UE data-related key information e.g., the UE data-related key information, the UE data-related security algorithm information, the indication data packet, whether the UE data is the first UE data packet, the UE data packet number, the old key, the new key, the data direction of the UE data
  • the bearer information associated with the UE data-related bearer e.
  • the first UE data is encrypted or integrity protected by the old key or old security algorithm.
  • the first node may continue transmitting after receiving the key information associated with the UE data (as described in Step 301). If the key information associated with the UE data indicates updating the key, the first node continues performing the encryption operation and/or integrity protection operation on the subsequent UE data after generating the new key.
  • the first node continuously transmits the UE data encrypted by the old key.
  • the first node may indicate the key used when transmitting the UE data, such as using the old key, using the new key.
  • the first node transmits a security information indication packet before transmitting the data packet encrypted by the new key.
  • the security information indication packet separates the data encrypted by the old key from the data encrypted by the new key.
  • the data encrypted by the old key security are transmitted before the security information indication packet.
  • the data encrypted by the new key security are transmitted after the security information indication packet.
  • the first node may transmit the security information indication packet to the UE and other radio access network nodes via a paging message.
  • the first node performs the encryption operation or the integrity protection operation based on the key information associated with the UE data (the key information associated with the UE data being described in Step 301, and description thereof being omitted for simplicity).
  • the first node may use the old key for performing the encryption operation or the integrity protection operation on the related UE data packet.
  • the first node may use the new key for performing the encryption operation or the integrity protection operation on the related UE data packet.
  • the first node When the key information associated with the UE data indicates that the used key-related number is the N-th key, the first node first makes comparison on a corresponding key related number corresponding to the key. If the key-related number is consistent with the serial number corresponding to the old key, the old key may be used to perform encryption or integrity protection on the associated UE data packet. If the key-related number is consistent with the serial number corresponding to the new key, the new key may be used to perform encryption or integrity protection on the associated UE data packet.
  • the first node when the first node is the old radio access network node, the first node may perform the encryption or integrity protection operation on the UE data from the saved UE context.
  • the first node is the UE, and the first node may receive the information on the UE data and/or the UE context from the new radio access network node or the old radio access network node for performing encryption or integrity protection on the UE data, e.g., receiving the key information associated with the UE data, and generating a new key for encryption of the remaining UE data and transmission if the key information associated with the UE data indicates updating the key.
  • the first node may perform the paging control operation on the UE data according to at least one of the information on the UE data and/or the UE context, e.g., the size of the UE data packet, the bearer information (QoS, ARP) on the UE data-related bearer, the QoS flow information (QoS) on the UE data-related QoS flow.
  • the information on the UE data and/or the UE context e.g., the size of the UE data packet, the bearer information (QoS, ARP) on the UE data-related bearer, the QoS flow information (QoS) on the UE data-related QoS flow.
  • the bearer information QoS, ARP
  • QoS QoS flow information
  • the first node determines the priority of the paging and the scheduling of the paging resource according to the size of the UE data packet.
  • the first node determines the priority of the paging and the scheduling of the paging resource based on the UE data-related bearer information (QoS, ARP).
  • QoS UE data-related bearer information
  • the first node determines the priority of the paging and the scheduling of the paging resource based on the QoS flow information (QoS) on the UE data-related QoS flow.
  • QoS QoS flow information
  • the second radio access network node may receive transmission requests for different UE data from a plurality of radio access network nodes. How to guarantee QoS of these data, in which order schedules the UE data-related QoS are needed to be determined.
  • the first node may occupy resources (e.g., common channel resource) based on at least one of the information on the UE data and/or the UE context, such as the size of the UE data packet, the bearer information of the UE data-related bearer, the session information of the UE data-related session, and the QoS flow information associated with the UE data-related QoS flow.
  • resources e.g., common channel resource
  • the first node when the first node is the UE, a plurality of the first nodes desires to occupy the common resource for data transmission, and which UEs can success depend on priorities of the UEs and/or priorities of the UE data (e.g., QoS of the UE data-related bearer, ARP, QoS of the UE data-related QoS flow).
  • the first node may transmit at least one of the information on the UE data and/or the UE context for resource occupation while transmitting the UE data.
  • the first node may transmit the information on the UE data and/or the UE context to at least one of: a radio access network node, a core network node, a data termination point, a UE, a non-access stratum (e.g. a NAS layer) of the UE, an access stratum (e.g. an AS layer) of the UE, an application layer (e.g.
  • an APP layer of the UE, a CU, a DU, a core network user plane node, a core network control plane node, a source radio access network node in a movement process of the UE, a target radio access network node in a movement process of the UE, a new radio access network node the UE accesses in the light connection mode or the inactive state, an old radio access network node which saves the context of the UE in the light connection mode or the inactive state, a radio access network node that suspends the UE, and a radio access network node the UE requests to resume a connection.
  • the method 300 may further comprise steps as follows (not shown): the first node transmitting the information on the UE data and/or the UE context to at least one of: a radio access network node, a core network node, a data termination point, a UE, a non-access stratum (e.g. a NAS layer) of the UE, an access stratum (e.g. an AS layer) of the UE, an application layer (e.g.
  • a radio access network node e.g. a core network node, a data termination point, a UE, a non-access stratum (e.g. a NAS layer) of the UE, an access stratum (e.g. an AS layer) of the UE, an application layer (e.g.
  • an APP layer of the UE, a CU, a DU, a core network user plane node, a core network control plane node, a source radio access network node in a movement process of the UE, a target radio access network node in a movement process of the UE, a new radio access network node the UE accesses in the light connection mode or the inactive state, an old radio access network node which saves the context of the UE in the light connection mode or the inactive state, a radio access network node that suspends the UE, and a radio access network node the UE requests to resume a connection.
  • the information on the UE data and/or the UE context transmitted by the first node may be the information on the UE data and/or the UE context obtained by the first node, or the information on the UE data and/or the UE context updated after Step 302.
  • Fig. 4 is a schematic flowchart of the method of controlling the data transmission according to the second exemplary embodiment of the present disclosure. As shown in Fig. 4, the method 400 may include Steps 401 and 402.
  • Step 401 the second node determines whether a predetermined condition is satisfied.
  • the predetermined condition may at least include: transmitting the UE data in an inactive state.
  • the second node may be at least one of: a radio access network node, a core network node, a data termination point, a UE, a non-access stratum (e.g. a NAS layer) of the UE, an access stratum of the UE, an application layer of the UE, a CU, a DU, a core network user plane node, a core network control plane node, a source radio access network node in a movement process of the UE, a target radio access network node in a movement process of the UE, a new radio access network node the UE accesses in the light connection mode or the inactive state, an old radio access network node which saves the context of the UE in the light connection mode or the inactive state, a radio access network node that suspends the UE, and a radio access network node the UE requests to resume a connection.
  • a radio access network node e.g. a NAS layer
  • the second node transmits information on UE data and/or UE context, when it is determined that the predetermined condition is satisfied.
  • Step 301 the information on the UE data has been described in Step 301, and description thereof thus will be omitted for simplicity.
  • Step 301 the UE context has been described in Step 301, and description thereof thus will be omitted for simplicity.
  • the UE data are downlink data
  • the second node transmits the UE data, the information on the UE data, and/or the UE context by paging.
  • the second node may also transmit the paging to other nodes.
  • the second node is the old radio access network node.
  • the old radio access network node initiates the paging at the radio access network side to transmit the UE data to the inactive UE.
  • the old radio access network node also transmits the paging to the other radio access network node(s), and asks the other radio access network node(s) to page the UE together. It is easily understood that the paging area of the inactive UE is also the movement area of the inactive UE.
  • the data are uplink data
  • the second node transmits the UE data, the information on the UE data, and/or the UE context through a synchronization process or a first RRC process.
  • the second node may transmit the information on the UE data and/or the UE context to at least one of: a radio access network node, a core network node, a data termination point, a UE, a non-access stratum of the UE, an access stratum of the UE, an application layer of the UE, a CU, a DU, a core network user plane node, a core network control plane node, a source radio access network node in a movement process of the UE, a target radio access network node in a movement process of the UE, a new radio access network node the UE accesses in the light connection mode or the inactive state, an old radio access network node which saves the context of the UE in the light connection mode or the inactive state, a radio access network node that suspends the UE, and a radio access network node the UE requests to resume a connection.
  • a radio access network node a core network node, a data termination point, a
  • Fig. 5 is a schematic structure diagram of the device 500 according to an exemplary embodiment of the present disclosure.
  • the device 500 may be configured to perform the methods 300 and 400 as described above with reference to Figs. 3 and 4.
  • Figs. 3 and 4 For the sake of brevity, only the schematic structure of the device according to the exemplary embodiment of the present disclosure is described herein, and the details which have already been described in the methods with reference to Figs. 3 and 4 are omitted.
  • the device 500 may include a communication interface 501 for external communication; a processing unit or a processor 503, wherein the processor 503 may be a combination of a single unit or a plurality of units for performing different steps of the methods; and a memory 505, in which computer-executable instructions are stored.
  • the instructions when executed by the processor 503, cause the processor 503 to obtain information on UE data and/or UE context (as described in Step 301, and description thereof being omitted for simplicity); and perform control for transmission of the UE data, according to the obtained information on the UE data and/or UE context (as described in Step 302, and description thereof being omitted for simplicity).
  • the device 500 may be embodied as the first node of performing the method 300 described above with reference to Fig. 3.
  • the instructions when executed by the processor 503, cause the processor 503 to determine whether a predetermined condition is satisfied (as described in Step 401, and description thereof being omitted for simplicity); and transmit information on user equipment ‘UE’ data and/or UE context, when it is determined that the predetermined condition is satisfied (as described in Step 402, and description thereof being omitted for simplicity).
  • the device 500 may be embodied as the second node of performing the method 400 described above with reference to Fig. 4.
  • the predetermined condition at least includes: transmitting the UE data in an inactive state.
  • the first node may be embodied as the data receiving party, the data transmitting party that implements the method according to the embodiment of the present disclosure; and the second node may be embodied as a control information providing party that implements the method according to the exemplary embodiment of the present disclosure.
  • the second node may transmit control information (i.e., the information on the UE data and/or the UE context) if the predetermined condition is satisfied.
  • the first node may receive the control information, and control the reception and transmission operations of the data based on the control information.
  • Fig. 6 is a first schematic signal flow diagram between network entities to which a method according to an exemplary embodiment of the present disclosure is applied.
  • the UE transmits data in the inactive state.
  • the new radio access network node the UE accesses is not the radio access network node that saves the UE context.
  • the new radio access network node transmits the UE data to the old radio access network node.
  • the process includes steps as follows.
  • Step 601 the UE initiates a random access request or an RRC resource request message to the new radio access network node.
  • the message contains the first data packet of the UE, the information on the UE data, and/or the UE context (the information on the UE data and the context of the UE having been described in Step 301).
  • the operation on resource occupancy has been described in Step 302.
  • the first UE data packet may be UE data that have been encrypted and/or integrity protected.
  • the security algorithm used is the old security algorithm
  • the key used is the old key.
  • the new radio access network node transmits obtained UE context request or data transmission request message to the old radio access network node.
  • the message contains the first data packet of the UE, the information on the first data packet of the UE (same as the information on the UE data in Step 301), and/or the UE context (as described in Step 301).
  • the old radio access network node After the old radio access network node receives, it may perform one of:
  • the new wireless access network node may decrypt the first received data packet of the UE according to the old key or the old security algorithm; and may decrypt the subsequent data packets of the UE according to the new key or the new security algorithm.
  • the old radio access network node may perform an integrity protection check on the first received data packet of the UE according to the old key, the old security algorithm data direction, and/or the data-related bearer information (DRB ID).
  • DRB ID data-related bearer information
  • the old radio access network node transmits the UE data, the information on the UE data packet (same as the information on the UE data in Step 301), and/or the UE context information to the core network.
  • the old radio access network node determines the data channel for data transmission according to the data-related bearer information (DRB ID) or the data-related session information (session ID), as described in Step 302.
  • DRB ID data-related bearer information
  • session ID data-related session information
  • the old radio access network node transmits a UE context response or data transmission response message to the new radio access network node. If the UE data needs a reception acknowledgement, the old radio access network node may return to the new radio access network node, the reception acknowledgement packet, the serial number of the UE data packet acknowledged to be received successfully, the information on the reception acknowledgement packet (same as the information on the UE data in Step 301) and/or the context information in the message.
  • the old radio access network node may return to the new radio access network node the transmission acknowledgement packet, the serial number of the UE data packet acknowledged to be transmitted successfully, the information on the transmission acknowledgement packet (same as the information on the UE data in Step 301) and/or the context information.
  • the new radio access network node returns a random access response or an RRC response message to the UE.
  • the message contains the information on the UE context (e.g., whether to update the key, information necessary to update the key).
  • the message may also contain information on the downlink data packet, such as the reception acknowledgement packet.
  • Fig. 7 is a second schematic signal flow diagram between network entities to which a method according to an exemplary embodiment of the present disclosure is applied.
  • the UE transmits data in the inactive state.
  • the new radio access network node the UE accesses is not the radio access network node that saves the UE context.
  • the new radio access network node obtains the UE context from the old radio access network node.
  • the obtained UE context contains the old security information of the UE.
  • the method comprises steps as follows.
  • Step 701 is identical with Step 601, and description thereof is thus omitted for simplicity.
  • the new radio access network node transmits a UE context acquisition request message to the old radio access network node.
  • the message contains an old security context acquisition request (e.g., an old key acquisition request, an old security algorithm acquisition request) for the UE;
  • the old radio access network node transmits a UE context acquisition response message to the new radio access network node.
  • the message contains old security context for the UE.
  • the new radio access network node After the new radio access network node receives, it may perform one of:
  • the new wireless access network node may decrypt the first received data packet of the UE according to the old key or the old security algorithm; and may decrypt the subsequent data packets of the UE according to the new key or the new security algorithm.
  • the old radio access network node may perform an integrity protection check on the first received data packet of the UE according to the old key, the old security algorithm data direction, and/or the data-related bearer information (DRB ID).
  • DRB ID data-related bearer information
  • the new radio access network node returns a random access response or an RRC response message to the UE.
  • the message contains the information on the UE context (e.g., whether to update the key, information necessary to update the key).
  • the message may also contain information on the downlink data packet, such as the reception acknowledgement packet.
  • Step 705 the new radio access network node initiates a path switching process.
  • the core network control node controls the core network user plane node to switch the data channel of the UE session to the new radio access network node.
  • the new radio access network node transmits to the core network the UE data, the information on the UE data packet (same as the information on the UE data in Step 301), and/or the UE context information.
  • the new radio access network node determines the data channel for data transmission according to the data-related bearer information (DRB ID) or the data-related session information (session ID), as described in Step 302.
  • DRB ID data-related bearer information
  • session ID data-related session information
  • the new radio access network node may initiate a UE context release request to the old radio access network node.
  • the new radio access network node may initiate a UE context release procedure to the old radio access network node.
  • the node serving the UE switches to the new radio access network node.
  • Fig. 8 is a third schematic signal flow diagram between network entities to which a method according to an exemplary embodiment of the present disclosure is applied.
  • the old radio access network node transmits one or more UE packets to the UE in the inactive state.
  • the method comprises steps as follows.
  • Step 801 the core network user plane node transmits downlink data to the old radio access network node.
  • the old radio access network node initiates a paging message for the UE.
  • the paging contains the UE data, the information on the UE data packet (same as the information on the UE data in Step 301), and/or the UE context information (e.g., whether to update the key, information necessary to update the key, whether a reception acknowledgement is required).
  • the paging area configured by the UE also includes other new access network nodes, and the old radio access network node initiates to the new radio access network node the paging for the UE.
  • the paging contains the UE data, the information on the UE data packet (same as the information on the UE data in Step 301), and/or the UE context information (e.g., whether to update the key, information necessary to update the key, whether a reception acknowledgement is required, QoS of the UE data-related bearer, ARP, QoS of the UE data-related QoS flow, a size of the data packet).
  • the new radio access network node initiates paging for the UE.
  • the paging contains the UE data, the information on the UE data packet (same as the information on the UE data in Step 301), and/or the UE context information (e.g., whether to update the key, information necessary to update the key, whether a reception acknowledgement is required).
  • the new radio access network node determines the priority of the paging and the allocation of the paging resource according to the information on the UE data, as described in Step 302.
  • the UE After the UE receives the data packet in the paging, the UE determines the QoS flow according to the information on the UE data, as described in Step 302. The UE transmits the data mapped to the application layer of the UE according to the determined QoS flow.
  • the UE does not need to return a paging response when at least one of the following is satisfied: the paging indicates that no response is required, that no reception acknowledgment is required to be returned, that there is no subsequent UE data packet, and the UE does not have UE data to be transmitted.
  • Fig. 9 is a fourth schematic signal flow diagram between network entities to which a method according to an exemplary embodiment of the present disclosure is applied.
  • the old radio access network node transmits one or more UE packets to the UE in the inactive state.
  • the method comprises steps as follows.
  • Steps 901-904 are identical with Steps 801-804, and description thereof is thus omitted for simplicity.
  • Step 905 the UE needs to return a paging response, and the UE accesses the new radio access network node.
  • the UE initiates a random access request or a RRC request message to the new radio access network node.
  • the message contains the information on the UE data (e.g., the acknowledgement of the UE for the UE data received in the paging) and/or the context of the UE (whether the security context of the UE has been updated).
  • the operation on resource occupancy has been described in Step 302.
  • Step 906 the new radio access network node transmits a UE context acquisition request message to the old radio access network node.
  • Step 907 the old access network node transmits a UE context acquisition response message to the new radio access network node.
  • the new radio access network node returns a random access response or an RRC response message to the UE.
  • the message contains the information on the UE context (such as whether to update the key, information necessary to update the key).
  • the message may also contain information on downlink packet, such as a reception acknowledgment packet.
  • the new radio access network node initiates a path switching process.
  • the core network control node controls the core network user plane node to switch the data channel of the UE session to the new radio access network node.
  • the new radio access network node may initiate a UE context release process to the old radio access network node.
  • the node serving the UE switches to the new radio access network node.
  • service continuity mode one indicates the mode that the service continuity is kept throughout
  • service continuity model two indicates the mode that the service continuity is kept within the designated area
  • service continuity mode three indicates the service continuity mode having multiple data endpoints.
  • 3GPP may eventually use other names to name the above-mentioned service continuity mode one, two, and three, which does not affect main contents of the present disclosure.
  • Bonjour of service continuity modes may be applied to two system architecture including SAE and 5G, as shown in Fig. 1 and Fig. 2.
  • the UE may support a variety of network slices or dedicated networks, and different network slices or dedicated networks may support different service types. Different UE sessions may be set up on different network slices. Generally, a data endpoint of a UE session is in a network slice. Changing the network slice may change the data endpoint. However, service continuity cannot be guaranteed when the data endpoint is changed.
  • a radio access network may support different network slices.
  • a network slice that is accessed by a target radio access network may not be a current network slice of the UE session. If the network slice of the UE session is changed, the data endpoint of the UE session may be changed.
  • a target node or a target cell may permit the UE to access but not permit a specific service of the UE to access.
  • a radio access network only learns UE session information but does not learn what service the UE session sets up. And an area where the service is permitted to access and an area where the service is prohibited to access are not clear.
  • Issue 2 when the UE moves under the same network system, operations of different service continuity modes are different. 1) For a service of service continuity mode one, the service continuity is supported, such as handover, UE context transfer, and data forwarding, etc. 2) For a UE session of service continuity mode two, the service continuity is supported within a service continuity area. When the UE moves out of the service continuity area, data endpoint changing is triggered. An old data endpoint is released firstly when a data endpoint of the UE session of service continuity mode two is changed.
  • UE session context For such session, it is of no significance to transfer UE session context or forward data between the UE and the old data endpoint to a target node when the UE is handed over to the target node, and may consider requesting release the session before the UE is handed over.
  • UE session of service continuity mode three the same UE session may be set up with multiple data endpoints with moving of the UE. As a session channel between the UE and an old data endpoint is not released, it is meaningful to forward the data between the UE and the old data endpoint to the target node when the UE is handed over to the target node. When the handover is complete, release of the session between the UE and the old data endpoint may be initiated.
  • a network slice supported by the target radio access network may not be a current network slice of the UE session, it may be considered to map the UE session to the network slice supported by the target network.
  • Changing the network slice may cause changing of the data endpoint.
  • Service continuity mode one is not supposed to change the data endpoint, so the UE session of service continuity mode one is not supposed to perform network slice mapping or changing.
  • a source or target radio access network node may initiate the release of the service, and the network slice is not changed.
  • an interoperable operation between network systems requires that the data endpoint of the UE session is kept.
  • the interoperable operation between network systems may be supported.
  • the majority of target network systems are no longer within a continuity keeping range of the UE session, and it is estimated that there is no need to support the interoperable operation between network systems.
  • Fig. 10 is a schematic flowchart of a method for controlling continuity of user equipment, according to an embodiment of the present disclosure. As shown in Fig. 10, the method includes following processes.
  • a first node learns at least one kind of continuity control information corresponding to a UE.
  • the continuity control information may include at least one of the following: service continuity mode information, keeping service continuity range information, data endpoint serving range information, service-permitted range information, service-prohibited range information, area information of an access-permitted area, area information of an access-prohibited area, information of an access-permitted network slice, area information of an area supported by a target node or a target cell, indication information about whether handover is performed, indication information about whether handover is prepared, release indication information, indication information about whether data is forwarded, indication information about whether an interoperable operation between networks is performed, indication information about whether a data endpoint is changed, indication information about whether a network slice is changed, indication information about whether there are multiple data endpoints, UE identifier information, session information, bearer information, QoS flow information, and service data flow information.
  • any of the continuity control information may be at a UE level, a UE session level, a bearer (e.g., E-RAB or DRB) level, a QoS flow level, or a service data flow level. It is not difficult to understand that the UE identifier information, the session information, the bearer information, the QoS flow information, and the service data flow information in the continuity control information are used to indicate identifiers of different levels, respectively. For example, UE session information in the continuity control information at the UE session level indicates an identifier of the UE session.
  • a bearer e.g., E-RAB or DRB
  • the continuity control information may be carried on one of S1, X2, NG2, or Xn interface messages including an initial context setup request message (e.g., an S1 or an NG2 interface message), a UE context recovery request message (e.g., an S1 or an NG2 interface message), a PDU session setup request message (e.g., an S1 or an NG2 interface message), a handover request message (e.g., an S1 or an NG2 interface message), a path conversion request confirming message (e.g., an S1 or an NG2 interface message), an obtaining UE context response message (e.g., an S1, an X2, an NG2, or an Xn interface message), and a handover request message (e.g., an S1, an X2, an NG2, or an Xn interface message).
  • an initial context setup request message e.g., an S1 or an NG2 interface message
  • a UE context recovery request message e.g., an S1
  • the first node may be one of the following: a first radio access network node, a source radio access network node during a UE moving procedure, a target radio access network node during the UE moving procedure, a new radio access network node that is accessed by the UE under a light-connection mode or in an inactive state, an old radio access network node where the UE stores UE context under the light-connection mode or in the inactive state, a radio access network node suspending the UE, a radio access network node where the UE requests connection recovery, a radio access network node, a core network node, a data endpoint, and the UE.
  • the first node may receive the above-described continuity control information from one of the following: a second radio access network node (i.e., a radio access network node different from the first radio access network node), a radio access network node, a core network node, a data endpoint, a source radio access network node during a UE moving procedure, a target radio access network node during the UE moving procedure, a new radio access network node that is accessed by the UE under a light-connection mode or in an inactive state, an old radio access network node where the UE stores UE context under the light-connection mode or in the inactive state, a radio access network node suspending the UE, a radio access network node where the UE requests connection recovery, a radio access network node, a core network node, a data endpoint, and the UE.
  • a second radio access network node i.e., a radio access network node different from the first radio access network node
  • the service continuity mode information may include a plurality of service continuity modes, such as the above-mentioned service continuity mode one, two, and three.
  • service continuity mode one may indicate that the data endpoint of the UE is kept unchanged;
  • service continuity mode two indicates that the data endpoint is kept unchanged in a keeping service continuity area or in a serving area of the data endpoint, and the data endpoint may be changed out of the keeping service continuity area or the serving area of the data endpoint;
  • service continuity mode three indicates that the UE may have two data endpoints at the same time, for example, when the UE and a first data endpoint are not released, the UE is permitted to set up the same session with a second data endpoint.
  • the data endpoint may be a data endpoint at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • the bearer e.g., E-RAB or DRB
  • the keeping service continuity range information may include at least one of the following: service type information of keeping service continuity, and area information of the keeping service continuity area.
  • the area information may include, but not be limited to, at least one of the following: a network system type (such as a 3G network, EPC, NGC), a radio access technology type (such as GERA, UTRA, EUTRA, NR), a network type (such as GERAN, UTRAN, EUTRAN , NR), a network identifier (such as PLMN), a location area identifier (such as RA, LA, TA), network slice information, a radio access network node identifier, a cell identifier, and so on.
  • a network system type such as a 3G network, EPC, NGC
  • a radio access technology type such as GERA, UTRA, EUTRA, NR
  • a network type such as GERAN, UTRAN, EUTRAN , NR
  • a network identifier such as PLMN
  • the area information of the keeping service continuity area is the same as the area information described above.
  • the keeping service continuity area may indicate that the service continuity is required to be kept within an indicated area, such as unchanging a data endpoint, initiating handover when the UE moves to the target node, performing data forwarding, etc.
  • the service type information may include, but not be limited to, at least one of the following: Enhanced Mobile Broadband (eMBB), Ultra-Reliability and Low Latency Communications (URLLC), Massive Machine Type Communication (mMTC), mission-critical MTC, IP Multimedia Subsystem, voice services, data flow services, video services, Virtual Reality (VR) services, and short message services.
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra-Reliability and Low Latency Communications
  • mMTC Massive Machine Type Communication
  • IP Multimedia Subsystem IP Multimedia Subsystem
  • the data endpoint serving range information may include at least one of the following: information of the data endpoint and area information of a serving area of the data endpoint.
  • contents of the area information of the serving area of the data endpoint coincide with contents of the area information described above, which are not described repeatedly herein.
  • the information of the data endpoint may include at least one of the following: an identifier of the data endpoint, an IP address of the data endpoint, a transport layer address, and a transport layer TEID.
  • the area information of the keeping service continuity area may be a subset of the serving area of the data endpoint.
  • the area information of the area supported by the target node or the target cell coincides with the contents of the area information described above, which are not described repeatedly herein.
  • the indication information about whether the handover is performed may include at least one of the following: a handover indication and a no-handover indication.
  • the handover indication may indicate that the handover is either enabled or permitted.
  • the no-handover indication may indicate that the handover is neither enabled nor permitted.
  • the no-handover indication may also be expressed as a release indication.
  • the indication information about whether the handover is performed may be handover indication information at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • the indication information about whether the handover is prepared may include at least one of the following: a handover-preparation indication, and a no-handover-preparation indication.
  • the handover-preparation indication may be to allocate radio resource, allocate a data forwarding address, and so on.
  • the no-handover-preparation indication may be not to allocate the radio resource, not to allocate the data forwarding address, and so on.
  • the indication information about whether the handover is prepared may be handover indication information at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • the bearer e.g., E-RAB or DRB
  • the indication information about whether the handover is performed may also be reflected as the indication information about whether the handover is prepared.
  • a source radio access network node may learn that the session is enabled or permitted to be handed over.
  • the source radio access network node sends a handover-preparation indication about the session to the target radio access network node.
  • the target radio access network node may learn that the UE session is not enabled or permitted to be handed over.
  • the source radio access network node When the source radio access network node initiates the handover to the target radio access network node, the source radio access network node sends a no-handover-preparation indication about the session to the target radio access network node. It is not difficult to understand that when the first node is the source radio access network node, whether the handover is initiated is determined according to whether the handover indication is received or not. When the first node is the target radio access network node, whether the handover preparation is performed is determined according to whether the handover-preparation indication is received or not.
  • the release indication information may include at least one of the following: release prior to handover, release after handover, a release indication, and a no-release indication.
  • the release prior to handover may indicate that the source radio access network node may be released firstly when the target cell of the handover does not belong to the keeping service continuity area or the serving area of the data endpoint, such as associated session, bearer, QoS flow, service data flow, etc.
  • the release after handover may indicate that the handover may be completed firstly and then the target radio access network node initiates the release when the target cell of the handover does not belong to the keeping service continuity area or the serving area of the data endpoint, such as associated session, bearer, QoS flow, service data flow, etc.
  • the release indication may be either enabled or permitted to release.
  • the no-release indication may be neither enabled nor permitted to release.
  • the no-release indication may also be reflected as the handover indication.
  • the release indication information may be release indication information at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • the indication information about whether the data is forwarded may include at least one of the following: a data-forwarding indication, and a no-data-forwarding indication.
  • the data-forwarding indication information may be at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • the session information may include at least one of the following: session identifier information, a session type (e.g., a PDU session type), service type information in the session, a QoS flow Indicator in the session, service data flow information in the session, a UE address of the session, an identifier of a data endpoint of the session, an IP type, and a non-IP type.
  • the service type information in the session may refer to the service type information described above, which is not described repeatedly herein.
  • the bearer information may include at least one of the following: a bearer identifier (e.g., an E-RAB ID, a DRB ID), service type information in the bearer (the service type information in the bearer may refer to the service type information described above).
  • a bearer identifier e.g., an E-RAB ID, a DRB ID
  • service type information in the bearer may refer to the service type information described above.
  • the QoS flow information may include at least one of the following: a QoS flow indicator, service data flow information in the QoS flow, and service type information in the QoS flow (the service type information in the QoS flow may refer to the service type information described above).
  • the service data flow information may include at least one of the following: a service data flow identifier (e.g., a quintuple group such as a source IP, a source port, a target IP, a target port, and payload information), and service type information in the service data flow (the service type information of the service data flow may refer to the service type information described above).
  • a service data flow identifier e.g., a quintuple group such as a source IP, a source port, a target IP, a target port, and payload information
  • service type information in the service data flow may refer to the service type information described above.
  • the data continuity is kept.
  • the UE may be requested to initiate handover, context transfer, handover preparation, data forwarding, and the like.
  • the source node may not initiate handover with respect to the UE session (e.g., indicating not to hand over the session, indicating to release the session, or indicating not to send the context of the session), not request the session to forward data (e.g., indicating the session not to forward data); the target node may not perform handover preparation for the UE session (e.g., according to a no-handover indication or a release indication regarding the session, not allocate radio bearer resource, QoS flow, and radio bearer mapping etc., for the session), may not allocate a data forwarding address for the UE session (e.g., according to the no-handover indication, the release indication, or a no-data-forwarding indication regarding the session, not allocate the data forwarding address for the session.
  • the target node may not perform handover preparation for the UE session (e.g., according to a no-handover indication or a release indication regarding the session, not allocate radio bearer resource, QoS flow, and radio bearer mapping etc.,
  • the source node or the target node may be released directly to accelerate handover procedures of other sessions.
  • the UE may initiate the setup of the session between the UE and the second data endpoint. If all of UE sessions are the session described above, the UE may be released directly.
  • the source node may request to release a session channel between the radio access network node and an old data endpoint before the handover.
  • the network may initiate setup of a session between the UE and a second data endpoint without releasing a session between the UE and a first data endpoint.
  • session context may be transferred.
  • a source node may initiate the handover, and a target node may perform handover preparation.
  • the source node may require data forwarding, and the target node may allocate a data forwarding address.
  • the target node may request to release a session channel between the radio access network node and an old data endpoint after the handover.
  • the indication information about whether the interoperable operation between networks is performed may include at least one of the following: an interoperable-operation-between-networks indication, and a no-interoperable-operation-between-networks indication.
  • the indication information about whether the interoperable operation between networks is performed may further include indication information of whether dual attachments are performed and indication information of whether inter-network handover is performed.
  • the interoperable-operation-between-networks indication, a dual-attachments indication, and an inter-network handover indication may respectively indicate that the interoperable operation between networks is enabled or permitted, the dual attachments are enabled or permitted, and the inter-network handover is enabled or permitted.
  • the no-interoperable-operation-between-networks indication, a no-dual-attachments indication, and a no-inter-network handover indication may respectively indicate that the interoperable operation between networks is not enabled or permitted, the dual attachments are not enabled or permitted, and the inter-network handover is not enabled or permitted.
  • the indication information about whether the interoperable operation between networks is performed, the indication information of whether dual attachments are performed, and the indication information of whether inter-network handover is performed may be at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • a data endpoint when the interoperable operation between network systems is performed, such as dual attachments (dual attaching to two network systems and connecting to the same data endpoint), a data endpoint is not changed during handover between the network systems. If the data endpoint is to be changed, the UE may directly access a target network system and release a connection with a source network system without performing the interoperable operation between network systems. It is not difficult to understand that a UE session of service continuity mode one may perform the interoperable operation between network systems, the interoperable operation between network systems may be performed between network systems supported by service continuity mode two, and the interoperable operation between network systems may not be performed if the UE session of service continuity mode two does not support the target network system.
  • the indication information about whether the data endpoint is changed may include at least one of the following: an indication indicating that the data endpoint is enabled or permitted to be changed and an indication indicating that the data endpoint is not enabled or permitted to be changed.
  • the indication information about whether the data endpoint is changed may be at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • the indication information about whether the network slice is changed may include at least one of the following: an indication indicating that the network slice is enabled or permitted to be changed or mapped and an indication indicating that the network slice is not enabled or permitted to be changed or mapped.
  • the indication information about whether the network slice is changed may be at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • a data endpoint may be part of a network slice.
  • the UE session may be mapped to another network slice. Changing of the network slice may cause changing of the data endpoint. It is not difficult to understand that a session in which a data endpoint is enabled or permitted to be changed may be implemented with network slice mapping or network slice changing.
  • the information of the access-permitted network slice may include at least one of the following: information of the network slice, and area information of an area supporting the network slice (the area information of the area supporting the network slice may refer to the area information of the keeping service continuity area described above, which is not described repeatedly herein).
  • the information of the access-permitted network slice may be at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • the information of the network slice may include at least one of the following: an identifier of the network slice, service type information supported by the network slice (the supported service type information may refer to the above-described service type, which is not described repeatedly herein), and area information of a network slice area (the area information of the network slice area may refer to the above-described area information, which is not described repeatedly herein).
  • the service-permitted range information may include at least one of the following: a service type, and area information of a service-permitted area (the area information of the service-permitted area may refer to the contents of the area information described above, which is not described repeatedly herein).
  • the service-prohibited range information may include at least one of the following: a service type, and area information of a service-prohibited area (the area information of the service-prohibited area may refer to the contents of the area information described above, which is not described repeatedly herein).
  • the service-permitted range information and the service-prohibited range information may respectively indicate an area where a service is permitted to access and an area where the service is not permitted to access.
  • the service may be at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • At least one of following operations may be performed, including not transferring the UE session to the target node, not initiating the handover of the session to the target node, and not requiring forward the data of the session to the target node.
  • At least one of following operations may be performed, including not allocating a data forwarding address for the session, not performing handover preparation for the session, and notifying the core network to release the session, in which the reason of releasing the session is a service of the session is not permitted to access.
  • the area information of the access-prohibited area may refer to the contents of the area information described above, which is not described repeatedly herein.
  • the indication information about whether there are multiple data endpoints includes at least one of the following: a multiple-data-endpoints indication and a single-data-endpoint indication.
  • the multiple-data-endpoints indication may indicate that a plurality of data endpoints are enabled or permitted at the same time.
  • the single-data-endpoint indication may indicate that a single data endpoint is enabled or permitted at the same time.
  • the indication information about whether there are multiple data endpoints may be at the UE level, the UE session level, the bearer (e.g., E-RAB or DRB) level, the QoS flow level, or the service data flow level.
  • the bearer e.g., E-RAB or DRB
  • the method for controlling continuity of user equipment may further include following processes.
  • the first node performs corresponding continuity control to the UE.
  • continuity control information may refer to descriptions in block 1001 and are not described repeatedly herein.
  • the operation of performing corresponding continuity control to the UE may include at least one of the following: handover control, release control, data forwarding control, interoperable-operation-between-networks control, network slice changing or mapping control, and continuity operation information configuration.
  • the handover control includes at least one of the following: whether to initiate the handover, and whether to perform the handover preparation. It is not difficult to understand that when the first node is the source node, the handover control may be initiating the handover; and when the first node is the target node, the handover control may be the handover preparation.
  • the initiating the handover or the handover preparation may include at least one of the following: sending a context at a correlative level (e.g., a UE context, a UE session context, a bearer context, bearer configuration, a QoS flow context, mapping between a QoS flow and radio bearer, or a service data flow context), preparing radio resources for the UE, configuring the radio bearer, allocating a data forwarding address, and indicating handover session information to the core network node.
  • a context at a correlative level e.g., a UE context, a UE session context, a bearer context, bearer configuration, a QoS flow context, mapping between a QoS flow and radio bearer, or a service data flow context
  • preparing radio resources for the UE configuring the radio bearer, allocating a data forwarding address, and indicating handover session information to the core network node.
  • No-initiating the handover or no-handover-preparation may include at least one of the following: not sending the context at the correlative level (e.g., the UE context, the UE session context, the bearer context, the bearer configuration, the QoS flow context, the mapping between the QoS flow and the radio bearer, or the service data flow context), not preparing the radio resources for the UE, not configuring the radio bearer, not allocating the data forwarding address, and indicating released session information to the core network node.
  • the context at the correlative level e.g., the UE context, the UE session context, the bearer context, the bearer configuration, the QoS flow context, the mapping between the QoS flow and the radio bearer, or the service data flow context
  • the first node may determine the handover control based on at least one piece of the continuity control information.
  • the correlative level of the handover control may be the UE, the UE session, the bearer (e.g., E-RAB or DRB), the QoS flow, or the service data flow.
  • the handover control at the UE session level may be that: 1) for a UE session meeting a condition of initiating the handover or initiating the handover preparation, context transfer of the UE session, handover of the UE session, or handover preparation of the UE session (e.g., radio bearer configuration) etc., may be initiated; 2) for a UE session meeting a condition of not initiating the handover or not initiating the handover preparation, context transfer of the UE session, handover of the UE session, or handover preparation of the UE session, may not be initiated.
  • the first node initiates the handover or performs the handover preparation for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode one is learnt
  • service continuity mode two is learnt and the target node or the target cell belongs to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the keeping service continuity area
  • the target node or the target cell belongs to the serving area of the data endpoint
  • service continuity mode three is learnt
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, it is learnt that the target node or the target cell belongs to the access-permitted area, it is learnt that the target node or the target cell does not belong to the access-prohibited area, it is learnt that the target node or the target cell supports a current network slice of the correlative level
  • the handover indication is learnt
  • the handover-preparation indication is learnt
  • the no-release indication is learnt
  • the data-forwarding indication is learnt
  • the interoperable-operation-between-networks indication is learnt
  • the indication indicating that the data endpoint is not changed is learnt
  • the indication indicating that the data endpoint is changed and the multiple-data-endpoints indication are learnt
  • the indication indicating that the network slice is not changed is learnt
  • the single-data-endpoint indication is learnt and the target node or the target cell belongs to the keeping service continuity area
  • the single-data-endpoint indication is learnt and the target node or the target cell belongs to the serving area of the data endpoint.
  • the first node does not initiate the handover or perform the handover preparation for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode two is learnt and the target node or the target cell does not belong to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell does not belong to the serving area of the data endpoint, the target node or the target cell does not belong to the keeping service continuity area, the target node or the target cell does not belong to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-prohibited area, it is learnt that the target node or the target cell does not belong to the service-permitted area, it is learnt that the target node or the target cell does not belong to the access-permitted area, it is learnt that the target node or the target cell belongs to the access-prohibited area, it is learnt that the target node or the target cell does not support a current network slice of the correlative level and service continuity mode one is learnt, it is learnt that the target node or the target cell does not support the current network slice of the correlative level and the single-data-endpoint indication is learnt,
  • the handover indication is not learnt, the handover-preparation indication is not learnt, the no-handover indication is learnt, the no-handover-preparation indication is learnt, the release indication is learnt, the no-data-forwarding indication is learnt, the no-interoperable-operation-between-networks indication is learnt, the indication indicating that the data endpoint is changed is learnt, the indication indicating that the data endpoint is changed and the single-data-endpoint indication are learnt, and the indication indicating that the network slice is changed is learnt.
  • the core network may release a correlative session after receiving the notification.
  • the first node may determine the release control based on at least one piece of the continuity control information.
  • a correlative level of the release control may be the UE, the UE session, the bearer (e.g., E-RAB or DRB), the QoS flow, or the service data flow. It is not difficult to understand that the release control at the UE session level may be initiating the release of a UE session meeting a release condition. In some embodiments, the release control indicates that initiating the release before or after the handover.
  • the first node initiates the release for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode two is learnt and the target node or the target cell does not belong to the serving area of the data endpoint, the target node or the target cell does not belong to the keeping service continuity area, the target node or the target cell does not belong to the serving area of the data endpoint,
  • the target node or the target cell does not belong to the service-permitted area, it is learnt that the target node or the target cell belongs to the service-prohibited area, it is learnt that the target node or the target cell does not belong to the access-permitted area, it is learnt that the target node or the target cell belongs to the access-prohibited area, it is learnt that the target node or the target cell does not support a network slice of the correlative level and service continuity mode one is learnt, it is learnt that the target node or the target cell does not support the network slice of the correlative level and the single-data-endpoint indication is learnt,
  • the handover indication is not learnt, the handover-preparation indication is not learnt, the no-handover indication is learnt, the no-handover-preparation indication is learnt, the release indication is learnt, the no-data-forwarding indication is learnt, the no-interoperable-operation-between-networks indication is learnt, the indication indicating that the data endpoint is changed is learnt, the indication indicating that the data endpoint is changed and the single-data-endpoint indication are learnt, and the indication indicating that the network slice is changed is learnt.
  • the first node initiates pre-handover release for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode two is learnt, the target node or the target cell does not belong to the keeping service continuity area, and the target node or the target cell does not belong to the serving area of the data endpoint.
  • the first node initiates post-handover release for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode three is learnt, the target node or the target cell does not belong to the keeping service continuity area, and the target node or the target cell does not belong to the serving area of the data endpoint.
  • the core network may be notified of the to-be-released UE session: the core network, and the UE, and the reason for release (which may be an explanation for meeting a release condition) is explained. Then the core network or the UE may release a correlative session after receiving the notification.
  • the first node may determine the data forwarding control based on at least one piece of the continuity control information.
  • the data forwarding control may include one of the following: whether to require the data forwarding, and whether to allocate a data forwarding address. It is not difficult to understand that when the first node is the source node, the data forwarding control may be whether to require the data forwarding; when the first node is the target node, the data forwarding control may be whether to allocate the data forwarding address.
  • the correlative level of data forwarding control may be the UE, the UE session, the bearer (e.g., E-RAB or DRB), the QoS flow, or the service data flow. It is not difficult to understand that the data forwarding control at the UE session level may be initiating data forwarding control about a UE session meeting a data forwarding control condition.
  • the first node requires data forwarding or allocates the data forwarding address for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode one is learnt
  • service continuity mode two is learnt and the target node or the target cell belongs to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the keeping service continuity area
  • the target node or the target cell belongs to the serving area of the data endpoint
  • service continuity mode three is learnt
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, it is learnt that the target node or the target cell belongs to the access-permitted area, it is learnt that the target node or the target cell does not belong to the access-prohibited area, it is learnt that the target node or the target cell supports a current network slice of the correlative level
  • the handover indication is learnt
  • the handover-preparation indication is learnt
  • the no-release indication is learnt
  • the data-forwarding indication is learnt
  • the interoperable-operation-between-networks indication is learnt
  • the indication indicating that the data endpoint is not changed is learnt
  • the indication indicating that the network slice is not changed is learnt
  • the data-forwarding indication is learnt
  • the single-data-endpoint indication is learnt and the target node or the target cell belongs to the keeping service continuity area
  • the single-data-endpoint indication is learnt and the target node or the target cell belongs to the serving area of the data endpoint.
  • the first node does not require data forwarding or allocate the data forwarding address for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode two is learnt and the target node or the target cell does not belong to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell does not belong to the serving area of the data endpoint, the target node or the target cell does not belong to the keeping service continuity area, the target node or the target cell does not belong to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-prohibited area, it is learnt that the target node or the target cell does not belong to the service-permitted area, it is learnt that the target node or the target cell belongs to the access-prohibited area, it is learnt that the target node or the target cell does not support a network slice of the correlative level and service continuity mode one is learnt, it is learnt that the target node or the target cell does not support the network slice of the correlative level and the single-data-endpoint indication is learnt,
  • the handover indication is not learnt, the no-handover-preparation indication is not learnt, the no-handover indication is learnt, the no-handover-preparation indication is learnt, the release indication is learnt, the no-interoperable-operation-between-networks indication is learnt, the indication indicating that the data endpoint is changed is learnt, the indication indicating that the data endpoint is changed and the single-data-endpoint indication are learnt, the indication indicating that the network slice is changed is learnt, the data-forwarding indication is not received, and the no-data-forwarding indication is learnt.
  • One of the following may be notified of a UE session that does not require data forwarding or does not allocate the data forwarding address: the core network, and the UE, and the reason for not requiring the data forwarding or not allocating the data forwarding address (which may be an explanation for meeting a condition of not requiring the data forwarding or not allocating the data forwarding address) is explained.
  • the first node determines the interoperable-operation-between-networks control based on at least one piece of the continuity control information.
  • the interoperable-operation-between-networks control may include at least one of the following: whether it is inter-network handover, and whether it is dual attachments.
  • a correlative level of the interoperable-operation-between-networks control may be the UE, the UE session, the bearer (e.g., E-RAB or DRB), the QoS flow, or the service data flow. It is not difficult to understand that interoperable-operation-between-networks control at the UE level may be initiating interoperable-operation-between-networks control about a UE meeting an interoperable-operation-between-networks control condition.
  • the first node initiates the interoperable operation between networks for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode one is learnt
  • service continuity mode two is learnt and the target node or the target cell belongs to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the keeping service continuity area
  • the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, it is learnt that the target node or the target cell belongs to the access-permitted area, it is learnt that the target node or the target cell does not belong to the access-prohibited area,
  • the single-data-endpoint indication is learnt, the interoperable-operation-between-networks indication is received, the indication indicating that the data endpoint is not changed is learnt, and the indication indicating that the network slice is not changed is learnt.
  • the first node initiates the inter-network handover for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode one is learnt
  • service continuity mode two is learnt and the target node or the target cell belongs to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the keeping service continuity area
  • the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, it is learnt that the target node or the target cell belongs to the access-permitted area, it is learnt that the target node or the target cell does not belong to the access-prohibited area, the single-data-endpoint indication is learnt, service continuity mode three is learnt,
  • the handover indication is learnt
  • the handover-preparation indication is learnt
  • the inter-network handover indication is learnt
  • the no-release indication is learnt
  • the data-forwarding indication is learnt
  • the interoperable-operation-between-networks indication is learnt
  • the indication indicating that the data endpoint is not changed is learnt.
  • the first node initiates inter-network dual attachments for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode one is learnt
  • service continuity mode two is learnt and the target node or the target cell belongs to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the keeping service continuity area
  • the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, it is learnt that the target node or the target cell belongs to the access-permitted area, it is learnt that the target node or the target cell does not belong to the access-prohibited area,
  • the single-data-endpoint indication is learnt
  • service continuity mode three is learnt
  • the dual-attachments indication is learnt
  • the indication indicating that the data endpoint is not changed is learnt.
  • the first node does not initiate the interoperable operation between networks, does not initiate the inter-network handover, or does not initiate the dual attachments for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • service continuity mode two is learnt and the target node or the target cell does not belong to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell does not belong to the serving area of the data endpoint, the target node or the target cell does not belong to the keeping service continuity area, the target node or the target cell does not belong to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-prohibited area, it is learnt that the target node or the target cell does not belong to the service-permitted area, it is learnt that the target node or the target cell does not belong to the access-permitted area, it is learnt that the target node or the target cell belongs to the access-prohibited area,
  • the multiple-data-endpoints indication is learnt, the handover indication is not received, the no-handover-preparation indication is not received, the no-handover indication is learnt, the no-handover-preparation indication is learnt, the release indication is learnt, the no-interoperable-operation-between-networks indication is learnt, the indication indicating that the data endpoint is changed is learnt, the indication indicating that the network slice is changed is learnt, the data-forwarding indication is not received, and the no-data-forwarding indication is learnt.
  • the first node determines whether to perform the network slice changing or mapping control based on at least one piece of the continuity control information.
  • a correlative level of the network slice changing or mapping control may be the UE, the UE session, the bearer (e.g., E-RAB or DRB), the QoS flow, or the service data flow. It is not difficult to understand that the network slice changing or mapping control at the UE level may be initiating the network slice changing or mapping control about a UE session meeting a network slice changing or mapping control condition.
  • the first node initiates the network slice changing or mapping for the correlative level when the first node determines that the correlative level meets at least one of the following conditions:
  • the target node or the target cell does not support a network slice of the correlative level (e.g., the UE, the UE session, the bearer, the QoS flow, or the service data flow) at the source node,
  • a network slice of the correlative level e.g., the UE, the UE session, the bearer, the QoS flow, or the service data flow
  • service continuity mode two is learnt
  • service continuity mode three is learnt
  • service continuity mode two is learnt and the target node or the target cell does not belong to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell does not belong to the serving area of the data endpoint, the target node or the target cell does not belong to the keeping service continuity area, the target node or the target cell does not belong to the serving area of the data endpoint,
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, it is learnt that the target node or the target cell belongs to the access-permitted area, it is learnt that the target node or the target cell does not belong to the access-prohibited area,
  • the multiple-data-endpoints indication is learnt
  • the handover indication is learnt
  • the handover-preparation indication is learnt
  • the no-release indication is learnt
  • the data-forwarding indication is received
  • the indication indicating that the data endpoint is changed is learnt
  • the indication indicating that the network slice is changed is learnt.
  • the network slice mapping may be performed, in which a new network slice is reselected and the core network is informed of the newly-selected network slice.
  • the core network may trigger the UE to release the UE session with the data endpoint of the source network slice and to set up a UE session with a data endpoint of the target network slice.
  • the first node may configure the continuity operation information based on at least one piece of the continuity control information.
  • a correlative level of the continuity operation information configuration may be the UE, the UE session, the bearer (e.g., E-RAB or DRB), the QoS flow, or the service data flow.
  • the bearer e.g., E-RAB or DRB
  • the QoS flow e.g., the QoS flow
  • the service data flow e.g., the service data flow.
  • the first node may configure at least one of the following indications upon meeting at least one of the following conditions.
  • the indications include the handover indication, the handover-preparation indication, the no-release indication, the data-forwarding indication, the interoperable-operation-between-networks indication, the inter-network handover indication, the dual-attachments indication, and the indication indicating that the data endpoint is not changed.
  • the conditions include: service continuity mode one is learnt, service continuity mode two is learnt and the target node or the target cell belongs to the keeping service continuity area, service continuity mode two is learnt and the target node or the target cell belongs to the serving area of the data endpoint, service continuity mode three is learnt, it is learnt that the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, and it is learnt that the target node or the target cell does not belong to the access-permitted area.
  • the first node may configure at least one of the following indications upon meeting at least one of the following conditions.
  • the indications include the no-handover indication, the no-handover-preparation indication, a pre-handover release indication, a post-handover release indication, the release indication, the no-data-forwarding indication, the no-interoperable-operation-between-networks indication, the no-inter-network handover indication, and a no-dual-attachments indication.
  • the conditions include: service continuity mode two is learnt and the target node or the target cell does not belong to the keeping service continuity area, service continuity mode two is learnt and the target node or the target cell does not belong to the serving area of the data endpoint, it is learnt that the target node or the target cell belongs to the service-prohibited area, it is learnt that the target node or the target cell does not belong to the service-permitted area, and it is learnt that the target node or the target cell belongs to the access-prohibited area.
  • the first node may configure the indication indicating that the data endpoint is not changed when at least one of the following conditions is met:
  • service continuity mode one is learnt
  • service continuity mode two is learnt and the target node or the target cell belongs to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell belongs to the serving area of the data endpoint
  • service continuity mode three is learnt and the target node or the target cell belongs to the keeping service continuity area
  • service continuity mode three is learnt and the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, and it is learnt that the target node or the target cell does not belong to the access-prohibited area.
  • the first node may configure the indication indicating that the data endpoint is changed when at least one of the following conditions is met:
  • service continuity mode two is learnt
  • service continuity mode three is learnt
  • service continuity mode two is learnt and the target node or the target cell does not belong to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell does not belong to the serving area of the data endpoint
  • service continuity mode three is learnt and the target node or the target cell does not belong to the keeping service continuity area
  • service continuity mode three is learnt and the target node or the target cell does not belong to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, and it is learnt that the target node or the target cell does not belong to the access-prohibited area.
  • the first node may configure the indication indicating that the network slice is not changed when at least one of the following conditions is met:
  • service continuity mode one is learnt
  • service continuity mode two is learnt and the target node or the target cell belongs to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell belongs to the serving area of the data endpoint
  • service continuity mode three is learnt and the target node or the target cell belongs to the keeping service continuity area
  • service continuity mode three is learnt and the target node or the target cell belongs to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, and it is learnt that the target node or the target cell does not belong to the access-prohibited area.
  • the first node may configure the indication indicating that the network slice is changed when at least one of the following conditions is met:
  • service continuity mode two is learnt
  • service continuity mode three is learnt
  • service continuity mode two is learnt and the target node or the target cell does not belong to the keeping service continuity area
  • service continuity mode two is learnt and the target node or the target cell does not belong to the serving area of the data endpoint
  • service continuity mode three is learnt and the target node or the target cell does not belong to the keeping service continuity area
  • service continuity mode three is learnt and the target node or the target cell does not belong to the serving area of the data endpoint
  • the target node or the target cell belongs to the service-permitted area, it is learnt that the target node or the target cell does not belong to the service-prohibited area, and it is learnt that the target node or the target cell does not belong to the access-prohibited area.
  • the first node may configure the single-data-endpoint indication when at least one of the following conditions is met:
  • service continuity mode one is learnt
  • service continuity mode two is learnt
  • the first node may configure the multiple-data-endpoints indication when at least one of the following conditions is met:
  • service continuity mode three is learnt, and it is learnt that load balancing is required.
  • a correlative level of the continuity operation information may be the UE, the UE session, the bearer (e.g., E-RAB or DRB), the QoS flow, or the service data flow, e.g., continuity operation information at the UE session level.
  • a configured correlative level of the continuity operation information is a learnt correlative level of the continuity control information. For example, for service continuity mode one of a session, the indication information of the session about whether the handover is performed may be configured as the handover indication.
  • the method for controlling continuity of the UE may further include one of the following procedures:
  • the first node transmits at least one piece of continuity control information of the UE (as described in block 1001), the first node transmits at least one piece of configured data-controllable operation information (as described in block 1002), the first node transmits information of the correlative level performing the continuity control (the UE identifier information, the session information, the bearer information, the QoS flow information, the service data flow information as described in block 1001), the first node transmits information of the continuity control performed by the correlative level (for example, the continuity control of a UE session is no-handover, etc.), the first node transmits a reason for the continuity control performed by the correlative level (such as meeting a continuity control condition, for example, a reason why the continuity control of a UE session is not to be handed over).
  • a reason for the continuity control performed by the correlative level such as meeting a continuity control condition, for example, a reason why the continuity control of a UE session is not to be handed over.
  • the continuity control information of the corresponding UE transmitted by the first node may be the continuity control information learnt by the first node or at least one piece of data-controllable operation information configured by the first node. For example, according to a learnt service continuity mode, the first node may determine whether a network slice may be changed or mapped, and whether a data endpoint may be changed.
  • the first node may transmit the above-described information to at least one of the following: a third radio access network node (i.e., a radio access network node different from the first radio access network node and the second radio access network node), the radio access network node, the source radio access network node during the UE moving process, the target radio access network node during the UE moving process, a new radio access network node which the UE accesses under a light-connection mode or in an inactive state, an old radio access network node where the UE stores UE context under the light-connection mode or in the inactive state, a radio access network node suspending the UE, a radio access network node where the UE requests connection recovery, a radio access network node, a core network node, a data endpoint, and the UE.
  • a third radio access network node i.e., a radio access network node different from the first radio access network node and the second radio access network node
  • the radio access network node the
  • embodiments of the present disclosure propose a method for controlling continuity of the UE.
  • the first node may implement continuity control to the UE differentially according to different information corresponding to the UE, so as to save signaling overhead and reduce the delay for the UE accessing a network.
  • a UE moving process on the one hand, unnecessary resource allocation and data forwarding is reduced, and thus the handover process is accelerated; on the other hand, unnecessary interoperable operations between systems are reduced, so that the UE may access a new network system quickly; moreover, when the target cell does not support the current network slice, a service of the UE may be mapped to a network slice supported by the target cell according to a service type of the UE, and thereby the UE is served at full steam and serving experience of the UE is improved.
  • Example embodiments 1-6 are all about how a radio access network serving a UE obtains continuity control information about a UE session.
  • Example embodiments 3-4 embody handover control and data forwarding control.
  • Example embodiment 6 embodies release control.
  • Fig. 11 is a schematic flowchart of a method for controlling continuity of a UE, according to the first embodiment of the present disclosure.
  • a radio access network node obtains continuity control information about a UE session during a UE session setup process.
  • the method includes following procedures.
  • the UE sends a Radio Resource Control (RRC) message to the radio access network node, in which the message includes a UE session setup request.
  • RRC Radio Resource Control
  • the radio access network node sends an initial UE message or an uplink NAS transmission message to a core network node, in which the message includes the UE session setup request.
  • the core network sends an initial UE context setup request message or a PDU session setup request message to the radio access network.
  • the message includes continuity control information, as described in details of block 1001.
  • the radio access network node may perform corresponding continuity control, which may include at least one of the following: handover control, release control, data forwarding control, interoperable operation between networks control, network slice changing or mapping control, as described in details of block 1002.
  • the radio access network node configures a radio bearer about the UE session and transmits radio bearer configuration to the UE.
  • the UE returns a radio bearer configuration response to the radio access network node after completing the radio bearer configuration about the UE session.
  • the radio access network node returns an initial UE context setup response message or a PDU session setup response message to the core network.
  • Fig. 12 is a schematic flowchart of a method for controlling continuity of a UE, according to the second embodiment of the present disclosure.
  • a radio access network node obtains continuity control information about a UE session during a setup process or a recovery process of a connection between a UE and a network.
  • the method includes following procedures.
  • the UE sets up or recovers a Radio Resource Control (RRC) connection with the radio access network node.
  • RRC Radio Resource Control
  • the radio access network node sends an initial UE message to a core network control node.
  • the core network control node sends an initial context setup request message to the radio access network node.
  • the initial context setup request message may include continuity control information corresponding to the UE (the continuity control information may refer to details described in block 1001).
  • the radio access network node may perform continuity control, as described in details of block 1002.
  • the radio access network node performs RRC connection reconfiguration to the UE.
  • the radio access network node sends an initial context setup response message to the core network control node.
  • Fig. 13 is a schematic flowchart of a method for controlling continuity of a UE, according to the third embodiment of the present disclosure.
  • the third example embodiment is applied to a process in which a source radio access network node triggers handover between radio nodes when a UE is connected to the network.
  • the method includes following procedures.
  • the source radio access network node receives a measurement report of the UE.
  • the source radio access network node selects a target radio access network node as a target node.
  • the source radio access network node sends a handover request message to the target radio access network node.
  • the handover request message may include continuity control information corresponding to the UE (the continuity control information may refer to details described in block 1001).
  • the target radio access network node may perform continuity control, as described in details of block 1002.
  • the source radio access network node may not indicate a handover-preparation request, and the target radio access network node may not prepare radio resources for the session.
  • the target radio access network node returns a handover request confirming message to the source radio access network node.
  • the source radio access network node sends a handover command message to the UE.
  • the UE accesses the target radio access network node.
  • the target radio access network node sends a path conversion request message to the core network.
  • the path conversion request message includes session information of a session requested to be released (the session information may refer to details described in block 1001).
  • the session requested to be released may be a session received at block 602 indicating no-handover-preparation, which may refer to the handover control described in block 1002, and is not described repeatedly herein.
  • the target radio access network node sends a path conversion request confirming message to the core network.
  • the message may include continuity control information corresponding to the UE (the continuity control information may refer to details described in block 1001).
  • the target radio access network node may perform continuity control, as described in details of block 1002.
  • the target radio access network node sends a UE context release request message to the source radio access network node.
  • the source radio access network node sends a UE context release response message to the target radio access network node.
  • Fig. 14 is a schematic flowchart of a method for controlling continuity of a UE, according to the fourth embodiment of the present disclosure.
  • the fourth example embodiment is applied to a process in which the handover is performed through a core network.
  • the method includes following procedures.
  • a source radio access network node receives a measurement report of the UE.
  • the source radio access network node selects a target radio access network node as a target node.
  • the source radio access network node sends a handover request message to the core network.
  • the message may include continuity control information corresponding to the UE (the continuity control information may refer to details described in block 1001).
  • the target radio access network node may perform continuity control, as described in details of block 1002.
  • the source radio access network node may not indicate a handover-preparation request, and the target radio access network node may not prepare radio resources for the session.
  • the core network sends a handover request message to the target radio access network node.
  • the source radio access network node may not indicate a handover-preparation request, and the target radio access network node may not prepare radio resources for the session.
  • the message may include continuity control information corresponding to the UE (the continuity control information may refer to details described in block 1001).
  • the target radio access network node may perform continuity control, as described in details of block 1002.
  • the target radio access network node returns a handover request confirming message to the core network.
  • the core network returns a handover command message to the source radio access network node.
  • the source radio access network node sends a handover command message to the UE.
  • the UE accesses the target radio access network node.
  • the target radio access network node sends a handover completion notification message to the core network.
  • the message includes session information of a session requested to be released (the session information may refer to details described in block 1001).
  • the session requested to be released may be a session received at block 1402 indicating no-handover-preparation, which may refer to the handover control described in block 1002, and is not described repeatedly herein.
  • the core network sends a UE context release request message to the source radio access network node.
  • the source radio access network node sends a UE context release response message to the core network.
  • Fig. 15 is a schematic flowchart of a method for controlling continuity of a UE, according to the fifth embodiment of the present disclosure.
  • a new radio access network node obtains continuity control information about the UE from an old radio access network node during a UE connection recovery process.
  • the method includes following procedures.
  • the UE sends a RRC connection recovery request to the new radio access network node.
  • the new radio access network node sends a UE context obtaining request message to the old radio access network node.
  • the old radio access network node returns a UE context obtaining response message to the new radio access network node.
  • the message may include continuity control information corresponding to the UE (the continuity control information may refer to details described in block 1001).
  • the radio access network node may perform continuity control, as described in details of block 1002.
  • the new radio access network node returns a RRC connection recovery response to the UE.
  • the new radio access network node sends a path conversion request to the core network.
  • the new radio access network node sends a path conversion request confirming message to the core network.
  • the message may include continuity control information corresponding to the UE (the continuity control information may refer to details described in block 1001).
  • the new radio access network node may perform continuity control, as described in details of block 1002.
  • the new radio access network node sends a UE context release request message to the old radio access network node.
  • the source radio access network node sends a UE context release response message to the old radio access network node.
  • Fig.16 is a schematic flowchart of a method for controlling continuity of a UE, according to the sixth embodiment of the present disclosure.
  • a UE session is released based on obtained continuity control information about the UE during a UE moving process.
  • the method includes following procedures.
  • a source radio access network node receives a measurement report of the UE.
  • the source radio access network node selects a target radio access network node.
  • the source radio access network node sends a PDU session release request message to a core network node.
  • the message includes session information of a session requested to be released (the session information may refer to details described in block 1001).
  • the session requested to be released may be a session learnt to indicate no-handover-preparation or pre-handover release, which may refer to the handover control described in block 1002, and is not described repeatedly herein.
  • the core network node sends a PDU session release response message to the source radio access network node.
  • the source radio access network node sends a handover request message to the target radio access network node. Subsequent unrelated procedures are omitted.
  • service continuity operations can be configured or appropriate continuity control operations can be performed.
  • unnecessary resource allocation and data forwarding is reduced, and thus the handover process is accelerated; on the other hand, unnecessary interoperable operations between systems are reduced, so that the UE may access a new network system quickly; moreover, when the target cell does not support the current network slice, a service of the UE may be mapped to a network slice supported by the target cell according to a service type of the UE, and thereby the UE is served at full steam and serving experience of the UE is improved.
  • embodiments of the present disclosure also propose an apparatus for controlling continuity of the UE, which may be a core network device.
  • the apparatus includes an information receiving module 1701 and a control module 1702.
  • the information receiving module 1701 is configured to receive, through a node, at least one kind of continuity control information corresponding to the UE; the control module 1702 is configured to perform, based on the continuity control information, corresponding continuity control to the UE through a core network node.
  • the above-described apparatus for controlling continuity of the UE may further include an information sending module 1703, which is configure to send the continuity control information corresponding to the UE to a remote end through the node, in which information included in the continuity control information may refer to details described in block 1701 and is not described repeatedly herein.
  • each module in the apparatus for controlling continuity of the UE may refer to details in blocks 1701 and 1702 described above, and is not described repeatedly herein.
  • the programs running on the device according to the present disclosure may be programs that enable the computer to implement functions of the embodiments of the present disclosure by controlling a central processing unit (CPU).
  • the programs or information processed by the programs may be temporarily stored in a volatile memory, such as a random access memory (RAM), a hard disk drive (HDD), a non-volatile memory (e.g., flash memory), or other memory system.
  • RAM random access memory
  • HDD hard disk drive
  • non-volatile memory e.g., flash memory
  • the programs for realizing the functions of the embodiments of the present disclosure may be recorded on a computer-readable recording medium. Corresponding functions can be realized by making the computer system read the programs recorded on the recording medium and execute these programs.
  • the so-called “computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware, such as a peripheral device.
  • the "computer-readable recording medium” may be a semi-conductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium for a short-time dynamic storage program, or any other computer readable recording medium.
  • circuitry e.g., monolithic or multi-chip integrated circuits.
  • the circuitry designed to perform the functions described in this specification may include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices.
  • the general purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the circuit may be a digital circuit or an analog circuit.
  • One or more embodiments of the present disclosure may also be implemented using these new integrated circuit techniques in the event of a new integrated circuit technology that replaces existing integrated circuits due to advances in semiconductor technology.

Landscapes

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

Abstract

La présente invention concerne un système de communication pré-5ème génération (5G) ou 5G permettant de prendre en charge des débits de données plus élevés, au-delà d'un système de communication de 4ème génération (4G) tel que LTE (évolution à long terme). Selon certains modes de réalisation, la présente invention concerne un procédé de commande de transmission de données et un dispositif permettant de mettre en oeuvre le procédé. Le procédé consiste à : obtenir des informations sur des données d'UE et/ou un contexte d'UE; et effectuer une commande pour la transmission des données d'UE, selon les informations obtenues sur les données d'UE et/ou le contexte d'UE. Selon certains modes de réalisation, la présente invention concerne en outre un autre procédé de commande d'état de transmission de données et un dispositif permettant de mettre en oeuvre le procédé. Le procédé consiste à : déterminer si une condition prédéterminée de transmission de données est satisfaite; et transmettre des informations sur des données d'UE et/ou un contexte d'UE, lorsqu'il est déterminé que la condition prédéterminée est satisfaite. Selon certains modes de réalisation, la présente invention concerne également un procédé et un appareil permettant de commander la continuité d'UE.
PCT/KR2018/001574 2017-02-06 2018-02-06 Procédé et dispositif de commande de transmission de données, procédé et appareil de commande de continuité d'ue WO2018143769A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710067271.2A CN108616944A (zh) 2017-02-06 2017-02-06 对用户设备进行连续性控制的方法及相应设备
CN201710067271.2 2017-02-06
CN201710187207.8 2017-03-24
CN201710187207.8A CN108924826B (zh) 2017-03-24 2017-03-24 数据传送的控制方法及设备

Publications (1)

Publication Number Publication Date
WO2018143769A1 true WO2018143769A1 (fr) 2018-08-09

Family

ID=63040906

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/001574 WO2018143769A1 (fr) 2017-02-06 2018-02-06 Procédé et dispositif de commande de transmission de données, procédé et appareil de commande de continuité d'ue

Country Status (1)

Country Link
WO (1) WO2018143769A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI718874B (zh) * 2019-02-18 2021-02-11 聯發科技股份有限公司 檢查配置給使用者設備的參數錯誤的方法及裝置
WO2022151917A1 (fr) * 2021-01-15 2022-07-21 大唐移动通信设备有限公司 Procédé et appareil de traitement de message, terminal et dispositif côté réseau
RU2805981C1 (ru) * 2020-04-03 2023-10-24 Гуандун Оппо Мобайл Телекоммьюникейшнз Корп., Лтд. Способ беспроводной связи, оконечное устройство и сетевое устройство

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170013515A1 (en) * 2014-05-08 2017-01-12 Intel IP Corporation User equipment and methods to indicate power saving mode configuration to ran nodes

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170013515A1 (en) * 2014-05-08 2017-01-12 Intel IP Corporation User equipment and methods to indicate power saving mode configuration to ran nodes

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Baseline solution for small data transmission in RRC_INACTIVE", R2-168713, 3GPP TSG RAN WG2 MEETING #96, 5 November 2016 (2016-11-05), Reno, Nevada, USA, XP051193201 *
HUAWEI ET AL.: "Data transmission in inactive state, option A vs. option B", R2-1700188, 3GPP TSG RAN WG2 #ADHOC, 7 January 2017 (2017-01-07), Spokane(WA), USA, XP051203894 *
NOKIA ET AL.: "Data transmission in INACTIVE", R2-167706, 3GPP TSG RAN WG2 MEETING #96, 4 November 2016 (2016-11-04), Reno, USA, XP051192252 *
ZTE: "Handling token and key derivation for data transmitting in RRC_INACTIVE", 3GPP TSG SA WG3 (SECURITY) MEETING #86, 1 February 2017 (2017-02-01), Sophia Antipolis, France, pages 3 - 170106, XP051228839 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI718874B (zh) * 2019-02-18 2021-02-11 聯發科技股份有限公司 檢查配置給使用者設備的參數錯誤的方法及裝置
RU2805981C1 (ru) * 2020-04-03 2023-10-24 Гуандун Оппо Мобайл Телекоммьюникейшнз Корп., Лтд. Способ беспроводной связи, оконечное устройство и сетевое устройство
WO2022151917A1 (fr) * 2021-01-15 2022-07-21 大唐移动通信设备有限公司 Procédé et appareil de traitement de message, terminal et dispositif côté réseau

Similar Documents

Publication Publication Date Title
WO2018111030A1 (fr) Procédé destiné à exécuter un transfert intercellulaire dans un système de communication sans fil et appareil associé
WO2020204501A1 (fr) Procédé de prise en charge d'accès à un réseau fermé, ue, station de base et support d'enregistrement lisible
WO2019031901A1 (fr) Procédé et dispositif pour exploiter et commander un flux de données
WO2018062949A1 (fr) Procédé et appareil d'établissement de double connectivité pour transmettre des données dans une nouvelle architecture de communication radio
EP3516922A1 (fr) Procédé et appareil d'établissement de double connectivité pour transmettre des données dans une nouvelle architecture de communication radio
EP3479647A1 (fr) Procédé d'établissement d'une interface fronthaul, procédé de mise en uvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en uvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base
WO2019031915A1 (fr) Procédé et dispositif d'établissement de connectivité double
EP3639615A1 (fr) Appareil et procédé de gestion de connexions dans un système de communication sans fil
EP3443805A1 (fr) Procédé et appareil de commande de connexion légère
WO2017039042A1 (fr) Procédé et dispositif de transmission/réception de données de terminal dans un système de communication sans fil
EP3610675A1 (fr) Appareil et procédé permettant de réaliser un transfert dans un système de communication sans fil
WO2021054770A1 (fr) Procédé et dispositif de commande de débit de données dans un système de communication sans fil
WO2021006691A1 (fr) Procédé et dispositif de routage de paquet de données, et procédé et dispositif de commande de transmission de paquet de données
WO2018203739A1 (fr) Procédé d'établissement d'une interface fronthaul, procédé de mise en œuvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en œuvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base
WO2018203734A1 (fr) Appareil et procédé permettant de réaliser un transfert dans un système de communication sans fil
WO2021066515A1 (fr) Nœud principal, nœud secondaire et équipement d'utilisateur dans un réseau de communication mobile et leurs procédés de communication entre eux
WO2019031941A1 (fr) Procédé permettant de prendre en charge un transfert intercellulaire et appareil correspondant
WO2018230982A1 (fr) Appareil et procédé de gestion de connexions dans un système de communication sans fil
WO2017196161A1 (fr) Procédé et appareil de commande de connexion légère
WO2021025308A1 (fr) Procédé de traitement d'amf pour prendre en charge de multiples usim
WO2019177397A1 (fr) Procédé et appareil permettant d'établir support radio
EP3424237A1 (fr) Procédé destiné à commander l'agrégation de réseau local sans fil et équipement associé
WO2022231231A1 (fr) Procédé et dispositif de prise en charge d'un transfert
WO2018030826A1 (fr) Procédé de commande d'un équipement d'utilisateur
WO2022086233A1 (fr) Procédé et dispositif de transmission de multidiffusion

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

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

Country of ref document: EP

Kind code of ref document: A1