Sign In to Follow Application
View All Documents & Correspondence

Base Station, Radio Terminal, And Methods Therefor

Abstract: This base station (1) controls the state transition of a wireless terminal (2) among a first RRC state a second RRC state and a third RRC state. Further the base station (1) explicitly or implicitly notifies to the wireless terminal (2) whether or not a network slice that has been set to the wireless terminal (2) for data communication in at least the first RRC state is available in each cell included in a RAN notification area that has been set by a RAN (3). Thus for example a wireless terminal in a first state (e.g. a RRC_INACTIVE state) can easily know the availability of a network slice in a cell to be reselected or a cell that has been reselected.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
02 July 2019
Publication Number
34/2019
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
archana@anandandanand.com
Parent Application
Patent Number
Legal Status
Grant Date
2023-08-08
Renewal Date

Applicants

NEC CORPORATION
7-1, Shiba 5-chome, Minato-ku, Tokyo 1088001

Inventors

1. FUTAKI Hisashi
c/o NEC Corporation, 7-1, Shiba 5-chome, Minato-ku, Tokyo 1088001
2. HAYASHI Sadafuku
c/o NEC Corporation, 7-1, Shiba 5-chome, Minato-ku, Tokyo 1088001

Specification

0001]The present disclosure relates to wireless communication systems and, more particularly, the wireless terminal mobility.
BACKGROUND
[0002]3rd Generation Partnership Project (3GPP) has (see Non-Patent Document 1) fifth standardization work generation mobile communication system (5G) as 3GPP Release 14 have started in 2016 towards the introduction of after 2020. 5G is realized by a combination of innovative improvement and development through the introduction of continuous improvement and development of the LTE and LTE-Advanced (enhancement / evolution) and new 5G air interface (new Radio Access Technology (RAT)) It is assumed to be. New RAT, for example, LTE / LTE-Advanced continuous development frequency band of interest (eg, 6 GHz or less) frequencies higher than, for example 10 GHz or more super high frequency band and 30 GHz or more mm to support the sideband.
[0003]
 In this specification, the fifth-generation mobile communication system is also referred to 5G System, or Next Generation (NextGen) System (NG System). New RAT for 5G System is, New Radio (NR), called 5G RAT, or NG RAT. New radio access network for 5G System (Radio Access Network (RAN)) is referred to as 5G-RAN or NextGen RAN (NG RAN). New base station within the 5G-RAN is called NR NodeB (NR NB) or gNodeB (gNB). New core network for 5G System is called 5G Core Network (5G-CN) or NextGen Core (NG Core). Wireless terminal connected to 5G System (User Equipment (UE)) is, 5G UE, called NextGen UE (NG UE) or simply UE. RAT for 5G System, UE, radio access network, core network, the network entity (node), and the official name, such as protocol layer will be future decisions in the process of standardization work progresses.
[0004]
 Also, the term "LTE" as used herein, unless otherwise indicated, includes an improvement and development of the LTE and LTE-Advanced for enabling interworking between 5G System. Improvement and development of the LTE and LTE-Advanced for interworking with 5G System is, LTE-Advanced Pro, LTE +, or also called enhanced LTE (eLTE). Furthermore, "Evolved Packet Core (EPC)" as used herein, "Mobility Management Entity (MME)", "Serving Gateway (S-GW)", and "Packet Data Network (PDN) Gateway (P-GW terminology LTE network or logical entities) "or the like, unless otherwise indicated, includes these improvements and development for enabling interworking between 5G System. Improved EPC, MME, S-GW, and P-GW, for example, enhanced EPC (eEPC), enhanced MME (eMME), enhanced S-GW (eS-GW), and enhanced P-GW (eP-GW ) also called.
[0005]
 In LTE and LTE-Advanced, in order of Quality of Service (QoS) and packet routing, the bearer for each and PDN connection specific QoS class RAN (ie, Evolved Universal Terrestrial RAN (E-UTRAN)) and a core network (ie, used by both EPC). That is, in the Bearer-based QoS (or per-bearer QoS) concept is one or more Evolved Packet System (EPS) bearers are set up between the P-GW of the UE and EPC, the plurality that have the same QoS class service data flow (service data flows (SDFs)) is transferred through one EPS bearer satisfying these QoS. SDF is, Policy and Charging Control (PCC) rule-based SDF template (ie, packet filters) is one or more packet flows that match. Further, for packet routing, each packet to be sent through the EPS bearer can discern whether associated with this packet which bearer (ie, General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel) (The identify ) contains information for.
[0006]
 In contrast, in 5G System, might radio bearer is used in the 5G-RAN, the bearers in an interface between the 5G-CN in and 5G-CN and 5G-RAN has been considered not to be used are (see non-Patent Document 1). Specifically, PDU Flows are defined instead of the EPS bearer, one or more SDFs are mapped to one or more PDU Flows. PDU flow between the user plane termination entity in 5G UE and NG Core (ie, the entity corresponding to the P-GW in the EPC) corresponds to the EPS bearer in EPS Bearer-based QoS concepts. In other words, 5G System is, Bearer-based QoS concept of place in Flow-based QoS (or per-flow QoS) to adopt the concept. In the Flow-based QoS concept, QoS is handled in the PDU flow unit (handled). Therefore, PDU flow is also referred to as a QoS flow. Note that association between the 5G UE and the data network (association) is referred to as PDU session (PDU session). PDU session is a term corresponding to LTE and LTE-Advanced PDN connection (PDN connection). Can be more than one PDU Flows (or QoS Flows) is set in one PDU session.
[0007]
 Furthermore, the 5G System supports network slicing also been studied (see Non-Patent Document 1). Network slicing uses Network Function Virtualization (NFV) technology and software-defined networking (SDN) technology makes it possible to create a logical network having a plurality of virtualization on a physical network. Each of virtualized logical networks, called network slice (network slice) or network slice instance (network slice instance), comprising a logical node (nodes) and functions (functions), certain traffic and it is used for signaling. Both 5G-RAN or 5G-CN, or they have a Slice Selection Function (SSF). SSF, based on information provided by at least one of the 5G UE and 5G-CN, selects one or more network slices suitable for the 5G UE.
[0008]
 Figure 1 shows the basic architecture of the 5G system. UE establishes one or more signaling radio bearers (Signalling Radio Bearers (SRBs)) and one or more data radio bearers (Data Radio Bearers (DRBs)) between the GNb. 5G-CN and gNB establishes a control plane interfaces and user plane interface for the UE. Control plane interface between the 5G-CN and gNB (ie, RAN) is referred to as NG2 interface or NG-c interface, transfer of Non-Access Stratum (NAS) information and control between 5G-CN and GNb It is used for the transfer of information. User plane interface between the 5G-CN and GNb (ie, RAN) is called the NG3 interface or NG-u interface, packets of one or more PDU Flows in the UE the PDU session (or QoS Flows) used to transfer (packets-).
[0009]
 Furthermore, the 5G System, in addition to RRC_CONNECTED state and RRC_IDLE state, a new RRC state is introduced (for example, see Non-Patent Document 1-5). New RRC state is referred to as RRC_INACTIVE state or RRC_INACTIVE_CONNECTED state.
[0010]
 RRC_CONNECTED state and RRC_IDLE state of 5G System, respectively a RRC_CONNECTED state and RRC_IDLE state of LTE with similar characteristics. When UE is RRC_CONNECTED state, maintaining the AS context UE and 5G-RAN, the position of the UE is known by the 5G-RAN at the cell level. UE mobility is RRC_CONNECTED state is handled by a handover controlled by 5G-RAN. On the other hand, when the UE is in RRC_IDLE state, UE and 5G-RAN has to release the AS context, not known position of the UE is the 5G-RAN, location registration area-position of the UE is the 5G-CN it is known in the level. Location registration area corresponds to a LTE tracking area (Tracking Area (TA)). UE mobility is RRC_IDLE state is handled by the cell reselection controlled by the UE. In addition, RRC state of the AS layer, the connection management of the NAS layer (NG Connection Management (NG CM)) is associated with the state. A RRC_CONNECTED state the UE is considered to be NG-CM-CONNECTED state in the UE and 5G-CN. On the other hand, UE is RRC_IDLE state is believed to be NG-CM-IDLE state in the UE and 5G-CN.
[0011]
 RRC_INACTIVE state can be said to be an intermediate state between RRC_CONNETED state and RRC_IDLE state. Several features of RRC_INACTIVE state similar to their RRC_CONNETED state, but several other features of RRC_INACTIVE state similar to their RRC_IDLE state.
[0012]
 When UE is RRC_INACTIVE state, UE and 5G-RAN maintains at least a portion of the AS context. AS context held by the UE and 5G-RAN for the UE is RRC_INACTIVE conditions include, for example, radio bearer setup, and AS security context. Furthermore, 5G-RAN maintains while establishing the control plane and the user plane connection between the 5G-CN (ie, NG2 and NG3 interface of FIG. 1) for the RRC_INACTIVE state UE. A RRC_INACTIVE state UE is considered to be the NG-CM-CONNECTED state in the UE and 5G-CN. That, 5G-CN is, UE does not distinguish between whether or RRC_INACTIVE state is RRC_CONNECTED state. These features of RRC_INACTIVE state, similar to the characteristics of RRC_CONNETED state.
[0013]
 However, UE mobility is RRC_INACTIVE state is similar to that of UE is RRC_IDLE state. That, UE mobility is RRC_INACTIVE state is handled by the cell reselection controlled by the UE.
[0014]
 Figure 2 shows the state transition between the three RRC states that are currently proposed. The UE may transition to and from the RRC_CONNECTED state and RRC_INACTIVE state (step 201 and 202). Transition between the RRC_CONNECTED state and RRC_INACTIVE state, reusing the defined RRC connection pending (Suspend) and resume (Resume) procedure in 3GPP Release 13 for LTE is assumed. AS contexts that are stored in the 5G-RAN for the UE is RRC_INACTIVE state can be transferred between RAN nodes (between gNBs). Specifically, when the UE transitions from RRC_INACTIVE state in RRC_CONNECTED state acquisition, RRC message (eg, RRC Connection Resume request) from the UE GNb which has received the AS context of the UE from other GNb ( fetch / retrieve) may be.
[0015]
 Position of the UE is RRC_INACTIVE condition is known by 5G-RAN at the level of the newly defined by RAN notification area (RAN Notification Area (RNA)). RAN notification area, RAN-based Notification Area, also referred to as a RAN paging area, or RAN location update area. RAN notification area (RNA) includes one or more cells is determined by 5G-RAN, it is set to the UE by the 5G-RAN. UE of RRC_INACTIVE state does not need to be notified (report) that even when moving between cells by the cell reselection in the RAN notification area was performed cell reselection to the 5G-RAN. UE of RRC_INACTIVE state, when re-selecting a RAN notification area outside the cell, requesting the updating of the RAN notification area 5G-RAN.
[0016]
 Figure 3 shows an example of a UE mobility is RRC_INACTIVE state. Initially, UE 301 is a RRC_CONNECTED state (321) in cell 351 of GNB311, assigned an individual (dedicated) radio resources from GNB311, has established a dedicated radio bearer (dedicated radio bearers) 322. gNB311 determines the transition to RRC_INACTIVE state of UE 301, it sets the RAN notification area 340 to UE 301, transmits an RRC message (eg, RRC Suspend message) to the UE 301 (323). In response to an instruction from GNB311, UE 301 enters the RRC_CONNECTED state to RRC_INACTIVE state (324).
[0017]
 A RRC_INACTIVE state UE301 performs cell reselection procedure, re-select a cell 352 of gNB312 (325). Since the cells 352 included in the RAN notification area 340 set in the UE 301, UE 301 does not report the cell reselection (that updating of UE location information) to 5G-RAN (eg, cell 352 or GNB312). UE301 is moved further, re-select a cell 353 of gNB313 (326). Since the cell 353 is not included in the RAN notification area 340 set in the UE 301, UE 301 transmits RAN notifies area update request (327) to GNB313. The request (327) is, RRC message (eg, RRC Resume Request message) requesting the transition to RRC_CONNECTED from RRC_INACTIVE may be transmitted using. gNB313 obtains the AS context UE301 from GNB311, to re-establish the Packet Data Convergence Protocol (PDCP) and Radio Link Control (RLC) for radio bearers using the AS context obtained. Then, GNB313 transmits an RRC message (eg, RRC resume message) to transition the UE301 in RRC_CONNECTED state. In response to an instruction from GNB311, UE 301, in the cell 353, it enters from RRC_INACTIVE state in RRC_CONNECTED state (329). UE301 can be transmitted and received data using the dedicated radio bearer (dedicated radio bearers) 330.
CITATION
Non-patent literature
[0018]
非特許文献1 : 3GPP TR 23.799 V14.0.0 (2016-12) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14)”, December 2016
Summary of the Invention
Problems that the Invention is to Solve
[0019]
 Present inventors have conducted a study for the UE mobility of RRC_INACTIVE state, we found several problems. For example, the UE mobility of RRC_INACTIVE state, it may be necessary to consider the network slices. This is because, .UE desired network slice status desired network slice in the re-selected cell (reselected cell is not available because that may occur, for example, is in RRC_CONNECTED state before the UE enters RRC_INACTIVE state the (has been or set) has been selected by the network for the UE is a network slice when.
[0020]
 In the example of FIG. 4, 5G-CN430 is a network function for common network functions (Common Network Functions (NFs)) 431, network functions for network slice A (NFs for slice A) 432, and network slice B ( including the NFs for slice B) 433. Common NFs431 includes a common control plane network function (Common Control plane NF (CCNF)), may further comprise a common user plane network function (Common User plane NF (CUNF)). NFs for slice A432 is slice-specific user plane network function includes (Slice specific User plane NF (SUNF)), further slice-specific control plane network function (Slice specific Control plane NF (SCNF)) may include. Similarly, NFs for slice B433 includes SUNF, may further comprise SCNF.
[0021]
 In the example of FIG. 4, GNB411 and gNB412 are connected to the Common NFs431, NFs for slice A432, and NFs for slice B433. In contrast, GNB413 has been connected to the Common NFs431 and NFs for slice A432, not connected to the NFs for slice B433. That is, the network slice B is not available in the cell 423 of GNB413.
[0022]
 In the example of FIG. 4, UE 401 is RRC_CONNECTED state in a cell 421 of GNB411, network slice B is set for the UE 401. UE401 is and transmit and receive data over the network slice B. Thereafter, UE 401 is set to RAN notification area 440 by GNB411, enters RRC_INACTIVE state. More Thereafter, UE 401 performs a cell reselection (452). However, one problem is the target cell, whether desired network slices in other words reselect the cell to (cell to be reselected) or re-selected cell (reselected cell) can be used for RRC_INACTIVE state UE401 it is that but that how know.
[0023]
 As an example, it may be preferable in the re-selected cell (reselected cell) whether a desired network slices are available can be determined by the UE in RRC_INACTIVE state. Knowing that the desired network slice can be used in the re-selected cell (reselected cell) If, UE of RRC_INACTIVE state, without performing a special operation, the RRC_INACTIVE state in the re-selected cell (reselected cell) It might be able to stay. In contrast, if the re-selected cell (reselected cell) whether a desired network slices can be used is known to be unclear, UE promptly enters the RRC_CONNECTED state in the re-selected cell, You might be required to use the network slice network. Alternatively, the UE of RRC_INACTIVE state, if the desired network slice in reselection the cell to (cell to be reselected) or re-selected cell (reselected cell) is not available is known, another other cells from this You might can be further re-selection.
[0024]
 Therefore, one of the objective to be achieved is the embodiment disclosed herein, the network in the target cell, i.e. the reselected is a cell (cell to be reselected) or re-selected cell (reselected cell) slices apparatus for use possibility (availability) facilitates to know the UE of RRC_INACTIVE state is to provide a method, and a program. Incidentally, this objective should more embodiments disclosed herein is noted that only one of several objects of it and to achieve. Other objects or problems and novel features will become apparent from the description, or the accompanying drawings of this specification.
Means for Solving the Problems
[0025]
 In a first aspect, the base station includes a memory, and at least one processor coupled to said memory. Wherein the at least one processor is a first RRC state, it is configured to control the second RRC state, and the state transition of the first wireless terminal among the third RRC state. Wherein the first RRC state, the first wireless terminal and the RAN is in state to maintain the access layer (Access stratum (AS)) context, and the at the first level of the position of the wireless terminal cell a condition known by the RAN. The second RRC state is a state where the first wireless terminal and the RAN maintains at least a portion of the AS context, RAN notification and the position of the first wireless terminal set by the RAN it is a state in which at the level of the area is known by the RAN. The third RRC state is a state where the first wireless terminal and the RAN has released the AS context, and position of the first wireless terminal is in a state not known by the RAN . Wherein the at least one processor is further used in each cell in which the first network slice set in the first wireless terminal for data communication with at least the first RRC state is included in the RAN notification area possible is configured to notify explicitly or implicitly the first wireless terminal whether or not.
[0026]
 In a second aspect, the base station includes a memory, and at least one processor coupled to said memory. Wherein the at least one processor is a first RRC state, it is configured to control the state transitions of the wireless terminals between the second RRC state, and a third RRC state. Wherein the at least one processor is further configured to transmit the first in the cell available or not available 1 or system information indicating the more networks slices of the base station in the first cell there.
[0027]
 In a third aspect, the radio terminal includes a transceiver, and at least one processor. Wherein the at least one processor is configured to control the transceiver in one or more cells associated with a radio access network (RAN). Wherein the at least one processor is a first RRC state, it is configured to control the state transitions of the wireless terminals between the second RRC state, and a third RRC state. Wherein the at least one processor is re further first network slice set in the wireless terminal for data communication with at least the first RRC state, the cell reselection in the second RRC state it is configured to check whether or not it is possible to use in the cells selected.
[0028]
 In a fourth aspect, a method in a base station which is disposed in a radio access network (RAN) is, (a) a first RRC state, the second RRC state, and the first between the third RRC state controlling the state transitions of the wireless terminals, and (b) at least the first of the first network slice set in the first wireless terminal for data communication in a RRC state is set by the RAN notifying the explicitly or implicitly the first wireless terminal whether or not it is possible to use in each cell included in the RAN notification area, including.
[0029]
 In a fifth aspect, a method in a base station which is disposed in a radio access network (RAN) is, (a) a first RRC state, the second RRC state, and the first between the third RRC state controlling the state transitions of the wireless terminals, and (b) transmits the system information indicating the first in the cell available or unavailable one or more network slices of the base station in the first cell to it, including the.
[0030]
 In a sixth aspect, a method in a wireless terminal, (a) a first RRC state, to control the state transitions of the wireless terminals between the second RRC state, and the third RRC state, and ( b) at least the first of the first network slice the set in the wireless terminal for data communication in a RRC state is available in a cell is re-selected by cell reselection by the second RRC state possible to confirm whether or not it is, including the.
[0031]
 In a seventh aspect, the program includes the when loaded into a computer, instructions for performing a method according to any one of the fourth to sixth aspects described above to a computer (software code).
Effect of the invention
[0032]
 According to the embodiments described above, the target cell, i.e. a cell (cell to be reselected) to be re-selected or re-selected cell (reselected cell) availability of network slices in (availability) to know the UE of RRC_INACTIVE state the apparatus that facilitates and can provide a method, and a program.
BRIEF DESCRIPTION OF THE DRAWINGS
[0033]
FIG. 1 is a diagram illustrating the basic architecture of the 5G System according to background art.
Is a diagram showing the state transition of three RRC states of 5G System according to [2] Background Art.
3 is a diagram showing an example of a UE mobility RRC_INACTIVE state according to the background art.
It is a diagram for explaining one problem with UE mobility obtained RRC_INACTIVE state by [4] inventor.
5 is a diagram showing an example of configuration of a wireless communication network in accordance with some embodiments.
6 is a sequence diagram showing an example of information exchange between gNBs according to the first embodiment.
7 is a flowchart illustrating an example of the operation of gNB according to the first embodiment.
8 is a flowchart showing an example of the operation of the UE according to the first embodiment.
9 is a flowchart showing an example of an operation of the UE according to the first embodiment.
FIG. 10 is a flowchart illustrating an example of the operation of gNB according to the second embodiment.
11 is a flowchart showing an example of an operation of the UE according to the second embodiment.
12 is a sequence diagram showing an example of gNB and UE operation according to the third embodiment.
13 is a sequence diagram showing an example of gNB and UE operation according to the third embodiment.
14 is a flowchart showing an example of the operation of the UE according to the third embodiment.
15 is a block diagram showing a configuration example of a gNB according to some embodiments.
16 is a block diagram showing a configuration example of a UE according to some embodiments.
DESCRIPTION OF THE INVENTION
[0034]
 Hereinafter, specific embodiments will be described in detail with reference to the drawings. In the drawings, the same or corresponding components are denoted by the same reference numerals, for clarity of description, repeated explanation is omitted as appropriate.
[0035]
 A plurality of embodiments described below can can either be carried out independently, also be implemented in appropriate combination. These several embodiments have different novel features together. Accordingly, the plurality of embodiments, contribute to solving the different purpose or task to each other, which contributes to achieve different effects from each other.
[0036]
 A plurality of embodiments shown below is described the 5G System that uses and RRC_INACTIVE state supports network slicing as the main subject. However, these embodiments may be applied to other wireless communication systems and support network slicing using RRC_INACTIVE state or similar RRC state therewith.
[0037]

 FIG. 5 shows a configuration example of a wireless communication network according to some embodiments including the present embodiment. In the example of FIG. 5, a wireless communications network includes a 5G UE2,5G-RAN3, and 5G-CN4.
[0038]
 5G-CN4 includes control plane network features that are not shown (Control Plane Network Functions (CP NFs)) and a user plane network functions (User Plane Network Functions (UP NFs)), providing a plurality of network slices . Multiple networks slices, for example, are distinguished by the service or use case is provided to the UE on each network slices. Use case, for example, broadband communications (enhanced Mobile Broad Band: eMBB), reliable, low-latency communication including:: (mMTC massive Machine Type Communication) (Ultra Reliable and Low Latency Communication URLLC), and many connection M2M communication.
[0039]
 5G-RAN3 includes a plurality of gNB including gNB1A and GNB1B. Each gNB1 (eg, gNB1A, gNB1B) is operated at least one cell 11 (eg, cell 11A, the cell 11B). Each gNB1 is connected to the 5G-CN4, support one or more network slices. In other words, one or more network slices are or can be used to support the cells 11 of each GNB1. In some implementations, 5G-RAN3, in order to provide end-to-end network slicing the UE2, the selected 5G-CN4 of the network slice (referred to as a Core Network (CN) slices) for UE2 allocating the associated RAN slices and wirelessly (radio) slice UE2. Each RAN slice, provides an infrastructure storage and processing resources in the CN-RAN3 including GNB1. Each radio slice, time resources, provides frequency resources, code resources, signal sequence resource or radio resources including space resources, or any combination thereof.
[0040]
 UE2, for the uplink and downlink communications, using one or more cells 11 is provided by one or more GNB1. UE2 is, RRC_CONNECTED state supports multiple RRC states including RRC_INACTIVE state, and RRC_IDLE state. 5G-RAN3 (gNB1) and the UE2, RRC_CONNECTED state, controls the UE2 state transitions between a plurality of RRC states including RRC_INACTIVE state, and the RRC_IDLE state.
[0041]
 For example, GNB1A, when transitioning to RRC_INACTIVE state UE2 from RRC_CONNECTED state, RRC message transmitted (eg, RRC Connection Release, RRC Connection Suspend, or RRC Connection Deactivate) the RAN notification area information in the UE2, to the UE2 setting the RAN notification area. RAN notification area includes one or more cells are provided by one or more GNB1, UE2 enters the RRC_INACTIVE state in response to reception of the RRC message from GNB1A. UE2 of RRC_INACTIVE state moves between cells by cell reselection UE2 led not required to report the cell reselection in the RAN notification area (that updating of UE location information) to 5G-RAN3. Meanwhile, UE2 is configured RAN notification area outside of the cell (eg, cell 11B) in response to the reselected, requesting an update of RAN notification area gNB1B the reselected cell 11B (or, to notify the gNB1B that has left the set RAN notification area). gNB1B determines a new RAN notification area for UE2, sets the determined RAN notifies area UE2. That is, as already described, the position of UE2 in RRC_INACTIVE condition is known to 5G-RAN3 in RAN notification area level.
[0042]
 As already explained, RAN notification area (RNA) includes one or more cells is determined by 5G-RAN3, it is set by the 5G-RAN3 to UE2. RAN notification area, RAN-based Notification Area, also referred to as a RAN paging area, or RAN location update area.
[0043]
 RAN notification area information, for example whether the information may at least comprise a showing contained what cell to the RAN notification area. Further, with respect to RAN notification area identifier (eg, area number) may be applied. Further, the identifier of the RAN notification area (eg, RNA ID) and, the relationship between the cell (s) to be embraced therein, may be to uniquely determined within a given area. In this case, RAN notification area information may include information of a cell that is included with the identifier RAN notification area (eg, cell identifier).
[0044]
 gNB1A may inform the RAN notification area information in its own cell 11A. In this case, RAN notification area information includes a plurality of RAN notification area, condition (eg, category, type) is given to each may be selected RAN notification area UE2 corresponds to itself. The conditions are, for example, UE2 (or desired) using slices category or slice type of network slices (eg, Slice / Service Type: SST), the category or type of terminal, UE2 reception quality or coverage level based thereon , transfer characteristics of UE2 (eg, UE speed, whether stationary terminal), or any combination thereof.
[0045]
 RAN notification area set to UE2 may be the same as the UE2 location registration area (ie, the area corresponding to the LTE tracking area (TA)). If an individual RAN notification area to each network slice (ie Slice specific RNA) is set, at least one location registration area (eg, TA) and may be the same among the plurality of RAN notification area. If RNA is the same as the TA, the information element indicating a cell list included in the RNA in the RAN notification area information sent from gNB1 to UE2 (eg, RanAreaCellList Information Element (IE)) are may be omitted (i.e. , Optional IE). Alternatively, RAN notification area information, instead of the information element indicating cell list information element (eg, TrackingAreaCode IE) indicating the TA identifier may comprise (i.e., Choice). In other words, GNB1 to indicate the RAN notification area, may select one of RanAreaCellList IE and TrackingAreaCode IE.
[0046]
 For transmission including a plurality of RAN notification area RAN notification area information, GNB1A includes other gNB (eg, gNB1B) from the RAN notification area information (eg, the RAN notifies area identifier, constituting the RAN notification area a combination) of the cell identifier may be received via the gNB between interfaces (Xn). The other gNB the cell gNB1A (eg, cell 11A) may be a gNB which manages a cell which belongs to a different other RAN notification area and belongs RAN notification area. Information about the RAN notification area for receiving similarly from other gNB may be information for different other RAN notification area the RAN notifies area cell gNB1A (eg, cell 11A) belongs.
[0047]
 If UE2 is using multiple network slices (or hopes), UE2 may select a RAN notification area based on the highest priority network slices are actually used based on the network slice may select a RAN notification area. Alternatively, UE2 may select a RAN notification area on the basis of the network slices included in the upper network slice category or type of the list contained in the RAN notification area information.
[0048]
 Individual information network slice RAN notification area (eg, an identifier, category or type) is not explicitly (default RAN notification area) may be included in the RAN notification area information described above. Other this case, for example, the default RAN notification area, except may be the RAN notification area is valid for UE2 irrespective of the network slice, explicitly notified network slices RAN notification area information it may be the RAN notification area is valid for the network slices. Furthermore, if the RAN notification area information includes a plurality of RAN notification area, UE2 unless cell after cell reselection included in at least one of a plurality of RAN notification area, it transmits an update request for location information to gNB1 it may not be.
[0049]
 Instead of indication by the aforementioned RRC message, GNB1 notifies the value of the predetermined timer that triggers a transition to RRC_INACTIVE state UE2, the transition to RRC_INACTIVE state based on the value and the corresponding timer of the timer UE2 it may be executed. For example, UE2 in RRC_CONNECTED state, the timer restart (i.e., the timer is reset again start) each for transmitting or receiving the user data may transition to and, RRC_INACTIVE state When the timer expires.
[0050]
 The following describes UE2 mobility of RRC_INACTIVE state according to the present embodiment. gNB1 according to the present embodiment, used in each cell is set to UE2 for data communication at least RRC_CONNECTED state (or selected) to one or more networks slices are included in the RAN notification area for UE2 It is constructed explicitly to notify the UE2 to possible whether. More specifically, in this embodiment, GNB1 shows explicitly whether or not it is possible to use in each cell or cell group one or more networks slices set to UE2 are included in the RAN notification area is configured to transmit information (referred to as slice availability (availability) information) UE2. gNB1, instead of slicing availability (availability) information, the slice (referred to as slice support information) explicitly indicates information whether is supported may be sent to UE2. Slice availability information or the slice support information, network slices can be used in one or more cells included in the RAN notification area or RAN notification area (supported) one or more types (eg, category, type) the may indicate. Hereinafter will be described a slice availability information as an example, it is of course possible to use a slice support information instead.
[0051]
 In some implementations, GNB1, when setting the RAN notification area UE2, may transmit a slice availability information to UE2. Slice availability information may be one of information elements associated with RAN notification area (eg, a list of cells). Additionally or alternatively, GNB1 is the procedure for transitioning the UE2 from RRC_CONNECTED state to RRC_INACTIVE state (eg, RRC messages), CPU 170 may transmit a slice availability information to UE2.
[0052]
 Figure 6 is a flowchart showing an example of the operation of gNB1 the (process 600). In step 601, GNB1 the network slice used by UE2 in RRC_CONNECTED state to generate a slice availability information indicating whether or not it is possible to use in each cell included in the RAN notification area. In step 602, GNB1 sends slices availability information to UE2. gNB1 is, RAN notification area may send a slice availability information in conjunction with (eg, a list of cells). In step 603, GNB1 transitions the UE2 from RRC_CONNECTED state to RRC_INACTIVE state. Incidentally, as described above, GNB1, together with the transmission of slices availability information may transmit an instruction to transition the UE2 to RRC_INACTIVE state.
[0053]
 Each gNB1 needs to know slices availability of each cell that is provided by other gNBs1 or other gNBs1 (or slice support status). In some implementations, the slice availability of the network operator O & M (Operation and Management) other gNBs1 cells via server (cells) may be set to each GNB1. Additionally or alternatively, each gNB1 communicates with other gNB1 on gNB between interfaces (Xn) (eg, Xn Setup Request / Response messages), thereby slices availability of a cell of another gNB1 dynamically it may be acquired. Each GNB1, if slice usability is changed (or updated), optionally informs the other gNB1 (eg, gNB Configuration Update message). Additionally or alternatively, each gNB1 communicates with other gNB1 via an interface (NG2, NG-c) between gNB1 and 5G-CN4, dynamic slices availability of a cell of another gNB1 it may be acquired.
[0054]
 Figure 7 is a sequence diagram showing an example of a communication between two gNB1 the (process 700).
In step 701, GNB1A sends information indicating the network available slice in each cell that is provided by gNB1A (eg, Network Slice Availability Information ) to GNB1B. gNB1A may transmit the information in response to a request from GNB1B. Additionally or alternatively, GNB1A in response to the slice availability of updates in any cell that is provided by GNB1A, may send the update to GNB1B. Additionally or alternatively, GNB1A is a slice availability of each cell may be transmitted periodically to GNB1B. In step 702, GNB1B sends information indicating the network available slice in each cell that is provided by gNB1B (eg, Network Slice Availability Information ) to GNB1A. Additionally or alternatively, GNB1A via a core network (5G-CN4) and interfaces (NG2, NG-c), information indicating the network available slice in each cell that is provided by gNB1A (eg, Network Slice Availability Information) may be sent to gNB1B.
[0055]
 Incidentally, as described above, GNB1A is via RAN notification area information gNB between interfaces (Xn) between gNB1B a (and eg, the identifier of the RAN notification area, the combination of the identifier of the cells constituting the RAN notification area) it may be transmitted and received Te. In this case, RAN notification area information, RAN notification area cell 11 of the sender gNB1 belongs, or destination may indicate RAN notification area to cell 11 of gNB1 belongs. That is, when belonging to gNB1A the cell 11A and a cell 11B is different RAN notification area, each of which manage GNB1B (or should be supplied), each gNB1, by sharing the RAN notification area information between GNb, to UE2 a plurality of RAN notification area may be recognized to be included in the RAN notification area information transmitted.
[0056]
 RAN notification area information communicated between gNB may be included in the information (eg, Network Slice Availability Information) indicating a network available slice in each cell is provided by gNB1A shown in FIG. On the contrary, RAN notification area information communicated between gNB may include information (eg, Network Slice Availability Information) indicating an available network slices in each cell that is provided by gNB1A shown in FIG.
[0057]
 In some implementations, the information indicating the network available slice in each cell that is provided by GNB1A and gNB1B may be sent from the core network (5G-CN4) to gNB1B and GNB1A. In this case, it is necessary to 5G-CN is to know the available (or supported) network sliced ​​in advance in each GNB1. For example, 5G-CN4 is available (or supported) network slice each GNB1 may be specified for each GNB1. Alternatively, 5G-CN4 is the available (or supported) network slice report in the GNB1 may receive from each GNB1.
[0058]
 UE2 according to the present embodiment was set to UE2 for data communication at least RRC_CONNECTED state (or is permitted (authorized) or have been approved (accepted)) 1 or more networks slices, RRC_INACTIVE it is configured to confirm the re-selected by (or reselected) whether it can use the cell (or whether or not supported) by the cell reselection condition. More specifically, in this embodiment, UE2 is configured to receive a slice availability information described above from GNB1. Slice availability information explicitly indicating whether one or more networks slices set to UE2 are available in each cell included in the RAN notification area for UE2.
[0059]
 Figure 8 is a flowchart showing an example of operation of UE2 (process 800). In step 801, UE2 is RRC_CONNECTED state receives a slice availability information described above from the serving GNB1. In step 802, UE2, in response to an instruction from the serving GNB1, transitions from RRC_CONNECTED state to RRC_INACTIVE state. In step 803, UE2 performs a cell reselection RRC_INACTIVE state. UE2 is confirmed based on the reselected by (or reselected) cell slice availability information whether the desired network slices are available. Here, the desired network slice, UE2 have been past network when was RRC_CONNECTED state (ie, 5G-CN4 or 5G-RAN3 or both) was set to UE2 by (or permitted (authorized) or it has been approved (accepted)) may be one or more networks slices.
[0060]
 Hereinafter, an example of the operation of the UE2 after confirming the network slices availability. Figure 9 is a flowchart showing an example of operation of UE2 (process 900). In step 901, UE2 checks the network slices availability of reselected by (or reselected) cell by cell reselection RRC_INACTIVE state. If desired network slice in the re-selected cell can be used, UE2 is (continue camping on to that cell) to remain in the cell.
[0061]
 If desired network slice in the re-selected cell if not available, UE2 is the gNB1 the reselected cell, notifies the desired network slice (step 902). The notification is moved to the desired requirements of the network slice, for example, to set the desired network slice UE2 (or provide) required or desired network slice is available (which is or supported) cells (eg , handover, may be a re-direction) request. Note, UE2, if desired network slice in the re-selected cell can not be confirmed can be used, the gNB1 the reselected cell may notify the desired network slices. In other words, UE2, when the re-selected cell whether desired network slices can be used is found to be not known, the gNB1 the reselected cell, notifies the desired network slices it may be.
[0062]
 In some implementations, UE2, after shifting to the RRC_CONNECTED state, may send a notification of the desired network slices. Alternatively, UE2 may transmit a notification of desired network slices in RRC_INACTIVE state. In other words, UE2, without completely changes the RRC_CONNECTED state, may send the notification. In other words Furthermore, UE2 may transmit the notification before the RRC_CONNECTED state. In one example, UE2 is in the procedure for transition to RRC_CONNECTED state, may send the notification. Specifically, UE2 is, RRC messages for transition to RRC_CONNECTED state (eg, RRC Connection Resume request, or RRC Connection the Activate) may transmit the notification using. Alternatively, UE2, leaving transmission capable signals RRC_INACTIVE state (eg, PRACH preamble, RACH data, UL reference signal, MAC Control Element (CE)), or RRC message (eg, UL Information Transfer, UL Direct Information, or UE Assistance Information) using, may send a notification of the desired network slices. In this case, the signal or message may be transmitted by using the radio resource notification from pre gNB1 to the UE2 (set) by individual (dedicated), using the radio resource that is shared among a plurality of UE2 it may be sent Te. In the latter case, for example the UE2, a separate grant is not required (grant-free) transmission mode for uplink transmission may transmit a notification of desired network slices. RRC message, for example, the first step of the uplink transmission in the new random access procedure for the NR (eg, RACH data) may be sent in. New random access procedure for the NR may be a procedure simplified to all two steps procedure of contention-based random access consisting of all four steps in the conventional LTE (Contention-based Random Access). UE2 is, whether performing random access or four steps performing random access two steps may be set in advance from GNB1. Or, Permitted (which is or supported) in a cell reselection after the cell random access may be performed towards. Whether or not random access 2 steps and four steps is permitted (or supported), the setting information of the wireless resources utilized each being determined by whether or not they are transmitted in the system information it may be. It may be sent in RACH data). New random access procedure for the NR may be a procedure simplified to all two steps procedure of contention-based random access consisting of all four steps in the conventional LTE (Contention-based Random Access). UE2 is, whether performing random access or four steps performing random access two steps may be set in advance from GNB1. Or, Permitted (which is or supported) in a cell reselection after the cell random access may be performed towards. Whether or not random access 2 steps and four steps is permitted (or supported), the setting information of the wireless resources utilized each being determined by whether or not they are transmitted in the system information it may be. It may be sent in RACH data). New random access procedure for the NR may be a procedure simplified to all two steps procedure of contention-based random access consisting of all four steps in the conventional LTE (Contention-based Random Access). UE2 is, whether performing random access or four steps performing random access two steps may be set in advance from GNB1. Or, Permitted (which is or supported) in a cell reselection after the cell random access may be performed towards. Whether or not random access 2 steps and four steps is permitted (or supported), the setting information of the wireless resources utilized each being determined by whether or not they are transmitted in the system information it may be.
[0063]
 Notification of the desired network slice, for example, UE2 identification information of a desired network slices (eg, unique identifier or a temporary identifier of a network slice, slice category network slices, or slice type (eg, Slice / Service Type: SST) ) or it may be explicitly sending a. For example, identification information of a desired network slice is included in the RRC message or MAC Control Element, network slice selection assist information (Network Slice Selection Assistance Information: NSSAI) may be transmitted with. Additionally or alternatively, the identification information of the desired network slice, it pre-association was predetermined signal sequence (eg, RACH preamble, UL reference signal) or a predetermined time, frequency, code, or space of the radio it may be transmitted implicitly using resources. gNB1 is to the association information between the identification information and signal sequence or radio resources desired network slices may be notified in the own cell may notify individually UE2. When informed by GNB1, UE2 if you reselect the cell may receive information of associations which are the reported in reselection target cell (monitor). Further, a plurality of network nodes (eg, Network Slice Instance: NSI) is when supporting slice type of the same network slice (offering), an identifier for distinguishing the plurality of network nodes (eg, Slice Defferentiator: the SD) gNB1 or 5G-CN may be set to UE2. In this case, UE2 is also the identifier may be transmitted explicitly or implicitly in the notification of the desired network slices.
[0064]
 gNB1, after receiving a signal indicating an RRC message or the notification includes the notification, may be put UE2 in RRC_CONNECTED state (i.e. may be to transition), it may be fastened to UE2 in RRC_INACTIVE state. In some implementations, GNB1, when the network slice requested by the UE2 is not available in the GNB1 or the cell may be transferred to a suitable cell UE2. Specifically, GNB1 may transfer the UE2 to network slices available (being or support) other cells request from UE2. Other cell transferring UE2, be other cells which are provided by different the gNB1 itself a cell received by the gNB1 notification of desired network sliced ​​from UE2 (ie, re-selected cells by UE2) good. Alternatively, other cells to transfer the UE2 may be a cell of another GNB1. gNB1 is to transfer the UE2 to the appropriate cell, the handover procedure or redirection procedure (eg, RRC connection release with redirection) may be used.
[0065]
 Note, UE2 receives the RAN notification area information including a plurality of RAN notification area, and transmits the uplink data in the cell reselection after the cell (i.e., there is uplink data to be transmitted), the following it may operate as. UE2 is the uplink data belongs (or association was) network slice or not (whether it is or supported) or is available in the cell, the RAN notifies area including the corresponding cell based on whether or not corresponding to the network slice, or RAN notification area corresponding to the network slice may be determined based on whether by this cell. For example, UE2 is uplink data to be transmitted (is or associate) belonging When RAN notification area corresponding to the network slice containing cell after cell reselection, so as to transmit the uplink data it may be. Otherwise (if that is not included), UE2 may notify the gNB1 the desired network slices.
[0066]
 As understood from the above description, GNB1 according to the present embodiment is configured to transmit a slice availability information to UE2. Slice availability information, available in each cell is set to UE2 for data communication at least RRC_CONNECTED state (or selected) to one or more networks slices are included in the RAN notification area for UE2 indicating whether or not it is. Thus, slicing availability information, to check whether the desired network slices are available in the cell (or re-selected cell) to be re-selected by the cell reselection RRC_INACTIVE state UE2 to enable the. The present embodiments are, therefore, re-selected the cell (cell to be reselected) or re-selected cell availability of network slices in (reselected cell) a (availability) UE2 of RRC_INACTIVE state to facilitate knowing (facilitate) can be.
[0067]

 The present embodiment provides a modification of the UE2 mobility of RRC_INACTIVE state. Configuration example of a wireless communication network of this embodiment is the same as FIG.
[0068]
 gNB1 according to the present embodiment was set to UE2 for data communication at least RRC_CONNECTED state (or selected, authorized, or approved) one or RAN for multiple networks slices UE2 it is configured to notify the implicitly UE2 whether it is possible to use in each cell included in the notification area. More specifically, in this embodiment, GNB1 is configured network slices for UE2 the RRC_CONNECTED state is available (or supported) one or more cells only in RRC_INACTIVE state UE2 It is configured to include the RAN notification area for, and is configured to set the RAN notification area UE2. Therefore, the RAN notification area is implicitly indicating that it can be used in each cell network slice set to UE2 are included in the RAN notification area.
[0069]
 Figure 10 is a flowchart showing an example of the operation of gNB1 the (processing 1000). In step 1001, the network slice set to UE2 of RRC_CONNECTED state is available only include one or more cells in RAN notification area. In step 1002, GNB1 notifies the determined RAN notifies area UE2. In step 1003, GNB1 transitions the UE2 from RRC_CONNECTED state to RRC_INACTIVE state.
[0070]
 Figure 11 is a flowchart showing an example of operation of UE2 (processing 1100). In step 1101, UE2 is RRC_CONNECTED state, receives the setting of the RAN notification area from the serving GNB1. The RAN notification area includes only one or more of the cell network slice set to UE2 are available. In step 1102, UE2, in response to an instruction from the serving GNB1, transitions from RRC_CONNECTED state to RRC_INACTIVE state. In step 1103, UE2 performs a cell reselection RRC_INACTIVE state. UE2 is whether desired network slice cell to be reselected is available, the cell is the reselection confirmed based on whether or not included in the RAN notification area. Here, the desired network slice, UE2 is time was RRC_CONNECTED state to the network (ie, 5G-CN4 or 5G-RAN3 or both) by was set to UE2 (or allowed to have or approved past it was) may be one or more networks slices.
[0071]
 Operation of UE2 and gNB1 after the network slice availability UE2 is confirmed may be the same as the examples described in the first embodiment.
[0072]
 gNB1 may set a plurality of RAN notification area UE2, may transmit the RAN notification area information including a plurality of RAN notification area UE2. At least one of the plurality of RAN notification area contained in RAN notification area information has been set for UE2 (or selected, is permitted, or approved) network slices are available (or support may be determined to contain only are) one or more cells are. For example, if the first and second RAN notification area is set to a UE2, first RAN notification area is configured for UE2 (is or selected, is permitted, or approved) network slices There comprises only be used (or supported) one or more cells, the second RAN notifying area moved without notifying the UE2 is GNB1 (i.e., cell reselection) capable 1 or contain more cells may be. In this case, the second RAN notifying area defaults to UE2, first RAN notification area may be optionally set UE2. That, GNB1 is the second RAN notification area may always sent to the UE2 as RAN notification area applied to UE2 irrespective of use of the network slices. Meanwhile, GNB1 is, UE2 is only to configure network slices or UE2 use the network slice, it may transmit the first RAN notification area UE2.
[0073]
 Additionally or alternatively, it is set to UE2 (or selected, is permitted, or approved) RAN notification area may be set for each slice category or slice type of network slices. In one example, the correspondence relationship between the plurality of RAN notification area and a plurality of networks slices may be defined by a set order of the plurality of setting order and a plurality of networks slices RAN notification area. That is, the first RAN notification area setting order, the setting order may be associated with the first network slice. Alternatively, the correspondence between the plurality of RAN notification area and a plurality of network slices may be defined by ascending multiple setting order and a plurality of networks slice identifier RAN notification area. That is, the first RAN notification area setting order may be associated with a network slice with the lowest identifier. Incidentally, if different from the number of RAN notification area number is set to UE2 network slice set to UE2 excluding the default settings described above (default · RAN notification area), UE2 applies the handling of following it may be. If the number of configured network slice is greater than the number of RAN notification area, UE2, the network slice remainder which can not be associated with RAN notification area serving cell (i.e., cell UE2 receives the RAN notification area) other than recognized in not available (or unsupported). Conversely, if the number of configured network slice is less than the number of RAN notification area, UE2 ignores RAN notification area of ​​less that can not be associated with a network slice.
[0074]
 As understood from the above description, GNB1 according to the present embodiment is set to UE2 for data communication at least RRC_CONNECTED state (or selected) one or more networks slices available determine the RAN notification area containing only one or more cells, and notifies the determined RAN notifies area UE2. Thus, RAN notification area, allows to check whether the desired network slices are available in the reselected the cell (or re-selected cells) by the cell reselection RRC_INACTIVE state UE2 to. The present embodiments are, therefore, re-selected the cell (cell to be reselected) or re-selected cell availability of network slices in (reselected cell) a (availability) UE2 of RRC_INACTIVE state to facilitate knowing be able to.
[0075]

 The present embodiment provides a modification of the UE2 mobility of RRC_INACTIVE state. Configuration example of a wireless communication network of this embodiment is the same as FIG.
[0076]
 gNB1, in each cell of the own available (which is or supported) in the cell or not available (or not supported) 1 or system information indicating the more networks slices according to this embodiment It is configured to transmit the (System Information (SI)). The system information may be included in the broadcast system information block broadcasted in each cell. Alternatively, the system information may be included in the on-demand system information block transmitted to the UE2 according to with or triggered internal network in response to a request message from UE2.
[0077]
 Figure 12 is a sequence diagram showing an example (process 1200) of operation of gNB1 and UE2 according to the present embodiment. In step 1201, UE2 is RRC_INACTIVE state, the cell reselection procedure. In step 1202, UE2 receives system information from gNB1 In reselected the cell (or re-selected cell). The system information includes the network slice using possibility (availability) information. Network slices availability information indicates one or more network slices or unusable available in the cell. As described above, the network slices availability information may be included in the on-demand system information block.
[0078]
 If the network slices availability information is a broadcast system information block, UE2 responds to cell reselection, receives the broadcast system information block in the re-selected cell, the re-selected cell it may confirm the network slice availability.
[0079]
 If the network slices availability information is on-demand system information block, for example gNB1 the system information including a network slices availability information, primary information that is meant to be sent on-demand system information block (eg , indication of system information on the network slicing, to notify the availability of network slicing SI). If the primary information is transmitted in the system information required to access the UE2 cell (eg, LTE of Essential system information, or, Minimum system information of NR), UE2 is the before performing cell reselection to receive primary information. Then UE2, when performing cell reselection (in response thereto), and requests the transmission of the on-demand system information block GNB1. gNB1 transmits the network slices availability information in response to a request from UE2.
[0080]
 UE2 is a transmission request for on-demand system information block may be transmitted immediately in response to the cell reselection. Alternatively, UE2 is a transmission request for on-demand system information blocks may be sent when uplink data to be transmitted to the transition to the RRC_CONNECTED state for or for other purposes that have occurred. Additionally or alternatively, UE2 is a transmission request for on-demand system information block may be transmitted remains RRC_INACTIVE state. In the case the primary information to be transmitted in the system information other (other than the system information required for ie, UE2 accesses to the cell), UE2 is after performing the cell reselection (in response thereto) the primary information it may receive. In some implementations, UE2 is a transmission request for on-demand system information block may be transmitted on the random access channel (Random Access Channel (RACH)), the individual (dedicated) signaling (eg, RRC signaling, or Medium Access Control (MAC) Control Element (CE)) may be transmitted using.
[0081]
 Figure 13 is a sequence diagram showing an example of the operation of gNB1 and UE2 (the processing 1300) when the network slices availability information is an on-demand system information block. In step 1301, GNB1 sends a notification of the available on-demand system information. Notification of the available on-demand system information corresponds to the primary information described above. The notification, UE2 are included in the system information (eg, Essential SI, SIB1) to be broadcast in the cell 11 of the are and GNB1 required to access the cell 11 of GNB1. Alternatively, the notification of the available on-demand system information may be included in other SI are not Essential SI.
