Technical field
[0001]
The present disclosure is the core node, base station, radio terminal, a communication method, a radio resource allocation method, the base station selection method, and a program, core node, particularly the allocation of radio resources, base station, radio terminal, a communication method, a radio resource allocation The method, base station selection method, and a program.
BACKGROUND
[0002]
　In recent years, study on IoT (Internet Of Things) service has been promoted. The IoT services, without user terminal to perform autonomously communication (hereinafter referred to as IoT terminal) is used numerous. Thus, in order to provide IoT services using a number of IoT terminal in a network communication carrier or the like is managed, it is desirable to efficiently accommodate many IoT terminal.
[0003]
　Non-Patent Document 1 11 pages, method of managing radio resources allocated to the terminal is described. Specifically, the radio resource group having a plurality of radio resources are divided into a plurality of RAN (Radio Access Network) Slice, it is described that assigns each of the RAN Slice to a particular service. In other words, the radio terminal used for a particular service is allocated radio resources included in the RAN Slice predetermined. Thus, by assigning the RAN Slice for each service, it is possible to prevent the case where the wireless terminal for use in a particular service has increased, not the radio resource is allocated to other services.
CITATION
Non-patent literature
[0004]
非特許文献1 : Vision on 5G Radio Access Technologies, Huawei Technologies, 3GPP RAN workshop on 5G, Sept.17-18, 2015, Phoenix, USA, RWS-150006
Summary of the Invention
Problems that the Invention is to Solve
[0005]
　However, Non-Patent Document 1 has been described to be managed by dividing a radio resource group to a plurality of RAN Slice, it does not describe or assign radio resources to how radio terminal . In other words, the radio terminal used for a particular service, the allocation method of the radio resource is not established. Allocation Method of radio resources is a method of allocating radio resources are allocated RAN Slice for a particular service to a wireless terminal. Therefore, the radio resources of the RAN Slice that divided and managed, it is not possible to allocate the appropriate radio terminal.
[0006]
　The purpose of the present disclosure, the radio resource RAN Slice assigned to each service, the core node may be assigned properly to the wireless terminal using the service, the base station, a wireless terminal, a communication method, a radio resource allocation method, base station selecting method, and to provide a program.
Means for Solving the Problems
[0007]
　Core node according to the first aspect of the present disclosure manages a determining unit for determining a radio resource to be allocated in accordance with the service provided to the wireless terminal, a plurality of radio resources, each RAN Slice associated with the service base to the station, in which and a communication unit for transmitting the resource identification information indicating the radio resources determined in said determining unit.
[0008]
　The base station according to the second aspect of the present disclosure, a plurality of radio resources, a management unit which manages each RAN Slice associated with the service, transmitted from the core node, depending on the service provided to the wireless terminal a communication unit that receives the resource identification information indicating a radio resource to be allocated, and a resource allocator for a radio resource allocated to the wireless terminal shown in the resource identification information is intended.
[0009]
　Wireless terminal according to a third aspect of the present disclosure includes a receiving portion in which a plurality of base station receives a respective broadcast information to be transmitted, from among said plurality of base stations, RAN providing service to which the host terminal to use a determining unit that determines to connect the base station that has transmitted the broadcast information including a RAN Slice identification information indicating the Slice, in which comprises a.
[0010]
　Communication method according to the fourth terminal of the present disclosure determines the radio resources to be allocated depending on the service provided to the wireless terminal, a plurality of radio resources, the base station which manages each RAN Slice associated with the service , and transmits the resource identification information indicating the determined radio resource.
[0011]
　Fifth radio resource allocating method according to an aspect of the present disclosure, a plurality of radio resources, manage each RAN Slice associated with the service, transmitted from the core node allocates depending on the service to be provided to the wireless terminal receiving the resource identification information indicating the radio resource, it is intended to allocate a radio resource indicated in the resource identification information to the wireless terminal.
[0012]
　Base station selection method according to a sixth aspect of the present disclosure is to receive a respective broadcast information in which a plurality of base stations transmit, from the plurality of base stations, indicating the RAN Slice to provide Use service RAN It decides to connect the Slice identification information the base station that has transmitted the broadcast information including, but.
[0013]
　Program according to a seventh aspect of the present disclosure determines the radio resources to be allocated depending on the service provided to the wireless terminal, a plurality of radio resources, the base station which manages each RAN Slice associated with the service, it is intended to execute on a computer that transmits a resource identification information indicating the determined radio resource.
Effect of the invention
[0014]
　The present disclosure, the radio resource RAN Slice assigned to each service, the core node can be properly assigned to the radio terminal using the service, the base station, a wireless terminal, a communication method, a radio resource allocation method, the base station method selection, and it can provide a program.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015]
FIG. 1 is a configuration diagram of a communication system in the first embodiment.
FIG. 2 is a configuration diagram of a communication system according to the second embodiment.
3 is a block diagram of a UE according to the second embodiment.
4 is a configuration diagram of a radio resource according eNodeB managed to the second embodiment.
5 is a diagram showing the information managed in each node device according to the second embodiment.
6 is a diagram showing the flow of the Attach procedure according to the second embodiment.
7 is a diagram showing the flow of the Attach procedure according to the second embodiment.
8 is a diagram illustrating a UE a triggered flow Service Request procedure according to the second embodiment.
9 is a diagram illustrating a UE a triggered flow Service Request procedure according to the second embodiment.
10 is a diagram showing the flow of the Attach procedure according to the third embodiment.
11 is a diagram illustrating a UE a triggered flow Service Request procedure according to the third embodiment.
12 is a configuration diagram of a communication system according to the fourth embodiment.
13 is a diagram showing the flow of Combined GPRS / IMSI Attach Procedure according to the fourth embodiment.
14 is a diagram illustrating a flow of PDP Context Activation Procedure for Iu mode according to the fourth embodiment.
15 is a diagram showing a flow of PDP Context Activation Procedure for Iu mode according to the fourth embodiment.
16 is a diagram showing the flow of MS Initiated Service Request Procedure using GN / Gp according to the fourth embodiment.
17 is a diagram showing the flow of MS Initiated Service Request Procedure using GN / Gp according to the fourth embodiment.
18 is a diagram illustrating a flow of PDP Context Activation Procedure for Iu mode according to the fifth embodiment.
19 is a diagram showing the flow of MS Initiated Service Request Procedure using GN / Gp according to the fifth embodiment.
FIG. 20 is a block diagram of a base station according to each embodiment.
21 is a configuration diagram of a radio terminal according to each embodiment.
FIG. 22 is a configuration diagram of the core node according to each embodiment.
DESCRIPTION OF THE INVENTION
[0016]
　(Embodiment 1)
　Hereinafter, with reference to the drawings will be described embodiments of the present disclosure. Configuration Example of the present disclosure a communication system according to a first embodiment of will be described with reference to FIG. Figure 1 is a core node 10, base station 20 and, has a radio terminal 30. Core node 10, base station 20 and, the wireless terminal 30 may be a computer device processor operates by executing a program stored in the memory.
[0017]
　Core node 10 may be a 3GPP MME that in (3rd Generation Partnership Project) is defined as a node that performs the session management and mobility management (Mobility Management Entity) or SGSN (Serving General Packet Radio Service Support Node) and the like. The base station 20 may be a eNodeB which is defined in 3GPP (evolved Node B). eNodeB is a base station that supports LTE (Long Term Evolution) as a wireless communication system. Further, the base station 20 may be replaced with a RNC (Radio Network Controller) and NodeB which is defined as a device for controlling the base station in 3GPP.
[0018]
　Wireless terminal 30, a mobile phone, a smart phone terminal, or may be a tablet-type terminal or the like. Or, the radio terminal 30, IoT terminal, MTC (Machine Type Communication) terminal, or it may be an M2M (Machine to Machine) terminal or the like.
[0019]
　Next, a configuration example of the core node 10. Core node 10 includes a communication unit 12 and the determining unit 14. Components comprising the core node 10, such as the communication unit 12 and the determining unit 14, the processor may be a software or module processing is performed by executing a program stored in the memory. Or, the components constituting the core node 10 can be a hardware such as a circuit or chip. The communication unit 12 includes a transmission unit (Transmitter) and receiver (Receiver).
[0020]
　Determining unit 14 uses the service information indicating a service provided to the radio terminal 30 determines a radio resource to be allocated to the radio terminal 30. Radio resources, for example, be a resource that is managed at the base station 20. Radio resource may be a resource that is determined using at least one of frequency and time.
[0021]
　The services provided to the wireless terminal 30, e.g., voice service that provides a voice call, image data or data service for transmitting the text data and the like, or even broadcasting services, etc. for distributing simultaneously data good. Or services provided to the wireless terminal 30 may be an IoT service. IoT service, for example, may be a service or automatic operation services, etc. using a smart meter. Service shown as a service to be provided to the radio terminal 30 is not limited to the service indicated above, to the radio terminal 30 may be provided various services. Service information is information for identifying a service provided to the wireless terminal 30.
[0022]
　Communication unit 12, to the base station 20 which manages by dividing a radio resource group having a plurality of radio resources into a plurality of RAN Slice, transmits a resource identification information indicating the radio resource determined in the determination section 14. Individual RAN Slice has a portion of the radio resources included in the radio resource groups. Individual RAN Slice has at least one radio resource. One of radio resources, for example, be a resource identified using a specific frequency band and a particular time period. RAN Slice may be paraphrased to have an area that combines multiple radio resources. Further, RAN Slice, among the radio resources set by the base station 20 manages, it may be paraphrased as having some of the radio resource groups. RAN Slice is associated with services provided to the wireless terminal. That, RAN Slice has at least one radio resource allocated to the wireless terminal using a specific service.
[0023]
　Resource identification information is information identifying the radio resources by the base station 20 manages, information identifying at least one radio resource. The communication unit 12 transmits the resource identification information indicating the radio resource included in the RAN Slice associated with services provided to the wireless terminal 30 to the base station 20.
[0024]
　Next, a configuration example of the base station 20. The base station 20 includes a communication unit 22, the management unit 24, and has a resource assignment unit 26. Components comprising the communication unit 22, the management unit 24, and the base station 20, such as resource assignment unit 26 is a software or module process is executed by the processor executing the program stored in the memory it may be. Or, the components constituting the base station 20 may be hardware such as a circuit or chip. The communication unit 22 includes a transmission unit (Transmitter) and receiver (Receiver).
[0025]
　Management unit 24 manages by dividing a radio resource group having a plurality of radio resources into a plurality of RAN Slice. Communication unit 22, is transmitted from the core node 10, receives the resource identification information indicating a radio resource to be allocated to the radio terminal 30. Resource identification information indicates the radio resource included in the RAN Slice associated with services provided to the wireless terminal 30.
[0026]
　Resource allocation unit 26 allocates the radio resource indicated in the resource identification information to the wireless terminal 30.
[0027]
　As described above, by using the communication system of FIG. 1, the core node 10, to the base station 20 which manages by dividing a radio resource group to a plurality of RAN Slice, a radio resource to be allocated to the radio terminal 30 It may send a resource identification information indicating. Thus, the base station 20 can allocate the radio resources designated by the core node 10 to the radio terminal 30. Core node 10, based on the service the radio terminal 30 is utilized, it is possible to determine the radio resource to be allocated to the radio terminal 30. Therefore, the base station 20 can be assigned to the appropriate radio terminal 30 a radio resource included in the RAN Slice the wireless terminal 30 is associated with the service to be used.
[0028]
　(Second Embodiment)
　Subsequently, configuration of the present disclosure exemplary communication system according to a second embodiment of the will be described with reference to FIG. Communication system of FIG. 2 is a communication system supporting LTE as a wireless communication scheme, a defined communication system as EPS (Evolved Packet System) in 3GPP. Incidentally, FIG. 2 is based on the diagram of TS 23.401 V 13.5.0 Figure 4.2.1-1.
[0029]
　Communication system of Figure 2, UE (User Equipment) 40, E-UTRAN (Evolved-Universal Mobile Telecommunications System Terrestrial Radio Access Network) 41, MME42, HSS (Home Subscriber Server) 43, SGSN44, SGW (Serving Gateway) 45, PGW (Packet Data Network Gateway) 46, PCRF (Policy and Charging Rules Function) entity 47 (hereinafter referred to as PCRF47), UTRAN48, GERAN (GSM (registered trademark) (Global System for Mobile communications) EDGE (Enhanced Data Rates for Global Evolution) Radio Access Network) has 49, Operator's IP Services50.
[0030]
　UE40 is a term used as a generic term for a wireless terminal in 3GPP. The UE, for example, may be replaced with MS (Mobile Station). E-UTRAN41 is a RAN LTE is used as a radio access system (Radio Access Network). UTRAN48 is a RAN using a 3G radio system as a radio access system. GERAN49 is a RAN using a 2G radio system as a radio access system.
[0031]
　MME42 and SGSN44 are nodes that perform mobility management and session management concerning UE 40. HSS43 is a node that manages subscriber information about the UE40. Subscriber information, including information about the services UE40 to use. SGW45 and PGW46 is a node for relaying data transmitted between the UE40 and Operator's IP Services50. Operator's IP Services50, for example, the server device operators such as to provide a service to UE40 managed, or may be a server device group and the like. PCRF47 is a node that manages the policy and charging rules and the like.
[0032]
　Between UE40 and the E-UTRAN41 is, LTE-Uu reference points are determined. Between the E-UTRAN41 and MME42 has defined the S1-MME reference point. Between MME42 and HSS43 is, S6 reference point is defined. Between MME42 and SGSN44 is, S3 reference point is defined. Between the E-UTRAN41 and SGW45 is determined that S1-U reference point. Between MME42 and SGW45 is, S11 reference point is defined. Between SGSN44 and SGW45 is, S4 reference point is defined. Between SGW45 and UTRAN48 is, S12 reference point is defined. Between SGW45 and PGW46 is, S5 / S8 reference point is defined. Between PGW46 and PCRF47 is, Gx reference point is defined. Between the PGW46 and the Operator's IP Services50 is, SGi reference points have been established. Between the PCRF47 and the Operator's IP Services50 is, Rx reference point is defined. Between MME42 and other MME is, S1-10 reference point is defined.
[0033]
　Subsequently, with reference to FIG. 3, illustrating an example of the configuration of UE 40. UE40 includes a communication unit 71, RAN Slice availability determining unit 72 and the destination RAN Slice selection unit 73. Components comprising the UE40, the processor may be a software or module processing is performed by executing a program stored in the memory. Or, the components constituting the UE40 may be hardware such as a circuit or chip.
[0034]
　The communication unit 71 performs wireless communication using the eNodeB and LTE included in E-UTRAN41. The communication unit 71 receives the broadcast information transmitted from the eNodeB. The communication unit 71 may receive broadcast information from a plurality of eNodeB. Broadcast information is transmitted, for example, by using a BCCH (Broadcast Control Channel). The broadcast information includes at least one RAN Slice ID. RAN Slice ID is information for identifying a RAN Slice the eNodeB managed. Further, RAN Slice is a wireless resource that is used to provide a particular service. That, UE 40 by receiving broadcast information, can eNodeB to recognize the possible services provided. The communication unit 71 outputs the RAN Slice ID included in the broadcast information to the RAN Slice availability determining unit 72.
[0035]
　RAN Slice availability determining unit 72, the RAN Slice ID output from the communication unit 71, determines whether the RAN Slice associated with the service that UE40 is utilized there. RAN Slice availability determining unit 72, and held in advance at least one RAN Slice ID indicating the RAN Slice associated with the service that UE40 is utilized. RAN Slice availability determining unit 72 determines in the output from the communication unit 71 RAN Slice ID, whether it contains a RAN Slice ID held in advance. RAN Slice availability determining unit 72, from among the outputted RAN Slice ID from the communication unit 71, and outputs the RAN Slice ID that matches the RAN Slice ID stored in advance to the destination RAN Slice selection unit 73.
[0036]
　Destination RAN Slice selection unit 73, when receiving the RAN Slice availability determining unit 72 of a plurality of RAN Slice ID, based on a predefined policy, selects a RAN Slice utilized. For example, the destination RAN Slice selection unit 73 may select a RAN Slice ID transmitted wave strength from strongest eNodeB. Or, the destination RAN Slice selection unit 73 is determined in advance a priority to each RAN Slice ID, may select the highest priority RAN Slice ID. Destination RAN Slice selection unit 73 outputs the selected RAN Slice ID to the communication unit 71. Or, the destination RAN Slice selection unit 73 may select a RAN Slice ID for a particular service using preferentially. Particular service, for example, IoT service or an automatic operation services.
[0037]
　The communication unit 71 performs the connection processing between the eNodeB with RAN Slice ID outputted from the connected RAN Slice selection unit 73.
[0038]
　Then, according to the second embodiment of the present disclosure with reference to FIG. 4, illustrating an example of the configuration of the wireless resources to be managed in eNodeB included in the E-UTRAN41. In FIG. 4, eNodeB indicates that managing radio resources group including a plurality of radio resources. Further, in FIG. 4, eNodeB have shown that they are managed by dividing the radio resource groups on the RAN Slice #A and RAN Slice #B. Further, in FIG. 4, RAN Slice #A have shown that it is composed of a plurality of radio resources group assigned to a particular group. A specific group, for example, be a group that uses the services associated with RAN Slice #A. The specific group may include a plurality of UE using the service associated with the RAN Slice #A. For example, RAN Slice #A may be RAN Slice for automatic operation. Further, a specific group may be an automatic operation service companies to provide. UE, the radio resource included in the radio resource groups are allocated to the group which the own apparatus belongs is assigned. Radio resource allocated to the UE, for example, is identified by the Resource ID.
[0039]
　Subsequently, with reference to FIG. 5, UE40, eNodeB, MME42, HSS43, and information included in the information management apparatus. Information management apparatus is an apparatus different from the HSS43, is a device that manages subscriber information. In FIG. 5, it is shown as different devices and HSS43 and information management system, may be the same device as HSS43 the information management apparatus. In other words, it may have a function of HSS43 the information management apparatus.
[0040]
　UE40 includes a IMSI (Internal Mobile Subscriber Identity) and RAN Slice ID. IMSI is information for identifying the UE. RAN Slice ID is information indicating a RAN Slice associated with the service that UE40 is utilized.
[0041]
　eNodeB manages in association with RAN Slice ID and Resource ID. RAN Slice ID is information for identifying a RAN Slice the eNodeB is managing. Resource ID is information identifying the radio resources allocated to UE 40. Resource ID is information that is uniquely identified within the eNodeB. And one RAN Slice ID, is associated with a plurality of Resource ID. Further, eNodeB, when managing a plurality of RAN Slice, having a plurality of RAN Slice ID.
[0042]
　HSS43 manages in association with the IMSI and UE the Usage type. UE the Usage type is information for identifying a service or group to which the UE belongs UE utilizes identified by IMSI. HSS43 manages the IMSI and UE the Usage type for a plurality of UE.
[0043]
　Information management apparatus manages in association with the Service ID and the UE the Usage type. Service ID is information for identifying a group to which services and UE the UE to use belongs. Service ID is information that is uniquely identified in the communication system. Information management apparatus manages the Service ID and UE the Usage type for a plurality of UE. If HSS43 the information management apparatus and is the same device, HSS43 includes IMSI, the UE the Usage type, manages in association with the Service ID. Service the UE to use is specified using the Service ID. Also, Service ID is specified using the UE the Usage type. Service ID may be identified using the subscriber information other than the UE the Usage type.
[0044]
　MME42 manages in association with the Service ID and Resource ID. That, MME42 can using Service ID, identifies the Resource ID to be assigned to the UE at eNodeB.
[0045]
　In FIG. 5, eNodeB is, while managing the radio resources by using the Resource ID that is uniquely identified within the eNodeB, by managing the radio resources by using the Service ID that is uniquely identified in the communication system it may be. In this case, MME42 does not need to manage the Service ID and the Resource ID, using the Service ID, it is possible to instruct the radio resources to be allocated to the UE to eNodeB.
[0046]
　Subsequently, the flow of Attach procedure according to the second embodiment of the present disclosure will be described with reference to FIG. 6, in the communication system shown in FIG. 2 shows a flow of processing when the Attach procedure is successfully completed. Attach procedure shown in Figure 6, TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: are based on the Attach procedure. In Attach procedure of FIG. 6, TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: For Attach procedure and the same processing will not be described in detail.
[0047]
　Further, UE 6 corresponds to UE40 in Figure 2, eNodeB of FIG. 6 corresponds to eNodeB included in the E-UTRAN41 in FIG. new new MME in FIG. 6 corresponds to MME42 in FIG. Old MME / SGSN in FIG. 6, UE 40 is a MME / SGSN that allocated to the previous Attach. In the Attach procedure shown in FIG. 6, for example, by the UE40 has moved, explain the operation when different MME (new MME) is allocated MME / SGSN that allocated to the previous Attach (Old MME / SGSN) to. Serving GW in FIG. 6 corresponds to SGW45 in FIG. PDN GW in FIG. 6 corresponds to PGW46 in FIG. PCRF in FIG. 6 corresponds to PCRF47 in FIG. HSS in FIG. 6 corresponds to HSS43 in FIG. Further, EIR in FIG 6 (Equipment Identity Register) are not shown in FIG. 2, UE identification information (e.g., ME (Mobile Equipment) Identity) is a node that manages.
[0048]
　1 to 7 of FIG. 6 in FIG. 6, TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: for Attach is similar to the process shown in procedure, a detailed description thereof will be omitted. In 7 the processing of the 1 to 6 in FIG. 6, mainly, the authentication process for the UE is performed.
[0049]
　When 7 processes 1 to 6 in FIG. 6 is completed, new new MME sends an Update the Location Request message to the HSS (8 in Fig. 6). Update Location Request message, including the IMSI of the UE. 9 and 10 of FIG. 6 in FIG. 6, TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: for Attach is similar to the process shown in procedure, a detailed description thereof will be omitted. In 9 and processing 10 of FIG. 6 in FIG. 6, mainly, the process for deleting the information about the UE that is managed in the Old MME / SGSN is performed.
[0050]
　The HSS in 8 of FIG. 6, obtains the IMSI of the UE, and identify the UE the Usage type associated with the acquired IMSI. Further, HSS from the information management device, acquires the Service ID associated with the identified UE the Usage type. If HSS and the information management apparatus is the same device, HSS, using the UE the Usage type of identified, further identifies the Service ID associated with the identified UE the Usage type.
[0051]
　HSS sends an Update the Location Ack message to the new new MME (11 in FIG. 6). Update Location Ack message includes a Service ID.
[0052]
　12 through 16 of FIG. 6 in FIG. 6, TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: for Attach is similar to the process shown in procedure, a detailed description thereof will be omitted. In 12 to 16 of FIG. 6 in FIG. 6, mainly, between the Serving GW and the PDN GW, the process of establishing a session or bearer UE uses is performed.
[0053]
　new new MME, in 11 of FIG. 6, the UE obtains the Service ID identifies the service and groups the UE belongs to use to identify the Resource ID identifying the radio resources allocated to the UE at eNodeB. Resource ID is associated with the Service ID. new new MME has determined the Resource ID, and transmits the Initial Context Setup Request message to the eNodeB (17 in FIG. 6). Initial Context Setup Request message includes a Resource ID.
[0054]
　Then, eNodeB determines whether it is possible to allocate the radio resources indicated by the Resource ID transmitted from the new new MME to the UE. For example, eNodeB, when the radio resource indicated by the Resource ID is not assigned to another UE, it may be determined that it is possible to allocate the radio resources indicated by the Resource ID transmitted from the new new MME. eNodeB, when judging that it is possible to allocate the radio resources indicated by the Resource ID transmitted from the new new MME to UE, and transmits an RRC Connection Reconfiguration message to the UE (18 in FIG. 6). RRC Connection Reconfiguration message includes an information for specifying the radio resource indicated by the Resource ID transmitted from the new new MME. Information for specifying the radio resource may be, for example, identification information such as frequency and time slot of a wireless resource. Thus, UE, the radio resource included in the RAN Slice about services utilizing is notified that assignable.
[0055]
　26 of 19 to 6 in FIG. 6, TS23.401 V13.5.0 (2015-12) Figure 5.3.2.1-1: for Attach is similar to the process shown in procedure, a detailed description thereof will be omitted. In 19 to 26 of FIG. 6 in FIG. 6 is mainly processing for notifying the information about the radio bearer to the Serving GW established between the UE and the eNodeB is executed.
[0056]
　Subsequently, the flow of Attach procedure according to the second embodiment of the present disclosure will be described with reference to FIG. 7, in the communication system shown in FIG. 2 shows a flow of processing when the Attach procedure does not complete successfully. 17 of 1 to 7 in FIG. 7 is omitted because it is similar to FIG.
[0057]
　eNodeB determines in 17 of FIG. 7, upon receiving the Initial Context Setup Request message containing the Resource ID, whether it can allocate radio resources indicated by the Resource ID to the UE.
[0058]
　In this example, eNodeB, when judging that it is impossible to allocate radio resources indicated by the Resource ID transmitted from the new new MME to UE, without sending the RRC Connection Reconfiguration message to the UE, new new the Initial Context Setup Response message and it transmits to the MME (18 in FIG. 7). The Initial Context Setup Response message includes information indicating that it can not allocate radio resources to the UE.
[0059]
　Then, new new MME via the eNodeB, the transceiver sends the Attach Reject message to the UE (19 in FIG. 7). new new MME by sending an Attach Reject message to the UE, and notifies that the Attach procedure did not complete successfully to the UE. Thus, UE, the radio resource included in the RAN Slice about services utilizing is notified that assignable.
[0060]
　Subsequently, with reference to FIG. 8, will be described UE triggered Service Request procedure flow according to the second embodiment of the present disclosure. Figure 8 is a communication system shown in FIG. 2 shows a flow of processes performed when UE triggered Service Request procedure has been successfully completed. UE a triggered Service Request procedure is, for example, a process that the UE is performed when such starts or when outgoing starts data transmission. Given that UE triggered Service Request procedure is performed, Attach procedure has been completed successfully, MME is assumed to manage the subscriber information about the UE.
[0061]
　UE triggered Service Request procedure shown in FIG. 8, TS23.401 V13.5.0 (2015-12) Figure 5.3.4.1-1: is based on the UE triggered Service Request procedure. In UE triggered Service Request procedure of FIG. 8, TS23.401 V13.5.0 (2015-12) Figure 5.3.4.1-1: For UE triggered Service Request procedure and the same processing will not be described in detail.
[0062]
　First, UE, via the eNodeB transmits the NAS Service Request message to the MME (2 in 1 and 8 in FIG. 8). MME uses the subscriber information relating to UE, and identify the Service ID associated with the UE. Then, between the UE and the MME, further, between the MME and the HSS, the authentication process for the UE is performed (3 in FIG. 8).
[0063]
　Next, MME is, S1-AP comprises a Resource ID associated with the identified Service ID: Initial Context Setup Request message and transmits to the eNodeB (4 in FIG. 8).
[0064]
　Then, eNodeB determines whether it is possible to allocate the radio resources indicated by the Resource ID transmitted from the MME to the UE. eNodeB, when judging that it is possible to allocate the radio resources indicated by the Resource ID transmitted from the new new MME to UE, for allocating radio resources indicated by the Resource ID to UE, and a Radio Bearer Establishment process (of FIG. 8 5). 6 subsequent processing in FIG. 8, TS23.401 V13.5.0 (2015-12) Figure 5.3.4.1-1: a detailed description thereof will be omitted since it is similar to the UE triggered Service Request procedure. In 6 subsequent processing in FIG. 8 is mainly processing for notifying the information about the radio bearer to the Serving GW and the PDN GW that was established between the UE and the eNodeB is executed.
[0065]
　Subsequently, the UE triggered Service Request procedure flow according to the second embodiment of the present disclosure will be described with reference to FIG. 9, in the communication system shown in FIG. 2 shows a flow of processes performed when UE triggered Service Request procedure does not complete successfully. 1 through 4 of FIG. 9 in FIG. 9 is omitted because it is similar to FIG.
[0066]
　eNodeB, in 4 of FIG. 9, S1-AP comprises a Resource ID: determines upon receiving the Initial Context Setup Request message, whether it can allocate radio resources indicated by the Resource ID to the UE.
[0067]
　In this example, eNodeB, when judging that it is impossible to allocate radio resources indicated by the Resource ID transmitted from the MME to the UE, without executing a Radio Bearer Establishment process, S1-AP: The Initial Context Setup Response message and transmits to the MME (5 in Figure 9). S1-AP: Initial Context Setup Response message includes information indicating that it can not allocate radio resources to the UE.
[0068]
　Next, MME via the eNodeB, NAS: sending a Service Reject message to the UE (6 in Fig. 9). The MME, NAS: by sending a Service Reject message to the UE, and notifies the UE triggered Service Request procedure did not complete successfully to the UE.
[0069]
　As described above, by using the communication system according to a second embodiment of the present disclosure, MME can be based on the service and belonging group to which the UE uses to identify the radio resources to be allocated to the UE. Specifically, MME can identify the radio resource included in the RAN Slice associated with the service that the UE uses. Thus, eNodeB is to UE to use the services associated with the RAN Slice, can allocate radio resources included in the RAN Slice. As a result, eNodeB may prevent assigning radio resources included in the RAN Slice associated with different service that the UE uses the service to the UE.
[0070]
　Further, MME can identify the radio resources to be allocated to the UE by using the Service ID that identifies the group to which the UE belongs. Thus, RAN Slice is to be composed from the radio resource group to be allocated to a plurality of specific groups, the radio resources allocated to different groups and groups the UE belongs, can be prevented to assign to the UE.
[0071]
　Further, eNodeB is a radio resource included in the Resource ID designated by the MME, there can be determined whether it can be assigned to the UE. Thereby, UE, when it is notified that it is impossible to allocate radio resources from eNodeB, a eNodeB that provides a service for the UE to use, reselect another eNodeB having available radio resources be able to.
[0072]
　(Third Embodiment)
　Subsequently, a description is given of the flow of processing when the Attach procedure according to the third embodiment of the present disclosure has been successfully completed. Here, mainly described processes different process flow in FIG. In the second embodiment, determining the eNodeB, whether a radio resource indicated by the Resource ID may be assigned to the UE. On the other hand, in the third embodiment determines the MME, whether a radio resource indicated by the Resource ID may be assigned to the UE.
[0073]
　The eNodeB to be periodically sent to MME the allocation state of the radio resource. That, MME is assumed to hold the allocation state of eNodeB radio resources. In this case, new new MME determines in 11 of Figure 6, when receiving the Update the Location Ack message that contains the Service ID, whether the Resource ID associated with the Service ID may be assigned to the UE. new new MME, when judging that it is possible to allocate radio resources to the UE, and executes the 12 subsequent steps in FIG. However, unlike the second embodiment, eNodeB, when receiving the Initial Context Setup Request message in 17 of Figure 6 it does not perform the process of determining whether or not it is possible to allocate radio resources to the UE.
[0074]
　Subsequently, with reference to FIG. 10, Attach procedure according to the third embodiment of the present disclosure will be described flow of processing if not completed successfully. 11 of 1 through 10 in FIG. 10 will be omitted because it is similar to that of 1 to 11 in FIG. 6 in FIG.
[0075]
　new new MME determines in 11 of FIG. 10, upon receiving the Update the Location Ack message that contains the Service ID, whether the Resource ID associated with the Service ID may be assigned to the UE. new new MME, when judging that it is impossible to allocate radio resources to the UE, without executing the 12 subsequent steps in FIG. 6, the Attach Reject message to the UE via the eNodeB (12 in FIG. 10) . new new MME by sending an Attach Reject message to the UE, and notifies that the Attach procedure did not complete successfully to the UE.
[0076]
　Then according to the third embodiment of the present disclosure, UE triggered Service Request procedure is described a flow of processing in successful. Here, mainly described processes different process flow in FIG. In the second embodiment, determining the eNodeB, whether a radio resource indicated by the Resource ID may be assigned to the UE. On the other hand, in the third embodiment determines the MME, whether a radio resource indicated by the Resource ID may be assigned to the UE.
[0077]
　The eNodeB to be periodically sent to MME the allocation state of the radio resource. That, MME is assumed to hold the allocation state of eNodeB radio resources.
[0078]
　In this case, MME, in 2 of FIG. 8, NAS: upon receiving the Service Request message, to identify the Service ID by using the subscriber information relating to UE, further identifies the Resource ID associated with the Service ID. MME determines whether it is possible to allocate the radio resources indicated by the Resource ID to the UE. The MME, when it is determined that it is possible to allocate radio resources to the UE, and perform the 4 subsequent steps in FIG. However, unlike the second embodiment, eNodeB is, S1-AP in 4 of FIG. 8: when receiving the Initial Context Setup Request message, the process of determining whether it is possible to allocate radio resources to the UE do not run.
[0079]
　Subsequently, UE triggered Service Request procedure according to the third embodiment of the present disclosure illustrating a flow of processing in not completed successfully with reference to FIG. 3 in 1 to 11 in FIG. 11 is omitted because it is similar to the third 1 to 8 in FIG.
[0080]
　The MME, in 2 of FIG. 11, NAS: upon receiving the Service Request message, to identify the Service ID by using the subscriber information relating to UE, further identifies the Resource ID associated with the Service ID. MME determines whether it is possible to allocate the radio resources indicated by the Resource ID to the UE. The MME, when it is determined that it is impossible to allocate radio resources to the UE, without executing the 4 subsequent steps in FIG. 8, NAS: 4 and Service Reject message via eNodeB sends to the UE (FIG. 11 5 in FIG. 11). The MME, NAS: by sending a Service Reject message to the UE, and notifies the UE triggered Service Request procedure did not complete successfully to the UE.
[0081]
　As described above, by using the communication system according to a third embodiment of the present disclosure, MME is a radio resource indicated by the specified Resource ID, it is possible to determine whether it can be assigned to the UE . Thereby, MME is, when it is determined that it is impossible to allocate radio resources, without performing a plurality of processes including a setting processing of a radio bearer between the eNodeB and the UE, Attach procedure and UE triggered Service Request procedure it is possible to stop. Therefore, MME can be reduced as compared when it is determined that it is impossible to allocate radio resources, the number of messages Attach procedure and UE triggered Service Request procedure and the number of messages in the second embodiment.
[0082]
　(Embodiment 4)
　Subsequently, configuration of the present disclosure exemplary communication system according to Embodiment 4 of the will be described with reference to FIG. 12. Communication system of FIG. 12 is a communication system that supports 3G wireless communication system as a radio communication system is a communication system defined as GPRS in 3GPP.
[0083]
　Communication system of FIG. 12, MS60, UTRAN61, SGSN62, GGSN63 (Gateway GPRS Support Node), HLR (Home Location Register) 64, PDN (Packet Data Network) 65, MSC (Mobile Switching Center) / VLR (Visited Location Register) and a 66 and EIR67.
[0084]
　MS60 is a term used as a generic term for a wireless terminal in 3GPP. MS, for example, may be replaced with UE. MS60 is the same configuration as the UE40 shown in FIG. UTRAN61 is a RAN using a 3G radio system as a radio access system. UTRAN61 has the RNC.
[0085]
　SGSN62 is a node that performs the mobility management and session management concerning MS 60. HLR64 is a node that manages subscriber information about the MS60. Subscriber information, including information about the services MS60 to use. GGSN63 is a node for relaying data transmitted between the MS60 and PDN65. PDN65, for example, the server device operators such as to provide a service to the MS60 managed, or may be a network or the like including a server device group.
[0086]
　MSC / VLR66 has a circuit-switched (the Circuit Switched) function is a node that manages subscriber information of the MS. EIR67 the identity of the MS (e.g., IMEI: International Mobile Equipment Identity) is a node that manages.
[0087]
　Between MS60 and UTRAN61 is, Uu reference point is defined. Between UTRAN61 and SGSN62 is, Iu reference point is defined. Between SGSN62 and GGSN63 is, Gn reference point are determined. Between SGSN62 the HLR64 is, Gr reference point is defined. Between GGSN63 and HLR64 is determined that Gc reference point. Between GGSN63 and PDN65 is, Gi reference point is defined. Between UTRAN61 and MSC / VLR66 is, Iu reference point is defined. Between SGSN62 and MSC / VLR66 is, Gs reference point is defined. Between HLR64 and MSC / VLR66 is, D reference point is defined. Between SGSN62 and EIR67 is, Gp reference point is defined.
[0088]
　UTRAN61 configuration of the wireless resources to be managed in the RNC included in is the same as FIG. That is, in FIG. 4, the radio resource group eNodeB managed, replaced by a radio resource group managed by the RNC.
[0089]
　MS60, RNC, SGSN62, HLR64, and information included in the information management apparatus, and similarly to FIG. 5. That is, replacing the UE40 in FIG 5 to MS 60, replacing the eNodeB in FIG 5 to the RNC, replacing MME42 in FIG 5 to SGSN62, replacing HSS43 in FIG 5 to the HLR64.
[0090]
　Subsequently, with Combined GPRS / IMSI Attach Procedure according to the fourth embodiment of the present disclosure will be described with reference to FIG. 13. 13, in the communication system shown in FIG. 12 shows a processing flow when Combined GPRS / IMSI Attach Procedure is successfully completed. The Combined GPRS / IMSI shown in FIG. 13 Attach Procedure is, TS23.060 V13.5.0 (2015-12) Figure 22: is based on the Combined GPRS / IMSI Attach Procedure. In A Combined GPRS / IMSI Attach Procedure of FIG. 13, TS23.060 V13.5.0 (2015-12) Figure 22: The Combined GPRS / IMSI Attach same processing as Procedure will not be described in detail.
[0091]
　Also, MS of FIG. 13 corresponds to MS60 in FIG. RAN of Figure 13 corresponds to UTRAN61 in FIG. new new SGSN in FIG. 13 corresponds to SGSN62 in FIG. old SGSN in FIG. 13, MS 60 is the SGSN that allocated in the last Combined GPRS / IMSI Attach Procedure. In Combined GPRS / IMSI Attach Procedure shown in FIG. 13, for example, by the MS60 has moved, SGSN assigned in a previous Combined GPRS / IMSI Attach Procedure (Old SGSN) and a different SGSN (new SGSN) are assigned the operation of a case will be described.
[0092]
　GGSN in Figure 13 corresponds to GGSN63 in FIG. HLR of FIG. 13 corresponds to HLR64 in FIG. new new MSC / VLR in Figure 13 corresponds to MSC / VLR66 in FIG. old MSC / VLR in Figure 13, MS 60 is the MSC / VLR assigned in a previous Combined GPRS / IMSI Attach Procedure. EIR in Figure 13 corresponds to EIR67 in FIG.
[0093]
　6 of 1 to 13 in FIG. 13, TS23.060 V13.5.0 (2015-12) Figure 22: for Combined GPRS / IMSI Attach is similar to the process shown in Procedure, a detailed description thereof will be omitted. In the processing of 6 in 1 to 13 in FIG. 13, mainly authentication for the MS is performed.
[0094]
　When 6 treatment in 1 to 13 in FIG. 13 is completed, new new SGSN sends an Update the Location Request message to the HLR (7a in Fig. 13). Update Location Request message, including the IMSI of the MS. 7b through 7e of Figure 13 in FIG. 13, TS23.060 V13.5.0 (2015-12) Figure 22: for Combined GPRS / IMSI Attach is similar to the process shown in Procedure, a detailed description thereof will be omitted. In the process of 7e and 7b to 13 of Figure 13 is mainly a process of deleting information about the MS that is managed in OldSGSN is executed.
[0095]
　The HLR, in 7a of Figure 13 obtains the IMSI of the MS, and identifies the UE the Usage type associated with the acquired IMSI. Furthermore, HLR, from the information management apparatus, acquires a Service ID associated with the identified UE the Usage type. If HLR information management device and is the same device, HLR uses the UE the Usage type of identified, further identifies the Service ID associated with the identified UE the Usage type.
[0096]
　The HLR sends the Insert Subscriber Data message to the new new SGSN (7f in Figure 13). Insert Subscriber Data message includes a Service ID.
[0097]
　8h of 7g to 13 in FIG. 13, TS23.060 V13.5.0 (2015-12) Figure 22: for Combined GPRS / IMSI Attach is similar to the process shown in Procedure, a detailed description thereof will be omitted. In 8h of 7g to 13 of Figure 13 it is mainly a process of registering the HLR to SGSN and MSC / VLR assigned in this Attach Procedure is executed.
[0098]
　Service ID has been described as included in the Insert Subscriber Data message in 7f of Figure 13, Service ID may be included in the Update the Location Ack message in 7h in FIG.
[0099]
　12 of 9 to 13 in FIG. 13, TS23.060 V13.5.0 (2015-12) Figure 22: for Combined GPRS / IMSI Attach is similar to the process shown in Procedure, a detailed description thereof will be omitted. In 9 to 12 of FIG. 13 in FIG. 13 mainly includes processing associated with the completion of the Attach Procedure is executed.
[0100]
　Subsequently, PDP Context Activation Procedure for Iu mode with be described according to the fourth embodiment of the present disclosure with reference to FIG. 14. PDP Context Activation Procedure for Iu mode shown in FIG. 14, TS23.060 V13.5.0 (2015-12) Figure 64: it is based on PDP Context Activation Procedure for Iu mode. In PDP Context Activation Procedure for Iu mode in FIG. 14, TS23.060 V13.5.0 (2015-12) Figure 64: The PDP Context Activation Procedure for Iu mode and the same processing will not be described in detail.
[0101]
　PDP Context Activation Procedure for Iu mode is, for example, processing MS is performed when such to initiate or outgoing when starting the data transmission. The assumption that PDP Context Activation Procedure for Iu mode is executed, Attach procedure has been completed successfully, SGSN is assumed to manage the subscriber information about the MS.
[0102]
　First, MS, via the RAN sends the the Activate PDP Context Request message to the SGSN (1 in FIG. 14). The SGSN, using the subscriber information of the MS, and identifies the Service ID associated with the MS. 4 in FIG. 14, TS23.060 V13.5.0 (2015-12) Figure 64: omitted PDP Context Activation Procedure for Iu mode and hence detailed similar process description. In 4 of FIG. 14, mainly a process of the MS to establish a session or bearer used between the SGSN and GGSN is performed.
[0103]
　The SGSN, the Resource ID associated with the identified Service ID, the Radio Access Bearer process, and notifies the RAN (5 in Figure 14). Furthermore, RAN determines whether a radio resource indicated by the Resource ID notified from SGSN can that can be assigned to the MS. RAN, if it is determined that the radio resource indicated by the Resource ID transmitted from the SGSN can be allocated to the MS, the Radio Access Bearer Setup process 5 in FIG. 14, allocates the radio resources indicated by the Resource ID to the MS. 6 and subsequent steps in FIG. 14, TS23.060 V13.5.0 (2015-12) Figure 64: omitted PDP Context Activation Procedure for Iu mode and hence detailed similar description. In 6 subsequent processing in FIG. 8 is mainly processing for notifying the information about the radio bearer established between the MS and the RAN to the GGSN is executed.
[0104]
　Subsequently, the flow of PDP Context Activation Procedure for Iu mode according to the fourth embodiment of the present disclosure will be described with reference to FIG. 15. Figure 15 is a communication system shown in FIG. 12, PDP Context Activation Procedure for Iu mode indicates the flow of processing when not complete successfully. 4 in 1 and 15 in FIG. 15 is omitted because it is similar to FIG. 14.
[0105]
　SGSN sends a RAB Assignment Request message including the Resource ID to RAN (7 in Fig. 15). RAN determines in 7 of 15, upon receiving the RAB Assignment Request message including the Resource ID, whether it is possible to be able to allocate the radio resources indicated by the Resource ID to the MS.
[0106]
　RAN, when judging that it is impossible to allocate radio resources indicated by the Resource ID transmitted from the SGSN to the MS, without establishing a radio bearer between the the MS, and transmits a RAB Assignment Response message to the SGSN (Figure 7 of 15).
[0107]
　Then, SGSN, in order to remove the PDP Context between the GGSN, which is set at 4 in FIG. 15, between the GGSN, to receive the Delete PDP Context Request / Response messages (8 in FIG. 15).
[0108]
　Then, SGSN via RAN, sending a the Activate PDP Context Reject message to the MS (9 in Figure 15). SGSN by sending the Activate PDP Context Reject message to the MS, and notifies that the PDP Context Activation Procedure for Iu mode is not completed successfully to the MS.
[0109]
　Subsequently, MS Initiated Service Request Procedure using GN / Gp with be described according to the fourth embodiment of the present disclosure with reference to FIG. 16. MS Initiated Service Request Procedure using GN / Gp shown in FIG. 16, TS23.060 V13.5.0 (2015-12) Figure 50: is based on the MS Initiated Service Request Procedure using GN / Gp. In MS Initiated Service Request Procedure using GN / Gp in FIG. 16, TS23.060 V13.5.0 (2015-12) Figure 50: The MS Initiated Service Request Procedure using GN / Gp similar process, detailed description thereof is omitted .
[0110]
　Figure 16 is a communication system of FIG. 12, MS Initiated Service Request Procedure using GN / Gp indicates a flow of processing in the case of successful. MS Initiated Service Request Procedure using GN / Gp is, for example, processing MS is performed when such to initiate or outgoing when starting the data transmission. The assumption that MS Initiated Service Request Procedure using GN / Gp is ​​executed, Attach procedure has been completed successfully, SGSN is assumed to manage the subscriber information about the MS.
[0111]
　16 will be described as RNC having the UTRAN61 a RAN in FIGS. 13 to 15. 1 in FIG. 16, TS23.060 V13.5.0 (2015-12) Figure 50: a detailed description thereof will be omitted since it is similar to the process shown in MS Initiated Service Request Procedure using GN / Gp.
[0112]
　Then, MS transmits a Service Request message to the SGSN via the RNC (2 in Figure 16). The SGSN, using the subscriber information on the MS, and identifies the Service ID associated with the MS. Then, between the MS and the RNC, between the RNC and the SGSN, further, between the SGSN and the HLR, the authentication processing for the MS is performed (3 in FIG. 16).
[0113]
　Then, SGSN is a Radio Access Bearer Assignment Request message including the Resource ID associated with the identified Service ID and transmits to the RNC (4 in Figure 16).
[0114]
　Then, RNC determines whether a radio resource indicated by the Resource ID transmitted from the SGSN can be allocated to the MS. The RNC, if it is determined that the radio resource indicated by the Resource ID transmitted from the SGSN can be allocated to the MS, in order to allocate the radio resources indicated by the Resource ID to the MS, and transmits a Radio Bearer Setup message (in FIG. 16 5). 6 subsequent processing of FIG. 16, TS23.060 V13.5.0 (2015-12) Figure 50: a detailed description thereof will be omitted since it is similar to the MS Initiated Service Request Procedure using GN / Gp.
[0115]
　Subsequently, MS Initiated Service Request Procedure using GN / Gp with be described according to the fourth embodiment of the present disclosure with reference to FIG. 17. Figure 17 is a communication system of FIG. 12, MS Initiated Service Request Procedure using GN / Gp indicates the flow of processing when not complete successfully.
[0116]
　4 of 1 to 17 of Figure 17 is omitted 4 and is similar in 1 to 16 in FIG. 16. RNC determines whether it is possible to allocate the radio resources indicated by the Resource ID transmitted from the SGSN in 4 of FIG. 17 to the MS. If the RNC determines that it is not possible to allocate the radio resources indicated by the Resource ID transmitted from the SGSN to the MS, without sending a Radio Bearer Setup message to the MS, the Radio Access Bearer Assignment Response message to SGSN sends (Fig. 5 of 17). Then, SGSN via the RNC, sends a Service Reject message to the MS (6 in Fig. 17). SGSN by sending a Service Reject message to the MS, and notifies that the MS Initiated Service Request Procedure using GN / Gp did not complete successfully to the MS.
[0117]
　As described above, by using the communication system according to the fourth embodiment of the present disclosure, similar to the case of using the EPS, RAN or the RNC, RAN associated with a different service and service the MS available the radio resource included in the Slice can be prevented to assign to the MS.
[0118]
　Furthermore, SGSN can identify the radio resources to be allocated to the MS using a Service ID for identifying a group to which the MS belongs. Thus, RAN Slice is to be composed from the radio resource group to be allocated to a plurality of specific groups, the radio resource which the MS is assigned to a group different from a group to which they belong can be prevented to assign to the MS.
[0119]
　Further, RAN or the RNC, a radio resource included in the Resource ID designated by the SGSN, it is possible to determine whether it can be assigned to the MS. Thereby, MS, when it is notified that it is impossible to allocate radio resources from RAN, a RAN that provides a service MS utilizes, reselect another RAN with available wireless resources be able to.
[0120]
　(Embodiment 5)
　Then according to the fifth embodiment of the present disclosure, PDP Context Activation Procedure for Iu mode will be described a flow of processing in successful. Here, mainly described processes different process flow in FIG. 14. In the fourth embodiment, determining the RAN, whether a radio resource indicated by the Resource ID may be assigned to the MS. On the other hand, in the fifth embodiment, determining the SGSN, whether a radio resource indicated by the Resource ID may be assigned to the MS.
[0121]
　RAN is to be periodically sent to SGSN the allocation state of the radio resource. That, SGSN is assumed to hold the allocation state of the radio resources of the RAN.
[0122]
　In this case, SGSN, in 1 of FIG. 14, upon receiving the the Activate PDP Context Request message, to identify the Service ID by using the subscriber information relating to MS, further identifies the Resource ID associated with the Service ID. SGSN determines whether it is possible to allocate the radio resources indicated by the Resource ID to the MS. SGSN, when judging that it is possible to allocate radio resources to the MS, and executes the 4 subsequent steps in FIG. 14. However, RAN, in 5 of 14, does not execute the process of determining whether or not it is possible to allocate radio resources to the MS.
[0123]
　Subsequently, PDP Context Activation Procedure for Iu mode according to the fifth embodiment of the present disclosure illustrating a flow of processing in not completed successfully with reference to FIG. 1 in Figure 18 is omitted because it is similar to one in FIG. 14.
[0124]
　The SGSN, in 1 of FIG. 18, upon receiving the the Activate PDP Context Request message, to identify the Service ID by using the subscriber information relating to MS, further identifies the Resource ID associated with the Service ID. SGSN determines whether it is possible to allocate the radio resources indicated by the Resource ID to the MS. SGSN, when judging that it is impossible to allocate radio resources to the MS, without executing the 4 subsequent steps in FIG. 14, and transmits the the Activate PDP Context Reject message via the RAN to MS (2 in Fig. 18) . SGSN by sending the Activate PDP Context Reject message to the MS, and notifies that the PDP Context Activation Procedure for Iu mode is not completed successfully to the UE.
[0125]
　Then according to the fifth embodiment of the present disclosure, MS Initiated Service Request Procedure using GN / Gp will be described a flow of processing in successful. Here, mainly described processes different process flow in FIG. 16. In the fourth embodiment, determining the RAN, whether a radio resource indicated by the Resource ID may be assigned to the MS. On the other hand, in the fifth embodiment, determining the SGSN, whether a radio resource indicated by the Resource ID may be assigned to the MS.
[0126]
　RAN is to be periodically sent to SGSN the allocation state of the radio resource. That, SGSN is assumed to hold the allocation state of the radio resources of the RAN.
[0127]
　In this case, SGSN, in 2 of FIG. 16, upon receiving the Service Request message, to identify the Service ID by using the subscriber information relating to MS, further identifies the Resource ID associated with the Service ID. SGSN determines whether it is possible to allocate the radio resources indicated by the Resource ID to the MS. SGSN, when judging that it is possible to allocate radio resources to the MS, and executes the 3 subsequent steps in FIG. 16. However, RAN, in 4 of 16, does not execute the process of determining whether or not it is possible to allocate radio resources to the MS.
[0128]
　Subsequently, MS Initiated Service Request Procedure using GN / Gp according to the fifth embodiment of the present disclosure illustrating a flow of processing in not completed successfully with reference to FIG. 3 in 1 to 19 in FIG. 19 will be omitted because it is similar to 3 of 1 to 16 in FIG. 16.
[0129]
　The SGSN in 2 of FIG. 19, upon receiving the Service Request message, to identify the Service ID by using the subscriber information relating to MS, further identifies the Resource ID associated with the Service ID. SGSN determines whether it is possible to allocate the radio resources indicated by the Resource ID to the MS. SGSN, when judging that it is impossible to allocate radio resources to the MS, without executing the 4 subsequent steps in FIG. 16, it sends a Service Reject message via the RNC to the MS (4 in Figure 19). SGSN by sending a Service Reject message to the MS, and notifies that the MS Initiated Service Request Procedure using GN / Gp did not complete successfully to the UE.
[0130]
　As described above, by using the communication system according to a fifth embodiment of the present disclosure, SGSN is a radio resource indicated by the specified Resource ID, it is possible to determine whether it can be assigned to the UE . Thereby, SGSN is, when it is determined that it is impossible to allocate radio resources, without performing a plurality of processes including a setting processing of a radio bearer between the MS and the RAN (RNC), Attach procedure, PDP Context Activation Procedure for Iu mode, and it is possible to stop the MS Initiated Service Request Procedure using GN / Gp. Therefore, SGSN is in when it is determined that it is impossible to allocate radio resources, Attach procedure, PDP Context Activation Procedure for Iu mode, and MS Initiated Service Request Procedure the number of messages in the using GN / Gp can be reduced.
[0131]
　Then the following were described in several of the embodiments described above, the core node 10, the base station 20, an example of the configuration of the radio terminal 30 will be described. Figure 20 is a block diagram showing a configuration example of the base station 20. Referring to FIG. 20, the base station 20 includes an RF transceiver 1001, a network interface 1003, a processor 1004, and memory 1005. RF transceiver 1001 performs an analog RF signal processing to communicate with the UEs. RF transceiver 1001 may include a plurality of transceivers. RF transceiver 1001 is coupled to antenna 1002 and the processor 1004. RF transceiver 1001 receives the modulated symbol data (or OFDM symbol data) from the processor 1004, generates a transmission RF signal and provides a transmit RF signal to the antenna 1002. Also, RF transceiver 1001 to generate a baseband received signal based on the reception RF signal received by an antenna 1002, and supplies it to the processor 1004.
[0132]
　Network interface 1003 is used to communicate with a network node (eg, core node 10). Network interface 1003 may include, for example, a network interface card that complies with the IEEE 802.3 series (NIC).
[0133]
　The processor 1004, performs data plane processing and control plane processing including digital baseband signal processing for wireless communication. For example, in the case of LTE and LTE-Advanced, a digital baseband signal processing by the processor 1004 may include MAC layer, and the signal processing of the PHY layer.
[0134]
　Processor 1004 may include multiple processors. For example, the processor 1004 is a modem processor (eg, DSP) to perform the digital baseband signal processing, and a protocol stack processor for performing control plane processing may include (eg, CPU or MPU).
[0135]
　Memory 1005 is constituted by a combination of volatile and nonvolatile memory. Memory 1005 may include a physically independent plurality of memory devices. Volatile memory may be, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. The non-volatile memory, a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. Memory 1005 may include a storage that is remotely located from the processor 1004. In this case, the processor 1004 may access the memory 1005 via the I / O interfaces that are not network interface 1003 or illustrated.
[0136]
　Memory 1005 may store software modules (computer program) including instructions and data for processing by the base station 20 which is described in several embodiments above. In some implementations, the processor 1004, by executing the software modules from the memory 1005 may be configured to perform processing of the remote node 10 which is described in the above embodiment.
[0137]
　Figure 21 is a block diagram showing a configuration example of the wireless terminal 30. Radio Frequency (RF) transceiver 1101 performs an analog RF signal processing for communicating with the base station 20. Analog RF signal processing performed by the RF transceiver 1101 includes a frequency up-conversion, the frequency down-conversion, and amplification. RF transceiver 1101 is coupled to antenna 1102 and the base band processor 1103. That, RF transceiver 1101 receives the modulated symbol data (or OFDM symbol data) from the baseband processor 1103, generates a transmission RF signal and provides a transmit RF signal to the antenna 1102. Also, RF transceiver 1101 to generate a baseband received signal based on the reception RF signal received by an antenna 1102, and supplies it to the baseband processor 1103.
[0138]
　Baseband processor 1103 performs control plane processing and digital baseband signal processing for wireless communication (data plane processing). Digital baseband signal processing, (a) data compression / decompression, (b) segmentation / concatenation of data, generation / decomposition of (c) transmission format (transmission frame), (d) transmission channel coding / decoding , including generation of (e) modulation (symbol mapping) / demodulation, and OFDM symbol data by (f) Inverse Fast Fourier Transform (IFFT) (baseband OFDM signal). On the other hand, the control plane processing, layer 1 (eg, transmission power control), Layer 2 (eg, radio resource management, and hybrid automatic repeat request (HARQ) process), and layer 3 (eg, attach, mobility and call management including communication management signaling) related.
[0139]
　For example, in the case of LTE and LTE-Advanced, a digital baseband signal processing by a baseband processor 1103, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, includes a signal processing of the MAC layer, and a PHY layer But good. Further, the control plane processing by baseband processor 1103, Non-Access Stratum (NAS) protocol, RRC protocol, and may include a process of MAC CE.
[0140]
　Baseband processor 1103, a modem processor that performs digital baseband signal processing (eg, Digital Signal Processor (DSP)) and protocol stack processor for performing control plane processing (eg, Central Processing Unit (CPU), or Micro Processing Unit it may include (MPU)). In this case, the protocol stack processor for performing control plane processing may be shared with an application processor 1104 which will be described later.
[0141]
　The application processor 1104, CPU, MPU, also referred to as a microprocessor or processor cores. The application processor 1104 may include a plurality of processors (multiple processor cores). The application processor 1104, a memory 1106 or illustrated which do not result system read from the memory a software program (Operating System (OS)) and various application programs (e.g., call application, WEB browser, a mailer, a camera operation application, music playback by running the application), to implement the various functions of the wireless terminal 30.
[0142]
　In some implementations, as indicated by the dashed line (1105) in FIG. 21, the baseband processor 1103 and an application processor 1104 may be integrated on a single chip. In other words, the baseband processor 1103 and an application processor 1104 may be implemented as a single System on Chip (SoC) device 1105. SoC devices, sometimes referred to as system Large Scale Integration (LSI) or chipset.
[0143]
　Memory 1106 is a volatile memory or nonvolatile memory, or a combination thereof. Memory 1106 may include a physically independent plurality of memory devices. Volatile memory may be, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. The non-volatile memory, a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. For example, memory 1106, a baseband processor 1103, an application processor 1104, and may contain accessible external memory device from SoC1105. Memory 1106, within baseband processor 1103, within the application processor 1104, or may include an integrated chip memory device within SoC1105. Furthermore, memory 1106 may include a memory in the Universal Integrated Circuit Card (UICC).
[0144]
　Memory 1106 may store software modules (computer program) including instructions and data for processing by the wireless terminal 30 that has been described in several embodiments above. In some implementations, the baseband processor 1103 or the application processor 1104, by executing the software modules from the memory 1106, may be configured to perform processing of the wireless terminal 30 that is described in the above embodiment good.
[0145]
　Figure 22 is a block diagram showing a configuration example of the core node 10. Referring to FIG. 22, the center node 20 includes a network interface 1201, a processor 1202, and memory 1203. Network interface 1201 is used to communicate with a network node (eg, base station 20). Network interface 1201 may include, for example, a network interface card that complies with the IEEE 802.3 series (NIC).
[0146]
　The processor 1202 reads and executes the software from the memory 1203 (a computer program), the process of core node 10 which is described with reference to a sequence diagram and flow chart in the embodiment described above. The processor 1202, e.g., a microprocessor, MPU, or a CPU. Processor 1202 may include multiple processors.
[0147]
　The processor 1202, performs data plane processing and control plane processing including digital baseband signal processing for wireless communication. For example, in the case of LTE and LTE-Advanced, a digital baseband signal processing by the processor 1004, PDCP layer may include a signal processing of the RLC layer and the MAC layer. Further, the signal processing by the processor 1202 may include signal processing GTP-U · UDP / IP layer in the X2-U interface and S1-U interface. The control plane processing by the processor 1004, X2AP protocol may include a process of S1-MME protocol and the RRC protocol.
[0148]
　Processor 1202 may include multiple processors. For example, the processor 1004 is a modem processor that performs digital baseband signal processing (eg, DSP), X2-U interface and S1-U interface of the GTP-U · UDP / IP layer processor for performing signal processing (eg, DSP), and a protocol stack processor for performing control plane processing (eg, may include a CPU or MPU).
[0149]
　Memory 1203 is constituted by a combination of volatile and nonvolatile memory. Memory 1203 may include a storage that is remotely located from the processor 1202. In this case, the processor 1202 may access the memory 1203 via the I / O interface (not shown).
[0150]
　In the example of FIG. 22, the memory 1203 is used for storing software modules. Processor 1202, these software modules that run from the memory 1203, it is possible to perform the processing of the core node 10 described in the above embodiment.
[0151]
　As described with reference to FIGS. 20 to 22, the base station 20 in the above embodiment, each processor in the wireless terminal 30 and the core node 10, for performing the algorithm described with reference to the drawings in the computer executing one or more programs including instructions.
[0152]
　In the above example, the program may be stored using a non-transitory computer readable media of various types (non-transitory computer readable medium), it can be supplied to the computer. Non-transitory computer readable media include with various types of entities (tangible storage medium). Examples of non-transitory computer readable media include magnetic storage media (such as floppy disks, magnetic tape, hard disk drive), magneto-optical recording medium (e.g. optical disk), CD-ROM (Read Only Memory), CD-R, CD-R / W, a semiconductor memory (e.g., a mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access memory)) includes a. The program may be provided to a computer using a temporary computer readable media of various types (transitory computer readable medium). Examples of transitory computer readable media include electric signals, optical signals, and electromagnetic waves. Transitory computer readable media, wired communication path such as electrical wires and optical fibers, or via a wireless communication path can provide the program to a computer.
[0153]
　The present disclosure is not limited to the above embodiments, but can be appropriately changed without departing from the spirit. The present disclosure may be implemented in combination in the form of respective embodiments as appropriate.
[0154]
　Having described the present disclosure with reference to the embodiment, the present disclosure is not intended to be limited by the foregoing. The present disclosure of the configuration and details may be various modifications that those skilled in the art within the scope of disclosure can be understood.
[0155]
　This application claims priority based on Japanese Patent Application No. 2016-058260 filed on March 23, 2016, the entire disclosure of which is incorporated herein.
[0156]
　Some or all of the above embodiments, can be described as the following notes, not limited to the following.
　(Supplementary Note 1)
　and a determination unit for determining a radio resource to be allocated in accordance with the service provided to the wireless terminal,
　a plurality of radio resources, the base station which manages each RAN Slice associated with the service, determined in the determination unit comprising a communication unit, a for transmitting resource identification information indicating a radio resource
core node.
　(Supplementary Note 2)
　The determination unit may
　indicate the service that the wireless terminal is to use, and service identification information that is uniquely identified in the mobile core network, and manages in association with the resource identification information, terminal identification of the wireless terminal from a management device that manages in association with information and the service identification information, and acquires the service identification information, core node according to Appendix 1.
　(Supplementary Note 3)
　as the resource identification information, the service identification information that is uniquely identified in the mobile core network is used, the core node according to Appendix 2.
　(Supplementary Note 4)
　The determination unit
　based on the availability of radio resources in the base station, determines whether radio resources exist to be allocated to the wireless terminal in a RAN Slice to provide a service which the wireless terminal is to use to core node according to any one of Supplementary Notes 1 to 3.
　(Supplementary Note 5)
　The communication unit
　when the wireless resource to be allocated to the wireless terminal in the determination unit determines that there is no, refuse show that through the base station to the wireless terminal can not be allocated radio resources to send a message, the core node according to Appendix 4.
　(Supplementary Note 6)
　The plurality of radio resources, a management unit which manages each RAN Slice associated with the service,
　transmitted from the core node, the resource identification information indicating a radio resource to be allocated in accordance with the service provided to the wireless terminal a communication unit that receives,
　and a resource allocator for a radio resource allocated to the wireless terminal shown in the resource identification information,
　the base station.
　(Supplementary Note 7)
　The resource allocation unit,
　depending on the availability of radio resources, and determines whether to allocate a radio resource indicated in the resource identification information to the wireless terminal, a base station according to Appendix 6.
　(Supplementary Note 8)
　If the radio resources allocated in the resource allocation unit to the radio terminal is determined not to exist, further comprising a communication unit for transmitting the rejection message indicating that it can not allocate radio resources to the wireless terminal, the base station according to Appendix 7.
　(Supplementary Note 9)
　and receiving portion in which a plurality of base station receives a respective broadcast information to be transmitted,
　from among said plurality of base stations, including RAN Slice identification information indicating the RAN Slice for providing a service to which the host terminal to use wireless terminal comprising: a determining unit, a deciding to connect with the base station that has transmitted the broadcast information.
　(Supplementary Note 10)
　The determination unit
　when the base station which transmitted the broadcast information including a RAN Slice identification information indicating the RAN Slice to provide Use service there are a plurality of radio waves of the radio waves output from the respective base station determining a base station to be connected based on the intensity, the wireless terminal according to supplementary note 9.
　(Supplementary Note 11)
　The determining unit
　when receiving a rejection message indicating that it is impossible to allocate radio resources from the base station, transmitting broadcast information including a RAN Slice identification information indicating the RAN Slice to provide Use service from a plurality of base stations have been, it decides to connect the determined the base station and the different base station, the wireless terminal according to supplementary note 9 or 10.
　(Supplementary Note 12)
　determines the radio resources to be allocated depending on the service provided to the wireless terminal,
　resources indicating a plurality of radio resources, the base station which manages each RAN Slice associated with the service, the determined radio resources transmitting the identification information, communication method.
　(Supplementary Note 13)
　a plurality of radio resources, manage each RAN Slice associated with the service,
　transmitted from the core node receives the resource identification information indicating a radio resource to be allocated in accordance with the service provided to the wireless terminal,
　allocating a radio resource indicated in the resource identification information to the wireless terminal, the radio resource allocation method.
　(Supplementary Note 14)
　a plurality of base stations to receive a respective broadcast information to be transmitted,
　from among said plurality of base stations, has transmitted the broadcast information including a RAN Slice identification information indicating the RAN Slice to provide Use service It determines to connect the base station, the base station selection method.
　(Supplementary Note 15)
　determines the radio resources to be allocated depending on the service provided to the wireless terminal,
　resources indicating a plurality of radio resources, the base station which manages each RAN Slice associated with the service, the determined radio resources program for executing that transmits the identification information to the computer.
DESCRIPTION OF SYMBOLS
[0157]
　10 core node
　12 communication unit
　14 determination unit
　20 base station
　22 communication section
　24 control section
　26 resource assignment unit
　30 the wireless terminal
　40 UE
　41
　E-UTRAN
　42 MME
　43 HSS
　44 SGSN
　45 SGW
　46 PGW
　47 PCRF
　48 UTRAN 49 GERAN
　50 Operator's IP Services
　MS 60
　61 UTRAN
　62 SGSN
　63 GGSN
　64 HLR
　65 PDN
　66 MSC
　/ VLR 67
　EIR 71 communication unit
　72 RAN Slice availability determining unit
　73 the destination RAN Slice selection unit
　81 control unit
　82 communication unit

