[go: up one dir, main page]

WO2019063086A1 - Transfert de contexte par l'intermédiaire du dernier nœud ran visité - Google Patents

Transfert de contexte par l'intermédiaire du dernier nœud ran visité Download PDF

Info

Publication number
WO2019063086A1
WO2019063086A1 PCT/EP2017/074698 EP2017074698W WO2019063086A1 WO 2019063086 A1 WO2019063086 A1 WO 2019063086A1 EP 2017074698 W EP2017074698 W EP 2017074698W WO 2019063086 A1 WO2019063086 A1 WO 2019063086A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
last visited
identifier
context
cell
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2017/074698
Other languages
English (en)
Inventor
Philippe Godin
Alessio Casati
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 Technologies Oy
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/EP2017/074698 priority Critical patent/WO2019063086A1/fr
Publication of WO2019063086A1 publication Critical patent/WO2019063086A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present invention relates to an apparatus, a method, and a computer program product related to context transfer, and in particular to context transfer in mobile networks.
  • RNA RAN Notification Area
  • the terminal if the terminal is in the inactive state in the notification area, the terminal does not inform another cell of the notification area on a location update when it moves from the last visited cell of the notification area to the other cell of the notification area, and, the terminal informs a new cell (or its base station) outside the notification area on the location update when it moves from the last visited cell of the notification area to the new cell outside the notification area.
  • the inactive state intends to limit battery consumption for the UE similarly to the idle state, while at the same time the UE may reach the connected state with little signalling (less signalling compared to transition from idle state to connected state) when to send data.
  • the UE In inactive state, the UE remains ECM-connected from 5GC (5G core network) point of view and therefore the NG connection between 5GC and gNB is maintained. This means that, when a packet arrives for paging the UE (mobile terminating call), the packet gets routed directly to the last serving gNB (called anchor gNB) which triggers itself the RAN paging in the RNA. I.e.
  • the anchor gNB pages the UE in its cells of the RNA and sends an Xn Paging message (a paging message over the Xn interface) to its neighbour gNBs of the RNA, which in turn page the UE in their cells.
  • the Xn interface is a direct interface between two base stations acting as peers, wherein the peers terminate the XnAP protocol.
  • the location of the UE is monitored by the RAN. More precisely, whenever the UE moves out of the RNA it must inform the anchor gNB with an RRC Location Update message: If in this case the UE is located under a new gNB, the anchor function is relocated and the new gNB becomes the new anchor gNB.
  • a UE is configured from connected state into inactive state by its last serving gNB which sends to the UE an RRC Suspend message including the applicable RNA.
  • the last serving gNB becomes the anchor gNB for the UE keeping the UE context when the UE is in inactive state.
  • This last serving gNB would typically configure an RNA comprising a list of cells or a list of "RAN Areas" which in general includes one or more cells of the last serving gNB and possibly includes one or more cells of one or more neighbour gNBs with which the last serving gNB has a direct connection (Xn connectivity).
  • the last requirement is set to make the paging successful. Indeed, if t e RNA comprised a cell whose gNB is not Xn-connected to the anchor gNB, then the RAN paging would not reach that gNB and therefore would not reach the UE.
  • the UE When the UE moves out of the RNA it must inform the anchor gNB so that a new RNA can be configured to the UE and possibly the anchor function may be relocated.
  • the first cell seen (reached) by the UE out of the RNA can be a cell of a new gNB (i.e. UE changes gNB when moving out of the RNA).
  • the RRC Location Update message sent by the UE is received by this new gNB which must relay it to the anchor gNB over Xn.
  • the new gNB typically triggers an Xn context fetch procedure to also retrieve the UE context (or part thereof).
  • RNA with Xn reachability i.e. comprising either its own cells or cells of neighbour gNBs with which it has Xn connectivity
  • the "best existing” solution proposed so far in 3GPP is to use the 5GC (5G Core Network) as a relay.
  • 5GC 5G Core Network
  • the new gNB When receiving the RRC Location Update message from the UE, the new gNB typically triggers an NG message "context fetch request" towards an AMF including an anchor gNB ID and its own new gNB ID.
  • the AMF recognizes the anchor gNB ID and relays this request over NG interface towards the anchor gNB.
  • the anchor gNB ID replies with NG Context fetch response message towards the AMF including the context of the UE and setting the received new gNB ID as destination.
  • the AMF recognizes the new gNB ID and is able to propagate the NG Context fetch response message towards the new gNB.
  • New gNB gets the UE context.
  • the context retrieval involving the core network will introduce an extra delay which is critical, especially for paging time.
  • the UE access stratum context transfer does not remain confined within the RAN while the UE is RRC-INACTIVE, which is not consistent with the fact that the UE is perceived to be connected to a certain gNB with no need to transfer state transitions to the CN.
  • the new gNB and the anchor gNB do not share a AMF.
  • the right peer CN node has to be found where to send the context transfer request if this was via the CN and if the new AMF does not have a NG relationship with the anchor gNB (for sure the NG relationship to the same AMF exists inside the RNA, but this is not guaranteed outside).
  • the new AMF does not have a NG relationship with the anchor gNB (for sure the NG relationship to the same AMF exists inside the RNA, but this is not guaranteed outside).
  • a context comprises information (e.g. parameters) which are relevant for at least one of authenticaton, authorization, accounting, security information, radio bearer information, header compression, QoS, Policy, sub-IP protocols, and services for the UE.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform checking if a terminal is in an inactive state in a notification area, monitoring if the terminal moves from a last visited cell of the notification area to a new cell outside the notification area; instructing the terminal to provide an anchor base station identifier of an anchor base station, a context identifier of a context for the terminal, and at least one of a last visited cell identifier of the last visited cell and a last visited base station identifier of a last visited base station to the new base station if the terminal is in the inactive state and moves from the last visited cell to the new cell;
  • the last visited cell belongs to the last visited base station
  • the new cell belongs to the new base station.
  • At least one of the anchor base station identifier, the context identifier, and the at least one of the last visited cell identifier and the last visited base station identifier may be provided along with the informing of the new cell on the location update of the terminal from the last visited cell to the new cell.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform monitoring if a new base station receives, from a terminal, location update information for the terminal, an anchor base station identifier of an anchor base station, a context identifier of a context, and at least one of a last visited cell identifier of a last visited cell and a last visited base station identifier of a last visited base station; checking if a first direct connection between the new base station and the anchor base station exists if the location update information and the anchor base station identifier are received; instructing the new base station to request the context from the anchor base station via the last visited base station if the first direct connection does not exist and the at least one of the last visited cell identifier and the last visited base station identifier is received; wherein the request for the context from the anchor base station comprises the anchor base
  • the at least one processor may be arranged to cause the apparatus to further perform, if the last visited cell identifier of the last visited cell is received and the last visited base station identifier is not received, identifying the last visited base station based on the last visited cell identifier, wherein the last visited cell belongs to the last visited base station.
  • At least one of the anchor base station identifier, the context identifier, and the at least one of the last visited cell identifier and the last visited base station identifier may be comprised in the location update information from the terminal.
  • the context may be requested via a second direct connection between the new base station and the last visited base station.
  • At least one of the first direct connection and the second direct connection may be based on an Xn interface.
  • an apparatus comprising at least one processor, at least one memory including computer program code, and the at least one processor, with the at least one memory and the computer program code, being arranged to cause the apparatus to at least perform supervising if a last visited base station receives a request for a context from a new base station, wherein the request for the context comprises an anchor base station identifier of an anchor base station and a context identifier of the context; instructing the last visited base station to ask the anchor base station for the context if the last visited base station receives the request; monitoring if the last visited base station receives the context from the anchor base station in response to the asking for the context; prompting the last visited base station to forward the context to the new base station in response to the received request if the last visited base station receives the context.
  • the anchor base station may be asked for the context via a first direct connection between the last visited base station and the anchor base station; and/or the request may be received and the context may be forwarded via a second direct connection between the last visited base station and the new base station.
  • At least one of the first direct connection and the second direct connection may be based on an Xn interface.
  • the at least one processor may be arranged to cause the apparatus to further perform checking, if the request is received, if the anchor base station identifier identifies the last visited base station; inhibiting the instructing of the last visited base station if the anchor base station identifier identifies the last visited base station.
  • a method comprising checking if a terminal is in an inactive state in a notification area, monitoring if the terminal moves from a last visited cell of the notification area to a new cell outside the notification area; instructing the terminal to provide an anchor base station identifier of an anchor base station, a context identifier of a context for the terminal, and at least one of a last visited cell identifier of the last visited cell and a last visited base station identifier of a last visited base station to the new base station if the terminal is in the inactive state and moves from the last visited cell to the new cell; wherein the last visited cell belongs to the last visited base station; the new cell belongs to the new base station.
  • At least one of the anchor base station identifier, the context identifier, and the at least one of the last visited cell identifier and the last visited base station identifier may be provided along with the informing of the new cell on the location update of the terminal from the last visited cell to the new cell.
  • a method comprising monitoring if a new base station receives, from a terminal, location update information for the terminal, an anchor base station identifier of an anchor base station, a context identifier of a context, and at least one of a last visited cell identifier of a last visited cell and a last visited base station identifier of a last visited base station; checking if a first direct connection between the new base station and the anchor base station exists if the location update information and the anchor base station identifier are received; instructing the new base station to request the context from the anchor base station via the last visited base station if the first direct connection does not exist and the at least one of the last visited cell identifier and the last visited base station identifier is received; wherein the request for the context from the anchor base station comprises the anchor base station identifier and the context identifier.
  • the method may further comprise, if the last visited cell identifier of the last visited cell is received and the last visited base station identifier is not received, identifying the last visited base station based on the last visited cell identifier, wherein the last visited cell belongs to the last visited base station.
  • At least one of the anchor base station identifier, the context identifier, and the at least one of the last visited cell identifier and the last visited base station identifier may be comprised in the location update information from the terminal.
  • the context may be requested via a second direct connection between the new base station and the last visited base station.
  • At least one of the first direct connection and the second direct connection may be based on an Xn interface.
  • a method comprising supervising if a last visited base station receives a request for a context from a new base station, wherein the request for the context comprises an anchor base station identifier of an anchor base station and a context identifier of the context; instructing the last visited base station to ask the anchor base station for the context if the last visited base station receives the request; monitoring if the last visited base station receives the context from the anchor base station in response to the asking for the context; prompting the last visited base station to forward the context to the new base station in response to the received request if the last visited base station receives the context.
  • the anchor base station may be asked for the context via a first direct connection between the last visited base station and the anchor base station; and/or the request may be received and the context may be forwarded via a second direct connection between the last visited base station and the new base station.
  • At least one of the first direct connection and the second direct connection may be based on an Xn interface.
  • the method may further comprise checking, if the request is received, if the anchor base station identifier identifies the last visited base station; inhibiting the instructing of the last visited base station if the anchor base station identifier identifies the last visited base station.
  • Each of the methods of the fourth to sixth aspects may be a method of context fetching.
  • 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 fourth to sixth aspects.
  • the computer program product may be embodied as a computer-readable medium or directly loadable into a computer.
  • the concentration of processing load in the AMF central node is avoided by using a distributed mechanism.
  • the processing load is spread across many gNBs instead of being concentrated in the AMF.
  • Fig. 1 shows a call flow according to an embodiment of the invention
  • Fig. 2 shows an apparatus according to an embodiment of the invention
  • Fig. 3 shows a method according to an embodiment of the invention
  • Fig. 4 shows an apparatus according to an embodiment of the invention
  • Fig. 5 shows a method according to an embodiment of the invention
  • Fig. 6 shows an apparatus according to an embodiment of the invention
  • Fig. 7 shows a method according to an embodiment of the invention.
  • Fig. 8 shows an apparatus according to an 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.
  • Some embodiments of the invention provide mechanisms to inform the anchor gNB on the location update of the UE to a new gNB outside the RNA and to transfer the context for the UE to the new gNB.
  • the UE when the UE moves out of the RNA it includes the identity of the last cell (e.g. NGCI) which it has visited in the RNA in the RRC Location Update message to the new gNB, in addition to anchor gNB ID and UE context ID.
  • the new gNB extracts from the identity of the last visited cell (its NGCI) the identity of the gNB serving the last visited cell in the RNA, i.e. the identity of the Last Visited gNB (LV gNB) in the last used RNA.
  • the new gNB sends over a direct Xn interface to the LV gNB (also named relay gNB) an Xn message (called e.g. Xn Relay message) which includes the anchor gNB ID as destination, the new gNB ID as source, and the Xn context fetch request comprising the UE context ID.
  • Xn Relay message an Xn message which includes the anchor gNB ID as destination, the new gNB ID as source, and the Xn context fetch request comprising the UE context ID.
  • the LV gNB propagates the Xn Context fetch request towards the anchor gNB over a second direct interface between the LV gNB and the anchor gNB.
  • the new gNB may provide to the Anchor gNB, via the relay gNB (LV gNB), all the information a new gNB being Xn connected with the Anhor gNB would provide, in order for the Anchor gNB e.g. to compute the security keys for the UE in the New gNB.
  • LV gNB relay gNB
  • the same mechanism is used by the anchor gNB to reply via the LV gNB to the new gNB by sending a Relay Response Xn message including the new gNB ID as destination, the anchor gNB ID as source and including the UE context.
  • Embodiments of the invention avoid at least some of the drawbacks mentioned above of the "best existing" solution.
  • the request for the context and the response via the relay gNB are transmitted via respective direct interfaces (i.e. a first Xn interface between anchor gNB and relay gNB and a second Xn interface between the relay gNB and the new gNB in the case of Xn interfaces)
  • the context fetch is confined to the RAN such that one of the purposes of the inactive state feature are fulfilled.
  • the term "direct interface” relates to the logical structure of the interface which does not comprise an intervening node on the top layer. However, on the lower layers, the interface may be based on intervening nodes such as routers, bridges, etc.
  • the CN e.g. 5GC
  • the UE provides the ID of the anchor gNB, the context ID, and the ID of the previous visited cell in the location update message to the new gNB.
  • the UE provides one or more of these information elements in one or more additional messages different from the location update message to the new gNB. Preferably, such additional message(s) follow the location update message, but they may precede the location update message instead.
  • Fig. 1 shows a call flow according to an embodiment of the invention.
  • the call flow may be performed when the UE moves from a cell of the LV gNB in the RNA to a cell of the new gNB outside the RNA, wherein the anchor gNB and the new gNB are not Xn connected.
  • the UE provides in the RRC location update message to the new gNB an ID of the last visited cell (LV NGCI), an ID of the anchor gNB, and a UE context ID, which identifies the context for the UE kept in the anchor gNB.
  • LV NGCI the last visited cell
  • UE context ID which identifies the context for the UE kept in the anchor gNB.
  • the new gNB derives the ID of the gNB to which the last visited cell belongs (LV gNB-ID) from LV NGCI. Then, it issues, via XN interface to the LV gNB (relay gNB), an Xn relay request containing a context fetch request, which comprises the ID of the new gNB, the ID of the anchor gNB, and context fetch information including at least the UE context ID.
  • the LV gNB propagates the Xn context fetch request to the Anchor gNB via the Xn interface between LV gNB and anchor gNB.
  • the anchor gNB provides the context to the LV gNB, which forwards the context to the new gNB in response to the Xn relay request.
  • the request from the LV gNB (relay gNB) arriving at the anchor gNB may have the same format as a corresponding request from a new gNB outside the RNA which is Xn connected to the anchor gNB.
  • the destination indicated in the request (new gNB) is different from the originator of the request (relay gNB) arriving at the anchor gNB, while, in the latter case, these identifiers may be the same.
  • the anchor gNB does not check if these IDs are the same, the anchor gNB need not to be modified over a conventional anchor gNB such that embodiments of the invention may be backwards compatible with respect to the anchor gNB.
  • At least one of the request from the new gNB to the relay gNB and the request from the relay gNB to the anchor gNB may not comprise an indication of the final destination for the context (i.e. the ID of the new gNB).
  • the anchor gNB may not need this information.
  • the relay gNB knows the new gNB because it receives the request from the new gNB.
  • the UE may provide to the new gNB an identifier of the LV gNB instead of or in addition to the LV NGCI.
  • the new gNB need not to derive the ID of the LV gNB from the LV NGCI.
  • the identifier of the LV gNB may be embedded in the cell identifier of the last visited cell.
  • Fig. 2 shows an apparatus according to an embodiment of the invention.
  • the apparatus may be a terminal such as a UE, an loT device, a MTC device, or an element thereof.
  • Fig. 3 shows a method according to an embodiment of the invention.
  • the apparatus according to Fig. 2 may perform the method of Fig. 3 but is not limited to this method.
  • the method of Fig. 3 may be performed by the apparatus of Fig. 2 but is not limited to being performed by this apparatus.
  • the apparatus comprises checking means 10, monitoring means 20, and instructing means 30.
  • Each of the checking means 10, monitoring means 20, and instructing means 30 may be a checker, monitor, and instructor, respectively.
  • Each of the checking means 10, monitoring means 20, and instructing means 30 may be a checking processor, monitoring processor, and instructing processor, respectively.
  • the checking means 10 checks if a terminal is in an inactive state (e.g. RRC_inactive state) in a notification area (e.g. RNA) (S10). If the terminal is in the inactive state in the notification area, the terminal does not inform another cell of the notification area on a location update when it moves from the last visited cell of the notification area to the other cell of the notification area, and, the terminal informs a new cell outside the notification area on the location update when it moves from the last visited cell of the notification area to the new cell outside the notification area.
  • an inactive state e.g. RRC_inactive state
  • a notification area e.g. RNA
  • the monitoring means 20 monitors if the terminal moves from a last visited cell of the notification area to a new cell outside the notification area (S20).
  • the last visited cell belongs to a last visited base station (sometimes also called relay base station), and the new cell belongs to a new base station.
  • S10 and S20 may follow S10, or S10 may follow S20.
  • S10 and S20 may be performed fully or partly in parallel.
  • the terminal may provide a location update information to the new cell because it is in the inactive state in the notification area and the new cell is outside the notification area.
  • this step may be outside the claimed method and may be controlled by another apparatus.
  • the instructing means instructs the terminal to provide an anchor base station identifier of an anchor base station, a context identifier of a context for the terminal, and at least one of a last visited cell identifier of the last visited cell and a last visited base station identifier of a last visited base station to the new base station (S30).
  • Fig. 4 shows an apparatus according to an embodiment of the invention.
  • the apparatus may be a base station such as a NB (e.g. gNB or eNB), or an element thereof. It may have the role of a new base station.
  • Fig. 5 shows a method according to an 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 monitoring means 1 10, checking means 120, and instructing means 130.
  • Each of the monitoring means 1 10, checking means 120, and instructing means 130 may be a monitor, checker, and instructor, respectively.
  • Each of the monitoring means1 10, checking means 120, and instructing means 130 may be a monitoring processor, checking processor, and instructing processor, respectively.
  • the monitoring means 1 10 monitors if a new base station receives, from a terminal (e.g. UE), location update information for the terminal, an anchor base station identifier of an anchor base station, a context identifier of a context, and at least one of a last visited cell identifier of a last visited cell and a last visited base station identifier of a last visited base station (S1 10). If the last visited cell identifier is provided, the apparatus assumes that the last visited cell belongs to the last visited base station.
  • a terminal e.g. UE
  • the checking means 120 checks if a first direct connection between the new base station and the anchor base station exists (S120).
  • the request for the context from the anchor base station comprises the anchor base station identifier and the context identifier. It may additionally comprise an identifier of the new base station. Due to S130, the last visited base station is sometimes called a relay base station.
  • Fig. 6 shows an apparatus according to an embodiment of the invention.
  • the apparatus may be a base station such as a NB (e.g. gNB or eNB), or an element thereof. It may have the role of a relay base station and of the last visited base station in the RNA for a terminal.
  • Fig. 7 shows a method according to an 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 supervising means 210, instructing means 230, monitoring means 240, and prompting means 250.
  • Each of the supervising means 210, instructing means 230, monitoring means 240, and prompting means 250 may be a supervisor, instructor, monitor, and prompter, respectively.
  • Each of the supervising means 210, instructing means 230, monitoring means 240, and prompting means 250 may be a supervising processor, instructing processor, monitoring processor, and prompting processor, respectively.
  • the apparatus may comprise checking means 220 which may be a checker or a checking processor.
  • the supervising means 210 supervises if a last visited base station (sometimes also named relay base station) receives a request for a context from a new base station (S210).
  • the request for the context comprises an anchor base station identifier of an anchor base station and a context identifier of the context.
  • the instructing means 230 instructs the last visited base station to ask the anchor base station for the context (S230).
  • the monitoring means 240 monitors if the last visited base station receives the context from the anchor base station in response to the asking for the context instructed in S230 (S240).
  • the prompting means 250 prompts the last visited base station to forward the context to the new base station in response to the request received in S210 (S250).
  • Fig. 8 shows an apparatus according to an embodiment of the invention.
  • the apparatus comprises at least one processor 410, at least one memory 420 including computer program code, and the at least one processor 410, with the at least one memory 420 and the computer program code, being arranged to cause the apparatus to at least perform at least one of the methods according to Figs. 3, 5, and 7.
  • the term "context" in the present application includes both the full context and a portion of the context.
  • Embodiments of the invention are described with respect to a UE.
  • a UE is a particular kind of a terminal. All kinds of terminals may belong to embodiments of the invention. E.g., terminals in which embodiments of the invention are implemented may be a loT device, a MTC device, a laptop, a tablet, a smartphone, a mobile phone, etc.
  • the invention is described for a 5G network. However, it may be employed also in other networks of other radio technologies where a concept of an inactive state (such as RRCjnactive state) in a notification area (such as a RAN notification area) exists, even if different terms may be used in other technologies.
  • the terminal does not inform a new cell on a location update if the new cell is in the notification area, and informs the new cell on the location update if the new cell is not in the notification area, wherein the context of the terminal is kept at an anchor base station while the terminal moves in the notification area.
  • another direct interface between base stations than the Xn interface may be used, such as an X2 interface in LTE and LTE-A.
  • a base station may be a RAN node of the respective radio technology.
  • 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, protocols, and methods are based on current standards. In other versions or other technologies, the names of these network elements and/or protocols and/or methods may be different, as long as they provide a corresponding functionality.
  • 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 embodied in the cloud.
  • example embodiments of the present invention provide, for example, a terminal such as a UE, an loT device, a MTC device 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 base station such as a NB (e.g.
  • gNB gNode B
  • eNB eNode B
  • 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.

Landscapes

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

Abstract

L'invention concerne un procédé consistant à surveiller si une nouvelle station de base reçoit, en provenance d'un terminal, des informations de mise à jour de localisation pour le terminal, un identifiant de station de base d'ancrage, un identifiant de contexte et l'identifiant de la dernière cellule visitée et/ou l'identifiant de la dernière station de base visitée ; à vérifier si une première connexion directe entre la nouvelle station de base et la station de base d'ancrage existe si les informations de mise à jour de localisation et l'identifiant de station de base d'ancrage sont reçus ; à ordonner à la nouvelle station de base de demander le contexte à la station de base d'ancrage par l'intermédiaire de la dernière station de base visitée si la première connexion directe n'existe pas et que l'identifiant de la dernière cellule visitée et/ou l'identifiant de la dernière station de base visitée sont reçus ; la demande de contexte à la station de base d'ancrage comprenant l'identifiant de station de base d'ancrage et l'identifiant de contexte.
PCT/EP2017/074698 2017-09-28 2017-09-28 Transfert de contexte par l'intermédiaire du dernier nœud ran visité Ceased WO2019063086A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/074698 WO2019063086A1 (fr) 2017-09-28 2017-09-28 Transfert de contexte par l'intermédiaire du dernier nœud ran visité

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/074698 WO2019063086A1 (fr) 2017-09-28 2017-09-28 Transfert de contexte par l'intermédiaire du dernier nœud ran visité

Publications (1)

Publication Number Publication Date
WO2019063086A1 true WO2019063086A1 (fr) 2019-04-04

Family

ID=60043166

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/074698 Ceased WO2019063086A1 (fr) 2017-09-28 2017-09-28 Transfert de contexte par l'intermédiaire du dernier nœud ran visité

Country Status (1)

Country Link
WO (1) WO2019063086A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109819392A (zh) * 2017-11-20 2019-05-28 华为技术有限公司 一种位置信息的上报方法和装置
US12185219B2 (en) 2020-09-15 2024-12-31 Nokia Technologies Oy NG based context release and data forwarding for multi-hop mobility

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2426976A1 (fr) * 2009-04-27 2012-03-07 NTT DoCoMo, Inc. Système de communication mobile
US20170078940A1 (en) * 2014-03-06 2017-03-16 Nec Corporation Apparatus, system and method for dual connectivity

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2426976A1 (fr) * 2009-04-27 2012-03-07 NTT DoCoMo, Inc. Système de communication mobile
US20170078940A1 (en) * 2014-03-06 2017-03-16 Nec Corporation Apparatus, system and method for dual connectivity

Non-Patent Citations (8)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP) (Release 15)", 3GPP STANDARD; 3GPP TS 38.413, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. V0.3.0, 4 September 2017 (2017-09-04), pages 1 - 85, XP051336843 *
EIKO SEIDEL: "3GPP 5G RAN Study Completed", 31 March 2017 (2017-03-31), XP055425158, Retrieved from the Internet <URL:http://www.nomor.de/uploads/6d/ca/6dca62aa90c67f23a89822f614b6c59b/2017-03-3GPP-5G-RAN-Study-Completed-v1-0.pdf> [retrieved on 20171115] *
ERICSSON: "Signalling flows for paging and resume for RRC_INACTIVE", vol. RAN WG2, no. Spokane, Wa; 20170117 - 20170119, 17 January 2017 (2017-01-17), XP051211108, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170117] *
HAILU SOFONIAS ET AL: "Hybrid paging and location tracking scheme for inactive 5G UEs", 2017 EUROPEAN CONFERENCE ON NETWORKS AND COMMUNICATIONS (EUCNC), IEEE, 12 June 2017 (2017-06-12), pages 1 - 6, XP033122294, DOI: 10.1109/EUCNC.2017.7980730 *
HUAWEI: "S1 Context fetch for Light Connection", vol. RAN WG3, no. Reno, Nevada; 20161114 - 20161118, 14 November 2016 (2016-11-14), XP051178863, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN3/Docs/> [retrieved on 20161114] *
LG ELECTRONICS INC: "UE context management between eNBs without X2 interface", vol. RAN WG3, no. Athens, Greece; 20170213 - 20170217, 12 February 2017 (2017-02-12), XP051213136, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN3/Docs/> [retrieved on 20170212] *
NOKIA ET AL: "Response to R3-173945", 10 October 2017 (2017-10-10), XP055425630, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN3/Docs> [retrieved on 20171116] *
PATRIK RUGELAND ET AL: "5G PPP mmMAGIC Architectural enablers and concepts for mm-wave RAN integration", 29 March 2017 (2017-03-29), XP055424624, Retrieved from the Internet <URL:https://bscw.5g-mmmagic.eu/pub/bscw.cgi/d187833/mmMAGIC_Architectural_enablers_mmWave_integration.pdf> [retrieved on 20171114] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109819392A (zh) * 2017-11-20 2019-05-28 华为技术有限公司 一种位置信息的上报方法和装置
US11463981B2 (en) 2017-11-20 2022-10-04 Huawei Technologies Co., Ltd. Location information reporting method and apparatus
US12185219B2 (en) 2020-09-15 2024-12-31 Nokia Technologies Oy NG based context release and data forwarding for multi-hop mobility

Similar Documents

Publication Publication Date Title
US11937131B2 (en) Resume request followed by release and redirect
CN113329462B (zh) 用于双活跃连接切换的方法和设备
US20240349246A1 (en) Methods and apparatuses for paging in a communications network
EP3046389B1 (fr) Procede, dispositif et systeme de communication
KR102264618B1 (ko) 통신 방법, 액세스 네트워크 장치, 및 단말기
CN109845361B (zh) 用于在无线通信网络中寻呼无线设备的无线电接入网络节点和核心网络节点
US11202338B2 (en) Session establishment method and apparatus
CN113316223B (zh) 一种状态切换方法及装置
EP3567973B1 (fr) Procédé de communication, terminal et dispositif de réseau d&#39;accès
EP2567525B1 (fr) Gestion d&#39;un temporisateur d&#39;enregistrement pour assurer une continuité de services dans le système ims
CN102724704A (zh) 服务核心网络节点变更时处理移动装置的可联系性的方法
CN110089194A (zh) 使配置双连接的无线终端能够进入不活动模式的方法和节点
CN110754112B (zh) 网络接入方法以及移动性支持和数据传送的方法和装置
CN113647162B (zh) 无线通信装置及操作方法、通信网络的节点及操作方法
US9655079B2 (en) Apparatus and method for paging in wireless communication system
US10237780B2 (en) Method for allowing user equipment to detach from network entity
CN111699703B (zh) 在无线电接入网中对数据进行路由的方法、基站、终端
WO2019063086A1 (fr) Transfert de contexte par l&#39;intermédiaire du dernier nœud ran visité
WO2020034802A1 (fr) Procédé et dispositif d&#39;activation de session pdu
CN107404762A (zh) 资源处理方法及装置
CN109479228B (zh) 一种数据处理方法及装置
CN112822789A (zh) 非激活态终端的重定向方法、电子设备及计算机可读介质
WO2018001301A1 (fr) Procédé, appareil et système de commande d&#39;équipement d&#39;utilisateur, et passerelle de réseau
CN116076124A (zh) 数据传输控制信息的扩展缓冲
CN117676741A (zh) QoS信息的发送方法、接收方法、装置、设备及介质

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17781050

Country of ref document: EP

Kind code of ref document: A1