JPWO2018131453A1 - RAN connection control method and base station - Google Patents

Abstract

A base station (eNB) having a table storing parameter information for RAN connection setting in association with MMEGI, which is an example of information for selecting a slice to be allocated in accordance with a service used by a terminal, is an attach request. (Or TAU request) is received from the terminal (UE) (S1), and the MMEGI to be selected according to the UE Usage type (for example, mobility of the terminal, service request quality, etc.) related to the service usage of the terminal is sent to the core network Request and obtain (S6), determine a RAN connection method between the terminal and the base station (eNB) based on the obtained MMEGI (S8), obtain parameter information corresponding to the MMEGI from the table, and By notifying the terminal of the information, the terminal can be connected to the RAN by the determined RAN connection method. Control is performed (S9 to S12).

Description

  The present invention relates to a RAN connection control method and a base station.

  In recent years, quality of experience (QoE), which indicates the quality experienced by a terminal user for services provided on a network, has been regarded as important as an index related to service quality in the network. Therefore, in order to maintain the QoE for each terminal user at a high level in the fifth generation (5G (5th Generation)) network era, when selecting a slice that is a virtual network logically generated on the network infrastructure. In addition to the core network, end-to-end (E2E) quality management considering quality in a radio access network (Radio Access Network (hereinafter referred to as “RAN”)) is important. Actually, there is almost no delay in the core network, so it is necessary to suppress the delay generated in the RAN in consideration of QoE for each terminal user.

3GPP TS 23.401

  Currently, in the standard proposed in Non-Patent Document 1, for example, when an attach request is made from a terminal to the base station when the terminal is turned on, the base station uses an MME (Mobility Management Entity) in the core network. Is selected based on the MME group identification information (MME Group Identifier (hereinafter referred to as “MMEGI”)) notified from the network, and the core network satisfying the service requirements (specifically, the MME selected according to the MMEGI) is selected. A process of redirecting the terminal is performed.

  However, Non-Patent Document 1 does not propose to control a wireless communication connection method (hereinafter referred to as “RAN connection method”) in the RAN between the terminal and the base station, and the RAN is based on a so-called best effort method. Only connection control is performed, and there is room for improvement in the control of the RAN connection method in consideration of QoE for each terminal user.

  The present invention has been made to solve the above-described problems, and an object thereof is to appropriately control the RAN connection method and improve the QoE for each terminal user.

  A RAN connection control method according to an embodiment of the present invention stores parameter information for setting up a RAN connection with a terminal in association with information for selecting a slice to be allocated according to a service used by the terminal. RAN connection control method executed by a base station comprising a table, a reception step of receiving an attach request or a location registration information update request from the terminal, and the attachment request or the location registration information by the reception step When an update request is received, an acquisition step of requesting and acquiring information for selecting a slice to be allocated according to the service used by the terminal from the core network, and the slice acquired by the acquisition step RAN connection with the terminal based on the information for selection A determination step for determining a method; and the parameter information corresponding to the information for selecting the slice is obtained from the table, and the parameter information is notified to the terminal, whereby the RAN connection determined by the determination step is determined. And a control step of controlling to make a RAN connection with the terminal by a method.

  According to the RAN connection control method according to the embodiment of the present invention described above, when the base station receives an attach request or a location registration information update request from a terminal, the base station selects a slice to be allocated according to the service used by the terminal. Requesting the core network to acquire information to determine the RAN connection method with the terminal based on the acquired information for selecting the slice, and the information for selecting the slice Corresponding parameter information is obtained from the table, and the parameter information is notified to the terminal, thereby controlling the RAN connection with the terminal by the determined RAN connection method. Accordingly, an appropriate RAN connection method is determined based on the information for selecting the slice acquired from the core network, and the parameter information stored in association with the information for selecting the slice in advance (that is, Parameter information for setting the RAN connection between the terminal and the base station) and information for selecting the slice acquired from the core network are used to acquire parameter information appropriate for the terminal, and the parameter information Can be controlled to be connected to the terminal by the appropriate RAN connection method. Therefore, it is possible to appropriately control the RAN connection method and improve the QoE for each terminal user. Note that the above-mentioned “MMEGI” can be used as the “information for selecting a slice” and, for example, DCN (Dedicated Core Network) identification information (next-generation network proposed in 3GPP TR 23.799) ( So-called DCN-ID), Service Type and DNN (Domain Network Name) associated with the DCN-ID can be used.

  Further, an embodiment of the present invention relating to the above RAN connection control method can also be regarded as an invention relating to a base station, and can be described as follows. The invention according to the following base station has the same operation and effect.

  The base station according to an embodiment of the present invention stores a parameter information for setting a RAN connection with the terminal in association with information for selecting a slice to be allocated according to a service used by the terminal. And a receiving unit that receives an attach request or a location registration information update request from the terminal, and if the attach request or the location registration information update request is received by the receiving unit, it is assigned according to a service used by the terminal An acquisition unit that requests and acquires information for selecting a slice to be obtained from the core network, and a RAN connection method with the terminal is determined based on the information for selecting the slice acquired by the acquisition unit And determining the parameter information corresponding to the information for selecting the slice. Obtained from Le By notifying the parameter information to the terminal, and a control unit for controlling so as to connect the terminal and the RAN by the RAN connection method determined by the determination unit.

  According to the present invention, it is possible to appropriately control the RAN connection method and improve QoE for each terminal user.