The scope of the claims
[Requested item 1]
　Determining means for determining a radio resource to be allocated in accordance with the service provided to the wireless terminal,
　a plurality of radio resources, the base station which manages each RAN Slice associated with the service, the radio resources determined in said determining means and a communication means for transmitting the resource identification information indicating the
core node.
[Requested item 2]
　It said determining means
　the wireless terminal indicates a service to use, and service identification information that is uniquely identified in the mobile core network, and manages in association with the resource identification information, the terminal identification information of the wireless terminal service from a management device that manages in association with the identification information to obtain the service identification information, core node according to claim 1.
[Requested item 3]
　As the resource identification information, the service identification information that is uniquely identified in the mobile core network is used, the core node according to claim 2.
[Requested item 4]
　It said determining means,
　based on the availability of radio resources in the base station, the wireless terminal determines whether radio resources are present to be allocated to the wireless terminal in a RAN Slice to provide a service to use, claim core node according to any one of 1 to 3.
[Requested item 5]
　It said communication means,
　when the radio resource to be allocated in the determination unit to the radio terminal is determined not to exist, and transmits a rejection message indicating that it is impossible to allocate radio resources to the wireless terminal via the base station , core node according to claim 4.
[Requested item 6]
　A plurality of radio resources, a management unit which manages each RAN Slice associated with the service,
　transmitted from the core node, the communication means for receiving a resource identification information indicating a radio resource to be allocated in accordance with the service provided to the wireless terminal When,
　and a resource allocation means for allocating a radio resource indicated in the resource identification information to the wireless terminal,
　a base station.
[Requested item 7]
　It said resource allocation means,
　in accordance with the usage of radio resources and determines whether to allocate a radio resource indicated in the resource identification information to the wireless terminal, a base station according to claim 6.
[Requested item 8]
　If the radio resource to be allocated to the wireless terminal in the resource allocation means is determined not to exist, further comprising a communication means for transmitting a rejection message indicating that it is impossible to allocate radio resources to the wireless terminal, in claim 7 the base station according.
[Requested item 9]
　Receiving means for receiving each of the broadcast information, a plurality of base stations transmit
　transmission from the plurality of base stations, broadcast information including a RAN Slice identification information indicating the RAN Slice for providing a service to which the host terminal to use wireless terminal and a determining means for determining to connect with to have the base station.
[Requested item 10]
　It said determining means,
　when the base station which transmitted the broadcast information including a RAN Slice identification information indicating the RAN Slice to provide Use service there are multiple, based on the field intensity of radio waves output from the respective base station determining a base station to be connected, the wireless terminal according to claim 9.
[Requested item 11]
　It said determining means,
　from said base station when receiving a rejection message indicating that it is impossible to allocate radio resources, a plurality of which has transmitted the broadcast information including a RAN Slice identification information indicating the RAN Slice to provide Use service from the base station, it determines to connect the determined the base station and the different base station, the wireless terminal according to claim 9 or 10.
[Requested item 12]
　Determining the radio resources to be allocated depending on the service provided to the wireless terminal,
　it transmits a plurality of radio resources, the base station which manages each RAN Slice associated with the service, resource identification information indicating the determined radio resources to, communication method.
[Requested item 13]
　A plurality of radio resources, manage each RAN Slice associated with the service,
　transmitted from the core node receives the resource identification information indicating a radio resource to be allocated in accordance with the service provided to the wireless terminal,
　the resource identification information allocating radio resources to the wireless terminal shown in, the radio resource allocation method.
[Requested item 14]
　Receiving a respective notification information in which a plurality of base stations transmit,
　from the plurality of base stations, connected to the base station that has transmitted the broadcast information including a RAN Slice identification information indicating the RAN Slice to provide Use service determining, the base station selection method to.
[Requested item 15]
　Determining the radio resources to be allocated depending on the service provided to the wireless terminal,
　it transmits a plurality of radio resources, the base station which manages each RAN Slice associated with the service, resource identification information indicating the determined radio resources non-transitory computer readable medium which stores a program to be executed by a computer to.