[go: up one dir, main page]

WO2025175429A1 - Améliorations apportées à la prise en charge d'un état rrc_inactif - Google Patents

Améliorations apportées à la prise en charge d'un état rrc_inactif

Info

Publication number
WO2025175429A1
WO2025175429A1 PCT/CN2024/077598 CN2024077598W WO2025175429A1 WO 2025175429 A1 WO2025175429 A1 WO 2025175429A1 CN 2024077598 W CN2024077598 W CN 2024077598W WO 2025175429 A1 WO2025175429 A1 WO 2025175429A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
context
data forwarding
cell
satellite
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/077598
Other languages
English (en)
Inventor
Ayaz AHMED
Philippe Godin
Xiang Xu
Suresh P Nair
Ahmad AWADA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
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 Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to PCT/CN2024/077598 priority Critical patent/WO2025175429A1/fr
Publication of WO2025175429A1 publication Critical patent/WO2025175429A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18565—Arrangements for preventing unauthorised access or for providing user protection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • Example embodiments of the present disclosure generally relate to the field of communication, and in particular, to network elements, methods, apparatuses, and non-transitory computer readable mediums for enhancements required to support RRC_INACTIVE state functionality when served by non-terrestrial network (NTN) regenerative non-geostationary (NGSO) satellite deployments.
  • NTN non-terrestrial network
  • NGSO regenerative non-geostationary
  • 3GPP has considered two architecture options for New Radio (NR) NTN i.e., transparent architecture in which the satellite payload performs frequency conversion, amplification and filtering, with the gNB located on the ground, and regenerative architecture in which part or full gNB shall be onboard the satellite.
  • NR New Radio
  • NTN Enhancements in Release-19 are expected to introduce the support of regenerative payload for NR NTN.
  • One of the expected enhancements under NTN mobility and service continuity is “Enhanced support in RRC_INACTIVE” . It must be noted that, basic support of RRC_INACTIVE state for NR NTN is available already in 3GPP Release-17.
  • a first network element comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network element at least to: update, based on a new security key derived, the security context included in user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell served by the first network element; and transmit, to a second network element which is to serve the cell after satellite switch, the UE context including the updated security context with new security key, before the satellite switch, wherein the UE context including the updated security context with the new security key is transmitted to a next serving network element till the at least one UE is resumed to a connected state.
  • UE user equipment
  • the satellite switch herein refers to as change of NGSO satellite hosting full or part of the gNB serving fixed NTN cell on earth; i.e. the outgoing satellite stops serving the cell and an incoming satellite starts serving.
  • the network elements (the first and second network elements) may be hosted on to a NGSO satellite which continuously orbits the earth.
  • a second network element comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the second network element at least to: receive, from a first network element serving the cell, which is to be served by the second network element after satellite switch, user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell, before the satellite switch, wherein the UE context includes updated security context with new security key; and store the UE context including the updated security context with new security key, wherein the UE context including the updated security context with the new security key is received by a next serving network element till the at least one UE is resumed to a connected state.
  • UE user equipment
  • a method comprises: updating, at a first network element and based on a new security key derived, the security context included in user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell served by the first network element; and transmitting, to a second network element which is to serve the cell after satellite switch, the UE context including the updated security context with new security key, before the satellite switch, wherein the UE context including the updated security context with the new security key is transmitted to a next serving network element till the at least one UE is resumed to a connected state.
  • UE user equipment
  • a method comprises: receiving, from a first network element serving the cell which is to be served by a second network element, user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell, before satellite switch, wherein the UE context includes updated security context with new security key; and storing, at the second network element, the UE context including the updated security context with new security key, wherein the UE context including the updated security context with the new security key is received by a next serving network element till the at least one UE is resumed to a connected state.
  • UE user equipment
  • a method comprises: receiving, from a second network element which is to serve a cell served by a first network element, a path switch request for a plurality of user equipments (UEs) to switch a next generation (NG) user plane (NG-U) downlink (DL) termination point hosted by the first network element to the second network element; and transmitting, to the second network element, a path switch response indicating the NG-U DL termination point has been switched to the second network element.
  • UEs next generation
  • NG-U next generation
  • DL downlink
  • an apparatus comprises: means for updating, at a first network element and based on a new security key derived, the security context included in user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell served by the first network element; and means for transmitting, to a second network element which is to serve the cell after satellite switch, the UE context including the updated security context with new security key, before the satellite switch, wherein the UE context including the updated security context with the new security key is transmitted to a next serving network element till the at least one UE is resumed to a connected state.
  • UE user equipment
  • an apparatus comprises: means for receiving, from a first network element serving the cell which is to be served by a second network element, user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell, before satellite switch; and means for storing, at the second network element, the UE context including the updated security context with new security key, wherein the UE context including the updated security context with the new security key is received by a next serving network element till the at least one UE is resumed to a connected state.
  • UE user equipment
  • an apparatus comprises: means for receiving, from a second network element which is to serve a cell served by a first network element, a path switch request for a plurality of user equipments (UEs) to switch a next generation (NG) user plane (NG-U) downlink (DL) termination point hosted by the first network element to the second network element; and means for transmitting, to the second network element, a path switch response indicating the NG-U DL termination point has been switched to the second network element.
  • NG next generation
  • NG-U next generation
  • DL downlink
  • a non-transitory computer-readable storage medium comprising program instructions.
  • the program instructions when executed by an apparatus, cause the apparatus to perform at least the following: updating, at a first network element and based on a new security key derived, the security context included in user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell served by the first network element; and transmitting, to a second network element which is to serve the cell after satellite switch, the UE context including the updated security context with new security key, before the satellite switch, wherein the UE context including the updated security context with the new security key is transmitted to a next serving network element till the at least one UE is resumed to a connected state.
  • UE user equipment
  • a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receive, from a first network element serving the cell which is to be served by a second network element, user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell, before satellite switch, wherein the UE context includes updated security context with new security key; and store, at the second network element, the UE context including the updated security context with new security key, wherein the UE context including the updated security context with the new security key is received by a next serving network element till the at least one UE is resumed to a connected state.
  • UE user equipment
  • FIG. 1B illustrates an example connection resume scenario in case of regenerative
  • FIG. 3 illustrates a process flow for one example implementation in accordance with some example embodiments of the present disclosure
  • FIG. 4 illustrates a process flow for another example implementation in accordance with some example embodiments of the present disclosure
  • FIG. 5 illustrates a flowchart of an example method implemented at a first network element in accordance with some other embodiments of the present disclosure
  • FIG. 6 illustrates a flowchart of an example method implemented at a second network element in accordance with some other embodiments of the present disclosure
  • FIG. 7 illustrates a flowchart of an example method implemented at a third network element in accordance with some other embodiments of the present disclosure
  • FIG. 8 illustrates a simplified block diagram of a device that is suitable for implementing some example embodiments of the present disclosure.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • circuitry may refer to one or more or all of the following:
  • the term “network device” refers to a node in a communication network via which a terminal device receives services (e.g., positioning services) therefrom.
  • the network device may refer to a core network device or access network device, such as base station (BS) or an access point (AP) or a transmission and reception point (TRP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a remote radio unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a WiFi device, a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.
  • the terms “network device” , “AP device” , “AP” and “access point” may be used interchangeably.
  • the core network 140 may support, for example, user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 140 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a packet data network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway packet data network gateway
  • UPF user plane function
  • a data forwarding address indication including data forwarding address (es) in step 17 is also representative only and cannot be initiated without direct Xn interface connectivity (i.e. Xn connectivity between gNB3 and gNB1) . It means that the data forwarding path between the last serving node that hosts the UE context (gNB1) and the NG-U DL termination point, and the current serving satellite gNB (gNB3) cannot be set up without some enhancements to 3GPP Xn Interface specifications.
  • the functional support of RRC_INACTIVE state that enables a connection to be resumed successfully from RRC_INACTIVE state to RRC_CONNECTED state in NTN regenerative NGSO satellite deployment scenarios is not feasible with existing specifications without enhancements to Xn interface.
  • the second network element 230 transmits (206) , to the third network element 240, a path switch request 207 for a plurality of UEs to switch a next generation (NG) user plane (NG-U) downlink (DL) termination point hosted by the first network element 220 to the second network element 230.
  • the third network element 240 receives (208) , from the second network element 230 which is to serve the cell 110 served by the first network element 220, the path switch request 207 for a plurality of UEs to switch the NG-U DL termination point from the first network element 220 to the second network element 230.
  • the third network element 240 may correspond to the AMF 141 as shown in FIG. 1A.
  • the third network element 240 transmits (209) , to the second network element 230, a path switch response 210 indicating the NG-U DL termination point has been switched from the first network element 220 to the second network element 230.
  • the second network element 230 then receives (211) , from the third network element 240, the path switch response 210 indicating the NG-U DL termination point has been switched to the second network element 230.
  • the proactive transfer of the UE context including the updated security context with new security key for UEs in the RRC_INACTIVE state is enabled, for facilitating the connection resume. Meanwhile, the NG-U DL termination has been changed to the new serving satellite base station.
  • FIG. 3 illustrates a process flow 300 for one example implementation in accordance with some example embodiments of the present disclosure.
  • a UE is in RRC_CONNECTED state (step 1) , while consecutive satellite gNBs have Xn connectivity (step 3) , where satellite gNB1 receive DL data from UPF (step 2) .
  • NGSO satellite 1 hostsing gNB 1 moves the UE to RRC_INACTIVE state (step 5) , via a RRCRelease message with a suspend configuration.
  • a stationary UE may remain in the same NTN cell and a moving UE may re-select a new NTN cell.
  • gNB 1 serve the cell (step 7) .
  • a satellite switch is triggered, resulting into satellite 1 drifting away and satellite 2 (hosting gNB 2) starting to serve the UE.
  • step 8 before satellite switch, successive serving gNBs, transfer the UE context of all the RRC_INACTIVE UEs to the next serving satellite gNB (without path switch) .
  • the serving gNB that initiated RRC_CONNECTED state to RRC_INACTIVE state transition maintains the UE context till the NG-U DL termination points switched to the new serving satellite gNB after connection is resumed, and the UE context release at last serving gNB shall be triggered after successful connection resume and path switch.
  • step 9 i.e., before the satellite switch, while satellite 1 (hosting gNB1) is still serving the cell, the serving gNB1 updates the AS security context in the UE context of all the RRC_INACTIVE state UEs with a computed security key. Furthermore, in step 10, i.e., before satellite 1 switches and satellite 2 starts to serve, satellite 1 (hosting gNB 1) proactively moves the UE context with the updated AS security context using the new computed security key of all the RRC_INACTIVE state UEs via a non-UE associated (or UE-associated) Xn interface message (s) with UE contexts, for example, included in a transparent container.
  • a non-UE associated (or UE-associated) Xn interface message (s) with UE contexts, for example, included in a transparent container.
  • the satellite 2 (hosting gNB 2) creates/stores UE context including the new security key for all the RRC_INACTIVE state UEs for which the context was transferred.
  • the satellite 2 triggers a data forwarding address indication including at least one data forwarding address for data transfer towards the last serving satellite (hosting gNB 1) to enable NG-U DL data transfer.
  • DL data is transmitted from UPF to the last serving gNB.
  • a data forwarding tunnel is set up between the last serving gNB1 and the current serving gNB2.
  • step 14 From time (T+Tl) , gNB2 serves cell.
  • the subsequent steps 15 and 16 are similar to steps 9 and 10.
  • step 17 is similar to step 11, but triggers step 18 to set up a nested tunnel for NG-U DL data.
  • DL data may be transmitted from UPF to the last serving gNB and from the last serving gNB to the current serving gNB.
  • step 21 i.e., at time ‘T+2T1’ , the satellite 3 (hosting gNB 3) starts to serve the cell, and the UE has UL data to send (step 22) , hence it triggers a RRC resume request in step 23.
  • step 24 as the current serving satellite 3 (hosting gNB 3) has already received the UE context (including the updated security context with new security key) in step 16, it triggers the RRCResume message towards the UE (step 25) .
  • step 26 UE shall decrypt the RRC resume message using the new security key.
  • step 27 the UE transitions from RRC_INACTIVE to RRC_CONNECTED state.
  • step 28 RRC resume complete message is transmitted from the UE.
  • a path switch request procedure for a plurality of UEs shall be triggered by the current serving satellite 3 (hosting gNB3) to switch the NG-U DL termination point from satellite 1 (hosting gNB1) .
  • gNB3 transmits a path switch request for the plurality of UEs to the AMF, and receives a path switch response from the AMF.
  • step 31 DL data may be transmitted from UPF to the current serving gNB (gNB) .
  • AMF releases the UE context of the plurality of UEs in last serving satellite gNB (e.g., via an indication) .
  • the serving satellite gNB proactively transfers the UE context of all the UEs in the RRC_INACTIVE state including the updated security context with new security key, to the next serving satellite gNB, while the path switch is triggered only upon successful connection resume.
  • Successive serving satellite gNBs before satellite switch (or cell switch) updates the security context by computing a security key and proactively transfers the UE context of all the UEs in the RRC_INACTIVE state to the next serving satellite gNB. This may be done in a non-UE associated Xn (or UE-associated) signaling message with UE contexts, for example, included in a transparent container.
  • the last serving satellite gNB that initiated RRC_CONNECTED state to RRC_INACTIVE state transition still maintains the UE contexts of the UEs in the RRC_INACTIVE state, as it still hosts the NG-U DL termination point till the connection is resumed successfully.
  • the new serving satellite gNB after satellite switch, creates and/or stores the UE context for all the UEs and initiates the data forwarding address indication via a Xn-U Address Indication including the data forwarding addresses for potential data transfer before NG-U DL termination point changes for all the UEs.
  • a connection resume shall be directly executed at the current serving satellite gNB without “UE context retrieval” over Xn interface. It enables fast RRC_INACTIVE state to RRC_CONNECTED state transition with no Xn signaling overhead and delay during connection resume.
  • the new serving satellite gNB Upon successful connection resume of one or more UEs, the new serving satellite gNB triggers NG-U DL path switch via a path switch request procedure for one or more UEs.
  • a path switch request procedure may be enhanced to include the path switch request for multiple UEs which have resumed the connection at the same time.
  • the 5G Core Upon successful path switch, the 5G Core (5GC) initiates the release of the contexts in the last serving gNBs.
  • FIG. 4 illustrates a process flow 400 for another example implementation in accordance with some example embodiments of the present disclosure.
  • a UE is in RRC_CONNECTED state (step 1) , while consecutive satellite gNBs have Xn connectivity (step 3) , where satellite gNB1 receive DL data from UPF (step 2) .
  • NGSO satellite 1 hostsing gNB 1 moves a UE to RRC_INACTIVE state (step 5) , via a RRC Release message with a suspend configuration.
  • a stationary UE may remain in the same NTN cell and a moving UE may re-select a new NTN cell.
  • gNB 1 serve the cell (step 7) .
  • a satellite switch is triggered, resulting into satellite 1 drifting away and satellite 2 (hosting gNB 2) starting to serve the UE.
  • step 8 before satellite switch, successive serving gNBs, transfer the UE context of all the RRC_INACTIVE UEs to the next serving satellite gNB (followed by a path switch) .
  • step 9 i.e., before the satellite switch, while satellite 1 (hosting gNB1) is still serving the cell, the serving gNB1 updates the AS security context in the UE context of all the RRC_INACTIVE state UEs with a computed security key.
  • satellite 1 (hosting gNB 1) proactively moves the UE context with the updated AS security context of all the RRC_INACTIVE state UEs via a non-UE associated (or UE-associated) Xn interface message (s) with UE contexts, for example, included in a transparent container. It also includes the computed security key.
  • the satellite 2 (hosting gNB 2) creates/stores UE context including the new security key for all the RRC_INACTIVE state UEs for which the context was transferred (step 10) .
  • step 11 From time (T+t1) , gNB2 serves the cell.
  • step 12 the satellite 2 triggers a data forwarding address indication including at least one data forwarding address for data transfer towards the last serving satellite (hosting gNB 1) to enable NG-U DL data transfer.
  • a data forwarding tunnel is set up between the last serving gNB1 and the current serving gNB2.
  • the new serving satellite 2 (hosting gNB 2) , triggers a path switch request procedure.
  • gNB2 transmits a path switch request to the AMF (step 13) , and receives a path switch response from the AMF (step 14) , where DL data may be transmitted from UPF to gNB2 (step 15) .
  • step 16 after the path switch request procedure successfully completed, UE context at last serving satellite 1 (hosting gNB 1) shall be released.
  • the subsequent steps 17 and 19 are similar to the steps 9 and 10.
  • the subsequent steps 21 to 25 are similar to the steps 12 to 16.
  • step 26 i.e., at time ‘T+2T1’ , the satellite 3 (hosting gNB 3) starts to serve the cell.
  • UE has UL data to send (step 27) , hence it triggers a RRCResumeRequest in step 28 is initiated.
  • step 29 as the current serving satellite 3 (hosting gNB 3) has already received the UE context (including the updated security context with new security key) in step 19, it triggers the RRCResume message towards the UE and the UE successfully resumes the connection with step 30.
  • step 31 UE shall decrypt the RRC resume message using new key.
  • step 32 the UE transitions from RRC_INACTIVE to RRC_CONNECTED state.
  • step 33 RRC resume complete message is transmitted from the UE.
  • the data transmission shall happen in this implementation without NG signaling delay due to the path switch request procedure.
  • the serving satellite gNB proactively transfers the UE context of all the UEs in the RRC_INACTIVE state including updated AS security context with a new security key, to the next serving satellite gNB, while the NG-U DL termination (for all the UEs in the RRC_INACTIVE state) is also changed to the new serving gNB at the time of satellite switch.
  • Successive serving satellite gNBs before satellite switch (or cell switch) updates the security context by computing a security key and proactively transfers the UE context of all the UEs in the RRC_INACTIVE state to the next serving satellite gNB. This may be done in a non-UE associated Xn (or UE-associated) signaling message with UE contexts, for example, included in a transparent container.
  • the new serving satellite gNB Upon reception of new non-UE associated (or UE associated) Xn interface message, carrying UE contexts of RRC_INACTIVE state UEs (as in previous step) , after satellite switch, the new serving satellite gNB shall create the UE context for all the UEs in the RRC_INACTIVE state, initiate the data forwarding address indication via a Xn-U Address Indication including the data forwarding addresses for potential data transfer before NG-U DL termination point changes for all the UEs in the RRC_INACTIVE state, and triggers NG-U DL path switch via a path switch request procedure.
  • a path switch request procedure may be enhanced to include the path switch requests for multiple UEs which have resumed the connection at the same time, in a single message.
  • a connection resume shall be directly executed at the current serving satellite gNB without “UE context retrieval” over Xn interface. It enables fast RRC_INACTIVE state to RRC_CONNECTED state transition with no Xn signaling overhead during connection resume.
  • the NG-U DL termination is also switching to the new serving satellite gNB with the satellite switch, the data transfer after connection resume happens without the delay involved in triggering the path switch request procedure after successful RRC resume.
  • the UE context release shall be triggered by 5GC after the path switch request has been completed successfully.
  • the present disclosure provides a workable and optimal solution to support RRC_INACTIVE state in NTN regenerative NGSO scenarios. It does the proactive transfer of the UE context including the updated security context with new security key for RRC_INACTIVE state UEs, which is vital for the RRC connection resume to work successfully.
  • the Xn signaling for UE context retrieval upon a RRCResumeRequest is not required, due to proactive UE context transfer including the updated security context with new security key for RRC_INACTIVE state UEs at the time of satellite switch.
  • both the Xn signaling for UE context retrieval upon the RRC resume request, and the NG signaling for a path switch request after connection resume is not required, due to proactive UE context transfer including the updated security context with new security key for RRC_INACTIVE state UEs at the time of satellite switch and the NG-U DL path switch after each satellite switch.
  • FIG. 5 illustrates a flowchart of an example method 500 implemented at a first network element in accordance with some other embodiments of the present disclosure. It is to be understood that the method 500 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard. For ease of understanding, the method 500 will be described from the perspective of the first network element 120 with reference to FIG. 1A.
  • the first network element 120 updates, based on a new security key derived, the security context included in user equipment (UE) context of at least one UE 111 in RRC_INACTIVE state in a cell 110 served by the first network element 120.
  • the first network element 120 transmits, to a second network element 130 which is to serve the cell 110 after satellite switch, the UE context including the updated security context with new security key, before the satellite switch.
  • the UE context including the updated security context with the new security key is transmitted to a next serving network element till the at least one UE 111 is resumed to a connected state.
  • the satellite switch herein refers to as change of NGSO satellite hosting full or part of the gNB serving fixed NTN cell on earth; i.e.
  • the network elements may be hosted on to a NGSO satellite which continuously orbits the earth.
  • the network elements may be hosted on to a NGSO satellite which continuously orbits the earth.
  • the UE context may be transmitted via a non-UE associated Xn interface message or a UE-associated message, and may be included in a transparent container.
  • the first network element 120 may transition, via a radio resource control (RRC) release message with a suspend configuration, the at least one UE 111 from RRC_CONNECTED state to the RRC_INACTIVE state.
  • RRC radio resource control
  • the UE context is received via a non-UE associated Xn interface message or a UE-associated message, and may be included in a transparent container.
  • the second network element 130 may transmit, to a third network element 141, a path switch request for a plurality of user equipments (UEs) to switch the NG-U DL termination point from the first network element 120 to the second network element 130, after the at least one UE 111 is resumed to the RRC_CONNECTED state, and may receive, from the third network element 141, a path switch request response indicating the NG-U DL termination point has been switched to the second network element 130.
  • UEs user equipments
  • the second network element 130 may receive a RRC resume request triggered by the at least one UE 111, after switching a NG-U downlink (DL) termination point hosted by the first network element 120 to the second network element 130, and may transmit a RRC resume message to the at least one UE 111 based on the UE context including the updated security context, wherein the RRC resume message is encrypted using the new security key.
  • DL downlink
  • the first network element 120 is a last serving network element, and the second network element 130 is a current serving network element; the first network element 120 and the second network element 130 may be satellite base stations; or the third network element 141 may be an access and mobility management function (AMF) .
  • AMF access and mobility management function
  • FIG. 7 illustrates a flowchart of an example method 700 implemented at a second network element in accordance with some other embodiments of the present disclosure. It is to be understood that the method 700 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard. For ease of understanding, the method 700 will be described from the perspective of the third network element 141 with reference to FIG. 1A.
  • the third network element 141 receives, from a second network element 130 which is to serve a cell 110 served by a first network element 120, a path switch request for a plurality of user equipments (UEs) to switch a next generation (NG) user plane (NG-U) downlink (DL) termination point hosted by the first network element 120 to the second network element 130.
  • the third network element 141 transmits, to the second network element 130, a path switch response indicating the NG-U DL termination point has been switched to the second network element 130.
  • the path switch request response may be received after the plurality of UEs are resumed to the RRC_CONNECTED state.
  • the path switch request response may be received after UE context of the plurality of UEs is transfer from the first network element 120 to the second network element 130 while the plurality of UEs are still in the inactive state.
  • the apparatus comprises: means for updating, based on a new security key derived, the security context included in user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell served by the first network element; and means for transmitting, to a second network element which is to serve the cell after satellite switch, the UE context including the updated security context with new security key, before the satellite switch.
  • UE user equipment
  • the satellite switch herein refers to as change of NGSO satellite hosting full or part of the gNB serving fixed NTN cell on earth; i.e. the outgoing satellite stops serving the cell and an incoming satellite starts serving.
  • the network elements (the first and second network elements) may be hosted on to a NGSO satellite which continuously orbits the earth.
  • the network elements may be hosted on to a NGSO satellite which continuously orbits the earth.
  • the UE context may be transmitted via a non-UE associated Xn interface message or a UE-associated message, and may be included in a transparent container.
  • the apparatus may comprise: means for receiving, from the second network element, a data forwarding address indication including at least one data forwarding address for data transfer, before switching of the cell from the first network element to the second network element, wherein based on the data forwarding address indication, a data forwarding tunnel between the first network element and the second network element is established, and wherein before switching of the cell from the second network element to a next serving network element, a data forwarding address indication including at least one data forwarding address of the next serving network element is received by the second network element from the next serving network element, such that the second network element forwards the data forwarding address indication including at least one data forwarding address of the next serving network element to the first network element to forward data received from a next generation (NG) user plane (NG-U) at the first network element to the next serving network element in a nested tunnel.
  • NG next generation
  • NG-U next generation user plane
  • the apparatus may comprise: means for transitioning, via a radio resource control (RRC) release message with a suspend configuration, the at least one UE from RRC_CONNECTED state to the RRC_INACTIVE state.
  • RRC radio resource control
  • the apparatus may comprise: means for maintaining the UE context including the updated security context until a NG-U downlink (DL) termination point hosted by the first network element is switch to the second network element after the plurality of UEs are resumed to the RRC_CONNECTED state.
  • DL downlink
  • the apparatus may comprise: means for receiving, from the second network element, a data forwarding address indication including at least one data forwarding address for data transfer, after switching of the cell from the first network element to the second network element, wherein based on the data forwarding address indication, a data forwarding tunnel between the first network element and the second network element is established, wherein after switching of the cell from the second network element to a next serving network element, a data forwarding address indication including at least one data forwarding address of the next serving network element is received by the second network element from the next serving network element, such that the data forwarding address indication including at least one data forwarding address of the next serving network element is forwarded by the second network element to the first network element for establishing a data forwarding nested tunnel between the first network element and the next serving network element, till a NG-U DL termination point hosted by the first network element is switched to a network element where the at least one UE resumes connection from the inactive state to the connected state.
  • the apparatus may comprise: means for releasing the UE context including the updated security context, after a data forwarding tunnel between the first network element and the second network element is established based on the data forwarding address indication.
  • the first network element is a last serving network element, and the second network element is a current serving network element; the first network element and the second network element may be satellite base stations; or the third network element may be an access and mobility management function (AMF) .
  • AMF access and mobility management function
  • the apparatus further comprises means for performing other steps in some embodiments of the method 500.
  • the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
  • an apparatus capable of performing the method 600 may comprise means for performing the respective steps of the method 600.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises: means for receiving, from a first network element serving the cell which is to be served by the second network element after satellite switch, user equipment (UE) context of at least one UE in RRC_INACTIVE state in the cell, before the satellite switch, wherein the UE context includes updated security context wih new security key; and means for storing the UE context including the updated security context with new security key.
  • the UE context including the updated security context with the new security key is received by a next serving network element till the at least one UE has resumed to a connected state.
  • the UE context may be received via a non-UE associated Xn interface message or a UE-associated message, and may be included in a transparent container.
  • the apparatus may comprise means for transmit, a data forwarding address indication including at least one data forwarding address for data transfer, before switching of the cell from the first network element to the second network element, wherein based on the data forwarding address indication, a data forwarding tunnel between the first network element and the second network element is established, and wherein before switching of the cell from the second network element to a next serving network element, a data forwarding address indication including at least one data forwarding address of the next serving network element is transmitted by the next serving network element to the second network element, such that the second network element forwards the data forwarding address indication including at least one data forwarding address of the next serving network element to the first network element to forward data received from a next generation (NG) user plane (NG-U) at the first network element to the next serving network element in a nested tunnel.
  • NG next generation
  • NG-U next generation user plane
  • the apparatus may comprise means for receiving a RRC resume request triggered by the at least one UE, before switching a NG-U downlink (DL) termination point hosted by the first network element to the second network element; and means for transmitting a RRC resume message to the at least one UE based on the UE context including the updated security context, wherein the RRC resume message is encrypted using the new security key.
  • a RRC resume request triggered by the at least one UE, before switching a NG-U downlink (DL) termination point hosted by the first network element to the second network element
  • DL downlink
  • the apparatus may comprise means for transmitting, to a third network element, a path switch request for a plurality of user equipments (UEs) to switch the NG-U DL termination point from the first network element to the second network element, after the plurality of UEs are resumed to the RRC_CONNECTED state; and means for receiving, from the third network element, a path switch request response indicating the NG-U DL termination point has been switched to the second network element.
  • UEs user equipments
  • the apparatus may comprise means for transmitting, to the first network element, a data forwarding address indication including at least one data forwarding address for data transfer, after switching of the cell from the first network element to the second network element, wherein based on the data forwarding address indication, a data forwarding tunnel between the first network element and the second network element is established, and wherein after switching of the cell from the second network element to a next serving network element, a data forwarding address indication including at least one data forwarding address of the next serving network element is received by the second network element from the next serving network element, such that the data forwarding address indication including at least one data forwarding address of the next serving network element is forwarded by the second network element to the first network element for establishing a data forwarding nested tunnel between the first network element and the next serving network element, till a NG-U DL termination point hosted by the first network element is switched to a network element where the at least one UE is resumes connection from the inactive state to the connected state.
  • the apparatus may comprise means for receiving a RRC resume request triggered by the at least one UE, after switching a NG-U downlink (DL) termination point hosted by the first network element to the second network element; and means for transmitting a RRC resume message to the at least one UE based on the UE context including the updated security context, wherein the RRC resume message is encrypted using the new security key.
  • a RRC resume request triggered by the at least one UE, after switching a NG-U downlink (DL) termination point hosted by the first network element to the second network element
  • DL downlink
  • the apparatus may comprise means for transmitting, to a third network element, a path switch request for a plurality of user equipments (UEs) to switch the NG-U DL termination point from the first network element to the second network element, after the UE context including the updated security context with the new security key is received by the second network element while the plurality of UEs is still in the inactive state; and means for receiving, from the third network element, a path switch request response indicating the NG-U DL termination point has been switched to the second network element.
  • UEs user equipments
  • the first network element is a last serving network element, and the second network element is a current serving network element; the first network element and the second network element may be satellite base stations; or the third network element may be an access and mobility management function (AMF) .
  • AMF access and mobility management function
  • the apparatus further comprises means for performing other steps in some embodiments of the method 600.
  • the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.
  • an apparatus capable of performing the method 700 may comprise means for performing the respective steps of the method 700.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises: means for receiving, from a second network element which is to serve a cell served by a first network element, a path switch request for a plurality of user equipments (UEs) to switch a next generation (NG) user plane (NG-U) downlink (DL) termination point hosted by the first network element to the second network element; and means for transmitting, to the second network element, a path switch response indicating the NG-U DL termination point has been switched to the second network element.
  • NG next generation
  • NG-U next generation
  • DL downlink
  • the path switch request response may be received after the plurality of UEs are resumed to the RRC_CONNECTED state.
  • the apparatus comprises: means for transmitting, to the first network element, an indication to release UE context of the plurality of UEs.
  • the path switch request response may be received after UE context of the plurality of UEs is transfer from the first network element to the second network element while the plurality of UEs are still in the inactive state.
  • the first network element is a last serving network element, and the second network element is a current serving network element; the first network element and the second network element may be satellite base stations; or the third network element may be an access and mobility management function (AMF) .
  • AMF access and mobility management function
  • FIG. 8 illustrates a simplified block diagram of a device 800 that is suitable for implementing some example embodiments of the present disclosure.
  • the device 800 may be provided to implement a communication device, for example, the first network element 120 or the second network element 130 or the third network element 141 as shown in FIG. 1A.
  • the device 800 includes one or more processors 810, one or more memories 820 coupled to the processor 810, and one or more communication modules 840 coupled to the processor 810.
  • the communication module 840 is for bidirectional communications.
  • the communication module 840 has at least one antenna to facilitate communication.
  • the communication interface may represent any interface that is necessary for communication with other network elements.
  • the processor 810 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 820 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 824, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage.
  • the volatile memories include, but are not limited to, a random access memory (RAM) 822 and other volatile memories that will not last in the power-down duration.
  • the embodiments of the present disclosure may be implemented by means of the program 830 so that the device 800 may perform any process of the disclosure as discussed with reference to FIGS. 2-7.
  • the embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 830 may be tangibly contained in a computer-readable medium which may be included in the device 800 (such as in the memory 820) or other storage devices that are accessible by the device 800.
  • the device 800 may load the program 830 from the computer-readable medium to the RAM 822 for execution.
  • the computer-readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • FIG. 9 illustrates a block diagram of an example of a computer-readable medium 900 in accordance with some example embodiments of the present disclosure.
  • the computer-readable medium 900 has the program 830 stored thereon. It is noted that although the computer-readable medium 900 is depicted in form of CD or DVD in FIG. 1A1, the computer-readable medium 900 may be in any other form suitable for carry or hold the program 830.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method 500, 600 and 700 as described above with reference to FIG. 5, FIG 6 or FIG 7.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer-readable medium, and the like.
  • the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium.
  • a computer-readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer-readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • non-transitory is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • General Physics & Mathematics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des exemples de modes de réalisation de la présente divulgation proposent une solution permettant de prendre en charge des équipements utilisateurs (UE) à l'état inactif dans des réseaux de communication. Dans un procédé donné à titre d'exemple, un premier élément de réseau met à jour, sur la base d'une nouvelle clé de sécurité dérivée, le contexte de sécurité inclus dans le contexte d'UE d'au moins un UE dans un état inactif dans une cellule, et transmet, à un deuxième élément de réseau qui doit desservir la cellule après la commutation par satellite, le contexte d'UE comprenant le contexte de sécurité mis à jour avec la nouvelle clé de sécurité, avant le commutateur satellite. Le deuxième élément de réseau reçoit et stocke le contexte d'UE comprenant le contexte de sécurité mis à jour avec la nouvelle clé de sécurité, avant la commutation par satellite. De cette manière, le transfert proactif du contexte d'UE comprenant le contexte de sécurité mis à jour avec une nouvelle clé de sécurité pour des UE dans l'état inactif est activé, pour faciliter la reprise de connexion.
PCT/CN2024/077598 2024-02-19 2024-02-19 Améliorations apportées à la prise en charge d'un état rrc_inactif Pending WO2025175429A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/077598 WO2025175429A1 (fr) 2024-02-19 2024-02-19 Améliorations apportées à la prise en charge d'un état rrc_inactif

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/077598 WO2025175429A1 (fr) 2024-02-19 2024-02-19 Améliorations apportées à la prise en charge d'un état rrc_inactif

Publications (1)

Publication Number Publication Date
WO2025175429A1 true WO2025175429A1 (fr) 2025-08-28

Family

ID=96846371

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/077598 Pending WO2025175429A1 (fr) 2024-02-19 2024-02-19 Améliorations apportées à la prise en charge d'un état rrc_inactif

Country Status (1)

Country Link
WO (1) WO2025175429A1 (fr)

Similar Documents

Publication Publication Date Title
CN113661733B (zh) 用于核心网络节点间的切换
EP4022977B1 (fr) Réduction de signalisation lors d'un transfert intercellulaire d'un noeud iab
US20250126537A1 (en) Mechanism for transition to another cell without handover in a non-terrestrial network
WO2022056693A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2025175429A1 (fr) Améliorations apportées à la prise en charge d'un état rrc_inactif
EP4278749A1 (fr) Procédés, dispositifs et support de communication
US20240015594A1 (en) Uplink Data Duplication Avoidance
US12127051B2 (en) Device, method, apparatus and computer readable medium for inter-master node handover
US20240129989A1 (en) Method, device and computer storage medium of communication
WO2021243518A1 (fr) Accès initial de dispositif distant via un relais
WO2022027380A1 (fr) Dispositif, procédé, appareil et support lisible par ordinateur pour communication iab
WO2025060001A1 (fr) Transfert intercellulaire dans un scénario lorsque à la fois une unité distribuée source et une unité distribuée cible sont co-localisées
WO2025030345A1 (fr) Mécanisme de sélection d'un dispositif de réseau non terrestre
WO2025199930A1 (fr) Fourniture d'informations de relations de voisinage
WO2024055172A1 (fr) Transfert de trafic dans un scénario de relais d'équipement utilisateur à réseau
WO2024227300A1 (fr) Achèvement d'une procédure de strate de non-accès dans une architecture stockage et transmission
WO2025171589A1 (fr) Mappage de trafic de plan utilisateur
US20250056250A1 (en) Master node centric reference configuration generation
WO2024065209A1 (fr) Transmission de données précoce à destination d'un mobile pour internet des objets
WO2024243880A1 (fr) Valeur de temporisateur de strate de non-accès dynamique dans un réseau non terrestre
WO2025166586A1 (fr) Migration mobile d'accès intégré et de liaison terrestre (iab)
US12507313B2 (en) Mobile terminated small data transmission bearer handling
WO2025076785A1 (fr) Création de rapport de qualité d'expérience avec des informations de transfert
US20250056520A1 (en) Beam management assistance
WO2025112008A1 (fr) Communication sécurisée dans un système d'enregistrement et retransmission de réseau non terrestre

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

Country of ref document: EP

Kind code of ref document: A1