It is a figure which shows the structural example of the communication system which concerns on one Embodiment of this invention. It is a figure which shows the example of data of the table which a base station hold | maintains. It is a figure which shows the hardware structural example of each apparatus. It is a sequence diagram which shows the process example when an attach request is transmitted from the terminal. It is a sequence diagram which shows the process example when the position registration information update (TAU) request is transmitted from the terminal.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[Description of Configuration of Communication System and Each Device According to Embodiment]
As shown in FIG. 1, a communication system according to an embodiment of the present invention includes a terminal (User Equipment (hereinafter also referred to as “UE”)) 10 and an eNodeB (hereinafter referred to as “eNB”) 20 corresponding to a base station in the RAN. A plurality of mobility management entities (MMEs) 30, a home subscriber server (HSS) 60, a plurality of serving gateways (SGWs) 40, and a plurality of packet data network gateways (PGWs) 50 located upstream of the SGW 40, , Including.

  The MME 30 is a device that performs processing such as location management, authentication control, communication path setting, and the like of the UE 10 located in the network, and corresponds to the “processing server” recited in the claims. The HSS 60 is a device that manages user information (subscriber information) of terminal users. The SGW 40 is a gateway device that functions as a serving packet switch that accommodates LTE (Long Term Evolution), and one or a plurality of SGWs 40 are provided corresponding to the requirements of the communication service used by the UE 10. The PGW 50 is a junction point with a PDN (Packet data network), and is a gateway device that performs IP address assignment, packet transfer to the SGW, and the like.

  Now, as a functional block related to the present invention, the eNB 20 uses an MME Group Identifier (hereinafter referred to as parameter information for selecting a slice to be allocated according to the service used by the UE 10) as parameter information for setting the RAN connection. A table 21 stored in association with “MMEGI”, a receiving unit 22 that receives a location registration information update (Tracking Area Update) request (hereinafter referred to as “TAU request”) or an attach request from the UE 10, and a receiving unit 22 When a TAU request or an attach request is received by the UE 10, the UE 10 is assigned to the UE 10 according to usage type information (hereinafter referred to as “UE Usage type”, including the mobility of the UE 10, service request quality, etc.). Information for selecting the slice The MMEGI) requesting the core network to acquire, the determination unit 24 for determining the RAN connection method between the UE 10 and the eNB 20 based on the MMEGI acquired by the acquisition unit 23, and the parameters corresponding to the MMEGI And a control unit 25 configured to control the RAN connection between the UE 10 and the eNB 20 by acquiring the information from the table 21 and notifying the UE 10 of the parameter information by the RAN connection method determined by the determination unit 24.

  In FIG. 2, the example of data of the table 21 which eNB20 hold | maintains is shown. As shown in FIG. 2, the table 21 includes, as parameter information for setting the RAN connection, for example, information on the radio communication frequency band that can be used by the terminal and the MAC layer of the radio communication section that is used by the terminal. Is stored in association with MMEGI. By using such various parameter information, a suitable RAN connection method can be selected.

  Further, as the parameter information, the table 21 may further include delay time information allowable by the terminal, information relating to whether or not to discard the packet, and spare parameters including information related to a combination thereof. In this case, flexible priority control can be performed.

  Here, an example of the hardware configuration of the eNB 20 corresponding to the “base station” of the present invention will be described with reference to FIG. The eNB 20 may be physically configured as a computer device including a processor 20A, a memory 20B, a storage 20C, a communication module 20D, an input device 20E, an output device 20F, a bus 20G, and the like. The functional block (configuration unit) of the eNB 20 is realized by any combination of hardware and / or software. Further, the means for realizing each functional block is not particularly limited. In other words, each functional block may be realized by one device physically and / or logically coupled, or two physically and / or logically separated two wired and / or wirelessly linked to each other. You may implement | achieve with the above apparatus. Note that the hardware configuration example described below is not limited to the eNB 20 and may be employed in the HSS 60, the PGW 50, the SGW 40, the MME 30, and the UE 10 illustrated in FIG.

  In the following description, the term “apparatus” can be read as a circuit, a device, a unit, or the like. The hardware configuration of the eNB 20 may be configured to include one or a plurality of devices illustrated in the figure, or may be configured not to include some devices.

  Each function in the eNB 20 reads predetermined software (program) on hardware such as the processor 20A and the memory 20B, so that the processor 20A performs calculation, performs communication by the communication module 20D, and stores data in the memory 20B and the storage 20C. This is realized by controlling reading and / or writing.

  For example, the processor 20A operates an operating system to control the entire computer. The processor 20A may be configured by a central processing unit (CPU) including an interface with a peripheral device, a control device, an arithmetic device, a register, and the like.

  Further, the processor 20A reads a program (program code), a software module, and data from the storage 20C and / or the communication module 20D to the memory 20B, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. For example, the reception unit 22, the acquisition unit 23, the determination unit 24, the control unit 25, and the like may be realized by a control program stored in the memory 20B and executed by the processor 20A, and are similarly realized for other functional blocks. May be. Although the above-described various processes have been described as being executed by one processor 20A, they may be executed simultaneously or sequentially by two or more processors 20A. The processor 20A may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunication line.

  The memory 20B is a computer-readable recording medium and includes, for example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), and the like. May be. The memory 20B may be called a register, a cache, a main memory (main storage device), or the like. The memory 20B can store a program (program code), a software module, and the like that can be executed to implement the wireless communication method according to the embodiment of the present invention.

  The storage 20C is a computer-readable recording medium, such as an optical disc such as a CD-ROM (Compact Disc ROM), a hard disc drive, a flexible disc, a magneto-optical disc (eg, a compact disc, a digital versatile disc, a Blu-ray). (Registered trademark) disk, smart card, flash memory (for example, card, stick, key drive), floppy (registered trademark) disk, magnetic strip, and the like. The storage 20C may be called an auxiliary storage device. The above-described storage medium may be, for example, a database, a server, or other suitable medium including the memory 20B and / or the storage 20C.

  The communication module 20D is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also referred to as a network device, a network controller, a network card, or the like.

  The input device 20E is an input device that accepts external input. The output device 20F is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 20E and the output device 20F may have an integrated configuration (for example, a touch panel).

  Each device such as the processor 20A and the memory 20B is connected by a bus 20G for communicating information. The bus 20G may be configured with a single bus or may be configured with different buses between devices.

  The eNB 20 includes hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). Alternatively, some or all of the functional blocks may be realized by the hardware. For example, the processor 20A may be implemented by at least one of these hardware.

[Description of Processing Contents According to Embodiment of Invention]
Hereinafter, processing contents according to the RAN connection control method of the present invention will be described.

(Figure 4: Example of processing when an attach request is sent from the UE)
First, a processing example when an attach request is transmitted from the UE, for example, triggered by the power-on of the UE, for example, will be described with reference to FIG. In the process of FIG. 4, as the MME 30 in FIG. 1, a default MME previously associated with the eNB and an MME (selected MME) corresponding to the MMEGI selected in the process described later are involved. These are referred to as “default MME” and “selected MME”.

  As shown in FIG. 4, when the eNB receives an attach request from the UE (step S1), the eNB transfers the attach request to the default MME (step S2), and the existing sequence defined in 3GPP (steps S3 to S6). After that, MMEGI is acquired. Specifically, after receiving the attach request, the default MME sends an authentication information request to the HSS in order to obtain UE authentication information (step S3). As a response, the default MME returns an authentication information response including the UE usage type. Receive from HSS (step S4). And default MME selects the information (here MMEGI) for selecting the slice (namely, slice corresponding to the use service of UE registered into HSS) which should be allocated according to received UE usage type (step). S5) A reroute NAS request including the selected MMEGI and attach message is transmitted to the eNB (step S6). Thereby, eNB can acquire MMEGI which should be selected according to UE usage type.

  Thereafter, the eNB performs processing based on the obtained MMEGI after executing processing (for example, allocation of network resources for services to the UE) (step S7) based on the existing sequence of NNSF (NAS Node Selection Function). The RAN connection method between the eNBs is determined (step S8), and the parameter information corresponding to the acquired MMEGI is acquired from the table 21 of FIG. 2 and the parameter information is notified to the UE. The RAN connection method is used to control the RAN connection between the UE and the eNB (steps S9 to S11).

  Specifically, the eNB instructs the UE to change to the RAN connection method determined in step S8 (step S9), receives an acknowledgment from the UE (step S10), and then determines whether to change to the determined RAN connection method. A change process is performed (step S11). For example, in the example of FIG. 2, when the eNB acquires “MMEGI1” as the MMEGI, the service requirement of “full” as the radio communication frequency band that can be used by the UE and “high” as the priority in the MAC layer of the radio communication section The RAN connection method is changed to satisfy the above condition. In addition, when the eNB acquires “MMEGI3” as the MMEGI, the RAN connection is performed so as to satisfy the service requirement of “best effort” as the radio communication frequency band usable by the UE and “medium” as the priority in the MAC layer of the radio communication section. The method is changed.

  Further, the eNB sends an attach request, an MMEGI, and an MME corresponding to the acquired MMEGI (that is, an MME corresponding to a slice allocated according to the UE usage type; described as “selected MME” in FIG. 4). The initial UE message including is transmitted (step S12). Thereafter, similar to the existing sequence, the selected MME redirects the UE and eNB to a suitable core network (SGW and PGW in FIG. 1) that satisfies the service requirements of the UE.

  Through the above processing, it is possible to appropriately control the RAN connection method in consideration of end-to-end quality including quality in RAN, and to improve QoE for each terminal user.

  When redirecting to the core network, the eNB may perform a new RAN connection while maintaining the previous RAN connection with the terminal, or disconnect the previous RAN connection with the terminal. A new RAN connection may be made above. Thus, flexible control is possible by selectively holding or disconnecting the previous RAN connection. In addition, the control for performing a new RAN connection while maintaining the previous RAN connection with the terminal, and the control for performing the new RAN connection after disconnecting the previous RAN connection with the terminal are performed by existing protocols. Is possible.

(FIG. 5: Processing example when TAU request is transmitted from UE)
Next, an example of processing when a TAU request is transmitted from the UE triggered by, for example, the UE moving across a location registration area (Tracking Area) will be described with reference to FIG. In the process of FIG. 5, as the MME 30 of FIG. 1, a default MME similar to that of FIG. 4, an old MME involved in providing services to the UE before movement, and an MME ( These are referred to as “default MME”, “old MME”, and “selected MME”, respectively.

  As shown in FIG. 5, when the eNB receives the TAU request from the UE (Step S21), the eNB transfers the TAU request to the default MME (Step S22), and the existing sequence defined in 3GPP (Steps S23 to S26). After that, MMEGI is acquired. Specifically, after receiving the TAU request, the default MME sends an identification / context request to the old MME to obtain information on the old MME and UE (step S23), and includes a UE usage type as a response. An identification / context response is received from the old MME (step S24). And default MME selects the information (here MMEGI) for selecting the slice (namely, slice which should take over the usage service of UE before movement) according to received UE usage type (step S25). Then, a reroute NAS request including the selected MMEGI and the TAU message is transmitted to the eNB (step S26). Thereby, eNB can acquire MMEGI which should be selected according to UE usage type.

  Thereafter, the eNB performs processing based on the obtained MMEGI after the execution of processing based on the NNSF (NAS Node Selection Function) of the existing sequence (for example, network resource allocation for service to the UE) (step S27). The RAN connection method between the eNBs is determined (step S28), and the parameter information corresponding to the acquired MMEGI is acquired from the table 21 of FIG. 2 and the parameter information is notified to the UE. The RAN connection method is used to control the RAN connection between the UE and the eNB (steps S29 to S31).

  Specifically, the eNB instructs the UE to change to the RAN connection method determined in step S28 (step S29), and after receiving an acknowledgment from the UE (step S30), the eNB changes to the determined RAN connection method. A change process is performed (step S31). The change process here is the same as the process of FIG. 4 described above.

  Further, the eNB sends the TAU request, the MMEGI, and the MME corresponding to the acquired MMEGI (that is, the MME corresponding to the slice assigned according to the UE usage type; described as “selected MME” in FIG. 5). The initial UE message including is transmitted (step S32). Thereafter, similar to the existing sequence, the selected MME redirects the UE and eNB to a suitable core network (SGW and PGW in FIG. 1) that satisfies the service requirements of the UE.

  Through the above processing, it is possible to appropriately control the RAN connection method in consideration of end-to-end quality including quality in RAN, and to improve QoE for each terminal user.

  Similar to the processing of FIG. 4, when redirecting to the core network, the eNB may perform a new RAN connection while maintaining the previous RAN connection with the terminal, or After disconnecting the previous RAN connection, a new RAN connection may be made. Thus, flexible control is possible by selectively holding or disconnecting the previous RAN connection.

  In the above embodiment, the embodiment in which the present invention is applied to a network based on the standard proposed in 3GPP TS 23.401 has been described. However, the present invention may be applied to, for example, the following 3GPP TR 23.799. It can also be applied to generational networks. Specifically, in the above embodiment, processing using MMEGI has been described as an example of information for selecting a slice to be allocated according to a service used by a terminal. However, when the present invention is applied to a next-generation network As the information for selecting the slice, DCN (Dedicated Core Network) identification information (so-called DCN-ID), Service Type associated with the DCN-ID, DNN (Domain Network Name), etc., instead of the MMEGI Either of them can be used to execute the same RAN connection control, and the same operations and effects can be achieved. In the case of a next generation network, for example, the MME 30 in the configuration diagram of FIG. 1 is a common control plane (Common Control Plane), the HSS 60 is an SDM (Subscription Data Management), and the SGW 40 and the PGW 50 are CP-SM (Control Plane-). It becomes a core network that includes Session Management and User Plane.

  Further, in the above embodiment, as parameter information for setting up the RAN connection, information on radio resource allocation shown in FIG. 2 (for example, a radio communication frequency band that can be used by the terminal) is illustrated, and radio resource allocation in the RAN connection is illustrated. An example of controlling the above has been described. However, the present invention is not limited to the control of radio resource allocation in the RAN connection, and the terminal connects to either the cellular communication network or the non-cellular communication network as parameter information for setting the RAN connection. Such information may be stored in a table, and the information may be used to control to which of the cellular communication network and the non-cellular communication network the terminal is connected. The non-cellular communication network means a communication network other than the cellular communication network (for example, a wireless local area network (LAN)), specifically, a wireless communication network based on the Wi-Fi (registered trademark) standard, This includes wireless communication networks based on the LoRA (registered trademark) standard and the Sigfox (registered trademark) standard, which are wireless standards for Massive IoT (large-scale IoT (Internet of Things)).

  Although the present embodiment has been described in detail above, it will be apparent to those skilled in the art that the present embodiment is not limited to the embodiment described in this specification. The present embodiment can be implemented as a modification and change without departing from the spirit and scope of the present invention defined by the description of the scope of claims. Therefore, the description of the present specification is for illustrative purposes and does not have any limiting meaning to the present embodiment.

  The notification of information is not limited to the aspect / embodiment described in the present specification, and may be performed by other methods. For example, information notification includes physical layer signaling (for example, DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or a combination thereof. The RRC signaling may be referred to as an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

  Each aspect / embodiment described herein includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA. (Registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB (Ultra-WideBand), The present invention may be applied to a Bluetooth (registered trademark), a system using other appropriate systems, and / or a next generation system extended based on these systems.

  As long as there is no contradiction, the order of the processing procedures, sequences, flowcharts, and the like of each aspect / embodiment described in this specification may be changed. For example, the methods described herein present the elements of the various steps in an exemplary order and are not limited to the specific order presented.

  Information or the like can be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input / output may be performed via a plurality of network nodes.

  Input / output information and the like may be stored in a specific location (for example, a memory) or may be managed by a management table. Input / output information and the like can be overwritten, updated, or additionally written. The output information or the like may be deleted. The input information or the like may be transmitted to another device.

  The determination may be performed by a value represented by 1 bit (0 or 1), may be performed by a true / false value (Boolean: true or false), or may be performed by comparing numerical values (for example, a predetermined value) Comparison with the value).

  Each aspect / embodiment described in this specification may be used independently, may be used in combination, or may be switched according to execution. In addition, notification of predetermined information (for example, notification of being “X”) is not limited to explicitly performed, but is performed implicitly (for example, notification of the predetermined information is not performed). Also good.

  Software, whether it is called software, firmware, middleware, microcode, hardware description language, or other names, instructions, instruction sets, code, code segments, program codes, programs, subprograms, software modules , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. should be interpreted broadly.

  Also, software, instructions, etc. may be transmitted / received via a transmission medium. For example, software may use websites, servers, or other devices using wired technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or wireless technology such as infrared, wireless and microwave. When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission media.

  Information, signals, etc. described herein may be represented using any of a variety of different technologies. For example, data, commands, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these May be represented by a combination of

  Note that the terms described in this specification and / or terms necessary for understanding this specification may be replaced with terms having the same or similar meaning.

  As used herein, the terms “system” and “network” are used interchangeably.

  In addition, information, parameters, and the like described in this specification may be represented by absolute values, may be represented by relative values from a predetermined value, or may be represented by other corresponding information. . For example, the radio resource may be indicated by an index.

  The names used for the parameters described above are not limiting in any way. Further, mathematical formulas and the like that use these parameters may differ from those explicitly disclosed herein. Since various channels (eg, PUCCH, PDCCH, etc.) and information elements (eg, TPC) can be identified by any suitable name, the various names assigned to these various channels and information elements are However, it is not limited.

  The base station (eNB) of this embodiment can accommodate one or a plurality of cells (also called sectors). When the base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each smaller area can be divided into a base station subsystem (for example, an indoor small base station RRH: Remote). Communication service can also be provided by Radio Head). The term “cell” or “sector” refers to part or all of the coverage area of a base station and / or base station subsystem that provides communication services in this coverage. Further, the terms “base station”, “eNB”, “cell”, and “sector” may be used interchangeably herein. A base station may also be referred to in terms such as a fixed station, NodeB, access point, femto cell, small cell, and the like.

  A terminal (UE) is defined by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal , Wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate terminology.

  As used herein, the terms “determining” and “determining” may encompass a wide variety of actions. “Judgment” and “determination” are, for example, judgment, calculation, calculation, processing, derivation, investigating, looking up (eg, table , Searching in a database or another data structure), considering ascertaining as “determining”, “deciding”, and the like. In addition, “determination” and “determination” include receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (accessing) (e.g., accessing data in a memory) may be considered as "determined" or "determined". In addition, “determination” and “decision” means that “resolving”, “selecting”, “choosing”, “establishing”, and “comparing” are regarded as “determining” and “deciding”. May be included. In other words, “determination” and “determination” may include considering some operation as “determination” and “determination”.

  As used herein, the phrase “based on” does not mean “based only on,” unless expressly specified otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”

  These terms are similar to the term “comprising” as long as “include”, “including” and variations thereof are used herein or in the claims. It is intended to be comprehensive. Furthermore, the term “or” as used herein or in the claims is not intended to be an exclusive OR.

  In this specification, a plurality of devices are also included unless there is only one device that is clearly present in context or technically.

  10 ... UE (terminal), 20 ... eNB (base station), 20A ... processor, 20B ... memory, 20C ... storage, 20D ... communication module, 20E ... input device, 20F ... output device, 20G ... bus, 21 ... table, DESCRIPTION OF SYMBOLS 22 ... Reception part, 23 ... Acquisition part, 24 ... Determination part, 25 ... Control part, 30 ... MME (processing server), 40 ... SGW, 50 ... PGW, 60 ... HSS.

Claims (6)

RAN connection executed by a base station comprising a table storing parameter information for setting up a RAN connection with the terminal in association with information for selecting a slice to be allocated according to a service used by the terminal A control method,
A receiving step of receiving an attach request or a location registration information update request from the terminal;
An acquisition step of requesting and acquiring information for selecting a slice to be allocated according to the service used by the terminal when the attach request or the location registration information update request is received by the reception step. When,
A determining step of determining a RAN connection method with the terminal based on information for selecting the slice acquired by the acquiring step;
The parameter information corresponding to the information for selecting the slice is acquired from the table, and the parameter information is notified to the terminal, whereby the RAN is connected to the terminal by the RAN connection method determined in the determination step. Control steps to control,
A RAN connection control method comprising: In the control step, the base station
Make a new RAN connection while maintaining the previous RAN connection with the terminal, or
Disconnect the previous RAN connection with the terminal and perform a new RAN connection.
The connection control method according to claim 1. The parameter information is
Information on radio communication frequency bands available by the terminal, and
Priority information in the MAC layer of the wireless communication section used by the terminal,
The connection control method according to claim 1 or 2, comprising at least one of the following. The parameter information is
A preliminary parameter including at least one of delay time information acceptable by the terminal and information regarding whether or not to discard a packet;
The connection control method according to claim 3, further comprising: The parameter information is
Information on whether the terminal has a RAN connection between a cellular communication network and a non-cellular communication network;
The connection control method as described in any one of Claims 1-4 containing this. A table storing parameter information for setting a RAN connection with the terminal in association with information for selecting a slice to be allocated according to a service used by the terminal;
A receiving unit for receiving an attach request or a location registration information update request from the terminal;
An acquisition unit that requests and acquires information for selecting a slice to be allocated according to a service used by the terminal when the attachment unit or the location registration information update request is received by the reception unit. When,
A determination unit that determines a RAN connection method with the terminal based on information for selecting the slice acquired by the acquisition unit;
The parameter information corresponding to the information for selecting the slice is acquired from the table, and the parameter information is notified to the terminal, whereby the RAN connection method determined by the determination unit is used for RAN connection with the terminal. A control unit for controlling
A base station comprising:

Images