[0082]
 In step 1302, UE2 is RRC_INACTIVE state, the cell reselection procedure. UE2 is. Check the "notification of the available on-demand system information" included in the system information received in step 1301, it sends a transmission request for on-demand SI including network slice information GNB1 (step 1304). The notification of the available on-demand system information, if contained in the other SI are not Essential SI, UE2 is cell reselection after the the other SI (eg, SIBX) may receive the ( step 1303). If the notification of available on-demand system information is included in Essential SI (eg, SIB1), step 1303 is omitted. In step 1305, it receives the system information including the network slice using possibility (availability) information from GNB1.
[0083]
 Figure 14 is a flowchart showing an example of operation of UE2 (processing 1400). In step 1401, UE2 responds to cell reselection in RRC_INACTIVE state, attempts at re-selected cell to receive the system information including the network slices availability information. In step 1402, UE2 is desired network slice whether or not it is possible to use re-selected cell, to check based on the received system information. Here, the desired network slice, UE2 is time was RRC_CONNECTED state to the network (ie, 5G-CN4 or 5G-RAN3 or both) by was set to UE2 (or allowed to have or approved past it was) may be one or more networks slices.
[0084]
 Operation of UE2 and gNB1 after the network slice availability UE2 is confirmed may be the same as the examples described in the first embodiment.
[0085]
 As understood from the above description, GNB1 according to the present embodiment, the system information indicating the network slices availability of each cell is transmitted in each cell. Thus, system information, possible to confirm whether the desired network slices are available in the reselected the cell (or re-selected cells) by the cell reselection RRC_INACTIVE state UE2 to. The present embodiments are, therefore, re-selected the cell (cell to be reselected) or re-selected cell availability of network slices in (reselected cell) a (availability) UE2 of RRC_INACTIVE state to facilitate knowing be able to.
[0086]

 The present embodiment provides an operation when the UE2 addressed downlink user data RRC_INACTIVE state arrives at the network. Configuration example of a wireless communication network of this embodiment is the same as FIG.
[0087]
 If UE2 addressed downlink user data RRC_INACTIVE state arrives at 5G-CN4, 5G-CN4 is gNB1 (eg, gNB1A) UE2 has been connected at the time of transition to RRC_INACTIVE state the user data to Forward. gNB1A transmits existing paging (Paging message) and incoming notification downlink user data similar (also referred to as RAN-based paging) in its cells 11A. Furthermore, gNB1 RAN notifies area set to UE2 (RNA) is another (eg, gNB1B) if it contains cells, GNb between interfaces to GNB1B that downlink user data to the UE2 has arrived (Xn) inform through the (Xn also referred to as paging). The Xn paging may include information RAN notification area UE2 belongs (RNA). And gNB1B likewise may send RAN-based paging its cells 11B included in the RNA.
[0088]
 gNB1A is, in Xn paging (ie, notification that the downlink user data has arrived to UE2) to be sent to the gNB1B, it had been had been set for the UE2 (or had been permitted (authorized) or approval (accepted)) may include information indicating one or more networks slices. Thus, GNB1B can know the UE2 (or desired) using network slice.
[0089]
 gNB1A is to Xn paging (ie, notification that downlink user data arrives to UE2) sending the GNB1B, it may include information set for the UE2 (notification) has been RAN notification area. Thus, GNB1B can know the cell to transmit the RAN-based paging.
[0090]
 Then, in the following, a configuration example of gNB1 and UE2 in accordance with embodiments described above. Figure 15 is a block diagram showing a configuration example of a gNB1 according to the embodiment described above. Referring to FIG. 15, GNB1 is, Radio Frequency transceiver 1501, a network interface 1503, a processor 1504, and memory 1505. RF transceiver 1501 performs an analog RF signal processing for communicating with NG UEs including UE2. RF transceiver 1501 may include a plurality of transceivers. RF transceiver 1501 is coupled to the antenna array 1502 and the processor 1504. RF transceiver 1501 receives the modulated symbol data from the processor 1504, generates a transmission RF signal and provides a transmit RF signal to the antenna array 1502. Also, RF transceiver 1501 to generate a baseband received signal based on the reception RF signal received by the antenna array 1502, and supplies it to the processor 1504. RF transceiver 1501 may include an analog beamformer circuitry for beam forming. Analog beamformer circuit includes, for example, a plurality of phase shifters and a plurality of power amplifiers.
[0091]
 Network interface 1503 is used to communicate with a network node (eg, the control node and forwarding node of 5G-CN4). Network interface 1503 may include, for example, a network interface card that complies with the IEEE 802.3 series (NIC).
[0092]
 The processor 1504 performs control plane processing and digital baseband signal processing for wireless communication (data plane processing). Processor 1504 may include multiple processors. For example, the processor 1504, a modem processor that performs digital baseband signal processing (eg, Digital Signal Processor (DSP)) and protocol stack processor for performing control plane processing (eg, Central Processing Unit (CPU) or Micro Processing Unit ( MPU)) may include. Processor 1504 may include a digital beamformer module for beamforming. Digital beamformer module, Multiple Input Multiple Output (MIMO) may include an encoder and precoder.
[0093]
 Memory 1505 is constituted by a combination of volatile and nonvolatile memory. Volatile memory may be, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. The non-volatile memory, a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. Memory 1505 may include a storage that is remotely located from the processor 1504. In this case, the processor 1504 may access the memory 1505 via the I / O interfaces that are not network interface 1503 or illustrated.
[0094]
 Memory 1505 may store one or more software modules (computer program) 1506 containing instructions and data for processing by gNB1 described in several embodiments described above. In some implementations, the processor 1504, the software module 1506 that reads out and executes from the memory 1505 may be configured to perform processing of gNB1 described in the above embodiments.
[0095]
 Figure 16 is a block diagram showing a configuration example of UE2. Radio Frequency (RF) transceiver 1601 performs an analog RF signal processing for communicating with GNB1. RF transceiver 1601 may include a plurality of transceivers. Analog RF signal processing performed by the RF transceiver 1601 includes a frequency up-conversion, the frequency down-conversion, and amplification. RF transceiver 1601 is coupled to the antenna array 1602, and a baseband processor 1603. RF transceiver 1601 receives the modulated symbol data (or OFDM symbol data) from the baseband processor 1603, generates a transmission RF signal and provides a transmit RF signal to the antenna array 1602. Also, RF transceiver 1601 to generate a baseband received signal based on the reception RF signal received by the antenna array 1602, and supplies it to the baseband processor 1603. RF transceiver 1601 may include an analog beamformer circuitry for beam forming. Analog beamformer circuit includes, for example, a plurality of phase shifters and a plurality of power amplifiers.
[0096]
 Baseband processor 1603 performs control plane processing and digital baseband signal processing for wireless communication (data plane processing). Digital baseband signal processing, (a) data compression / decompression, (b) segmentation / concatenation of data, generation / decomposition of (c) transmission format (transmission frame), (d) transmission channel coding / decoding , including generation of (e) modulation (symbol mapping) / demodulation, and OFDM symbol data by (f) Inverse Fast Fourier Transform (IFFT) (baseband OFDM signal). On the other hand, the control plane processing, layer 1 (eg, transmission power control), Layer 2 (eg, radio resource management, and hybrid automatic repeat request (HARQ) process), and layer 3 (eg, attach, mobility and call management including communication management signaling) related.
[0097]
 For example, a digital baseband signal processing by a baseband processor 1603, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, may include a signal processing of the MAC layer, and the PHY layer. Further, the control plane processing by baseband processor 1603, Non-Access Stratum (NAS) protocol, RRC protocol, and may include a process of MAC CE.
[0098]
 Baseband processor 1603 may perform MIMO encoding and precoding for beamforming.
[0099]
 Baseband processor 1603 may include a modem processor that performs digital baseband signal processing (eg, DSP) and a protocol stack processor for performing control plane processing (eg, CPU or MPU). In this case, the protocol stack processor for performing control plane processing may be shared with an application processor 1604 which will be described later.
[0100]
 The application processor 1604, CPU, MPU, also referred to as a microprocessor or processor cores. The application processor 1604 may include a plurality of processors (multiple processor cores). The application processor 1604, a memory 1606 or illustrated which do not result system read from the memory a software program (Operating System (OS)) and various application programs (e.g., call application, WEB browser, a mailer, a camera operation application, music playback by running the application), to implement the various functions of the UE2.
[0101]
 In some implementations, as indicated by the dashed line (1605) in FIG. 16, the baseband processor 1603 and an application processor 1604 may be integrated on a single chip. In other words, the baseband processor 1603 and an application processor 1604 may be implemented as a single System on Chip (SoC) device 1605. SoC devices, sometimes referred to as system Large Scale Integration (LSI) or chipset.
[0102]
 Memory 1606 is a volatile memory or nonvolatile memory, or a combination thereof. Memory 1606 may include a physically independent plurality of memory devices. Volatile memory is, for example, a SRAM or DRAM, or a combination thereof. The non-volatile memory, MROM, EEPROM, flash memory, or hard disk drive, or any combination thereof. For example, memory 1606, a baseband processor 1603, an application processor 1604, and may contain accessible external memory device from SoC1605. Memory 1606, within baseband processor 1603, within the application processor 1604, or may include an integrated chip memory device within SoC1605. Furthermore, memory 1606 may include a memory in the Universal Integrated Circuit Card (UICC).
[0103]
 Memory 1606 may store one or more software modules (computer program) 1607 containing instructions and data for processing by the UE2 described in several embodiments described above. Configuration In some implementations, the baseband processor 1603 or the application processor 1604, the software modules 1607 and executes from the memory 1606, to perform the processing of UE2 described with reference to the drawings in the above embodiments it may be.
[0104]
 As described with reference to FIGS. 15 and 16, each of the processors included in gNB1 and UE2 according to the embodiment described above, 1 or includes instructions for causing the algorithm described with reference to the drawings in the computer to run multiple programs. This program is stored using a non-transitory computer readable media of various types (non-transitory computer readable medium), it can be supplied to the computer. Non-transitory computer readable media include with various types of entities (tangible storage medium). Examples of non-transitory computer readable media include magnetic storage media (such as floppy disks, magnetic tape, hard disk drive), magneto-optical recording medium (e.g., magneto-optical disk), Compact Disc Read Only Memory (CD-ROM), CD- R, including CD-R / W, a semiconductor memory (e.g., a mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access memory (RAM)). The program may be provided to a computer using a temporary computer readable media of various types (transitory computer readable medium). Examples of transitory computer readable media include electric signals, optical signals, and electromagnetic waves. Transitory computer readable media, wired communication path such as electrical wires and optical fibers, or via a wireless communication path can provide the program to a computer.
