WO2023001353A1 - Stockage d'informations persistantes d'ue à travers des transitions d'états de gestion de connexions (cm) - Google Patents

Stockage d'informations persistantes d'ue à travers des transitions d'états de gestion de connexions (cm) Download PDF

Info

Publication number
WO2023001353A1
WO2023001353A1 PCT/EP2021/070096 EP2021070096W WO2023001353A1 WO 2023001353 A1 WO2023001353 A1 WO 2023001353A1 EP 2021070096 W EP2021070096 W EP 2021070096W WO 2023001353 A1 WO2023001353 A1 WO 2023001353A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
context
session
database
identifier
Prior art date
Application number
PCT/EP2021/070096
Other languages
English (en)
Inventor
Bahare MASOOD KHORSANDI
Ömer BULAKCI
Subramanya CHANDRASHEKAR
Mu HE
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2021/070096 priority Critical patent/WO2023001353A1/fr
Publication of WO2023001353A1 publication Critical patent/WO2023001353A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present disclosure relates to UE context in relation state transitions (in particular CM state transitions).
  • the NG control plane interface (NG-C) is defined as an interface between the NG-RAN node and the AMF over N2 interface.
  • the NG interface supports the UE Context Management function which allows the AMF to establish, modify or release a UE Context in the AMF and the NG-RAN node, e.g. to support user associated signaling on NG-C.
  • the corresponding procedures are defined:
  • the Connection Management (CM) procedure comprises the functions of establishing and releasing a NAS signaling connection between a UE and the AMF over N1 interface. It comprises both the access network (AN) signaling connection between the UE and the AN (e.g., RRC Connection over 3GPP access) and the N2 connection for this UE between the AN and the AMF.
  • AN access network
  • Two CM states are used to reflect the NAS signaling connection of the UE with the AMF:
  • CM-IDLE A UE in a CM-IDLE state has no NAS signaling connection established with the AMF over N1 interface. There are no AN signaling connections, N2 connection, and N3 connections for the UE in the CM-IDLE state. In the CM-IDLE state, the UE is in the RRC IDLE state in the AN.
  • CM-CONNECTED A UE in a CM-CONNECTED state has a NAS signaling connection with the AMF over N1 interface.
  • a NAS signaling connection uses an RRC Connection between the UE and the NG-RAN and an NGAP UE association between the AN and the AMF for 3GPP access.
  • the UE In the CM- CONNECTED state, the UE is either in RRC CONNECTED state or RRC INACTIVE state in the AN.
  • a UE/user needs to register with the network to receive services that require registration. Once registered, and if applicable, the UE updates its registration with the network.
  • the Registration Management is used to register or deregister a UE/user with the network and establish the UE context in the network.
  • Two RM states are used in the UE and the AMF to reflect the registration status of the UE in the network (PLMN):
  • RM-DEREGISTERED In this state, the UE is not registered with the network.
  • the UE context in AMF holds no valid location or routing information for the UE so the UE is not reachable by the AMF.
  • RM-REGISTERED In this state, the UE is registered with the network and can receive services that require registration with the network.
  • the UE shall not be in CM-IDLE state and in RM-REGISTERED state, the UE shall
  • NG-RAN node UE context is a collection of information in an NG-RAN node associated with one UE, which contains the necessary information required to maintain the NG-RAN services towards the UE in a CONNECTED state. This includes UE’s identifiers and those allocated by network, PDU session details, user plane tunnel addresses and other user session information.
  • the UE context also includes some capability information and intelligence generated by network pertaining to that UE.
  • the NG-RAN node UE context is created when the UE transitions to RRC CONNECTED for the first time. During handover preparation, the UE context is passed to the target NG-RAN node.
  • a similar UE context is stored in the UE as well, albeit not all information in the UE context stored in NG-RAN is typically stored in the UE.
  • the respective UE context is released in both network and the UE whenever the UE transitions from CM-CONNECTED to CM- IDLE.
  • N1 interface is an interface from 5G-UE to AMF of core (via NG-RAN).
  • N1 interface is transparent for NG-RAN.
  • an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform: monitoring if a terminal transits from a connected state into an idle state, wherein a terminal context is related to the terminal in the connected state, and the terminal context comprises a session-related portion and a session-unrelated portion different from the session-related portion; storing the terminal context for the terminal into a database while the terminal is in the connected state or when the terminal transits from the connected state into the idle state; maintaining at least a part of the session-unrelated portion of the terminal context for the terminal in the database if the terminal transits from the connected state into the idle state; wherein each of the connected state and the idle state is a respective state of a connection management for the terminal.
  • an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform: supervising if a terminal transits from an idle state into a connected state, wherein a terminal context is to be related to the terminal in the connected state, and the terminal context comprises a session-related portion and a session-unrelated portion different from the session-related portion; retrieving at least a part of the session-unrelated portion of the terminal context for the terminal from a database if the terminal transits from the idle state into the connected state; applying the retrieved at least part of the session-unrelated portion of the terminal context to the connected state of the terminal if the terminal transits from the idle state into the connected state; wherein each of the connected state and the idle state is a respective state of a connection management for the terminal.
  • an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform: storing a terminal context associated with a context key for a terminal in a first database, wherein the terminal context is received from a first instance of a network function, the terminal context is related to the terminal in a connected state, and the terminal context comprises a session-related portion and a session-unrelated portion different from the session-related portion; receiving a first request from a second instance of the network function, including a context key, to provide at least a part of the session-unrelated portion of the terminal context for the terminal; providing at least the part of the session-unrelated portion of the terminal context for the terminal, associated with the context key, to the second instance of the network function in response to receiving the first request.
  • an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform: supervising if a first database receives a request to provide at least a part of a session-unrelated portion of a terminal context associated with a given context key for a terminal, wherein the terminal context is related to the terminal in a connected state, and the terminal context comprises a session-related portion and the session-unrelated portion different from the session-related portion; checking, based on the given context key, if the first database stores at least the part of the session-unrelated portion of the terminal context for the terminal if the first database receives the request; querying a global database, based on the given context key, for an identification of a second database storing at least the part of the session-unrelated portion of the terminal context for the terminal if the first database does not store at least the part of the session-unrelated portion of the terminal context for the terminal; receiving at least the part of
  • an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform: monitoring if a query for an identification of a second database is received from a first database based on at least a context key or a cell id, wherein the second database stores at least a part of a session-unrelated portion of a terminal context for a terminal, the terminal context is related to the terminal in a connected state, and the terminal context comprises a session-related portion and the session-unrelated portion different from the session-related portion; causing a transfer of at least the part of the session-unrelated portion of the terminal context for the terminal from the second database to the first database if the query is received from the first database.
  • an apparatus comprising: one or more processors, and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform: supervising if a terminal in a connected state receives an identifier from a network function, wherein a terminal context is related to the terminal in the connected state, and the identifier is related to the terminal context; instructing the terminal to store the identifier if the terminal receives the identifier; monitoring if the terminal decides to send a connection request to transit from an idle state to the connected state; providing the identifier to the network function if the terminal sends the connection request; each of the connected state and the idle state is a respective state of a connection management for the terminal.
  • a method comprising: monitoring if a terminal transits from a connected state into an idle state, wherein a terminal context is related to the terminal in the connected state, and the terminal context comprises a session-related portion and a session-unrelated portion different from the session-related portion; storing the terminal context for the terminal into a database while the terminal is in the connected state or when the terminal transits from the connected state into the idle state; maintaining at least a part of the session-unrelated portion of the terminal context for the terminal in the database if the terminal transits from the connected state into the idle state; wherein each of the connected state and the idle state is a respective state of a connection management for the terminal.
  • a method comprising: supervising if a terminal transits from an idle state into a connected state, wherein a terminal context is to be related to the terminal in the connected state, and the terminal context comprises a session-related portion and a session-unrelated portion different from the session-related portion; retrieving at least a part of the session-unrelated portion of the terminal context for the terminal from a database if the terminal transits from the idle state into the connected state; applying the retrieved at least part of the session-unrelated portion of the terminal context to the connected state of the terminal if the terminal transits from the idle state into the connected state; wherein each of the connected state and the idle state is a respective state of a connection management for the terminal.
  • a method comprising: storing a terminal context associated with a context key for a terminal in a first database, wherein the terminal context is received from a first instance of a network function, the terminal context is related to the terminal in a connected state, and the terminal context comprises a session-related portion and a session-unrelated portion different from the session-related portion; receiving a first request from a second instance of the network function, including a context key, to provide at least a part of the session-unrelated portion of the terminal context for the terminal; providing at least the part of the session-unrelated portion of the terminal context for the terminal, associated with the context key, to the second instance of the network function in response to receiving the first request.
  • a method comprising: supervising if a first database receives a request to provide at least a part of a session-unrelated portion of a terminal context associated with a given context key for a terminal, wherein the terminal context is related to the terminal in a connected state, and the terminal context comprises a session-related portion and the session-unrelated portion different from the session-related portion; checking, based on the given context key, if the first database stores at least the part of the session-unrelated portion of the terminal context for the terminal if the first database receives the request; querying a global database, based on the given context key, for an identification of a second database storing at least the part of the session-unrelated portion of the terminal context for the terminal if the first database does not store at least the part of the session-unrelated portion of the terminal context for the terminal; receiving at least the part of the session-unrelated portion of the terminal context for the terminal from the second database.
  • a method comprising: monitoring if a query for an identification of a second database is received from a first database based on at least a context key or a cell id, wherein the second database stores at least a part of a session-unrelated portion of a terminal context for a terminal, the terminal context is related to the terminal in a connected state, and the terminal context comprises a session-related portion and the session-unrelated portion different from the session-related portion; causing a transfer of at least the part of the session-unrelated portion of the terminal context for the terminal from the second database to the first database if the query is received from the first database.
  • a method comprising: supervising if a terminal in a connected state receives an identifier from a network function, wherein a terminal context is related to the terminal in the connected state, and the identifier is related to the terminal context; instructing the terminal to store the identifier if the terminal receives the identifier; monitoring if the terminal decides to send a connection request to transit from an idle state to the connected state; providing the identifier to the network function if the terminal sends the connection request; each of the connected state and the idle state is a respective state of a connection management for the terminal.
  • Each of the methods of the seventh to twelfth aspect may be a method of terminal context storage.
  • a computer program product comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out the method according to any of the seventh to twelfth aspects.
  • the computer program product may be embodied as a computer-readable medium or directly loadable into a computer.
  • • signaling load may be reduced or offloaded as a background task; • session independent information for the UE does not get lost and may be applied whenever appropriate, regardless of the UE’s state transitions.
  • Fig. 1 shows a RAN DB implementation
  • Fig. 2 shows a message flow according to some example embodiments of the invention
  • Fig. 3 shows a hierarchical database design according to some example embodiments of the invention
  • Fig. 4 shows an apparatus according to an example embodiment of the invention
  • Fig. 5 shows a method according to an example embodiment of the invention
  • Fig. 6 shows an apparatus according to an example embodiment of the invention
  • Fig. 7 shows a method according to an example embodiment of the invention
  • Fig. 8 shows an apparatus according to an example embodiment of the invention
  • Fig. 9 shows a method according to an example embodiment of the invention.
  • Fig. 10 shows an apparatus according to an example embodiment of the invention
  • Fig. 11 shows a method according to an example embodiment of the invention
  • Fig. 12 shows an apparatus according to an example embodiment of the invention.
  • Fig. 13 shows a method according to an example embodiment of the invention
  • Fig. 14 shows an apparatus according to an example embodiment of the invention
  • Fig. 15 shows a method according to an example embodiment of the invention
  • Fig. 16 shows an apparatus according to an example embodiment of the invention.
  • the apparatus is configured to perform the corresponding method, although in some cases only the apparatus or only the method are described.
  • RAN Database (hereafter RAN DB, also known as AN DB) is a context storage shared by a set of NG-RAN nodes and AMFs, e.g., in the same target area or geographical area.
  • the RAN DB may be implemented as a central entity or multiple local entities with a central entity co-ordinating them. The usefulness is when data stored by one entity is retrieved by another entity by providing the same key.
  • the storing and retrieving entities could be NG-RAN nodes, AMFs or one of the logical components of those nodes.
  • Fig. 1 shows an example of a RAN DB, wherein the RAN DB is connected to two gNBs and three AMFs.
  • the UE context needs to be created fora regular operation of the UE, e.g., related to the handling of the sessions of the UE according to the UE subscription and profile. Subsequent state transitions for each individual UE may happen several times between CM-IDLE and CM- CONNECTED and back, and each time when the UE transitions to CM-CONNECTED state, a new connection to NG-RAN node (hereafter gNB) and registration request toward AMF is required.
  • gNB NG-RAN node
  • UE context information can be divided into two main categories:
  • UE Connection Context which is regarding the establishment of the UE connection such as UE identifiers, UE capability, PDU sessions IDs, allowed NSSAI, etc.);
  • UE Historical Intelligence is the information generated based on the use cases such as SON applications and AI/ML solutions and used to identify and optimize service for UE groups, such as UE trajectory, power-related, mobility-related behaviors or patterns, etc.
  • the difference between the UE connection context and the historical intelligence is that the former is session related which includes dynamic resource allocation in each logical entity like UE identifiers, network addresses and identifiers, tunnel end-point identifiers, UE’s DRB info, etc.
  • the latter is kind of semi-static information like UE mobility history information, UE power related data/inference, intelligence built based on UE/network reporting/monitoring, n/w algorithm information applicable to the UE etc.
  • the UE historical intelligence is assumed to be built over a longer period of time and maybe used by the network whenever the UE enters CONNECTED mode.
  • the historical intelligence may be a part of other information stored in the context which is not related to a particular user session.
  • This part is also called a general (or session-unrelated) portion of the respective UE context.
  • the UE connection context and the session-unrelated portion jointly make up the UE context information.
  • the UE context information may consist of the session-related portion and the session-unrelated portion.
  • historical intelligence may be read as a pars pro toto for the session-unrelated portion.
  • O-RAN Open-Radio Access Networks
  • the O-RAN system architecture can include an automation part that consists of a Near-Real-time (Near-RT) RAN Intelligence Controller (RIC) within the RAN and a Non-RT RIC within Service Management and Orchestration (SMO).
  • Near-RT Near-Real-time
  • RIC RAN Intelligence Controller
  • SMO Service Management and Orchestration
  • the Near-RT may connect via an E2 interface to the 3GPP RAN, e.g., 5G standalone architecture with split RAN (CU/DU-split), where the RAN nodes are called E2 Nodes.
  • the Non-RT RIC may reside in service management & orchestration (SMO).
  • SMO service management & orchestration
  • the Non-RT RIC may perform non-real-time operations and may (through the A1 interface) communicate with Near-RT RIC over a defined A1 interface.
  • the Non-RT RIC may modify internal applications at the Non-RT RIC or Near-RT RIC.
  • the Non-RT RIC 330 may monitor, analyze, and feedback on the Near-RT RIC state; provide enrichment information; and facilitate, train, and distribute machine learning (ML) models for previous tasks.
  • ML machine learning
  • the Near-RT RIC may, through the E2 interface, communicate with one or more E2 Nodes, such as E2 node (open control unit (O-CU) control plane (O-CU-CP), O-CU user plane (O-CU-UP), open distributed unit (O-DU), and open evolved NodeB (O-eNB)) for time sensitive management and control of the radio resources, such as interference management, handover management, Quality of Service (QoS) management, and radio connection management.
  • E2 node open control unit (O-CU) control plane (O-CU-CP), O-CU user plane (O-CU-UP), open distributed unit (O-DU), and open evolved NodeB (O-eNB)
  • E2 node open control unit (O-CU) control plane (O-CU-CP), O-CU user plane (O-CU-UP), open distributed unit (O-DU), and open evolved NodeB (O-eNB)
  • E2 node open control unit (O-CU) control plane (O-CU-CP), O-CU user plane
  • the intelligence generated at RAN or RIC, based on AI/ML methods and employed for optimization algorithms in RAN is not stored in the AMF UE context. Hence this cannot be retrieved from the CN when a UE transitions to CM-CONNECTED from CM-IDLE subsequently.
  • the network does not store the UE context when a UE is transitioned to IDLE mode. Whenever UE changes its status to CM-IDLE and comes back to CM- CONNECTED, gNB creates UE Connection Context. On the other hand, the UE Historical Intelligence is lost as a result of the previous status change of UE from CM- CONNECTED to CM-IDLE and it is not maintained in the CM-IDLE mode. It cannot be retrieved when the UE comes back to CM-CONNECTED and has to be regenerated in the new session, which takes quite a long time.
  • Some example embodiments of the invention address the issue of data loss during multiple UE state transitions.
  • the UE context which includes both UE Historical Intelligence and UE Connection Context data, is stored in the RAN DB.
  • NG- RAN node and/or AMF may retrieve the UE context (at least the UE historical intelligence) from the RAN DB whenever the UE transitions from CM-IDLE to CM- CONNECTED.
  • the UE context is stored or updated in the RAN DB in the subsequent CONNECTED to IDLE state transitions as well.
  • one or more (if not all) of the functions are defined as a service-based (SB) architecture (SBA) which can be implemented in a cloud-based platform and utilizes service-based interfaces (SBI) for exposing and accessing the defined and/or implemented services (see, e.g., 3GPP TS 23.501]
  • SBA service-based
  • core network functions such as the network slice selection function (NSSF), network exposure function (NEF), policy control function (PCF), and the like.
  • NSSF network slice selection function
  • NEF network exposure function
  • PCF policy control function
  • NFs network functions
  • NFs network functions
  • a network function may provide a service, such as a service provider as well as consume services, such as a service consumer.
  • the network function may expose its services through a Service Based Interface (SBI) that employs a well-defined interface application programming interface (API), such as a REST API using a cloud-friendly transfer protocol, such as HTTP(S) (also referred to an SBI messaging bus).
  • SBI Service Based Interface
  • API application programming interface
  • HTTP(S) also referred to an SBI messaging bus
  • NRF network repository function
  • NRF network repository function
  • the network function (NF) service is one type of capability exposed by an NF (e.g., a NF service producer) to other authorized NFs (NF service consumers) through a service-based interface (SBI) as described in for example 3GPP TS 23.501.
  • the NF may expose one or more NF services.
  • NF services may communicate directly between NF Service Consumers and NF Service Producers, or indirectly via a Service Communication Proxy (SCP).
  • SCP Service Communication Proxy
  • the access network (AN) such as a radio access network (RAN)
  • RAN radio access network
  • the associated interfaces within the access network and between the access network and the core network (CN) may continue to be defined in terms of legacy point- to-point (P2P) interfaces, rather than in accordance with a service-based architecture.
  • the ORAN also employs peer-to-peer (P2P) interfaces, such as the E2 interface towards E2 Nodes, rather than a service-based architecture including service- based interfaces (
  • the N2 interface 112 is a 3GPP NG-C Application Protocol over stream control transmission protocol (SCTP), and is between RAN (e.g., a gNB) and an Access and Mobility management Function (AMF) in the core network.
  • SCTP 3GPP NG-C Application Protocol over stream control transmission protocol
  • AMF Access and Mobility management Function
  • P2P point-to-point
  • gNBs point-to-point interfaces
  • CU-CP Centralized Unit Control Plane
  • CU-UP Centralized Unit User Plane
  • the RAN DB may be employed as a data storage function (DSF) as part of service based architecture in RAN, referred to as service-based RAN (SB-RAN) herein.
  • DSF data storage function
  • SB-RAN service-based RAN
  • overall system architecture and framework can include Service-Based Interfaces (SBI) between (R)AN and CN, and within (R)AN.
  • SBI Service-Based Interfaces
  • An SB-RAN architecture can comprise AN elements, such as RAN NFs belonging to a 3GPP and O-RAN.
  • Such SB-RAN architecture may be referred to as a unified SB-(R)AN architecture.
  • one of the proposed functions is AN Data Storage Function (AN-DSF) which is a database that can be implemented in a centralized way, e.g., AN-DSF for multiple AN nodes, or a distributed way, e.g., AN node DSF. It proposes a Data Storage service that involves a DB to store data (e.g., UE context data) that may be accessible to any authorized network function (NF).
  • AN-DSF AN Data Storage Function
  • a data storage function having a service-based interface (SBI).
  • the DSF is a (R)AN element (function, or node), in which case it is referred to as a (R)AN-DSF.
  • the (R)AN DSF may be used to retrieve (e.g., fetch), store, and update a UE’s context information. These operations may be performed by any authorized network function (NF), such as a source gNB base station, a target gNB base station, Near-RT RIC, and/or other network functions or entities in the (R)AN and/or core and/or another domain, e.g., network management or service domain.
  • NF authorized network function
  • the DSF may be accessed by an authorized entity to store a UE’s context information. Moreover, the UE context information at the DSF may be accessed for updating in case of an event occurrence requiring an update on one or more pieces of UE context information or for retrieving in case of an event occurrence requiring the presence one or more pieces of UE context information.
  • the DSF may provide UE context storage, update, fetch and any other operation that may provide efficient handling of UE context information in the network.
  • the RAN-DSF may be implemented as part of a data storage architecture that may include one or more elements (e.g., functions or nodes).
  • a RAN data storage architecture may include a RAN-DSF, a data repository, and/or a data management entity.
  • different deployment options may be implemented, where the elements may be collocated.
  • the elements of the data storage architecture may perform storage and retrieval of data, such as UE context information.
  • the authorized and registered (R)AN elements may subscribe, via the SBI, to the (R)AN DSF’s UE context service with the associated (R)AN element ID, e.g., gNB ID and/or E2 Node ID.
  • the context service at the DSF is responsible for handling registration, subscription, retrieval, and/or publication of UE context information.
  • the authorization may be performed by the RAN DSF or another NF, e.g., network repository function, which can be in RAN.
  • the NF profiles and the associated authorized services may be pre-configured.
  • the authorization can be based on, e.g., operator configurations and/or network management configurations, such as OAM.
  • the UE Connection Context can also be useful in a subsequent session, e.g., in case of stationary UEs that are associated with certain slices or services. For such UEs, some information in the connection context could be more deterministic over certain time period.
  • the NG-RAN node and/or AMF may retrieve at least some part of the UE connection context, too. b.
  • a UE persistent identifier which remains same across one or more state transitions (e.g.: Masked IMEI or its derivative, S-TMSI, GUTI, etc.) is used as a key to index the UE context stored in RAN DB so that the context retrieval can be performed from anywhere in the RAN.
  • a network allocated identifier (e.g.: AMF ID + AMF UE NGAP ID) is sent to the UE while it is in CM-CONNECTED mode and the UE is asked to remember and return it whenever the UE returns from CM-IDLE to CM-CONNECTED mode.
  • Some example embodiments of the invention address the problem of UE context transfer in case of a UE entering CM-CONNECTED mode from CM-IDLE mode.
  • the UE context storage is performed only after the UE’s first network access, i.e. its first state transition to CM-CONNECTED mode.
  • UE context retrieval is only possible after the UE context has been stored for the first time.
  • UE Context retrieval when UE changes its status from CM-IDLE to CM- Connected, after having gone from CONNECTED to IDLE, is illustrated at greater detail hereinafter.
  • the RAN DB may be connected to a single gNB and/or to a single AMF. Having a shared database between the gNBs and AMFs can help to facilitate the storage and retrieval of UE Context information.
  • the serving gNBs and AMFs may add/update the respective UE context in the RAN DB.
  • a UE may have information stored by both NG RAN and AMF in the same or different UE context (depending on the context key used) which can be later retrieved by the corresponding entities by providing the same context key.
  • Fig. 2 shows a call flow of the UE context retrieval in case of a state transition of a UE according to some example embodiments of the invention.
  • Figs. 2a and 2b are parts of the message flow for the same UE, where the UE undergoes transition from idle mode to connected mode more than once.
  • the call flow shows some actions related to the UE connection request according to the prior art.
  • (source) gNB and/or (source) AMF will store/update the respective UE context in RAN DB using a respective context key. Then, potentially after some time, the UE goes into CM-IDLE state.
  • the second part of the call flow (on Fig. 2b) is related to the scenario where the same UE returns to CM-CONNECTED, after being in CM-IDLE mode.
  • related UE context can be retrieved by target gNB and/or serving AMF from RAN DB, by providing the same identifier which was used as context key.
  • the UE in particular if a network allocated context key is employed, the UE is expected to store and return the context key in the RRC Connection Request to the target gNB.
  • the target gNB is the gNB at which the UE goes into CM-CONNECTED again.
  • the target gNB may be the same as or different from the source gNB.
  • the serving AMF before the state transition to CM-IDLE may be the same as or different from the serving AMF after the state transition from CM-IDLE.
  • the context is stored in the RAN DB indexed by the context key.
  • the context key a.
  • UE 5G-GUTI Global Unique Temporary Identifier
  • 5G-GUTI contains a variety of information e.g., information regarding the cell and also the responsible AMF, and also it is one of the most secure UE identification that can be used between UE, gNB, and AMF.
  • S-TMSI c. Masked IMEI (International Mobile Station Equipment Identity) or a derivative of it.
  • a network allocated identifier may be employed for this purpose.
  • the network may allocate the identifier (e.g.: AMF ID + AMF UE NGAP ID) to the UE and the UE is asked to remember and return it whenever the UE returns from IDLE to CONNECTED mode.
  • the network allocated identifier should be unique in the RAN area.
  • AMF ID is unique in the entire RAN and AMF UE NGAP ID is a ID allocated by the AMF to the UE and is unique inside the coverage of the AMF. A combination of these two IDs will be unique in the entire RAN.
  • UE requests network access for the first-time using RRC connection setup request to Source gNB.
  • the trigger for such connection request can be by the UE, i.e. , mobile originated (MO) traffic or can be by the network via paging, i.e. , mobile terminated (MT) traffic.
  • the UE may perform the initial access via, e.g., 2-step RACH and 4-step RACH.
  • Source gNB Upon receipt of RRC connection setup request, Source gNB creates a UE context.
  • Source gNB replies to the RRC connection setup request by RRC connection setup and provides the created UE context or a part of it to UE.
  • UE is now in CM- CONNECTED mode.
  • gNB selects an AMF.
  • Source gNB stores the UE context, indexed by UE context key, into the RAN DB (may be implemented as RAN DSF).
  • RAN DB acknowledges that the UE context is stored.
  • Actions 3 and (4+5) may be performed in parallel or in an arbitrary sequence.
  • source gNB sends an Initial UE message to the AMF.
  • the NG-C message containing the Initial UE message to the AMF may optionally comprise information regarding the stored UE context of the gNB.
  • AMF Upon receipt of the Initial UE message, AMF creates its UE context for the session after the UE authentication is successful. AMF stores its UE context in RAN DB. If the NG-C message comprises information of the stored UE context for the gNB, AMF may re-use the same context key. Thus, it may store “its” UE context in the same UE context as the UE context of the gNB. Alternatively, AMF may use an own context key and, thus, store a further UE context for the UE in the RAN DB.
  • the RAN DB acknowledges that the UE context of the AMF is stored in the RAN DB.
  • the UE may setup PDU sessions to perform UP data transmission (in UL and/or DL), and any NG-RAN logical entity (e.g.: gNB-CU-CP, gNB-DU, gNB-CU-UP) or any other RAN network function or AMF may generate “UE historical intelligence” information, while the UE is in CONNECTED mode. This is stored in the RAN DB indexed by the same context key which was used to store the session-related portion of the UE context. Some time later, the PDU sessions are released at AMF and the session-related portion of the UE context may be removed.
  • NG-RAN logical entity e.g.: gNB-CU-CP, gNB-DU, gNB-CU-UP
  • AMF may generate “UE historical intelligence” information, while the UE is in CONNECTED mode. This is stored in the RAN DB indexed by the same
  • AMF may send an Update UE Context message associated with the UE context key. This message may include an indication to delete only the session related data. Furthermore, this message may include modifications to the UE context before the UE is sent to the Idle state. The UE is sent to CM-IDLE. UE may remain in RM-REGISTERED state. For this purpose, AMF sends UE context release command to source gNB. Accordingly, source gNB releases (removes) its UE context. In some example embodiments, source gNB may send an Update UE Context message associated with the UE context key. This message may include an indication to delete only the session related data.
  • this message may include modifications to the UE context before the UE is sent to the Idle state.
  • the Source gNB sends RRC Release to UE such that the UE goes to CM-IDLE.
  • the source gNB may also provide the UE with a UE persistent identifier (ID) which the UE is expected to return to the NG-RAN node in the next RRC Connection Request.
  • ID UE persistent identifier
  • the persistent identifier can be the UE context key. That is, the UE persistent ID and the UE context key are either the same or are mapped to each other at the network side.
  • RAN DB At release of the PDU sessions and the RRC connection, RAN DB is not informed on the UE release. Therefore, RAN DB maintains the UE context(s). However, in some example embodiments, AMF and/or gNB inform RAN DB on the release(s). In such example embodiments, RAN DB may remove a part of the UE context(s). However, RAN DB maintains at least a part of the session-unrelated portion of the UE context(s). In some example embodiments, RAN DB maintains the entire session-unrelated portion of the UE context(s).
  • PART-2 (Fig. 2b) of this embodiment is described below.
  • the actions of PART-2 follow those of PART-1.
  • the time lag between these PARTs is arbitrary.
  • UE performs 2 nd (or subsequent) network access using RRC Connection request to target gNB.
  • Source gNB and Target gNB may be the same or different from each other.
  • the trigger for such connection request can be by the UE, i.e. , mobile originated (MO) traffic or can be by the network via paging, i.e., mobile terminated (MT) traffic.
  • the UE may perform the initial access via, e.g., 2-step RACH and 4-step RACH.
  • the target gNB retrieves the UE context from RAN DB using the context key.
  • this context key may be obtained on the network side based on the UE persistent identifier which is returned by the UE in the RRC Connection Request.
  • the UE persistent ID and the UE context key are either the same or are mapped to each other at the network side.
  • RAN DB sends UE context to target gNB. Since the UE context stored in the RAN DB comprises at least some session-unrelated information such as UE historical information, the same is available for the new sessions, even if the target gNB is different from the source gNB. Besides, if the UE context stored in RAN DB while the UE was in CM-IDLE comprises session-related data, too, these may be used in the RRC Connection setup. The target gNB may create the UE context using at least a part of the data retrieved from RAN DB.
  • session-unrelated information such as UE historical information
  • Target gNB sends RRC connection setup and provides the created context or a part of it to the UE. Thus, UE is in CM-CONNECTED state.
  • the context key may also be shared with the selected AMF along with the Initial UE message
  • AMF decides on the key to retrieve the UE context from RAN DB.
  • AMF may also use the key received from target gNB,, or the AMF may have an internal mapping between the RAN UE context key and its own, if it used a different key than the RAN.
  • AMF retrieves the UE context using the appropriate context key.
  • RAN DB provides the UE context to AMF.
  • AMF may create a UE context using the UE context stored at RAN DB, too.
  • Actions 22 to 25 correspond to actions 10 to 13 of PART-1, wherein the source gNB is replaced by the target gNB.
  • keeping the UE persistent ID across the state transitions particularly when the UE transitions from the Connected state to Idle state, provides the target access node, e.g., target gNB, to which the UE performs a new connection establishment, with the capability of retrieving the UE context from the RAN DB.
  • target access node e.g., target gNB
  • Such UE persistent ID can be unique RAN-wide.
  • the UE persistent ID can be unique in the registration area (RA) of the UE.
  • the information stored in the UE context of the RAN DB is available for use at the target gNB and serving AMF.
  • the UE context information related the UE intelligence can be utilized for further UE-related optimizations.
  • Such intelligence information can be utilized by AI/ML algorithms or data analytics functions in the 5GS.
  • the historical intelligence can be considered as kind of semi-static information like UE mobility history information, UE power related data/inference, intelligence built based on U E/network reporting/monitoring, n/w algorithm information applicable to the UE etc.
  • the UE historical intelligence is assumed to be built over a longer period of time and maybe used by the network whenever the UE enters CONNECTED mode.
  • the UE context storage in the RAN DB may be done only once, after execution of the initial access procedure.
  • Fig. 2 shows a case where the gNBs are split in CU and DU.
  • the respective actions are performed by CU-CP.
  • the respective actions may be performed by the (unsplit, i.e., aggregated) gNB.
  • the shown entities herein can be in any form that consequently realizes service-based architecture principles.
  • the communication among these entities can be performed over interfaces via any communication technology that enables service-based communication.
  • the shown entities can be in the form of (but not limited to) NFs or microservices and the shown procedures can be performed via SBI.
  • HTTP(S) can be used for the communications between the network elements/network functions/microservices.
  • the shown information elements can be communicated via HTTP Request and Response messages, e.g., HTTP POST, HTTP GET, HTTP PUT, HTTP PATCH Request messages and the associated HTTP Response messages.
  • Microservices could be understood as more modular services (as compared with services produced/provided by NFs) that come together to provide a meaningful service/application.
  • an NF can provide one or more services
  • a microservice can represent small modules that make up the services in the NF.
  • microservices can communicate with each other, e.g., statelessly.
  • the UE context key maybe IMSI, which is accessible only to AMF (NAS message), but not to NG-RAN node.
  • the UE context maybe stored in the RAN DB for the first time by AMF and the context key shared with the NG-RAN node over NG interface.
  • the NG-RAN node may use the same context key or one of its own.
  • the NG-RAN node may be able to retrieve the UE context key for a given UE only after AMF identifies the UE based on NG: Initial UE message, and sends back the context key to the NG-RAN node in a response message thereto.
  • AMF Access Management Function
  • the RAN DB has an architecture to ensure that UE Context retrieval can be performed from anywhere within the RAN, or at least from large parts of the RAN.
  • (Local) RAN DBs are typically shared between sets of gNBs and AMFs which have the same coverage or geographical area (“registration area”).
  • the Local RAN DB is used to store the relevant UE Context information (as explained in the previous sections).
  • Fig. 3 illustrates, some (or even all) Local RAN DBs may be connected to a Global DB registration entity, called hereafter Global DB.
  • Global DB is a registry for all the UE Context information and their respective RAN DB ID.
  • the RAN DB ID indicates the Local RAN DB where the UE context is stored, i.e. the location of that information.
  • Global DB can help to locate the Local RAN DB containing the UE Context information.
  • scenario 2 there are 3 potential scenarios, whereof scenario 2 illustrated in Fig. 3.
  • the previous local RAN DB informs the Global DB (1. in Fig. 3) on the context key for which it has stored the UE context (at least the historical intelligence information):
  • UE changes its status from CM-IDLE to CM-CONNECTED in the same registration area in which it was CM-CONNECTED before.
  • the target gNB and the serving AMF can easily fetch the relative information from the local RAN DB by having the correct UE context key. This scenario does not need a Global DB involvement.
  • the target gNB and the new serving AMF cannot locate the UE context (including UE Historical Intelligence information) in the Local RAN DB.
  • Local RAN DB queries (2. in Fig. 3) the Global DB for the exact location of the UE context (including Historical Intelligence information) (the location of the RAN DB which was previously serving the UE).
  • Global DB searches its database based on the UE identification for a match. If the search is successful, then Global DB requests the previous local RAN DB (3. in Fig.
  • the previous local RAN DB transfers the UE context (at least the UE Historical Intelligence information) to the new local RAN DB (4. in Fig. 3). Obviously, the transfer is feasible due to the current UE status (CM-IDLE).
  • CM-IDLE CM- CONNECTED
  • CM-CONNECTED CM- CONNECTED
  • Global DB updates its registry with the new location of the UE Historical Intelligence information.
  • neither the new local RAN DB nor Global DB can locate the UE context (incl. UE Historical Intelligence information). This may happen e.g. if UE connects to network for the first time. In this case, the target gNB and the serving AMF undergo the standard procedures to register the UE in the Core Network.
  • Fig. 4 shows an apparatus according to an example embodiment of the invention.
  • the apparatus may be a connection management function, such as a gNB or eNB, or a registration management function, such as a AMF, or an element thereof.
  • Fig. 5 shows a method according to an example embodiment of the invention.
  • the apparatus according to Fig. 4 may perform the method of Fig. 5 but is not limited to this method.
  • the method of Fig. 5 may be performed by the apparatus of Fig. 4 but is not limited to being performed by this apparatus.
  • the apparatus comprises means for storing 10, means for monitoring 20, and means for maintaining 30.
  • the means for storing 10, means for monitoring 20, and means for maintaining 30 may be a storing means, monitoring means, and maintaining means, respectively.
  • the means for storing 10, means for monitoring 20, and means for maintaining 30 may be a storage device, monitor, and maintainer, respectively.
  • the means for storing 10, means for monitoring 20, and means for maintaining 30 may be a storing processor, monitoring processor, and maintaining processor, respectively.
  • the means for storing 10 stores a context for the terminal (“terminal context” or “UE context”) into a database (S10).
  • the context comprises a session-related portion and a session-unrelated portion different from the session-related portion.
  • the context is stored into the database while the terminal is in the connected state or (latest) when the terminal transits from the connected state into the idle state.
  • the means for monitoring 20 monitors if a terminal transits from a connected state into an idle state (S20).
  • the connected state is a state of a connection management for the terminal.
  • the idle state is another state of the connection management for the terminal.
  • the context is related to the terminal in the connected state. A context is typically not related to the terminal in the idle state.
  • the means for maintaining 30 maintains at least a part of the session-unrelated portion of the context for the terminal in the database if the terminal transits from the connected state into the idle state (S30). I.e., the database is inhibited to remove at least the session-unrelated portion of the context in the idle state after the transition from the connected state.
  • the means for maintaining 30 may inhibit that the database gets informed on the state transition to the idle state, or the means for maintaining 30 may inhibit to request removing at least the session-unrelated portion of the context from the database.
  • Fig. 6 shows an apparatus according to an example embodiment of the invention.
  • the apparatus may be a connection management function, such as a gNB or eNB, or a registration management function, such as an AMF, or an element thereof.
  • Fig. 7 shows a method according to an example embodiment of the invention.
  • the apparatus according to Fig. 6 may perform the method of Fig. 7 but is not limited to this method.
  • the method of Fig. 7 may be performed by the apparatus of Fig. 6 but is not limited to being performed by this apparatus.
  • the apparatus comprises means for supervising 110, means for retrieving 120, and means for applying 130.
  • the means for supervising 110, means for retrieving 120, and means for applying 130 may be a supervising means, retrieving means, and applying means, respectively.
  • the means for supervising 110, means for retrieving 120, and means for applying 130 may be a supervisor, retriever, and applicator, respectively.
  • the means for supervising 110, means for retrieving 120, and means for applying 130 may be a supervising processor, retrieving processor, and applying processor, respectively.
  • the means for supervising 110 supervises if a terminal transits from an idle state into a connected state (S110).
  • the connected state is a state of a connection management for the terminal.
  • the idle state is another state of the connection management for the terminal.
  • the means for retrieving 120 retrieves at least a part of a session-unrelated portion of a context for the terminal (“terminal context” or “UE context”) from a database (S120).
  • the context is to be related to the terminal in the connected state.
  • the context comprises a session-related portion and a session-unrelated portion different from the session- related portion.
  • a context is typically not related to the terminal in the idle state.
  • the means for applying 130 applies the retrieved session-unrelated portion of the context to the connected state of the terminal (S130).
  • Fig. 8 shows an apparatus according to an example embodiment of the invention.
  • the apparatus may be a database such as a (local) RAN DB, or an element thereof.
  • Fig. 9 shows a method according to an example embodiment of the invention.
  • the apparatus according to Fig. 8 may perform the method of Fig. 9 but is not limited to this method.
  • the method of Fig. 9 may be performed by the apparatus of Fig. 8 but is not limited to being performed by this apparatus.
  • the apparatus comprises means for storing 210, means for receiving 220, and means for providing 230.
  • the means for storing 210, means for receiving 220, and means for providing 230 may be a storing means, receiving means, and providing means, respectively.
  • the means for storing 210, means for receiving 220, and means for providing 230 may be a storage device, receiver, and provider, respectively.
  • the means for storing 210, means for receiving 220, and means for providing 230 may be a storing processor, receiving processor, and providing processor, respectively.
  • the means for storing 210 stores a context for a terminal (“terminal context” or “UE context”) in a first database (S210).
  • the context is received from a first instance of a network function (such as a connection management function (e.g.
  • the context is related to the terminal in a connected state.
  • the context comprises a session-related portion and a session- unrelated portion different from the session-related portion.
  • a context is typically not related to the terminal in the idle state.
  • the means for receiving 220 receives a first request from a second instance of the network function (S220).
  • the request requests to provide at least a part of the session- unrelated portion of the context for the terminal.
  • the first instance of the network function may be different from or the same as the second instance of the network function.
  • the means for providing 230 provides at least the part of the session-unrelated portion of the context for the terminal to the second instance (S230) in response to receiving the first request.
  • Fig. 10 shows an apparatus according to an example embodiment of the invention.
  • the apparatus may be a database such as a (local) RAN DB, or an element thereof.
  • Fig. 11 shows a method according to an example embodiment of the invention.
  • the apparatus according to Fig. 10 may perform the method of Fig. 11 but is not limited to this method.
  • the method of Fig. 11 may be performed by the apparatus of Fig. 10 but is not limited to being performed by this apparatus.
  • the apparatus comprises means for supervising 310, means for checking 320, means for querying 330, and means for receiving 340.
  • the means for supervising 310, means for checking 320, means for querying 330, and means for receiving 340 may be a supervising means, checking means, querying means, and receiving means, respectively.
  • the means for supervising 310, means for checking 320, means for querying 330, and means for receiving 340 may be a supervisor, checker, questor, and receiver, respectively.
  • the means for supervising 310, means for checking 320, means for querying 330, and means for receiving 340 may be a supervising processor, checking processor, querying processor, and receiving processor, respectively.
  • the means for supervising 310 supervises if a first database receives a request to provide at least a part of a session-unrelated portion of a context for a terminal (“terminal context” or “UE context”) (S310).
  • the context is related to the terminal in a connected state.
  • the context comprises a session-related portion and the session-unrelated portion different from the session-related portion.
  • a context is typically not related to the terminal in the idle state.
  • the means for checking 320 checks if the first database stores at least the part of the session-unrelated portion of the context for the terminal (S320).
  • the means for querying 330 queries a global database for an identification of a second database (S330). According to the global database, the second database stores at least the part of the session-unrelated portion of the context for the terminal.
  • the means for receiving 340 receives at least the part of the session-unrelated portion of the context for the terminal from the second database (S340). It may then store at least the part of the session-unrelated portion of the context into the first database, and provide at least the part of the session-unrelated portion in response to the request of S310.
  • Fig. 12 shows an apparatus according to an example embodiment of the invention.
  • the apparatus may be a database such as a global DB, or an element thereof.
  • Fig. 13 shows a method according to an example embodiment of the invention.
  • the apparatus according to Fig. 12 may perform the method of Fig. 13 but is not limited to this method.
  • the method of Fig. 13 may be performed by the apparatus of Fig. 12 but is not limited to being performed by this apparatus.
  • the apparatus comprises means for monitoring 410 and means for causing 420.
  • the means for monitoring 410 and means for causing 420 may be a monitoring means and causing means, respectively.
  • the means for monitoring 410 and means for causing 420 may be a monitor and causer, respectively.
  • the means for monitoring 410 and means for causing 420 may be a monitoring processor and causing processor, respectively.
  • the means for monitoring 410 monitors if a query for an identification of a second database is received from a first database (S410).
  • the second database stores at least a part of a session-unrelated portion of a context for a terminal (“terminal context” or “UE context”).
  • the context is related to the terminal in a connected state.
  • the context comprises a session-related portion and the session-unrelated portion different from the session-related portion.
  • a context is typically not related to the terminal in the idle state.
  • the means for causing 420 causes a transfer of at least the part of the session-unrelated portion of the context for the terminal from the second database to the first database (S420).
  • the means for causing may trigger the second database to provide at least the part of the session-unrelated portion of the context to the first database, or trigger the first database to request at least the part of the session-unrelated portion of the context from the second database.
  • Fig. 14 shows an apparatus according to an example embodiment of the invention.
  • the apparatus may be a terminal such as a UE, or an element thereof.
  • Fig. 15 shows a method according to an example embodiment of the invention.
  • the apparatus according to Fig. 14 may perform the method of Fig. 15 but is not limited to this method.
  • the method of Fig. 14 may be performed by the apparatus of Fig. 14 but is not limited to being performed by this apparatus.
  • the apparatus comprises means for supervising 510, means for instructing 520, means for monitoring 530, and means for providing 540.
  • the means for supervising 510, means for instructing 520, means for monitoring 530, and means for providing 540 may be a supervising means, instructing means, monitoring means, and providing means, respectively.
  • the means for supervising 510, means for instructing 520, means for monitoring 530, and means for providing 540 may be a supervisor, instructor, monitor, and provider, respectively.
  • the means for supervising 510, means for instructing 520, means for monitoring 530, and means for providing 540 may be a supervising processor, instructing processor, monitoring processor, and providing processor, respectively.
  • the means for supervising 510 supervises if a terminal in a connected state receives an identifier from a network function (S510).
  • a terminal context UE context
  • the identifier is related to the terminal context. I.e., the identifier may be a context key of the terminal context.
  • the means for instructing 520 instructs the terminal to store the identifier (S520).
  • the means for monitoring 530 monitors if the terminal decides to send a connection request to transit from an idle state to the connected state (S530). In some example embodiments, the means for monitoring 530 monitors only if the means for instructing 520 instructed the terminal to store the identifier previously, i.e., if the UE decides to transit at least for the second time into connected state. Each of the connected state and the idle state is a respective state of a connection management for the terminal. The terminal may decide to send the connection request for a mobile originated traffic or a mobile terminated traffic (after being paged).
  • the means for providing 540 provides the identifier to the network function (S540).
  • the terminal may provide the identifier in the connection request, or it may provide the identifier in a separate message.
  • the separate message may precede or follow the connection request,
  • Fig. 16 shows an apparatus according to an embodiment of the invention.
  • the apparatus comprises at least one processor 810, at least one memory 820 including computer program code, and the at least one processor 810, with the at least one memory 820 and the computer program code, being arranged to cause the apparatus to at least perform at least one of the methods according to Figs. 5, 7, 9, 11, 13, and 15 and related description.
  • Some example embodiments of this invention are particularly useful in a 5G network.
  • the invention is not limited to 5G. It may be used in other networks, too, e.g. in former or forthcoming generations of 3GPP networks such as 4G, 6G, 7G, etc. It may be used in any wireless (mobile) and wireline communication networks, where a UE context may comprise both session-related context data and other context data that are not related to the session.
  • the other context data may be named e.g. session- unrelated context data, or general context data, or semi-static context data.
  • One piece of information may be transmitted in one or plural messages from one entity to another entity. Each of these messages may comprise further (different) pieces of information.
  • Names of network elements, network functions, protocols, and methods are based on current standards. In other versions or other technologies, the names of these network elements and/or network functions and/or protocols and/or methods may be different, as long as they provide a corresponding functionality.
  • AMF serves as a function to which all UEs which are currently served must be registered. In other networks than 5G networks, this role may have a different name.
  • the AMF corresponds to a MME of LTE or a MSC of GSM.
  • AMF may be responsible for Connection Management, Reachability Management, Mobility Management and/or various functions relating to security and access management and authorization for the slice.
  • gNB is an access node of a 5G RAN.
  • example embodiments are not restricted to 5G RAN.
  • eNB may take the role of the access node.
  • Example embodiments are not even restricted to 3GPP networks.
  • AP may take the role of the access node.
  • the terminal may correspond to the technology of the access node.
  • the terminal may be a UE. It may be a MTC device, etc.
  • a UE context may be named terminal context instead.
  • each of the entities described in the present description may be based on a different hardware, or some or all of the entities may be based on the same hardware. It does not necessarily mean that they are based on different software. That is, each of the entities described in the present description may be based on different software, or some or all of the entities may be based on the same software.
  • Each of the entities described in the present description may be deployed in the cloud.
  • example embodiments of the present invention provide, for example, a network function involved in configuration management and/or registration management of a UE, such as an access management function and/or node of an access network (e.g. RAN) such as a gNB, eNB, etc., or a component thereof, an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s).
  • a database such as a AN DB (e.g.
  • a RAN DB or a component thereof, an apparatus embodying the same, a method for controlling and/or operating the same, and computer program(s) controlling and/or operating the same as well as mediums carrying such computer program(s) and forming computer program product(s).
  • Implementations of any of the above described blocks, apparatuses, systems, techniques or methods include, as non-limiting examples, implementations as hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • Each of the entities described in the present description may be embodied in the cloud.

Landscapes

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

Abstract

L'invention concerne un procédé consistant : à surveiller si un terminal transite d'un état connecté à un état de repos, un contexte de terminal étant associé au terminal en état connecté et comprenant une partie liée à une session et une partie non liée à la session, différente de la partie liée à la session; à stocker le contexte de terminal destiné au terminal dans une base de données tandis que le terminal est en état connecté ou lorsque le terminal transite de l'état connecté à l'état de repos; et à maintenir au moins une partie de la partie non liée à la session du contexte de terminal destiné au terminal dans la base de données si le terminal transite de l'état connecté à l'état de repos, chacun de l'état connecté et de l'état de repos étant un état respectif d'une CM destinée au terminal.
PCT/EP2021/070096 2021-07-19 2021-07-19 Stockage d'informations persistantes d'ue à travers des transitions d'états de gestion de connexions (cm) WO2023001353A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/070096 WO2023001353A1 (fr) 2021-07-19 2021-07-19 Stockage d'informations persistantes d'ue à travers des transitions d'états de gestion de connexions (cm)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2021/070096 WO2023001353A1 (fr) 2021-07-19 2021-07-19 Stockage d'informations persistantes d'ue à travers des transitions d'états de gestion de connexions (cm)

Publications (1)

Publication Number Publication Date
WO2023001353A1 true WO2023001353A1 (fr) 2023-01-26

Family

ID=77071550

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/070096 WO2023001353A1 (fr) 2021-07-19 2021-07-19 Stockage d'informations persistantes d'ue à travers des transitions d'états de gestion de connexions (cm)

Country Status (1)

Country Link
WO (1) WO2023001353A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200029297A1 (en) * 2016-09-29 2020-01-23 Samsung Electronics Co., Ltd Method for communication in system in which 4g and 5g coexist, and device therefor

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200029297A1 (en) * 2016-09-29 2020-01-23 Samsung Electronics Co., Ltd Method for communication in system in which 4g and 5g coexist, and device therefor

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.501
3GPP TS 29.510
3GPP TS 38.401
ALCATEL-LUCENT ET AL: "Commenting contribution on Ericsson's S3-160157 "Security for RRC Connection Suspend and Resume procedure in solution 18 for Narrow Band CIoT"", vol. SA WG3, no. Dubrovnik, Croatia; 20160201 - 20160205, 31 January 2016 (2016-01-31), XP051060492, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/SA3/Docs/> [retrieved on 20160131] *
CATT: "Open Issues of Solution 18", 3GPP TSG-RAN WG2 #NB-IOT R2- 160460, 21 January 2016 (2016-01-21), Budapest, pages 1 - 4, XP055537270, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ ran/WG2_RL2/TSGR2_AHs/2016_01_LTE_NB_IoT/Docs/R2-160460.zip> [retrieved on 20181220] *
NOKIA ET AL: "Mega CR to clean up", vol. SA WG2, no. Online; 20201116 - 20201120, 9 November 2020 (2020-11-09), XP051953383, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_142e_Electronic/Docs/S2-2009068.zip S2-2009068-23501-MegaEditorialCR_r04.docx> [retrieved on 20201109] *
NOKIA NETWORKS: "Signaling details for UP based solution", vol. RAN WG3, no. Budapest, HU; 20160120 - 20160122, 19 January 2016 (2016-01-19), XP051055956, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN3/Docs/> [retrieved on 20160119] *

Similar Documents

Publication Publication Date Title
CN111771394B (zh) 用于ue上下文和pdu会话上下文管理的系统和方法
US20220150994A1 (en) Session Management Method and System, and Terminal for Locating a User Plane Function (UPF) Entity when a Session is an Inactive State
CN110291837B (zh) 网络注册和网络切片选择系统和方法
CN110049070B (zh) 事件通知方法及相关设备
EP3689035B1 (fr) Sélection adaptative de tranche de réseau
KR20200064088A (ko) Ue(user equipment)에서의 정책 프로비저닝
JP7238152B2 (ja) 中間セッション管理機能の挿入後の無線通信を管理するための移動通信コアネットワークデバイス及び方法
CN111615844B (zh) 用于选择服务无线通信设备的会话管理实体的方法和装置
EP3445072A1 (fr) Réseau de communication radio mobile et procédé pour associer un dispositif de terminal radio mobile à une instance de tranche de réseau d&#39;un réseau de communication radio mobile
JP7450049B2 (ja) ユーザ装置またはｐｐｄｕセッションにサービスする分散ネットワーク機能の露出と発見
CN111328019B (zh) 识别终端的方法、装置
WO2021225087A1 (fr) Support pour une notification d&#39;événement de quota de tranche de réseau
US20200280837A1 (en) System and interface for cross administration or technology domain network functions (nfs) instantiation and configuration for roaming users
CN112005580B (zh) 边缘服务连续性
US20220225459A1 (en) Communication network component and method for handling a service request
EP3881496A1 (fr) Mécanisme de découverte de nef par rapport à une gestion de pfd
US10057871B2 (en) Data transmission method and base station
WO2023001353A1 (fr) Stockage d&#39;informations persistantes d&#39;ue à travers des transitions d&#39;états de gestion de connexions (cm)
CN115884153A (zh) 通信的方法和装置
KR20200114916A (ko) 이동 통신 시스템에서 네트워크 분석 정보를 udm을 통해 전달 할 때 nf의 동작과 동기화 방법
CN116033372A (zh) 一种通信方法及装置
KR20240102935A (ko) 액세스 유형별 네트워크 슬라이스 승인 제어를 위한 방법
CN117158032A (zh) 通信网络布置和用于选择通信网络的网络功能的方法
CN112584446A (zh) 一种用户面功能选择方法及装置、存储介质

Legal Events

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

Ref document number: 21746452

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE