WO2018131453A1 - Ran connection control method and base station - Google Patents

Ran connection control method and base station Download PDF

Info

Publication number
WO2018131453A1
WO2018131453A1 PCT/JP2017/046398 JP2017046398W WO2018131453A1 WO 2018131453 A1 WO2018131453 A1 WO 2018131453A1 JP 2017046398 W JP2017046398 W JP 2017046398W WO 2018131453 A1 WO2018131453 A1 WO 2018131453A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal
ran connection
ran
slice
Prior art date
Application number
PCT/JP2017/046398
Other languages
French (fr)
Japanese (ja)
Inventor
優樹 勝間田
拓也 下城
滋 岩科
芳文 森広
雅純 清水
大輔 野島
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to JP2018561910A priority Critical patent/JP6967018B2/en
Publication of WO2018131453A1 publication Critical patent/WO2018131453A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • the present invention relates to a RAN connection control method and a base station.
  • Non-Patent Document 1 when an attach request is made from the terminal to the base station when the terminal is turned on, the base station uses the MME (Mobility Management Entity) in the core network. SME selects slices based on MME group identification information (MME Group Identifier (hereinafter referred to as “MMEGI”)) notified from the core network (specifically, MME selected according to MMEGI) A process of redirecting the terminal is performed.
  • MME Mobility Management Entity
  • 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.
  • RAN connection method a wireless communication connection method
  • the present invention has been made to solve the above-described problems, and an object of the present invention is to appropriately control the RAN connection method and improve QoE for each terminal user.
  • a RAN connection control method 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
  • 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 with the terminal based on information to select
  • a determination step for determining a connection 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 determined in the determination step is determined.
  • the base station 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.
  • 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.
  • the above-mentioned “information for selecting a slice” the above-mentioned MMEGI can be used.
  • DCN Dedicated Core Network
  • Identification information nodet-generation network proposed in 3GPP TR 23.799
  • So-called DCN-ID Service Type
  • DNN Domain Network Name
  • an embodiment of the present invention related to the above RAN connection control method can be regarded as an invention related 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 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.
  • 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 table by reporting 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.
  • the present invention it is possible to appropriately control the RAN connection method and improve QoE for each terminal user.
  • a communication system 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.
  • UE User Equipment
  • eNB eNodeB
  • MMEs mobility management entities
  • HSS home subscriber server
  • SGWs serving gateways
  • PGWs packet data network gateways
  • 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 a “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 with a PDN (Packet data network), and is a gateway device that performs IP address assignment, packet transfer to the SGW, and the like.
  • PDN Packet data network
  • the eNB 20 uses an MME Group Identifier (hereinafter referred to as parameter information for setting a RAN connection), which is an example of information for selecting a slice to be allocated according to the service used by the UE 10.
  • MME Group Identifier hereinafter referred to as parameter information for setting a 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
  • TAU request location registration information update
  • UE Usage type usage type information
  • an acquisition unit 23 that requests (here, MMEGI) to acquire from the core network
  • a determination unit 24 that determines a RAN connection method between the UE 10 and the eNB 20 based on the MMEGI acquired by the acquisition unit 23
  • a control unit 25 that obtains parameter information to be performed from the table 21 and notifies the UE 10 of the parameter information by performing RAN connection between the UE 10 and the eNB 20 by the RAN connection method determined by the determination unit 24.
  • FIG. 2 shows a data example of the table 21 held by the eNB 20.
  • 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.
  • the table 21 may further include delay time information acceptable by the terminal, information on whether or not to discard the packet, and spare parameters including information on a combination thereof. In this case, flexible priority control can be performed.
  • 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
  • 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.
  • 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.
  • the processor 20A controls the entire computer by operating an operating system, for example.
  • the processor 20A may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like.
  • CPU central processing unit
  • 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.
  • a program program that causes a computer to execute at least a part of the operations described in the above embodiments is used.
  • 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.
  • 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 disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, 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.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • the eNB when the eNB receives an attach request from the UE (step S1), the eNB forwards 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 above attach request, the default MME sends an authentication information request to the HSS to obtain UE authentication information (step S3), and an authentication information response including the UE usage type is sent as a response. Receive from HSS (step S4).
  • the default MME selects information (here, MMEGI) for selecting a slice to be allocated according to the received UE usage type (that is, a slice corresponding to the UE usage service registered in the HSS) (step MMEGI in this case).
  • MMEGI MMEGI
  • a reroute NAS request including the selected MMEGI and the attach message is transmitted to the eNB (step S6).
  • eNB can acquire MMEGI which should be selected according to UE usage type.
  • the eNB performs processing based on the MNSF (NAS Node Selection Function) of the existing sequence (for example, allocation of network resources for service to the UE) (step S7), and then executes the UE and the UE based on the acquired MMEGI.
  • 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).
  • 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.
  • 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.
  • the eNB sends an attach request and an MMEGI to the MME corresponding to the acquired MMEGI (that is, the MME corresponding to the slice allocated according to the UE usage type; described as “selected MME” in FIG. 4).
  • An initial UE message including the message is transmitted (step S12).
  • 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.
  • 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.
  • flexible control is possible by selectively holding or disconnecting the previous RAN connection.
  • 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
  • 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.
  • the eNB 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 above 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 the UE usage type as a response. An identification / context response is received from the old MME (step S24).
  • the default MME selects information (in this case, MMEGI) for selecting a slice to be allocated according to the received UE usage type (that is, a slice that should take over the usage service of the UE before movement) (step S25).
  • MMEGI MME select information
  • the reroute NAS request including the selected MMEGI and the TAU message is transmitted to the eNB (step S26).
  • eNB can acquire MMEGI which should be selected according to UE usage type.
  • the eNB performs processing based on the existing sequence MNSF (NAS Node Selection Function) (for example, allocation of network resources for service to the UE) (step S27), and then executes the UE and the UE based on the acquired MMEGI.
  • 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).
  • 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.
  • the eNB sends the TAU request and the MMEGI to the MME corresponding to the acquired MMEGI (that is, the MME corresponding to the slice allocated according to the UE usage type; described as “selected MME” in FIG. 5).
  • An initial UE message including the message is transmitted (step S32).
  • 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.
  • 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.
  • flexible control is possible by selectively holding or disconnecting the previous RAN connection.
  • the embodiment in which the present invention is applied to the network based on the standard proposed in 3GPP TS 23.401 has been described.
  • the present invention is, for example, the following proposed in 3GPP TR 23.799. It can also be applied to generational networks.
  • 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.
  • DCN Dedicated Core Network
  • DCN-ID Service Type
  • DNN Domain Network Name
  • 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)
  • the SGW 40 and the PGW 50 are CP-SM (Control Plane-Control). It becomes a core network including Session Management and User Plane.
  • radio resource allocation in FIG. 2 for example, a radio communication frequency band that can be used by the terminal
  • radio resource allocation in the RAN connection is illustrated.
  • An example of controlling the above has been described.
  • 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)).
  • LAN wireless local area network
  • LAN wireless local area network
  • Wi-Fi registered trademark
  • notification of information is not limited to the aspect / embodiment described in this specification, and may be performed by other methods.
  • notification of information 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 called 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 in this specification includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • SUPER 3G IMT-Advanced
  • 4G 5G
  • FRA Full Radio Access
  • W-CDMA Wideband
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access 2000
  • UMB User 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 another appropriate system, and / or a next generation system extended based on the system.
  • Information etc. 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.
  • the input / output information or 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).
  • notification of predetermined information is not limited to explicitly performed, but is performed implicitly (for example, notification of the predetermined information is not performed). Also good.
  • software, instructions, etc. may be transmitted / received via a transmission medium.
  • 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.
  • 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.
  • DSL digital subscriber line
  • wireless technology such as infrared, wireless and microwave.
  • system and “network” used in this specification are used interchangeably.
  • 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.
  • the radio resource may be indicated by an index.
  • 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). A 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 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.
  • determining may encompass a wide variety of actions. “Judgment” and “decision” 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.
  • 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”.
  • 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”.
  • 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.”

Abstract

A base station (eNB) provided with a table, in which parameter information for RAN connection setting is associated with MMEGIs being an example of information for selecting a slice to be allocated according to a service used by user equipment, and stored, receives an attach request (or a TAU request) from user equipment (UE) (S1), requests and acquires, from a core network, an MMEGI to be selected according to a UE Usage type (for example, mobility, service request quality, or the like of the user equipment) relating to the service use of the user equipment (S6), determines a RAN connection method between the user equipment and the base station (eNB) on the basis of the acquired MMEGI (S8), and performs control such that RAN connection with the user equipment is performed by the determined RAN connection method by acquiring parameter information associated with the MMEGI from the table and notifying the user equipment of the parameter information (S9-S12).

Description

ＲＡＮ接続制御方法および基地局RAN connection control method and base station
　本発明は、ＲＡＮ接続制御方法および基地局に関する。 The present invention relates to a RAN connection control method and a base station.
　近年、ネットワークにおけるサービス品質に関する指標として、ネットワーク上で提供されるサービスについて端末ユーザにより体感される品質を示すＱｏＥ（Quality　of　Experience）が重要視されている。そのため、第５世代（５Ｇ（5th　Generation））ネットワーク時代において端末ユーザ毎のＱｏＥを高いレベルに維持するためには、ネットワークインフラ上に論理的に生成される仮想ネットワークであるスライスを選択する際にコアネットワークに加え無線アクセス網（Radio　Access　Network（以下「ＲＡＮ」と称する））における品質も考慮したエンドツーエンド（end　to　end：E2E）の品質管理が重要となる。実際にコアネットワークにおいては遅延が発生することは殆ど無いため、端末ユーザ毎のＱｏＥを考慮してＲＡＮにおいて発生する遅延を抑える必要がある。 In recent years, QoE (Quality of Experience), which indicates the quality experienced by terminal users regarding services provided on the network, has been regarded as an important index for service quality in the network. Therefore, in order to maintain the QoE for each terminal user at a high level in the 5th generation (5G (5th Generation)) network era, when selecting a slice which is a virtual network logically generated on the network infrastructure. In addition to the core network, end-to-end (E2E) quality management that considers the quality of the 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.
　現在、非特許文献１にて提案されている規格では、例えば、端末の電源オン時などに端末から基地局へattach要求した場合等に、基地局は、コアネットワーク内のＭＭＥ（Mobility　Management　Entity）から通知されるＭＭＥグループ識別情報（MME　Group　Identifier（以下「ＭＭＥＧＩ」と称する））に基づいてスライス選択を行い、サービス要件を満たすコアネットワーク（具体的にはＭＭＥＧＩに応じて選択されるＭＭＥ）に上記端末をリダイレクトする処理を行う。 Currently, in the standard proposed in Non-Patent Document 1, for example, when an attach request is made from the terminal to the base station when the terminal is turned on, the base station uses the MME (Mobility Management Entity) in the core network. SME selects slices based on MME group identification information (MME Group Identifier (hereinafter referred to as “MMEGI”)) notified from the core network (specifically, MME selected according to MMEGI) 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 of the present invention is to appropriately control the RAN connection method and improve 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 with the terminal based on information to select A determination step for determining a connection 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 determined in the determination step is determined. And a control step of controlling to make a RAN connection with the terminal according to a connection method.
　上記の本発明の一実施形態に係るＲＡＮ接続制御方法によれば、基地局は、アタッチリクエスト又は位置登録情報更新リクエストを端末から受信した場合に、端末の利用サービスに応じて割り当てるべきスライスを選択するための情報を、コアネットワークに要求して取得し、取得された上記スライスを選択するための情報に基づいて端末とのＲＡＮ接続方法を決定し、そして、上記スライスを選択するための情報に対応するパラメータ情報をテーブルから取得し該パラメータ情報を端末に通知することで、上記決定されたＲＡＮ接続方法によって端末とＲＡＮ接続するよう制御する。これにより、コアネットワークから取得した上記スライスを選択するための情報に基づいて適切なＲＡＮ接続方法を決定するとともに、予め上記スライスを選択するための情報に対応付けて記憶されたパラメータ情報（即ち、端末と基地局とのＲＡＮ接続を設定するためのパラメータ情報）とコアネットワークから取得された上記スライスを選択するための情報とを用いて、上記端末にとって適切なパラメータ情報を取得し、該パラメータ情報を端末に通知することで上記適切なＲＡＮ接続方法によって端末とＲＡＮ接続するよう制御することができる。よって、ＲＡＮ接続方法を適切に制御し、端末ユーザ毎のＱｏＥ向上を図ることができる。なお、上記の「スライスを選択するための情報」としては、上述したＭＭＥＧＩを用いることができ、さらに、例えば３ＧＰＰ　ＴＲ　２３．７９９に提案された次世代ネットワークにおけるＤＣＮ（Dedicated　Core　Network）識別情報（いわゆるDCN-ID）、該DCN-IDに対応付けられるService　TypeおよびＤＮＮ（Domain　Network　Name）等を用いることができる。 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. As the above-mentioned “information for selecting a slice”, the above-mentioned MMEGI can be used. Further, 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.
　また、上記のＲＡＮ接続制御方法に係る本発明の一実施形態は、基地局に係る発明として捉えることもでき、以下のように記述できる。下記の基地局に係る発明も同様の作用・効果を奏する。 Also, an embodiment of the present invention related to the above RAN connection control method can be regarded as an invention related 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 table by reporting 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 example of a process when a location 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.
　［発明の実施形態に係る通信システムおよび各装置の構成の説明］
　図１に示すように本発明の一実施形態に係る通信システムは、端末（User　Equipment（以下「ＵＥ」ともいう））１０と、ＲＡＮにおける基地局に相当するｅＮｏｄｅＢ（以下「ｅＮＢ」という）２０と、複数のＭＭＥ（Mobility　Management　Entity）３０と、ＨＳＳ（Home　Subscriber　Server）６０と、複数のＳＧＷ（Serving　gateway）４０と、ＳＧＷ４０の上流側に位置する複数のＰＧＷ（Packet　data　network　gateway）５０と、を含んで構成されている。 [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.
　ＭＭＥ３０は、ネットワークに在圏するＵＥ１０の位置管理、認証制御、通信経路設定等の処理を行う装置であり、特許請求の範囲に記載された「処理サーバ」に対応する。ＨＳＳ６０は、端末ユーザのユーザ情報（加入者情報）を管理する装置である。ＳＧＷ４０は、ＬＴＥ（Long　Term　Evolution）を収容する在圏パケット交換機の機能を果たすゲートウェイ装置であり、ＵＥ１０により利用される通信サービスの要件に対応して一又は複数のＳＧＷ４０が設けられる。ＰＧＷ５０は、ＰＤＮ（Packet　data　network）との接合点であり、ＩＰアドレスの割当て、ＳＧＷへのパケット転送などを行うゲートウェイ装置である。 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 a “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 with a PDN (Packet data network), and is a gateway device that performs IP address assignment, packet transfer to the SGW, and the like.
　さて、本発明に関連する機能ブロックとして、ｅＮＢ２０は、ＲＡＮ接続を設定するためのパラメータ情報が、ＵＥ１０の利用サービスに応じて割り当てるべきスライスを選択するための情報の一例であるMME　Group　Identifier（以下「ＭＭＥＧＩ」という）に対応付けて記憶されたテーブル２１と、位置登録情報更新（Tracking　Area　Update）リクエスト（以下「ＴＡＵリクエスト」という）又はアタッチリクエストをＵＥ１０から受信する受信部２２と、受信部２２によりＴＡＵリクエスト又はアタッチリクエストが受信された場合に、ＵＥ１０のサービス利用に関する利用タイプ情報（以下「UE　Usage　type」という。例えばＵＥ１０の移動度、サービス要求品質などを含む））に応じてＵＥ１０に割り当てるべきスライスを選択するための情報（ここではＭＭＥＧＩ）を、コアネットワークに要求して取得する取得部２３と、取得部２３により取得されたＭＭＥＧＩに基づいてＵＥ１０とｅＮＢ２０間のＲＡＮ接続方法を決定する決定部２４と、ＭＭＥＧＩに対応するパラメータ情報をテーブル２１から取得し該パラメータ情報をＵＥ１０に通知することで、上記決定部２４により決定されたＲＡＮ接続方法によってＵＥ１０とｅＮＢ２０間でＲＡＮ接続するよう制御する制御部２５と、を備える。 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 setting a RAN connection), which is an example of information for selecting a slice to be allocated according to the service used by the UE 10. 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, allocation is made 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 slices Corresponding to MMEGI, an acquisition unit 23 that requests (here, MMEGI) to acquire from the core network, a determination unit 24 that determines a RAN connection method between the UE 10 and the eNB 20 based on the MMEGI acquired by the acquisition unit 23 A control unit 25 that obtains parameter information to be performed from the table 21 and notifies the UE 10 of the parameter information by performing RAN connection between the UE 10 and the eNB 20 by the RAN connection method determined by the determination unit 24. .
　図２には、ｅＮＢ２０が保持するテーブル２１のデータ例を示す。この図２に示すように、テーブル２１には、ＲＡＮ接続を設定するためのパラメータ情報として、例えば、端末により利用可能な無線通信周波数帯の情報、および端末により利用される無線通信区間のＭＡＣ層における優先度情報がＭＭＥＧＩに対応付けて記憶されている。このような多様なパラメータ情報を用いることで好適なＲＡＮ接続方法を選択することが可能となる。 FIG. 2 shows a data example of the table 21 held by the eNB 20. 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 acceptable by the terminal, information on whether or not to discard the packet, and spare parameters including information on a combination thereof. In this case, flexible priority control can be performed.
　ここで、図３を参照して、本発明の「基地局」に相当するｅＮＢ２０のハードウェア構成の一例について説明する。ｅＮＢ２０は、物理的には、プロセッサ２０Ａ、メモリ２０Ｂ、ストレージ２０Ｃ、通信モジュール２０Ｄ、入力装置２０Ｅ、出力装置２０Ｆ、バス２０Ｇなどを含むコンピュータ装置として構成されてもよい。ｅＮＢ２０の機能ブロック（構成部）は、ハードウェア及び／又はソフトウェアの任意の組み合わせによって実現される。また、各機能ブロックの実現手段は特に限定されない。すなわち、各機能ブロックは、物理的及び／又は論理的に結合した１つの装置により実現されてもよいし、有線及び／又は無線で相互にリンクした物理的及び／又は論理的に分離した２つ以上の装置により実現されてもよい。なお、以下で説明するハードウェア構成例は、ｅＮＢ２０に限らず、図１に示すＨＳＳ６０、ＰＧＷ５０、ＳＧＷ４０、ＭＭＥ３０、ＵＥ１０において採用してもよい。 Here, an example of a 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.
　プロセッサ２０Ａは、例えば、オペレーティングシステムを動作させてコンピュータ全体を制御する。プロセッサ２０Ａは、周辺装置とのインターフェース、制御装置、演算装置、レジスタなどを含む中央処理装置（ＣＰＵ：Central　Processing　Unit）で構成されてもよい。 The processor 20A controls the entire computer by operating an operating system, for example. The processor 20A may be configured by a central processing unit (CPU) including an interface with peripheral devices, 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.
　メモリ２０Ｂは、コンピュータ読み取り可能な記録媒体であり、例えば、ＲＯＭ（Read　Only　Memory）、ＥＰＲＯＭ（Erasable　Programmable　ＲＯＭ）、ＥＥＰＲＯＭ（Electrically　Erasable　Programmable　ＲＯＭ）、ＲＡＭ（Random　Access　Memory）などの少なくとも１つで構成されてもよい。メモリ２０Ｂは、レジスタ、キャッシュ、メインメモリ（主記憶装置）などと呼ばれてもよい。メモリ２０Ｂは、本発明の一実施の形態に係る無線通信方法を実施するために実行可能なプログラム（プログラムコード）、ソフトウェアモジュールなどを保存することができる。 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.
　ストレージ２０Ｃは、コンピュータ読み取り可能な記録媒体であり、例えば、ＣＤ－ＲＯＭ（Compact　Disc　ＲＯＭ）などの光ディスク、ハードディスクドライブ、フレキシブルディスク、光磁気ディスク(例えば、コンパクトディスク、デジタル多用途ディスク、Ｂｌｕ－ｒａｙ（登録商標）ディスク)、スマートカード、フラッシュメモリ(例えば、カード、スティック、キードライブ)、フロッピー（登録商標）ディスク、磁気ストリップなどの少なくとも１つで構成されてもよい。ストレージ２０Ｃは、補助記憶装置と呼ばれてもよい。上述の記憶媒体は、例えば、メモリ２０Ｂ及び／又はストレージ２０Ｃを含むデータベース、サーバその他の適切な媒体であってもよい。 The storage 20C is a computer-readable recording medium, such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, 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.
　入力装置２０Ｅは、外部からの入力を受け付ける入力デバイスである。出力装置２０Ｆは、外部への出力を実施する出力デバイス（例えば、ディスプレイ、スピーカー、LEDランプなど）である。なお、入力装置２０Ｅ及び出力装置２０Ｆは、一体となった構成（例えば、タッチパネル）であってもよい。 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).
　また、プロセッサ２０Ａ、メモリ２０Ｂなどの各装置は、情報を通信するためのバス２０Ｇで接続される。バス２０Ｇは、単一のバスで構成されてもよいし、装置間で異なるバスで構成されてもよい。 Further, 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.
　また、ｅＮＢ２０は、マイクロプロセッサ、デジタル信号プロセッサ（ＤＳＰ：Digital　Signal　Processor）、ＡＳＩＣ（Application　Specific　Integrated　Circuit）、ＰＬＤ（Programmable　Logic　Device）、ＦＰＧＡ（Field　Programmable　Gate　Array）などのハードウェアを含んで構成されてもよく、当該ハードウェアにより、各機能ブロックの一部又は全てが実現されてもよい。例えば、プロセッサ２０Ａは、これらのハードウェアの少なくとも１つで実装されてもよい。 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”.
　図４に示すように、ｅＮＢは、アタッチリクエストをＵＥから受信すると（ステップＳ１）、当該アタッチリクエストをデフォルトＭＭＥへ転送し（ステップＳ２）、３ＧＰＰに規定された既存シーケンス（ステップＳ３～Ｓ６）を経てＭＭＥＧＩを取得する。具体的に、デフォルトＭＭＥは、上記アタッチリクエストを受信した後、ＵＥの認証情報を得るためにauthentication　information　requestをＨＳＳに送り（ステップＳ３）、その応答として、UE　usage　typeを含んだauthentication　information　responseをＨＳＳから受信する（ステップＳ４）。そして、デフォルトＭＭＥは、受信したUE　usage　typeに応じて割り当てるべきスライス（即ち、ＨＳＳに登録されたＵＥの利用サービスに対応したスライス）を選択するための情報（ここではＭＭＥＧＩ）を選択し（ステップＳ５）、選択されたＭＭＥＧＩとアタッチメッセージとを含んだreroute　NAS　requestをｅＮＢへ送信する（ステップＳ６）。これにより、ｅＮＢは、UE　usage　typeに応じて選択されるべきＭＭＥＧＩを取得することができる。 As shown in FIG. 4, when the eNB receives an attach request from the UE (step S1), the eNB forwards 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 above attach request, the default MME sends an authentication information request to the HSS to obtain UE authentication information (step S3), and an authentication information response including the UE usage type is sent as a response. Receive from HSS (step S4). Then, the default MME selects information (here, MMEGI) for selecting a slice to be allocated according to the received UE usage type (that is, a slice corresponding to the UE usage service registered in the HSS) (step MMEGI in this case). S5) A reroute NAS request including the selected MMEGI and the attach message is transmitted to the eNB (step S6). Thereby, eNB can acquire MMEGI which should be selected according to UE usage type.
　以後、ｅＮＢは、既存シーケンスのＮＮＳＦ（NAS　Node　Selection　Function）に基づく処理（例えばＵＥへのサービスのためのネットワーク資源割当てなど）（ステップＳ７）の実行後、上記取得されたＭＭＥＧＩに基づいてＵＥとｅＮＢ間のＲＡＮ接続方法を決定し（ステップＳ８）、そして、上記取得されたＭＭＥＧＩに対応するパラメータ情報を図２のテーブル２１から取得して該パラメータ情報をＵＥに通知することで、上記決定されたＲＡＮ接続方法によってＵＥとｅＮＢ間でＲＡＮ接続するよう制御する（ステップＳ９～Ｓ１１）。 Thereafter, the eNB performs processing based on the MNSF (NAS Node Selection Function) of the existing sequence (for example, allocation of network resources for service to the UE) (step S7), and then executes the UE and the UE based on the acquired MMEGI. 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.
　さらに、ｅＮＢは、上記取得されたＭＭＥＧＩに対応するＭＭＥ（即ち、UE　usage　typeに応じて割り当てられるスライスに対応するＭＭＥ；図４では「選択されたＭＭＥ」と記載）に、アタッチリクエストとＭＭＥＧＩとを含んだinitial　UE　messageを送信する（ステップＳ１２）。以後、既存シーケンスと同様に、上記選択されたＭＭＥにより、ＵＥおよびｅＮＢは、ＵＥのサービス要件を満たす好適なコアネットワーク（図１のＳＧＷおよびＰＧＷ）へリダイレクトされる。 Further, the eNB sends an attach request and an MMEGI to the MME corresponding to the acquired MMEGI (that is, the MME corresponding to the slice allocated according to the UE usage type; described as “selected MME” in FIG. 4). An initial UE message including the message 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.
　（図５：ＵＥからＴＡＵリクエストが送信された場合の処理例）
　次に、図５を用いて、例えばＵＥが位置登録エリア（Tracking　Area）を跨ぐ移動をした事等をトリガーにしてＵＥからＴＡＵリクエストが送信された場合の処理例を説明する。図５の処理では、図１のＭＭＥ３０として、図４と同様のデフォルトＭＭＥと、移動前のＵＥへのサービス提供に関わっていた旧ＭＭＥと、後述の処理で選択されるＭＭＥＧＩに対応するＭＭＥ（選択されたＭＭＥ）とが関与するため、これらをそれぞれ「デフォルトＭＭＥ」、「旧ＭＭＥ」、「選択されたＭＭＥ」と称する。 (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.
　図５に示すように、ｅＮＢは、ＵＥからＴＡＵリクエストを受信すると（ステップＳ２１）、当該ＴＡＵリクエストをデフォルトＭＭＥへ転送し（ステップＳ２２）、３ＧＰＰに規定された既存シーケンス（ステップＳ２３～Ｓ２６）を経てＭＭＥＧＩを取得する。具体的に、デフォルトＭＭＥは、上記ＴＡＵリクエストを受信した後、旧ＭＭＥおよびＵＥの情報を得るためにidentification/context　requestを旧ＭＭＥに送り（ステップＳ２３）、その応答として、UE　usage　typeを含んだidentification/context　responseを旧ＭＭＥから受信する（ステップＳ２４）。そして、デフォルトＭＭＥは、受信したＵＥ　usage　typeに応じて割り当てるべきスライス（即ち、移動前のＵＥの利用サービスを引き継ぐべきスライス）を選択するための情報（ここではＭＭＥＧＩ）を選択し（ステップＳ２５）、選択されたＭＭＥＧＩとＴＡＵメッセージとを含んだreroute　NAS　requestをｅＮＢへ送信する（ステップＳ２６）。これにより、ｅＮＢは、UE　usage　typeに応じて選択されるべきＭＭＥＧＩを取得することができる。 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 above 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 the UE usage type as a response. An identification / context response is received from the old MME (step S24). Then, the default MME selects information (in this case, MMEGI) for selecting a slice to be allocated according to the received UE usage type (that is, a slice that should take over the usage service of the UE before movement) (step S25). The 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.
　以後、ｅＮＢは、既存シーケンスのＮＮＳＦ（NAS　Node　Selection　Function）に基づく処理（例えばＵＥへのサービスのためのネットワーク資源割当てなど）（ステップＳ２７）の実行後、上記取得されたＭＭＥＧＩに基づいてＵＥとｅＮＢ間のＲＡＮ接続方法を決定し（ステップＳ２８）、そして、上記取得されたＭＭＥＧＩに対応するパラメータ情報を図２のテーブル２１から取得して該パラメータ情報をＵＥに通知することで、上記決定されたＲＡＮ接続方法によってＵＥとｅＮＢ間でＲＡＮ接続するよう制御する（ステップＳ２９～Ｓ３１）。 After that, the eNB performs processing based on the existing sequence MNSF (NAS Node Selection Function) (for example, allocation of network resources for service to the UE) (step S27), and then executes the UE and the UE based on the acquired MMEGI. 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.
　さらに、ｅＮＢは、上記取得されたＭＭＥＧＩに対応するＭＭＥ（即ち、UE　usage　typeに応じて割り当てられるスライスに対応するＭＭＥ；図５では「選択されたＭＭＥ」と記載）に、ＴＡＵリクエストとＭＭＥＧＩとを含んだinitial　UE　messageを送信する（ステップＳ３２）。以後、既存シーケンスと同様に、上記選択されたＭＭＥにより、ＵＥおよびｅＮＢは、ＵＥのサービス要件を満たす好適なコアネットワーク（図１のＳＧＷおよびＰＧＷ）へリダイレクトされる。 Further, the eNB sends the TAU request and the MMEGI to the MME corresponding to the acquired MMEGI (that is, the MME corresponding to the slice allocated according to the UE usage type; described as “selected MME” in FIG. 5). An initial UE message including the message 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.
　また、上記実施形態では、３ＧＰＰ　ＴＳ　２３．４０１に提案された規格をベースとしたネットワークに本発明を適用した実施形態を説明したが、本発明は、例えば３ＧＰＰ　ＴＲ　２３．７９９に提案された次世代ネットワークにも適用可能である。具体的には、上記実施形態では、端末の利用サービスに応じて割り当てるべきスライスを選択するための情報の一例として、ＭＭＥＧＩを用いた処理を説明したが、本発明を次世代ネットワークに適用する場合、上記スライスを選択するための情報として、上記ＭＭＥＧＩに代わり、ＤＣＮ（Dedicated　Core　Network）識別情報（いわゆるDCN-ID）、該DCN-IDに対応付けられるService　TypeおよびＤＮＮ（Domain　Network　Name）等のいずれかを用いて、同様のＲＡＮ接続制御を実行することができ、同様の作用・効果を奏する。なお、次世代ネットワークの場合、例えば、図１の構成図におけるＭＭＥ３０は共通制御プレーン（Common　Control　Plane）となり、ＨＳＳ６０はＳＤＭ（Subscription　Data　Management）となり、ＳＧＷ４０およびＰＧＷ５０は、CP-SM（Control　Plane-Session　Management）およびユーザプレーン（User　Plane）を含んだコアネットワークとなる。 In the above embodiment, the embodiment in which the present invention is applied to the network based on the standard proposed in 3GPP TS 23.401 has been described. The present invention is, for example, the following proposed in 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 information for selecting the slice, DCN (Dedicated Core Network) identification information (so-called DCN-ID), Service Type and DNN (Domain Network Name) associated with the DCN-ID, etc. are used 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 the 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-Control). It becomes a core network including Session Management and User Plane.
　また、上記実施形態では、ＲＡＮ接続を設定するためのパラメータ情報として、図２に示す無線リソース割当てに関する情報（例えば端末により利用可能な無線通信周波数帯など）を例示し、ＲＡＮ接続における無線リソース割当てを制御する例を説明した。ただし、本発明は、ＲＡＮ接続における無線リソース割当ての制御に限定されるものではなく、ＲＡＮ接続を設定するためのパラメータ情報として、端末がセルラ通信網および非セルラ通信網のうちどちらにＲＡＮ接続するかに関する情報をテーブルに記憶しておき、当該情報を用いて端末がセルラ通信網および非セルラ通信網のうちどちらにＲＡＮ接続するかを制御してもよい。なお、非セルラ通信網とは、セルラ通信網以外の通信網（例えば無線ＬＡＮ（Local　Area　Network）等）を意味し、具体的には、Wi-Fi（登録商標）規格に基づく無線通信網、Massive　IoT（大規模IoT（Internet　of　Things））向けの無線規格であるLoRA（登録商標）規格およびSigfox（登録商標）規格などに基づく無線通信網が含まれる。 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)).
　以上、本実施形態について詳細に説明したが、当業者にとっては、本実施形態が本明細書中に説明した実施形態に限定されるものではないということは明らかである。本実施形態は、特許請求の範囲の記載により定まる本発明の趣旨及び範囲を逸脱することなく修正及び変更態様として実施することができる。したがって、本明細書の記載は、例示説明を目的とするものであり、本実施形態に対して何ら制限的な意味を有するものではない。 As mentioned above, although this embodiment was described in detail, it is clear for those skilled in the art that this embodiment is not limited to 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.
　情報の通知は、本明細書で説明した態様／実施形態に限られず、他の方法で行われてもよい。例えば、情報の通知は、物理レイヤシグナリング（例えば、ＤＣＩ（Downlink　Control　Information）、ＵＣＩ（Uplink　Control　Information））、上位レイヤシグナリング（例えば、ＲＲＣ（Radio　Resource　Control）シグナリング、ＭＡＣ（Medium　Access　Control）シグナリング、報知情報（ＭＩＢ（Master　Information　Block）、ＳＩＢ（System　Information　Block）））、その他の信号又はこれらの組み合わせによって実施されてもよい。また、ＲＲＣシグナリングは、ＲＲＣメッセージと呼ばれてもよく、例えば、ＲＲＣコネクションセットアップ（RRC　Connection　Setup）メッセージ、ＲＲＣコネクション再構成（RRC　Connection　Reconfiguration）メッセージなどであってもよい。 The notification of information is not limited to the aspect / embodiment described in this specification, and may be performed by other methods. For example, notification of information 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. Further, the RRC signaling may be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.
　本明細書で説明した各態様／実施形態は、ＬＴＥ（Long　Term　Evolution）、ＬＴＥ－Ａ（LTE-Advanced）、ＳＵＰＥＲ　３Ｇ、ＩＭＴ－Ａｄｖａｎｃｅｄ、４Ｇ、５Ｇ、ＦＲＡ（Future　Radio　Access）、Ｗ－ＣＤＭＡ（登録商標）、ＧＳＭ（登録商標）、ＣＤＭＡ２０００、ＵＭＢ（Ultra　Mobile　Broadband）、ＩＥＥＥ　８０２．１１（Ｗｉ－Ｆｉ）、ＩＥＥＥ　８０２．１６（ＷｉＭＡＸ）、ＩＥＥＥ　８０２．２０、ＵＷＢ（Ultra-WideBand）、Ｂｌｕｅｔｏｏｔｈ（登録商標）、その他の適切なシステムを利用するシステム及び／又はこれらに基づいて拡張された次世代システムに適用されてもよい。 Each aspect / embodiment described in this specification 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 another appropriate system, and / or a next generation system extended based on the system.
　本明細書で説明した各態様／実施形態の処理手順、シーケンス、フローチャートなどは、矛盾の無い限り、順序を入れ替えてもよい。例えば、本明細書で説明した方法については、例示的な順序で様々なステップの要素を提示しており、提示した特定の順序に限定されない。 The processing procedures, sequences, flowcharts and the like of each aspect / embodiment described in this specification may be switched in order as long as there is no contradiction. 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 etc. 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.
　入出力された情報等は特定の場所(例えば、メモリ)に保存されてもよいし、管理テーブルで管理してもよい。入出力される情報等は、上書き、更新、または追記され得る。出力された情報等は削除されてもよい。入力された情報等は他の装置へ送信されてもよい。 The input / output information or 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.
　判定は、１ビットで表される値（０か１か）によって行われてもよいし、真偽値（Boolean：trueまたはfalse）によって行われてもよいし、数値の比較（例えば、所定の値との比較）によって行われてもよい。 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 alone, 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, codes, 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.
　また、ソフトウェア、命令などは、伝送媒体を介して送受信されてもよい。例えば、ソフトウェアが、同軸ケーブル、光ファイバケーブル、ツイストペア及びデジタル加入者回線（ＤＳＬ）などの有線技術及び／又は赤外線、無線及びマイクロ波などの無線技術を使用してウェブサイト、サーバ、又は他のリモートソースから送信される場合、これらの有線技術及び／又は無線技術は、伝送媒体の定義内に含まれる。 Further, 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.
　本明細書で説明した情報、信号などは、様々な異なる技術のいずれかを使用して表されてもよい。例えば、上記の説明全体に渡って言及され得るデータ、命令、コマンド、情報、信号、ビット、シンボル、チップなどは、電圧、電流、電磁波、磁界若しくは磁性粒子、光場若しくは光子、又はこれらの任意の組み合わせによって表されてもよい。 The 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.
　本明細書で使用する「システム」および「ネットワーク」という用語は、互換的に使用される。 The terms “system” and “network” used in this specification 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 above parameters are not limited 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, etc.) can be identified by any suitable name, the various names assigned to these various channels and information elements are However, it is not limited.
　本実施形態の基地局（ｅＮＢ）は、１つまたは複数の（セクタとも呼ばれる）セルを収容することができる。基地局が複数のセルを収容する場合、基地局のカバレッジエリア全体は複数のより小さいエリアに区分でき、各々のより小さいエリアは、基地局サブシステム（例えば、屋内用の小型基地局ＲＲＨ：Ｒｅｍｏｔｅ　Ｒａｄｉｏ　Ｈｅａｄ）によって通信サービスを提供することもできる。「セル」または「セクタ」という用語は、このカバレッジにおいて通信サービスを行う基地局、および／または基地局サブシステムのカバレッジエリアの一部または全体を指す。さらに、「基地局」「ｅＮＢ」、「セル」、および「セクタ」という用語は、本明細書では互換的に使用され得る。基地局は、固定局（fixed　station）、ＮｏｄｅＢ、アクセスポイント（access　point）、フェムトセル、スモールセルなどの用語で呼ばれる場合もある。 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). A 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.
　本明細書で使用する「判断(determining)」、「決定(determining)」という用語は、多種多様な動作を包含する場合がある。「判断」、「決定」は、例えば、判定(judging)、計算(calculating)、算出(computing)、処理(processing)、導出(deriving)、調査(investigating)、探索(looking　up)（例えば、テーブル、データベースまたは別のデータ構造での探索）、確認(ascertaining)した事を「判断」「決定」したとみなす事などを含み得る。また、「判断」、「決定」は、受信(receiving)（例えば、情報を受信すること）、送信(transmitting)(例えば、情報を送信すること)、入力(input)、出力(output)、アクセス(accessing)（例えば、メモリ中のデータにアクセスすること）した事を「判断」「決定」したとみなす事などを含み得る。また、「判断」、「決定」は、解決(resolving)、選択(selecting)、選定(choosing)、確立(establishing)、比較(comparing)などした事を「判断」「決定」したとみなす事を含み得る。つまり、「判断」「決定」は、何らかの動作を「判断」「決定」したとみなす事を含み得る。 As used herein, the terms “determining” and “determining” may encompass a wide variety of actions. “Judgment” and “decision” 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.”
　「含む（include）」、「含んでいる（including）」、およびそれらの変形が、本明細書あるいは特許請求の範囲で使用されている限り、これら用語は、用語「備える(comprising)」と同様に、包括的であることが意図される。さらに、本明細書あるいは特許請求の範囲において使用されている用語「または（or）」は、排他的論理和ではないことが意図される。 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.
　本明細書において、文脈または技術的に明らかに1つのみしか存在しない装置である場合以外は、複数の装置をも含むものとする。 In this specification, unless there is only one device that is clearly present in context or technically, a plurality of devices are also included.
　１０…ＵＥ（端末）、２０…ｅＮＢ（基地局）、２０Ａ…プロセッサ、２０Ｂ…メモリ、２０Ｃ…ストレージ、２０Ｄ…通信モジュール、２０Ｅ…入力装置、２０Ｆ…出力装置、２０Ｇ…バス、２１…テーブル、２２…受信部、２３…取得部、２４…決定部、２５…制御部、３０…ＭＭＥ（処理サーバ）、４０…ＳＧＷ、５０…ＰＧＷ、６０…ＨＳＳ。 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)

  1. 　端末の利用サービスに応じて割り当てるべきスライスを選択するための情報に対応付けて、前記端末とのＲＡＮ接続を設定するためのパラメータ情報を記憶したテーブル、を備える基地局、によって実行されるＲＡＮ接続制御方法であって、
    　アタッチリクエスト又は位置登録情報更新リクエストを前記端末から受信する受信ステップと、
    　前記受信ステップにより前記アタッチリクエスト又は前記位置登録情報更新リクエストが受信された場合に、前記端末の利用サービスに応じて割り当てるべきスライスを選択するための情報を、コアネットワークに要求して取得する取得ステップと、
    　前記取得ステップにより取得された前記スライスを選択するための情報に基づいて前記端末とのＲＡＮ接続方法を決定する決定ステップと、
    　前記スライスを選択するための情報に対応する前記パラメータ情報を前記テーブルから取得し該パラメータ情報を前記端末に通知することで、前記決定ステップにより決定された前記ＲＡＮ接続方法によって前記端末とＲＡＮ接続するよう制御する制御ステップと、
    　を備えるＲＡＮ接続制御方法。     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. A control step for controlling
    A RAN connection control method comprising:
  2. 　前記制御ステップにおいて、前記基地局は、
    前記端末との従前のＲＡＮ接続を保持したまま新たなＲＡＮ接続を行う、又は、
    前記端末との従前のＲＡＮ接続を切断した上で新たなＲＡＮ接続を行う、
    　請求項１に記載の接続制御方法。     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.
  3. 　前記パラメータ情報は、
    　前記端末により利用可能な無線通信周波数帯の情報、および、
    　前記端末により利用される無線通信区間のＭＡＣ層における優先度情報、
    　の少なくとも１つを含む、請求項１又は２に記載の接続制御方法。     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.
  4. 　前記パラメータ情報は、
    　前記端末により許容可能な遅延時間情報およびパケット破棄の可否に係る情報の少なくとも１つを含む予備パラメータ、
    　をさらに含む、請求項３に記載の接続制御方法。     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:
  5. 　前記パラメータ情報は、
    　前記端末がセルラ通信網および非セルラ通信網のうちどちらにＲＡＮ接続するかに関する情報、
    　を含む、請求項１～４の何れか一項に記載の接続制御方法。     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 according to any one of claims 1 to 4, further comprising:
  6. 　端末の利用サービスに応じて割り当てるべきスライスを選択するための情報に対応付けて、前記端末とのＲＡＮ接続を設定するためのパラメータ情報を記憶したテーブルと、
    　アタッチリクエスト又は位置登録情報更新リクエストを前記端末から受信する受信部と、
    　前記受信部により前記アタッチリクエスト又は前記位置登録情報更新リクエストが受信された場合に、前記端末の利用サービスに応じて割り当てるべきスライスを選択するための情報を、コアネットワークに要求して取得する取得部と、
    　前記取得部により取得された前記スライスを選択するための情報に基づいて前記端末とのＲＡＮ接続方法を決定する決定部と、
    　前記スライスを選択するための情報に対応する前記パラメータ情報を前記テーブルから取得し該パラメータ情報を前記端末に通知することで、前記決定部により決定された前記ＲＡＮ接続方法によって前記端末とＲＡＮ接続するよう制御する制御部と、
    　を備える基地局。     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:
PCT/JP2017/046398 2017-01-10 2017-12-25 Ran connection control method and base station WO2018131453A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2018561910A JP6967018B2 (en) 2017-01-10 2017-12-25 RAN connection control method and base station

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017001726 2017-01-10
JP2017-001726 2017-01-10

Publications (1)

Publication Number Publication Date
WO2018131453A1 true WO2018131453A1 (en) 2018-07-19

Family

ID=62839532

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2017/046398 WO2018131453A1 (en) 2017-01-10 2017-12-25 Ran connection control method and base station

Country Status (2)

Country Link
JP (1) JP6967018B2 (en)
WO (1) WO2018131453A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114726729A (en) * 2022-04-06 2022-07-08 北京邮电大学 Admission control method and system of wireless access network facing network slice

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111510979B (en) * 2014-05-08 2022-09-20 交互数字专利控股公司 Method for redirecting a UE to a dedicated core network node and mobility management entity MME

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Pro ject, General Packet Radio Service(GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access", 3GPP TS 23401, VOL. 13.9.0 (2016-12), 16 December 2016 (2016-12-16), pages 1;110 - 112;302-305, XP055514887 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114726729A (en) * 2022-04-06 2022-07-08 北京邮电大学 Admission control method and system of wireless access network facing network slice
CN114726729B (en) * 2022-04-06 2023-08-29 北京邮电大学 Admission control method and system of wireless access network facing network slicing

Also Published As

Publication number Publication date
JP6967018B2 (en) 2021-11-17
JPWO2018131453A1 (en) 2019-11-07

Similar Documents

Publication Publication Date Title
US8917662B2 (en) Server for control plane at mobile communication network and method for controlling establishment of connection thereof
WO2020145300A1 (en) User device, network node, and communication system
JP7204403B2 (en) network node
WO2018207775A1 (en) Network device and wireless communication method
WO2019037500A1 (en) Method and apparatus for selecting radio access network device
WO2017141810A1 (en) Transmission device selection method, gateway selection method, and communication system
JP6768116B2 (en) Communication control device selection method and communication system
EP2800448B1 (en) Method and device for achieving multi-cell service on base station equipment
WO2020059149A1 (en) Network node
JP7018884B2 (en) Communication method
JP2020053719A (en) User device and network node
EP3911022B1 (en) Network node, and user device
WO2018131453A1 (en) Ran connection control method and base station
EP3522674B1 (en) Communication control methods and communication systems
WO2022091188A1 (en) Network node and communication method
JP2018170713A (en) Communication terminal
JP2020194990A (en) Node group and migration method
JP7345565B2 (en) Communication device and communication method
WO2022097290A1 (en) Terminal and communication system
WO2018061924A1 (en) Communication control method and communication system
WO2022029957A1 (en) Terminal, network node, and communication method
WO2018173567A1 (en) Node and migration method
WO2020144856A1 (en) Communication management device and data management device
JP2024023414A (en) Terminal and communication method
CN116762376A (en) Network node and communication method

Legal Events

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

Ref document number: 17891387

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018561910

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17891387

Country of ref document: EP

Kind code of ref document: A1