[0105]

 5G-RAN3 described in the above-described embodiment, Cloud Radio Access Network (C- RAN) may be implemented on the basis of the concept. C-RAN may also be referred to as the Centralized RAN. Accordingly, the processes and operations performed by gNB1 described in the above embodiments, the Digital Unit (DU) contained in the C-RAN architecture, or may be provided by a combination of DU and Radio Unit (RU). DU is called the Baseband Unit (BBU) or Central Unit (CU). The RU, Remote Radio Head (RRH), Remote Radio Equipment (RRE), Distributed Unit (DU), or Transmission and Reception Point (TRP or TRxP) also called. That is, the processes and operations performed by each gNB1 described in the above embodiments may be provided by any one or more wireless stations (or RAN node).
[0106]
 The above-described embodiment has been described focusing on cell reselection by a UE in RRC_INACTIVE state. However, the network slices availability (network slice availability), for example not only be set for each cell may be further set for each PLMN. In other words, the desired network slices UE2 is not (whether it is or supported) or can be used in stay cells may be different for each PLMN. For example, availability information for networks slice (Network slice availability information) may be sent to UE2 in "per PLMN". Desired network slice UE2 the selected PLMN is not available (or not supported) if, UE AS layer may notify it to the NAS layer. In this case, AS layer may inform network slice information for each PLMN (eg, whether the network slice is available information, or network slice is available information) to the NAS layer. Then, NAS layer performs PLMN selection in consideration of the information received from the AS layer, the result (ie new selected PLMN) may be notified to the AS layer.
[0107]
 The embodiments described above may be applied to already any wireless communication systems support network slicing and using the RRC_INACTIVE state or similar RRC state therewith as described. For example, LTE in E-UTRAN (eNB) is connected to the 5G-CN, if the network slicing is supported in the cell of the E-UTRAN can be considered. Furthermore, as RRC_INACTIVE state described above, UE and eNB maintains at least a portion of the AS context of the UE, and UE knowledge is the level in E-UTRAN for a predetermined area set by the E-UTRAN location of is if you are state or sub-state or operation mode is supported is assumed. At this time, the predetermined area may be a similar RAN notification area, location area of ​​the core network (eg, TA) and may be the same.

claims

A base station that is provided for radio access network (RAN),
 a memory,
 and at least one processor coupled to said memory,
comprising a
 at least one processor, a first RRC state, the second RRC states, and is configured to control the state transitions of the first wireless terminal among the third RRC state,
 the first RRC state, the first wireless terminal and the RAN has access layer (access a state of maintaining a stratum (AS)) context, and a state where the position of the first wireless terminal is known by the RAN at the level of the cell,
 the second RRC state, the first a state in which the wireless terminal and the RAN maintains at least a portion of the AS context, and the state in which the position of the first wireless terminal is known by the RAN at the level of the RAN notification area set by the RAN There,
 the third RRC state, the first wireless terminal and the RAN is a state in which has released the AS context, and the state where the position of the first wireless terminal is not known by the RAN and at,
 the at least one processor is further the first network slice set in the first wireless terminal for data communication with at least the first RRC state is included in the RAN notification area explicitly or implicitly the first wireless terminal is configured to notify, whether it is possible to use in the cell
base station.
[Requested item 2]
 Wherein the at least one processor transmits the first information indicating explicitly whether it is possible to use in each cell of the first network slice is included in the RAN notifies area to the first wireless terminal as configured,
the base station according to claim 1.
[Requested item 3]
 Wherein the at least one processor, at the time of setting the RAN notification area to the first wireless terminal, configured to transmit the first information to the first wireless terminal,
according to claim 2 base station.
[Requested item 4]
 Wherein the at least one processor, in the procedure for transition to the second RRC state the first wireless terminal from the first RRC state, to transmit the first information to the first wireless terminal configured,
the base station according to claim 2 or 3.
[Requested item 5]
 Wherein the at least one processor, the configured including RAN notification area, and the RAN notifying area for the first of the first wireless terminal only one or more cells is a network slices available the is configured to set the first wireless terminal,
 the RAN notifies area is implicitly indicating that it can be used in each cell of the first network slice is included in the RAN notification area,
according to claim 1 base stations of.
[Requested item 6]
 Wherein the at least one processor, information indicating the one or more network slices or unusable available in each cell of the other base stations, received from the other base station via an interface between base stations is configured,
the base station according to any one of claims 1 to 5.
[Requested item 7]
 Wherein the at least one processor is in the second in the steps to transition the wireless terminal from the second RRC state to the first RRC state or after, the first RRC state the second wireless terminal in the past and second information indicating a second network slice is set to the second wireless terminal when was configured to receive from the second wireless terminal,
one of the claims 1 to 6, the base station according to item 1 or.
[Requested item 8]
 Wherein the at least one processor, the when the second network slice is the base station or the second wireless terminal is not available in the cell to be connected, the second wireless terminal to another base station or another cell It is configured to move in,
the base station according to claim 7.
[Requested item 9]
 Wherein the first RRC state is a RRC_CONNECTED state,
 the second RRC state is a RRC_INACTIVE state,
 the third RRC state is a RRC_IDLE state,
in any one of claims 1 to 8 the base station according.
[Requested item 10]
 The RAN notification area, good areas without reported by moving between cells and the cell reselection to the RAN by the cell reselection when the first wireless terminal is the second RRC state there,
the base station according to any one of claims 1-9.
[Requested item 11]
 A base station that is provided for radio access network (RAN),
 a memory,
 and at least one processor coupled to said memory,
comprising a
 at least one processor, a first RRC state, the second It is configured to control the state transitions of the wireless terminals between the RRC states, and a third RRC state,
 the first RRC state, the wireless terminal and the RAN has access layer (access stratum (aS)) context a state of maintaining, and said a state where the position of the wireless terminal is known by the RAN at the level of the cell,
 the second RRC state, the at least one wireless terminal and the RAN are the AS context a state that maintains the parts, and the the state in which the position of the wireless terminal is known by the RAN at the level of the set RAN notification area by said RAN,
 said third RRC state, before A state where the wireless terminal and the RAN has released the AS context, a and state the position of the wireless terminal is not known by the RAN,
 wherein the at least one processor is further third of the base station it has, is configured to transmit in said first cell are available or unavailable one or more system information indicating the network slices in one cell
base station.
[Requested item 12]
 The system information is the broadcast system information is broadcast in the first cell, or the on-demand system information in response to a request message from the radio terminal is transmitted to the wireless terminal,
in claim 11 the base station according.
[Requested item 13]
 Wherein the at least one processor, said at steps or in subsequent shifts to the first RRC state wireless terminals from the second RRC state, when the wireless terminal was the past first RRC state wherein the information indicating the first network slice that has been set in the wireless terminal is configured to receive from the wireless terminal,
a base station according to claim 11 or 12.
[Requested item 14]
 Wherein the at least one processor, said if it is not available in the first network slice the base station or the cell in which the wireless terminal is connected, be configured to transfer the wireless terminal to another base station or another cell are,
the base station according to claim 13.
[Requested item 15]
 Wherein the first RRC state is a RRC_CONNECTED state,
 the second RRC state is a RRC_INACTIVE state,
 the third RRC state is a RRC_IDLE state,
in any one of claims 11 to 14 the base station according.
[Requested item 16]
 A wireless terminal,
 a transceiver,
 and at least one processor configured to control the transceiver in one or more cells associated with a radio access network (RAN),
includes a,
 the at least one processor, first RRC state, the second RRC state, and the between the third RRC state is configured to control the state transition of the wireless terminal,
 the first RRC state, the wireless terminal and the RAN is access layer is a state of maintaining (access stratum (AS)) context, and the the state in which the position of the wireless terminal is known by the RAN at the level of the cell,
 the second RRC state, the wireless terminal and a state in which the RAN maintains at least a portion of the AS context, the in RAN and at the level of the RAN notification area whose position is set by the RAN wireless terminal A state known me,
 the third RRC state, the a state in which the wireless terminal and the RAN has released the AS context and location of the wireless terminal known by the RAN an absence,
 the at least one processor further includes a first network slice set in the wireless terminal for data communication with at least the first RRC state is in the second RRC state it is configured to check whether or not it is possible to use in the cell to be reselected by the cell reselection,
the radio terminal.
[Requested item 17]
 Wherein the at least one processor, whether it is available in each cell a first network slice set in the wireless terminal for data communication with at least the first RRC state is included in the RAN notification area it has, configured to receive first information indicating explicitly from the base station in the RAN or
wireless terminal according to claim 16.
[Requested item 18]
 Wherein the at least one processor is within steps the wireless terminal transitions to the second RRC state from the first RRC state, configured to receive the first information,
according to claim 17 wireless terminal.
[Requested item 19]
 The RAN notification area includes only the first one or more cellular networks slice is available,
 wherein the at least one processor receives a configuration of the RAN notification area from the base station in the RAN configured,
 the at least one processor, wherein based on whether the cell is re-selected is included in the RAN notification area, whether the first network slice can be used in the cell to be the reselected It is configured to check whether,
wireless terminal according to claim 16.
[Requested item 20]
 Wherein the at least one processor is the second in response to cell reselection in RRC state, the re-selected by the system information indicating the one or more network slices available or unavailable used in the cell wherein the received configured to attempt in the cell to be reselected,
 the at least one processor, based on the system information, checks whether available in the cell where the first network slice is the reselected It is configured to,
wireless terminal according to claim 16.
[Requested item 21]
 The system information is the broadcast system information is broadcast in the cell to be reselected, or the on-demand system information in response is transmitted to the radio terminal in the request message from the wireless terminal,
according to claim 20 wireless terminal according to.
[Requested item 22]
 Wherein the at least one processor, when the first network slice can not confirm that it can be used in a cell that is the re-selection, the re the wireless terminal from the second RRC state to the first RRC state in the procedure in or after a transition in the cells selected, the second information indicating the first network slice is configured to be transmitted to the base station of the cell to be reselected,
either claims 16-21 wireless terminal according to any one of claims.
[Requested item 23]
 Wherein the first RRC state is a RRC_CONNECTED state,
 the second RRC state is a RRC_INACTIVE state,
 the third RRC state is a RRC_IDLE state,
in any one of claims 16-22 wireless terminal according.
[Requested item 24]
 A method in a base station that is provided for radio access network (RAN),
 a first RRC state, the second RRC state, and the first control state transition of the wireless terminal between the third RRC state to it, and
 used in each cell at least said first of the first network slice set in the first wireless terminal for data communication in a RRC state is included in the RAN notification area set by the RAN possible is whether explicitly or implicitly the notifying the first wireless terminal,
comprising a
 first RRC state, the first wireless terminal and the RAN has access layer (access stratum (AS)) is a state of maintaining a context, and a state where the position of the first wireless terminal is known by the RAN at the level of the cell,
 the second RRC state, the first radio terminal and the RAN are the AS configuration A state of maintaining at least a portion of the text, and a state where the position of the first wireless terminal is known by the RAN at the level of the RAN notification area,
 the third RRC state, the first a state where the first wireless terminal and the RAN has released the aS context, a and a state in which the position of the first wireless terminal is not known by the RAN,
the method.
[Requested item 25]
 A method in a base station that is provided for radio access network (RAN),
 a first RRC state, to control the state transitions of the wireless terminals between the second RRC state, and the third RRC state, and
 that, to transmit the first in the cell available or not available 1 or system information indicating the more networks slices of the base station in the first cell
comprises a
 first RRC state , the wireless terminal and the RAN is in state to maintain the access layer (access stratum (AS)) context, a and the state in which the position of the wireless terminal is known by the RAN at the level of the cell,
 the second RRC states, the wireless terminal and the RAN is in state to maintain at least a portion of the AS context, and at the level of the RAN notification area whose position is set by the RAN of the wireless terminal A condition known by serial RAN,
 the third RRC state, the a state in which the wireless terminal and the RAN has released the AS context, is and known by said RAN location of the wireless terminal it is a state does not,
method.
[Requested item 26]
 A method in a wireless terminal,
 a first RRC state, the second RRC state, and a third controlling state transition of the wireless terminal between the RRC states, and
 at least the first RRC state wherein the first network slice set in the wireless terminal checks whether it is possible to use in the cell is re-selected by cell reselection by the second RRC state for data communication,
the provided,
 the first RRC state, the wireless terminal and the radio access network (RAN) access layer (access stratum (AS)) is a state of maintaining a context, and at the level of the position the cell of the radio terminal wherein a condition known by RAN,
 the second RRC state, the wireless terminal and the RAN is in state to maintain at least a portion of the AS context, and the position of the wireless terminal RAN A condition known by the RAN in a more set RAN notification level area,
 the third RRC state is a state where the wireless terminal and the RAN has released the AS context, and the it is a state in which the position of the wireless terminal is not known by the RAN,
the method.
[Requested item 27]
 The non-transitory computer readable medium storing a program for causing a process in a base station which is disposed in a radio access network (RAN) to a computer,
 the method comprising
 a first RRC state, the second RRC state, and a third controlling state transition of the first wireless terminal among RRC state, and
 is set to the first wireless terminal for data communication with at least the first RRC state the first network slice notify explicitly or implicitly the first wireless terminal whether or not it is possible to use in each cell included in the RAN notification area set by the RAN,
includes a,
 the the first RRC state, the first wireless terminal and the RAN has access layer (access stratum (AS)) is a state of maintaining a context, the and in the first level of the position of the wireless terminal cell RAN A condition known by
 the second RRC state is a state where the first wireless terminal and the RAN maintains at least a portion of the AS context, and position of the first wireless terminal a state but which is known by the RAN at the level of the RAN notification area,
 the third RRC state is a state where the first wireless terminal and the RAN has released the AS context, and the first position of the wireless terminal is in a state not known by the RAN,
non-transitory computer readable media.
[Requested item 28]
 The non-transitory computer readable medium storing a program for causing a process in a base station which is disposed in a radio access network (RAN) to a computer,
 the method comprising
 a first RRC state, the second RRC state, and a third controlling state transition of the wireless terminal between the RRC states, and
 system according to the first in a cell available or unavailable one or more network slices of the base station transmitting the information in the first cell,
comprising a
 first RRC state is an state of maintaining the radio terminal and the radio access network (RAN) access layer (access stratum (AS)) context and wherein a state where the position of the wireless terminal is known by the RAN at the level of the cell,
 the second RRC state, the wireless terminal and the RAN are the AS copolymer A state of maintaining at least a portion of the text, and the a state in which the position of the wireless terminal is known by the RAN at the level of the RAN notification area set by said RAN,
 said third RRC state, wherein a state of the wireless terminal and the RAN has released the aS context, and the location of the wireless terminal is in a state not known by the RAN,
non-transitory computer readable media.
[Requested item 29]
 The non-transitory computer readable medium storing a program for causing a method in a wireless terminal to a computer,
 the method comprising
 a first RRC state, the second RRC state, and during the third RRC state It said controlling state transition of the wireless terminal, and at
 least the first network slice the set in the wireless terminal for data communication in the first RRC state is in the second RRC state confirming whether or not it is possible to use in the cell is re-selected by cell reselection,
comprising a
 first RRC state, the wireless terminal and the radio access network (RAN) access layer (access stratum ( AS)) is a state of maintaining a context, and the the state in which the position of the wireless terminal is known by the RAN at the level of the cell,
 the second RRC state, the wireless terminal and the front A state in which serial RAN maintains at least a portion of the AS context, a and the state in which the position of the wireless terminal is known by the level of the set RAN notification area RAN by the RAN,
 the third the RRC states, the a state of the wireless terminal and the RAN has released the aS context, and the location of the wireless terminal is in a state not known by the RAN,
non-transitory computer readable media.

Documents

Application Documents

# Name Date
1 201917026475.pdf 2019-07-02
2 201917026475-TRANSLATIOIN OF PRIOIRTY DOCUMENTS ETC. [02-07-2019(online)].pdf 2019-07-02
3 201917026475-STATEMENT OF UNDERTAKING (FORM 3) [02-07-2019(online)].pdf 2019-07-02
4 201917026475-REQUEST FOR EXAMINATION (FORM-18) [02-07-2019(online)].pdf 2019-07-02
5 201917026475-PROOF OF RIGHT [02-07-2019(online)].pdf 2019-07-02
6 201917026475-PRIORITY DOCUMENTS [02-07-2019(online)].pdf 2019-07-02
7 201917026475-POWER OF AUTHORITY [02-07-2019(online)].pdf 2019-07-02
8 201917026475-FORM 18 [02-07-2019(online)].pdf 2019-07-02
9 201917026475-FORM 1 [02-07-2019(online)].pdf 2019-07-02
10 201917026475-DRAWINGS [02-07-2019(online)].pdf 2019-07-02
11 201917026475-DECLARATION OF INVENTORSHIP (FORM 5) [02-07-2019(online)].pdf 2019-07-02
12 201917026475-COMPLETE SPECIFICATION [02-07-2019(online)].pdf 2019-07-02
13 201917026475-Power of Attorney-040719.pdf 2019-07-16
14 201917026475-OTHERS-040719.pdf 2019-07-16
15 201917026475-OTHERS-040719-.pdf 2019-07-16
16 201917026475-Correspondence-040719.pdf 2019-07-16
17 201917026475-OTHERS-120719.pdf 2019-07-22
18 201917026475-OTHERS-120719-1.pdf 2019-07-22
19 201917026475-OTHERS-120719-.pdf 2019-07-22
20 201917026475-Correspondence-120719.pdf 2019-07-22
21 abstract.jpg 2019-08-08
22 201917026475-FORM 3 [26-12-2019(online)].pdf 2019-12-26
23 201917026475-OTHERS [09-02-2021(online)].pdf 2021-02-09
24 201917026475-Information under section 8(2) [09-02-2021(online)].pdf 2021-02-09
25 201917026475-FORM-26 [09-02-2021(online)].pdf 2021-02-09
26 201917026475-FORM 3 [09-02-2021(online)].pdf 2021-02-09
27 201917026475-FER_SER_REPLY [09-02-2021(online)].pdf 2021-02-09
28 201917026475-DRAWING [09-02-2021(online)].pdf 2021-02-09
29 201917026475-COMPLETE SPECIFICATION [09-02-2021(online)].pdf 2021-02-09
30 201917026475-CLAIMS [09-02-2021(online)].pdf 2021-02-09
31 201917026475-ABSTRACT [09-02-2021(online)].pdf 2021-02-09
32 201917027056-Power of Attorney-010421.pdf 2021-10-18
33 201917027056-Correspondence-010421.pdf 2021-10-18
34 201917026475-Power of Attorney-010421.pdf 2021-10-18
35 201917026475-FER.pdf 2021-10-18
36 201917026475-Correspondence-010421.pdf 2021-10-18
37 201917026475-PatentCertificate08-08-2023.pdf 2023-08-08
38 201917026475-IntimationOfGrant08-08-2023.pdf 2023-08-08

Search Strategy

1 475E_27-08-2020.pdf

ERegister / Renewals

3rd: 03 Nov 2023

From 21/11/2019 - To 21/11/2020

4th: 03 Nov 2023

From 21/11/2020 - To 21/11/2021

5th: 03 Nov 2023

From 21/11/2021 - To 21/11/2022

6th: 03 Nov 2023

From 21/11/2022 - To 21/11/2023

7th: 03 Nov 2023

From 21/11/2023 - To 21/11/2024

8th: 18 Nov 2024

From 21/11/2024 - To 21/11/2025

9th: 18 Nov 2025

From 21/11/2025 - To 21/11/2026